Cisco Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Cisco Upgrading the Cisco ONS 15454 SDH to Release 9.2.1

 

 

Retour à l'accueil, cliquez ici

Upgrading the Cisco ONS 15454 SDH to Release 9.2.1

 

Downloads

 

 

Voir également :

[TXT]

 Cisco-Telephones-IP-..> 01-Jun-2013 10:28  2.4M  

[TXT]

 Cisco-UCS-C200-Serve..> 01-Jun-2013 10:27  2.6M  

[TXT]

 Cisco-ONS-15454-DWDM..> 01-Jun-2013 10:27  4.8M  

[TXT]

 Cisco-ONS-15454-Refe..> 01-Jun-2013 10:26  3.0M  

[TXT]

 Cisco-Unified-IP-Pho..> 01-Jun-2013 08:01  2.3M  

[TXT]

 Cisco-Meraki-Cloud-C..> 01-Jun-2013 07:55  2.3M  

[TXT]

 Cisco-IPSec-Negotiat..> 01-Jun-2013 07:52  2.1M  

[TXT]

 Cisco-ASA-5500.htm      01-Jun-2013 07:45  2.1M  

[TXT]

 CiscoSecurityApplian..> 01-Jun-2013 07:35  2.0M  

[TXT]

 Cisco-Manuel-du-tele..> 03-Apr-2013 15:45  2.0M  

[TXT]

 Cisco-836-Router-and..> 03-Apr-2013 15:38  1.6M  

[TXT]

 Cisco-837-Router-and..> 03-Apr-2013 15:38  1.6M  

[TXT]

 Cisco-Manuel-du-tele..> 03-Apr-2013 15:37  1.8M  

[TXT]

 Cisco-ASR-9000-Serie..> 04-Sep-2012 10:04  4.1M  

[TXT]

 Cisco-ASR-9000-Serie..> 04-Sep-2012 09:44  3.5M  

[TXT]

 Cisco-ASR-9000-Serie..> 04-Sep-2012 09:40  3.0M  

[TXT]

 Cisco-ASR-9000-Serie..> 04-Sep-2012 09:34  2.9M  

[TXT]

 Cisco-ASR-9000-Serie..> 04-Sep-2012 09:29  2.7M  

[TXT]

 Cisco-ASR-9000-Serie..> 04-Sep-2012 09:24  3.7M  

[TXT]

 CiscoPrimeNetworkCon..> 04-Sep-2012 09:17  3.0M  

[TXT]

 XML-Schema-Object-Do..> 03-Sep-2012 18:55  2.1M  

[TXT]

 XML-Schema-Object-Do..> 03-Sep-2012 18:35  4.9M  

[TXT]

 Cisco-IOS-XR-XML-API..> 03-Sep-2012 18:29  4.7M  

[TXT]

 Cisco-ASR-9000-Serie..> 03-Sep-2012 17:25  5.0M  

[TXT]

 Cisco-ASR-9000-Serie..> 03-Sep-2012 17:20  5.7M  

[TXT]

 Cisco-ASR-9000-Serie..> 03-Sep-2012 17:15  5.9M  

[TXT]

 Cisco-IOS-XR-Carrier..> 03-Sep-2012 17:10  4.5M  

[TXT]

 Cisco-ASR-9000-Serie..> 03-Sep-2012 17:07  4.3M  

[TXT]

 Cisco-Introduction-t..> 03-Sep-2012 16:57  4.2M  

[TXT]

 Cisco-Security-Appli..> 03-Sep-2012 16:54  4.2M  

[TXT]

 liendocumentationcis..> 28-Jan-2012 10:29  5.2K  

[TXT]

 white_paper_c11-4621..> 28-Jan-2012 10:24   55K  

[TXT]

 cisco.htm               26-Jan-2012 17:35  1.5M  

[TXT]

 liendocumentationcis..> 26-Jan-2012 17:32  5.2K  

[TXT]

 liensdocumentationci..> 26-Jan-2012 17:31  5.0K  

[TXT]

 CiscoASA5500.htm        01-Jan-2012 22:26  3.3M  

[TXT]

 ciscoVPNClientAdmini..> 01-Jan-2012 12:56  223K  

[TXT]

 Cisco7600SeriesRoute..> 01-Jan-2012 12:51  2.7M 
Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 This document explains how to upgrade Cisco ONS 15454 SDH Cisco Transport Controller (CTC), using the advanced Timing, Communications, and Control (TCC2) or advanced Timing, Communications, and Control Plus (TCC2P),Timing Communications ControlThree (TCC3),Transport Node Controller (TNC), or Transport Shelf Controller (TSC) card. To understand the supported software upgrade paths, refer to the Software Upgrade Compatibility, on page 2. Note The TSC and TNC cards are the control cards installed on ONS 15454 M2 and ONS 15454 M6 shelves. • Software Upgrade Compatibility, page 2 • Errorless Upgrades and Exceptions, page 4 • Document Procedures, page 6 • NTP-U487 Preparing to Upgrade to a New Release, page 7 • NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, page 11 • NTP-U489 Upgrade the Cisco ONS 15454 SDH Software , page 12 • NTP-U490 Install Public-Key Security Certificate, page 22 • NTP-U491 Restore the Previous Software Load and Database, page 23 • NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 Card, page 27 • NTP-U510 Upgrade the TSC Card to the TNC Card, page 29 • NTP-U493 Upgrade to the ONS 15454 Software Using TL1, page 30 • Related Documentation, page 36 • Obtaining Documentation and Submitting a Service Request, page 37 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 1Software Upgrade Compatibility This table describes the possible upgrade paths supported from Releases 4.1.x, 4.5.x, 4.6.x, 4.7.x, 5.0.x, 6.0.x, 6.2.x, 7.0.x, 7.2.x, 8.0.x, 8.5.x, 9.0.x, 9.1.x, 9.2 to Release 9.2.1 in the MSPP (Multiservice Provisioning Platform) platform. Releases 8.6.1, 8.5.x, 9.0.1, 9.1.0, 9.2.0, 9.2.0.3 can be upgraded to Release 9.2.1 in Cisco ONS 15454 SDH MSPP. Note Table 1: Supported Software Upgrades for the Cisco ONS 15454 SDH MSPP Release Upgrade Options 4.5.x2 , 4.6.x2 , 4.7.x2 , 5.0.x2 , 6.0.x2 , 6.2.x2 , 7.0.x2 , 7.2.x2 , 8.0.x2 , 8.5.x2 4.1x1 4.6.x2 , 4.7.x2 , 5.0.x2 , 6.0.x2 , 6.2.x2 , 7.0.x2 , 7.2.x2 4.5.x 4.7.x2 , 5.0.x2 , 6.0.x2 , 6.2.x2 , 7.0.x2 , 7.2.x2 4.6.x 5.0.x2 , 6.0.x2 , 6.2.x2 , 7.0.x2 , 7.2.x2 4.7.x 6.0.x2 , 6.2.x2 , 7.0.x2 , 7.2.x2 , 8.0.x2 , 8.5.x2 5.0.x , 9.1 6.2.x2 , 7.0.x2 , 7.2.x2 , 8.0.x2 , 8.5.x2 6.0.x 7.2.x2 , 8.0.x2 , 8.5.x2 6.2.x , 9.0.x, 9.1, 9.2 7.2.x2 , 8.0.x2 , 8.5.x2 7.0.x , 9.0.x, 9.1, 9.2, 9.2.1 5 8.0.x2 , 8.5.x2 7.2.x , 9.0.x, 9.1 9.2 8.5.x2 8.0.x , 9.0.x, 9.1, 9.2 8.5.x2 , 9.0.x4 , 9.14,5 , 9.25 8.5.x , 9.2.1 3 9.0.x 9.0.x, 9.1, 9.2, 9.2.1 9.1.x 9.1.x, 9.2, 9.2.1 9.2.0 9.2.1 6 1 Before upgrading from R4.1.x or later, make sure that the TCC2P cards are installed. 2 Support is limited because Cisco has either announced End-of-Life of the release, or the version you are upgrading to is a non-preferred release. 3 R8.5.4 and R8.6.1 can be upgraded to R9.2.1.5. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 2 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Software Upgrade Compatibility4 ForE1 payload,R8.5.4 toR9.0 orR9.1 upgrade is notsupported.Also, during an upgrade fromR8.5.4 toR9.0 orR9.1,theE1 traffic islost and can be recovered by applying and releasing terminal or facility loopback on the E1 ports that carries traffic. 5 Not supported for R8.5.1 release. 6 R7.0.4 and R 9.2.0 can be upgraded to R9.2.1.4. This table describes the possible upgrade paths supported from Releases 4.1.x, 4.5.x, 4.6.x, 4.7.x, 5.0.x, 6.0.x, 6.2.x, 7.0.x, 7.2.x, 8.0.x, 8.5.x, 9.0.x, 9.1.x, 9.2 to Releases 9.2.1 inMSTP (MultiserviceTransport Platform). Releases 8.6.1, 8.5.x, 9.0.1, 9.0.0, 9.1.0, 9.2.0, 9.2.0.2, 9.2.0.3 can be upgraded to Release 9.2.1 in CiscoONS 15454 SDH MSTP. Release 9.2.0, 9.2.0.2, and 9.2.0.3 can be upgraded to Release 9.2.1 in Cisco ONS 15454 SDH M2 and Cisco ONS 15454 M6 SDH MSTP. Table 2: Supported Software Upgrades for the Cisco ONS 15454 SDH MSTP Release Upgrade Options 4.5.x8 , 4.6.x8 , 4.7.x8 , 5.0.x8 , 6.0.x8 , 6.2.x8 , 7.0.x8 , 7.2.x8 , 8.0.x8 , 8.5.x8 4.1x7 4.6.x8 , 4.7.x8 , 5.0.x8 , 6.0.x8 , 6.2.x8 , 7.0.x8 , 7.2.x8 4.5.x 4.7.x8 , 5.0.x8 , 6.0.x8 , 6.2.x8 , 7.0.x8 , 7.2.x8 4.6.x9 5.0.x8 , 6.0.x8 , 6.2.x8 , 7.0.x8 , 7.2.x8 4.7.x 6.0.x8 , 6.2.x8 , 7.0.x8 , 7.2.x8 , 8.0.x8 , 8.5.x8 5.0.x , 9.1, 9.2 6.2.x8 , 7.0.x8 , 7.2.x8 , 8.0.x8 , 8.5.x8 6.0.x 7.2.x8 , 8.0.x8 , 8.5.x8 6.2.x , 9.0.x, 9.1, 9.2 7.2.x8 , 8.0.x8 , 8.5.x8,10 , 9.0.x10 , 9.1.x10 , 9.210 , 9.2.110,11 7.0.x 8.0.x8 , 8.5.x8 7.2.x , 9.0.x, 9.2, 9.2.1 8.5.x8 8.0.x , 9.0.x, 9.1, 9.2 8.5.x8 , 9.0.x, 9.112 , 9.212 8.5.x , 9.2.1 9.0.x 9.0.x, 9.1, 9.2, 9.2.1 9.1.x 9.1.x, 9.2, 9.2.1 9.2.x 9.2.1 7 Before upgrading from R4.1.x or later, make sure that the TCC2P cards are installed. 8 Support is limited because Cisco has either announced End-of-Life of the release, or the version you are upgrading to is a non-preferred release. 9 If a direct upgrade from R4.6.x to R8.0.0 or later is performed on ONS 15454 nodes containing TXP and MXP cards, CTC does not display the cards in card view. Therefore, when upgrading from R4.6.x to R8.0.0 and later, a step upgrade to R7.0.7 is recommended before upgrading to R8.0 and later. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 3 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Software Upgrade Compatibility10 To upgrade a multi-shelf node from R7.0.0 or R7.0.1 to R8.5.x, R9.0.x, R9.1.x, R9.2, or R9.2.1 perform a step upgrade to R8.0.0 before upgrading to the destination version. R7.0.2 through R7.0.5 can be upgraded directly to R8.5.x, R9.0.x, R9.1.x, R9.2, or R9.2.1. 11 To upgrade a multi-shelf node from R7.0.6 to R9.2.1, perform a two step upgrade to R8.00 or R8.51 and then to R9.2.1. 12 Upgrade is not supported for R8.5.1. All other 8.5.x releases are supported. Errorless Upgrades and Exceptions This section describes important information to be aware of before you begin the upgrade process: • When a node installed with GE_XP, GE_XPE, 10GE_XP, or 10GE_XPE cards configured with REP or LACP is upgraded, traffic loss may occur. This traffic loss is due to reconvergence when the cards soft reset during the upgrade process. • The MXP_MR_2.5 and MXPP_MR_2.5 cards automatically download a new field-programmable gate array (FPGA) image during an upgrade from a software release prior to R7.0 to R9.2.1.x.The upgrades forDWDMconfigurations are expected to be errorlesswith the following exceptionsif nodes are running MXP_MR_2.5 and MXPP_MR_2.5 cards: • If Y-cable protection is not provisioned, the data path incurs a traffic hit of up to 10 seconds or less. • IfY-cable protection is provisioned on cardsrunningFiber Channel (FC) payloads,traffic switches away from the card downloading the new FPGA causing the FC link to be reinitialized. • If Y-cable protection is provisioned on cards running Gigabit Ethernet (GE) payloads, there is no traffic interruption. • During R7.x and R8.x upgrades to later releases, user data channel (UDC) traffic passing through the OSC-CSM and OSCM cards incur a traffic hit for a few milliseconds. • During an upgrade from R 8.5.x, R 9.0, or R 9.1 to R 9.2.x or later releases, a loss of Gigabit Ethernet traffic of up to one second is incurred. This traffic loss occurs when auto-negotiation is disabled on the far end of the ADM-10G card. If the node has a path protection circuit, a path protection switchover occurs. To avoid this switchover during an upgrade, perform the path protection lockout procedure before upgrading the software. Note, however, this procedure does not help avoid hits in the flow of traffic. • During a revert procedure, if Gigabit Ethernet traffic is not flowing or GFP alarms are present on an ADM-10G card, hard-reset the ADM-10G card to ensure smooth traffic flow. • In R9.2.1.x, the CE-1000-4 card incurs a traffic hit of 30 seconds during activation and FPGA card upgrade. The upgraded CE-1000-4 card also incurs a traffic hit of 110 seconds if the software is subsequently reverted, because the FPGA is downgraded during the revert. When upgrading from R5.0 to R6.0 or later in enhanced card mode on nodes running an FC_MR-4 card, ahitlesssoftwareupgrade isnotpossible.Thisisbecause theFPGA mustbeupgradedtosupportdifferential delay in enhanced mode. However, the upgrade is hitless in the line rate mode. Note The following tables are define where errorless upgrades or exceptions can occur. The following table applies to nodes equipped with XC-VXC-10G cards Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 4 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Errorless Upgrades and ExceptionsCard Type Expected Traffic Effect E3 Errorless E1-42 Errorless DS31 Errorless STMn Errorless MRC-12 Errorless ML-Series Ethernet Traffic hits 3 to 8 minutes (approximately) G-Series Ethernet Errorless (except as noted) E-Series and CE-SeriesEthernet Errorless The following table applies to nodes equipped with XC-VXL-10G or XC-VXL-2.5G cards Card Type Expected Traffic Effect E3 Errorless E1-42 Errorless DS31 Errorless STMn Errorless MRC-12 Errorless ML-Series Ethernet Traffic hits 3 to 8 minutes (approximately) G-Series Ethernet Errorless (except as noted) E-Series and CE-Series Ethernet Errorless The following table applies to nodes equipped with XC10G cards. Table 3: XC10G Card Type Expected Traffic Effect E3 Errorless STM1E Errorless E1-42 Errorless Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 5 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Errorless Upgrades and ExceptionsCard Type Expected Traffic Effect STMn Errorless E-Series Ethernet Traffic hits 3 to 8 minutes (approximately) ML-Series Ethernet Traffic hits 3 to 8 minutes (approximately) G-Series Ethernet Errorless (except as noted) Document Procedures Procedures in this document must be performed in consecutive order unless noted otherwise. Ensure that the procedure is completed for each node in a given network. If you are new to upgrading the ONS 15454 SDH, make a printed copy of this document and use it as a checklist. Each non-trouble procedure (NTP) is a list of steps designed to accomplish a specific procedure. Follow the steps untilthe procedure is complete. If you need more detailed instructions, refer to the detail-level procedure (DLP) specified in the procedure steps. Throughout this guide, NTPs are referred as “procedures” and DLPs as “tasks.” Every reference to a procedure includes its NTP number, and every reference to a task includes its DLP number. The DLP (task) supplies additional task details to support the NTP. The DLP lists numbered steps that lead you through completion of a task. Some steps require that equipment indications be checked for verification. When a proper response is not obtained, a trouble clearing reference is provided. This section lists the document procedures (NTPs). Turn to a procedure for applicable tasks (DLPs). 1 NTP-U487 Preparing to Upgrade to a New Release, on page 7—This procedure contains critical information and tasks that you must read and complete before beginning the upgrade process. 2 NTP-U488 BackUp the CiscoONS15454SDHSoftwareDatabase, on page 11—Complete the database backup to ensure that you have preserved your node and network provisioning in the event that you need to restore them. 3 NTP-U489 Upgrade the Cisco ONS 15454 SDH Software , on page 12—Complete this procedure to complete the upgrade. 4 NTP-U490 Install Public-Key Security Certificate, on page 22— Complete this procedure to be able to run the ONS 15454 Software. 5 NTP-U491 Restore the Previous Software Load and Database, on page 23— Complete this procedure if you want to return to the previous software load you were running before activating the new release. 6 NTP-U493Upgrade to theONS 15454 SoftwareUsingTL1, on page 30— Complete this procedure only if you want to upgrade to a new release using Transaction Language (TL1). Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 6 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Document ProceduresNTP-U487 Preparing to Upgrade to a New Release This procedure provides critical information checks and tasks you must complete before beginning an upgrade to R9.2.1.x. Purpose Tools/Equipment Cisco ONS 15454 SDH nodes "DLP-G46Log into CTC" in the "ConnectthePC andLog into theGUI" document. Prerequisite Procedures Required/As Needed Required Onsite/Remote Onsite or remote Security Level Superuser Procedure Step 1 Before you begin, make sure that information related to your site, for example, date, street address, site phone number, and dialup number are stored in a safe and accessible location. The data will be useful during and after the upgrade. Step 2 Read the release notes of the release you are upgrading to. Visit http://www.cisco.com/en/US/products/hw/ optical/ps2006/prod_release_notes_list.html to download the release notes. Disable APC before upgrading from R7.0.x to R8.0.x or later and enable it after the upgrade is complete. Note Step 3 Complete the task, DLP-U544 Verify CTC Workstation Requirements, on page 7. Step 4 Complete the task, DLP-U545 Verify Common Control Cards, on page 9. Step 5 When you have completed the tasks for this section, proceed with the procedure, NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11. Stop. You have completed this procedure. DLP-U544 Verify CTC Workstation Requirements This task lists PC or UNIX workstation hardware and software requirements. Perform this task before upgrading the workstation to run the software. Purpose Tools/Equipment PC or UNIX workstation Prerequisite Procedures None Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 7 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U487 Preparing to Upgrade to a New ReleaseRequired/As Needed Required Onsite/Remote Onsite or remote Security Level Superuser Procedure Step 1 Ensure that your workstation meets the following requirements: Area Requirements Notes Pentium III/IV or a faster processor — UltraSPARC-III or faster processor for UNIX workstation Processor (PC only) RAM 384 MB/1 GB RAM or more — Minimum of 190/250 MB of — available disc space Hard drive • Releases prior to R8.5.x are not supported on Windows Vista or Windows 7 Use the latest patch or service pack released by the OS vendor. Check with the vendor for the latest patch or service pack. Note • Releases prior to R9.2.1 are not supported on Apple Mac OS X PC. CTC cannot be launched on a Mac OS-X PC using a browser. Use the CTC cache installer to launch CTC on a MAC OS-X PC. The CTC cache installer prepopulates the CTC cache with the required jar files. Either of the following: • Windows: ◦Windows 98 ◦Windows NT 4.0 ( with SP 6a) ◦Windows 2000 Professional ◦Windows Server 2003 ◦Windows Server 2008 ◦Windows XP Professional ◦Windows Vista ◦Windows 7 • UNIX workstation ◦Solaris Version 8 ◦Solaris Version 9 ◦Solaris Version 10 • Apple Mac OS X Operating System Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 8 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U544 Verify CTC Workstation RequirementsArea Requirements Notes You can check the JRE version in your browser window after entering the node IP address in the URL window under Java Version. Tip For important information about CTC backward compatibility affected by your choice of JRE version, see the Readme.txt or Readme.html file on the software CD. Note To install JRE 1.6, the Java Policy file, or the online help, see the installation instructionsin the Cisco ONS 15454 DWDM Configuration Guide. Note Java Plug-in 1.4.2 Java Plug-in 5.0 JRE 1.6 Java Plug-in 1.6 Java Policy file Java Runtime Environment Either of the following: — • Windows ◦Internet Explorer 6.x ◦Internet Explorer 7.x ◦Internet Explorer 8.x ◦Netscape 7.x • UNIX Workstation ◦Mozilla 1.7 ◦Netscape 7.x • Apple Mac OS X ◦Safari Web browser Step 2 Return to your originating procedure (NTP). DLP-U545 Verify Common Control Cards This task lists card-slot requirements of common control cards , and cross connect cards (XC-VXL-10G, XC-VXL-2.5G, XC-VXC-10G, XC10G cards ) in a node. Purpose Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 9 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U545 Verify Common Control CardsTools/Equipment PC or UNIX workstation with CTC installed Prerequisite Procedures Install the TCC2, TCC2P, TCC3, TNC, or TSC control cards. Required/As Needed Required Onsite/Remote Onsite or remote Security Level Superuser The TCC2P card is an enhanced version of the TCC2 card and includes enhancements such as Ethernet security features and 64K composite clock BITS timing. The TCC3 card is an enhanced version of the TCC2P card and includes enhancements such as increased memory size and compact flash space. Note Note TCC2P or TCC3 cards act as TCC2 cards in releases prior to Software R6.0. Note The TNC and TSC controller cards are installed on the ONS 15454 M2 and ONS 15454 M6 shelves. TheTCC2 card fails to bootwhen it is added as a standby card to a node containing an activeTCC2P card configured in the secure mode. Caution Dense wavelength division multiplexing (DWDM) nodes need only control cards installed during the upgrade. Note Procedure Step 1 Make sure that the control cards and cross connect cards are installed in the appropriate slots on all the nodes in the network and on both the slots as indicated in the following section: • ONS 15454 SDH shelf - ◦TCC2, TCC2P or TCC3 cards are in Slots 7 and 11 ◦XC-VXL-10G, XC-VXL-2.5G, XC-VXC-10G, XC10G cards are in Slots 8 and 10 • ONS 15454 M6 shelf —TNC or TSC card in Slots 1 and 8 • ONS 15454 M2 shelf—TNC or TSC card is in Slot 1 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 10 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U545 Verify Common Control CardsStep 2 Repeat Step 1 for every node in the network. Step 3 Return to your originating procedure (NTP). NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database This procedure retains all configuration data for your network before performing the upgrade. Purpose Tools/Equipment PC or UNIX workstation • "DLP-G46Log into CTC" in the "Connect the PC andLog into the GUI" document. • NTP-U487 Preparing to Upgrade to a New Release, on page 7 Prerequisite Procedures Required/As Needed Required Onsite/Remote Onsite or remote Security Level Superuser Note (MS-SPRing nodes only) The database must be backed up when using an MS-SPRing. Procedure Step 1 In the node view, click the Maintenance>Database tabs. Step 2 In the database pane, click the Backup button. The Database Backup dialog box is displayed. Step 3 Click Browse. Navigate to the local PC directory or network directory and type a database name using the IP address of the node to upgrade (such as database15454SDH010107.db) in the File Name field and click OK. To overwrite an existing file, click Yes. Step 4 When the backup is complete, click OK. Step 5 Repeat Steps 1 through 5 for each node in the network. Step 6 (Optional) It is recommended that you manually log critical information by either writing it down, printing screens, or by exporting the data to an appropriate format, as applicable. Use the following table to determine the information that should be logged. Information Record Data Here IP address of the node Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 11 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U488 Back Up the Cisco ONS 15454 SDH Software DatabaseInformation Record Data Here Node name Timing settings DCC13 connections—list all optical ports with active DCCs User IDs of all users, including at least one Superuser Inventory—A print screen of the Inventory window Active TCC2/TCC2P/TCC3 card Slot 7 or Slot 11 Active XC-VXL-10G, XC-VXL-2.5G, XC10G, or XC-VXC-10G Slot 8 or Slot 10 card Active TNC/TSC (Cisco ONS 15454 M6) cards Slot 1 and Slot 8 Active TNC/TSC (Cisco ONS 15454 M2) card Slot 1 Network information—Aprint screen of the Provisioning tab in the network view Current configuration (MS-SPRing, linear, etc.)— A print screen, as needed List all protection groups in the system—A print screen of the Protection group window List alarms—A print screen of the Alarm window List circuits—A print screen of the Circuit window 13 DCC=data communications channel Stop. You have completed this procedure. NTP-U489 Upgrade the Cisco ONS 15454 SDH Software This procedure upgrades the CTC software to R9.2.1.x and must be performed on all nodes, or groups of nodes to be upgraded. Purpose Tools/Equipment PC or UNIX workstation Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 12 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U489 Upgrade the Cisco ONS 15454 SDH SoftwareNTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 Prerequisite Procedures Required/As Needed Required Onsite/Remote Onsite or remote Security Level Superuser Caution Do not perform maintenance or provisioning activities during the activation task. During a parallel upgrade,when end-to-end circuitsin anML-Seriesresilient packet ring (RPR) are present across multiple nodes, traffic resumes only after all the nodes in these circuits complete activation Note Several alarms are raised during the upgrade due to software incompatibility.However. these alarms clear after the upgrade is complete. Note Several alarms are raised on the ML-Series cards since they undergo a hard reboot during the upgrade (cold restart is rarely used). These alarms clear after the upgrade is complete. On the ML-Series port the LOA, TPTFAIL, and VCG DOWN alarms are raised. On the paths traversed by the ML-Series circuits the SD-P, SF-P, and PDI-P alarms are raised. Note During the upgrade of R8.0 or R8.5.x to a later release, if path protection circuits of type UPSR_DRI or 2waydcwas createdonanADM-10Gcard, anyexistingsoftwareprovisioningonthe cardislost.Therefore, make sure that these path protection circuit types are not present before you upgrade to a later release. Note The ADM-10G card does not support adding drops to existing Synchronous Transport Signal (STS) circuits. Therefore, when upgrading from R8.0 to a later release, delete any STS circuits with multiple drops on the ADM-10G card. Note When upgrading to R9.0 or later, the TCC2P or TCC3 cards undergo hard reboot. During this period, the standby TCC2P or TCC3 card displays the “NP” state. This is expected behavior and has no impact on the system functionality. Note Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 13 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U489 Upgrade the Cisco ONS 15454 SDH SoftwareProcedure Step 1 Insert the Cisco ONS 15454 SDH Software CD into the workstation CD-ROM drive (or otherwise acquire access to the software) to begin the upgrade process. Inserting the software CD activates the CTC Java Setup Wizard. Use the setup wizard to install the components or click Cancel to continue with the upgrade. Note Step 2 (MS-SPRing nodes only) The database must be backed up prior to locking the MS-SPRing. See NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 procedure for details. Step 3 (MS-SPRing nodes only) Complete the DLP-U547 Perform a MS-SPRing Lockout, on page 16 task. Step 4 Complete the DLP-U546 Download the ONS 15454 SDH Software, on page 15 task for all nodes to be upgraded. Step 5 Complete the DLP-U548 Activate the New Cisco ONS 15454 SDH Software, on page 17 task for all nodes to be upgraded. Only one node can be activated at a time. During a parallel upgrade, activate another node as soon as the controller cards reboot successfully. To perform parallel upgrade remotely, wait five minutes for the controller cards to reboot completely. Note Step 6 Complete the DLP-U549 Delete Cached JAR Files, on page 20 task, as necessary. If the Cisco ONS 15454 SDH software is downloaded again after a version is activated, a revert to the previous version cannot be performed. Caution Step 7 (Optional) If you wish to ensure that a software revert to the previous software release is no longer possible, complete the DLP-U546 Download the ONS 15454 SDH Software, on page 15 task or all nodes, or groups of nodes you are upgrading a second time. Step 8 Complete the DLP-U550 Remove the MS-SPRingLockout, on page 21 task for all MS-SPRing nodes in the network. Leave the MS-SPRing in the lockout state until you have finished activating all nodes. Note Step 9 For MS-SPRing nodes only, complete the DLP-U551 Set the Date and Time, on page 22 task for nodes that are not using Simple Network Time Protocol (SNTP). Step 10 If you need to return to the software and database you had before activating Software R9.2.1.x, proceed with the NTP-U491 Restore the Previous Software Load and Database, on page 23 procedure. When you upgrade a TCC2 card to a TCC2P, the SFTWDOWN alarm can be raised and cleared more thanoncebefore the softwaredownloadis complete.For example,whenyouremove the standby TCC2 card in Slot 11 and replace it with a TCC2P card, the SFTWDOWN alarm occurs within moments of this replacement. It can briefly clear and then occur again before the alarm is finally cleared at the end of the upgrade process. Note When you upgrade a TCC2P card to a TCC3, the SFTWDOWN alarm can be raised and cleared more thanoncebefore the softwaredownloadis complete.For example,whenyouremove the standby TCC2P card in Slot 11 and replace it with a TCC3 card, the SFTWDOWN alarm occurs within moments of this replacement. It can briefly clear and then occur again before the alarm is finally cleared at the end of the upgrade process Note Step 11 To back up the Software R9.2.1.x database for the working software load, see NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 procedure in order to preserve the database for the current release. After the upgrade is complete, the date and time in CTC is reset. Stop. You have completed this procedure. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 14 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U489 Upgrade the Cisco ONS 15454 SDH SoftwareDLP-U546 Download the ONS 15454 SDH Software This task downloads R9.2.1.x software to the ONS 15454 SDH nodes prior to activation. Purpose Tools/Equipment PC or UNIX workstation NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 Prerequisite Procedures Required/As Needed Required Onsite/Remote Onsite or remote Security Level Maintenance user or higher The TCC2/TCC2P/TCC3/TNC/TSC cardcontainsflash memorywithtwopartitions—workingandprotect (backup). An upgrade downloads the software to the protect (backup) partition of the flash memory on both the standby and active TCC2/TCC2P/TCC3/TNC/TSC cards. This download is not traffic affecting because the active software continues to run in the primary RAM location. The software can therefore be downloaded at any time. Note To download and upgrade the software usingTL1,see theNTP-U493Upgrade to theONS15454Software Using TL1, on page 30 procedure. Note Procedure Step 1 From CTC View menu, choose Go to Network View. Step 2 Make sure that the alarm filter is turned off. To do so, complete the following: a) Click the Filter tool located at the lower-left side of the window. The Alarm Filter dialog box appears. b) Click to select any check box that is not selected in the Show Severity section of the General tab. Step 3 Resolve any outstanding alarms. To view alarms for all the nodes in the network, click the Alarms tab. The SWFTDWN alarm is raised on the standby and active TCC2, TCC2P, TCC3, TNC, or TSC cards during software download. The alarms clears as soon as the download is complete. Note Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 15 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U546 Download the ONS 15454 SDH SoftwareStep 4 From the CTC View menu, choose Go to Home View to go to the node view. Step 5 Click the Maintenance> Software tabs. Step 6 Click the Download button. The Download Selection dialog box appears. Step 7 Locate the software files on the ONS 15454 SDH software CD or on your hard drive. Step 8 To open the Cisco ONS 15454 SDH folder, choose the file with the PKG extension and click Open. Step 9 From the list of compatible nodes, select the nodes where the software must be downloaded. Itisrecommendedthatsimultaneoussoftwaredownloadsonthe sectiondata communications channel (SDCC) be limited to eight nodes at a time, using the central node to complete the download. If more than eight concurrent software downloads are selected at a time, it is placed in a queue. Note Step 10 Click OK. The Download Status column monitors the progress of the download. Step 11 Return to your originating procedure (NTP). DLP-U547 Perform a MS-SPRing Lockout This task performs a MS-SPRing lockout. If you have MS-SPRing provisioned, you must perform this task before beginning the upgrade. Purpose Tools/Equipment PC or UNIX workstation NTP-U488 BackUp the CiscoONS 15454 SDHSoftwareDatabase, on page 11 Prerequisite Procedures Required/As Needed Required for MS-SPRing only Onsite/Remote Onsite or remote Security Level Maintenance user or higher (MS-SPRingnodesonly)Thedatabase mustbebackedupprior tolockingtheMS-SPRing.SeeNTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 procedure for details. Note During the activation,MS-SPRing spans are not protected.You must leave theMS-SPRing in the lockout state until you have finished activating all nodes in the ring. Ensure that the lockout is removed after activation. Note Note To prevent ring or span switching, perform the lockout on both the east and west spans of each node. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 16 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U547 Perform a MS-SPRing LockoutProcedure Step 1 In node view, click the Maintenance tab, then click the MS-SPRing button. Step 2 For each of the MS-SPRing trunk (span) cards (STM-4, STM-16, STM-64, MRC-2.5G-12 ,MRC-12, STM64-XFP), perform the following steps: a) Next to the trunk card row, click the East Switch column to show the shortcut menu. b) From the menu options, choose Lockout Protect. c) Click the Apply button. d) In the same row, click the West Switch column to show the shortcut menu. e) From the menu options, choose Lockout Protect. f) Click the Apply button. Ignore any Default K alarms that occur on the protect VC4 time slots during this lockout period. Note Certain MS-SPRing-related alarms might be raised following activation of the first node in the ring. The followingalarms,if raised, arenormal, andshouldnot cause concern.Theyclearuponcompletion of the upgrade, after all nodes have been activated. Note • MSSP-OOSYNC (MN) • RING-MISMATCH (MJ) • APSCDFLTK (MN) • MSSP-RESYNC (NA) Step 3 Return to your originating procedure (NTP). DLP-U548 Activate the New Cisco ONS 15454 SDH Software Purpose This task activates the software on each node in the network. Tools/Equipment PC or UNIX workstation DLP-U546 Download the ONS 15454 SDH Software, on page 15 DLP-U547 Perform a MS-SPRing Lockout, on page 16 (if required) Prerequisite Procedures Required/As Needed Required Onsite/Remote Onsite or remote Security Level Superuser Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 17 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U548 Activate the New Cisco ONS 15454 SDH SoftwareIt is recommended that the first node that is activated be connected via LAN. This ensures that the new CTC JAR files download to the workstation as quickly as possible. If a node is provisioned to have no LAN access, the value is overridden in the case of node isolation. Additionally, if the node is not reachable, the LAN access is turned on. It is recommended that you avoid node isolation. Note G-Series cards (G1000-4 and G1K-4) purchased prior to R7.2 incur a traffic hit of 2 to 3 minutes per card during activation and FPGA card upgrade. When the software is reverted, the upgraded cards incur a traffic hit of 2 to 3 minutes since the FPGA is also downgraded. Caution Procedure Step 1 If CTC is not already started, start CTC. Step 2 Record the IP address of the node. The IP address can be obtained either on the LCD or on the upper left corner of the CTC window. Step 3 Make sure that the alarm filter is turned off. To do so, complete the following: a) Click the Filter tool at the lower-left side of the window. The Alarm Filter dialog box appears. b) Click to select any check box that is not selected in the Show Severity section of the General tab. Make sure that all cards that are part of a 1+1 or Y-cable protection group must be active on the working card of the protection group and no protection switches are occurring. Step 4 Ensure that traffic carrying protect cards are in a standby state. To do so, complete the following: a) In the node view, click Maintenance > Protection tabs. b) Select each protection group listed and viewthe active orstandby status of each card in theSelectedGroup area. Step 5 In shelf view, click the Maintenance > Software tabs. Step 6 Verify that the version in the Protect Version column is R9.2.1.x. Step 7 Click the Activate button. The Activate dialog box displays a warning message. Step 8 Click Yes to proceed with the activation. An Activation Successful message indicates that the software is successfully activated. Step 9 Click OK. The connection between CTC and the node is lost and CTC displays the Network view. Step 10 After activating the node, the software upgrade reboot occurs as follows: • All the common control cards (TCC2, TCC2P, TCC3, TNC, or TSC) in the node reboot beginning with the standby card.As soon as the standby card reboots, it signals the active card to reset as a standby card and the standby card transitions to active. • While the secondcommoncontrol cardreboots,the standbycross-connect cardbeginsrebooting, followed by the active cross-connect card. • The E-Series Ethernet cards reset simultaneously. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 18 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U548 Activate the New Cisco ONS 15454 SDH Software• Protect cardsin theY-cable protection group boot next,in the order thatthe protection groupwas created. • Next,the traffic cards,G-SeriesEthernet cards, CE-SeriesEthernet cards, andML-SeriesEthernet cards boot consecutively, in ascending order of slot number with the exception of E1-42 protect cards. E1-42 cards reset before any peer working cards.. • The SYSBOOT alarm is raised as soon as the common control cards and cross-connect card reset. This alarm clears when all the cards reset. The activation process can take up to 30 minutes, depending on the number of cards installed in the node. After the common control cards finish resetting and all associated alarms clear, you can safely proceed to the next step. (If you are upgrading remotely and cannot see the nodes, wait for 5 minutes for the process to complete, then check to ensure that related alarms have cleared before proceeding.) During the software upgrade, a reset alarm is raised on all the cards. When upgrading from Release 6.0, 6.1, 6.2, 6.2.x, 7.0, 7.0.x, 7.2, or 7.2.x to 8.0, a MANRESET alarm is raised on standby TCC cards and anAUTORESETalarm in allthe other cards.However, from R8.0,theMANRESETalarm is not raised and the AUTORESET alarm is raised on all the cards. Note Step 11 In CTC, choose File > Exit. Step 12 Start CTC again. Step 13 Click the Setting button in the CTC launcher window. The CTC launcher settings dialog box appears. Step 14 Click the Delete Cache button in the Cache tab. A warning message is displayed. Step 15 Click Yes to proceed with the cache deletion. Step 16 Click OK to close the CTC launcher settings dialog box. Step 17 (Optional) Run the CacheLoader pre-caching utility.This logs you into CTC at a faster pace after an upgrade. However, you must log into nodes running releases prior to Software R4.6. If you do not plan to run the pre-caching utility, it is recommended that the first node you activate be a LAN-connected node. This ensures that the new CTC JAR files download to your workstation as quickly as possible. Note Perform the following steps to run the Cache Loader. a) Load the Software CD into your CD-ROM drive. If the directory of the CD does not open automatically, open it. b) Double-click the setup.exe file to run the Installation Wizard. The CTC Installation Wizard dialog box appears. c) Click the Next button. The Setup Options dialog box appears. d) Choose Custom, and click the Next button. The Custom Options dialog box appears. e) Click to select Cisco Transport Controller, and CTC JAR files (deselect any other preselected options) and click the Next button. A confirmation dialog box appears. f) Click the Next button again. The CTC Cache Loader pre-caches the JAR files to your workstation, displaying a progress status box. g) When the utility finishes, click OK, and in the wizard, click Finish. Step 18 Click the Launch CTC button. The new CTC applet loads. The login window is displayed. Step 19 Type the user name and password and click Login. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 19 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U548 Activate the New Cisco ONS 15454 SDH SoftwareCompleteSteps 11 through 19 only after upgrading the first node in a network.Thisis because cached files must be removed from your workstation only once. For the remaining nodes, you will still be disconnected and moved to the network view during the node reboot. After the reboot is complete, CTC restores connectivity to the node. Note Step 20 Return to your originating procedure (NTP). DLP-U549 Delete Cached JAR Files Purpose This task deletes cached JAR files. Tools/Equipment PC or UNIX workstation Prerequisite Procedures None Required/As Needed You need to complete this task after you activate the first network node. Onsite/Remote Onsite or remote Security Level Maintenance user or higher Whenever the CTC software is upgraded or reverted, make sure that the browser and hard drive cache files are cleared. Note Procedure Step 1 Delete cached files from your browser directory. In Netscape: a) Select Edit > Preferences. Click the Advanced tab and click the Cache button. b) Click the Clear Memory Cache button, and click OK. c) Click the Clear Disk Cache button, and click OK twice. In Microsoft Internet Explorer: a) Select Tools > Internet Options. The Internet Options dialog box appears. b) Click the General tab, and then click the Delete Files button. c) Select the Delete all offline content check box. d) Click OK twice. Step 2 Close the browser. Cached JAR files cannot be deleted from the hard drive untilthe browser is closed.Other applications that use JAR files must also be closed. Note Step 3 On Windows systems, delete cached files from your workstation in this location: Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 20 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U549 Delete Cached JAR FilesC:\Documents and Settings\username\Application Data\Cisco\CTC Step 4 Reopen the browser. You should now be able to connect to CTC. Step 5 Return to your originating procedure (NTP). DLP-U550 Remove the MS-SPRing Lockout Thistaskremoves aMS-SPRinglockout. Release the span lockouts on all MS-SPRing nodes after the new software load is activated on all nodes. Purpose Tools/Equipment PC or UNIX workstation DLP-U548Activate theNewCiscoONS15454SDH Software, on page 17 Prerequisite Procedures Required/As Needed Required for MS-SPRing Onsite/Remote Onsite or remote Security Level Maintenance Procedure Step 1 In CTC node view, click the Maintenance tab, then click the MS-SPRing button. Step 2 For each of the MS-SPRing trunk (span) cards (STM-4, STM-16, STM-64, ,MRC-2.5G-12 ,MRC-12, STM64-XFP), perform the following steps: a) Next to the trunk card row, click the West Switch column to show the shortcut menu. b) From the shortcut menu, click Clear. When removing a lockout, be sure to apply your changes each time you choose the Clear option. If you try to select Clear for more than one lockout at a time, you risk traffic loss on the first ring switch. Note c) In the same row, click the East Switch column to show the shortcut menu. d) From the shortcut menu, click Clear. Step 3 Repeat this task as many times as necessary to remove all MS-SPRing span lockouts on the upgrade nodes. Step 4 Return to your originating procedure (NTP). Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 21 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U550 Remove the MS-SPRing LockoutDLP-U551 Set the Date and Time This task sets the date and time. If you are not using SNTP, the upgrade procedure can cause theDate/Time setting to change.Perform thistask to reset the date and time at each node. Purpose Tools/Equipment PC or UNIX workstation Prerequisite Procedures None Required/As Needed As needed Onsite/Remote Onsite or remote Security Level Superuser Note If you are using SNTP, this task is not applicable. Procedure Step 1 In CTC node view, click the Provisioning > General tabs. Step 2 Set the correct date and time. Click Apply . Step 3 Repeat Steps 1 and 2 on all the remaining nodes. Step 4 Return to your originating procedure (NTP). NTP-U490 Install Public-Key Security Certificate This procedure installs the ITU Recommendation X.509 public-key security certificate.The public-key certificate is required to run Software R4.1 or later. Purpose Tools/Equipment None Thisprocedure isperformedwhenlogginginto CTC. You cannot perform it at any other time. Prerequisite Procedures This procedure is required to run ONS 15454 Software R4.1 or later. Required/As Needed Onsite/Remote Onsite or remote Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 22 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U551 Set the Date and TimeSecurity Level Provisioning or higher Procedure Step 1 Log into CTC. Step 2 If the Java Plug-in Security Warning dialog box appears, choose one of the following options: • Grant This Session—Installs the public-key certificate on the PC only for the current session. After the session ends, the certificate is deleted. This dialog box appears at the next login into ONS 15454 SDH. • Deny—Denies permission to install the certificate. If this option is chosen, login into the ONS 15454 SDH. is denied. • Grant always—Installs the public-key certificate and does not delete it after the session is over. It is recommended to use this option. • View Certificate—The public-key security certificate is displayed. After the completion of the security certificate dialog boxes, the web browser displays information about the Java and system environments. If this is the first login, a CTC downloading message appears while CTC files are downloaded to the computer.The process can take several minutes,if itisthe firsttime.After the download, the CTC Login dialog box appears. Step 3 Returntothe software anddatabaseyouhadbefore activatingthe9.2.1.xsoftware,proceedwiththeNTP-U491 Restore the Previous Software Load and Database, on page 23 procedure. Stop. You have completed this procedure. NTP-U491 Restore the Previous Software Load and Database This procedure returnsto the software and database provisioning thatwas present before 9.2.1.x was activated. The software load and database cannot be restored to the previous version if the software on both the working and protect cards were upgraded to 9.2.1.x. Purpose Tools/Equipment PC or UNIX workstation "DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document. NTP-U487 Preparing to Upgrade to a New Release, on page 7 NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 NTP-U489 Upgrade the Cisco ONS 15454 SDH Software , on page 12 PrerequisiteProcedures Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 23 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U491 Restore the Previous Software Load and DatabaseRequired/As Needed As needed Onsite/Remote Onsite or remote Security Level Superuser Tasks to revert to a previous load are not part of the upgrade, and are provided here as a convenience to those wishing to perform a revert after an upgrade. If you have successfully performed all necessary procedures up to this point, you have finished the software upgrade. Note If a node is set to secure, dual-IP mode, the database information is overwritten with this configuration and cannot be reverted to single-IP repeater mode. Caution The defaults database files (db files) used to restore the basic configuration on a single non-multishelf node are shipped along with the standard 9.2.1.x software release package. For a multishelf set-up, the multishelf configuration must be unprovisioned to restore the basic configuration using the defaults database file.Also,the database backup from a multishelfsystem can be used to restore the same multishelf system. Note Procedure Step 1 (MS-SPRing nodes only) The database must be backed up prior to locking the MS-SPRing. See NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 procedure for details. Step 2 (MS-SPRing nodes only) Complete the DLP-U547 Perform a MS-SPRing Lockout, on page 16 task. Step 3 Complete the DLP-U552 Revert to Protect Load, on page 24 task. Step 4 (MS-SPRing nodes only) Complete the DLP-U550 Remove the MS-SPRing Lockout, on page 21 task. Step 5 If the software revertto your previous release failed to restore the database, complete theDLP-U553Manually Restore the Database, on page 26 task. Stop. You have completed this procedure. DLP-U552 Revert to Protect Load This task reverts to the software you were running prior to the last activation. You cannot revert backwardsto a previous version of the protect load if the software on both the working and protect sides is Software R9.2.1.x. Purpose Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 24 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U552 Revert to Protect LoadTools/Equipment PC or UNIX workstation NTP-U487 Preparing to Upgrade to a New Release, on page 7 NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 NTP-U489 Upgrade the Cisco ONS 15454 SDH Software , on page 12 DLP-U547 Perform a MS-SPRing Lockout, on page 16 Prerequisite Procedures Required/As Needed Required for revert Onsite/Remote Onsite or remote Security Level Superuser To perform a supported (non-service-affecting) revert from 9.2.1.x, the release you want to revert to must havebeenworkingatthe timeyouactivatedtothe currentsoftwareversiononthatnode.Also, a supported revert automatically restores the node configuration at the time of the previous activation. The exception to this is when you have downloaded 9.2.1.x a second time, ensuring that no revert to a previous load can take place. In this case, the revert occurs, but is not traffic-affecting and does not change the database. Note Ensure that all cards that are part of a protection group (1+1 or Y-cable) are active on the working card of that protection group and that no protection switches are occurring. To ensure that traffic carrying protect cards are in a standby state, in the node view click the Maintenance tab, and view the Protect column for each of the listed protection groups. View the active/standby status of each card in the Maintenance tab. Note Procedure Step 1 From the node view, click the Maintenance tab, then click the Software button. Step 2 Verify that the protect software displays the release you upgraded from. Step 3 Click the Revert button. Revert activates the protect software and restores the database from the previous load. A dialog box asks you to confirm the choice. Any FPGA downgrades during the revert process may affect traffic. Configuration changes made after activation are lost when you revert. Note Step 4 Click OK. This begins the revert process and drops the connection to the node. Step 5 Wait until the software revert completes before continuing. The system reboot may take up to 30 minutes to complete. Note Step 6 Wait one minute before reverting another node. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 25 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U552 Revert to Protect LoadStep 7 After reverting all the nodes in the network, restart the browser and log back into the last node that was reverted. This uploads the appropriate CTC applet to your workstation. Step 8 Perform the DLP-U549 Delete Cached JAR Files, on page 20 task. Step 9 Return to your originating procedure (NTP). DLP-U553 Manually Restore the Database This task manually restores the database. Use this task if you were unable to perform a revert successfully and need to restore the database. Purpose Tools/Equipment PC or UNIX workstation DLP-U552 Revert to Protect Load, on page 24 DLP-U550 Remove the MS-SPRing Lockout, on page 21 (if required) Prerequisite Procedures Required/As Needed As needed Onsite/Remote Onsite or remote Security Level Superuser Caution Do not perform these steps unless the software revert failed. Caution This process is service affecting and should be performed during a maintenance window. Procedure Step 1 In CTC node view, click the Maintenance tab, then click the Database button. Step 2 Click the Restore button. The Open dialog box appears. Step 3 Select the previously saved database file and click the Open button. The database is restored and the TCC2/TCC2P/TCC3/TNC/TSC cards reboot. Step 4 When the TCC2/TCC2P/TCC3/TNC/TSC cards have finished rebooting, log into CTC and verify that the database is restored. Wait one minute before restoring the next node. Step 5 Repeat Steps 1 to 4 for each node in the network. You have now completed the manual database restore. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 26 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 DLP-U553 Manually Restore the DatabaseWhen the complete database is restored, the node does not report an event regarding the IP change; the node reboots and configures the new IP from the database. If the IP address being restored is not in the CTC network IP addressing scheme, you might lose visibility of the node.To resolve this, you must launch CTC with the IP mentioned in the table against the database backup. Refer to the table, “Manually RecordedData” intheNTP-U488 BackUpthe CiscoONS15454SDHSoftwareDatabase, on page 11 procedure for more information. Note Step 6 Return to your originating procedure (NTP). NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 Card This procedure upgrades the TCC2/TCC2P card to theTCC3 card.TheTCC3 card supportsONS15454 SDHR9.2.1.x.TheTCC2/TCC2Pcardis compatible with ONS 15454 SDH , as well as earlier software versions. Purpose Tools/Equipment Two TCC3 cards Prerequisite Procedures None Required/As Needed As needed Onsite/Remote Onsite Security Level Maintenance or higher Downgradeproceduresfrom TCC3cardstoTCC2P/TCC2cards arenotsupported.LogintotheTechnical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). Note Procedure Step 1 Log into CTC. For detailed instructions, refer to the Cisco ONS 15454 SDH Procedure Guide. Step 2 VerifythattheLANwiresonthebackplane are installedproperly.TheTCC3carddoesnot autodetect miswired LANconnections. If aLANconnection is miswired, aLANConnectionPolarity Reversed condition appears. For information on installing LAN wires, refer to the Cisco ONS 15454 SDH Procedure Guide. Step 3 Verify that the node you are upgrading has ONS 15454 SDH R9.2.1.x installed. The software version is displayed in the upper left corner of the window. Step 4 Complete the NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 procedure before beginning the upgrade. Step 5 Physically replace the standby TCC2/TCC2P card on the ONS 15454 SDH with a TCC3 card. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 27 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 Carda) Check the LED on the faceplate. The ACT/STBY LED on the faceplate of the TCC2/TCC2P/TCC3 card indicateswhether the card is in active or standby mode.AgreenACT/STBYLEDindicates an active card and an amber light indicates a standby card. b) Open the standby TCC2/TCC2P card ejectors. c) Slide the card out of the slot. This raises the IMPROPRMVL alarm, which clears when the upgrade is complete. d) Open the ejectors on the TCC3 card to be installed. e) Slide the TCC3 card into the slot along the guide rails. f) Close the ejectors. g) In CTC node view, Ldg (loading) appears on the newly installed TCC3. The MEA (card mismatch) alarm appears because CTC recognizes a mismatch between TCC card types. Disregard this alarm; it clears by the end of the procedure. Note It takes approximately 10 minutes for the active TCC2/TCC2P card to copy the system software and database to the newly installed TCC3 card. During this operation, the LEDs on the TCC3 card flash Fail and then the active/standby LED flashes. When the transfer completes, the TCC3 card reboots and goes into standby mode after approximately three minutes. Do not remove the card from the shelf during a database transfer. Note If your active TCC2/TCC2P card resets during the upgrade before the new TCC3 card is in full standby mode, remove the new TCC3 card immediately. Caution Step 6 When the newly installed TCC3 card is in standby, right-click the active TCC2/TCC2P card in CTC. Step 7 From the pull-down menu, click Reset Card. Wait for the TCC2/TCC2P card to reboot. The ONS 15454 SDH switches the standby TCC3 card to active mode. The TCC2/TCC2P card verifies that it has the same database as the TCC3 card and then switches to standby. Step 8 Verifythatthe remainingTCC2/TCC2Pcardisnowinstandby mode (theACT/STBYLEDchangestoamber). Step 9 Physically replace the remaining TCC2/TCC2P card with the second TCC3 card. a) Open the TCC2/TCC2P card ejectors. b) Slide the card out of the slot. This raises the IMPROPRMVL alarm, which clears when the upgrade is complete. c) Open the ejectors on the TCC3 card. d) Slide the TCC3 card into the slot along the guide rails. e) Close the ejectors. When a newly installed TCC3 card has a different version of the ONS 15454 SDH software installed from the version running on the activeTCC3 card,the newly installedTCC3 card automatically copies the software version running on the activeTCC3 card.You do not need to do anything in this situation. However,loading theTCC3 card does not boot up in the normal manner. When the card isfirstinserted, the red FAIL LED stays on for a short period. The FAIL LED then blinks normally and all LEDs go dark.After loadingthenewsoftware for approximately10 minutes,theTCC3cardbecomesthe standby card and the amber LED is illuminated. Tip Step 10 If power-related alarms occur after the second TCC3 card is installed, check the voltage on the backplane. Refer to the Cisco ONS 15454 SDH Troubleshooting Guide for information on clearing alarms. Stop. You have completed this procedure. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 28 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U492 Upgrade the TCC2/TCC2P Card to the TCC3 CardNTP-U510 Upgrade the TSC Card to the TNC Card This procedure upgrades the TSC card to the TNC card on the Cisco ONS 15454 M6 shelf. Purpose Tools/Equipment Two TNC cards "DLP-G46 Log into CTC" in the "Connect the PC and Log into the GUI" document. Prerequisite Procedures Required/As Needed As needed Onsite/Remote Onsite Security Level Maintenance or higher Procedure Step 1 Verify that the LAN wires on the RJ-45 LAN port are installed properly. The TNC card does not autodetect miswiredLANconnections. If aLANconnection is miswired, aLANConnectionPolarity Reversed condition appears. For information on installing LAN wires, refer to the Cisco ONS 15454 Procedure Guide. Step 2 Verify that the node you are upgrading has ONS 15454 M6 Software installed. The software version is displayed in the upper left corner of the window. Step 3 Complete the NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 procedure before beginning the upgrade. Step 4 Physically replace the standby TSC card with a TNC card. a) Check the LED on the faceplate. The ACT/STBY LED on the faceplate of the TNC/TSC card indicates whether the card is in active or standby mode. A green ACT/STBY LED indicates an active card and an amber light indicates a standby card. b) Open the ejectors on the standby TSC card. c) Slide the card out of the slot. This raises the IMPROPRMVL alarm, which clears when the upgrade is complete. d) Right-click the slot from which the TSC card was ejected out. e) Click Delete Card to delete TSC from CTC. If the TSC card is not deleted from the CTC shelf view before inserting the TNC card, the MEA (card mismatch) alarm appears on that slot. Note f) Open the ejectors on the TNC card to be installed. g) Slide the TNC card into the slot along the guide rails. h) Close the ejectors. i) In CTC node view, Ldg (loading) appears on the newly installed TNC card. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 29 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U510 Upgrade the TSC Card to the TNC CardIt takes approximately 10 minutes for the active TSC card to copy the system software and database to the newly installed TNC card. During this operation, the LEDs on the TNC card flash Fail and then the active/standby LED flashes. When the transfer completes, the TNC card reboots and goes into standby mode after approximately three minutes. Do not remove the card from the shelf during a database transfer. Note Ifyour activeTSC cardresetsduringtheupgradebefore thenewTNC cardisinfullstandby mode, remove the new TNC card immediately. Caution Step 5 When the newly installed TNC card is in standby, right-click the active TSC card in CTC. Step 6 From the pull-down menu, click Reset Card. Wait for the TSC card to reboot. The standby TNC card is switched to active mode. The TSC card verifies that it has the same database as the TNC card and then switches to standby. Step 7 Verify that the remaining TSC card is now in standby mode (the ACT/STBY LED changes to amber). Step 8 Physically replace the remaining TSC card with the second TNC card. a) Open the ejectors on the TSC card. b) Slide the card out of the slot. This raises the IMPROPRMVL alarm, which clears when the upgrade is complete. c) Right-click the slot from which the TSC card was ejected out. d) Click Delete Card to delete TSC from CTC. If the TSC card is not deleted from the CTC shelf view before inserting the TNC card, the MEA (card mismatch) alarm appears on that slot. e) Open the ejectors on the TNC card. f) Slide the TNC card into the slot along the guide rails. g) Close the ejectors. The second TNC card boots up. The second TNC card must also copy the database. Do not remove the card from the shelf during a database transfer. Step 9 If power-related alarms occur after the second TNC card is installed, check the voltage on the RJ-45 LAN port. Refer to the Cisco ONS 15454 Troubleshooting Guide for information on clearing the alarms. Stop. You have completed this procedure. NTP-U493 Upgrade to the ONS 15454 Software Using TL1 This procedure upgrades the ONS 15454 SDH software to R9.2.1.x using TL1 rather than CTC. Purpose Tools/Equipment PC or UNIX workstation NTP-U487 Preparing to Upgrade to a New Release, on page 7 NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 Prerequisite Procedures Required/As Needed Optional Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 30 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U493 Upgrade to the ONS 15454 Software Using TL1Onsite/Remote Onsite or remote Security Level Superuser This procedure assumes you are upgrading using TL1 Release 6.x and later. TL1 commands used prior to activation to Release 6.x vary in syntax depending on the ONS 15454 release that you are actually upgrading from. To ensure that your syntax for each command is correct, see the TL1 syntax in the Cisco ONSSDH15454TL1 CommandGuide foryourparticular releasewhenissuingthe followingcommands: Note • ACT-USER • COPY-RFILE • REPT EVT FXFR • OPR-PROTNSW- • RTRV-COND-ALL • RTRV-ALM-ALL • RLS-PROTNSW- To download the software usingTL1, an FTP server or a terminal emulation program likeHyperTerminal must be running on the workstation. Note The download (COPY-RFILE) command is different when downloading software to a gateway network element (GNE) or an end network element (ENE) under the following conditions: Note • FTP is being used. • Server is set up with a login and password of FTPUSER1 and FTPUSERPASSWORD1. • FTP server has an IP address of 10.1.1.1. • FTP server is running on the standard FTP port. • Software package is called "15454SDH-0xxx-xxxx-xxxx.pkg". When upgrading from R8.0 and later, if the path protection circuits of type UPSR_DRI or 2waydc is created on the ADM-10G card, software provisioning is lost. Ensure that there are no path protection circuits of typeUPSR_DRI or 2waydc created on theADM-10Gcard before upgrading to the latest release. Note The GNE and ENE commands are as follows: • When downloading software to a GNE, use a command similar to: Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 31 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U493 Upgrade to the ONS 15454 Software Using TL1COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL, SRC=“ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1/15454-03xx-A04K-1405.pkg”; • When downloading software to an ENE, use a command similar to: COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL, SRC=“ftp://FTPUSER1:FTPUSERPASSWORD1@10.111.11.1:2361@90.90.90.90/15454-03xx-A04K-1405.pkg”; The ":2361" after the FTP server IP address 10.111.11.1 denotes port 21 on the server. The software PKG file in the preceding example is located in the home directory of the FTP server. If the software PKG file is not in the home directory on the FTP server, insert the directory path where the software PKG resides between the last IP address and the PKG file in the command line. An example is shown here. COPY-RFILE:NODENAME:RFILE-PKG:CTAG::TYPE=SWDL, SRC=“ftp://FTPUSER1:FTPUSERPASSWORD1@10.1.1.1:21@90.90.90.90/CISCO/SOFTWARE/15454-03xx-A04K-1405.pkg”; Procedure Step 1 To use TL1 commands, set up an FTP session or use HyperTerminal or a similar terminal emulation package to establish a session with the ONS 15454 SDH node. Step 2 Type the IP address for the node, using port 3083 or 2361. The terminal emulation interface displays a warning message and a command prompt (usually >). You can enter TL1 commands at this prompt. Step 3 Type the ACT-USER (Activate User) command in the TL1 request window to open a TL1 session: ACT-USER:[]::::; where: • is the target identifier (optional). • is the Operation Support System (OSS) profile user ID (required). • is the correlation tag that correlates command and response messages (required). • is the password identifier (required). For example, in the TL1 command: ACT-USER::CISCO99:100::PASSWORD; ACT-USER is the activation command, CISCO99 is the user ID, 100 is the correlation tag (used to correlate commands to command responses), and PASSWORDis the password associatedwith the user ID. A response message containing the CTAG that you specified indicates the completion status of the command. Step 4 Repeat Step 2 for each node to be upgraded. Step 5 Select the IP address for the node, using port 3083 or 2361. Step 6 Type the COPY-RFILE command in the TL1 window or, if you are using HyperTerminal, click Transfer > Receive File, and use the associated dialog box to select a file to receive. The COPY-RFILE command downloads a newsoftware package from the location specified by theFTPURLinto the inactive flash partition residing on the controller card. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 32 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U493 Upgrade to the ONS 15454 Software Using TL1COPY-RFILE:[]::::TYPE=,[SRC=],[DEST=],[OVWRT=],[FTTD=]; where: • is the target identifier (optional). • is the source AID (required). • is the correlation tag that correlates command and response messages (required). • is the file transfer protocol (required). • specifies the source of the file to be transferred (required). • is the destination of the file to be transferred (required). • is overwrite. If is yes, then files should be overwritten. If is no, then file transfers will fail if the file already exists at the destination (required). • is the URL format (required). Step 7 Repeat Step 6 for all nodes to be upgraded. Step 8 Look for the REPT EVT FXFR message in the TL1 window. REPT EVT FXFR is an autonomous message used to report the start, completion, and completed percentage status of the software download. REPT EVT FXFR also reports any failure during the software upgrade, including invalid package, invalid path, invalid user ID/password, and loss of network connection. The format of the message is: REPT EVT FXFR SID DATE TIME A ATAG REPT EVT FXFR ",,[],[]" ; where: • indicates the transferred file path name and is a string. • indicates the file transferred status: Start, IP (in progress), or COMPLD. • indicates the file transferred result: success or failure. FXFR_RSLT is optional (the FXFR_RSLT is only sent when the FXFR_STATUS is COMPLD). • indicates the percentage transfer complete and is optional (the BYTES_XFRD is only sent when the FXFR_STATUS is IP or COMPLD). Step 9 Complete “NTP-U487 Preparing to Upgrade to a New Release, on page 7” procedure on page 8 for each node to be upgraded. Step 10 Complete NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 for each node to be upgraded. Step 11 Lock each MS-SPRing span on all the nodes being upgraded using the following command: OPR-PROTNSW-:[]::::,[][:]; where: • is the target identifier (optional). Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 33 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U493 Upgrade to the ONS 15454 Software Using TL1• is the Access IDentifier that indicates the facility in the node to which the switch request is directed. • is the correlation tag that correlates command and response messages (optional). • is the switch command that is to be initiated on the paths. • is the MS-SPRing switch type. • is the direction of transmission in which switching is to be made and is relative to the SDH line or path identified by the AID. The default value is RCV and should be changed to BTH. Some nodes might have more than one MS-SPRing. If this is the case, all MS-SPRing spans on all nodes being upgraded must be locked.Nodes that are not being upgraded do not requireMS-SPRing spanslockouts.You must be aware of each span thatis part of aMS-SPRing to make sure all necessary spans are locked. Note Note Ignore anyDefaultKalarmsthatoccurontheprotectVC time slotsduringthe lockout. SomeMS-SPRing-related alarms may be raised following activation of the first node in the ring.The following alarms, if raised, are normal, and should not cause concern. They clear upon completion of theupgrade, after allnodeshavebeenactivated:MS-SPRing-OOSYNC (MN); RING-MISMATCH (MJ); APSCDFLTK (MN); MS-SPRing-RESYNC (NA). Note Step 12 Verify that all necessary MS-SPRing spans on each node being upgraded have been locked out using the following command: RTRV-PROTNSW-:[]::[::::]; where: • is the target identifier (optional) • isthe accessidentifier thatindicatesthe facility in the node towhich the switch requestis directed (must not be null) (required). • is the correlation tag that correlates command and response messages (optional). Step 13 Verify that there are no outstanding alarms or conditions on each node using the following commands: RTRV-PROTNSW-:[]::[::::]; where: • is the target identifier (optional) • isthe accessidentifier thatindicatesthe facility in the node towhich the switch requestis directed (must not be null) (required). • is the type of condition to be retrieved. A null value is equivalent to ALL. RTRV-ALM-ALL:[]:[]:::[],[],[][,,,]; where: • is the target identifier • is the Access IDentifier that indicates the facility in the node to which the switch request is directed (must not be null). • is the correlation tag that correlates command and response messages (optional). • is a notification code. A null value is equivalent to ALL. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 34 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U493 Upgrade to the ONS 15454 Software Using TL1• is the type of alarm condition. A null value is equivalent to ALL. • is the effect on service caused by the alarm condition. A null value is equivalent to ALL. Resolve all issues before proceeding. You can activate only one node at a time. However, in a parallel upgrade you can begin activation of the next node as soon as the controller cards for the current node have rebooted successfully. If youwish to perform a parallel upgrade remotely,wait five minutesfor the controller cardsto complete the reboot. Note Step 14 Starting at the node farthest from the GNE, type the APPLY command to activate the system software. APPLY:[]::[::]; where: • is the target identifier (optional). • is the correlation tag that correlates command and response messages. • indicates a memory switch action during the software upgrade.MEM_SW_TYPE is ACT for activate. MEM_SW_TYPE is CANC to cancel the activation. If the command is successful, the appropriate flash is selected and the TCC2/TCC2P/TCC3/TNC/TSC card reboots. The following occurs: • Each card in the node reboots, beginning with the standby TCC2/TCC2P/TCC3/TNC/TSC card. When the standby TCC2/TCC2P/TCC3/TNC/TSC card reboots, it signals to the active TCC2/TCC2P/TCC3/TNC/TSC card that it is ready to take over. When the active TCC2/TCC2P/TCC3/TNC/TSC receives this signal, it resets itself, and the standby TCC2/TCC2P/TCC3/TNC/TSC takes over and transitions to active. The pre-upgrade version of the TCC2/TCC2P/TCC3/TNC/TSC card is now the standby TCC2/TCC2P/TCC3/TNC/TSC. • While the second TCC2/TCC2P/TCC3/TNC/TSC is rebooting, the stand by cross-connect card (SONET/SDH only) reboots, and then the active cross-connect card (SONET only) reboots. • Next, the E-Series Ethernet cards reset simultaneously. • Any cards in Y-cable protection groups boot next, one at a time (protect card first), in order of first creation (refer to the CTC protection group list for order of first creation). • Next,the traffic cards,G-SeriesEthernet cards, CE-SeriesEthernet cards, andML-SeriesEthernet cards boot consecutively, in ascending order of slot number, first standby, then working, for each card pair, with the exception that E1-42 protect cards will always be reset before any of their peer working cards. • A system reboot (SYSBOOT) alarm is raised while activation is in progress (following the TCC2/TCC2P/TCC3/TNC/TSC and cross-connect card resets). When all cards have reset, this alarm clears. The complete activation process can take up to 30 minutes, depending on how many cards are installed. After the common control cards finish resetting and all associated alarms clear, you can safely proceed to the next step. (If you are upgrading remotely and cannot see the nodes, wait for 5 minutes for the process to complete, then check to ensure that related alarms have cleared before proceeding.) Repeat this step for each node thatwill be upgraded, moving from the furthest node from theGNEtoward theGNEitself,which should be activated last. Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 35 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 NTP-U493 Upgrade to the ONS 15454 Software Using TL1You might have to log in to each node again to activate the software. Note Step 15 After all nodes have been activated, log in using CTC or Telnet and verify there are no outstanding alarms. Step 16 Remove all MS-SPRing lockouts using the following TL1 command: RLS-PROTNSW-:[]::[::]; where: • is the target identifier (optional) • isthe accessidentifier thatindicatesthe facility in the node towhich the switch requestis directed (must not be null) (required). • is the correlation tag that correlates command and response messages (optional). • is the direction of transmission (transmit or receive). The possible values are: ◦RCV—Receive direction only (default) ◦TRMT—Transmit direction only ◦BTH—Both transmit and receive directions For example: RLS-PROTNSW-OC48:PETALUMA:FAC-6-1:209::BTH; Step 17 To back up the database for the working software load, see NTP-U488 Back Up the Cisco ONS 15454 SDH Software Database, on page 11 in order to preserve the database for the current software. Stop. You have completed this procedure. Related Documentation Use this document in conjunction with the following publications: • Release notes: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_release_notes_list.html • TL1 command guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_command_reference_list.html • Reference guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_technical_reference_list.html • Procedure guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_installation_guides_list.html • Configuration guides: http://www.cisco.com/en/US/products/hw/optical/ps2006/products_installation_and_configuration_ guides_list.html • Troubleshooting guides: Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 36 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Related Documentationhttp://www.cisco.com/en/US/products/hw/optical/ps2006/prod_troubleshooting_guides_list.html Obtaining Documentation and Submitting a Service Request For informationonobtainingdocumentation,submittinga service request, andgatheringadditionalinformation, 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.html Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 OL-23756-01 37 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Obtaining Documentation and Submitting a Service Request Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 38 OL-23756-01 Upgrading the Cisco ONS 15454 SDH to Release 9.2.1 Obtaining Documentation and Submitting a Service Request Cisco Small Business Pro Téléphones IP SPA 500 Modèles 501G, 502G, 504G, 508G et 509G GUIDE DE L'UTILISATEUR Cisco Small Business Pro Téléphones IP SPA 500 Modèles 501G, 502G, 504G, 508G et 509G© 2011 Cisco Systems, Inc. Tous droits réservés. OL-24293-01 Cisco et le logo Cisco sont des marques déposées de Cisco Systems, Inc. et/ou de ses filiales aux États-Unis et dans d'autres pays. Vous trouverez une liste des marques commerciales de Cisco sur la page Web www.cisco.com/go/trademarks. Les autres marques commerciales mentionnées dans les présentes sont la propriété de leurs détenteurs respectifs. L'utilisation du terme « partenaire » n'implique pas de relation de partenariat entre Cisco et toute autre entreprise. (1005R)Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 3 Table des matières Chapitre 1 : Pour commencer 8 À propos de ce document 8 Présentation des téléphones IP Cisco Small Business Pro 10 Présentation des lignes et des boutons du téléphone 11 Composants du téléphone 11 Boutons de fonction 14 Utilisation des raccourcis clavier 17 Console de réception Cisco SPA 500S 18 Entretien du téléphone 19 Chapitre 2 : Installation du téléphone 20 Avant de commencer 21 Connexions du téléphone 22 Connexion du combiné 22 Installation du support (facultatif) 23 Fixation du téléphone au mur (facultatif) 24 Réglage de la patte d'accrochage du combiné 28 Connexion à l'alimentation 29 Connexion du téléphone au réseau 30 Connexion du téléphone à un réseau sans fil 30 Connexion d'un PC au téléphone (facultatif) 31 Connexion de casques filaires et sans fil (facultatif) 31 Vérification du démarrage du téléphone 32 Mise à niveau du microprogramme du téléphone 33 Identification de la version actuelle du microprogramme 33 Téléchargement du microprogramme 34 Obtention de l'adresse IP du téléphone 34 Installation du microprogramme 35Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 4 Table des matières Chapitre 3 : Utilisation des fonctions de base du téléphone 36 Utilisation du matériel et des accessoires du téléphone 37 Utilisation du haut-parleur 37 Utilisation du casque avec le téléphone IP 37 Basculement entre le combiné, le casque et le haut-parleur pendant un appel 37 Envoi de données audio au haut-parleur du téléphone 37 Choix du périphérique audio préféré 38 Réglage du volume de l'appel et mode Muet 39 Réglage du volume de l’appel 39 Réglage du volume de la sonnerie 39 Utilisation du mode Muet 39 Émission ou réception d’un appel 39 Utilisation de l’assistance à la numérotation 40 Mise en attente d’un appel 41 Reprise d’un appel 41 Fin d’un appel 41 Transfert d’appel 41 Transfert accompagné 42 Transfert direct 42 Transfert d’un appel en attente vers un appel actif 43 Recomposition d’un numéro 43 Affichage et rappel des appels manqués 44 Activation et désactivation du raccourci des appels manqués 45 Renvoi d'appel 45 Renvoi de tous les appels 46 Renvoi d'appel lorsque votre téléphone est occupé 46 Renvoi des appels manqués 47 Attente avant le renvoi d’appel si pas de réponse 48 Arrêt du renvoi d'appel 48Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 5 Table des matières Configuration de la fonction Ne pas déranger 48 Activation de la fonction Ne pas déranger 49 Désactivation de la fonction Ne pas déranger 49 Activation et désactivation de la fonction d'appel en attente 50 Prise d’appel 51 Parcage d'un appel 51 Conférence téléphonique à trois 53 Mise en place d'une conférence entre un appel en attente et un appel actif 54 Utilisation des répertoires téléphoniques 54 Utilisation du répertoire personnel 55 Utilisation du répertoire d’entreprise 56 Utilisation des listes de l'historique des appels 57 Consultation des listes de l’historique des appels 57 Appel à partir des listes de l’historique des appels 58 Suppression d’un numéro d’une liste d’historique des appels 58 Enregistrement d’un numéro d’une liste d’historique des appels dans votre répertoire 58 Définition ou modification d’un mot de passe de téléphone 59 Accès à la messagerie vocale 59 Chapitre 4 : Utilisation des fonctionnalités avancées du téléphone 61 Configuration des fonctions de confidentialité et de sécurité 62 Blocage de l’ID de l’appelant 62 Blocage des appels anonymes 62 Utilisation de l'appel sécurisé 63 Activation de l’assistance à la numérotation 64 Création de numérotations rapides 65 Création de numérotations rapides sur des boutons de ligne disponibles 65 Création de numérotations rapides numériques 66 Utilisation de la numérotation rapide 66 Utilisation de la fonction de radiomessagerie 67Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 6 Table des matières Appel d'un autre téléphone par radiomessagerie 67 Appel d'un groupe de téléphones par radiomessagerie 67 Configuration de la réponse automatique 67 Contrôle d’un autre téléphone et accès à celui-ci depuis votre téléphone 68 Personnalisation de l’écran LCD 68 Modification du contraste de l’écran LCD 69 Modification des paramètres de rétroéclairage de l'écran 69 Configuration de l’économiseur d’écran du téléphone 70 Activation de l’économiseur d’écran 71 Utilisation des sonneries 71 Modification de la sonnerie 72 Configuration de la date et de l’heure du téléphone 72 Réglage de la date et de l’heure du téléphone 72 Utilisation des codes étoile 73 Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G 75 Procédures avancées destinées au personnel de l’assistance technique 78 Redémarrage du téléphone 79 Chapitre 5 : Utilisation de l'interface Web 80 Connexion à l'interface Web 81 Configuration de la fonction Ne pas déranger 82 Configuration du renvoi d'appel 82 Configuration de la fonction d'appel en attente 83 Blocage de l'ID de l'appelant 84 Blocage des appels anonymes 84 Utilisation du répertoire personnel 85 Consultation des listes de l'historique des appels 85 Création de numérotations rapides 86Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 7 Table des matières Acceptation de messages texte 86 Réglage du volume audio 87 Modification du contraste de l'écran LCD 88 Configuration de l'économiseur d'écran du téléphone 88 Chapitre 6 : Utilisation de la console de réception Cisco SPA 500S 90 Connexion de la console de réception Cisco SPA 500S au téléphone IP 91 Connexion d'une seule console Cisco SPA 500S 92 Connexion d'une deuxième console Cisco SPA 500S 96 Configuration de la console Cisco SPA 500S 98 Utilisation de la console Cisco SPA 500S 99 Contrôle de la console Cisco SPA 500S 99 Annexe A : Pour en savoir plus 1001 Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 8 Pour commencer Ce chapitre présente le document et apporte des informations de base sur le téléphone IP Cisco Small Business Pro. Il comprend les sections suivantes : • À propos de ce document, page 8 • Présentation des téléphones IP Cisco Small Business Pro, page 10 • Présentation des lignes et des boutons du téléphone, page 11 À propos de ce document Ce guide décrit les tâches et les concepts relatifs à l'utilisation et à la configuration du téléphone IP Cisco Small Business Pro. REMARQUE Les fonctionnalités du téléphone IP Cisco Small Business Pro varient selon le type de système de contrôle des appels que vous utilisez. Ce document explique comment utiliser les téléphones IP Cisco Small Business Pro avec un système de téléphonie SIP, tel que le système vocal Cisco SPA 9000 ou un système Broadsoft ou Asterisk. Si vous utilisez le téléphone IP Cisco Small Business Pro avec un système Cisco Unified Communications 500, reportez-vous au Cisco Unified Communications Manager Express for Cisco Small Business Pro IP Phone SPA 50X (SPCP) User Guide.Pour commencer À propos de ce document Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 9 1 Organisation Ce tableau décrit le contenu de chaque chapitre de ce document. Titre Description Chapitre 1 Pour commencer Description de ce guide et présentation des téléphones IP Cisco Small Business Pro. Chapitre 2 Installation du téléphone Instructions de connexion et d'installation du téléphone. Chapitre 3 Utilisation des fonctions de base du téléphone Description des opérations de base (émettre et recevoir un appel, transférer un appel, configurer le renvoi d'appel, prendre un appel, etc.). Chapitre 4 Utilisation des fonctionnalités avancées du téléphone Description des opérations avancées (configurer les fonctions de confidentialité et de sécurité, les numérotations rapides, les contacts et la sonnerie, etc.). Chapitre 5 Utilisation de l'interface Web Connexion à l'interface utilisateur Web du téléphone et utilisation de l'interface. Chapitre 6 Utilisation de la console de réception Cisco SPA 500S Utilisation de la console Cisco SPA 500S. Annexe A Pour en savoir plus Liste de documents connexes et liens d'accès.Pour commencer Présentation des téléphones IP Cisco Small Business Pro Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 10 1 Présentation des téléphones IP Cisco Small Business Pro Les téléphones IP Cisco Small Business sont des téléphones VoIP (Voice over Internet Protocol, Voix sur IP) dotés de nombreuses fonctionnalités permettant de communiquer vocalement sur un réseau IP. Ces téléphones offrent des fonctionnalités traditionnelles, comme le renvoi d'appel, la recomposition d'un numéro, la numérotation rapide, le transfert d'appel, la conférence téléphonique et l'accès à la messagerie vocale. Les appels peuvent être émis ou reçus à l'aide d'un combiné, d'un casque ou d'un haut-parleur. Les téléphones IP proposent également des fonctionnalités spéciales qui ne sont pas disponibles sur des téléphones traditionnels. Les téléphones IP Cisco Small Business Pro sont dotés de ports Ethernet qui vous permettent de les relier au réseau informatique. Ils possèdent également des ports Ethernet supplémentaires qui vous permettent de connecter un ordinateur au réseau par le biais du téléphone IP. À la différence des téléphones traditionnels, les téléphones IP Cisco Small Business Pro nécessitent une source d'alimentation distincte. Vous pouvez alimenter les téléphones en les connectant à un commutateur qui fournit une alimentation électrique par câble Ethernet (POE, Power over Ethernet) ou en utilisant un adaptateur secteur PA100 en option. Le tableau suivant répertorie les téléphones IP Cisco Small Business Pro traités dans ce document et leurs fonctionnalités respectives : SPA 501G SPA 502G SPA 504G SPA 508G SPA 509G Écran Étiquettes papier LCD monochrome 128 x 64 rétroéclairé Lignes 8 1 4 8 12 Touches de fonction 4 fixes (rappel, annulation, conférence et transfert) 4 dynamiques Bouton de navigation Aucun Bouton de navigation quadridirectionnelPour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 11 1 Présentation des lignes et des boutons du téléphone Reportez-vous au graphique et au tableau ci-après pour identifier les éléments du téléphone. Composants du téléphone Figure 1 Composants du téléphone Le modèle Cisco SPA 509G est représenté sur la photo précédente pour illustrer les fonctionnalités du téléphone IP Cisco Small Business Pro. Les autres modèles possèdent des fonctionnalités différentes. Reportez-vous à la section « Présentation des téléphones IP Cisco Small Business Pro » à la page 10.Pour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 12 1 Les objets numérotés sur la photo sont expliqués dans le tableau suivant. N° Fonctionnalité du téléphone Description 1 Combiné Décrochez-le pour passer un appel ou répondre à un appel. 2 Voyant de message en attente Émet une lumière rouge continue quand vous avez un nouveau message vocal. Émet une lumière rouge clignotante lors d'un appel entrant. 3 Écran LCD Affiche la date et l'heure, le nom de la station téléphonique, les postes et les options des touches de fonction. (Non disponible sur le modèle Cisco SPA 501G.) 4 Touches de ligne Indiquent l'état des lignes téléphoniques. (Non disponibles sur le modèle Cisco SPA 502G.) Couleur des touches : Vert : la ligne est inactive. Rouge (lumière continue) : la ligne est active ou en cours d'utilisation. Rouge (lumière clignotante) : la ligne est en attente. Orange : la ligne n'est pas enregistrée (inutilisable). L’administrateur du système téléphonique peut également programmer ces touches pour effectuer des fonctions telles que la numérotation abrégée, la prise d’appel ou la surveillance d’un poste.Pour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 13 1 5 Boutons de fonction Appuyez sur un bouton de fonction pour effectuer l'action indiquée sur l'écran LCD. Remarque : le modèle Cisco SPA 501G possède les quatre boutons suivants. Recomp. : compose le dernier numéro appelé. Annuler : annule une action (par exemple un transfert). Conférence : au cours d'un appel, appuyez sur ce bouton pour établir une conférence téléphonique et composer un autre numéro. Lorsque le deuxième interlocuteur répond, appuyez de nouveau sur Conference pour établir la conférence. Transfert : transfère un appel. Reportez-vous à la section « Transfert d’appel » à la page 41. 6 Bouton de navigation Appuyez sur une flèche pour faire défiler vers la gauche, la droite, le haut ou le bas les éléments affichés sur l'écran LCD. (Non disponible sur le modèle Cisco SPA 501G.) 7 Bouton Messages Appuyez sur ce bouton pour accéder à la messagerie vocale (celle-ci doit être configurée par l'administrateur du système téléphonique). 8 Bouton Attente Appuyez sur ce bouton pour mettre un appel en attente. N° Fonctionnalité du téléphone DescriptionPour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 14 1 Boutons de fonction Les boutons de fonction et les intitulés sur l'écran varient selon le modèle du téléphone et la configuration du système téléphonique. (Les boutons de fonction ne sont pas disponibles sur le modèle Cisco SPA 501G.) Appuyez sur la flèche droite ou la flèche gauche du bouton de navigation pour afficher d'autres boutons de fonction. 9 Bouton Configuration Appuyez sur ce bouton pour accéder à un menu vous permettant de configurer des fonctionnalités et vos préférences (par exemple, le répertoire téléphonique et les numérotations rapides), d'accéder à l'historique des appels et de définir des fonctions (telles que le renvoi d'appel). Pour le modèle Cisco SPA 501G, ce bouton donne accès au menu Interactive Voice Response, qui vous permet d'effectuer des tâches telles que l'obtention de l'adresse IP du téléphone. Pour obtenir plus d'informations, reportez-vous aux guides de l'utilisateur sur le site Cisco.com. (Voir la liste des liens à la fin de ce document.) 10 Bouton Muet Appuyez sur ce bouton pour mettre le téléphone en mode muet ou annuler ce mode. Quand le téléphone est en mode muet, le bouton émet une lumière rouge. S'il clignote, cela signifie que la connexion réseau est introuvable. 11 Bouton Volume Appuyez sur + pour augmenter le volume et sur- pour diminuer le volume du combiné, du casque, du hautparleur (lorsque le combiné est décroché) ou le volume de la sonnerie (lorsque le combiné est raccroché). 12 Bouton Casque Appuyez sur ce bouton pour activer ou désactiver le casque. Lorsque le casque est activé, le bouton émet une lumière verte. 13 Bouton Haut-parleur Appuyez sur ce bouton pour activer ou désactiver le haut-parleur. Lorsque le haut-parleur est activé, le bouton émet une lumière verte. 14 Clavier Permet de composer des numéros de téléphone, d'entrer des lettres et de sélectionner des options du menu. N° Fonctionnalité du téléphone DescriptionPour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 15 1 Vous trouverez ci-après une liste partielle des boutons de fonction qui peuvent être disponibles sur le téléphone. Ces boutons de fonction peuvent ne pas figurer sur votre téléphone, ou il est possible que celui-ci comporte d'autres boutons qui ne sont pas répertoriés ici. Par exemple, l’administrateur du système téléphonique peut aussi configurer des boutons de fonction personnalisés sur votre téléphone, comme des boutons de numérotation rapide vers le numéro d’une entreprise ou des boutons permettant d’accéder à un programme spécialisé qui s’exécute sur votre téléphone. Pour obtenir plus d'informations, contactez l’administrateur du système téléphonique. Bouton Fonction << ou >> Permet de se déplacer vers la gauche ou vers la droite dans une entrée, sans supprimer les caractères. actif Active l'économiseur d'écran. ajout Permet d'ajouter une entrée. annul Permet d'annuler toutes les modifications apportées, si vous appuyez dessus avant ok ou enreg. bis Permet d'afficher la liste des numéros récemment composés. comp Permet de composer un numéro. conf Permet d'établir une conférence téléphonique. confLx Permet d'établir une conférence entre les lignes actives du téléphone. dar Permet de composer le numéro du dernier appel reçu. décGr Permet de répondre à un appel qui sonne sur un poste en identifiant le numéro de ce poste. décro Permet de répondre à un appel qui sonne sur un autre poste en entrant le numéro de ce poste. déparq Permet de reprendre un appel parqué. éditer Permet d'ouvrir un élément pour modifier des chiffres ou des lettres, ou activer ou désactiver une fonctionnalité. enreg Permet d'enregistrer vos modifications. ignorer Permet d'ignorer un appel entrant.Pour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 16 1 manq Permet d'afficher la liste des appels manqués. npd Ne pas déranger ; permet de couper la sonnerie du téléphone. -npd Permet de rétablir la sonnerie du téléphone. o/n Permet d'entrer dans un sous-menu et de basculer entre Oui et Non pour activer ou désactiver une option. parq Permet de mettre un appel en attente au numéro de parcage désigné. Si vous le reprenez ou que l'appelant se déconnecte, l'appel n'est plus parqué. Cette option doit être configurée par l'administrateur du système téléphonique. phold Permet de mettre un appel en attente sur une ligne partagée active. renvoi Permet de renvoyer tous les appels à destination de votre téléphone à un numéro spécifié. rép Permet d'accéder aux répertoires téléphoniques. reprnd Permet de reprendre un appel en attente. -Rvap Désactive le renvoi d'appel. sélect Permet de sélectionner l'élément en surbrillance sur l'écran LCD. starcode Permet d'entrer un code étoile. Reportez-vous à « Utilisation des codes étoile » à la page 73. supCar Permet de supprimer le chiffre ou la lettre en dernière position. suppr Permet de supprimer un élément entier (par exemple, un numéro de la liste de l'historique des appels). tranLx Permet de transférer une ligne active sur le téléphone à un numéro appelé. transf Permet de transférer un appel. tranSi Permet d'effectuer un transfert d'appel direct (transfert d'un appel sans parler à l'interlocuteur auquel vous transférez l'appel). Bouton FonctionPour commencer Présentation des lignes et des boutons du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 17 1 Utilisation des raccourcis clavier Lorsque vous utilisez les menus du téléphone, vous pouvez utiliser le clavier pour entrer le numéro indiqué à côté de l'élément du menu ou du sous-menu sur l'écran LCD. (Ne s'applique pas au modèle Cisco SPA 501G.) Par exemple, pour obtenir votre adresse IP sur le modèle SPA 504G, appuyez sur le bouton Configuration et composez le 9. L'adresse IP s'affiche sur l'écran Réseau. REMARQUE Les menus et les options varient selon le modèle du téléphone.Pour commencer Console de réception Cisco SPA 500S Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 18 1 Console de réception Cisco SPA 500S La console de réception Cisco SPA 500S pour les téléphones IP Cisco Small Business Pro est dotée de 32 boutons et 32 DEL programmables 3 couleurs (rouge, vert, orange) et prend en charge le tableau de voyants d'occupation Broadsoft et le contrôle des lignes Asterisk. La console Cisco SPA 500S se fixe au téléphone IP avec le bras de fixation fourni (non représenté). Elle est alimentée directement par le téléphone IP et ne nécessite pas d'alimentation séparée. Vous pouvez relier deux unités Cisco SPA 500S à un même téléphone IP, ce qui vous donne la possibilité de contrôler 64 lignes distinctes au total. Pour obtenir plus d'informations sur la console Cisco SPA 500S, reportez-vous au Chapitre 6, « Utilisation de la console de réception Cisco SPA 500S ».Pour commencer Entretien du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 19 1 Entretien du téléphone Les téléphones IP Cisco Small Business Pro sont des appareils électroniques qui ne doivent pas faire l'objet d'une exposition excessive à la chaleur, au soleil, au froid ou à l'eau. Pour nettoyer le téléphone, utilisez une serviette en papier ou en tissu légèrement imbibée d'eau. Veillez à ne pas pulvériser de solution de nettoyage directement sur l'appareil ni à la verser dessus.2 Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 20 Installation du téléphone Ce chapitre explique comment installer le téléphone IP Cisco Small Business Pro et le connecter au réseau. Il comprend les sections suivantes : • Avant de commencer, page 21 • Connexions du téléphone, page 22 • Connexion du combiné, page 22 • Installation du support (facultatif), page 23 • Fixation du téléphone au mur (facultatif), page 24 • Connexion à l'alimentation, page 29 • Connexion du téléphone au réseau, page 30 • Connexion d'un PC au téléphone (facultatif), page 31 • Connexion de casques filaires et sans fil (facultatif), page 31 • Vérification du démarrage du téléphone, page 32 • Mise à niveau du microprogramme du téléphone, page 33Installation du téléphone Avant de commencer Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 21 2 Avant de commencer Avant d'installer et de connecter le téléphone, contactez l'administrateur système (le cas échéant) pour vous assurer que le téléphone peut être installé dans votre réseau, prenez connaissance des consignes de sécurité, et vérifiez que vous avez en votre possession tous les éléments du téléphone et l'ensemble de la documentation. REMARQUE Le port RJ-11 « AUX » est réservé à la connexion à la console de réception Cisco SPA 500S qui fonctionne avec les téléphones IP. Il ne doit pas être utilisé comme port de ligne téléphonique. ! AVERTISSEMENT N'insérez pas de cordon de ligne téléphonique dans le port « AUX ».Installation du téléphone Connexions du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 22 2 Connexions du téléphone La photo suivante illustre la connexion des différents éléments du téléphone. Figure 1 Connexions du téléphone Connexion du combiné ÉTAPE 1 Retournez le téléphone afin d'accéder aux ports situés à l'arrière de l'unité. ! AVERTISSEMENT N'insérez pas de cordon de ligne téléphonique dans le port auxiliaire. ÉTAPE 2 Insérez l'extrémité la plus longue du cordon téléphonique dans le port du combiné situé sur le téléphone (indiqué par un symbole en forme de téléphone). ÉTAPE 3 (Facultatif) Faites passer le cordon téléphonique dans le canal de passage du câble. ÉTAPE 4 Insérez l'autre extrémité du cordon téléphonique dans le port situé en bas du combiné (non illustré).Installation du téléphone Installation du support (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 23 2 Installation du support (facultatif) REMARQUE Ne fixez pas le support pour bureau si vous voulez monter le téléphone au mur. Si vous désirez utiliser une console de réception Cisco SPA 500S, fixez la console avant le support pour bureau. ÉTAPE 1 Connectez le support pour téléphone en alignant les pattes situées sur le support avec les orifices du téléphone. ÉTAPE 2 Enclenchez les pattes du bas dans les orifices inférieurs du téléphone, puis appuyez légèrement sur le support. Les pattes du haut doivent s'enclencher facilement dans les orifices supérieurs du support. Ne forcez pas.Installation du téléphone Fixation du téléphone au mur (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 24 2 Fixation du téléphone au mur (facultatif) Pour monter le téléphone au mur, vous devez vous procurer le kit de support mural MB100. Figure 2 Kit de support mural MB100Installation du téléphone Fixation du téléphone au mur (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 25 2 ÉTAPE 1 Pour fixer le support de montage, alignez les deux goupilles du support de montage avec les orifices dans la base du téléphone. ÉTAPE 2 Orientez le support de montage de manière à ce que le port Ethernet et le port du combiné du téléphone soient accessibles après l'installation. ÉTAPE 3 Appuyez sur le support de montage pour l'introduire dans la base du téléphone. Faites glisser le support de montage vers le haut pour l'emboîter.Installation du téléphone Fixation du téléphone au mur (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 26 2 ÉTAPE 4 (Facultatif) Si une prise Wi-Fi ou PoE est installée, placez-la dans le bac.Installation du téléphone Fixation du téléphone au mur (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 27 2 Branchez les câbles Ethernet et d'alimentation.Installation du téléphone Fixation du téléphone au mur (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 28 2 ÉTAPE 5 Accrochez le support à des vis fixées au mur. Réglage de la patte d'accrochage du combiné Si vous montez le téléphone sur une surface verticale, vous devez tourner la patte d'accrochage du combiné située sur le téléphone de sorte que le combiné ne tombe pas du téléphone lorsque vous le placez sur son support. ÉTAPE 1 Appuyez sur le loquet. ÉTAPE 2 Faites glisser la patte d'accrochage vers le haut jusqu'à ce qu'elle se détache du téléphone.Installation du téléphone Connexion à l'alimentation Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 29 2 ÉTAPE 3 Faites tourner la patte de 180° et réinsérez-la dans la base du téléphone. La patte attrape désormais la fente dans le combiné lorsque vous placez ce dernier sur son support. Connexion à l'alimentation Si vous utilisez une source d'alimentation externe, insérez une extrémité du cordon d'alimentation dans une prise murale et l'autre extrémité dans le port d'alimentation situé sur le téléphone. Installation du téléphone Connexion du téléphone au réseau Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 30 2 Connexion du téléphone au réseau Si vous utilisez une connexion Ethernet : ÉTAPE 1 Insérez une extrémité du câble Ethernet dans le port réseau du téléphone (indiqué par « SW »). ÉTAPE 2 Insérez l'autre extrémité du câble Ethernet dans le périphérique approprié sur le réseau, par exemple un commutateur réseau. Connexion du téléphone à un réseau sans fil Vous pouvez utiliser le pont sans fil G Cisco WBP54G pour adaptateurs de téléphone afin de connecter le téléphone IP à un réseau G sans fil au lieu d'utiliser le réseau local câblé. REMARQUE Cette procédure nécessite l'adaptateur secteur Cisco PA100 pour téléphonie IP du système vocal SPA 9000 en option pour alimenter le pont WBP54G. Pour connecter le téléphone au pont Cisco WBP54G : ÉTAPE 1 Configurez le pont Cisco WBP54G à l'aide de l'assistant d'installation. Reportezvous aux instructions du Wireless-G Bridge for Phone Adapters Quick Installation Guide, disponible sur le site cisco.com. Reportez-vous à Annexe A, « Pour en savoir plus », pour obtenir la liste des documents et des emplacements. ÉTAPE 2 Au cours du processus de l'assistant d'installation, connectez le câble réseau Ethernet du pont WBP54G à l'arrière de la base du téléphone IP dans la fente indiquée par « SW ». Reportez-vous au graphique « Connexions du téléphone ». ÉTAPE 3 Connectez le câble d'alimentation du pont WBP54G au port d'alimentation sur la base du téléphone IP. ÉTAPE 4 Branchez l'adaptateur secteur du téléphone IP sur le port d'alimentation du pont WBP54G. ÉTAPE 5 Branchez l'autre extrémité de l'adaptateur secteur du téléphone IP sur une prise murale.Installation du téléphone Connexion d'un PC au téléphone (facultatif) Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 31 2 Connexion d'un PC au téléphone (facultatif) Pour connecter un PC au téléphone (facultatif) : ÉTAPE 1 Pour fournir l'accès réseau à un PC, connectez une extrémité d'un câble Ethernet supplémentaire (non fourni) au port PC à l'arrière du téléphone. Reportez-vous au graphique « Connexions du téléphone ». ÉTAPE 2 Connectez l'autre extrémité du câble Ethernet au port réseau du PC. Connexion de casques filaires et sans fil (facultatif) Les téléphones IP prennent en charge les casques de différents fabricants. Pour connaître les derniers modèles pris en charge, contactez votre revendeur. Vous trouverez des informations supplémentaires sur les sites Web des fabricants : www.plantronics.com www.jabra.com Le processus de connexion peut varier selon la marque et le type de casque. Pour obtenir plus d'informations, reportez-vous à la documentation fournie avec le casque. En général, pour connecter un casque : • Casque sans fil : reliez le cordon téléphonique du casque au port téléphonique à l'arrière du téléphone IP. • Casque filaire : connectez la prise de 2,5 mm du casque au port casque situé sur le côté droit du téléphone IP, comme illustré ci-dessous :Installation du téléphone Vérification du démarrage du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 32 2 Vérification du démarrage du téléphone Une fois que vous avez branché le téléphone au secteur et que vous l'avez relié au réseau, le téléphone exécute une séquence de démarrage. Pendant cette opération, les téléphones à écran affichent le logo Cisco et le message « Initialisation du réseau ». Tous les voyants du téléphone clignotent. Une fois que le téléphone est correctement connecté au réseau, celui-ci reçoit une configuration de base, et les touches de ligne téléphonique doivent émettre une lumière verte (sur les modèles dotés de telles touches). Sur les modèles dotés d'un écran, le téléphone affiche le menu standard du téléphone. La date, le nom et le numéro du téléphone apparaissent sur la première ligne de l'écran LCD. En bas de l'écran LCD, les touches de fonction sont affichées au-dessus des boutons de fonction associés. Sur les modèles sans écran, comme le téléphone Cisco SPA 501G, les boutons de ligne doivent émettre une lumière verte et une tonalité doit se faire entendre lorsque vous décrochez le combiné ou lorsque vous appuyez sur le bouton du haut-parleur.Installation du téléphone Mise à niveau du microprogramme du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 33 2 Si le téléphone ne démarre pas, vérifiez l'installation et les connexions. Si elles sont correctes, débranchez et rebranchez le téléphone. Si vous ne voyez toujours rien à l’écran, contactez l’administrateur du système téléphonique ou le fournisseur de services téléphoniques Internet. Mise à niveau du microprogramme du téléphone Un microprogramme est préinstallé dans le téléphone. Des versions plus récentes de ce microprogramme ont cependant pu être développées en vue de fournir des fonctionnalités supplémentaires et de résoudre des problèmes liés au téléphone. Pour optimiser les performances de votre téléphone, vous devrez peut-être le mettre à niveau vers la dernière version du microprogramme. ! AVERTISSEMENT Si vous utilisez le téléphone avec un système de service de téléphonie Internet, consultez votre fournisseur d'accès avant de procéder à cette mise à niveau. Il est possible qu'il exécute une mise à niveau automatique et que vous n'ayez pas besoin d'intervenir. Pour mettre à niveau le microprogramme de votre téléphone, effectuez l'une des opérations suivantes : • Téléchargez le microprogramme sur le site Web de Cisco et installez-le à partir de votre ordinateur. Les instructions sont détaillées dans la section suivante. • Procédez à la mise à niveau à l'aide de l'assistant d'installation du système vocal Cisco SPA 9000 (si votre téléphone se trouve sur le réseau d'un système vocal Cisco SPA 9000). Reportez-vous au Cisco SPA 9000 Voice System Setup Wizard User Guide. Identification de la version actuelle du microprogramme Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Accédez à Infos produit et appuyez sur sélect. ÉTAPE 3 Accédez à Version logicielle. Le numéro de version du microprogramme s'affiche.Installation du téléphone Mise à niveau du microprogramme du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 34 2 Cisco SPA 501G : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Entrez 150 et appuyez sur #. La version du microprogramme s'affiche. Téléchargement du microprogramme Accédez au site www.tools.cisco.com/support/downloads et entrez le numéro du modèle dans le champ de recherche de logiciel. Enregistrez le microprogramme sur le bureau de l'ordinateur. Obtention de l'adresse IP du téléphone Avant de procéder à la mise à niveau, vous devez obtenir l'adresse IP du téléphone. Pour obtenir l'adresse IP : Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Accédez à Réseau, puis appuyez sur sélect. ÉTAPE 3 Accédez à IP actuelle. Il s'agit de l'adresse IP du téléphone. SPA 501G : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Entrez 110 et appuyez sur #. L'adresse IP s'affiche.Installation du téléphone Mise à niveau du microprogramme du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 35 2 Installation du microprogramme ÉTAPE 1 Procédez à l'extraction du microprogramme sur votre ordinateur. REMARQUE Si vous utilisez une connexion VPN, vous devrez peut-être vous déconnecter avant de poursuivre pour que l'ordinateur puisse communiquer directement avec le téléphone pour la mise à niveau. ÉTAPE 2 Lancez le fichier exécutable de mise à niveau du microprogramme (en doublecliquant sur upg-spa504-6-2-0.exe, par exemple). ÉTAPE 3 Lisez le message concernant la mise à niveau et votre fournisseur d'accès, puis cliquez sur Continue. ÉTAPE 4 Entrez l'adresse IP du téléphone et vérifiez l'adresse de l'ordinateur. ÉTAPE 5 Cliquez sur OK. Des informations relatives aux éléments logiciels et matériels actuels du téléphone s'affichent. ÉTAPE 6 Cliquez sur Upgrade pour lancer la mise à niveau. REMARQUE Attendez que la mise à niveau soit terminée (que les voyants ne clignotent plus) pour débrancher le téléphone. ÉTAPE 7 Cliquez sur OK pour quitter le message d'état de la mise à niveau.3 Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 36 Utilisation des fonctions de base du téléphone Ce chapitre fournit des instructions sur l’utilisation des fonctions de base du téléphone. Il comprend les sections suivantes : • Utilisation du matériel et des accessoires du téléphone, page 37 • Réglage du volume de l'appel et mode Muet, page 39 • Émission ou réception d’un appel, page 39 • Mise en attente d’un appel, page 41 • Reprise d’un appel, page 41 • Fin d’un appel, page 41 • Transfert d’appel, page 41 • Recomposition d’un numéro, page 43 • Affichage et rappel des appels manqués, page 44 • Activation et désactivation du raccourci des appels manqués, page 45 • Renvoi d'appel, page 45 • Configuration de la fonction Ne pas déranger, page 48 • Activation et désactivation de la fonction d'appel en attente, page 50 • Prise d’appel, page 51 • Parcage d'un appel, page 51 • Conférence téléphonique à trois, page 53 • Utilisation des répertoires téléphoniques, page 54 • Utilisation des listes de l'historique des appels, page 57 • Définition ou modification d’un mot de passe de téléphone, page 59 • Accès à la messagerie vocale, page 59Utilisation des fonctions de base du téléphone Utilisation du matériel et des accessoires du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 37 3 Utilisation du matériel et des accessoires du téléphone Utilisation du haut-parleur Pour utiliser le haut-parleur, appuyez sur le bouton Haut-parleur (le combiné peut être raccroché ou décroché). Utilisation du casque avec le téléphone IP Installez le casque comme décrit dans la section « Connexion de casques filaires et sans fil (facultatif) » à la page 31. REMARQUE Les étapes à suivre pour utiliser le casque avec le téléphone IP peuvent varier. Pour obtenir plus d'informations, reportez-vous à la documentation fournie avec le casque. Pour utiliser un casque filaire, appuyez sur le bouton Casque du téléphone et composez le numéro à appeler, ou appuyez sur le bouton du casque pour répondre à un appel. Pour utiliser un casque sans fil, décrochez le combiné avant de passer ou de recevoir un appel par le biais du casque. Basculement entre le combiné, le casque et le haut-parleur pendant un appel Tous ces périphériques audio peuvent être utilisés pendant un appel. Vous ne pouvez utiliser qu’un seul périphérique à la fois. Vous pouvez raccrocher le combiné si vous utilisez la fonction haut-parleur ou casque. Si vous passez de la fonction combiné à la fonction haut-parleur, assurezvous que le voyant correspondant est bien allumé avant de raccrocher le combiné. Toutefois, si vous passez de la fonction combiné à la fonction casque sans fil, ne raccrochez pas le combiné sous peine de couper l'appel. Envoi de données audio au haut-parleur du téléphone Cette option permet d’envoyer des données audio au haut-parleur lorsque le combiné est décroché.Utilisation des fonctions de base du téléphone Utilisation du matériel et des accessoires du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 38 3 REMARQUE Ceci ne s'applique pas au modèle Cisco SPA 501G. ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Envoyer signal audio au haut-parleur > Modif. ÉTAPE 4 Appuyez sur o/n pour activer ou désactiver la fonction. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur Enreg.. Choix du périphérique audio préféré Cette option désigne le casque ou le haut-parleur comme périphérique audio préféré lorsque le combiné n’est pas utilisé. REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. Pour choisir le périphérique audio préféré : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Périphérique audio préféré et appuyez sur Modif. ÉTAPE 4 Appuyez sur Option pour afficher les options disponibles. Lorsque l'option souhaitée s'affiche, appuyez sur ok. ÉTAPE 5 Appuyez sur Enreg..Utilisation des fonctions de base du téléphone Réglage du volume de l'appel et mode Muet Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 39 3 Réglage du volume de l'appel et mode Muet Vous pouvez également modifier le réglage du volume d’appel depuis votre ordinateur à l’aide de l’interface Web du téléphone IP. Reportez-vous à la section « Réglage du volume audio » à la page 87. Réglage du volume de l’appel Pour régler le volume du combiné ou du haut-parleur, décrochez le combiné ou appuyez sur le bouton Haut-parleur. Appuyez sur + sur le bouton Volume pour augmenter le volume ou sur - pour le diminuer. Appuyez sur Enreg. (excepté sur le modèle Cisco SPA 501G). Réglage du volume de la sonnerie Pour régler le volume de la sonnerie, raccrochez le combiné et désactivez le bouton du haut-parleur, puis appuyez sur le bouton Volume. Appuyez sur Enreg. (excepté sur le modèle Cisco SPA 501G). Utilisation du mode Muet Pour désactiver le son du microphone du téléphone, du haut-parleur ou du microphone du casque, appuyez sur le bouton Muet sur le téléphone. Le bouton émet une lumière rouge. Appuyez de nouveau sur le bouton Muet pour rétablir le son. Si aucun périphérique audio n’est allumé, la touche Muet n’a aucun effet. Lorsque vous passez du haut-parleur au combiné, le mode Muet est automatiquement désactivé. Émission ou réception d’un appel REMARQUE Vous devrez peut-être composer un ou plusieurs numéros pour accéder à une ligne extérieure. Posez la question à l'administrateur du système téléphonique.Utilisation des fonctions de base du téléphone Émission ou réception d’un appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 40 3 Pour émettre ou répondre à un appel, effectuez l’une des opérations suivantes : • Décrochez le combiné. • Appuyez sur le bouton Haut-parleur. • Appuyez sur le bouton Casque. • Appuyez sur un bouton de ligne vert (pour passer un appel) ou émettant une lumière rouge clignotante (pour répondre à un appel). (Ne s'applique pas au modèle Cisco SPA 502G.) Si vous êtes en train de recevoir un appel et qu'un autre appel arrive, appuyez sur le bouton de la ligne émettant une lumière rouge clignotante ou appuyez sur le bouton Attente pour mettre le premier appel en attente et répondre à l'appel entrant. Pour reprendre le premier appel, appuyez sur le bouton de la ligne correspondant à l'appel ou sélectionnez-le à l'aide de la flèche montante ou descendante du bouton de navigation, puis appuyez sur la touche de fonction Reprend (Cisco SPA 502G). Utilisation de l’assistance à la numérotation Si l'assistance à la numérotation est activée lors de l’émission d’un appel, les numéros correspondant aux derniers appels passés ou reçus s’affichent à l’écran lorsque vous commencez à composer votre numéro. REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. Pour choisir un des numéros affichés : ÉTAPE 1 Utilisez le bouton de navigation pour faire défiler l’affichage et mettre un numéro en surbrillance sur l’écran LCD. ÉTAPE 2 Appuyez sur Compos pour passer l'appel. Pour obtenir plus d'informations sur l'activation de cette fonction, reportez-vous à « Activation de l’assistance à la numérotation » à la page 64.Utilisation des fonctions de base du téléphone Mise en attente d’un appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 41 3 Mise en attente d’un appel Pour mettre un appel en attente, appuyez sur le bouton Attente. L'interlocuteur peut alors entendre une série de signaux sonores ou de la musique pour lui indiquer que l'appel est en attente. Un seul appel peut être actif à la fois. Le bouton Attente permet de mettre en attente l'appel actif. Reprise d’un appel Pour reprendre l’appel, appuyez sur le bouton de la ligne émettant une lumière rouge clignotante pour l’appel. (Sur le modèle Cisco SPA 502G, appuyez sur la touche de fonction Reprend.) Fin d’un appel Pour terminer un appel : • Si vous utilisez le combiné, raccrochez. • Si vous utilisez le haut-parleur, appuyez sur le bouton Haut-parleur. • Si vous utilisez le casque, appuyez sur le bouton Casque (filaire) ou raccrochez le combiné (sans fil). Transfert d’appel Vous pouvez effectuer les types de transferts suivants : • Transfert accompagné : vous appelez la personne à laquelle vous transférez l'appel et : - vous effectuez le transfert pendant que le téléphone sonne ; - vous attendez que la personne réponde pour transférer l’appel. • Transfert direct : vous effectuez le transfert sans parler à l’interlocuteur auquel vous transférez l’appel.Utilisation des fonctions de base du téléphone Transfert d’appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 42 3 Transfert accompagné Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : ÉTAPE 1 Lors d’un appel actif, appuyez sur transf. L’appel est mis en attente et une nouvelle ligne est ouverte pour composer le numéro. ÉTAPE 2 Effectuez l’une des opérations suivantes : • Entrez le numéro auquel vous souhaitez transférer l'appel, puis appuyez sur comp ou attendez quelques secondes. • Appuyez sur rép et choisissez un numéro dans le répertoire personnel ou sélectionnez Nouvelle entrée et appuyez sur comp. Si vous raccrochez avant que le deuxième appel ne sonne, le transfert échoue et le premier appel est déconnecté. En cas d'erreur de composition, utilisez la touche delChar, effacer ou annul (non applicable au Cisco SPA 502G) pour modifier le numéro avant de transférer l'appel. ÉTAPE 3 Appuyez sur transf pendant la sonnerie ou à tout moment lorsque votre interlocuteur a répondu. Cisco SPA 501G : ÉTAPE 1 Au cours d'un appel actif, appuyez sur le bouton Transfert. ÉTAPE 2 Entrez le numéro auquel vous voulez transférer l’appel. ÉTAPE 3 Lorsque vous entendez la sonnerie ou que votre interlocuteur a répondu, appuyez à nouveau sur le bouton Transfert. Transfert direct Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : ÉTAPE 1 Pendant un appel actif, appuyez sur la touche de fonction tranSi. ÉTAPE 2 Entrez le numéro auquel vous souhaitez transférer l'appel et appuyez sur comp. L’appel est transféré et aucune autre intervention de votre part n’est nécessaire.Utilisation des fonctions de base du téléphone Recomposition d’un numéro Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 43 3 Transfert d’un appel en attente vers un appel actif REMARQUE Ceci ne s'applique pas au modèle Cisco SPA 501G. Si vous avez un appel en attente et un appel actif, vous pouvez transférer l’un de ces appels vers l’autre pour mettre en relation les deux interlocuteurs. (Il ne s’agit pas d’une conférence téléphonique, car vous quittez l’appel après le transfert.) Lorsque vous avez un appel actif et un ou plusieurs appels en attente, appuyez sur la touche de fonction tranLx. • Si vous avez uniquement un appel en attente, il est transféré à l’interlocuteur actif et vous êtes déconnecté. • Si vous avez plusieurs appels en attente, choisissez celui à transférer en appuyant sur le bouton de ligne correspondant. Recomposition d’un numéro Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : Pour rappeler le dernier numéro appelé, appuyez deux fois sur la touche de fonction bis. Pour rappeler un autre numéro : ÉTAPE 1 Appuyez sur la touche de fonction bis et sélectionnez le numéro souhaité. ÉTAPE 2 (Facultatif) Appuyez sur éditer pour sélectionner un numéro et le modifier (par exemple, pour ajouter un indicatif téléphonique). Une fois que vous avez terminé, appuyez sur ok. ÉTAPE 3 Décrochez le combiné ou appuyez sur comp pour composer automatiquement le numéro sélectionné. Cisco SPA 501G : Pour rappeler le dernier numéro, appuyez sur le bouton Bis. Utilisation des fonctions de base du téléphone Affichage et rappel des appels manqués Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 44 3 Affichage et rappel des appels manqués L'écran LCD du téléphone IP vous indique si vous avez reçu un appel auquel vous n'avez pas répondu. REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. Pour rappeler un appel manqué : • Si l’écran LCD indique un appel manqué, appuyez sur la touche de fonction dar pour revenir au dernier appel manqué. Appuyez sur la touche de fonction manq pour afficher la liste des appels manqués, sélectionnez un appel et appuyez sur comp. • Si l'écran LCD n'affiche aucun appel manqué, vous pouvez rappeler un numéro à partir de la liste des appels manqués : a. Appuyez sur le bouton Configuration. b. Sélectionnez Historique des appels. c. Sélectionnez Appels manqués. d. Choisissez l'appel à rappeler et appuyez sur comp. REMARQUE Si l’appel provient d’un numéro interurbain, vous devrez peut-être modifier l’appel avant de pouvoir rappeler le numéro. Appuyez sur la touche de fonction éditer pour modifier l’appel et effectuez votre modification à l’aide des boutons de fonction et du clavier. Pour afficher la liste des appels manqués : • Si l’écran LCD affiche un appel manqué, appuyez sur la touche de fonction manq pour afficher la liste des appels manqués. • Si l’écran LCD n’affiche pas d’appel manqué : a. Appuyez sur le bouton Configuration. b. Sélectionnez Historique des appels. c. Sélectionnez Appels manqués.Utilisation des fonctions de base du téléphone Activation et désactivation du raccourci des appels manqués Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 45 3 Activation et désactivation du raccourci des appels manqués Cette option permet d’activer ou de désactiver les touches de fonction dar et manq qui s’affichent sur l’écran du téléphone IP en cas d’appel manqué. REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. Pour accéder à cette option : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Racc. appel manqué et appuyez sur éditer. ÉTAPE 4 Appuyez sur o/n pour activer ou désactiver la fonction. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur Enreg.. Renvoi d'appel Vous pouvez renvoyer tous les appels, les appels reçus lorsque le téléphone est occupé ou les appels manqués. Vous pouvez également définir les options de renvoi à partir de votre ordinateur à l'aide de l'interface Web du téléphone IP (reportez-vous à la section « Configuration du renvoi d'appel » à la page 82). REMARQUE Pour le modèle Cisco SPA 501G, vous pouvez utiliser uniquement l'interface Web du téléphone IP ou des codes étoile pour définir des renvois d'appels. Les codes étoile appropriés sont indiqués dans les instructions ci-dessous.Utilisation des fonctions de base du téléphone Renvoi d'appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 46 3 Renvoi de tous les appels À l'aide de la touche de fonction renvoi : ÉTAPE 1 Appuyez sur la touche de fonction renvoi. ÉTAPE 2 Entrez le numéro vers lequel vous voulez renvoyer tous les appels ; par exemple votre boîte vocale, un autre poste ou une ligne extérieure. Si vous renvoyez les appels vers une ligne extérieure, veillez à utiliser les codes d’accès et les indicatifs requis. ÉTAPE 3 Appuyez sur comp. L'écran LCD affiche les appels renvoyés. À l’aide du code étoile : Appuyez sur *72 et entrez le numéro vers lequel vous souhaitez renvoyer tous les appels. À l’aide du bouton Configuration : ÉTAPE 1 Appuyez sur le bouton Configuration et sélectionnez Transfert d'appels > Renvoi de tous les appels. ÉTAPE 2 Appuyez sur éditer. ÉTAPE 3 Entrez le numéro vers lequel vous voulez renvoyer tous les appels ; par exemple votre boîte vocale, un autre poste ou une ligne extérieure. Si vous renvoyez les appels vers une ligne extérieure, veillez à utiliser les codes d’accès et les indicatifs requis. ÉTAPE 4 Appuyez sur OK. ÉTAPE 5 Appuyez sur Enreg.. Renvoi d'appel lorsque votre téléphone est occupé À l’aide du code étoile : Appuyez sur *90 et entrez le numéro vers lequel vous souhaitez renvoyer les appels.Utilisation des fonctions de base du téléphone Renvoi d'appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 47 3 À l’aide du bouton Configuration : ÉTAPE 1 Appuyez sur le bouton Configuration et sélectionnez Transfert d'appels > Renvoi si numéro occupé. ÉTAPE 2 Appuyez sur la touche de fonction éditer. ÉTAPE 3 Entrez le numéro vers lequel vous souhaitez renvoyer tous les appels (par exemple, un autre poste ou une ligne extérieure). En cas de renvoi vers une ligne extérieure, veillez à utiliser les codes d’accès et les indicatifs requis. Pour entrer « vm » (connexion à la messagerie vocale si l’administrateur du système téléphonique a configuré cette fonction), appuyez sur le bouton de navigation droit, puis sur la touche de fonction alpha et tapez les lettres à l’aide du clavier. Appuyez sur le bouton de navigation gauche. ÉTAPE 4 Appuyez sur OK. ÉTAPE 5 Appuyez sur Enreg.. Renvoi des appels manqués À l’aide du code étoile : Appuyez sur *92 et entrez le numéro vers lequel vous souhaitez renvoyer les appels. À l’aide du bouton Configuration : ÉTAPE 1 Dans l'écran Transfert d'appels, vérifiez que l'option Renvoi si pas de réponse s'affiche en surbrillance et appuyez sur la touche de fonction éditer. ÉTAPE 2 Entrez « vm » pour la messagerie vocale ou le numéro vers lequel les appels doivent être renvoyés (par exemple, un autre poste ou une liste extérieure). Si vous renvoyez les appels vers une ligne extérieure, veillez à utiliser les codes d’accès et les indicatifs requis. ÉTAPE 3 Appuyez sur OK. ÉTAPE 4 Appuyez sur Enreg..Utilisation des fonctions de base du téléphone Configuration de la fonction Ne pas déranger Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 48 3 Attente avant le renvoi d’appel si pas de réponse ÉTAPE 1 Dans l'écran Transfert d'appels, vérifiez que l'option Renvoi si pas de réponse après un moment défini s'affiche en surbrillance et appuyez sur la touche de fonction éditer. ÉTAPE 2 Entrez la période d’attente en secondes pour les appels manqués. ÉTAPE 3 Appuyez sur OK. ÉTAPE 4 Appuyez sur Enreg.. Arrêt du renvoi d'appel Pour arrêter le renvoi d’appel, appuyez sur la touche de fonction -Rvap. Pour arrêter le renvoi, vous pouvez également appuyer sur le bouton Configuration et sélectionner Transfert d'appels > éditer. Appuyez sur effacer, puis sur ok. Appuyez sur Enreg.. À l’aide de codes étoile : • Entrez *73 pour désactiver le renvoi d’appel. • Entrez *91 pour désactiver le renvoi d’appel si occupé. • Entrez *93 pour désactiver le renvoi d’appel si pas de réponse. Configuration de la fonction Ne pas déranger La fonctionnalité Ne pas déranger vous permet de couper la sonnerie du téléphone en cas d'appel entrant. Si la messagerie vocale est configurée, tous les appels entrants sont immédiatement dirigés vers la messagerie. Sinon, l’appelant entend un signal ou un message indiquant que la ligne est occupée. Vous pouvez également définir la fonction Ne pas déranger à partir de votre ordinateur à l'aide de l'interface Web du téléphone IP (reportez-vous à la section « Configuration de la fonction Ne pas déranger » à la page 82).Utilisation des fonctions de base du téléphone Configuration de la fonction Ne pas déranger Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 49 3 REMARQUE Pour le modèle Cisco SPA 501G, vous pouvez définir la fonction Ne pas déranger uniquement à l'aide de l'interface Web du téléphone IP ou du code étoile. Activation de la fonction Ne pas déranger À l’aide de la touche de fonction npd : Pour activer la fonction Ne pas déranger, appuyez sur la touche de fonction npd. L'écran LCD indique que la fonction Ne pas déranger est activée sur le téléphone. À l’aide du bouton Configuration : Vous pouvez également accéder à la fonction Ne pas déranger en procédant comme suit : ÉTAPE 1 Appuyez sur le bouton Configuration et sélectionnez Préférences > Ne pas déranger. ÉTAPE 2 Appuyez sur la touche de fonction éditer. ÉTAPE 3 Appuyez sur o/n pour sélectionner o, puis sur ok. ÉTAPE 4 Appuyez sur Enreg.. À l’aide du code étoile : Entrez *78 pour activer la fonction Ne pas déranger. Désactivation de la fonction Ne pas déranger À l’aide de la touche de fonction -npd : Pour désactiver la fonction Do Not Disturb, appuyez sur la touche de fonction -npd. À l’aide du bouton Configuration : Pour désactiver la fonction Ne pas déranger, vous pouvez également appuyer sur le bouton Configuration et sélectionner Préférences > Ne pas déranger. À l’aide du code étoile : Entrez *79 pour désactiver la fonction Ne pas déranger.Utilisation des fonctions de base du téléphone Activation et désactivation de la fonction d'appel en attente Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 50 3 Activation et désactivation de la fonction d'appel en attente La fonction d'appel en attente vous informe pendant un appel qu'un deuxième appel est en cours en faisant sonner votre téléphone et en affichant un message d'état. Si vous désactivez cette fonction, les appels entrants ne sonnent pas sur votre téléphone si vous êtes déjà en ligne et l’appelant entend un signal ou un message indiquant que la ligne est occupée. Vous pouvez également activer et désactiver la fonction d'appel en attente à partir de votre ordinateur à l'aide de l'interface Web du téléphone IP. Reportez-vous à la section « Configuration de la fonction d'appel en attente » à la page 83. REMARQUE Pour le modèle Cisco SPA 501G, vous pouvez configurer la fonction d'appel en attente uniquement à l'aide de l'interface Web du téléphone IP ou d'un code étoile. À l’aide du bouton Configuration : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Appel en attente et appuyez sur éditer. ÉTAPE 4 Appuyez sur la touche de fonction o/n pour activer ou désactiver la fonction. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur Enreg.. À l’aide du code étoile : • Entrez *56 pour activer la fonction d'appel en attente. • Entrez *71 avant de composer un numéro pour activer la fonction pour cet appel. • Entrez *57 pour désactiver la fonction d'appel en attente. • Entrez *72 avant de composer un numéro pour désactiver la fonction pour cet appel.Utilisation des fonctions de base du téléphone Prise d’appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 51 3 Prise d’appel Vous pouvez prendre un appel qui sonne sur un autre poste. En fonction de la configuration du réseau téléphonique, vous pouvez prendre un appel dans les situations suivantes : • Prendre un appel qui sonne sur un poste dans votre groupe à l’aide de la touche de fonction décGr. (Non disponible sur le modèle Cisco SPA 501G.) • Prendre un appel qui sonne sur un poste spécifique à l’aide de la touche de fonction décro. (Non disponible sur le modèle Cisco SPA 501G.) • Prendre un appel qui sonne sur un poste configuré sur l’un des boutons de ligne du téléphone. Nécessite l’intervention de l’administrateur du système téléphonique. (Non disponible sur le modèle Cisco SPA 502G.) Pour prendre un appel qui sonne sur un poste dans votre groupe : ÉTAPE 1 Appuyez sur la touche de fonction décGr. Le téléphone affiche toutes les stations du groupe qui sonnent. Appuyez sur comp pour afficher la liste des appels. ÉTAPE 2 Choisissez l'appel que vous voulez prendre et appuyez sur comp. Pour prendre un appel qui sonne sur un poste spécifique : ÉTAPE 1 Appuyez sur la touche de fonction décro. ÉTAPE 2 Entrez le numéro de poste du téléphone dont vous voulez prendre l’appel, puis appuyez sur comp. ÉTAPE 3 Appuyez une nouvelle fois sur comp. Pour prendre un appel qui sonne sur un poste configuré sur l’un des boutons de ligne du téléphone, appuyez sur le bouton de la ligne qui clignote. Parcage d'un appel Vous pouvez « parquer » un appel sur une ligne spécifique pour qu'un autre employé de votre société puisse prendre l'appel. L'appel est actif jusqu'à ce qu'il soit retiré de la file d'attente ou que l'interlocuteur raccroche.Utilisation des fonctions de base du téléphone Parcage d'un appel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 52 3 REMARQUE Non disponible sur le modèle Cisco SPA 501G. Pour parquer un appel : ÉTAPE 1 Lorsque vous avez un appel actif, appuyez sur la touche de fonction parq. ÉTAPE 2 Entrez un numéro pour identifier la ligne de mise en file d’attente et appuyez sur comp. Le numéro de la ligne de parcage ne correspond pas à un véritable numéro de poste et vous pouvez opter pour n’importe quel numéro simple à mémoriser (100, par exemple). L'appel est ensuite parqué sur cette ligne et l'appelant entend une musique ou des messages d'attente. ÉTAPE 3 Vous ou un autre utilisateur devez ensuite retirer l’appel de la file d’attente. Pour cela, vous pouvez utiliser la touche de fonction déparq (si vous connaissez le numéro de la ligne) ou afficher la liste des appels parqués et retirer cet appel de la liste. Pour retirer l’appel de la file d’attente si vous connaissez le numéro de la ligne : ÉTAPE 1 Appuyez sur la touche de fonction déparq. ÉTAPE 2 Entrez le numéro de la ligne de parcage (par exemple, le numéro entré à l’étape 2 de la procédure de parcage d'un appel). ÉTAPE 3 Appuyez sur comp. L’appel est pris sur votre téléphone. Pour afficher la liste des appels parqués (et retirer des appels de cette liste) : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Etat de la file d'attente. ÉTAPE 3 Choisissez l’appel parqué que vous souhaitez récupérer et appuyez sur déparq.Utilisation des fonctions de base du téléphone Conférence téléphonique à trois Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 53 3 Conférence téléphonique à trois Pour établir une conférence téléphonique, vous pouvez procéder comme suit : • Appeler les deux numéros et appuyer sur la touche de fonction conf. • Établir une conférence entre un appel actif et un appel en attente à l'aide de la touche de fonction confLX (non disponible sur le modèle Cisco SPA 501G) Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : Pour établir une conférence téléphonique : ÉTAPE 1 Appuyez sur la touche de fonction conf pendant un appel actif. Le premier appel est mis en attente, une deuxième ligne est ouverte et une tonalité se fait entendre. ÉTAPE 2 Composez le numéro de téléphone de la deuxième personne. ÉTAPE 3 Appuyez une nouvelle fois sur la touche de fonction conf. Les trois interlocuteurs sont alors connectés à la conférence téléphonique. Lorsque vous raccrochez, les deux autres interlocuteurs sont déconnectés. Cisco SPA 501G : ÉTAPE 1 Appuyez sur le bouton Conférence pendant un appel actif. Le premier appel est mis en attente, une deuxième ligne est ouverte et une tonalité se fait entendre. ÉTAPE 2 Composez le numéro de téléphone de la deuxième personne. ÉTAPE 3 Appuyez une nouvelle fois sur le bouton Conférence. Les trois interlocuteurs sont alors connectés à la conférence téléphonique. Lorsque vous raccrochez, les deux autres interlocuteurs sont déconnectés.Utilisation des fonctions de base du téléphone Utilisation des répertoires téléphoniques Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 54 3 Mise en place d'une conférence entre un appel en attente et un appel actif REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. Si vous avez un appel en attente et un appel actif, vous pouvez établir une conférence entre l’appel actif, l’appel en attente et vous-même. Lorsque vous avez un appel actif et un ou plusieurs appels en attente, appuyez sur la touche de fonction confLx. • Si vous avez un seul appel en attente, la conférence est établie entre les deux appels et vous. • Si vous avez plusieurs appels en attente, choisissez celui qui doit participer à la conférence en appuyant sur le bouton de ligne correspondant. Utilisation des répertoires téléphoniques Les téléphones IP proposent plusieurs types de répertoires téléphoniques en fonction du modèle du téléphone et de la configuration effectuée par l’administrateur système. En règle générale, les téléphones fournissent les types de répertoires suivants : • Répertoire personnel : pour le stockage et la consultation des numéros couramment composés. Vous pouvez également composer les numéros à partir du répertoire. • Répertoire d’entreprise : liste des numéros de téléphone et des postes de la société. Selon la configuration du réseau téléphonique, vous pouvez avoir accès aux répertoires suivants : - Répertoire d'entreprise (LVS) - Répertoire LDAP REMARQUE (Non disponible sur le modèle Cisco SPA 501G.)Utilisation des fonctions de base du téléphone Utilisation des répertoires téléphoniques Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 55 3 Utilisation du répertoire personnel Pour accéder au répertoire personnel, appuyez sur la touche de fonction rép ou sur le bouton Configuration et sélectionnez Répertoire. Vous pouvez également consulter et modifier le répertoire à partir de votre ordinateur à l’aide de l’interface Web du téléphone IP. Reportez-vous à la section « Utilisation du répertoire personnel » à la page 85. Pour ajouter une nouvelle entrée au répertoire : ÉTAPE 1 Dans l’écran Répertoire, sélectionnez Nouvelle entrée et appuyez sur la touche de fonction ajout. ÉTAPE 2 Utilisez le clavier pour saisir le nom de l’entrée du répertoire. Appuyez à plusieurs reprises sur une touche chiffrée pour afficher une autre lettre correspondant à ce chiffre. Par exemple, pour entrer Mary, appuyez une fois sur le 6 et relâchez (M), une fois sur le 2 et relâchez (A), trois fois rapides sur le 7 et relâchez (R) et trois fois rapides sur le 9 et relâchez (Y). Utilisez les touches de fonction supCar pour supprimer des lettres, <<< et >>> pour vous déplacer d'un caractère vers la gauche ou la droite, et effacer pour effacer la totalité du nom. Lorsque le nom est entré, accédez au champ Numéro à l’aide du bouton de navigation. ÉTAPE 3 Entrez le numéro de téléphone, y compris les chiffres à composer pour accéder à une ligne extérieure et l’indicatif approprié si nécessaire. ÉTAPE 4 (Facultatif) Pour changer le type de sonnerie de l’appelant : a. Appuyez sur la touche de fonction option. b. Parcourez les différents types de sonneries. c. Appuyez sur la touche de fonction Jouer pour écouter la sonnerie sélectionnée ou sélect pour affecter cette sonnerie à la personne dont vous ajoutez le numéro au répertoire. ÉTAPE 5 Appuyez sur enreg pour enregistrer l'entrée.Utilisation des fonctions de base du téléphone Utilisation des répertoires téléphoniques Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 56 3 Utilisation du répertoire d’entreprise REMARQUE Selon votre fournisseur de services téléphoniques Internet ou la configuration du réseau de l’entreprise, il est possible que vous ne disposiez d’aucun répertoire d’entreprise. Pour utiliser le répertoire d’entreprise : ÉTAPE 1 Appuyez sur la touche de fonction rép ou bien appuyez sur le bouton Configuration et sélectionnez Répertoirey. ÉTAPE 2 Sélectionnez Nouvelle entrée. ÉTAPE 3 Sélectionnez une entrée et appuyez sur la touche de fonction comp. Appuyez sur annul pour quitter. Pour utiliser le répertoire LDAP : ÉTAPE 1 Appuyez sur la touche de fonction rép ou bien appuyez sur le bouton Configuration et sélectionnez Répertoires. ÉTAPE 2 Accédez à Nom de répertoire LDAP et appuyez sur Sélect. REMARQUE Le nom du répertoire est configuré par l’administrateur du système téléphonique et peut varier. ÉTAPE 3 Renseignez les champs et appuyez sur recher.. ÉTAPE 4 Dans les résultats, appuyez sur Compos pour composer le numéro ou sélectionnez l'une des autres options disponibles.Utilisation des fonctions de base du téléphone Utilisation des listes de l'historique des appels Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 57 3 Utilisation des listes de l'historique des appels Vous pouvez également consulter les listes de l’historique des appels à partir de votre ordinateur à l’aide de l’interface Web du téléphone IP. Reportez-vous à la section « Consultation des listes de l'historique des appels » à la page 85. REMARQUE L'interface Web permet également de consulter les listes de l'historique des appels pour le Cisco SPA 501G. Consultation des listes de l’historique des appels Pour consulter les listes de l’historique des appels : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Historique des appels. ÉTAPE 3 Sélectionnez la liste à afficher. Les listes de l’historique des appels suivantes sont disponibles : • Liste de rappel : affiche les 60 derniers numéros composés depuis le téléphone. • Appels pris : affiche l’identifiant des appelants des 60 derniers appels auxquels vous avez répondu. • Appels manqués : affiche les 60 derniers appels manqués.Utilisation des fonctions de base du téléphone Utilisation des listes de l'historique des appels Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 58 3 Appel à partir des listes de l’historique des appels Pour composer un numéro à partir d'une liste de l'historique des appels : ÉTAPE 1 Sélectionnez l’appel. ÉTAPE 2 Appuyez sur comp. REMARQUE Si l’appel provient d’un numéro interurbain, vous pouvez être amené à modifier le numéro avant de pouvoir le composer. Appuyez sur la touche de fonction Modif pour modifier l'appel et effectuez votre modification à l'aide des boutons de fonction et du clavier. Suppression d’un numéro d’une liste d’historique des appels ÉTAPE 1 Sélectionnez un appel dans la liste des rappels, des appels reçus ou des appels manqués. ÉTAPE 2 Appuyez sur suppre. ÉTAPE 3 Appuyez sur OK. Enregistrement d’un numéro d’une liste d’historique des appels dans votre répertoire ÉTAPE 1 Sélectionnez un appel dans la liste des rappels, des appels reçus ou des appels manqués. ÉTAPE 2 À l'aide du bouton de navigation, déplacez-vous vers la droite pour accéder à d'autres boutons de fonction et appuyez sur enreg. ÉTAPE 3 Modifiez les informations si nécessaire et appuyez une nouvelle fois sur enreg. L’entrée est ajoutée à votre répertoire.Utilisation des fonctions de base du téléphone Définition ou modification d’un mot de passe de téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 59 3 Définition ou modification d’un mot de passe de téléphone Vous pouvez définir ou modifier le mot de passe de votre téléphone pour empêcher toute utilisation non autorisée. Pour définir un mot de passe pour le téléphone : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Définir le mot de passe. ÉTAPE 3 Entrez un mot de passe numérique. Entrez une deuxième fois le même mot de passe. ÉTAPE 4 Appuyez sur enreg. Accès à la messagerie vocale Pour accéder à la messagerie vocale, appuyez sur le bouton Messages du téléphone. L'administrateur système doit configurer votre téléphone avec le numéro de messagerie vocale approprié pour que vous accédiez automatiquement à votre système de messagerie vocale en appuyant sur le bouton Messages. Pour modifier le numéro de votre messagerie vocale (par exemple, si votre téléphone ne fait pas partie d’un système vocal Cisco SPA 9000 et si vous disposez d’une messagerie vocale externe), procédez comme suit : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Accédez à la Messagerie vocale et appuyez sur sélect. ÉTAPE 3 Entrez le numéro à composer pour la messagerie vocale. Pour un système vocal Cisco SPA 9000, il s'agit normalement de « vmm ». Pour un système externe, entrez le numéro de téléphone, y compris les numéros à composer pour accéder à une ligne extérieure.Utilisation des fonctions de base du téléphone Accès à la messagerie vocale Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 60 3 CONSEIL Pour effacer le contenu du champ, appuyez sur effacer. Pour entrer des lettres, appuyez sur le bouton de navigation droit pour faire défiler l'affichage, puis appuyez sur la touche de fonction alpha. ÉTAPE 4 Appuyez sur enreg.4 Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 61 Utilisation des fonctionnalités avancées du téléphone Ce chapitre explique comment configurer les fonctionnalités avancées du téléphone IP. Il comprend les sections suivantes : • Configuration des fonctions de confidentialité et de sécurité, page 62 • Création de numérotations rapides, page 65 • Utilisation de la numérotation rapide, page 66 • Utilisation de la fonction de radiomessagerie, page 67 • Contrôle d’un autre téléphone et accès à celui-ci depuis votre téléphone, page 68 • Personnalisation de l’écran LCD, page 68 • Utilisation des sonneries, page 71 • Configuration de la date et de l’heure du téléphone, page 72 • Utilisation des codes étoile, page 73 • Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G, page 75 • Procédures avancées destinées au personnel de l’assistance technique, page 78Utilisation des fonctionnalités avancées du téléphone Configuration des fonctions de confidentialité et de sécurité Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 62 4 Configuration des fonctions de confidentialité et de sécurité Vous pouvez également configurer ces fonctions à l’aide de votre ordinateur ou de l’interface Web du téléphone IP. Reportez-vous aux sections « Blocage de l'ID de l'appelant » à la page 84 et « Blocage des appels anonymes » à la page 84. REMARQUE Pour le modèle Cisco SPA 501G, vous devez configurer ces fonctions à l'aide de l'interface Web du téléphone IP ou de codes étoile (voir ci-dessous). Blocage de l’ID de l’appelant Vous pouvez bloquer l’ID de l’appelant sur votre téléphone afin que la personne que vous appelez ne puisse pas voir votre numéro de téléphone. À l’aide du bouton Configuration : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Bloque l'identification de l'appelant et appuyez sur éditer. ÉTAPE 4 Appuyez sur o/n et choisissez oui. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur enreg. À l’aide du code étoile : Appuyez sur *67 avant de composer le numéro. (Appuyez sur *68 pour désactiver le blocage.) Blocage des appels anonymes Le blocage des appels anonymes refuse les appels dont l’ID de l’appelant est inconnu (par exemple, si un appelant a configuré son téléphone pour que son ID d’appelant n’apparaisse pas, l’appel est considéré comme anonyme). L’appelant entend un signal ou un message indiquant que la ligne est occupée.Utilisation des fonctionnalités avancées du téléphone Configuration des fonctions de confidentialité et de sécurité Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 63 4 À l’aide du bouton Configuration : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Bloquer les appels anonymes et appuyez sur éditer. ÉTAPE 4 Appuyez sur o/n et choisissez oui. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur enreg. À l’aide du code étoile : Appuyez sur *77. Vous devez appuyer sur *87 pour désactiver le rejet des appels anonymes. Utilisation de l'appel sécurisé La fonction d'appel sécurisé permet de crypter l'appel actif pour éviter les écoutes. Avant d'activer la fonction d'appel sécurisé, vérifiez auprès de votre opérateur si elle est disponible. À l'aide du bouton Configuration (ne s'applique pas au modèle Cisco SPA 501G) : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 SélectionnezAppel sécurisé et appuyez sur éditer. ÉTAPE 4 Appuyez sur o/n et choisissez oui. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur enreg. Lorsque vous composez un numéro, vous entendez une tonalité avant l’appel.Utilisation des fonctionnalités avancées du téléphone Activation de l’assistance à la numérotation Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 64 4 À l’aide de codes étoile : • *16 active la fonction d'appel sécurisé pour tous les appels. • *18 active la fonction d'appel sécurisé pour un seul appel. Pour désactiver la fonction d'appel sécurisé : • *16 désactive la fonction d'appel sécurisé pour tous les appels. • *18 désactive la fonction d'appel sécurisé pour un seul appel. Activation de l’assistance à la numérotation Si vous activez l’assistance à la numérotation, lorsque vous passez des appels, l’écran LCD affiche les numéros correspondants du répertoire et des listes d’historique des appels. REMARQUE Cette fonction n'est pas disponible sur le modèle Cisco SPA 501G. Pour activer l’assistance à la numérotation : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Préférences de numérotation et appuyez sur éditer. ÉTAPE 4 Appuyez sur o/n et choisissez oui. ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur enreg. Si l'assistance à la numérotation est activée lorsque vous passez des appels, utilisez le bouton de navigation pour parcourir la liste des numéros sur l'écran LCD, sélectionnez un numéro, puis appuyez sur comp pour le composer. Utilisation des fonctionnalités avancées du téléphone Création de numérotations rapides Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 65 4 Création de numérotations rapides Vous pouvez configurer différents types de numérotations rapides : • Vous pouvez affecter un bouton de ligne disponible sur votre téléphone à la numérotation rapide. • Selon la configuration des postes et le nombre de boutons de ligne du téléphone, vous pouvez définir jusqu'à 7 numérotations rapides sur les boutons de ligne. • Si une numérotation rapide est affectée à un numéro, ce numéro est composé automatiquement lorsque vous appuyez sur la touche correspondante. Vous pouvez définir jusqu'à 8 numérotations rapides de ce type. Il peut s’agir d’un numéro de téléphone, d’une adresse IP ou d’une URL. Vous pouvez créer et modifier des numérotations rapides au moyen de votre ordinateur et de l’interface Web pour téléphone IP. Reportez-vous à la section « Création de numérotations rapides » à la page 86. REMARQUE Pour le modèle Cisco SPA 501G, créez les numérotations rapides à l'aide de l'interface Web du téléphone IP. Création de numérotations rapides sur des boutons de ligne disponibles ÉTAPE 1 Appuyez sur un bouton de ligne inutilisé et maintenez-le enfoncé pendant trois secondes. La fenêtre Définir numérot. abrégée s’affiche. ÉTAPE 2 Entrez le nom de la numérotation rapide. ÉTAPE 3 Appuyez sur la touche Flèche descendante pour accéder au champ de saisie du numéro de téléphone. Entrez le numéro de téléphone et appuyez sur Enreg.. ÉTAPE 4 Une fois créée, la numérotation rapide s'affiche en regard du bouton de ligne. Appuyez sur ce bouton pour utiliser la numérotation rapide.Utilisation des fonctionnalités avancées du téléphone Utilisation de la numérotation rapide Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 66 4 REMARQUE Pour les modèles Cisco SPA 501G et Cisco SPA 502G, l'administrateur du système téléphonique peut utiliser l'interface Web pour affecter des numérotations rapides aux boutons de ligne disponibles. Cette fonction administrative est accessible à partir des pages Admin > Configuration avancée. Création de numérotations rapides numériques ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Numérotation rapide. ÉTAPE 3 Pour créer une nouvelle numérotation rapide, faites défiler pour sélectionner une numérotation rapide inutilisée (marquée Not Assigned) Pour modifier une numérotation rapide existante, sélectionnez-la. ÉTAPE 4 Appuyez sur éditer. ÉTAPE 5 Entrez le numéro à affecter à la numérotation rapide et appuyez sur ok. Utilisation de la numérotation rapide Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : Pour appeler l'un des numéros de numérotation rapide que vous avez configurés, effectuez l'une des opérations suivantes : • Prenez une ligne et appuyez à l'aide du clavier sur le numéro correspondant à la numérotation rapide, puis appuyez sur Compos. • Appuyez sur le bouton Configuration, sélectionnez Numérotation rapide, choisissez le numéro et appuyez sur Compos. Cisco SPA 504G, SPA508G, SPA509G : Appuyez sur le bouton de ligne inutilisé configuré pour la numérotation rapide. Cisco SPA 501G : Sur le clavier, appuyez sur le numéro correspondant à la numérotation rapide et attendez quelques secondes.Utilisation des fonctionnalités avancées du téléphone Utilisation de la fonction de radiomessagerie Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 67 4 Utilisation de la fonction de radiomessagerie Le téléphone IP peut répondre automatiquement à des contacts provenant d'autres téléphones IP Cisco du système vocal Cisco SPA 9000. Lorsque votre téléphone reçoit un appel par radiomessagerie, il émet une série de signaux sonores et la communication audio bilatérale est établie avec le téléphone de l’appelant. Vous n'êtes pas obligé d'accepter ce type d'appel. REMARQUE Pour utiliser cette fonctionnalité, votre téléphone doit appartenir au réseau d'un système vocal Cisco SPA 9000. Appel d'un autre téléphone par radiomessagerie Pour appeler un autre téléphone par radiomessagerie, composez le *96 et le poste du téléphone concerné. Si le téléphone que vous appelez par radiomessagerie n'est pas configuré pour y répondre automatiquement, l'appel sonne comme un appel vocal standard. Appel d'un groupe de téléphones par radiomessagerie L'administrateur de votre système téléphonique peut configurer un groupe de téléphones que vous pouvez appeler simultanément par radiomessagerie. Chaque groupe de radiomessagerie est associé à un numéro. Votre administrateur doit vous indiquer les numéros des groupes configurés. Pour appeler un groupe par radiomessagerie, composez le *96 et le numéro du groupe. Configuration de la réponse automatique Pour configurer votre téléphone pour qu'il réponde aux appels par radiomessagerie : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Page Réponse automatique et appuyez sur éditer. ÉTAPE 4 Appuyez sur o/n et choisissez oui.Utilisation des fonctionnalités avancées du téléphone Contrôle d’un autre téléphone et accès à celui-ci depuis votre téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 68 4 ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur enreg. Contrôle d’un autre téléphone et accès à celui-ci depuis votre téléphone L'administrateur système peut configurer votre téléphone de sorte que vous puissiez contrôler le téléphone d'un autre utilisateur depuis votre téléphone. Si cette fonctionnalité est configurée, certains boutons de ligne de votre téléphone sont assignés pour afficher l’état des téléphones d’autres utilisateurs. Par exemple, si la ligne 4 est configurée pour afficher la ligne de Laurent, la couleur des DEL indique l'état de cette ligne : • Vert : la ligne est inactive. • Rouge (lumière continue) : la ligne est active ou en cours d’utilisation. • Rouge (lumière clignotante) : la ligne sonne. • Orange (lumière continue) : la ligne n’est pas enregistrée (inutilisable). • Orange (lumière clignotante) : la ligne n’est pas configurée correctement. Par ailleurs, si l'administrateur système a configuré cette fonctionnalité, vous pouvez appuyer sur ce même bouton de ligne (4) pour appeler le poste de Laurent ou prendre un appel sonnant sur son poste. REMARQUE Ne s'applique pas au modèle Cisco SPA 502G. Personnalisation de l’écran LCD REMARQUE Non disponible sur le modèle Cisco SPA 501G. Vous pouvez personnaliser l’écran LCD de plusieurs manières.Utilisation des fonctionnalités avancées du téléphone Personnalisation de l’écran LCD Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 69 4 Modification du contraste de l’écran LCD Vous pouvez également modifier le contraste de l’écran LCD à partir de votre ordinateur à l’aide de l’interface Web du téléphone IP. Reportez-vous à la section « Modification du contraste de l'écran LCD » à la page 88. Pour régler le contraste de l’écran LCD : ÉTAPE 1 Appuyez sur le bouton Configuration, accédez à LCD Contrast, sélectionnez cette option et appuyez sur le bouton sélect. ÉTAPE 2 Utilisez le bouton de navigation pour régler le contraste de l’écran. Appuyez sur le bouton de navigation gauche pour diminuer le contraste et sur le bouton de navigation droit pour l’augmenter. ÉTAPE 3 Appuyez sur enreg. Modification des paramètres de rétroéclairage de l'écran Le rétroéclairage de l'écran est automatiquement désactivé après une période donnée. Vous pouvez modifier cette période pour prolonger la durée du rétroéclairage ou pour que ce dernier soit toujours activé. ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Préférences. ÉTAPE 3 Sélectionnez Délai rétroéclairage et appuyez sur éditer. ÉTAPE 4 Appuyez sur Option pour sélectionner le réglage souhaité : • 10 secondes • 20 secondes • 30 secondes • always on ÉTAPE 5 Appuyez sur OK. ÉTAPE 6 Appuyez sur enreg.Utilisation des fonctionnalités avancées du téléphone Personnalisation de l’écran LCD Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 70 4 Configuration de l’économiseur d’écran du téléphone Vous pouvez activer l’économiseur d’écran du téléphone et préciser son apparence et la période d’inactivité au bout de laquelle il doit s’afficher. Certaines options peuvent être configurées à partir de votre ordinateur à l’aide de l’interface Web du téléphone IP. Reportez-vous à la section « Configuration de l'économiseur d'écran du téléphone » à la page 88. Pour configurer l’économiseur d’écran : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Mode économiseur d'écran. Pour activer l’économiseur d’écran : ÉTAPE 1 Dans Mode économiseur d'écran, sélectionnez Activer économ. écran et appuyez sur éditer. ÉTAPE 2 Appuyez sur o/n et choisissez oui. ÉTAPE 3 Appuyez sur OK. ÉTAPE 4 Appuyez sur enreg. Pour indiquer le délai avant l’activation de l’économiseur d’écran lorsque le téléphone est inactif : ÉTAPE 1 Dans Mode économiseur d'écran, sélectionnez Délai d'attente économiseur d'écran et appuyez sur éditer. ÉTAPE 2 Entrez le délai en secondes avant le démarrage de l'économiseur d'écran. ÉTAPE 3 Appuyez sur OK. ÉTAPE 4 Appuyez sur enreg.Utilisation des fonctionnalités avancées du téléphone Utilisation des sonneries Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 71 4 Pour modifier l’image de l’économiseur d’écran : ÉTAPE 1 Dans Mode économiseur d'écran, sélectionnez Icône économiseur d'écran et appuyez sur éditer. ÉTAPE 2 Appuyez sur option à plusieurs reprises pour faire défiler les options disponibles et sélectionner celle qui vous convient. Les options sont les suivantes : • Image de fond : affiche l’image de fond du téléphone. • DuréeStation : affiche l’ID de la station et l’heure sur l’image. • Verrou : affiche un verrou sur l’image. • Téléphone : affiche un téléphone sur l’image. • Date/Heure : affiche la date et l’heure sur l’image. ÉTAPE 3 Appuyez sur OK. ÉTAPE 4 Appuyez sur enreg. Activation de l’économiseur d’écran Pour activer immédiatement l’économiseur d’écran du téléphone : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Accédez à Mode économiseur d'écran et appuyez sur activ. (L’activation immédiate de l’économiseur d’écran n’est disponible que si la fonctionnalité correspondante est activée.) Utilisation des sonneries REMARQUE Non disponible sur le modèle Cisco SPA 501G. Chaque poste du téléphone peut avoir une sonnerie différente. Vous pouvez également créer vos propres sonneries.Utilisation des fonctionnalités avancées du téléphone Configuration de la date et de l’heure du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 72 4 Modification de la sonnerie Pour modifier une sonnerie : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Sonnerie. ÉTAPE 3 Sélectionnez le poste pour lequel vous souhaitez définir une sonnerie et appuyez sur changer. ÉTAPE 4 Faites défiler les sonneries et appuyez sur Jouer pour écouter la sonnerie en surbrillance. Appuyez sur sélect pour attribuer la sonnerie en surbrillance au poste. Configuration de la date et de l’heure du téléphone Réglage de la date et de l’heure du téléphone La date et l’heure de votre téléphone sont généralement définies par le serveur proxy SIP ou le serveur NTP. Cependant, vous pouvez procéder comme suit pour les modifier : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Sélectionnez Heure/date. ÉTAPE 3 Saisissez la date au format jj*mm*aa (elle s’affiche sous la forme j/m). ÉTAPE 4 Saisissez l’heure au format hh*mm*ss (elle s’affiche sous la forme h:mm). ÉTAPE 5 Si l'heure ne s'affiche pas correctement au format am (a) ou pm (p), vous pouvez l'ajuster à l'aide de l'option de décalage. Pour passer de a.m. à p.m., saisissez *12*00*00. Pour passer de p.m. à a.m., saisissez #12*00*00. ÉTAPE 6 Appuyez sur enreg. Vous pouvez définir une seule de ces options, si nécessaire.Utilisation des fonctionnalités avancées du téléphone Utilisation des codes étoile Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 73 4 Utilisation des codes étoile Le téléphone IP peut prendre en charge plusieurs codes étoile pour accéder à des services supplémentaires du téléphone. Vous devez saisir ces codes, qui commencent avec un astérisque (*), avant de composer un numéro de téléphone et d’accéder à ces services. Par exemple, pour bloquer l’ID de l’appelant (code étoile 67), vous devez composer le *67, puis le numéro de téléphone de votre correspondant. La liste des codes étoile courants est présentée ci-dessous. Il est possible que certains codes ne soient pas disponibles ; consultez votre administrateur système pour en savoir plus. Code Définition 16 Active la fonction d'appel sécurisé pour tous les appels.* Reportez-vous à Utilisation de l'appel sécurisé, page 63. 17 Désactive la fonction d'appel sécurisé pour tous les appels.* Reportez-vous à Utilisation de l'appel sécurisé, page 63. 18 Active la fonction d'appel sécurisé pour un seul appel.* Reportez-vous à Utilisation de l'appel sécurisé, page 63. 19 Désactive la fonction d'appel sécurisé pour un seul appel.* Reportez-vous à Utilisation de l'appel sécurisé, page 63. 36 Permet de prendre un appel qui sonne sur un autre poste.* Reportez-vous à Prise d’appel, page 51. 37 Permet de prendre un appel de groupe.* Reportez-vous à Prise d’appel, page 51. 38 Permet de parquer un appel.* Reportez-vous à Parcage d'un appel, page 51. 39 Permet de retirer un appel de la file d'attente.* Reportez-vous Parcage d'un appel, page 51. 56 Active la fonction d'appel en attente. Reportez-vous à Activation et désactivation de la fonction d'appel en attente, page 50. 57 Désactive la fonction d'appel en attente. Reportez-vous à Activation et désactivation de la fonction d'appel en attente, page 50.Utilisation des fonctionnalités avancées du téléphone Utilisation des codes étoile Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 74 4 66 Active la fonction de rappel. Le téléphone IP compose régulièrement un numéro occupé jusqu’à ce que l’appel sonne ou que le correspondant décroche, puis vous informe que l’appel est effectué. 67 Bloque l’ID de l’appelant. Reportez-vous à Blocage de l’ID de l’appelant, page 62. 68 Débloque l’ID de l’appelant. Reportez-vous à Blocage de l’ID de l’appelant, page 62. 69 Appelle le dernier numéro composé sur le téléphone. 70 Désactive la fonction d'appel en attente pour un seul appel. Reportez-vous à Activation et désactivation de la fonction d'appel en attente, page 50. 71 Active la fonction d'appel en attente pour un seul appel. Reportez-vous à Activation et désactivation de la fonction d'appel en attente, page 50. 72 Active le renvoi de tous les appels. Reportez-vous à Renvoi d'appel, page 45. 73 Désactive le renvoi de tous les appels. Reportez-vous à Renvoi d'appel, page 45. 77 Active le blocage des appels anonymes. Reportez-vous à Blocage des appels anonymes, page 62. 78 Active la fonctionnalité Ne pas déranger. Reportez-vous à Configuration de la fonction Ne pas déranger, page 48. 79 Désactive la fonctionnalité Ne pas déranger. Reportez-vous à Configuration de la fonction Ne pas déranger, page 48. 86 Désactive le rappel. 87 Désactive le blocage des appels anonymes. Reportez-vous à Blocage des appels anonymes, page 62. 90 Active le renvoi d'appel lorsque la ligne est occupée. Reportez-vous à Renvoi d'appel, page 45. 91 Désactive le renvoi d'appel lorsque la ligne est occupée. Reportez-vous à Renvoi d'appel, page 45. 92 Active le renvoi des appels manqués. Reportez-vous à Renvoi d'appel, page 45. Code DéfinitionUtilisation des fonctionnalités avancées du téléphone Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 75 4 *Votre téléphone IP doit appartenir au réseau d'un système vocal Cisco SPA 9000. **Le poste contacté doit appartenir au réseau d'un système vocal Cisco SPA 9000. Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G Le modèle Cisco SPA 501G propose un menu Interactive Voice Response. Vous pouvez entrer des options et recevoir des informations sur le téléphone et sur son utilisation. Pour accéder au menu IVR : ÉTAPE 1 Appuyez sur le bouton Configuration. Entrez l'option IVR en appuyant sur les chiffres correspondant à l'option souhaitée, puis appuyez sur #. Certains menus nécessitent la saisie d’informations ou de numéros supplémentaires. Les options fréquemment utilisées sont répertoriées dans le tableau suivant : 93 Désactive le renvoi des appels manqués. Reportez-vous à Renvoi d'appel, page 45. 96 Appelle un poste par radiomessagerie.** Reportez-vous à Utilisation de la fonction de radiomessagerie, page 67. 98 Effectue un transfert direct. Transfert d’appel, page 41. Code Définition Numéro Option 100 Indique si le protocole DHCP est activé. 110 Affiche l’adresse IP du téléphone. 120 Affiche le masque de réseau du téléphone. 130 Affiche l’adresse de la passerelle. 140 Affiche l’adresse MAC (matérielle) du téléphone.Utilisation des fonctionnalités avancées du téléphone Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 76 4 150 Affiche la version du logiciel du téléphone. 160 Affiche l’adresse du serveur DNS principal. 170 Affiche le port HTTP d’écoute du serveur Web (par défaut le 80). 180 Affiche l’adresse de multidiffusions IP (utilisée pour la communication du système Cisco SPA 9000 avec le téléphone IP). 220 Affiche la méthode de contrôle des appels (SIP ou SPCP). 221 Définit le contrôle des appels (entrez la valeur correspondant à la méthode choisie et appuyez sur #) : • 0 : SIP • 1 : SPCP Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. 73738 Rétablit les paramètres et éléments logiciels par défaut du téléphone. Appuyez sur 1 pour confirmer ou sur * pour quitter. Si vous optez pour la réinitialisation, raccrochez le combiné pour quitter et lancer le processus de restauration. 87778 Rétablit les paramètres utilisateur par défaut du téléphone (supprime tous les paramètres utilisateur tels que les numérotations rapides). Appuyez sur 1 pour confirmer ou sur * pour quitter. Si vous optez pour la réinitialisation, raccrochez le combiné pour quitter et lancer le processus de restauration. 732668 Redémarre le téléphone. Appuyez sur #, puis raccrochez le combiné pour réamorcer le téléphone. 111 Définit une adresse IP statique. Entrez l'adresse (utilisez « * » pour entrer la valeur « . »), puis appuyez sur #. Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. REMARQUE Le protocole DHCP doit être désactivé pour l'utilisation de cette option. Si ce n'est pas le cas, un message d'erreur s'affiche. Numéro OptionUtilisation des fonctionnalités avancées du téléphone Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 77 4 121 Définit un masque de réseau. Entrez l'adresse (utilisez « * » pour entrer la valeur « . »), puis appuyez sur #. Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. REMARQUE Le protocole DHCP doit être désactivé pour l'utilisation de cette option. Si ce n'est pas le cas, un message d'erreur s'affiche. 131 Définit une passerelle. Entrez l'adresse (utilisez « * » pour entrer la valeur « . »), puis appuyez sur #. Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. REMARQUE Le protocole DHCP doit être désactivé pour l'utilisation de cette option. Si ce n'est pas le cas, un message d'erreur s'affiche. 161 Définit l'adresse du serveur DNS principal. Entrez l'adresse (utilisez « * » pour entrer la valeur « . »), puis appuyez sur #. Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. 181 Définit l'adresse de multidiffusion IP (utilisée pour la communication du système Cisco SPA 9000 avec le téléphone IP). Entrez l'adresse (utilisez « * » pour entrer la valeur « . »), puis appuyez sur #. Pour enregistrer, appuyez sur1. Pour vérifier la valeur saisie, appuyez sur 2. Pour entrer une nouvelle valeur, appuyez sur 3. Pour quitter, appuyez sur *. 7932 Active ou désactive le serveur Web. Appuyez sur 1 pour activer l'accès ou sur 0 pour le désactiver, puis appuyez sur #. Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. 723646 Active ou désactive l'accès administrateur sur l'interface Web. Appuyez sur 1 pour activer l'accès ou sur 0 pour le désactiver, puis appuyez sur #. Appuyez sur 1 pour enregistrer, sur 2 pour vérifier la valeur, sur 3 pour entrer une nouvelle valeur et sur * pour quitter. Numéro OptionUtilisation des fonctionnalités avancées du téléphone Procédures avancées destinées au personnel de l’assistance technique Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 78 4 Procédures avancées destinées au personnel de l’assistance technique ! AVERTISSEMENT Ces menus permettent de configurer le téléphone et le réseau téléphonique, et de résoudre les problèmes associés. Modifiez ces réglages et exécutez ces procédures uniquement si l'administrateur du système téléphonique vous y invite. Pour accéder aux menus avancés des modèles Cisco SPA 502G, SPA 504G, SPA 508G et SPA 509G, procédez comme suit. Pour le modèle Cisco SPA 501G, une grande partie de ces options est accessible à partir du système de réponse vocale interactif. Reportez-vous à la section « Utilisation du menu Interactive Voice Response sur le modèle Cisco SPA 501G » à la page 75. ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Vous avez le choix entre les options suivantes : • Réseau : ce paramètre permet de configurer et de dépanner le réseau. Vous ne devez modifier ces paramètres que si votre administrateur vous y invite car ces opérations peuvent modifier sérieusement les fonctions de votre téléphone. • Infos produit : ce paramètre affiche le nom du produit, le numéro de série, la version du logiciel, la version matérielle, l’adresse MAC et le certificat client. • Etat : ce paramètre affiche l’état du téléphone, le poste et les boutons de ligne. • Redémarrage : reportez-vous à Redémarrage du téléphone, page 79. • Redémarrage : redémarre le téléphone. • Paramètres d'usine par défaut : rétablit les paramètres d’usine du téléphone. ! AVERTISSEMENT Si vous choisissez Paramètres d'usine par défaut, le téléphone retrouvera ses paramètres d’usine d’origine et tous les paramètres actuels seront effacés, y compris le répertoire et les fichiers journaux des appels. Il est également possible que le numéro de poste du téléphone soit modifié.Utilisation des fonctionnalités avancées du téléphone Procédures avancées destinées au personnel de l’assistance technique Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 79 4 • Réinit personnalisée : rétablit les derniers profils de personnalisation du téléphone. • Langue : modifie la langue du téléphone (en fonction de la disponibilité et de la configuration réalisée par l’administrateur système). Redémarrage du téléphone Ce paramètre permet de configurer et de dépanner le réseau. Vous ne devez le modifier que si l'administrateur du système téléphonique vous y invite, car ces opérations peuvent affecter le fonctionnement de votre téléphone. Pour redémarrer le téléphone : Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509 : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Accédez à Redémarrage et appuyez sur sélect. ÉTAPE 3 Appuyez sur OK. Cisco SPA 501G : ÉTAPE 1 Appuyez sur le bouton Configuration. ÉTAPE 2 Dans le menu du système de réponse vocale interactif, entrez 732668 et appuyez sur #. ÉTAPE 3 Raccrochez le combiné pour lancer le redémarrage.5 Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 80 Utilisation de l'interface Web L'interface Web du téléphone IP Cisco IP vous permet de configurer certaines fonctionnalités de votre téléphone à l'aide d'un navigateur Web. Ce chapitre contient les sections suivantes : • Connexion à l'interface Web, page 81 • Configuration de la fonction Ne pas déranger, page 82 • Configuration du renvoi d'appel, page 82 • Configuration de la fonction d'appel en attente, page 83 • Blocage de l'ID de l'appelant, page 84 • Blocage des appels anonymes, page 84 • Utilisation du répertoire personnel, page 85 • Consultation des listes de l'historique des appels, page 85 • Création de numérotations rapides, page 86 • Acceptation de messages texte, page 86 • Réglage du volume audio, page 87 • Modification du contraste de l'écran LCD, page 88 • Configuration de l'économiseur d'écran du téléphone, page 88Utilisation de l'interface Web Connexion à l'interface Web Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 81 5 Connexion à l'interface Web ÉTAPE 1 Obtenez l'adresse IP du téléphone : Cisco SPA 502G, SPA 504G, SPA 508G, SPA 509G : a. Appuyez sur le bouton Configuration. b. Accédez à Réseau, puis appuyez sur sélect. c. Accédez à IP actuelle. Il s'agit de l'adresse IP de votre téléphone. Cisco SPA 501G : a. Appuyez sur le bouton Configuration. b. Entrez 110 et appuyez sur #. L'adresse IP s'affiche. ÉTAPE 2 Ouvrez Internet Explorer sur votre ordinateur. ÉTAPE 3 Entrez l'adresse IP dans la barre d'outils du navigateur. L'interface Web comporte quatre onglets principaux : • Voice : contient des informations sur le téléphone et notamment les sousonglets suivants : - Info : contient des informations sur le système et le téléphone (lecture seule). - System : permet de configurer un mot de passe et des paramètres réseau. - Phone : permet d'activer l'économiseur d'écran. - User : contient les paramètres relatifs au renvoi d'appel, aux numérotations rapides, aux appels en attente, à la fonction de confidentialité et à l'audio. • Call History : affiche la liste des appels reçus et émis sur le téléphone. • Personal Directory : contient le carnet d'adresses personnel. • Attendant Console Status : fournit des informations sur les consoles Cisco SPA 500S, le cas échéant.Utilisation de l'interface Web Configuration de la fonction Ne pas déranger Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 82 5 Configuration de la fonction Ne pas déranger La fonctionnalité Ne pas déranger vous permet de couper la sonnerie du téléphone en cas d'appel entrant. Si la messagerie vocale est configurée, tous les appels entrants sont immédiatement dirigés vers la messagerie. Sinon, l'appelant entend un signal ou un message indiquant que la ligne est occupée. Pour activer la fonctionnalité Ne pas déranger : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Supplementary Services, localisez le champ Do Not Disturb. ÉTAPE 4 Sélectionnez Yes pour activer la fonctionnalité Do Not Disturb. ÉTAPE 5 Au bas de la page, cliquez sur Submit All Changes. REMARQUE Vous pouvez désactiver la fonctionnalité Do Not Disturb à partir du téléphone ou de l’interface Web. Configuration du renvoi d'appel ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User.Utilisation de l'interface Web Configuration de la fonction d'appel en attente Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 83 5 ÉTAPE 3 Dans Call Forward, vous pouvez configurer les champs suivants : • CFWD All Dest : renvoie tous les appels vers le numéro indiqué. • CFWD Busy Dest : renvoie tous les appels vers un autre numéro lorsque le téléphone est occupé. Entrez le numéro vers lequel les appels doivent être renvoyés. • CFWD No Ans Dest : renvoie les appels vers un autre numéro en l'absence de réponse. Entrez le numéro vers lequel les appels doivent être renvoyés. • CFWD No Ans Delay : délai d'attente en secondes avant le renvoi des appels en l'absence de réponse sur votre téléphone. Entrez le délai en secondes. ÉTAPE 4 Au bas de la page, cliquez sur Submit All Changes. Configuration de la fonction d'appel en attente La fonction d'appel en attente vous informe pendant un appel qu'un deuxième appel est en cours en faisant sonner votre téléphone et en affichant un message d'état. Si vous désactivez cette fonction, les appels entrants ne sonnent pas sur votre téléphone si vous êtes déjà en ligne et l'appelant entend un signal ou un message indiquant que la ligne est occupée. Pour activer ou désactiver la fonction d'appel en attente : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Supplementary Services, localisez le champ CW Setting. ÉTAPE 4 Sélectionnez yes ou no pour activer ou désactiver la fonction. ÉTAPE 5 Au bas de la page, cliquez sur Submit All Changes. Utilisation de l'interface Web Blocage de l'ID de l'appelant Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 84 5 Blocage de l'ID de l'appelant Vous pouvez bloquer l'ID de l'appelant sur votre téléphone afin que la personne que vous appelez ne puisse pas voir votre numéro de téléphone. Pour bloquer l'ID de l'appelant : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Supplementary Services, localisez le champ Block CID Setting. ÉTAPE 4 Sélectionnez yes ou no pour activer ou désactiver la fonction. ÉTAPE 5 Au bas de la page, cliquez sur Submit All Changes. Blocage des appels anonymes Le blocage des appels anonymes refuse les appels dont l'ID de l'appelant est inconnu. Par exemple, si un appelant a configuré son téléphone pour que son ID n'apparaisse pas, l'appel est considéré comme anonyme. L'appelant entend un signal ou un message indiquant que la ligne est occupée. Pour bloquer les appels anonymes : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Supplementary Services, localisez le champ Block ANC Setting. ÉTAPE 4 Sélectionnez yes ou no pour activer ou désactiver la fonction. ÉTAPE 5 Au bas de la page, cliquez sur Submit All Changes. Utilisation de l'interface Web Utilisation du répertoire personnel Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 85 5 Utilisation du répertoire personnel Le téléphone IP contient un répertoire dans lequel vous pouvez enregistrer et consulter les numéros que vous composez fréquemment. Vous pouvez composer les numéros directement depuis le répertoire, qui s'affiche sur l'écran du téléphone. REMARQUE Ceci ne s'applique pas au modèle Cisco SPA 501G. Pour consulter et modifier le répertoire personnel : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Cliquez sur l'onglet Personal Directory. Une fenêtre affiche les listes du répertoire personnel du téléphone. Pour créer une entrée dans le répertoire : ÉTAPE 1 Sélectionnez la ligne et entrez les informations au format suivant : n=Marketing;p=5045551212 où n indique le nom de l'entrée et p le numéro de téléphone (avec l'indicatif). ÉTAPE 2 Au bas de la page, cliquez sur Submit All Changes. Consultation des listes de l'historique des appels Pour afficher les listes de l'historique des appels : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Cliquez sur l'onglet Call History. Une fenêtre affiche les listes de l'historique des appels du téléphone. Ces fonctions comprennent : • Placed : affiche les 60 derniers numéros composés depuis le téléphone. • Answered : affiche l'identité des appelants des 60 derniers appels auxquels vous avez répondu.Utilisation de l'interface Web Création de numérotations rapides Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 86 5 • Missed : affiche les 60 derniers appels manqués. Cliquez sur l'onglet de chaque liste pour afficher la liste. Création de numérotations rapides Vous pouvez configurer jusqu'à 8 numérotations rapides pour les touches numérotées. Il peut s'agir d'un numéro de téléphone, d'une adresse IP ou d'une URL. Pour créer ou modifier une numérotation rapide numérique : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Speed Dial, entrez les numéros de numérotation rapide à créer ou à modifier. ÉTAPE 4 Cliquez sur Submit All Changes. Acceptation de messages texte Votre téléphone peut accepter des messages texte provenant d'autres téléphones IP ou services. Pour accepter des messages texte d'autres téléphones IP : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Supplementary Services, définissez le champ Text Message sur yes. ÉTAPE 4 Cliquez sur Submit All Changes. Utilisation de l'interface Web Réglage du volume audio Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 87 5 Pour accepter des messages texte d'un tiers : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Supplementary Services, définissez le champ Text Message from 3d Party sur yes. ÉTAPE 4 Cliquez sur Submit All Changes. Réglage du volume audio ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. Dans Audio Volume, vous pouvez régler les paramètres suivants : • Volume de la sonnerie • Volume du haut-parleur • Volume du combiné • Volume du casque Entrez une valeur comprise entre1 et 10, 1 correspondant au volume le plus bas. ÉTAPE 3 Cliquez sur Submit All Changes.Utilisation de l'interface Web Modification du contraste de l'écran LCD Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 88 5 Modification du contraste de l'écran LCD REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet User. ÉTAPE 3 Dans Audio Volume, vous pouvez régler le volume audio en saisissant une valeur comprise entre1 et 10, 1 correspondant au volume le plus bas. ÉTAPE 4 Cliquez sur Submit All Changes. Configuration de l'économiseur d'écran du téléphone REMARQUE Ne s'applique pas au modèle Cisco SPA 501G. Pour configurer l'économiseur d'écran du téléphone : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Dans l'onglet Voice, cliquez sur le sous-onglet Phone. Dans General, vous pouvez configurer les options suivantes : • Screen Saver Enable : permet d'activer et de désactiver l'économiseur d'écran. • Screen Saver Wait : permet de définir le délai d'attente en secondes avant le démarrage de l'économiseur d'écran lorsque le téléphone est inactif. • Icône Screen Saver : définit le type d'affichage : - Une image de fond. - L'heure de la station au centre de l'écran.Utilisation de l'interface Web Configuration de l'économiseur d'écran du téléphone Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 89 5 - Une icône représentant un verrou qui se déplace sur l'écran. Lorsque le téléphone est verrouillé, le message « Press any key to unlock your phone » défile dans la ligne d'état. - Une icône représentant un téléphone qui se déplace sur l'écran. - La date et l'heure de la station au centre de l'écran. ÉTAPE 3 Cliquez sur Submit All Changes.6 Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 90 Utilisation de la console de réception Cisco SPA 500S Ce chapitre explique comment installer et utiliser la console de réception Cisco SPA 500S avec le téléphone IP. Figure 1 Console de réception Cisco SPA 500SUtilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 91 6 La console de réception Cisco SPA 500S pour les téléphones IP Cisco SPA 500 est dotée de 32 boutons et 32 DEL programmables 3 couleurs (rouge, vert, orange) et prend en charge le tableau de voyants d’occupation Broadsoft et le contrôle des lignes Asterisk. La console Cisco SPA 500S se fixe au téléphone IP avec le bras de fixation fourni. Elle est alimentée directement par le téléphone IP et ne nécessite pas d'alimentation séparée. Vous pouvez relier deux unités Cisco SPA 500S à un même téléphone IP, ce qui vous donne la possibilité de contrôler 64 lignes distinctes au total. Connexion de la console de réception Cisco SPA 500S au téléphone IP Pour connecter la console de réception Cisco SPA 500S au téléphone IP, munissez-vous des éléments suivants : • Console de réception Cisco SPA 500S • Bras de fixation • Deux (2) vis de fixation • Câble d'interconnexion auxiliaire • SupportUtilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 92 6 Connexion d'une seule console Cisco SPA 500S ÉTAPE 1 Retournez le téléphone IP et la console Cisco SPA 500S. ÉTAPE 2 Alignez le trou de vis dans le téléphone IP avec l'un des trous sur le bras de fixation. ÉTAPE 3 Insérez les tiges situées sur le bras de fixation dans les trous correspondants sur le téléphone IP.Utilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 93 6 ÉTAPE 4 Fixez le bras de fixation au téléphone IP à l'aide de la vis du bras de fixation. ÉTAPE 5 Alignez le trou de vis droit dans la console Cisco SPA 500S avec le trou inutilisé sur le bras de fixation. ÉTAPE 6 Insérez les tiges situées sur le bras de fixation dans les trous correspondants sur la console Cisco SPA 500S.Utilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 94 6 ÉTAPE 7 Fixez le bras de fixation à la console Cisco SPA 500S à l'aide de la vis du bras de fixation. ! AVERTISSEMENT Ne branchez pas de câble téléphonique sur le port AUX. Utilisez uniquement le câble auxiliaire fourni avec la console Cisco SPA 500S. ÉTAPE 8 Localisez le port AUX IN à l'arrière de la console Cisco SPA 500S. Connectez l'une des extrémités du câble auxiliaire à ce port. ÉTAPE 9 Localisez le port AUX à l'arrière du téléphone IP. Connectez l'autre extrémité du câble auxiliaire à ce port. La console Cisco SPA 500S est alimentée par le câble auxiliaire relié au téléphone IP ; aucune source d'alimentation supplémentaire n'est requise.Utilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 95 6 ÉTAPE 10 Faites passer le câble auxiliaire dans le canal de passage du câble de la console Cisco SPA 500S. ÉTAPE 11 Fixez le support de bureau approprié à chaque unité.Utilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 96 6 Connexion d'une deuxième console Cisco SPA 500S Vous pouvez connecter deux consoles de réception Cisco SPA 500S à un téléphone IP Cisco SPA 500. Les instructions de cette section vous permettent de connecter une deuxième console Cisco SPA 500S. Si vous n'avez pas l'intention de connecter une deuxième console Cisco SPA 500S, passez à « Configuration de la console Cisco SPA 500S » à la page 98. ÉTAPE 1 Fixez la première console Cisco SPA 500S au téléphone IP et connectez le câble auxiliaire comme décrit dans la section « Connexion de la console de réception Cisco SPA 500S au téléphone IP » à la page 91. ÉTAPE 2 Alignez le trou de vis gauche dans la première console Cisco SPA 500S avec l'un des trous du bras de fixation. ÉTAPE 3 Insérez les tiges situées sur le bras de fixation dans les trous correspondants sur la console Cisco SPA 500S. ÉTAPE 4 Fixez le bras de fixation à la première console Cisco SPA 500S à l'aide de la vis du bras de fixation. ÉTAPE 5 Insérez les tiges situées sur le bras de fixation dans les trous correspondants sur la console Cisco SPA 500S. Utilisation de la console de réception Cisco SPA 500S Connexion de la console de réception Cisco SPA 500S au téléphone IP Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 97 6 ÉTAPE 6 Fixez le bras de fixation à la deuxième console Cisco SPA 500S à l'aide de la vis du bras de fixation. ! AVERTISSEMENT Ne branchez pas de câble téléphonique sur le port AUX. Utilisez uniquement le câble auxiliaire fourni avec la console Cisco SPA 500S. ÉTAPE 7 Localisez le port AUX OUT à l'arrière de la première console Cisco SPA 500S. Connectez l'une des extrémités du câble auxiliaire à ce port. ÉTAPE 8 Localisez le port AUX IN à l'arrière de la deuxième console Cisco SPA 500S. Connectez l'autre extrémité du câble auxiliaire à ce port. ÉTAPE 9 Faites passer le câble auxiliaire dans le canal de passage du câble. La console Cisco SPA 500S est alimentée par le câble auxiliaire relié au téléphone IP ; aucune source d'alimentation supplémentaire n'est requise. ÉTAPE 10 Fixez les supports de bureau appropriés à chaque unité.Utilisation de la console de réception Cisco SPA 500S Configuration de la console Cisco SPA 500S Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 98 6 Configuration de la console Cisco SPA 500S Vous pouvez configurer la console Cisco SPA 500S pour vous permettre d'accéder facilement à d'autres lignes téléphoniques du système. Par exemple, vous pouvez configurer les boutons de la console Cisco SPA 500S pour contrôler un autre poste, composer rapidement un numéro, transférer des appels vers un autre poste, etc. REMARQUE Les options disponibles sur la console Cisco SPA 500S dépendent de la configuration du système téléphonique. Il est possible que votre système téléphonique ne propose pas toutes les fonctionnalités mentionnées dans ce document. La configuration de la console Cisco SPA 500S et l'attribution des boutons de ligne sont effectuées par l'administrateur système et ne sont pas décrites dans ce document. Pour configurer la console Cisco SPA 500S : • Si la console Cisco SPA 500S et le téléphone IP associé font partie d'un système vocal Cisco SPA 9000, nous vous recommandons d'utiliser l'assistant d'installation de ce système. Les instructions d’utilisation de l’assistant sont disponibles dans le document System Configuration Using the SPA 9000 Setup Wizard sur le site Cisco.com. Reportez-vous à l'Annexe A, « Pour en savoir plus » pour obtenir le lien vers ce document. • Pour configurer manuellement la console Cisco SPA 500S à l'aide de l'interface utilisateur Web du téléphone IP associé, consultez le document Cisco SPA 500 Series and Wireless IP Phone Administration Guide sur le site Cisco.com. Reportez-vous à l'Annexe A, « Pour en savoir plus » pour obtenir le lien vers ce document. • Si vous utilisez la console Cisco SPA 500S et le téléphone IP associé avec un serveur Broadsoft ou Asterisk, consultez le document Cisco SPA 500 Series and Wireless IP Phone Administration Guide sur le site Cisco.com. Reportez-vous à l'Annexe A, « Pour en savoir plus » pour obtenir le lien vers ce document.Utilisation de la console de réception Cisco SPA 500S Utilisation de la console Cisco SPA 500S Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 99 6 Utilisation de la console Cisco SPA 500S Les fonctions des boutons Cisco SPA 500S peuvent varier selon la configuration. Cependant, vous pouvez en général : • Contrôler un poste en examinant sa couleur. La couleur de la DEL d’un bouton de ligne donne des indications sur la ligne : - Vert : la ligne est inactive. - Rouge (fixe) : la ligne est en cours d'utilisation. - Rouge (clignotant) : la ligne sonne. - Orange (fixe) : la ligne n'est pas enregistrée ; la connexion du téléphone pose problème. - Orange (clignotant) : la ligne n'est pas configurée correctement. - Éteinte : la ligne n'est pas configurée. • Transférer un appel actif en appuyant sur le bouton de ligne sur la console Cisco SPA 500S. (Le bouton de ligne doit être configuré en tant que numérotation rapide pour le numéro vers lequel vous transférez l'appel.) • Composer un poste configuré en appuyant sur le bouton de ligne vert sur la console Cisco SPA 500S. • Prendre un appel qui sonne sur le poste en appuyant sur le bouton de ligne rouge clignotant. Contrôle de la console Cisco SPA 500S Pour afficher l'état de la console Cisco SPA 500S : ÉTAPE 1 Connectez-vous à l'interface Web. ÉTAPE 2 Cliquez sur l'onglet Att Console Status.A Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 100 Pour en savoir plus Cisco propose une vaste gamme de ressources pour vous aider à tirer pleinement parti du Téléphone IP Cisco Small Business. Ressources sur les produits Assistance technique Communauté d'assistance Cisco Small Business www.cisco.com/go/smallbizsupport Assistance technique et documentation en ligne (identifiant de connexion obligatoire) www.cisco.com/support Coordonnées de l'assistance téléphonique www.cisco.com/en/US/support/ tsd_cisco_small_business_support_center_conta cts.html Téléchargement de logiciels (identifiant de connexion obligatoire) Accédez à tools.cisco.com/support/downloads, puis entrez le numéro du modèle dans le champ Software Search. Documentation sur les produits Téléphone IP www.cisco.com/en/US/products/ps10499/ tsd_products_support_series_home.html Accessoires http://cisco.com/en/US/products/ps10042/ tsd_products_support_series_home.html Système vocal Cisco SPA 9000 www.cisco.com/en/US/products/ps10030/ tsd_products_support_series_home.html Cisco Unified Communicatio ns 500 pour les petites entreprises www.cisco.com/en/US/products/ps7293/ tsd_products_support_series_home.htmlPour en savoir plus Guide de l'utilisateur du téléphone IP Cisco Small Business Pro SPA 50X (SIP) 101 A Liste de documents Reportez-vous aux documents suivants (disponibles en cliquant sur les URL répertoriées ci-dessus) pour obtenir plus d'informations sur votre produit. • Guide de démarrage du téléphone IP modèle 50X Cisco Small Business Pro : installation et configuration initiale du téléphone IP Cisco. • Cisco WBP54G Wireless-G Bridge for Phone Adapters User Guide : installation et utilisation du pont sans fil WBP54G avec le téléphone IP Cisco. • Cisco Small Business Pro SPA 500 Series and WIP310 IP Phone Administration Guide : administration et configuration avancée du téléphone IP Cisco. • Cisco SPA 9000 Voice System Administration Guide : administration et configuration du système vocal Cisco SPA 9000. • Cisco SPA 9000 Voice System Using Setup Wizard Installation and Configuration Guide : installation du système vocal Cisco SPA 9000 à l'aide de l'assistant d'installation. • Cisco SPA 9000 Voice System Web-UI Based Product Installation and Configuration Guide : installation du système vocal Cisco SPA 9000 à l'aide de l'interface utilisateur Web. Cisco Small Business Site Cisco Partner Central pour les PME (identifiant partenaire obligatoire) www.cisco.com/web/partners/sell/smb Accueil Cisco Small Business www.cisco.com/smb Marketplace www.cisco.com/go/marketplace Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual Product and Documentation Release 7.0 Last Updated: August 2012 Text Part Number: 78-17234-01THE 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. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense. The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation. Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense. You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures: • Turn the television or radio antenna until the interference stops. • Move the equipment to one side or the other of the television or radio. • Move the equipment farther away from the television or radio. • Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.) Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco ONS 15310-CL and Cisco ONS 15310-MA Release Manual, Release 7.0 Copyright © 2004–2012 Cisco Systems, Inc. All rights reserved.iii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 CONTENTS About this Manual xxi Revision History xxi Document Objectives xxii Audience xxii Document Organization xxiii Related Documentation xxiv Document Conventions xxiv Obtaining Optical Networking Information xxxi Where to Find Safety and Warning Information xxxi Cisco Optical Networking Product Documentation CD-ROM xxxi Obtaining Documentation and Submitting a Service Request xxxi CHAPTER 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1-1 1.1 Installation Overview 1-1 1.2 Rack Installation 1-2 1.2.1 Mounting Bracket 1-3 1.2.2 Mounting a Single Node 1-5 1.2.3 Mounting Multiple Nodes 1-5 1.3 Power and Ground Description 1-5 1.4 Cable Description and Installation 1-5 1.4.1 Cabling Types 1-6 1.4.2 Fiber Cable Installation 1-6 1.4.3 Coaxial Cable Installation 1-6 1.4.4 DS-1 Cable Installation 1-7 1.4.5 Alarm Cable Installation 1-7 1.4.6 BITS Cable Installation 1-8 1.4.7 UDC Cable Installation 1-8 1.5 Fans 1-9 1.6 Cards and Slots 1-9 CHAPTER 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2-1 2.1 Installation Overview 2-1 2.2 Rack Installation 2-2Contents iv Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 2.2.1 Mounting Brackets 2-3 2.2.2 Mounting a Single Node 2-4 2.2.3 Mounting Multiple Nodes 2-5 2.3 Electrical Interface Assemblies 2-5 2.4 Front Door 2-6 2.5 Power and Ground Description 2-7 2.6 Cable Description and Installation 2-10 2.6.1 Cabling Types 2-10 2.6.2 Fiber Cable Installation 2-12 2.6.3 Coaxial Cable Installation 2-13 2.6.4 DS-1 Cable Installation 2-13 2.6.5 Alarm Cable Installation 2-17 2.6.6 BITS Cable Installation 2-18 2.6.7 UDC Cable Installation 2-19 2.7 Cable Routing and Management 2-19 2.7.1 Standard Cable Management Bracket 2-19 2.7.2 Extended Cable Management Bracket 2-20 2.8 Fan-Tray Assembly 2-21 2.8.1 Fan Speed and Power Requirements 2-22 2.8.2 Fan Failure 2-22 2.8.3 Air Filter 2-22 2.9 Cards and Slots 2-22 CHAPTER 3 Card Reference 3-1 3.1 Card Summary and Compatibility 3-1 3.1.1 Card Summary 3-3 3.1.2 Card Compatibility 3-4 3.2 15310-CL-CTX Card 3-5 3.2.1 Features 3-6 3.2.2 Synchronization and Timing 3-7 3.2.3 System Cross-Connect 3-7 3.2.4 15310-CL-CTX Optical Interfaces 3-7 3.2.5 Communication and Control 3-7 3.2.6 Electrical Interface (BBE and WBE) 3-8 3.2.7 15310-CL-CTX Card-Level Indicators 3-8 3.3 CTX2500 Card 3-8 3.3.1 System Cross-Connect 3-9 3.3.2 CTX2500 Card Side Switches 3-9Contents v Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 3.3.3 CTX2500 Optical Interfaces 3-10 3.3.4 CTX2500 Card-Level Indicators 3-10 3.3.5 CTX2500 Port-Level Indicators 3-10 3.4 CE-100T-8 Card 3-10 3.4.1 CE-100T-8 Card-Level Indicators 3-13 3.4.2 CE-100T-8 Port-Level Indicators 3-13 3.5 ML-100T-8 Card 3-14 3.5.1 ML-100T-8 Card Description 3-14 3.5.2 ML-Series Cisco IOS CLI Console Port 3-15 3.5.3 ML-100T-8 Card-Level Indicators 3-17 3.5.4 ML-100T-8 Port-Level Indicators 3-17 3.6 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards 3-18 3.6.1 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Card-Level Indicators 3-19 3.7 Filler Cards 3-19 3.8 SFP Modules 3-20 3.8.1 Compatibility by Card 3-21 3.8.2 SFP Description 3-22 3.8.3 PPM Provisioning 3-23 CHAPTER 4 Card Protection 4-1 4.1 Overview 4-1 4.2 ONS 15310-CL Port Protection 4-2 4.2.1 1+1 Optical Port Protection 4-2 4.2.2 Unprotected Ports 4-2 4.3 ONS 15310-MA Card and Port Protection 4-2 4.3.1 .1:1 Electrical Card Protection 4-2 4.3.2 .1+1 Optical Port Protection 4-4 4.3.3 .CTX2500 Card Equipment Protection 4-5 4.4 Automatic Protection Switching 4-5 4.5 External Switching Commands 4-6 CHAPTER 5 Cisco Transport Controller Operation 5-1 5.1 CTC Software Delivery Methods 5-1 5.1.1 CTC Software Installed on the 15310-CL-CTX or CTX2500 Card 5-1 5.1.2 CTC Software Installed on the PC or UNIX Workstation 5-2 5.2 CTC Installation Overview 5-3 5.3 PC and UNIX Workstation Requirements 5-3 5.4 ONS 15310-CL and ONS 15310-MA Connection 5-5Contents vi Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 5.5 CTC Window 5-6 5.5.1 Node View 5-6 5.5.1.1 CTC Card Colors 5-6 5.5.1.2 Node View Card Shortcuts 5-8 5.5.1.3 Node View Tabs 5-8 5.5.2 Network View 5-9 5.5.2.1 CTC Node Colors 5-9 5.5.2.2 Network View Tabs 5-10 5.5.2.3 DCC Links 5-10 5.5.2.4 Link Consolidation 5-10 5.5.3 Card View 5-11 5.5.4 Print and Export CTC Data 5-13 5.6 Common Control Card Reset 5-14 5.7 Traffic Card Reset 5-14 5.8 Database Backup 5-14 5.9 Software Revert 5-15 CHAPTER 6 Security 6-1 6.1 Users IDs and Security Levels 6-1 6.2 User Privileges and Policies 6-2 6.2.1 User Privileges by CTC Action 6-2 6.2.2 Security Policies 6-5 6.2.2.1 Superuser Privileges for Provisioning Users 6-5 6.2.2.2 Idle User Timeout 6-6 6.2.2.3 User Password, Login, and Access Policies 6-6 6.3 Audit Trail 6-6 6.3.1 Audit Trail Log Entries 6-7 6.3.2 Audit Trail Capacities 6-7 6.4 RADIUS Security 6-7 6.4.1 RADIUS Authentication 6-8 6.4.2 Shared Secrets 6-8 CHAPTER 7 Timing 7-1 7.1 Timing Parameters 7-1 7.2 Network Timing 7-2 7.3 Synchronization Status Messaging 7-3Contents vii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 CHAPTER 8 Circuits and Tunnels 8-1 8.1 Overview 8-1 8.2 Circuit Properties 8-2 8.2.1 Circuit Status 8-3 8.2.2 Circuit States 8-4 8.2.3 Circuit Protection Types 8-5 8.2.4 Circuit Information in the Edit Circuits Window 8-5 8.3 VT1.5 Bandwidth 8-7 8.4 VT Tunnels and Aggregation Points 8-8 8.5 DCC Tunnels 8-8 8.5.1 Traditional DCC Tunnels 8-8 8.5.2 IP-Encapsulated Tunnels 8-9 8.6 Virtual Concatenated Circuits 8-9 8.6.1 VCAT Circuit States 8-10 8.6.2 VCAT Member Routing 8-10 8.6.3 Link Capacity Adjustment 8-11 8.6.4 VCAT Circuit Size 8-12 8.7 Section and Path Trace 8-13 8.8 Bridge and Roll 8-13 8.8.1 Rolls Window 8-13 8.8.2 Roll Status 8-15 8.8.3 Single and Dual Rolls 8-15 8.8.4 Two-Circuit Bridge and Roll 8-18 8.8.5 Protected Circuits 8-18 8.9 Merged Circuits 8-18 8.10 Reconfigured Circuits 8-19 8.11 Server Trails 8-20 CHAPTER 9 SONET Topologies and Upgrades 9-1 9.1 Path Protection Dual-Ring Interconnect for the ONS 15310-MA 9-1 9.2 Terminal Point-to-Point and Linear ADM Configurations 9-2 9.3 Interoperability 9-3 9.3.1 Subtending Rings 9-3 9.3.2 Linear Connections 9-5 9.4 Path-Protected Mesh Networks 9-6 9.5 Four Node Configurations 9-8 9.6 OC-N Speed Upgrades 9-8Contents viii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 9.6.1 Span Upgrade Wizard 9-9 9.6.2 Manual Span Upgrades 9-9 CHAPTER 10 Management Network Connectivity 10-1 10.1 IP Networking Overview 10-2 10.2 IP Addressing Scenarios 10-2 10.2.1 Scenario 1: CTC and ONS 15310-CL or ONS 15310-MA Nodes on the Same Subnet 10-3 10.2.2 Scenario 2: CTC and ONS 15310-CL or ONS 15310-MA Nodes Connected to a Router 10-3 10.2.3 Scenario 3: Using Proxy ARP to Enable an ONS 15310-CL or ONS 15310-MA Gateway 10-4 10.2.4 Scenario 4: Default Gateway on CTC Computer 10-6 10.2.5 Scenario 5: Using Static Routes to Connect to LANs 10-7 10.2.6 Scenario 6: Using OSPF 10-9 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server 10-11 10.3 Provisionable Patchcords 10-16 10.4 Routing Table 10-17 10.5 External Firewalls 10-18 10.6 Open GNE 10-20 10.7 TCP/IP and OSI Networking 10-22 10.7.1 Point-to-Point Protocol 10-23 10.7.2 Link Access Protocol on the D Channel 10-24 10.7.3 OSI Connectionless Network Service 10-24 10.7.4 OSI Routing 10-27 10.7.4.1 End System-to-Intermediate System Protocol 10-28 10.7.4.2 Intermediate System-to-Intermediate System Protocol 10-28 10.7.5 TARP 10-29 10.7.5.1 TARP Processing 10-30 10.7.5.2 TARP Loop Detection Buffer 10-31 10.7.5.3 Manual TARP Adjacencies 10-32 10.7.5.4 Manual TID to NSAP Provisioning 10-32 10.7.6 OSI Virtual Routers 10-32 10.7.7 IP-over-CLNS Tunnels 10-33 10.7.7.1 Provisioning IP-over-CLNS Tunnels 10-34 10.7.7.2 IP Over CLNS Tunnel Scenario 1: ONS Node to Other Vendor GNE 10-34 10.7.7.3 IP-Over-CLNS Tunnel Scenario 2: ONS Node to Router 10-35 10.7.7.4 IP-Over-CLNS Tunnel Scenario 3: ONS Node to Router Across an OSI DCN 10-37 10.7.8 Provisioning OSI in CTC 10-39 CHAPTER 11 Alarm Monitoring and Management 11-1 11.1 Overview 11-1Contents ix Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 11.2 Viewing Alarms 11-1 11.2.1 Viewing Alarms With Each Node’s Time Zone 11-4 11.2.2 Controlling Alarm Display 11-4 11.2.3 Filtering Alarms 11-4 11.2.4 Viewing Alarm-Affected Circuits 11-5 11.2.5 Conditions Tab 11-5 11.2.6 Controlling the Conditions Display 11-6 11.2.6.1 Retrieving and Displaying Conditions 11-6 11.2.6.2 Conditions Column Descriptions 11-6 11.2.6.3 Filtering Conditions 11-7 11.2.7 Viewing History 11-7 11.2.7.1 History Column Descriptions 11-8 11.2.7.2 Retrieving and Displaying Alarm and Condition History 11-8 11.2.8 Alarm History and Log Buffer Capacities 11-9 11.3 Alarm Severities 11-9 11.4 Alarm Profiles 11-10 11.4.1 Creating and Modifying Alarm Profiles 11-10 11.4.2 Alarm Profile Buttons 11-11 11.4.3 Alarm Profile Editing 11-11 11.4.4 Alarm Severity Options 11-11 11.4.5 Row Display Options 11-12 11.4.6 Applying Alarm Profiles 11-12 11.5 Alarm Suppression 11-13 11.5.1 Alarms Suppressed for Maintenance 11-13 11.5.2 Alarms Suppressed by User Command 11-14 11.6 External Alarms and Controls 11-14 11.6.1 External Alarm Input 11-14 11.6.2 External Control Output 11-15 CHAPTER 12 Performance Monitoring 12-1 12.1 Threshold Performance Monitoring 12-2 12.2 Intermediate-Path Performance Monitoring 12-3 12.3 Pointer Justification Count Performance Monitoring 12-3 12.4 Performance Monitoring Parameter Definitions 12-4 12.5 Performance Monitoring for Electrical Ports 12-10 12.5.1 DS-1 Port Performance Monitoring Parameters 12-10 12.5.2 DS-3 Port Performance Monitoring Parameters 12-12 12.5.3 EC-1 Port Performance Monitoring Parameters 12-13Contents x Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 12.6 Performance Monitoring for Ethernet Cards 12-15 12.6.1 CE-100T-8 and ML-100T-8 Card Ethernet Performance Monitoring Parameters 12-15 12.6.1.1 CE-100T-8 and ML-100T-8 Card Ether Ports Statistics Window 12-15 12.6.1.2 CE-100T-8 and ML-100T-8 Card Ether Ports Utilization Window 12-17 12.6.1.3 CE-100T-8 and ML-100T-8 Card Ether Ports History Window 12-18 12.6.1.4 CE-100T-8 and ML-100T-8 Card POS Ports Statistics Parameters 12-18 12.6.1.5 CE-100T-8 and ML-100T-8 Card POS Ports Utilization Window 12-20 12.6.1.6 CE-100T-8 and ML-100T-8 Card POS Ports History Window 12-20 12.7 Performance Monitoring for Optical Ports 12-20 12.7.1 OC-3 Port Performance Monitoring Parameters 12-20 12.7.2 OC-12 Port Performance Monitoring Parameters 12-22 12.7.3 OC-48 Port Performance Monitoring Parameters for ONS 15310-MA 12-24 CHAPTER 13 SNMP 13-1 13.1 SNMP Overview 13-1 13.2 SNMP Basic Components 13-2 13.3 SNMP Proxy Support Over Firewalls 13-3 13.4 SNMP Version Support 13-4 13.5 SNMP Management Information Bases 13-4 13.6 SNMP Traps 13-6 13.7 SNMP Community Names 13-8 13.8 SNMP Remote Network Monitoring 13-8 13.8.1 Ethernet Statistics Group 13-8 13.8.2 History Control Group 13-8 13.8.3 Ethernet History Group 13-8 13.8.4 Alarm Group 13-9 13.8.5 Event Group 13-9 13.9 CE-100T-8 and ML-100T-8 RMON MIBs 13-9 APPENDIX A Specifications A-1 A.1 Cisco ONS 15310-CL Shelf Specifications A-1 A.1.1 Bandwidth A-1 A.1.2 Expansion Slot A-1 A.1.3 Internal Cards A-1 A.1.4 15310-CL-CTX A-2 A.1.5 Configurations A-3 A.1.6 Cisco Transport Controller A-3 A.1.7 TL1 Craft Interface A-3Contents xi Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 A.1.8 LEDs A-3 A.1.9 Alarm Interface A-4 A.1.10 DS1 Interface A-4 A.1.11 DS3/EC1 Interface A-4 A.1.12 Nonvolatile Memory A-4 A.1.13 BITS Interface A-5 A.1.14 Push Buttons A-5 A.1.15 System Timing A-5 A.1.16 Power Specifications A-5 A.1.17 Environmental Specifications A-6 A.1.18 Shelf Dimensions A-6 A.2 Cisco ONS 15310-MA Shelf Specifications A-6 A.2.1 Alarm Interface A-6 A.2.2 UDC Interface A-6 A.2.3 Cisco Transport Controller LAN Interface A-7 A.2.4 TL1 Craft Interface A-7 A.2.5 Configurations A-7 A.2.6 LEDs A-7 A.2.7 Push Buttons A-8 A.2.8 BITS Interface A-8 A.2.9 System Timing A-8 A.2.10 Power Specifications A-8 A.2.11 Environmental Specifications A-9 A.2.12 Fan-Tray Assembly Specifications A-9 A.2.13 Shelf Dimensions A-9 A.3 Card Specifications A-10 A.3.1 CTX2500 Card A-10 A.3.2 Nonvolatile Memory A-11 A.3.3 CE-100T-8 and ML-100T-8 Cards A-11 A.3.4 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards A-12 A.3.5 Filler Cards A-14 A.4 SFP Specifications A-15 APPENDIX B Administrative and Service States B-1 B.1 Service States B-1 B.2 Administrative States B-2 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-5Contents xii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 APPENDIX C Network Element Defaults C-1 C.1 Network Element Defaults Description C-1 C.2 ONS 15310-CL 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 15310-CL-CTX Card Default Settings C-4 C.2.3.2 Ethernet Card Default Settings C-20 C.3 Cisco ONS 15310-CL Node Default Settings C-20 C.3.1 Time Zones C-26 C.4 CTC Default Settings C-29 C.5 ONS 15310-MA Card Default Settings C-30 C.5.1 Configuration Defaults C-30 C.5.2 Threshold Defaults C-31 C.5.3 Defaults by Card C-31 CTX2500 Card Default Settings C-32 DS1-28/DS3-EC1-3 Card Default Settings C-48 DS1-84/DS3-EC1-3 Card Default Settings C-56 C.5.3.1 Ethernet Card Default Settings C-64 C.6 Cisco ONS 15310-MA Node Default Settings C-64 I NDEXFIGURES xiii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Figure 1-1 ONS 15310-CL Shelf Assembly Dimensions 1-3 Figure 1-2 Mounting Brackets (19-Inch Orientation) 1-4 Figure 1-3 Mounting Brackets (23-Inch Orientation) 1-4 Figure 1-4 Pins 1 and 8 on the RJ-45 Connector 1-7 Figure 1-5 Installing an Ethernet Card 1-10 Figure 2-1 ONS 15310-MA Shelf Assembly Dimensions 2-3 Figure 2-2 Mounting a Single ONS 15310-MA in a Rack 2-4 Figure 2-3 High-Density EIA Connectors 2-6 Figure 2-4 ONS 15310-MA Door Ground Strap 2-7 Figure 2-5 Ground Holes on the Bottom of the ONS 15310-MA Shelf Assembly 2-8 Figure 2-6 Ground Holes on the Left and Right Sides of the ONS 15310-MA Shelf Assembly 2-9 Figure 2-7 ACS Cable T015654 2-11 Figure 2-8 Shelf Assembly with Fiber Guide Installed 2-12 Figure 2-9 BNC Insertion and Removal Tool 2-13 Figure 2-10 Installing the Standard Cable Management Bracket 2-20 Figure 2-11 Installing the Extended Cable Management Bracket 2-21 Figure 2-12 Installing a Card in an ONS 15310-MA 2-23 Figure 3-1 ONS 15310-CL with Expansion Card Being Inserted 3-2 Figure 3-2 ONS 15310-MA with Cards Installed 3-3 Figure 3-3 ONS 15310-CL Front Panel 3-5 Figure 3-4 15310-CL-CTX Block Diagram 3-6 Figure 3-5 CTX2500 Faceplate and Block Diagram 3-9 Figure 3-6 CE-100T-8 Faceplate and Block Diagram 3-12 Figure 3-7 Console Cable Adapter 3-15 Figure 3-8 ML-100T-8 Card Faceplate and Block Diagram 3-16 Figure 3-9 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Card Faceplates and Block Diagram 3-18 Figure 3-10 Filler Card 3-19 Figure 3-11 CTX2500 Filler Card 3-20 Figure 3-12 Mylar Tab SFP 3-23 Figure 3-13 Actuator/Button SFP 3-23 Figure 3-14 Bail Clasp SFP 3-23Figures xiv Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Figure 4-1 ONS 15310-MA Chassis Card Layout 4-3 Figure 5-1 CTC Software Versions in an ONS 15310-CL (Node View) 5-2 Figure 5-2 Terminal Loopback Indicator 5-8 Figure 5-3 Facility Loopback Indicator 5-8 Figure 5-4 CTC Card View in an ONS 15310-CL Showing an ML-100T-8 Card 5-12 Figure 7-1 ONS 15310-CL and ONS 15310-MA Timing Example 7-2 Figure 8-1 Terminal Loopback in the Edit Circuits Window 8-7 Figure 8-2 VCAT Common Fiber Routing 8-10 Figure 8-3 VCAT Split Fiber Routing 8-11 Figure 8-4 Rolls Window 8-14 Figure 8-5 Single Source Roll 8-16 Figure 8-6 Single Destination Roll 8-16 Figure 8-7 Single Roll from One Circuit to Another Circuit (Destination Changes) 8-16 Figure 8-8 Single Roll from One Circuit to Another Circuit (Source Changes) 8-17 Figure 8-9 Dual Roll to Reroute a Link 8-17 Figure 8-10 Dual Roll to Reroute to a Different Node 8-18 Figure 9-1 ONS 15310-CL Linear ADM Configuration 9-2 Figure 9-2 ONS 15310-MA Linear ADM Configuration 9-3 Figure 9-3 ONS 15454 with Two ONS 15310-CL Nodes Subtending Path Protections 9-3 Figure 9-4 ONS 15310-MA with Two Subtending Path Protection Configurations 9-4 Figure 9-5 ONS 15310-CL Ring Subtended from an ONS 15454 Ring 9-4 Figure 9-6 ONS 15310-MA Ring Subtended from an ONS 15454 Ring 9-5 Figure 9-7 Linear or Path Protection Connection Between ONS 15454 and ONS 15310 or ONS 15310-MA Nodes 9-5 Figure 9-8 Path-Protected Mesh Network for ONS 15310-CL Nodes 9-6 Figure 9-9 Path-Protected Mesh Network for ONS 15310-MA Nodes 9-7 Figure 9-10 Virtual Ring for ONS 15310-MAs 9-8 Figure 10-1 Scenario 1: CTC and ONS 15310-CL or ONS 15310-MA Nodes on the Same Subnet 10-3 Figure 10-2 Scenario 2: CTC and ONS 15310-CL or ONS 15310-MA Nodes Connected to Router 10-4 Figure 10-3 Scenario 3: Using Proxy ARP 10-5 Figure 10-4 Scenario 3: Using Proxy ARP with Static Routing 10-6 Figure 10-5 Scenario 4: Default Gateway on a CTC Computer 10-7 Figure 10-6 Scenario 5: Static Route with One CTC Computer Used as a Destination 10-8 Figure 10-7 Scenario 5: Static Route with Multiple LAN Destinations 10-9 Figure 10-8 Scenario 6: OSPF Enabled 10-10 Figure 10-9 Scenario 6: OSPF Not Enabled 10-11Figures xv Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Figure 10-10 ONS 15310-CL or ONS 15310-MA Proxy Server with GNE and ENEs on the Same Subnet 10-13 Figure 10-11 Scenario 7: Proxy Server with GNE and ENEs on Different Subnets 10-14 Figure 10-12 Scenario 7: Proxy Server with ENEs on Multiple Rings 10-15 Figure 10-13 Proxy and Firewall Tunnels for Foreign Terminations 10-21 Figure 10-14 Foreign Node Connection to an ENE Ethernet Port 10-22 Figure 10-15 ISO-DCC NSAP Address 10-26 Figure 10-16 Level 1 and Level 2 OSI Routing 10-28 Figure 10-17 Manual TARP Adjacencies 10-32 Figure 10-18 IP-over-CLNS Tunnel Flow 10-33 Figure 10-19 IP Over CLNS Tunnel Scenario 1: ONS NE to Other Vender GNE 10-35 Figure 10-20 IP-Over-CLNS Tunnel Scenario 2: ONS Node to Router 10-37 Figure 10-21 IP-Over-CLNS Tunnel Scenario 3: ONS Node to Router Across an OSI DCN 10-38 Figure 11-1 ONS 15310-MA Select Affected Circuits Option 11-5 Figure 11-2 Alarm Profile for a 15310-MA CTX2500 Card 11-13 Figure 12-1 TCAs Displayed in CTC 12-2 Figure 12-2 Monitored Signal Types for the DS-1 Ports 12-11 Figure 12-3 PM Parameter Read Points on the DS-1 Ports 12-11 Figure 12-4 Monitored Signal Types for the DS-3 Ports 12-12 Figure 12-5 PM Parameter Read Points on the DS-3 Ports 12-13 Figure 12-6 Monitored Signal Types for the EC-1 Port 12-14 Figure 12-7 PM Read Points on the EC-1 Port 12-14 Figure 12-8 Monitored Signal Types for the OC-3 Port 12-21 Figure 12-9 PM Parameter Read Points on the OC-3 Port 12-21 Figure 12-10 Monitored Signal Types for the OC-12 Ports 12-22 Figure 12-11 PM Parameter Read Points on the OC-12 Ports 12-23 Figure 12-12 Monitored Signal Types for the OC-48 Ports 12-24 Figure 12-13 PM Parameter Read Points on the OC-48 Ports 12-25 Figure 13-1 Basic Network Managed by SNMP 13-2 Figure 13-2 SNMP Agent Gathering Data from a MIB and Sending Traps to the Manager 13-3 Figure 13-3 Example of the Primary SNMP Components 13-3Figures xvi Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0TABLES xvii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Table 1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual Chapters i-xxiii Table 1-1 Alarm Pin Assignments 1-7 Table 1-2 BITS Cable Pin Assignments 1-8 Table 1-3 UDC Cable Pin Assignments 1-8 Table 1-4 Port Line Rates, Connector Types, and Locations 1-10 Table 2-1 DS-1 Cables 2-11 Table 2-2 Champ Connector Pin Assignments—Side-A EIA, Connectors J8 and J9; Side-B EIA, Connectors J21 and J22 2-13 Table 2-3 Champ Connector Pin Assignments—Side-A EIA, Connectors J10 and J11; Side-B EIA, Connectors J23 and J24 2-15 Table 2-4 Champ Connector Pin Assignments—Side-A EIA, Connectors J12 and J13; Side-B EIA, Connectors J25 and J26 2-16 Table 2-5 Default Alarm Pin Assignments—Inputs 2-17 Table 2-6 Default Alarm Pin Assignments—Outputs 2-17 Table 2-7 BITS Cable Pin Assignments 2-18 Table 2-8 UDC Cable Pin Assignments 2-19 Table 2-9 Port Line Rates, Connector Types, and Locations 2-23 Table 3-1 ONS 15310-CL and ONS 15310-MA Cards and Descriptions 3-3 Table 3-2 ONS 15310-CL and ONS 15310-MA Software Release Compatibility Per Card 3-4 Table 3-3 15310-CL-CTX Card-Level Indicators 3-8 Table 3-4 CTX2500 Card-Level Indicators 3-10 Table 3-5 CE-100T-8 Card-Level Indicators 3-13 Table 3-6 CE-100T-8 Port-Level Indicators 3-14 Table 3-7 ML-100T-8 Card-Level Indicators 3-17 Table 3-8 ML-100T-8 Port-Level Indicators 3-17 Table 3-9 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Card-Level Indicators 3-19 Table 3-10 SFP Card Compatibility 3-21 Table 5-1 CTC Computer Requirements 5-4 Table 5-2 ONS 15310-CL and ONS 15310-MA Connection Methods 5-5 Table 5-3 Node View Card and Slot Colors 5-6 Table 5-4 Node View Card Port Colors and Service States 5-7 Table 5-5 Node View Card Statuses 5-8Tables xviii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Table 5-6 Node View Tabs and Subtabs 5-8 Table 5-7 Node Colors Indicating Status in Network View 5-9 Table 5-8 Network View Tabs and Subtabs 5-10 Table 5-9 Link Icons 5-10 Table 5-10 Card View Tabs and Subtabs 5-12 Table 6-1 ONS 15310-CL and ONS 15310-MA Security Levels—Node View 6-2 Table 6-2 ONS 15310-CL and ONS 15310-MA Security Levels—Network View 6-4 Table 6-3 Default User Idle Times 6-6 Table 7-1 SSM Generation 1 Message Set 7-3 Table 7-2 SSM Generation 2 Message Set 7-3 Table 8-1 ONS 15310-CL and ONS 15310-MA Circuit Status 8-3 Table 8-2 Circuit Protection Types 8-5 Table 8-3 Port State Color Indicators 8-6 Table 8-4 DCC Tunnels 8-9 Table 8-5 ONS 15310-CL Card VCAT Circuit Rates and Members 8-12 Table 8-6 ONS 15310-CL VCAT Card Capabilities 8-12 Table 8-7 ONS 15310-CL and ONS 15310-MA Cards/Ports Capable of J1/J2 Path Trace 8-13 Table 8-8 Roll Statuses 8-15 Table 10-1 General P Troubleshooting Checklist 10-2 Table 10-2 ONS 15310-CL or ONS 15310-MA GNE and ENE Settings 10-13 Table 10-3 Proxy Server Firewall Filtering Rules 10-15 Table 10-4 Proxy Server Firewall Filtering Rules When the Packet is Addressed to the ONS 15310-CL or ONS 15310-MA 10-16 Table 10-5 Client and Trunk Card Combinations in Provisionable Patchcords 10-17 Table 10-6 Sample Routing Table Entries 10-17 Table 10-7 Ports Used by the 15310-CL-CTX or CTX2500 10-19 Table 10-8 TCP/IP and OSI Protocols 10-23 Table 10-9 NSAP Fields 10-25 Table 10-10 TARP PDU Fields 10-29 Table 10-11 TARP PDU Types 10-30 Table 10-12 TARP Timers 10-31 Table 10-13 TARP Processing Flow 10-31 Table 10-14 IP Over CLNS Tunnel Cisco IOS Commands 10-34 Table 10-15 OSI Actions from the CTC Node View Provisioning Tab 10-39 Table 10-16 OSI Actions from the CTC Maintenance Tab 10-39 Table 11-1 Alarms Column Descriptions 11-2Tables xix Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Table 11-2 Color Codes for Alarm and Condition Severities 11-3 Table 11-3 STS and Alarm Object Identification 11-3 Table 11-4 Alarm Display 11-4 Table 11-5 Conditions Display 11-6 Table 11-6 Conditions Column Description 11-6 Table 11-7 History Column Description 11-8 Table 11-8 Alarm Profile Buttons 11-11 Table 11-9 Alarm Profile Editing Options 11-11 Table 12-1 Electrical Ports that Report RX Direction for TCAs 12-3 Table 12-2 Performance Monitoring Parameters 12-4 Table 12-3 PM Parameters for DS-1 Ports 12-12 Table 12-4 Parameters for DS-3 Ports 12-13 Table 12-5 EC-1 Port PM Parameters 12-15 Table 12-6 CE-100T-8 and ML-100T-8 Ether Ports Statistics Parameters 12-16 Table 12-7 maxBaseRate for STS Circuits 12-18 Table 12-8 Ethernet History Statistics per Time Interval 12-18 Table 12-9 CE-100T-8 and ML-100T-8 POS Ports Parameters for HDLC Mode 12-18 Table 12-10 CE-100T-8 and ML-100T-8 POS Ports Parameters for GFP-F Mode 12-19 Table 12-11 OC-3 Port PM Parameters 12-22 Table 12-12 OC12 Port PM Parameters 12-23 Table 12-13 OC48 Port PM Parameters 12-25 Table 13-1 SNMP Message Types 13-4 Table 13-2 IETF Standard MIBs Implemented in the ONS 15454, ONS 15327, ONS 15310-CL and ONS 15310-MA SNMP Agent 13-5 Table 13-3 ONS Proprietary MIBs 13-5 Table 13-4 SNMPv2 Trap Variable Bindings 13-6 Table 13-5 Traps Supported in the ONS 15310-CL and ONS 15310-MA 13-7 Table A-1 LED Description A-4 Table A-2 LED Description A-8 Table A-3 SFP Specifications—ONS 15310-CL and ONS 15310-MA A-15 Table A-4 SFP Specifications—ONS 15310-MA Only A-15 Table A-5 Single-Mode Fiber SFP Port Cabling Specifications—ONS 15310-CL and ONS 15310-MA A-15 Table A-6 Single-Mode Fiber SFP Port Cabling Specifications—ONS 15310-MA Only A-16 Table B-1 ONS 15310-CL and ONS 15310-MA Service State Primary States and Primary State Qualifiers B-1 Table B-2 ONS 15310-CL and and ONS 15310-MA Secondary States B-2 Table B-3 ONS 15310-CL and ONS 15310-MA Administrative States B-3Tables xx Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Table B-4 ONS 15310-CL and ONS 15310-MA Card Service State Transitions B-3 Table B-5 ONS 15310-CL and ONS 15310-MA Port and Cross-Connect Service State Transitions B-6 Table C-1 15310-CL-CTX Card Default Settings C-4 Table C-2 Ethernet Card Default Settings C-20 Table C-3 Cisco ONS 15310-CL Node Default Settings C-21 Table C-4 Time Zones C-26 Table C-5 CTC Default Settings C-29 Table C-6 CTX2500 Card Default Settings C-32 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings C-48 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings C-56 Table C-9 ONS 15310-MA Node Default Settings C-65xxi Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This section explains the objectives, intended audience, and organization of this publication and describes the conventions that convey instructions and other information. This section provides the following information: • Revision History • Document Objectives • Audience • Document Organization • Related Documentation • Document Conventions • Obtaining Optical Networking Information • Obtaining Documentation and Submitting a Service Request Revision History Date Notes April 2007 • Revision History Table added for the first time. • Corrected product part numbers for the UBIC-V and UBIC-H DS3 cables. • Added server trail information in the Virtual Concatenated Circuits section in Chapter 8. • Updated About this Guide chapter. September 2007 Added a new rule for creation of protection groups under section “1:1 Electrical Card Protection” in the “Card Protection” chapter.xxii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manual Document Objectives The Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual provides hardware and software reference information for Cisco ONS 15310 nodes and networks. Use this manual in conjunction with the appropriate publications listed in the Related Documentation section. 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. October 2008 • Updated alarm information in External Alarms and Controls section in Alarm Monitoring and Management chapter. • Added a note in Card Default Settings and Node Default Settings section of Appendix C, Network Element Defaults. • Updated section Cabling Types in Chapter 2 with ACS Cable T015654 model and table for compatible DS-1 cables available from Lorom Indrustrial Co., LTD. • Added a note in Table A-8, Single-Mode Fiber SFP Port Cabling Specifications—ONS 15310-MA Only of Appendix A, Specifications. March 2009 • Updated section External Alarms and Controls in Chapter 11, Alarm Monitoring and Management. December 2009 • Updated Figure 2.7, “ACS Cable T015654” in Chapter 2, “Cisco ONS 15310-MA Shelf Assembly Hardware”. April 2010 • Updated the section “SNMP Overview” in the chapter “SNMP”. July 2010 • Updated the section “CE-100T-8 and ML-100T-8 Cards” in the appendix “Specifications”. July 2011 Added a note in the “PC and UNIX Workstation Requirements” section of Chapter, “Cisco Transport Controller Operation”. March 2012 Updated the sections “15310-CL-CTX” and “CTX2500 Card” in the appendix “Specifications”. August 2012 The full length book-PDF was generated. Date Notesxxiii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manual Document Organization Table 1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual Chapters Title Summary Chapter 1, “Cisco ONS 15310-CL Shelf Assembly Hardware” Includes descriptions of the rack, power and ground, cables, fans, and slots on the ONS 15310-CL. Chapter 2, “Cisco ONS 15310-MA Shelf Assembly Hardware” Includes descriptions of the rack, power and ground, cables, electrical interface assemblies (EIAs), fan-tray assembly (FTA), and slots on the ONS 15310-MA. Chapter 3, “Card Reference” Includes descriptions of all cards in the ONS 15310-CL and 15310-MA. Chapter 4, “Card Protection” Includes electrical and optical card protection methods. Chapter 5, “Cisco Transport Controller Operation” Includes information about CTC installation, the CTC window, computer requirements, software versions, and database reset and revert. Chapter 6, “Security” Includes information for user set up, security privileges, security policies, audit trail, and RADIUS authentication. Chapter 7, “Timing” Includes node and network timing information. Chapter 8, “Circuits and Tunnels” Includes STS and VT, bidirectional and unidirectional, revertive and nonrevertive, electrical and optical, multiple and path trace circuit information, as well as data communications channel (DCC) tunnels. Chapter 9, “SONET Topologies and Upgrades” Includes the SONET configurations used by the ONS 15310-CL and ONS 15310-MA; including path protection configurations, linear add/drop multiplexers (ADMs), subtending rings, and optical bus configurations, as well as information about upgrading optical speeds within any configuration. Chapter 10, “Management Network Connectivity” Includes IP addressing scenarios and information about provisionable patchcords, the IP routing table, external firewalls, open gateway network element (GNE) networks, and OSI protocols. Chapter 11, “Alarm Monitoring and Management” Includes CTC alarm management information. Chapter 12, “Performance Monitoring” Includes performance-monitoring parameters for each ONS 15310-CL and ONS 15310-MA card. Chapter 13, “SNMP” Describes Simple Network Management Protocol (SNMP) as implemented by the ONS 15310-CL and ONS 15310-MA.xxiv Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manual Related Documentation Use the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual in conjunction with the following referenced publications: • Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide Provides installation, turn up, test, and maintenance procedures. • Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide Provides alarm descriptions and troubleshooting procedures, general troubleshooting procedures, error messages, performance monitoring parameters, and SNMP information. • Cisco ONS SONET TL1 Command Guide Provides a full TL1 command and autonomous message set including parameters, AIDs, conditions and modifiers for the Cisco ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and Cisco ONS 15310-MA systems. • Cisco ONS SONET TL1 Reference Guide Provides general information, procedures, and errors for TL1 in theCisco ONS 15454, ONS 15327, ONS 15600, ONS 15310-CL, and Cisco ONS 15310-MA systems. • Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide Provides software feature and operation information for Ethernet cards in the Cisco ONS 15310-CL and Cisco ONS 15310-MA. • Release Notes for the Cisco ONS 15310-CL Release 7.0 Provides caveats, closed issues, and new features and functionality information. • Release Notes for the Cisco ONS 15310-MA Release 7.0 Provides caveats, closed issues, and new features and functionality information. For an update on End-of-Life and End-of-Sale notices, refer to http://www.cisco.com/en/US/products/hw/optical/ps2001/prod_eol_notices_list.html. Document Conventions This publication uses the following conventions: Appendix A, “Specifications” Includes shelf assembly and card specifications for the ONS 15310-CL and ONS 15310-MA. Appendix B, “Administrative and Service States” Describes card, port, and cross-connect service states. Appendix C, “Network Element Defaults” Lists card, node, and CTC-level network element (NE) defaults. Table 1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual Chapters Title Summaryxxv Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manual Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document. Caution Means reader be careful. In this situation, the user might do something that could result in equipment damage or loss of data. Convention Application boldface Commands and keywords in body text. italic Command input that is supplied by the user. [ ] Keywords or arguments that appear within square brackets are optional. { x | x | x } A choice of keywords (represented by x) appears in braces separated by vertical bars. The user must select one. 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.xxvi Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manual Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071 SAVE THESE INSTRUCTIONS Waarschuwing BELANGRIJKE VEILIGHEIDSINSTRUCTIES Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van de standaard praktijken om ongelukken te voorkomen. Gebruik het nummer van de verklaring onderaan de waarschuwing als u een vertaling van de waarschuwing die bij het apparaat wordt geleverd, wilt raadplegen. BEWAAR DEZE INSTRUCTIES Varoitus TÄRKEITÄ TURVALLISUUSOHJEITA Tämä varoitusmerkki merkitsee vaaraa. Tilanne voi aiheuttaa ruumiillisia vammoja. Ennen kuin käsittelet laitteistoa, huomioi sähköpiirien käsittelemiseen liittyvät riskit ja tutustu onnettomuuksien yleisiin ehkäisytapoihin. Turvallisuusvaroitusten käännökset löytyvät laitteen mukana toimitettujen käännettyjen turvallisuusvaroitusten joukosta varoitusten lopussa näkyvien lausuntonumeroiden avulla. SÄILYTÄ NÄMÄ OHJEET 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. Pour prendre connaissance des traductions des avertissements figurant dans les consignes de sécurité traduites qui accompagnent cet appareil, référez-vous au numéro de l'instruction situé à la fin de chaque avertissement. CONSERVEZ CES INFORMATIONS Warnung WICHTIGE SICHERHEITSHINWEISE Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu Verletzungen führen kann. Machen Sie sich vor der Arbeit mit Geräten mit den Gefahren elektrischer Schaltungen und den üblichen Verfahren zur Vorbeugung vor Unfällen vertraut. Suchen Sie mit der am Ende jeder Warnung angegebenen Anweisungsnummer nach der jeweiligen Übersetzung in den übersetzten Sicherheitshinweisen, die zusammen mit diesem Gerät ausgeliefert wurden. BEWAHREN SIE DIESE HINWEISE GUT AUF.xxvii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manual Avvertenza IMPORTANTI ISTRUZIONI SULLA SICUREZZA Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti. Utilizzare il numero di istruzione presente alla fine di ciascuna avvertenza per individuare le traduzioni delle avvertenze riportate in questo documento. CONSERVARE QUESTE ISTRUZIONI Advarsel VIKTIGE SIKKERHETSINSTRUKSJONER Dette advarselssymbolet betyr fare. Du er i en situasjon som kan føre til skade på person. Før du begynner å arbeide med noe av utstyret, må du være oppmerksom på farene forbundet med elektriske kretser, og kjenne til standardprosedyrer for å forhindre ulykker. Bruk nummeret i slutten av hver advarsel for å finne oversettelsen i de oversatte sikkerhetsadvarslene som fulgte med denne enheten. TA VARE PÅ DISSE INSTRUKSJONENE Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA Este símbolo de aviso significa perigo. Você está em uma situação que poderá ser causadora de lesões corporais. Antes de iniciar a utilização de qualquer equipamento, tenha conhecimento dos perigos envolvidos no manuseio de circuitos elétricos e familiarize-se com as práticas habituais de prevenção de acidentes. Utilize o número da instrução fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham este dispositivo. GUARDE ESTAS INSTRUÇÕES ¡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. GUARDE ESTAS INSTRUCCIONES Varning! VIKTIGA SÄKERHETSANVISNINGAR Denna varningssignal signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanliga förfaranden för att förebygga olyckor. Använd det nummer som finns i slutet av varje varning för att hitta dess översättning i de översatta säkerhetsvarningar som medföljer denna anordning. SPARA DESSA ANVISNINGARxxviii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manualxxix Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 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. GUARDE ESTAS INSTRUÇÕES Advarsel VIGTIGE SIKKERHEDSANVISNINGER Dette advarselssymbol betyder fare. Du befinder dig i en situation med risiko for legemesbeskadigelse. Før du begynder arbejde på udstyr, skal du være opmærksom på de involverede risici, der er ved elektriske kredsløb, og du skal sætte dig ind i standardprocedurer til undgåelse af ulykker. Brug erklæringsnummeret efter hver advarsel for at finde oversættelsen i de oversatte advarsler, der fulgte med denne enhed. GEM DISSE ANVISNINGERxxx Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this Manualxxxi Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 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. This publication describes the international agency compliance and safety information for the Cisco ONS 15310 system. It also includes translations of the safety warnings that appear in the ONS 15310 system documentation. Cisco Optical Networking Product Documentation CD-ROM Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation. 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.html Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0xxxii Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 About this ManualCHAPTER 1-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 1 Cisco ONS 15310-CL Shelf Assembly Hardware This chapter provides a description of Cisco ONS 15310-CL shelf hardware. Instructions for installing equipment are provided in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 1.1 Installation Overview, page 1-1 • 1.2 Rack Installation, page 1-2 • 1.3 Power and Ground Description, page 1-5 • 1.4 Cable Description and Installation, page 1-5 • 1.5 Fans, page 1-9 • 1.6 Cards and Slots, page 1-9 Note The Cisco ONS 15310-CL assembly is intended for use with telecommunications equipment only. Note The ONS 15310-CL is designed to comply with Telcordia GR-1089-CORE Type 2 and Type 4. Install and operate the ONS 15310-CL only in environments that do not expose wiring or cabling to the outside plant. Acceptable applications include Central Office Environments (COEs), Electronic Equipment Enclosures (EEEs), Controlled Environment Vaults (CEVs), huts, and Customer Premise Environments (CPEs). 1.1 Installation Overview You can mount the ONS 15310-CL in a 19- or 23-inch (482.6 or 584.2 mm) rack or it can be placed on a flat surface using the installed rubber feet. When installed in a rack, reversible mounting brackets should be used on each side of the shelf. The shelf assembly weighs 11.5 pounds (5.22 kg) without a card installed and 12.5 pounds (5.67 kg) with all hardware installed. The ONS 15310-CL is powered using –48 VDC or 100/240 VAC power. AC power terminals are accessible on the front panel and the DC power connection is accessible on the rear of the shelf assembly. CRIT, MAJ, MIN, and REM alarm LEDs are visible on the front of the node and indicate whether a Critical, Major, Minor, or Remote alarm is present anywhere on the ONS 15310-CL. Ethernet cards, small form-factor pluggables (SFPs), cables, and ports are accessible through the front of the shelf assembly only. 1-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.2 Rack Installation When installed in an equipment rack, the ONS 15310-CL assembly is typically connected to a fuse and alarm panel that provides centralized alarm connection points and distributed power for the ONS 15310-CL. Fuse and alarm panels are third-party equipment and are not described in this documentation. If you are unsure about the requirements or specifications for a fuse and alarm panel, consult the documentation for that product. Note In this chapter, the terms “ONS 15310-CL” and “shelf assembly” are used interchangeably. In the installation context, these terms have the same meaning. Otherwise, shelf assembly refers to the physical steel enclosure that holds cards and connects power, and ONS 15310-CL refers to the entire system, both hardware and software. Install the ONS 15310-CL in compliance with your local and national electrical codes: • 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 Detailed compliance and safety information is provided in the Cisco Optical Transport Products Safety and Compliance Information document that ships with the Cisco ONS 15310-CL. 1.2 Rack Installation The ONS 15310-CL is easily mounted in a 19- or 23-inch (482.6 or 584.2 mm) equipment rack. The shelf assembly can be mounted so that it projects five inches from the front of the rack. It mounts in both EIA-standard and Telcordia-standard racks. The shelf assembly is a total of 17.25 inches (438.2 mm) wide. The ONS 15310-CL measures 1.75 inches high, 19 or 23 inches wide (depending on which brackets are installed), and 15 inches deep (44.4 x 482.6 or 584.2 x 381 mm). Figure 1-1 shows the dimensions of the ONS 15310-CL shelf assembly.1-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.2.1 Mounting Bracket Figure 1-1 ONS 15310-CL Shelf Assembly Dimensions 1.2.1 Mounting Bracket Caution Use only the fastening hardware provided with the ONS 15310-CL to prevent loosening, deterioration, and electromechanical corrosion of the hardware and joined material. Caution When mounting the ONS 15310-CL in a frame with a non-conductive coating (such as paint, lacquer, or enamel) use either the thread-forming screws provided with the ONS 15310-CL shipping kit or remove the coating from the threads to ensure electrical continuity. The shelf assembly comes with two mounting brackets, one for use with a 19-inch (482.6 mm) or 23-inch (584.2 mm) rack. Figure 1-2 shows the mounting bracket orientation for a 19-inch rack. Front View 17.25 in. (438.2 mm) Side View 13.0 in. (330.2 mm) Top View 17.25 in. (438.2 mm) 1.75 in. (44.4 mm) 13.0 in. (330.2 mm) 19.0 or 23.0 in. (482.6 or 584.2 mm) 19.0 or 23.0 in. (482.6 or 584.2 mm) 1248981-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.2.1 Mounting Bracket Figure 1-2 Mounting Brackets (19-Inch Orientation) Figure 1-3 shows the mounting bracket orientations for a 23-inch rack. The brackets are installed in the same mounting holes for both rack sizes. Figure 1-3 Mounting Brackets (23-Inch Orientation) 124942 1249431-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.2.2 Mounting a Single Node 1.2.2 Mounting a Single Node Mounting the ONS 15310-CL in a rack requires a minimum of 1.75 inches of vertical rack space (plus 1 inch [25.4 mm] for air flow). To ensure that the mounting is secure, use two #12-24 mounting screws for each side of the shelf assembly. 1.2.3 Mounting Multiple Nodes Most standard seven-foot (2.1 m) racks can hold numerous ONS 15310-CL nodes and a fuse and alarm panel. 1.3 Power and Ground Description This section describes how to connect the ONS 15310-CL shelf assembly to the power supply. For detailed procedures, refer to the “Install the Cisco ONS 15310-CL” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Terminate the chassis ground on the rear of the shelf assembly to either the office ground or rack ground before you install the power. Use the grounding lug to attach the #6 AWG ground cable to the shelf assembly according to local site practice. Ground one cable to ground the shelf assembly. Terminate the other end of the rack ground cable to ground according to local site practice. If the system loses power or the 15310-CL-CTX card is reset, you must reset the ONS 15310-CL clock unless the node has been previously provisioned to use Simple Network Time Protocol (SNTP) to update the clock over the LAN. Caution Always use the supplied ESD wristband when working with a powered ONS 15310-CL. Plug the wristband cable into the ESD jack located to the left of the expansion slot. Warning A readily accessible two-poled disconnect device must be incorporated in the fixed wiring. Statement 1022 The ONS 15310-CL can be ordered with either AC or DC power capability. The DC power option provides redundant –48 VDC power terminals on the rear of the chassis. The terminals are labeled A and B and are located at each end of the shelf assembly. The ONS 15310-CL AC power connector is located at the bottom right on the front of the chassis. The power cables are provided with the ship kit. To install redundant power feeds, use four power cables and one ground cable. For a single power feed, only two power cables and one ground cable are required. Use #14 AWG power cables and a #6 AWG ground cable and, to ensure circuit overcurrent protection, use a conductor with low impedance. However, the conductor must have the capability to safely conduct any fault current that might be imposed. Do not use aluminum conductors. 1.4 Cable Description and Installation This section describes fiber-optic, DS-3/EC-1 (coaxial), DS-1 (96-pin LFH), UDC, and twisted-pair cables. 1-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.4.1 Cabling Types 1.4.1 Cabling Types The following types of cables are used with the ONS 15310-CL: • Optical cables: The OC-3/12 signals operate over fiber spans via small form-factor pluggable (SFP) optics, including intermediate-reach (IR), and long-reach (LR) SFPs. Specification references can be found for the interface in ITU G.957 and GR-253. See “1.4.2 Fiber Cable Installation” section on page 1-6 for more information. Make sure the fiber cables do not bend excessively; maintaining a proper bend radius prevents damage to the optical cable. • Coaxial cables: Coaxial cables connect to the electrical ports using MiniBNC cable connectors. Coaxial cables carry DS-3/EC-1 traffic to and from the ONS 15310-CL. The ONS 15310-CL supports up to three transmit and three receive coaxial connectors on each shelf assembly. Note Cisco recommends you use Cisco-orderable MiniBNC cables to ensure interoperability between the cables and Trompeter MiniBNC connectors on the ONS 15310-CL. • LFH cables: A 96-pin LFH cable provides access to a maximum of 21 DS-1s. See the “1.4.4 DS-1 Cable Installation” section on page 1-7 for more information about the DS-1 cables and connectors. • RJ-45 cables: RJ-45 cables connect to the alarm, LAN, CRAFT, UDC, and timing (BITS) ports. Shielded Twisted-pair (STP) #22 or #24 AWG wire is required for the CRAFT, and UDC ports. Unshielded Twisted-pair is sufficient for the alarm, LAN, and timing ports. 1.4.2 Fiber Cable Installation To install fiber-optic cables on the ONS 15310-CL, a fiber cable with an LC connector must be connected to the SFPs installed in the SFP port on the ONS 15310-CL. The left side connector on the SFP is the transmit port and the right side connector is the receive port. Cisco recommends that you label the transmit and receive ports and the working and protection fibers at each end of the fiber span to avoid confusion with cables that are similar in appearance. Caution You must provide some type of strain relief for the cables, using either the tie-bars specifically designed for the ONS 15310-CL or a site-specific solution. Note Clean all fiber connectors thoroughly. Dust particles can degrade performance. Put caps on any fiber connectors that you do not use. 1.4.3 Coaxial Cable Installation For DS-3/EC-1 traffic the ONS 15310-CL uses coaxial cables and connectors. Cisco recommends connecting a 735A coaxial cable to a patch panel. Use a compatible straight male BNC connector to connect the cable to the DS-3/EC-1 ports. The DS-3/EC-1 cables should be terminated with MiniBNC connectors on the ONS 15310-CL side and BNC connectors on the client side. The electromagnetic compatibility (EMC) performance of the node depends on good-quality DS-3/EC-1 coaxial cables, such as Shuner Type G 03233 D, or the equivalent.1-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.4.4 DS-1 Cable Installation 1.4.4 DS-1 Cable Installation The ONS 15310-CL uses 96-pin LFH connector cabling for DS-1 connections. 1.4.5 Alarm Cable Installation The alarm cables attach to the front of the 15310-CL using an RJ-45 connector that plugs into the ALARM port. The other end of the cable plugs into the alarm-collection equipment. Terminate this end of the cable according to local site practice. The pins on the ALARM port correspond to the three external alarm inputs and the two external alarm outputs (controls) that you can define using Cisco Transport Controller (CTC). Table 1-1 lists the input alarm pinouts and the corresponding alarm function numbers assigned to each port. Figure 1-4 shows RJ-45 pin numbering. Figure 1-4 Pins 1 and 8 on the RJ-45 Connector For more information about external alarms and controls, see the “11.6 External Alarms and Controls” section on page 11-14. Table 1-1 Alarm Pin Assignments RJ-45 Pin Number Function 1 Alarm Contact 1+ 2 Alarm Contact 1– 3 Alarm Contact 2+ 4 Alarm Contact 2– 5 Alarm Input 1 6 Alarm Input 2 7 Alarm Input 3 8 Alarm Input Common 49564 Pin 1 Pin 81-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.4.6 BITS Cable Installation 1.4.6 BITS Cable Installation The building integrated timing supply (BITS) cables attach to the ONS 15310-CL using BITS clock cable and twisted-pair #22 or #24 unshielded AWG wire terminated with an RJ-45 connector that plugs into the BITS port. The other end of the cable plugs into the BITS clock. Terminate this end of the cable according to local site practice. The 15310-CL has one BITS input and one BITS output. The BITS inputs and outputs have corresponding pins on the RJ-45 BITS ports. When connecting BITS cable to the ONS 15310-CL, see Table 1-2 for the BITS cable pin assignments. For more information about connecting BITS timing to the ONS 15310-CL, refer to Chapter 7, “Timing.”. Note Refer to Telcordia SR-NWT-002224 for rules about how to provision timing references. 1.4.7 UDC Cable Installation The 64K/RS-232 user data channel (UDC) interface provides E1, E2, F1, and F2 byte input and output. When connecting UDC cable to the ONS 15310-CL, see Table 1-3 for the UDC cable pin assignments. Shielded Twisted-pair (STP) #22 or #24 AWG wire is required for the UDC ports. . Table 1-2 BITS Cable Pin Assignments RJ-45 Pin Number Function 1 BITS Output+ 2 BITS Output– 3 BITS Input+ 4 — 5 — 6 BITS Input– 7 — 8 — Table 1-3 UDC Cable Pin Assignments Pin Number Function (RS-232 Mode) Function (64K Mode) 1 NC TX+ 2 DTR TX– 3 TXD RX+ 4 GND GND 5 GND GND 6 RXC RX–1-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.5 Fans 1.5 Fans The ONS 15310-CL has five fans permanently mounted to the inside of the chassis. The fans are not removable. 1.6 Cards and Slots Caution Always use the supplied ESD wristband when working with a powered ONS 15310-CL. Plug the wristband cable into the ESD jack located to the left of the expansion slot. The ONS 15310-CL provides one expansion slot that can accommodate one of two Ethernet cards, the CE-100T-8 card or the ML-100T-8 card. These cards have electrical plugs at the back that plug into electrical connectors on the shelf assembly backplane. When the ejectors are fully closed, the card plugs into the assembly backplane. Refer to Chapter 3, “Card Reference” for more information about ONS 15310-CL cards. 7 NC NC 8 NC NC Table 1-3 UDC Cable Pin Assignments (continued) Pin Number Function (RS-232 Mode) Function (64K Mode)1-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 1 Cisco ONS 15310-CL Shelf Assembly Hardware 1.6 Cards and Slots Figure 1-5 shows card installation for the ONS 15310-CL. Figure 1-5 Installing an Ethernet Card Note DS-1 and DS-3/EC-1 interfaces are not intended for direct connection to the network. These interfaces should be connected to the network via a CSU/DSU that has the proper certification. Table 1-4 lists the number of ports, line rates, connector options, and connector locations for ONS 15310-CL electrical, Ethernet, and optical interfaces. 124657 Table 1-4 Port Line Rates, Connector Types, and Locations Interface Ports Line Rate per Port Connector Type Connector Location DS-1 21 1.544 Mbps 96-pin LFH Front of the 15310-CL DS-3 3 44.736 Mbps 75-ohm MiniBNC Front of the 15310-CL EC-1 3 51.84 Mbps 75-ohm MiniBNC Front of the 15310-CL OC-3/OC-12 2 155.52 Mbps (STS-3) 622.08 Mbps (STS-12) LC Front of the 15310-CL CE-100T-8 8 10/100 Mbps RJ-45 CE-100T-8 card faceplate (expansion slot) ML-100T-8 8 10/1000 Mbps RJ-45 ML-100T-8 card faceplate (expansion slot)CHAPTER 2-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 2 Cisco ONS 15310-MA Shelf Assembly Hardware This chapter provides a description of Cisco ONS 15310-MA shelf hardware. Instructions for installing equipment are provided in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 2.1 Installation Overview, page 2-1 • 2.2 Rack Installation, page 2-2 • 2.3 Electrical Interface Assemblies, page 2-5 • 2.4 Front Door, page 2-6 • 2.5 Power and Ground Description, page 2-7 • 2.6 Cable Description and Installation, page 2-10 • 2.7 Cable Routing and Management, page 2-19 • 2.8 Fan-Tray Assembly, page 2-21 • 2.9 Cards and Slots, page 2-22 Note The Cisco ONS 15310-MA assembly is intended for use with telecommunications equipment only. Note The ONS 15310-MA is designed to comply with Telcordia GR-1089-CORE Type 2 and Type 4. Acceptable applications include Central Office Environments (COEs), Electronic Equipment Enclosures (EEEs), Controlled Environment Vaults (CEVs), huts, and Customer Premise Environments (CPEs). 2.1 Installation Overview You can mount the ONS 15310-MA in a 19-inch (482.6 mm) or 23-inch (584.2 mm) rack. The ONS 15310-MA is powered using –48 VDC power. DC power connections are accessed from the rear of the shelf assembly. ONS 15310-MA Ethernet and optical ports are accessible at the front of the shelf assembly, and electrical connections (DS-1, DS-3/EC-1) are accessible at the rear of the shelf assembly through electrical interface assemblies (EIAs).2-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.2 Rack Installation When installed in an equipment rack, the ONS 15310-MA assembly is typically connected to a fuse and alarm panel that provides centralized alarm connection points and distributed power for the ONS 15310-MA. Fuse and alarm panels are third-party equipment and are not described in this documentation. If you are unsure about the requirements or specifications for a fuse and alarm panel, consult the documentation for that product. Note In this chapter, the terms “ONS 15310-MA” and “shelf assembly” are used interchangeably. In the installation context, these terms have the same meaning. Otherwise, shelf assembly refers to the physical steel enclosure that holds cards and connects power, and ONS 15310-MA refers to the entire system, both hardware and software. Install the ONS 15310-MA in compliance with your local and national electrical codes: • 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 Detailed compliance and safety information is provided in the Cisco Optical Transport Products Safety and Compliance Information document that ships with the Cisco ONS 15310-MA. 2.2 Rack Installation The ONS 15310-MA is easily mounted in a 19-inch (482.6 mm) or 23-inch (584.2 mm) equipment rack. The shelf assembly can be mounted so that it projects five inches from the front of the rack. It mounts in both EIA-standard and Telcordia-standard racks. A single shelf assembly is 10.67 inches (27.1 mm) wide and occupies 6 RUs (10.5 in. [267.6 mm]) in a rack when installed with a standard cable management bracket. If an extended cable management bracket is installed below the shelf assembly, an additional RU is occupied, for a total of 7 RUs (12.25 in. [311.1 mm]). Two shelf assemblies can be installed side-by-side in a single 23-inch rack; see the “2.2.3 Mounting Multiple Nodes” section on page 2-5 for more information. The ONS 15310-MA measures 10.44 inches (26.51 cm) high, 10.67 inches (27.10 cm) wide, and 12 inches (20.48 cm) deep. Figure 2-1 shows the dimensions of the ONS 15310-MA shelf assembly.2-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.2.1 Mounting Brackets Figure 2-1 ONS 15310-MA Shelf Assembly Dimensions 2.2.1 Mounting Brackets Caution Use only the fastening hardware provided with the ONS 15310-MA to prevent loosening, deterioration, and electromechanical corrosion of the hardware and joined material. Caution When mounting the ONS 15310-MA in a frame with a nonconductive coating (such as paint, lacquer, or enamel) use either the thread-forming screws provided with the ONS 15310-MA shipping kit or remove the coating from the threads to ensure electrical continuity. The shelf assembly ships with mounting brackets suitable for use with 19-inch (482.6mm) and 23-inch (584.2 mm) racks. 12 inches (20.48 cm) deep 10.44 inches (26.51 cm) high 10.67 inches (27.10 cm) wide 1446882-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.2.2 Mounting a Single Node 2.2.2 Mounting a Single Node Mounting the ONS 15310-MA in a rack requires a minimum of 10.5 inches of vertical rack space. To ensure that the mounting is secure, use four #12-24 mounting screws for each side of the shelf assembly. If the larger cable router is used, 12.5 inches of rack space is required. Figure 2-2 shows a single ONS 15310-MA being mounted in a rack, using a universal bracket. Figure 2-2 Mounting a Single ONS 15310-MA in a Rack 1447052-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.2.3 Mounting Multiple Nodes 2.2.3 Mounting Multiple Nodes Most standard seven-foot (2.1 m) racks can hold numerous ONS 15310-MA nodes and a fuse and alarm panel. Two shelf assemblies can be installed side-by-side in a single 23-inch rack, using a special mounting bracket. You can install both ONS 15310-MA shelves in the 23-inch rack at one time, or you can mount a second shelf assembly next to a shelf assembly that has already been installed. Refer to the “Install the Cisco ONS 15310-MA” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for more information. 2.3 Electrical Interface Assemblies High-density EIAs are attached to the ONS 15310-MA shelf assembly backplane to provide up to 168 transmit and receive DS-1 connections through six Champ connectors per side (A and B) or six transmit and receive DS-3/EC-1 connections through six BNC connectors per side. The EIAs are designed to support DS-1, DS-3, and EC-1 signals. The appropriate cable assembly is required depending on the type of signal. Note The HD expansion connectors on the high-density EIA are not supported in Software Release 7.0.x and earlier. You can install EIAs on one or both sides of the ONS 15310-MA. As you face the rear of the shelf assembly, the right side is the A side (15310-EIA-HD-A) and the left side is the B side (15310-EIA-HD-B). Figure 2-3 shows the J connectors on the A- and B-side high-density EIAs installed on the ONS 15310-MA.2-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.4 Front Door Figure 2-3 High-Density EIA Connectors To install the EIA on the rear of the shelf assembly, you must first remove the standard sheet metal covers. The EIAs use the same screw holes as the standard sheet metal covers, but they use three holes for panhead screws and two holes for jack screws. When installed with the standard door and cabling on the backplane, the ONS 15310-MA shelf measures approximately 13.7 inches (34.8 cm) deep when fully populated with backplane cables. 2.4 Front Door The ONS 15310-MA is orderable with a front door. You must install the ground strap on the door after you install the door (Figure 2-4). 151584 DS1 OUT J8 DS1 IN J9 DS1 OUT J10 DS1 IN J11 DS1 OUT J12 DS1 IN J13 J20-HD DS3 1 3 2 J6-ALM INPUT PWR A J15-IN J16-OUT J17-IN J14-OUT J18-OUT J19-IN PID VID S/N BAR CODE CLEI CODE P/N COO -48VDC RTN DS1 OUT J21 DS1 IN J22 DS1 OUT J23 DS1 IN J24 DS1 OUT J25 DS1 IN J26 J33-HD DS3 1 2 3 PWR B J1-LAN J29-OUT J30-IN J31-OUT J27-OUT J28-IN J32-IN PID VID S/N CLEI CODE BAR CODE P/N COO RTN -48VDC J2-CRFT J3-UDC J4-BITS1 J5-BITS2 J7-ALM OUT2-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.5 Power and Ground Description Figure 2-4 ONS 15310-MA Door Ground Strap 2.5 Power and Ground Description This section describes how to connect the ONS 15310-MA shelf assembly to the power supply. For detailed procedures, refer to the “Install the Cisco ONS 15310-MA” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Terminate the chassis ground (located on both sides of the rear of the shelf assembly or at the bottom of the shelf assembly) to either the office ground or rack ground before you install the power. Use the grounding lug to attach the #6 AWG ground cable to the #10-32 mount ground lug on the shelf assembly according to local site practice. Ground one cable to ground the shelf assembly. Terminate the other end of the rack ground cable to ground according to local site practice. Figure 2-5 shows the grounding holes on the bottom of the ONS 15310-MA. 1447062-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.5 Power and Ground Description Figure 2-5 Ground Holes on the Bottom of the ONS 15310-MA Shelf Assembly Figure 2-6 show the grounding holes on the sides of the ONS 15310-MA. 144707 Ground holes2-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.5 Power and Ground Description Figure 2-6 Ground Holes on the Left and Right Sides of the ONS 15310-MA Shelf Assembly Caution Always use the supplied ESD wristband when working with a powered ONS 15310-MA. Plug the wristband cable into either ESD jack, located on the far left and right slots of the shelf assembly. Note Use an external disconnect for service purposes and install it according to local site practice. Ground holes 144708 Ground holes2-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6 Cable Description and Installation The ONS 15310-MA DC power provides redundant –48 VDC power terminals on the rear of the chassis. The terminals are labeled A and B and are located at each end of the shelf assembly. To install redundant power feeds, use four power cables and one ground cable. For a single power feed, only two power cables and one ground cable are required. Use #12 AWG power cables and a #6 AWG ground cable and, to ensure circuit overcurrent protection, use a conductor with low impedance. The conductor must have the capability to safely conduct any fault current that might be imposed. Do not use aluminum conductors. Caution If the system loses power or the CTX2500 card is reset, you must reset the ONS 15310-MA clock unless the node has been previously provisioned to use Simple Network Time Protocol (SNTP). SNTP updates the clock over the LAN. 2.6 Cable Description and Installation This section describes fiber-optic, DS-3/EC-1 (coaxial), DS-1 (64-pin Champ), UDC, and twisted-pair cables. 2.6.1 Cabling Types The following types of cables are used with the ONS 15310-MA: • Optical cables: The OC-3/12/48 signals operate over fiber spans through SFP optics, including intermediate-reach (IR) and long-reach (LR) SFPs. Specification references can be found for the interface in ITU G.957 and Telcordia GR-253. See the “2.6.2 Fiber Cable Installation” section on page 2-12 for more information. Make sure the fiber cables do not bend excessively; maintaining a proper bend radius prevents damage to the optical cable. • DS-1 cables: DS-1 cables (shielded, twisted-pair) connect to the electrical ports at the rear of the shelf assembly using Champ cable connectors. DS-1 cables carry DS-1 traffic to and from the ONS 15310-MA. The ONS 15310-MA supports up to three transmit and three receive Champ-64 connectors on each side of the shelf assembly, for a maximum of 84 DS-1 signals per side of the shelf. A compatible DS-1 cable is available from Atlanta Cable Sales, Inc. Atlanta Cable Sales, Inc. 495 Horizon Drive, Suite 200 Suwanee, GA 30024 1-800-241-9881, Ext. 4014 http://www.acssolutions.com The ACS part number and description are: T015654-Length. Cable assembly with the cable exit at 1 & 33. This cable solution offers two screw points on the cable head for attachment, see Figure 2-7 on page 2-11, and is equivalent in characteristics to the defacto 1161A rated cable. 2-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.1 Cabling Types Figure 2-7 ACS Cable T015654 Refer to Table 2-1 for compatible DS-1 cables available from Lorom Indrustrial Co., LTD. Lorom Industrial Co., LTD. 15th Floor, Room 2, Number 78, Sec 2 AN-HO Road Taipei, Taiwan Phone: 886-2-2706-6037 Fax: 886-2-2704-6396 • Coaxial cables: Coaxial cables connect to the electrical ports using BNC cable connectors. Coaxial cables carry DS-3/EC-1 traffic to and from the ONS 15310-MA. The ONS 15310-MA supports up to three transmit and three receive coaxial connectors on each shelf assembly. • RJ-45 cables: RJ-45 cables connect to the LAN, CRAFT, and UDC ports. An unshielded twisted-pair (STP) #22 or #24 AWG wire is required for the CRAFT and UDC ports. Unshielded twisted-pair is sufficient for the alarm, LAN, and timing ports. 10/100-Mbps RJ-45 Ethernet cables are used to connect the CE-100T-8 and ML-100T-8 cards. • Alarm and timing (BITS) cables: The Alarm In port requires a shielded cable terminated with a DB-37 connector; Alarm Out requires a shielded cable terminated with a DB-25 connector; and the building integrated timing supply (BITS) ports require DB-9 connectors. 240751 1 33 32 & 64 1 & 33 Front view Top view of hood 64 position male Telco connector Main label 1/8” clear heatshrink covering screw P1 label 32 64 Table 2-1 DS-1 Cables ACS Part Numbers Length Description PCAM90SPA0PC001 25 feet Connector-Wire Wrap, DSX PCAM90SPA1OC001 50 feet Connector-Wire Wrap, DSX PCAM90SPA3MC001 100 feet Connector-Wire Wrap, DSX PCAM90SPA7IC001 200 feet Connector-Wire Wrap, DSX2-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.2 Fiber Cable Installation 2.6.2 Fiber Cable Installation To install fiber-optic cables on the ONS 15310-MA, a fiber cable with an LC connector must be connected to an SFP. SFPs are installed in the SFP port on the ONS 15310-MA. Each LC connector contains the transmit (Tx) and receive (Rx) signal for that port. Cisco recommends that you label the transmit and receive ports and the working and protection fibers at each end of the fiber span to avoid confusion with cables that are similar in appearance. You can route fiber cables through the optional fiber guide, installed at the bottom of the shelf assembly (Figure 2-8). Figure 2-8 Shelf Assembly with Fiber Guide Installed Caution You must provide some type of strain relief for the cables, using either a tie-bar or other site-specific solution. 144704 Fiber guide2-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.3 Coaxial Cable Installation Note Clean all fiber connectors thoroughly. Dust particles can degrade performance. Put caps on any fiber connectors that you do not use. 2.6.3 Coaxial Cable Installation For DS-3/EC-1 traffic, the ONS 15310-MA uses coaxial cables and connectors. Cisco recommends connecting a 735A coaxial cable to a patch panel. Use a compatible male BNC connector to connect the cable to the DS-3/EC-1 ports. The DS-3/EC-1 cables should be terminated with BNC connectors on the ONS 15310-MA side and BNC connectors on the client side. Due to the minimal space between BNC connectors and DS-1 connectors, you might require a special tool for inserting and removing BNC EIAs (Figure 2-9). Figure 2-9 BNC Insertion and Removal Tool 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 2.6.4 DS-1 Cable Installation The ONS 15310-MA uses 64-pin Champ connector cabling for DS-1 connections. Table 2-2 lists the Champ connector pin assignments and the corresponding EIA connector mapping for connectors J8 and J9 on the EIA installed on the A side, and connectors J21 and J22 on the EIA installed on the B side. 44552 Table 2-2 Champ Connector Pin Assignments—Side-A EIA, Connectors J8 and J9; Side-B EIA, Connectors J21 and J22 Signal Pin Signal Pin Ring Port 1 1 Tip Port 1 33 Ring Port 2 2 Tip Port 2 34 Ring Port 3 3 Tip Port 3 35 Ring Port 4 4 Tip Port 4 362-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.4 DS-1 Cable Installation Table 2-3 lists the Champ connector pin assignments and the corresponding EIA connector mapping for connectors J10 and J11 on the EIA installed on the A side, and connectors J23 and J24 on the EIA installed on the B side. Ring Port 5 5 Tip Port 5 37 Ring Port 6 6 Tip Port 6 38 Ring Port 7 7 Tip Port 7 39 Ring Port 8 8 Tip Port 8 40 Ring Port 9 9 Tip Port 9 41 Ring Port 10 10 Tip Port 10 42 Ring Port 11 11 Tip Port 11 43 Ring Port 12 12 Tip Port 12 44 Ring Port 13 13 Tip Port 13 45 Ring Port 14 14 Tip Port 14 46 Ring Port 15 15 Tip Port 15 47 Ring Port 16 16 Tip Port 16 48 Ring Port 17 17 Tip Port 17 49 Ring Port 18 18 Tip Port 18 50 Ring Port 19 19 Tip Port 19 51 Ring Port 20 20 Tip Port 20 52 Ring Port 21 21 Tip Port 21 53 Ring Port 22 22 Tip Port 22 54 Ring Port 23 23 Tip Port 23 55 Ring Port 24 24 Tip Port 24 56 Ring Port 25 25 Tip Port 25 57 Ring Port 26 26 Tip Port 26 58 Ring Port 27 27 Tip Port 27 59 Ring Port 28 28 Tip Port 28 60 Unused 29 Unused 61 Unused 30 Unused 62 Unused 31 Unused 63 Unused 32 Unused 64 Table 2-2 Champ Connector Pin Assignments—Side-A EIA, Connectors J8 and J9; Side-B EIA, Connectors J21 and J22 (continued) Signal Pin Signal Pin2-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.4 DS-1 Cable Installation Table 2-4 lists the Champ connector pin assignments and the corresponding EIA mapping for connectors J12 and J13 on the A-side EIA, and connectors J25 and J26 on the B-side EIA. Table 2-3 Champ Connector Pin Assignments—Side-A EIA, Connectors J10 and J11; Side-B EIA, Connectors J23 and J24 Signal Pin Signal Pin Ring Port 29 1 Tip Port 29 33 Ring Port 30 2 Tip Port 30 34 Ring Port 31 3 Tip Port 31 35 Ring Port 32 4 Tip Port 32 36 Ring Port 33 5 Tip Port 33 37 Ring Port 34 6 Tip Port 34 38 Ring Port 35 7 Tip Port 35 39 Ring Port 36 8 Tip Port 36 40 Ring Port 37 9 Tip Port 37 41 Ring Port 38 10 Tip Port 38 42 Ring Port 39 11 Tip Port 39 43 Ring Port 40 12 Tip Port 40 44 Ring Port 41 13 Tip Port 41 45 Ring Port 42 14 Tip Port 42 46 Ring Port 43 15 Tip Port 43 47 Ring Port 44 16 Tip Port 44 48 Ring Port 45 17 Tip Port 45 49 Ring Port 46 18 Tip Port 46 50 Ring Port 47 19 Tip Port 47 51 Ring Port 48 20 Tip Port 48 52 Ring Port 49 21 Tip Port 49 53 Ring Port 50 22 Tip Port 50 54 Ring Port 51 23 Tip Port 51 55 Ring Port 52 24 Tip Port 52 56 Ring Port 53 25 Tip Port 53 57 Ring Port 54 26 Tip Port 54 58 Ring Port 55 27 Tip Port 55 59 Ring Port 56 28 Tip Port 56 60 Unused 29 Unused 61 Unused 30 Unused 62 Unused 31 Unused 63 Unused 32 Unused 642-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.4 DS-1 Cable Installation Table 2-4 Champ Connector Pin Assignments—Side-A EIA, Connectors J12 and J13; Side-B EIA, Connectors J25 and J26 Signal Pin Signal Pin Ring Port 57 1 Tip Port 57 33 Ring Port 58 2 Tip Port 58 34 Ring Port 59 3 Tip Port 59 35 Ring Port 60 4 Tip Port 60 36 Ring Port 61 5 Tip Port 61 37 Ring Port 62 6 Tip Port 62 38 Ring Port 63 7 Tip Port 63 39 Ring Port 64 8 Tip Port 64 40 Ring Port 65 9 Tip Port 65 41 Ring Port 66 10 Tip Port 66 42 Ring Port 67 11 Tip Port 67 43 Ring Port 68 12 Tip Port 68 44 Ring Port 69 13 Tip Port 69 45 Ring Port 70 14 Tip Port 70 46 Ring Port 71 15 Tip Port 71 47 Ring Port 72 16 Tip Port 72 48 Ring Port 73 17 Tip Port 73 49 Ring Port 74 18 Tip Port 74 50 Ring Port 75 19 Tip Port 75 51 Ring Port 76 20 Tip Port 76 52 Ring Port 77 21 Tip Port 77 53 Ring Port 78 22 Tip Port 78 54 Ring Port 79 23 Tip Port 79 55 Ring Port 80 24 Tip Port 80 56 Ring Port 81 25 Tip Port 81 57 Ring Port 82 26 Tip Port 82 58 Ring Port 83 27 Tip Port 83 59 Ring Port 84 28 Tip Port 84 60 Unused 29 Unused 61 Unused 30 Unused 62 Unused 31 Unused 63 Unused 32 Unused 642-17 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.5 Alarm Cable Installation 2.6.5 Alarm Cable Installation The alarm cables attach to the rear of the ONS 15310-MA at the ALARM In and ALARM Out ports. The other ends of the cables plug into the alarm-collection equipment. Terminate the ends of these cables according to local site practice. The pins on the ALARM In and ALARM Out ports correspond to the 32 external alarm inputs and the 8 external alarm outputs (controls) that you can define using Cisco Transport Controller (CTC). Table 2-5 shows the default input alarm pinouts and the corresponding alarm numbers assigned to each port. Refer to this table when connecting alarm cables to the ONS 15310-MA. Table 2-6 shows the default output alarm pinouts and the corresponding alarm numbers assigned to each port. Refer to this table when connecting alarm cables to the ONS 15310-MA. Table 2-5 Default Alarm Pin Assignments—Inputs DB-37 Pin Number Function DB-37 Pin Number Function 1 Alarm 1 20 Alarm 18 2 Alarm 2 21 Alarm 19 3 Alarm 3 22 Alarm 20 4 Alarm 4 23 Alarm 21 5 Alarm 5 24 Alarm 22 6 Alarm 6 25 Alarm 23 7 Alarm 7 26 Alarm 24 8 Alarm 8 27 Common 17–24 9 Common 1–8 28 Alarm 25 10 Alarm 9 29 Alarm 26 11 Alarm 10 30 Alarm 27 12 Alarm 11 31 Alarm 28 13 Alarm 12 32 Alarm 29 14 Alarm 13 33 Alarm 30 15 Alarm 14 34 Alarm 31 16 Alarm 15 35 Alarm 32 17 Alarm 16 36 Common 25–32 18 Common 9–16 37 N/C 19 Alarm 17 — — Table 2-6 Default Alarm Pin Assignments—Outputs DB-25 Pin Number Function DB-25 Pin Number Function 1 Out 1+ 14 Out 2+ 2 Out 1– 15 Out 2– 3 — 16 Out 3+ 4 — 17 Out 3–2-18 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.6 BITS Cable Installation For more information about external alarms and controls, see the “11.6 External Alarms and Controls” section on page 11-14. 2.6.6 BITS Cable Installation The BITS clock cable (terminated with a DB-9 connector) attaches to the BITS port on the ONS 15310-MA. The other end of the cable plugs into the BITS clock. Terminate this end of the cable according to local site practice. The 15310-MA has one BITS input and one BITS output. The BITS inputs and outputs have corresponding pins on the DB-9 BITS ports. When connecting BITS cable to the ONS 15310-MA, see Table 2-7 for the BITS cable pin assignments. For more information about connecting BITS timing to the ONS 15310-MA, refer to Chapter 7, “Timing.” 5 — 18 Out 4+ 6 — 19 Out 4– 7 — 20 Out 5+ 8 — 21 Out 5– 9 — 22 Out 6+ 10 — 23 Out 6– 11 — 24 Out 7+ 12 Out 8+ 25 Out 7– 13 Out 8– — — Table 2-6 Default Alarm Pin Assignments—Outputs (continued) DB-25 Pin Number Function DB-25 Pin Number Function Table 2-7 BITS Cable Pin Assignments DB-9 Pin Number Function 1 BITS Output+ 2 BITS Output– 3 — 4 — 5 — 6 BITS Input+ 7 BITS Input– 8 — 9 —2-19 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.6.7 UDC Cable Installation Note Refer to Telcordia SR-NWT-002224 for rules about how to provision timing references. 2.6.7 UDC Cable Installation The 64K, EIA/TIA-232 user data channel (UDC) interface provides F1 and F2 byte input and output. When connecting the UDC cable to the ONS 15310-MA, see Table 2-8 for the UDC cable pin assignments. Unshielded twisted-pair #22 or #24 AWG wire is required for the UDC ports. 2.7 Cable Routing and Management Two types of cable management brackets are available for the ONS 15310-MA shelf assembly: the standard bracket, which ships with the ONS 15310-MA ship kit, and the extended bracket, which ships as a separate orderable part. You can install either bracket under the shelf assembly. 2.7.1 Standard Cable Management Bracket The standard cable management bracket has one area in the rear that can be used for routing cables. Fiber-optic cable can be routed through the rear trough of the bracket. Ethernet cables can be passed through the front of the bracket to be bundled and secured using tie-wraps or other site-specific materials. Figure 2-10 shows the installation of the standard cable management bracket. Table 2-8 UDC Cable Pin Assignments RJ-45 Pin Number RS-232/64K Mode 1 TX + 2 TX – 3 RX + 4 — 5 — 6 RX – 7 — 8 —2-20 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.7.2 Extended Cable Management Bracket Figure 2-10 Installing the Standard Cable Management Bracket 2.7.2 Extended Cable Management Bracket The extended cable management bracket has two areas that can be used for routing cables, one in the front and one in the rear. Fiber-optic cables can be routed through the smaller front trough, and Ethernet cables can be routed through the larger rear trough. 1515772-21 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.8 Fan-Tray Assembly Figure 2-11 shows the installation of the extended cable management bracket. Figure 2-11 Installing the Extended Cable Management Bracket 2.8 Fan-Tray Assembly The fan-tray assembly is located at the top of the ONS 15310-MA shelf assembly, under the air filter, rear exhaust, and air inlet. The fan tray is a removable drawer that holds four fans and the fan-control circuitry for the ONS 15310-MA. After you install the fan tray, you should only need to access it if a fan failure occurs. 1515782-22 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.8.1 Fan Speed and Power Requirements The front of the fan-tray assembly has CRIT, MAJ, and MIN alarm LEDs that illuminate if a Critical, Major, or Minor alarm is present anywhere on the ONS 15310-MA assembly. 2.8.1 Fan Speed and Power Requirements Fan speed is controlled by temperature sensors on the CTX2500 card. The sensors measure the input air temperature at the fan-tray assembly. Fan speed options are low, medium, and high. 2.8.2 Fan Failure If one or more fans fail on the fan-tray assembly, replace the entire assembly. You cannot replace individual fans. The red Fan Fail LED on the front of the fan tray illuminates when one or more fans fail. For fan-tray replacement instructions, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. The red Fan Fail LED is unlit after you install a working fan tray. 2.8.3 Air Filter The ONS 15310-MA contains a reusable air filter (15310-MA-FTF) that is installed above the fan-tray assembly. The reusable filter is made of a gray, open-cell, polyurethane foam that is specially coated to provide fire and fungi resistance. Spare filters should be kept in stock. Caution Do not operate an ONS 15310-MA without the mandatory fan-tray air filter. 2.9 Cards and Slots Caution Always use the supplied ESD wristband when working with a powered ONS 15310-MA. Plug the wristband cable into either ESD jack, located on the far left and right slots of the shelf assembly. The ONS 15310-MA has six card slots. Slots 3 and 4 are dedicated to the common-control (CTX2500) cards. Slots 1, 2, 5, and 6 can accommodate the following traffic cards: • Ethernet: CE-100T-8 card, ML-100T-8 card • Electrical: DS1-28/DS3-EC1-3 card, DS1-84/DS3-EC1-3 card These cards have plugs at the rear of the card. When the ejectors are fully closed, the card plugs into the assembly backplane. When no card is installed in a card slot, a filler card should be installed. Use a CTX2500 filler card in empty CTX2500 slots (Slots 3 and 4), and an expansion filler card in empty traffic card slots (Slots 1, 2, 5, and 6). Refer to Chapter 3, “Card Reference” for more information about ONS 15310-MA cards.2-23 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.9 Cards and Slots Figure 2-12 shows card installation for the ONS 15310-MA. Figure 2-12 Installing a Card in an ONS 15310-MA Table 2-9 lists the number of ports, line rates, connector options, and connector locations for ONS 15310-MA electrical, Ethernet, and optical interfaces. 144703 Table 2-9 Port Line Rates, Connector Types, and Locations Interface Ports Line Rate per Port Connector Type Connector Location DS-1 28/84 1.544 Mbps Champ Rear of the 15310-MA shelf assembly DS-3 3 44.736 Mbps BNC Rear of the 15310-MA shelf assembly EC-1 3 51.84 Mbps BNC Rear of the 15310-MA shelf assembly OC-3/OC-12/OC-48 2 155.52 Mbps (STS-3) 622.08 Mbps (STS-12) LC CTX2500 card faceplate Ethernet (CE-100T-8 card)1 1. The CE-100T-8 card with PID 15310-CE-100T-8 is not compatible with the ONS 15310-MA, only the ONS 15310-CL. The 15310-P-CE-100T-8 is compatible with both the ONS 15310-MA and ONS 15310-CL shelf assemblies. 8 10/100 Mbps RJ-45 CE-100T-8 card faceplate Ethernet (ML-100T-8 card)2 2. The ML-100T-8 card with PID 15310-ML-100T-8 is not compatible with the ONS 15310-MA, only the ONS 15310-CL. The 15310-P-ML-100T-8 is compatible with both the ONS 15310-MA and ONS 15310-CL shelf assemblies. 8 10/1000 Mbps RJ-45 ML-100T-8 card faceplate 2-24 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 2 Cisco ONS 15310-MA Shelf Assembly Hardware 2.9 Cards and SlotsCHAPTER 3-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 3 Card Reference This chapter describes the Cisco ONS 15310-CL and Cisco ONS 15310-MA cards. It includes descriptions and block diagrams for each card. For specifications, see Appendix A, “Specifications.”For card installation and turn-up procedures, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 3.1 Card Summary and Compatibility, page 3-1 • 3.2 15310-CL-CTX Card, page 3-5 • 3.3 CTX2500 Card, page 3-8 • 3.4 CE-100T-8 Card, page 3-10 • 3.5 ML-100T-8 Card, page 3-14 • 3.6 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards, page 3-18 • 3.7 Filler Cards, page 3-19 • 3.8 SFP Modules, page 3-20 Note The I-Temp symbol is located on the faceplate of an I-Temp compliant card. A card without this symbol is C-Temp compliant. 3.1 Card Summary and Compatibility The Cisco ONS 15310-CL uses a common-control card (the 15310-CL-CTX), an interconnect card, a connector expansion card, and a traffic expansion card (either the CE-100T-8 or ML-100T-8 Ethernet card). The 15310-CL-CTX card provides optical and electrical connections for the ONS 15310-CL. The Cisco ONS 15310-MA uses a common-control card (the CTX2500) and a combination of Ethernet cards (CE-100T-8 and ML-100T-8) and electrical cards (DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3). The CTX2500 card provides optical connections for the ONS 15310-MA. This section provides a card summary. Figure 3-1 shows the ONS 15310-CL with an expansion card being inserted. 3-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.1 Card Summary and Compatibility Figure 3-1 ONS 15310-CL with Expansion Card Being Inserted Figure 3-2 shows the ONS 15310-MA fully populated with cards. Expansion Card 15310_CTX-CL Card 131593 Front Panel3-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.1.1 Card Summary Figure 3-2 ONS 15310-MA with Cards Installed 3.1.1 Card Summary Table 3-1 ONS 15310-CL and ONS 15310-MA Cards and Descriptions Card Compatible Platform(s) Description For Additional Information... 15310-CL-CTX CL only The 15310-CL-CTX card serves as the common control and central switching element for the ONS 15310-CL. See the “3.2 15310-CL-CTX Card” section on page 3-5. CTX2500 MA only The CTX2500 card serves as the common control and central switching element for the ONS 15310-MA. See the “3.3 CTX2500 Card” section on page 3-8. CE-100T-8 MA and CL The CE-100T-8 card provides eight RJ-45 10/100-Mbps Ethernet ports. See the “3.4 CE-100T-8 Card” section on page 3-10. ML-100T-8 MA and CL The ML-100T-8 Ethernet card provides eight ports of 10/100 Ethernet-encapsulated traffic into SONET/SDH STS-3/STM-1 payloads. See the “3.5 ML-100T-8 Card” section on page 3-14. 1446893-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.1.2 Card Compatibility 3.1.2 Card Compatibility Table 3-2 lists CTC software release compatibility for each ONS 15310-CL and ONS 15310-MA card. In the table, “Yes” means that the card is compatible with the listed software release. . DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 MA only The DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards provide 28 and 84 Telcordia-compliant DS-1 ports, respectively, as well as three DS-3/EC-1 ports. See the “3.6 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards” section on page 3-18. Filler Card (Traffic Slot) MA and CL The FILLER card is used to fill unused traffic card slots in the ONS 15310-CL and ONS 15310-MA shelves. The Cisco Transport Controller (CTC) graphical user interface (GUI) detects the filler card. See the “3.7 Filler Cards” section on page 3-19. Filler Card (CTX2500 Slot) MA only The CTX FILLER card is used to fill unused CTX2500 card slots in the ONS 15310-MA shelf. CTC detects the filler card. See the “3.7 Filler Cards” section on page 3-19. SFP Modules MA and CL Small Form-factor Pluggables (SFPs) are integrated fiber-optic transceivers that provide high-speed serial links from a port or slot to the network. See the “3.8 SFP Modules” section on page 3-20 Table 3-1 ONS 15310-CL and ONS 15310-MA Cards and Descriptions (continued) Card Compatible Platform(s) Description For Additional Information... Table 3-2 ONS 15310-CL and ONS 15310-MA Software Release Compatibility Per Card Card R5.0 R6.0 R7.0 15310-CL-CTX (ONS 15310-CL Only) Yes Yes Yes CTX2500 (ONS 15310-MA Only) No No Yes CE-100T-8 Card1 1. The CE-100T-8 card with product ID (PID) 15310-CE-100T-8 is not compatible with the ONS 15310-MA. 15310-P-CE-100T-8 is compatible with both the ONS 15310-MA and ONS 15310-CL shelf assemblies. Yes Yes Yes ML-100T-8 Card2 2. The ML-100T-8 card with PID 15310-ML-100T-8 is not compatible with the ONS 15310-MA shelf assembly. 15310-P-ML-100T-8 is compatible with both the ONS 15310-MA and ONS 15310-CL shelf assemblies. Yes Yes Yes DS1-28/DS3-3 (ONS 15310-MA Only) No No Yes DS1-84/DS3-3 (ONS 15310-MA Only) No No Yes FILLER Card Yes Yes Yes CTX FILLER Card (ONS 15310-MA Only) No No Yes3-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.2 15310-CL-CTX Card 3.2 15310-CL-CTX Card This section describes the features and functions of the ONS 15310-CL Common Control, Timing, Cross-Connect Customer-Located (15310-CL-CTX) card. The 15310-CL-CTX card is an internal, nonremovable card residing in the ONS 15310-CL platform. It operates in a nonredundant configuration and performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET data communications channel (DCC) termination, system fault detection, and cross-connect maintenance and management for the ONS 15310-CL. The card also provides the circuitry for the DS-1, DS-3/EC-1, and OC-3/OC-12 interfaces and ensures that the system maintains timing with SMC stability. The 15310-CL-CTX card connects to an expansion card (CE-100T-8 or ML-100T-8) through a mechanical interconnect card within the ONS 15310-CL chassis that is similar to a backplane in appearance. The ONS 15310-CL provides a front chassis opening that accepts either a filler card, a CE-100T-8 plug-in card, or an ML-100T-8 plug-in card. When a card is plugged in, it connects to the 15310-CL-CTX card through the interconnect card. The 15310-CL-CTX has three sets of ports: • Wideband electrical (WBE) ports • Broadband electrical (BBE) ports • Optical pluggable port module (PPM) ports; PPM is the graphical user interface term for SFPs See the “3.2.6 Electrical Interface (BBE and WBE)” section on page 3-8 and the “3.2.4 15310-CL-CTX Optical Interfaces” section on page 3-7 for more information. The 15310-CL-CTX card does not have a faceplate because it is located inside the chassis; however, the 15310-CL-CTX LED indicators and connectors are located on the ONS 15310-CL front panel (Figure 3-3). Figure 3-3 ONS 15310-CL Front Panel FAIL ALARM PWR SYNC EXPANSION LAMP TEST SYSTEM RESET Tx Rx 1 LAN BITS CRAFT ALARM UDC DS1 (1-21) Tx Rx 2 Tx Rx 1 100-240V~ 50-60Hz 2A DS3/ EC1 Tx Rx 2 DS3/ EC1 Tx Rx 3 DS3/ EC1 CLASS 1 LASER CLEI BARCODE 1246463-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.2.1 Features Figure 3-4 shows a functional block diagram of the 15310-CL-CTX card. Figure 3-4 15310-CL-CTX Block Diagram 3.2.1 Features The 15310-CL-CTX card has the following features: • Support for a maximum of 21 bidirectional DS-1 and three DS-3/EC-1 ports • Support for two SFP/LC optical interfaces for OC-3/OC-12 • 10/100BaseT LAN interface for CTC software • 57.6-K maximum baud rate EIA/TIA-232 craft interface for Transaction Language One (TL1) • Configurable alarm inputs and outputs (three input alarms and two alarm output contacts) 155M STS-XC LINE / SECTION TERMINATION POINTER PROCESSOR SFP OC3/12 SFP OC3/12 REFERENCE MONITOR + SELECTION MUX 19.44M SYSTEM PLL WITH HOLDOVER TCXO 20ppm CLOCK Line Section Termination VT-XC TU-XC IDE INTERFACE Compact BOOT FLASH Flash Card Memory Processor BITS LIU + FRAMER 1.544M / 2.048M ALARM Input/Contact CRAFT RS232 LAN 10/100M UDC 64K/ RS232 Interface NON-ISOLATED DC-DC CONVERTERS 3.3V 2.5V ETC BITS Cross Connect SONET Traffic STS48 (SXC-9) PDH Mapper T1/E1 LIUs T3/E3/ STS1 LIU 21 T1 3 T3/EC1 ETHERNET Expansion slot Front Panel Interface FAN Controller Overhead Bus 19.44M SYSTEM PLL PDH CLOCKS SONET CLOCKS PDH SUBSYSTEM CLOCK GEN 155M XC PLL USER DATA CHANNEL RS232 FANS CLOCK SUBSYSTEM PROCESSOR COMPLEX Front Panel Interface LEDs POWER SUBSYSTEM Expansion Port Timing Subsystem 1246503-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.2.2 Synchronization and Timing • One building integrated timing supply (BITS) input and one BITS output • User data channel (UDC) connector for synchronous 64-Kbps or asynchronous EIA/TIA-232 communication • Free-running SMC clock accurate to 20 ppm • Timing reference to external BITS, optical links, or DS-1/EC-1 ports • Retime any DS-1/EC-1 port, or use the ports as a timing source • Nonblocking high-order STS1 cross-connect • STS-48 worth of low-order cross-connect • STS-24 worth of low-order VT1.5 cross-connect 3.2.2 Synchronization and Timing This synchronization and timing subsystem is responsible for monitoring and selecting reference clocks in the node. A free-running SMC clock, accurate to 20 ppm, is available for internal synchronization in the event that no synchronization timing source is available. The 15310-CL-CTX card is normally synchronized from the optical link. 3.2.3 System Cross-Connect This subsystem is responsible for the set up and maintenance of cross-connections within the system. It supports STS-Nc, STS-1, and VT1.5 cross-connect capability in SONET mode. 3.2.4 15310-CL-CTX Optical Interfaces The optical subsystem provides two SFP optical transceivers for two OC-3/OC-12 SONET-compliant interfaces. SFPs attach to the ONS 15310-CL front panel via two SFP (PPM) slots. Each slot can contain a single-rate (OC-3 or OC-12) or multirate (OC-3 and OC-12) PPM. Note PPM is the graphical user interface term for SFPs. Single-rate PPMs are autoprovisioned when they are installed, but multirate PPMs must be provisioned. This behavior can be controlled by NE defaults. To provision, edit, or delete PPM ports, refer to the “Change Port Settings” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. For more information about PPMs, see the “3.8 SFP Modules” section on page 3-20. 3.2.5 Communication and Control This subsystem is responsible for overall control of the system, such as system initialization, provisioning, alarm reporting, maintenance, diagnostics, intercard communication, DCC termination, and system fault detection.3-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.2.6 Electrical Interface (BBE and WBE) 3.2.6 Electrical Interface (BBE and WBE) This subsystem supports Telcordia GR-499 compliant, 1.544-Mbps (DS-1) and 44.736-Mbps (DS-3/EC-1) interfaces. Performance monitoring (PM) is provided by means of this interface to allow validation of signal quality. There are three DS-3 or EC-1 (BBE) ports located on the ONS 15310-CL front panel. BBE ports are automatically provisioned as DS-3 ports via network element (NE) defaults, but can be provisioned as EC-1 ports. See Appendix C, “Network Element Defaults Description” for more information. BBE ports support provisioning, configuration, creation, and deletion via CTC. Any outgoing DS-1 signal can be retimed to eliminate accumulated jitter and wander at the point of egress from a synchronous network. Any incoming DS-1 signal from the transport element can also be used as timing source. There are 21 DS-1 (WBE) ports available at the LFH 96-pin connector on the ONS 15310-CL front panel. WBE ports are automatically provisioned and cannot be deleted or changed. 3.2.7 15310-CL-CTX Card-Level Indicators The 15310-CL-CTX card is responsible for operating the LED indicators on the ONS 15310-CL front panel. The panel has four card-level LEDs, described in Table 3-3. 3.3 CTX2500 Card The CTX2500 card, for use with the ONS 15310-MA, is a fully nonblocking cross-connect card that operates in either a simplex or duplex (redundant) configuration. It performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET DCC termination, system fault detection, and cross-connect maintenance and management for the ONS 15310-MA. The card also provides the circuitry for the OC-3/OC-12/OC-48 interfaces, and ensures that the system maintains timing with SMC stability. Caution If the system loses power or the CTX2500 card is reset, you must reset the ONS 15310-MA clock unless the node has been previously provisioned to use Simple Network Time Protocol (SNTP) to update the clock over the LAN. Table 3-3 15310-CL-CTX 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 15310-CL-CTX card. As part of the boot sequence, the FAIL LED turns on and flashes until the software deems the card operational. ALARM LED (Red/Amber) The ALARM LED is red for Critical and Major alarm conditions. It is amber for Minor alarm conditions. PWR LED (Green/Amber) The PWR LED is green if AC power is connected and operating or if both DC power sources are connected and operating. The LED is amber if only one DC power source is connected and operating. SYNC LED (Green/Amber/Red) The SYNC LED is green if the 15310-CL-CTX card detects both a primary and secondary clock reference. It is amber if the card detects only a single clock reference. The LED is RED if the card detects no clock reference.3-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.3.1 System Cross-Connect Figure 3-5 shows the CTX2500 card faceplate and block diagram. Figure 3-5 CTX2500 Faceplate and Block Diagram 3.3.1 System Cross-Connect The CTX2500 card provides 576 x 576 STS-1 level cross-connections and 2688 x 2688 VT1.5s. 3.3.2 CTX2500 Card Side Switches The CTX2500 supports errorless side switches (less than a 50-ms impact to any traffic) when the switch is initiated through software, through either a soft-reset or a software upgrade where there is no FPGA or firmware upgrade. A side switch means switching from a CTX2500 on one side of the shelf to the redundant CTX2500 on the other side of the shelf. 145768 ASIC I2C LED RJ45 FP CRAFT RJ45 FP ENET Backplane Connectors STS1 XC TU XC VT XC OCN I/F TIMING MOD SCL I/F ATA I/F CPU I/F Front Panel PLL VXCO OCXO LIU FPGA CPLD ENWT SW DC/DC XPT SW XPT SW SFP1 SFP1 XPT and SFP Control/Status From Nile2 CPLD Compact FLASH FLASH DDR SDRAM FPGA BUS FANOUT PROCESSOR TEMP SFP1/2 IDPROM REFCLK_IN REFCLK_OUT3-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.3.3 CTX2500 Optical Interfaces 3.3.3 CTX2500 Optical Interfaces There are two PPM (SFP) slots on the CTX2500 faceplate to provide optical interfaces. (PPM is the graphical user interface term for SFP.) Each slot can contain a one-port PPM. Cisco-qualified PPMs can be single-rate (OC-3, OC-12, or OC-48) or multirate (OC-3/OC-12). Single-rate PPMs are autoprovisioned when they are installed, but multirate PPMs must be provisioned. This behavior can be controlled by NE defaults. Note To provision, edit, or delete PPM ports, refer to the “Change Port Settings” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. For more information about PPM/SFP hardware, see the “3.8 SFP Modules” section on page 3-20. 3.3.4 CTX2500 Card-Level Indicators The CTX2500 card has four card-level LEDs, described in Table 3-3. 3.3.5 CTX2500 Port-Level Indicators Two bicolor LEDs show the status per port (Ports 1 and 2). The port LED is green if the port is available to carry traffic and is provisioned as in-service. The port LED is red if there is a signal failure or loss of signal on the port. 3.4 CE-100T-8 Card This section describes the features and functions of the Layer 1 Ethernet card, the CE-100T-8. This card is compatible with both the ONS 15310-CL and the ONS 15310-MA. Note The CE-100T-8 card with PID 15310-CE-100T-8 is not compatible with the ONS 15310-MA. The 15310-P-CE-100T-8 is compatible with both the ONS 15310-MA and ONS 15310-CL shelf assemblies. If you install a 15310-CE-100T-8 in an ONS 15310-MA shelf assembly, you will receive a mismatched equipment alarm (MEA). You can view the PID under the node view Inventory tab in CTC. Table 3-4 CTX2500 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 turns on and flashes until the software deems the card operational. ACT/STBY LED (Green/Amber) The ACT/STBY LED is green if the card is the active CTX2500 card. It is amber if the card is the standby card. SYNC LED (Green/Amber) The SYNC LED is green if the CTX2500 card detects both a primary and secondary clock reference. It is amber if the card detects only a single clock reference. 3-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.4 CE-100T-8 Card The CE-100T-8 card maps 8-port 10/100-Mbps Ethernet-encapsulated traffic into SONET payloads, making use of low-order (VT1.5) virtual concatenation (VCAT), high-order (STS-1, STS-3c) VCAT, generic framing procedure (GFP), and Point-to-Point Protocol/high-level data link control (PPP/HDLC) framing protocols. It also supports the link capacity adjustment scheme (LCAS), which allows hitless dynamic adjustment of SONET link bandwidth. The CE-100T-8 card provides eight RJ-45 10/100-Mbps Ethernet ports on the faceplate of the card. An inactive RJ-11 console port is also on the faceplate. The circuit types supported are: • STS-1 and STS-3c CCAT • STS-1-Nv VCAT (N = 1–3) • STS-1-Nv LCAS (N = 1–3) • STS-1-2v software LCAS (SW-LCAS) (compatible with ML-Series cards only) • VT1.5-Nv VCAT (N = 1–64) • VT1.5-Nv LCAS (N = 1–64) Each 10/100 Ethernet port can be mapped to a SONET channel in increments of VT1.5 or STS-1 granularity. There are eight backend packet-over-SONET (POS) ports (VCAT groups [VCGs]) available on the ML-100T-8 card. Additionally, the CE-100T-8 card supports packet processing, classification, quality of service (QoS)-based queuing, and traffic scheduling.3-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.4 CE-100T-8 Card Figure 3-6 shows the CE-100T-8 card faceplate and block diagram. Figure 3-6 CE-100T-8 Faceplate and Block Diagram The following paragraphs describe the general functions of the CE-100T-8 card and relate it to the block diagram in Figure 3-6. In the ingress direction (Ethernet-to-SONET), an octal PHY, which performs all of the physical layer interface functions for 10/100-Mbps Ethernet, sends the frame to the packet processor for queuing in the respective packet buffer memory. The packet processor performs packet processing, packet switching, and classification. The Ethernet frames are then passed over SMII channels to the POS mappers, where Ethernet traffic is terminated and is encapsulated using the PPP/HDLC or GFP framing protocols. The encapsulation method is selected on a per-port basis. The encapsulated Ethernet frames are then mapped into a configurable number of VCAT low-order and high-order payloads, such as VT1.5 synchronous payload envelope (SPE), STS-1 SPE, or a contiguous concatenated (CCAT) payload such as STS-3c SPE. Up to 64 VT1.5 SPEs or three STS-1 SPEs can be virtually concatenated. The SPE from each POS mapper (up to STS-3) carrying encapsulated Ethernet frames are passed onto the multiplexer/demultiplexer (mux/demux) next, where the STS-3 frames from both POS mappers are multiplexed to form an STS-12 frame for transport over the SONET network by means of the Bridging Transmission Convergence (BTC-48) application-specific integrated circuit (ASIC). CE-100T-8 Console ACTIVE FAIL LINK 1 ACT LINK 2 ACT LINK 3 ACT LINK 4 ACT LINK 5 ACT LINK 7 ACT LINK 6 ACT LINK 8 ACT Packet Processor (QoS and Queuing) SMII SMII 8 x RJ45 8 STS12 STS-3 STS-3 BTC48 Octal 8 PHY POS Mapper and VCAT/ LCAS Engine POS Mapper and VCAT/ LCAS Engine Mux/ Demux B a c k p l a n e 8 SMII 7 SMII SMII to MII Adapter MII Intercard Ethernet Links PHY CPU Complex 1345903-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.4.1 CE-100T-8 Card-Level Indicators Note Although the STS-3 frames are multiplexed into an STS-12 frame, the frame carries at most an STS-6 payload, leaving half of the STS-12 bandwidth free. In the egress direction (SONET-to-Ethernet), the mux/demux extracts the first and second STS-3 SPEs from the STS-12 frame it receives from the BTC-48 before sending them to the POS mappers. The STS-3 SONET SPE carrying GFP or PPP/HDLC encapsulated Ethernet frames are then extracted and buffered in the external memory of the POS mappers. This memory is used for providing alignment and differential delay compensation for the received low/high order virtual concatenated payloads. When alignment and delay compensation are complete, the Ethernet frames are decapsulated with one of the framing protocols (GFP or PPP/HDLC). Decapsulated Ethernet frames are then passed onto the packet processor for QoS queuing and traffic scheduling. The network processor switches the frame to one of the corresponding PHY channels and then onto the Ethernet port for transmission to the external clients. With regard to QoS, the VLAN class-of-service (CoS) threshold (value 0 to 7, default 7) and the IP type-of-service (ToS) threshold (value 0 to 255, default 255) on incoming Ethernet packets are both available for priority queuing. These thresholds are provisionable through CTC, TL1, and Cisco Transport Manager (CTM). CoS takes precedence over ToS unless the CoS threshold is set to the default of 7. This threshold value does not prioritize any packets based on CoS, so ToS is used. The value configured is a threshold and any value greater than that value is set as a priority. For example, if a CoS of 5 is set as the threshold, only CoS values of 6 and 7 would be set to priority. 3.4.1 CE-100T-8 Card-Level Indicators The CE-100T-8 card faceplate has two card-level LED indicators, described in Table 3-5. 3.4.2 CE-100T-8 Port-Level Indicators The CE-100T-8 card has two LEDs embedded into each of the eight Ethernet-port RJ-45 connectors. The LEDs are described in Table 3-6. Table 3-5 CE-100T-8 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 CE-100T-8 card. As part of the boot sequence, the FAIL LED blinks until the software deems the card operational, then it turns off. ACT LED (Green) The ACT LED provides the operational status of the CE-100T-8. When the ACT LED is green, it indicates that the CE-100T-8 card is active and the software is operational; otherwise, it is off.3-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.5 ML-100T-8 Card 3.5 ML-100T-8 Card This section describes the features and functions of the Layer 2 10/100 Ethernet card, the ML-100T-8. The card is compatible with both the ONS 15310-CL and the ONS 15310-MA. Note The ML-100T-8 card with PID 15310-ML-100T-8 is not compatible with the ONS 15310-MA. 15310-P-ML-100T-8 is compatible with both the ONS 15310-MA and ONS 15310-CL shelf assemblies. If you install a 15310-ML-100T-8 in an ONS 15310-MA shelf assembly, you will receive a mismatched equipment alarm (MEA). You can view the PID under the node view Inventory tab in CTC. 3.5.1 ML-100T-8 Card Description The ML-100T-8 card maps eight ports of 10/100 Ethernet encapsulated traffic into SONET STS-3 payloads. The card is compatible with high-order STS-1 VCAT and the GFP and PPP/HDLC framing protocols. It also supports LCAS, which allows hitless dynamic adjustment of SONET/SDH link bandwidth. Each 10/100 Ethernet port can be mapped to a SONET channel in increments of STS-1 granularity. The ML-100T-8 card provides a switched operating mode, with eight subscriber interfaces and two virtual POS (VCG) interfaces mapped through the cross-connect for transport with other services between network elements (NEs). The circuit types supported are: • STS-1 • STS-1-Nv VCAT (N=1–2) • STS-1-Nv LCAS (N=1–2) • STS-1-2v SW-LCAS Additionally, the ML-100T-8 card supports packet processing, classification, QoS-based queuing, traffic scheduling, and packet multiplexing services for Layer 2/3. Table 3-6 CE-100T-8 Port-Level Indicators Port-Level Indicators Description ACT LED (Amber) A steady amber LED indicates a link is detected, but there is an issue inhibiting traffic. A blinking amber LED means traffic is flowing. LINK LED (Green) A steady green LED indicates that a link is detected, but there is no traffic. A blinking green LED flashes at a rate proportional to the level of traffic being received and transmitted over the port. Both ACT and LINK LED OFF Unlit green and amber LEDs indicate no traffic.3-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.5.2 ML-Series Cisco IOS CLI Console Port 3.5.2 ML-Series Cisco IOS CLI Console Port The ML-Series card has an RJ-11 serial console port on the card faceplate labeled Console. It enables communication from the serial port of a PC or workstation running terminal emulation software to the Cisco IOS command line interface (CLI) on a specific ML-Series card. Due to space limitations on the ML-Series card faceplate, the console port is an RJ-11 modular jack instead of the more common RJ-45 modular jack. Cisco supplies an RJ-11 to RJ-45 console cable adapter with each ML-Series card. After connecting the adapter, the console port functions like the standard Cisco RJ-45 console port. Figure 3-7 shows the RJ-11-to-RJ-45 console cable adapter. Figure 3-7 Console Cable Adapter 789703-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.5.2 ML-Series Cisco IOS CLI Console Port Figure 3-8 shows the ML-100T-8 card faceplate and block diagram. Figure 3-8 ML-100T-8 Card Faceplate and Block Diagram The following paragraphs describe the general functions of the ML-100T-8 card and relate to the block diagram in Figure 3-8. In the ingress direction (Ethernet-to-SONET), Ethernet frames first enter from a physical Ethernet port to one of the corresponding channels of the octal PHY, which performs all of the physical layer interface functions for 10/100 Ethernet. The PHY sends the Ethernet frame to the packet processor by means of the SMII interfaces for queuing in the respective packet buffer memory. The packet processor performs packet processing, packet switching, and classification. The Ethernet frames are then passed on to the POS mappers through the SMII interfaces. The POS mappers terminate the 10/100-Mbps Ethernet traffic. The Ethernet frames are extracted and buffered in POS mapper external memory. Ethernet frames are encapsulated using one of the framing protocols (PPP/HDLC or GFP), selected on a per-port basis. The encapsulated Ethernet frames are mapped into a configurable number of STS-1 or VCAT high-order payloads (STS-1-1v or STS-1-2v). The SPE from each POS mapper (up to STS-3) carrying encapsulated Ethernet frames are next passed onto the mux/demux, where the STS-3 frames from both POS mappers are multiplexed to form an STS-12 frame for transport over the SONET network by means of the BTC-48 ASIC. 134591 ML-100T-8 Console ACTIVE FAIL LINK 0 ACT LINK 1 ACT LINK 2 ACT LINK 3 ACT LINK 4 ACT LINK 6 ACT LINK 5 ACT LINK 7 ACT Packet Buffer 1.5MB Control Mem 0.5MB nP3400 SMII SMII 8 x RJ45 4 32MB eMDM STS12 STS-3 STS-3 60x Part of eMDM FPGA 1 MII 77MHz 155MHz 19.44MHz FCC3 MPC8270 FCC1 FCC2 MII MII Payload SCL CPLD BTC48 8 6 SMII 8 4 BMC5228 Octal PHY Option 2 SDRAM 8 MB Ethermap #2 SDRAM 8MB Ethermap #1 eMDM FPGA B a c k p l a n e Intercard Ethernet Links INTEL LXT973 PHY Flash 8MB SDRAM 128MB Option 13-17 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.5.3 ML-100T-8 Card-Level Indicators Note Although the STS-3 frames are multiplexed into an STS-12 frame, the frame carries at most an STS-6 payload, leaving half of the STS-12 bandwidth free. In the egress direction (SONET-to-Ethernet), the mux/demux extracts the first and second STS-3 SPEs from the STS-12 frame it receives from the BTC-48 before sending it to the POS mapper. The STS-3 SONET SPEs carrying GFP or PPP/HDLC encapsulated Ethernet frames are then extracted and buffered in the POS mapper external memory. This memory is used for providing alignment and differential delay compensation for the received high-order VCAT payloads. After alignment and delay compensation have been done, the Ethernet frames are decapsulated with one of the framing protocols (GFP or PPP/HDLC). Decapsulated Ethernet frames are then passed onto the network processor for QoS queuing, traffic scheduling, packet switching, and multiplexing. The network processor switches the frame to one of the corresponding PHY channels and then onto the Ethernet port for transmission to the external clients. 3.5.3 ML-100T-8 Card-Level Indicators The ML-100T-8 card faceplate has two card-level LED indicators, described in Table 3-7. 3.5.4 ML-100T-8 Port-Level Indicators The ML-100T-8 card has two LEDs embedded into each of the eight Ethernet port RJ-45 connectors. The LEDs are described in Table 3-8. Table 3-7 ML-100T-8 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 CE-100T-8 card. As part of the boot sequence, the FAIL LED blinks until the software deems the card operational, then it turns off. ACT LED (Green) The ACT LED provides the operational status of the ML-100T-8. When the ACT LED is green, it indicates that the ML-100T-8 card is active and the software is operational; otherwise, it is off. Table 3-8 ML-100T-8 Port-Level Indicators Port-Level Indicators Description ACT LED (Amber) A steady amber LED indicates a link is detected, but there is an issue inhibiting traffic. A blinking amber LED means traffic is flowing. LINK LED (Green) A steady green LED indicates that a link is detected, but there is no traffic. A blinking green LED flashes at a rate proportional to the level of traffic being received and transmitted over the port. Both ACT and LINK LED OFF Unlit LEDs indicate no traffic.3-18 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.6 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards 3.6 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards Note For hardware specifications, see the “A.3.4 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards” section on page A-12. The ONS 15310-MA DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards provide 28 or 84 Telcordia-compliant, GR-499 DS-1 ports per card, respectively, and three DS-3/EC-1 ports. Each DS-1 port operates at 1.544 Mbps. Each DS-3/EC-1 port operates at 44.736 Mbps over a single 75-ohm 728 A or equivalent coaxial span. These cards can operate as a working or protect card in 1:1 protection schemes. In addition, the DS1-28/DS3-EC1-3 card provides retiming, so that any outgoing DS-1 signal can be retimed to eliminate accumulated jitter and wander at the point of egress from a synchronous network. Any incoming DS-1 signal from the transport element can also be used as a timing source. The DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards can be installed in Slots 1, 2, 5, and 6. Card installed in Slots 1 and 2 correspond with the electrical interface assembly (EIA) installed on Side A at the rear of the shelf assembly, and cards in Slots 5 and 6 correspond with the EIA installed on Side B. See the “4.3.1 .1:1 Electrical Card Protection” section on page 4-2 for information about electrical card protection and supported shelf configurations. Figure 3-9 shows the DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 card faceplates and block diagram. Figure 3-9 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Card Faceplates and Block Diagram DS1-28 DS3-EC1-3 DS1-84 DS3-EC1-3 8270 CPU Flash 4Mx16 DDR 16Mx1 6 x2 Address/ Data Buffers ITURI FPGA PSOC Power Supply Monitor Voltages 48V->3.3V Power Sequence 3.3V->1.5V, 1.8V, 2.5V, 2.5V Power Shutdown 2.5V->1.2V, 1.25V Clocks/ PLL T1& T3/EC1 Mapper Octal T1 LIUs x11 Temp Sensor DS3/EC1 XFMR & Relays Headers JTAG PLD Mictorsx4 DIRK FPGA ENET BP DS3/EC1 LIU 144710 FAIL ACT/ STBY DS1 SF DS3 SF FAIL ACT/ STBY DS1 SF DS3 SF3-19 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.6.1 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Card-Level Indicators 3.6.1 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Card-Level Indicators The DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards have three card-level LED indicators (Table 3-9). 3.7 Filler Cards If a card slot is left empty, a filler card must be installed in the slot. The filler card serves three functions: it prevents exposure to hazardous voltages and currents inside the chassis, it eliminates electromagnetic interference (EMI) that might disrupt other equipment, and it directs the flow of cooling air through the chassis. Caution Do not operate the ONS 15310-CL or ONS 15310-MA system unless a card is plugged into each card slot. The blank card is a printed circuit board (PCB) with a blank faceplate and two rear connectors that plug into receptacles at the back of the slot. CTC detects when a filler card is plugged in and displays it in node view. Figure 3-10 shows the filler card faceplate. This card is used in the ONS 15310-CL expansion slot and ONS 15310-MA traffic card slots. Figure 3-10 Filler Card Caution Do not attempt to install the FILLER card in a CTX2500 card slot (Slots 3 and 4) on the 15310-MA shelf assembly. Only a CTX FILLER card should be installed in the CTX2500 slot. Table 3-9 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 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 Green (Active) Amber (Standby) When the ACT/STBY LED is green, the card is operational and ready to carry traffic. When the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber DS1 and DS3 SF LEDs Indicates a signal failure or condition such as LOS or LOF on one or more card ports. 1316693-20 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.8 SFP Modules Figure 3-11 shows the CTX2500 filler card faceplate for the ONS 15310-MA. Figure 3-11 CTX2500 Filler Card Caution Do not attempt to install the CTX FILLER card in a traffic card slot (Slots 1, 2, 5, and 6 in the ONS 15310-MA, and the expansion card slot in the ONS 15310-CL). Only 15310-EXP-FILLER cards should be installed in the traffic card slots. 3.8 SFP Modules This section describes the small-form factor pluggables (SFPs) that can be used with the 15310-CL-CTX and CTX2500 cards to provide optical interfaces. The 15310-CL-CTX card does not have a faceplate because it is located inside the chassis; therefore, the two SFP slots are located on the ONS 15310-CL faceplate, just to the left of the LAN connector (see Figure 3-3 on page 3-5). The SFP slots for the ONS 15310-MA are located at the bottom of the CTX2500 card. Ethernet and electrical cards do not use SFPs. 1457693-21 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.8.1 Compatibility by Card 3.8.1 Compatibility by Card Table 3-10 lists the SFPs compatible with the 15310-CL-CTX and CTX2500 cards. For more information about SFPs, see the “A.4 SFP Specifications” section on page A-15. Caution Only use SFPs certified for use in Cisco Optical Networking Systems (ONSs). The qualified Cisco SFP top assembly numbers (TANs) are provided in Table 3-10. Table 3-10 SFP Card Compatibility Card Compatible SFP (Cisco Product ID) Cisco Top Assembly Number (TAN) 15310-CL-CTX (ONS 15310-CL) and CTX2500 (ONS 15310-MA) ONS-SI-155-L1 ONS-SI-155-L2 ONS-SI-155-I1 ONS-SI-622-L1 ONS-SI-622-L2 ONS-SI-622-I1 10-1957-01 10-1937-01 10-1938-01 10-1958-01 10-1936-01 10-1956-01 CTX2500 (ONS 15310-MA) only ONS-SI-2G-I1 ONS-SI-2G-L1 ONS-SI-2G-S1 ONS-SI-2G-L2 ONS-SE-155-1470 ONS-SE-155-1490 ONS-SE-155-1510 ONS-SE-155-1530 ONS-SE-155-1550 ONS-SE-155-1570 10-1993-01 10-2102-01 10-1992-01 10-1990-01 10-1996-01 10-1998-01 10-1999-01 10-2000-01 10-2001-01 10-2002-01 ONS-SE-155-1590 ONS-SE-155-1610 ONS-SE-622-1470 ONS-SE-622-1490 ONS-SE-622-1510 ONS-SE-622-1530 ONS-SE-622-1550 ONS-SE-622-1570 ONS-SE-622-1590 ONS-SE-622-1610 10-2003-01 10-1997-01 10-2004-01 10-2005-01 10-2006-01 10-2007-01 10-2008-01 10-2009-01 10-2010-01 10-2011-01 ONS-SC-2G-30.3 ONS-SC-2G-31.1 ONS-SC-2G-31.9 ONS-SC-2G-32.6 ONS-SC-2G-34.2 ONS-SC-2G-35.0 ONS-SC-2G-35.8 ONS-SC-2G-36.6 ONS-SC-2G-38.1 ONS-SC-2G-38.9 10-2155-01 10-2156-01 10-2157-01 10-2158-01 10-2159-01 10-2160-01 10-2161-01 10-2162-01 10-2163-01 10-2164-013-22 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.8.2 SFP Description 3.8.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 SFPs. There is no correlation between the type of latch to the model type (such as SX or LX/LH) or technology type (such as Gigabit Ethernet). See the label on the SFP for the technology type and model. One type of latch available is a mylar tab, shown in Figure 3-12. A second type of latch is an actuator/button (Figure 3-13), and a third type is a bail clasp (Figure 3-14). SFP dimensions are: • 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 –5 to 70 degrees C (23 to 158 degrees F) • EXT—Extended operating temperature range –5 to 85 degrees C (23 to 185 degrees F) • IND—Industrial operating temperature range –40 to 85 degrees C (–40 to 85 degrees F) CTX2500 (ONS 15310-MA) only (continued) ONS-SC-2G-39.7 ONS-SC-2G-40.5 ONS-SC-2G-42.1 ONS-SC-2G-42.9 ONS-SC-2G-43.7 ONS-SC-2G-44.5 ONS-SC-2G-46.1 ONS-SC-2G-46.9 ONS-SC-2G-47.7 ONS-SC-2G-48.5 10-2165-01 10-2185-01 10-2166-01 10-2167-01 10-2168-01 10-2169-01 10-2170-01 10-2171-01 10-2172-01 10-2173-01 ONS-SC-2G-50.1 ONS-SC-2G-50.9 ONS-SC-2G-51.7 ONS-SC-2G-52.5 ONS-SC-2G-54.1 ONS-SC-2G-54.9 ONS-SC-2G-55.7 ONS-SC-2G-56.5 ONS-SC-2G-58.1 ONS-SC-2G-58.9 ONS-SC-2G-59.7 ONS-SC-2G-60.6 10-2186-01 10-2174-01 10-2175-01 10-2176-01 10-2177-01 10-2178-01 10-2179-01 10-2180-01 10-2181-01 10-2182-01 10-2183-01 10-2184-01 Table 3-10 SFP Card Compatibility (continued) Card Compatible SFP (Cisco Product ID) Cisco Top Assembly Number (TAN)3-23 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.8.3 PPM Provisioning Figure 3-12 Mylar Tab SFP Figure 3-13 Actuator/Button SFP Figure 3-14 Bail Clasp SFP 3.8.3 PPM Provisioning SFPs are known as pluggable port modules (PPMs) in CTC. PPMs provide OC-3 and OC-12 line rates for the ONS 15310-CL and they provide OC-3, OC-12, and OC-48 line rates for the ONS 15310-MA. See the “3.2.4 15310-CL-CTX Optical Interfaces” section on page 3-7 and the “3.3.3 CTX2500 Optical Interfaces” section on page 3-10 for more information. To provision PPMs, including provisioning or changing the optical line rate, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. 63065 63066 630673-24 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 3 Card Reference 3.8.3 PPM ProvisioningCHAPTER 4-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 4 Card Protection Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration. This chapter describes the card and port protection configurations for the Cisco ONS 15310-CL and Cisco ONS 15310-MA. To provision protection, refer to the “Turn Up a Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 4.1 Overview, page 4-1 • 4.2 ONS 15310-CL Port Protection, page 4-2 • 4.3 ONS 15310-MA Card and Port Protection, page 4-2 • 4.4 Automatic Protection Switching, page 4-5 • 4.5 External Switching Commands, page 4-6 4.1 Overview The Cisco ONS 15310-CL has a single common control card (15310-CTX-CL), so no redundant common-control protection is available. The only card protection available is 1+1 optical protection through the two optical ports. The ONS 15310-CL does not provide electrical interface protection (1:1 and 1:N). The optical ports on the 15310-CTX-CL card are provided through Small Form-factor Pluggables (SFPs), which are referred to as pluggable port modules (PPMs) in Cisco Transport Controller (CTC), the ONS 15310-CL software interface. See the “3.2.4 15310-CL-CTX Optical Interfaces” section on page 3-7 for more information. The Cisco ONS 15310-MA has a pair of common control cards (CTX2500), each with two optical ports, and up to four electrical cards (DS1-28/DS3-EC1-3 or DS1-84/DS3-EC1-3). 1:1 protection groups are supported for like pairs of electrical cards, and 1+1 protection groups can be set up between two optical ports on the same CTX2500 card or between the optical ports on two separate CTX2500 cards. Optimized 1+1 protection can be set up by provisioning optical ports as Synchronous Digital Hierarchy (SDH) ports. Due to the support of a pair of CTX2500 common control cards, the CTX2500 card is also 1:1 protected. The 15310-MA can also function in a single CTX2500 configuration mode. 4-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 4 Card Protection 4.2 ONS 15310-CL Port Protection 4.2 ONS15310-CL Port Protection This section describes the port protection methods for the ONS 15310-CL. 4.2.1 1+1 Optical Port Protection When you set up 1+1 optical protection for the ONS 15310-CL, the working optical port on one ONS 15310-CL node is paired with a working optical port on other ONS 15310-CL nodes in a 1+1 protection group. Similarly, the protect optical port on one ONS 15310-CL node is paired with protect optical ports on other ONS 15310-CL nodes in a 1+1 protection group. The data rate and port type of the protect port must match that of the working port. Because the ONS 15310-CL has only two optical ports, they must always be in the same protection group. The rates of the two ports must be the same, either OC-3 or OC-12. 1+1 span protection can be either revertive or nonrevertive. With nonrevertive 1+1 protection, when a failure occurs and the signal switches from the working port to the protect port, the signal stays switched until it is manually switched back. Revertive 1+1 protection automatically switches the signal back to the working port when the working port comes back online after the wait-to-restore (WTR) time has elapsed. To provision 1+1 protection, refer to the “Turn Up a Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. 4.2.2 Unprotected Ports An unprotected port is not included in a protection scheme; therefore, a port failure or a signal error results in lost data. Because no bandwidth lies in reserve for protection, unprotected schemes maximize the available ONS 15310-CL bandwidth. Unprotected is the default protection type. 4.3 ONS15310-MA Card and Port Protection This section describes the card and port protection methods for the ONS 15310-MA. 4.3.1 .1:1 Electrical Card Protection The ONS 15310-MA chassis accommodates two types of electrical cards, the DS1-28/DS3-EC1-3 andDS1-84/DS3-EC1-3, and one type of common-control card, the CTX2500. Figure 4-1 illustrates one possible chassis configuration, with two CTX2500 cards and two pairs of DS1-84/DS3-EC1-3 cards. The following examples show a few of the several possible ONS 15310-MA chassis configurations: • No electrical cards at all. This is the case if you choose to install Ethernet cards, such as the CE-100T-8 or ML-100T-8, instead of electrical cards. The Ethernet cards cannot be used to form a protection group. • Unprotected electrical cards. This is the case if, instead of a pair of electrical cards in Slots 1 and 2 or 5 and 6, you install only a single electrical card in Slots 1, 2, 5, or 6. A filler card or Ethernet card must be installed in a slot where an input/output (I/O) card is missing.4-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 4 Card Protection 4.3.1 .1:1 Electrical Card Protection • A single CTX2500 card. In this case, a filler card must be installed in a slot where a CTX2500 card is missing. • A mix of electrical cards. A DS1-28/DS3-EC1-3 card can protect an adjacent DS1-28/DS3-EC1-3 card, a DS1-84/DS3-EC1-3 card can protect an adjacent DS1-84/DS3-EC1-3 card, and a DS1-84/DS3-EC1-3 card can protect an adjacent DS1-28/DS3-EC1-3 card. However, a DS1-28/DS3-EC1-3 card cannot protect an adjacent DS1-84/DS3-EC1-3 card. Figure 4-1 ONS 15310-MA Chassis Card Layout The configuration of the backplane connectors creates two sets of paired (adjacent) expansion slots for electrical cards. Slots 1 and 2 are a pair and Slots 5 and 6 are a pair. When two electrical cards are plugged into either of the card-slot pairs, the ONS 15310-MA automatically creates a 1:1 protection group for the two cards, if possible. If a protection group cannot be created (see the rules for protection group creation later in this section), one of the cards will be marked as UNKNOWN with the state as MISMATCH in CTC, because the ONS 15310-MA cannot support two unprotected electrical cards in the 1–2 or 5–6 card slot pairs. The 1:1 automatic protection group is created when the second electrical card in a pair is either plugged in or is preprovisioned. Unprotected is the default state for the first electrical card plugged into (or preprovisioned) in either the Slot 1-to-2 or Slot 5-to-6 card slot pairs. When the second card is plugged in or preprovisioned, the protection group is created, if possible. 1446894-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 4 Card Protection 4.3.2 .1+1 Optical Port Protection When protection groups are created, the following rules must be noted: 1. The protection group will be automatically created if possible. If the node cannot create the protection group automatically, then the second card to be plugged in or preprovisioned will be shown as UNKNOWN with the state as MISMATCH in CTC. 2. If possible, the ONS 15310-MA designates the cards in Slots 1 and 5 as working. If Slot 1 or 5 cannot be working (due to violation of one of the other rules), then Slot 2 or 6 will be the working slot. 3. Cards can protect like cards. In addition, a DS1-84/DS3-EC1-3 card can protect a DS1-28/DS3-EC1-3 card. However, a DS1-28/DS3-EC1-3 card cannot protect a DS1-84/DS3-EC1-3 card. 4. If the first card to be provisioned has existing circuits or is in use as a timing source when the second card is provisioned, then the first card must become the working card and cannot become the protect card. 5. The timing source will not switch to a protect card, when a soft reset is executed on the card that is used as a timing source. 6. Automatic protection groups default to nonrevertive. The protection group can be edited to turn on reversion and set a revert time. The protection group can also be edited to change the protection group name. The following scenario does not result in the creation of a protection group because rules are violated: 1. Plug a DS1-84/DS3-EC1-3 card into Slot 1 and provision a circuit on it. 2. Plug a DS1-28/DS3-EC1-3 card into Slot 2. The DS1-84/DS3-EC1-3 card needs to be the working card, because it has a circuit on it (see Rule 4). However, the DS1-28/DS3-EC1-3 card cannot protect the DS1-84/DS3-EC1-3 card (see Rule 3), so no protection group is formed. The following scenario also does not result in the creation of a protection group because rules are violated: 1. Plug a DS1-28/DS3-EC1-3 card into Slot 1 and enable the retiming option on it. 2. Plug a DS1-84/DS3-EC1-3 card into Slot 2. Because the DS1-84/DS3-EC1-3 card does not support retiming, it cannot become a protection card for the DS1-28/DS3-EC1-3 card, so no protection group is formed. The following scenario results in the creation of a protection group because no rules are violated: 1. Plug a DS1-28/DS3-EC1-3card into Slot 1 and provision a circuit on it. 2. Plug a DS1-84/DS3-EC1-3 card into Slot 2. A protection group is automatically formed, with the DS1-28/DS3-EC1-3 card operating as the working card, and the DS1-84/DS3-EC1-3 card operating as the protection card. Automatic protection groups cannot be created or deleted by users. A protection group is automatically deleted when the protect card is deleted. 4.3.2 .1+1 Optical Port Protection With two CTX2500 cards installed, four optical ports are available (two on each card). A 1+1 protection group can be created between any two pairs of optical ports with matched port rates. 4-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 4 Card Protection 4.3.3 .CTX2500 Card Equipment Protection A protection group can be created using two ports on the same CTX2500 card or between ports on adjacent CTX2500 cards. You can also create a 1+1 protection group on each card for a total of two protection groups. In this case, working and protection ports are provisioned on Slot 3 and working and protection ports are provisioned on Slot 4 (the same card can have both working and protect ports on it). The CTX2500 card supports optimized 1+1 protection groups.Optimized 1+1 protection is mainly used in networks that have linear 1+1 bidirectional protection schemes and it requires that optical ports are provisioned to SDH.Optimized 1+1 is a line-level protection scheme that includes two lines: working and protect. One of the two lines assumes the role of the primary channel, from which traffic is selected, and the other port assumes the role of the secondary channel, which protects the primary channel. Traffic switches from the primary to the secondary channel based on either an external switching command or line conditions. After the line condition or the external switching command that was responsible for a switch clears, the roles of the two sides are reversed. 4.3.3 .CTX2500 Card Equipment Protection The ONS15310MA supports a single and dual CTX2500 card configuration. In the dual configuration, with two CTX2500 cards inserted in slot 3 and slot4, the CTX2500 card is also protected. One of the cards becomes the active card and the other becomes the standby card. Soft resets executed in the dual CTX2500 card configuration as well as in the single CTX2500 card configuration are errorless. Software upgrades in the single and dual configurations are also errorless. In the dual configuration, there is a switchover from active CTX2500 card to standby CTX2500 card during the soft reset of the active CTX2500 card. After the soft reset or software upgrade, the old standby CTX2500 card becomes the new active CTX2500 card. The old active CTX2500 card becomes the standby CTX2500 card. The CTX2500 card is equipment protected in a dual CTX2500 card configuration. Any reset occurring on the active CTX2500 card that is triggered due to a watchdog failure or an equipment failure causes a switchover of the CTX2500 card, causing the old standby card to become the active card. If there are any path protection or 1+1 protected ports configured with the protection ports across the two CTX2500 cards, there will be a protection switch such that the port on the new active CTX2500 card becomes the active port for 1+1 or the selector through that port will be the active selector for path protection. Note • Any unprotected port on the old CTX2500 card that is reset may undergo a traffic loss when the CTX2500 comes back up. • If protection exists between two optical ports on the same CTX2500 card and if the CTX2500 card goes through a reset, the traffic may be affected when the CTX2500 card comes back up. The two items above do not apply for a user-initiated soft reset or software upgrade. These resets are errorless 4.4 Automatic Protection Switching Unidirectional switching allows traffic on the transmit and receive optical fibers to switch independently. 4-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 4 Card Protection 4.5 External Switching Commands With nonrevertive 1+1 protection, automatic protection switching (APS) switches a signal after a failure from the working port to the protect port and the signal stays switched to the protect port until it is manually switched back. Revertive switching automatically switches the signal back to the working port when the working port comes back online. 1+1 protection is unidirectional and nonrevertive by default; revertive switching is easily provisioned using CTC. Traffic over a 1+1 APS link is errorless during a soft reboot or a software upgrade for ONS 15310-CL nodes regardless of whether the 1+1 APS protection is active. 4.5 External Switching Commands The external switching commands on the ONS 15310-CL and ONS 15310-MA are Manual, Force, and Lock Out. A Manual switch will switch traffic if the path has an error rate less than the signal degrade (SD). A Force switch will switch traffic even if the path has SD or signal fail (SF) conditions. A Force switch has a higher priority than a Manual switch. In 1+1 mode, however, if there is an SF condition on the protect line, the SF condition has a higher priority than Force, and Force cannot override the SF condition to make a switch to the protect line. Lockouts can only be applied to a protect port (in 1+1 configurations) and prevent traffic from switching to the protect port under any circumstance. 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 5-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 5 Cisco Transport Controller Operation This chapter describes Cisco Transport Controller (CTC), the Cisco ONS 15310-CL and Cisco ONS 15310-MA software interface. For CTC set up and login information, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 5.1 CTC Software Delivery Methods, page 5-1 • 5.2 CTC Installation Overview, page 5-3 • 5.3 PC and UNIX Workstation Requirements, page 5-3 • 5.4 ONS 15310-CL and ONS 15310-MA Connection, page 5-5 • 5.5 CTC Window, page 5-6 • 5.6 Common Control Card Reset, page 5-14 • 5.7 Traffic Card Reset, page 5-14 • 5.8 Database Backup, page 5-14 • 5.9 Software Revert, page 5-15 5.1 CTC Software Delivery Methods ONS 15310-CL and ONS 15310-MA provisioning and administration is performed using CTC software. CTC is a Java application that is stored on the 15310-CL-CTX card in the ONS 15310-CL or on the CTX2500 card in the ONS 15310-MA. CTC is downloaded to your workstation the first time you log into a ONS 15310-CL or ONS 15310-MA with a new software release. 5.1.1 CTC Software Installed on the 15310-CL-CTX or CTX2500 Card CTC software is preloaded on the 15310-CL-CTX and CTX2500 cards; therefore, you do not need to install software. You can view the software versions that are installed on an ONS 15310-CL or ONS 15310-MA by selecting the Maintenance > Software tabs in node view (Figure 5-1). Select the tabs in network view to view the software versions installed on all the network nodes. 5-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.1.2 CTC Software Installed on the PC or UNIX Workstation Figure 5-1 CTC Software Versions in an ONS 15310-CL (Node View) 5.1.2 CTC Software Installed on the PC or UNIX Workstation CTC software Java Archive (JAR) files are installed on your computer using one of the following methods: • The JAR files are downloaded from the 15310-CL-CTX card or CTX2500 card and installed on your computer automatically the first time you connect to an ONS 15310-CL or ONS 15310-MA. Downloading the CTC software files at login ensures that your computer has the same CTC software version as the ONS 15310-CL or ONS 15310-MA you are accessing. The CTC JAR files are stored in the temporary directory designated by your computer operating system. You can use the Delete CTC Cache button to remove files. If the files are deleted, they are downloaded the next time you connect to an ONS node. Downloading the CTC JAR files may take 1-2 minutes, or 45-50 minutes, depending on the bandwidth of the connection between your workstation and the ONS 15310-CL or ONS 15310-MA. JAR files downloaded from a modem or a data communication channel (DCC) network link will require more time than JAR files downloaded over a LAN connection. • You can install the JAR files on your computer using the CTC setup wizard provided on the CTC software CD. If you install the JAR files with the setup wizard you do not need to wait for the files to download the first time you log into the node. In addition, you can manage ONS 15310-CL or ONS 15310-MA nodes that are added to networks with ONS nodes running older software releases. After you install the JAR files, you can log into an ONS 15454 running an earlier software release and manage the ONS 15310-CL or ONS 15310-MA nodes. However, if you use the Delete CTC Cache function, you must reinstall the JAR files from the software CD. During network topology discovery, CTC polls each node in the network to determine which one contains the most recent version of the CTC software. If CTC discovers a node in the network that has a more recent version of CTC than the version you are currently running, CTC generates a message 5-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.2 CTC Installation Overview stating that a later version of CTC has been found in the network and offers to install the CTC software upgrade JAR files. If you have network discovery disabled, CTC will not seek more recent versions of the software. Unreachable nodes are not included in the upgrade discovery. Note Upgrading the CTC software will overwrite your existing software. You must restart CTC after the upgrade is complete. 5.2 CTC Installation Overview To connect to an ONS 15310-CL or ONS 15310-MA using CTC, enter the ONS 15310-CL or ONS 15310-MA IP address in the URL field of t Navigator or Microsoft Internet Explorer. After connecting to an ONS 15310-CL or ONS 15310-MA, the following events occur automatically: 1. The CTC launcher applet downloads from the 15310-CL-CTX card or CTX2500 card to your computer. 2. The launcher determines whether your computer has a CTC release matching the release on the 15310-CL-CTX card or CTX2500 card. 3. If the computer does not have CTC installed, or if the installed release is older than the 15310-CL-CTX card or CTX2500 card version, the launcher downloads the CTC program files from the card. 4. The launcher starts CTC. The CTC session is separate from the web browser session, so the web browser is no longer needed. 5. You should always log into nodes having the latest software release unless you run the CTC setup wizard and install the ONS 15310-CL or ONS 15310-MA JAR client software files on your computer. If the JAR files are installed on your computer, you can log into ONS 15454s running Release 4.1 or later o manage ONS 15310-CL or ONS 15310-MA nodes that are connected by DCCs to the ONS 15454s. Each ONS 15310-CL or ONS 15310-MA can handle up to five concurrent CTC sessions. CTC performance can vary, depending on the volume of activity in each session, network bandwidth, and 15310-CL-CTX/CTX2500 card load. Note You can also use TL1 commands to communicate with the ONS 15310-CL or ONS 15310-MA through VT100 terminals and VT100 emulation software, or you can Telnet to an ONS 15310-CL or ONS 15310-MA using TL1 port 3083. Refer to the Cisco ONS SONET TL1 Command Guide for a comprehensive list of TL1 commands. 5.3 PC and UNIX Workstation Requirements To use CTC, your computer must have a web browser with the correct Java Runtime Environment (JRE) installed for the software release in use. The correct JRE and Java plug-in for each CTC software release are included on the Cisco ONS 15310-CL and Cisco ONS 15310-MA software CDs. Table 5-1 lists the requirements for PCs and UNIX workstations.5-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.3 PC and UNIX Workstation Requirements Note To avoid network performance issues, Cisco recommends managing a maximum of 50 nodes concurrently with CTC. The 50 nodes can be on a single DCC or split across multiple DCCs. Cisco does not recommend running multiple CTC sessions when managing two or more large networks. To manage more than 50 nodes, Cisco recommends using Cisco Transport Manager (CTM). If you do use CTC to manage more than 50 nodes, you can improve performance by adjusting the heap size; see the “General Troubleshooting” chapter of the Table 5-1 CTC Computer Requirements Area Requirements Notes Processor Pentium III 700 MHz, UltraSPARC, or equivalent 700 Mhz is the recommended processor speed. You can use computers with a lower processor speed; however, you might experience longer response times and slower performance. RAM 384 MB RAM recommended, 512 MB RAM optimum Cisco recommends using 512 MB RAM for networks with 25 nodes or more to avoid longer response times and slower performance. Hard drive 20 GB hard drive with 50 MB of space available — Operating System • PC: Windows 98, Windows NT 4.0 with Service Pack 6a, Windows 2000 with Service Pack 3, or Windows XP with Service Pack 1 • Workstation: Solaris versions 8 or 9 — Java Runtime Environment JRE 1.4.2 or 5.0 JRE 1.4.2 is installed by the CTC Installation Wizard included on the Cisco ONS 15310-CL software CD and the Cisco ONS 15310-MA software CD. JRE 1.4.2 and JRE 5.0 provide enhancements to CTC performance, especially for large networks with numerous circuits. Web browser • PC: Internet Explorer 6.x, Netscape 7.x • UNIX Workstation: Mozilla 1.7, Netscape 7.x For the PC, use JRE 1.4.2 or 5.0 with any supported web browser. Cisco recommends that you use Internet Explorer 6.0. Internet Explorer 6.x is available at the following site: http://www.microsoft.com Cable User-supplied Cat-5 straight-through cable with RJ-45 connectors on each end to connect the computer to the ONS 15310-CL or ONS 15310-MA directly or though a LAN —5-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.4 ONS 15310-CL and ONS 15310-MA Connection Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. You can also create login node groups; see the “Connect the PC and Log Into the GUI” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. 5.4 ONS 15310-CL and ONS 15310-MA Connection Table 5-2 lists the connection options and requirements for connecting a PC to the ONS 15310-CL or ONS 15310-MA node. Table 5-2 ONS 15310-CL and ONS 15310-MA Connection Methods Method Description Requirements Local craft Refers to onsite network connections between the CTC computer and the ONS 15310-CL/ONS 15310-MA using one of the following: • The RJ-45 (LAN) port on the front of the ONS 15310-CL • The RJ-45 (LAN) port on the ONS 15310-MA CTX2500 card faceplate • A hub or switch to which the ONS 15310-CL or ONS 15310-MA is connected If you do not use Dynamic Host Configuration Protocol (DHCP), you must change the computer IP address, subnet mask, and default router, or use automatic host detection. Corporate LAN Refers to a connection to the ONS 15310-CL or ONS 15310-MA through a corporate or network operations center (NOC) LAN. • The ONS 15310-CL or ONS 15310-MA must be provisioned for LAN connectivity, including IP address, subnet mask, default gateway. • The ONS 15310-CL or ONS 15310-MA must be physically connected to the corporate LAN. • The CTC computer must be connected to the corporate LAN that has connectivity to the ONS 15310-CL or ONS 15310-MA.5-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5 CTC Window 5.5 CTC Window The CTC window appears after you log into an ONS 15310-CL or ONS 15310-MA. The CTC window includes a menu bar, toolbar, and a top and bottom pane. The top pane provides status information about the selected objects and a graphic of the current view. The bottom pane provides tabs and subtabs to view ONS 15310-CL or ONS 15310-MA information and perform provisioning and maintenance. The CTC window provides three views: network, node, and card. 5.5.1 Node View Node view is the first view that appears after you log into an ONS 15310-CL or ONS 15310-MA. The login node is the first node shown, and it is the “home view” for the session. Node view allows you to view and manage one node. The status area shows the node name; IP address; session boot date and time; number of Critical (CR), Major (MJ), and Minor (MN) alarms; the name of the current logged-in user; the security level of the user; the software version; and the network element default setup. 5.5.1.1 CTC Card Colors The graphic area of the CTC window depicts the shelf assembly. The colors of the cards in the graphic reflect the real-time status of the physical card and slot (Table 5-3). TL1 Refers to a connection to the ONS 15310-CL or ONS 15310-MA using TL1 rather than CTC. TL1 sessions can be started from CTC, or you can use a TL1 terminal. The physical connection can be a craft connection, corporate LAN, or a TL1 terminal. Refer to the Cisco ONS SONET TL1 Reference Guide. — Remote Refers to a connection made to the ONS 15310-CL or ONS 15310-MA using a modem. • A modem must be connected to the ONS 15310-CL or ONS 15310-MA. • The modem must be provisioned for the ONS 15310-CL or ONS 15310-MA. To run CTC, the modem must be provisioned for Ethernet access. Table 5-2 ONS 15310-CL and ONS 15310-MA Connection Methods (continued) Method Description Requirements Table 5-3 Node View Card and Slot Colors Card and Slot Color Status Gray Slot is not provisioned; no card is installed. Violet Slot is provisioned; no card is installed. White Slot is provisioned; a functioning card is installed. Yellow Slot is provisioned; a Minor alarm condition exists.5-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.1 Node View The port color in both card and node view indicates the port service state. Table 5-4 lists the port colors and their service states. For more information about port service states, see Appendix B, “Administrative and Service States.” Orange Slot is provisioned; a Major alarm condition exists. Red Slot is provisioned; a Critical alarm exists. Table 5-3 Node View Card and Slot Colors (continued) Card and Slot Color Status Table 5-4 Node View Card Port Colors and Service States Port Color Service State Description Cyan (blue) OOS-MA,LPBK (Out-of-Service and Management, Loopback) Port is in a loopback state. On the card in node view, a line between ports indicates that the port is in terminal or facility loopback (see Figure 5-2 on page 5-8 and Figure 5-3 on page 5-8). Traffic is carried and alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. Cyan (blue) OOS-MA,MT (Out-of-Service and Management, Maintenance) Port is out-of-service for maintenance. Traffic is carried and loopbacks are allowed. Alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. Use OOS-MA,MT for testing or to suppress alarms temporarily. Change the state to IS-NR, OOS-MA,DSBLD, or OOS-AU,AINS when testing is complete. Gray OOS-MA,DSBLD (Out-of-Service and Management, Disabled) The port is out-of-service and unable to carry traffic. Loopbacks are not allowed in this service state. Green IS-NR (In-Service and Normal) The port is fully operational and performing as provisioned. 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. The node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in OOS-AU,AINS state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. The AINS port will automatically transition to IS-NR when a signal is received for the length of time provisioned in the soak field.5-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.1 Node View Figure 5-2 Terminal Loopback Indicator Figure 5-3 Facility Loopback Indicator Table 5-5 lists the card statuses. 5.5.1.2 Node View Card Shortcuts If you move your mouse over cards in the graphic, popups display additional information about the card including the card type; card status (active or standby); the type of alarm, such as Critical, Major, and Minor (if any); and the alarm profile used by the card. Right-click a card to reveal a shortcut menu, which you can use to open, reset, or delete the card. Right-click a card slot to preprovision it before installing the card. 5.5.1.3 Node View Tabs Table 5-6 lists the tabs and subtabs available in the node view. Table 5-5 Node View Card Statuses Card Status Description Stby Card is in standby. Act Card is active. NP Card is not present. Mis Card is mismatched. Ldg Card is resetting. Table 5-6 Node View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the node and updates them in real time. — Conditions Displays a list of standing conditions on the node. — History Provides a history of node alarms including date, type, and severity of each alarm. The Session subtab displays alarms and events for the current session. The Node subtab displays alarms and events retrieved from a fixed-size log on the node. Session, Node Circuits Creates, deletes, edits, and maps circuits. Circuits, Rolls5-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.2 Network View 5.5.2 Network View Network view allows you to view and manage ONS 15310-CL or ONS 15310-MA nodes that have DCC connections to the node that you logged into and any login node groups you have selected. Nodes with DCC connections to the login node will not appear if you selected Disable Network Discovery on the Login dialog box. The graphic area displays a background image with colored ONS 15310-CL or ONS 15310-MA icons. A Superuser can set up the logical network view feature, which enables each user to see the same network view. Selecting a node or span in the graphic area displays information about the node and span in the status area. The icon colors indicate the node status (Table 5-7). 5.5.2.1 CTC Node Colors The color of a node in network view indicates the node alarm status. Table 5-7 lists the node colors shown in network view. Provisioning Provisions the ONS 15310-CL node. General, Network, OSI, Protection, Security, SNMP, Comm Channels, Timing, Alarm Profiles, Defaults Inventory Provides inventory information (part number, serial number, Common Language Equipment Identification [CLEI] codes) for cards installed in the node. Allows you to delete and reset cards, and to change card service state. For more information on card service states, see Appendix B, “Administrative and Service States.” — Maintenance Performs maintenance tasks for the node. Database, OSI, Protection, Software, Cross-Connect, Overhead XConnect, Diagnostic, Timing, Audit, RIP Routing Table, Routing Table, Table 5-6 Node View Tabs and Subtabs (continued) Tab Description Subtabs Table 5-7 Node Colors Indicating Status in Network View Color Alarm Status Green No alarms Yellow Minor alarms Orange Major alarms Red Critical alarms Gray with Unknown# Node initializing for the first time (CTC displays Unknown# because CTC has not yet discovered the name of the node)5-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.2 Network View 5.5.2.2 Network View Tabs Table 5-8 lists the tabs and subtabs available in the network view. 5.5.2.3 DCC Links The lines between nodes in the network view indicate DCC connections between the nodes. Active DCC connections appear as green/solid or green/dashed. Solid means circuits can be routed through the link, and dashed means circuits cannot be routed through the link. A gray link is in a fail state. 5.5.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 into a more streamlined view. Link consolidation allows you to condense multiple inter-nodal links into a single link. The link consolidation sorts links by class, meaning that, for example, all DCC links are consolidated together. You can access individual links within consolidated links using the right-click shortcut menu. Each link has an associated icon (Table 5-9). Table 5-8 Network View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the network and updates them in real time. — Conditions Displays a list of standing conditions on the network. — History Provides a history of network alarms including date, type, and severity of each alarm. — Circuits Creates, deletes, edits, filters, and searches for network circuits. Circuits, Rolls Provisioning Provision security, alarm profiles, BLSRs, and overhead circuits. Security, Alarm Profiles, BLSR, Overhead Circuits, Provisionable Patchcords (PPC) Maintenance Displays the type of equipment and the status of each node in the network; displays working and protect software versions, and allows software to be downloaded. Software Table 5-9 Link Icons Icon Description DCC icon GCC icon5-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.3 Card View Note Link consolidation is only available on non-detailed maps. Non-detailed maps display nodes in icon form instead of detailed form, meaning the nodes appear as rectangles with ports on the sides. Refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for more information about consolidated links. 5.5.3 Card View Card view provides information about individual ONS 15310-CL or ONS 15310-MA cards. Use this view to perform card-specific maintenance and provisioning (Figure 5-4). A graphic showing the ports on the card appears in the graphic area. The status area provides the node name, slot, number of alarms, card type, equipment type, and either the card status (active or standby), card service state if the card is present, or port service state (Table 5-4 on page 5-7). The information that appears and the actions you can perform depend on the card. OTS icon PPC icon Server Trail icon Table 5-9 Link Icons Icon Description5-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.3 Card View Figure 5-4 CTC Card View in an ONS 15310-CL Showing an ML-100T-8 Card Table 5-10 shows the tabs and subtabs available in card view. The subtabs, fields, and information shown under each tab depend on the card type selected. Table 5-10 Card View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the card and updates them in real-time. — Conditions Displays a list of standing conditions on the card. — History Provides a history of card alarms including date, object, port, and severity of each alarm. Session (displays alarms and events for the current session), Card (displays alarms and events retrieved from a fixed-size log on the card) Circuits Creates, deletes, edits, and search circuits, and completes rolls. Circuits, Rolls5-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.5.4 Print and Export CTC Data 5.5.4 Print and Export CTC Data You can use the File > Print or File > Export options to print or export CTC provisioning information for record keeping or troubleshooting. The functions can be performed in card, node, or network views. The File > Print function sends the data to a local or network printer. File > Export exports the data to a file where it can be imported into other computer applications, such as spreadsheets and database management programs. Whether you choose to print or export data, you can choose from the following options: • Entire frame—Prints or exports the entire CTC window including the graphical view of the card, node, or network. This option is available for all windows. Provisioning Provisions a card. 15310-CL-CTX card and 15310-MA electrical cards: Wideband Ports, Broadband Ports, DS1 (subtabs include Line, Line Thresholds, Elect Path Thresholds, and SONET Thresholds); DS3 (subtabs include Line, Line Thresholds, Elect Path Thresholds, and SONET Thresholds); EC1 (subtabs include Line, SONET Thresholds, and SONET STS) 15310-CL-CTX card and CTX2500 card: Optical (subtabs include Line, SONET Thresholds, SONET STS, and Optics Thresholds); Pluggable Port Modules; External Alarms; External Controls, and Alarm Profiles. Ethernet cards (subtabs depend on the card type): Ether Ports, POS Ports, Ether VLAN, Ether Card, Ether Thresholds, Alarm Profiles Maintenance Performs maintenance tasks for the card. 15310-CL-CTX card and 15310-MA electrical cards: DS1 (subtabs include Loopback, Protection, Path Trace AINS Soak); DS3 (subtabs include Loopback, Protection, Path Trace AINS Soak); EC1(subtabs include Loopback, Protection, Path Trace AINS Soak) 15310-CL-CTX card and CTX2500 card: Optical (subtabs include Loopback, ALS, Protection, Path Trace AINS Soak); External Alarms; External Controls; and Virtual Wires Ethernet cards: Path Trace, Loopback, Bandwidth Performance Performs performance monitoring for the card. 15310-CL-CTX card and CTX2500 card: DS1, DS3, EC1, Optical Ethernet cards (subtabs depend on the card type): Ether Ports, POS Ports Table 5-10 Card View Tabs and Subtabs (continued) Tab Description Subtabs5-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.6 Common Control Card Reset • Tabbed view—Prints or exports the lower half of the CTC window containing tabs and data. The printout includes the selected tab (on top) and the data shown in the tab window. For example, if you print the History window tabbed view, you print only history items appearing in the window. This option is available for all windows. • Table Contents—Prints CTC data in table format without graphical representations of shelves, cards, or tabs. This option does not apply to all windows; refer to the print task in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for specifics. • The Table Contents option prints all the data contained in a table with the same column headings. For example, if you print the History window Table Contents view, you print all data included in the table whether or not items appear in the window. 5.6 Common Control Card Reset You can reset the common control card for the ONS 15310-CL (the 15310-CL-CTX card) or the ONS 15310-MA (the CTX2500 card) by using the hard-reset or soft-reset commands in CTC. A soft reset reboots the 15310-CL-CTX or CTX2500 card and reloads the operating system and the application software. A hard reset temporarily removes power from the 15310-CL-CTX card and CTX2500 card and clears all buffer memory. Before you hard-reset a card, put the card in standby mode by completing a soft-reset. From the node view, select a card and right-click to open a menu with the hard-reset and soft-reset commands. Soft resets do not impact traffic, but hard resets are service affecting. A card must be in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state before you can perform a hard reset. 5.7 Traffic Card Reset You can reset the CE-100T-8, ML-100T-8, DS1-28/DS3-EC1-3, and DS1-28/DS3-EC1-3 cards by using the hard-reset or soft-reset commands in CTC. A soft reset reboots the card and reloads the operating system and the application software. A hard reset temporarily removes power from the card and clears all buffer memory. From the node view, select a card and right-click to open a menu with the hard-reset and soft-reset commands. A card must be in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state before you can perform a hard reset. 5.8 Database Backup You can store a back-up version of the database on the workstation running CTC. This operation should be part of a regular ONS 15310-CL and ONS 15310-MA maintenance program performed at approximately weekly intervals and should also be completed when preparing an ONS 15310-CL or ONS 15310-MA for a pending natural disaster, such as a flood. Note The following parameters are not backed up and restored: node name, IP address, mask and gateway, and Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up database with a different node name, the circuits will map to the new node name. Cisco recommends keeping a record of the old and new node names.5-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.9 Software Revert 5.9 Software Revert When you click the Activate button after a software upgrade, the 15310-CL-CTX or CTX2500 copies the current working database and saves it in a reserved location in the 15310-CL-CTX or CTX2500 flash memory. If you later need to revert to the original working software load from the protect software load, the saved database installs automatically. You do not need to restore the database manually or recreate circuits. The revert feature is useful if a maintenance window closes while you are upgrading CTC software. You can revert to the standby software load without losing traffic. When the next maintenance window opens, complete the upgrade and activate the new software load. Circuits that were created and provisioning that was performed after a software load is activated (upgraded to a higher release) do not reinstate with a revert. The database configuration at the time of activation is reinstated after a revert. This does not apply to maintenance reverts (for example 7.0.1 to 7.0.0), because maintenance releases use the same database.5-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 5 Cisco Transport Controller Operation 5.9 Software RevertCHAPTER 6-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 6 Security This chapter provides information about Cisco ONS 15310-CL and Cisco ONS 15310-MA user security. To provision security, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 6.1 Users IDs and Security Levels, page 6-1 • 6.2 User Privileges and Policies, page 6-2 • 6.3 Audit Trail, page 6-6 • 6.4 RADIUS Security, page 6-7 6.1 Users IDs and Security Levels A CISCO15 user ID is provided with the ONS 15310-CL and ONS 15310-MA for use with initial login. Use this ID to set up other ONS 15310-CL and ONS 15310-MA user IDs. (For instructions, see the “Turn Up a Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.) Note Cisco Transport Controller (CTC) does not display the CISCO15 user ID when you log in. An ONS 15310-CL and ONS 15310-MA node can support up to 500 user IDs. Each CTC or Transaction Language 1 (TL1) user ID can be assigned one of the following security levels: • Retrieve—Users can retrieve and view CTC information but cannot set or modify parameters. • Maintenance—Users can access only the ONS 15310-CL and ONS 15310-MA maintenance options. • Provisioning—Users can access provisioning and maintenance options. • Superuser—Users can perform all of the functions of the other security levels as well as set names, passwords, and security levels for other users. By default, multiple concurrent user ID sessions are permitted on the node; that is, multiple users can log into a node using the same user ID. However, you can provision the node to allow only a single login per user ID and prevent concurrent logins for all users. See Table 6-3 on page 6-6 for idle user timeout information for each security level. 6-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.2 User Privileges and Policies 6.2 User Privileges and Policies This section lists user privileges for each CTC action and describes the security policies available to Superusers. 6.2.1 User Privileges by CTC Action Table 6-1 shows the actions that each user privilege level can perform in node view. Table 6-1 ONS 15310-CL and ONS 15310-MA Security Levels—Node View CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser Alarms — Synchronize/Filter/Delete Cleared Alarms XX X X Conditions — Retrieve/Filter X X X X History Session Filter X X X X Shelf Retrieve/Filter X X X X Circuits Circuits Create/Edit/Delete — — X X Filter/Search X X X X Rolls Complete/Force Valid Signal/Finish —— X X Provisioning General Edit — — Partial1 X Network General: Edit — — — X Static Routing: Create/Edit/ Delete —— X X OSPF: Create/Edit/Delete — — X X RIP: Create/Edit/Delete — — X X Proxy: Create/Edit/Delete — — — X Firewall: Create/Edit/Delete — — — X OSI Main Setup: Edit — — — X TARP: Config: Edit — — X X TARP: Static TDC: Add/Edit/Delete —— X X TARP: MAT: Add/Edit/Delete — — X X Routers: Setup: Edit — — — X Routers: Subnets: Edit/Enable/Disable —— X X Tunnels: Create/Edit/Delete — — X X Protection Create/Delete/Edit — — X X6-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.2.1 User Privileges by CTC Action Provisioning (continued) Security Users: Create/Delete/Clear Security Intrusion Alarm —— — X Users: Change Same user Same user Same user All users Active Logins: View/Logout/ Retrieve Last Activity Time —— — X Policy: Edit/View — — — X Access: Edit/View — — — X RADIUS Server: Create/Edit/Delete/Move Up/ Move Down/View —— — X Legal Disclaimer: Edit — — — X SNMP Create/Edit/Delete — — X X Browse trap destinations X X X X Comm Channels SDCC: Create/Edit/Delete — — X X LDCC: Create/Edit/Delete — — X X PPC: Create/Edit/Delete — — X X Timing General/BITS Facilities: Edit — — X X Orderwire Enable Buzzer — — X X Alarm Extenders External Alarms: Edit — — X X External Controls: Edit — — X X Alarm Profiles Alarm Behavior: Edit — — X X Alarm Profile Editor: Store/Delete2 —— X X Alarm Profile Editor: New/Load/Compare/Available/ Usage XX X X Defaults Edit/Import — — — X Reset/Export X X X X Inventory — Delete — — X X Hard Reset/Soft Reset — X X X Maintenance Database Backup — X X X Restore — — — X Network Routing Table: Retrieve X X X X RIP Routing Table: Retrieve X X X X Table 6-1 ONS 15310-CL and ONS 15310-MA Security Levels—Node View (continued) CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser6-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.2.1 User Privileges by CTC Action Table 6-2 shows the actions that each user privilege level can perform in network view. Maintenance (continued) OSI IS-IS RIB: Refresh X X X X ES-IS RIB: Refresh X X X X TDC: TID to NSAP/Flush Dynamic Entries —X X X TDC: Refresh X X X X Protection Switch/Lock out/ Lock-on/Clear/ Unlock —X X X Software Download — X X X Activate/Revert — — — X Cross-Connect Resource Usage: Delete — — X X Resource Usage: Refresh X X X X Overhead XConnect View X X X X Alarm Extenders External Alarms: View X X X X External Controls: View X X X X Virtual Wires: View/Retrieve X X X X Diagnostic Retrieve Tech Support Log — — X X Lamp Test — X X X Timing Source: Edit — X X X Report: View/Refresh X X X X Audit Retrieve — — — X Archive — — X X Test Access View X X X X 1. Provisioner user cannot change node name, contact, location, or Virtual Tributary alarm indication signal (AIS-V) insertion on STS-1 signal degrade (SD) parameters. 2. The action buttons in the subtab are active for all users, but the actions can be completely performed only by the users with the required security levels. Table 6-1 ONS 15310-CL and ONS 15310-MA Security Levels—Node View (continued) CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser Table 6-2 ONS 15310-CL and ONS 15310-MA Security Levels—Network View CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser Alarms — Synchronize/Filter/Delete cleared alarms XX X X Conditions — Retrieve/Filter X X X X History — Filter X X X X6-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.2.2 Security Policies 6.2.2 Security Policies Users with the Superuser security privilege can provision security policies on the ONS 15310-CL and ONS 15310-MA. These security policies include idle user timeouts, password changes, password aging, and user lockout parameters. In addition, a Superuser can access the ONS 15310-CL and ONS 15310-MA through the LAN port on the front of the node. 6.2.2.1 Superuser Privileges for Provisioning Users Superusers can grant permission to Provisioning users to perform a set of tasks. The tasks include retrieving an audit log, restoring a database, clearing performance monitoring (PM) parameters, and activating and reverting software loads. These privileges, except the PM clearing privilege, can only be granted using CTC network element (NE) defaults. See Appendix C, “Network Element Defaults” for more information. To grant the PM clearing privilege using CTC, click the Provisioning > Security > Access tabs. For more information about setting up Superuser privileges, refer to the “Change Node Settings” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Circuits Circuits Create/Edit/Delete — — X X Filter/Search X X X X Rolls Complete/ Force Valid Signal/ Finish —— X X Provisioning Security Users: Create/Delete/Clear Security Intrusion Alarm —— — X Users: Change Same User Same User Same User All Users Active logins: Logout/Retrieve Last Activity Time —— — X Policy: Change — — — X Alarm Profiles Store/Delete1 —— X X New/Load/Compare/Available/ Usage XX X X BLSR Create/Delete/Edit/Upgrade — — X X Overhead Circuits Create/Delete/Edit/Merge — — X X Search X X X X Provisionable Patchcords (PPC) Create/Edit/Delete — — X X Server Trails Create/Edit/Delete — — X X Maintenance Software Download/Cancel — X X X Diagnostic OSPF Node Information: Retrieve/Clear XX X X 1. The action buttons in the subtab are active for all users, but the actions can be completely performed only by the users assigned with the required security levels. Table 6-2 ONS 15310-CL and ONS 15310-MA Security Levels—Network View (continued) CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser6-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.3 Audit Trail 6.2.2.2 Idle User Timeout Each ONS 15310-CL and ONS 15310-MA 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. A lockout prevents 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 6-3. The user idle period can be modified by a Superuser; refer to the “Change Node Settings” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for instructions. 6.2.2.3 User Password, Login, and Access Policies Superusers can view real-time lists of users who are logged in via CTC or TL1 for each node. Superusers can also provision the following password, login, and node access policies: • Password expirations and reuse—Superusers can specify when users must change their passwords and how frequently passwords can be reused. • Login attempts and locking out users—Superusers can specify the maximum number of times that a user can unsuccessfully attempt to log in before being locked out of CTC. Superusers can also provision the length of time before the lockout is removed. • Disabling users—Superusers can provision the length of time before inactive user IDs are disabled. • Node access and user sessions—Superusers can limit the number of CTC sessions one user can have, and they can prohibit access to the ONS 15310-CL and ONS 15310-MA using the LAN connection. • Secure shell—Superusers can select secure shell (SSH) instead of Telnet at the CTC Provisioning > Security > Access tab. SSH is a terminal-remote host Internet protocol that uses encrypted links. It provides authentication and secure communication over channels that are not secure. Port 22 is the default port and cannot be changed. 6.3 Audit Trail The ONS 15310-CL and ONS 15310-MA maintain a GR-839-CORE-compliant audit trail log that resides on the 15310-CL-CTX and CTX2500 cards respectively. Audit trails are useful for maintaining security, recovering lost transactions, and tracing user activities. The audit trail log shows who has accessed the node and what operations were performed during a given period of time. The log includes authorized Cisco support logins and logouts using the operating system command line interface (CLI), CTC, and TL1; the log also includes FTP actions, circuit creation/deletion, and user/system generated actions. Event monitoring is also recorded in the audit log. An event is defined as a change in status of an element within the network. External events, internal events, attribute changes, and software upload/download activities are recorded in the audit trail. Table 6-3 Default User Idle Times Security Level Idle Time Superuser 15 minutes Provisioning 30 minutes Maintenance 60 minutes Retrieve Unlimited6-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.3.1 Audit Trail Log Entries To view the audit trail log, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Users can access the audit trail logs from any management interface (CTC, Cisco Transport Manager [CTM], or TL1). The audit trail is stored in persistent memory and is not corrupted by processor switches or upgrades. Note The ONS 15310-CL and ONS 15310-MA do not support a real-time clock with battery backup. Therefore, when you reset 15310-CL-CTX and CTX2500 cards, the audit log is reset to 1970 until you set the date and time again. 6.3.1 Audit Trail Log Entries Audit trail records capture various types of activities. Individual audit entries contain some or all of the following information: • User—Name of the user performing the action • Host—Host from where the activity is logged • Device ID—IP address of the device involved in the activity • Application—Name of the application involved in the activity • Task—Name of the task involved in the activity (view a dialog box, apply configuration, and so on) • Connection Mode—The service used to connect to the node (for example, Telnet, console, or Simple Network Management Protocol [SNMP]) • Category—Type of change: Hardware, Software, or Configuration • Status—Status of the user action: Read, Initial, Successful, Timeout, or Failed • Time—Time of change • Message Type—Denotes whether the event succeeded or failed • Message Details—A description of the change 6.3.2 Audit Trail Capacities The ONS 15310-CL and ONS 15310-MA is able to store 640 log entries.When this limit is reached, the oldest entries are overwritten with new events. When the log server is 80 percent full, an AUD-LOG-LOW condition is raised and logged. When the log server reaches the maximum capacity of 640 entries and begins overwriting records that were not archived, an AUD-LOG-LOSS condition is raised and logged. This event indicates that audit trail records have been lost. Until you off-load the file, this event will not occur a second time regardless of the amount of entries that are overwritten by incoming data. To export the audit trail log, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. 6.4 RADIUS Security Users with Superuser security privileges can configure nodes to use Remote Authentication Dial In User Service (RADIUS) authentication. Cisco Systems uses a strategy known as authentication, authorization, and accounting (AAA) for enabling, verifying, and tracking the actions of remote users. 6-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.4.1 RADIUS Authentication 6.4.1 RADIUS Authentication RADIUS is a system of distributed security that secures remote access to networks and network services against unauthorized access. RADIUS contains three components: • A protocol with a frame format that utilizes User Datagram Protocol (UDP)/IP • A server • A client The server runs on a central computer, typically at a customer site, while the clients reside in the dial-up access servers and can be distributed throughout the network. ONS 15310-CL and ONS 15310-MA nodes operate as clients of the RADIUS server. The client is responsible for passing user information to designated RADIUS servers, and then acting on the response that is returned. RADIUS servers are responsible for receiving user connection requests, authenticating the user, and returning all configuration information necessary for the client to deliver service to the user. The RADIUS servers can act as proxy clients to other kinds of authentication servers. Transactions between the RADIUS client and server are authenticated through the use of a shared secret, which is never sent over the network. In addition, any user passwords are sent encrypted between the client and RADIUS server. This prevents someone monitoring an unsecured network from determine a user's password. Refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide to implement RADIUS authentication. 6.4.2 Shared Secrets A shared secret is a text string that serves as a password between: • A RADIUS client and a 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. Shared secrets are used to: • Verify that RADIUS messages, with the exception of the Access-Request message, are sent by a RADIUS-enabled device that is configured with the same shared secret. • Verify that the RADIUS message has not been modified in transit (message integrity). • Encrypt some RADIUS attributes, such as User-Password and Tunnel-Password. When creating and using a shared secret: • Use the same case-sensitive shared secret on both RADIUS devices. • Use a different shared secret for each RADIUS server-RADIUS client pair. • Generate a random sequence at least 22 characters long to ensure a random shared secret. • Use any standard alphanumeric and special characters. • Use a shared secret of up to 128 characters in length. To protect your server and your RADIUS clients from brute force attacks, use long shared secrets (more than 22 characters). • Make the shared secret a random sequence from each of the following three categories: letters (upper or lower case), numbers, and punctuation. 6-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 6 Security 6.4.2 Shared Secrets • Change the shared secret often to protect your server and your RADIUS clients from dictionary attacks. An example of a strong shared secret is 8d#>9fq4bV)H7%a3-zE13sW$hIa32M#m Timing > Report tabs show current timing information for an ONS 15310-CL and ONS 15310-MA, including the timing mode, clock state and status, switch type, and reference data. Caution 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 mixed timing mode with caution. 7.2 Network Timing Figure 7-1 shows an example of an ONS 15310-CL and ONS 15310-MA network timing setup. Node 1 is set to external timing. One reference is set to BITS, the two references are set to internal. The BITS output pins on the CTX cards of Node 3 provide timing to outside equipment, such as a digital access line multiplexer. Figure 7-1 ONS 15310-CL and ONS 15310-MA Timing Example Node 4 Timing Line Ref 1: Slot 4 Ref 2: Slot 3 Ref 3: Internal (ST3) Node 2 Timing Line Ref 1: Slot 3 Ref 2: Slot 4 Ref 3: Internal (ST3) Node 1 Timing External Ref 1: BITS Ref 2: Internal Ref 3: Internal (ST3) Node 3 Timing Line Ref 1: Slot 3 Ref 2: Slot 4 Ref 3: Internal (ST3) BITS out BITS source Third party equipment Slot 3 Slot 3 Slot 3 Slot 3 Slot 4 Slot 4 Slot 4 Slot 4 1248937-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 7 Timing 7.3 Synchronization Status Messaging 7.3 Synchronization Status Messaging Synchronization status messaging (SSM) is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops. 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 SSM for the ONS 15310-CL and ONS 15310-MA, consult your timing reference documentation to determine which message set to use. Table 7-1 and Table 7-2 show the Generation 1 and Generation 2 message sets. Table 7-1 SSM Generation 1 Message Set Message Quality Description PRS 1 Primary reference source—Stratum 1 STU 2 Synchronization traceability unknown ST2 3 Stratum 2 ST3 4 Stratum 3 SMC 5 SONET minimum clock ST4 6 Stratum 4 DUS 7 Do not use for timing synchronization RES Reserved; quality level set by user Table 7-2 SSM Generation 2 Message Set Message Quality Description PRS 1 Primary reference source—Stratum 1 STU 2 Synchronization traceability unknown ST2 3 Stratum 2 TNC 4 Transit node clock ST3E 5 Stratum 3E ST3 6 Stratum 3 SMC 7 SONET minimum clock ST4 8 Stratum 4 DUS 9 Do not use for timing synchronization RES Reserved; quality level set by user7-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 7 Timing 7.3 Synchronization Status MessagingCHAPTER 8-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 8 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This chapter explains Cisco ONS 15310-CL and Cisco ONS 15310-MA synchronous transport signal (STS) and Virtual Tributary (VT) circuits and VT and data communications channel (DCC) tunnels. To provision circuits and tunnels, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 8.1 Overview, page 8-1 • 8.2 Circuit Properties, page 8-2 • 8.3 VT1.5 Bandwidth, page 8-7 • 8.4 VT Tunnels and Aggregation Points, page 8-8 • 8.5 DCC Tunnels, page 8-8 • 8.6 Virtual Concatenated Circuits, page 8-9 • 8.7 Section and Path Trace, page 8-13 • 8.8 Bridge and Roll, page 8-13 • 8.9 Merged Circuits, page 8-18 • 8.10 Reconfigured Circuits, page 8-19 • 8.11 Server Trails, page 8-20 8.1 Overview You can create circuits across and within ONS 15310-CL and ONS 15310-MA 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. 8-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.2 Circuit Properties • Automatically or manually route circuits. • Automatically create multiple circuits with autoranging. VT tunnels do not use autoranging. • Provide full protection to the circuit path. • Provide only protected sources and destinations for circuits. • Define a secondary circuit source or destination that allows you to interoperate an ONS 15310-CL or an ONS 15310-MA path protection with third-party equipment path protection configurations. • Set path protection circuits as revertive or nonrevertive. For the ONS 15310-CL and ONS 15310-MA CE-100T-8 or ML-100T-8 cards, you can provision circuits either before or after the cards are installed if the slots are provisioned. For the 15310-CL-CTX and the 15310-MA CTX2500 card, you must preprovision the small form-factor pluggables (SFPs) (called pluggable port modules [PPMs] in CTC) before you can create an optical circuit. However, circuits do not carry traffic until the cards and SFPs are installed and the ports are In-Service and Normal (IS-NR); Out-of-Service and Autonomous, Automatic In-Service (OO-AU,AINS); or Out-of-Service and Management, Maintenance (OOS-MA,MT). 8.2 Circuit Properties You can view information about circuits in the ONS 15310-CL and ONS 15310-MA Circuits window, which appears in network, node, and card view. The Circuits window shows the following information: • Name—The name of the circuit. The circuit name can be manually assigned or automatically generated. • Type—The circuit types are: STS (STS circuit), VT (VT circuit), VTT (VT tunnel), VAP (VT aggregation point), STS-V (STS virtual concatenated [VCAT] circuit), or VT-V (VT VCAT circuit). • Size—The circuit size. VT circuits are 1.5. ONS 15310-CL STS circuits are 1, 3c, 6c, 9c, or 12c. ONS 15310-MA STS circuits are 1, 3c, 6c, 9c, 12c, 24c, and 48c. VCAT circuits are VT1.5-nv or STS-1-nv, where n is the number of members. • Protection—The type of circuit protection. • Direction—The circuit direction, either two-way or one-way. • Status—The circuit status. See the “8.2.1 Circuit Status” section on page 8-3. • Source—The circuit source in the format: node/slot/port “port name”/STS/VT. (Port name appears in quotes.) Node and slot always appear; port “port name”/STS/VT might appear, depending on the source card, circuit type, and whether a name is assigned to the port. If the port uses a pluggable port module (PPM), the port format is PPM-port number, for example, p2-1. If the port is a DS-1, DS-3, or EC-1 port, port type is indicated, for example, pDS1. If the circuit size is a concatenated size (3c, 6c, 9c, 12c), STSs used in the circuit are indicated by an ellipsis, for example, S7..9, (STSs 7, 8, and 9) or S10..12 (STSs 10, 11, and 12). • Destination—The circuit destination in the same format as the circuit source. • # of Spans—The number of internode links that constitute the circuit. Right-clicking the column displays a shortcut menu from which you can choose to show or hide circuit span detail. • State—The circuit state. See the “8.2.2 Circuit States” section on page 8-4. The Filter button allows you to filter the circuits in network, node, or card view based on circuit name, size, type, direction, and other attributes. In addition, you can export the Circuit window data in HTML, comma-separated values (CSV), or tab-separated values (TSV) format using the Export command from the File menu.8-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.2.1 Circuit Status 8.2.1 Circuit Status The circuit statuses that appear in the Circuit window Status column are generated by Cisco Transport Controller (CTC) based on conditions along the circuit path. Table 8-1 shows the statuses that can appear in the Status column. Table 8-1 ONS 15310-CL and ONS 15310-MA Circuit Status Status Definition/Activity CREATING CTC is creating a circuit. DISCOVERED CTC created a circuit. All components are in place and a complete path exists from circuit source to destination. DELETING CTC is deleting a circuit. PARTIAL A CTC-created circuit is missing a cross-connect or network span or a complete path from source to destination(s) does not exist. In CTC, circuits are represented using cross-connects and network spans. If a network span is missing from a circuit, the circuit status is PARTIAL. However, a PARTIAL status does not necessarily mean a circuit traffic failure has occurred, because traffic might flow on a protect path. Network spans are in one of two states: up or down. On CTC circuit and network maps, up spans appear as green lines, and down spans appear as gray lines. If a failure occurs on a network span during a CTC session, the span remains on the network map but its color changes to gray to indicate that the span is down. If you restart your CTC session while the failure is active, the new CTC session cannot discover the span and its span line does not appear on the network map. Subsequently, circuits routed on a network span that goes down appear as DISCOVERED during the current CTC session, but appear as PARTIAL to users who log in after the span failure. DISCOVERED_TL1 A TL1-created circuit or a TL1-like CTC-created circuit is complete. A complete path from source to destinations exists. PARTIAL_TL1 A TL1-created circuit or a TL1-like CTC-created circuit is missing a cross-connect or circuit span (network link), and a complete path from source to destinations does not exist. CONVERSION_PENDING An existing circuit in a topology upgrade is set to this status. The circuit returns to the DISCOVERED status when the topology upgrade is complete. For more information about in-service topology upgrades, see Chapter 9, “SONET Topologies and Upgrades.” PENDING_MERGE Any new circuits created to represent an alternate path in a topology upgrade are set to this status to indicate that the circuit is temporary. These circuits can be deleted if a topology upgrade fails. For more information about in-service topology upgrades, see Chapter 9, “SONET Topologies and Upgrades.” DROP_PENDING A circuit is set to this status when a new circuit drop is being added.8-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.2.2 Circuit States 8.2.2 Circuit States The circuit service state is an aggregate of the cross-connect states within the circuit. • If all cross-connects in a circuit are in the IS-NR service state, the circuit service state is In-Service (IS). • If all cross-connects in a circuit are in an Out-of-Service (OOS) service state, such as OOS-MA,MT; Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS); or Out-of-Service and Management, Disabled (OOS-MA,DSBLD), the circuit service state is OOS. • PARTIAL is appended to the OOS circuit service state when circuit cross-connect states are mixed and not all states are IS-NR. The OOS-PARTIAL state can occur during automatic or manual transitions between states. OOS-PARTIAL can appear during a manual transition caused by an abnormal event such as a CTC crash or communication error, or if one of the cross-connects could not be changed. Refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide for troubleshooting procedures. You can assign a state to circuit cross-connects at two points: • During circuit creation, you can set the state on the Create Circuit wizard. • After circuit creation, you can change a circuit state in the Edit Circuit window or from the Tools > Circuits > Set Circuit State menu. Note After you have created an initial circuit in a CTC session, the subsequent circuit states default to the circuit state of the initial circuit, regardless of which nodes in the network the circuits traverse or the node.ckt.state default setting. During circuit creation, you can apply a service state to the drop ports in a circuit; however, CTC does not apply a requested state other than IS-NR to drop ports if: • The port is a timing source. • The port is provisioned for orderwire or tunnel orderwire. • The port is provisioned as a DCC or DCC tunnel. • The port supports 1+1. Circuits do not use the soak timer, but ports do. The soak period is the amount of time that the port remains in the OOS-AU,AINS service state after a signal is continuously received. When the cross-connects in a circuit are in the OOS-AU,AINS service state, the ONS 15310-CL and ONS 15310-MA monitor the cross-connects for an error-free signal. It changes the state of the circuit from OOS to IS or to OOS-PARTIAL as each cross-connect assigned to the circuit path is completed. This allows you to provision a circuit using TL1, verify its path continuity, and prepare the port to go into service when it receives an error-free signal for the time specified in the port soak timer. Two common examples of state changes you see when provisioning circuits using CTC are: • When assigning the IS,AINS administrative state to cross-connects in VT1.5 circuits and VT tunnels, the source and destination ports on the VT1.5 circuits remain in the OOS-AU,AINS service state until an alarm-free signal is received for the duration of the soak timer. When the soak timer expires and an alarm-free signal is found, the VT1.5 source port and destination port service states change to IS-NR and the circuit service state becomes IS. 8-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.2.3 Circuit Protection Types • When assigning the IS,AINS administrative state to cross-connects in STS circuits, the circuit source and destination ports transition to the OOS-AU,AINS service state. When an alarm-free signal is received, the source and destination ports remain OOS-AU,AINS for the duration of the soak timer. After the port soak timer expires, STS source and destination ports change to IS-NR and the circuit service state to IS. To find the remaining port soak time, choose the Maintenance > AINS Soak tabs in card view and click the Retrieve button. If the port is in the OOS-AU,AINS service state and has a good signal, the Time Until IS column shows the soak count down status. If the port is OOS-AU,AINS and has a bad signal, the Time Until IS column indicates that the signal is bad. You must click the Retrieve button to obtain the latest time value. For more information about port and cross-connect service states, see Appendix B, “Administrative and Service States.” 8.2.3 Circuit Protection Types The Protection column on the Circuit window shows the card (line) and SONET topology (path) protection used for the entire circuit path. Table 8-2 shows the protection type indicators that you see in this column. 8.2.4 Circuit Information in the Edit Circuits Window You can edit a selected circuit using the Edit button on the Circuits window. The tabs that appear depend on the circuit chosen: • General—Displays general circuit information and allows you to edit the circuit name. • Monitors—Displays possible monitor sources and allows you to create a monitor circuit. • Path Protection Selectors—Allows you to change path protection selectors. • Path Protection Switch Counts—Allows you to change path protection switch protection paths. • State—Allows you to edit cross-connect service states. • Merge—Allows you to merge aligned circuits. For more information, see the “8.9 Merged Circuits” section on page 8-18. Table 8-2 Circuit Protection Types Protection Type Description 1+1 The circuit is protected by a 1+1 protection group. N/A A circuit with connections on the same node is not protected. Protected The circuit is protected by diverse SONET topologies, for example, a path protection and 1+1. Unknown A circuit has a source and destination on different nodes and communication is down between the nodes. This protection type appears if not all circuit components are known. Unprot (black) A circuit with a source and destination on different nodes is not protected. Unprot (red) A circuit created as a fully protected circuit is no longer protected due to a system change, such as removal of a 1+1 protection group. Path Protection The circuit is protected by a path protection.8-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.2.4 Circuit Information in the Edit Circuits Window Using the Export command from the File menu, you can export data from the Path Protection Selectors, Path Protection Switch Counts, State, and Merge tabs in HTML, comma-separated values (CSV), or tab-separated values (TSV) format. The Show Detailed Map checkbox in the Edit Circuit window updates the graphical view of the circuit to show more detailed routing information, such as: • Circuit direction (unidirectional/bidirectional) • The nodes, STSs, and VTs through which the circuit passes including slots and port numbers • The circuit source and destination points • Open Shortest Path First (OSPF) area IDs • Link protection (path protection, unprotected, 1+1) and bandwidth (OC-N) Alarms and states can also be viewed on the circuit map, including: • 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 selectors states By default, the working path on the detailed circuit map is indicated by a green bidirectional arrow, and the protect path is indicated by a purple bidirectional arrow. Source and destination ports are shown as circles with an S and D. Port states are indicated by colors, shown in Table 8-3. Notations within or next to the squares or selector pentagons on each node indicate switches and other conditions. For example: • F = Force switch • M = Manual switch • L = Lockout switch • Arrow = Facility (outward) or terminal (inward) loopback (Figure 8-1) Table 8-3 Port State Color Indicators Port Color State Green IS-NR Gray OOS-MA,DSBLD Purple OOS-AU,AINS Light blue OOS-MA,MT8-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.3 VT1.5 Bandwidth Figure 8-1 Terminal Loopback in the Edit Circuits Window Move the mouse cursor over nodes, ports, and spans to see tooltips with information including the number of alarms on a node (organized by severity), a port’s service state, and the protection topology. Right-click a node, port, or span on the detailed circuit map to initiate certain circuit actions: • Right-click a unidirectional circuit destination node to add a drop to the circuit. • Right-click a port containing a path-trace-capable card to initiate the path trace. • Right-click a path protection span to change the state of the path selectors in the path protection circuit. 8.3 VT1.5 Bandwidth The 15310-CL-CTX card performs port-to-port time-division multiplexing (TDM). Because VT1.5 multiplexing is STS-based, understanding how VT1.5 circuits use the 15310-CL-CTX VT matrix resources is necessary to avoid unexpected depletion of VT matrix capacity. The key VT matrix principles are as follows: • The VT matrix has 24 logical STS ports. All VT1.5 multiplexing is achieved through these logical STS ports. • Because each logical STS termination on the VT matrix can carry 28 VT1.5s, the VT matrix capacity is 672 VT 1.5s (24 times 28). 8-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.4 VT Tunnels and Aggregation Points The 15310-CL-CTX card can map up to 24 STSs for VT1.5 traffic. Because one STS can carry 28 VT1.5s, the 15310-CL-CTX card can terminate up to 672 VT1.5s or 336 VT1.5 cross-connects. However, to terminate 336 VT1.5 cross-connects, each STS mapped for VT1.5 traffic must carry 28 VT1.5 circuits. If you assign each VT1.5 circuit to a different STS, the 15310-CL-CTX card VT1.5 cross-connect capacity is reached after you create 12 VT1.5 circuits. The CTX2500 in the ONS 15310-MA also performs port-to-port time-division multiplexing (TDM). The VT matrix for the CTX2500 has 96 logical STS ports. All VT1.5 multiplexing is achieved through these logical STS ports. Although the CTX2500 can support up to 2688 VT1.5 cross-connects and 1344 bidirectional VT circuits, the maximum number of VTs that can be provisioned for Software Release 7.0 is 2128 VT cross-connects and 1064 bidirectional VT circuits. 8.4 VT Tunnels and Aggregation Points To maximize VT1.5 cross-connect resources, you can tunnel VT1.5 circuits through ONS 15310-CL and ONS 15310-MA nodes. VT1.5 tunnels do not use VT matrix capacity at pass-through nodes, thereby freeing the cross-connect resources for other VT1.5 circuits. VT aggregation points (VAPs) allow you to provision circuits from multiple VT1.5 sources to a single STS destination. Like circuits, a VAP has a source and a destination. The source is the STS grooming end, the node where the VT1.5 circuits are aggregated into a single STS. The VAP STS must be an OC-N port. VT matrix resources are not used on the VAP source node, which is the key advantage of VAPs. The VAP destination is the node where the VT1.5 circuits originate. Circuits can originate on any ONS 15310-CL or ONS 15310-MA card or port. 8.5 DCC Tunnels Each SONET frame provides four DCCs for network element (NE) Operations, Administration, Maintenance, and Provisioning (OAM&P): one on the SONET Section layer (DCC1) and three on the SONET Line layer (DCC2, DCC3, DCC4). The ONS 15310-CL and ONS 15310-MA use the Section DCC (SDCC) or Line DCC (LDCC) for management and provisioning. When multiple DCC channels exist between two neighboring nodes, the ONS 15310-CL or ONS 15310-MA balances traffic over the existing DCC channels using a load-balancing algorithm. This algorithm chooses a DCC for packet transport by considering packet size and DCC utilization. You can tunnel third-party SONET equipment across ONS 15310-CL or ONS 15310-MA networks using one of two tunneling methods, a traditional DCC tunnel or an IP-encapsulated tunnel. 8.5.1 Traditional DCC Tunnels In traditional DCC tunnels, you can use the three available channels of the LDCC and/or the single channel of the SDCC, when not used for ONS 15310-CL or ONS 15310-MA DCC terminations, to tunnel third-party SONET equipment across ONS networks. A DCC tunnel endpoint is defined by slot, port, and DCC channel. You can connect any of the four available channels to any other available channel. To create a DCC tunnel, you connect the tunnel endpoints from one ONS 15310-CL or ONS 15310-MA optical port to another.8-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.5.2 IP-Encapsulated Tunnels Table 8-4 shows the DCC tunnels that you can create. When you create DCC tunnels, keep the following guidelines in mind: • An optical port used for a DCC termination cannot be used as a DCC tunnel endpoint, and an optical port that is used as a DCC tunnel endpoint cannot be used as a DCC termination. • All DCC tunnel connections are bidirectional. 8.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. An IP-encapsulated tunnel is a virtual path, which adds protection when traffic travels between different networks. IP-encapsulated tunneling has the potential to flood the DCC network with traffic, which causes CTC performance to degrade. The data originating from an IP tunnel can be throttled to a user-specified rate, which is a percentage of the total SDCC bandwidth. Each ONS 15310-CL or ONS 15310-MA supports one IP-encapsulated tunnel. You can convert a traditional DCC tunnel to an IP-encapsulated tunnel or an IP-encapsulated tunnel to a traditional DCC tunnel. Only tunnels in the Discovered status can be converted. Caution Converting from one tunnel type to the other is service-affecting. 8.6 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 ONS 15310-CL and ONS 15310-MA cards that support VCAT circuits are the CE-100T-8 and ML-100T-8 cards. In a VCAT circuit, circuit bandwidth is divided into smaller circuits called VCAT members. The individual members act as independent TDM circuits. All VCAT members should be the same size and must originate/terminate at the same end points. To enable end-to-end connectivity in a VCAT circuit that traverses through a third-party network, you must create a server trail between the ports. For more details, refer to the "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Table 8-4 DCC Tunnels DCC SONET Layer SONET Bytes OC-3, OC-12 DCC1 Section D1 to D3 Yes DCC2 Line D4 to D6 Yes DCC3 Line D7 to D9 Yes DCC4 Line D10 to D12 Yes8-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.6.1 VCAT Circuit States 8.6.1 VCAT Circuit States The state of a VCAT circuit is an aggregate of its member circuits. You can view whether a VCAT member is In Group or Out of Group in the VCAT State column in the Edit Circuits window. • If all member circuits are IS, the VCAT circuit is IS. • If all In Group member circuits are OOS, the VCAT circuit state is OOS. • If no member circuits exist or if all are Out of Group, the state of a VCAT circuit is OOS. • A VCAT circuit is OOS-PARTIAL when In Group member states are mixed and not all member states are IS. 8.6.2 VCAT Member Routing The automatic and manual routing selection applies to the entire VCAT circuit, that is, all members are manually or automatically routed. Bidirectional VCAT circuits are symmetric, which means that the same number of members travel in each direction. With automatic routing, you can specify the constraints for individual members; with manual routing, you can select different spans for different members. Two types of automatic and manual routing are available for VCAT members on CE-100T-8 and ML-100T-8 cards: common fiber routing and split fiber routing. In common fiber routing, all VCAT members travel on the same fibers, which eliminates delay between members. Three protection options are available for common fiber routing: Fully Protected, PCA, and Unprotected. Split fiber routing allows the individual members to be routed on different fibers or each member to have different routing constraints. This mode offers the greatest bandwidth efficiency and also the possibility of differential delay, which is handled by the buffers on the terminating cards or ports. Three protection options are available for split fiber routing: Fully Protected, Unprotected, and DRI. In both common fiber and split fiber routing, each member can use a different protection scheme; however, for common fiber routing, CTC checks the combination to make sure that a valid route exists. If it does not, the user must modify the protection type. In both common fiber and split fiber routing, intermediate nodes treat the VCAT members as normal circuits that are independently routed and protected by the SONET network. At the terminating nodes, these member circuits are multiplexed into a contiguous stream of data. Figure 8-2 shows an example of common fiber routing. Figure 8-2 VCAT Common Fiber Routing Member 1 VCG-2 Member 2 102170 Intermediate NE Member 1 VCG-1 Member 2 Member 1 VCG-2 Member 2 Member 1 VCG-1 Member 2 VCAT Function VCAT Function VCAT Function VCAT Function STS-1 STS-2 STS-3 STS-4 STS-1 STS-2 STS-3 STS-4 CE-100T-8 CE-100T-88-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.6.3 Link Capacity Adjustment Figure 8-3 shows an example of split fiber routing. Figure 8-3 VCAT Split Fiber Routing 8.6.3 Link Capacity Adjustment The CE-100T-8 and ML-100T-8 cards support the Link Capacity Adjustment Scheme (LCAS), which is a signaling protocol that allows dynamic bandwidth adjustment of VCAT circuits. When a member fails, LCAS temporarily removes the failed member from the VCAT circuit for the duration of the failure, leaving the remaining members to carry the traffic. When the failure clears, the member circuit is automatically added back into the VCAT circuit. You can select LCAS during VCAT circuit creation. Note Although LCAS operations are errorless, a SONET error can affect one or more VCAT members. If this occurs, the VCAT Group Degraded (VCG-DEG) alarm is raised. For information about clearing this alarm, refer to the “Alarm Troubleshooting” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. SW-LCAS is a limited form of LCAS that allows the VCAT circuit to adapt to member failures and keep traffic flowing at a reduced bandwidth. SW-LCAS is necessary when interoperating with the ONS 15454 ML-Series cards. SW-LCAS uses legacy SONET failure indicators like path alarm indication signal (AIS-P) and path remote defect indication (RDI-P) to detect member failure. You can select SW-LCAS during VCAT circuit creation. In addition, you can create non-LCAS VCAT circuits, which do not use LCAS or SW-LCAS. While LCAS and SW-LCAS member cross-connects can be in different service states, all In Group non-LCAS members must have cross-connects in the same service state. A non-LCAS circuit can mix Out of Group and In Group members if the In Group members are in the same service state. Non-LCAS members do not support the OOS-MA,OOG service state; to put a non-LCAS member in the Out of Group VCAT state, use OOS-MA,DSBLD. Note Protection switching for LCAS and non-LCAS VCAT circuits might exceed 60 ms. Traffic loss for VT VCAT circuits is approximately two times more than traffic loss for an STS VCAT circuit. You can minimize traffic loss by reducing path differential delay. 124065 VCAT Function Source VCAT at NE Traffic Traffic Virtually Concatenated Group Member #1 Member #2 Member #3 Intermediate NE VCAT Function with Differential Delay Buffer Destination VCAT at NE Intermediate NE Intermediate NE8-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.6.4 VCAT Circuit Size 8.6.4 VCAT Circuit Size Table 8-5 lists supported VCAT circuit rates and the number of members for each card. Use the Members tab in the Edit Circuit window to add or delete members from a VCAT circuit. The capability to add or delete members depends on whether the VCAT circuit is LCAS, SW-LCAS, or non-LCAS: • For VCAT LCAS circuits, you can add or delete members without affecting service. Before deleting a member, Cisco recommends that you put the member in the OOS-MA,OOG service state. • For SW-LCAS circuits used when interoperating with ONS 15454 ML-Series cards, you cannot add or delete members. • For non-LCAS VCAT circuits that use CE-100T-8 cards, adding and deleting members to/from the circuit is possible, but service-affecting. For ML-100T-8 cards, you cannot add or delete members from non-LCAS VCAT circuits without affecting the entire VCAT circuit. Table 8-6 summarizes the VCAT capabilities for the CE-100T-8 and ML-100T-8 cards. Table 8-5 ONS 15310-CL Card VCAT Circuit Rates and Members Card Circuit Rate Number of Members CE-100T-8 1 1. A VCAT circuit with an ONS 15310-CL or ONS 15310-MA CE-100T-8 or ML-100T-8 card as a source or destination and an ONS 15454 ML-Series card as a source or destination can have only two members. VT1.5 1–64 STS-1 1–3 ML-100T-8 1 STS-1 1–2 Table 8-6 ONS 15310-CL VCAT Card Capabilities Card Mode Add a Member Delete a Member Support OOS-MA,OOG CE-100T-8 LCAS Yes Yes Yes SW-LCAS No No No Non-LCAS Yes1 1. For CE-100T-8 cards, you can add or delete members after creating a VCAT circuit with no protection. During the time it takes to add or delete members (from seconds to minutes), the entire VCAT circuit will be unable to carry traffic. Yes1 No ML-100T-8 LCAS Yes Yes Yes SW-LCAS No No No Non-LCAS No No No8-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.7 Section and Path Trace 8.7 Section and Path Trace SONET J0 section and J1 and J2 path trace are repeated, fixed-length strings composed of 16 or 64 consecutive bytes. You can use the strings to monitor interruptions or changes to circuit traffic. For the ONS 15310-MA node, J0 section trace is supported for optical and EC-1 ports on the CTX2500, DS1-84/DS3-3, or DS1-28/DS3-EC1-3 cards. Table 8-7 shows the ONS 15310-CL and ONS 15310-MA cards and/or ports that support J1 and/or J2 path trace. If the string received at a circuit drop port does not match the string that the port expects to receive, an alarm is raised. Two path trace modes are available: • Automatic—The receiving port assumes that the first string it receives is the baseline string. • Manual—The receiving port uses a string that you manually enter as the baseline string. 8.8 Bridge and Roll The CTC Bridge and Roll wizard reroutes live traffic without interrupting service. The bridge process takes traffic from a designated “roll from” facility and establishes a cross-connect to the designated “roll to” facility. When the bridged signal at the receiving end point is verified, the roll process creates a new cross-connect to receive the new signal. When the roll completes, the original cross-connects are released. You can use the bridge and roll feature for maintenance functions such as card or facility replacement, or for load balancing. You can perform a bridge and roll on the following ONS platforms: ONS 15600, ONS 15454, ONS 15454 SDH, ONS 15327, ONS 15310-CL, and ONS 15310-MA. 8.8.1 Rolls Window The Rolls window lists information about a rolled circuit before the roll process is complete. You can access the Rolls window by clicking the Circuits > Rolls tabs in either network or node view. Figure 8-4 shows the Rolls window. Table 8-7 ONS 15310-CL and ONS 15310-MA Cards/Ports Capable of J1/J2 Path Trace Trace Function J1 or J2 Cards/Ports Transmit and receive J1 ONS 15310-CL DS-1 and DS-3 ports ML-100T-8 J1 and J2 CE-100T-8 J2 ONS 15310-MA OC-N, and DS1 ports Receive J1 ONS 15310-CL EC-1, OC-3, and OC-12 ports ONS 15310-MA OC-N, DS1, and DS3 ports 8-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.8.1 Rolls Window Figure 8-4 Rolls Window The Rolls window information includes: • Roll From Circuit—The circuit with connections that will no longer be used when the roll process is complete. • Roll To Circuit—The circuit that will carry the traffic when 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 “8.8.2 Roll Status” section on page 8-15 for information. • Roll Valid Signal—If the Roll Valid Signal status is true, a valid signal was found on the new port. If the Roll Valid Signal status is false, a valid signal was not found. It is not possible to get a true Roll Valid Signal status for a one-way destination roll. • Roll Mode—The mode indicates whether the roll is automatic or manual. CTC implements a roll mode at the circuit level. TL1 implements a roll mode at the cross-connect level. If a single roll is performed, CTC and TL1 behave the same. If a dual roll is performed, the roll mode specified in CTC might be different than the roll mode retrieved in TL1. For example, if you select Automatic, CTC coordinates the two rolls to minimize possible traffic hits by using the Manual mode behind the scenes. When both rolls have a good signal, CTC signals the nodes to complete the roll. – Automatic—When a valid signal is received on the new path, CTC completes the roll on the node automatically. One-way source rolls are always automatic. – Manual—You must complete a manual roll after a valid signal is received. One-way destination rolls are always manual. • Roll Path—The fixed point of the roll object. • Roll From Path— The old path that is being rerouted. • Roll To Path—The new path where the Roll From Path is rerouted. • Complete—Completes a manual roll after a valid signal is received. You can complete a manual roll if it is in a ROLL_PENDING status and you have not yet completed the roll or have not cancelled its sibling roll. • Force Valid Signal—Forces a roll onto the Roll To Circuit destination without a valid signal. If you choose Force Valid Signal, traffic on the circuit that is involved in the roll will be dropped when the roll is completed. • Finish—Completes the circuit processing of both manual and automatic rolls and changes the circuit status from ROLL_PENDING to DISCOVERED. After a roll, the Finish button also removes any cross-connects that are no longer used from the Roll From Circuit field.8-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.8.2 Roll Status • Cancel—Cancels the roll process. When the roll mode is Manual, cancel roll is only allowed before you click the Complete button. When the roll mode is Auto, cancel roll is only allowed before a good signal is detected by the node or before you click the Force Valid Signal button. 8.8.2 Roll Status Table 8-8 lists the roll statuses. You can only reroute circuits that have a DISCOVERED status. (See Table 8-1 on page 8-3 for a list of circuit statuses.) You cannot reroute circuits that are in the ROLL_PENDING status. 8.8.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 8-5 and Figure 8-6, respectively). • Roll a segment of the circuit onto another chosen circuit (Figure 8-7 on page 8-16). This roll also results in a new destination or a new source. Table 8-8 Roll Statuses State Description ROLL_PENDING The roll is awaiting completion or cancellation. ROLL_COMPLETED The roll is complete. Click the Finish button. ROLL_CANCELLED The roll has been canceled. TL1_ROLL A TL1 roll was initiated. Note If a roll is created using TL1, a CTC user cannot complete or cancel the roll. Also, if a roll is created using CTC, a TL1 user cannot complete or cancel the roll. You must use the same interface to complete or change a roll. INCOMPLETE This state appears when the underlying circuit becomes incomplete. To correct this state, you must fix the underlying circuit problem before the roll state will change. For example, a circuit traveling on Nodes A, B, and C can become INCOMPLETE if Node B is rebooted. The cross connect information is lost on Node B during a reboot. The Roll State on Nodes A and C will change to INCOMPLETE.8-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.8.3 Single and Dual Rolls In Figure 8-5, you can select any available STS on Node 1 for a new source. Figure 8-5 Single Source Roll In Figure 8-6, you can select any available STS on Node 2 for a new destination. Figure 8-6 Single Destination Roll Figure 8-7 shows one circuit rolling onto another circuit at the destination. The new circuit has cross-connects on Node 1, Node 3, and Node 4. CTC deletes the cross-connect on Node 2 after the roll. Figure 8-7 Single Roll from One Circuit to Another Circuit (Destination Changes) 83267 S1 Node 1 S2 Node 2 D Original leg New leg 83266 S Node 1 D2 Node 2 D1 Original leg New leg 78703 S Node 1 D D2 Node 2 Node 3 Node 4 Original leg New leg8-17 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.8.3 Single and Dual Rolls Figure 8-8 shows one circuit rolling onto another circuit at the source. Figure 8-8 Single Roll from One Circuit to Another Circuit (Source Changes) Note Create a Roll To Circuit before rolling a circuit with the source on Node 3 and the destination on Node 4. A dual roll involves two cross-connects. It allows you to reroute intermediate segments of a circuit, but keep the original source and destination. If the new segments require new cross-connects, use the Bridge and Roll wizard or create a new circuit and then perform a roll. Dual rolls have several constraints: • You must complete or cancel both cross-connects rolled in a dual roll. You cannot complete one roll and cancel the other roll. • When a Roll To circuit is involved in the dual roll, the first roll must roll onto the source of the Roll To circuit and the second roll must roll onto the destination of the Roll To circuit. Figure 8-9 illustrates a dual roll on the same circuit. Figure 8-9 Dual Roll to Reroute a Link 134274 S Node 1 Node 2 D Node 3 Node 4 Original leg New leg S2 83268 S Node 1 Node 2 D Original leg New leg8-18 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.8.4 Two-Circuit Bridge and Roll Figure 8-10 illustrates a dual roll involving two circuits. Figure 8-10 Dual Roll to Reroute to a Different Node Note If a new segment is created on Nodes 3 and 4 using the Bridge and Roll wizard, the created circuit has the same name as the original circuit with the suffix _ROLL**. The circuit source is on Node 3 and the circuit destination is on Node 4. 8.8.4 Two-Circuit Bridge and Roll When using the bridge and roll feature to reroute traffic using two circuits, the following constraints apply: • DCC must be enabled on the circuits involved in a roll before roll creation. • A maximum of two rolls can exist between any two circuits. • If two rolls are involved between two circuits, both rolls must be on the original circuit. The second circuit should not carry live traffic. The two rolls loop from the second circuit back to the original circuit. The roll mode of the two rolls must be identical (either automatic or manual). • If a single roll exists on a circuit, you must roll the connection onto the source or the destination of the second circuit and not an intermediate node in the circuit. 8.8.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. However, you cannot roll a single path selector. 8.9 Merged Circuits A circuit merge combines a single selected circuit with one or more circuits. You can merge VT tunnels, VAP circuits, orderwire and user data channel (UDC) overhead circuits, CTC-created traffic circuits, and TL1-created traffic circuits. To merge circuits, you choose a master circuit on the CTC Circuits tab. 83102 S Node 1 Node 2 D Node 3 Node 4 Original leg New leg8-19 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.10 Reconfigured Circuits Then, you choose the circuits that you want to merge with the master circuit on the Merge tab in the Edit Circuits window. The Merge tab shows only the circuits that are available for merging with the master circuit: • Circuit cross-connects must create a single, contiguous path. • Circuits types must be a compatible. For example, you can combine an STS circuit with a VAP circuit to create a longer VAP circuit, but you cannot combine a VT circuit with an STS circuit. • Circuit directions must be compatible. You can merge a one-way and a two-way circuit, but not two one-way circuits in opposing directions. • Circuit sizes must be identical. • Circuit endpoints must send or receive the same framing format. • The merged circuits must become a DISCOVERED circuit. If all connections from the master circuit and all connections from the merged circuits align to form one complete circuit, the merge is successful. If all connections from the master circuit and some, but not all, connections from the other circuits align to form a single complete circuit, CTC notifies you and gives you the chance to cancel the merge process. If you choose to continue, the aligned connections merge successfully into the master circuit, and the unaligned connections remain in the original circuits. All connections in the completed master circuit use the original master circuit name. All connections from the master circuit and at least one connection from the other selected circuits must be used in the resulting circuit for the merge to succeed. If a merge fails, the master circuit and all other circuits remain unchanged. When the circuit merge completes successfully, the resulting circuit retains the name of the master circuit. 8.10 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, CTC-created circuits, and TL1-created circuits. The Reconfigure command maintains the names of the original cross-connects. Use the CTC Tools > Circuits > Reconfigure Circuits command to reconfigure selected circuits. During reconfiguration, CTC reassembles all connections of the selected circuits into circuits based on path size, direction, and alignment. Some circuits might merge and others might split into multiple circuits. If the resulting circuit is a valid circuit, it appears as a DISCOVERED circuit. Otherwise, the circuit appears as a PARTIAL or PARTIAL_TL1 circuit. Note PARTIAL tunnel circuits do not split into multiple circuits during reconfiguration.8-20 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 8 Circuits and Tunnels 8.11 Server Trails 8.11 Server Trails A server trail is a non-DCC link across a third-party network that connects two CTC network domains. A server trail allows circuit provisioning when no DCC is available. You can create server trails between any two optical or DS-3 ports. The end ports on a server trail can be different types. Server trails are not allowed on DCC-enabled ports. The server trail link is bidirectional and can be VT1.5, VT2, STS1, STS-3c, STS-6c, STS-12c, or STS-48c, depending on the port; you cannot upgrade an existing server trail to another size. A server trail link can be one of the following protection types: Preemptible, Unprotected, and Fully Protected. The server trail protection type determines the protection type for any circuits that traverse it. PCA circuits will use server trails with the Preemptible attribute. When creating circuits or VCATs, you can choose a server trail link during manual circuit routing. CTC may also route circuits over server trail links during automatic routing. VCAT common-fiber automatic routing is not supported.CHAPTER 9-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 9 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This chapter explains Cisco ONS 15310-CL and Cisco ONS 15310-MA SONET topologies and upgrades. To provision topologies, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 9.1 Path Protection Dual-Ring Interconnect for the ONS 15310-MA, page 9-1 • 9.2 Terminal Point-to-Point and Linear ADM Configurations, page 9-2 • 9.3 Interoperability, page 9-3 • 9.4 Path-Protected Mesh Networks, page 9-6 • 9.5 Four Node Configurations, page 9-8 • 9.6 OC-N Speed Upgrades, page 9-8 9.1 Path Protection Dual-Ring Interconnect for the ONS 15310-MA The path protection dual-ring interconnect topology (path protection DRI) provides an extra level of path protection between interconnected path protection configurations. In DRIs, traffic is dropped and continued at the interconnecting nodes to eliminate single points of failure. Two DRI topologies can be implemented on the Cisco ONS 15310-MA: the traditional DRI uses four Cisco ONS 15310-MAs at the interconnect nodes, and the integrated DRI uses two nodes. To route circuits on the DRI, you must choose the DRI option during circuit provisioning. Circuits with the DRI option enabled will be routed on the DRI path. 9-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.2 Terminal Point-to-Point and Linear ADM Configurations A hold-off timer sets the amount of time before a selector switch occurs. It reduces the likelihood of multiple switches, such as a service selector and a path selector. For example, if a path protection DRI service selector switch does not restore traffic, then the path selector switches after the hold-off time. The path protection DRI hold-off timer default is 100 ms. You can change this setting in the Path Protection Selectors tab of the Edit Circuits window. 9.2 Terminal Point-to-Point and Linear ADM Configurations You can configure ONS 15310-CLs and Cisco ONS 15310-MAs in a terminal point-to-point network (two nodes) or as a line of add/drop multiplexers (ADMs) (3 or more nodes) by configuring the OC-N ports as the working path and a second set as the protect path. Unlike rings, terminal and linear ADMs require that the OC-N port at each node be in 1+1 protection to ensure that a break to the working line is automatically routed to the protect line. Note In a linear ADM configuration, two OC-N ports in 1+1 protection are connected to two OC-N ports in 1+1 protection on a second node. On the second node, two more OC-N ports are connected to a third node. The third node can be connected to a fourth node, and so on, depending on the number of nodes in the linear ADM. The ONS 15310-CL has only two optical ports. This restricts an ONS 15310-CL to being the end node in a linear ADM network since both ports are necessary to create the 1+1 protection group to the neighbor node. The 15310-MA has four optical ports, so it can operate either as a terminal or intermediate node in a linear ADM network. Figure 9-1 shows two ONS 15310-CLs in a linear ADM configuration with an ONS 15454. In this example, working traffic flows from the ONS 15310 Node 1/Slot 2/Port 2-1 to the ONS 15454 Node 2/Slot 5, and from Node 2/Slot 12 to the ONS 15310 Node 3/Slot 2/Port 2-1. You create the protect path by placing Slot 2/Port 2-1 in 1+1 protection with Slot 2/Port 1-1 at Nodes 1 through 3. Figure 9-1 ONS 15310-CL Linear ADM Configuration Figure 9-2 shows three ONS 15310-MAs in a linear ADM configuration. In this example, working traffic flows from Node 1/Slot 3/Port 2-1 to Node 2/Slot 4/Port 2-1, and from Node 2/Slot 3/Port 2-1 to the Node 3/Slot 4/Port 2-1. You create the protect path by placing Slot 3/Port 2-1 in 1+1 protection with Slot 4/Port 2-2 at Nodes 1 through 3. Node 1 Node 2 Node 3 Slot 2 Port 2-1 to Slot 5 Slot 2 Port 1-1 to Slot 6 Working Path Protect Path 124412 Slot 13 to Slot 2 Port 1-1 Slot 12 to Slot 2 Port 2-1 ONS 15454 ONS 15310-CL ONS 15310-CL9-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.3 Interoperability Figure 9-2 ONS 15310-MA Linear ADM Configuration 9.3 Interoperability The ONS 15310-CL supports up to two SONET SDCCs and one path protection per node. The ONS 15310-MA supports up to four SONET SDCCs and two path protection per node. You can install ONS 15310-CL and ONS 15310-MA nodes into a network comprised entirely of ONS 15310 CL or MA nodes or into a network that has a mix of ONS 15310-CL, ONS 15310-MA, ONS 15454, and ONS 15327 nodes. The ONS 15310-CL and ONS 15310-MA nodes interoperate with the ONS 15454 and ONS 15327 nodes in linear or path protection configurations. Because connection procedures for these types of nodes are the same (for example, adding or dropping nodes from a path protection or linear configuration, or creating DCCs), follow the instructions in the “Add and Remove Nodes” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide whenever you make connections between ONS 15310-CL, ONS 15310-MA, ONS 15454, and ONS 15327 nodes. 9.3.1 Subtending Rings Subtending rings reduce the number of nodes and cards required and reduce external shelf-to-shelf cabling. Figure 9-3 shows an ONS 15454 with two subtending rings using ONS 15310-CL nodes. Figure 9-3 ONS 15454 with Two ONS 15310-CL Nodes Subtending Path Protections Figure 9-4 shows an ONS 15310-MA with two subtending rings path protection configurations. Node 1 Node 2 Node 3 Slot 3 Port 2-1 to Slot 4 Port 2-1 Working Path Protect Path 145753 Slot 3 Port 2-1 to Slot 4 Port 2-1 ONS 15310-MA ONS 15310-MA ONS 15310-MA Slot 3 Port 2-2 to Slot 4 Port 2-2 Slot 3 Port 2-2 to Slot 4 Port 2-2 ONS 15454 124459 ONS 15310 ONS 153109-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.3.1 Subtending Rings Figure 9-4 ONS 15310-MA with Two Subtending Path Protection Configurations Figure 9-5 shows a ring of ONS 15310-CL nodes subtended from a ring of ONS 15454 nodes. Figure 9-5 ONS 15310-CL Ring Subtended from an ONS 15454 Ring Figure 9-6 shows a ring of ONS 15310-MA nodes subtended from a ring of ONS 15454 nodes. 145954 ONS 15310-MA ONS 15310-MA ONS 15310-MA ONS 15454 ONS 15454 ONS 15454 ONS 15454 BLSR ONS 15310-CL ONS 15310-CL OC-3 or OC-12 OC-3 or OC-12 1244619-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.3.2 Linear Connections Figure 9-6 ONS 15310-MA Ring Subtended from an ONS 15454 Ring 9.3.2 Linear Connections Figure 9-7 shows a basic linear or path protection connection between ONS 15310-CL and ONS 15454 nodes. Note Please note that Figure 9-7 shows an ONS 15310-CL node, however; the illustration can be applied to both the ONS 15310-CL and ONS 15310-MA nodes. Figure 9-7 Linear or Path Protection Connection Between ONS 15454 and ONS 15310 or ONS 15310-MA Nodes ONS 15454 ONS 15454 ONS 15454 ONS 15454 BLSR ONS 15310-MA ONS 15310-MA OC-3, OC-12, or OC-48 OC-3, OC-12, or OC-48 145955 1+1 Linear (Point-to-Point) ONS 15310 ONS 15454 1244609-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.4 Path-Protected Mesh Networks 9.4 Path-Protected Mesh Networks In addition to single path protection configurations, terminal point-to-point or linear ADMs, you can extend ONS 15310-CL and ONS 15310-MA traffic protection by creating path-protected mesh networks (PPMNs). PPMNs include multiple ONS 15310-CL and ONS 15310-MA SONET topologies and extend the protection provided by a single path protection to the meshed architecture of several interconnecting rings. In a PPMN, circuits travel diverse paths through a network of single or multiple meshed rings. When you create circuits, CTC can automatically route circuits across the PPMN or you can manually route them. You can also choose levels of circuit protection. For example, if you choose full protection, CTC creates an alternate route for the circuit in addition to the main route. The second route follows a unique path through the network between the source and destination and sets up a second set of cross-connections. For example, in Figure 9-8, a circuit is created from the ONS 15454 shown at Node 3 to the ONS 15454 shown at Node 9. CTC determines that the shortest route between the two nodes passes through Node 8 and Node 7, shown by the dotted line, and automatically creates cross-connections at Nodes 3, 8, 7, and 9 to provide the primary circuit path. If full protection is selected, CTC creates a second unique route between Nodes 3 and 9 which, in this example, passes through Nodes 2, 1, and 11. Cross-connections are automatically created at Nodes 3, 2, 1, 11, and 9, shown by the dashed line. If a failure occurs on the primary path, traffic switches to the second circuit path. In this example, Node 9 switches from the traffic coming in from Node 7 to the traffic coming in from Node 11 and service resumes. The switch occurs within 50 ms. Figure 9-8 Path-Protected Mesh Network for ONS 15310-CL Nodes = Primary path = Secondary path Working tr Protect traffic affic Source Node Destination Node 124462 Node 1 Node 11 Node 2 Node 4 Node 5 Node 6 Node 7 Node 10 Node 8 Node 9 Node 39-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.4 Path-Protected Mesh Networks For example, in Figure 9-9, a circuit is created from Node 3 to Node 9. CTC determines that the shortest route between the two nodes passes through Node 8 and Node 7, shown by the dotted line, and automatically creates cross-connections at Nodes 3, 8, 7, and 9 to provide the primary circuit path. If full protection is selected, CTC creates a second unique route between Nodes 3 and 9 which, in this example, passes through Nodes 2, 1, and 11. Cross-connections are automatically created at Nodes 3, 2, 1, 11, and 9, shown by the dashed line. If a failure occurs on the primary path, traffic switches to the second circuit path. In this example, Node 9 switches from the traffic coming in from Node 7 to the traffic coming in from Node 11 and service resumes. The switch occurs within 50 ms. Figure 9-9 Path-Protected Mesh Network for ONS 15310-MA Nodes PPMN also allows spans with different SONET speeds to be mixed together in “virtual rings.” Figure 9-10 shows an ONS 15310-MA with Nodes 1, 2, 3, and 4 in a standard OC-48 ring. Nodes 5, 6, 7, and 8 link to the backbone ring through the OC-12 fiber. The virtual ring formed by Nodes 5, 6, 7, and 8 use both the OC-48 and OC-12 cards. = Primary path = Secondary path Working tr Protect traffic affic Source Node Destination Node 145956 Node 1 Node 11 Node 2 Node 4 Node 5 Node 6 Node 7 Node 10 Node 8 Node 9 Node 39-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.5 Four Node Configurations Figure 9-10 Virtual Ring for ONS 15310-MAs 9.5 Four Node Configurations You can link multiple ONS 15310-CL or ONS 15310-MA nodes using their OC-N ports (also known as creating a fiber-optic bus) to accommodate more access traffic than a single ONS 15310-CL or ONS 15310-MA can support. For example, to drop more than 21 DS-1s or 3 DS-3s (the maximum that can be aggregated in a single ONS 15310-CL node), you can link the nodes but not merge multiple nodes into a single ONS 15310-CL. You can link nodes with OC-N fiber spans as you would link any other two network nodes. The nodes can be grouped in one facility to aggregate more local traffic. 9.6 OC-N Speed Upgrades A span is the optical fiber connection between two ONS 15310-CL or ONS 15310-MA nodes. In a span (optical speed) upgrade, the transmission rate of a span is upgraded from an OC-3 to OC-12 signal (ONS 15310-CL or ONS 15310-MA), from an OC-12 to OC-48 signal (ONS 15310-MA only), or from an OC-3 to OC-48 signal (ONS 15310-MA only), but all other span configuration attributes remain unchanged. With multiple nodes, a span upgrade is a coordinated series of upgrades on all nodes in the ring or protection group. The ONS 15310-CL nodes support the span upgrade wizard if you are upgrading two ONS 15310-CLs with 1+1 protection from OC-3 to OC-12. The ONS 15310-MA nodes support the span upgrade wizard if you are upgrading two ONS 15310-MAs with 1+1 protection from OC-3 to OC-12, OC-12 to OC-48, or OC-3 to OC-48. To perform a span upgrade, the higher-rate pluggable port module (PPM) must replace the lower-rate PPM in the same slot. If you are using a multi-rate PPM, you do not need to physically replace the PPM. All spans in the network must be upgraded. The 1+1 protection configuration of the original lower-rate PPM is retained for the higher-rate PPM. OC-12 OC-48 OC-12 145957 ONS 15310-MA Node 5 ONS 1510-MA Node 1 ONS 15310-MA Node 6 ONS 15310-MA Node 2 ONS 15310-MA Node 4 ONS 15310-MA Node 8 ONS 15310-MA Node 3 ONS 15310-MA Node 79-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.6.1 Span Upgrade Wizard When performing span upgrades, Cisco recommends that you upgrade all spans in a network consecutively and in the same maintenance window. Until all spans are upgraded, mismatched PPM types will be present. If you are upgrading two ONS 15310-CL nodes with 1+1 protection from OC-3 to OC-12, or two ONS 15310-MA nodes with 1+1 protection from OC-3 to OC-12, OC-12 to OC-48, or OC-3 to OC-48, Cisco recommends using the Span Upgrade Wizard to perform span upgrades. Although you can also use the manual span upgrade procedures, the manual procedures are mainly provided as error recovery for the wizard. The Span Upgrade Wizard and the manual span upgrade procedures require at least two technicians (one at each end of the span) who can communicate with each other during the upgrade. Upgrading a span is non-service affecting and will cause no more than three switches, each of which is less than 50 ms in duration. To initiate the span upgrade, right-click the span and choose Span Upgrade. Note Span upgrades do not upgrade SONET topologies (for example, a 1+1 group to a path protection). Refer to the “Convert Network Configurations” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for topology upgrade procedures. 9.6.1 Span Upgrade Wizard The Span Upgrade Wizard automates all steps in the manual 1+1 span upgrade procedure, if you are upgrading two ONS 15310-CL or ONS 15310-MA nodes. The wizard can upgrade both lines of a 1+1 group. The Span Upgrade Wizard requires that spans have DCCs enabled. The Span Upgrade Wizard provides no way to back out of an upgrade. In the case of an error, you must exit the wizard and initiate the manual procedure to either continue with the upgrade or back out of it. To continue with the manual procedure, examine the standing conditions and alarms to identify the stage in which the wizard failure occurred. 9.6.2 Manual Span Upgrades Manual span upgrades are mainly provided as error recovery for the Span Upgrade Wizard, but they can be used to perform span upgrades. You can perform a manual span upgrade on a 1+1 protection group, if you are upgrading two ONS 15310-CL or ONS 15310-MA nodes. Downgrading can be performed to back out of a span upgrade. The procedure for downgrading is the same as upgrading except that you provision a lower-rate PPM (OC-3 for the ONS 15310-CL, or OC-3 or OC12 for the 15310-MA) and install a lower-rate PPM (if you are not using a multi-rate PPM). You cannot downgrade if circuits exist on the STSs that will be removed (the higher STSs).9-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 9 SONET Topologies and Upgrades 9.6.2 Manual Span UpgradesCHAPTER 10-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 10 Management Network Connectivity This chapter provides an overview of Cisco ONS 15310-CL and Cisco ONS 15310-MA 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 15310-CL or ONS 15310-MA nodes, and communication among networked ONS 15310-CL or ONS 15310-MA nodes. The chapter provides scenarios showing ONS 15310-CL and ONS 15310-MA nodes in common IP network configurations as well as information about provisionable patchcords, the IP routing table, external firewalls, and open gateway network element (GNE) networks. Although ONS 15310-CL and ONS 15310-MA DCN communication is based on IP, ONS 15310-CL and ONS 15310-MA nodes can be networked to equipment that is based on the Open System Interconnection (OSI) protocol suites. This chapter describes the OSI implementation and provides scenarios that show how the ONS 15310-CL and ONS 15310-MA can be networked within a mixed IP and OSI environment. Chapter topics include: • 10.1 IP Networking Overview, page 10-2 • 10.2 IP Addressing Scenarios, page 10-2 • 10.3 Provisionable Patchcords, page 10-16 • 10.4 Routing Table, page 10-17 • 10.5 External Firewalls, page 10-18 • 10.6 Open GNE, page 10-20 • 10.7 TCP/IP and OSI Networking, page 10-22 Note This chapter does not provide a comprehensive explanation of IP networking concepts and procedures, nor does it provide IP addressing examples to meet all networked scenarios. For networking setup instructions, refer to the “Turn Up a Node” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Note To connect ONS 15310-CL or ONS 15310-MA nodes to an IP network, you must work with a LAN administrator or other individual at your site who has IP networking training and experience. 10-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.1 IP Networking Overview 10.1 IP Networking Overview ONS 15310-CL and ONS 15310-MA nodes can be connected in many different ways within an IP environment: • They can be connected to LANs through direct connections or a router. • IP subnetting can create ONS 15310-CL or ONS 15310-MA login node groups, which allow you to provision non-data communications channel (DCC) connected nodes in a network. • Different IP functions and protocols can be used to achieve specific network goals. For example, Proxy Address Resolution Protocol (ARP) enables one LAN-connected ONS 15310-CL or ONS 15310-MA to serve as a gateway for ONS 15310-CL or ONS 15310-MA nodes that are not connected to the LAN. • You can create static routes to enable connections among multiple Cisco Transport Controller (CTC) sessions with ONS 15310-CL or ONS 15310-MA nodes that reside on the same subnet with multiple CTC sessions. • If ONS 15310-CL or ONS 15310-MA nodes are connected to Open Shortest Path First (OSPF) networks, ONS 15310-CL or ONS 15310-MA network information is automatically communicated across multiple LANs and WANs. • The ONS 15310-CL and ONS 15310-MA proxy server controls the visibility and accessibility between CTC computers and ONS 15310-CL or ONS 15310-MA element nodes. 10.2 IP Addressing Scenarios ONS 15310-CL and ONS 15310-MA IP addressing generally has seven common scenarios or configurations. Use the scenarios as building blocks for more complex network configurations. Table 10-1 provides a general list of items to check when setting up ONS 15310-CL or ONS 15310-MA nodes in IP networks. Table 10-1 General P Troubleshooting Checklist Item What to Check Link integrity Verify that link integrity exists between: • CTC computer and network hub/switch • ONS 15310-CL or ONS 15310-MA nodes (RJ-45 ports labeled LAN) and network hub/switch • Router ports and hub/switch ports Node hub/switch ports Verify connectivity. If connectivity problems occur, set the hub or switch port that is connected to the ONS 15310-CL or ONS 15310-MA to 10 Mbps half-duplex. Ping Ping the node to test connections between computers and ONS 15310-CL or ONS 15310-MA nodes. IP addresses/subnet masks Verify that ONS 15310-CL or ONS 15310-MA IP addresses and subnet masks are set up correctly. Optical connectivity Verify that ONS 15310-CL or ONS 15310-MA optical trunk ports are in service and that a DCC is enabled on each trunk port.10-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.1 Scenario 1: CTC and ONS 15310-CL or ONS 15310-MA Nodes on the Same Subnet 10.2.1 Scenario 1: CTC and ONS 15310-CL or ONS 15310-MA Nodes on the Same Subnet Scenario 1 shows a basic ONS 15310-CL or ONS 15310-MA LAN configuration (Figure 10-1). The ONS 15310-CL or ONS 15310-MA nodes and CTC computer reside on the same subnet. All nodes connect to LAN A and have DCC connections. Figure 10-1 Scenario 1: CTC and ONS 15310-CL or ONS 15310-MA Nodes on the Same Subnet 10.2.2 Scenario 2: CTC and ONS 15310-CL or ONS 15310-MA Nodes Connected to a Router In Scenario 2 the CTC computer resides on a subnet (192.168.1.0) and attaches to LAN A (Figure 10-2). The ONS 15310-CL or ONS 15310-MA nodes reside on a different subnet (192.168.2.0) and attach to LAN B. A router connects LAN A to LAN B. The IP address of router interface A is set to LAN A (192.168.1.1), and the IP address of router interface B is set to LAN B (192.168.2.1). On the CTC computer, the default gateway is set to router interface A. If the LAN uses Dynamic Host Configuration Protocol (DHCP), the default gateway and IP address are assigned automatically. In Figure 10-2, a DHCP server is not available. CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = N/A Host Routes = N/A ONS 15310 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #2 IP Address 192.168.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN A SONET RING 12469110-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.3 Scenario 3: Using Proxy ARP to Enable an ONS 15310-CL or ONS 15310-MA Gateway Figure 10-2 Scenario 2: CTC and ONS 15310-CL or ONS 15310-MA Nodes Connected to Router 10.2.3 Scenario 3: Using Proxy ARP to Enable an ONS 15310-CL or ONS15310-MA Gateway ARP matches higher-level IP addresses to the physical addresses of the destination host. It uses a lookup table (called ARP cache) to perform the translation. When the address is not found in the ARP cache, a broadcast is sent out on the network with a special format called the ARP request. If one of the machines on the network recognizes its own IP address in the request, it sends an ARP reply back to the requesting host. The reply contains the physical hardware address of the receiving host. The requesting host stores this address in its ARP cache so that all subsequent datagrams (packets) to this destination IP address can be translated to a physical address. Proxy ARP enables one LAN-connected ONS 15310-CL or ONS 15310-MA to respond to the ARP request for ONS 15310-CL or ONS 15310-MA nodes not connected to the LAN. (Proxy ARP requires no user configuration.) For the proxy ARP node to require no user confirmation, the DCC-connected nodes must reside on the same subnet. When a LAN device sends an ARP request to an ONS 15310-CL or ONS 15310-MA that is not connected to the LAN, the gateway ONS 15310-CL or ONS 15310-MA returns its MAC address to the LAN device. The LAN device then sends the datagram for the remote ONS 15310-CL or ONS 15310-MA to the MAC address of the proxy node. The proxy ONS 15310-CL or ONS 15310-MA uses its routing table to forward the datagram to the non-LAN ONS 15310-CL or ONS 15310-MA. 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 Default Router = N/A Host Routes = N/A ONS 15310 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A ONS 15310 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A ONS 15310 #3 IP Address 192.168.2.30 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A LAN B LAN A Int "A" Int "B" SONET RING 12469210-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.3 Scenario 3: Using Proxy ARP to Enable an ONS 15310-CL or ONS 15310-MA Gateway Scenario 3 is similar to Scenario 1, but only one ONS 15310-CL or ONS 15310-MA node (#1) connects to the LAN (Figure 10-3). Two ONS 15310-CL or ONS 15310-MA nodes (#2 and #3) connect to Node 1 through the SONET DCC. Because all three nodes are on the same subnet, Proxy ARP enables Node 1 to serve as a gateway for Nodes 2 and 3. Note This scenario assumes all CTC connections are to Node 1. If you connect a laptop to either Node 2 or Node 3, network partitioning occurs, and neither the laptop or the CTC computer is able to see all nodes. If you want laptops to connect directly to end network elements, you need to create static routes (see Scenario 5) or enable the ONS 15310-CL or ONS 15310-MA proxy server (see Scenario 7). Figure 10-3 Scenario 3: Using Proxy ARP You can also use proxy ARP to communicate with hosts attached to the craft Ethernet ports of DCC-connected nodes (Figure 10-4). The node with an attached host must have a static route to the host. Static routes are propagated to all DCC peers using OSPF. The existing proxy ARP node is the gateway for additional hosts. Each node examines its routing table for routes to hosts that are not connected to the DCC network but are within the subnet. The existing proxy server replies to ARP requests for these additional hosts with the node MAC address. The existence of the host route in the routing table ensures that the IP packets addressed to the additional hosts are routed properly. Other than establishing a static route between a node and an additional host, no provisioning is necessary. The following restrictions apply: • Only one node acts as the proxy ARP server for any given additional host. • A node cannot be the proxy ARP server for a host connected to its Ethernet port. In Figure 10-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 can be set up as an additional host. CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = N/A ONS 15310 #2 IP Address 192.168.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN A SONET RING 12469310-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.4 Scenario 4: Default Gateway on CTC Computer Figure 10-4 Scenario 3: Using Proxy ARP with Static Routing 10.2.4 Scenario 4: Default Gateway on CTC Computer Scenario 4 is similar to Scenario 3, but ONS 15310-CL or ONS 15310-MA Node 2 and Node 3 reside on different subnets, 192.168.2.0 and 192.168.3.0, respectively (Figure 10-5). Node 1 and the CTC computer are on subnet 192.168.1.0. Proxy ARP is not used because the network includes different subnets. For the CTC computer to communicate with Nodes 2 and 3, Node 1 is entered as the default gateway on the CTC computer. CTC Workstation IP Address 192.168.1.100 Subnet Mark at CTC Workstation 255.255.255.0 Default Gateway = N/A ONS 15310 #2 IP Address 192.168.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = Destination 192.168.1.100 Mask 255.255.255.0 Next Hop 192.168.1.10 ONS 15310 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = Destination 192.168.1.31 Mask 255.255.255.255 Next Hop 192.168.1.30 ONS 152xx IP Address 192.168.1.31 Subnet Mask 255.255.255.0 LAN A SONET RING 12468810-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.5 Scenario 5: Using Static Routes to Connect to LANs Figure 10-5 Scenario 4: Default Gateway on a CTC Computer 10.2.5 Scenario 5: Using Static Routes to Connect to LANs Static routes are used for two purposes: • To connect ONS 15310-CL or ONS 15310-MA nodes to CTC sessions on one subnet that are connected by a router to ONS 15310-CL or ONS 15310-MA nodes residing on another subnet. (These static routes are not needed if OSPF is enabled. Scenario 6 shows an OSPF example.) • To enable multiple CTC sessions among ONS 15310-CL or ONS 15310-MA nodes residing on the same subnet. In Figure 10-6, one CTC residing on subnet 192.168.1.0 connects to a router through interface A. (The router is not set up with OSPF.) ONS 15310-CL or ONS 15310-MA nodes residing on different subnets are connected through Node 1 to the router through interface B. Because Nodes 2 and 3 are on different subnets, proxy ARP does not enable Node 1 as a gateway. To connect to CTC computers on LAN A, a static route is created on Node 1. CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.10 Host Routes = N/A ONS 15310 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #3 IP Address 192.168.3.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN A SONET RING 12469410-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.5 Scenario 5: Using Static Routes to Connect to LANs Figure 10-6 Scenario 5: Static Route with One CTC Computer Used as a Destination The destination and subnet mask entries control access to the ONS 15310-CL or ONS 15310-MA nodes: • If a single CTC computer is connected to a router, enter the complete CTC “host route” IP address as the destination with a subnet mask of 255.255.255.255. • If CTC computers on a subnet are connected to a router, enter the destination subnet (in this example, 192.168.1.0) and a subnet mask of 255.255.255.0. • If all CTC computers are connected to a router, enter a destination of 0.0.0.0 and a subnet mask of 0.0.0.0. Figure 10-7 shows an example. The IP address of router interface B is entered as the next hop, and the cost (number of hops from source to destination) is 2. 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 Default Router = N/A Static Routes = Destination 192.168.3.20 Gateway 192.168.2.10 Destination 192.168.4.30 Gateway 192.168.2.10 ONS 15310 #2 IP Address 192.168.3.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = Destination 192.168.1.100 Mask 255.255.255.255 Next Hop 192.168.2.1 Cost = 2 ONS 15310 #3 IP Address 192.168.4.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" SONET RING 12469510-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.6 Scenario 6: Using OSPF Figure 10-7 Scenario 5: Static Route with Multiple LAN Destinations 10.2.6 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. Each link state router captures the link state “advertisements” and puts them together to create a topology of the entire network or area. From this database, the router calculates a routing table by constructing a shortest path tree. Routes are recalculated when topology changes occur. The ONS 15310-CL or ONS 15310-MA uses OSPF protocol in internal ONS 15310-CL or ONS 15310-MA networks for node discovery, circuit routing, and node management. You can enable OSPF on the ONS 15310-CL or ONS 15310-MA so that the ONS 15310-CL or ONS 15310-MA topology is 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 #1 IP Address of interface ”A” to LAN “A” 192.168.1.1 IP Address of interface “B” to LAN “B” 192.168.2.1 Subnet Mask 255.255.255.0 ONS 15310 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 ONS 15310 #3 IP Address 192.168.2.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" SONET RING Static Routes Destination 0.0.0.0 Mask 0.0.0.0 Next Hop 192.168.2.1 Cost = 2 LAN C LAN D Router #3 Router #2 12489910-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.6 Scenario 6: Using OSPF sent to OSPF routers on a LAN. Advertising the ONS 15310-CL or ONS 15310-MA network topology to LAN routers eliminates the need to enter static routes for ONS 15310-CL or ONS 15310-MA subnetworks manually. OSPF divides networks into smaller regions, called areas. An area is a collection of networked end systems, routers, and transmission facilities organized by traffic patterns. Each OSPF area has a unique ID number, known as the area ID. Every OSPF network has one backbone area called “area 0.” All other OSPF areas must connect to area 0. When you enable an ONS 15310-CL or ONS 15310-MA OSPF topology for advertising to an OSPF network, you must assign an OSPF area ID in decimal format to the network. Coordinate the area ID number assignment with your LAN administrator. All DCC-connected ONS 15310-CL or ONS 15310-MA nodes should be assigned the same OSPF area ID. Figure 10-8 shows a network enabled for OSPF. Figure 10-8 Scenario 6: OSPF Enabled Figure 10-9 shows the same network without OSPF. Static routes must be manually added to the router for CTC computers on LAN A to communicate with Nodes 2 and 3 because these nodes reside on different subnets. 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 ONS 15310 #2 IP Address 192.168.3.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A ONS 15310 #3 IP Address 192.168.4.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" SONET RING 12469610-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server Figure 10-9 Scenario 6: OSPF Not Enabled 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server The ONS 15310-CL or ONS 15310-MA proxy server is a set of functions that allows you to network ONS 15310-CL or ONS 15310-MA nodes in environments where visibility and accessibility between nodes and CTC computers must be restricted. For example, you can set up a network so that field technicians and network operating center (NOC) personnel can both access the same nodes while preventing the field technicians from accessing the NOC LAN. To do this, one ONS 15310-CL or ONS 15310-MA node is provisioned as a gateway network element (GNE) and the other nodes are provisioned as end network elements (ENEs). The GNE tunnels connections between CTC computers and ENEs, which provides management capability while preventing access for non-ONS 15310-CL or ONS 15310-MA management purposes. CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.1 Host Routes = N/A Router IP Address of interface “A” to LAN A 192.168.1.1 IP Address of interface “B” to LAN B 192.168.2.1 Subnet Mask 255.255.255.0 Static Routes = Destination 192.168.3.20 Next Hop 192.168.2.10 Destination 192.168.4.30 Next Hop 192.168.2.10 ONS 15310 #2 IP Address 192.168.3.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15310 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes Destination = 192.168.1.100 Mask = 255.255.255.255 Next Hop = 192.168.2.1 Cost = 2 ONS 15310 #3 IP Address 192.168.4.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" SONET RING 12480010-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server The ONS 15310-CL or ONS 15310-MA proxy server performs the following tasks: • Isolates DCC IP traffic from Ethernet (CRAFT port) traffic and accepts packets based on filtering rules. The filtering rules depend on whether the packet arrives at the DCC or CRAFT port Ethernet interface. Table 10-3 on page 10-15 and Table 10-4 on page 10-16 provide the filtering rules. • Processes SNTP (Simple Network Timing Protocol) and NTP (Network Timing Protocol) requests. Element ONS 15310-CL or ONS 15310-MA NEs can derive time-of-day from an SNTP/NTP LAN server through the GNE. • Process SNMPv1 traps. The GNE receives SNMPv1 traps from the ENE and forwards them to all provisioned SNMPv1 trap destinations. The ONS 15310-CL or ONS 15310-MA proxy server is provisioned using the Enable proxy server on port check box on the Provisioning > Network > General tab. If checked, the ONS 15310-CL or ONS 15310-MA serves as a proxy for connections between CTC clients and ONS 15310-CL or ONS 15310-MA nodes that are DCC-connected to the proxy ONS 15310-CL or ONS 15310-MA. The CTC client establishes connections to DCC-connected nodes through the proxy node. The CTC client can connect to nodes that it cannot directly reach from the host on which it runs. If the Enable proxy server on port check box is not checked, the node does not proxy for any CTC clients, although any established proxy connections continue until the CTC client exits. In addition, you can set the proxy server as an ENE or a GNE: Note If you launch CTC against a node through a NAT (Network Address Translation) or PAT (Port Address Translation) router and that node does not have proxy enabled, your CTC session starts and initially appears to be fine. However CTC never receives alarm updates and disconnects and reconnects every two minutes. If the proxy is accidentally disabled, it is still possible to enable the proxy during a reconnect cycle and recover your ability to manage the node, even through a NAT/PAT firewall. • External Network Element (ENE)—If set as an ENE, the ONS 15310-CL or ONS 15310-MA neither installs nor advertises default or static routes. CTC computers can communicate with the node using the craft port, but they cannot communicate directly with any other DCC-connected node. In addition, firewall is enabled, which means that the node prevents IP traffic from being routed between the DCC and the LAN port. The ONS 15310-CL or ONS 15310-MA can communicate with machines connected to the LAN port or connected through the DCC. However, the DCC-connected machines cannot communicate with the LAN-connected machines, and the LAN-connected machines cannot communicate with the DCC-connected machines. A CTC client using the LAN to connect to the firewall-enabled node can use the proxy capability to manage the DCC-connected nodes that would otherwise be unreachable. A CTC client connected to a DCC-connected node can only manage other DCC-connected nodes and the firewall itself. • Gateway Network Element (GNE)—If set as a GNE, the CTC computer is visible to other DCC-connected nodes and firewall is enabled. • Proxy-only—If Proxy-only is selected, CTC cannot communicate with any other DCC-connected ONS 15310-CL or ONS 15310-MA nodes and firewall is not enabled. Figure 10-10 shows an ONS 15310-CL or ONS 15310-MA proxy server implementation. A GNE is connected to a central office LAN and to ENEs. The central office LAN is connected to a NOC LAN, which has CTC computers. The NOC CTC computer and craft technicians must both be able to access the ENEs. However, the craft technicians must be prevented from accessing or seeing the NOC or central office LANs.10-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server In the example, the GNE is assigned an IP address within the central office LAN and is physically connected to the LAN through its LAN port. ENEs are assigned IP addresses that are outside the central office LAN and given private network IP addresses. If the ENEs are collocated, the LAN ports could be connected to a hub. However, the hub should have no other network connections. Figure 10-10 ONS 15310-CL or ONS 15310-MA Proxy Server with GNE and ENEs on the Same Subnet Table 10-2 shows recommended settings for ONS 15310-CL or ONS 15310-MA GNEs and ENEs in the configuration shown in Figure 10-10. Figure 10-11 shows the same proxy server implementation with ONS 15310-CL or ONS 15310-MA ENEs on different subnets. In this example, GNEs and ENEs are provisioned with the settings shown in Table 10-2. NOC CTC station Local CTC station IP 10.10.10.10 NOC LAN 97.1.1.x Interface 0/0 97.1.1.1 Interface 0/1 86.1.1.1 Interface 0/1 192.168.20.1 ONS 15310 GNE IP 192.168.20.20 Default gateway 192.168.20.1 Interface 0/0 86.1.1.3 ONS 15310 ENE ONS 15310 ENE ONS 15310 ENE IP 192.168.20.0/24 Central Office LAN 86.x.x.x 124697 Table 10-2 ONS 15310-CL or ONS 15310-MA GNE and ENE Settings Setting ONS 15310-CL and ONS 15310-MA GNE ONS 15310-CL and ONS 15310-MA ENE OSPF Off Off SNTP Server (if used) SNTP server IP address Set to node GNE IP address SNMP (if used) SNMPv1 trap destinations Set SNMPv1 trap destinations to node GNE10-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server Figure 10-11 Scenario 7: Proxy Server with GNE and ENEs on Different Subnets Figure 10-12 shows the implementation with ONS 15310-CL or ONS 15310-MA ENEs in multiple rings. In this example, GNEs and ENEs are provisioned with the settings shown in Table 10-2. NOC CTC station Local CTC station IP 10.10.10.10 NOC LAN 97.1.1.x Interface 0/0 97.1.1.1 Interface 0/1 86.1.1.1 ONS 15310 GNE IP 86.10.10.100 Default gateway 86.1.1.1 ONS 15310 ENE ONS 15310 ENE ONS 15310 ENE IP 192.168.0.0/24 Central Office LAN 86.x.x.x 12469810-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.2.7 Scenario 7: Provisioning the ONS 15310-CL or ONS 15310-MA Proxy Server Figure 10-12 Scenario 7: Proxy Server with ENEs on Multiple Rings Table 10-3 shows the rules the ONS 15310-CL or ONS 15310-MA follows to filter packets when Enable Firewall is enabled. Table 10-4 shows additional rules that apply if the packet addressed to the ONS 15310-CL or ONS 15310-MA is discarded. Rejected packets are silently discarded. NOC CTC station NOC LAN 97.1.1.x Interface 0/0 97.1.1.1 Interface 0/1 86.1.1.1 Switch ONS 15310 GNE ONS 15310 ENE ONS 15310 ENE IP 192.168.0.0/24 Central Office LAN 86.x.x.x ONS 15310 GNE ONS 15310 ENE Local CTC station IP 10.10.10.10 ONS 15310 ENE ONS 15310 ENE IP 192.0.0.0/24 ONS 15310 ENE 124699 Table 10-3 Proxy Server Firewall Filtering Rules Packets arriving at: Are accepted if the IP destination address is: 15310-CL-CTX or CTX2500 Ethernet interface • The ONS 15310-CL or ONS 15310-MA shelf itself • The ONS 15310-CL or ONS 15310-MA’s subnet broadcast address • Within the 224.0.0.0/8 network (reserved network used for standard multicast messages) • Subnet mask = 255.255.255.255 DCC interface • The ONS 15310-CL or ONS 15310-MA itself • Any destination that is connected through another DCC interface • Within the 224.0.0.0/8 network10-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.3 Provisionable Patchcords If you implement the proxy server, keep the following rules in mind: 1. All DCC-connected ONS 15310-CL or ONS 15310-MA nodes on the same Ethernet segment must have the same Craft Access Only setting. Mixed values produce unpredictable results, and might leave some nodes unreachable through the shared Ethernet segment. 2. All DCC-connected ONS 15310-CL or ONS 15310-MA nodes on the same Ethernet segment must have the same Enable Firewall setting. Mixed values produce unpredictable results. Some nodes might become unreachable. 3. If you check Enable Firewall, always check Enable Proxy. If Enable Proxy is unchecked, CTC is not able to see nodes on the DCC side of the ONS 15310-CL or ONS 15310-MA. 4. If Craft Access Only is checked, check Enable Proxy. If Enable Proxy is not checked, CTC is not able to see nodes on the DCC side of the ONS 15310-CL or ONS 15310-MA. If nodes become unreachable in cases 1, 2, and 3, you can correct the setting with one of the following actions: • Disconnect the craft computer from the unreachable ONS 15310-CL or ONS 15310-MA. Connect to the ONS 15310-CL or ONS 15310-MA through another ONS 15310-CL or ONS 15310-MA in the network that has a DCC connection to the unreachable node. • Disconnect the Ethernet cable from the unreachable ONS 15310-CL or ONS 15310-MA. Connect a CTC computer directly to the ONS 15310-CL or ONS 15310-MA. 10.3 Provisionable Patchcords A provisionable patchcord is a user-provisioned link that is advertised by OSPF throughout the network. Provisionable patchcords, also called virtual links, are needed if an ONS 15310-CL or ONS 15310-MA optical port is connected to an ONS 15454 transponder or muxponder client port provisioned in transparent mode. Provisionable patchcords are required on both ends of a physical link. The provisioning at each end includes a local patchcord ID, slot/port information, remote IP address, and remote patchcord ID. Patchcords appear as dashed lines in CTC network view. Table 10-4 Proxy Server Firewall Filtering Rules When the Packet is Addressed to the ONS 15310-CL or ONS 15310-MA Packets Arrive At Accepts Rejects 15310-CL-CTX or CTX2500 LAN port • All User Datagram Protocol (UDP) packets except those in the Rejected column • UDP packets addressed to the SNMP trap relay port (391) DCC interface • All UDP packets • All TCP packets except those packets addressed to the Telnet and SOCKS proxy server ports • OSPF packets • Internet Control Message Protocol (ICMP) packets • TCP packets addressed to the Telnet port • TCP packets addressed to the proxy server port • All packets other than UDP, TCP, OSPF, ICMP10-17 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.4 Routing Table Table 10-5 lists the supported combinations for ONS 15310-CL or ONS 15310-MA optical ports and the ONS 15454 transponder/muxponder cards used in a provisionable patchcord. For more information about the ONS 15454 transponder and muxponder cards, refer to the Cisco ONS 15454 DWDM Reference Manual. Optical ports have the following requirements when used in a provisionable patchcord: • An optical port connected to an ONS 15454 transponder/muxponder port requires a section data communications channel (SDCC)/line data communications channel (LDCC) termination. • If the optical port is the protection port in a 1+1 group, the working port must have an SDCC/LDCC termination provisioned. • If a remote end (ONS 15454) of a provisionable patchcord is Y-cable protected, an optical port requires two patchcords. 10.4 Routing Table ONS 15310-CL or ONS 15310-MA routing information appears on the Maintenance > Routing Table tabs. 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. • Usage—Shows the number of times the listed route has been used. • Interface—Shows the ONS 15310-CL or ONS 15310-MA interface used to access the destination. – cpm0—The ONS 15310-CL or ONS 15310-MA Ethernet interface (RJ45 LAN jack) – pdcc0—An SDCC interface, that is, an OC-N trunk port identified as the SDCC termination – lo0—A loopback interface Table 10-6 shows sample routing entries for an ONS 15310-CL or ONS 15310-MA. Table 10-5 Client and Trunk Card Combinations in Provisionable Patchcords ONS 15310-CL and ONS 15310-MA Trunk Ports ONS 15454 Client Cards MXP_2.5G_10G/ TXP_MR_10G TXP(P)_MR_2.5G MXP_2.5G_10E/ TXP_MR_10E OC-3 optical port — Yes — OC-12 optical port — Yes — Table 10-6 Sample Routing Table Entries Entry Destination Mask Gateway Interface 1 0.0.0.0 0.0.0.0 172.20.214.1 cpm0 2 172.20.214.0 255.255.255.0 172.20.214.92 cpm0 3 172.20.214.92 255.255.255.255 127.0.0.1 lo0 4 172.20.214.93 255.255.255.255 0.0.0.0 pdcc0 5 172.20.214.94 255.255.255.255 172.20.214.93 pdcc010-18 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.5 External Firewalls Entry 1 shows the following: • Destination (0.0.0.0) is the default route entry. All undefined destination network or host entries on this routing table is mapped to the default route entry. • Mask (0.0.0.0) is always 0 for the default route. • Gateway (172.20.214.1) is the default gateway address. All outbound traffic that cannot be found in this routing table or is not on the node’s local subnet is sent to this gateway. • Interface (cpm0) indicates that the ONS 15310-CL or ONS 15310-MA Ethernet interface is used to reach the gateway. Entry 2 shows the following: • Destination (172.20.214.0) is the destination network IP address. • Mask (255.255.255.0) is a 24-bit mask, meaning all addresses within the 172.20.214.0 subnet can be a destination. • Gateway (172.20.214.92) is the gateway address. All outbound traffic belonging to this network is sent to this gateway. • Interface (cpm0) indicates that the ONS 15310-CL or ONS 15310-MA Ethernet interface is used to reach the gateway. Entry 3 shows the following: • Destination (172.20.214.92) is the destination host IP address. • Mask (255.255.255.255) is a 32-bit mask, meaning only the 172.20.214.92 address is a destination. • Gateway (127.0.0.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.255) is a 32-bit mask, meaning only the 172.20.214.93 address is a destination. • Gateway (0.0.0.0) means the destination host is directly attached to the node. • Interface (pdcc0) indicates that a SONET SDCC interface is used to reach the destination host. Entry 5 shows a DCC-connected node that is accessible through a node that is not directly connected: • Destination (172.20.214.94) is the destination host IP address. • Mask (255.255.255.255) is a 32-bit mask, meaning only the 172.20.214.94 address is a destination. • Gateway (172.20.214.93) indicates that the destination host is accessed through a node with IP address 172.20.214.93. • Interface (pdcc0) indicates that a SONET SDCC interface is used to reach the gateway. 10.5 External Firewalls Table 10-7 shows the ports that are used by the 15310-CL-CTX or CTX2500 cards. 10-19 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.5 External Firewalls The following access control list (ACL) examples show a firewall configuration when the proxy server gateway setting is not enabled. In the example, the CTC workstation address is 192.168.10.10 and the ONS 15310-CL or ONS 15310-MA address is 10.10.10.100. The firewall is attached to the GNE, so the inbound path is CTC to the GNE and the outbound path is from the GNE to CTC. The CTC CORBA Standard constant is 683 and the TCC CORBA Default is TCC Fixed (57790). access-list 100 remark *** Inbound ACL, CTC -> NE *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq www access-list 100 remark *** allows initial contact with the 15310-CL/15310-MA using http (port 80) *** access-list 100 remark Table 10-7 Ports Used by the 15310-CL-CTX or CTX2500 Port Function Action1 1. D = deny, NA = not applicable, OK = do not deny 0 Never used D 20 FTP D 21 FTP control D 22 SSH (Secure Shell) D 23 Telnet D 80 HTTP D 111 SUNRPC (Sun Remote Procedure Call) NA 161 SNMP traps destinations D 162 SNMP traps destinations D 513 rlogin NA 683 CORBA IIOP OK 1080 Proxy server (socks) D 2001-2017 I/O card Telnet D 2018 DCC processor on active 15310-CL or 15310-MA-CTX D 2361 TL1 D 3082 Raw TL1 D 3083 TL1 D 5001 Bidirectional line switch ring (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 OK10-20 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.6 Open GNE access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq 57790 access-list 100 remark *** allows CTC communication with the 15310-CL/15310-MA GNE (port 57790) *** access-list 100 remark access-list 101 remark access-list 101 permit tcp host 10.10.10.100 host 192.168.10.10 eq 683 access-list 101 remark *** allows alarms etc., from the 15310-CL/15310-MA (random port) to the CTC workstation (port 683) *** access-list 100 remark access-list 101 permit tcp host 10.10.10.100 host 192.168.10.10 established access-list 101 remark *** allows ACKs from the 15310-CL/15310-MA GNE to CTC *** The following ACL examples show a firewall configuration when the proxy server gateway setting is enabled. As with the first example, the CTC workstation address is 192.168.10.10 and the ONS 15310-CL or ONS 15310-MA address is 10.10.10.100. The firewall is attached to the GNE, so the inbound path is CTC to the GNE and the outbound path is from the GNE to CTC. The CTC CORBA Standard constant is 683 and the TCC CORBA Default is TCC Fixed (57790). access-list 100 remark *** Inbound ACL, CTC -> NE *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq www access-list 100 remark *** allows initial contact with the 15310-CL/15310-MA using http (port 80) *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq 1080 access-list 100 remark *** allows CTC communication with the 15310-CL/15310-MA GNE proxy server (port 1080) *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 established access-list 100 remark *** allows ACKs from CTC to the 15310-CL/15310-MA GNE *** access-list 101 remark *** Outbound ACL, NE -> CTC *** access-list 101 remark access-list 101 permit tcp host 10.10.10.100 eq 1080 host 192.168.10.10 access-list 101 remark *** allows alarms and other communications from the 15310-CL/15310-MA (proxy server) to the CTC workstation (port 683) *** access-list 100 remark access-list 101 permit tcp host 10.10.10.100 host 192.168.10.10 established access-list 101 remark *** allows ACKs from the 15310-CL/15310-MA GNE to CTC *** 10.6 Open GNE The ONS 15310-CL or ONS 15310-MA can communicate with non-ONS nodes that do not support point-to-point protocol (PPP) vendor extensions or OSPF type 10 opaque link-state advertisements (LSA), both of which are necessary for automatic node and link discovery. An open GNE configuration allows the DCC-based network to function as an IP network for non-ONS nodes. To configure an open GNE network, you can provision SDCC and LDCC terminations to include a far-end, non-ONS node using either the default IP address of 0.0.0.0 or a specified IP address. You provision a far-end, non-ONS node by checking the “Far End is Foreign” check box during SDCC and LDCC creation. The default 0.0.0.0 IP address allows the far-end, non-ONS node to provide the IP address; if you set an IP address other than 0.0.0.0, a link is established only if the far-end node identifies itself with that IP address, providing an extra level of security. By default, the proxy server only allows connections to discovered ONS peers and the firewall blocks all IP traffic between the DCC network and LAN. You can, however, provision proxy tunnels to allow up to 12 additional destinations for SOCKS version 5 connections to non-ONS nodes. You can also provision firewall tunnels to allow up to 12 additional destinations for direct IP connectivity between the 10-21 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.6 Open GNE DCC network and LAN. Proxy and firewall tunnels include both a source and destination subnet. The connection must originate within the source subnet and terminate within the destination subnet before either the SOCKS connection or IP packet flow is allowed. To set up proxy and firewall subnets in CTC, use the Provisioning > Network > Proxy and Firewalls subtabs. The availability of proxy and/or firewall tunnels depends on the network access settings of the node: • If the node is configured with the proxy server enabled in GNE or ENE mode, you must set up a proxy tunnel and/or a firewall tunnel. • If the node is configured with the proxy server enabled in proxy-only mode, you can set up proxy tunnels. Firewall tunnels are not allowed. • If the node is configured with the proxy server disabled, neither proxy tunnels or firewall tunnels are allowed. Figure 10-13 shows an example of a foreign node connected to the DCC network. Proxy and firewall tunnels are useful in this example because the GNE would otherwise block IP access between the PC and the foreign node. Figure 10-13 Proxy and Firewall Tunnels for Foreign Terminations Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15310 Gateway NE 10.10.10.100/24 ONS 15310 External NE 10.10.10.250/24 Non-ONS node Foreign NE 130.94.122.199/28 ONS 15310 External NE 10.10.10.150/24 ONS 15310 External NE 10.10.10.200/24 124689 Local/Craft CTC 192.168.20.20 Ethernet SONET10-22 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7 TCP/IP and OSI Networking Figure 10-14 shows a remote node connected to an ENE Ethernet port. Proxy and firewall tunnels are useful in this example because the GNE would otherwise block IP access between the PC and foreign node. This configuration also requires a firewall tunnel on the ENE. Figure 10-14 Foreign Node Connection to an ENE Ethernet Port 10.7 TCP/IP and OSI Networking ONS 15310-CL and ONS 15310-MA DCN communication is based on the TCP/IP protocol suite. However, ONS 15310-CL and ONS 15310-MA nodes can also be networked with equipment that uses the OSI protocol suite. While TCP/IP and OSI protocols are not directly compatible, they do have the same objectives and occupy similar layers of the OSI reference model. Table 10-8 shows the protocols that are involved when TCP/IP-based NEs are networked with OSI-based NEs. Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15310 Gateway NE 10.10.10.100/24 ONS 15310 External NE 10.10.10.250/24 ONS 15310 External NE 10.10.10.150/24 ONS 15310 External NE 10.10.10.200/24 124690 Local/Craft CTC 192.168.20.20 Ethernet SONET Non-ONS node Foreign NE 130.94.122.199/2810-23 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.1 Point-to-Point Protocol 10.7.1 Point-to-Point Protocol Point-to-Point protocol (PPP) is a data link (Layer 2) encapsulation protocol that transports datagrams over point-to-point links. Although PPP was developed to transport IP traffic, it can carry other protocols including the OSI Connectionless Network Protocol (CLNP). PPP components used in the transport of OSI include: • High-level data link control (HDLC)—Performs the datagram encapsulation for transport across point-to-point links. • Link control protocol (LCP)—Establishes, configures, and tests point-to-point connections. CTC automatically enables IP over PPP whenever you create an SDCC or LDCC. The SDCC or LDCC can be provisioned to support OSI over PPP. Table 10-8 TCP/IP and OSI Protocols OSI Model IP Protocols OSI Protocols IP-OSI Tunnels Layer 7 Application • TL1 • FTP • HTTP • Telnet • IIOP • TARP1 1. TARP = TID Address Resolution Protocol • TL1 (over OSI) • FTAM2 • ACSE3 2. FTAM = File Transfer and Access Management 3. ACSE = association-control service element Layer 6 Presentation • PST4 4. PST = Presentation layer Layer 5 Session • Session Layer 4 Transport • TCP • UDP • TP (Transport) Class 4 • IP-over-CLNS5 tunnels 5. CLNS = Connectionless Network Layer Service Layer 3 Network • IP • OSPF • CLNP6 • ES-IS7 • IS-IS8 6. CLNP = Connectionless Network Layer Protocol 7. ES-IS = End System-to-Intermediate System 8. IS-IS = Intermediate System-to-Intermediate System Layer 2 Data link • PPP • PPP • LAP-D9 9. LAP-D = Link Access Protocol on the D Channel Layer 1 Physical DCC, LAN, fiber, electrical DCC, LAN, fiber, electrical10-24 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.2 Link Access Protocol on the D Channel 10.7.2 Link Access Protocol on the D Channel LAP-D is a data link protocol used in the OSI protocol stack. LAP-D is assigned when you provision an ONS 15310-CL or ONS 15310-MA SDCC as OSI-only. Provisionable LAP-D parameters include: • Transfer Service—One of the following transfer services must be assigned: – Acknowledged Information Transfer Service (AITS)—(Default) Does not exchange data until a logical connection between two LAP-D users is established. This service provides reliable data transfer, flow control, and error control mechanisms. – Unacknowledged Information Transfer Service (UITS)—Transfers frames containing user data with no acknowledgement. The service does not guarantee that the data presented by one user will be delivered to another user, nor does it inform the user if the delivery attempt fails. It does not provide any flow control or error control mechanisms. • Mode—LAP-D is set to either Network or User mode. This parameter sets the LAP-D frame command/response (C/R) value, which indicates whether the frame is a command or a response. • Maximum transmission unit (MTU)—The LAP-D N201 parameter sets the maximum number of octets in a LAP-D information frame. The range is 512 to 1500 octets. Note The MTU must be the same size for all NEs on the network. • Transmission Timers—The following LAP-D timers can be provisioned: – The T200 timer sets the timeout period for initiating retries or declaring failures. – The T203 timer provisions the maximum time between frame exchanges, that is, the trigger for transmission of the LAP-D “keep-alive” Receive Ready (RR) frames. Fixed values are assigned to the following LAP-D parameters: • Terminal Endpoint Identifier (TEI)—A fixed value of 0 is assigned. • Service Access Point Identifier (SAPI)—A fixed value of 62 is assigned. • N200 supervisory frame retransmissions—A fixed value of 3 is assigned. 10.7.3 OSI Connectionless Network Service OSI connectionless network service is implemented by using the Connectionless Network Protocol (CLNP) and Connectionless Network Service (CLNS). CLNP and CLNS are described in the ISO 8473 standard. CLNS provides network layer services to the transport layer through CLNP. CLNS does not perform connection setup or termination because paths are determined independently for each packet that is transmitted through a network. CLNS relies on transport layer protocols to perform error detection and correction. CLNP is an OSI network layer protocol that carries upper-layer data and error indications over connectionless links. CLNP provides the interface between the CLNS and upper layers. CLNP performs many of the same services for the transport layer as IP. The CLNP datagram is very similar to the IP datagram. It provides mechanisms for fragmentation (data unit identification, fragment/total length, and offset). Like IP, a checksum computed on the CLNP header verifies that the information used to process the CLNP datagram is transmitted correctly, and a lifetime control mechanism (Time to Live) limits the amount of time a datagram is allowed to remain in the system.10-25 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.3 OSI Connectionless Network Service CLNP uses network service access points (NSAPs) to identify network devices. The CLNP source and destination addresses are NSAPs. In addition, CLNP uses a network element title (NET) to identify a network-entity in an end system (ES) or intermediate system (IS). NETs are allocated from the same name space as NSAP addresses. Whether an address is an NSAP address or a NET depends on the network selector value in the NSAP. The ONS 15310-CL and ONS 15310-MA support the ISO Data Country Code (ISO-DCC) NSAP address format as specified in ISO 8348. The NSAP address is divided into an initial domain part (IDP) and a domain-specific part (DSP). NSAP fields are shown in Table 10-9. NSAP field values are in hexadecimal format. All NSAPs are editable and shorter NSAPs can be used; however, NSAPs for all NEs residing within the same OSI network area usually have the same NSAP format. Table 10-9 NSAP Fields Field Definition Description IDP AFI Authority and format identifier Specifies the NSAP address format. The initial value is 39 for the ISO-DCC address format. IDI Initial domain identifier Specifies the country code. The initial value is 840F, the United States country code padded with an F. DSP DFI DSP format identifier Specifies the DSP format. The initial value is 80, indicating the DSP format follows American National Standards Institute (ANSI) standards. ORG Organization Organization identifier. The initial value is 000000. Reserved Reserved Reserved NSAP field. The Reserved field is normally all zeros (0000). RD Routing domain Defines the routing domain. The initial value is 0000. AREA Area Identifies the OSI routing area to which the node belongs. The initial value is 0000.10-26 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.3 OSI Connectionless Network Service Figure 10-15 shows the default ISO-DCC NSAP address delivered with the ONS 15310-CL/ONS 15310-MA. The System ID is automatically populated with the node’s MAC address. Figure 10-15 ISO-DCC NSAP Address System System identifier The ONS 15310-CL system identifier is set to its IEEE 802.3 MAC address. Each ONS 15310-CL supports one OSI virtual router. SEL Selector The selector field directs the protocol data units (PDUs) to the correct destination using the CLNP network layer service. Selector values supported by the ONS 15310-CL include: • 00—Network Entity Title (NET). Used to exchange PDUs in the ES-IS and IS-IS routing exchange protocols. (See the “10.7.4.1 End System-to-Intermediate System Protocol” section on page 10-28, and the “10.7.4.2 Intermediate System-to-Intermediate System Protocol” section on page 10-28.) • 1D—Selector for Transport Class 4 (and for FTAM and TL1 applications (Telcordia GR-253-CORE standard) • AF—Selector for the TARP protocol (Telcordia GR-253-CORE standard) • 2F—Selector for the GRE IP-over-CLNS tunnel (ITU/RFC standard) • CC—Selector for the Cisco IP-over-CLNS tunnels (Cisco specific) • E0—Selector for the OSI ping application (Cisco specific) NSELs are only advertised when the node is configured as an ES. They are not advertised when a node is configured as an IS. Tunnel NSELs are not advertised until a tunnel is created. Table 10-9 NSAP Fields (continued) Field Definition Description 39.840F.80.000000.0000.0000.0000.xxxxxxxxxxxx.00 131598 AFI IDI ORG Reserved RD Area System ID Authority and Format Identifier SEL NSAP Selector DFI DSP Format Identifier Routing Domain Initial Domain Identifier10-27 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.4 OSI Routing The ONS 15310-CL/ONS 15310-MA main NSAP address is shown on the node view Provisioning > OSI > Main Setup subtab. This address is also the Router 1 primary manual area address, which is viewed and edited on the Provisioning > OSI > Routers subtab. See the “10.7.6 OSI Virtual Routers” section on page 10-32 for information about the OSI router and manual area addresses in CTC. 10.7.4 OSI Routing OSI architecture includes ESs and ISs. The OSI routing scheme includes: • A set of routing protocols that allow ESs and ISs to collect and distribute the information necessary to determine routes. Protocols include the ES-IS and IS-IS protocols. ES-IS routing establishes connectivity among ESs and ISs attached to the same (single) subnetwork. • A routing information base (RIB) containing this information, from which routes between ESs can be computed. The RIB consists of a table of entries that identify a destination (for example, an NSAP), the subnetwork over which packets should be forwarded to reach that destination, and a routing metric. The routing metric communicates characteristics of the route (such as delay properties or expected error rate) that are used to evaluate the suitability of a route compared to another route with different properties, for transporting a particular packet or class of packets. • A routing algorithm, Shortest Path First (SPF), that uses information contained in the RIB to derive routes between ESs. 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. An IS composes intermediate system hello (ISH) messages to announce its configuration information to ISs and ESs that are connected to the same broadcast subnetwork. Like the ESHs, the ISH contains the addressing information for the IS (the NET and the subnetwork point-of-attachment address [SNPA]) and a holding time. ISHs might also communicate a suggested ES configuration time recommending a configuration timer to ESs. The exchange of ISHs is called neighbor greeting or initialization. Each router learns about the other routers with which they share direct connectivity. After the initialization, each router constructs a link-state packet (LSP). The LSP contains a list of the names of the IS’s neighbors and the cost to reach each of the neighbors. Routers then distribute the LSPs to all of the other routers. When all LSPs are propagated to all routers, each router has a complete map of the network topology (in the form of LSPs). Routers use the LSPs and the SPF algorithm to compute routes to every destination in the network. OSI networks are divided into areas and domains. An area is a group of contiguous networks and attached hosts that is designated as an area by a network administrator. A domain is a collection of connected areas. Routing domains provides full connectivity to all ESs within the domains. Routing within the same area is known as Level 1 routing. Routing between two areas is known as Level 2 routing. LSPs that are exchanged within a Level 1 area are called L1 LSPs. LSPs that are exchanged across Level 2 areas are called L2 LSPs. Figure 10-16 shows an example of Level 1 and Level 2 routing. Note The ONS 15310-CL and ONS 15310-MA do not support Level 1/Level 2 routing. Level 1/Level 2 routing is supported by the ONS 15454, ONS 15454 SDH, and the ONS 15600.10-28 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.4 OSI Routing Figure 10-16 Level 1 and Level 2 OSI Routing When you provision an ONS 15310-CL or ONS 15310-MA for a network with NEs that use both the TCP/IP and OSI protocol stacks, you will provision it as one of the following: • End System—The ONS 15310-CL or ONS 15310-MA performs OSI ES functions and relies upon an IS for communication with nodes that reside within its OSI area. • Intermediate System Level 1—The ONS 15310-CL performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area. 10.7.4.1 End System-to-Intermediate System Protocol ES-IS is an OSI protocol that defines how ESs (hosts) and ISs (routers) learn about each other. ES-IS configuration information is transmitted at regular intervals through the ES and IS hello messages. The hello messages contain the subnetwork and network layer addresses of the systems that generate them. The ES-IS configuration protocol communicates both OSI network layer addresses and OSI subnetwork addresses. OSI network layer addresses identify either the NSAP, which is the interface between OSI Layer 3 and Layer 4, or the NET, which is the network layer entity in an OSI IS. OSI SNPAs are the points at which an ES or IS is physically attached to a subnetwork. The SNPA address uniquely identifies each system attached to the subnetwork. In an Ethernet network, for example, the SNPA is the 48-bit MAC address. Part of the configuration information transmitted by ES-IS is the NSAP-to-SNPA or NET-to-SNPA mapping. 10.7.4.2 Intermediate System-to-Intermediate System Protocol IS-IS is an OSI link-state hierarchical routing protocol that floods the network with link-state information to build a complete, consistent picture of a network topology. IS-IS distinguishes between Level 1 and Level 2 ISs. Level 1 ISs communicate with other Level 1 ISs in the same area. Level 2 ISs route between Level 1 areas and form an intradomain routing backbone. Level 1 ISs need to know only how to get to the nearest Level 2 IS. The backbone routing protocol can change without impacting the intra-area routing protocol. OSI routing begins when the ESs discover the nearest IS by listening to ISH packets. When an ES wants to send a packet to another ES, it sends the packet to one of the ISs on its directly attached network. The router then looks up the destination address and forwards the packet along the best route. If the destination ES is on the same subnetwork, the local IS knows this from listening to ESHs and forwards Level 2 routing Area 1 IS IS IS IS Area 2 Domain Level 1 routing Level 1 routing ES 131597 ES ES ES10-29 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.5 TARP the packet appropriately. The IS also might provide a redirect (RD) message back to the source to tell it that a more direct route is available. If the destination address is an ES on another subnetwork in the same area, the IS knows the correct route and forwards the packet appropriately. If the destination address is an ES in another area, the Level 1 IS sends the packet to the nearest Level 2 IS. Forwarding through Level 2 ISs continues until the packet reaches a Level 2 IS in the destination area. Within the destination area, the ISs forward the packet along the best path until the destination ES is reached. Link-state update messages help ISs learn about the network topology. Each IS generates an update specifying the ESs and ISs to which it is connected, as well as the associated metrics. The update is then sent to all neighboring ISs, which forward (flood) it to their neighbors, and so on. (Sequence numbers terminate the flood and distinguish old updates from new ones.) Using these updates, each IS can build a complete topology of the network. When the topology changes, new updates are sent. IS-IS uses a single required default metric with a maximum path value of 1024. The metric is arbitrary and typically is assigned by a network administrator. Any single link can have a maximum value of 64, and path links are calculated by summing link values. Maximum metric values were set at these levels to provide the granularity to support various link types while at the same time ensuring that the shortest-path algorithm used for route computation is reasonably efficient. Three optional IS-IS metrics (costs)—delay, expense, and error—are not supported by the ONS 15310-CL or ONS 15310-MA. IS-IS maintains a mapping of the metrics to the quality of service (QoS) option in the CLNP packet header. IS-IS uses the mappings to compute routes through the internetwork. 10.7.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 (see Table 10-9 on page 10-25). TARP uses a selective PDU propagation methodology in conjunction with a distributed database (that resides within the NEs) of TID-to-NET mappings. TARP allows NEs to translate between TID and NET by automatically exchanging mapping information with other NEs. The TARP PDU is carried by the standard CLNP Data PDU. TARP PDU fields are shown in Table 10-10. Table 10-10 TARP PDU Fields Field Abbreviation Size (bytes) Description TARP Lifetime tar-lif 2 The TARP time-to-live in hops. TARP Sequence Number tar-seq 2 The TARP sequence number used for loop detection. Protocol Address Type tar-pro 1 Used to identify the type of protocol address that the TID must be mapped to. The value FE is used to identify the CLNP address type. TARP Type Code tar-tcd 1 The TARP Type Code identifies the TARP type of PDU. Five TARP types, shown in Table 10-11, are defined. TID Target Length tar-tln 1 The number of octets that are in the tar-ttg field. TID Originator Length tar-oln 1 The number of octets that are in the tar-tor field. Protocol Address Length tar-pln 1 The number of octets that are in the tar-por field.10-30 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.5 TARP Table 10-11 shows the TARP PDU types that govern TARP interaction and routing. 10.7.5.1 TARP Processing A TARP data cache (TDC) is created at each NE to facilitate TARP processing. In CTC, the TDC is displayed and managed on the node view Maintenance > OSI > TDC subtab. The TDC subtab contains the following TARP PDU fields: • TID—TID of the originating NE (tar-tor). • NSAP—NSAP of the originating NE. • Type— Indicates whether the TARP PDU was created through the TARP propagation process (dynamic) or manually created (static). Provisionable timers, shown in Table 10-12, control TARP processing. TID of Target tar-ttg n = 0, 1, 2... TID value for the target NE. TID of Originator tar-tor n = 0, 1, 2... TID value of the TARP PDU originator. Protocol Address of Originator tar-por n = 0, 1, 2... Protocol address (for the protocol type identified in the tar-pro field) of the TARP PDU originator. When the tar-pro field is set to FE (hex), tar-por will contain a CLNP address (that is, the NET). Table 10-10 TARP PDU Fields (continued) Field Abbreviation Size (bytes) Description Table 10-11 TARP PDU Types Type Description Procedure 1 Sent when a device has a TID for which it has no matching NSAP. After an NE originates a TARP Type 1 PDU, the PDU is sent to all adjacencies within the NE’s routing area. 2 Sent when a device has a TID for which it has no matching NSAP and no response was received from the Type 1 PDU. After an NE originates a TARP Type 2 PDU, the PDU is sent to all Level 1 and Level 2 neighbors. 3 Sent as a response to Type 1, Type 2, or Type 5 PDUs. After a TARP Request (Type 1 or 2) PDU is received, 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. A Type 4 PDU is a notification of a TID or Protocol Address change at the NE that originates the notification. The PDU is sent to all adjacencies inside and outside the NE’s routing area. 5 Sent when a device needs a TID that corresponds to a specific NSAP. When a Type 5 PDU is sent, the CLNP destination address is known, so the PDU is sent to only that address. Type 5 PDUs do not use the TARP propagation procedures.10-31 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.5 TARP Table 10-13 shows the main TARP processes and the general sequence of events that occurs in each process. 10.7.5.2 TARP Loop Detection Buffer The TARP loop detection buffer (LDB) can be enabled to prevent duplicate TARP PDUs from entering the TDC. When a TARP Type 1, 2, or 4 PDU arrives, TARP checks its LDB for the NET address of the PDU originator match. If no match is found, TARP processes the PDU and assigns a tar-por, tar-seq (sequence) entry for the PDU to the LDB. If the tar-seq is zero, a timer associated with the LDB entry is started using the provisionable LDB entry timer on the node view OSI > TARP > Config tab. If a match exists, the tar-seq is compared to the LDB entry. If the tar-seq is not zero and is less than or equal to the LDB entry, the PDU is discarded. If the tar-seq is greater than the LDB entry, the PDU is processed and the tar-seq field in the LDB entry is updated with the new value. The Cisco ONS 15310-CL and Cisco ONS 15310-MA LDB holds approximately 500 entries. The LDB is flushed periodically based on the time set in the LDB Flush timer on the node view OSI > TARP > Config tabs. Table 10-12 TARP Timers Timer Description Default (seconds) Range (seconds) T1 Waiting for response to TARP Type 1 Request PDU 15 0–3600 T2 Waiting for response to TARP Type 2 Request PDU 25 0–3600 T3 Waiting for response to address resolution request 40 0–3600 T4 Timer starts when T2 expires (used during error recovery) 20 0–3600 Table 10-13 TARP Processing Flow Process General TARP Flow Find a NET that matches a TID 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. If Timer T2 expires before a match is found, Timer T4 is started. 5. If Timer T4 expires before a match is found, a Type 2 PDU is generated and Timer T2 is started. Find a TID that matches a NET A Type 5 PDU is generated. Timer T3 is used. However, if the timer expires, no error recovery procedure occurs, and a status message is provided to indicate that the TID cannot be found. Send a notification of TID or protocol address change TARP generates a Type 4 PDU in which the tar-ttg field contains the NE’s TID value that existed prior to the change of TID or protocol address. Confirmation that other NEs successfully received the address change is not sent.10-32 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.6 OSI Virtual Routers 10.7.5.3 Manual TARP Adjacencies TARP adjacencies can be manually provisioned in networks where ONS 15310-CL or ONS 15310-MA nodes must communicate across routers or non-SONET NEs that lack TARP capability. In CTC, manual TARP adjacencies are provisioned on the node view Provisioning > OSI > TARP > MAT (Manual Area Table) subtab. The manual adjacency causes a TARP request to hop through the general router or non-SONET NE, as shown in Figure 10-17. Figure 10-17 Manual TARP Adjacencies 10.7.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. Static entries allow you to forward TL1 commands to NEs that do not support TARP. However, static TDC entries are not dynamically updated, so outdated entries are not removed after the TID or the NSAP changes on the target node. 10.7.6 OSI Virtual Routers The ONS 15310-CL and ONS 15310-MA support one OSI virtual router. The router is provisioned on the Provisioning > OSI > Routers tabs. The router has an editable manual area address and a unique NSAP System ID that is set to the node MAC address. The router can be enabled and connected to different OSI routing areas. The Router 1 manual area address and System ID create the NSAP address assigned to the node’s TID. Router 1 supports OSI TARP and tunneling functions. These include: • TARP data cache • IP-over-CLNS tunnels • LAN subnet 131957 Generic router DCN DCN Manual adjacency10-33 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.7 IP-over-CLNS Tunnels In addition to the primary manual area address, you can also create two additional manual area addresses. These manual area addresses can be used to: • Split up an area—Nodes within a given area can accumulate to a point that they are difficult to manage, cause excessive traffic, or threaten to exceed the usable address space for an area. Additional manual area addresses can be assigned so that you can smoothly partition a network into separate areas without disrupting service. • Merge areas—Use transitional area addresses to merge as many as three separate areas into a single area that shares a common area address. • Change to a different address—You might need to change an area address for a particular group of nodes. Use multiple manual area addresses to allow incoming traffic intended for an old area address to continue being routed to associated nodes. 10.7.7 IP-over-CLNS Tunnels IP-over-CLNS tunnels are used to encapsulate IP for transport across OSI NEs. The ONS 15310-CL and ONS 15310-MA supports two tunnel types: • GRE—Generic Routing Encapsulation is a tunneling protocol that encapsulates one network layer for transport across another. GRE tunnels add both a CLNS header and a GRE header to the tunnel frames. GRE tunnels are supported by Cisco routers and some other vendor NEs. • Cisco IP—The Cisco IP tunnel directly encapsulates the IP packet with no intermediate header. Cisco IP is supported by most Cisco routers. Figure 10-18 shows the protocol flow when an IP-over-CLNS tunnel is created through four NEs (A, B, C, and D). The tunnel ends are configured on NEs A and D, which support both IP and OSI. NEs B and C only support OSI, so they only route the OSI packets. Figure 10-18 IP-over-CLNS Tunnel Flow 131956 NE-D SNMP RMON HTTP FTP Telnet UDP IPv4 GRE Tunnel LLC1 LAN CLNP LAPD DCC TCP EMS SNMP RMON HTTP FTP Telnet UDP IPv4 LLC1 LAN TCP NE-A (GNE) IPv4 GRE Tunnel LLC1 LAN CLNP LAPD DCC NE-C CLNP LAPD DCC NE-B CLNP LAPD DCC10-34 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.7 IP-over-CLNS Tunnels 10.7.7.1 Provisioning IP-over-CLNS Tunnels IP-over-CLNS tunnels must be carefully planned to prevent nodes from losing visibility or connectivity. Before you begin a tunnel, verify that the tunnel type, either Cisco IP or GRE, is supported by the equipment at the other end. Always verify IP and NSAP addresses. Provisioning of IP-over-CLNS tunnels in CTC is performed on the node view Provisioning > OSI > IP over CLNS Tunnels tab. For procedures, see the “Turn Up a Node” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Provisioning IP-over-CLNS tunnels on Cisco routers requires the following prerequisite tasks, as well as other OSI provisioning: • (Required) Enable IS-IS • (Optional) Enable routing for an area on an interface • (Optional) Assign multiple area addresses • (Optional) Configure IS-IS interface parameters • (Optional) Configure miscellaneous IS-IS parameters The Cisco IOS commands used to create IP-over-CLNS tunnels (CTunnels) are shown in Table 10-14. If you are provisioning an IP-over-CLNS tunnel on a Cisco router, always follow procedures provided in the Cisco IOS documentation for the router you are provisioning. For information about ISO CLNS provisioning including IP-over-CLNS tunnels, refer to the “Configuring ISO CLNS” chapter in the Cisco IOS Apollo Domain, Banyon VINES, DECnet, ISO CLNS, and XNS Configuration Guide. 10.7.7.2 IP Over CLNS Tunnel Scenario 1: ONS Node to Other Vendor GNE Figure 10-19 shows an IP-over-CLNS tunnel created from an ONS node to another vendor GNE. The other vendor NE has an IP connection to an IP DCN to which a CTC computer is attached. An OSI-only (LAP-D) SDCC and a GRE tunnel are created between the ONS NE 1 to the other vender GNE. IP-over-CLNS tunnel provisioning on the ONS NE 1: • Destination: 10.10.10.100 (CTC 1) • Mask: 255.255.255.255 for host route (CTC 1 only), or 255.255.255.0 for subnet route (all CTC computers residing on the 10.10.10.0 subnet) • NSAP: 39.840F.80.1111.0000.1111.1111.cccccccccccc.00 (other vendor GNE) • Metric: 110 Table 10-14 IP Over CLNS Tunnel Cisco 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. Specifies the destination NSAP1 address of the CTunnel, where the IP packets are extracted. 3 Router (config-if) # ip address ip-address mask Sets the primary or secondary IP address for an interface.10-35 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.7 IP-over-CLNS Tunnels • Tunnel Type: GRE IP-over-CLNS tunnel provisioning on the other vender GNE: • Destination: 10.20.30.30 (ONS NE 1) • Mask: 255.255.255.255 for host route (ONS NE 1 only), or 255.255.255.0 for subnet route (all ONS nodes residing on the 10.30.30.0 subnet) • NSAP: 39.840F.80.1111.0000.1111.1111.dddddddddddd.00 (ONS NE 1) • Metric: 110 • Tunnel Type: GRE Figure 10-19 IP Over CLNS Tunnel Scenario 1: ONS NE to Other Vender GNE 10.7.7.3 IP-Over-CLNS Tunnel Scenario 2: ONS Node to Router Figure 10-20 shows an IP-over-CLNS tunnel from an ONS node to a router. The other vendor NE has an OSI connection to a router on an IP DCN, to which a CTC computer is attached. An OSI-only (LAP-D) SDCC is created between the ONS NE 1 and the other vender GNE. The OSI-over-IP tunnel can be either the Cisco IP tunnel or a GRE tunnel, depending on the tunnel types supported by the router. 134355 CTC 1 10.10.10.100/24 IP DCN IP/OSI Vendor GNE 10.10.30.20/24 39.840F.80. 111111.0000.1111.1111.cccccccccccc.00 ONS NE 1 10.10.30.30/24 39.840F.80. 111111.0000.1111.1111.dddddddddddd.00 Other vendor NE OSI OSI-only DCC (LAPD) GRE tunnel OSI 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 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.0010-36 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.7 IP-over-CLNS Tunnels IP-over-CLNS tunnel provisioning on ONS NE 1: • Destination: 10.10.30.10 (Router 1, Interface 0/1) • Mask: 255.255.255.255 for host route (Router 1 only), or 255.255.255.0 for subnet route (all routers on the same subnet) • NSAP: 39.840F.80.1111.0000.1111.1111.bbbbbbbbbbbb.00 (Router 1) • Metric: 110 • Tunnel Type: Cisco IP CTunnel (IP over CLNS) provisioning on Router 1: ip routing clns routing interface ctunnel 102 ip address 10.10.30.30 255.255.255.0 ctunnel destination 39.840F.80.1111.0000.1111.1111.dddddddddddd.00 interface Ethernet0/1 clns router isis router isis net 39.840F.80.1111.0000.1111.1111.bbbbbbbbbbbb.0010-37 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.7 IP-over-CLNS Tunnels Figure 10-20 IP-Over-CLNS Tunnel Scenario 2: ONS Node to Router 10.7.7.4 IP-Over-CLNS Tunnel Scenario 3: ONS Node to Router Across an OSI DCN Figure 10-21 shows an IP-over-CLNS tunnel from an ONS node to a router across an OSI DCN. The other vendor NE has an OSI connection to an IP DCN to which a CTC computer is attached. An OSI-only (LAP-D) SDCC is created between the ONS NE 1 and the other vender GNE. The OSI-over-IP tunnel can be either the Cisco IP tunnel or a GRE tunnel, depending on the tunnel types supported by the router. IP-over-CLNS tunnel provisioning on ONS NE 1: • 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 IP-over-OSI tunnel provisioning on Router 2 (sample Cisco IOS provisioning): 134356 CTC 1 10.10.10.100/24 IP DCN OSI Other vendor GNE Other vendor NE OSI OSI-only DCC (LAPD) GRE or Cisco IP tunnel OSI ONS NE 1 10.10.30.30/24 39.840F.80. 111111.0000.1111.1111.dddddddddddd.00 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 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.0010-38 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.7 IP-over-CLNS Tunnels ip routing clns routing interface ctunnel 102 ip address 10.10.30.30 255.255.255.0 ctunnel destination 39.840F.80.1111.0000.1111.1111.dddddddddddd.00 interface Ethernet0/1 clns router isis router isis net 39.840F.80.1111.0000.1111.1111.aaaaaaaaaaaa.00 Figure 10-21 IP-Over-CLNS Tunnel Scenario 3: ONS Node to Router Across an OSI DCN 134357 CTC 1 10.10.10.100/24 OSI DCN OSI IP Other vendor GNE Other vendor NE OSI OSI-only DCC (LAPD) GRE or Cisco IP tunnel OSI ONS NE 1 10.10.30.30/24 39.840F.80. 111111.0000.1111.1111.dddddddddddd.00 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 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.0010-39 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.8 Provisioning OSI in CTC 10.7.8 Provisioning OSI in CTC Table 10-15 shows the OSI actions that can be performed in CTC using the node view Provisioning tab. Refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide for OSI procedures and tasks. Table 10-16 shows the OSI actions that can be performed in CTC using the node view Maintenance tab. Table 10-15 OSI Actions from the CTC Node View Provisioning Tab Tab Actions OSI > Main Setup • View and edit Primary Area Address. • Change OSI routing mode. • Change LSP buffers. OSI > TARP > Config Configure the TARP parameters: • PDU L1/L2 propagation and origination. • TARP data cache and loop detection buffer. • LAN storm suppression. • Type 4 PDU on startup. • TARP timers: LDB, T1, T2, T3, T4. OSI > TARP > Static TDC Add and delete static TARP data cache entries. OSI > TARP > MAT Add and delete static manual area table entries. OSI > Routers > Setup • Enable and disable routers. • Add, delete, and edit manual area addresses. OSI > Routers > Subnets Edit SDCC, LDCC, and LAN subnets that are provisioned for OSI. OSI > Tunnels Add, delete, and edit Cisco and IP-over-CLNS tunnels. Comm Channels > SDCC • Add OSI configuration to an SDCC. • Choose the data link layer protocol, PPP or LAP-D. Comm Channels > LDCC • Add OSI configuration to an SDCC. Table 10-16 OSI Actions from the CTC Maintenance Tab Tab Actions OSI > ISIS RIB View the IS-IS routing table. OSI > ESIS RIB View ESs that are attached to ISs. OSI > TDC • View the TARP data cache and identify static and dynamic entries. • Perform TID to NSAP resolutions. • Flush the TDC.10-40 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 10 Management Network Connectivity 10.7.8 Provisioning OSI in CTCCHAPTER 11-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 11 Alarm Monitoring and Management This chapter describes Cisco Transport Controller (CTC) alarm management. To troubleshoot specific alarms, refer to the Cisco ONS 15310-CL and ONS 15310-MA Troubleshooting Guide. Chapter topics include: • 11.1 Overview, page 11-1 • 11.2 Viewing Alarms, page 11-1 • 11.3 Alarm Severities, page 11-9 • 11.4 Alarm Profiles, page 11-10 • 11.5 Alarm Suppression, page 11-13 • 11.6 External Alarms and Controls, page 11-14 11.1 Overview Cisco Transport Controller (CTC) detects and reports SONET alarms generated by the Cisco ONS 15310-CL or ONS 15310-MA and the larger SONET network. You can use CTC to monitor and manage alarms at the card, node, or network level. Default alarm severities conform to the Telcordia GR-474-CORE standard, but you can set alarm severities in customized alarm profiles or suppress CTC alarm reporting. For a detailed description of the standard Telcordia categories employed by Optical Networking System (ONS) nodes, refer to the Cisco ONS 15310-CL and ONS 15310-MA Troubleshooting Guide. Note ONS 15310-CL and ONS 15310-MA alarms can also be monitored and managed through Transaction Language One (TL1) or a network management system (NMS). 11.2 Viewing Alarms You can use the Alarms tab to view card, node, or network-level alarms. The Alarms window shows alarms in conformance with Telcordia GR-474-CORE. This means that if a network problem causes two alarms, such as loss of frame (LOF) and loss of signal (LOS), CTC only shows the LOS alarm in this window because it supersedes LOF. (The LOF alarm can still be retrieved in the Conditions window.) 11-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2 Viewing Alarms The Path Width column in the Alarms and Conditions tabs expands upon alarmed object information contained in the access identifier (AID) string (such as “STS-4-1-3”) by giving the number of synchronous transport signals (STSs) contained in the alarmed path. For example, the Path Width will tell you whether a Critical alarm applies to an STS1 or an STS48c. The column reports the width as a 1, 3, 6, 12, 48, etc. as appropriate, understood to be “STS-N.” Table 11-1 lists the Alarms tab column headings and the information recorded in each column. Table 11-2 lists the color codes for alarm and condition severities. In addition to the severities listed in the table, CTC alarm profiles list inherited (I) and unset (U) severities. Table 11-1 Alarms Column Descriptions Column Information Recorded New Indicates a new alarm. To change this status, click either the Synchronize button or the Delete Cleared Alarms button. Date Date and time of the alarm. Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.) Object TL1 AID for the alarmed object. For an STSmon or VTmon, this is the monitored STS or VT object, which is explained in Table 11-3 on page 11-3. Eqpt Type Card type in this slot (appears only in network and node view). Shelf For 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. Path Width Indicates how many STSs are contained in the alarmed path. This information compliments the alarm object notation, which is explained in Table 11-3 on page 11-3. Sev Severity level: CR (Critical), MJ (Major), MN (Minor), NA (Not-Alarmed), NR (Not-Reported). ST Status: R (raised), C (clear). SA When checked, indicates a service-affecting alarm. Cond The error message/alarm name. These names are alphabetically defined in the “Alarm Troubleshooting” chapter of the Cisco ONS 15310-CL and ONS 15310-MA Troubleshooting Guide. Description Description of the alarm. Num Num (number) is the quantity of alarm messages received and is increments automatically as alarms occur to display the current total of received error messages. (The column is hidden by default; to view it, right-click a column and choose Show Column > Num.) Ref Ref (reference) is a unique identification number assigned to each alarm to reference a specific alarm message that is displayed. (The column is hidden by default; to view it, right-click a column and choose Show Column > Ref.)11-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2 Viewing Alarms In network view, CTC identifies STS and VT alarm objects using a TL1-type AID, as shown in Table 11-3. Table 11-2 Color Codes for Alarm and Condition Severities Color Description Red Raised Critical (CR) alarm Orange Raised Major (MJ) alarm Yellow Raised Minor (MN) alarm Magenta Raised Not-Alarmed (NA) condition Blue Raised Not-Reported (NR) condition White Cleared (C) alarm or condition Table 11-3 STS and Alarm Object Identification STS and VT Alarm Numbering (ONS 15310-CL and ONS 15310-MA) MON Object (Optical) Syntax and Examples OC3/OC12 STS Syntax: STS---- Ranges: STS-{2}-{1-2}-{1}-{1-n} 1 Example: STS-2-1-1-6 1. The maximum number of STSs depends on the rate and size of the STS. OC3/OC12 VT Syntax: VT1------ Ranges: VT1-{2}-{1-2}-{1}-{1-n 1 }-{1-7}-{1-4} Example: VT1-2-1-1-6-1-1 EC1 STS Syntax: STS--- Ranges: STS-{2}-{1-3}-{1-n} 1 Example: STS-2-1-6 EC1 VT Syntax: VT1----- Ranges: VT1-{2}-{1-3}-{1-n} 1 -{1-7}-{1-4} Example: VT1-2-1-6-1-1 TERM Object (Electrical) Syntax and Examples T1 STS Syntax: STS-- Ranges: STS-{2}-{1-n} 1 Example: STS-2-6 T1 VT Syntax: VT1---VT Group>- Ranges: VT1-{2}-{1-n} 1 -{1-7}-{1-3} Example: VT1-2-6-1-1 T3 STS Syntax: STS--- Ranges: STS-{2}-{1-3}-{1-n} 1 Example: STS-2-1-6 T3 VT VT not supported11-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2.1 Viewing Alarms With Each Node’s Time Zone 11.2.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. 11.2.2 Controlling Alarm Display You can control the display of the alarms shown in the Alarms window. Table 11-4 shows the actions you can perform in the Alarms window. 11.2.3 Filtering Alarms The alarm display can be filtered to prevent display of alarms with certain severities or alarms that occurred between certain dates and times. You can set the filtering parameters by clicking the Filter button at the bottom-left of the Alarms window. You can turn the filter on or off by clicking the Filter tool at the bottom-right of the window. CTC retains your filter activation setting. For example, if you turn the filter on and then log out, CTC keeps the filter active the next time you log in. Table 11-4 Alarm Display Button/Check box/Tool Action Filter button Allows you to change the display in the Alarms window to show only alarms that meet a certain severity level, occur in a specified time frame, and/or reflect specific conditions. For example, you can set the filter so that only Critical alarms are displayed in the window. If you enable the Filter feature by clicking the Filter tool in one CTC view, such as node view, it is enabled in the others as well (card view and network view). Synchronize button Updates the alarm display. Although CTC displays alarms in real time, the Synchronize button allows you to verify the alarm display. This is particularly useful during provisioning or troubleshooting. Delete Cleared Alarms button Deletes, from the view, alarms that have been cleared. AutoDelete Cleared Alarms check box If checked, CTC automatically deletes cleared alarms. Filter tool Enables or disables alarm filtering in the card, node, or network view. When enabled or disabled, this state applies to other views for that node and for all other nodes in the network. For example, if the Filter tool is enabled in the node (default login) view Alarms window, the network view Alarms window and card view Alarms window also show the tool enabled. All other nodes in the network also show the tool enabled.11-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2.4 Viewing Alarm-Affected Circuits 11.2.4 Viewing Alarm-Affected Circuits To view which ONS 15310-CL or ONS 15310-MA circuits are affected by a specific alarm, right-click an alarm in the Alarm window. A shortcut menu appears, as shown in Figure 11-1 (This figure illustrates the ONS 15310-MA, but the ONS 15310-CL behaves similarly.) When you select the Select Affected Circuits option, the Circuits window opens to show the circuits that are affected by the alarm. Figure 11-1 ONS 15310-MA Select Affected Circuits Option 11.2.5 Conditions Tab The Conditions window displays retrieved fault conditions. A condition is a fault or status detected by ONS 15310-CL or ONS 15310-MA hardware or software. When a condition occurs and continues for a minimum period, CTC raises a condition, which is a flag showing that this particular condition currently exists on theONS 15310-CL or ONS 15310-MA. The Conditions window shows all conditions that occur, including those that are superseded. For instance, if a network problem causes two alarms, such as LOF and LOS, CTC shows both the LOF and LOS conditions in this window (even though LOS supersedes LOF). Having all conditions visible can be helpful when troubleshooting the ONS 15310-CL or ONS 15310-MA. If you want to retrieve conditions that obey a root-cause hierarchy (that is, LOS supersedes and replaces LOF), you can exclude the same root causes by checking “Exclude Same Root Cause” check box in the window. Fault conditions include reported alarms and Not-Reported or Not-Alarmed conditions. Refer to the trouble notifications information in the Cisco ONS 15310-CL and ONS 15310-MA Troubleshooting Guide for more information about alarm and condition classifications.11-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2.6 Controlling the Conditions Display 11.2.6 Controlling the Conditions Display You can control the display of the conditions on the Conditions window. Table 11-5 shows the actions you can perform in the window. 11.2.6.1 Retrieving and Displaying Conditions The current set of all existing conditions maintained by the alarm manager can be seen when you click the Retrieve button. The set of conditions retrieved is relative to the view. For example, if you click the button while displaying the node view, node-specific conditions appear. If you click the button while displaying the network view, all conditions for the network (including ONS 15310-CL or ONS 15310-MA nodes and other connected nodes) appear, and the card view shows only card-specific conditions. You can also set a node to display conditions using the time zone where the node is located, rather than the time zone of the PC where they are being viewed. See the “11.2.1 Viewing Alarms With Each Node’s Time Zone” section on page 11-4 for more information. 11.2.6.2 Conditions Column Descriptions Table 11-6 lists the Conditions window column headings and the information recorded in each column. Table 11-5 Conditions Display Button Action Retrieve Retrieves the current set of all existing fault conditions, as maintained by the alarm manager, from the ONS 15310-CL or ONS 15310-MA. Filter Allows you to change the Conditions window display to only show the conditions that meet a certain severity level or occur in a specified time. For example, you can set the filter so that only Critical conditions display on the window. There is a Filter tool on the lower-right of the window that allows you to enable or disable the filter feature. Table 11-6 Conditions Column Description Column Information Recorded Date Date and time of the condition. Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.) Object TL1 AID for the condition object. For an STSmon or VTmon, this is the monitored STS or VT object, which is explained in Table 11-3 on page 11-3. Eqpt Type Card type in this slot (appears only in network and node view). Shelf For DWDM configurations, the shelf where the alarmed object is located. Visible in network view.11-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2.7 Viewing History 11.2.6.3 Filtering Conditions The condition display can be filtered to prevent the appearance of conditions (including alarms) with certain severities or that occurred between certain dates. You can set the filtering parameters by clicking the Filter button at the bottom-left of the Conditions window. You can turn the filter on or off by clicking the Filter tool at the bottom-right of the window. CTC retains your filter activation setting. For example, if you turn the filter on and then log out, CTC keeps the filter active the next time you log in. 11.2.7 Viewing History The History window displays historic alarm or condition data for the node or for your login session. You can chose to display only alarm history, only events, or both by checking check boxes in the History > Shelf window. You can view network-level alarm and condition history, such as for circuits, for all the nodes visible in network view. At the node level, you can see all port (facility), card, STS, and system-level history entries for that node. For example, protection-switching events or performance-monitoring threshold crossings appear here. If you double-click a card, you can view all port, card, and STS alarm or condition history that directly affects the port. Note In the Preference dialog General tab, the Maximum History Entries value only applies to the Session window. Different views of CTC display different kinds of history: • The History > Session window is shown in network view, node view, and card view. It shows alarms and conditions that occurred during the current user CTC session. • The History > Shelf window is only shown in node view. It shows the alarms and conditions that occurred on the node since CTC software was operated on the node. • The History > Card window is only shown in card view. It shows the alarms and conditions that occurred on the card since CTC software was installed on the node. Slot Slot where the condition occurred (appears only in network and node view). Port Port where the condition occurred. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with. Path Width Width of the signal path Sev1 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 Cisco ONS 15310-CL and ONS 15310-MA Troubleshooting Guide. Description Description of the condition. 1. All alarms, their severities, and service-affecting statuses are also displayed in the Condition tab unless you choose to filter the alarm from the display using the Filter button. Table 11-6 Conditions Column Description (continued) Column Information Recorded11-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2.7 Viewing History Tip Double-click an alarm in the History window to display the corresponding view. For example, double-clicking a card alarm takes you to card view. In network view, double-clicking a node alarm takes you to node view. 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. 11.2.7.1 History Column Descriptions Table 11-7 lists the History window column headings and the information recorded in each column. 11.2.7.2 Retrieving and Displaying Alarm and Condition History You can retrieve and view the history of alarms and conditions, as well as transients (passing notifications of processes as they occur) in the CTC history window. The information in this window is specific to the view where it is shown (that is, network history in the network view, node history in the node view, and card history in the card view). Table 11-7 History Column Description Column Information Recorded Num An incrementing count of alarm or condition messages. (The column is hidden by default; to view it, right-click a column and choose Show Column > Num.) Ref The reference number assigned to the alarm or condition. (The column is hidden by default; to view it, right-click a column and choose Show Column > Ref.) Date Date and time of the condition. Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.) Object TL1 AID for the condition object. For an STSmon or VTmon, this is the monitored STS or VT object, which is explained in Table 11-3 on page 11-3. Eqpt Type Card type in this slot (only displays in network view and node view). Shelf For DWDM configurations, the shelf where the alarmed object is located. Visible in network view. Slot Slot where the condition occurred (only displays in network view and node view). Port Port where the condition occurred. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with. Path Width Width of the signal path. Sev Severity level: Critical (CR), Major (MJ), Minor (MN), Not-Alarmed (NA), Not-Reported (NR). ST Status: raised (R), cleared (C), or transient (T). SA A service-affecting alarm (when checked). Description Description of the condition. Cond Condition name.11-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.2.8 Alarm History and Log Buffer Capacities The node and card history views are each divided into two tabs. In node view, when you click the Retrieve button, you can see the history of alarms, conditions, and transients that have occurred on the node in the History > Shelf window, and the history of alarms, conditions, and transients that have occurred on the node during your login session in the History > Session window. In the card-view history window, after you retrieve the card history, you can see the history of alarms, conditions, and transients 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. 11.2.8 Alarm History and Log Buffer Capacities The ONS 15310-CL or ONS 15310-MA alarm history log, stored in the 15310-CL-CTX or CTX2500 RSA memory, contains four categories of alarms. These include: • CR severity alarms • MJ severity alarms • MN severity alarms • the combined group of cleared, Not Alarmed severity, and Not Reported severity alarms Each category can store between 4 and 640 alarm chunks, or entries. In each category, when the upper limit is reached, the oldest entry in the category is deleted. The capacity is not user-provisionable. CTC also has a log buffer, separate from the alarm history log, that pertains to the total number of entries displayed in the Alarms, Conditions, and History windows. The total capacity is provisionable up to 5,000 entries. When the upper limit is reached, the oldest entries are deleted. 11.3 Alarm Severities The ONS 15310-CL and ONS 15310-MA alarm severities follow the Telcordia GR-474-CORE standard, so a condition may be Alarmed at a severity of Critical (CR), Major (MJ), or Minor (MN) with a severity of Not Alarmed (NA) or Not Reported (NR). These severities are reported in the CTC software Alarms, Conditions, and History windows at all levels: network, node, and card. ONS equipment provides a standard profile named “Default” that lists all alarms and conditions with severity settings based on Telcordia GR-253-CORE and other standards, but users can create their own profiles with different settings for some or all conditions and apply these wherever needed. (See the “11.4 Alarm Profiles” section on page 11-10 for more information.) For example, in a custom alarm profile, the default severity of a carrier loss (CARLOSS) alarm on an Ethernet port can be changed from Major to Critical. Critical and Major severities are only used for service-affecting alarms. If a condition is set as Critical or Major by profile, it will raise as a Minor alarm in the following situations: • In a protection group, if the alarm is on a standby entity (side not carrying traffic) • If the alarmed entity has no traffic provisioned on it, so no service is lost Because the alarm might be raised at two different levels, the alarm profile pane shows Critical as “CR / MN” and Major as “MJ / MN.”11-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.4 Alarm Profiles 11.4 Alarm Profiles The alarm profiles feature allows you to change default alarm severities by creating unique alarm profiles for individual ONS 15310-CL or ONS 15310-MA ports, cards, or nodes. A created alarm profile can be applied to any node on the network. Alarm profiles can be saved to a file and imported elsewhere in the network, but the profile must be stored locally on a node before it can be applied to the node, cards, or ports. 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-CORE severities. The reserved Inherited profile allows port alarm severities to be governed by the card-level severities, or card alarm severities to be determined by the node-level severities. If one or more alarm profiles is stored as files from elsewhere in the network onto the local PC or server hard drive where CTC resides, you can use as many profiles as you can physically store by deleting and replacing them locally in CTC so that only eight are active at any given time. 11.4.1 Creating and Modifying Alarm Profiles Alarm profiles are created in the network view using the Provisioning > Alarm Profiles tabs. A default alarm severity following Telcordia GR-474-CORE standards is preprovisioned for every alarm. After loading the default profile or another profile on the node, you can use the Clone feature to create custom profiles. After the new profile is created, the Alarm Profiles window shows the original profile—frequently Default—and the new profile. Note All default or user-defined severity settings that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in non-service affecting situations as defined in Telcordia GR-474-CORE. Tip To see the full list of profiles including those available for loading or cloning, click the Available button. You must load a profile before you can clone it. Wherever it is applied, the Default alarm profile sets severities to standard Telcordia GR-474-CORE 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. If you choose the Inherited profile from the network view, the severities at the lower levels (node and card) are copied from this selection. You do not have to apply a single severity profile to the node, card, and port level alarms. Different profiles can be applied at different levels. For example, you could use the inherited or default profile on a node and on all cards and ports, but apply a custom profile that downgrades an alarm on one particular card. Or you might choose to downgrade an OC-N unequipped path alarm (UNEQ-P) from Critical (CR) to Not Alarmed (NA) on an optical card because this alarm is raised and then clears every time you create a circuit. UNEQ-P alarms for the card with the custom profile would not display on the Alarms tab (but they would still be recorded on the Conditions and History tabs). When you modify severities in an alarm profile: • All Critical (CR) or Major (MJ) default or user-defined severity settings are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474-CORE. • Default severities are used for all alarms and conditions until you create a new profile and apply it.11-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.4.2 Alarm Profile Buttons 11.4.2 Alarm Profile Buttons The Alarm Profiles window displays six buttons at the bottom. Table 11-8 lists and describes each of the alarm profile buttons and their functions. 11.4.3 Alarm Profile Editing Table 11-9 lists and describes the five profile-editing options available when you right-click an alarm item in the profile column. 11.4.4 Alarm Severity Options To change or assign alarm severity, left-click the alarm severity you want to change in the alarm profile column. Seven severity levels appear for the alarm: • Not-reported (NR) • Not-alarmed (NA) • Minor (MN) • Major (MJ) • Critical (CR) Table 11-8 Alarm Profile Buttons Button Description New Adds a new alarm profile. Load Loads a profile from a node or a file. Store Saves profiles on a node (or nodes) or in a file. Delete Deletes profiles from a node. Compare Displays differences between alarm profiles (for example, individual alarms that are not configured equivalently between profiles). Available Displays all profiles available on each node. Usage Displays all entities (nodes and alarm subjects) present in the network and which profiles contain the alarm. Can be printed. Table 11-9 Alarm Profile Editing Options Button Description Store Saves a profile in a node or in a file. Rename Changes a profile name. Clone Creates a profile that contains the same alarm severity settings as the profile being cloned. Reset Restores a profile to its previous state or to the original state (if it has not yet been applied). Remove Removes a profile from the table editor.11-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.4.5 Row Display Options • Use Default • Inherited (I) Inherited and Use Default severity levels only appear in alarm profiles. They do not appear when you view alarms, history, or conditions. 11.4.5 Row Display Options In the network view, the Alarm Profiles window displays two check boxes at the bottom of the window: • Hide reference values—Highlights alarms with non-default severities by clearing alarm cells with default severities. This check-box is normally greyed out. It becomes active only when more than one profile is listed in the Alarm Profile Editor window. (The check box text changes to “Hide Values matching profile Default” in this case. • Hide identical rows—Hides rows of alarms that contain the same severity for each profile. 11.4.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 alarm profile applies to all cards in the node except cards that have their own profiles. A card alarm profile applies to all ports on the card except ports that have their own profiles. At the node level, you can apply profile changes on a card-by-card basis or set a profile for the entire node. At the card view, you can apply profile changes on a port-by-port basis or set alarm profiles for all ports on that card. Figure 11-2 shows an ONS 15310-MA CTX2500 card alarm profile.11-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.5 Alarm Suppression Figure 11-2 Alarm Profile for a 15310-MA CTX2500 Card 11.5 Alarm Suppression The following sections explain alarm suppression features for the ONS 15310-CL and ONS 15310-MA. 11.5.1 Alarms Suppressed for Maintenance When you place a port in OOS,MT administrative state, this raises the alarm suppressed for maintenance (AS-MT) alarm in the Conditions and History windows1 and causes subsequently raised alarms for that port to be suppressed. 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). When you place the port back into IS,AINS administrative state, the AS-MT alarm is resolved in all three windows. Suppressed alarms remain raised in the Conditions window until they are cleared. 1. AS-MT can be seen in the Alarms window as well if you have set the Filter dialog box to show NA severity events.11-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.5.2 Alarms Suppressed by User Command 11.5.2 Alarms Suppressed by User Command In the Provisioning > Alarm Profiles > Alarm Behavior tabs, the ONS 15310-CL and ONS 15310-MA have an alarm suppression option that clears raised alarm messages for the node, chassis, one or more slots (cards), or one or more ports. Using this option raises the alarms suppressed by user command, or AS-CMD alarm. The AS-CMD alarm, like the AS-MT alarm, appears in the Conditions, and History1 windows. Suppressed conditions (including alarms) appear only in the Conditions window--showing their normal severity in the Sev column. When the Suppress Alarms check box is unchecked, the AS-CMD alarm is cleared from all three windows. A suppression command applied at a higher level does not supersede a command applied at a lower level. For example, applying a node-level alarm suppression command makes all raised alarms for the node appear to be cleared, but it does not cancel out card-level or port-level suppression. Each of these conditions can exist independently and must be cleared independently. Caution Use alarm suppression with caution. If multiple CTC or TL1 sessions are open, suppressing the alarms in one session suppresses the alarms in all other open sessions. 11.6 External Alarms and Controls External alarm physical connections are made with the ONS 15310-CL or ONS 15310-MA ALARM port. However, the alarms are provisioned using the 15310-CL-CTX or CTX2500 card view for external sensors such as an open door and flood sensors, temperature sensors, and other environmental conditions. External control outputs on the 15310-CL-CTX and CTX2500 cards allow you to drive external visual or audible devices such as bells and lights. They can control other devices such as generators, heaters, and fans. Provision external alarms in the 15310-CL-CTX or CTX2500 card view Provisioning > External Alarms tab and provision controls in the 15310-CL-CTX or CTX2500 card view Provisioning > External Controls tab. Up to 32 alarm contact inputs and 8 alarm contact outputs are available with the 15310-MA-CTX2500 cards. The 15310-CL-CTX cards report 3 alarm inputs and 2 alarm outputs. 11.6.1 External Alarm Input You can provision each alarm input separately. Provisionable characteristics of external alarm inputs include: • Alarm type • Alarm severity (CR, MJ, MN, NA, and NR) • Alarm-trigger setting (open or closed); open means that the normal condition is to have current flowing through the contact, and the alarm is generated when the current stops flowing; closed means that normally no current flows through the contact, and the alarm is generated when current does flow. • Virtual wire associated with the alarm • CTC alarm log description (up to 63 characters)11-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.6.2 External Control Output Note If you provision an external alarm to raise when a contact is open, and you have not attached the alarm cable, the alarm will remain raised until the alarm cable is connected. Note When you provision an external alarm, the alarm object is ENV-IN-nn. The variable nn refers to the external alarm’s number, regardless of the name you assign. 11.6.2 External Control Output You can provision each alarm output separately. Provisionable characteristics of alarm outputs include: • Control type • Trigger type (alarm or virtual wire) • Description for CTC display • Closure setting (manually or by trigger). If you provision the output closure to be triggered, the following characteristics can be used as triggers: – Local NE alarm severity—A chosen alarm severity (for example, Major) and any higher-severity alarm (in this case, Critical) causes output closure – Remote NE alarm severity—Similar to local NE alarm severity trigger setting, but applies to remote alarms – Virtual wire entities—You can provision an alarm that is input to a virtual wire to trigger an external control output11-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 11 Alarm Monitoring and Management 11.6.2 External Control OutputCHAPTER 12-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 12 Performance Monitoring Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration. Performance monitoring (PM) parameters are used by service providers to gather, store, threshold, and report performance data for early detection of problems. In this chapter, PM parameters and concepts are defined for electrical cards, Ethernet cards, and optical cards in the Cisco ONS 15310-CL and Cisco ONS 15310-MA. For information about enabling and viewing PM parameters, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Chapter topics include: • 12.1 Threshold Performance Monitoring, page 12-2 • 12.2 Intermediate-Path Performance Monitoring, page 12-3 • 12.3 Pointer Justification Count Performance Monitoring, page 12-3 • 12.4 Performance Monitoring Parameter Definitions, page 12-4 • 12.5 Performance Monitoring for Electrical Ports, page 12-10 • 12.6 Performance Monitoring for Ethernet Cards, page 12-15 • 12.7 Performance Monitoring for Optical Ports, page 12-20 Note For additional information regarding PM parameters, refer to Telcordia’s GR-1230-CORE, GR-499-CORE, and GR-253-CORE documents, the Telcordia GR-820-CORE document titled Generic Digital Transmission Surveillance, and the ANSI T1.231 document entitled Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring.12-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.1 Threshold Performance Monitoring 12.1 Threshold Performance Monitoring Thresholds are used to set error levels for each PM parameter. You can program PM parameter threshold ranges from the Provisioning > Line Thresholds tab in card view. For procedures for provisioning card thresholds, such as line, path, and SONET thresholds, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. During the accumulation cycle, if the current value of a PM parameter reaches or exceeds its corresponding threshold value, a threshold crossing alert (TCA) is generated by the node and is sent to CTC. TCAs provide early detection of performance degradation. When a threshold is crossed, the node continues to count the errors during a given accumulation period. If 0 is entered as the threshold value, the PM parameter is disabled. Change the threshold if the default value does not satisfy your error monitoring needs. For example, customers with a critical DS-1 installed for 911 calls must guarantee the best quality of service on the line; therefore, they lower all thresholds so that the slightest error raises a TCA. When TCAs occur, CTC displays them in the Alarms tab. For example, in Figure 12-1, T-UASP-P is shown under the Cond column. The “T-” indicates a threshold crossing alert. For the DS-1 and DS-3/EC-1 electrical ports on the 15310-CL-CTX card and the 15310-MA DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards, RX or TX is appended to the TCA description (see the red circles in Figure 12-1). RX indicates that the TCA is associated with the receive direction, and TX indicates the TCA is associated with the transmit direction. Figure 12-1 TCAs Displayed in CTC For electrical ports, only the receive direction is detected and appended to TCA descriptions. The DS-1 and DS-3/EC-1 ports for which RX is appended to TCA descriptions are shown in Table 12-1.12-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.2 Intermediate-Path Performance Monitoring 12.2 Intermediate-Path Performance Monitoring Intermediate-path performance monitoring (IPPM) allows transparent monitoring of a constituent channel of an incoming transmission signal by a node that does not terminate that channel. You can program IPPM from the Provisioning > Optical > SONET STS tab in card view. Many large ONS 15310-CL and ONS 15310-MA networks only use line terminating equipment (LTE), not path terminating equipment (PTE). Software Release 5.0 and later allows monitoring of near-end PM parameter data on individual STS payloads by enabling IPPM. After enabling IPPM provisioning on the line card, service providers can monitor large amounts of synchronous transport signal (STS) traffic through intermediate nodes, thus making troubleshooting and maintenance activities more efficient. IPPM occurs only on STS paths that have IPPM enabled, and TCAs are raised only for PM parameters on the selected IPPM paths. The monitored IPPM parameters are STS CV-P, STS ES-P, STS SES-P, STS UAS-P, and STS FC-P. Note Far-end IPPM is not supported. However, SONET path PM parameters can be monitored by logging into the far-end node directly. The ONS 15310-CL and ONS 15310-MA perform IPPM by examining the overhead in the monitored path and by reading all of the near-end path PM parameters in the incoming direction of transmission. The IPPM process allows the path signal to pass bidirectionally through the node completely unaltered. The ONS 15310-MA also supports IPPM for SONET Virtual Tributary (VT). For detailed information about specific PM parameters, locate the card name in the following sections and review the appropriate definition. 12.3 Pointer Justification Count Performance Monitoring Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on SONET networks. When a network is out of sync, jitter and wander occurs on the transported signal. Excessive wander can cause terminating equipment to slip. It also causes slips at the synchronous digital hierarchy (SDH) and plesiochronous digital hierarchy (PDH) boundaries. Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses the encryption key, causing data to be transmitted again. Table 12-1 Electrical Ports that Report RX Direction for TCAs Port Line Path Near End Far End Near End Far End DS-1 YES YES YES YES DS-3 YES — YES YES EC-1 YES YES YES YES12-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.4 Performance Monitoring Parameter Definitions Pointers provide a way to align the phase variations in STS and VT payloads. The STS payload pointer is located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE), called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss. You can enable positive pointer justification count (PPJC) and negative pointer justification count (NPJC) PM parameters for LTE cards. PPJC is a count of path-detected (PPJC-Pdet) or path-generated (PPJC-Pgen) positive pointer justifications. NPJC is a count of path-detected (NPJC-Pdet) or path-generated (NPJC-Pgen) negative pointer justifications, depending on the specific PM parameter. A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means that the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS 1. For pointer justification count definitions, depending on the cards in use, see the “12.7.1 OC-3 Port Performance Monitoring Parameters” section on page 12-20 and the “12.7.2 OC-12 Port Performance Monitoring Parameters” section on page 12-22. In CTC, the count fields for PPJC and NPJC PM parameters appear white and blank unless they are enabled on the Provisioning > Optical > Line tab PJStsMon# drop-down list. 12.4 Performance Monitoring Parameter Definitions Table 12-2 gives a definition for each type of PM parameter found in the ONS 15310-CL and ONS 15310-MA. Table 12-2 Performance Monitoring Parameters Parameter Definition AISS-P Alarm Indication Signal Seconds Path (AISS-P) is a count of one-second intervals containing one or more AIS defects. CV-L Line Code Violations (CV-L) indicates the number of coding violations occurring on the line. This parameter is a count of bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the accumulation period. CV-LFE Far-End Line Coding Violations (CV-LFE) is a count of BIP errors detected by the far-end LTE and reported back to the near-end LTE using the Line Remote Error Indication (REI-L) in the line overhead. For SONET signals at rates below OC-48, up to 8 x n BIP errors per STS-N frame can be indicated using the REI-L indication. For OC-48 signals, up to 255 BIP errors per STS-N frame can be indicated. The current CV-L second register is incremented for each BIP error indicated by the incoming REI-L. CV-P Near-End STS Path Coding Violations (CV-P) is a count of BIP errors detected at the STS path layer (that is, using the B3 byte). Up to eight BIP errors can be detected per frame; each error increments the current CV-P second register. CV-PFE Far-End STS Path Coding Violations (CV-PFE) is a count of BIP errors detected at the STS path layer (that is, using the B3 byte). Up to eight BIP errors can be detected per frame; each error increments the current CV-PFE second register.12-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.4 Performance Monitoring Parameter Definitions CV-S Section Coding Violations (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). Up to eight section BIP errors can be detected per STS-N frame; each error increments the current CV-S second register. CV-V VT Layer Coding Violations (CV-V) is a count of the BIP errors detected at the VT path layer. Up to two BIP errors can be detected per VT superframe, with each error incrementing the current CV-V second register. CV-VFE Far-End VT Path Coding Violations (CV-VFE) is a count of the number of BIP errors detected by the far-end VT PTE and reported back to the near-end VT PTE using the VT Layer REI (REI-V) in the VT path overhead. Only one BIP error can be indicated per VT superframe using the REI-V bit. The current CV-VFE second register is incremented for each BIP error indicated by the incoming REI-V. ES-L Line Errored Seconds (ES-L) is a count of the seconds containing one or more anomalies (BPV + EXZ) and/or defects (that is, loss of signal) on the line. ES-LFE ES-LFE is a count of the seconds when at least one line-layer BIP error was reported by the far-end LTE or a RDI-L defect was present. ES-P Near-End STS Path Errored Seconds (ES-P) is a count of the seconds when at least one STS path BIP error was detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an ES-P. ES-PFE Far-End STS Path Errored Seconds (ES-PFE) is a count of the seconds when at least one STS path BIP error was detected. An AIS-P defect (or a lower-layer, traffic-related, far-end defect) or an LOP-P defect can also cause an STS ES-PFE. 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 a severely errored frame (SEF) or loss of signal (LOS) defect was present. ES-V Errored Seconds VT Layer (ES-V) is a count of the seconds when at least one VT Path BIP error was detected. An AIS-V defect (or a lower-layer, traffic-related, near-end defect) or an LOP-V defect can also cause an ES-V. ES-VFE Far-End VT Path Errored Seconds (ES-VFE) is a count of the seconds when at least one VT path BIP error was reported by the far-end VT PTE, or a one-bit RDI-V defect is present. FC-L Line Failure Count (FC-L) is a count of the number of near-end line failure events. A failure event begins when an AIS-L failure is declared or when a lower-layer, traffic-related, near-end failure is declared. This failure event ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period where it begins. Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition12-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.4 Performance Monitoring Parameter Definitions FC-LFE FC-LFE is a count of the number of far-end line failure events. A failure event begins when an RFI-L failure is declared, and it ends when the RFI-L failure clears. A failure event that begins in one period and ends in another period is counted only in the period where it began. FC-P Near-End STS Path Failure Counts (FC-P) is a count of the number of near-end STS path failure events. A failure event begins when an AIS-P failure, an LOP-P failure, a UNEQ-P failure, or a TIM-P failure is declared. A failure event also begins if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared. FC-PFE Far-End STS Path Failure Counts (FC-PFE) is a count of the number of near-end STS path failure events. A failure event begins when an AIS-P failure, an LOP-P failure, a UNEQ-P failure, or a TIM-P failure is declared. A failure event also begins if the STS PTE that is monitoring the path supports ERDI-P for that path. The failure event ends when these failures are cleared. LBC-HIGH Laser Bias Current—High (LBC-HIGH) is the highest percentage of laser bias current measured. LBC-LOW Laser Bias Current—LOW (LBC-LOW) is the lowest percentage of laser bias current measured. LOSS-L Line Loss of Signal (LOSS-L) is a count of one-second intervals containing one or more LOS defects. NPJC-PDET Negative Pointer Justification Count, STS Path Detected (NPJC-PDET). NPJC-PDET-P Negative Pointer Justification Count, STS Path Detected (NPJC-PDET-P) is a count of the negative pointer justifications detected on a particular path in an incoming SONET signal. NPJC-PGEN-P Negative Pointer Justification Count, STS Path Generated (NPJC-PGEN-P) is a count of the negative pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock. OPR-HIGH Optical Power Received—High (OPR-HIGH) is the measure of highest optical power received as a percentage of the nominal OPR. OPR-LOW Optical Power Received—Low (OPR-LOW) is the measure of lowest optical power received as a percentage of the nominal OPR. OPT-HIGH Optical Power Transmitted—High (OPT-HIGH) is the measure of highest optical power transmitted as a percentage of the nominal OPT. OPT-LOW Optical Power Transmitted—Low (OPT-LOW) is the measure of lowest optical power transmitted as a percentage of the nominal OPT. PJC-DIFF-P Pointer Justification Count Difference, STS Path (PJC-DIFF-P) is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. That is, PJC-DIFF-P is equal to (PPJC-PGEN – NPJC-PGEN) – (PPJC-PDET – NPJC-PDET). Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition12-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.4 Performance Monitoring Parameter Definitions PJCS-PDET-P Pointer Justification Count Seconds, STS Path Detected (PJCS-PDET-P) is a count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P Pointer Justification Count Seconds, STS Path Generated (PJCS-PGEN-P) is a count of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN. PPJC-PDET Positive Pointer Justification Count, STS Path Detected (PPJC-PDET) is a count of the positive pointer justifications detected on a particular path on an incoming SONET signal. PPJC-PDET-P Positive Pointer Justification Count, STS Path Detected (PPJC-PDET-P) is a count of the positive pointer justifications detected on a particular path in an incoming SONET signal. 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. PSC (1+1) In a 1+1 protection scheme for a working card, Protection Switching Count (PSC) is a count of the number of times service switches from a working card to a protection card plus the number of times service switches back to the working card. For a protection card, PSC is a count of the number of times service switches to a working card from a protection card plus the number of times service switches back to the protection card. The PSC PM is only applicable if revertive line-level protection switching is used. PSC (BLSR) For a protect line in a two-fiber bidirectional line switched ring (BLSR), PSC refers to the number of times a protection switch has occurred either to a particular span's line protection or away from a particular span's line protection. Therefore, if a protection switch occurs on a two-fiber BLSR, the PSC of the protection span to which the traffic is switched will increment, and when the switched traffic returns to its original working span from the protect span, the PSC of the protect span will increment again. PSD Protection Switching Duration (PSD) applies to the length of time, in seconds, that service is carried on another line. For a working line, PSD is a count of the number of seconds that service was carried on the protection line. For the protection line, PSD is a count of the seconds that the line was used to carry service. The PSD PM is only applicable if revertive line-level protection switching is used. Rx AISS-P Receive Path Alarm Indication Signal (Rx AISS-P) means that an AIS occurred on the receive end of the path. This parameter is a count of seconds containing one or more AIS defects. Rx CSS-P Receive Path Controlled Slip Seconds (Rx CSS-P) is a count of seconds during which a controlled slip has occurred. Counts of controlled slips can be accurately made only in the path terminating network element (NE) of the DS-1 signal where the controlled slip takes place. Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition12-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.4 Performance Monitoring Parameter Definitions Rx CV-P Receive Path Coding Violation (Rx CV-P) means that a coding violation occurred on the receive end of the path. For DS-1 extended super frame (ESF) paths, this parameter is a count of detected cyclic redundancy check (CRC)-6 errors. For the DS-1 super frame (SF) paths, the Rx CV-P parameter is a count of detected frame-bit errors (FE). Rx ES-P Receive Path Errored Seconds (Rx ES-P) is a count of the seconds containing one or more anomalies and/or defects for paths on the receive end of the signal. For DS1-ESF paths, this parameter is a count of one-second intervals containing one or more CRC-6 errors, one or more convergence sublayer (CS) events, or one or more SEF or AIS defects. For DS-1 SF paths, the Rx ES-P parameter is a count of one-second intervals containing one or more FE events, one or more CS events, or one or more SEF or AIS defects. Rx ESA-P Errored Second Type A is a count of one second intervals with exactly one CRC-6 error and no SEF or AIS defects. Rx ESB-P Errored Second Type B is a count of one second intervals with no less than 2 and no more than 319 CRC-6 errors, no SEF defects, and no AIS defects. Rx SAS-P Receive Path Severely Errored Seconds Frame/Alarm Indication Signal (Rx SAS-P) is a count of one-second intervals containing one or more SEFs or one or more AIS defects on the receive end of the signal. Rx SEFS-P Receive Path Severely Errored Frame-Path (SEFS-P) is a count of one-second performance report message (PRM) intervals containing an SE=1. Rx SES-P Receive Path Severely Errored Seconds (Rx SES-P) is a count of the seconds containing more than a particular quantity of anomalies and/or defects for paths on the receive end of the signal. For the DS1-ESF paths, this parameter is a count of seconds when 320 or more CRC-6 errors or one or more SEF or AIS defects occurred. For DS1-SF paths, SES is a second containing either the occurrence of four FEs or one or more SEF or AIS defects. Rx UAS-P Receive Path Unavailable Seconds (Rx UAS-P) is a count of one-second intervals when the DS-1 path is unavailable on the receive end of the signal. The DS-1 path is unavailable at the onset of 10 consecutive seconds that qualify as SESs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SES-Ps. The ten seconds with no SES-Ps are excluded from unavailable time. SEFS-S Severely Errored Framing Seconds (SEFS-S) is a count of the seconds when an SEF defect was present. An SEF defect is expected to be present during most seconds when an LOS or loss of frame (LOF) defect is present. However, there can be situations when the SEFS-S parameter is only incremented based on the presence of the SEF defect. SES-L Line Severely Errored Seconds (SES-L) is a count of the seconds containing more than a particular quantity of anomalies (BPV + EXZ > 1544) and/or defects on the line. Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition12-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.4 Performance Monitoring Parameter Definitions SES-LFE SES-LFE is a count of the seconds when K (see Telcordia GR-253-CORE for values) or more line-layer BIP errors were reported by the far-end LTE or an RDI-L defect was present. SES-P Near-End STS Path Severely Errored Seconds (SES-P) is a count of the seconds when K (2400) or more STS path BIP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an SES-P. SES-PFE Far-End STS Path Severely Errored Seconds (SES-PFE) is a count of the seconds when K (2400) or more STS path BIP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, far-end defect) or an LOP-P defect can also cause an SES-PFE. SES-S Section Severely Errored Seconds (SES-S) is a count of the seconds when K (see Telcordia GR-253 for value) or more section-layer BIP errors were detected or an SEF or LOS defect was present. SES-V Severely Errored Seconds VT Layer (SES-V) is a count of seconds when K (600) or more VT Path BIP errors were detected. An AIS-V defect (or a lower-layer, traffic-related, near-end defect) or an LOP-V defect can also cause SES-V. SES-VFE Far-End VT Path Severely Errored Seconds (SES-VFE) is a count of the seconds when K (600) or more VT path BIP errors were reported by the far-end VT PTE or a one-bit RDI-V defect was present. Tx AISS-P Transmit Path Alarm Indication Signal Seconds (Tx AISS-P) means that an alarm indication signal occurred on the transmit end of the path. This parameter is a count of seconds containing one or more AIS defects. Tx CV-P Transmit Path Coding Violation (Tx CV-P) means that a coding violation occurred on the transmit end of the path. For DS-1 ESF paths, this parameter is a count of detected CRC-6 errors. For the DS-1 SF paths, the Tx CV-P parameter is a count of detected FEs. Tx ES-P Transmit Path Errored Seconds (Tx ES-P) is a count of the seconds containing one or more anomalies and/or defects for paths on the transmit end of the signal. For DS-1 ESF paths, this parameter is a count of one-second intervals containing one or more CRC-6 errors, one or more CS events, or one or more SEF or AIS defects. For DS-1 SF paths, the Tx ES-P parameter is a count of one-second intervals containing one or more FE events, one or more CS events, or one or more SEF or AIS defects. Tx SAS-P Transmit Path Severely Errored Seconds Frame/Alarm Indication Signal (Tx SAS-P) is a count of one-second intervals containing one or more SEFs or one or more AIS defects on the transmit end of the signal. Tx SES-P Transmit Path Severely Errored Seconds (Tx SES-P) is a count of the seconds containing more than a particular quantity of anomalies and/or defects for paths on the transmit end of the signal. For the DS-1 ESF paths, this parameter is a count of seconds when 320 or more CRC-6 errors or one or more SEF or AIS defects occurred. For DS-1 SF paths, an SES is a second containing either the occurrence of four FEs or one or more SEF or AIS defects. Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition12-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.5 Performance Monitoring for Electrical Ports 12.5 Performance Monitoring for Electrical Ports The following sections define PM parameters for the DS-1 and DS-3 electrical ports. 12.5.1 DS-1 Port Performance Monitoring Parameters Figure 12-2 shows the signal types that support near-end and far-end PM parameters. Tx UAS-P Transmit Path Unavailable Seconds (Tx UAS-P) is a count of one-second intervals when the DS-1 path is unavailable on the transmit end of the signal. The DS-1 path is unavailable at the onset of 10 consecutive seconds that qualify as SESs, and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as SESs. UAS-L Line Unavailable Seconds (UAS-L) is a count of the seconds when the line is unavailable. A line becomes unavailable when ten consecutive seconds occur that qualify as SES-Ls, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-Ls. UAS-LFE UAS-LFE is a count of the seconds when the line is unavailable at the far end. A line becomes unavailable at the onset of ten consecutive seconds that qualify as SES-LFEs, and continues to be unavailable until the onset of ten consecutive seconds occur s that do not qualify as SES-LFEs. UAS-P Near-End STS Path Unavailable Seconds (UAS-P) is a count of the seconds when the STS path was unavailable. An STS path becomes unavailable when ten consecutive seconds occur that qualify as SES-Ps, and continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-Ps. UAS-PFE Far-End STS Path Unavailable Seconds (UAS-PFE) is a count of the seconds when the STS path was unavailable. An STS path becomes unavailable when ten consecutive seconds occur that qualify as SES-PFEs, and continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-PFEs. UAS-V VT Layer Unavailable Seconds (UAS-V) is a count of the seconds when the VT path was unavailable. A VT path becomes unavailable when ten consecutive seconds occur that qualify as SES-Vs, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-Vs. UAS-VFE Far-End VT Path Unavailable Seconds (UAS-VFE) is a count of the seconds when the VT path is unavailable at the far-end. A VT path is considered unavailable at the onset of ten consecutive seconds that qualify as SES-VFEs, and continues to be considered unavailable until the onset of 10 consecutive seconds that do not qualify as SES-VFEs. Table 12-2 Performance Monitoring Parameters (continued) Parameter Definition12-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.5.1 DS-1 Port Performance Monitoring Parameters Figure 12-2 Monitored Signal Types for the DS-1 Ports Note The XX in Figure 12-2 represents all PM parameters listed in Figure 12-3 with the given prefix and/or suffix. Figure 12-3 shows where overhead bytes detected on the application-specific integrated circuits (ASICs) produce PM parameters for the DS-1 ports. Figure 12-3 PM Parameter Read Points on the DS-1 Ports ONS 15310 PTE DS1 OC-N Fiber DS1 Signal DS1 Path (DS1 XX) PMs Near and Far End Supported DS1 Signal ONS 15310 OC-N DS1 VT Path (XX-V) PMs Near and Far End Supported STS Path (STS XX-P) PMs Near and Far End Supported PTE 124439 ONS 15310 DS1 Ports LIU Framer BTC Tx/Rx Cross Connect OC-N DS1 CV-L DS1 ES-L DS1 SES-L DS1 LOSS-L DS1 Rx AISS-P DS1 Rx CV-P DS1 Rx ES-P DS1 Rx SAS-P DS1 Rx SES-P DS1 Rx UAS-P DS1 Tx AISS-P DS1 Tx CV-P DS1 Tx ES-P DS1 Tx SAS-P DS1 Tx SES-P DS1 Tx UAS-P PMs read on LIU DS1 Side VT Level Path Level SONET Side CV-V ES-V SES-V UAS-V STS CV-P STS ES-P STS FC-P STS SES-P STS UAS-P STS CV-PFE STS ES-PFE STS FC-PFE STS SES-PFE STS UAS-PFE PMs read on Framer 12444012-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.5.2 DS-3 Port Performance Monitoring Parameters The PM parameters for the DS-1 ports are listed in Table 12-3. Note Under the Provisioning > DS1 > SONET Threshold tab, the 15310-CL-CTX, DS1-28/DS3-EC1-3, and DS1-84/DS3-EC1-3 cards have user-defined thresholds for the DS-1 receive (Rx) path PM parameters. In the SONET Threshold tab they appear as CV, ES, FC, SES, and UAS without the Rx prefix. Note Under the Performance tab, the displayed DS-1 Tx path PM parameter values are based on calculations performed by the card and therefore have no user-defined thresholds. The tab is labeled Elect[rical] Path Threshold. 12.5.2 DS-3 Port Performance Monitoring Parameters Figure 12-4 shows the signal types that support near-end and far-end PM parameters. Figure 12-4 Monitored Signal Types for the DS-3 Ports Note The XX in Figure 12-4 represents all PM parameters listed in Figure 12-5 with the given prefix and/or suffix. Table 12-3 PM Parameters for DS-1 Ports Line (NE) Rx Path (NE) Tx Path (NE) VT Path (NE) STS Path (NE) VT Path (FE) STS Path (FE) CV-L ES-L SES-L LOSS-L AISS-P CV-P ES-P FC-P SAS-P SES-P UAS-P CSS-P ESA-P ESB-P SEFS-P AISS-P CV-P ES-P FC-P SAS-P SES-P UAS-P CV-V ES-V FC-V SES-V UAS-V CV-P ES-P FC-P SES-P UAS-P FC-P CV-VFE ES-VFE SES-VFE UAS-VFE CV-PFE ES-PFE SES-PFE UAS-PFE FC-PFE ONS 15310 PTE DS3 OC-N Fiber DS3 Signal DS3 Path (DS3 XX) PMs Near and Far End Supported DS3 Signal ONS 15310 OC-N DS3 STS Path (STS XX-P) PMs Near and Far End Supported PTE 12444112-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.5.3 EC-1 Port Performance Monitoring Parameters Figure 12-5 shows where overhead bytes detected on the ASICs produce PM parameters for the DS-3 ports. Figure 12-5 PM Parameter Read Points on the DS-3 Ports The PM parameters for the DS-3 ports are listed in Table 12-4. 12.5.3 EC-1 Port Performance Monitoring Parameters Figure 12-6 shows signal types that support near-end and far-end PM parameters. Figure 12-7 shows where overhead bytes detected on the ASICs produce PM parameters for the EC1 port. ONS 15310 DS3 Ports LIU Mux/Demux ASIC BTC ASIC Cross Connect OC-N DS3 Side Path Level SONET Side STS CV-P STS ES-P STS FC-P STS SES-P STS UAS-P STS CV-PFE STS ES-PFE STS FC-PFE STS SES-PFE STS UAS-PFE DS3 CV-L DS3 ES-L DS3 SES-L DS3 LOSS-L PMs read on Mux/Demux ASIC PMs read on LIU 124442 Table 12-4 Parameters for DS-3 Ports Line (NE) Path (NE) STS Path (NE) Path (FE)1 1. The C-bit PM parameters (PM parameters that end in “CPP”) are applicable only if the line format is C-bit. STS Path (FE) CV-L ES-L SES-L LOSS-L AISS-P CVP-P ESP-P SASP-P SESP-P UASP-P CVCP-P ESCP-P SASCP-P SESCP-P UASCP-P CV-P ES-P SES-P UAS-P FC-P CVCP-PFE ESCP-PFE SASCP-PFE SESCP-PFE UASCP-PFE CV-PFE ES-PFE SES-PFE UAS-PFE FC-PFE12-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.5.3 EC-1 Port Performance Monitoring Parameters Figure 12-6 Monitored Signal Types for the EC-1 Port Note The XX in Figure 12-6 represents all PM parameters listed in Table 12-5 with the given prefix and/or suffix. Figure 12-7 PM Read Points on the EC-1 Port Table 12-5 lists the PM parameters for the EC-1 ports. 124453 ONS 15310 PTE EC1 OC-N Fiber EC1 Signal EC1 Path (EC1 XX) PMs Near and Far End Supported EC1 Signal ONS 15310 OC-N EC1 STS Path (STS XX-P) PMs Near and Far End Supported PTE 124454 ONS 15310 EC1 LIU Framer BTC Tx/Rx XC10G Card OC-N EC1 Side SONET Side STS CV-P STS ES-P STS FC-P STS SES-P STS UAS-P STS CV-PFE STS ES-PFE STS FC-PFE STS SES-PFE STS UAS-PFE CV-S ES-S SES-S SEFS-S CV-L SES-L ES-L UAS-L FC-L PPJC-Pdet NPJC-Pdet PPJC-Pgen NPJC-Pgen PMs read on LIU PMs read on Framer12-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.6 Performance Monitoring for Ethernet Cards 12.6 Performance Monitoring for Ethernet Cards The following sections define PM parameters and definitions for the CE-100T-8 and ML-100T-8 Ethernet cards. 12.6.1 CE-100T-8 and ML-100T-8 Card Ethernet Performance Monitoring Parameters CTC provides Ethernet performance information, including line-level parameters, port bandwidth consumption, and historical Ethernet statistics. The CE-100T-8 and ML-100T-8 card Ethernet performance information is divided into Ether Ports and POS Ports tabbed windows within the card view Performance tab window. 12.6.1.1 CE-100T-8 and ML-100T-8 Card Ether Ports Statistics Window The Ether Ports statistics window lists Ethernet parameters at the line level. The Ether Ports 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. The window also has a Clear button. The Clear button sets the values on the card to zero, but does not reset the CE-100T-8 and ML-100T-8 cards. During each automatic cycle, whether auto-refreshed or manually refreshed (using the Refresh button), statistics are added cumulatively and are not immediately adjusted to equal total received packets until testing ends. To see the final PM count totals, allow a few moments for the PM window statistics to finish testing and update fully. PM counts are also listed in the CE-100T-8 and ML-100T-8 card Performance > History window. Table 12-6 defines the CE-100T-8 and ML-100T-8 card Ether Ports statistics parameters. Table 12-5 EC-1 Port PM Parameters Section (NE) Line (NE) STS Path (NE) Line (FE) STS Path (FE) CV-S ES-S SES-S SEFSCV-L ES-L SES-L UAS-L FC-L CV-P ES-P SES-P UAS-P FC-P PPJC-PDET-P NPJC-PDET-P PPJC-PGEN-P NPJC-PGEN-P PJCS-PDET-P PJCS-PGEN-P PJC-DIFF-P CV-LFE ES-LFE SES-LFE UAS-LFE FC-LFE CV-PFE ES-PFE SES-PFE UAS-PFE FC-PFE12-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.6.1 CE-100T-8 and ML-100T-8 Card Ethernet Performance Monitoring Parameters Table 12-6 CE-100T-8 and ML-100T-8 Ether Ports Statistics Parameters Parameter Definition Time Last Cleared A time stamp indicating the last time statistics were reset. Link Status Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present. iflnOctets The total number of octets received on the interface, including framing octets. txTotalPkts The total number of transmit packets. rxTotalPkts The total number of receive packets. iflnUcastPkts The total number of unicast packets delivered to an appropriate protocol. ifInMulticastPkts Number of multicast frames received error free. ifInBroadcastPkts The number of packets, delivered by this sublayer to a higher (sub)layer, that were addressed to a broadcast address at this sublayer. ifInDiscards The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent them from being deliverable to a higher-layer protocol. iflnErrors Number of inbound packets discarded because they contain errors. ifOutOctets The total number of transmitted octets, including framing packets. ifOutUcastPkts The total number of unicast packets requested to transmit to a single address. ifOutMulticastPkts Number of multicast frames transmitted error free. ifOutBroadcastPkts The total number of packets that higher-level protocols requested be transmitted, and that were addressed to a broadcast address at this sublayer, including those that were discarded or not sent. dot3statsAlignmentErrors The number of frames with an alignment error, that is, frames with a length that is not an integral number of octets and where the frame cannot pass the frame check sequence (FCS) test. dot3StatsFCSErrors The number of frames with frame check errors, that is, where there is an integral number of octets, but an incorrect FCS. dot3StatsSingleCollisionFrames The number of successfully transmitted frames that had exactly one collision. dot3StatsFrameTooLong The count of frames received on a particular interface that exceed the maximum permitted frame size. etherStatsUndersizePkts The number of packets received with a length less than 64 octets. etherStatsFragments The total number of packets that are not an integral number of octets or have a bad FCS, and that are less than 64 octets long. etherStatsPkts64Octets The total number of packets received (including error packets) that were 64 octets in length. etherStatsPkts65to127Octets The total number of packets received (including error packets) that were 65 to 172 octets in length.12-17 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.6.1 CE-100T-8 and ML-100T-8 Card Ethernet Performance Monitoring Parameters 12.6.1.2 CE-100T-8 and ML-100T-8 Card Ether Ports Utilization Window The Ether Ports Utilization window shows the percentage of Tx and Rx line bandwidth used by the Ethernet ports during consecutive time segments. The Ether Ports Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 1 day. Line utilization for Ethernet ports is calculated with the following formulas: Rx = (inOctets + inPkts * 20) * 8 / 100% interval * maxBaseRate Tx = (outOctets + outPkts * 20) * 8 / 100% interval * maxBaseRate The interval is defined in seconds. The maxBaseRate is defined by raw bits per second in one direction for the Ethernet port (that is, 1 Gbps). The maxBaseRate for CE-100T-8 and ML-100T-8 Ethernet cards is shown in Table 12-7. etherStatsPkts128to255Octets The total number of packets received (including error packets) that were 128 to 255 octets in length. etherStatsPkts256to511Octets The total number of packets received (including error packets) that were 256 to 511 octets in length. etherStatsPkts512to1023Octets The total number of packets received (including error packets) that were 512 to 1023 octets in length. etherStatsPkts1024to1518Octets The total number of packets received (including error packets) that were 1024 to 1518 octets in length. etherStatsBroadcastPkts The total number of good packets received that were directed to the broadcast address. This does not include multicast packets. etherStatsMulticastPkts The total number of good packets received that were directed to a multicast address. This number does not include packets directed to the broadcast. etherStatsOversizePkts The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. etherStatsJabbers The total number of packets longer than 1518 octets that were not an integral number of octets or had a bad FCS. etherStatsOctets The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). etherStatsCollisions The best estimate of the total number of collisions on this segment. etherStatsCRCAlignErrors The total number of packets with a length between 64 and 1518 octets, inclusive, that had a bad FCS or were not an integral number of octets in length. etherStatsDropEvents The total number of events in which packets were dropped by the probe due to lack of resources. This number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. Table 12-6 CE-100T-8 and ML-100T-8 Ether Ports Statistics Parameters (continued) Parameter Definition12-18 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.6.1 CE-100T-8 and ML-100T-8 Card Ethernet Performance Monitoring Parameters Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity. 12.6.1.3 CE-100T-8 and ML-100T-8 Card Ether Ports History Window The Ether Ports History window lists past Ethernet statistics for the previous time intervals. Depending on the selected time interval, the Ether Ports History window displays the statistics for each port for the number of previous time intervals as shown in Table 12-8. The parameters are defined in Table 12-6 on page 12-16. 12.6.1.4 CE-100T-8 and ML-100T-8 Card POS Ports Statistics Parameters In the CE-100T-8 and ML-100T-8 POS Ports window, the parameters that appear depend on the framing mode employed by the cards. The two framing modes for the packet-over-SONET (POS) port on the CE-100T-8 and ML-100T-8 cards are high-level data link control (HDLC) and frame-mapped generic framing procedure (GFP-F). For more information on provisioning a framing mode, refer to Cisco ONS 15310-CL Procedure Guide The POS Ports statistics window lists POS parameters at the line level. Table 12-9 defines the CE-100T-8 and ML-100T-8 card POS ports parameters for HDLC mode. Table 12-7 maxBaseRate for STS Circuits STS maxBaseRate STS-1 51840000 STS-3c 155000000 STS-6c 311000000 STS-12c 622000000 Table 12-8 Ethernet History Statistics per Time Interval Time Interval Number of Intervals Displayed 1 minute 60 previous time intervals 15 minutes 32 previous time intervals 1 hour 24 previous time intervals 1 day (24 hours) 7 previous time intervals Table 12-9 CE-100T-8 and ML-100T-8 POS Ports Parameters for HDLC Mode Parameter Definition Time Last Cleared A time stamp indicating the last time statistics were reset. Link Status Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present. iflnOctets The total number of octets received on the interface, including framing octets.12-19 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.6.1 CE-100T-8 and ML-100T-8 Card Ethernet Performance Monitoring Parameters Table 12-10 defines the CE-100T-8 and ML-100T-8 card POS ports parameter for GFP-F mode. txTotalPkts The total number of transmit packets. ifInDiscards The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. iflnErrors Number of inbound packets discarded because they contain errors. ifOutOctets The total number of transmitted octets, including framing packets. rxTotalPkts The total number of receive packets. ifOutOversizePkts Number of packets larger than 1518 bytes sent out into SONET. Packets larger than 1600 bytes do not get transmitted. mediaIndStatsRxFramesBadCRC A count of the received Fibre Channel frames with errored CRCs. hdlcRxAborts Number of received packets aborted before input. ifInPayloadCRCErrors The number of receive data frames with payload CRC errors. ifOutPayloadCRCErrors The number of transmit data frames with payload CRC errors. Table 12-9 CE-100T-8 and ML-100T-8 POS Ports Parameters for HDLC Mode (continued) Parameter Definition Table 12-10 CE-100T-8 and ML-100T-8 POS Ports Parameters for GFP-F Mode Parameter Definition Time Last Cleared A time stamp indicating the last time statistics were reset. Link Status Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present. iflnOctets The total number of octets received on the interface, including framing octets. txTotalPkts The total number of transmit packets. ifInDiscards The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. iflnErrors Number of inbound packets discarded because they contain errors. ifOutOctets The total number of transmitted octets, including framing packets. rxTotalPkts The total number of receive packets. ifOutOversizePkts Number of packets larger than 1518 bytes sent out into SONET. Packets larger than 1600 bytes do not get transmitted. gfpStatsRxSBitErrors Receive frames with single bit errors (cHEC, tHEC, eHEC). gfpStatsRxMBitErrors Receive frames with multibit errors (cHEC, tHEC, eHEC). gfpStatsRxTypeInvalid Receive frames with invalid type (PTI, EXI, UPI). gfpStatsRxCRCErrors Receive data frames with payload CRC errors. gfpStatsRxCIDInvalid Receive frames with invalid CID.12-20 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7 Performance Monitoring for Optical Ports 12.6.1.5 CE-100T-8 and ML-100T-8 Card POS Ports Utilization Window The POS Ports Utilization window shows the percentage of Tx and Rx line bandwidth used by the POS ports during consecutive time segments. The POS Ports Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 1 day. Line utilization for POS ports is calculated with the following formulas: Rx = (inOctets * 8) / (interval * maxBaseRate) Tx = (outOctets * 8) / (interval * maxBaseRate) The interval is defined in seconds. The maxBaseRate is defined by raw bits per second in one direction for the Ethernet port (that is, 1 Gbps). Refer to Table 12-7 on page 12-18 for maxBaseRate values for STS circuits. Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity. 12.6.1.6 CE-100T-8 and ML-100T-8 Card POS Ports History Window The Ethernet POS Ports History window lists past Ethernet POS Ports 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 12-8 on page 12-18. The listed parameters are defined in Table 12-6 on page 12-16. 12.7 Performance Monitoring for Optical Ports The following sections list the PM parameters for the OC-3, OC-12 and OC-48 ports. The listed parameters are defined in Table 12-2 on page 12-4. 12.7.1 OC-3 Port Performance Monitoring Parameters Figure 12-8 shows the signal types that support near-end and far-end PM parameters. gfpStatsCSFRaised Number of Rx client management frames with client signal fail indication. ifInPayloadCRCErrors The number of receive data frames with payload CRC errors. ifOutPayloadCRCErrors The number of transmit data frames with payload CRC errors. Table 12-10 CE-100T-8 and ML-100T-8 POS Ports Parameters for GFP-F Mode (continued) Parameter Definition12-21 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7.1 OC-3 Port Performance Monitoring Parameters Figure 12-8 Monitored Signal Types for the OC-3 Port Figure 12-9 shows where overhead bytes detected on the ASICs produce PM parameters for the OC-3 port. Figure 12-9 PM Parameter Read Points on the OC-3 Port Note For PM locations relating to protection switch counts, see the Telcordia GR-253-CORE document. The PM parameters for the OC-3 ports are listed in Table 12-11. The listed parameters are defined in Table 12-2 on page 12-4. ONS 15310 PTE OC-3 OC-N Fiber OC-3 Signal OC-3 Signal ONS 15310 OC-N OC-3 STS Path (STS XX-P) PMs Near and Far End Supported PTE 124444 ONS 15310 OC-3 Port Pointer Processors BTC ASIC Cross Connect OC-N CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PPJC-Pdet NPJC-Pdet PPJC-Pgen NPJC-Pgen PJC-DIFF-P PJCS-PDET-P PJCS-PGEN-P Path Level STS CV-P STS ES-P STS FC-P STS SES-P STS UAS-P STS CV-PFE STS ES-PFE STS FC-PFE STS SES-PFE STS UAS-PFE PMs read on BTC ASIC PMs read on PMC 12444512-22 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7.2 OC-12 Port Performance Monitoring Parameters Note For information about troubleshooting path protection switch counts, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. For information about creating circuits that perform a switch, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. 12.7.2 OC-12 Port Performance Monitoring Parameters Figure 12-10 shows the signal types that support near-end and far-end PM parameters. Figure 12-11 shows where overhead bytes detected on the ASICs produce PM parameters for the OC-12 ports. Figure 12-10 Monitored Signal Types for the OC-12 Ports Note PM parameters on the protect STS are not supported for BLSR. The XX in Figure 12-10 represents all PM parameters listed in Figure 12-11 with the given prefix and/or suffix. Table 12-11 OC-3 Port PM Parameters Section (NE) Line (NE) STS Path (NE)1 1. In CTC, the count fields for PPJC and NPJC PM parameters appear white and blank unless they are enabled on the Provisioning > Line tab. See the “12.3 Pointer Justification Count Performance Monitoring” section on page 12-3. Physical (NE) Line (FE) STS Path (FE)2 2. SONET path PM parameters do not count unless IPPM is enabled. For additional information see the “12.2 Intermediate-Path Performance Monitoring” section on page 12-3. CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PSC (1+1) PSD CV-P ES-P SES-P UAS-P FC-P PPJC-PDET-P NPJC-PDET-P PPJC-PGEN-P NPJC-PGEN-P PJCDIFF-P PJCS-PDET-P PJCS-PGEN-P OPT-HIGH OPT-LOW OPR-HIGH OPR-LOW LBC-HIGH LBC-LOW CV-LFE ES-LFE SES-LFE UAS-LFE FC-LFE CV-PFE ES-PFE SES-PFE UAS-PFE FC-PFE ONS 15310 PTE OC12 OC-N Fiber OC-12 Signal OC-12 Signal ONS 15310 OC-N OC12 STS Path (STS XX-P) PMs Near and Far End Supported PTE 12444312-23 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7.2 OC-12 Port Performance Monitoring Parameters Figure 12-11 PM Parameter Read Points on the OC-12 Ports Note For PM locations relating to protection switch counts, see the Telcordia GR-1230-CORE document. The PM parameters for the OC-12 ports are listed in Table 12-12. The listed parameters are defined in Table 12-2 on page 12-4. ONS 15310 OC-12 Port Pointer Processors BTC ASIC Cross Connect OC-N CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PPJC-Pdet NPJC-Pdet PPJC-Pgen NPJC-Pgen Path Level STS CV-P STS ES-P STS FC-P STS SES-P STS UAS-P PPJC-PDET NPJC-PDET PPJC-PGEN NPJC-PGEN PJC-DIFF-P PJCS-PDET-P PJCS-PGEN-P PMs read on BTC ASIC PMs read on PMC 124446 Table 12-12 OC12 Port PM Parameters Section (NE) Line (NE) STS Path (NE)1 2 1. SONET path PM parameters do not count unless IPPM is enabled. For additional information, see the “12.2 Intermediate-Path Performance Monitoring” section on page 12-3. 2. In CTC, the count fields for PPJC and NPJC PM parameters appear white and blank unless they are enabled on the Provisioning > Line tab. See the “12.3 Pointer Justification Count Performance Monitoring” section on page 12-3. Physical (NE) Line (FE) CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PSC (1+1, 2F BLSR) PSD (2F BLSR) CV-P ES-P SES-P UAS-P FC-P PPJC-PDET-P NPJC-PDET-P PPJC-PGEN-P NPJC-PGEN-P PJCDIFF-P PJCS-PDET-P PJCS-PGEN-P OPT-HIGH OPT-LOW OPR-HIGH OPR-LOW LBC-HIGH LBC-LOW CV-LFE ES-LFE SES-LFE UAS-LFE FC-LFE12-24 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7.3 OC-48 Port Performance Monitoring Parameters for ONS 15310-MA Note For information about troubleshooting path protection switch counts, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. For information about creating circuits that perform a switch, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. 12.7.3 OC-48 Port Performance Monitoring Parameters for ONS15310-MA Figure 12-12 shows the signal types that support near-end and far-end PM parameters. Figure 12-13 shows where overhead bytes detected on the ASICs produce PM parameters for the OC-48 ports. Figure 12-12 Monitored Signal Types for the OC-48 Ports Note PM parameters on the protect STS are not supported for BLSR. The XX in Figure 12-12 represents all PM parameters listed in Figure 12-13 with the given prefix and/or suffix. PTE ONS 15310-MA OC-48 OC-N Fiber OC-48 Signal OC-48 Signal ONS 15310-MA OC-N OC-48 STS Path (STS XX-P) and VT Path PMs Near and Far End Supported PTE 15157912-25 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7.3 OC-48 Port Performance Monitoring Parameters for ONS 15310-MA Figure 12-13 PM Parameter Read Points on the OC-48 Ports Note For PM locations relating to protection switch counts, see the Telcordia GR-1230-CORE document. The PM parameters for the OC-48 ports are listed in Table 12-13. The listed parameters are defined in Table 12-2 on page 12-4. ONS 15310-MA OC-48 Port Pointer Processors BTC ASIC Cross Connect OC-N CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PPJC-Pdet NPJC-Pdet PPJC-Pgen NPJC-Pgen Path Level STS CV-P STS ES-P STS FC-P STS SES-P STS UAS-P PPJC-PDET NPJC-PDET PPJC-PGEN NPJC-PGEN PJC-DIFF-P PJCS-PDET-P PJCS-PGEN-P PMs read on BTC ASIC PMs read on PMC 151580 Table 12-13 OC48 Port PM Parameters Section (NE) Line (NE) STS Path (NE)1 2 1. SONET path PM parameters do not count unless IPPM is enabled. For additional information, see the “12.2 Intermediate-Path Performance Monitoring” section on page 12-3. 2. In CTC, the count fields for PPJC and NPJC PM parameters appear white and blank unless they are enabled on the Provisioning > Line tab. See the “12.3 Pointer Justification Count Performance Monitoring” section on page 12-3. Physical (NE) Line (FE) CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PSC (1+1, 2F BLSR) PSD (2F BLSR) CV-P ES-P SES-P UAS-P FC-P PPJC-PDET-P NPJC-PDET-P PPJC-PGEN-P NPJC-PGEN-P PJCDIFF-P PJCS-PDET-P PJCS-PGEN-P OPT-HIGH OPT-LOW OPR-HIGH OPR-LOW LBC-HIGH LBC-LOW CV-LFE ES-LFE SES-LFE UAS-LFE FC-LFE12-26 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 12 Performance Monitoring 12.7.3 OC-48 Port Performance Monitoring Parameters for ONS 15310-MA Note For information about troubleshooting path protection switch counts, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide. For information about creating circuits that perform a switch, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.CHAPTER 13-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 13 SNMP This chapter explains Simple Network Management Protocol (SNMP) as implemented by the Cisco ONS 15310-CL and ONS 15310-MA. For SNMP set up information, refer to the Cisco ONS 15310-CL and ONS 15310-MA Procedure Guide. Chapter topics include: • 13.1 SNMP Overview, page 13-1 • 13.2 SNMP Basic Components, page 13-2 • 13.3 SNMP Proxy Support Over Firewalls, page 13-3 • 13.4 SNMP Version Support, page 13-4 • 13.5 SNMP Management Information Bases, page 13-4 • 13.6 SNMP Traps, page 13-6 • 13.7 SNMP Community Names, page 13-8 • 13.8 SNMP Remote Network Monitoring, page 13-8 • 13.9 CE-100T-8 and ML-100T-8 RMON MIBs, page 13-9 13.1 SNMP Overview SNMP is an application-layer communication protocol that allows network devices to exchange management information. SNMP enables network administrators to manage network performance, find and solve network problems, and plan network growth. Up to 10 SNMP trap destinations and five concurrent Cisco Transport Controller (CTC) user sessions are allowed per node. The ONS 15310-CL and ONS 15310-MA use SNMP to provide asynchronous event notification to a network management system (NMS). ONS SNMP implementation uses standard Internet Engineering Task Force (IETF) management information bases (MIBs) to convey node-level inventory, fault, and performance management information for generic read-only management of DS-1, DS-3, SONET, and Ethernet technologies. SNMP allows limited management of the ONS 15310-CL and ONS 15310-MA by a generic SNMP manager—for example, HP OpenView Network Node Manager (NNM) or Open Systems Interconnection (OSI) NetExpert. The ONS 15310-CL and ONS 15310-MA support SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c). Both versions share many features, but SNMPv2c includes additional protocol operations. This chapter describes both versions and explains how to configure SNMP on the ONS 15310-CL and ONS 15310-MA.13-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.2 SNMP Basic Components Note It is recommended that the SNMP Manager timeout value be set to 60 seconds. Under certain conditions, if this value is lower than the recommended time, the TCC card can reset. However, the response time depends on various parameters such as object being queried, complexity, and number of hops in the node, etc. Note The CERENT-MSDWDM-MIB.mib and CERENT-FC-MIB.mib in the CiscoV2 directory support 64-bit performance monitoring counters. However, the SNMPv1 MIB in the CiscoV1 directory does not contain 64-bit performance monitoring counters, but supports the lower and higher word values of the corresponding 64-bit counter. The other MIB files in the CiscoV1 and CiscoV2 directories are identical in content and differ only in format. Figure 13-1 illustrates a basic network managed by SNMP. Figure 13-1 Basic Network Managed by SNMP 13.2 SNMP Basic Components An SNMP-managed network consists of three primary components: managed devices, agents, and management systems. A managed device is a network node that contains an SNMP agent and resides on an SNMP-managed network. Managed devices collect and store management information and use SNMP to make this information available to management systems that use SNMP. Managed devices include routers, access servers, switches, bridges, hubs, computer hosts, and network elements such as the ONS 15310-CL or ONS 15310-MA. An agent is a software module that resides in a managed device. An agent has local knowledge of management information and translates that information into a form compatible with SNMP. The SNMP agent gathers data from the MIB, which is the repository for device parameter and network data. The agent can also send traps, which are notifications of certain events (such as changes), to the manager. Figure 13-2 illustrates these SNMP operations. 5258213-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.3 SNMP Proxy Support Over Firewalls Figure 13-2 SNMP Agent Gathering Data from a MIB and Sending Traps to the Manager A management system such as HP OpenView executes applications that monitor and control managed devices. Management systems provide the bulk of the processing and memory resources required for network management. One or more management systems must exist on any managed network. Figure 13-3 illustrates the relationship between the three key SNMP components. Figure 13-3 Example of the Primary SNMP Components 13.3 SNMP Proxy Support Over Firewalls Firewalls, often used for isolating security risks inside networks or from outside, have traditionally prevented SNMP and other NMS monitoring and control applications from accessing NEs beyond a firewall. An application-level proxy is available at each firewall to transport SNMP protocol data units (PDU) between the NMS and NEs. This proxy, integrated into the firewall NE SNMP agent, exchanges requests and responses between the NMS and NEs and forwards NE autonomous messages to the NMS. The get, get-next, get-bulk Network device get-response, traps 32632 SNMP Manager NMS MIB SNMP Agent Management Entity Agent Management Database Agent NMS Management Database Managed Devices Agent Management Database 3393013-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.4 SNMP Version Support usefulness of the proxy feature is that network operations centers (NOCs) can fetch performance monitoring data such as remote monitoring (RMON) statistics across the entire network with little provisioning at the NOC and no additional provisioning at the NEs. The firewall proxy interoperates with common NMS such as HP-OpenView. It is intended to be used with many NEs through a single NE gateway in a gateway network element (GNE)-end network element (ENE) topology. Up to 64 SNMP requests (such as get, getnext, or getbulk) are supported at any time behind single or multiple firewalls. For security reasons, the SNMP proxy feature must be turned on at all receiving and transmitting NEs to be enabled. For instructions to do this, refer to the Cisco ONS 15310-CL and ONS 15310-MA Procedure Guide. The feature does not interoperate with earlier ONS 15310-CL releases. 13.4 SNMP Version Support The ONS 15310-CL and ONS 15310-MA support SNMP v1 and SNMPv2c traps and get requests. The SNMP MIBs in the ONS 15310-CL define alarms, traps, and status. Through SNMP, NMS applications can query a management agent using a supported MIB. The functional entities include Ethernet switches and SONET multiplexers. Refer to the Cisco ONS 15310-CL and ONS 15310-MA Procedure Guide for procedures to set up or change SNMP settings. 13.5 SNMP Management Information Bases A MIB is a hierarchically organized collection of information. It consists of managed objects and is identified by object identifiers. Network-management protocols, such as SNMP, are able to access to MIBs. The ONS 15310-CL SNMP agent communicates with an SNMP management application using SNMP messages. Table 13-1 describes these messages. A managed object (sometimes called a MIB object) is one of many specific characteristics of a managed device. Managed objects consist of one or more object instances (variables). Table 13-2 lists the IETF standard MIBs implemented in the ONS 15310-CL or ONS 15310-MA SNMP agent. Table 13-1 SNMP Message Types Operation Description get-request Retrieves a value from a specific variable. get-next-request Retrieves the value following the named variable; this operation is often used to retrieve variables from within a table. With this operation, an SNMP manager does not need to know the exact variable name. The SNMP manager searches sequentially to find the needed variable from within the MIB. get-response Replies to a get-request, get-next-request, get-bulk-request, or set-request sent by an NMS. get-bulk-request Fills the get-response with up to the max-repetition number of get-next interactions, similar to a get-next-request. set-request Provides remote network monitoring (RMON) MIB. trap Indicates that an event has occurred. An unsolicited message is sent by an SNMP agent to an SNMP manager.13-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.5 SNMP Management Information Bases The ONS 15310-CL and ONS 15310-MA MIBs in Table 13-3 are included on the software CD that ships with the ONS 15310-CL and ONS 15310-MA. Compile these MIBs in the order listed in Table 13-2 and then Table 13-3. If you do not follow the order, one or more MIB files might not compile. Table 13-2 IETF Standard MIBs Implemented in the ONS 15454, ONS 15327, ONS 15310-CL and ONS 15310-MA SNMP Agent RFC1 Number 1. RFC = Request for Comment Module Name Title/Comments — IANAifType-MIB.mib Internet Assigned Numbers Authority (IANA) ifType 1213 1907 RFC1213-MIB-rfc1213.mib, SNMPV2-MIB-rfc1907.mib Management Information Base for Network Management of TCP/IP-based internets:MIB-II Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) 1253 RFC1253-MIB-rfc1253.mib OSPF Version 2 Management Information Base 1493 BRIDGE-MIB-rfc1493.mib Definitions of Managed Objects for Bridges (This defines MIB objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments.) 2819 RMON-MIB-rfc2819.mib Remote Network Monitoring Management Information Base 2737 ENTITY-MIB-rfc2737.mib Entity MIB (Version 2) 2233 IF-MIB-rfc2233.mib Interfaces Group MIB using SMIv2 2358 EtherLike-MIB-rfc2358.mib Definitions of Managed Objects for the Ethernet-like Interface Types 2493 PerfHist-TC-MIB-rfc2493.mib Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals 2495 DS1-MIB-rfc2495.mib Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types 2496 DS3-MIB-rfc2496.mib Definitions of Managed Object for the DS3/E3 Interface Type 2558 SONET-MIB-rfc2558.mib Definitions of Managed Objects for the SONET/SDH Interface Type 2674 P-BRIDGE-MIB-rfc2674.mib Q-BRIDGE-MIB-rfc2674.mib Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions Table 13-3 ONS Proprietary MIBs MIB Number Module Name 1 CERENT-GLOBAL-REGISTRY.mib 2 CERENT-TC.mib 3 CERENT-454.mib (for ONS 15454 only)13-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.6 SNMP Traps If you cannot compile the ONS 15310-CL or ONS 15310-MA MIBs, call the Cisco Technical Assistance Center (Cisco TAC). Contact information for Cisco TAC is listed in the “Obtaining Documentation and Submitting a Service Request” section on page xxxi. 13.6 SNMP Traps The ONS 15310-CL or ONS 15310-MA can receive SNMP requests from a number of SNMP managers and send traps to 10 trap receivers. The ONS 15310-CL generates all alarms and events as SNMP traps. Both the ONS 15310-CL and ONS 15310-MA generate traps containing an object ID that uniquely identifies the alarm. An entity identifier uniquely identifies the entity that generated the alarm (slot, port, synchronous transport signal [STS], Virtual Tributary [VT], Spanning Tree Protocol [STP], and so on). The traps give the severity of the alarm (Critical, Major, Minor, event, and so on) and indicate whether the alarm is service affecting or non-service affecting. The traps also contain a date/time stamp that shows the date and time the alarm occurred. The ONS 15310-CL and ONS 15310-MA also generate a trap for each alarm when the alarm condition clears. Each SNMP trap contains ten variable bindings, listed in Table 13-4. 4 CERENT-GENERIC.mib (for ONS 15327 only) 5 CISCO-SMI.mib Table 13-3 ONS Proprietary MIBs (continued) MIB Number Module Name Table 13-4 SNMPv2 Trap Variable Bindings Number ONS 15454 Name ONS 15310-CL Name Description 1 sysUpTime sysUpTime The first variable binding in the variable binding list of an SNMPv2-Trap-PDU. 2 snmpTrapOID snmpTrapOID The second variable binding in the variable binding list of an SNMPv2-Trap-PDU. 3 cerent454NodeTime cerentGenericNodeTime The time that an event occurred 4 cerent454AlarmState cerentGenericAlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service- affecting statuses are service-affecting and non-service affecting. 5 cerent454AlarmObjectType cerentGenericAlarmObjectType The entity type that raised the alarm. The NMS should use this value to decide which table to poll for further information about the alarm. 6 cerent454AlarmObjectIndex cerentGenericAlarmObjectIndex Every alarm is raised by an object entry in a specific table. This variable is the index of the objects in each table; if the alarm is interface-related, this is the index of the interfaces in the interface table. 7 cerent454AlarmSlotNumber cerentGenericAlarmSlotNumber The slot of the object that raised the alarm. If a slot is not relevant to the alarm, the slot number is zero.13-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.6 SNMP Traps The ONS 15310-CL and ONS 15310-MA support the generic and IETF traps listed in Table 13-5. 8 cerent454AlarmPortNumber cerentGenericAlarmPortNumber The port of the object that raised the alarm. If a port is not relevant to the alarm, the port number is zero. 9 cerent454AlarmLineNumber cerentGenericAlarmLineNumber The object line that raised the alarm. If a line is not relevant to the alarm, the line number is zero. 10 cerent454AlarmObjectName cerentGenericAlarmObjectName The TL1-style user-visible name that uniquely identifies an object in the system. Table 13-4 SNMPv2 Trap Variable Bindings (continued) Number ONS 15454 Name ONS 15310-CL Name Description Table 13-5 Traps Supported in the ONS 15310-CL and ONS 15310-MA Trap From RFC No. MIB Description coldStart RFC1907-MIB Agent up, cold start. warmStart RFC1907-MIB Agent up, warm start. authenticationFailure RFC1907-MIB Community string does not match. newRoot RFC1493/ BRIDGE-MIB Sending agent is the new root of the spanning tree. topologyChange RFC1493/ BRIDGE-MIB A port in a bridge has changed from Learning to Forwarding or Forwarding to Blocking. entConfigChange RFC2737/ ENTITY-MIB The entLastChangeTime value has changed. dsx1LineStatusChange RFC2495/ DS1-MIB A dsx1LineStatusChange trap is sent when the value of an instance of dsx1LineStatus changes. The trap can be used by an NMS to trigger polls. When the line status change results from a higher-level line status change (for example, a DS-3), no traps for the DS-1 are sent. dsx3LineStatusChange RFC2496/ DS3-MIB A dsx3LineStatusLastChange trap is sent when the value of an instance of dsx3LineStatus changes. This trap can be used by an NMS to trigger polls. When the line status change results in a lower-level line status change (for example, a DS-1), no traps for the lower-level are sent. risingAlarm RFC2819/ RMON-MIB The SNMP trap that is generated when an alarm entry crosses the rising threshold and the entry generates an event that is configured for sending SNMP traps. fallingAlarm RFC2819/ RMON-MIB The SNMP trap that is generated when an alarm entry crosses the falling threshold and the entry generates an event that is configured for sending SNMP traps.13-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.7 SNMP Community Names 13.7 SNMP Community Names You can provision community names for all SNMP requests from the SNMP Trap Destination dialog box in CTC. In effect, SNMP considers any request valid that uses a community name matching a community name on the list of provisioned SNMP trap destinations. Otherwise, SNMP considers the request invalid and drops it. If an SNMP request contains an invalid community name, the request silently drops and the MIB variable (snmpInBadCommunityNames) increments. All MIB variables managed by the agent grant access to all SNMP requests containing a validated community name. 13.8 SNMP Remote Network Monitoring The ONS 15310-CL and ONS 15310-MA incorporate RMON to allow network operators to monitor the ONS 15310-CL Ethernet cards. This feature is not apparent to the typical CTC user, because RMON interoperates with an NMS. However, with CTC you can provision the RMON alarm thresholds. For the procedure, refer to the Cisco ONS 15310-CL and ONS 15310-MA Procedure Guide. CTC also monitors the five RMON groups implemented by the ONS 15310-CL. ONS 15310-CL and ONS 15310-MA RMON implementation is based on the IETF-standard MIB RFC2819. The ONS 15310-CL and ONS 15310-MA implement 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. Hence when these statistics are obtained via get-reques/get-next-request/SNMP Trap they don’t match the name used on the card or as seen by CTC/TL1. • For ex: STATS_MediaIndStatsRxFramesTooLong stats is mapped to cMediaIndependentInFramesTooLong variable in CERENT MIB. STATS_RxTotalPkts is mapped to mediaIndependentInPkts in HC-RMON-rfc3273.mib 13.8.1 Ethernet Statistics Group The Ethernet Statistics group contains the basic statistics for each monitored subnetwork in a single table named etherstats. The group also contains 64-bit statistics in the etherStatsHighCapacityTable. 13.8.2 History Control Group The History Control group defines sampling functions for one or more monitor interfaces. RFC 2819 defines the historyControlTable. 13.8.3 Ethernet History Group The ONS 15310-CL and ONS 15310-MA implement the etherHistoryTable as defined in RFC 2819, within the bounds of the historyControlTable. It also implements 64-bit Ethernet history in the etherHistoryHighCapacityTable.13-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.8.4 Alarm Group 13.8.4 Alarm Group The Alarm group consists of a single alarm table. This table provides the network performance alarm thresholds for the network management application. With CTC, you can provision the thresholds in the table. 13.8.5 Event Group The Event group consists of two tables, eventTable and logTable. The eventTable is read-only. The ONS 15310-CL and ONS 15310-MA implement the logTable as specified in RFC 2819. 13.9 CE-100T-8 and ML-100T-8 RMON MIBs The CE-100T-8 and CTX2500 use the ONG RMON. The ONG RMON contains the statistics, history, alarms, and events MIB groups from the standard RMON MIB. The ONG RMON is recommended for the ML-100T-8 and contains the statistics, history, alarms, and events MIB groups from the standard RMON MIB. The standard Cisco IOS RMON is also available for the ML-100T-8. 13-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual, R7.0 Chapter 13 SNMP 13.9 CE-100T-8 and ML-100T-8 RMON MIBsA-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 APPENDIX A 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This appendix contains shelf, card, and Small Form-factor Pluggable (SFP) specifications for the Cisco ONS 15310-CL and Cisco ONS 15310-MA. A.1 Cisco ONS 15310-CL Shelf Specifications This section includes hardware and software specifications. A.1.1 Bandwidth The following bandwidth specifications apply to the ONS 15310-CL: • Total bandwidth: 2.054 Gbps • Optical: 1.24 Gbps (2 x OC-12) • Electrical: 188 Mbps • Expansion: 622 Mbps (OC-12) A.1.2 Expansion Slot Total card slots: 1 expansion slot for CE-100T-8 and ML-100T-8 cards. A blank card (15310-EXP-FILLER) can also be plugged into the expansion slot. A.1.3 Internal Cards The following internal cards are available in the ONS 15310-CL: • 15310-CL-CTX cardA-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.1.4 15310-CL-CTX • Interconnect card • Connector expansion card A.1.4 15310-CL-CTX The 15310-CL-CTX card has the following specifications: • Optical ports – Two user upgradeable and hot swappable SFPs with SONET interface support – Support for multirate SFPs (155.520 Mbps and 622.080 Mbps) – Support for operating the two optical facilities at different line rates in unprotected facility mode (non 1+1 Automatic Protection Switching [APS] operation) • DS-1 ports – Supports Telcordia GR-499-compliant 1.544 Mbps (DS-1) interface – Performance monitoring (PM) is provided through the interface to allow validation of signal quality. – Any outgoing DS-1 signal can be retimed to eliminate accumulated jitter and wander at the point of egress from a synchronous network. – Any incoming T1 signal from the transport element can also be used as a timing source. • DS-3/EC1 ports – Supports Telcordia GR-499-compliant 44.736 Mbps (DS3) interfaces or EC1. – PM is provided through the interface to allow validation of signal quality. Each port can be provisioned in any combination of DS-3 or EC1. • Building integrated timing supply (BITS) – Supports one BITS input and one BITS output – The BITS I/O ports support a 100-ohm termination for external 1.544 Mbps DS1 timing signals. • Alarm – The alarm system provides three alarm inputs and two contacts for alarm outputs. • LAN – Supports a 10/100-Mbps Ethernet interface for Cisco Transport Controller/Transaction Language One (CTC/TL1) provisioning. – For node access in secure mode, SSL (for TL1) and HTTPS (for CTC) security protocols are supported. • Craft interface – An EIA/TIA-232 craft interface is provided and is used for TL1 provisioning. – The craft interface is set to 9600 baud, no parity, and 1 stop bit by default. • 64-kbps user data channel (UDC) digital interface – The 6- kbps digital interface provides a digital input and output. – Any F1 byte that is accessible on the system is interfaced at the UDC connector. – The UDC provides a simplex interface. Protection for UDC overhead channel(s) follows interface line protection for traffic.A-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.1.5 Configurations – The UDC can be enabled or disabled through the management interfaces. The default state is disabled. – The UDC supports a 64-kbps serial interface adaptation function to overhead byte F1. – The physical interface is defined in ITU-T G.703 as a 120-ohm, twisted pair connection. The jitter specification is defined in ITU-T G.823. – The physical interface is defined in ITU-T G.703 as a 120-ohm, twisted pair connection. The jitter specification is defined in ITU-T G.823. – The UDC supports a serial port interface adaptation function to overhead bytes F1. This is an EIA/TIA-232 interface capable of 9.6-, 19.2-, 38.4-, and 56-kbps operation. The rate is selectable through the management interface. The default is 56 kbps with no parity and 1 stop bit. A.1.5 Configurations The ONS 15310-CL supports the following configurations: • Two-fiber path protection • 1+1 protection • Path protected mesh network (PPMN) • Add/drop multiplexer (ADM) • Point-to-point (PPP) terminal mode A.1.6 Cisco Transport Controller CTC, the ONS 15310-CL graphical user interface (GUI), has the following specifications: • 10/100BaseT • 15310-CL-CTX access: RJ-45 connector A.1.7 TL1 Craft Interface TL1, the ONS 15310-CL craft interface, has the following specifications: • Speed: 9600 baud, no parity, 1 stop bit • 15310-CL-CTX: EIA/TIA-232 with RJ-45 type connector A.1.8 LEDs Table A-1 describes the possible LED colors and their significance.A-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.1.9 Alarm Interface A.1.9 Alarm Interface The ONS 15310-CL alarm interface has the following specifications: • Visual: Critical (red LED), Major (red LED), Minor (amber LED) • Three alarm inputs and two alarm contacts, all on the same RJ-45 connector (ALARM port) A.1.10 DS1 Interface The ONS 15310-CL DS-1 interface has the following specifications: • 21 DS-1 (1.544 Mbps) ports • Connector: LFH96 (100-ohm balanced) • Any two ports can be used as primary and secondary timing sources • A DS01 output can be retimed to system clock on a per-port basis A.1.11 DS3/EC1 Interface The ONS 15310-CL DS3/EC1 interface has the following specifications: • Three DS3 (44.736 Mbps)/EC1 (51.84 Mbps) ports • Connector: 75-ohm mini-BNC connector • Ports can be any combination of DS-3 and EC-1 A.1.12 Nonvolatile Memory The ONS 15310-CL nonvolatile memory has the following specifications: • 128 MB, Compact Flash card Table A-1 LED Description LED Color FAIL Red for system failure or during initialization ALARM Red (Major and Critical) Amber (Minor) PWR Green (AC source present or both DC sources present) Amber (one DC source present) SYNC Green (primary and secondary reference synchronization) Amber (only one reference) Red (loss of both references)A-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.1.13 BITS Interface A.1.13 BITS Interface The ONS 15310-CL BITS interface has the following specifications: • One DS-1 BITS input • One derived DS-1 output A.1.14 Push Buttons The ONS 15310-CL has the following push buttons: • Lamp test: When momentarily pushed, lights all LEDs on the ONS 15310-CL front panel. If an LED has more than one color, all the colors will be cycled when the lamp test button is pushed. Note Another use for the lamp test button is to reset the CTC password to its default value (otbu+1). To reset the password, press the lamp test button for at least five seconds, release it for a maximum of five seconds, then press it again for at least five seconds. After the button is released, the default password is set. • System reset: When pressed, performs a soft reset (does not impact traffic). A.1.15 System Timing The ONS 15310-CL has the following timing specifications: • +/– 20 ppm SONET Minimum Clock (SMC) free-running internal clock • Maintains SMC holdover (+/– 4.6 ppm for first 24 hours) in the event of reference frequency loss • Timing reference: External BITS, line optical port, any DS-1 clock, and internal clock A.1.16 Power Specifications The ONS 15310-CL has the following power specifications: • Input power: –48 VDC (dual DC power supply model) or 100/240 VAC (AC power model) • Maximum power consumption – DC chassis with no expansion board: 60 W – DC chassis with expansion board: 115 W – AC chassis with no expansion board: 70 W – AC chassis with expansion board: 140 W • Power requirements: –42 to –56 VDC or 100/240 VAC (+/– 10 percent) • Power terminals: Three-prong male locking connector for DC power supply model or three-prong male AC connector for AC power model Note An ONS 15310-CL that uses DC power is classified as DC-I (DC Isolated). This means that the DC return (RET) conductor at the DC power input connector is not bonded to the chassis frame ground.A-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.1.17 Environmental Specifications A.1.17 Environmental Specifications The ONS 15310-CL has the following environmental specifications: • Operating temperature: 0 to +55 degrees Celsius (32 to +131 degrees Fahrenheit) for AC chassis; –40 to +65 degrees Celsius (–40 to +149 degrees Fahrenheit) for dual-DC chassis • Operating humidity: 5 to 95 percent, noncondensing A.1.18 Shelf Dimensions The ONS 15310-CL has the following shelf dimensions: • Height: 1 Rack Unit (RU), 1.75 inches (4.45 cm) • Width: – 19.0 inches (48.3 cm) – 23.0 inches (58.4 cm) including rackmount brackets • Depth: – 15.0 inches (38.1 cm) sheet metal only – 15.8 inches (40.2) including mini-BNC and DC inlet connectors • Weight: – 11.5 lb. empty – 12.5 lb. maximum (line card installed) A.2 Cisco ONS 15310-MA Shelf Specifications This section provides ONS 15310-MA topologies; Cisco Transport Controller (CTC) specifications; LAN, TL1, modem, alarm, and electrical interface assembly (EIA) interface specifications; timing, power, and environmental specifications; and shelf dimensions. A.2.1 Alarm Interface The ONS 15310-MA alarm interface has the following specifications: • The alarm interface provides 32 alarm inputs and 8 contacts for alarm outputs. • Connector J6: Alarm inputs • Connector J7: Alarm outputs A.2.2 UDC Interface The ONS 15310-MA 64-kbps user data channel (UDC) digital interface has the following specifications: • The 64- kbps digital interface provides a digital input and output. • Any F1 byte that is accessible on the system is interfaced at the UDC connector.A-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.2.3 Cisco Transport Controller LAN Interface • The UDC provides a simplex interface. Protection for UDC overhead channel(s) follows interface line protection for traffic. • The UDC can be enabled or disabled through the management interfaces. The default state is disabled. • The physical interface is defined in ITU-T G.703 as a 120-ohm, twisted pair connection. The jitter specification is defined in ITU-T G.823. • The UDC supports a serial port interface adaptation function to overhead bytes F1. This is an EIA/TIA-232 interface capable of 9.6-, 19.2-, 38.4-, and 56-kbps operation. The rate is selectable through the management interface. The default is 56 kbps with no parity and 1 stop bit. • Connector J3: UDC A.2.3 Cisco Transport Controller LAN Interface The ONS 15310-MA CTC LAN interface has the following specifications: • 10/100BaseT • CTX2500 access: RJ-45 connector • Connector J3: LAN port A.2.4 TL1 Craft Interface The ONS 15310-MA TL1 craft interface has the following specifications: • Speed: 9600 baud, no parity, 1 stop bit • CTX2500: EIA/TIA-232 with RJ-45 type connector • Connector J2: Craft port A.2.5 Configurations The ONS 15310-MA supports the following configurations: • Two-fiber path protection • 1+1 protection • Path protected mesh network (PPMN) • Add/drop multiplexer (ADM) • Point-to-point (PPP) terminal mode A.2.6 LEDs Table A-1 describes the system-level LEDs, located on the on the ONS 15310-MA fan tray, and the possible LED colors and their significance.A-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.2.7 Push Buttons A.2.7 Push Buttons The ONS 15310-MA has the following push buttons: • Lamp test: When momentarily pushed, lights all LEDs on the ONS 15310-MA front panel. If an LED has more than one color, all the colors will be cycled when the lamp test button is pushed. Note Another use for the lamp test button is to reset the CTC password to its default value (otbu+1). To reset the password, press the lamp test button for at least five seconds, release it for a maximum of five seconds, then press it again for at least five seconds. After the button is released, the default password is set. A.2.8 BITS Interface The ONS 15310-MA has the following building integrated timing supply (BITS) specifications: – Supports two BITS inputs and two BITS outputs – The BITS I/O ports support a 100-ohm termination for external 1.544 Mbps DS1 timing signals. – Connector J4: BITS1; Connector J5: BITS2 A.2.9 System Timing The ONS 15310-MA has the following timing specifications: • +/– 20 ppm SONET Minimum Clock (ST3) free-running internal clock • Maintains SMC holdover (+/– 4.6 ppm for first 24 hours) in the event of reference frequency loss • Timing reference: External BITS, line optical port, any DS-1 clock, and internal clock A.2.10 Power Specifications The ONS 15310-MA has the following power specifications: Table A-2 LED Description LED Color and Meaning FAIL Red indicates system failure or during initialization CR Red indicates a critical alarm is present on the shelf assembly. MJ Red indicates a major alarm is present on the shelf assembly. MN Amber indicates a minor alarm is present on the shelf assembly. REM Red indicates a remote alarm is present on the shelf assembly. PWR A PWR B Green indicates that a DC power source present and within normal operating range. Red indicates that DC power source is not present, or is present and not within normal operating range.A-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.2.11 Environmental Specifications • Input power: –48 VDC • Maximum power consumption – Chassis with no cards installed (fan tray only): 55 W – Chassis with cards installed: 347 W • Power requirements: –44 to –54 VDC • Power terminals: Three-prong male locking connector Note An ONS 15310-MA that uses DC power is classified as DC-I (DC Isolated). This means that the DC return (RET) conductor at the DC power input connector is not bonded to the chassis frame ground. A.2.11 Environmental Specifications The ONS 15310-MA has the following environmental specifications: • Operating temperature: –40 to +65 degrees Celsius (–40 to +149 degrees Fahrenheit) • Operating humidity: 5 to 95 percent, noncondensing A.2.12 Fan-Tray Assembly Specifications • Environmental – Operating temperature: -40 to +65 degrees Celsius (-40 to 149 degrees Fahrenheit) – Operating humidity: 5 to 90%, noncondensing • Power – 50 W, 4.2 Amps (at 12 V), 170 BTU/hr • Shelf Acoustics (NEBS acoustic noise compliant) – Normal fan speed: 58 dBA – High fan speed: 64 dBA A.2.13 Shelf Dimensions The ONS 15310-MA has the following shelf dimensions: • Height: 6 Rack Units (RUs), 10.44 inches (26.51 cm) • Width: – 10.67 inches (27.10 cm) • Depth: – 12 inches (20.5 cm) without cables installed – 13.7 inches (34.8 cm) with cables installed • Weight: – 25 lbs. (11.3 kg) maximum (line cards, fan-tray assembly, and two electrical interface assemblies (EIAs) installed)A-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.3 Card Specifications A.3 Card Specifications This section provides specifications for the cards that can be installed in the 15310-CL expansion slot, including the CE-100T-8, ML-100T-8, and Filler cards. It also includes the 15310-MA electrical and CTX2500 cards. For compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. A.3.1 CTX2500 Card The CTX2500 card is installed in Slots 3 and 4 of the ONS 15310-MA only. The CTX2500 has the following specifications. • LAN Port – Supports a 10/100-Mbps Ethernet interface for Cisco Transport Controller/Transaction Language One (CTC/TL1) provisioning. – For node access in secure mode, SSL (for TL1) and HTTPS (for CTC) security protocols are supported. • CRAFT Port – An EIA/TIA-232 craft interface is provided and is used for TL1 provisioning. – The craft interface is set to 9600 baud, no parity, and 1 stop bit by default. • Nonvolatile memory – 128 MB, Compact Flash card • Optical ports: Line – Bit rate: OC-3 (155.520 Mbps), OC-12, (622.080 Mbps), and OC-48 (2488.320 Mbps), depending on the SFP installed Note Both optical interfaces on the card can be configured as OC-3, OC-12, or OC-48. – Code: Scrambled NRZ – Fiber: depends on the SFP used (see the “A.4 SFP Specifications” section on page A-15) – Loopback modes: Terminal and facility – Connectors: LC duplex connector for each SFP – Compliance: Telcordia SONET, Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.957 • Optical ports: Transmitter – Maximum transmitter output power: Depends on the SFP used (see the “A.4 SFP Specifications” section on page A-15) – Minimum transmitter output power: Depends on the SFP used (see the “A.4 SFP Specifications” section on page A-15) – Center wavelength: See wavelength plan – Center wavelength accuracy: 1 nm to 4 nm, depending on the SFP used – Transmitter: DFB laserA-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.3.2 Nonvolatile Memory • Optical ports: Receiver – Maximum receiver level: Depends on the SFP used (see the “A.4 SFP Specifications” section on page A-15) – Minimum receiver level: Depends on the SFP used (see the “A.4 SFP Specifications” section on page A-15) – Receiver: PIN PD – Receiver input wavelength range: Depends on the SFP used • Environmental – Operating temperature: C-Temp: +23 to +131 degrees Fahrenheit (–5 to +55 degrees Celsius) I-Temp: –40 to +149 degrees Fahrenheit (–40 to +65 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing – Power consumption: 9.28 W, 0.19 A, 31.68 BTU/hr • Dimensions – Height: 6.94 in. (167.28 mm) – Width: 1.45 in. (36.83 mm) – Depth: 8.35 in. (212.09 mm) – Weight not including clam shell: 1.6 lb (0.73 kg) LAN Port • Supports a 10/100-Mbps Ethernet interface for Cisco Transport Controller/Transaction Language One (CTC/TL1) provisioning. CRAFT Port • An EIA/TIA-232 craft interface is provided and is used for TL1 provisioning. • The craft interface is set to 9600 baud, no parity, and 1 stop bit by default. A.3.2 Nonvolatile Memory The ONS 15310-MA nonvolatile memory has a 128 MB Compact Flash card A.3.3 CE-100T-8 and ML-100T-8 Cards The CE-100T-8 and ML-100T-8 cards have the following specifications: • Environmental – Operating temperature C-Temp: 0 to +55 degrees Celsius (32 to 131 degrees Fahrenheit) – Operating humidity: 5 to 95%, noncondensing – Power consumption: 1.10A, 53 W • Dimensions – Height: 176 mm (6.93 in.)A-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.3.4 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards – Width: 34.29 mm (1.35 in.) – Depth: 238.25 mm (9.38 in.) – Weight (not including clam shell): 0.499 kg (1.1 lb) A.3.4 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards The ONS 15310-MA DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards have the following specifications: For DS1: For DS1: • Input – Bit rate: 1.544 Mbps +/- 32 ppm – Frame format: Unframed, SF (D4), ESF – Line code: AMI, B8ZS – Termination: AMP Champ – Input impedance: 100 ohms – Cable loss: Max 655 feet ABAM #22 or #24 AWG – AIS: TR-TSY-000191 compliant • Output – Bit rate: 1.544 Mbps +/- 32 ppm – Frame format: Unframed, SF (D4), ESF – Line code: AMI, B8ZS – Termination: AMP Champ – Input impedance: 100 ohms – Cable loss: Max 655 feet ABAM #22 or #24 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.6 V peak-to-peak – Loopback modes: Terminal and facility – Line build out: 0 - 131 ft., 132 - 262 ft., 263 - 393 ft., 394 - 524 ft., 525 - 655 ft. • Electrical interface: 64-pin Champ connectors on high-density EIA For DS3: • Input – Bit rate: 44.736 Mbps +/- 20 ppm – Frame format: Unframed, M13, C-bit – Line code: B3ZS – Termination: Unbalanced coaxial cable A-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.3.4 DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 Cards – Input impedance: 75 ohms +/-5 percent – Cable loss: Max 450 feet with 734A or 728A – AIS: TR-TSY-000191 compliant • Output – Bit rate: 44.736 Mbps +/- 20 ppm – Frame format: Unframed, M13, C-bit – Line code: B3ZS – Termination: Unbalanced coaxial cable – Input impedance: 75 ohms +/-5 percent – Cable loss: Max 450 feet with 734A or 728A cable – AIS: TR-TSY-000191 compliant – Power level: -1.8 to +5.7 dBm – Pulse shape: ANSI T1.102-1988 Figure 8 – Pulse amplitude: 0.36 to 0.85 V peak – Loopback modes: Terminal and facility – Line build out: 0 to 225 feet, 226 to 450 feet • Electrical interface: BNC Connectors on high-density EIA For EC-1: • Input – 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 or 728A – AIS: TR-TSY-000191 compliant • Output – 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 or 728A – 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.85 V peak to peak – Loopback modes: Terminal and facility A-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.3.5 Filler Cards – Line build out: 0 to 225 feet, 226 to 450 feet • Electrical interface: BNC connectors on high-density EIA • Surge protection: Telcordia GR-1089 • Operating temperature: I-Temp, -40 to +65 degrees Celsius. • Operating humidity: 5 to 95 percent, noncondensing • Power consumption: 36.60 W, 0.76 A, 124.97 BTU/hr • Dimensions – Height: 6.93 in. (17.60 cm) – Width: 1.35 in. (3.43 cm) – Depth: 8.80 in. (22.35 cm) – Card weight: 1.5 lbs (0.68 kg) A.3.5 Filler Cards The 15310-EXP-FILLER card has the following specifications: • Environmental – Operating temperature I-Temp: –40 to +65 degrees Celsius (–40 to 149 degrees Fahrenheit) – Operating humidity: 5 to 95 percent, noncondensing • Dimensions – Height: 6.93 in. (176 mm) – Width:1.35 in. (34.29 mm) – Depth: 9.38 in. (238.25 mm) – Card weight (not including clam shell): 0.9 lb (0.45 kg) The 15310-CTX-FILLER card has the following specifications: • Environmental – Operating temperature I-Temp: -40 to +65 degrees Celsius (-40 to 149 degrees Fahrenheit) – Operating humidity: 5 to 95%, noncondensing • Dimensions – Height: 6.94 in. (167.28 mm) – Width: 1.450 in. (36.83 mm) – Depth:8.35 in. (212.09 mm) – Weight not including clam shell: 0.51 lb (0.23 kg)A-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.4 SFP Specifications A.4 SFP Specifications Table A-3 lists specifications for available SFPs that can be used with the 15310-CL-CTX and CTX2500 cards. Table A-4 lists specifications for available SFPs that can be used only with the CTX2500 card. The 15310-CL-CTX card does not have a faceplate because it is located inside the chassis; therefore, the two SFP slots are located on the ONS 15310-CL faceplate, just to the left of the LAN port. The two SFP slots on the CTX2500 are located on CTX2500 faceplate. Table A-5 provides cabling specifications for the single-mode fiber (SMF) SFPs that can be used with both the 15310-CL-CTX and the ONS 15310-MA CTX2500. The ports of the listed SFPs have LC-type connectors. Table A-6 provides cabling specifications for SFPs that can only be used with the ONS 15310-MA CTX-2500 card. Table A-3 SFP Specifications—ONS 15310-CL and ONS 15310-MA SFP Product ID Interface Transmitter Output Power Min/Max (dBm) Receiver Input Power Min/Max (dBm) ONS-SI-155-L1 OC-3 –5.0 to 0 –34 to –10 ONS-SI-155-L2 OC-3 –5.0 to 0 –34 to –10 ONS-SI-155-I1 OC-3 –15 to –8.0 –28 to –8 ONS-SI-622-L1 OC-12 –3.0 to 2.0 –28 to –8 ONS-SI-622-L2 OC-12 –3.0 to 2.0 –28 to –8 ONS-SI-622-I1 OC-12/OC-3 –15 to –8.0 –28 to –8 Table A-4 SFP Specifications—ONS 15310-MA Only SFP Product ID Interface Transmitter Output Power Min/Max (dBm) Receiver Input Power Min/Max (dBm) ONS-SE-155-1470= through ONS-SE-155-1610= OC-3 0 to +5 –34 to –3 (at BER 10-10) ONS-SE-622-1470= through ONS-SE-622-1610= OC-12 0 to +5 –28 to –3 (at BER 10-10) ONS-SI-2G-I1= OC-48 –5.0 to 0 –18 to –0 ONS-SI-2G-L1= OC-48 –3 to +2 –27 to –9 ONS-SI-2G-L2= OC-48 –3 to +2 –28 to –9 ONS-SI-2G-S1= OC-48 –10 to -3 –18 to –3 ONS-SC-2G-30.3= through ONS-SC-2G-60.6= OC-48 0 to +4 –28 to –9 Table A-5 Single-Mode Fiber SFP Port Cabling Specifications—ONS 15310-CL and ONS 15310-MA SFP Product ID Wavelength1 Fiber Type Cable Distance ONS-SI-155-L1 Long Reach 1310 nm 9 micro SMF 50 km (31.07 miles) ONS-SI-155-L2 Long Reach 1550 nm 9 micro SMF 100 km (62.15 miles)A-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix A Specifications A.4 SFP Specifications ONS-SI-155-I1 Intermediate Reach 1310 nm 9 micro SMF 21 km (13.05 miles) ONS-SI-622-L1 Long Reach 1310 nm 9 micron SMF 42 km (26.10 miles) ONS-SI-622-L2 Long Reach 1550 nm 9 micron SMF 85 km (52.82 miles) ONS-SI-622-I1 Intermediate Reach 1310 nm 9 micron SMF 21 km (13.05 miles) 1. Typical loss on a 1310-nm wavelength SMF is 0.6 dB/km. Table A-6 Single-Mode Fiber SFP Port Cabling Specifications—ONS 15310-MA Only SFP Product ID Wavelength1 1. Typical loss on a 1310-nm wavelength SMF is 0.6 dB/km. Fiber Type Cable Distance ONS-SE-155-1470 through ONS-SE-155-1610 (CWDM) 1470 nm through 1610 nm, according to the wavelength indicated in the SFP’s product ID 9 micron SMF 120 km (74.56 miles) ONS-SE-622-1470 through ONS-SE-622-1610 (CWDM) 1470 nm through 1610 nm, according to the wavelength indicated in the SFP’s product ID 9 micron SMF 100 km (62.14 miles) ONS-SI-2G-I1 1310 nm 9 micron SMF 15 km (9.3 miles) ONS-SI-2G-L1 1310 nm 9 micron SMF 40 km (25.80 miles) ONS-SI-2G-L2 1550 nm 9 micron SMF 80 km (49.71 miles) ONS-SI-2G-S1 1310 nm 9 micron SMF 2 km (1.2 miles) ONS-SC-2G-30.3 through ONS-SC-2G-60.6 (DWDM) 1530.30 nm through 1560.60 nm, according to the wavelength indicated in the SFP’s product ID Note When using ONS-SC-2G-xx.x on CTX-2500 the Cisco ONS 15310 -MA operating temperature specification is limited to –5 to +55 degrees Celsius (+23 to +131 degrees Fahrenheit). 9 micron SMF N/A2 2. ONS-SC-2G-xx.x cable distance varies depending on DWDM system installation. Table A-5 Single-Mode Fiber SFP Port Cabling Specifications—ONS 15310-CL and ONS 15310-MA (continued) SFP Product ID Wavelength1 Fiber Type Cable DistanceB-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 APPENDIX B Administrative and Service States This appendix describes the administrative and service states for Cisco ONS 15310-CL and Cisco ONS 15310-MA cards, ports, and cross-connects. For circuit state information, see Chapter 8, “Circuits and Tunnels.” Software Release 6.0 and later states are based on the generic state model defined in Telcordia GR-1093 Core, Issue 2 and ITU-T X.731. B.1 Service States Service states include a Primary State (PST), a Primary State Qualifier (PSTQ), and one or more Secondary States (SST). Table B-1 lists the service state PSTs and PSTQs supported by the ONS 15310-CL and ONS 15310-MA. Table B-2 defines the SSTs supported by the ONS 15310-CL and ONS 15310-MA. Table B-1 ONS 15310-CL and ONS 15310-MA Service State Primary States and Primary State Qualifiers Primary State, Primary State Qualifier Definition IS-NR (In-Service and Normal) The entity is fully operational and will perform as provisioned. OOS-AU (Out-of-Service and Autonomous) The entity is not operational because of an autonomous event. OOS-AUMA (Out-of-Service and Autonomous Management) The entity is not operational because of an autonomous event and has also been manually removed from service. OOS-MA (Out-of-Service and Management) The entity has been manually removed from service.B-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.2 Administrative States B.2 Administrative States Administrative states are used to manage service states. Administrative states consist of a PST and an SST. Table B-3 lists the administrative states supported by the ONS 15310-CL and and ONS 15310-MA. See Table B-2 on page B-2 for SST definitions. Note A change in the administrative state of an entity does not change the service state of supporting or supported entities. Table B-2 ONS 15310-CL and and ONS 15310-MA Secondary States Secondary State Definition AINS (Automatic In-Service) The entity is delayed before transitioning to the IS-NR service state. The transition to IS-NR depends on correction of conditions, or on a soak timer. Alarm reporting is suppressed, but traffic is carried. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. DSBLD (Disabled) The entity was manually removed from service and does not provide its provisioned functions. All services are disrupted; the entity is unable to carry traffic. FLT (Fault) The entity has a raised alarm or condition. LPBK (Loopback) The entity is in loopback mode. MEA (Mismatched Equipment) An improper card is installed. For example, an installed card is not compatible with the card preprovisioning or the slot. This SST applies only to cards. MT (Maintenance) The entity has been manually removed from service for a maintenance activity but still performs its provisioned functions. Alarm reporting is suppressed, but traffic is carried. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. OOG (Out of Group) The virtual concatenated (VCAT) member cross-connect is not used to carry VCAT group traffic. This state is used to put a member circuit out of the group and to stop sending traffic. OOS-MA,OOG only applies to the cross-connects on an end node where VCAT resides. The cross-connects on intermediate nodes are in the OOS-MA,MT service state. SWDL (Software Download) The card is involved in a software and database download. This SST applies only to cards. UAS (Unassigned) The card is not provisioned in the database. This SST applies only to cards. UEQ (Unequipped) The card is not physically present (that is, an empty slot). This SST applies only to cards.B-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3 Service State Transitions B.3 Service State Transitions This section describes the transition from one service state to the next for cards, ports, and cross-connects. A service state transition is based on the action performed on the entity. Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnOOS-MTPorts to TRUE on the NE Defaults tab. B.3.1 Card Service State Transitions Table B-4 lists card service state transitions. Table B-3 ONS 15310-CL and ONS 15310-MA 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 member cross-connect from service and from the group of members. Table B-4 ONS 15310-CL and ONS 15310-MA Card Service State Transitions Current Service State Action Next Service State IS-NR Change the administrative state to OOS,MT. OOS-MA,MT Delete the card. OOS-AUMA,UAS Pull the card. OOS-AU,UEQ Reset the card. OOS-AU,SWDL Alarm/condition is raised. OOS-AU,FLT OOS-AU,AINS and MEA Pull the card. OOS-AU,AINS & UEQ Delete the card. OOS-AUMA,UAS if the card is valid OOS-AUMA,MEA & UAS if the card is invalid OOS-AU,AINS & SWDL Restart completed. IS-NR Pull the card. OOS-AU,AINS & UEQB-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.1 Card Service State Transitions 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 OOS-AU,FLT Pull the card. OOS-AU,UEQ Delete the card. OOS-AUMA,UAS Change the administrative state to OOS,MT. OOS-AUMA,FLT & MT Reset the card. OOS-AU,SWDL Alarm/condition is cleared. IS-NR OOS-AU,MEA Pull the card. OOS-AU,UEQ Delete the card. OOS-AUMA,UAS if the card is valid OOS-AUMA,MEA & UAS if the card is invalid Change the administrative state to OOS,MT. OOS-AUMA,MEA & MT OOS-AU,SWDL Restart completed. IS-NR Pull the card. OOS-AU,UEQ OOS-AU,UEQ Insert a valid card. OOS-AU,SWDL Insert an invalid card. OOS-AU,MEA Delete the card. OOS-AUMA,UAS & UEQ Change the administrative state to OOS,MT. OOS-AUMA,MT & UEQ OOS-AUMA,FLT & MT Pull the card. OOS-AUMA,MT & UEQ Delete the card. OOS-AUMA,UAS Change the administrative state to IS. OOS-AU,FLT Reset the card. OOS-AUMA,MT & SWDL Alarm/condition is cleared. OOS-MA,MT OOS-AUMA,MEA & MT Change the administrative state to IS. OOS-AU,MEA Pull the card. OOS-AUMA,MT & UEQ Delete the card. OOS-AUMA,UAS if the card is valid OOS-AUMA,MEA & UAS if the card is invalid OOS-AUMA,MEA & UAS Pull the card. OOS-AUMA,UAS & UEQ Provision the card. OOS-AU,MEA Table B-4 ONS 15310-CL and ONS 15310-MA Card Service State Transitions (continued) Current Service State Action Next Service StateB-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions B.3.2 Port and Cross-Connect Service State Transitions Table B-5 lists the port and cross-connect service state transitions. Port states do not impact cross-connect states with one exception. A cross-connect in the OOS-AU,AINS service state cannot transition autonomously into the IS-NR service state until the parent port is IS-NR. Note Deleting a port or cross-connect removes the entity from the system. The deleted entity does not transition to another service state. OOS-AUMA,MT & SWDL Restart completed. OOS-MA,MT Pull the card. OOS-AUMA,MT & UEQ 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. OOS-AUMA,MEA & MT Delete the card. OOS-AUMA,UAS & UEQ OOS-AUMA,UAS Pull the card. OOS-AUMA,UAS & UEQ Provision an invalid card. OOS-AU,MEA Provision a valid card. OOS-AU,SWDL OOS-AUMA,UAS & UEQ Insert a valid card. OOS-AU,SWDL Insert an invalid card. OOS-AUMA,MEA & UAS Preprovision a card. OOS-AU,AINS & UEQ OOS-MA,MT Change the administrative state to IS. IS-NR Delete the card. OOS-AUMA,UAS Pull the card. OOS-AUMA,MT & UEQ Reset the card. OOS-AUMA,MT & SWDL Alarm/condition is raised. OOS-AUMA,FLT & MT Table B-4 ONS 15310-CL and ONS 15310-MA Card Service State Transitions (continued) Current Service State Action Next Service StateB-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions Table B-5 ONS 15310-CL and ONS 15310-MA Port and Cross-Connect Service State Transitions Current Service State Action Next Service State IS-NR Put the port or cross-connect in the OOS,MT administrative state. OOS-MA,MT Put the port or cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect Put the port or cross-connect in the IS,AINS administrative state. OOS-AU,AINS Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-MA,MT & OOG Alarm/condition is raised. OOS-AU,FLT OOS-AU,FLT & OOG for a VCAT cross-connect OOS-AU,AINS Put the port or cross-connect in the IS administrative state. IS-NR Put the port or cross-connect in the OOS,MT administrative state. OOS-MA,MT Put the port or cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-MA,MT and OOG Alarm/condition is raised. OOS-AU,AINS & FLT OOS-AU,AINS & FLT & OOG for a VCAT cross-connect 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. OOS-MA,DSBLD Put the port or cross-connect in the OOS,MT administrative state. OOS-AUMA,FLT & MT Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-AUMA,FLT & MT & OOGB-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions OOS-AU,AINS & FLT & OOG Alarm/condition is cleared. OOS-AU,AINS or OOS-MA,MT • If an In Group member is IS-NR or OOS-AU,AINS, the member transitions to OOS-AU,AINS. • If an In Group member is OOS-MA,MT, the member transitions to OOS-MA,MT. Put the VCAT cross-connect in the IS administrative state. OOS-AU,FLT & OOG Put the VCAT cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD & OOG Put the VCAT cross-connect in the OOS,MT administrative state. OOS-AUMA,FLT & MT & OOG OOS-AU,FLT Alarm/condition is cleared. IS-NR Put the port or cross-connect in the IS,AINS administrative state. OOS-AU,AINS & FLT Put the port or cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect Put the port or cross-connect in the OOS,MT administrative state OOS-AUMA,FLT & MT Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-AUMA,FLT & MT & OOG 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. • If an In Group member is OOS-MA,MT, the member transitions to OOS-MA,MT Put the VCAT cross-connect in the IS,AINS administrative state. OOS-AU,AINS & FLT & OOG Put the VCAT cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD & OOG Put the VCAT cross-connect in the OOS,MT administrative state. OOS-AUMA,FLT & MT & OOG Table B-5 ONS 15310-CL and ONS 15310-MA Port and Cross-Connect Service State Transitions Current Service State Action Next Service StateB-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions OOS-AUMA,FLT & LPBK & MT Release the loopback. OOS-AUMA,FLT & MT Alarm/condition is cleared. OOS-MA,LPBK & MT OOS-AUMA,FLT & LPBK & MT & OOG Release the loopback. OOS-AUMA,FLT & MT & OOG Alarm/condition is cleared. OOS-MT,MT & OOG OOS-AUMA,FLT & MT Alarm/condition is cleared. OOS-MA,MT Put the port or cross-connect in the IS administrative state. OOS-AU,FLT Put the port or cross-connect in the IS,AINS administrative state. OOS-AU,AINS & FLT Put the port or cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect Put the port or cross-connect in a loopback. OOS-AUMA,FLT & LPBK & MT Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-AUMA,FLT & MT & OOG OOS-AUMA,FLT & MT & OOG Alarm/condition is cleared. OOS-MA,MT & OOG Put the VCAT cross-connect in the IS administrative state. Note VCAT In Group members are in the OOS-AU,FLT or IS-NR service state. OOS-AU,FLT & OOG Put the VCAT cross-connect in the IS,AINS administrative state. Note VCAT In Group members are in the OOS-AU,AINS & FLT or IS-NR service state. OOS-AU,AINS & FLT & OOG Put the VCAT cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD & OOG Put the VCAT cross-connect in the OOS,MT administrative state. Note VCAT In Group members are in the OOS-MA,FLT & MT service state. OOS-MA,FLT & MT Operate a loopback. OOS-MA,FLT & LPBK & MT & OOG Table B-5 ONS 15310-CL and ONS 15310-MA Port and Cross-Connect Service State Transitions Current Service State Action Next Service StateB-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions OOS-MA,DSBLD 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. OOS-AU,AINS Put the port or cross-connect in the OOS,MT. OOS-MA,MT Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-MA,MT & OOG Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-MA,MT & OOG OOS-MA,LPBK & MT Release the loopback. Note While in OOS-MA,LPBK & MT, both Cisco Transport Controller (CTC) and Transaction Language One (TL1) allow a cross-connect to be deleted, which also removes the loopback. This applies only to the cross-connect, not the ports. OOS-MA,MT Alarm/condition is raised. OOS-AUMA,FLT & LPBK & MT OOS-AUMA,FLT & LPBK & MT & OOG for a VCAT cross-connect OOS-MA,LPBK & MT & OOG Alarm/condition is raised. OOS-AUMA,FLT & LPBK & MT & OOG Table B-5 ONS 15310-CL and ONS 15310-MA Port and Cross-Connect Service State Transitions Current Service State Action Next Service StateB-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix B Administrative and Service States B.3.2 Port and Cross-Connect Service State Transitions 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. OOS-AU,AINS Put the port or cross-connect in the OOS,DSBLD administrative state. OOS-MA,DSBLD OOS-MA,DSBLD & OOG for a VCAT cross-connect Put the port or cross-connect in a loopback. OOS-MA,LPBK & MT Put the VCAT cross-connect in the OOS,OOG administrative state. OOS-MA,MT & OOG Alarm/condition is raised. OOS-AUMA,FLT & MT OOS-AUMA,FLT & MT & OOG for a VCAT cross-connect OOG-MA,MT & OOG Alarm/condition is raised. OOS-AUMA,FLT & MT & OOG Table B-5 ONS 15310-CL and ONS 15310-MA Port and Cross-Connect Service State Transitions Current Service State Action Next Service StateC-1 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 APPENDIX 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This appendix describes the factory-configured (default) network element (NE) settings for the Cisco ONS 15310-CL and Cisco ONS 15310-MA. It includes descriptions of card default settings, node default settings, and Cisco Transport Controller (CTC) default settings. For procedures for importing, exporting, and editing the settings, refer to the “Maintain the Node” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Cards that are not listed in this appendix are not supported by user-configurable NE defaults settings. To change card settings individually (that is, without directly changing the NE defaults), refer to the “Change Port Settings” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. To change node settings, refer to the “Change Node Settings” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. This appendix includes the following sections: • C.1 Network Element Defaults Description, page C-1 • C.2 ONS 15310-CL Card Default Settings, page C-2 • C.3 Cisco ONS 15310-CL Node Default Settings, page C-20 • C.4 CTC Default Settings, page C-29 • C.5 ONS 15310-MA Card Default Settings, page C-30 • C.6 Cisco ONS 15310-MA Node Default Settings, page C-64 C.1 Network Element Defaults Description The NE defaults are preinstalled on each Cisco ONS 15310-CL and Cisco ONS 15310-MA common control card. They also ship as a file called 15310-defaults.txt (for the ONS 15310-CL), or 15310MA-defaults.txt (for the ONS 15310-MA) on the CTC software CD if you want to import the defaults onto existing common control cards. The NE defaults include card-level, CTC, and node-level defaults.C-2 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2 ONS 15310-CL Card Default Settings Changes to card provisioning that are made manually using procedures in the “Change Card Settings” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide override default settings. If you use the CTC Defaults editor (in the node view Provisioning > Defaults tab) or import a new defaults file, any changes to card or port settings only affect cards that are installed or preprovisioned after the defaults have changed. Changes that are made manually to most node-level default settings override the current settings, whether default or provisioned. If you change node-level default settings, either by using the Defaults editor or by importing a new defaults file, the new defaults reprovision the node immediately for all settings except those relating to protection (1+1 bidirectional switching, 1+1 reversion time, and 1+1 revertive), which apply to subsequent provisioning. Note Changing some node-level provisioning via NE defaults can cause CTC disconnection or a reboot of the node in order for the provisioning to take effect. Before you change a default, check in the Side Effects column of the Defaults editor (right-click a column header and select Show Column > Side Effects) and be prepared for the occurrence of any side effects listed for that default. C.2 ONS 15310-CL Card Default Settings The tables in this section list the default settings for Cisco ONS 15310-CL common control and Ethernet cards. Cisco provides several types of user-configurable defaults for these cards. Types of card defaults can be broadly grouped by function, as outlined in the following subsections. For information about individual card settings, refer to the “Change Port Settings” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Note When the card level defaults are changed, the new provisioning done after the defaults have changed is affected. Existing provisioning remains unaffected. C.2.1 Configuration Defaults Except as noted, card-level and port-level configuration defaults correspond to settings found in the CTC card-level Provisioning tabs. Note The full set of Automatic Laser Shutdown (ALS) configuration defaults can be found in the CTC card-level Maintenance > Optical > ALS tabs for supported cards. ALS defaults are supported for pluggable port modules (PPMs) on the 15310-CL-CTX card. Note ML-100T-8 console port access and Remote Authentication Dial In User Service (RADIUS) server access defaults can be found in the CTC card-level IOS tab for ML-100T-8 cards. Configuration defaults that correspond to settings that are reachable from the CTC card-level Provisioning tabs (except as noted) include the following types of options (arranged by CTC subtab): • Broadband Ports—(15310-CL-CTX cards only) Set the background block error (BBE) port rate as DS3, EC1, or unassigned (DS3 is the default).C-3 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.2 Threshold Defaults • Pluggable Port Modules—(15310-CL-CTX cards only) PPM (SFP) slot and port rate configuration settings. • DS1—(15310-CL-CTX cards only) DS-1 rate port-level line configuration settings. • DS3—(15310-CL-CTX cards only) DS-3 rate port-level line configuration settings. • EC1—(15310-CL-CTX cards only) EC-1 rate port-level line configuration and SONET synchronous transport signal (STS) settings. • Optical—(15310-CL-CTX cards only) OC-N rate port-level line configuration and SONET STS settings. • ALS (card-level Maintenance > ALS tab)—(15310-CL-CTX cards only) PPM (SFP) OC-N port ALS configuration defaults. • IOS (card-level IOS tab)—(ML-100T-8 cards only) Console port and RADIUS server access settings. • Ether Ports—(CE-100T-8 cards only) Line configuration settings (including 802 class of service [IEEE 802.1p CoS] and IP type of service [ToS]). • POS Ports—(CE-100T-8 cards only) Line configuration settings. Note Line configuration defaults for the CE-100T-8 card apply to both Ethernet port and packet-over-SONET (POS) port settings where the same setting exists for both. Note PPM (SFP) slots and ports are unassigned by default. You can optionally use the Defaults editor to change these defaults to automatically assign PPM slots to take a single-port PPM, and to automatically assign PPM port OC-N rates. However, use discretion in changing the default PPM port rate in cases where single-rate PPMs might be inserted in a card, since preprovisioned PPM port rates that are applied to a single-rate PPM of the wrong rate will result in a mismatch of equipment and software. Note For further information about the supported features of each individual card, see Chapter 12, “Performance Monitoring.”For more information about the supported features of Ethernet cards, consult the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide. C.2.2 Threshold Defaults Threshold default settings define the default cumulative values (thresholds) beyond which a threshold crossing alert (TCA) will be raised, making it possible to monitor the network and detect errors early. Card threshold default settings are provided as follows: • PM thresholds—(15310-CL-CTX cards only) Applicable to DS-1, DS-3, EC-1, and OC-N ports. Can be expressed in counts or seconds; includes line, electrical, and SONET thresholds. • Physical Layer thresholds—(15310-CL-CTX cards only) Applicable to OC-N ports. Expressed in percentages; includes optics thresholds.C-4 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card 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 Virtual Tributary (VT) for performance monitoring (PM) thresholds, and TCA (warning) or Alarm for physical thresholds. PM threshold types define the layer to which the threshold applies. Physical threshold types define the level of response expected when the threshold is crossed. Note For full descriptions of the thresholds you can set for each card, refer to Chapter 12, “Performance Monitoring.” Note For additional information regarding PM parameter threshold defaults as defined by Telcordia specifications, refer to Telcordia GR-820-CORE and GR-253-CORE. C.2.3 Defaults by Card In the tables that follow, card defaults are defined by the default name, its factory-configured value, and the domain of allowable values that you can assign to it. Note Some default values, such as certain thresholds, are interdependent. Before changing a value, review the domain for that default and any other related defaults for potential dependencies. C.2.3.1 15310-CL-CTX Card Default Settings Table C-1 lists the 15310-CL-CTX card default settings. Table C-1 15310-CL-CTX Card Default Settings Default Name Default Value Default Domain CTX.Broadband.portAssignment DS3-PORT UNASSIGNED, DS3-PORT, EC1-PORT CTX.DS1-PORT.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX.DS1-PORT.config.LineCoding AMI B8ZS, AMI CTX.DS1-PORT.config.LineLength 0 - 131 ft 0 - 131 ft, 132 - 262 ft, 263 - 393 ft, 394 - 524 ft, 525 - 655 ft CTX.DS1-PORT.config.LineType D4 ESF, D4, UNFRAMED CTX.DS1-PORT.config.RetimingEnabled FALSE TRUE, FALSE CTX.DS1-PORT.config.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX.DS1-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX.DS1-PORT.config.SendAISOnTerminalLoopback TRUE TRUE, FALSE CTX.DS1-PORT.config.SendAISVOnDefects FALSE FALSE, TRUE CTX.DS1-PORT.config.SendDoNotUse FALSE TRUE, FALSE CTX.DS1-PORT.config.SFBER 1.00E-04 1E-3, 1E-4, 1E-5C-5 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.DS1-PORT.config.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX.DS1-PORT.config.SyncMsgIn FALSE FALSE when LineType D4, E1_MF, E1_CRCMF, UNFRAMED, AUTO FRAME; FALSE, TRUE when LineType ESF, J_ESF CTX.DS1-PORT.config.TreatLOFAsDefect TRUE FALSE, TRUE CTX.DS1-PORT.pmthresholds.line.farend.15min.ES 65 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.line.farend.1day.ES 648 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.line.nearend.15min.CV 13340 (BPV count) 0 - 1388700 CTX.DS1-PORT.pmthresholds.line.nearend.15min.ES 65 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.line.nearend.15min.SES 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.line.nearend.1day.CV 133400 (BPV count) 0 - 133315200 CTX.DS1-PORT.pmthresholds.line.nearend.1day.ES 648 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.line.nearend.1day.SES 100 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.farend.15min.CSS 25 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.15min.CV 13296 (BIP count) 0 - 287100 CTX.DS1-PORT.pmthresholds.path.farend.15min.ES 65 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.15min.ESA 25 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.15min.ESB 25 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.15min.FC 10 (count) 0 - 90 CTX.DS1-PORT.pmthresholds.path.farend.15min.SEFS 25 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.15min.SES 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.15min.UAS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.farend.1day.CSS 25 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.farend.1day.CV 132960 (BIP count) 0 - 27561600 CTX.DS1-PORT.pmthresholds.path.farend.1day.ES 648 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.farend.1day.ESA 25 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.farend.1day.ESB 25 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.farend.1day.FC 40 (count) 0 - 8640 CTX.DS1-PORT.pmthresholds.path.farend.1day.SEFS 25 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.farend.1day.SES 100 (seconds) 0 - 86400 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-6 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.DS1-PORT.pmthresholds.path.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.nearend.15min.AISS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.nearend.15min.CV 13296 (BIP count) 0 - 287100 CTX.DS1-PORT.pmthresholds.path.nearend.15min.ES 65 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.nearend.15min.FC 10 (count) 0 - 90 CTX.DS1-PORT.pmthresholds.path.nearend.15min.SAS 2 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.nearend.15min.SES 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.path.nearend.1day.AISS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.nearend.1day.CV 132960 (BIP count) 0 - 27561600 CTX.DS1-PORT.pmthresholds.path.nearend.1day.ES 648 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.nearend.1day.FC 40 (count) 0 - 8640 CTX.DS1-PORT.pmthresholds.path.nearend.1day.SAS 17 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.nearend.1day.SES 100 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.path.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.sts.farend.15min.CV 15 (B3 count) 0 - 2160000 CTX.DS1-PORT.pmthresholds.sts.farend.15min.ES 12 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.sts.farend.15min.FC 10 (count) 0 - 72 CTX.DS1-PORT.pmthresholds.sts.farend.15min.SES 3 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.sts.farend.15min.UAS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.sts.farend.1day.CV 125 (B3 count) 0 - 207360000 CTX.DS1-PORT.pmthresholds.sts.farend.1day.ES 100 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.sts.farend.1day.FC 40 (count) 0 - 6912 CTX.DS1-PORT.pmthresholds.sts.farend.1day.SES 7 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.sts.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX.DS1-PORT.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 CTX.DS1-PORT.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX.DS1-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-7 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.DS1-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX.DS1-PORT.pmthresholds.vt.farend.15min.ES 12 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.vt.farend.15min.SES 3 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.vt.farend.15min.UAS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.vt.farend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX.DS1-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.vt.nearend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX.DS1-PORT.pmthresholds.vt.nearend.15min.ES 12 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.vt.nearend.15min.SES 3 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.DS1-PORT.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX.DS1-PORT.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.DS1-PORT.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS3-PORT.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX.DS3-PORT.config.FeInhibitLpbk FALSE TRUE, FALSE CTX.DS3-PORT.config.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft CTX.DS3-PORT.config.LineType M13 UNFRAMED, M13, C BIT CTX.DS3-PORT.config.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX.DS3-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX.DS3-PORT.config.SendAISOnTerminalLoopback TRUE TRUE, FALSE CTX.DS3-PORT.config.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 CTX.DS3-PORT.config.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX.DS3-PORT.pmthresholds.cpbitpath.farend.15min.CV 382 (BIP count) 0 - 287100 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.15min.ES 25 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.15min.SAS 2 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.15min.SES 4 (seconds) 0 - 900 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-8 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.DS3-PORT.pmthresholds.cpbitpath.farend.15min.UAS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.1day.CV 3820 (BIP count) 0 - 27561600 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.1day.ES 250 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.1day.SAS 8 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.1day.SES 40 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.cpbitpath.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.CV 382 (BIP count) 0 - 287100 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.ES 25 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.SES 4 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.CV 3820 (BIP count) 0 - 27561600 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.ES 250 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.SES 40 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.line.nearend.15min.CV 387 (BPV count) 0 - 38700 CTX.DS3-PORT.pmthresholds.line.nearend.15min.ES 25 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.line.nearend.15min.SES 4 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.line.nearend.1day.CV 3865 (BPV count) 0 - 3715200 CTX.DS3-PORT.pmthresholds.line.nearend.1day.ES 250 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.line.nearend.1day.SES 40 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.15min.AISS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.15min.CV 382 (BIP count) 0 - 287100 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.15min.ES 25 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.15min.SAS 2 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.15min.SES 4 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.1day.AISS 10 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.1day.CV 3820 (BIP count) 0 - 27561600 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.1day.ES 250 (seconds) 0 - 86400 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-9 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.DS3-PORT.pmthresholds.pbitpath.nearend.1day.SAS 8 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.1day.SES 40 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.pbitpath.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.sts.farend.15min.CV 15 (G1 count) 0 - 2160000 CTX.DS3-PORT.pmthresholds.sts.farend.15min.ES 12 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.sts.farend.15min.FC 10 (count) 0 - 72 CTX.DS3-PORT.pmthresholds.sts.farend.15min.SES 3 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.sts.farend.15min.UAS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.sts.farend.1day.CV 125 (G1 count) 0 - 207360000 CTX.DS3-PORT.pmthresholds.sts.farend.1day.ES 100 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.sts.farend.1day.FC 40 (count) 0 - 6912 CTX.DS3-PORT.pmthresholds.sts.farend.1day.SES 7 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.sts.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX.DS3-PORT.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 CTX.DS3-PORT.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.DS3-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX.DS3-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 CTX.DS3-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.DS3-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.EC1-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX.EC1-PORT.config.line.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft CTX.EC1-PORT.config.line.PJStsMon# 0 (STS #) 0 - 1 CTX.EC1-PORT.config.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX.EC1-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX.EC1-PORT.config.line.SendAISOnTerminalLoopback FALSE TRUE, FALSE CTX.EC1-PORT.config.line.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 CTX.EC1-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX.EC1-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-10 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.EC1-PORT.pmthresholds.line.farend.15min.CV 1312 (B2 count) 0 - 137700 CTX.EC1-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 CTX.EC1-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 8850600 CTX.EC1-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 72 CTX.EC1-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 CTX.EC1-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 CTX.EC1-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 CTX.EC1-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 CTX.EC1-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 138600 CTX.EC1-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 13305600 CTX.EC1-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-11 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.EC1-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC12-PORT.config.line.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES CTX.OC12-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX.OC12-PORT.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test CTX.OC12-PORT.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 CTX.OC12-PORT.config.line.AlsRecoveryPulseInterval 100 (seconds) 60 - 300 CTX.OC12-PORT.config.line.PJStsMon# 0 (STS #) 0 - 12 CTX.OC12-PORT.config.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-12 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC12-PORT.config.line.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE CTX.OC12-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX.OC12-PORT.config.line.SendDoNotUse FALSE FALSE, TRUE CTX.OC12-PORT.config.line.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 CTX.OC12-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX.OC12-PORT.config.line.SyncMsgIn TRUE FALSE, TRUE CTX.OC12-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE CTX.OC12-PORT.physicalthresholds.alarm.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.alarm.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX.OC12-PORT.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.alarm.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX.OC12-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX.OC12-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX.OC12-PORT.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.warning.15min.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX.OC12-PORT.physicalthresholds.warning.15min.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.warning.15min.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX.OC12-PORT.physicalthresholds.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.warning.1day.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX.OC12-PORT.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX.OC12-PORT.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX.OC12-PORT.physicalthresholds.warning.1day.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX.OC12-PORT.pmthresholds.line.farend.15min.CV 5315 (B2 count) 0 - 552600 CTX.OC12-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-13 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC12-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 CTX.OC12-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.line.farend.1day.CV 53150 (B2 count) 0 - 53049600 CTX.OC12-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 CTX.OC12-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.line.nearend.15min.CV 5315 (B2 count) 0 - 552600 CTX.OC12-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 CTX.OC12-PORT.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 CTX.OC12-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.line.nearend.1day.CV 53150 (B2 count) 0 - 53049600 CTX.OC12-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC12-PORT.pmthresholds.line.nearend.1day.PSC 5 (count) 0 - 57600 CTX.OC12-PORT.pmthresholds.line.nearend.1day.PSD 600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 553500 CTX.OC12-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 53136000 CTX.OC12-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-14 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.CV 75 (B3 count) 0 - 2160000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.ES 60 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.FC 10 (count) 0 - 72 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-15 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.SES 3 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts12c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.CV 750 (B3 count) 0 - 207360000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.ES 600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts12c.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.CV 25 (B3 count) 0 - 2160000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.ES 20 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.FC 10 (count) 0 - 72 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.SES 3 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.ES 200 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC3-PORT.config.line.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES CTX.OC3-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX.OC3-PORT.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test CTX.OC3-PORT.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 CTX.OC3-PORT.config.line.AlsRecoveryPulseInterval 100 (seconds) 60 - 300 CTX.OC3-PORT.config.line.PJStsMon# 0 (STS #) 0 - 3 CTX.OC3-PORT.config.line.SDBER 1.00E-07 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX.OC3-PORT.config.line.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE CTX.OC3-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX.OC3-PORT.config.line.SendDoNotUse FALSE FALSE, TRUE CTX.OC3-PORT.config.line.SFBER 1.00E-04 1E-3, 1E-4, 1E-5 CTX.OC3-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX.OC3-PORT.config.line.SyncMsgIn TRUE FALSE, TRUE CTX.OC3-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE CTX.OC3-PORT.physicalthresholds.alarm.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.alarm.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX.OC3-PORT.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.alarm.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX.OC3-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-17 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC3-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX.OC3-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX.OC3-PORT.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.warning.15min.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX.OC3-PORT.physicalthresholds.warning.15min.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.warning.15min.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX.OC3-PORT.physicalthresholds.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.warning.1day.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX.OC3-PORT.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX.OC3-PORT.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX.OC3-PORT.physicalthresholds.warning.1day.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX.OC3-PORT.pmthresholds.line.farend.15min.CV 1312 (B2 count) 0 - 137700 CTX.OC3-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 CTX.OC3-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 13219200 CTX.OC3-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 CTX.OC3-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 CTX.OC3-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 CTX.OC3-PORT.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 CTX.OC3-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-18 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC3-PORT.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 CTX.OC3-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC3-PORT.pmthresholds.line.nearend.1day.PSC 5 (count) 0 - 57600 CTX.OC3-PORT.pmthresholds.line.nearend.1day.PSD 600 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 138600 CTX.OC3-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 13305600 CTX.OC3-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-19 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.2.3 Defaults by Card CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.CV 25 (B3 count) 0 - 2160000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.ES 20 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.FC 10 (count) 0 - 72 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.SES 3 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts3c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.CV 250 (B3 count) 0 - 207360000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.ES 200 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.FC 40 (count) 0 - 6912 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX.OC3-PORT.pmthresholds.sts3c.nearend.1day.UAS 10 (seconds) 0 - 86400 Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default DomainC-20 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3 Cisco ONS 15310-CL Node Default Settings C.2.3.2 Ethernet Card Default Settings Table C-2 lists the CE-100T-8 and ML100T-8 card default settings. C.3 Cisco ONS 15310-CL Node Default Settings Table C-3 on page C-21 lists the node-level default settings for the Cisco ONS 15310-CL. Cisco provides the following types of node-level user-configurable defaults: • Circuit settings—Set the administrative state and path protection circuit defaults, and whether to have circuits send a payload defect indication condition (PDIP). • General settings—Set general node management defaults, including whether to use Daylight Savings Time (DST), whether to insert an Alarm Indication Signal VT (AIS-V) in each VT when the carrying STS crosses the signal degrade (SD) path bit error rate (BER) threshold, the IP address of the Network Time Protocol/Simple Network Time Protocol (NTP/SNTP) server to be used, the time zone where the node is located, the SD path BER value, the defaults description, and whether to report loopback conditions on ports in Out-of-Service, Maintenance (OOS-MT) service state. • Network settings—Set whether to prevent the display of node IP addresses in CTC (applicable for all users except Superusers), and the default gateway node type. • OSI settings—Set Open System Interconnection (OSI) main setup, generic routing encapsulation (GRE) tunnel, link access protocol on the D channel (LAP-D), router subnet, and TID address resolution protocol (TARP) settings. • 1+1 protection settings—Set whether or not 1+1 protected circuits have bidirectional switching, are revertive, and what the reversion time is. • Legal Disclaimer—Set the legal disclaimer that warns users at the login screen about the possible legal or contractual ramifications of accessing equipment, systems, or networks without authorization. CTX.PPM.portAssignment UNASSIGNE D UNASSIGNED, OC3-PORT, OC12-PORT CTX.PPM.slotAssignment UNASSIGNE D UNASSIGNED, PPM (1 Port) CTX.Wideband.portAssignment DS1-PORT DS1-PORT Table C-1 15310-CL-CTX Card Default Settings (continued) Default Name Default Value Default Domain Table C-2 Ethernet Card Default Settings Default Name Default Value Default Domain CE-100T-8.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CE-100T-8.config.State OOS,DSBLD IS, OOS,DSBLD, OOS,MT, IS,AINS CE-100T-8.etherPortConfig.802-1Q-VlanCoS 7 (count) 0 - 7 CE-100T-8.etherPortConfig.IP-ToS 255 (count) 0 - 255 ML100T.ios.consolePortAccess TRUE TRUE, FALSE ML100T.ios.radiusServerAccess FALSE TRUE, FALSEC-21 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3 Cisco ONS 15310-CL Node Default Settings • Security Access settings—Sets default security settings for LAN access, shell access, serial craft access, element management system (EMS) access (including Internet Inter-Object Request Broker Protocol [IIOP] listener port number), TL1 access, and Simple Network Management Protocol (SNMP) access. • Security Grant Permissions—Set default user security levels for activating/reverting software, performance monitoring data clearing, database restoring, and retrieving audit logs. • Security RADIUS settings—Set default RADIUS server settings for accounting port number, authentication port number, and whether to enable the node as a final authenticator. • Security Policy settings—Set the allowable failed logins before lockout, idle user timeout for each user level, optional lockout duration or manual unlock enabled, password reuse and change frequency policies, number of characters difference between the old and new password, password aging by security level, enforced single concurrent session per user, and option to disable inactive user after a set inactivity period. • BITS Timing settings—Set the AIS threshold, coding, framing, State, State Out, and line build-out (LBO) settings for building integrated timing supply 1 (BITS-1) timing. • General Timing settings—Set the mode (External, Line, or Mixed), quality of reserved (RES) timing (set the rule that defines the order of clock quality from lowest to highest), revertive, reversion time, and synchronization status messaging (SSM) message set for node timing. Note Any node level defaults changed using the Provisioning > Defaults tab, changes existing node level provisioning. Although this is service affecting, it depends on the type of defaults changed, for example, general, and all timing and security attributes. The “Changing default values for some node level attributes overrides the current provisioning.” message is displayed. The Side Effects column of the Defaults editor (right-click a column header and select Show Column > Side Effects) explains the effect of changing the default values. However, when the card level defaults are changed using the Provisioning > Defaults tab, existing card provisioning remains unaffected. Note For more information about each individual node setting, refer to the “Change Node Settings” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Table C-3 Cisco ONS 15310-CL Node Default Settings Default Name Default Value Default Domain NODE.circuits.SendPDIP FALSE TRUE, FALSE NODE.circuits.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS NODE.circuits.upsr.ReversionTime 5.0 (minutes) 0.5, 1.0, 1.5 .. 12.0 NODE.circuits.upsr.Revertive FALSE TRUE, FALSE NODE.circuits.upsr.STS_SDBER 1.00E-06 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 NODE.circuits.upsr.STS_SFBER 1.00E-04 1E-3, 1E-4, 1E-5 NODE.circuits.upsr.SwitchOnPDIP FALSE TRUE, FALSEC-22 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3 Cisco ONS 15310-CL Node Default Settings NODE.circuits.upsr.VT_SDBER 1.00E-06 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 NODE.circuits.upsr.VT_SFBER 1.00E-04 1E-3, 1E-4, 1E-5 NODE.general.DefaultsDescription Factory Defaults Free form field NODE.general.InsertAISVOnSDP FALSE TRUE, FALSE NODE.general.NtpSntpServer 0.0.0.0 IP Address NODE.general.ReportLoopbackConditionsOnOOS-MTPorts FALSE FALSE, TRUE NODE.general.SDPBER 1.00E-06 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 NODE.general.TimeZone (GMT-08:00) Pacific Time (US & Canada), Tijuana (For applicable time zones, see Table C-4 on page C-26.) NODE.general.UseDST TRUE TRUE, FALSE NODE.network.general.CtcIpDisplaySuppression FALSE TRUE, FALSE NODE.network.general.GatewaySettings None None, ENE, GNE, ProxyOnlyNode NODE.osi.greTunnel.OspfCost 110 110, 111, 112 .. 65535 NODE.osi.greTunnel.SubnetMask 24 (bits) 8, 9, 10 .. 32 NODE.osi.lapd.Mode AITS AITS, UITS NODE.osi.lapd.MTU 512 512, 513, 514 .. 1500 NODE.osi.lapd.Role Network Network, User NODE.osi.lapd.T200 200 (ms) 200, 300, 400 .. 20000 NODE.osi.lapd.T203 10000 (ms) 4000, 4100, 4200 .. 120000 NODE.osi.mainSetup.L1LSPBufferSize 512 (bytes) 512 - 1500 NODE.osi.mainSetup.NodeRoutingMode End System End System, Intermediate System Level 1 NODE.osi.subnet.DISPriority 63 1, 2, 3 .. 127 NODE.osi.subnet.ESH 10 (sec) 10, 20, 30 .. 1000 NODE.osi.subnet.IIH 3 (sec) 1, 2, 3 .. 600 NODE.osi.subnet.ISH 10 (sec) 10, 20, 30 .. 1000 NODE.osi.subnet.LANISISCost 20 1, 2, 3 .. 63 Table C-3 Cisco ONS 15310-CL Node Default Settings (continued) Default Name Default Value Default DomainC-23 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3 Cisco ONS 15310-CL Node Default Settings NODE.osi.subnet.LDCCISISCost 40 1, 2, 3 .. 63 NODE.osi.subnet.SDCCISISCost 60 1, 2, 3 .. 63 NODE.osi.tarp.L1DataCache TRUE FALSE, TRUE NODE.osi.tarp.LANStormSuppression TRUE FALSE, TRUE NODE.osi.tarp.LDB TRUE FALSE, TRUE NODE.osi.tarp.LDBEntry 5 (min) 1 - 10 NODE.osi.tarp.LDBFlush 5 (min) 0 - 1440 NODE.osi.tarp.PDUsL1Propagation 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.T4Timer 20 (sec) 0 - 3600 NODE.osi.tarp.Type4PDUDelay 0 (sec) 0 - 255 NODE.protection.1+1.BidirectionalSwitching FALSE TRUE, FALSE NODE.protection.1+1.ReversionTime 5.0 (minutes) 0.5, 1.0, 1.5 .. 12.0 NODE.protection.1+1.Revertive FALSE TRUE, FALSE NODE.security.emsAccess.AccessState NonSecure NonSecure, Secure NODE.security.emsAccess.IIOPListenerPort (May reboot node) 57790 (port #) 0 - 65535 NODE.security.grantPermission.ActivateRevertSoftware Superuser Provisioning, Superuser NODE.security.grantPermission.PMClearingPrivilege Provisioning Provisioning, Superuser NODE.security.grantPermission.RestoreDB Superuser Provisioning, Superuser NODE.security.grantPermission.RetrieveAuditLog Superuser Provisioning, Superuser NODE.security.idleUserTimeout.Maintenance 01:00 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.idleUserTimeout.Provisioning 00:30 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.idleUserTimeout.Retrieve 00:00 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.idleUserTimeout.Superuser 00:15 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.lanAccess.LANAccess (May disconnect CTC from node) Front Only No LAN Access, Front Only Table C-3 Cisco ONS 15310-CL Node Default Settings (continued) Default Name Default Value Default DomainC-24 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3 Cisco ONS 15310-CL Node Default Settings NODE.security.lanAccess.RestoreTimeout 5 (minutes) 0 - 60 NODE.security.legalDisclaimer.LoginWarningMessage WARN INGThis system is restricted to authorized users for business purposes. Unauthorized

access is a violation of the law. This service may be monitored for administrative

and security reasons. By proceeding, you consent to this monitoring. Free form field NODE.security.other.DisableInactiveUser FALSE FALSE, TRUE NODE.security.other.InactiveDuration 45 (days) 1, 2, 3 .. 99 when DisableInactiveU ser TRUE; 45 when DisableInactiveU ser FALSE NODE.security.other.SingleSessionPerUser FALSE TRUE, FALSE NODE.security.passwordAging.EnforcePasswordAging FALSE TRUE, FALSE NODE.security.passwordAging.maintenance.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.maintenance.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordAging.provisioning.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.provisioning.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordAging.retrieve.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.retrieve.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordAging.superuser.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.superuser.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordChange.CannotChangeNewPassword FALSE TRUE, FALSE Table C-3 Cisco ONS 15310-CL Node Default Settings (continued) Default Name Default Value Default DomainC-25 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3 Cisco ONS 15310-CL Node Default Settings NODE.security.passwordChange.CannotChangeNewPasswordForNDays 20 (days) 20 - 95 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.radiusServer.AccountingPort 1813 (port) 0 - 32767 NODE.security.radiusServer.AuthenticationPort 1812 (port) 0 - 32767 NODE.security.radiusServer.EnableNodeAsFinalAuthenticator TRUE FALSE, TRUE NODE.security.serialCraftAccess.EnableCraftPort TRUE TRUE, FALSE NODE.security.shellAccess.AccessState NonSecure Disabled, NonSecure, Secure NODE.security.shellAccess.EnableShellPassword FALSE TRUE, FALSE NODE.security.shellAccess.TelnetPort 23 23 - 9999 NODE.security.snmpAccess.AccessState NonSecure Disabled, NonSecure NODE.security.tl1Access.AccessState NonSecure Disabled, NonSecure, Secure NODE.security.userLockout.FailedLoginsAllowedBeforeLockout 5 (times) 0 - 10 NODE.security.userLockout.LockoutDuration 00:30 (mins:secs) 00:00, 00:05, 00:10 .. 10:00 NODE.security.userLockout.ManualUnlockBySuperuser FALSE TRUE, FALSE NODE.timing.bits-1.AISThreshold SMC PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES NODE.timing.bits-1.Coding B8ZS B8ZS, AMI NODE.timing.bits-1.Framing ESF ESF, D4 NODE.timing.bits-1.LBO 0-133 (ft) 0-133, 134-266, 267-399, 400-533, 534-655 NODE.timing.bits-1.State IS IS, OOS,DSBLD NODE.timing.bits-1.StateOut IS IS, OOS,DSBLD NODE.timing.general.Mode External External, Line, Mixed Table C-3 Cisco ONS 15310-CL Node Default Settings (continued) Default Name Default Value Default DomainC-26 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.3.1 Time Zones C.3.1 Time Zones Table C-4 lists the time zones that apply for node time zone defaults. Time zones in the table are ordered by their relative relationships to Greenwich Mean Time (GMT), and the default values are displayed in the correct format for valid default input. NODE.timing.general.QualityOfRES RES=DUS PRS Optical > ALS tabs for supported cards. ALS defaults are supported for PPM (SFP) OC-N ports on the CTX2500 card. Note ML-100T-8 console port access and RADIUS server access defaults can be found in the CTC card-level IOS tab for ML-100T-8 cards. Configuration defaults that correspond to settings that are reachable from the CTC card-level Provisioning tabs (except as noted) include the following types of options (arranged by CTC subtab): • Broadband Ports—(DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards only) Set the BBE port rate as DS3, EC1, or unassigned (DS3 is the default). • DS1—(DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards only) DS-1 rate port-level line configuration settings. • DS3—(DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards only) DS-3 rate port-level line configuration settings. • EC1—(DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards only) EC-1 rate port-level line configuration and SONET STS settings. • Pluggable Port Modules—(CTX2500 cards only) PPM (SFP) slot and port rate configuration settings. • Optical—(CTX2500 cards only) OC-N rate port-level line configuration and SONET STS settings. • ALS (card-level Maintenance > Optical > ALS tab)—(CTX2500 cards only) PPM (SFP) OC-N port ALS configuration defaults. • IOS (card-level IOS tab)—(ML-100T-8 cards only) Console port and RADIUS server access settings. • Ether Ports—(CE-100T-8 cards only) Line configuration settings (including IEEE 802.1p CoS and IP ToS). • POS Ports—(CE-100T-8 cards only) Line configuration settings.C-31 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.2 Threshold Defaults Note Line configuration defaults for the CE-100T-8 apply to both Ethernet port and POS port settings, where the same setting exists for both. Note PPM (SFP) slots and ports are unassigned by default. You can optionally use the Defaults editor to change these defaults to automatically assign PPM slots to take a single-port PPM, and to automatically assign PPM port OC-N rates. However, use discretion in changing the default PPM port rate in cases where single-rate PPMs might be inserted in a card, since preprovisioned PPM port rates that are applied to a single-rate PPM of the wrong rate will result in a mismatch of equipment and software. Note For further information about the supported features of each individual card, see Chapter 3, “Card Reference.”For further information about the supported features of Ethernet cards, consult the Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide. C.5.2 Threshold Defaults Threshold default settings define the default cumulative values (thresholds) beyond which a TCA will be raised, making it possible to monitor the network and detect errors early. Card threshold default settings are provided as follows: • PM thresholds—(CTX2500, DS1-28/DS3-EC1-3, and DS1-84/DS3-EC1-3 cards) Applicable to DS-1, DS-3, EC-1, and OC-N ports. Can be expressed in counts or seconds; includes line, electrical, and SONET thresholds. • Physical Layer thresholds—(CTX2500 cards only) Applicable to OC-N ports. 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 PM thresholds, and TCA (warning) or Alarm (for physical thresholds). PM threshold types define the layer to which the threshold applies. Physical threshold types define the level of response expected when the threshold is crossed. Note For full descriptions of the thresholds you can set for each card, see Chapter 12, “Performance Monitoring.” Note For additional information regarding PM parameter threshold defaults as defined by Telcordia specifications, refer to Telcordia GR-820-CORE and GR-253-CORE. C.5.3 Defaults by Card In the tables that follow, card defaults are defined by the default name, its factory-configured value, and the domain of allowable values that you can assign to it.C-32 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card Note Some default values, such as certain thresholds, are interdependent. Before changing a value, review the domain for that default and any other related defaults for potential dependencies. CTX2500 Card Default Settings Table C-6 lists the CTX2500 card default settings. Table C-6 CTX2500 Card Default Settings Default Name Default Value Default Domain CTX-2500.OC12-PORT.config.line.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES CTX-2500.OC12-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX-2500.OC12-PORT.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test CTX-2500.OC12-PORT.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 CTX-2500.OC12-PORT.config.line.AlsRecoveryPulseInterval 100 (seconds) 60 - 300 CTX-2500.OC12-PORT.config.line.PJStsMon# 0 (STS #) 0 - 12 CTX-2500.OC12-PORT.config.line.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX-2500.OC12-PORT.config.line.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE CTX-2500.OC12-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX-2500.OC12-PORT.config.line.SendAISOnTerminalLoopback FALSE TRUE, FALSE CTX-2500.OC12-PORT.config.line.SendDoNotUse FALSE FALSE, TRUE CTX-2500.OC12-PORT.config.line.SFBER 1E-4 1E-3, 1E-4, 1E-5 CTX-2500.OC12-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX-2500.OC12-PORT.config.line.SyncMsgIn TRUE FALSE, TRUE CTX-2500.OC12-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE CTX-2500.OC12-PORT.physicalthresholds.alarm.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.alarm.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGHC-33 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC12-PORT.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.alarm.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC12-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC12-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC12-PORT.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.warning.15min.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC12-PORT.physicalthresholds.warning.15min.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.warning.15min.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC12-PORT.physicalthresholds.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.warning.1day.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC12-PORT.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC12-PORT.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC12-PORT.physicalthresholds.warning.1day.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC12-PORT.pmthresholds.line.farend.15min.CV 5315 (B2 count) 0 - 552600 CTX-2500.OC12-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 CTX-2500.OC12-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-34 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC12-PORT.pmthresholds.line.farend.1day.CV 53150 (B2 count) 0 - 53049600 CTX-2500.OC12-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.CV 5315 (B2 count) 0 - 552600 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.CV 53150 (B2 count) 0 - 53049600 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.PSC 5 (count) 0 - 57600 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.PSD 600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 553500 CTX-2500.OC12-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 53136000 CTX-2500.OC12-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-35 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.CV 75 (B3 count) 0 - 2160000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.ES 60 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.15min.UAS 10 (seconds) 0 - 900 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-36 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.CV 750 (B3 count) 0 - 207360000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.ES 600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts12c.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.CV 25 (B3 count) 0 - 2160000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.ES 20 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.ES 200 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-37 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.sts3c-9c.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX-2500.OC12-PORT.pmthresholds.vt.farend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.vt.farend.15min.FC 10 (count) 0 - 72 CTX-2500.OC12-PORT.pmthresholds.vt.farend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.vt.farend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.vt.farend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX-2500.OC12-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.vt.farend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC12-PORT.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC3-PORT.config.line.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES CTX-2500.OC3-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX-2500.OC3-PORT.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-38 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC3-PORT.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 CTX-2500.OC3-PORT.config.line.AlsRecoveryPulseInterval 100 (seconds) 60 - 300 CTX-2500.OC3-PORT.config.line.PJStsMon# 0 (STS #) 0 - 3 CTX-2500.OC3-PORT.config.line.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX-2500.OC3-PORT.config.line.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE CTX-2500.OC3-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX-2500.OC3-PORT.config.line.SendAISOnTerminalLoopback FALSE TRUE, FALSE CTX-2500.OC3-PORT.config.line.SendDoNotUse FALSE FALSE, TRUE CTX-2500.OC3-PORT.config.line.SFBER 1E-4 1E-3, 1E-4, 1E-5 CTX-2500.OC3-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX-2500.OC3-PORT.config.line.SyncMsgIn TRUE FALSE, TRUE CTX-2500.OC3-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE CTX-2500.OC3-PORT.physicalthresholds.alarm.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.alarm.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC3-PORT.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.alarm.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC3-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC3-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC3-PORT.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-39 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC3-PORT.physicalthresholds.warning.15min.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC3-PORT.physicalthresholds.warning.15min.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.warning.15min.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC3-PORT.physicalthresholds.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.warning.1day.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC3-PORT.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC3-PORT.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC3-PORT.physicalthresholds.warning.1day.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC3-PORT.pmthresholds.line.farend.15min.CV 1312 (B2 count) 0 - 137700 CTX-2500.OC3-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 CTX-2500.OC3-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 13219200 CTX-2500.OC3-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC3-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-40 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.PSC 5 (count) 0 - 57600 CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.PSD 600 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 138600 CTX-2500.OC3-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 13305600 CTX-2500.OC3-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-41 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.CV 25 (B3 count) 0 - 2160000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.ES 20 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.CV 250 (B3 count) 0 - 207360000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.ES 200 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.sts3c.nearend.1day.UAS 10 (seconds) 0 - 86400 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-42 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC3-PORT.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX-2500.OC3-PORT.pmthresholds.vt.farend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.vt.farend.15min.FC 10 (count) 0 - 72 CTX-2500.OC3-PORT.pmthresholds.vt.farend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.vt.farend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.vt.farend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX-2500.OC3-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.vt.farend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC3-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC3-PORT.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.config.line.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES CTX-2500.OC48-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 CTX-2500.OC48-PORT.config.line.AlsMode Disabled Disabled, Auto Restart, Manual Restart, Manual Restart for Test CTX-2500.OC48-PORT.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 CTX-2500.OC48-PORT.config.line.AlsRecoveryPulseInterval 100 (seconds) 60 - 300 CTX-2500.OC48-PORT.config.line.PJStsMon# 0 (STS #) 0 - 48 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-43 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC48-PORT.config.line.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 CTX-2500.OC48-PORT.config.line.SendDoNotUse FALSE FALSE when SendDoNotUse TRUE; FALSE, TRUE when SendDoNotUse FALSE CTX-2500.OC48-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE CTX-2500.OC48-PORT.config.line.SendAISOnTerminalLoopback FALSE TRUE, FALSE CTX-2500.OC48-PORT.config.line.SendDoNotUse FALSE FALSE, TRUE CTX-2500.OC48-PORT.config.line.SFBER 1E-4 1E-3, 1E-4, 1E-5 CTX-2500.OC48-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS CTX-2500.OC48-PORT.config.line.SyncMsgIn TRUE FALSE, TRUE CTX-2500.OC48-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE CTX-2500.OC48-PORT.physicalthresholds.alarm.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.alarm.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC48-PORT.physicalthresholds.alarm.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.alarm.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC48-PORT.physicalthresholds.alarm.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.alarm.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC48-PORT.physicalthresholds.warning.15min.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.warning.15min.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC48-PORT.physicalthresholds.warning.15min.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.warning.15min.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC48-PORT.physicalthresholds.warning.15min.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.warning.15min.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-44 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC48-PORT.physicalthresholds.warning.1day.LBC-HIGH 200 (%) LBC-LOW, LBC-LOW + 1.0, LBC-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.warning.1day.LBC-LOW 20 (%) 0.0, 1.0, 2.0 .. LBC-HIGH CTX-2500.OC48-PORT.physicalthresholds.warning.1day.OPR-HIGH 200 (%) OPR-LOW, OPR-LOW + 1.0, OPR-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.warning.1day.OPR-LOW 50 (%) -1.0, 0.0, 1.0 .. OPR-HIGH CTX-2500.OC48-PORT.physicalthresholds.warning.1day.OPT-HIGH 120 (%) OPT-LOW, OPT-LOW + 1.0, OPT-LOW + 2.0 .. 255.0 CTX-2500.OC48-PORT.physicalthresholds.warning.1day.OPT-LOW 80 (%) 0.0, 1.0, 2.0 .. OPT-HIGH CTX-2500.OC48-PORT.pmthresholds.line.farend.15min.CV 21260 (B2 count) 0 - 2212200 CTX-2500.OC48-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.farend.1day.CV 212600 (B2 count) 0 - 212371200 CTX-2500.OC48-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.CV 21260 (B2 count) 0 - 2212200 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.PSC 1 (count) 0 - 600 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.PSD 300 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.CV 212600 (B2 count) 0 - 212371200 CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.PSC 5 (count) 0 - 57600 CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.PSD 600 (seconds) 0 - 86400 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-45 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 2151900 CTX-2500.OC48-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 206582400 CTX-2500.OC48-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-46 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.CV 75 (B3 count) 0 - 2160000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.ES 60 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.CV 750 (B3 count) 0 - 207360000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.ES 600 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts12c-48c.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.CV 25 (B3 count) 0 - 2160000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.ES 20 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-47 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.CV 250 (B3 count) 0 - 207360000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.ES 200 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.sts3c-9c.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX-2500.OC48-PORT.pmthresholds.vt.farend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.vt.farend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.vt.farend.15min.SES 3 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.vt.farend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.vt.farend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX-2500.OC48-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.vt.farend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.15min.CV 15 (BIP8 count) 0 - 2160000 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.15min.ES 12 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.15min.FC 10 (count) 0 - 72 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.15min.SES 3 (seconds) 0 - 900 Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default DomainC-48 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28/DS3-EC1-3 Card Default Settings Table C-7 lists the DS1-28/DS3-EC1-3 card default settings. CTX-2500.OC48-PORT.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.1day.FC 40 (count) 0 - 6912 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 CTX-2500.OC48-PORT.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 CTX-2500.PPM.portAssignment UNASSIGNE D UNASSIGNED, OC3-PORT, OC12-PORT, OC48-PORT CTX-2500.PPM.slotAssignment UNASSIGNE D UNASSIGNED, PPM (1 Port) Table C-6 CTX2500 Card Default Settings (continued) Default Name Default Value Default Domain Table C-7 DS1-28/DS3-EC1-3 Card Default Settings Default Name Default Value Default Domain DS1-28-DS3-EC1-3.Broadband.portAssignment DS3-PORT UNASSIGNED, DS3-PORT, EC1-PORT DS1-28-DS3-EC1-3.DS1-PORT.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS1-28-DS3-EC1-3.DS1-PORT.config.LineCoding AMI B8ZS, AMI DS1-28-DS3-EC1-3.DS1-PORT.config.LineLength 0 - 131 ft 0 - 131 ft, 132 - 262 ft, 263 - 393 ft, 394 - 524 ft, 525 - 655 ft DS1-28-DS3-EC1-3.DS1-PORT.config.LineType AUTO FRAME ESF, D4, UNFRAMED, AUTO FRAME DS1-28-DS3-EC1-3.DS1-PORT.config.RetimingEnabled FALSE TRUE, FALSE DS1-28-DS3-EC1-3.DS1-PORT.config.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS1-28-DS3-EC1-3.DS1-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS1-28-DS3-EC1-3.DS1-PORT.config.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS1-28-DS3-EC1-3.DS1-PORT.config.SendAISVOnDefects FALSE FALSE, TRUE DS1-28-DS3-EC1-3.DS1-PORT.config.SendDoNotUse FALSE TRUE, FALSE DS1-28-DS3-EC1-3.DS1-PORT.config.SFBER 1E-4 1E-3, 1E-4, 1E-5C-49 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.DS1-PORT.config.State OOS,DSBLD OOS,DSBLD when LineType AUTO FRAME; IS, OOS,DSBLD, OOS,MT, IS,AINS when LineType ESF, D4, UNFRAMED DS1-28-DS3-EC1-3.DS1-PORT.config.SyncMsgIn FALSE FALSE when LineType D4, E1_MF, E1_CRCMF, UNFRAMED, AUTO FRAME; FALSE, TRUE when LineType ESF, J_ESF DS1-28-DS3-EC1-3.DS1-PORT.config.TreatLOFAsDefect TRUE FALSE, TRUE DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.ESFE 65 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.ESNE 65 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.SESFE 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.SESNE 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.UASFE 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.UASNE 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.ESFE 648 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.ESNE 648 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.SESFE 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.SESNE 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.UASFE 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.UASNE 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.farend.15min.ES 65 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.farend.1day.ES 648 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.CV 13340 (BPV count) 0 - 1388700 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.ES 65 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.SES 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.CV 133400 (BPV count) 0 - 133315200 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.ES 648 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.SES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.CSS 25 (seconds) 0 - 900 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-50 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.CV 13296 (BIP count) 0 - 287100 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.ES 65 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.ESA 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.ESB 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.FC 10 (count) 0 - 90 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.SEFS 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.SES 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.CSS 25 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.CV 132960 (BIP count) 0 - 27561600 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.ES 648 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.ESA 25 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.ESB 25 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.FC 40 (count) 0 - 8640 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.SEFS 25 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.SES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.AISS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.CV 13296 (BIP count) 0 - 287100 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.ES 65 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.FC 10 (count) 0 - 90 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.SAS 2 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.SES 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.AISS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.CV 132960 (BIP count) 0 - 27561600 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.ES 648 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.FC 40 (count) 0 - 8640 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.SAS 17 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.SES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.CV 15 (B3 count) 0 - 2160000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.ES 12 (seconds) 0 - 900 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-51 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.CV 125 (B3 count) 0 - 207360000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.FC 40 (count) 0 - 6912 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.ES 12 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.CV 125 (BIP8 count) 0 - 207360000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.CV 15 (BIP8 count) 0 - 2160000 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.ES 12 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-52 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.FC 40 (count) 0 - 72 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS1-28-DS3-EC1-3.DS3-PORT.config.FeInhibitLpbk FALSE TRUE, FALSE DS1-28-DS3-EC1-3.DS3-PORT.config.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft DS1-28-DS3-EC1-3.DS3-PORT.config.LineType M13 UNFRAMED, M13, C BIT DS1-28-DS3-EC1-3.DS3-PORT.config.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS1-28-DS3-EC1-3.DS3-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS1-28-DS3-EC1-3.DS3-PORT.config.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS1-28-DS3-EC1-3.DS3-PORT.config.SFBER 1E-4 1E-3, 1E-4, 1E-5 DS1-28-DS3-EC1-3.DS3-PORT.config.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.CV 382 (BIP count) 0 - 287100 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.ES 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.SAS 2 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.SES 4 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.CV 3820 (BIP count) 0 - 27561600 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.ES 250 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.SAS 8 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.SES 40 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.CV 382 (BIP count) 0 - 287100 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.ES 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.SES 4 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.CV 3820 (BIP count) 0 - 27561600 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.ES 250 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.SES 40 (seconds) 0 - 86400 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-53 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.CV 387 (BPV count) 0 - 38700 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.ES 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.SES 4 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.CV 3865 (BPV count) 0 - 3715200 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.ES 250 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.SES 40 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.AISS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.CV 382 (BIP count) 0 - 287100 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.ES 25 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.SAS 2 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.SES 4 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.AISS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.CV 3820 (BIP count) 0 - 27561600 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.ES 250 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.SAS 8 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.SES 40 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.CV 15 (G1 count) 0 - 2160000 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.ES 12 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.CV 125 (G1 count) 0 - 207360000 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.FC 40 (count) 0 - 6912 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-54 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS1-28-DS3-EC1-3.EC1-PORT.config.line.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft DS1-28-DS3-EC1-3.EC1-PORT.config.line.PJStsMon# 0 (STS #) 0 - 1 DS1-28-DS3-EC1-3.EC1-PORT.config.line.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS1-28-DS3-EC1-3.EC1-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS1-28-DS3-EC1-3.EC1-PORT.config.line.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS1-28-DS3-EC1-3.EC1-PORT.config.line.SFBER 1E-4 1E-3, 1E-4, 1E-5 DS1-28-DS3-EC1-3.EC1-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS DS1-28-DS3-EC1-3.EC1-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.CV 1312 (B2 count) 0 - 137700 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 8850600 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 72 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-55 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 138600 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 13305600 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-56 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84/DS3-EC1-3 Card Default Settings Table C-8 lists the DS1-84/DS3-EC1-3 card default settings. DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-28-DS3-EC1-3.Wideband.portAssignment DS1-PORT DS1-PORT Table C-7 DS1-28/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default Domain Table C-8 DS1-84/DS3-EC1-3 Card Default Settings Default Name Default Value Default Domain DS1-84-DS3-EC1-3.Broadband.portAssignment DS3-PORT UNASSIGNED, DS3-PORT, EC1-PORT DS1-84-DS3-EC1-3.DS1-PORT.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS1-84-DS3-EC1-3.DS1-PORT.config.LineCoding AMI B8ZS, AMI DS1-84-DS3-EC1-3.DS1-PORT.config.LineLength 0 - 131 ft 0 - 131 ft, 132 - 262 ft, 263 - 393 ft, 394 - 524 ft, 525 - 655 ft DS1-84-DS3-EC1-3.DS1-PORT.config.LineType AUTO FRAME ESF, D4, UNFRAMED, AUTO FRAME DS1-84-DS3-EC1-3.DS1-PORT.config.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS1-84-DS3-EC1-3.DS1-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS1-84-DS3-EC1-3.DS1-PORT.config.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS1-84-DS3-EC1-3.DS1-PORT.config.SendAISVOnDefects FALSE FALSE, TRUE DS1-84-DS3-EC1-3.DS1-PORT.config.SendDoNotUse FALSE TRUE, FALSE DS1-84-DS3-EC1-3.DS1-PORT.config.SFBER 1E-4 1E-3, 1E-4, 1E-5C-57 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.DS1-PORT.config.State OOS,DSBLD OOS,DSBLD when LineType AUTO FRAME; IS, OOS,DSBLD, OOS,MT, IS,AINS when LineType ESF, D4, UNFRAMED DS1-84-DS3-EC1-3.DS1-PORT.config.SyncMsgIn FALSE FALSE when LineType D4, E1_MF, E1_CRCMF, UNFRAMED, AUTO FRAME; FALSE, TRUE when LineType ESF, J_ESF DS1-84-DS3-EC1-3.DS1-PORT.config.TreatLOFAsDefect TRUE FALSE, TRUE DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.ESFE 65 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.ESNE 65 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.SESFE 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.SESNE 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.UASFE 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.15min.UASNE 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.ESFE 648 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.ESNE 648 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.SESFE 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.SESNE 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.UASFE 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.ds1network.farend.1day.UASNE 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.farend.15min.ES 65 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.farend.1day.ES 648 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.CV 13340 (BPV count) 0 - 1388700 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.ES 65 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.15min.SES 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.CV 133400 (BPV count) 0 - 133315200 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.ES 648 (seconds) 0 - 86400 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-58 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.line.nearend.1day.SES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.CSS 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.CV 13296 (BIP count) 0 - 287100 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.ES 65 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.ESA 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.ESB 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.FC 10 (count) 0 - 90 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.SEFS 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.SES 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.CSS 25 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.CV 132960 (BIP count) 0 - 27561600 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.ES 648 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.ESA 25 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.ESB 25 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.FC 40 (count) 0 - 8640 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.SEFS 25 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.SES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.AISS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.CV 13296 (BIP count) 0 - 287100 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.ES 65 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.FC 10 (count) 0 - 90 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.SAS 2 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.SES 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.AISS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.CV 132960 (BIP count) 0 - 27561600 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.ES 648 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.FC 40 (count) 0 - 8640 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.SAS 17 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.SES 100 (seconds) 0 - 86400 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-59 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.path.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.CV 15 (B3 count) 0 - 2160000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.SES 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.CV 125 (B3 count) 0 - 207360000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.ES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.FC 40 (count) 0 - 6912 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.CV 15 (BIP8 count) 0 - 2160000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.SES 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.CV 125 (BIP8 count) 0 - 207360000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.ES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.CV 15 (BIP8 count) 0 - 2160000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.FC 10 (count) 0 - 72 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-60 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.SES 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.CV 125 (BIP8 count) 0 - 207360000 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.FC 40 (count) 0 - 72 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS1-PORT.pmthresholds.vt.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.config.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS1-84-DS3-EC1-3.DS3-PORT.config.FeInhibitLpbk FALSE TRUE, FALSE DS1-84-DS3-EC1-3.DS3-PORT.config.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft DS1-84-DS3-EC1-3.DS3-PORT.config.LineType M13 UNFRAMED, M13, C BIT DS1-84-DS3-EC1-3.DS3-PORT.config.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS1-84-DS3-EC1-3.DS3-PORT.config.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS1-84-DS3-EC1-3.DS3-PORT.config.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS1-84-DS3-EC1-3.DS3-PORT.config.SFBER 1E-4 1E-3, 1E-4, 1E-5 DS1-84-DS3-EC1-3.DS3-PORT.config.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.CV 382 (BIP count) 0 - 287100 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.ES 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.SAS 2 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.SES 4 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.CV 3820 (BIP count) 0 - 27561600 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.ES 250 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.SAS 8 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.SES 40 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.CV 382 (BIP count) 0 - 287100 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.ES 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.SES 4 (seconds) 0 - 900 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-61 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.CV 3820 (BIP count) 0 - 27561600 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.ES 250 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.SES 40 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.cpbitpath.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.CV 387 (BPV count) 0 - 38700 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.ES 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.LOSS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.15min.SES 4 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.CV 3865 (BPV count) 0 - 3715200 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.ES 250 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.LOSS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.line.nearend.1day.SES 40 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.AISS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.CV 382 (BIP count) 0 - 287100 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.ES 25 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.SAS 2 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.SES 4 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.AISS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.CV 3820 (BIP count) 0 - 27561600 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.ES 250 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.SAS 8 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.SES 40 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.pbitpath.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.CV 15 (G1 count) 0 - 2160000 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.SES 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.CV 125 (G1 count) 0 - 207360000 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.ES 100 (seconds) 0 - 86400 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-62 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.FC 40 (count) 0 - 6912 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.CV 15 (B3 count) 0 - 2160000 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.SES 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.FC 40 (count) 0 - 6912 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.DS3-PORT.pmthresholds.sts.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.config.line.AINSSoakTime 08:00 (hours:mins) 00:00, 00:15, 00:30 .. 48:00 DS1-84-DS3-EC1-3.EC1-PORT.config.line.LineLength 0 - 225 ft 0 - 225 ft, 226 - 450 ft DS1-84-DS3-EC1-3.EC1-PORT.config.line.PJStsMon# 0 (STS #) 0 - 1 DS1-84-DS3-EC1-3.EC1-PORT.config.line.SDBER 1E-7 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 DS1-84-DS3-EC1-3.EC1-PORT.config.line.SendAISOnFacilityLoopback TRUE TRUE, FALSE DS1-84-DS3-EC1-3.EC1-PORT.config.line.SendAISOnTerminalLoopback FALSE TRUE, FALSE DS1-84-DS3-EC1-3.EC1-PORT.config.line.SFBER 1E-4 1E-3, 1E-4, 1E-5 DS1-84-DS3-EC1-3.EC1-PORT.config.line.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS DS1-84-DS3-EC1-3.EC1-PORT.config.sts.IPPMEnabled FALSE TRUE, FALSE DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.CV 1312 (B2 count) 0 - 137700 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.ES 87 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.SES 1 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.15min.UAS 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.CV 13120 (B2 count) 0 - 8850600 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.ES 864 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.FC 40 (count) 0 - 72 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-63 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.5.3 Defaults by Card DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.SES 4 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.farend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.CV 1312 (B2 count) 0 - 137700 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.ES 87 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.SES 1 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.15min.UAS 3 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.CV 13120 (B2 count) 0 - 13219200 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.ES 864 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.FC 40 (count) 0 - 6912 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.SES 4 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.line.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.CV 10000 (B1 count) 0 - 138600 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.ES 500 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.SEFS 500 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.15min.SES 500 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.CV 100000 (B1 count) 0 - 13305600 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.ES 5000 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.SEFS 5000 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.section.nearend.1day.SES 5000 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.CV 15 (B3 count) 0 - 2160000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.ES 12 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.FC 10 (count) 0 - 72 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PDET 60 (count) 0 - 7200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.NPJC-PGEN 60 (count) 0 - 7200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCDIFF 60 (count) 0 - 14400000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCS-PDET 100 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PJCS-PGEN 100 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PPJC-PDET 60 (count) 0 - 7200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.PPJC-PGEN 60 (count) 0 - 7200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.SES 3 (seconds) 0 - 900 Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-64 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings C.5.3.1 Ethernet Card Default Settings Refer to Table C-2 for the CE-100T-8 and ML-100T-8 card default settings. C.6 Cisco ONS 15310-MA Node Default Settings Table C-9 on page C-65 lists the node-level default settings for the Cisco ONS 15310-MA. Cisco provides the following types of node-level user-configurable defaults: • Circuit settings—Set the administrative state and path protection circuit defaults. • General settings—Set general node management defaults, including whether to use DST, whether to insert AIS-V in each VT when the carrying STS crosses the SD path BER threshold, the IP address of the NTP/SNTP server to be used, the time zone where the node is located, the SD path BER value, the defaults description, whether to raise a condition on an empty card slot, and whether to report loopback conditions on ports with an OOS-MT service state. • Network settings—Set whether to prevent the display of node IP addresses in CTC (applicable for all users except Superusers), default gateway node type, and whether to raise an alarm when the backplane LAN cable is disconnected. • OSI settings—Set OSI main setup, GRE tunnel, LAP-D, router subnet, and TARP settings. • 1+1 and Optimized 1+1 protection settings—Set whether or not protected circuits have bidirectional switching, are revertive, and what the reversion time is; set optimized 1+1 detection, recovery, and verify guard timer values. DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.15min.UAS 10 (seconds) 0 - 900 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.CV 125 (B3 count) 0 - 207360000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.ES 100 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.FC 40 (count) 0 - 6912 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.NPJC-PDET 5760 (count) 0 - 691200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.NPJC-PGEN 5760 (count) 0 - 691200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCDIFF 5760 (count) 0 - 1382400000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCS-PDET 9600 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PJCS-PGEN 9600 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PPJC-PDET 5760 (count) 0 - 691200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.PPJC-PGEN 5760 (count) 0 - 691200000 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.SES 7 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.EC1-PORT.pmthresholds.sts1.nearend.1day.UAS 10 (seconds) 0 - 86400 DS1-84-DS3-EC1-3.Wideband.portAssignment DS1-PORT DS1-PORT Table C-8 DS1-84/DS3-EC1-3 Card Default Settings (continued) Default Name Default Value Default DomainC-65 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings Note Optimized 1+1 supports three timers that ensure the correct state of the cards at key points in card communication. A verification guard timer is used when a Force is issued, to ensure that the far end has a chance to respond. A detection guard timer is used to ensure the presence of an SF/SD condition before switching away from a card. A recover guard timer ensures the absence of SF/SD prior to switching to a card. You can change the default number of seconds before these timers expire by changing the NE default for the corresponding timer to a value within its domain of allowable values. • Legal Disclaimer—Set the legal disclaimer that warns users at the login screen about the possible legal or contractual ramifications of accessing equipment, systems, or networks without authorization. • Security Access settings—Set default security settings for LAN access, shell access, serial craft access, EMS access (including IIOP listener port number), TL1 access, and SNMP access. • Security Grant Permissions—Set default user security levels for activating/reverting software, PMC learning, database restoring, and retrieving audit logs. • Security RADIUS settings—Sets default RADIUS server settings for accounting port number, authentication port number, and whether to enable the node as a final authenticator. • Security Policy settings—Set the allowable failed logins before lockout, idle user timeout for each user level, optional lockout duration or manual unlock enabled, password reuse and change frequency policies, number of characters difference between the old and new password, password aging by security level, enforced single concurrent session per user, and option to disable inactive user after a set inactivity period. • BITS Timing settings—Set the AIS threshold, coding, framing, State, State Out, and LBO settings for BITS-1 and BITS-2 timing. • General Timing settings—Set the mode (External, Line, or Mixed), quality of reserved (RES) timing (set the rule that defines the order of clock quality from lowest to highest), revertive, reversion time, and SSM message set for node timing. Note For more information about each individual node setting, refer to the “Change Node Settings” chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. Note For Cisco ONS 15310-MA CTC level default settings refer to the “C.4 CTC Default Settings” section on page C-29. Table C-9 ONS 15310-MA Node Default Settings Default Name Default Value Default Domain NODE.circuits.State IS,AINS IS, OOS,DSBLD, OOS,MT, IS,AINS NODE.circuits.upsr.ReversionTime 5.0 (minutes) 0.5, 1.0, 1.5 .. 12.0 NODE.circuits.upsr.Revertive FALSE TRUE, FALSEC-66 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings NODE.circuits.upsr.STS_SDBER 1E-6 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 NODE.circuits.upsr.STS_SFBER 1E-4 1E-3, 1E-4, 1E-5 NODE.circuits.upsr.SwitchOnPDIP FALSE TRUE, FALSE NODE.circuits.upsr.VT_SDBER 1E-6 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 NODE.circuits.upsr.VT_SFBER 1E-4 1E-3, 1E-4, 1E-5 NODE.general.DefaultsDescription Factory Defaults Free form field NODE.general.InsertAISVOnSDP FALSE TRUE, FALSE NODE.general.NtpSntpServer 10.92.18.1 IP Address NODE.general.RaiseConditionOnEmptySlot FALSE TRUE, FALSE NODE.general.ReportLoopbackConditionsOnOOS-MTPorts FALSE FALSE, TRUE NODE.general.SDPBER 1E-6 1E-5, 1E-6, 1E-7, 1E-8, 1E-9 NODE.general.TimeZone (GMT-08:00) Pacific Time (US & Canada), Tijuana (For applicable time zones, see Table C-4 on page C-26.) NODE.general.UseDST TRUE TRUE, FALSE NODE.network.general.AlarmMissingBackplaneLAN FALSE TRUE, FALSE NODE.network.general.CtcIpDisplaySuppression FALSE TRUE, FALSE NODE.network.general.GatewaySettings None None, ENE, GNE, ProxyOnlyNode NODE.osi.greTunnel.OspfCost 110 110, 111, 112 .. 65535 NODE.osi.greTunnel.SubnetMask 24 (bits) 8, 9, 10 .. 32 NODE.osi.lapd.Mode AITS AITS, UITS NODE.osi.lapd.MTU 512 512, 513, 514 .. 1500 NODE.osi.lapd.Role Network Network, User NODE.osi.lapd.T200 200 (ms) 200, 300, 400 .. 20000 NODE.osi.lapd.T203 10000 (ms) 4000, 4100, 4200 .. 120000 NODE.osi.mainSetup.L1LSPBufferSize 512 (bytes) 512 - 1500 Table C-9 ONS 15310-MA Node Default Settings (continued) Default Name Default Value Default DomainC-67 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings NODE.osi.mainSetup.NodeRoutingMode End System End System, Intermediate System Level 1 NODE.osi.subnet.DISPriority 63 1, 2, 3 .. 127 NODE.osi.subnet.ESH 10 (sec) 10, 20, 30 .. 1000 NODE.osi.subnet.IIH 3 (sec) 1, 2, 3 .. 600 NODE.osi.subnet.ISH 10 (sec) 10, 20, 30 .. 1000 NODE.osi.subnet.LANISISCost 20 1, 2, 3 .. 63 NODE.osi.subnet.LDCCISISCost 40 1, 2, 3 .. 63 NODE.osi.subnet.SDCCISISCost 60 1, 2, 3 .. 63 NODE.osi.tarp.L1DataCache TRUE FALSE, TRUE NODE.osi.tarp.LANStormSuppression TRUE FALSE, TRUE NODE.osi.tarp.LDB TRUE FALSE, TRUE NODE.osi.tarp.LDBEntry 5 (min) 1 - 10 NODE.osi.tarp.LDBFlush 5 (min) 0 - 1440 NODE.osi.tarp.PDUsL1Propagation 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.T4Timer 20 (sec) 0 - 3600 NODE.osi.tarp.Type4PDUDelay 0 (sec) 0 - 255 NODE.protection.1+1.BidirectionalSwitching FALSE TRUE, FALSE NODE.protection.1+1.DetectionGuardTimer 1 (seconds) 0, 0.05, 0.1, 0.5, 1, 2, 3, 4, 5 NODE.protection.1+1.RecoveryGuardTimer 1 (seconds) 0, 0.05, 0.1 .. 10 NODE.protection.1+1.ReversionTime 5.0 (minutes) 0.5, 1.0, 1.5 .. 12.0 NODE.protection.1+1.Revertive FALSE TRUE, FALSE NODE.protection.1+1.VerifyGuardTimer 0.5 (seconds) 0.5, 1 NODE.security.emsAccess.AccessState NonSecure NonSecure, Secure NODE.security.emsAccess.IIOPListenerPort (May reboot node) 57790 (port #) 0 - 65535 NODE.security.grantPermission.ActivateRevertSoftware Superuser Provisioning, Superuser NODE.security.grantPermission.PMClearingPrivilege Provisioning Provisioning, Superuser Table C-9 ONS 15310-MA Node Default Settings (continued) Default Name Default Value Default DomainC-68 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings NODE.security.grantPermission.RestoreDB Superuser Provisioning, Superuser NODE.security.grantPermission.RetrieveAuditLog Superuser Provisioning, Superuser NODE.security.idleUserTimeout.Maintenance 01:00 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.idleUserTimeout.Provisioning 00:30 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.idleUserTimeout.Retrieve 00:00 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.idleUserTimeout.Superuser 00:15 (hours:mins) 00:00, 00:01, 00:02 .. 16:39 NODE.security.lanAccess.LANAccess (May disconnect CTC from node) Front & Backplane No LAN Access, Backplane Only, Front Only, Front & Backplane NODE.security.lanAccess.RestoreTimeout 5 (minutes) 0 - 60 NODE.security.legalDisclaimer.LoginWarningMessage WARNI NGThis system is restricted to authorized users for business purposes. Unauthorized

access is a violation of the law. This service may be monitored for administrative

and security reasons. By proceeding, you consent to this monitoring. Free form field NODE.security.other.DisableInactiveUser FALSE FALSE, TRUE Table C-9 ONS 15310-MA Node Default Settings (continued) Default Name Default Value Default DomainC-69 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings NODE.security.other.InactiveDuration 45 (days) 1, 2, 3 .. 99 when DisableInactiveU ser TRUE; 45 when DisableInactiveU ser FALSE NODE.security.other.SingleSessionPerUser FALSE TRUE, FALSE NODE.security.passwordAging.EnforcePasswordAging FALSE TRUE, FALSE NODE.security.passwordAging.maintenance.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.maintenance.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordAging.provisioning.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.provisioning.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordAging.retrieve.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.retrieve.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordAging.superuser.AgingPeriod 45 (days) 20 - 90 NODE.security.passwordAging.superuser.WarningPeriod 5 (days) 2 - 20 NODE.security.passwordChange.CannotChangeNewPassword FALSE TRUE, FALSE NODE.security.passwordChange.CannotChangeNewPasswordForNDays 20 (days) 20 - 95 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.radiusServer.AccountingPort 1813 (port) 0 - 32767 NODE.security.radiusServer.AuthenticationPort 1812 (port) 0 - 32767 NODE.security.radiusServer.EnableNodeAsFinalAuthenticator TRUE FALSE, TRUE NODE.security.serialCraftAccess.EnableCraftPort TRUE TRUE, FALSE NODE.security.shellAccess.AccessState NonSecure Disabled, NonSecure, Secure NODE.security.shellAccess.EnableShellPassword FALSE TRUE, FALSE NODE.security.shellAccess.TelnetPort 23 23 - 9999 NODE.security.snmpAccess.AccessState NonSecure Disabled, NonSecure NODE.security.tl1Access.AccessState NonSecure Disabled, NonSecure, Secure NODE.security.userLockout.FailedLoginsAllowedBeforeLockout 5 (times) 0 - 10 NODE.security.userLockout.LockoutDuration 00:30 (mins:secs) 00:00, 00:05, 00:10 .. 10:00 NODE.security.userLockout.ManualUnlockBySuperuser FALSE TRUE, FALSE Table C-9 ONS 15310-MA Node Default Settings (continued) Default Name Default Value Default DomainC-70 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings NODE.timing.bits-1.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES NODE.timing.bits-1.AISThreshold SMC PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES NODE.timing.bits-1.Coding B8ZS B8ZS, AMI NODE.timing.bits-1.Framing ESF ESF, D4 NODE.timing.bits-1.LBO 0-133 (ft) 0-133, 134-266, 267-399, 400-533, 534-655 NODE.timing.bits-1.State OOS,DSBLD IS, OOS,DSBLD NODE.timing.bits-1.StateOut IS IS, OOS,DSBLD NODE.timing.bits-2.AdminSSMIn STU PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES NODE.timing.bits-2.AISThreshold SMC PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, RES NODE.timing.bits-2.Coding B8ZS B8ZS, AMI NODE.timing.bits-2.Framing ESF ESF, D4 NODE.timing.bits-2.LBO 0-133 (ft) 0-133, 134-266, 267-399, 400-533, 534-655 NODE.timing.bits-2.State OOS,DSBLD IS, OOS,DSBLD NODE.timing.bits-2.StateOut IS IS, OOS,DSBLD NODE.timing.general.Mode Line External, Line, Mixed Table C-9 ONS 15310-MA Node Default Settings (continued) Default Name Default Value Default DomainC-71 Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. R7.0 Appendix C Network Element Defaults C.6 Cisco ONS 15310-MA Node Default Settings NODE.timing.general.QualityOfRES RES=DUS PRS Command parameters that must be replaced by module-specific codes.lxv Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Preface Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071 SAVE THESE INSTRUCTIONS Waarschuwing BELANGRIJKE VEILIGHEIDSINSTRUCTIES Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van de standaard praktijken om ongelukken te voorkomen. Gebruik het nummer van de verklaring onderaan de waarschuwing als u een vertaling van de waarschuwing die bij het apparaat wordt geleverd, wilt raadplegen. BEWAAR DEZE INSTRUCTIES Varoitus TÄRKEITÄ TURVALLISUUSOHJEITA Tämä varoitusmerkki merkitsee vaaraa. Tilanne voi aiheuttaa ruumiillisia vammoja. Ennen kuin käsittelet laitteistoa, huomioi sähköpiirien käsittelemiseen liittyvät riskit ja tutustu onnettomuuksien yleisiin ehkäisytapoihin. Turvallisuusvaroitusten käännökset löytyvät laitteen mukana toimitettujen käännettyjen turvallisuusvaroitusten joukosta varoitusten lopussa näkyvien lausuntonumeroiden avulla. SÄILYTÄ NÄMÄ OHJEET 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. Pour prendre connaissance des traductions des avertissements figurant dans les consignes de sécurité traduites qui accompagnent cet appareil, référez-vous au numéro de l'instruction situé à la fin de chaque avertissement. CONSERVEZ CES INFORMATIONS Warnung WICHTIGE SICHERHEITSHINWEISE Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu Verletzungen führen kann. Machen Sie sich vor der Arbeit mit Geräten mit den Gefahren elektrischer Schaltungen und den üblichen Verfahren zur Vorbeugung vor Unfällen vertraut. Suchen Sie mit der am Ende jeder Warnung angegebenen Anweisungsnummer nach der jeweiligen Übersetzung in den übersetzten Sicherheitshinweisen, die zusammen mit diesem Gerät ausgeliefert wurden. BEWAHREN SIE DIESE HINWEISE GUT AUF.lxvi Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Preface Avvertenza IMPORTANTI ISTRUZIONI SULLA SICUREZZA Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti. Utilizzare il numero di istruzione presente alla fine di ciascuna avvertenza per individuare le traduzioni delle avvertenze riportate in questo documento. CONSERVARE QUESTE ISTRUZIONI Advarsel VIKTIGE SIKKERHETSINSTRUKSJONER Dette advarselssymbolet betyr fare. Du er i en situasjon som kan føre til skade på person. Før du begynner å arbeide med noe av utstyret, må du være oppmerksom på farene forbundet med elektriske kretser, og kjenne til standardprosedyrer for å forhindre ulykker. Bruk nummeret i slutten av hver advarsel for å finne oversettelsen i de oversatte sikkerhetsadvarslene som fulgte med denne enheten. TA VARE PÅ DISSE INSTRUKSJONENE Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA Este símbolo de aviso significa perigo. Você está em uma situação que poderá ser causadora de lesões corporais. Antes de iniciar a utilização de qualquer equipamento, tenha conhecimento dos perigos envolvidos no manuseio de circuitos elétricos e familiarize-se com as práticas habituais de prevenção de acidentes. Utilize o número da instrução fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham este dispositivo. GUARDE ESTAS INSTRUÇÕES ¡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. GUARDE ESTAS INSTRUCCIONES Varning! VIKTIGA SÄKERHETSANVISNINGAR Denna varningssignal signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanliga förfaranden för att förebygga olyckor. Använd det nummer som finns i slutet av varje varning för att hitta dess översättning i de översatta säkerhetsvarningar som medföljer denna anordning. SPARA DESSA ANVISNINGARlxvii Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Prefacelxviii Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Preface 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. GUARDE ESTAS INSTRUÇÕES Advarsel VIGTIGE SIKKERHEDSANVISNINGER Dette advarselssymbol betyder fare. Du befinder dig i en situation med risiko for legemesbeskadigelse. Før du begynder arbejde på udstyr, skal du være opmærksom på de involverede risici, der er ved elektriske kredsløb, og du skal sætte dig ind i standardprocedurer til undgåelse af ulykker. Brug erklæringsnummeret efter hver advarsel for at finde oversættelsen i de oversatte advarsler, der fulgte med denne enhed. GEM DISSE ANVISNINGERlxix Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Prefacelxx Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Preface 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. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation. Cisco Optical Networking Product Documentation CD-ROM Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation. 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.html Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.CHAPTER 1-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 1 Cisco ONS 15454 (ANSI and ETSI), ONS 15454 M2, and ONS 15454 M6 Shelf Assembly For information on the Cisco ONS 15454 (ANSI and ETSI), ONS 15454 M2, and ONS 15454 M6 shelf assemblies, see the Cisco ONS 15454 Hardware Installation Guide.1-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 1 Cisco ONS 15454 (ANSI and ETSI), ONS 15454 M2, and ONS 15454 M6 Shelf AssemblyCHAPTER 2-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This chapter describes the Cisco ONS 15454 common-control cards. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise. Chapter topics include: • 2.1 Card Overview, page 2-2 • 2.3 TCC2 Card, page 2-3 • 2.4 TCC2P Card, page 2-8 • 2.5 TCC3 Card, page 2-12 • 2.6 TNC Card, page 2-16 • 2.7 TSC Card, page 2-25 • 2.8 Digital Image Signing, page 2-33 • 2.9 AIC-I Card, page 2-34 • 2.10 MS-ISC-100T Card, page 2-39 • 2.11 Front Mount Electrical Connections, page 2-422-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Card Overview 2.1 Card Overview The card overview section lists the cards described in this chapter. 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. For a list of slots and symbols, see the “Card Slot Requirements” section in the Cisco ONS 15454 Hardware Installation Guide. 2.1.1 Common Control Cards The following common control cards are needed to support the functions of the DWDM, transponder, and muxponder cards on ONS 15454 shelf: • TCC2 or TCC2P or TCC3 • AIC-I (optional) • MS-ISC-100T (multishelf configurations only) The TNC and TSC cards are used to support the functions of DWDM, transponder, and muxponder cards on the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 shelves. 2.1.2 Card Compatibility Table 2-1 lists the platform and software release compatibility for the control cards. Table 2-1 Platform and Software Release Compatibility for Control Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.2 TCC2 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454-DWDM TCC2P 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454-DWDM AIC-I 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454-DWDM MS-ISC-100T 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454-DWDM TCC3 No No No No No No No No No No No 15454-DWDM TNC No No No No No No No No No No No 15454-M2 and 15454-M6 TSC No No No No No No No No No No No 15454-M2 and 15454-M62-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Safety Labels 2.1.3 Front Mount Electrical Connections (ETSI only) The following Front Mount Electrical Connections (FMECs) are needed to support the functions of the DWDM, transponder, and muxponder cards: • MIC-A/P • MIC-C/T/P 2.2 Safety Labels This section explains the significance of the safety labels attached to some of the cards. The faceplates of the cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. 2.2.1 Hazard Level 1 Label The Hazard Level 1 label is shown in Figure 2-1. Figure 2-1 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. This label is displayed on the faceplate of the cards. Warning Class 1 laser product. Statement 1008 2.3 TCC2 Card (Cisco ONS 15454 only) Note For TCC2 card specifications, see the “A.3.1 TCC2 Card Specifications” section on page A-4. The Advanced Timing, Communications, and Control (TCC2) card performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET section overhead (SOH) data communications channel/generic communications channel (DCC/GCC) HAZARD LEVEL 1 655422-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2 Card termination, optical service channel (OSC) DWDM data communications network (DCN) termination, and system fault detection for the ONS 15454. The TCC2 also ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing requirements. It monitors the supply voltage of the system. Note The LAN interface of the TCC2 card meets the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). Figure 2-2 shows the faceplate and block diagram for the TCC2. 2-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2 Card Figure 2-2 TCC2 Faceplate and Block Diagram 2.3.1 TCC2 Functionality The TCC2 card terminates up to 32 DCCs. The TCC2 hardware is prepared for up to 84 DCCs, which will be available in a future software release. FAIL A PWR B ACT/STBY ACO CRIT MIN REM SYNC RS-232 TCP/IP MAJ ACO TCC2 LAMP BACKPLANE Ethernet Repeater Mate TCC2 Ethernet Port Backplane Ethernet Port (Shared with Mate TCC2) SDRAM Memory & Compact Flash FPGA TCCA ASIC SCL Processor Serial Debug Modem Interface RS-232 Craft Interface Backplane RS-232 Port (Shared with Mate TCC2) Faceplate RS-232 Port Note: Only 1 RS-232 Port Can Be Active - Backplane Port Will Supercede Faceplate Port Faceplate Ethernet Port SCL Links to All Cards HDLC Message Bus Mate TCC2 HDLC Link Modem Interface (Not Used) 400MHz Processor Communications Processor SCC3 MCC1 FCC1 MCC2 SCC4 FCC2 SCC1 SCC2 DCC Processor System Timing BITS Input/ Output Ref Clocks (all I/O Slots) -48V PWR Monitors Real Time Clock 1376392-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2 Card The node database, IP address, and system software are stored in TCC2 nonvolatile memory, which allows quick recovery in the event of a power or card failure. The TCC2 performs all system-timing functions for each ONS 15454. The TCC2 monitors the recovered clocks from each traffic card and two building integrated timing supply (BITS) ports for frequency accuracy. The TCC2 selects a recovered clock, a BITS, or an internal Stratum 3 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 TCC2 to synchronize with the recovered clock, which provides holdover if the reference is lost. The TCC2 monitors both supply voltage inputs on the shelf. An alarm is generated if one of the supply voltage inputs has a voltage out of the specified range. Install TCC2 cards in Slots 7 and 11 for redundancy. If the active TCC2 fails, traffic switches to the protect TCC2. The TCC2 card has two built-in interface ports for accessing the system: an RJ-45 10BaseT LAN interface and an EIA/TIA-232 ASCII interface for local craft access. It also has a 10BaseT LAN port for user interfaces via the backplane. 2.3.2 Redundant TCC2 Card Installation Cisco does not support operation of the ONS 15454 with only one TCC2 card. For full functionality and to safeguard your system, always operate with two TCC2 cards. When a second TCC2 card is inserted into a node, it synchronizes its software, its backup software, and its database with the active TCC2. If the software version of the new TCC2 does not match the version on the active TCC2, the newly inserted TCC2 copies from the active TCC2, taking about 15 to 20 minutes to complete. If the backup software version on the new TCC2 does not match the version on the active TCC2, the newly inserted TCC2 copies the backup software from the active TCC2 again, taking about 15 to 20 minutes. Copying the database from the active TCC2 takes about 3 minutes. Depending on the software version and backup version the new TCC2 started with, the entire process can take between 3 and 40 minutes. 2.3.3 TCC2 Card-Level Indicators The TCC2 faceplate has ten LEDs. Table 2-2 describes the two card-level LEDs on the TCC2 faceplate. Table 2-2 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 Green (Active) Yellow (Standby) Indicates the TCC2 is active (green) or in standby (yellow) mode. The ACT/STBY LED also provides the timing reference and shelf control. When the active TCC2 is writing to its database or to the standby TCC2 database, the card LEDs blink. To avoid memory corruption, do not remove the TCC2 when the active or standby LED is blinking. 2-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2 Card 2.3.4 Network-Level Indicators Table 2-3 describes the six network-level LEDs on the TCC2 faceplate. 2.3.5 Power-Level Indicators Table 2-4 describes the two power-level LEDs on the TCC2 faceplate. Note For ONS 15454 ETSI shelf, the power-level LEDs are either green or red. The LED is green when the voltage on supply inputs is between the extremely low battery voltage and extremely high battery voltage thresholds. The LED is red when the voltage on supply inputs is above extremely high battery voltage or below extremely low battery voltage thresholds. Table 2-3 TCC2 Network-Level Indicators System-Level LEDs Definition Red CRIT LED Indicates critical alarms in the network at the local terminal. Red MAJ LED Indicates major alarms in the network at the local terminal. Yellow MIN LED Indicates minor alarms in the network at the local terminal. Red REM LED Provides first-level alarm isolation. The remote (REM) LED turns red when an alarm is present in one or more of the remote terminals. Green SYNC LED Indicates that node timing is synchronized to an external reference. Green ACO LED After pressing the alarm cutoff (ACO) button, the ACO LED turns green. The ACO button opens the audible alarm closure on the backplane. ACO is stopped if a new alarm occurs. After the originating alarm is cleared, the ACO LED and audible alarm control are reset. Table 2-4 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. The LED is amber when the voltage on supply input A is between the high battery voltage and extremely high battery voltage (EHIBATVG) thresholds or between the low battery voltage and extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input A is above extremely high battery voltage or below extremely low battery voltage thresholds. Green/Amber/Red PWR B LED The PWR B LED is green when the voltage on supply input B is between the low battery voltage and high battery voltage thresholds. The LED is amber when the voltage on supply input B is between the high battery voltage and extremely high battery voltage thresholds or between the low battery voltage and extremely low battery voltage thresholds. The LED is red when the voltage on supply input B is above extremely high battery voltage or below extremely low battery voltage thresholds. 2-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2P Card 2.4 TCC2P Card (Cisco ONS 15454 only) Note For TCC2P card specifications, see the “A.3.2 TCC2P Card Specifications” section on page A-5. The Advanced Timing, Communications, and Control Plus (TCC2P) card is an enhanced version of the TCC2 card. The primary enhancements are Ethernet security features and 64K composite clock BITS timing. The TCC2P card performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET SOH DCC/GCC termination, and system fault detection for the ONS 15454. The TCC2P also ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing requirements. It monitors the supply voltage of the system. The TCC2P card supports multi-shelf management. The TCC2P card acts as a shelf controller and node controller for the ONS 15454. The TCC2P card supports up to 12 subtended shelves through the MSM-ISC card or external switch. In a multi-shelf configuration, the TCC2P card allows the ONS 15454 node to be a node controller if an M6 shelf is subtended to it. The TCC2P card is compliant to the following standards: • The LAN interface of the TCC2P card meets the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from –40 to 32 degrees Fahrenheit (–40 to 0 degrees Celsius). • The TCC2P card is Restriction of Use of Hazardous Substances (RoHS) complaint. The RoHS regulations limit or ban the specific substances such as lead, cadmium, polybrominated biphenyl (PBB), mercury, hexavalent chromium, and polybrominated diphenyl ether (PBDE) flame retardants in a new electronic and electric equipment. Figure 2-3 shows the faceplate and block diagram for the TCC2P card. 2-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2P Card Figure 2-3 TCC2P Faceplate and Block Diagram FAIL A PWR B ACT/STBY ACO CRIT MIN REM SYNC RS-232 TCP/IP MAJ ACO TCC2P LAMP BACKPLANE Ethernet Switch Mate TCC2 Ethernet Port Backplane Ethernet Port (Shared with Mate TCC2) SDRAM Memory & Compact Flash FPGA TCCA ASIC SCL Processor Serial Debug Modem Interface EIA/TIA 232 Craft Interface Backplane EIA/TIA 232 Port (Shared with Mate TCC2) Faceplate EIA/TIA 232 Port Note: Only 1 EIA/TIA 232 Port Can Be Active - Backplane Port Will Supercede Faceplate Port Faceplate Ethernet Port SCL Links to All Cards HDLC Message Bus Mate TCC2 HDLC Link Modem Interface 400MHz (Not Used) Processor Communications Processor SCC3 MCC1 FCC1 MCC2 SCC4 FCC2 SMC1 SCC2 DCC Processor System Timing BITS Input/ Output Ref Clocks -48V PWR (all I/O Slots) Monitors Real Time Clock Ethernet Phy SCC12-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2P Card 2.4.1 TCC2P Functionality The TCC2P card supports multichannel, high-level data link control (HDLC) processing for the DCC. Up to 84 DCCs can be routed over the TCC2P card and up to 84 section DCCs can be terminated at the TCC2P card (subject to the available optical digital communication channels). The TCC2P selects and processes 84 DCCs to facilitate remote system management interfaces. 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. The TCC2P card performs all system-timing functions for each ONS 15454. The TCC2P card monitors the recovered clocks from each traffic card and two BITS ports for frequency accuracy. The TCC2P card selects a recovered clock, a BITS, or an internal Stratum 3 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 TCC2P card supports 64/8K composite clock and 6.312 MHz timing output. The TCC2P card monitors both supply voltage inputs on the shelf. An alarm is generated if one of the supply voltage inputs has a voltage out of the specified range. Install TCC2P cards in Slots 7 and 11 for redundancy. If the active TCC2P card fails, traffic switches to the protect TCC2P card. All TCC2P card protection switches conform to protection switching standards when the bit error rate (BER) counts are not in excess of 1 * 10 exp – 3 and completion time is less than 50 ms. The TCC2P card has two built-in Ethernet interface ports for accessing the system: one built-in RJ-45 port on the front faceplate for on-site craft access and a second port on the backplane. The rear Ethernet interface is for permanent LAN access and all remote access via TCP/IP as well as for Operations Support System (OSS) access. The front and rear Ethernet interfaces can be provisioned with different IP addresses using CTC. Two EIA/TIA-232 serial ports, one on the faceplate and a second on the backplane, allow for craft interface in TL1 mode. Note To use the serial port craft interface wire-wrap pins on the backplane, the DTR signal line on the backplane port wire-wrap pin must be connected and active. 2.4.2 Redundant TCC2P Card Installation Cisco does not support operation of the ONS 15454 with only one TCC2P card. For full functionality and to safeguard your system, always operate with two TCC2P cards. When a second TCC2P card is inserted into a node, it synchronizes its software, its backup software, and its database with the active TCC2P card. If the software version of the new TCC2P card does not match the version on the active TCC2P card, the newly inserted TCC2P card copies from the active TCC2P card, taking about 15 to 20 minutes to complete. If the backup software version on the new TCC2P card does not match the version on the active TCC2P card, the newly inserted TCC2P card copies the backup 2-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC2P Card software from the active TCC2P card again, taking about 15 to 20 minutes. Copying the database from the active TCC2P card takes about 3 minutes. Depending on the software version and backup version the new TCC2P card started with, the entire process can take between 3 and 40 minutes. 2.4.3 TCC2P Card-Level Indicators The TCC2P faceplate has ten LEDs. Table 2-5 describes the two card-level LEDs on the TCC2P faceplate. 2.4.4 Network-Level Indicators Table 2-6 describes the six network-level LEDs on the TCC2P faceplate. Table 2-5 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 Green (Active) Amber (Standby) Indicates the TCC2P is active (green) or in standby (amber) mode. The ACT/STBY LED also provides the timing reference and shelf control. When the active TCC2P is writing to its database or to the standby TCC2P database, the card LEDs blink. To avoid memory corruption, do not remove the TCC2P when the active or standby LED is blinking. Table 2-6 TCC2P Network-Level Indicators System-Level LEDs Definition Red CRIT LED Indicates critical alarms in the network at the local terminal. Red MAJ LED Indicates major alarms in the network at the local terminal. Amber MIN LED Indicates minor alarms in the network at the local terminal. Red REM LED Provides first-level alarm isolation. The remote (REM) LED turns red when an alarm is present in one or more of the remote terminals. Green SYNC LED Indicates that node timing is synchronized to an external reference. Green ACO LED After pressing the ACO button, the ACO LED turns green. The ACO button opens the audible alarm closure on the backplane. ACO is stopped if a new alarm occurs. After the originating alarm is cleared, the ACO LED and audible alarm control are reset.2-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC3 Card 2.4.5 Power-Level Indicators Table 2-7 describes the two power-level LEDs on the TCC2P faceplate. Note For ONS 15454 ETSI shelf, the power-level LEDs are either green or red. The LED is green when the voltage on supply inputs is between the extremely low battery voltage and extremely high battery voltage thresholds. The LED is red when the voltage on supply inputs is above extremely high battery voltage or below extremely low battery voltage thresholds. 2.5 TCC3 Card (Cisco ONS 15454 only) Note For TCC3 card specifications, see the “A.3.3 TCC3 Card Specifications” section on page A-6. The Timing Communications Control Three (TCC3) card is an enhanced version of the TCC2P card. The primary enhancements include the increase in memory size and compact flash space. The TCC3 card boots up as TCC2P card in older releases and as TCC3 card from Release 9.2 onwards. The TCC3 card performs system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection/resolution, SONET SOH DCC/GCC termination, and system fault detection for the ONS 15454. The TCC3 also ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing requirements. It monitors the supply voltage of the system. The TCC3 card supports multi-shelf management. The TCC3 card acts as a shelf controller and node controller for the ONS 15454. The TCC3 card supports up to 30 subtended shelves through the MSM-ISC card or external switch. In a multi-shelf configuration, the TCC3 card allows the ONS 15454 node to be a node controller if an M6 shelf is subtended to it. We recommend the use the TCC3 card as a node controller when the number of subtended shelves exceeds 12. Table 2-7 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. The LED is amber when the voltage on supply input A is between the high battery voltage and extremely high battery voltage (EHIBATVG) thresholds or between the low battery voltage and extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input A is above extremely high battery voltage or below extremely low battery voltage thresholds. Green/Amber/Red PWR B LED The PWR B LED is green when the voltage on supply input B is between the low battery voltage and high battery voltage thresholds. The LED is amber when the voltage on supply input B is between the high battery voltage and extremely high battery voltage thresholds or between the low battery voltage and extremely low battery voltage thresholds. The LED is red when the voltage on supply input B is above extremely high battery voltage or below extremely low battery voltage thresholds. 2-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC3 Card The TCC3 card is compliant with the following standards: • The LAN interface of the TCC3 card meets the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures ranging from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from –40 to 32 degrees Fahrenheit (–40 to 0 degrees Celsius). • The TCC3 card is Restriction of Use of Hazardous Substances (RoHS) compliant. The RoHS regulations limit or ban the specific substances such as lead, cadmium, polybrominated biphenyl (PBB), mercury, hexavalent chromium, and polybrominated diphenyl ether (PBDE) flame retardants in a new electronic and electric equipment. Figure 2-3 shows the faceplate and block diagram for the TCC3 card. Figure 2-4 TCC3 Faceplate and Block Diagram FAIL A PWR B ACT/STBY ACO CRIT MIN REM SYNC RS-232 TCP/IP MAJ ACO TCC3 LAMP BACKPLANE Ethernet Switch Mate TCC Ethernet Port Backplane Ethernet Port (Shared with Mate TCC) SDRAM Memory & Compact Flash FPGA TCCA FPGA SCL Processor Serial Debug Modem Interface EIA/TIA 232 Craft Interface Backplane EIA/TIA 232 Port (Shared with Mate TCC) Faceplate EIA/TIA 232 Port Note: Only 1 EIA/TIA 232 Port Can Be Active - Backplane Port Will Supercede Faceplate Port Faceplate Ethernet Port SCL Links to All Cards HDLC Message Bus Mate TCC HDLC Link Modem Interface (Not Used) 400MHz Processor Communications Processor SCC3 MCC1 FCC1 MCC2 SCC4 FCC2 SMC1 SCC2 DCC Processor System Timing BITS Input/ Output Ref Clocks (all I/O Slots) -48V PWR Monitors Real Time Clock Ethernet Phy SCC1 2486632-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC3 Card 2.5.1 TCC3 Functionality The TCC3 card supports multichannel, high-level data link control (HDLC) processing for the DCC. Up to 84 DCCs can be routed over the TCC3 card and up to 84 section DCCs can be terminated at the TCC3 card (subject to the available optical digital communication channels). The TCC3 selects and processes 84 DCCs to facilitate remote system management interfaces. The TCC3 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 the TCC3 card’s nonvolatile memory, which allows quick recovery of data in the event of a power or card failure. The TCC3 card performs all system-timing functions for the ONS 15454. The TCC3 card monitors the recovered clocks from each traffic card and two BITS ports for frequency accuracy. The TCC3 card selects a recovered clock, a BITS, or an internal Stratum 3 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 TCC3 card to synchronize with the recovered clock, which provides holdover if the reference is lost. The TCC3 card supports 64/8K composite clock and 6.312 MHz timing output. The TCC3 card monitors both the supply voltage inputs on the shelf. An alarm is generated if one of the supply voltage inputs has a voltage level above the specified range. The TCC3 card has two built-in Ethernet interface ports for accessing the system: one built-in RJ-45 port on the front faceplate for on-site craft access and a second port on the backplane. The rear Ethernet interface is for permanent LAN access and all remote access via TCP/IP as well as for Operations Support System (OSS) access. The front and rear Ethernet interfaces can be provisioned with different IP addresses using CTC. Two EIA/TIA-232 serial ports, one on the faceplate and a second on the backplane, allow for craft interface in TL1 mode. Note To use the serial port craft interface wire-wrap pins on the backplane, the DTR signal line on the backplane port wire-wrap pin must be connected and active. 2.5.2 Redundant TCC3 Card Installation We do not recommend the operation of the ONS 15454 with only one TCC3 card. For full functionality and to safeguard your system, always operate with two TCC3 cards. Install TCC3 cards in Slots 7 and 11 for redundancy. If the active TCC3 card fails, traffic switches to the protect TCC3 card. All TCC3 card protection switches conform to protection switching standards when the bit error rate (BER) counts are not in excess of 1 * 10 exp – 3 and completion time is less than 50 ms. When a second TCC3 card is inserted into a node, it synchronizes its software, backup software, and database with those of the active TCC3 card. If the software version of the new TCC3 card does not match the version on the active TCC3 card, the newly inserted TCC3 card copies from the active TCC3 card, taking about 15 to 20 minutes to complete. Copying the database from the active TCC3 card takes about 3 minutes. Depending on the software version and backup version the new TCC3 card started with, the entire process can take between 3 and 40 minutes. 2-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TCC3 Card 2.5.3 TCC3 Card-Level Indicators The TCC3 faceplate has ten LEDs. Table 2-5 describes the two card-level LEDs on the TCC3 faceplate. 2.5.4 Network-Level Indicators Table 2-6 describes the six network-level LEDs on the TCC3 faceplate. Table 2-8 TCC3 Card-Level Indicators Card-Level LEDs Definition Red FAIL LED Indicates the TCC3 card is being reset. The FAIL LED flashes during the boot and write process. Replace the card if the FAIL LED persists. ACT/STBY LED Green (Active) Amber (Standby) Indicates the TCC3 is active (green) or in standby (amber) mode. The ACT/STBY LED also provides the timing reference and shelf control. When the active TCC3 is writing to its database or to the standby TCC3 database, the card LEDs blink. To avoid memory corruption, do not remove the TCC3 when the active or standby LED is blinking. Table 2-9 TCC3 Network-Level Indicators System-Level LEDs Definition Red CRIT LED Indicates critical alarms in the network at the local terminal. Red MAJ LED Indicates major alarms in the network at the local terminal. Amber MIN LED Indicates minor alarms in the network at the local terminal. Red REM LED Indicates first-level alarm isolation. The remote (REM) LED turns red when an alarm is present in one or more of the remote terminals. Green SYNC LED Indicates that node timing is synchronized to an external reference. Green ACO LED Indicates teh audible alarms. After pressing the ACO button, the ACO LED turns green. The ACO button opens the audible alarm closure on the backplane. ACO is stopped if a new alarm occurs. After the originating alarm is cleared, the ACO LED and audible alarm control are reset.2-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card 2.5.5 Power-Level Indicators Table 2-7 describes the two power-level LEDs on the TCC3 faceplate. Note For the ONS 15454 ETSI shelf, the power-level LEDs are either green or red. The LED is green when the voltage on supply inputs is between the extremely low battery voltage and extremely high battery voltage thresholds. The LED is red when the voltage on supply inputs is above extremely high battery voltage or below extremely low battery voltage thresholds. 2.6 TNC Card (Cisco ONS 15454 M2 and ONS 15454 M6 only) The TNC card combines the functions of multiple cards such as TCC2P, OSCM, ISC, and AIC-I cards. The card has a similar look and feel to TCC2/TCC2P/TCC3 cards. Note For TNC card specifications, see the A.3.4 TNC Card Specifications (Cisco ONS 15454 M2 and Cisco ONS 15454 M6), page A-6 section. The TNC card is provisioned as master and slave in the 15454-M6 shelf, and as a stand-alone card in the 15454-M2 shelf. The TNC card serves as the processor card for the node. On the 15454-M6 shelf, install redundant TNC cards in slots 1 and 8. If the active TNC card fails, system traffic switches to the redundant TNC card. The card supports line cards from slots 2 to 7. On the 15454-M2 shelf, install the stand-alone TNC card in slot 1. The TNC card supports line cards in slots 2 and 3. Table 2-10 TCC3 Power-Level Indicators Power-Level LEDs Definition Green/Amber/Red PWR A LED Indicates the voltage on supply input A. 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. The LED is amber when the voltage on supply input A is between the high battery voltage and extremely high battery voltage (EHIBATVG) thresholds or between the low battery voltage and extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input A is above extremely high battery voltage or below extremely low battery voltage thresholds. Green/Amber/Red PWR B LED Indicates the voltage on supply input B.The PWR B LED is green when the voltage on supply input B is between the low battery voltage and high battery voltage thresholds. The LED is amber when the voltage on supply input B is between the high battery voltage and extremely high battery voltage thresholds or between the low battery voltage and extremely low battery voltage thresholds. The LED is red when the voltage on supply input B is above extremely high battery voltage or below extremely low battery voltage thresholds. 2-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card The TNC card monitors both the supply voltage inputs on the 15454-M6 shelf. The TNC card raises an alarm if one of the supply voltage inputs has a voltage out of the specified range. The 15454-M2 shelf has dual power supply. You can insert and remove the TNC card even when the system is online, without impacting the system traffic. You can upgrade the TSC card to a TNC card. During the upgrade, the TNC card does not support OSC functions such as UDC, VoIP, DCC, and timing function. However, you can still provision the SFP ports on the TNC card during the upgrade. The TNC and TSC cards cannot be inserted in the same shelf. Note Downgrade procedures from TNC cards to TSC cards are not supported. For information on upgrading TSC card to a TNC card, refer chapter, "Upgrade, Add, and Remove Cards and Nodes" in the Cisco ONS 15454 DWDM Procedure Guide. The TNC card supports all the alarms supported by the TCC2P and AIC-I cards. The card adjusts the fan speed according to the temperature and reports a fan failure alarm. Note The LAN interface of the TNC card meets the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from -40 to 32 degrees Fahrenheit (-40 to 0 degrees Celsius). 2.6.1 Functions of TNC The functions of the TNC card are explained in the following sections: 2.6.1.1 Communication and Control The TNC card acts as node controller and shelf controller. The control tasks include system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection, and resolution. The control tasks also include SONET and SDH data communications channel (DCC) termination, 84 section SDCC and multiplex section MSDCC terminations, 28 SDCC tunnels or SDCC-to-line LDCC terminations, and system fault detection for the 15454-M2 and 15454-M6 shelves. The system initialization tasks include assigning the network parameters to the system and loading the system with the provisioning data stored in the database. The line cards in the system do not boot without the TNC card. The TNC card supports and provides the following: • OSC communication to implement the Optical DCN, User Data Channels and Voice over IP interface. • Supervisory data channel (SDC) for communication between the nodes. • Two point-to-point Ethernet channels at 10 Mbps to carry Voice over IP traffic. • Two point-to-point Ethernet channels at 10/100 Mbps to carry UDC traffic. • Passive inventory of external devices on the 15454-M2 and 15454-M6 shelves. • Supports OSC, UDC, and VoIP traffic. Two UDC/VoIP ports are present on the external connection unit that can be configured to carry UDC/VoIP traffic.2-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card Note The TNC card supports UDC and VoIP configuration only when OSC is configured on the ports. To delete the OSC channel on a port, delete the UDC and VoIP configuration on that port. For more information, refer chapter, "Install the Cisco ONS 15454 Shelf Assembly" in the Cisco ONS 15454 DWDM Procedure Guide. On the 15454-M2 and 15454-M6 shelves, the TNC card must adhere to the following rules for SDCC/LDCC allocation: • SDCC + SDCC Tunnels <= 68 • LDCC <= 28 • IP Tunnels <= 10 • SDCC + SDCC tunnels + (LDCC * 3) <= 84 2.6.1.2 Optical Service Channel The TNC card supports two optical service channels (OSC) through two small-form factor pluggable (SFP) ports. The two SFP ports are named SFP1 and SFP2. The supported SFPs on TNC ports are ONS-SC-OSC-ULH, ONS-SE-155-1510, and ONS-SC-Z3-1510. Note When you replace SFPs on the TNC card, provisioning for the current SFP has to be deleted before the new SFP is plugged in. SFP1 supports the following payloads: • OC-3/STM-1 • Fast Ethernet (FE) • Gigabit Ethernet (GE) SFP2 supports the following payloads: • Fast Ethernet (FE) • Gigabit Ethernet (GE) 2.6.1.3 Timing and Synchronization The TNC card performs all the system-timing functions for the 15454-M2 and 15454-M6 shelves. This includes short-term clock recovery, reducing the need to reset the calendar and time-of-day settings after a power failure. The TNC card ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing and synchronization requirements. The TNC card supports external, line, and internal timing inputs. The TNC card supports 64KHz+8KHz composite clock and 6.312 MHz timing output. Note The TNC card supports the BITS-1 and BITS-2 external timing interfaces on the ONS 15454 M6 shelf. The card supports the BITS-1 interface on the ONS 15454 M2 shelf.2-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card The TNC card monitors the recovered clocks from each traffic card and two building integrated timing supply (BITS-1 and BITS-2) ports for accurate frequencies. The card selects a recovered clock, a BITS, OC-N/STM-N, or an internal Stratum 3 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 TNC card to synchronize with the recovered clock, which provides holdover if the reference is lost. The card supports SNTP operation that allows the nodes to synchronize the system clock automatically with a reference SNTP server following system reboots, card resets, and software upgrades. For more information on the timing function, see the Timing Reference chapter. 2.6.1.4 MultiShelf Management The TNC card supports multishelf management of up to 30 shelves including the node controller. The card supports up to 29 subtending shelves. The subtending shelves can be the ONS 15454 M6 or ONS 15454 shelves. This allows network administrators to isolate faults and provision new services across the DWDM network. In the ONS 15454 M6 shelf, there are six FE RJ45 ports on the ECU and each TNC card supports three FE RJ45 connections to connect subtending shelves. 2.6.1.5 Database Storage The TNC card provides 4 GB of non-volatile database storage (IDE Compact Flash Module) for communication, provisioning, and system control. This allows full database recovery during power failure. The TNC card supports writing and reading to and from an external non-volatile memory device. The card also communicates with the non-volatile memory device through a USB 2.0 standard interface. The USB-WRITE-FAIL alarm may be raised on the TNC card when synchronization occurs between Compact Flash and USB Flash. If this alarm does not clear even after 20 minutes duration, it is recommended to contact TAC. For information on USB-WRITE-FAIL alarm, see the Cisco ONS 15454 DWDM Troubleshooting Guide. Note The configuration details are stored in the database of the TNC card. The database restore from a TNC card to a TSC card or vice versa is not supported. 2.6.1.6 Interface Ports The TNC card has three built-in interface ports: • RJ-45 LAN port • RJ-45 console port • RS-232 port (serial port) The RJ-45 LAN port and RS-232 port are located on the faceplate of the TNC card. The RJ-45 console port is behind the faceplate of the TNC card. The front access RJ-45 LAN port provides 10/100 BASE-T Ethernet connectivity to the system. The RJ-45 LAN port has LEDs to provide link and activity status. The RJ-45 LAN port provides local and remote access to the Cisco Transport Controller through a common Web interface. The RJ-45 console port is used to launch a debug session on the TNC card.2-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card The RS-232 port is used to connect to the Transaction Language 1 (TL1) management interface. In TL1 mode, the RS-232 port runs at 9.6 Kbps without any flow control. The front access LAN port and RJ-45 EMS LAN port can be provisioned with different IP addresses by configuring the TNC card in secure mode using CTC. On 15454 M2, the EMS port is on the power module. On 15454 M6, the EMS port is on the ECU. The two SFP ports (SFP1 and SFP2) are used for primary OSC and secondary OSC connections. SFP1 supports OC-3/STM-1, FE, or GE payloads; SFP2 supports FE or GE payloads. The two SFP ports on the TNC card are in IS,AINS administrative state during payload creation. In this state, only the following alarms are raised: • AS-MT alarm on PPM • AS-CMD alarm on PPM and facility • Prov-Mismatch alarm on PPM The TX power is -40 and RX power is -50 for Ultra long-haul SFPs. The TX power is -40 and RX power is -40 for other SFPs. When the OSC is created, the two SFP ports move to IS state. In this state, all the supported alarms are raised. Note VLAN tagged traffic is not supported on UDC or VoIP ports that are present on the external connection unit. 2.6.1.7 External Alarms and Controls The TNC card provides customer-defined (environmental) alarms and external controls on the ONS 15454 M6 shelf. The card provides input/output alarm contact closures. The TNC card operates in two modes: • External alarms mode - This is the default mode and up to 14 alarm input ports can be configured. External alarms (input contacts) are typically used for external sensors such as open doors, temperature sensors, flood sensors, and other environmental conditions. • External control mode - Up to 10 alarm input ports and four alarm output ports can be configured. External controls (output contacts) are typically used to drive visual or audible devices such as bells and lights, but they can control other devices such as generators, heaters, and fans. To configure the external alarms and external controls, go to Provisioning -> Alarm Extenders tab in the CTC node view. To view the external alarms and external controls, go to Maintenance -> Alarm Extenders tab in the CTC node view. For information on how to configure and view the external alarms and external controls, refer chapter “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. Note The LCD module must be present in the ONS 15454 M6 shelf assembly to provision alarms from the ECU, fan-tray assembly, or power modules. For information on pinouts of external alarms and external controls, see the “ONS 15454 ANSI Alarm, Timing, LAN, and Craft Pin Connections” section in the Cisco ONS 15454 Hardware Installtion Guide.2-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card 2.6.1.8 Digital Image Signing (DIS) The TNC card provides services that authenticate the origin of the software running on the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms, see the 2.8 Digital Image Signing, page 2-33 section. 2.6.2 Faceplate and Block Diagram The faceplate design of the TNC card allows sufficient space to insert or remove cables while accessing the Ethernet and SFP ports. The TNC card can be installed only in slots 1 or 8 of the ONS 15454 M6 shelf and in slot 1 of the ONS 15454 M2 shelf. The TNC card has an identifier on the faceplate that matches with an identifier in the shelf. A key is also provided on the backplane interface connectors as identifier in the shelf. The TNC card supports field-programmable gate array (FPGA) for the backplane interface. The TNC card has three FPGA: TCCA, SYNTIDE, and FRAMPOS. Figure 2-5 illustrates the faceplate and block diagram for the TNC card. Figure 2-5 TNC Faceplate and Block Diagram HAZARD LEVEL 1 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No.50, DATED JUNE 24, 2007 TNC FAIL ACT/STBY ACO SFP2 PWR A B LAMP TEST SFP1 LINK EIA/TIA-232 LINK ACT TCP/IP LINK ACT ACT TX RX TX RX CRIT REM MAJ SYNC MIN ACO 1GB DDR2 Mini-DIMM CPU MPC8568E GE Phy GE Phy GE Phy SFP1 SFP2 BusMux CPLD Ethernet Switch Local Ethernet Switch External Glue Logic CPLD SYNTIDE FPGA Boot Flash USB Controller FRAMPOS FPGA TCCA FPGA T1/E1 Framers LOG NVRAM FE Phy 4GB Compact Flash 2778552-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card 2.6.3 Lamp Test The TNC card supports a lamp test function that is activated by pressing the Lamp Test button on the faceplate or from CTC. The lamp test function allows the user to test the working state of LEDs and ensures that all LEDs are functional. When you activate the lamp test function, all the port LEDs illuminate simultaneously for several seconds. 2.6.4 TNC Card Installation (ONS 15454 M6) On the ONS 15454 M6 shelf, the TNC card operates in either simplex or duplex (redundant) control mode. In redundant control mode, high availability is achieved. When a redundant TNC card is inserted into a node, it synchronizes its software, backup software, and database with the active TNC card. If the software versions do not match, the redundant TNC card copies from the active TNC card, taking about 15 to 20 minutes to complete. If the software versions match, the redundant TNC card copies the backup software from the active TNC card, taking about 15 to 20 minutes. Copying the database from the active TNC card takes about 3 minutes. Depending on the software version and backup version the redundant TNC card started with, the entire process can take between 3 and 40 minutes. 2.6.5 Card-Level Indicators The TNC faceplate has twelve LEDs. Table 2-11 describes the two card-level LEDs on the TNC faceplate. 2.6.6 Network-Level Indicators Table 2-12 describes the six network-level LEDs on the TNC faceplate. Table 2-11 TNC Card-Level Indicators Card-Level LEDs Definition Red FAIL LED Indicates the TNC card is in fail mode. This LED is on during reset. This LED flashes during the boot and write process. Replace the card if the FAIL LED persists. ACT/STBY LED Green (Active) Amber (Standby) Indicates the TNC card is active (green) or in standby (amber) mode. The ACT/STBY LED also provides the timing reference and shelf control. When the active TNC is writing to its database or to the standby TNC database, the card LEDs blink. To avoid memory corruption, do not remove the TNC card when the active or standby LED is blinking.2-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card Table 2-12 TNC Network-Level Indicators System-Level LEDs Definition Red CRIT LED Indicates critical alarms in the network at the local terminal. Red MAJ LED Indicates major alarms in the network at the local terminal. Yellow MIN LED Indicates minor alarms in the network at the local terminal. Red REM LED Provides first-level alarm isolation. The remote (REM) LED turns red when a critical, major, or minor alarm is present in one or more of the remote terminals. Green SYNC LED Indicates the synchronization status; Indicates that node timing is synchronized to an external reference. Green ACO LED Indicates the Alarm Cut-Off status. After pressing the ACO button, the ACO LED turns green. The ACO button opens the audible alarm closure on the backplane. ACO is stopped if a new alarm occurs. After the originating alarm is cleared, the ACO LED and audible alarm control are reset.2-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TNC Card 2.6.7 Power-Level Indicators Table 2-13 describes the two power-level LEDs on the TNC faceplate. 2.6.8 Ethernet Port Indicators Table 2-14 describes the two port-level LEDs on the TNC faceplate. 2.6.9 SFP Indicators Table 2-15 describes the SFP LED indicators. Table 2-13 TNC Power-Level Indicators Power-Level LEDs Definition Green/Red PWR A LED Indicates the status of power to the card. 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. The LED is red when the voltage on supply input A is above high battery voltage/extremely high battery voltage (EHIBATVG ) or below low battery voltage/extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input A is 0. Green/Red PWR B LED Indicates the status of power to the card. The PWR B LED is green when the voltage on supply input B is between the low battery voltage and high battery voltage thresholds. The LED is red when the voltage on supply input B is above high battery voltage/extremely high battery (EHIBATVG ) voltage or below low battery voltage/extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input B is 0. Table 2-14 TNC Port-Level Indicators Port-Level LEDs Definition Green LINK LED Indicates the connectivity status. Amber ACT LED Indicates data reception.2-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card 2.6.10 Protection Schemes The TNC card supports active and redundant architecture. The ONS 15454 M6 shelf supports 1:1 equipment protection with one TNC card acting as active and the other TNC card as redundant. The ONS 15454 M2 shelf supports simplex control mode. In this mode, the active TNC card operates without a redundant TNC card. The ONS 15454 M6 shelf supports both simplex and redundant control mode. In redundant control mode, the active TNC card operates with a redundant TNC card as the backup. If the active TNC card is removed, system traffic switches to the redundant TNC card. If the redundant TNC card is not present or not in the standby state, removing the active TNC card results in loss of system traffic and management connectivity. In redundant control mode, a TNC card can protect another TNC card. However, a TNC card cannot protect a TSC card or vice versa. 2.6.11 Cards Supported by TNC The TNC card supports 15454 MSTP line cards except the following cards: • OSCM • ISC • AIC • AIC-I The TNC card is not interoperable with TCC2 /TCC2P/TCC3 cards. The TNC and TCC cards cannot be inserted in the same shelf. The line cards such as Transponder and Muxponder cards can be inserted in the ONS 15454 M2 and ONS 15454 M6 shelves along with the TNC card. 2.7 TSC Card (Cisco ONS 15454 M2 and ONS 15454 M6 only) The TSC card combines the functions of multiple cards such as TCC2P, ISC, and AIC-I cards. The card has a similar look and feel to TCC2/TCC2P/TCC3 cards. Table 2-15 TNC SFP Indicators Port Type Link LED Activity LED OC3 • RED - No link • GREEN - Link — FE • RED - No link • GREEN - Link Blinks on packet flow GE • RED - No link • GREEN - Link Blinks on packet flow2-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card Note For TSC card specifications, see the A.3.5 TSC Card Specifications (ONS 15454 M2 and ONS 15454 M6), page A-7 section. The TSC card is provisioned as master and slave in the ONS 15454 M6 shelf, and as a stand-alone card in the ONS 15454 M2 shelf. The TSC card serves as the processor card for the node. On the ONS 15454 M6 shelf, install redundant TSC cards in slots 1 and 8. If the active TSC card fails, system traffic switches to the redundant TSC card. The TSC card supports line cards from slots 2 to 7. On the ONS 15454 M2 shelf, install the stand-alone TSC card in slot 1. The TSC card supports line cards in slots 2 and 3. The TSC card monitors both the supply voltage inputs on the 15454-M6 shelf. The TSC card raises an alarm if one of the supply voltage inputs has a voltage out of the specified range. The 15454-M2 shelf has dual power supply. You can insert and remove the TSC card even when the system is online, without impacting the system traffic. The TSC card does not support optical service channel (OSC) and SFP ports. You can upgrade the TSC card to a TNC card. During the upgrade, the TNC card does not support OSC functions such as UDC, VoIP, DCC, and timing function. However, you can still provision SFP ports on the TNC card during the upgrade. The TNC and TSC cards cannot be inserted in the same shelf. The TSC card supports all the alarms supported by the TCC2P and AIC-I cards. The card adjusts the fan speed according to the temperature and reports a fan failure alarm. Note The LAN interface of the TSC card meets the standard Ethernet specifications by supporting a cable length of 328 ft (100 m) at temperatures from 32 to 149 degrees Fahrenheit (0 to 65 degrees Celsius). The interfaces can operate with a cable length of 32.8 ft (10 m) maximum at temperatures from -40 to 32 degrees Fahrenheit (-40 to 0 degrees Celsius). 2.7.1 Functions of TSC The functions of the TSC card are explained in the following sections: 2.7.1.1 Communication and Control The TSC card acts as a shelf controller. The control tasks include system initialization, provisioning, alarm reporting, maintenance, diagnostics, IP address detection, and resolution. The control tasks also include SONET and SDH data communications channel (DCC) termination, 84 section SDCC and multiplex section MSDCC terminations, 28 SDCC tunnels or SDCC-to-line LDCC terminations, and system fault detection for the ONS 15454 M2 and ONS 15454 M6 shelves. The system initialization tasks include assigning the network parameters to the system and loading the system with the provisioning data stored in the database. The line cards in the system do not boot without the TSC card. The TSC card supports and provides the following: • Passive inventory of external devices on the 15454-M2 and 15454-M6 shelves. • 100 Mbps UDC on the 15454-M6 shelf. 2-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card On the 15454-M2 and 15454-M6 shelves, the TSC card must adhere to the following rules for SDCC/LDCC allocation. • SDCC + SDCC Tunnels <= 68 • LDCC <= 28 • IP Tunnels <= 10 • SDCC + SDCC tunnels + (LDCC * 3) <= 84 2.7.1.2 Timing and Synchronization The TSC card performs all the system-timing functions for the 15454-M2 and 15454-M6 shelves. This includes short-term clock recovery, reducing the need to reset the calendar and time-of-day settings after a power failure. The TSC card ensures that the system maintains Stratum 3 (Telcordia GR-253-CORE) timing and synchronization requirements. The TSC card supports external, line, and internal timing inputs. The TSC card supports 64KHz+8KHz composite clock and 6.312 MHz timing output. Note The TSC card supports the BITS-1 and BITS-2 external timing interfaces on the 15454-M6 shelf. The card supports the BITS-1 interface on the 15454-M2 shelf. The TSC card monitors the recovered clocks from each traffic card and two building integrated timing supply (BITS-1 and BITS-2) ports for accurate frequencies. The card selects a recovered clock, a BITS, OC-N/STM-N, or an internal Stratum 3 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 TSC card to synchronize with the recovered clock, which provides holdover if the reference is lost. The card supports SNTP operation that allows the nodes to synchronize the system clock automatically with a reference SNTP server following system reboots, card resets, and software upgrades. For more information on the timing function, see the Timing Reference chapter. 2.7.1.3 MultiShelf Management The TSC card supports multishelf management with support for up to 30 shelves including the node controller. The card supports up to 29 subtending shelves. The subtending shelves can be the 15454-M6 or 15454-DWDM shelves. This allows network administrators to isolate faults and provision new services across the DWDM network. In the 15454-M6 shelf, there are six FE RJ45 ports on the ECU. Each TSC card supports three FE RJ45 connections to connect subtending shelves. 2.7.1.4 Database Storage The TSC card provides 4 GB of non-volatile database storage (IDE Compact Flash Module) for communication, provisioning, and system control. This allows full database recovery during power failure. The TSC card supports writing and reading to and from an external non-volatile memory device. The card also communicates with the non-volatile memory device through a USB 2.0 standard interface.2-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card Note The configuration details are stored in the database of the TSC card. The database restore from a TSC card to a TNC card or vice versa is not supported. 2.7.1.5 Interface Ports The TSC card has three built-in interface ports: • RJ-45 LAN port • RJ-45 console port • RS-232 port (serial port) The RJ-45 LAN port and RS-232 port are located on the faceplate of the TSC card. The RJ-45 console port is behind the faceplate of the TSC card. The front access RJ-45 LAN port provides 10/100 BASE-T Ethernet connectivity to the system. The RJ-45 LAN port has LEDs to provide link and activity status. The RJ-45 LAN port provides local and remote access to the Cisco Transport Controller through a common Web interface. The RJ-45 console port is used to launch a debug session on the TSC card. The RS-232 port is used to connect to the TL1 management interface. In TL1 mode, the RS-232 port runs at 9.6 Kbps without any flow control. The front access LAN port and RJ-45 EMS LAN port can be provisioned with different IP addresses by configuring the TSC card in secure mode using CTC. On 15454 M2, the EMS port is on the power module. On 15454 M6, the EMS port is on the ECU. 2.7.1.6 External Alarms and Controls The TSC card provides customer-defined (environmental) alarms and external controls on the ONS 15454 M6 shelf. The card provides input/output alarm contact closures. The TSC card operates in two modes: • External alarms mode - This is the default mode and up to 14 alarm input ports can be configured. External alarms (input contacts) are typically used for external sensors such as open doors, temperature sensors, flood sensors, and other environmental conditions. • External control mode - Up to 10 alarm input ports and four alarm output ports can be configured. External controls (output contacts) are typically used to drive visual or audible devices such as bells and lights, but they can control other devices such as generators, heaters, and fans. To configure the external alarms and external controls, go to Provisioning -> Alarm Extenders tab in the CTC node view. To view the external alarms and external controls, go to Maintenance -> Alarm Extenders tab in the CTC node view. For information on how to configure and view the external alarms and external controls, refer chapter “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. Note The LCD module must be present in the ONS 15454 M6 shelf assembly to provision alarms from the ECU, fan-tray assembly, or power modules. For information on pinouts of external alarms and external controls, see the “ONS 15454 ANSI Alarm, Timing, LAN, and Craft Pin Connections” section in the Cisco ONS 15454 Hardware Installation Guide.2-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card 2.7.1.7 Digital Image Signing (DIS) The TSC card provides services that authenticate the origin of the software running on the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms. For more information, see the 2.8 Digital Image Signing, page 2-33 section. 2.7.2 Faceplate and Block Diagram The faceplate design of the TSC card allows sufficient space to insert or remove cables while accessing the Ethernet ports. The TSC card can be installed only in slots 1 or 8 of the 15454-M6 shelf and in slot 1 of the 15454-M2 shelf. The TSC card has an identifier on the faceplate that matches with an identifier in the shelf. A key is also provided on the backplane interface connectors as identifier in the shelf. The TSC card supports field-programmable gate array (FPGA) for the backplane interface. The TSC card has two FPGA: TCCA and SYNTIDE. Figure 2-6 illustrates the faceplate and block diagram for the TSC card. Figure 2-6 TSC Faceplate and Block Diagram TSC FAIL ACT/STBY CRIT REM MAJ SYNC MIN ACO ACO PWR A B LAMP TEST EIA/TIA-232 TCP/IP LINK ACT 256MB DDR2 Mini-DIMM CPU MPC8568E GE Phy GE Phy BusMux CPLD Ethernet Switch Local Ethernet Switch External Glue Logic CPLD SYNTIDE FPGA Boot Flash USB Controller TCCA FPGA T1/E1 Framers LOG NVRAM 256MB Compact Flash 2778562-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card 2.7.3 Lamp Test The TSC card supports a lamp test function that is activated by pressing the Lamp Test button on the faceplate or from CTC. The lamp test function allows the user to test the working state of LEDs and ensures that all LEDs are functional. When you activate the lamp test function, all the port LEDs illuminate simultaneously for several seconds. 2.7.4 TSC Card Installation (ONS 15454 M6) On the ONS 15454 M6 shelf, the TSC card operates in either simplex or duplex (redundant) control mode. In redundant control mode, high availability is achieved. When a redundant TSC card is inserted into a node, it synchronizes its software, backup software, and database with the active TSC card. If the software versions do not match, the redundant TSC card copies from the active TSC card, taking about 15 to 20 minutes to complete. If the software versions match, the redundant TSC card copies the backup software from the active TSC card, taking about 15 to 20 minutes. Copying the database from the active TSC card takes about 3 minutes. Depending on the software version and backup version the redundant TSC card started with, the entire process can take between 3 and 40 minutes. 2.7.5 Card-Level Indicators The TSC faceplate has twelve LEDs. Table 2-11 describes the two card-level LEDs on the TSC faceplate. 2.7.6 Network-Level Indicators Table 2-12 describes the six network-level LEDs on the TSC faceplate. Table 2-16 TSC Card-Level Indicators Card-Level LEDs Definition Red FAIL LED Indicates the TSC card is in fail mode. The FAIL LED flashes during the boot and write process. Replace the card if the FAIL LED persists. ACT/STBY LED Green (Active) Amber (Standby) Indicates the TSC card is active (green) or in standby (amber) mode. The ACT/STBY LED also provides the timing reference and shelf control. When the active TSC is writing to its database or to the standby TSC database, the card LEDs blink. To avoid memory corruption, do not remove the TSC card when the active or standby LED is blinking.2-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card 2.7.7 Power-Level Indicators Table 2-13 describes the two power-level LEDs on the TSC faceplate. Table 2-17 TSC Network-Level Indicators System-Level LEDs Definition Red CRIT LED Indicates critical alarms in the network at the local terminal. Red MAJ LED Indicates major alarms in the network at the local terminal. Yellow MIN LED Indicates minor alarms in the network at the local terminal. Red REM LED Provides first-level alarm isolation. The remote (REM) LED turns red when a critical, major, or minor alarm is present in one or more of the remote terminals. Green SYNC LED Indicates the synchronization status; Indicates that node timing is synchronized to an external reference. Green ACO LED Indicates the Alarm Cut-Off status. After pressing the ACO button, the ACO LED turns green. The ACO button opens the audible alarm closure on the backplane. ACO is stopped if a new alarm occurs. After the originating alarm is cleared, the ACO LED and audible alarm control are reset.2-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards TSC Card 2.7.8 Ethernet Port Indicators Table 2-14 describes the two port-level LEDs on the TSC faceplate. 2.7.9 Protection Schemes The TSC card supports active and redundant architecture. The ONS 15454 M6 shelf supports 1:1 equipment protection with one TSC card acting as active and the other TSC card as redundant. The 15454-M2 shelf supports simplex control mode. In this mode, the active TSC card operates without a redundant TSC card. The 15454-M6 shelf supports both simplex and redundant control mode. In redundant control mode, the active TSC card operates with a redundant TSC card as the backup. If the active TSC card is removed, system traffic switches to the redundant TSC card. If the redundant TSC card is not present or not in the standby state, removing the active TSC card results in loss of system traffic and management connectivity. Table 2-18 TSC Power-Level Indicators Power-Level LEDs Definition Green/Red PWR A LED Indicates the status of power to the card. 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. The LED is red when the voltage on supply input A is above high battery voltage/extremely high battery voltage (EHIBATVG ) or below low battery voltage/extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input A is 0. Green/Red PWR B LED Indicates the status of power to the card. The PWR B LED is green when the voltage on supply input B is between the low battery voltage and high battery voltage thresholds. The LED is red when the voltage on supply input B is above high battery voltage/extremely high battery (EHIBATVG ) voltage or below low battery voltage/extremely low battery voltage (ELWBATVG) thresholds. The LED is red when the voltage on supply input B is 0. Table 2-19 TSC Port-Level Indicators Port-Level LEDs Definition Green LINK LED Indicates the connectivity status. Amber ACT LED Indicates the data reception.2-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Digital Image Signing In redundant control mode, a TSC card can protect another TSC card. However, a TSC card cannot protect a TNC card or vice versa. 2.7.10 Cards Supported by TSC The TSC card supports 15454 MSTP line cards except the following cards: • OSCM • ISC • AIC • AIC-I The TSC card is not interoperable with TCC2 /TCC2P/TCC3 cards. The TSC and TCC cards cannot be inserted in the same shelf. The line cards such as Transponder and Muxponder cards can be inserted in the 15454-M2 and 15454-M6 shelves along with the TSC card. 2.8 Digital Image Signing (Cisco ONS 15454 M2 and ONS 15454 M6 only) The DIS feature complies with the new U.S. Government Federal Information Processing Standard (FIPS) 140-3 to provide security for all software provided on the Cisco ONS 15454 M6 and ONS 15454 M2 platforms. This standard requires software to be digitally signed and verified for authenticity and integrity prior to load and execution. DIS feature automatically provides increased protection. DIS focuses on software security and provides increased protection from attacks and threats to Cisco ONS 15454 M2 and ONS 15454 M6 products. DIS verifies software integrity and provides assurance that the software has not been tampered with or modified. Digitally signed Cisco software provides counterfeit protection. New controller cards, such as TNC/TSC, provide services that authenticate the origin of the software running on the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms. The signage and verification process is transparent until verification fails. 2.8.1 DIS Identification Digitally signed software can be identified by the last three characters appended to the working version and protected version field in CTC. The DIS conventions can be viewed under the working version displayed in the Maintenance > Software tab in CTC. For example, 9.2.0 (09.20-X10C-29.09-SDA) and 9.2.0 (09.20-010C-18.18-SPA).2-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards AIC-I Card The significance of the three characters appended to the software version is explained in Table: For information on how to retrieve and view DIS information in CTC please refer to the “Turn Up a Node” Chapter in the Cisco ONS 15454 DWDM Procedure Guide, 9.2. 2.9 AIC-I Card (Cisco ONS 15454 only) Note For hardware specifications, see the “A.3.6 AIC-I Card Specifications” section on page A-8. The optional Alarm Interface Controller–International (AIC-I) card provides customer-defined (environmental) alarms and controls and supports local and express orderwire. It provides 12 customer-defined input and 4 customer-defined input/output contacts. The physical connections are via the backplane wire-wrap pin terminals. If you use the additional alarm expansion panel (AEP), the AIC-I card can support up to 32 inputs and 16 outputs, which are connected on the AEP connectors. The AEP is compatible with ANSI shelves only. A power monitoring function monitors the supply voltage (–48 VDC). Figure 2-7 shows the AIC-I faceplate and a block diagram of the card. Table 2-20 DIS Conventions in the Software Version Character Meaning S (first character) Indicates that the package is signed. P or D (second character) Production (P) or Development (D) image. Production image—Software approved for general release. Development image—development software provided under special conditions for limited use. A (third character) This third character indicates the version of the key used for signature generation. The version changes when a key is revoked and a new key is used. The values of the version key varies from A to Z.2-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards AIC-I Card Figure 2-7 AIC-I Faceplate and Block Diagram 2.9.1 AIC-I Card-Level Indicators Table 2-21 describes the eight card-level LEDs on the AIC-I card faceplate. AIC-I Fail Express orderwire Local orderwire EEPROM LED x2 AIC-I FPGA SCL links 4 x IN/OUT Power Monitoring 12/16 x IN Ringer Act Ring Ring Input Output 78828 FAIL ACT ACC INPUT/OUTPUT EOW LOW RING AIC-1 (DTMF) (DTMF) UDC-A UDC-B DCC-A DCC-B ACC PWR A B RING DCC-B DCC-A UDC-B UDC-A Table 2-21 AIC-I Card-Level Indicators Card-Level LEDs Description Red FAIL LED Indicates that the card’s processor is not ready. The FAIL LED is on during reset and flashes during the boot process. Replace the card if the red FAIL LED persists. Green ACT LED Indicates the AIC-I card is provisioned for operation.2-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards AIC-I Card 2.9.2 External Alarms and Controls The AIC-I card provides input/output alarm contact closures. You can define up to 12 external alarm inputs and 4 external alarm inputs/outputs (user configurable). The physical connections are made using the backplane wire-wrap pins or FMEC connections. For information about increasing the number of input/output contacts, see the “ONS 15454 ANSI Alarm Expansion Panel” section in the Cisco ONS 15454 Hardware Installation Guide. LEDs on the front panel of the AIC-I indicate the status of the alarm lines, one LED representing all of the inputs and one LED representing all of the outputs. External alarms (input contacts) are typically used for external sensors such as open doors, temperature sensors, flood sensors, and other environmental conditions. External controls (output contacts) are typically used to drive visual or audible devices such as bells and lights, but they can control other devices such as generators, heaters, and fans. You can program each of the twelve input alarm contacts separately. You can program each of the sixteen input alarm contacts separately. Choices include: • Alarm on Closure or Alarm on Open • Alarm severity of any level (Critical, Major, Minor, Not Alarmed, Not Reported) • Service Affecting or Non-Service Affecting alarm-service level • 63-character alarm description for CTC display in the alarm log You cannot assign the fan-tray abbreviation for the alarm; the abbreviation reflects the generic name of the input contacts. The alarm condition remains raised until the external input stops driving the contact or you provision the alarm input. 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. 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. It is red when the input voltage on supply input B is out of range. Yellow INPUT LED The INPUT LED is yellow when there is an alarm condition on at least one of the alarm inputs. Yellow OUTPUT LED The OUTPUT LED is yellow when there is an alarm condition on at least one of the alarm outputs. Green RING LED The RING LED on the local orderwire (LOW) side is flashing green when a call is received on the LOW. Green RING LED The RING LED on the express orderwire (EOW) side is flashing green when a call is received on the EOW. Table 2-21 AIC-I Card-Level Indicators (continued) Card-Level LEDs Description2-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards AIC-I Card • Remote NE alarm severity: Same as the local NE alarm severity but applies to remote alarms only. • Virtual wire entities: You can provision any environmental alarm input to raise a signal on any virtual wire on external outputs 1 through 4 when the alarm input is an event. You can provision a signal on any virtual wire as a trigger for an external control output. You can also program the output alarm contacts (external controls) separately. In addition to provisionable triggers, you can manually force each external output contact to open or close. Manual operation takes precedence over any provisioned triggers that might be present. Note For ANSI shelves, the number of inputs and outputs can be increased using the AEP. The AEP is connected to the shelf backplane and requires an external wire-wrap panel. 2.9.3 Orderwire Orderwire allows a craftsperson to plug a phoneset into an ONS 15454 and communicate with craftspeople working at other ONS 15454s or other facility equipment. The orderwire is a pulse code modulation (PCM) encoded voice channel that uses E1 or E2 bytes in section/line overhead. The AIC-I allows simultaneous use of both local (section overhead signal) and express (line overhead channel) orderwire channels on a SONET/SDH ring or particular optics facility. Express orderwire also allows communication via regeneration sites when the regenerator is not a Cisco device. You can provision orderwire functions with CTC similar to the current provisioning model for DCC/GCC channels. In CTC, you provision the orderwire communications network during ring turn-up so that all NEs on the ring can reach one another. Orderwire terminations (that is, the optics facilities that receive and process the orderwire channels) are provisionable. Both express and local orderwire can be configured as on or off on a particular SONET/SDH facility. The ONS 15454 supports up to four orderwire channel terminations per shelf. This allows linear, single ring, dual ring, and small hub-and-spoke configurations. Orderwire is not protected in ring topologies such as bidirectional line switched ring (BLSR), multiplex section-shared protection ring (MS-SPRing), path protection, or subnetwork connection protection (SNCP) ring. Caution Do not configure orderwire loops. Orderwire loops cause feedback that disables the orderwire channel. The ONS 15454 implementation of both local and express orderwire is broadcast in nature. The line acts as a party line. Anyone who picks up the orderwire channel can communicate with all other participants on the connected orderwire subnetwork. The local orderwire party line is separate from the express orderwire party line. Up to four OC-N/STM-N facilities for each local and express orderwire are provisionable as orderwire paths. 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. Individual dialing is initiated by pressing * and the individual four-digit number on the DTMF pad. Table 2-22 shows the pins on the orderwire connector that correspond to the tip and ring orderwire assignments. 2-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards AIC-I Card When provisioning the orderwire subnetwork, make sure that an orderwire loop does not exist. Loops cause oscillation and an unusable orderwire channel. Figure 2-8 shows the standard RJ-11 connectors used for orderwire ports. Figure 2-8 RJ-11 Connector 2.9.4 Power Monitoring The AIC-I card provides a power monitoring circuit that monitors the supply voltage of –48 VDC for presence, undervoltage, and overvoltage. 2.9.5 User Data Channel The user data channel (UDC) features a dedicated data channel of 64 kbps (F1 byte) between two nodes in an ONS 15454 network. Each AIC-I card provides two user data channels, UDC-A and UDC-B, through separate RJ-11 connectors on the front of the AIC-I card. Each UDC can be routed to an individual optical interface in the ONS 15454. For instructions, see the Cisco ONS 15454 DWDM Procedure Guide. The UDC ports are standard RJ-11 receptacles. Table 2-23 lists the UDC pin assignments. Table 2-22 Orderwire Pin Assignments RJ-11 Pin Number Description 1 Four-wire receive ring 2 Four-wire transmit tip 3 Two-wire ring 4 Two-wire tip 5 Four-wire transmit ring 6 Four-wire receive tip 61077 Pin 1 Pin 6 RJ-11 Table 2-23 UDC Pin Assignments RJ-11 Pin Number Description 1 For future use 2 TXN 3 RXN2-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards MS-ISC-100T Card 2.9.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 data communications channels, DCC-A and DCC-B, through separate RJ-45 connectors on the front of the AIC-I card. Each DCC can be routed to an individual optical interface in the ONS 15454. For instructions, see the Cisco ONS 15454 DWDM Procedure Guide. The DCC ports are synchronous serial interfaces. The DCC ports are standard RJ-45 receptacles. Table 2-24 lists the DCC pin assignments. 2.10 MS-ISC-100T Card (Cisco ONS 15454 only) Note For hardware specifications, see the “A.3.10 MS-ISC-100T Card Specifications” section on page A-11. The Multishelf Internal Switch Card (MS-ISC-100T) is an Ethernet switch used to implement the multishelf LAN. It connects the node controller shelf to the network and to subtending shelves. The MS-ISC-100T must always be equipped on the node controller shelf; it cannot be provisioned on a subtending controller shelf. The recommended configuration is to implement LAN redundancy using two MS-ISC-100T cards: one switch is connected to the Ethernet front panel port of the TCC2/TCC2P card in Slot 7, and the other switch is connected to the Ethernet front panel port of the TCC2/TCC2P card in Slot 11. The Ethernet 4 RXP 5 TXP 6 For future use Table 2-23 UDC Pin Assignments (continued) RJ-11 Pin Number Description Table 2-24 DCC Pin Assignments RJ-45 Pin Number Description 1 TCLKP 2 TCLKN 3 TXP 4 TXN 5 RCLKP 6 RCLKN 7 RXP 8 RXN2-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards MS-ISC-100T Card configuration of the MS-ISC-100T card is part of the software package and is automatically loaded. The MS-ISC-100T card operates in Slots 1 to 6 and 12 to 17 on the node controller shelf; the recommended slots are Slot 6 and Slot 12. Table 2-25 lists the MS-ISC-100T port assignments. Figure 2-9 shows the card faceplate. Caution Shielded twisted-pair cabling should be used for interbuilding applications. Table 2-25 MS-ISC-100T Card Port Assignments Port Description DCN 1and DCN 2 Connection to the network SSC1 to SSC7 Connection to subtending shelves NC Connection to TCC2/TCC2P using a cross-over cable PRT Connection to the PRT port of the redundant MS-ISC-100T2-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards MS-ISC-100T Card Figure 2-9 MS-ISC-100T Faceplate 2.10.1 MS-ISC-100T Card-Level Indicators The MS-ISC-100T card supports two card-level LED indicators. The card-level indicators are described in Table 2-26. FAIL ACT MS ISC 100T CONSOLE 145274 DC2 SSC1 SSC2 SSC3 SSC4 SSC5 SSC6 SSC7 NC PRT DCN12-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Front Mount Electrical Connections 2.11 Front Mount Electrical Connections This section describes the MIC-A/P and MIC-C/T/P FMECs, which provide power, external alarm, and timing connections for the ONS 15454 ETSI shelf. 2.11.1 MIC-A/P FMEC Note For hardware specifications, see the “A.3.8 MIC-A/P FMEC Specifications (ETSI only)” section on page A-10. The MIC-A/P FMEC provides connection for the BATTERY B input, one of the two possible redundant power supply inputs. It also provides connection for eight alarm outputs (coming from the TCC2/TCC2P card), sixteen alarm inputs, and four configurable alarm inputs/outputs. Its position is in Slot 23 in the center of the subrack Electrical Facility Connection Assembly (EFCA) area. The MIC-A/P FMEC has the following features: • Connection for one of the two possible redundant power supply inputs • Connection for eight alarm outputs (coming from the TCC2/TCC2P card) • Connection for four configurable alarm inputs/outputs • Connection for sixteen alarm inputs • Storage of manufacturing and inventory data For proper system operation, both the MIC-A/P and MIC-C/T/P FMECs must be installed in the ONS 15454 ETSI shelf. Figure 2-10 shows the MIC-A/P faceplate. Figure 2-10 MIC-A/P Faceplate Figure 2-11 shows a block diagram of the MIC-A/P. Table 2-26 MS-ISC-100T 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 card. If the ACT LED is green, it indicates that the card is active and the software is operational. MIC-A/P ALARM IN/OUT CLEI CODE BARCODE POWER RATING GND CAUT BATTERY B ION TIGHTEN THE FACEPLATE GHTEN THE FACEPLATE SCREWS WITH 1.0 NM TORQUE SCREWS WITH 1.0 NM TORQUE 2713052-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Front Mount Electrical Connections Figure 2-11 MIC-A/P Block Diagram Table 2-27 shows the alarm interface pinouts on the MIC-A/P DB-62 connector. Inventory Data (EEPROM) 61332 B a c k p l a n e 3W3 Connector Alarms DB62 Connector Power 16 Alarm inputs 4 Alarm in/outputs Table 2-27 Alarm Interface Pinouts on the MIC-A/P DB-62 Connector Pin No. Signal Name Signal Description 1 ALMCUTOFF N Alarm cutoff, normally open ACO pair 2 ALMCUTOFF P Alarm cutoff, normally open ACO pair 3 ALMINP0 N Alarm input pair 1, reports closure on connected wires 4 ALMINP0 P Alarm input pair 1, reports closure on connected wires 5 ALMINP1 N Alarm input pair 2, reports closure on connected wires 6 ALMINP1 P Alarm input pair 2, reports closure on connected wires 7 ALMINP2 N Alarm input pair 3, reports closure on connected wires 8 ALMINP2 P Alarm input pair 3, reports closure on connected wires 9 ALMINP3 N Alarm input pair 4, reports closure on connected wires 10 ALMINP3 P Alarm input pair 4, reports closure on connected wires 11 EXALM0 N External customer alarm 1 12 EXALM0 P External customer alarm 1 13 GND Ground 14 EXALM1 N External customer alarm 2 15 EXALM1 P External customer alarm 2 16 EXALM2 N External customer alarm 3 17 EXALM2 P External customer alarm 3 18 EXALM3 N External customer alarm 4 19 EXALM3 P External customer alarm 4 20 EXALM4 N External customer alarm 5 21 EXALM4 P External customer alarm 5 22 EXALM5 N External customer alarm 6 23 EXALM5 P External customer alarm 6 24 EXALM6 N External customer alarm 7 25 EXALM6 P External customer alarm 72-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Front Mount Electrical Connections 26 GND Ground 27 EXALM7 N External customer alarm 8 28 EXALM7 P External customer alarm 8 29 EXALM8 N External customer alarm 9 30 EXALM8 P External customer alarm 9 31 EXALM9 N External customer alarm 10 32 EXALM9 P External customer alarm 10 33 EXALM10 N External customer alarm 11 34 EXALM10 P External customer alarm 11 35 EXALM11 N External customer alarm 12 36 EXALM11 P External customer alarm 12 37 ALMOUP0 N Normally open output pair 1 38 ALMOUP0 P Normally open output pair 1 39 GND Ground 40 ALMOUP1 N Normally open output pair 2 41 ALMOUP1 P Normally open output pair 2 42 ALMOUP2 N Normally open output pair 3 43 ALMOUP2 P Normally open output pair 3 44 ALMOUP3 N Normally open output pair 4 45 ALMOUP3 P Normally open output pair 4 46 AUDALM0 N Normally open Minor audible alarm 47 AUDALM0 P Normally open Minor audible alarm 48 AUDALM1 N Normally open Major audible alarm 49 AUDALM1 P Normally open Major audible alarm 50 AUDALM2 N Normally open Critical audible alarm 51 AUDALM2 P Normally open Critical audible alarm 52 GND Ground 53 AUDALM3 N Normally open Remote audible alarm 54 AUDALM3 P Normally open Remote audible alarm 55 VISALM0 N Normally open Minor visual alarm 56 VISALM0 P Normally open Minor visual alarm 57 VISALM1 N Normally open Major visual alarm 58 VISALM1 P Normally open Major visual alarm 59 VISALM2 N Normally open Critical visual alarm 60 VISALM2 P Normally open Critical visual alarm Table 2-27 Alarm Interface Pinouts on the MIC-A/P DB-62 Connector (continued) Pin No. Signal Name Signal Description2-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Front Mount Electrical Connections 2.11.2 MIC-C/T/P FMEC Note For hardware specifications, see the “A.3.9 MIC-C/T/P FMEC Specifications (ETSI only)” section on page A-10. The MIC-C/T/P FMEC provides connection for the BATTERY A input, one of the two possible redundant power supply inputs. It also provides connection for system management serial port, system management LAN port, modem port (for future use), and system timing inputs and outputs. Install the MIC-C/T/P in Slot 24. The MIC-C/T/P FMEC has the following features: • Connection for one of the two possible redundant power supply inputs • Connection for two serial ports for local craft/modem (for future use) • Connection for one LAN port • Connection for two system timing inputs • Connection for two system timing outputs • Storage of manufacturing and inventory data For proper system operation, both the MIC-A/P and MIC-C/T/P FMECs must be installed in the shelf. Figure 2-12 shows the MIC-C/T/P FMEC faceplate. Figure 2-12 MIC-C/T/P Faceplate Figure 2-13 shows a block diagram of the MIC-C/T/P. 61 VISALM3 N Normally open Remote visual alarm 62 VISALM3 P Normally open Remote visual alarm Table 2-27 Alarm Interface Pinouts on the MIC-A/P DB-62 Connector (continued) Pin No. Signal Name Signal Description MIC-C/T/P CLEI CODE BARCODE POWER RATING GND T BATTERY A IMING A IN TIMING B OUT CAUTION TIGHTEN THE FACEPLATE GHTEN THE FACEPLATE SCREWS WITH 1.0 NM TORQUE SCREWS WITH 1.0 NM TORQUE 271306 LAN AUX TERM L ACT INK2-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 2 Common Control Cards Front Mount Electrical Connections Figure 2-13 MIC-C/T/P Block Diagram The MIC-C/T/P FMEC has one pair of LEDs located on the RJ45 LAN connector. The green LED is on when a link is present, and the amber LED is on when data is being transferred. Inventory Data (EEPROM) 61334 B a c k p l a n e 3W3 connector Power RJ-45 connectors System management serial ports RJ-45 connectors System management LAN 4 coaxial connectors Timing 2 x in / 2 x outCHAPTER 3-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 3 Optical Service Channel Cards This chapter describes the optical service channel (OSC) cards for Cisco ONS 15454 dense wavelength division multiplexing (DWDM) networks. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note Unless noted otherwise, the cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 3.1 Card Overview, page 3-1 • 3.2 Class 1 Laser Safety Labels, page 3-3 • 3.3 OSCM Card, page 3-5 • 3.4 OSC-CSM Card, page 3-9 3.1 Card Overview This section provides card summary and compatibility information. 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. For a list of slots and symbols, see the “Card Slot Requirements” section in the Cisco ONS 15454 Hardware Installation Guide. An optical service channel (OSC) is a bidirectional channel connecting two adjacent nodes in a DWDM ring. For every DWDM node (except terminal nodes), two different OSC terminations are present, one for the west side and another for the east side. The channel transports OSC overhead that is used to manage ONS 15454 DWDM networks. An OSC signal uses the 1510-nm wavelength and does not affect client traffic. The primary purpose of this channel is to carry clock synchronization and orderwire channel communications for the DWDM network. It also provides transparent links between each node in the network. The OSC is an OC-3/STM-1 formatted signal. 3-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards Card Overview There are two versions of the OSC modules: the OSCM, and the OSC-CSM, which contains the OSC wavelength combiner and separator component in addition to the OSC module. The Mesh/Multiring Upgrade (MMU) card is used to optically bypass a given wavelength from one section of the network or ring to another one without requiring 3R regeneration. Note On 15454-M2 and 15454-M6 shelves, the TNC card includes the functions of the OSCM card. OSC can be created on the OC3 port (SFP-0) of the TNC card. The TNC card supports two optical service channels (OSC): primary OSC and secondary OSC. The primary optical service channel (SFP-0) supports the following interfaces: • OC-3/STM-1 • Fast Ethernet (FE) • Gigabit Ethernet (GE). The secondary optical service channel (SFP-1) supports the following interfaces: • Fast Ethernet (FE) • Gigabit Ethernet (GE). 3.1.1 Card Summary Table 3-1 lists and summarizes the functions of each card. 3.1.2 Card Compatibility Table 3-2 lists the CTC software compatibility for the OSC and OSCM cards. Table 3-1 OSCM, OSC-CSM, and MMU Card Summary Card Port Description For Additional Information OSCM The OSCM has one set of optical ports and one Ethernet port located on the faceplate. It operates in Slots 8 and 10. See the “3.3 OSCM Card” section on page 3-5. OSC-CSM The OSC-CSM has three sets of optical ports and one Ethernet port located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “3.4 OSC-CSM Card” section on page 3-9. Table 3-2 Software Release Compatibility for Optical Service Channel Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.2 OSCM Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes OSC-CS M Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes3-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards Class 1 Laser Safety Labels 3.2 Class 1 Laser Safety Labels This section explains the significance of the safety labels attached to the OSCM and OSC-CSM cards. The faceplates of the cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. 3.2.1 Class 1 Laser Product Label The Class 1 Laser Product label is shown in Figure 3-1. Figure 3-1 Class 1 Laser Product Label Class 1 lasers are products whose irradiance does not exceed the Maximum Permissible Exposure (MPE) value. Therefore, for Class 1 laser products the output power is below the level at which it is believed eye damage will occur. Exposure to the beam of a Class 1 laser will not result in eye injury and may therefore be considered safe. However, some Class 1 laser products may contain laser systems of a higher Class but there are adequate engineering control measures to ensure that access to the beam is not reasonably likely. Anyone who dismantles a Class 1 laser product that contains a higher Class laser system is potentially at risk of exposure to a hazardous laser beam 3.2.2 Hazard Level 1 Label The Hazard Level 1 label is shown in Figure 3-2. Figure 3-2 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. This label is displayed on the faceplate of the cards. 3.2.3 Laser Source Connector Label The Laser Source Connector label is shown in Figure 3-3. CLASS 1 LASER PRODUCT 145952 HAZARD LEVEL 1 655423-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards Class 1 Laser Safety Labels Figure 3-3 Laser Source Connector Label This label indicates that a laser source is present at the optical connector where the label has been placed. 3.2.4 FDA Statement Label The FDA Statement labels are shown in Figure 3-4 and Figure 3-5. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 3-4 FDA Statement Label Figure 3-5 FDA Statement Label 3.2.5 Shock Hazard Label The Shock Hazard label is shown in Figure 3-6. 96635 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 20073-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSCM Card Figure 3-6 Shock Hazard Label This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself. This section describes the optical service channel cards. An optical service channel (OSC) is a bidirectional channel connecting two adjacent nodes in a DWDM ring. For every DWDM node (except terminal nodes), two different OSC terminations are present, one for the west side and another for the east side. The channel transports OSC overhead that is used to manage ONS 15454 DWDM networks. An OSC signal uses the 1510-nm wavelength and does not affect client traffic. The primary purpose of this channel is to carry clock synchronization and orderwire channel communications for the DWDM network. It also provides transparent links between each node in the network. The OSC is an OC-3/STM-1 formatted signal. There are two versions of the OSC modules: the OSCM, and the OSC-CSM, which contains the OSC wavelength combiner and separator component in addition to the OSC module. 3.3 OSCM Card (Cisco ONS 15454 only) Note For OSCM card specifications, see the “A.4.1 OSCM Card Specifications” section on page A-11. Note On 15454-M2 and 15454-M6 shelves, the TNC card includes the functions of the OSCM card. The OSCM card is used in amplified nodes that include the OPT-BST, OPT-BST-E, or OPT-BST-L booster amplifier. The OPT-BST, OPT-BST-E, and OPT-BST-L cards include the required OSC wavelength combiner and separator component. The OSCM cannot be used in nodes where you use OC-N/STM-N cards, electrical cards, or cross-connect cards. The OSCM uses Slots 8 and 10, which are also cross-connect card slots. The OSCM supports the following features: • OC-3/STM-1 formatted OSC • Supervisory data channel (SDC) forwarded to the TCC2/TCC2P/TCC3 cards for processing • Distribution of the synchronous clock to all nodes in the ring • 100BaseT far-end (FE) User Channel (UC) • Monitoring functions such as orderwire support and optical safety 655413-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSCM Card The OC-3/STM-1 section data communications channel (SDCC or RS-DCC) overhead bytes are used for network communications. An optical transceiver terminates the OC-3/STM-1, then it is regenerated and converted into an electrical signal. The SDCC or RS-DCC bytes are forwarded to the active and standby TCC2/TCC2P/TCC3 cards for processing through the system communication link (SCL) bus on the backplane. Orderwire bytes (E1, E2, F1) are also forwarded via the SCL bus to the TCC2/TCC2P/TCC3 for forwarding to the AIC-I card. The payload portion of the OC-3/STM-1 is used to carry the fast Ethernet UC. The frame is sent to a packet-over-SONET/SDH (POS) processing block that extracts the Ethernet packets and makes them available at the RJ-45 connector. The OSCM distributes the reference clock information by removing it from the incoming OC-3/STM-1 signal and then sending it to the DWDM cards. The DWDM cards then forward the clock information to the active and standby TCC2/TCC2P/TCC3 cards.3-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSCM Card Figure 3-7 shows the OSCM card faceplate and block diagram. Figure 3-7 OSCM Card Faceplate For information on safety labels for the card, see the “3.2 Class 1 Laser Safety Labels” section on page 3-3. Figure 3-8 shows the block diagram of the variable optical attenuator (VOA) within the OSCM. OSCM FAIL ACT SF UC RX TX 96464 ASIC OC3-ULR Optical transceiver OSC Line OC-3 FPGA OC-12 POS OC-3 MII 145944 Processor VOA Physical Interface DC/DC 19.44 MHz Line Ref clock Power supply Input filters MT CLKt BAT A&B 0 Slot 1-6 MT CLKt 0 Slot 12-17 6 M P SCL Bus to TCCs FE FE User Channel 6 TOH & Cell Bus3-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSCM Card Figure 3-8 OSCM VOA Optical Module Functional Block Diagram 3.3.1 Power Monitoring Physical photodiode P1 monitors the power for the OSCM card. The returned power level value is calibrated to the OSC TX port (Table 3-3). For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 3.3.2 OSCM Card-Level Indicators The OSCM card has three card-level LED indicators, described in Table 3-4. P1 P1 OSC TX Physical photodiode OSC Variable optical attenuator Control Module OSC RX Control Interface 124968 Table 3-3 OSCM VOA Port Calibration Photodiode CTC Type Name Calibrated to Port P1 Output OSC OSC TX Table 3-4 OSCM Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists.3-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card 3.3.3 OSCM Port-Level Indicators You can find the status of the card ports 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. The OSCM has one OC-3/STM-1 optical port located on the faceplate. One long-reach OSC transmits and receives the OSC to and from another DWDM node. Both DCN data and FE payload are carried on this link. 3.4 OSC-CSM Card Note For OSC-CSM card specifications, see the “A.4.2 OSC-CSM Card Specifications” section on page A-12. The OSC-CSM card is used in unamplified nodes. This means that the booster amplifier with the OSC wavelength combiner and separator is not required for OSC-CSM operation. The OSC-CSM can be installed in Slots 1 to 6 and 12 to 17. To operate in hybrid mode, the OSC-CSM cards must be accompanied by cross-connect cards. The cross-connect cards enable functionality on the OC-N/STM-N cards and electrical cards. The OSC-CSM supports the following features: • Optical combiner and separator module for multiplexing and demultiplexing the optical service channel to or from the wavelength division multiplexing (WDM) signal • OC-3/STM-1 formatted OSC • SDC forwarded to the TCC2/TCC2P/TCC3 cards for processing • Distribution of the synchronous clock to all nodes in the ring • 100BaseT FE UC • Monitoring functions such as orderwire support • Optical safety: Signal loss detection and alarming, fast transmitted power shut down by means of an optical 1x1 switch • Optical safety remote interlock (OSRI), a feature capable of shutting down the optical output power Green ACT LED The green ACT LED indicates that the OSCM is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as loss of signal (LOS), loss of frame alignment (LOF), line alarm indication signal (AIS-L), or high BER on one or more of the card’s ports. The amber signal fail (SF) LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off. Table 3-4 OSCM Card-Level Indicators (continued) Card-Level Indicators Description3-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card • Automatic laser shutdown (ALS), a safety mechanism used in the event of a fiber cut. For details on ALS provisioning for the card, see the Cisco ONS 15454 DWDM Procedure Guide. For information on using the card to implement ALS in a network, see the “12.11 Network Optical Safety” section on page 12-27. The WDM signal coming from the line is passed through the OSC combiner and separator, where the OSC signal is extracted from the WDM signal. The WDM signal is sent along with the remaining channels to the COM port (label on the front panel) for routing to the OADM or amplifier units, while the OSC signal is sent to an optical transceiver. The OSC is an OC-3/STM-1 formatted signal. The OC-3/STM-1 SDCC or RS-DCC overhead bytes are used for network communications. An optical transceiver terminates the OC-3/STM-1, and then it is regenerated and converted into an electrical signal. The SDCC or RS-DCC bytes are forwarded to the active and standby TCC2/TCC2P/TCC3 cards for processing via the SCL bus on the backplane. Orderwire bytes (E1, E2, F1) are also forwarded via the SCL bus to the TCC2/TCC2P/TCC3 for forwarding to the AIC-I card. The payload portion of the OC-3/STM-1 is used to carry the fast Ethernet UC. The frame is sent to a POS processing block that extracts the Ethernet packets and makes them available at the RJ-45 front panel connector. The OSC-CSM distributes the reference clock information by removing it from the incoming OC-3/STM-1 signal and then sending it to the active and standby TCC2/TCC2P/TCC3 cards. The clock distribution is different from the OSCM card because the OSC-CSM does not use Slot 8 or 10 (cross-connect card slots). Note S1 and S2 (Figure 3-11 on page 3-13) are optical splitters with a splitter ratio of 2:98. The result is that the power at the MON TX port is about 17 dB lower than the relevant power at the COM RX port, and the power at the MON RX port is about 20 dB lower than the power at the COM TX port. The difference is due to the presence of a tap coupler for the P1 photodiode.3-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card Figure 3-9 shows the OSC-CSM faceplate. Figure 3-9 OSC-CSM Faceplate For information on safety labels for the card, see the “3.2 Class 1 Laser Safety Labels” section on page 3-3. Figure 3-10 shows a block diagram of the OSC-CSM card. 96465 OSC CSM FAIL ACT SF UC RX MON TX RX COM TX RX LINE TX ASIC OC3-ULR Optical transceiver OSC combiner separator OSC Line COM OC-3 FPGA OC-12 POS OC-3 MII TOH & Cell Bus 145943 Processor Physical Interface DC/DC Power supply Input filters MPMP BAT A&B SCL Bus to TCCs RxClkRef FE User Channel3-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card Figure 3-10 OSC-CSM Block Diagram ASIC OC3-ULR Optical transceiver OSC combiner separator OSC Line COM OC-3 FPGA OC-12 POS OC-3 MII TOH & Cell Bus 96477 Processor Physical Interface DC/DC Power supply Input filters MPMP BAT A&B SCL Bus to TCCs RxClkRef FE User Data Channel3-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card Figure 3-11 shows the OSC-CSM optical module functional block diagram. Figure 3-11 OSC-CSM Optical Module Functional Block Diagram 3.4.1 Power Monitoring Physical photodiodes P1, P2, P3, and P5 monitor the power for the OSC-CSM card. Their function is as follows: • P1: The returned power value is calibrated to the LINE RX port, including the insertion loss of the previous filter (the reading of this power dynamic range has been brought backward towards the LINE RX output). • P2: The returned value is calibrated to the LINE RX port. • P3: The returned value is calibrated to the COM RX port. • P5: The returned value is calibrated to the OSC TX port, including the insertion loss of the subsequent filter. The returned power level values are calibrated to the ports as shown in Table 3-5. P P P P P V V 124897 MON RX MON TX COM TX OSC RX LINE TX COM RX LINE RX DROP section ADD section OSC TX Control Interface Filter Filter S1 P1 P2 P5 P4 PV1 PV2 P3 HW Switch Control Opt. Switch S2 Virtual photodiode Physical photodiode Variable optical attenuator P V Optical splitter Control3-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card The OSC power on the LINE TX is the same as the power reported from P5. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 3.4.2 Alarms and Thresholds Table 3-6 lists the alarms and its related thresholds for the OSC-CSM card. 3.4.3 OSC-CSM Card-Level Indicators The OSC-CSM card has three card-level LED indicators, described in Table 3-7. Table 3-5 OSC-CSM Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameters P1 Input Line LINE RX Channel Power Supported OSC Power P2 Input Line LINE RX OSC Power Supported P3 Input Com COM RX Channel Power Supported P5 Output OSC OSC TX OSC Power Supported Table 3-6 Alarms and Thresholds Port Alarms Thresholds LINE RX LOS None LOS-P LOS-P Fail Low LOS-O LOS-O Fail Low LINE TX None None OSC TX OPWR-DEG-HIGH OPWR-DEG-HIGH Th OPWR-DEG-LOW OPWR-DEG-LOW Th OPWR-FAIL-LOW OPWR-FAIL-LOW Th OSC RX None None COM TX None None COM RX LOS-P LOS-P Fail Low3-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM Card 3.4.4 OSC-CSM Port-Level Indicators You can find the status of the card ports 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. The OSC-CSM has a OC3 port and three other sets of ports located on the faceplate. Table 3-7 OSC-CSM Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OSC-CSM is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, AIS-L, or high BER on one or more of the card’s ports. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.3-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 3 Optical Service Channel Cards OSC-CSM CardCHAPTER 4-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 4 Optical Amplifier Cards This chapter describes the optical amplifier cards used in Cisco ONS 15454 dense wavelength division multiplexing (DWDM) networks. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 4.1 Card Overview, page 4-1 • 4.2 Class 1M Laser Safety Labels, page 4-5 • 4.3 OPT-PRE Amplifier Card, page 4-7 • 4.4 OPT-BST Amplifier Card, page 4-11 • 4.5 OPT-BST-E Amplifier Card, page 4-16 • 4.6 OPT-BST-L Amplifier Card, page 4-19 • 4.7 OPT-AMP-L Card, page 4-24 • 4.8 OPT-AMP-17-C Card, page 4-29 • 4.9 OPT-AMP-C Card, page 4-33 • 4.10 OPT-RAMP-C and OPT-RAMP-CE Cards, page 4-38 4.1 Card Overview This section provides summary and compatibility information for the optical amplifier cards. Note Each card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. Cards should be installed in slots that have the same symbols. For a list of slots and symbols, see the "Card Slot Requirements" section in the Cisco ONS 15454 Hardware Installation Guide. 4-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards Card Overview Optical amplifiers are used in amplified nodes (such as hub nodes), amplified OADM nodes, and line amplifier nodes. The nine types of ONS 15454 DWDM amplifiers are: • Optical Preamplifier (OPT-PRE) • Optical Booster amplifier (OPT-BST) • Optical Booster Enhanced amplifier (OPT-BST-E) • Optical Booster L-band amplifier (OPT-BST-L) • Optical L-band preamplifier (OPT-AMP-L) • Optical C-band amplifier (OPT-AMP-17-C). • Optical C-band high-gain high-power amplifier (OPT-AMP-C) • Optical C-band Raman amplifier (OPT-RAMP-C) • Optical C-band enhanced Raman amplifier (OPT-RAMP-CE) Optical amplifier card architecture includes an optical plug-in module with a controller that manages optical power, laser current, and temperature control loops. An amplifier also manages communication with the TCC2/TCC2P/TCC3/TNC/TSC card and operation, administration, maintenance, and provisioning (OAM&P) functions such as provisioning, controls, and alarms. 4.1.1 Applications Using CTC (CTC > Card > Provisioning), the following amplifiers can be configured as booster or preamplifiers: • OPT-AMP-C • OPT-AMP-17C • OPT-AMP-L • OPT-BST-E • OPT-BST The amplifier functions as a booster amplifier by default. The amplifier role is automatically configured when the CTP NE update configuration file is loaded in CTC. The amplifier role can also be manually modified. Note The OPT-BST and OPT-BST-E amplifiers are supported as preamplifiers in sites that are equipped with the OPT-RAMP-C card. In any other configuration, the OPT-BST and OPT-BST-E cards must be configured as a booster amplifier. For more information about the supported configurations and network topologies, see Chapter 11, “Node Reference” and Chapter 12, “Network Reference.” 4.1.2 Card Summary Table 4-1 lists and summarizes the functions of each optical amplifier card.4-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards Card Overview 4.1.3 Card Compatibility Table 4-2 lists the Cisco Transport Controller (CTC) software compatibility for each optical amplifier card. Table 4-1 Optical Amplifier Cards for the ONS 15454 Card Port Description For Additional Information OPT-PRE The OPT-PRE amplifier has five optical ports (three sets) located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “4.3 OPT-PRE Amplifier Card” section on page 4-7. OPT-BST The OPT-BST amplifier has four sets of optical ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “4.4 OPT-BST Amplifier Card” section on page 4-11. OPT-BST-E The OPT-BST-E amplifier has four sets of optical ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “4.5 OPT-BST-E Amplifier Card” section on page 4-16. OPT-BST-L The OPT-BST-L L-band amplifier has four sets of optical ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “4.6 OPT-BST-L Amplifier Card” section on page 4-19. OPT-AMP-L The OPT-AMP-L L-band preamplifier has five sets of optical ports located on the faceplate. It is a two-slot card that operates in Slots 1 to 6 and 12 to 17. See the “4.7 OPT-AMP-L Card” section on page 4-24. OPT-AMP-17-C The OPT-AMP-17-C C-band low-gain preamplifier/booster amplifier has four sets of optical ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “4.8 OPT-AMP-17-C Card” section on page 4-29. OPT-AMP-C The OPT-AMP-C C-band high-gain, high-power preamplifier/booster amplifier has five sets of optical ports located on the faceplate. It operates as a preamplifier when equipped and provisioned in Slots 2 to 6 and 11 to 16 or as a booster amplifier when equipped and provisioned in Slot 1 and 17. See the “4.9 OPT-AMP-C Card” section on page 4-33. OPT-RAMP-C The OPT-RAMP-C C-band amplifier has five sets of optical ports located on the faceplate and operates in Slots 1 to 5 and 12 to 16. See the “4.10 OPT-RAMP-C and OPT-RAMP-CE Cards” section on page 4-38. OPT-RAMP-CE The OPT-RAMP-CE C-band amplifier has five sets of optical ports located on the faceplate and operates in Slots 1 to 5 and 12 to 16. See the “4.10 OPT-RAMP-C and OPT-RAMP-CE Cards” section on page 4-38.4-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards Card Overview Table 4-2 Software Release Compatibility for Optical Amplifier Cards Card Type R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R 9.2 OPT-PRE 15454- DWDM 15454- DWDM 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWD M 15454 -DWD M 15454- DWD M 15454 -DWD M 15454- DWDM 15454 -DW DM ONS 15454, 15454 -M2, 15454 -M6 OPT-BST 15454- DWDM 15454- DWDM 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWD M 15454 -DWD M 15454- DWD M 15454 -DWD M 15454- DWDM 15454 -DW DM ONS 15454, 15454 -M2, 15454 -M6 OPT-BST-E No No 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWD M 15454 -DWD M 15454- DWD M 15454 -DWD M 15454- DWDM 15454 -DW DM ONS 15454, 15454 -M2, 15454 -M6 OPT-BST-L No No No No No 15454- DWD M 15454 -DWD M 15454- DWD M 15454 -DWD M 15454- DWDM 15454 -DW DM 15454 -DWD M OPT-AMP-L No No No No No 15454- DWD M 15454 -DWD M 15454- DWD M 15454 -DWD M 15454- DWDM 15454 -DW DM 15454 -DWD M OPT-AMP-17-C No No No No No No No 15454- DWD M 15454 -DWD M 15454- DWDM 15454 -DW DM ONS 15454, 15454 -M2, 15454 -M6 OPT-AMP-C No No No No No No No No 15454 -DWD M 15454- DWDM 15454 -DW DM ONS 15454, 15454 -M2, 15454 -M6 OPT-RAMP-C No No No No No No No No No 15454- DWDM 15454 -DW DM ONS 15454, 15454 -M6 OPT-RAMP-CE No No No No No No No No No No 15454 -DW DM ONS 15454, 15454 -M64-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards Class 1M Laser Safety Labels 4.1.4 Optical Power Alarms and Thresholds Table 4-3 lists the alarms and related thresholds for the OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-17-C, and OPT-AMP-C cards. 4.2 Class 1M Laser Safety Labels This section explains the significance of the safety labels attached to the optical amplifier cards. The faceplates of the cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. 4.2.1 Class 1M Laser Product Statement Figure 4-1 shows the Class 1M Laser Product statement. Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam. Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can be harmful to the eye if the beam is viewed using magnifying optical instruments. Figure 4-1 Class 1M Laser Product Statement Table 4-3 Alarms and Thresholds Port Alarms Thresholds LINE RX LOS None LOS-P LOS-P Fail Low LOS-O LOS-O Fail Low LINE TX OPWR-FAIL OPWR Fail Low OSC TX None None OSC RX None None COM TX None None COM RX LOS-P LOS-P Fail Low CAUTION HAZARD LEVEL 1M INVISIBLE LASER RADIATION DO NOT VIEW DIRECTLY WITH NON-ATTENUATING OPTICAL INSTRUMENTS λ = = 1400nm TO 1610nm 1459534-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards Class 1M Laser Safety Labels 4.2.2 Hazard Level 1M Label Figure 4-2 shows the Hazard Level 1M label. The Hazard Level label warns users against exposure to laser radiation calculated in accordance with IEC60825-1 Ed.1.2. This label is displayed on the faceplate of the cards. Figure 4-2 Hazard Level Label 4.2.3 Laser Source Connector Label Figure 4-3 shows the Laser Source Connector label. This label indicates that a laser source is present at the optical connector where the label appears. Figure 4-3 Laser Source Connector Label 4.2.4 FDA Statement Label The FDA Statement labels are shown in Figure 4-4 and Figure 4-5. Figure 4-4 FDA Statement Label HAZARD LEVEL 1M 145990 96635 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 20014-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-PRE Amplifier Card Figure 4-5 FDA Statement Label These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. 4.2.5 Shock Hazard Label Figure 4-6 shows the Shock Hazard label. This label alerts you to an electrical hazard within the card. The potential for shock exists when you remove adjacent cards during maintenance or touch exposed electrical circuity on the card. Figure 4-6 Shock Hazard Label 4.3 OPT-PRE Amplifier Card Note For hardware specifications, see the “A.5.1 OPT-PRE Amplifier Card Specifications” section on page A-13. Note For OPT-PRE card safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-PRE is a C-band, DWDM, two-stage erbium-doped fiber amplifier (EDFA) with midamplifier loss (MAL) that can be connected to a dispersion compensating unit (DCU). The OPT-PRE is equipped with a built-in variable optical attenuator (VOA) that controls the gain tilt and can also be used to pad the DCU to a reference value. You can install the OPT-PRE in Slots 1 to 6 and 12 to 17. The card is designed to support up to 80 channels at 50-GHz channel spacing. The OPT-PRE features include: • Fixed gain mode with programmable tilt • True variable gain 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 2007 655414-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-PRE Amplifier Card • Fast transient suppression • Nondistorting low-frequency transfer function • Settable maximum output power • Fixed output power mode (mode used during provisioning) • MAL for fiber-based DCU • Amplified spontaneous emissions (ASE) compensation in fixed gain mode • Full monitoring and alarm handling with settable thresholds • Four signal photodiodes to monitor the input and output optical power of the two amplifier stages through CTC • An optical output port for external monitoring Note The optical splitter has a ratio of 1:99, resulting in about 20 dB-lower power at the MON port than at the COM TX port. 4.3.1 OPT-PRE Faceplate Ports The OPT-PRE amplifier has five optical ports located on the faceplate: • MON is the output monitor port • COM RX (receive) is the input signal port • COM TX (transmit) is the output signal port • DC RX is the MAL input signal port • DC TX is the MAL output signal port4-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-PRE Amplifier Card Figure 4-7 shows the OPT-PRE amplifier card faceplate. Figure 4-7 OPT-PRE Faceplate 4.3.2 OPT-PRE Block Diagrams Figure 4-8 shows a simplified block diagram of the OPT-PRE card’s features. OPT PRE FAIL ACT SF MON RX COM TX RX DC TX 964664-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-PRE Amplifier Card Figure 4-8 OPT-PRE Block Diagram Figure 4-9 shows the a block diagram of how the OPT-PRE optical module functions. Figure 4-9 OPT-PRE Optical Module Functional Block Diagram 4.3.3 OPT-PRE Power Monitoring Physical photodiodes P1, P2, P3, and P4 monitor the power for the OPT-PRE card. Table 4-4 shows the returned power level values calibrated to each port. Optical module COM RX DC RX 96478 Processor DC TX COM TX MON FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 98298 DCU COM RX COM TX DC TX DC RX MON P1 P2 P3 P4 P Physical photodiode Variable optical attenuator Table 4-4 OPT-PRE Port Calibration Photodiode CTC Type Name Calibrated to Port P1 Input Com COM RX P2 Output DC DC TX P3 Input DC DC RX P4 Output COM (Total Output) COM TX Output COM (Signal Output)4-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST Amplifier Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.3.4 OPT-PRE Amplifier Card-Level Indicators Table 4-5 shows the three card-level LED indicators on the OPT-PRE amplifier card. 4.3.5 OPT-PRE Amplifier Port-Level Indicators You can determine the status of the card ports 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. 4.4 OPT-BST Amplifier Card Note For hardware specifications, see the “A.5.2 OPT-BST Amplifier Card Specifications” section on page A-13. Note For OPT-BST card safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-BST is designed to ultimately support up to 80 channels at 50-GHz channel spacing. The OPT-BST is a C-band, DWDM EDFA with optical service channel (OSC) add-and-drop capability. When an OPT-BST installed in the an ONS 15454, an OSCM card is also needed to process the OSC. You can install the OPT-BST in Slots 1 to 6 and 12 to 17. The card’s features include: • Fixed gain mode (with programmable tilt) • Gain range of 5 to 20 dB in constant gain mode and output power mode • True variable gain • Built-in VOA to control gain tilt • Fast transient suppression Table 4-5 OPT-PRE Amplifier Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-PRE is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST Amplifier Card • Nondistorting low-frequency transfer function • Settable maximum output power • Fixed output power mode (mode used during provisioning) • ASE compensation in fixed gain mode • Full monitoring and alarm handling with settable thresholds • Optical Safety Remote Interlock (OSRI), a CTC software feature capable of shutting down optical output power or reducing the power to a safe level (automatic power reduction) • Automatic laser shutdown (ALS), a safety mechanism used in the event of a fiber cut. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. For information about using the card to implement ALS in a network, see the “12.11 Network Optical Safety” section on page 12-27. Note The optical splitters each have a ratio of 1:99. The result is that MON TX and MON RX port power is about 20 dB lower than COM TX and COM RX port power. 4.4.1 OPT-BST Faceplate Ports The OPT-BST amplifier has eight optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port. • LINE TX is the output signal port. • LINE RX is the input signal port (receive section). • COM TX is the output signal port (receive section). • OSC RX is the OSC add input port. • OSC TX is the OSC drop output port.4-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST Amplifier Card Figure 4-10 shows the OPT-BST amplifier card faceplate. Figure 4-10 OPT-BST Faceplate 4.4.2 OPT-BST Block Diagrams Figure 4-11 shows a simplified block diagram of the OPT-BST card’s features. OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX 964674-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST Amplifier Card Figure 4-11 OPT-BST Block Diagram Figure 4-12 shows a block diagram of how the OPT-BST optical module functions. Figure 4-12 OPT-BST Optical Module Functional Block Diagram 4.4.3 OPT-BST Power Monitoring Physical photodiodes P1, P2, P3, and P4 monitor the power for the OPT-BST card. Table 4-6 shows the returned power level values calibrated to each port. Optical module Line RX Monitor Line RX 96479 Processor Line TX COM TX Com RX OSC TX Monitor Line TX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 98300 MON TX OSC RX MON RX OSC TX OSC COM RX P1 P2 P3 P4 COM TX LINE TX APR signal LINE RX in RX P Physical photodiode Table 4-6 OPT-BST Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameter P1 Input Com COM RX Channel Power Supported4-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST Amplifier Card The power on the OSC TX and COM TX ports are calculated by adding the insertion loss (IL) to the power reported from P3 and P4. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.4.4 OPT-BST Card-Level Indicators Table 4-7 describes the three card-level LED indicators on the OPT-BST card. 4.4.5 OPT-BST Port-Level Indicators You can determine the status of the card ports 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. P2 Output Line (Total Output) LINE TX Channel Power Supported Output Line (Signal Output) P3 Input Line LINE RX Channel Power Supported P4 Input Line LINE RX OSC Power Supported Table 4-6 OPT-BST Port Calibration (continued) Photodiode CTC Type Name Calibrated to Port Power PM Parameter Table 4-7 OPT-BST Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-BST is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-E Amplifier Card 4.5 OPT-BST-E Amplifier Card Note For hardware specifications, see the “A.5.3 OPT-BST-E Amplifier Card Specifications” section on page A-14. Note For OPT-BST-E safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-BST-E amplifier card is a gain-enhanced version of the OPT-BST card. It is designed to support up to 80 channels at 50-GHz channel spacing. The OPT-BST-E is a C-band, DWDM EDFA with OSC add-and-drop capability. When an OPT-BST-E installed, an OSCM card is needed to process the OSC. You can install the OPT-BST-E in Slots 1 to 6 and 12 to 17. The card’s features include: • Fixed gain mode (with programmable tilt) • True variable gain • Gain range of 8 to 23 dBm with the tilt managed at 0 dBm in constant gain mode and output power mode • Enhanced gain range of 23 to 26 dBm with unmanaged tilt • Built-in VOA to control the gain tilt • Fast transient suppression • Nondistorting low-frequency transfer function • Settable maximum output power • Fixed output power mode (mode used during provisioning) • ASE compensation in fixed gain mode • Full monitoring and alarm handling with settable thresholds • OSRI • ALS Note The optical splitters each have a ratio of 1:99. The result is that MON TX and MON RX port power is about 20 dB lower than COM TX and COM RX port power. 4.5.1 OPT-BST-E Faceplate Ports The OPT-BST-E amplifier card has eight optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port. • LINE TX is the output signal port. • LINE RX is the input signal port (receive section). • COM TX is the output signal port (receive section).4-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-E Amplifier Card • OSC RX is the OSC add input port. • OSC TX is the OSC drop output port. Figure 4-13 shows the OPT-BST-E amplifier card faceplate. Figure 4-13 OPT-BST-E Faceplate 4.5.2 OPT-BST-E Block Diagrams Figure 4-14 shows a simplified block diagram of the OPT-BST-E card’s features. OPT BST-E FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX 1459394-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-E Amplifier Card Figure 4-14 OPT-BST-E Block Diagram Figure 4-15 shows a block diagram of how the OPT-BST-E optical module functions. Figure 4-15 OPT-BST-E Optical Module Functional Block Diagram 4.5.3 OPT-BST-E Power Monitoring Physical photodiodes P1, P2, P3, and P4 monitor the power for the OPT-BST-E card. Table 4-8 shows the returned power level values calibrated to each port. Optical module Line RX Monitor Line RX 96479 Processor Line TX COM TX Com RX OSC TX Monitor Line TX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 98300 MON TX OSC RX MON RX OSC TX OSC COM RX P1 P2 P3 P4 COM TX LINE TX APR signal LINE RX in RX P Physical photodiode Table 4-8 OPT-BST-E Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameter P1 Input Com COM RX Channel Power Supported4-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-L Amplifier Card The power on the OSC-TX and COM-TX ports are calculated by adding the insertion loss (IL) to the power reported from P3 and P4. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.5.4 OPT-BST-E Card-Level Indicators Table 4-9 describes the three card-level LED indicators on the OPT-BST-E amplifier card. 4.5.5 OPT-BST-E Port-Level Indicators You can determine the status of the card ports 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. 4.6 OPT-BST-L Amplifier Card (Cisco ONS 15454 only) P2 Output Line (Total Output) LINE TX Channel Power Supported Output Line (Signal Output) P3 Input Line LINE RX Channel Power Supported P4 Input Line LINE RX OSC Power Supported Table 4-8 OPT-BST-E Port Calibration (continued) Photodiode CTC Type Name Calibrated to Port Power PM Parameter Table 4-9 OPT-BST-E Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-BST-E is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-L Amplifier Card Note For hardware specifications, see the “A.5.4 OPT-BST-L Amplifier Card Specifications” section on page A-15. Note For OPT-BST-L safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-BST-L is an L-band, DWDM EDFA with OSC add-and-drop capability. The card is well suited for use in networks that employ dispersion shifted (DS) fiber or SMF-28 single-mode fiber. The OPT-BST-L is designed to ultimately support 64 channels at 50-GHz channel spacing, but in Software R9.0 and earlier it is limited to 32 channels at 100-GHz spacing.When an ONS 15454 has an OPT-BST-L installed, an OSCM card is needed to process the OSC. You can install the OPT-BST-L in Slots 1 to 6 and 12 to 17. The card’s features include: • Fixed gain mode (with programmable tilt) • Standard gain range of 8 to 20 dB in the programmable gain tilt mode • True variable gain • 20 to 27 dB gain range in the uncontrolled gain tilt mode • Built-in VOA to control gain tilt • Fast transient suppression • Nondistorting low-frequency transfer function • Settable maximum output power • Fixed output power mode (mode used during provisioning) • ASE compensation in fixed gain mode • Full monitoring and alarm handling with settable thresholds • OSRI • ALS Note The optical splitters each have a ratio of 1:99. The result is that MON TX and MON RX port power is about 20 dB lower than COM TX and COM RX port power. 4.6.1 OPT-BST-L Faceplate Ports The OPT-BST-L amplifier has eight optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port. • LINE TX is the output signal port. • LINE RX is the input signal port (receive section). • COM TX is the output signal port (receive section). • OSC RX is the OSC add input port. 4-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-L Amplifier Card • OSC TX is the OSC drop output port. Figure 4-16 shows the OPT-BST-L card faceplate. Figure 4-16 OPT-BST-L Faceplate 4.6.2 OPT-BST-L Block Diagrams Figure 4-17 shows a simplified block diagram of the OPT-BST-L card’s features. OPT BST-L FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX 1809294-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-L Amplifier Card Figure 4-17 OPT-BST-L Block Diagram Figure 4-18 shows a block diagram of how the OPT-BST-L optical module functions. Figure 4-18 OPT-BST-L Optical Module Functional Block Diagram 4.6.3 OPT-BST-L Power Monitoring Physical photodiodes P1, P2, P3, P4, and P5 monitor the power for the OPT-BST-L card. Table 4-10 shows the returned power level values calibrated to each port. Optical module Line RX Monitor Line RX 180930 Processor Line TX COM TX COM RX OSC TX Monitor Line TX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 134976 MON TX OSC RX MON RX OSC TX OSC COM RX P1 P2 P4 P5 COM TX LINE TX APR signal LINE RX in RX P Physical photodiode P3 Table 4-10 OPT-BST-L Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameter P1 Input COM COM RX Channel Power Supported4-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-BST-L Amplifier Card The power values on the OSC-TX and COM-TX ports are calculated by adding the insertion loss (IL) to the power values reported from P4 and P5. The OSC power on the LINE TX is calculated by adding the IL to the power reported from P3. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.6.4 OPT-BST-L Card-Level Indicators Table 4-11 shows the three card-level LEDs on the OPT-BST-L card. 4.6.5 OPT-BST-L Port-Level Indicators You can determine the status of the card ports 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. P2 Output Line (Total Output) LINE TX Channel Power Supported Output Line (Signal Output) P3 Input OSC OSC RX OSC Power Supported P4 Input Line LINE RX Channel Power Supported P5 Input Line LINE RX OSC Power Supported Table 4-10 OPT-BST-L Port Calibration (continued) Photodiode CTC Type Name Calibrated to Port Power PM Parameter Table 4-11 OPT-BST-L Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-BST-L is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-L Card 4.7 OPT-AMP-L Card (Cisco ONS 15454 only) Note For hardware specifications, see the “A.5.5 OPT-AMP-L Preamplifier Card Specifications” section on page A-15. Note For OPT-AMP-L card safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-AMP-L is an L-band, DWDM optical amplifier card consisting of a two-stage EDFA with midstage access loss (MSL) for an external DCU and OSC add-and-drop capability. Using CTC, the card is provisionable as a preamplifier (OPT-PRE) or booster amplifier (OPT-BST), and is well suited for use in networks that employ DS or SMF-28 fiber. The amplifier can operate up to 64 optical transmission channels at 50-GHz channel spacing in the 1570 nm to 1605 nm wavelength range. When an OPT-AMP-L installed, an OSCM card is needed to process the OSC. You can install the two-slot OPT-AMP-L in Slots 1 to 6 and 12 to 17. The card has the following features: • Maximum power output of 20 dBm • True variable gain amplifier with settable range from 12 to 24 dBm in the standard gain range and 24 dBm to 35 dbM with uncontrolled gain tilt • Built-in VOA to control gain tilt • Up to 12 dBm MSL for an external DCU • Fast transient suppression; able to adjust power levels in hundreds of microseconds to avoid bit errors in failure or capacity growth situations • Nondistorting low frequency transfer function • Midstage access loss for dispersion compensation unit • Constant pump current mode (test mode) • Constant output power mode (used during optical node setup) • Constant gain mode • Internal ASE compensation in constant gain mode and in constant output power mode • Full monitoring and alarm handling capability • Optical safety support through signal loss detection and alarm at any input port, fast power down control (less than one second), and reduced maximum output power in safe power mode. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. For information on using the card to implement ALS in a network, see the “12.11 Network Optical Safety” section on page 12-27. Note Before disconnecting any OPT AMP-L fiber for troubleshooting, first make sure the OPT AMP-L card is unplugged.4-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-L Card 4.7.1 OPT-AMP-L Faceplate Ports The OPT-AMP-L amplifier card has ten optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port. • LINE TX is the output signal port. • LINE RX is the input signal port (receive section). • COM TX is the output signal port (receive section). • OSC RX is the OSC add input port. • OSC TX is the OSC drop output port. • DC TX is the output signal to the DCU. • DC RX is the input signal from the DCU.4-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-L Card Figure 4-19 shows the OPT-AMP-L card faceplate. Figure 4-19 OPT-AMP-L Faceplate 4.7.2 OPT-AMP-L Block Diagrams Figure 4-20 shows a simplified block diagram of the OPT-AMP-L card’s features. OPT-AMP-L FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX RX DC TX 1809314-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-L Card Figure 4-20 OPT-AMP-L Block Diagram Figure 4-21 shows a block diagram of how the OPT-AMP-L optical module functions. Figure 4-21 OPT-AMP-L Optical Module Functional Block Diagram Optical module Monitor Line RX Line RX DC RX Processor Line TX DC TX COM TX COM RX OSC TX Monitor Line TX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 180932 MON TX OSC RX OSC TX COM RX COM TX MON RX LINE TX LINE RX P1 P Physical photodiode Variable optical attenuator P2 P3 P6 P4 DC TX DC RX External Mid-Stage Loss OSC Add OSC Drop P7 P5 Transmit Section Receive Section 1452564-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-L Card 4.7.3 OPT-AMP-L Power Monitoring Physical photodiodes P1 through P7 monitor the power for the OPT-AMP-L card. Table 4-12 shows the returned power level values calibrated to each port. The power values on the OSC-TX and COM-TX ports are calculated by adding the insertion loss (IL) to the power values reported from P5 and P6. The power values on the LINE TX port is calculated by adding the IL to the power value reported from P7. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.7.4 OPT-AMP-L Card-Level Indicators Table 4-13 shows the three card-level LEDs on the OPT-AMP-L card. Table 4-12 OPT-AMP-L Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameter P1 Input COM COM RX Channel Power Supported P2 Output DC (total power) DC TX Channel Power Supported Output DC (signal power) P3 Input DC (input power) DC RX Channel Power Supported P4 Output Line (total power) LINE TX Channel Power Supported Output Line (signal power) P5 Input Line LINE RX Channel Power Supported P6 Input Line LINE RX OSC Power Supported P7 Input OSC OSC RX OSC Power Supported Table 4-13 OPT-AMP-L Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-AMP-L is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-17-C Card 4.7.5 OPT-AMP-L Port-Level Indicators You can determine the status of the card ports 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. 4.8 OPT-AMP-17-C Card Note For hardware specifications, see the “A.5.6 OPT-AMP-17-C Amplifier Card Specifications” section on page A-16. Note For OPT-AMP-17-C safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-AMP-17-C is a 17-dB gain, C-band, DWDM EDFA amplifier/preamplifier with OSC add-and-drop capability. It supports 80 channels at 50-GHz channel spacing in the C-band (that is, the 1529 nm to 1562.5 nm wavelength range). When an ONS 15454 has an OPT-AMP-17-C installed, an OSCM card is needed to process the OSC. You can install the OPT-AMP-17-C in Slots 1 to 6 and 12 to 17. The card’s features include: • Fixed gain mode (no programmable tilt) • Standard gain range of 14 to 20 dB at startup when configured as a preamplifier • Standard gain range of 20 to 23 dB in the transient mode when configured as a preamplifier • Gain range of 14 to 23 dB (with no transient gain range) when configured as a booster amplifier • True variable gain • Fast transient suppression • Nondistorting low-frequency transfer function • Settable maximum output power • Fixed output power mode (mode used during provisioning) • ASE compensation in fixed gain mode • Full monitoring and alarm handling with settable thresholds • OSRI • ALS 4.8.1 OPT-AMP-17-C Faceplate Ports The OPT-AMP-17-C amplifier card has eight optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port. 4-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-17-C Card • LINE TX is the output signal port. • LINE RX is the input signal port (receive section). • COM TX is the output signal port (receive section). • OSC RX is the OSC add input port. • OSC TX is the OSC drop output port. Figure 4-22 shows the OPT-AMP-17-C amplifier card faceplate. Figure 4-22 OPT-AMP-17-C Faceplate OPT -AMP 17-C FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX 1595204-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-17-C Card 4.8.2 OPT-AMP-17-C Block Diagrams Figure 4-23 shows a simplified block diagram of the OPT-AMP-17C card’s features. Figure 4-23 OPT-AMP17-C Block Diagram Figure 4-24 shows how the OPT-AMP-17-C optical module functions. Figure 4-24 OPT-AMP-17-C Optical Module Functional Block Diagram Optical module Line RX Monitor Line RX 180928 Processor Line TX COM TX COM RX OSC TX Monitor Line TX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B MON TX OSC RX MON RX OSC TX OSC COM RX P1 P2 P4 P5 COM TX LINE TX APR signal LINE RX in RX P Physical photodiode P3 OSC add OSC drop 1595194-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-17-C Card 4.8.3 OPT-AMP-17-C Automatic Power Control A transient gain range of 20 to 23 dB is available to APC in order to permit other amplifiers to reach their expected set points. However, operation in this range is not continuous. At startup, the OPT-AMP-17-C card caps the gain at a maximum of 20 dB. Note When the OPT-AMP-17-C operates as a booster amplifier, APC does not control its gain. 4.8.4 OPT-AMP-17-C Power Monitoring Physical photodiodes P1, P2, P3, P4, and P5 monitor power for the OPT-AMP-17-C card. Table 4-14 shows the returned power level values calibrated to each port. The power on the OSC-TX and COM-TX ports are calculated by adding the insertion loss (IL) to the power reported from P3 and P4. The OSC power on the LINE TX is calculated by adding the IL to the power reported from P5. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.8.5 OPT-AMP-17-C Card-Level Indicators Table 4-15 shows the three card-level LEDs on the OPT-AMP-17-C card. Table 4-14 OPT-AMP-17-C Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameter P1 Input COM COM RX Channel Power Supported P2 Output Line (Total Output) LINE TX Channel Power Supported Output Line (Signal Output) P3 Input Line LINE RX Channel Power Supported P4 Input Line LINE RX OSC Power Supported P5 Input OSC OSC RX OSC Power Supported Table 4-15 OPT-AMP-17-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists.4-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-C Card 4.8.6 OPT-AMP-17-C Port-Level Indicators You can determine the status of the card ports 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. 4.9 OPT-AMP-C Card Note For hardware specifications, see the “A.5.7 OPT-AMP-C Amplifier Card Specifications” section on page A-17. Note For OPT-AMP-C card safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-AMP-C card is a 20-dB output power, C-band, DWDM EDFA amplifier/preamplifier. It contains mid-stage access loss for a Dispersion Compensation Unit (DCU). To control gain tilt, a VOA is used. The VOA can also be used to attenuate the signal to the DCU to a reference value. The amplifier module also includes the OSC add (TX direction) and drop (RX direction) optical filters. The OPT-AMP-C card supports 80 channels at 50-GHz channel spacing in the C-band (that is, the 1529 nm to 1562.5 nm wavelength range). When an ONS 15454 has an OPT-AMP-C card installed, an OSCM card is needed to process the OSC. You can install the OPT-AMP-C card in Slots 1 to 6 and 12 to 17. Slots 2 to 6 and Slots 12 to 16 are the default slots for provisioning the OPT-AMP-C card as a preamplifier, and slots 1 and 17 are the default slots for provisioning the OPT-AMP-C card as a booster amplifier. The card’s features include: • Fast transient suppression • Nondistorting low-frequency transfer function • Mid-stage access for DCU • Constant pump current mode (test mode) • Fixed output power mode (mode used during provisioning) • Constant gain mode • ASE compensation in Constant Gain and Constant Output Power modes • Programmable tilt Green ACT LED The green ACT LED indicates that the OPT-AMP-17-C is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off. Table 4-15 OPT-AMP-17-C Card-Level Indicators (continued) Card-Level Indicators Description4-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-C Card • Full monitoring and alarm handling capability • Gain range with gain tilt control of 12 to 24 dB • Extended gain range (with uncontrolled tilt) of 24 to 35 dB • Full monitoring and alarm handling with settable thresholds • OSRI • ALS 4.9.1 OPT-AMP-C Card Faceplate Ports The OPT-AMP-C amplifier card has 10 optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port. • COM TX is the output signal port (receive section). • DC RX is the input DCU port. • DC TX is the output DCU port. • OSC RX is the OSC add input port. • OSC TX is the OSC drop output port. • LINE RX is the input signal port (receive section). • LINE TX is the output signal port. 4-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-C Card Figure 4-25 shows the OPT-AMP-C amplifier card faceplate. Figure 4-25 OPT-AMP-C Card Faceplate 4.9.2 OPT-AMP-C Card Block Diagrams Figure 4-26 shows a simplified block diagram of the OPT-AMP-C card features. OPT -AMP -C FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX DC TX RX LINE TX 2745104-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-C Card Figure 4-26 OPT-AMP-C Block Diagram Figure 4-27 shows how the OPT-AMP-C optical module functions. Figure 4-27 OPT-AMP-C Optical Module Functional Block Diagram Optical module Line RX Monitor Line RX 240356 Processor COM TX COM RX Line TX OSC TX Monitor Line TX DCU TX DCU RX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B MON TX OSC RX OSC TX COM RX COM TX MON RX LINE TX LINE RX P1 P Physical photodiode Variable optical attenuator P2 P3 P6 P4 DC TX DC RX External Mid-Stage Loss OSC Add OSC Drop P7 P5 Transmit Section Receive Section 1452564-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-AMP-C Card 4.9.3 OPT-AMP-C Card Power Monitoring Physical photodiodes P1 through P7 monitor the power for the OPT-AMP-C card (see Table 4-16). The power on the OSC-TX and COM-TX ports are calculated by adding the insertion loss (IL) to the power reported from P5 and P6. The OSC power on the LINE TX is calculated by adding the IL to the power reported from P7. The PM parameters for the power values are listed in Table 19-31. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.9.4 OPT-AMP-C Card-Level Indicators Table 4-17 shows the three card-level LEDs on the OPT-AMP-C card. Table 4-16 OPT-AMP-C Port Calibration Photodiode CTC Type Name Calibrated to Port Power PM Parameters P1 Input COM COM RX Channel Power Supported P2 Output DC (total power) DC TX Channel Power Supported Output DC (signal power) P3 Input DC (input power) DC RX Channel Power Supported P4 Output Line (total power) LINE TX Channel Power Supported Output Line (signal power) P5 Input Line LINE RX Channel Power Supported P6 Input Line LINE RX OSC Power Supported P7 Input OSC OSC RX OSC Power Supported Table 4-17 OPT-AMP-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-AMP-C card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE Cards 4.9.5 OPT-AMP-C Card Port-Level Indicators You can determine the status of the card ports 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. 4.10 OPT-RAMP-C and OPT-RAMP-CE Cards (Cisco ONS 15454 and ONS 15454 M6 only) Note For hardware specifications, see the “A.5.8 OPT-RAMP-C Amplifier Card Specifications” section on page A-17 and “A.5.9 OPT-RAMP-CE Amplifier Card Specifications” section on page A-18. Note For OPT-RAMP-C or OPT-RAMP-CE card safety labels, see the “4.2 Class 1M Laser Safety Labels” section on page 4-5. The OPT-RAMP-C card is a double-slot card that improves unregenerated sections in long spans using the span fiber to amplify the optical signal. Different wavelengths in C-band receive different gain values. To achieve Raman amplification, two Raman signals (that do not carry any payload or overhead) are required to be transmitted on the optical fiber because the gain generated by one signal is not flat. The energy of these Raman signals transfer to the higher region of the spectrum thereby amplifying the signals transmitted at higher wavelengths. The Raman effect reduces span loss but does not compensate it completely. When the Raman optical powers are set correctly, a gain profile with limited ripple is achieved. The wavelengths of the Raman signals are not in the C-band of the spectrum (used by MSTP for payload signals). The two Raman wavelengths are fixed and always the same. Due to a limited Raman gain, an EDFA amplifier is embedded into the card to generate a higher total gain. An embedded EDFA gain block provides a first amplification stage, while the mid stage access (MSA) is used for DCU loss compensation. The OPT-RAMP-CE card is a 20 dBm output power, gain-enhanced version of the OPT-RAMP-C card and is optimized for short spans. The OPT-RAMP-C and OPT-RAMP-CE cards can support up to 80 optical transmission channels at 50-GHz channel spacing over the C-band of the optical spectrum (wavelengths from 1529 nm to 1562.5 nm). To provide a counter-propagating Raman pump into the transmission fiber, the Raman amplifier provides up to 500 mW at the LINE-RX connector. The OPT-RAMP-C or OPT-RAMP-CE card can be installed in Slots 1 to 5 and 12 to 16, and supports all network configurations. However, the OPT-RAMP-C or OPT-RAMP-CE card must be equipped on both endpoints of a span. The Raman total power and Raman ratio can be configured using CTC. For information on how to configure the Raman parameters, refer the Cisco ONS 15454 DWDM Procedure Guide. The Raman configuration can be viewed on the Maintenance > Installation tab. The features of the OPT-RAMP-C and OPT-RAMP-CE card include: • Raman pump with embedded EDFA gain block • Raman section: 500 mW total pump power for two pump wavelengths • EDFA section: – OPT-RAMP-C: 16 dB gain and 17 dB output power4-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE Cards – OPT-RAMP-CE: 11 dB gain and 20 dB output power • Gain Flattening Filter (GFF) for Raman plus EDFA ripple compensation • MSA for DC units • VOA for DC input power control • Full monitoring of pump, OSC, and signal power • Fast gain control for transient suppression • Low-FIT (hardware-managed) optical laser safety • Hardware output signals for LOS monitoring at input photodiodes • Optical service channel add and drop filters • Raman pump back-reflection detector 4.10.1 Card Faceplate Ports The OPT-RAMP-C and OPT-RAMP-CE cards have ten optical ports located on the faceplate: • MON RX is the output monitor port (receive section). • MON TX is the output monitor port. • COM RX is the input signal port (receive section). • COM TX is the output signal port. • DC RX is the input DCU port. • DC TX is the output DCU port. • OSC RX is the OSC add input port. • OSC TX is the OSC drop output port. • LINE RX is the input signal port (receive section). • LINE TX is the output signal port. Figure 4-28 shows the OPT-RAMP-C card faceplate.4-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE Cards Figure 4-28 OPT-RAMP-C Faceplate The OPT-RAMP-CE card faceplate is the same as that of the OPT-RAMP-C card. 4.10.2 Card Block Diagram Figure 4-29 shows a simplified block diagram of the OPT-RAMP-C and OPT-RAMP-CE card features. 270710 LINE OSC DC COM MOM RX TX RX TX RX TX RX TX RX TX FAIL ACT DF OPT-RAMP-C4-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE Cards Figure 4-29 OPT-RAMP-C and OPT-RAMP-CE Block Diagram Figure 4-30 shows a block diagram of how the OPT-RAMP-C and OPT-RAMP-CE card functions. Figure 4-30 OPT-RAMP-C and OPT-RAMP-CE Card Functional Block Diagram Optical module Line RX Monitor Line RX 240356 Processor COM TX COM RX Line TX OSC TX Monitor Line TX DCU TX DCU RX OSC RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 270709 OSC-TX W to E section E to W section Line-TX Line-RX COM-RX COM-TX OSC Drop OSC Add Pump 1 Pump 2 PD 8 PD 9 PD 11 PD 10 PD 12 PD 7 PD 5 PD 6 PD 1 PD 2 PD 3 PD 4 Pump Drop Pump Add PD Physical photodiode Variable optical attenuator4-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE Cards Two Raman pump lasers are combined internally and launched in-fiber at the LINE-RX port, thereby counter-propagating with the DWDM signal. An EDFA gain block provides further amplification of the DWDM signal, which allows regulated output power entry in the mid stage access and acts upon the VOA attenuation. While the optical filters are present for the OSC add and drop functions, the OSC signal counter-propagates with the DWDM signal. Two monitor ports, MON-RX and MON-TX, are provided at the EDFA input and output stages and are used to evaluate the total gain ripple. A total of 12 photodiodes (PDs) are provided, allowing full monitoring of RP power, DWDM power, and OSC power in each section of the device. In particular, PD12 allows the detection of the remnant Raman pump power at the end of the counter-pumped span, while PD11 detects the amount of Raman pump power backscattered by the LINE-RX connector and transmission fiber. The EDFA section calculates the signal power, considering the expected ASE power contribution to the total output power. The signal output power or the signal gain can be used as feedback signals for the EDFA pump power control loop. The ASE power is derived according to the working EDFA gain. PD2, PD3, and PD4 provide the total power measured by the photodiode and the signal power is derived by calculating the total power value. The insertion loss of the main optical path and the relative optical attenuation of the two monitor ports are stored into the card’s not-volatile memory. 4.10.3 OPT-RAMP-C and OPT-RAMP-CE Card Power Monitoring Physical photodiodes PD1 through PD12 monitor the power for the OPT-RAMP-C and OPT-RAMP-CE cards (see Table 4-18). For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 4.10.4 OPT-RAMP-C and OPT-RAMP-CE Card Level Indicators Table 4-19 shows the three card-level LEDs on the OPT-RAMP-C and OPT-RAMP-CE cards. Table 4-18 OPT-RAMP-C and OPT-RAMP-CE Port Calibration Photodiode CTC Type Name Calibrated to Port PD1 EDFA DWDM Input Power LINE-RX PD2 EDFA Output Power (pre-VOA attenuation) DC-TX (port with 0 dB VOA attenuation) PD3 DCU Input Power DC-TX PD4 DCU Output Power DC-RX PD5 DWDM Input Power COM-RX PD6 OSC ADD Input Power OSC-RX PD7 OSC DROP Output Power OSC-TX PD8 Pump 1 in-fiber Output Power LINE-RX PD9 Pump 2 in-fiber Output Power LINE-RX PD10 Total Pump in-fiber Output Power LINE-RX PD11 Back-Reflected Pump Power LINE-RX PD12 Remnant Pump Power LINE-TX4-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE Cards 4.10.5 OPT-RAMP-C and OPT-RAMP-CE Card Port-Level Indicators You can determine the status of the card ports 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. Table 4-19 OPT-RAMP-C and OPT-RAMP-CE Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the OPT-RAMP-C or OPT-RAMP-CE card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.4-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 4 Optical Amplifier Cards OPT-RAMP-C and OPT-RAMP-CE CardsCHAPTER 5-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 5 Multiplexer and Demultiplexer Cards This chapter describes legacy multiplexer and demultiplexer cards used in Cisco ONS 15454 dense wavelength division multiplexing (DWDM) networks. For installation and card turn-up procedures, see the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, see the Cisco Optical Transport Products Safety and Compliance Information document. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 5.1 Card Overview, page 5-1 • 5.2 Safety Labels, page 5-8 • 5.3 32MUX-O Card, page 5-13 • 5.4 32DMX-O Card, page 5-17 • 5.5 4MD-xx.x Card, page 5-21 Note For a description of the 32DMX, 32DMX-L, 40-DMX-C, 40-DMX-CE, 40-MUX-C, 40-WSS-C, 40-WSS-CE, and 40-WXC-C cards, see Chapter 9, “Reconfigurable Optical Add/Drop Cards.” 5.1 Card Overview The card overview section contains card summary, compatibility, interface class, and channel allocation plan information for legacy multiplexer and demultiplexer cards. 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. For a list of slots and symbols, see the "Card Slot Requirements" section in the Cisco ONS 15454 Hardware Installation Guide. 5-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Card Overview 5.1.1 Card Summary Table 5-1 lists and summarizes the functions of the 32MUX-O, 32DMX-O, and 4MD-xx.x cards. 5.1.2 Card Compatibility Table 5-2 lists the CTC software compatibility for the legacy cards. 5.1.3 Interface Classes The 32MUX-O, 32DMX-O, and 4MD-xx.x cards have different input and output optical channel signals depending on the interface card where the input signal originates. The input interface cards have been grouped in classes listed in Table 5-3. The subsequent tables list the optical performance and output power of each interface class. Table 5-1 Multiplexer and Demultiplexer Cards Card Port Description For Additional Information 32MUX-O The 32MUX-O has five sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “5.3 32MUX-O Card” section on page 5-13. 32DMX-O The 32DMX-O has five sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. “5.4 32DMX-O Card” section on page 5-17 4MD-xx.x The 4MD-xx.x card has five sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “5.5 4MD-xx.x Card” section on page 5-21. Table 5-2 Software Compatibility for Legacy Multiplexer and Demultiplexer Cards Release Cards 32MUX-O 32DMX-O 4MD-xx.x R4.5 Yes Yes Yes R4.6 Yes Yes Yes R4.7 Yes Yes Yes R5.0 Yes Yes Yes R6.0 Yes Yes Yes R7.0 Yes Yes Yes R7.2 Yes Yes Yes R8.0 Yes Yes Yes R8.5 Yes Yes Yes R9.0 Yes Yes Yes R9.1 Yes Yes Yes R9.2 Yes Yes Yes5-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Card Overview Table 5-5 lists the optical performance parameters for 40-Gbps cards that provide signal input to multiplexer and demultiplexer cards. Table 5-3 ONS 15454 Card Interfaces Assigned to Input Power Classes Input Power Class Card A 10-Gbps multirate transponder cards (TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L) with forward error correction (FEC) enabled, 10-Gbps muxponder cards (MXP_2.5G_10G, MXP_2.5G_10E, MXP_MR_10DME_C, MXP_MR_10DME_L, MXP_2.5G_10E_C, and MXP_2.5G_10E_L) with FEC enabled, and 40-Gbps muxponder card (40G-MXP-C) B 10-Gbps multirate transponder card (TXP_MR_10G) without FEC, 10-Gbps muxponder cards (MXP_2.5G_10G, MXP_MR_10DME_C, MXP_MR_10DME_L), 40-Gbps muxponder card (40G-MXP-C), and ADM-10G cards with FEC disabled C OC-192 LR ITU cards (TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L) without FEC D 2.5-Gbps multirate transponder card (TXP_MR_2.5G), both protected and unprotected, with FEC enabled E OC-48 100-GHz DWDM muxponder card (MXP_MR_2.5G) and 2.5-Gbps multirate transponder card (TXP_MR_2.5G), protected or unprotected, with FEC disabled and retime, reshape, and regenerate (3R) mode enabled F 2.5-Gbps multirate transponder card (TXP_MR_2.5G), protected or unprotected, in regenerate and reshape (2R) mode G OC-48 ELR 100 GHz card H 2/4 port GbE transponder (GBIC WDM 100GHz) I TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L cards with enhanced FEC (E-FEC) and the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_10DME_C, MXP_MR_10DME_L, and 40G-MXP-C cards with E-FEC enabled Table 5-4 40-Gbps Interface Optical Performance Parameter Class A Class B Class I Type Power Limited OSNR1 Limited Power Limited OSNR Limited Power Limited OSNR Limited Maximum bit rate 40 Gbps 40 Gbps 40 Gbps Regeneration 3R 3R 3R FEC Yes No Yes (E-FEC) Threshold Optimum Average Optimum Maximum BER2 10–15 10–12 10–15 OSNR1 sensitivity 23 dB 9 dB 23 dB 19 dB 20 dB 8 dB Power sensitivity –24 dBm –18 dBm –21 dBm –20 dBm –26 dBm –18 dBm Power overload –8 dBm –8 dBm –8 dBm5-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Card Overview Table 5-5 lists the optical performance parameters that provide signal input for the 40-Gbps multiplexer and demultiplexer cards. Transmitted Power Range3 OC-192 LR ITU — — — Dispersion compensation tolerance +/–800 ps/nm +/–1,000 ps/nm +/–800 ps/nm 1. OSNR = optical signal-to-noise ratio 2. BER = bit error rate 3. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 5-4 40-Gbps Interface Optical Performance (continued) Parameter Class A Class B Class I Type Power Limited OSNR1 Limited Power Limited OSNR Limited Power Limited OSNR Limited Table 5-5 10-Gbps Interface Optical Performance Parameters Parameter Class A Class B Class C Class I Type Power Limited OSNR1 Limited Power Limited OSNR Limited OSNR Limited Power Limited OSNR Limited Maximum bit rate 10 Gbps 10 Gbps 10 Gbps 10 Gbps Regeneration 3R 3R 3R 3R FEC Yes No No Yes (E-FEC) Threshold Optimum Average Average Optimum Maximum BER2 10–15 10–12 10–12 10–15 OSNR1 sensitivity 23 dB 9 dB 23 dB 19 dB 19 dB 20 dB 8 dB Power sensitivity –24 dBm –18 dBm –21 dBm –20 dBm –22 dBm –26 dBm –18 dBm Power overload –8 dBm –8 dBm –9 dBm –8 dBm Transmitted Power Range3 10-Gbps multirate transponder/10-Gbps FEC transponder (TXP_MR_10G) +2.5 to 3.5 dBm +2.5 to 3.5 dBm — — OC-192 LR ITU — — +3.0 to 6.0 dBm — 10-Gbps multirate transponder/10-Gbps FEC transponder (TXP_MR_10E) +3.0 to 6.0 dBm +3.0 to 6.0 dBm — +3.0 to 6.0 dBm Dispersion compensation tolerance +/–800 ps/nm +/–1,000 ps/nm +/–1,000 ps/nm +/–800 ps/nm5-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Card Overview Table 5-6 lists the optical interface performance parameters for 2.5-Gbps cards that provide signal input to multiplexer and demultiplexer cards. 5.1.4 Channel Allocation Plan ONS 15454 DWDM multiplexer and demultiplexer cards are designed for use with specific channels in the C band and L band. In most cases, the channels for these cards are either numbered (for example, 1 to 32 or 1 to 40) or delimited (odd or even). Client interfaces must comply with these channel assignments to be compatible with the ONS 15454 system. Table 5-7 lists the channel IDs and wavelengths assigned to the C-band DWDM channels. 1. OSNR = optical signal-to-noise ratio 2. BER = bit error rate 3. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 5-6 2.5-Gbps Interface Optical Performance Parameter Class D Class E Class F Class G Class H Class J Type Power Limited OSNR Limited Power Limited OSNR Limited OSNR Limited Power Limited OSNR Limited Power Limited OSNR Limited Power Limited Maximum bit rate 2.5 Gbps 2.5 Gbps 2.5 Gbps 2.5 Gbps 1.25 Gbps 2.5 Gbps Regeneration 3R 3R 2R 3R 3R 3R FEC Yes No No No No No Threshold Average Average Average Average Average Average Maximum BER 10–15 10–12 10–12 10–12 10–12 10–12 OSNR sensitivity 14 dB 6 dB 14 dB 10 dB 15 dB 14 dB 11 dB 13 dB 8 dB 12 dB Power sensitivity –31 dBm –25 dBm –30 dBm –23 dBm –24 dBm –27 dBm –33 dBm –28 dBm –18 dBm –26 dBm Power overload –9 dBm –9 dBm –9 dBm –9 dBm –7 dBm –17dBm Transmitted Power Range1 1. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. TXP_MR_2.5G –1.0 to 1.0 dBm –1.0 to 1.0 dBm –1.0 to 1.0 dBm –2.0 to 0 dBm TXPP_MR_2.5G –4.5 to –2.5 dBm –4.5 to –2.5 dBm –4.5 to –2.5 dBm MXP_MR_2.5G — +2.0 to +4.0 dBm — MXPP_MR_2.5G — –1.5 to +0.5 dBm — 2/4 port GbE Transponder (GBIC WDM 100GHz) +2.5 to 3.5 dBm — Dispersion compensation tolerance –1200 to +5400 ps/nm –1200 to +5400 ps/nm –1200 to +3300 ps/nm –1200 to +3300 ps/nm –1000 to +3600 ps/nm –1000 to +3200 ps/nm5-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Card Overview Note In some cases, a card uses only one of the bands (C band or L band) and some or all of the channels listed in a band. Also, some cards use channels on the 100-GHz ITU grid while others use channels on the 50-GHz ITU grid. See the specific card description or Appendix A, “Hardware Specifications” for more details. Table 5-7 DWDM Channel Allocation Plan (C Band) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.365-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Card Overview Table 5-8 lists the channel IDs and wavelengths assigned to the L-band channels. 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 5-7 DWDM Channel Allocation Plan (C Band) (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table 5-8 DWDM Channel Allocation Plan (L Band) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 190.85 1570.83 41 188.85 1587.46 2 190.8 1571.24 42 188.8 1587.88 3 190.75 1571.65 43 188.75 1588.30 4 190.7 1572.06 44 188.7 1588.73 5 190.65 1572.48 45 188.65 1589.15 6 190.6 1572.89 46 188.6 1589.57 7 190.55 1573.30 47 188.55 1589.99 8 190.5 1573.71 48 188.5 1590.41 9 190.45 1574.13 49 188.45 1590.83 10 190.4 1574.54 50 188.4 1591.26 11 190.35 1574.95 51 188.35 1591.68 12 190.3 1575.37 52 188.3 1592.10 13 190.25 1575.78 53 188.25 1592.52 14 190.2 1576.20 54 188.2 1592.95 15 190.15 1576.61 55 188.15 1593.37 16 190.1 1577.03 56 188.1 1593.79 17 190.05 1577.44 57 188.05 1594.22 18 190 1577.86 58 188 1594.64 19 189.95 1578.27 59 187.95 1595.065-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Safety Labels 5.2 Safety Labels This section explains the significance of the safety labels attached to some of the cards. The faceplates of the cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. 5.2.1 Class 1 Laser Product Labels The 32MUX-O card has a Class 1 laser. The labels that appear on the card are described in the following sections. 5.2.1.1 Class 1 Laser Product Label The Class 1 Laser Product label is shown in Figure 5-1. 20 189.9 1578.69 60 187.9 1595.49 21 189.85 1579.10 61 187.85 1595.91 22 189.8 1579.52 62 187.8 1596.34 23 189.75 1579.93 63 187.75 1596.76 24 189.7 1580.35 64 187.7 1597.19 25 189.65 1580.77 65 187.65 1597.62 26 189.6 1581.18 66 187.6 1598.04 27 189.55 1581.60 67 187.55 1598.47 28 189.5 1582.02 68 187.5 1598.89 29 189.45 1582.44 69 187.45 1599.32 30 189.4 1582.85 70 187.4 1599.75 31 189.35 1583.27 71 187.35 1600.17 32 189.3 1583.69 72 187.3 1600.60 33 189.25 1584.11 73 187.25 1601.03 34 189.2 1584.53 74 187.2 1601.46 35 189.15 1584.95 75 187.15 1601.88 36 189.1 1585.36 76 187.1 1602.31 37 189.05 1585.78 77 187.05 1602.74 38 189 1586.20 78 187 1603.17 39 188.95 1586.62 79 186.95 1603.60 40 188.9 1587.04 80 186.9 1604.03 Table 5-8 DWDM Channel Allocation Plan (L Band) (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)5-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Safety Labels Figure 5-1 Class 1 Laser Product Label Class 1 lasers are products whose irradiance does not exceed the Maximum Permissible Exposure (MPE) value. Therefore, for Class 1 laser products the output power is below the level at which it is believed eye damage will occur. Exposure to the beam of a Class 1 laser will not result in eye injury and may therefore be considered safe. However, some Class 1 laser products may contain laser systems of a higher class but there are adequate engineering control measures to ensure that access to the beam is not reasonably likely. Anyone who dismantles a Class 1 laser product that contains a higher Class laser system is potentially at risk of exposure to a hazardous laser beam 5.2.1.2 Hazard Level 1 Label The Hazard Level 1 label is shown in Figure 5-2. This label is displayed on the faceplate of the cards. Figure 5-2 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. 5.2.1.3 Laser Source Connector Label The Laser Source Connector label is shown in Figure 5-3. Figure 5-3 Laser Source Connector Label This label indicates that a laser source is present at the optical connector where the label has been placed. CLASS 1 LASER PRODUCT 145952 HAZARD LEVEL 1 65542 966355-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Safety Labels 5.2.1.4 FDA Statement Label The FDA Statement labels are shown in Figure 5-4 and Figure 5-5. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 5-4 FDA Statement Label Figure 5-5 FDA Statement Label 5.2.1.5 Shock Hazard Label The Shock Hazard label is shown in Figure 5-6. Figure 5-6 Shock Hazard Label This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself. 5.2.2 Class 1M Laser Product Cards The 32DMX-O and 4MD-xx.x cards have Class IM lasers. The labels that appear on these cards are described in the following subsections. 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 2007 655415-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Safety Labels 5.2.2.1 Class 1M Laser Product Statement The Class 1M Laser Product statement is shown in Figure 5-7. Figure 5-7 Class 1M Laser Product Statement Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam. Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can be harmful to the eye if the beam is viewed using magnifying optical instruments. 5.2.2.2 Hazard Level 1M Label The Hazard Level 1M label is shown in Figure 5-8. Figure 5-8 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. This label is displayed on the faceplate of the cards. 5.2.2.3 Laser Source Connector Label The Laser Source Connector label is shown in Figure 5-9. Figure 5-9 Laser Source Connector Label CAUTION HAZARD LEVEL 1M INVISIBLE LASER RADIATION DO NOT VIEW DIRECTLY WITH NON-ATTENUATING OPTICAL INSTRUMENTS λ = = 1400nm TO 1610nm 145953 HAZARD LEVEL 1M 145990 966355-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards Safety Labels This label indicates that a laser source is present at the optical connector where the label has been placed. 5.2.2.4 FDA Statement Label The FDA Statement labels are shown in Figure 5-10 and Figure 5-11. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 5-10 FDA Statement Label Figure 5-11 FDA Statement Label 5.2.2.5 Shock Hazard Label The Shock Hazard label is shown in Figure 5-6. Figure 5-12 Shock Hazard Label This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself. 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 2007 655415-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32MUX-O Card 5.3 32MUX-O Card Note See the “A.7.1 32MUX-O Card Specifications” section on page A-20 for hardware specifications. The 32-Channel Multiplexer (32MUX-O) card multiplexes 32 100-GHz-spaced channels identified in the channel plan. The 32MUX-O card takes up two slots in an ONS 15454 and can be installed in Slots 1 to 5 and 12 to 16. The 32MUX-O features include: • Arrayed waveguide grating (AWG) device that enables full multiplexing functions for the channels. • Each single-channel port is equipped with VOAs for automatic optical power regulation prior to multiplexing. In the case of electrical power failure, the VOA is set to its maximum attenuation for safety purposes. A manual VOA setting is also available. • Each single-channel port is monitored using a photodiode to enable automatic power regulation. An additional optical monitoring port with 1:99 splitting ratio is available. Figure 5-13 shows the 32MUX-O faceplate.5-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32MUX-O Card Figure 5-13 32MUX-O Faceplate For information on safety labels for the card, see the “5.2.1 Class 1 Laser Product Labels” section on page 5-8. Figure 5-14 shows a block diagram of the 32MUX-O card. 30.3 - 36.6 38.1 - 44.5 46.1 - 52.5 54.1 - 60.6 32MUX-0 COM TX RX MON FAIL ACT SF 964685-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32MUX-O Card Figure 5-14 32MUX-O Block Diagram The 32MUX-O card has four receive connectors that accept multifiber push-on (MPO) cables on its front panel for the client input interfaces. MPO cables break out into eight separate cables. The 32MUX-O card also has two LC-PC-II optical connectors, one for the main output and the other for the monitor port. Figure 5-15 shows the 32MUX-O optical module functional block diagram. Figure 5-15 32MUX-O Optical Module Functional Block Diagram 5.3.1 Channel Plan The 32MUX-O is typically used in hub nodes and provides the multiplexing of 32 channels, spaced at 100 GHz, into one fiber before their amplification and transmission along the line. The channel plan is shown in Table 5-9. Optical module 30.3 to 36.6 8 CHS RX 38.1 to 44.5 8 CHS RX 46.1 to 52.5 8 CHS RX 54.1 to 60.6 8 CHS RX 134413 Processor MON COM TX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 98301 1 32 Control Control interface Physical photodiode Variable optical attenuator MON COM TX Inputs P32 P31 P30 P29 P4 P3 P2 P1 P5-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32MUX-O Card Table 5-9 32MUX-O Channel Plan Channel Number1 1. The Channel Number column is only for reference purposes. The channel ID is consistent with the ONS 15454 and is used in card identification. Channel ID Frequency (GHz) Wavelength (nm) 1 30.3 195.9 1530.33 2 31.2 195.8 1531.12 3 31.9 195.7 1531.90 4 32.6 195.6 1532.68 5 34.2 195.4 1534.25 6 35.0 195.3 1535.04 7 35.8 195.2 1535.82 8 36.6 195.1 1536.61 9 38.1 194.9 1538.19 10 38.9 194.8 1538.98 11 39.7 194.7 1539.77 12 40.5 194.6 1540.56 13 42.1 194.4 1542.14 14 42.9 194.3 1542.94 15 43.7 194.2 1543.73 16 44.5 194.1 1544.53 17 46.1 193.9 1546.12 18 46.9 193.8 1546.92 19 47.7 193.7 1547.72 20 48.5 193.6 1548.51 21 50.1 193.4 1550.12 22 50.9 193.3 1550.92 23 51.7 193.2 1551.72 24 52.5 193.1 1552.52 25 54.1 192.9 1554.13 26 54.9 192.8 1554.94 27 55.7 192.7 1555.75 28 56.5 192.6 1556.55 29 58.1 192.4 1558.17 30 58.9 192.3 1558.98 31 59.7 192.2 1559.79 32 60.6 192.1 1560.615-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32DMX-O Card 5.3.2 Power Monitoring Physical photodiodes P1 through P32 monitor the power for the 32MUX-O card. The returned power level values are calibrated to the ports as shown in Table 5-10. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 5.3.3 32MUX-O Card-Level Indicators The 32MUX-O card has three card-level LED indicators, described in Table 5-11. 5.3.4 32MUX-O Port-Level Indicators You can find the status of the card ports 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. The 32MUX-O card has five sets of ports located on the faceplate. COM TX is the line output. COM MON is the optical monitoring port. The xx.x to yy.y RX ports represent the four groups of eight channels ranging from wavelength xx.x to wavelength yy.y, according to the channel plan. 5.4 32DMX-O Card Note See the “A.7.2 32DMX-O Card Specifications” section on page A-20 for hardware specifications. Table 5-10 32MUX-O Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P32 ADD COM TX Table 5-11 32MUX-O Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 32MUX-O is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.5-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32DMX-O Card The 32-Channel Demultiplexer (32DMX-O) card demultiplexes 32 100-GHz-spaced channels identified in the channel plan. The 32DMX-O takes up two slots in an ONS 15454 and can be installed in Slots 1 to 5 and 12 to 16. The 32DMX-O features include: • AWG that enables channel demultiplexing functions. • Each single-channel port is equipped with VOAs for automatic optical power regulation after demultiplexing. In the case of electrical power failure, the VOA is set to its maximum attenuation for safety purposes. A manual VOA setting is also available. • The 32DXM-O has four physical receive connectors that accept MPO cables on its front panel for the client input interfaces. MPO cables break out into eight separate cables. Note In contrast, the single-slot 32DMX card does not have VOAs on each drop port for optical power regulation. The 32DMX optical demultiplexer module is used in conjunction with the 32WSS card in ONS 15454 Multiservice Transport Platform (MSTP) nodes. • Each single-channel port is monitored using a photodiode to enable automatic power regulation. Figure 5-16 shows the 32DMX-O card faceplate.5-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32DMX-O Card Figure 5-16 32DMX-O Faceplate For information on safety labels for the card, see the “5.2.2 Class 1M Laser Product Cards” section on page 5-10. Figure 5-17 shows a block diagram of the 32DMX-O card. 32DMX-0 FAIL ACT SF 30.3 - 36.6 38.1 - 44.5 46.1 - 52.5 TX 54.1 - 60.6 RX COM MON 1459355-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 32DMX-O Card Figure 5-17 32DMX-O Block Diagram Figure 5-18 shows the 32DMX-O optical module functional block diagram. Figure 5-18 32DMX-O Optical Module Functional Block Diagram 5.4.1 Power Monitoring Physical photodiodes P1 through P33 monitor the power for the 32DMX-O card. The returned power level values are calibrated to the ports as shown in Table 5-12. Optical module 30.3 to 36.6 8 CHS TX 38.1 to 44.5 8 CHS TX 46.1 to 52.5 8 CHS TX 54.1 to 60.6 8 CHS TX 96480 Processor MON COM RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 98302 1 32 Control Control interface Physical photodiode Variable optical attenuator COM RX DROP TX P32 P31 P30 P29 P4 P3 P2 P1 P P33 Table 5-12 32DMX-O Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P32 DROP DROP TX P33 INPUT COM COM RX5-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 4MD-xx.x Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 5.4.2 32DMX-O Card-Level Indicators The 32DMX-O card has three card-level LED indicators, described in Table 5-13. 5.4.3 32DMX-O Port-Level Indicators You can find the status of the card ports 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. The 32DMX-O card has five sets of ports located on the faceplate. MON is the output monitor port. COM RX is the line input. The xx.x to yy.y TX ports represent the four groups of eight channels ranging from wavelength xx.x to wavelength yy.y according to the channel plan. 5.5 4MD-xx.x Card Note See the “A.7.3 4MD-xx.x Card Specifications” section on page A-21 for hardware specifications. The 4-Channel Multiplexer/Demultiplexer (4MD-xx.x) card multiplexes and demultiplexes four 100-GHz-spaced channels identified in the channel plan. The 4MD-xx.x card is designed to be used with band OADMs (both AD-1B-xx.x and AD-4B-xx.x). The card is bidirectional. The demultiplexer and multiplexer functions are implemented in two different sections of the same card. In this way, the same card can manage signals flowing in opposite directions. There are eight versions of this card that correspond with the eight sub-bands specified in Table 5-14 on page 5-24. The 4MD-xx.x can be installed in Slots 1 to 6 and 12 to 17. The 4MD-xx.x has the following features implemented inside a plug-in optical module: • Passive cascade of interferential filters perform the channel multiplex/demultiplex function. • Software-controlled VOAs at every port of the multiplex section regulate the optical power of each multiplexed channel. Table 5-13 32DMX-O Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 32DMX-O is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.5-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 4MD-xx.x Card • Software-monitored photodiodes at the input and output multiplexer and demultiplexer ports for power control and safety purposes. • Software-monitored virtual photodiodes at the common DWDM output and input ports. A virtual photodiode is a firmware calculation of the optical power at that port. This calculation is based on the single channel photodiode reading and insertion losses of the appropriated paths. Figure 5-19 shows the 4MD-xx.x faceplate. Figure 5-19 4MD-xx.x Faceplate For information on safety labels for the card, see the “5.2.2 Class 1M Laser Product Cards” section on page 5-10. Figure 5-20 shows a block diagram of the 4MD-xx.x card. 4MD -X.XX FAIL ACT SF RX 15xx.xx TX RX 15xx.xx TX RX 15xx.xx TX RX 15xx.xx TX RX COM TX 964705-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 4MD-xx.x Card Figure 5-20 4MD-xx.x Block Diagram Figure 5-21 shows the 4MD-xx.x optical module functional block diagram. Figure 5-21 4MD-xx.x Optical Module Functional Block Diagram The optical module shown in Figure 5-21 is optically passive and consists of a cascade of interferential filters that perform the channel multiplexing and demultiplexing functions. VOAs are present in every input path of the multiplex section in order to regulate the optical power of each multiplexed channel. Some optical input and output ports are monitored by means of photodiodes implemented both for power control and for safety purposes. An internal control manages VOA settings and functionality as well as photodiode detection and alarm thresholds. The power at the main output Optical Module Channel Inputs 96482 Processor COM TX COM RX Channel Outputs FPGA For SCL Bus management SCL Bus TCC M SCL Bus TCC P DC/DC converter Power supply input filters BAT A&B 98303 Virtual photodiode COM TX COM RX Demux RX channels TX channels Physical photodiode Variable optical attenuator Control Control interface V1 V Mux P1 P2 P3 P3 P5 P6 P7 P8 P V25-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 4MD-xx.x Card and input ports is monitored through the use of virtual photodiodes. A virtual photodiode is implemented in the firmware of the plug-in module. This firmware calculates the power on a port, summing the measured values from all single channel ports (and applying the proper path insertion loss) and then providing the TCC2/TCC2P/TCC3/TNC/TSC card with the obtained value. 5.5.1 Wavelength Pairs Table 5-14 shows the band IDs and the add/drop channel IDs for the 4MD-xx.x card. 5.5.2 Power Monitoring Physical photodiodes P1 through P8 and virtual photodiodes V1 and V2 monitor the power for the 4MD-xx.x card. The returned power level values are calibrated to the ports as shown in Table 5-15. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 5.5.3 4MD-xx.x Card-Level Indicators The 4MD-xx.x card has three card-level LED indicators, described in Table 5-16. Table 5-14 4MD-xx.x Channel Sets Band ID Add/Drop Channel IDs Band 30.3 (A) 30.3, 31.2, 31.9, 32.6 Band 34.2 (B) 34.2, 35.0, 35.8, 36.6 Band 38.1 (C) 38.1, 38.9, 39.7, 40.5 Band 42.1 (D) 42.1, 42.9, 43.7, 44.5 Band 46.1 (E) 46.1, 46.9, 47.7, 48.5 Band 50.1 (F) 50.1, 50.9, 51.7, 52.5 Band 54.1 (G) 54.1, 54.9, 55.7, 56.5 Band 58.1 (H) 58.1, 58.9, 59.7, 60.6 Table 5-15 4MD-xx.x Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P4 ADD COM TX P5–P8 DROP DROP TX V1 OUT COM COM TX V2 IN COM COM RX5-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 4MD-xx.x Card 5.5.4 4MD-xx.x Port-Level Indicators You can find the status of the card ports 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. The 4MD-xx.x card has five sets of ports located on the faceplate. COM RX is the line input. COM TX is the line output. The 15xx.x TX ports represent demultiplexed channel outputs 1 to 4. The 15xx.x RX ports represent multiplexed channel inputs 1 to 4. Table 5-16 4MD-xx.x Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 4MD-xx.x card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.5-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 5 Multiplexer and Demultiplexer Cards 4MD-xx.x CardCHAPTER 6-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 6 Tunable Dispersion Compensating Units This chapter explains the Tunable Dispersion Compensating Units (T-DCU) used in Cisco ONS 15454 dense wavelength division multiplexing (DWDM) networks. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. The T-DCU unit compensates for chromatic dispersion (CD) of the transmission fiber. The T-DCU provides two line cards with varied set of tunable wavelengths to compensate for CD. This chapter includes: • 6.1 Card Overview, page 6-1 • 6.2 Class 1M Laser Safety Labels, page 6-2 • 6.3 TDC-CC and TDC-FC Cards, page 6-3 • 6.4 Monitoring Optical Performance, page 6-7 6.1 Card Overview The T-DCU card provides a selectable set of discrete negative chromatic dispersion values to compensate for chromatic dispersion of the transmission line. The card operates over the entire C-band (in the range of 1529.0 nm to 1562.5 nm) and monitors the optical power at the input and the output ports. The two types of T-DCU line cards are: • TDC-CC (Coarse T-DCU) • TDC-FC (Fine T-DCU) Note Each T-DCU card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. Cards should be installed in slots that have the same symbols. See the 1.16.1 Card Slot Requirements section on page 1-59 for a list of slots and symbols.6-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units Class 1M Laser Safety Labels 6.1.1 Card Summary Table 6-1 lists and summarizes the information about the TDC-CC and TDC-FC cards. 6.2 Class 1M Laser Safety Labels This section explains the significance of the safety labels attached to some of the cards. The faceplates of the cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. 6.2.1 Class 1M Laser Product Cards The TDC-CC and TDC-FC cards can be connected to Class 1M lasers. The labels that appear on these cards are described in the following subsections. Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam. Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can be harmful to the eye if the beam is viewed using magnifying optical instruments. 6.2.1.1 Hazard Level 1M Label The Hazard Level 1M label is shown in Figure 6-1. Figure 6-1 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. Table 6-1 T-DCU Cards Card Port Description For Additional Information TDC-CC The TDC-CC has one set of optical ports located on the faceplate. It operates in slots 1 to 6 and slots 12 to 17. See the 6.3 TDC-CC and TDC-FC Cards section. TDC-FC The TDC-FC has one set of optical ports located on the faceplate. It operates in slots 1 to 6 and slots 12 to 17. CAUTION HAZARD LEVEL 1M INVISIBLE LASER RADIATION DO NOT VIEW DIRECTLY WITH NON-ATTENUATING OPTICAL INSTRUMENTS λ = = 1400nm TO 1610nm 1459536-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units TDC-CC and TDC-FC Cards 6.2.1.2 Laser Source Connector Label The Laser Source Connector label is shown in Figure 6-2. Figure 6-2 Laser Source Connector Label This label indicates that a laser source is present at the optical connector where the label has been placed. 6.2.1.3 FDA Statement Label The FDA Statement labels are shown in Figure 6-3 and Figure 6-4. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 6-3 FDA Statement Label Figure 6-4 FDA Statement Label 6.3 TDC-CC and TDC-FC Cards The TDC-CC card provides 16 values of CD ranging from 0 to -1650 ps/nm with a granularity of 110 ps/nm in the C-band spectrum. The TDC-FC card provides 16 values of CD ranging from 0 to -675 ps/nm with a granularity of 45 ps/nm in the C-band spectrum. 96635 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 20076-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units TDC-CC and TDC-FC Cards You can configure the TDC-CC and TDC-FC cards for the CD value listed in Table 6-2. Refer to the Cisco ONS 15454 DWDM Procedure Guide to set the compensating value using CTC. 6.3.1 Key Features The TDC-CC and TDC-FC cards provide the following features: • Single slot card with three LEDs on the front panel. • Two LC-PC-II optical connectors on the front panel. • Operates in slots from slot 1 to 6 and 12 to 17. • Operates over the C-band (wavelengths from 1529 nm to 1562.5 nm) of the optical spectrum. • Allows upto 16 provisionable CD values for chromatic dispersion compensation. • Connects to OPT-PRE, OPT-AMP-C, OPT-RAMP-C, and OPT-RAMP-CE amplifiers and 40-SMR-1 and 40-SMR-2 cards. • Supports performance monitoring and alarm handling for selectable thresholds. • Allows monitoring and provisioning using CTC, SNMP, or TL1. Table 6-2 TDC-CC and TDC-FC Tunable CD Value Unit Configuration TDC-CC [ps/nm] TDC-FC [ps/nm] 0 0 1 1. The default value of the TDC-CC CD value for Coarse Unit is 0. 0 2 2. The default value of the TDC-FC value for Fine Unit is 0. 1 -110 -45 2 -220 -90 3 -330 -135 4 -440 -180 5 -550 -225 6 -660 -270 7 -770 -315 8 -880 -360 9 -990 -405 10 -1100 -450 11 -1210 -495 12 -1320 -540 13 -1430 -585 14 -1540 -630 15 -1650 -6756-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units TDC-CC and TDC-FC Cards 6.3.2 TDC-CC and TDC-FC Faceplate Diagram Figure 6-5 shows the TDC-CC and TDC-FC faceplate diagram. The TDC-CC and TDC-FC cards can be installed or pulled out of operation from any user interface slot, without impacting other service cards operating within that shelf. To install the TDC-CC and TDC-FC cards, refer the section NTP-G30 Install the DWDM Cards of the Cisco ONS 15454 DWDM Procedure Guide. Figure 6-5 TDC-CC and TDC-FC Faceplates Note The coarse T-DCU is identified with the card label as TDC-CC and the fine T-DCU with TDC-FC in the faceplate of the T-DCU card. TDC-CC FAIL ACT SF DC RX TX TDC-FC FAIL ACT SF DC RX TX Any of the 12 general purpose slots 2764446-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units TDC-CC and TDC-FC Cards 6.3.3 Functioning of Optical Ports The T-DCU unit contains the DC-RX (input) and DC-TX (output) ports. The optical signal enters the DC-RX port, compensates the chromatic dispersion and then exits from the DC-TX port. 6.3.4 TDC-CC and TDC-FC Block Diagram The TDC-CC and TDC-FC cards embed an optical module with four spools (D1, D2, D3, and D4) of dispersion compensating fiber that connects through the 2x2 bypass switches (Figure 6-6). Each bypass switch allows the corresponding dispersion compensation fiber spools to connect to the optical path from the DC-RX (input port) to the DC-TX (output port). The switch configuration selects the requested CD value and combines the four spools based on the 16 chromatic dispersion compensation values fetched. The photodiodes PD1 and PD2 are used to monitor the input and output ports respectively. Figure 6-6 Block Diagram of TDC-CC and TDC-FC 6.3.5 Lamp Test The TDC-CC and TDC-FC cards support a lamp test function that is activated either from the ONS 15454 front panel or CTC to ensure that all LEDs are functional. 6.3.6 TDC-CC and TDC-FC Card-Level Indicators Table 6-3 lists the card-level LEDs on the TDC-CC and TDC-FC cards. 276445 2x2 Switch D1 2x2 Switch D2 2x2 Switch D3 2x2 Switch D4 S1 S2 S3 S4 DC-RX DC-TX PD1 PD26-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units Monitoring Optical Performance 6.4 Monitoring Optical Performance The TDC-CC and TDC-FC cards monitor the optical input power and optical output power of the fiber. It monitors the insertion loss from the input (DC-RX) to the output (DC-TX) port, with the help of the two photodiodes PD1 and PD2. The TDC-CC and TDC-FC cards report the minimum, average, and maximum power statistics of each of the monitored ports or channels in the specific card. To view the optical power statistics of the TDC-CC and TDC-FC cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. The performance data is recorded at 15 minutes and 24 hours intervals. Note You can view the performance monitoring (PM) data of the card using CTC, SNMP, and TL1 interfaces. Note The PM data is stored on a wrap-around basis at 32 x 15 min and 2 x 24 hour intervals. Table 6-3 TDC-CC and TDC-FC Card-Level Indicators Card-Level LED Description Red FAIL LED The 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. ACT/STBY LED Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or both ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The Amber SF LED indicates a signal failure or condition such as LOS and LOF on one or more of the card ports. The amber SF LED is also ON if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns OFF.6-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 6 Tunable Dispersion Compensating Units Monitoring Optical PerformanceCHAPTER 7-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 7 Protection Switching Module This chapter describes the Protection Switching Module (PSM) card used in Cisco ONS 15454 dense wavelength division multiplexing (DWDM) networks. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 7.1 PSM Card Overview • 7.2 Key Features • 7.3 PSM Block Diagram • 7.4 PSM Faceplate Ports • 7.5 PSM Card-Level Indicators • 7.6 PSM Bidirectional Switching 7.1 PSM Card Overview The PSM card performs splitter protection functions. In the transmit (TX) section of the PSM card (see Figure 7-1), the signal received on the common receive port is duplicated by a hardware splitter to both the working and protect transmit ports. In the receive (RX) section of the PSM card (Figure 7-1), a switch is provided to select one of the two input signals (on working and protect receive ports) to be transmitted through the common transmit port. The PSM card supports multiple protection configurations: • Channel protection—The PSM COM ports are connected to the TXP/MXP trunk ports. • Line (or path) protection—The PSM working (W) and protect (P) ports are connected directly to the external line. • Multiplex section protection—The PSM is equipped between the MUX/DMX stage and the amplification stage. • Standalone—The PSM can be equipped in any slot and supports all node configurations.7-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 7 Protection Switching Module Key Features The PSM card is a single-slot card that can be installed in any node from Slot 1 to 6 and 12 to 17. The PSM card includes six LC-PC-II optical connectors on the front panel. In channel protection configuration, the PSM card can be installed in a different shelf from its peer TXP/MXP card. Note It is strongly recommended that you use the default layouts designed by Cisco Transport Planner, which place the PSM card and its peer TXP/MXP card as close as possible to simplify cable management. For more information on the node configurations supported for the PSM card, see the “11.3 Supported Node Configurations for PSM Card” section on page 11-38. For more information on the network topologies supported for the PSM card, see the “12.6 Network Topologies for the PSM Card” section on page 12-19. 7.2 Key Features The PSM card provides the following features: • Operates over the C-band (wavelengths from 1529 nm to 1562.5 nm) and L-band (wavelengths from 1570.5 nm to 1604 nm) of the optical spectrum. • Implements bidirectional nonrevertive protection scheme. For more details on bidirectional switching, see the “7.6 PSM Bidirectional Switching” section on page 7-5. • Supports automatic creation of splitter protection group when the PSM card is provisioned. • Supports switching priorities based on ITU-T G.873.1. • Supports performance monitoring and alarm handling with settable thresholds. • Supports automatic laser shutdown (ALS), a safety mechanism used in the event of a fiber cut. ALS is applicable only in line protection configuration. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. For information about using the card to implement ALS in a network, see the “12.11 Network Optical Safety” section on page 12-27. 7.3 PSM Block Diagram Figure 7-1 shows a simplified block diagram of the PSM card.7-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 7 Protection Switching Module PSM Faceplate Ports Figure 7-1 PSM Block Diagram 7.4 PSM Faceplate Ports The PSM card has six optical ports located on the faceplate: • COM-RX (receive) is the input signal port. • COM-TX (transmit) is the output signal port. • W-RX is the working input signal port (receive section). • W-TX is the working output signal port (transmit section). • P-RX is the protect input signal port (receive section). • P-TX is the protect output signal port (transmit section). All ports are equipped with photodiodes to monitor optical power and other related thresholds. The COM-RX port is equipped with a virtual photodiode (firmware calculations of port optical power) to monitor optical power. The W-RX, P-RX, W-TX, and P-TX ports have optical power regulation, which are provided by variable optical attenuators (VOA). All VOAs equipped within the PSM card work in control attenuation mode. Figure 7-2 shows the PSM card faceplate. 270910 TX Section RX Section COM-RX W-TX P-TX W-RX P-RX COM-TX PD5 VOA3 1x2 Switch 50/50 Splitter PD2 PD4 PD3 VOA1 PD1 VOA2 Virtual PD7-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 7 Protection Switching Module PSM Card-Level Indicators Figure 7-2 PSM Card Faceplate 7.5 PSM Card-Level Indicators Table 7-1 shows the three card-level indicators on the PSM card. 270911 PSM FAIL ACT SF P COM RX TX RX TX RX TX W 1345567 Any of the 12 general purpose slots Table 7-1 PSM Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists.7-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 7 Protection Switching Module PSM Bidirectional Switching 7.6 PSM Bidirectional Switching A VOA is equipped after the hardware splitter within the PSM card. The VOA implements bidirectional switching when there is a single fiber cut in a protection configuration involving two peer PSM cards. Figure 7-3 shows a sample configuration that explains the bidirectional switching capability of the PSM card. Figure 7-3 PSM Bidirectional Switching In this example, there is a fiber cut in the working path from Station A to Station B as shown in Figure 7-3. As a result of the fiber cut, an LOS alarm is raised on the W-RX port of Station B and it immediately switches traffic on to its P-RX port. Station B simultaneously also stops transmission (for approximately 25 milliseconds) on its W-TX port, which raises an LOS alarm on the W-RX port of Station A. This causes Station A to also switch traffic to its P-RX port. In this way, PSM implements bidirectional switching without any data exchange between the two stations. Since the two stations do not communicate using signaling protocols (overhead bytes), a Manual or Force protection switch on the PSM card is implemented by creating a traffic hit. For example, consider that you perform a Manual or Force protection switch on Station A. The TX VOA on the active path is set to automatic VOA shutdown (AVS) state for 25 milliseconds. This causes Station B to switch traffic to the other path because it cannot differentiate between a maintenance operation and a real fail. After 25 milliseconds, the VOA in Station A is automatically reset. However, Station B will not revert back by itself because of nonrevertive switching protection scheme used in the PSM card. Green ACT LED The green ACT LED indicates that the PSM is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off. Table 7-1 PSM Card-Level Indicators (continued) Card-Level Indicators Description 270915 TX Section RX Section COM-RX W-TX P-TX W-RX P-RX W-RX P-RX W-TX P-TX COM-TX PD5 RX Section TX Section COM-TX COM-RX PD3 PD4 PD2 PD1 A B PD3 PD4 PD2 PD1 PD57-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 7 Protection Switching Module PSM Bidirectional Switching To effectively implement switching, the Lockout and Force commands must be performed on both the stations. If these commands are not performed on both the stations, the far-end and near-end PSMs can be misaligned. In case of misalignment, when a path recovers, traffic might not recover automatically. You might have to perform a Force protection switch to recover traffic. Note The order in which you repair the paths is important in the event of a double failure (both the working and protect paths are down due to a fiber cut) on the PSM card in line protection configuration when the active path is the working path. If you repair the working path first, traffic is automatically restored. However, if you repair the protect path first, traffic is not automatically restored. You must perform a Force protection switch to restore traffic on the protect path.CHAPTER 8-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 8 Optical Add/Drop Cards This chapter describes optical add/drop cards used in Cisco ONS 15454 dense wavelength division multiplexing (DWDM) networks. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 8.1 Card Overview, page 8-1 • 8.2 Class 1M Laser Product Safety Lasers, page 8-8 • 8.3 AD-1C-xx.x Card, page 8-11 • 8.4 AD-2C-xx.x Card, page 8-14 • 8.5 AD-4C-xx.x Card, page 8-18 • 8.6 AD-1B-xx.x Card, page 8-22 • 8.7 AD-4B-xx.x Card, page 8-25 8.1 Card Overview The card overview section contains card overview, software compatibility, interface class, and channel allocation information for optical add/drop cards. 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. For a list of slots and symbols, see the "Card Slot Requirements" section in the Cisco ONS 15454 Hardware Installation Guide. Optical add/drop cards are divided into two groups: band optical add/drop multiplexer (OADM) cards and channel OADM cards. Band OADM cards add and drop one or four bands of adjacent channels. The cards in this chapter, including the 4-Band OADM (AD-4B-xx.x) and the 1-Band OADM (AD-1B-xx.x) 8-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Card Overview are utilized only in the C band. Channel OADM cards add and drop one, two, or four adjacent channels; they include the 4-Channel OADM (AD-4C-xx.x), the 2-Channel OADM (AD-2C-xx.x), and the 1-Channel OADM (AD-1C-xx.x). Note For information about L band add and drop capability, see Chapter 9, “Reconfigurable Optical Add/Drop Cards.” 8.1.1 Card Summary Table 8-1 lists and summarizes the functions of the optical add/drop cards. 8.1.2 Card Compatibility Table 8-2 lists the CTC software compatibility for each optical add/drop card. Table 8-1 Optical Add/Drop Cards Card Port Description For Additional Information AD-1C-xx.x The AD-1C-xx.x card has three sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “8.3 AD-1C-xx.x Card” section on page 8-11. AD-2C-xx.x The AD-2C-xx.x card has four sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “8.4 AD-2C-xx.x Card” section on page 8-14. AD-4C-xx.x The AD-4C-xx.x card has six sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “8.5 AD-4C-xx.x Card” section on page 8-18. AD-1B-xx.x The AD-1B-xx.x card has three sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “8.6 AD-1B-xx.x Card” section on page 8-22. AD-4B-xx.x The AD-4B-xx.x card has six sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “8.7 AD-4B-xx.x Card” section on page 8-25.8-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Card Overview 8.1.3 Interface Classes The AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, and AD-4B-xx.x cards have different input and output optical channel signals depending on the interface card where the input signal originates from. The input interface cards have been grouped in classes listed in Table 8-3. The subsequent tables list the optical performances and output power of each interface class. Table 8-2 Software Release Compatibility for Optical Add/Drop Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.2 AD-1C-xx.x 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454- DWD M 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWDM 15454- DWDM 15454 -DWD M 15454- DWDM , 15454- M2, 15454- M6 AD-2C-xx.x 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454- DWD M 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWDM 15454- DWDM 15454 -DWD M 15454- DWDM , 15454- M2, 15454- M6 AD-4C-xx.x 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454- DWD M 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWDM 15454- DWDM 15454 -DWD M 15454- DWDM , 15454- M2, 15454- M6 AD-1B-xx.x 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454- DWD M 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWDM 15454- DWDM 15454 -DWD M 15454- DWDM AD-4B-xx.x 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454- DWD M 15454- DWD M 15454 -DW DM 15454- DWD M 15454- DWDM 15454- DWDM 15454 -DWD M 15454- DWDM8-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Card Overview Table 8-4 lists the optical performance parameters for 40-Gbps cards that provide signal input to the optical add/drop cards. Table 8-3 ONS 15454 Card Interfaces Assigned to Input Power Classes Input Power Class Card A 10-Gbps multirate transponder cards (TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L) with forward error correction (FEC) enabled, 10-Gbps muxponder cards (MXP_2.5G_10G, MXP_2.5G_10E, MXP_MR_10DME_C, MXP_MR_10DME_L, MXP_2.5G_10E_C, and MXP_2.5G_10E_L) with FEC enabled, and 40-Gbps muxponder card (40G-MXP-C) B 10-Gbps multirate transponder card (TXP_MR_10G) without FEC and the 10-Gbps muxponder card (MXP_2.5G_10G, MXP_MR_10DME_C, MXP_MR_10DME_L), and 40-Gbps muxponder card (40G-MXP-C), and ADM-10G cards with FEC disabled C OC-192 LR ITU cards (TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L) without FEC D 2.5-Gbps multirate transponder card (TXP_MR_2.5G), both protected and unprotected, with FEC enabled E OC-48 100-GHz DWDM muxponder card (MXP_MR_2.5G) and 2.5-Gbps multirate transponder card (TXP_MR_2.5G), both protected and unprotected, with FEC disabled and retime, reshape, and regenerate (3R) mode enabled F 2.5-Gbps multirate transponder card (TXP_MR_2.5G), both protected and unprotected, in regenerate and reshape (2R) mode G OC-48 ELR 100 GHz card H 2/4 port GbE transponder (GBIC WDM 100GHz) I TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L cards with enhanced FEC (E-FEC) and the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_10DME_C, MXP_MR_10DME_L, and 40G-MXP-C cards with E-FEC enabled Table 8-4 40-Gbps Interface Optical Performance Parameter Class A Class B Class I Type Power Limited OSNR1 Limited (if appl.) Power Limited OSNR Limited (if appl.) Power Limited OSNR Limited (if appl.) Maximum bit rate 40 Gbps 40 Gbps 40 Gbps Regeneration 3R 3R 3R FEC Yes No Yes (E-FEC) Threshold Optimum Average Optimum Maximum BER2 10–15 10–12 10–15 OSNR1 sensitivity 23 dB 9 dB 23 dB 19 dB 20 dB 8 dB Power sensitivity –24 dBm –18 dBm –21 dBm –20 dBm –26 dBm –18 dBm8-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Card Overview Table 8-5 lists the optical performance parameters for 40-Gbps cards that provide signal input to the optical add/drop cards. Power overload –8 dBm –8 dBm –8 dBm Transmitted Power Range3 OC-192 LR ITU — — — Dispersion compensation tolerance +/–800 ps/nm +/–1,000 ps/nm +/–800 ps/nm 1. OSNR = optical signal-to-noise ratio 2. BER = bit error rate 3. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 8-4 40-Gbps Interface Optical Performance (continued) Parameter Class A Class B Class I Type Power Limited OSNR1 Limited (if appl.) Power Limited OSNR Limited (if appl.) Power Limited OSNR Limited (if appl.) Table 8-5 10-Gbps Interface Optical Performance Parameter Class A Class B Class C Class I Type Power Limited OSNR1 Limited (if appl.) Power Limited OSNR Limited (if appl.) OSNR Limited Power Limited OSNR Limited (if appl.) Maximum bit rate 10 Gbps 10 Gbps 10 Gbps 10 Gbps Regeneration 3R 3R 3R 3R FEC Yes No No Yes (E-FEC) Threshold Optimum Average Average Optimum Maximum BER2 10–15 10–12 10–12 10–15 OSNR1 sensitivity 23 dB 9 dB 23 dB 19 dB 19 dB 20 dB 8 dB Power sensitivity –24 dBm –18 dBm –21 dBm –20 dBm –22 dBm –26 dBm –18 dBm Power overload –8 dBm –8 dBm –9 dBm –8 dBm Transmitted Power Range3 10-Gbps multirate transponder/10-Gbps FEC transponder (TXP_MR_10G) +2.5 to 3.5 dBm +2.5 to 3.5 dBm — — OC-192 LR ITU — — +3.0 to 6.0 dBm —8-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Card Overview 2.5-Gbps cards that provide signal input to the optical add/drop cards have the interface performance parameters listed in Table 8-6. 10-Gbps multirate transponder/10-Gbps FEC transponder (TXP_MR_10E) +3.0 to 6.0 dBm +3.0 to 6.0 dBm — +3.0 to 6.0 dBm Dispersion compensation tolerance +/–800 ps/nm +/–1,000 ps/nm +/–1,000 ps/nm +/–800 ps/nm 1. OSNR = optical signal-to-noise ratio 2. BER = bit error rate 3. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 8-5 10-Gbps Interface Optical Performance (continued) Parameter Class A Class B Class C Class I Type Power Limited OSNR1 Limited (if appl.) Power Limited OSNR Limited (if appl.) OSNR Limited Power Limited OSNR Limited (if appl.) Table 8-6 2.5-Gbps Interface Optical Performance Parameter Class D Class E Class F Class G Class H Class J Type Power Limited OSNR Limited (if appl.) Power Limited OSNR Limited (if appl.) OSNR Limited Power Limited OSNR Limited (if appl.) Power Limited OSNR Limited (if appl.) Power Limited Maximum bit rate 2.5 Gbps 2.5 Gbps 2.5 Gbps 2.5 Gbps 1.25 Gbps 2.5 Gbps Regeneration 3R 3R 2R 3R 3R 3R FEC Yes No No No No No Threshold Average Average Average Average Average Average Maximum BER 10–15 10–12 10–12 10–12 10–12 10–12 OSNR sensitivity 14 dB 6 dB 14 dB 10 dB 15 dB 14 dB 11 dB 13 dB 8 dB 12 dB Power sensitivity –31 dBm –25 dBm –30 dBm –23 dBm –24 dBm –27 dBm –33 dBm –28 dBm –18 dBm –26 dBm Power overload –9 dBm –9 dBm –9 dBm –9 dBm –7 dBm –17dBm Transmitted Power Range1 TXP_MR_2.5G –1.0 to 1.0 dBm –1.0 to 1.0 dBm –1.0 to 1.0 dBm –2.0 to 0 dBm — — TXPP_MR_2.5G –4.5 to –2.5 dBm –4.5 to –2.5 dBm –4.5 to –2.5 dBm MXP_MR_2.5G — +2.0 to +4.0 dBm — MXPP_MR_2.5G — –1.5 to +0.5 dBm —8-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Card Overview 8.1.4 DWDM Card Channel Allocation Plan ONS 15454 DWDM channel OADM and band OADM cards are designed for use with specific channels in the C band. In most cases, the channels for these cards are either numbered (for example, 1 to 32) or delimited (odd or even). Client interfaces must comply with these channel assignments to be compatible with the ONS 15454 system. Table 8-7 lists the channel IDs and wavelengths assigned to the C-band DWDM channels. Note In some cases, a card uses only some or all of the channels listed in a band. Also, some cards use channels on the 100-GHz ITU-T grid while others use channels on the 50-GHz ITU-T grid. See specific card descriptions in Appendix A, “Hardware Specifications,” for more details. 2/4 port GbE Transponder (GBIC WDM 100GHz) — — — — +2.5 to 3.5 dBm — Dispersion compensation tolerance –1200 to +5400 ps/nm –1200 to +5400 ps/nm –1200 to +3300 ps/nm –1200 to +3300 ps/nm –1000 to +3600 ps/nm –1000 to +3200 ps/nm 1. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 8-6 2.5-Gbps Interface Optical Performance (continued) Parameter Class D Class E Class F Class G Class H Class J Type Power Limited OSNR Limited (if appl.) Power Limited OSNR Limited (if appl.) OSNR Limited Power Limited OSNR Limited (if appl.) Power Limited OSNR Limited (if appl.) Power Limited Table 8-7 DWDM Channel Allocation Plan (C Band) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.1168-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Class 1M Laser Product Safety Lasers 8.2 Class 1M Laser Product Safety Lasers This section lists the safety labels attached to the AD-1C-xx.x, AD-2C-xx.x, AD-4c-xx.x, AD-1B-xx.x, and AD-4B-xx.xx cards. 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 8-7 DWDM Channel Allocation Plan (C Band) (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)8-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Class 1M Laser Product Safety Lasers 8.2.1 Class 1M Laser Product Statement The Class 1M Laser Product statement is shown in Figure 8-1. Figure 8-1 Class 1M Laser Product Statement Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam. Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can be harmful to the eye if the beam is viewed using magnifying optical instruments. 8.2.2 Hazard Level 1M Label The Hazard Level 1M label is shown in Figure 8-2. Figure 8-2 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. This label is displayed on the faceplate of the cards. 8.2.3 Laser Source Connector Label The Laser Source Connector label is shown in Figure 8-3. CAUTION HAZARD LEVEL 1M INVISIBLE LASER RADIATION DO NOT VIEW DIRECTLY WITH NON-ATTENUATING OPTICAL INSTRUMENTS λ = = 1400nm TO 1610nm 145953 HAZARD LEVEL 1M 1459908-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards Class 1M Laser Product Safety Lasers Figure 8-3 Laser Source Connector Label This label indicates that a laser source is present at the optical connector where the label has been placed. 8.2.4 FDA Statement Label The FDA Statement labels are shown in Figure 8-4 and Figure 8-5. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 8-4 FDA Statement Label Figure 8-5 FDA Statement Label 8.2.5 Shock Hazard Label The Shock Hazard label is shown in Figure 8-6. 96635 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 20078-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-1C-xx.x Card Figure 8-6 Shock Hazard Label This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself. 8.3 AD-1C-xx.x Card Note See the “A.9.1 AD-1C-xx.x Card Specifications” section on page A-44 for hardware specifications. The 1-Channel OADM (AD-1C-xx.x) card passively adds or drops one of the 32 channels utilized within the 100-GHz-spacing of the DWDM card system. Thirty-two versions of this card—each designed only for use with one wavelength—are used in the ONS 15454 DWDM system. Each wavelength version of the card has a different part number. The AD-1C-xx.x can be installed in Slots 1 to 6 and 12 to 17. The AD-1C-xx.x has the following internal features: • Two cascaded passive optical interferential filters perform the channel add and drop functions. • One software-controlled variable optical attenuator (VOA) regulates the optical power of the inserted channel. • Software-controlled VOA regulates the insertion loss of the express optical path. • VOA settings and functions, photodiode detection, and alarm thresholds, are internally controlled. • Virtual photodiodes (firmware calculations of port optical power) at the common DWDM output and input ports are monitored within the software. Figure 8-7 shows the AD-1C-xx.x faceplate. 655418-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-1C-xx.x Card Figure 8-7 AD-1C-xx.x Faceplate For information on safety labels for the card, see the “8.2 Class 1M Laser Product Safety Lasers” section on page 8-8. Figure 8-8 shows a block diagram of the AD-1C-xx.x card. AD-1C -X.XX FAIL ACT SF RX 15xx.xx TX RX EXP TX RX COM TX 964738-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-1C-xx.x Card Figure 8-8 AD-1C-xx.x Block Diagram Figure 8-9 shows the AD-1C-xx.x optical module functional block diagram. Figure 8-9 AD-1C-xx.x Optical Module Functional Block Diagram 8.3.1 Power Monitoring Physical photodiodes P1 through P4 and virtual photodiodes V1 and V2 monitor the power for the AD-1C-xx.x card. The returned power level values are calibrated to the ports as shown in Table 8-8. Optical Module COM RX COM TX 124074 uP8260 processor DC/DC converter EXP TX EXP RX FPGA For SCL Bus management SCL Bus TCC M SCL Bus TCC P Power supply Input filters BAT A&B Add Rx Drop Tx 98304 Control Control interface Virtual photodiode COM RX EXP RX EXP TX TX Channel 15xx.xx RX Physical photodiode Variable optical attenuator V1 P COM TX P1 P3 P5 P4 V2 P2 V Table 8-8 AD-1C-xx.x Port Calibration Photodiode CTC Type Name Calibrated to Port P1 ADD DROP RX P2 DROP DROP TX8-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-2C-xx.x Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 8.3.2 AD-1C-xx.x Card-Level Indicators The AD-1C-xx.x card has three card-level LED indicators, described in Table 8-9. 8.3.3 AD-1C-xx.x Port-Level Indicators You can find the status of the card port 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. The AD-1C-xx.x has six LC-PC-II optical ports: two for add/drop channel client input and output, two for express channel input and output, and two for communication. 8.4 AD-2C-xx.x Card Note See the “A.9.2 AD-2C-xx.x Card Specifications” section on page A-44 for hardware specifications. The 2-Channel OADM (AD-2C-xx.x) card passively adds or drops two adjacent 100-GHz channels within the same band. Sixteen versions of this card—each designed for use with one pair of wavelengths—are used in the ONS 15454 DWDM system. The card bidirectionally adds and drops in two different sections on the same card to manage signal flow in both directions. Each version of the card has a different part number. The AD-2C-xx.x has the following features: P3 IN EXP EXP RX P4 OUT EXP EXP TX V1 IN COM COM RX V2 OUT COM COM TX Table 8-8 AD-1C-xx.x Port Calibration (continued) Photodiode CTC Type Name Calibrated to Port Table 8-9 AD-1C-xx.x Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the AD-1C-xx.x card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure. The SF LED also illuminates when the transmitting and receiving fibers are incorrectly connected. When the fibers are properly connected, the LED turns off.8-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-2C-xx.x Card • Passive cascade of interferential filters perform the channel add and drop functions. • Two software-controlled VOAs in the add section, one for each add port, regulate the optical power of inserted channels. • Software-controlled VOAs regulate insertion loss on express channels. • VOA settings and functions, photodiode detection, and alarm thresholds are internally controlled. • Virtual photodiodes (firmware calculation of port optical power) at the common DWDM output and input ports are monitored within the software. Figure 8-10 shows the AD-2C-xx.x faceplate. Figure 8-10 AD-2C-xx.x Faceplate For information on safety labels for the card, see the “8.2 Class 1M Laser Product Safety Lasers” section on page 8-8. AD-2C -X.XX FAIL ACT SF RX 15xx.xx TX RX 15xx.xx TX RX EXP TX RX COM TX 964748-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-2C-xx.x Card Figure 8-11 shows a block diagram of the AD-2C-xx.x card. Figure 8-11 AD-2C-xx.x Block Diagram Figure 8-12 shows the AD-2C-xx.x optical module functional block diagram. Figure 8-12 AD-2C-xx.x Optical Module Functional Block Diagram 8.4.1 Wavelength Pairs The AD-2C-xx.x cards are provisioned for the wavelength pairs listed in Table 8-10. In this table, channel IDs are given rather than wavelengths. To compare channel IDs with the actual wavelengths they represent, see wavelengths in Table 8-7 on page 8-7. Optical Module COM RX COM TX 98305 uP8260 processor DC/DC converter EXP TX EXP RX FPGA For SCL Bus management SCL Bus TCC M SCL Bus TCC P Power supply input filters BAT A&B Add RX Drop TX Add RX Drop TX CH 1 CH 2 98306 Control Control interface Virtual photodiode COM RX EXP RX EXP TX TX Second channel TX RX RX Physical photodiode Variable optical attenuator V V1 V2 COM TX First channel P1 P P3 P4 P2 P5 P7 P68-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-2C-xx.x Card 8.4.2 Power Monitoring Physical photodiodes P1 through P10 and virtual photodiodes V1 and V2 monitor the power for the AD-2C-xx.x card. The returned power level values are calibrated to the ports as shown in Table 8-11. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 8.4.3 AD-2C-xx.x Card-Level Indicators The AD-2C-xx.x card has three card-level LED indicators, described in Table 8-12. Table 8-10 AD-2C-xx.x Channel Pairs Band ID Add/Drop Channel ID Band 30.3 (A) 30.3, 31.2 31.9, 32.6 Band 34.2 (B) 34.2, 35.0 35.8, 36.6 Band 38.1 (C) 38.1, 38.9 39.7, 40.5 Band 42.1 (D) 42.1, 42.9 43.7, 44.5 Band 46.1 (E) 46.1, 46.9 47.7, 48.5 Band 50.1 (F) 50.1, 50.9 51.7, 52.5 Band 54.1 (G) 54.1, 54.9 55.7, 56.5 Band 58.1 (H) 58.1, 58.9 59.7, 60.6 Table 8-11 AD-2C-xx.x Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P2 ADD COM TX P3–P4 DROP DROP TX P5 IN EXP EXP RX P6 OUT EXP EXP TX V1 IN COM COM RX V2 OUT COM COM TX8-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4C-xx.x Card 8.4.4 AD-2C-xx.x Port-Level Indicators You can find the status of the card port 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. The AD-2C-xx.x card has eight LC-PC-II optical ports: four for add/drop channel client input and output, two for express channel input and output, and two for communication. 8.5 AD-4C-xx.x Card Note See the “A.9.3 AD-4C-xx.x Card Specifications” section on page A-45 for hardware specifications. The 4-Channel OADM (AD-4C-xx.x) card passively adds or drops all four 100-GHz-spaced channels within the same band. Eight versions of this card—each designed for use with one band of wavelengths—are used in the ONS 15454 DWDM system. The card bidirectionally adds and drops in two different sections on the same card to manage signal flow in both directions. There are eight versions of this card with eight part numbers. The AD-4C-xx.x has the following features: • Passive cascade of interferential filters perform the channel add and drop functions. • Four software-controlled VOAs in the add section, one for each add port, regulate the optical power of inserted channels. • Two software-controlled VOAs regulate insertion loss on express and drop path, respectively. • Internal control of the VOA settings and functions, photodiode detection, and alarm thresholds. • Software-monitored virtual photodiodes (firmware calculation of port optical power) at the common DWDM output and input ports. Figure 8-13 shows the AD-4C-xx.x faceplate. Table 8-12 AD-2C-xx.x Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the AD-2C-xx.x card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.8-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4C-xx.x Card Figure 8-13 AD-4C-xx.x Faceplate For information on safety labels for the card, see the “8.2 Class 1M Laser Product Safety Lasers” section on page 8-8. Figure 8-14 shows a block diagram of the AD-4C-xx.x card. AD-4C -X.XX FAIL ACT SF RX 15xx.xx TX RX 15xx.xx TX RX 15xx.xx TX RX 15xx.xx TX RX EXP TX RX COM TX 964758-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4C-xx.x Card Figure 8-14 AD-4C-xx.x Block Diagram Figure 8-15 shows the AD-4C-xx.x optical module functional block diagram. Figure 8-15 AD-4C-xx.x Optical Module Functional Block Diagram 8.5.1 Wavelength Sets The AD-4C-xx.x cards are provisioned for the sets of four 100-GHz-spaced wavelengths shown Table 8-13 on page 8-21. Optical Module COM RX COM TX 124075 uP8260 processor DC/DC converter EXP TX EXP RX FPGA For SCL Bus management SCL Bus TCC M SCL Bus TCC P Power supply Input filters BAT A&B Add Rx Drop Tx Channel 1 Add Rx Drop Tx Channel 2 Add Rx Drop Tx Channel 3 Add Rx Drop Tx Channel 4 98299 Control Control interface 4Ch OADM module Virtual photodiode COM RX COM TX EXP RX EXP TX TX Channels RX Channels Physical photodiode Variable optical attenuator V V1 V2 P1 P9 P11 P10 P12 P2 P3 P4 P5 P6 P7 P8 P8-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4C-xx.x Card 8.5.2 Power Monitoring Physical photodiodes P1 through P10 and virtual photodiodes V1 and V2 monitor the power for the AD-4C-xx.x card. The returned power level values are calibrated to the ports as shown in Table 8-14. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 8.5.3 AD-4C-xx.x Card-Level Indicators The AD-4C-xx.x card has three card-level LED indicators, described in Table 8-15. Table 8-13 AD-4C-xx.x Channel Sets Band ID Add/Drop Wavelengths Band 30.3 (A) 1530.3, 1531.2, 1531.9, 1532.6 Band 34.2 (B) 1534.2, 1535.0, 1535.8, 1536.6 Band 38.1 (C) 1538.1, 1538.9, 1539.7, 1540.5 Band 42.1 (D) 1542.1, 1542.9, 1543.7, 1544.5 Band 46.1 (E) 1546.1, 1546.9, 1547.7, 1548.5 Band 50.1 (F) 1550.1, 1550.9, 1551.7, 1552.5 Band 54.1 (G) 1554.1, 1554.9, 1555.7, 1556.5 Band 58.1 (H) 1558.1, 1558.9, 1559.7, 1560.6 Table 8-14 AD-4C-xx.x Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P4 ADD COM TX P5–P8 DROP DROP TX P9 IN EXP EXP RX P10 OUT EXP EXP TX V1 IN COM COM RX V2 OUT COM COM TX Table 8-15 AD-4C-xx.x Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists.8-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-1B-xx.x Card 8.5.4 AD-4C-xx.x Port-Level Indicators You can find the status of the card port 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. The AD-4C-xx.x card has 12 LC-PC-II optical ports: eight for add/drop channel client input and output, two for express channel input and output, and two for communication. 8.6 AD-1B-xx.x Card (Cisco ONS 15454 only) Note See the “A.9.4 AD-1B-xx.x Card Specifications” section on page A-47 for hardware specifications. The 1-Band OADM (AD-1B-xx.x) card passively adds or drops a single band of four adjacent 100-GHz-spaced channels. Eight versions of this card with eight different part numbers—each version designed for use with one band of wavelengths—are used in the ONS 15454 DWDM system. The card bidirectionally adds and drops in two different sections on the same card to manage signal flow in both directions. This card can be used when there is asymmetric adding and dropping on each side (east or west) of the node; a band can be added or dropped on one side but not on the other. The AD-1B xx.x can be installed in Slots 1 to 6 and 12 to17 and has the following features: • Passive cascaded interferential filters perform the channel add and drop functions. • Two software-controlled VOAs regulate the optical power flowing in the express and drop OADM paths (drop section). • Output power of the dropped band is set by changing the attenuation of the VOA drop. • The VOA express is used to regulate the insertion loss of the express path. • VOA settings and functions, photodiode detection, and alarm thresholds are internally controlled. • Virtual photodiode (firmware calculation of port optical power) at the common DWDM output are monitored within the software. Figure 8-16 shows the AD-1B-xx.x faceplate. Green ACT LED The green ACT LED indicates that the AD-4C-xx.x card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure or condition. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off. Table 8-15 AD-4C-xx.x Card-Level Indicators (continued) Card-Level Indicators Description8-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-1B-xx.x Card Figure 8-16 AD-1B-xx.x Faceplate For information on safety labels for the card, see the “8.2 Class 1M Laser Product Safety Lasers” section on page 8-8. Figure 8-17 shows a block diagram of the AD-1B-xx.x card. AD-1B -X.XX FAIL ACT SF RX XX.X TX RX EXP TX RX COM TX 964718-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-1B-xx.x Card Figure 8-17 AD-1B-xx.x Block Diagram Figure 8-18 shows the AD-1B-xx.x optical module functional block diagram. Figure 8-18 AD-1B-xx.x Optical Module Functional Block Diagram 8.6.1 Power Monitoring Physical photodiodes P1 through P4 and virtual photodiodes V1 and V2 monitor the power for the AD-1B-xx.x card. The returned power level values are calibrated to the ports as shown in Table 8-16. Optical Module COM RX COM TX 124073 uP8260 processor DC/DC converter EXP TX EXP RX FPGA For SCL Bus management SCL Bus TCC M SCL Bus TCC P Power supply Input filters BAT A&B Band xx.x Rx Band xx.x Tx 98307 Control Control interface Virtual photodiode COM RX EXP RX EXP TX TX Band xx.x Physical photodiode RX Physical photodiode V V2 V1 COM TX P1 P3 P5 P4 P2 P Table 8-16 AD-1B-xx.x Port Calibration Photodiode CTC Type Name Calibrated to Port P1 ADD BAND RX P2 DROP BAND TX8-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4B-xx.x Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 8.6.2 AD-1B-xx.x Card-Level Indicators The AD-1B-xx.x card has three card-level LED indicators, described in Table 8-17. 8.6.3 AD-1B-xx.x Port-Level Indicators You can find the status of the card port 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. The AD-1B-xx.x has six LC-PC-II optical ports: two for add/drop channel client input and output, two for express channel input and output, and two for communication. 8.7 AD-4B-xx.x Card (Cisco ONS 15454 only) The 4-Band OADM (AD-4B-xx.x) card passively adds or drops four bands of four adjacent 100-GHz-spaced channels. Two versions of this card with different part numbers—each version designed for use with one set of bands—are used in the ONS 15454 DWDM system. The card bidirectionally adds and drops in two different sections on the same card to manage signal flow in both directions. This card can be used when there is asymmetric adding and dropping on each side (east or west) of the node; a band can be added or dropped on one side but not on the other. The AD1B-xx.x can be installed in Slots 1 to 6 and 12 to 17 and has the following features: P3 IN EXP EXP RX P4 OUT EXP EXP TX V1 IN COM COM RX V2 OUT COM COM TX Table 8-16 AD-1B-xx.x Port Calibration (continued) Photodiode CTC Type Name Calibrated to Port Table 8-17 AD-1B-xx.x Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the AD-1B-xx.x card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.8-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4B-xx.x Card • Five software-controlled VOAs regulate the optical power flowing in the OADM paths. • Output power of each dropped band is set by changing the attenuation of each VOA drop. • The VOA express is used to regulate the insertion loss of the express path. • VOA settings and functions, photodiode detection, and alarm thresholds are internally controlled. • Virtual photodiode (firmware calculation of port optical power) at the common DWDM output port are monitored within the software. Figure 8-19 shows the AD-4B-xx.x faceplate. Figure 8-19 AD-4B-xx.x Faceplate For information on safety labels for the card, see the “8.2 Class 1M Laser Product Safety Lasers” section on page 8-8. Figure 8-20 shows a block diagram of the AD-4B-xx.x card. AD-4B -X.XX FAIL ACT SF RX XX.X TX RX XX.X TX RX XX.X TX RX XX.X TX RX EXP TX RX COM TX 964728-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4B-xx.x Card Figure 8-20 AD-4B-xx.x Block Diagram Figure 8-21 shows the AD-4B-xx.x optical module functional block diagram. Figure 8-21 AD-4B-xx.x Optical Module Functional Block Diagram 8.7.1 Power Monitoring Physical photodiodes P1 through P11 and virtual photodiode V1 monitor the power for the AD-4B-xx.x card. The returned power level values are calibrated to the ports as shown in Table 8-18. Optical Module COM RX COM TX 124075 uP8260 processor DC/DC converter EXP TX EXP RX FPGA For SCL Bus management SCL Bus TCC M SCL Bus TCC P Power supply Input filters BAT A&B Add Rx Drop Tx Channel 1 Add Rx Drop Tx Channel 2 Add Rx Drop Tx Channel 3 Add Rx Drop Tx Channel 4 Virtual photodiode COM RX TX B30.3 or B46.1 RX Control Control interface Physical photodiode Variable optical attenuator V V1 EXP RX EXP TX COM TX TX B34.2 or B50.1 RX TX B38.1 or B54.1 RX TX RX B42.1 or B58.1 98308 P1 P P2 P3 P4 P9 P11 P12 P10 P5 P6 P7 P88-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 8 Optical Add/Drop Cards AD-4B-xx.x Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 8.7.2 AD-4B-xx.x Card-Level Indicators The AD-4B-xx.x card has three card-level LED indicators, described in Table 8-19. 8.7.3 AD-4B-xx.x Port-Level Indicators You can find the status of the card port 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. The AD-4B-xx.x has 12 LC-PC-II optical ports: eight for add/drop band client input and output, two for express channel input and output, and two for communication. Table 8-18 AD-4B-xx.x Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P4 ADD COM TX P5–P8 DROP DROP TX P9 IN EXP EXP RX P10 OUT EXP EXP TX P11 IN COM COM RX V1 OUT COM COM TX Table 8-19 AD-4B-xx.x Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the AD-4B-xx.x card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.CHAPTER 9-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 9 Reconfigurable Optical Add/Drop Cards This chapter describes the Cisco ONS 15454 cards deployed in reconfigurable optical add/drop (ROADM) networks. For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 9.1 Card Overview, page 9-2 • 9.2 Safety Labels for Class 1M Laser Product Cards, page 9-14 • 9.3 32WSS Card, page 9-16 • 9.4 32WSS-L Card, page 9-23 • 9.5 32DMX Card, page 9-30 • 9.6 32DMX-L Card, page 9-35 • 9.7 40-DMX-C Card, page 9-40 • 9.8 40-DMX-CE Card, page 9-45 • 9.9 40-MUX-C Card, page 9-50 • 9.10 40-WSS-C Card, page 9-55 • 9.11 40-WSS-CE Card, page 9-61 • 9.12 40-WXC-C Card, page 9-68 • 9.13 80-WXC-C Card, page 9-74 • 9.14 Single Module ROADM (SMR-C) Cards, page 9-81 • 9.15 MMU Card, page 9-929-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview Note This chapter contains information about cards that perform mesh topology functions. Multiplexer and demultiplexer cards that do not perform these functions are described in Chapter 5, “Multiplexer and Demultiplexer Cards.” 9.1 Card Overview The ROADM cards include six add drop cards utilized in the C-band (32WSS, 32DMX, 32DMX-C, 40-MUX-C, 40-WXC-C, 80-WXC-C, and MMU), two add drop cards utilized for the L-band (32WSS-L, and 32DMX-L), and two single module ROADM (SMR) cards utilized in the C-band (40-SMR1-C and 40-SMR2-C). This section provides card summary, compatibility, channel allocation, and safety information. 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 that have the same symbols. For a list of slots and symbols, see the "Card Slot Requirements" section in the Cisco ONS 15454 Hardware Installation Guide. 9.1.1 Card Summary Table 9-1 lists and summarizes information about each ROADM card. Table 9-1 ROADM Card Summary Card Port Description For Additional Information 32WSS The 32WSS card has seven sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.3 32WSS Card” section on page 9-16 32WSS-L The 32WSS-L card has seven sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.4 32WSS-L Card” section on page 9-23 32DMX The 32DMX has five sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “9.5 32DMX Card” section on page 9-30 32DMX-L The 32DMX-L has five sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “9.6 32DMX-L Card” section on page 9-35 40-DMX-C The 40-DMX-C has six sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “9.7 40-DMX-C Card” section on page 9-40 40-DMX-CE The 40-DMX-CE has six sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “9.8 40-DMX-CE Card” section on page 9-45 40-MUX-C The 40-MUX-C has six sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “9.9 40-MUX-C Card” section on page 9-50.9-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview 9.1.2 Card Compatibility Table 9-2 lists the Cisco Transport Controller (CTC) software compatibility for the ROADM cards. 40-WSS-C The 40-WSS-C card has eight sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.10 40-WSS-C Card” section on page 9-55 40-WSS-CE The 40-WSS-CE card has eight sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.11 40-WSS-CE Card” section on page 9-61 40-WXC-C The 40-WXC-C card has five sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.12 40-WXC-C Card” section on page 9-68 80-WXC-C The 80-WXC-C card has 14 ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.13 80-WXC-C Card” section on page 9-74. 40-SMR1-C The 40-SMR1-C card has six sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.14 Single Module ROADM (SMR-C) Cards” section on page 9-81 40-SMR2-C The 40-SMR2-C card has six sets of ports located on the faceplate. It operates in Slots 1 to 5 and 12 to 16. See the “9.14 Single Module ROADM (SMR-C) Cards” section on page 9-81 MMU The MMU card has six sets of ports located on the faceplate. It operates in Slots 1 to 6 and 12 to 17. See the “9.15 MMU Card” section on page 9-92 Table 9-1 ROADM Card Summary (continued) Card Port Description For Additional Information Table 9-2 Software Release Compatibility for ROADM Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.2 32WSS No No 15454- DWDM 15454- DWDM 15454- DWDM 15454- DWD M 15454- DWD M 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM 32WSS-L No No No No No 15454- DWD M 15454- DWD M 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM 40-WSS-C No No No No No No No 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 15454-M 6 40-WSS-CE No No No No No No No 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 15454-M 69-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview 32DMX No No 15454- DWDM 15454- DWDM 15454- DWDM 15454- DWD M 15454- DWD M 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 32DMX-L No No No No No 15454- DWD M 15454- DWD M 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM 40-DMX-C No No No No No No No 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 15454-M 6 40-DMX-C E No No No No No No No 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 15454-M 6 40-MUX-C No No No No No No No 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 15454-M 6 40-WXC-C No No No No No No No 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM, 15454-M 6 80-WXC-C No No No No No No No No No No No 15454-D WDM, 15454-M 6 40-SMR1-C No No No No No No No No No No 15454 -DWD M 15454-D WDM, 15454-M 2, 15454-M 6 40-SMR2-C No No No No No No No No No No 15454 -DWD M 15454-D WDM, 15454-M 2, 15454-M 6 MMU No No No No No 15454- DWD M 15454- DWD M 15454- DWD M 15454- DWD M 15454 -DWD M 15454 -DWD M 15454-D WDM Table 9-2 Software Release Compatibility for ROADM Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.29-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview 9.1.3 Interface Classes The input interface cards have been grouped in classes listed in Table 9-3. The subsequent tables list the optical performance and output power of each interface class. Table 9-3 Cisco ONS 15454 Card Interfaces Assigned to Input Power Classes Input Power Class Card A 10-Gbps multirate transponder cards (TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L), 10-Gbps muxponder cards (MXP_2.5G_10G, MXP_2.5G_10E, MXP_MR_10DME_C, MXP_MR_10DME_L, MXP_2.5G_10E_C, and MXP_2.5G_10E_L) with forward error correction (FEC) enabled, and 40-Gbps muxponder card (40G-MXP-C) B 10-Gbps multirate transponder card (TXP_MR_10G) and muxponder card (MXP_2.5G_10G) without FEC C OC-192 LR ITU cards without FEC, 10-Gbps multirate transponder (TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L) and muxponder (MXP_2.5G_10E, MXP_2.5G_10E_L, and MXP_MR_10DME_L) cards with FEC disabled D 2.5-Gbps multirate transponder card (TXP_MR_2.5G), both protected and unprotected, with FEC enabled E OC-48 100-GHz dense wavelength division multiplexing (DWDM) muxponder card (MXP_MR_2.5G) and 2.5-Gbps multirate transponder card (TXP_MR_2.5G), protected or unprotected; FEC disabled; and retime, reshape, and regenerate (3R) mode enabled F 2.5-Gbps multirate transponder card (TXP_MR_2.5G), protected or unprotected, in regenerate and reshape (2R) mode G OC-48 ELR 100 GHz card H 2/4 port GbE transponder (GBIC WDM 100GHz) I 10-Gbps multirate transponder cards (TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L) and 10-Gbps muxponder cards (MXP_2.5G_10E, MXP_2.5G_10E_L, and MXP_MR_10DME_L) with enhanced FEC (E-FEC) enabled, and 40-Gbps muxponder card (40G-MXP-C) K OC-192/STM-64 LR ITU cards without FEC, 100GHz 10Gbps Ethernet Xponder (GE_XP, GE_XPE, 10GE_XP, 10GE_XPE), Sonet/SDH add/drop (ADM_10G), OTU2 Xponder (OTU2_XP), with FEC disabled L 40Gbps Duobinary CRS-1 DWDM ITU-T line card M 2.5 Gbps DWDM ITU-T SPF N 10Gbps enhanced full tunable transponder (TXP_MR_10E_C) and muxponder (MXP_2.5G_10E_C, MXP_MR_10DME_C) with E-FEC enabled O 10Gbps Ethernet Xponder (GE_XP, GE_XPE, 10GE_XP, 10GE_XPE), 10Gbps Sonet/SDH add/drop (ADM_10G), OTU2 Xponder (OTU2_XP), with FEC enabled P 10Gbps Ethernet Xponder (GE_XP, GE_XPE, 10GE_XP, 10GE_XPE), 10Gbps Sonet/SDH add/drop (ADM_10G), OTU2 Xponder (OTU2_XP), with E-FEC enabled9-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview Table 9-4 lists the optical performance parameters for 40-Gbps cards. T 40Gbps DPSK CRS-1 DWDM ITU-T line card V OC-192/STM-64 LR ITU cards without FEC, full tunable 10Gbps Ethernet Xponder (GE_XP, GE_XPE, 10GE_XP, 10GE_XPE), Sonet/SDH add/drop (ADM_10G), OTU2 Xponder (OTU2_XP), with FEC disabled, full tunable W 10Gbps Ethernet Xponder (GE_XP, GE_XPE, 10GE_XP, 10GE_XPE), Sonet/SDH add/drop (ADM_10G), OTU2 Xponder (OTU2_XP), with FEC enabled, full tunable X 10Gbps Ethernet Xponder (GE_XP, GE_XPE, 10GE_XP, 10GE_XPE), Sonet/SDH add/drop (ADM_10G), OTU2 Xponder (OTU2_XP), with E-FEC enabled, full tunable Y 10Gbps enhanced full tunable transponder (TXP_MR_10EX_C) and muxponder (MXP_2.5G_10EX_C, MXP_MR_10DMEX_C), with FEC enabled and maximum likelihood sequence estimator (MLSE) correction Z 10Gbps enhanced full tunable transponder (TXP_MR_10EX_C) and muxponder (MXP_2.5G_10EX_C, MXP_MR_10DMEX_C), with E-FEC enabled and MLSE correction Table 9-3 Cisco ONS 15454 Card Interfaces Assigned to Input Power Classes (continued) Input Power Class Card Table 9-4 40-Gbps Interface Optical Performance Parameter Class A Class I Type Power Limited OSNR1 Limited (if appl.) 1. OSNR = optical signal-to-noise ratio Power Limited OSNR Limited (if appl.) Maximum bit rate 10 Gbps 10 Gbps Regeneration 3R 3R FEC Yes Yes (E-FEC) Threshold Optimum Optimum Maximum BER2 2. BER = bit error rate 10–15 10–15 OSNR1 sensitivity 23 dB 9 dB 20 dB 8 dB Power sensitivity –24 dBm –18 dBm –26 dBm –18 dBm Power overload –8 dBm –8 dBm Transmitted Power Range3 3. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. OC-192 LR ITU — — Dispersion compensation tolerance +/–800 ps/nm +/–800 ps/nm9-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview Table 9-5, Table 9-6, and Table 9-7 lists the optical performance parameters for 10-Gbps cards. Table 9-5 10-Gbps Interface Optical Performance (Class A, B, C, I, and K) Parameter Class A Class B Class C Class I Class K Type Power Limited OSNR1 Limited Power Limited OSNR Limit ed Power Limited OSNR Limite d Power Limited OSNR Limited Power Limited OSNR Limited Maximum bit rate 10 Gbps 10 Gbps 10 Gbps 10 Gbps 10 Gbps Regeneratio n 3R 3R 3R 3R 3R FEC Yes No No Yes (E-FEC) No Threshold Optimum Average Average Optimum Average Maximum BER2 10–15 10–12 10–12 10–15 10–12 OSNR1 sensitivity 23 dB 8.5 dB 23 dB 19 dB 19 dB 19 dB 20 dB 6 dB 23 dB3 16 dB3 23 dB4 17 dB4 23 dB5 17 dB5 Power sensitivity –24 dBm –18 dBm –21 dBm –20 dBm –22 dBm –22 dBm –26 dBm –18 dBm –24 dBm3 –17 dBm3 –23 dBm4 –18 dBm4 –23 dBm5 –17 dBm5 Power overload –8 dBm –8 dBm –9 dBm –8 dBm –7 dBm Transmitted Power Range6 10-Gbps multirate transponder/ 10-Gbps FEC transponder +2.5 to 3.5 dBm (for TXP_MR_10G) +3.0 to 6.0 dBm (for TXP_MR_10E) +2.5 to 3.5 dBm +3.0 to 6.0 dBm +3.0 to 6.0 dBm — OC-192 LR ITU — — +3.0 to 6.0 dBm — –1.0 to +3.0 dBm 10-Gbps Ethernet Xponder, Sonet/SDH Add/Drop, OTU2 Xponder — — — — –1.0 to +3.0 dBm Dispersion compensatio n tolerance +/–800 ps/nm +/–1,000 ps/nm +/–1,000 ps/nm +/–800 ps/nm –400 to +800 ps/nm9-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview 1. OSNR = optical signal-to-noise ratio 2. BER = bit error rate 3. This value is for Xen Pak XFP used with Catalyst card. 4. This value is for XFP used with Catalyst, Xponder, and ADM-10G cards. 5. This value is for X2 XFP used with Catalyst card. 6. These values, decreased by patchcord and connector losses, are also the input power values for the optical add drop multiplexer (OADM) cards. Table 9-6 10-Gbps Interface Optical Performance (Class N, O, P, and V) Parameter Class N Class O Class P Class V Type Power Limited OSNR Limited Power Limited OSNR1 Limited 1. OSNR = optical signal-to-noise ratio Power Limited OSNR Limited Power Limited OSNR Limited Maximum bit rate 10 Gbps 10 Gbps 10 Gbps 10 Gbps Regeneration 3R 3R 3R 3R FEC Yes (E-FEC) Yes Yes (E-FEC) No Threshold Optimum Optimum Optimum Average Maximum BER2 2. BER = bit error rate 10–15 10–15 10–15 10–12 OSNR1 sensitivity 19 dB 5 dB 11 dB 11 dB 23 dB 8 dB 23 dB 16 dB Power sensitivity –27 dBm –20 dBm –18 dBm –18 dBm –27 dBm –18 dBm –24 dBm –18 dBm Power overload –8 dBm –7 dBm –7 dBm –7 dBm Transmitted Power Range3 3. These values, decreased by patchcord and connector losses, are also the input power values for the optical add drop multiplexer (OADM) cards. 10-Gbps multirate transponder/10-Gbp s FEC transponder +3.0 to 6.0 dBm — — — OC-192 LR ITU — — — 0 to +3.0 dBm 10-Gbps Ethernet Xponder, Sonet/SDH Add/Drop, OTU2 Xponder — –1.0 to +3.0 dBm –1.0 to +3.0 dBm 0 to +3.0 dBm Dispersion compensation tolerance +/–800 ps/nm –500 to +1100 ps/nm –500 to +1100 ps/nm –500 to +1600 ps/nm9-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview Table 9-8 and Table 9-9 lists the optical interface performance parameters for 2.5-Gbps cards. Table 9-7 10-Gbps Interface Optical Performance (Class W, X, Y, and Z) Parameter Class W Class X Class Y Class Z Type Power Limited OSNR Limited Power Limited OSNR Limited Power Limited OSNR1 Limited 1. OSNR = optical signal-to-noise ratio Power Limited OSNR Limited Maximum bit rate 10 Gbps 10 Gbps 10 Gbps 10 Gbps Regeneration 3R 3R 3R 3R FEC Yes Yes (E-FEC) Yes Yes (E-FEC) Threshold Optimum Optimum Optimum Optimum Maximum BER2 2. BER = bit error rate 10–15 10–15 10–15 10–15 OSNR1 sensitivity 8.5 dB 8.5 dB 19 dB 5 dB 23 dB 8 dB 19 dB 5.5 dB Power sensitivity –18 dBm –18 dBm –27 dBm –20 dBm –24 dBm –20 dBm –27 dBm –20 dBm Power overload –7 dBm –7 dBm –8 dBm –8 dBm Transmitted Power Range3 3. These values, decreased by patchcord and connector losses, are also the input power values for the optical add drop multiplexer (OADM) cards. 10-Gbps multirate transponder/10-Gbps FEC transponder — — +3.0 to 6.0 dBm +3.0 to 6.0 dBm OC-192 LR ITU — — — — 10-Gbps Ethernet Xponder, Sonet/SDH Add/Drop, OTU2 Xponder 0 to +3.0 dBm 0 to +3.0 dBm — — Dispersion compensation tolerance –500 to +1100 ps/nm –500 to +1300 ps/nm –800 to +1600 ps/nm –2200 to +3700 ps/nm Table 9-8 2.5-Gbps Interface Optical Performance (Class D, E, and F) Parameter Class D Class E Class F Type Power Limited OSNR Limited Power Limited OSNR Limited Power Limited OSNR Limited Maximum bit rate 2.5 Gbps 2.5 Gbps 2.5 Gbps Regeneration 3R 3R 2R FEC Yes No No Threshold Average Average Average Maximum BER 10–15 10–12 10–12 OSNR sensitivity 14 dB 5 dB 14 dB 10 dB 15 dB 15 dB Power sensitivity –31 dBm –25 dBm –30 dBm –23 dBm –24 dBm –24 dBm Power overload –9 dBm –9 dBm –9 dBm9-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview Transmitted Power Range1 TXP_MR_2.5G and TXPP_MR_2.5G –1.0 to 1.0 dBm –1.0 to 1.0 dBm –1.0 to 1.0 dBm MXP_MR_2.5G and MXPP_MR_2.5G — +2.0 to +4.0 dBm — OC-48 ELR 100 GHz — — — 2/4 port GbE Transponder (GBIC WDM 100GHz) ——— 2.5 Gbps DWDM ITU-T SPF ——— Dispersion compensation tolerance –1200 to +5400 ps/nm –1200 to +5400 ps/nm –1200 to +3300 ps/nm 1. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 9-9 2.5-Gbps Interface Optical Performance (Class G, H, and M) Parameter Class G Class H Class M Type Power Limited OSNR Limited Power Limited OSNR Limited Power Limited OSNR Limited Maximum bit rate 2.5 Gbps 1.25 Gbps 2.5 Gbps Regeneration 3R 3R 3R FEC No No No Threshold Average Average Average Maximum BER 10–12 10–12 10–12 OSNR sensitivity 14 dB 11 dB 13 dB 8 dB 14 dB 9 dB Power sensitivity –27 dBm –23 dBm –28 dBm –18 dBm –28 dBm –22 dBm Power overload –9 dBm –7 dBm –9 dBm Transmitted Power Range1 TXP_MR_2.5G — — — TXPP_MR_2.5G — MXP_MR_2.5G –2.0 to 0 dBm MXPP_MR_2.5G — OC-48 ELR 100 GHz — — — 2/4 port GbE Transponder (GBIC WDM 100GHz) –1200 to +3300 ps/nm 0 to +3 dBm — Table 9-8 2.5-Gbps Interface Optical Performance (Class D, E, and F) (continued) Parameter Class D Class E Class F Type Power Limited OSNR Limited Power Limited OSNR Limited Power Limited OSNR Limited9-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview 9.1.4 Channel Allocation Plans ONS 15454 DWDM ROADM cards are designed for use with specific channels in the C band and L band. In most cases, the channels for these cards are either numbered (for example, 1 to 32 or 1 to 40) or delimited (odd or even). Client interfaces must comply with these channel assignments to be compatible with the ONS 15454 system. . The following cards operate in the C-band: • 32WSS • 32DMX • 32DMX-C • 40-MUX-C • 40-WXC-C • 80-WXC-C • 40-SMR1-C • 40-SMR2-C • MMU Table 9-10 lists the C-band channel IDs and wavelengths at ITU-T 50-GHz intervals. This is a comprehensive C-band channel table that encompasses present and future card capabilities. . 2.5 Gbps DWDM ITU-T SPF — 0 to +4 dBm Dispersion compensation tolerance –1000 to +3600 ps/nm –800 to +2400 ps/nm 1. These values, decreased by patchcord and connector losses, are also the input power values for the OADM cards. Table 9-9 2.5-Gbps Interface Optical Performance (Class G, H, and M) (continued) Parameter Class G Class H Class M Type Power Limited OSNR Limited Power Limited OSNR Limited Power Limited OSNR Limited Table 9-10 DWDM C-Band1 Channel Allocation Plan with 50-GHz Spacing Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.5159-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview The following add drop cards utilize the L-band DWDM channels: 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 1. Channels on the C-band are 4-skip-1, starting at 1530.33 nm. Table 9-10 DWDM C-Band1 Channel Allocation Plan with 50-GHz Spacing (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)9-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Card Overview • 32WSS-L • 32DMX-L Table 9-11 lists the L-band channel IDs and wavelengths at ITU-T 50-GHz intervals. This is a comprehensive L-band channel table that encompasses present and future card capabilities. Table 9-11 DWDM L-band1 Channel Allocation Plan at 50 GHz Spacing Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 190.85 1570.83 41 188.85 1587.46 2 190.8 1571.24 42 188.8 1587.88 3 190.75 1571.65 43 188.75 1588.30 4 190.7 1572.06 44 188.7 1588.73 5 190.65 1572.48 45 188.65 1589.15 6 190.6 1572.89 46 188.6 1589.57 7 190.55 1573.30 47 188.55 1589.99 8 190.5 1573.71 48 188.5 1590.41 9 190.45 1574.13 49 188.45 1590.83 10 190.4 1574.54 50 188.4 1591.26 11 190.35 1574.95 51 188.35 1591.68 12 190.3 1575.37 52 188.3 1592.10 13 190.25 1575.78 53 188.25 1592.52 14 190.2 1576.20 54 188.2 1592.95 15 190.15 1576.61 55 188.15 1593.37 16 190.1 1577.03 56 188.1 1593.79 17 190.05 1577.44 57 188.05 1594.22 18 190 1577.86 58 188 1594.64 19 189.95 1578.27 59 187.95 1595.06 20 189.9 1578.69 60 187.9 1595.49 21 189.85 1579.10 61 187.85 1595.91 22 189.8 1579.52 62 187.8 1596.34 23 189.75 1579.93 63 187.75 1596.76 24 189.7 1580.35 64 187.7 1597.19 25 189.65 1580.77 65 187.65 1597.62 26 189.6 1581.18 66 187.6 1598.04 27 189.55 1581.60 67 187.55 1598.47 28 189.5 1582.02 68 187.5 1598.89 29 189.45 1582.44 69 187.45 1599.32 30 189.4 1582.85 70 187.4 1599.75 31 189.35 1583.27 71 187.35 1600.179-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Safety Labels for Class 1M Laser Product Cards 9.2 Safety Labels for Class 1M Laser Product Cards This section explains the significance of the safety labels attached to some of the cards. The card faceplates are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. The 40-SMR1-C and 40-SMR2-C cards have Class IM lasers. The labels that appear on these cards are described in the following subsections. 9.2.1 Class 1M Laser Product Statement Figure 9-1 shows the Class 1M Laser Product statement. Figure 9-1 Class 1M Laser Product Statement Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam. Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can be harmful to the eye if the beam is viewed using magnifying optical instruments. 32 189.3 1583.69 72 187.3 1600.60 33 189.25 1584.11 73 187.25 1601.03 34 189.2 1584.53 74 187.2 1601.46 35 189.15 1584.95 75 187.15 1601.88 36 189.1 1585.36 76 187.1 1602.31 37 189.05 1585.78 77 187.05 1602.74 38 189 1586.20 78 187 1603.17 39 188.95 1586.62 79 186.95 1603.60 40 188.9 1587.04 80 186.9 1604.03 1. Channels on the L-band are contiguous, starting at 1577.86 nm. The channels listed in this table begin with 1570.83 nm for backward compatibility with other ONS products. Table 9-11 DWDM L-band1 Channel Allocation Plan at 50 GHz Spacing (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) CAUTION HAZARD LEVEL 1M INVISIBLE LASER RADIATION DO NOT VIEW DIRECTLY WITH NON-ATTENUATING OPTICAL INSTRUMENTS λ = = 1400nm TO 1610nm 1459539-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Safety Labels for Class 1M Laser Product Cards 9.2.2 Hazard Level 1M Label Figure 9-2 shows the Hazard Level 1M label. The Hazard Level label warns users against exposure to laser radiation by Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. This label is displayed on the faceplate of the cards. Figure 9-2 Hazard Level Label 9.2.3 Laser Source Connector Label Figure 9-3 shows the Laser Source Connector label. This label indicates that a laser source is present at the optical connector where the label is located. Figure 9-3 Laser Source Connector Label 9.2.4 FDA Statement Label The FDA Statement labels are shown in Figure 9-4 and Figure 9-5. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 9-4 FDA Statement Label HAZARD LEVEL 1M 145990 96635 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 20019-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card Figure 9-5 FDA Statement Label 9.2.5 Shock Hazard Label Figure 9-6 shows the Shock Hazard label. This label alerts you to electrical hazards within a card. A shock hazard exists when you remove adjacent cards during maintenance, or when you touch exposed electrical circuitry on the card itself. Figure 9-6 Shock Hazard Label 9.3 32WSS Card (Cisco ONS 15454 only) Note See the “A.8.3 32WSS Card Specifications” section on page A-26 for hardware specifications. The two-slot 32-Channel Wavelength Selective Switch (32WSS) card performs channel add/drop processing within the ONS 15454 DWDM node. The 32WSS card can be installed in the following pairs of slots: • Slots 1 and 2 • Slots 3 and 4 • Slots 5 and 6 • Slots 12 and 13 • Slots 14 and 15 • Slots 16 and 17 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 2007 655419-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card 9.3.1 32WSS Faceplate Ports The 32WSS has six types of ports: • ADD RX ports (1 to 32): These ports are used for adding channels (listed in Table 9-13 on page 9-22). Each add channel is associated with an individual switch element that selects whether that channel is added. Each add port has optical power regulation provided by a variable optical attenuator (VOA). The 32WSS has four physical receive connectors that accept multifiber push-on (MPO) cables on its front panel for the client input interfaces.Each MPO cable breaks out into eight separate cables. • EXP RX port: The EXP RX port receives an optical signal from another 32WSS card in the same network element (NE). • EXP TX port: The EXP TX port sends an optical signal to the other 32WSS card within the NE. • COM TX port: The COM TX (line input) port sends an aggregate optical signal to a booster amplifier card (for example, OPT-BST) for transmission outside of the NE. • COM RX port: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE) and sends it to the optical splitter. • DROP TX port: The DROP TX port sends the split-off optical signal containing drop channels to the 32DMX card, where the channels are further processed and dropped. Figure 9-7 shows the 32WSS card front panel and identifies the traffic flow through the ports. 9-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card Figure 9-7 32WSS Faceplate and Ports 9.3.2 32WSS Block Diagram Figure 9-8 provides a high-level functional block diagram of the 32WSS card and Figure 9-9 on page 9-20 shows how optical signals are processed on the EXP RX and COM RX ports. 115291 FAIL ACT SF 54.1-60.6 46.1-52.5 38.1-44.5 30.3-36.6 DROP RX TX TX EXP RX TX COM RX TX ADD RX 32WSS 32 Add Ports Add 1-8 Add 9-16 Add 17-24 Add 25-32 DROP TX EXP RX EXP TX COM RX COM TX9-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card Figure 9-8 32WSS Block Diagram Aggregate optical signals that enter the EXP RX and COM RX port are processed in two ways: Add channel/pass-through and optical splitter processing. The optical processing stages are shown in Figure 9-9, which provides a detailed optical functional diagram of the 32WSS card. EXP RX port (In from other 32WSS within the network element) EXP TX port (To the other 32WSS within the network element) DROP TX port dropped channels (To COM RX port of 32DMX) COM RX port (In from preamplifier, OPT-PRE, or OSC-CSM) COM TX port (To OPT-BST or OSC-CSM) 115293 32 add ports Add 1 Add 2 Add 32 Optical splitter Add channel or pass-through Wavelength selective switch9-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card Figure 9-9 32WSS Optical Block Diagram The EXP RX PORT and COM RX PORT operate as follows: • EXP RX Port Add Channel/Pass-through Processing The incoming optical signal is received at the EXP RX port from the other 32WSS card within the NE. The incoming aggregate optical signal is demultiplexed into 32 individual wavelengths, or channels. Each channel is then individually processed by the optical switch, which performs add/pass-through processing. By using software controls, the switch either selects the optical channel coming in from the demultiplexer (that is, the pass-through channel) or it selects the external ADD channel. If the ADD port channel is selected this channel is transmitted and the optical signal coming from the demultiplexer is blocked. After the optical switch stage, all of the channels are multiplexed into an aggregate optical signal, which is sent out on the COM TX port. The output is typically connected to an OPT-BST or OPT-BST-E card (in the event a booster amplifier is needed) or to an OSC-CSM card (if no amplification is needed). • COM RX Port Optical Splitter Processing The COM RX port receives the incoming optical signal and directs it to the 32WSS card’s optical splitter. The splitter optically diverts channels that are designated to be dropped to the DROP TX port. The DROP TX port is typically connected to the COM RX port of the 32DMX where the drop channels are being dropped. Channels that are not dropped pass-through the optical splitter and flow out of the 32WSS card EXP TX port. Typically, this optical signal is connected to the other 32WSS module within the NE. 1 2 32 Add 32 32 1 pass-through EXP RX port (In from 32WSS) EXP TX port (To 32WSS) DROP TX port (To 32DMX) 2 pass-through 32 pass-through Optical splitter Dropped channels 2 Photodiode VOA COM RX port (In from OPT-PRE preamplifier or OSC-CSM) COM TX port (To OPT-BST or OSC-CSM) Add 2 2 Add 1 1 115292 Optical DMUX (AWG) Optical MUX (AWG) Optical switch (Add channel or pass-through) P1 P33 P2 P34 P32 P64 P65 P66 P67 P68 P699-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card • COM TX Port Monitoring The COM TX value can be measured by either a physical or a virtual photodiode of the 15454-32WSS card. If the vendor ID of the 15454-32WSS card is between 1024 (0x400) and 2047 (0x800) the COM TX value is measured by physical photodiode. If the vendor ID of the 15454-32WSS card is greater than 2048 (0x800), the COM TX value is measured by the virtual photodiode. For COM TX values measured by virtual photodiode, check the values at the RX port in the downstream of the COM TX port (COM-RX port on OPT-BST or OSC-CSM card). 9.3.3 32WSS ROADM Functionality The 32WSS card works in combination with the 32DMX card to implement ROADM functionality. As a ROADM node, the ONS 15454 can be configured to add or drop individual optical channels using CTC, Cisco TransportPlanner, and Cisco Transport Manager (CTM). ROADM functionality using the 32WSS card requires two 32DMX single-slot cards and two 32WSS double-slot cards (totalling six slots needed in the ONS 15454 chassis). For other cards’ ROADM functionality, see that card’s description in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. Note A terminal site can be configured using only a 32WSS card and a 32DMX card plugged into the east or west side of the shelf. 9.3.4 32WSS Power Monitoring Physical photodiodes P1 through P69 monitor the power for the 32WSS card. Table 9-12 shows how the returned power level values are calibrated to each port. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. Table 9-12 32WSS Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P32 ADD (Power ADD) ADD RX P33–P641 1. P33–P64 monitor either ADD or PASSTHROUGH power, depending on the state of the optical switch PASS THROUGH COM TX ADD (Power) COM TX P65 OUT EXP EXP TX P66 IN EXP EXP RX P67 OUT COM COM TX P68 IN COM COM RX P69 DROP DROP TX9-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS Card 9.3.5 32WSS Channel Allocation Plan The 32WSS Card’s channel labels, frequencies, and wavelengths are listed in Table 9-13. Table 9-13 32WSS Channel Allocation Plan Band ID Channel Label Frequency (THz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.1 195.1 1536.61 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.87 39.7 194.7 1539.77 40.5 194.6 1540.46 B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.619-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card 9.3.6 32WSS Card-Level Indicators Table 9-14 describes the three card-level LED indicators on the 32WSS card. 9.3.7 32WSS Port-Level Indicators You can find the alarm status of the 32WSS card’s ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.4 32WSS-L Card (Cisco ONS 15454 only) Note See the “A.8.4 32WSS-L Card Specifications” section on page A-28 for hardware specifications. The two-slot 32-Channel Wavelength Selective Switch L-Band (32WSS-L) card performs channel add/drop processing within the ONS 15454 DWDM node. The 32WSS-L card is particularly well suited for use in networks that employ DS fiber or SMF-28 single-mode fiber.The 32WSS-L card can be installed in the following pairs of slots: • Slots 1 and 2 • Slots 3 and 4 • Slots 5 and 6 • Slots 12 and 13 • Slots 14 and 15 • Slots16 and 17 Table 9-14 32WSS Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that there is an internal hardware failure. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 32WSS card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also illuminates when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card 9.4.1 32WSS-L Faceplate Ports The 32WSS-L card faceplate has six types of ports: • ADD RX ports (1 to 32): These ports are used for adding channels (which are listed in Table 9-16 on page 9-29). Each add channel is associated with an individual switch element that selects whether the channel is added. Each add port has optical power regulation provided by a VOA. • EXP RX port: The EXP RX port receives an optical signal from another 32WSS-L card in the same NE. • EXP TX port: The EXP TX port sends an optical signal to the other 32WSS-L card within the NE. • COM TX port: The COM TX port sends an aggregate optical signal to a booster amplifier card (for example, the OPT-BST card) for transmission outside of the NE. • COM RX port: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE) and sends it to the optical splitter. • DROP TX port: The DROP TX port sends the split-off optical signal with drop channels to the 32DMX-L card, where the channels are further processed and dropped. Figure 9-10 shows the 32WSS-L module front panel and identifies the traffic flow through the ports. 9-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card Figure 9-10 32WSS-L Faceplate and Ports 9.4.2 32WSS-L Block Diagram Figure 9-11 provides a high-level functional block diagram of the 32WSS-L card and Figure 9-12 on page 9-27 shows how optical signals are processed on the EXP RX and COM RX ports. 134973 FAIL ACT SF 98.0-04.0 91.2-97.1 84.5-90.4 77.8-83.6 DROP RX TX TX EXP RX TX COM RX TX ADD RX 32WSS-L 32 Add Ports Add 1-8 Add 9-16 Add 17-24 Add 25-32 DROP TX EXP RX EXP TX COM RX COM TX9-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card Figure 9-11 32WSS-L Block Diagram Aggregate optical signals that enter the EXP RX and COM RX ports are processed in two ways: add channel/pass-through and optical splitter processing. The optical processing stages are shown in Figure 9-12, which provides a detailed optical functional diagram of the 32WSS-L card. EXP RX port (In from other 32WSS-L within the network element) EXP TX port (To the other 32WSS-L within the network element) DROP TX port dropped channels (To COM RX port of 32DMX) COM RX port (In from OPT-AMP-L preamplifier or OSC-CSM) COM TX port (To o OPT-AMP-L booster or OSC-CSM) 134971 32 add ports Add 1 Add 2 Add 32 Optical splitter Add channel or pass-through Wavelength selective switch9-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card Figure 9-12 32WSS-L Optical Block Diagram The EXP RX PORT and COM RX PORT operate as follows: • EXP RX Port Add Channel/Pass-through Processing The incoming optical signal is received at the EXP RX port from the other 32WSS-L card within the NE. The incoming aggregate optical signal is demultiplexed into 32 individual wavelengths, or channels. Each channel is then individually processed by the optical switch, which performs add/pass-through processing. By using software controls, the switch either selects the optical channel coming in from the demultiplexer (that is, the pass-through channel) or it selects the external ADD channel. If the ADD port channel is selected this channel is transmitted and the optical signal coming from the demultiplexer is blocked. After the optical switch stage, all of the channels are multiplexed into an aggregate optical signal, which is sent out on the COM TX port. The output is typically connected to an OPT-AMP-L or OPT-BST-E card (in the event a booster amplifier is needed) or to an OSC-CSM card (if no amplification is needed). • COM RX Port Optical Splitter Processing The COM RX port receives the incoming optical signal and directs it to the 32WSS-L card’s optical splitter. The splitter optically diverts channels that are designated to be dropped to the DROP TX port. The DROP TX port is typically connected to the COM RX port of the 32DMX-L where the drop channels are being dropped. Channels that are not dropped pass-through the optical splitter and flow out of the 32WSS-L card EXP TX port. Typically, this optical signal is connected to the other 32WS-L module within the NE. 1 2 32 Add 32 32 1 pass-through EXP RX port (In from 32WSS-L) EXP TX port (To 32WSS-L) DROP TX port (To 32DMX-L) 2 pass-through 32 pass-through Optical splitter Dropped channels 2 Photodiode VOA Add 2 2 Add 1 1 134972 Optical DMUX (AWG) Optical MUX (AWG) Optical switch (Add channel or pass-through) P1 P33 P2 P34 P32 P64 P65 P66 P67 P68 P69 COM RX port (In from OPT-AMP-L preamplifier or OSC-CSM) COM TX port (To OPT-AMP-L booster or OSC-CSM)9-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card 9.4.3 32WSS-L ROADM Functionality The 32WSS-L works in combination with the 32DMX-L to implement L-band (1570 to 1620 nm) functionality. As a ROADM node, the ONS 15454 can be configured to add or drop individual optical channels using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 32WSS-L card requires two 32DMX-L single-slot cards and two 32WSS-L double-slot cards (totalling six slots needed in the ONS 15454 chassis). For other cards’ ROADM functionality, see that card’s description in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. Note A terminal site can be configured using a 32WSS-L card and a 32DMX-L card plugged into the east or west side of the shelf. 9.4.4 32WSS-L Power Monitoring Physical photodiodes P1 through P69 monitor the power for the 32WSS-L card. Table 9-15 shows the returned power level values calibrated to each port. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.4.5 32WSS-L Channel Plan The 32WSS-L card uses 32 banded channels on the ITU-T 100-GHz grid, as shown in Table 9-16. Table 9-15 32WSS-L Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P32 ADD (Power ADD) ADD RX P33–P641 1. P33–P64 monitor either ADD or PASSTHROUGH power, depending on the state of the optical switch PASS THROUGH COM TX ADD (Power) COM TX P65 OUT EXP EXP TX P66 IN EXP EXP RX P67 OUT COM COM TX P68 IN COM COM RX P69 DROP DROP TX9-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32WSS-L Card Table 9-16 32WSS-L Channel Plan Band ID Channel Label Frequency (THz) Wavelength (nm) B77.8 77.8 190 1577.86 78.6 189.9 1578.69 79.5 189.8 1579.52 80.3 189.7 1580.35 B81.1 81.1 189.6 1581.18 82.0 189.5 1582.02 82.8 189.4 1582.85 83.6 189.3 1583.69 B84.5 84.5 189.2 1584.53 85.3 189.1 1585.36 86.2 189 1586.20 87.0 188.9 1587.04 B87.8 87.8 188.8 1587.88 88.7 188.7 1588.73 89.5 188.6 1589.57 90.4 188.5 1590.41 B91.2 91.2 188.4 591.26 92.1 188.3 1592.10 92.9 188.2 1592.95 93.7 188.1 1593.79 B94.6 94.6 188 1594.64 95.4 187.9 1595.49 96.3 187.8 1596.34 97.1 187.7 1597.19 B98.0 98.0 187.6 1598.04 98.8 187.5 1598.89 99.7 187.4 1599.75 00.6 187.3 1600.60 B01.4 01.4 187.2 1601.46 02.3 187.1 1602.31 03.1 187 1603.17 04.0 186.9 1604.039-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX Card 9.4.6 32WSS-L Card-Level Indicators Table 9-17 describes the three card-level LED indicators on the 32WSS-L card. 9.5 32DMX Card (Cisco ONS 15454 only) Note See the “A.8.1 32DMX Card Specifications” section on page A-22 for hardware specifications. The single-slot 32-Channel Demultiplexer (32DMX) card is an optical demultiplexer. The card receives an aggregate optical signal on its COM RX port and demultiplexes it into to (32) ITU-T 100-GHz-spaced channels. The 32DMX card can be installed in Slots 1 to 6 and in Slots 12 to 17. 9.5.1 32DMX Faceplate Ports The 32DMX card has two types of ports: • COM RX port: COM RX is the input port for the aggregate optical signal being demultiplexed. This port is supported by a VOA for optical power regulation and a photodiode for optical power monitoring. • DROP TX ports (1 to 32): On its output, the 32DMX provides 32 drop ports (listed in Table 9-19 on page 9-33) that are typically used for dropping channels within the ROADM node. These ports are connected using four 8-fiber MPO ribbon connectors. The incoming optical signal to the demultiplexer comes into the COM RX port. This input port is connected using a single LC duplex optical connector.Each drop port has a photodiode for optical power monitoring. Unlike the two-slot 32DMX-O demultiplexer, the drop ports on the 32DMX do not have a VOA per channel for optical power regulation. For a description of the 32DMX-O card, see the “5.4 32DMX-O Card” section on page 5-17. Figure 9-13 shows the 32DMX card front panel and the basic traffic flow through the ports. Table 9-17 32WSS-L Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 32WSS-L card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX Card Figure 9-13 32DMX Faceplate and Ports 9.5.2 32DMX Block Diagram A block diagram of the 32DMX card is shown in Figure 9-14. 145936 32DMX FAIL ACT SF 54.1-60.6 46.1-52.5 38.1-44.5 30.3-36.6 COM RX TX MON 32 Drop Port Outputs 32 Drop Ports Logical View Drop 1-8 Drop 9-16 Drop 17-24 Drop 25-32 COM RX (Receives Drop-TX from 32WSS on COM RX) COM-RX Drop-1 Drop-2 Drop-329-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX Card Figure 9-14 32DMX Block Diagram Figure 9-15 shows the 32DMX optical module functional block diagram. Figure 9-15 32DMX Optical Module Functional Block Diagram 9.5.3 32DMX ROADM Functionality The 32DMX card works in combination with the 32WSS card to implement ROADM functionality. As a ROADM node, the ONS 15454 can be configured to add or drop individual optical channels using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 32DMX card requires two 32DMX single-slot cards and two 32WSS double-slot cards (for six slots total in the ONS 15454 chassis). Optical module 30.3 to 36.6 8 CHS TX 38.1 to 44.5 8 CHS TX 46.1 to 52.5 8 CHS TX 54.1 to 60.6 8 CHS TX 96480 Processor MON COM RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 1 32 Physical photodiode Variable optical attenuator COM RX 20 dB max attenuation DROP TX P4 P3 P2 P1 P32 P31 P30 P29 P33 P34 P 1249679-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX Card For information about the ROADM functionality for other cards, see that card’s description in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. Note A terminal site can be configured using only a 32WSS card and a 32DMX card plugged into the east or west side of the shelf. 9.5.4 32DMX Power Monitoring Physical photodiodes P1 through P33 monitor the power for the 32DMX card. The returned power level values are calibrated to the ports as shown in Table 9-18. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.5.5 32DMX Channel Allocation Plan The 32DMX card’s channel labels, frequencies, and wavelengths are listed in Table 9-19. Table 9-18 32DMX Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P32 DROP DROP TX P33 INPUT COM COM RX Table 9-19 32DMX Channel Allocation Plan Band ID Channel Label Frequency (THz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.1 195.1 1536.61 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.87 39.7 194.7 1539.77 40.5 194.6 1540.469-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX Card 9.5.6 32DMX Card-Level Indicators Table 9-20 describes the three card-level LED indicators on the 32DMX card. B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 Table 9-19 32DMX Channel Allocation Plan (continued) Band ID Channel Label Frequency (THz) Wavelength (nm) Table 9-20 32DMX Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 32DMX card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX-L Card 9.5.7 32DMX Port-Level Indicators You can find the alarm status of the 32DMX card’s ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.6 32DMX-L Card (Cisco ONS 15454 only) Note See the “A.8.2 32DMX-L Card Specifications” section on page A-24 for hardware specifications. The single-slot 32-Channel Demultiplexer L-Band card (32DMX-L) is an L-band optical demultiplexer. The card receives an aggregate optical signal on its COM RX port and demultiplexes it into to (32) 100-GHz-spaced channels. The 32DMX-L card is particularly well suited for use in networks that employ DS fiber or SMF-28 single-mode fiber. The 32DMX-L card can be installed in Slots 1 to 6 and in Slots 12 to 17. 9.6.1 32DMX-L Faceplate Ports The 32DMX-L card has two types of ports: • COM RX port: COM RX is the input port for the aggregate optical signal being demultiplexed. This port is supported by both a VOA for optical power regulation and a photodiode for optical power monitoring. • DROP TX ports (1 to 32): On its output, the 32DMX-L card provides 32 drop ports (listed in Table 9-25 on page 9-43) that are typically used for dropping channels within the ROADM node. These ports are connected using four 8-fiber MPO ribbon connectors. Each drop port has a photodiode for optical power monitoring. Unlike the two-slot 32DMX-O demultiplexer, the drop ports on the 32DMX-L do not have a VOA per channel for optical power regulation. For a description of the 32DMX-O card, see the “5.4 32DMX-O Card” section on page 5-17. Figure 9-16 shows the 32DMX-L card front panel and the basic traffic flow through the ports.9-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX-L Card Figure 9-16 32DMX-L Faceplate and Ports 9.6.2 32DMX-L Block Diagram Figure 9-17 shows a block diagram of the 32DMX-L card. 145940 32DMX FAIL ACT SF 98.0-04.0 91.2-97.1 84.5-90.4 77.8-83.6 COM RX TX 32 Drop Port Outputs 32 Drop Ports Logical View Drop 1-8 Drop 9-16 Drop 17-24 Drop 25-32 COM RX (Receives Drop-TX from 32WSS-L on COM RX) COM-RX Drop-1 Drop-2 Drop-32 MON9-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX-L Card Figure 9-17 32DMX-L Block Diagram Figure 9-18 shows the 32DMX-L optical module functional block diagram. Figure 9-18 32DMX-L Optical Module Functional Block Diagram 9.6.3 32DMX-L ROADM Functionality The 32DMX-L card works in combination with the 32WSS-L card to implement ROADM functionality. AS a ROADM node, the ONS 15454 can be configured to add or drop individual optical channels using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 32DMX-L card requires two 32DMX-L single-slot cards and two 32WSS-L double-slot cards (for a total of six slots in the ONS 15454 chassis). Optical module 77.8 to 83.6 8 CHS TX 84.5 to 90.4 8 CHS TX 91.2 to 97.1 8 CHS TX 98.0 to 04.0 8 CHS TX 134969 Processor MON COM RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 1 32 Physical photodiode Variable optical attenuator COM RX 20 dB max attenuation DROP TX P4 P3 P2 P1 P32 P31 P30 P29 P33 P34 P 1249679-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX-L Card For information about ROADM functionality for other cards, see that card’s description in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. Note A terminal site can be configured using only a 32WSS-L card and a 32DMX-L card plugged into the east or west side of the shelf. 9.6.4 32DMX-L Power Monitoring Physical photodiodes P1 through P33 monitor the power for the 32DMX-L card. The returned power level values are calibrated to the ports as shown in Table 9-21. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.6.5 32DMX-L Channel Plan The 32DMX-L card uses 32 banded channels on the ITU-T 100-GHz grid, as shown in Table 9-22. Table 9-21 32DMX-L Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P32 DROP DROP TX P33 INPUT COM COM RX Table 9-22 32DMX-L Channel Plan Band ID Channel Label Frequency (THz) Wavelength (nm) B77.8 77.8 190 1577.86 78.6 189.9 1578.69 79.5 189.8 1579.52 80.3 189.7 1580.35 B81.1 81.1 189.6 1581.18 82.0 189.5 1582.02 82.8 189.4 1582.85 83.6 189.3 1583.69 B84.5 84.5 189.2 1584.53 85.3 189.1 1585.36 86.2 189 1586.20 87.0 188.9 1587.049-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 32DMX-L Card 9.6.6 32DMX-L Card-Level Indicators Table 9-23 describes the three card-level LED indicators on the 32DMX-L card. B87.8 87.8 188.8 1587.88 88.7 188.7 1588.73 89.5 188.6 1589.57 90.4 188.5 1590.41 B91.2 91.2 188.4 1591.26 92.1 188.3 1592.10 92.9 188.2 1592.95 93.7 188.1 1593.79 B94.6 94.6 188 1594.64 95.4 187.9 1595.49 96.3 187.8 1596.34 97.1 187.7 1597.19 B98.0 98.0 187.6 1598.04 98.8 187.5 1598.89 99.7 187.4 1599.75 00.6 187.3 1600.60 B01.4 01.4 187.2 1601.46 02.3 187.1 1602.31 03.1 187 1603.17 04.0 186.9 1604.03 Table 9-22 32DMX-L Channel Plan (continued) Band ID Channel Label Frequency (THz) Wavelength (nm) Table 9-23 32DMX-L Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 32DMX-L card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-C Card 9.6.7 32DMX-L Port-Level Indicators You can find the alarm status of the 32DMX-L card’s ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.7 40-DMX-C Card (Cisco ONS 15454 and ONS 15454 M6 only) Note See the “A.8.6 40-DMX-C Card Specifications” section on page A-30 for hardware specifications. The single-slot 40-Channel Demultiplexer C-band (40-DMX-C) card demultiplexes 40 100-GHz-spaced channels identified in the channel plan (Table 9-25 on page 9-43), and sends them to dedicated output ports. The overall optical power can be adjusted using a single VOA that is common to all channels. The 40-DMX-C card is unidirectional, optically passive, and can be installed in Slots 1 to 6 and 12 to 17. 9.7.1 40-DMX-C Faceplate Ports The 40-DMX-C has two types of ports: • COM RX port: COM RX is the line input port for the aggregate optical signal being demultiplexed. This port is supported by a VOA for optical power regulation and a photodiode for per channel optical power monitoring. Note By default, the VOA is set to its maximum attenuation for safety purposes (for example, electrical power failure). A manual VOA setting is also available. • DROP TX ports (1 to 40): On its output, the 40-DMX-C card provides 40 drop ports that are typically used for dropping channels within the ROADM node. These ports are connected using five physical connectors on the front panel that accept MPO client input cables. (MPO cables break out into eight separate cables.) The 40-DMX-C card also has one LC-PC-II optical connector for the main input. Figure 9-19 shows the 40-DMX-C card faceplate.9-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-C Card Figure 9-19 40-DMX-C Faceplate 9.7.2 40-DMX-C Block Diagram Figure 9-20 shows a block diagram of the 40-DMX-C card. 159554 40-DMX-C 36.6 - 42.1 30.3 - 35.8 42.9 - 48.5 49.3 - 54.9 55.7 - 61.4 TX COM RX FAIL ACT SF 40 Drop Ports Drop 1-8 Drop 9-16 Drop 17-24 Drop 25-32 Drop 33-40 40 Drop Port Outputs Logical View COM-RX Drop-1 Drop-2 Drop-40 COM RX (Receives Drop-TX from 40-WSS-C on COM RX)9-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-C Card Figure 9-20 40-DMX-C Block Diagram Figure 9-21 shows the 40-DMX-C optical module functional block diagram. Figure 9-21 40-DMX-C Optical Module Functional Block Diagram 9.7.3 40-DMX-C ROADM Functionality The 40-DMX-C card works in combination with the 40-WSS-C card to implement ROADM functionality. As a ROADM node, the ONS 15454 can be configured at the optical channel level using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 40-DMX-C card requires two single-slot 40-DMX-C cards and two 40-WSS-C double-slot cards (for a total of six slots in the ONS 15454 chassis). Optical module 151971 Processor COM RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 36.6 to 42.1 8 CHS RX 30.3 to 35.8 8 CHS RX 42.9 to 48.5 8 CHS RX 49.3 to 54.9 8 CHS RX 55.7 to 61.4 8 CHS RX 1 40 Control Control interface Physical photodiode Variable optical attenuator COM RX DROP TX P40 P39 P38 P37 P4 P3 P2 P1 P P41 1519729-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-C Card For other cards’ ROADM functionality, see that card’s description in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. 9.7.4 40-DMX-C Power Monitoring Physical photodiodes P1 through P40 monitor the power at the outputs of the 40-DMX-C card. P41 monitors the total multiplexed power at the input, calibrated to the COM-RX port. Table 9-24 shows the returned power level values calibrated to each port. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.7.5 40-DMX-C Channel Plan Table 9-25 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are demultiplexed by the 40-DMX-C card. Table 9-24 40-DMX-C Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P40 DROP DROP TX P41 INPUT COM COM RX Table 9-25 40-DMX-C Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195 1537.40 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.359-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-C Card 9.7.6 40-DMX-C Card-Level Indicators The 40-DMX-C card has three card-level LED indicators, described in Table 9-26. B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194 1545.32 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.32 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193 1553.33 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192 1561.42 Table 9-25 40-DMX-C Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm)9-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-CE Card 9.7.7 40-DMX-C Port-Level Indicators You can find the alarm status of the 40-DMX-C card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.8 40-DMX-CE Card (Cisco ONS 15454 and ONS 15454 M6 only) Note See the “A.8.7 40-DMX-CE Card Specifications” section on page A-31 for hardware specifications. The single-slot 40-Channel Demultiplexer C-band, even channels (40-DMX-CE) card demultiplexes 40 100-GHz-spaced even-numbered channels identified in the channel plan (Table 9-28 on page 9-48), and sends them to dedicated output ports. The overall optical power can be adjusted using a single VOA that is common to all channels. The 40-DMX-CE card is unidirectional, optically passive, and can be installed in Slots 1 to 6 and 12 to 17. 9.8.1 40-DMX-CE Card Faceplate Ports The 40-DMX-CE card has two types of ports: • COM RX port: COM RX is the line input port for the aggregate optical signal being demultiplexed. This port is supported by a VOA for optical power regulation and a photodiode for per channel optical power monitoring. Note By default, the VOA is set to its maximum attenuation for safety purposes (for example, electrical power failure). A manual VOA setting is also available. Table 9-26 40-DMX-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 40-DMX-C card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-CE Card • DROP TX ports (1 to 40): On its output, the 40-DMX-CE card provides 40 drop ports that are typically used for dropping channels within the ROADM node. These ports are connected using five physical connectors on the front panel that accept MPO client input cables. (MPO cables break out into eight separate cables.) The 40-DMX-CE card also has one LC-PC-II optical connector for the main input. Figure 9-22 shows the 40-DMX-CE card faceplate. Figure 9-22 40-DMX-CE Card Faceplate 9.8.2 40-DMX-CE Card Block Diagram Figure 9-23 shows a block diagram of the 40-DMX-CE card. 240642 40-DMX-C 37.0 - 42.5 30.7 - 36.2 43.3 - 48.9 49.7 - 55.3 56.2 - 61.8 TX COM RX FAIL ACT SF 40 Drop Ports Drop 1-8 Drop 9-16 Drop 17-24 Drop 25-32 Drop 33-40 40 Drop Port Outputs Logical View COM-RX Drop-1 Drop-2 Drop-40 COM RX (Receives Drop-TX from 40-WSS-CE on COM RX)9-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-CE Card Figure 9-23 40-DMX-CE Card Block Diagram Figure 9-24 shows the 40-DMX-CE card optical module functional block diagram. Figure 9-24 40-DMX-CE Card Optical Module Functional Block Diagram 9.8.3 40-DMX-CE Card ROADM Functionality The 40-DMX-CE card works in combination with the 40-WSS-CE card to implement ROADM functionality. As a ROADM node, the ONS 15454 can be configured at the optical channel level using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 40-DMX-CE card requires two single-slot 40-DMX-CE cards and two 40-WSS-CE double-slot cards (for a total of six slots in the ONS 15454 chassis). Optical module 240641 Processor COM RX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 37.0 to 42.5 8 CHS RX 30.7 to 36.2 8 CHS RX 43.3 to 48.9 8 CHS RX 49.7 to 55.3 8 CHS RX 56.1 to 61.8 8 CHS RX 1 40 Control Control interface Physical photodiode Variable optical attenuator COM RX DROP TX P40 P39 P38 P37 P4 P3 P2 P1 P P41 1519729-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-CE Card For the ROADM functionality of other cards, see the description of that card in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. 9.8.4 40-DMX-CE Card Power Monitoring Physical photodiodes P1 through P40 monitor the power at the outputs of the 40-DMX-CE card. P41 monitors the total multiplexed power at the input, calibrated to the COM-RX port. Table 9-27 shows the returned power level values calibrated to each port. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.8.5 40-DMX-CE Card Channel Plan Table 9-28 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are demultiplexed by the 40-DMX-CE card. Table 9-27 40-DMX-CE Card Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P40 DROP DROP TX P41 INPUT COM COM RX Table 9-28 40-DMX-CE Card Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.7 30.7 195.85 1530.72 31.5 195.75 1531.51 32.3 195.65 1532.29 33.1 195.55 1533.07 33.9 195.45 1533.86 B34.6 34.6 195.35 1534.64 35.4 195.25 1535.43 36.2 195.15 1536.22 37.0 195.05 1537.00 37.8 194.95 1537.79 B38.6 38.6 194.85 1538.58 39.4 194.75 1539.37 40.1 194.65 1540.16 40.9 194.55 1540.95 41.8 194.45 1541.759-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-DMX-CE Card 9.8.6 40-DMX-CE Card-Level Indicators The 40-DMX-CE card has three card-level LED indicators, described in Table 9-29. B42.5 42.5 194.35 1542.54 43.3 194.25 1543.33 44.1 194.15 1544.13 44.9 194.05 1544.92 45.7 193.95 1545.72 B46.5 46.5 193.85 1546.52 47.3 193.75 1547.32 48.1 193.65 1548.11 48.9 193.55 1548.91 49.7 193.45 1549.72 B50.5 50.5 193.35 1550.52 51.3 193.25 1551.32 52.1 193.15 1552.12 52.9 193.05 1552.93 53.7 192.95 1553.73 B54.4 54.4 192.85 1554.54 55.3 192.75 1555.34 56.1 192.65 1556.15 56.9 192.55 1556.96 57.8 192.45 1557.77 B58.6 58.6 192.35 1558.58 59.4 192.25 1559.39 60.2 192.15 1560.20 61.0 192.05 1561.01 61.8 191.95 1561.83 Table 9-28 40-DMX-CE Card Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm) Table 9-29 40-DMX-CE Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists.9-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-MUX-C Card 9.8.7 40-DMX-CE Card Port-Level Indicators You can find the alarm status of the 40-DMX-CE card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to the “Manage Alarms” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 9.9 40-MUX-C Card (Cisco ONS 15454 and ONS 15454 M6 only) Note See the “A.8.5 40-MUX-C Card Specifications” section on page A-30 for hardware specifications. The single-slot 40-Channel Multiplexer C-band (40-MUX-C) card multiplexes forty ITU-T 100-GHz-spaced channels identified in the channel plan in Table 9-25 on page 9-43. The 40-MUX-C card can be installed in Slots 1 to 6 and 12 to 17. The 40-MUX-C card is typically used in hub nodes. 9.9.1 40-MUX-C Card Faceplate Ports The 40-MUX-C card has two types of ports: • COM TX port: COM TX is the line output port for the aggregate optical signal being multiplexed. This port is supported by both a VOA for optical power regulation and a photodiode for per channel optical power monitoring. Note By default, the VOA is set to its maximum attenuation for safety purposes (for example, electrical power failure). A manual VOA setting is also available. • DROP RX ports (1 to 40): The 40-MUX-C card provides 40 input optical channels. These ports are connected using five physical receive connectors on the card’s front panel that accept MPO cables for the client input interfaces. MPO cables break out into eight separate cables. The 40-DMX-C card also has one LC-PC-II optical connector for the main output. For the wavelength range, see Table 9-25 on page 9-43. Figure 9-25 shows the 40-MUX-C card faceplate. Green ACT LED The green ACT LED indicates that the 40-DMX-CE card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off. Table 9-29 40-DMX-CE Card-Level Indicators (continued) Card-Level Indicators Description9-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-MUX-C Card Figure 9-25 40-MUX-C Card Faceplate 9.9.2 40-MUX-C Card Block Diagram Figure 9-26 shows a block diagram of the 40-MUX-C card. 40-MUX-C 36.6 - 42.1 30.3 - 35.8 42.9 - 48.5 49.3 - 54.9 55.7 - 61.4 RX COM TX FAIL ACT SF 159555 Client ports 1-8 Client ports 9-16 Client ports 17-24 Client ports 25-32 Client ports 33-40 Logical View COM TX Client-1 Client-2 Client-40 40 Client Channel Inputs 40 Client Ports COM TX Sends combined signal to OPT- BST9-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-MUX-C Card Figure 9-26 40-MUX-C Card Block Diagram Figure 9-27 shows the 40-MUX-C optical module functional block diagram. Figure 9-27 40-MUX-C Optical Module Functional Block Diagram 9.9.3 40-MUX-C Card Power Monitoring Physical photodiodes P1 through P40 monitor the power of the individual input ports to the 40-MUX-C card. P41 monitors the total multiplexed output power, calibrated to the COM-TX port. Table 9-30 shows the returned power level values calibrated to each port. Optical module 36.6 to 42.1 8 CHS RX 30.3 to 35.8 8 CHS RX 42.9 to 48.5 8 CHS RX 49.3 to 54.9 8 CHS RX 55.7 to 61.4 8 CHS RX Processor COM TX FPGA For SCL Bus management SCL Bus TCCi M SCL Bus TCCi P DC/DC Power supply Input filters BAT A&B 151974 1 40 Control Control interface Physical photodiode Variable optical attenuator Inputs COM TX P40 P39 P38 P37 P4 P3 P2 P1 P 1519759-53 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-MUX-C Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.9.4 40-MUX-C Card Channel Plan Table 9-31 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are multiplexed by the 40-MUX-C card. Table 9-30 40-MUX-C Port Calibration Photodiode CTC Type Name Calibrated to Port P1–P40 ADD ADD RX P41 OUTPUT COM COM-TX Table 9-31 40-MUX-C Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195 1537.40 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.35 B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194 1545.329-54 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-MUX-C Card 9.9.5 40-MUX-C Card-Level Indicators The 40-MUX-C card has three card-level LED indicators, described in Table 9-32. B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.32 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193 1553.33 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192 1561.42 Table 9-31 40-MUX-C Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm) Table 9-32 40-MUX-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 40-MUX-C card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-55 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-C Card 9.9.6 40-MUX-C Port-Level Indicators You can find the alarm status of the 40-MUX-C card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.10 40-WSS-C Card (Cisco ONS 15454 and ONS 15454 M6 only) Note See the “A.8.8 40-WSS-C Card Specifications” section on page A-32 for hardware specifications. The double-slot 40-channel Wavelength Selective Switch C-Band (40-WSS-C) card switches 40 ITU-T 100-GHz-spaced channels identified in the channel plan (Table 9-25 on page 9-43) and sends them to dedicated output ports. The 40-WSS-C card is bidirectional and optically passive. The card can be installed in Slots 1 to 6 and 12 to 17 The 40-WSS-C features include: • Receipt of an aggregate DWDM signal into 40 output optical channels from the Line receive port (EXP RX) in one direction and from the COM-RX port in the other direction. • Per-channel optical power monitoring using photodiodes. • Signal splitting in a 70%-to-30% ratio, sent to the 40-DMX-C for dropping signals, then to the other 40-WSS-C card. • Aggregate DWDM signal monitoring and control through a variable optical attenuator (VOA). In the case of electrical power failure, the VOA is set to its maximum attenuation for safety purposes. A manual VOA setting is also available. Within the 40-WSS-C card, the first AWG opens the spectrum and each wavelength is directed to one of the ports of a 1x2 optical switch. The same wavelength can be passed through or stopped. If the pass-through wavelength is stopped, a new channel can be added at the ADD port. The card’s second AWG multiplexes all of the wavelengths, and the aggregate signal is output through the COM-TX port. 9.10.1 40-WSS-C Faceplate Ports The 40-WSS-C has eight types of ports: • ADD RX ports (1 to 40): These ports are used for adding channels. Each add channel is associated with an individual switch element that selects whether an individual channel is added. Each add port has optical power regulation provided by a VOA. The five connectors on the card faceplate accept MPO cables for the client input interfaces. MPO cables break out into eight separate cables. The 40-WSS-C card also has one LC-PC-II optical connector for the main input. • COM RX: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE) and sends it to the optical splitter. • COM TX: The COM TX port sends an aggregate optical signal to a booster amplifier card (for example, the OPT-BST card) for transmission outside of the NE.9-56 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-C Card • EXP RX port: The EXP RX port receives an optical signal from another 40-WSS-C card in the same NE. • EXP TX: The EXP TX port sends an optical signal to the other 40-WSS-C card within the NE. • DROP TX port: The DROP TX port sends the split off optical signal that contains drop channels to the 40-DMX-C card, where the channels are further processed and dropped. Figure 9-28 shows the 40-WSS-C card faceplate. Figure 9-28 40-WSS-C Faceplate 9.10.2 40-WSS-C Block Diagram Figure 9-29 shows a block diagram of the 40-WSS-C card. 159394 40-WSS-C 36.6 - 42.1 30.3 - 35.8 42.9 - 48.5 49.3 - 54.9 55.7 - 61.4 ADD RX COM RX TX EXP RX TX DROP TX FAIL ACT SF9-57 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-C Card Figure 9-29 40-WSS-C Block Diagram Figure 9-30 shows the 40-WSS-C optical module functional block diagram. 159393 ADD RX CONTROL Control Interface Comon TX Comon RX EXPRESS RX 2 2 ADD 2 2 Pas Through EXPRESS TX Virtual photodiode DROP TX 1 1 ADD 1 1 Pas Through 40 40 ADD 70/30 40 2 Pas Through9-58 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-C Card Figure 9-30 40-WSS-C Optical Module Functional Block Diagram 9.10.3 40-WSS-C ROADM Functionality The 40-WSS-C card works in combination with the 40-DMX-C card to implement ROADM functionality. As a ROADM node, the ONS 15454 can be configured at the optical channel level using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 40-WSS-C card requires two 40-WSS-C double-slot cards and two 40-DMX-C single-slot cards (for a total of six slots in the ONS 15454 chassis). For information about ROADM functionality for other cards, see that card’s description in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. 9.10.4 40-WSS-C Power Monitoring The 40-WSS-C has physical diodes that monitor power at various locations on the card. Table 9-33 lists the physical diode descriptions. Optical module 159392 uP8260 COM RX COM TX FPGA For SCL Bus management 2xSCL Buses DC/DC Power supply Input filters BAT A&B EXP RX ADD RX LC connector MPO connector EXP TX DROP TX Table 9-33 40-WSS-C Physical Photodiode Port Calibration Physical Photodiode CTC Type Name Calibrated to Port(s) P1 DROP DROP TX P2 EXP EXP RX9-59 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-C Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. Additionally, the 40-WSS-C has two virtual diodes. Virtual diodes are monitor points for each physical photodiode; they are identified with a physical diode relative to the way that the physical diode is identified with one of the two interlink (ILK) ports. Table 9-34 lists the virtual diodes. 9.10.5 40-WSS-C Channel Plan Table 9-35 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are switched by the 40-WSS-C card. PDi3 1 RX Add i RX ports (that is, channel input Add i RX power), up to 40 ports and therefore 40 PDs1 PDi4 1 TX COM TX port (that is, per channel output COM TX power) up to 40 channels and therefore 40 PDs PD5 COM COM TX port (that is, total output COM TX power) 1. i indicates any channel from 01 through 40. Table 9-33 40-WSS-C Physical Photodiode Port Calibration (continued) Physical Photodiode CTC Type Name Calibrated to Port(s) Table 9-34 40-WSS-C Virtual Photodiode Port Calibration Virtual Photodiode CTC Type Name Calibrated to Port(s) VPD1 COM COM RX port (total input COM RX power) VPD2 EXP EXP TX port (total output EXP TX power) Table 9-35 40-WSS-C Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195 1537.409-60 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-C Card 9.10.6 40-WSS-C Card-Level Indicators The 40-WSS-C card has three card-level LED indicators, described in Table 9-36. B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.35 B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194 1545.32 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.32 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193 1553.33 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192 1561.42 Table 9-35 40-WSS-C Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm)9-61 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card 9.10.7 40-WSS-C Port-Level Indicators You can find the alarm status of the 40-WSS-C card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to the “Manage Alarms” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 9.11 40-WSS-CE Card (Cisco ONS 15454 and ONS 15454 M6 only) Note See the “A.8.9 40-WSS-CE Card Specifications” section on page A-34 for hardware specifications. The double-slot 40-channel Wavelength Selective Switch Even-Channel C-Band (40-WSS-CE) card switches 40 ITU-T 100-GHz-spaced channels identified in the channel plan (Table 9-39 on page 9-66) and sends them to dedicated output ports. The 40-WSS-CE card is bidirectional and optically passive. The card can be installed in Slots 1 to 6 and 12 to 17. The 40-WSS-CE features include: • Receipt of an aggregate DWDM signal into 40 output optical channels from the Line receive port (EXP RX) in one direction and from the COM-RX port in the other direction. • Per-channel optical power monitoring using photodiodes. • Signal splitting in a 70-to-30 percent ratio, sent to the 40-DMX-CE card for dropping signals, then to the other 40-WSS-CE card. • Aggregate DWDM signal monitoring and control through a VOA. In the case of electrical power failure, the VOA is set to its maximum attenuation for safety purposes. A manual VOA setting is also available. Within the 40-WSS-CE card, the first AWG opens the spectrum and each wavelength is directed to one of the ports of a 1x2 optical switch. The same wavelength can be passed through or stopped. If the pass-through wavelength is stopped, a new channel can be added at the ADD port. The card’s second AWG multiplexes all of the wavelengths, and the aggregate signal is output through the COM-TX port. Table 9-36 40-WSS-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 40-WSS-C is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-62 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card 9.11.1 40-WSS-CE Faceplate Ports The 40-WSS-CE card has eight types of ports: • ADD RX ports (1 to 40): These ports are used for adding channels. Each add channel is associated with an individual switch element that selects whether an individual channel is added. Each add port has optical power regulation provided by a VOA. The five connectors on the card faceplate accept MPO cables for the client input interfaces. MPO cables break out into eight separate cables. The 40-WSS-CE card also has one LC-PC-II optical connector for the main input. • COM RX: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE) and sends it to the optical splitter. • COM TX: The COM TX port sends an aggregate optical signal to a booster amplifier card (for example, the OPT-BST card) for transmission outside of the NE. • EXP RX port: The EXP RX port receives an optical signal from another 40-WSS-CE card in the same NE. • EXP TX: The EXP TX port sends an optical signal to the other 40-WSS-CE card within the NE. • DROP TX port: The DROP TX port sends the split off optical signal that contains drop channels to the 40-DMX-C card, where the channels are further processed and dropped. Figure 9-31 shows the 40-WSS-CE card faceplate.9-63 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card Figure 9-31 40-WSS-CE Faceplate 9.11.2 40-WSS-CE Card Block Diagram Figure 9-32 shows a block diagram of the 40-WSS-CE card. 240643 40-WSS-C 37.0 - 42.5 30.7 - 36.2 43.3 - 48.9 49.7 - 55.3 56.2 - 61.8 ADD RX COM RX TX EXP RX TX DROP TX FAIL ACT SF9-64 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card Figure 9-32 40-WSS-CE Block Diagram Figure 9-33 shows the 40-WSS-CE optical module functional block diagram. 159393 ADD RX CONTROL Control Interface Comon TX Comon RX EXPRESS RX 2 2 ADD 2 2 Pas Through EXPRESS TX Virtual photodiode DROP TX 1 1 ADD 1 1 Pas Through 40 40 ADD 70/30 40 2 Pas Through9-65 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card Figure 9-33 40-WSS-CE Card Optical Module Functional Block Diagram 9.11.3 40-WSS-CE Card ROADM Functionality The 40-WSS-CE card works in combination with the 40-DMX-CE card to implement ROADM functionality. As a ROADM node, the ONS 15454 can be configured at the optical channel level using CTC, Cisco TransportPlanner, and CTM. ROADM functionality using the 40-WSS-CE card requires two 40-WSS-CE double-slot cards and two 40-DMX-CE single-slot cards (for a total of six slots in the ONS 15454 chassis). For information about ROADM functionality for another cards, see the description of that card in this chapter. For a diagram of a typical ROADM configuration, see the “11.1.3 ROADM Node” section on page 11-10. 9.11.4 40-WSS-CE Card Power Monitoring The 40-WSS-CE card has physical diodes that monitor power at various locations on the card. Table 9-37 lists the physical diode descriptions. Optical module 159392 uP8260 COM RX COM TX FPGA For SCL Bus management 2xSCL Buses DC/DC Power supply Input filters BAT A&B EXP RX ADD RX LC connector MPO connector EXP TX DROP TX Table 9-37 40-WSS-CE Physical Photodiode Port Calibration Physical Photodiode CTC Type Name Calibrated to Port(s) P1 DROP DROP TX P2 EXP EXP RX9-66 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. Additionally, the 40-WSS-CE card has two virtual diodes. Virtual diodes are monitor points for each physical photodiode; they are identified with a physical diode relative to the way that the physical diode is identified with one of the two interlink (ILK) ports. Table 9-38 lists the virtual diodes. 9.11.5 40-WSS-CE Card Channel Plan Table 9-39 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are switched by the 40-WSS-CE card. PDi3 1 RX Add i RX ports (that is, channel input Add i RX power), up to 40 ports and therefore 40 PDs1 PDi4 1 TX COM TX port (that is, per channel output COM TX power) up to 40 channels and therefore 40 PDs PD5 COM COM TX port (that is, total output COM TX power) 1. i indicates any channel from 01 through 40. Table 9-37 40-WSS-CE Physical Photodiode Port Calibration (continued) Physical Photodiode CTC Type Name Calibrated to Port(s) Table 9-38 40-WSS-CE Virtual Photodiode Port Calibration Virtual Photodiode CTC Type Name Calibrated to Port(s) VPD1 COM COM RX port (total input COM RX power) VPD2 EXP EXP TX port (total output EXP TX power) Table 9-39 40-WSS-CE Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.7 30.7 195.85 1530.72 31.5 195.75 1531.51 32.3 195.65 1532.29 33.1 195.55 1533.07 33.9 195.45 1533.86 B34.6 34.6 195.35 1534.64 35.4 195.25 1535.43 36.2 195.15 1536.22 37.0 195.05 1537.00 37.8 194.95 1537.799-67 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WSS-CE Card 9.11.6 40-WSS-CE Card-Level Indicators The 40-WSS-CE card has three card-level LED indicators, described in Table 9-40. B38.6 38.6 194.85 1538.58 39.4 194.75 1539.37 40.1 194.65 1540.16 40.9 194.55 1540.95 41.8 194.45 1541.75 B42.5 42.5 194.35 1542.54 43.3 194.25 1543.33 44.1 194.15 1544.13 44.9 194.05 1544.92 45.7 193.95 1545.72 B46.5 46.5 193.85 1546.52 47.3 193.75 1547.32 48.1 193.65 1548.11 48.9 193.55 1548.91 49.7 193.45 1549.72 B50.5 50.5 193.35 1550.52 51.3 193.25 1551.32 52.1 193.15 1552.12 52.9 193.05 1552.93 53.7 192.95 1553.73 B54.4 54.4 192.85 1554.54 55.3 192.75 1555.34 56.1 192.65 1556.15 56.9 192.55 1556.96 57.8 192.45 1557.77 B58.6 58.6 192.35 1558.58 59.4 192.25 1559.39 60.2 192.15 1560.20 61.0 192.05 1561.01 61.8 191.95 1561.83 Table 9-39 40-WSS-CE Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm)9-68 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WXC-C Card 9.11.7 40-WSS-CE Card Port-Level Indicators You can find the alarm status of the 40-WSS-CE card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to the “Manage Alarms” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 9.12 40-WXC-C Card (Cisco ONS 15454 and ONS 15454 M6 only) Note See the “A.8.10 40-WXC-C Card Specifications” section on page A-37 or hardware specifications. The double-slot 40-channel Wavelength Cross-Connect C-band (40-WXC-C) card selectively sends any wavelength combination coming from nine input ports to a common output port. The device can manage up to 41 channels spaced at 100GHz on each port according to the channel grid in Table 9-10 on page 9-11. Each channel can be selected from any input. The card is optically passive and provides bidirectional capability. It can be installed in Slots 1 to 6 and 12 to 17. .The 40-WXC-C card provides the following features: • Demultiplexing, selection, and multiplexing of DWDM aggregate signal from input ports to common output port. • Aggregate DWDM signal monitoring and control through a VOA. • VOAs are deployed in every channel path in order to regulate the channel’s optical power. In the case of an electrical power failure, VOAs are set to their maximum attenuation value, or to a fixed and configurable one. The VOA can also be set manually. • Per-channel optical power monitoring using photodiodes. The 40-WXC-C card acts as a selector element with the following characteristics: • It is able to select a wavelength from one input port and pass the wavelength through to the common out port. Simultaneously, the card can block the same wavelength coming from the other eight input ports. • It is able to stop wavelengths from all nine inputs. Table 9-40 40-WSS-CE Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 40-WSS-CE card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-69 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WXC-C Card • It is able to monitor optical power and control path attenuation using per channel VOA independently of the wavelength input-to-out port connection. 9.12.1 40-WXC-C Faceplate Ports The 40-WXC-C card has six types of ports: • COM RX: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE) and sends it to the optical splitter. • COM TX: The COM TX port sends an aggregate optical signal to a booster amplifier card (for example, the OPT-BST card) for transmission outside of the NE. • EXP TX: The EXP TX port sends an optical signal to the other 40-WXC-C card within the NE. • MON TX: The optical service channel (OSC) monitor. • ADD/DROP RX: The 40-WXC-C card provides 40 input optical channels. For the wavelength range, see Table 9-43 on page 9-73. • ADD/DROP TX: The DROP TX port sends the split off optical signal that contains drop channels to the 40-WXC-C card, where the channels are further processed and dropped. Figure 9-34 shows the 40-WXC-C card faceplate.9-70 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WXC-C Card Figure 9-34 40-WXC-C Faceplate 9.12.2 40-WXC-C Block Diagram Figure 9-35 shows the 40-WXC-C optical module functional block diagram. 159396 40-WXC EXP COM RX TX EXP TX ADD DROP RX TX MON TX FAIL ACT SF RX EXP RX Ports (from 1 to 8): fibres come FROM Mesh PP Monitor Port: monitors the traffic transmitted on COM TX Port DROP TX: fibre connected to 40-DMX for local chs drop ADD RX: fibre connected to 40- MUX or xx-WSS for local chs Add EXP TX: internal connection TO Mesh PP COM RX: line RX interface FROM Pre-Amplifier COM TX: line TX interface TO Booster Amplifier9-71 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WXC-C Card Figure 9-35 40-WXC-C Optical Module Functional Block Diagram 9.12.3 40-WXC-C Power Monitoring The 40-WXC-C has 83 physical diodes (P1 through P40) that monitor power at the outputs of the card. Table 9-41 describes the physical diodes. WXC optical module COM TX ADD RX Virtual PDi3 P5 Table 9-41 40-WXC-C Physical Photodiode Port Calibration Physical Photodiode CTC Type Name Calibrated to Port(s) P1 DROP DROP TX P2 EXP EXP RX PDi3 1 1. i indicates any channel from 01 through 40. RX Add i RX ports (that is, channel input Add i RX power), up to 40 ports and therefore 40 PDs1 PDi4 1 TX COM TX port (that is, per channel output COM TX power) up to 40 channels and therefore 40 PDs PD5 COM COM TX port (that is, total output COM TX power)9-72 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WXC-C Card For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. Additionally, the 40-WXC-C has two virtual diodes. Virtual diodes are monitor points for each physical photodiode; they are identified with a physical diode relative to the way that the physical diode is identified with one of the two interlink (ILK) ports. Table 9-42 lists the virtual diodes. The usage of WXC and mesh PP power readings to troubleshoot a LOS-P in WXC COM TX port in Side A is described in the following example. The example is explained assuming a single wavelength 1558.17 in the setup that comes from Side H to Side A. If there is more than one wavelength, then there is a risk of dropping traffic when pulling common fibers. The example is explained below: When the wavelength from side H is 1558.17, you can check the power reading at WXC EXP TX port of the WXC card and verify the consistency with side H pre output power and WXC COMRX-EXPTX port loss. You can also check with a power meter connected to the 8th fiber (since it is from side H) of an MPO-FC (or LC) cable connected to the TAP-TX port of the MESH-PP. This value should be consistent with the previous reading, less than the insertion loss of the installed PP-MESH. If it is consistent, the issue is with the MPO between side A WXC and PP-MESH. If it is not consistent, the issue is with the PP-MESH or the LC-LC from side H. With only the PP-MESH already tested during installation, the only issue can be with the patch cord b. You can check if the 1558.17 wavelength from side H is unequalized (that is, if the channel is not aligned with the linear fit of the power values of the other channels) by keeping the DMX COM-RX port of side H in maintenance, and checking both the signal and ASE levels of CHAN-TX ports of the DMX card. If the channel is equalized (that is, if the channel is aligned with the linear fit of the power values of the other channels), then the issue is in the WXC side A that cannot properly regulate the VOA for such channel. If the channel is unequalized, then the issue is on a remote node. Note With an OSA or a spare 40 DMX, you can see the light coming from all the sides from TAP-TX of the PP-MESH. 9.12.4 40-WXC-C Channel Plan Table 9-43 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are cross connected by the 40-WXC-C card. Table 9-42 40-WXC-C Virtual Photodiode Port Calibration Virtual Photodiode CTC Type Name Calibrated to Port(s) VPD1 COM COM RX port (total input COM RX power) VPD2 EXP EXP TX port (total output EXP TX power)9-73 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 40-WXC-C Card Table 9-43 40-WXC-C Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) Ch. 01 29.5 196 1529.55 B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195 1537.40 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.35 B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194 1545.32 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.32 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193 1553.339-74 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card 9.12.5 40-WXC-C Card-Level Indicators The 40-WXC-C card has three card-level LED indicators described in Table 9-44. 9.12.6 40-WXC-C Port-Level Indicators You can find the alarm status of the 40-WXC-C card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.13 80-WXC-C Card (Cisco ONS 15454 and ONS 15454 M6 only) B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192 1561.42 1. This channel is unused by the 40-WXC-C Table 9-43 40-WXC-C Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm) Table 9-44 40-WXC-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 40-WXC-C is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-75 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card Note See the “A.8.11 80-WXC-C Card Specifications” section on page A-38 or hardware specifications. The double-slot 80-channel Wavelength Cross-Connect C-band (80-WXC-C) card manages up to 80 ITU-T 100-GHz-spaced channels identified in the channel plan (Table 9-10 on page 9-11) and sends them to dedicated output ports. Each channel can be selected from any input port to any output port. The card is optically passive, and provides bidirectional capability. It can be installed in Slots 1 to 5 and 12 to 16 the ONS 15454 chassis and Slots 2 to 6 in the ONS 15454 M6 chassis. The 80-WXC-C card provides the following functionalities: • When used in the multiplexer or bidirectional mode, the 80-WXC-C card allows selection of a single wavelength or any combination of wavelengths from any of the nine input ports to the common output port. • When used in the bidirectional mode, the output wavelength from the COM-RX port is split to manage the express and drop wavelengths. • When used in the demultiplexer mode, the 80-WXC-C card, allows selection of a single wavelength or a combination of wavelengths from the common input port to any of the nine output ports. • Automatic VOA shutdown (AVS) blocking state on each wavelength and port. • Per-channel (closed loop) power regulation on the output port based on OCM block feedback. • Per-channel (open loop) attenuation regulation on the output port which is not based on the OCM feedback. The OCM unit provides per-channel optical power monitoring on the following ports: • COM port in output direction • COM port in input direction • DROP-TX port in output direction • Eight Express/Add/Drop (EAD) ports and one Add/Drop (AD) port in both input and output directions 9.13.1 80-WXC-C Faceplate and Optical Module Functional Block Diagram The 80-WXC-C card has 14 types of ports: • MON: The MON port monitors power on the COM T/R port. • COM RX: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE) and sends it to the optical splitter. • DROP TX: In the bidirectional mode, the DROP TX port sends the optical signal to the demultiplexer. • EXP TX: The EXP TX port sends the split off optical signal that contains pass-through channels to the other side of the NE . • COM T/R: The COM port is bidirectional. It functions as a COM TX port in the multiplexer mode and as a COM RX port in the demultiplexer mode. • AD T/R: The AD port functions as ADD RX port in bidirectional and multiplexer modes and as a DROP port in the demultiplexer mode. • EAD T/R i (where i = 1 to 8): The EAD ports function as EXP ports in the bidirectional mode, as ADD ports in the multiplexer mode, and as DROP ports in the demultiplexer mode.9-76 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card Figure 9-36 shows the 80-WXC-C card faceplate and the optical module functional block diagram. Figure 9-36 80-WXC-C Faceplate and the Optical Module Functional Block Diagram COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No.50, DATED JUNE 24, 2007 5 6 7 ADD / DROP 8 3 4 EXP DROP TX RX COM TX 1 2 R/T COM T/R MON FAIL ACT SF 80-WXC-C EXP / ADD / DROP R/T R/T R/T R/T 249126 VPD4 VPD3 VOA DROP_TX OCM 12 PD2 EAD 1...8 OCM 1...9 AD DROP TX EXP TX COM RX MON COM LC connectors Variable optical attenuator OUT OCM 10 OCM 11 1 10 PD1 9 40/60 12x1 Optical Switch OCM WXC9-77 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card The different units of the 80-WXC-C card are: • 40/60 splitter with VOA on drop path—The preamplifier output signal from the preamplifier is split in a 40%-to-60% ratio; 40% is sent on the drop path (DROP-TX port) and 60% is sent on the pass-through path (EXP-TX port). The VOA equipped on the drop path is used to match the power range of the receiver photodiode without the need for bulk attenuation. If a channel is expected to be dropped in the 80-WXC-C card, the pass-through channel is stopped after the EXP-TX port either by a 40-WSS-C or a 40-WXC-C card. • 50 Ghz 10 port WXC—The WXC block is optically passive and has bidirectional capability. The WXC block can selectively send any wavelength combination coming from the eight input EAD ports and one AD port to a common (COM) output port, when used as a multiplexer, whereas it can selectively send any wavelength combination coming from its common (COM) input port to any of the eight output EAD ports and one AD port, when used as a demultiplexer. The WXC block can manage (on each port) up to 80 channels according to the channel grid reported in Table 9-47. Each channel can be selected from any input and routed to any output. • 50 Ghz Optical Channel Monitor (OCM)—The OCM provides per channel power monitoring on the COM T/R, DROP-TX, AD, and EADi (i=1 to 8) ports. The power value for each wavelength is refreshed after a variable timer depending on the port and card activity. 9.13.2 80-WXC-C Power Monitoring The 80-WXC-C has two physical photodiodes and an OCM unit that monitors power at the different ports of the card. Table 9-45 describes the physical photodiodes. For information on the associated TL1 AIDs for the optical power monitoring points, see the “CTC Port Numbers and TL1 Aids” section in the Cisco ONS SONET TL1 Command Guide, Release 9.2. Table 9-45 80-WXC-C Port Calibration Physical Photodiode CTC Type Name Calibrated to Port(s) PD1 COM Total Power COM PD2 EXP-TX Total Power EXP-TX OCM1 EAD 1 Per-Channel and Total Power EAD-1 OCM2 EAD 2 Per-Channel and Total Power EAD-2 OCM3 EAD 3 Per-Channel and Total Power EAD-3 OCM4 EAD 4 Per-Channel and Total Power EAD-4 OCM5 EAD 5 Per-Channel and Total Power EAD-5 OCM6 EAD 6 Per-Channel and Total Power EAD-6 OCM7 EAD 7 Per-Channel and Total Power EAD-7 OCM8 EAD 8 Per-Channel and Total Power EAD-8 OCM9 AD Per-Channel and Total Power AD OCM10 Output Per-Channel and Total Power COM OCM11 Input Per-Channel and Total Power COM OCM12 Drop Per-Channel and Total Power DROP-TX9-78 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card Additionally, the 80-WXC-C has two virtual photodiodes. Table 9-46 lists the virtual photodiodes. 9.13.3 80-WXC-C Channel Plan Table 9-47 shows the 80 ITU-T 50-GHz-spaced, C-band channels (wavelengths) that are cross connected by the 80-WXC-C card. Table 9-46 80-WXC-C Virtual Photodiode Port Calibration Virtual Photodiode CTC Type Name Calibrated to Port(s) VPD3 DROP-TX Total Power DROP-TX VPD4 COM-RX Total Power COM-RX Table 9-47 80-WXC-C Channel Plan Band ID Channel Label Frequency (THz) Wavelength (nm) Ch. 01 - 196 1529.55 30.3 30.3 195.9 1530.33 30.7 195.85 1530.72 31.1 195.8 1531.12 31.5 195.75 1531.51 31.9 195.7 1531.90 32.3 195.65 1532.29 32.7 195.6 1532.68 33.1 195.55 1533.07 33.5 195.5 1533.47 33.9 195.45 1533.86 34.3 34.3 195.4 1534.25 34.6 195.35 1534.64 35.0 195.3 1535.04 35.4 195.25 1535.43 35.8 195.2 1535.82 36.2 195.15 1536.22 36.6 195.1 1536.61 37.0 195.05 1537 37.4 195 1537.40 37.8 194.95 1537.799-79 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card 38.2 38.2 194.9 1538.19 38.6 194.85 1538.58 39.0 194.8 1538.98 39.4 194.75 1539.37 39.8 194.7 1539.77 40.2 194.65 1540.16 40.6 194.6 1540.56 41.0 194.55 1540.95 41.3 194.5 1541.35 41.7 194.45 1541.75 42.1 42.1 194.4 1542.14 42.5 194.35 1542.94 42.9 194.3 1542.94 43.3 194.25 1543.33 43.7 194.2 1543.73 44.1 194.15 1544.13 44.5 194.1 1544.53 44.9 194.05 1544.92 45.3 194 1545.32 45.7 193.95 1545.72 46.1 46.1 193.9 1546.12 46.5 193.85 1546.52 46.9 193.8 1546.92 47.3 193.75 1547.32 47.7 193.7 1547.72 48.1 193.65 1548.11 48.5 193.6 1548.51 48.9 193.55 1548.91 49.3 193.5 1549.32 49.7 193.45 1549.72 Table 9-47 80-WXC-C Channel Plan (continued) Band ID Channel Label Frequency (THz) Wavelength (nm)9-80 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards 80-WXC-C Card 9.13.4 80-WXC-C Card-Level Indicators The 80-WXC-C card has three card-level LED indicators described in Table 9-48. 50.1 50.1 193.4 1550.12 50.5 193.35 1550.52 50.9 193.3 1550.92 51.3 193.25 1551.32 51.7 193.2 1551.72 52.1 193.15 1552.12 52.5 193.1 1552.52 52.9 193.05 1552.93 53.3 193 1553.33 53.7 192.95 1553.73 54.1 54.1 192.9 1554.13 54.5 192.85 1554.54 54.9 192.8 1554.94 55.3 192.75 1555.34 55.7 192.7 1555.75 56.2 192.65 1556.15 56.6 192.6 1556.55 57.0 192.55 1556.96 57.4 192.5 1557.36 57.8 192.45 1557.77 58.2 58.2 192.4 1558.17 58.6 192.35 1558.58 59.0 192.3 1558.98 59.4 192.25 1559.39 59.8 192.2 1559.79 60.2 192.15 1560.20 60.6 192.1 1560.61 61.0 192.05 1561.01 61.4 192 1561.42 61.8 191.95 1561.83 1. This channel is unused by the 80-WXC-C Table 9-47 80-WXC-C Channel Plan (continued) Band ID Channel Label Frequency (THz) Wavelength (nm)9-81 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.13.5 80-WXC-C Port-Level Indicators You can find the alarm status of the 80-WXC-C card ports using the LCD screen or unit. The LCD screen is on the ONS 15454 and ONS 15454 M2 fan-tray assembly and is a separate unit in ONS 15454 M6. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, see the “Manage Alarms” section in the Cisco ONS 15454 DWDM Procedure Guide. 9.14 Single Module ROADM (SMR-C) Cards Note See the “A.8.12 40-SMR1-C Card Specifications” section on page A-39 and “A.8.13 40-SMR2-C Card Specifications” section on page A-40, or hardware specifications. Note For 40-SMR1-C and 40-SMR2-C safety label information, see the “9.2 Safety Labels for Class 1M Laser Product Cards” section on page 9-14. The single-slot 40-channel single module ROADM (SMR-C) cards integrate the following functional blocks onto a single line card: • Optical preamplifier • Optical booster amplifier • Optical service channel (OSC) filter • 2x1 wavelength cross-connect (WXC) or a 4x1 WXC • Optical channel monitor (OCM) The SMR-C cards are available in two versions: • 9.14.2 40-SMR1-C Card • 9.14.3 40-SMR2-C Card The SMR-C cards can manage up to 40 channels spaced at 100GHz on each port according to the channel grid in Table 9-10. The cards can be installed in Slots 1 to 6 and 12 to 17. Table 9-48 80-WXC-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the 80-WXC-C is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-82 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.14.1 SMR-C Card Key Features The optical amplifier units in the SMR-C cards provide the following features: • Embedded gain flattening filter • Mid-stage access for dispersion compensation unit (only applicable for preamplifier erbium-doped fiber amplifier [EDFA]) • Fixed output power mode • Fixed gain mode • Nondistorting low-frequency transfer function • Amplified spontaneous emissions (ASE) compensation in fixed gain and fixed output power mode • Fast transient suppression • Programmable tilt (only applicable for preamplifier EDFA) • Full monitoring and alarm handling capability • Optical safety support through signal loss detection and alarm at any input port, fast power down control, and reduced maximum output power in safe power mode. • EDFA section calculates the signal power, by taking into account the expected ASE power contribution to the total output power. The signal output power or the signal gain can be used as feedback signals for the EDFA pump power control loop. The 1x2 WXC unit (40-SMR1-C card) provides the following features: • Selection of individual wavelength of the aggregated 100GHz signal from either the EXP-RX or ADD-RX ports • Automatic VOA shutdown (AVS) blocking state on each wavelength and port • Per-channel power regulation based on external OCM unit • Open loop path attenuation control for each wavelength and port The 1x4 WXC unit (40-SMR2-C card) provides the following features: • Selection of individual wavelength of the aggregated 100GHz signal from either the EXPi-RX (where i = 1, 2, 3) or ADD-RX ports • Automatic VOA shutdown (AVS) blocking state on each wavelength and port • Per-channel power regulation based on external OCM unit • Open loop path attenuation control for each wavelength and port The OCM unit provides per channel optical power monitoring at EXP-RX, ADD-RX, DROP-TX, and LINE-TX ports. 9.14.2 40-SMR1-C Card The 40-SMR1-C card includes a 100Ghz 1x2 WXC unit with integrated preamplifier unit (single EDFA). 9.14.2.1 40-SMR1-C Faceplate Ports The 40-SMR1-C card has the following types of ports: • MON RX: The MON RX port monitors power on the EXP-TX output port.9-83 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards • MON TX: The MON TX port monitors power on the LINE-TX output port. • DC RX: The DC RX port receives the optical signal from the dispersion compensating unit (DCU) and sends it to the second stage preamplifier input. • DC TX: The DC TX port sends the optical signal from the first stage preamplifier output to the DCU. • OSC RX: The OSC RX port is the OSC add input port. • OSC TX: The OSC TX port is the OSC drop output port. • ADD/DROP RX: The ADD RX port receives the optical signal from the multiplexer section of the NE and sends it to the 1x2 WXC unit. • ADD/DROP TX: The DROP TX port sends the split off optical signal to the demultiplexer section of the NE. • LINE RX: The LINE RX port is the input signal port. • LINE TX: The LINE TX port is the output signal port. • EXP RX: The EXP RX port receives the optical signal from the other side of the NE and sends it to the 1x2 WXC unit. • EXP TX: The EXP TX port sends the split off optical signal that contains pass-through channels to the other side of the NE. Figure 9-37 shows the 40-SMR1-C card faceplate. Figure 9-37 40-SMR1-C Faceplate 9.14.2.2 40-SMR1-C Block Diagram Figure 9-38 shows a block diagram of the 40-SMR1-C card. LEVEL 1M HAZARD OSC DC EXP MON RX TX ADD & DROP RX TX LINE RX TX RX TX RX TX RX TX SF ACT FAIL 1-C 40-SMR COMPLIES WITH 21 CFR 1040.10 AND FOR DEVIATIONS 1040.11 EXCEPT NOTICE No.50, DATED PURSUANT TO LASER JUNE 24, 2007 2764409-84 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards Figure 9-38 40-SMR1-C Block Diagram The different units of the 40-SMR1-C card are: • OSC filter—The OSC filter allows to add an OSC channel to the C-band in the transmission path and to drop an OSC channel on the receiving path. The OSCM card that is connected to the OSC-TX and OSC-RX ports generates the OSC channel. • Double-stage variable gain EDFA preamplifier—The double-stage preamplifier allows the insertion of a DCU between the DC-TX and DC-RX ports to compensate for chromatic dispersion. It is also equipped with built-in variable optical attenuator (VOA) and gain flattening filter (GFF) that provides tilt compensation and enables the use of this device over an extended range of span losses (5 dB to 35 dB). • 70/30 splitter and VOA—The output signal from the preamplifier is split in a 70%-to-30% ratio, 70% is sent on the pass-through path (EXP-TX port) and 30% is sent on the drop path (DROP-TX port). The VOA equipped on the drop path is used to match the power range of the receiver photo diode without the need for bulk attenuation. If a channel is expected to be dropped in the 40-SMR1-C card, the pass-through channel is stopped after the EXP-TX port either by a 40-WSS-C, 40-SMR1-C, or 40-SMR2-C card. • 1x2 WXC—The 1x2 WXC aggregates on its output port a 100-GHz-spaced optical channel received from either its ADD-RX or EXP-RX port. In addition to the switching function, the 1x2 WXC allows to set a different per channel power for each of the managed wavelengths and also monitor the optical power. • OCM—The OCM provides per channel power monitoring on the DROP-RX, EXP-RX, ADD-RX, and LINE-TX ports. The power value for each wavelength is refreshed after a variable timer depending on the port and card activity. OSC-TX DC-TX DC-RX DROP-TX OSC-RX ADD-RX OCM Block OCM4 OCM3 OCM2 OCM1 VOA3 VOA2 LINE TX LINE RX MON-TX EXP-RX EXP-TX MON-RX EDFA 1 (variable Gain VOA1 30% 70% OSC DROP PD2 PD3 PD4 TAP TAP PD5 TAP PD8 OSC ADD TAP TAP TAP 276446 TAP PD6 WXC Block PD1 LC connector9-85 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.14.2.3 40-SMR1-C Power Monitoring The 40-SMR1-C card has seven physical diodes (PD1 through PD6 and PD8) and an OCM unit that monitors power at the input and output ports of the card (see Table 9-49). 9.14.2.4 40-SMR1-C Channel Plan Table 9-50 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) supported by the 40-SMR1-C card. Table 9-49 40-SMR1-C Port Calibration Physical Photodiode CTC Type Name Calibrated to Port(s) PD1 LINE LINE-RX PD2 LINE LINE-RX PD3 DC DC-TX PD4 DC DC-RX PD5 EXP EXP-TX PD6 OSC OSC-RX PD8 LINE LINE-TX OCM1 LINE OCH LINE-TX OCM2 DROP OCH DROP-TX OCM3 ADD OCH ADD-RX OCM4 EXP OCH EXP-RX Table 9-50 40-SMR1-C Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195 1537.409-86 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.14.2.5 40-SMR1-C Card-Level Indicators The 40-SMR1-C card has three card-level LED indicators described in Table 9-51. B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.35 B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194 1545.32 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.32 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193 1553.33 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192 1561.42 Table 9-50 40-SMR1-C Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm)9-87 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.14.2.6 40-SMR1-C Port-Level Indicators You can find the alarm status of the 40-SMR1-C card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. 9.14.3 40-SMR2-C Card The 40-SMR2-C card includes a 100Ghz 1x4 WXC unit with integrated preamplifier and booster amplifier units (double EDFA). 9.14.3.1 40-SMR2-C Faceplate Ports The 40-SMR2-C card has the following types of ports: • MON RX: The MON RX port monitors power on the EXP-TX output port. • MON TX: The MON TX port monitors power on the LINE-TX output port. • DC RX: The DC RX port receives the optical signal from the dispersion compensating unit (DCU) and sends it to the second stage preamplifier input. • DC TX: The DC TX port sends the optical signal from the first stage preamplifier output to the DCU. • OSC RX: The OSC RX port is the OSC add input port. • OSC TX: The OSC TX port is the OSC drop output port. • ADD/DROP RX: The ADD RX port receives the optical signal from the multiplexer section of the NE and sends it to the 1x4 WXC unit. • ADD/DROP TX: The DROP TX port sends the split off optical signal to the demultiplexer section of the NE. • LINE RX: The LINE RX port is the input signal port. • LINE TX: The LINE TX port is the output signal port. • EXP TX: The EXP TX port sends the split off optical signal that contains pass-through channels to the other side of the NE. Table 9-51 40-SMR1-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-88 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards • EXPi-RX (where i = 1, 2, 3): The EXPi-RX port receives the optical signal from the other side of the NE and sends it to the 1x4 WXC unit. Figure 9-37 shows the 40-SMR2-C card faceplate. Figure 9-39 40-SMR2-C Faceplate 9.14.3.2 40-SMR2-C Block Diagram Figure 9-38 shows a block diagram of the 40-SMR2-C card. Figure 9-40 40-SMR2-C Block Diagram The different units of the 40-SMR2-C card are: 276441 EXP OSC DC RX TX ADD & DROP RX TX LINE RX TX RX TX RX TX MON SF ACT FAIL 2-C 40-SMR COMPLIES WITH 21 CFR 1040.10 AND FOR DEVIATIONS 1040.11 EXCEPT NOTICE No.50, DATED PURSUANT TO LASER JUNE 24, 2007 LEVEL 1M HAZARD OSC-TX DC-TX DC-RX DROP-TX OSC-RX ADD-RX LINE TX LINE RX MON-TX EXP1-RX EXP2-RX EXP3-RX MON-RX EDFA 1 (Variable Gain) EDFA 2 (Fixed Gain) 30% 70% OSC DROP PD2 PD3 PD4 TAP TAP PD5 TAP PD8 PD7 OSC ADD TAP TAP 276447 TAP PD6 4x1 WXC Block PD1 TAP TAP LC connector MPO connector EXP-TX 6 ports OCM Block9-89 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards • OSC filter—The OSC filter allows to add an OSC channel to the C-band in the transmission path and to drop an OSC channel on the receiving path. The OSCM card that is connected to the OSC-TX and OSC-RX ports generates the OSC channel. • Double-stage variable gain EDFA preamplifier—The double-stage preamplifier allows the insertion of a DCU between the DC-TX and DC-RX ports to compensate for chromatic dispersion. It is also equipped with built-in variable optical attenuator (VOA) and gain flattening filter (GFF) that provides tilt compensation and enables the use of this device over an extended range of span losses (5 dB to 35 dB). • 70/30 splitter and VOA—The output signal from the preamplifier is split in a 70%-to-30% ratio, 70% is sent on the pass-through path (EXP-TX port) and 30% is sent on the drop path (DROP-TX port). The VOA equipped on the drop path is used to match the power range of the receiver photo diode without the need for bulk attenuation. If a channel is expected to be dropped in the 40-SMR2-C card, the pass-through channel is stopped after the EXP-TX port by a 40-WSS-C, 40-SMR1-C, or 40-SMR2-C card. • 1x4 WXC—The 1x4 WXC aggregates on its output port a 100-GHz-spaced optical channel received from either its ADD-RX or EXPi-RX (where i = 1, 2, 3) port. In addition to the switching function, the 1x4 WXC allows to set a different per channel power for each of the managed wavelengths and also monitor the optical power. • Single-stage fixed gain EDFA booster amplifier—The booster amplifier amplifies the output signal from the 1x4 WXC unit before transmitting it into the fiber. Since it is a fixed gain (17 dB) amplifier, it does not allow gain tilt control. • OCM—The OCM provides per channel power monitoring on the DROP-RX, EXPi-RX (where i = 1, 2, 3), ADD-RX, and LINE-TX ports. The power value for each wavelength is refreshed after a variable timer depending on the port and card activity. 9.14.3.3 40-SMR2-C Power Monitoring The 40-SMR2-C card has eight physical diodes (PD1 through PD8) and an OCM unit that monitors power at the input and output ports of the card (see Table 9-52). Table 9-52 40-SMR2-C Port Calibration Physical Photodiode CTC Type Name Calibrated to Port(s) PD1 LINE LINE-RX PD2 LINE LINE-RX PD3 DC DC-TX PD4 DC DC-RX PD5 EXP EXP-TX PD6 OSC OSC-RX PD7 Not reported on CTC Internal port PD8 LINE LINE-TX OCM1 LINE OCH LINE-TX OCM2 DROP OCH DROP-TX OCM3 ADD OCH ADD-RX OCM4 EXP-1 OCH EXP1-RX9-90 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.14.3.4 40-SMR2-C Channel Plan Table 9-53 shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) supported by the 40-SMR2-C card. OCM5 EXP-2 OCH EXP2-RX OCM6 EXP-3 OCH EXP3-RX Table 9-52 40-SMR2-C Port Calibration (continued) Physical Photodiode CTC Type Name Calibrated to Port(s) Table 9-53 40-SMR2-C Channel Plan Band ID Channel Label Frequency (GHz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195 1537.40 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.35 B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194 1545.32 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.329-91 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards Single Module ROADM (SMR-C) Cards 9.14.3.5 40-SMR2-C Card-Level Indicators The 40-SMR2-C card has three card-level LED indicators described in Table 9-54. 9.14.3.6 40-SMR2-C Port-Level Indicators You can find the alarm status of the 40-SMR2-C card ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193 1553.33 B54.1 54.1 192.9 1554.13 54.9 192.8 1554.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192 1561.42 Table 9-53 40-SMR2-C Channel Plan (continued) Band ID Channel Label Frequency (GHz) Wavelength (nm) Table 9-54 40-SMR2-C Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card processor is not ready or that an internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-92 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards MMU Card 9.15 MMU Card (Cisco ONS 15454 only) The single-slot Mesh Multi-Ring Upgrade Module (MMU) card supports multiring and mesh upgrades for ROADM nodes in both the C-band and the L-band. Mesh/multiring upgrade is the capability to optically bypass a given wavelength from one section of the network or ring to another one without requiring 3R regeneration. In each node, you need to install one east MMU and one west MMU. The card can be installed in Slots 1 through 6 and 12 through 17. 9.15.1 MMU Faceplate Ports The MMU has six types of ports: • EXP RX port: The EXP RX port receives the optical signal from the ROADM section available on the NE. • EXP TX port: The EXP TX port sends the optical signal to the ROADM section available on the NE. • EXP-A RX port: The EXP-A RX port receives the optical signal from the ROADM section available on other NEs or rings. • EXP-A TX port: The EXP-A TX port sends the optical signal to the ROADM section available on other NEs or rings. • COM TX port: The COM TX port sends the optical signal to the fiber stage section. • COM RX port: The COM RX port receives the optical signal from the fiber stage section. Figure 9-41 shows the MMU card faceplate. 9-93 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards MMU Card Figure 9-41 MMU Faceplate and Ports 9.15.2 MMU Block Diagram Figure 9-42 provides a high-level functional block diagram of the MMU card. 145190 ACT FAIL MMU SF RX TX EXP A RX TX EXP RX TX COM9-94 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards MMU Card Figure 9-42 MMU Block Diagram 9.15.3 MMU Power Monitoring Physical photodiodes P1 through P3 monitor the power for the MMU card. The returned power level values are calibrated to the ports as shown in Table 9-55. VP1 to VP3 are virtual photodiodes that have been created by adding (by software computation) the relevant path insertion losses of the optical splitters (stored in the module) to the real photodiode (P1 to P3) measurement. For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2. 9.15.4 MMU Card-Level Indicators Table 9-56 describes the three card-level LED indicators on the MMU card. 145191 COM TX VPD2 75/25 PD1 EXP RX PD2 EXP A RX COM RX VPD3 95/5 95/5 VPD1 EXP TX Legend LC PC II Connector Optical splitter/coupler Real photodiode Virtual photodiode PD3 EXP A TX Table 9-55 MMU Port Calibration Photodiode CTC Type Name Calibrated to Port P1 1 (EXP-RX) EXP RX P2 5 (EXP A-RX) EXP A RX P3 6 (EXP A-TX) EXP A TX VP1 2 (EXP-TX) EXP TX VP2 4 (COM-TX) COM TX VP3 3 (COM-RX) COM RX9-95 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards MMU Card 9.15.5 MMU Port-Level Indicators You can find the alarm status of the MMU card’s ports using the LCD screen on the ONS 15454 fan-tray assembly. The screen displays the number and severity of alarms on a given port or slot. For the procedure to view these counts, refer to “Manage Alarms” in the Cisco ONS 15454 DWDM Procedure Guide. Table 9-56 MMU Card-Level Indicators Card-Level Indicators Description Red FAIL LED The red FAIL LED indicates that the card’s processor is not ready or that n internal hardware failure occurred. Replace the card if the red FAIL LED persists. Green ACT LED The green ACT LED indicates that the MMU card is carrying traffic or is traffic-ready. Amber SF LED The amber SF LED indicates a signal failure on one or more of the card’s ports. The amber SF LED also turns on when the transmit and receive fibers are incorrectly connected. When the fibers are properly connected, the light turns off.9-96 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 9 Reconfigurable Optical Add/Drop Cards MMU CardCHAPTER 10-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 10 Transponder and Muxponder 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. This chapter describes Cisco ONS 15454 transponder (TXP), muxponder (MXP), GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP cards, as well as their associated plug-in modules (Small Form-factor Pluggables [SFPs or XFPs]). For installation and card turn-up procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For card safety and compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise. Chapter topics include: • 10.1 Card Overview, page 10-2 • 10.2 Safety Labels, page 10-8 • 10.3 TXP_MR_10G Card, page 10-13 • 10.4 TXP_MR_10E Card, page 10-16 • 10.5 TXP_MR_10E_C and TXP_MR_10E_L Cards, page 10-21 • 10.6 TXP_MR_2.5G and TXPP_MR_2.5G Cards, page 10-25 • 10.7 MXP_2.5G_10G Card, page 10-29 • 10.8 MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards, page 10-40 • 10.9 MXP_MR_2.5G and MXPP_MR_2.5G Cards, page 10-49 • 10.10 MXP_MR_10DME_C and MXP_MR_10DME_L Cards, page 10-55 • 10.11 40G-MXP-C Card, page 10-64 • 10.12 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards, page 10-7110-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Card Overview • 10.13 ADM-10G Card, page 10-96 • 10.14 OTU2_XP Card, page 10-111 • 10.15 MLSE UT, page 10-121 • 10.16 TXP_MR_10EX_C Card, page 10-121 • 10.17 MXP_2.5G_10EX_C card, page 10-125 • 10.18 MXP_MR_10DMEX_C Card, page 10-132 • 10.19 Y-Cable and Splitter Protection, page 10-139 • 10.20 Far-End Laser Control, page 10-142 • 10.21 Jitter Considerations, page 10-142 • 10.22 Termination Modes, page 10-143 • 10.23 SFP and XFP Modules, page 10-144 Note Cisco ONS 15454 DWDM supports IBM's 5G DDR (Double Data Rate) InfiniBand1 interfaces. 10.1 Card Overview The card overview section lists the cards described in this chapter and provides compatibility information. 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. For a list of slots and symbols, see the "Card Slot Requirements" section in the Cisco ONS 15454 Hardware Installation Guide. The purpose of a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, or OTU2_XP card is to convert the “gray” optical client interface signals into trunk signals that operate in the “colored” dense wavelength division multiplexing (DWDM) wavelength range. Client-facing gray optical signals generally operate at shorter wavelengths, whereas DWDM colored optical signals are in the longer wavelength range (for example, 1490 nm = violet; 1510 nm = blue; 1530 nm = green; 1550 nm = yellow; 1570 nm = orange; 1590 nm = red; 1610 nm = brown). Some of the newer client-facing SFPs, however, operate in the colored region. Transponding or muxponding is the process of converting the signals between the client and trunk wavelengths. An MXP generally handles several client signals. It aggregates, or multiplexes, lower rate client signals together and sends them out over a higher rate trunk port. Likewise, it demultiplexes optical signals coming in on a trunk and sends them out to individual client ports. A TXP converts a single client signal to a single trunk signal and converts a single incoming trunk signal to a single client signal. GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can be provisioned as TXPs, as MXPs, or as Layer 2 switches. All of the TXP and MXP cards perform optical to electrical to optical (OEO) conversion. As a result, they are not optically transparent cards. The reason for this is that the cards must operate on the signals passing through them, so it is necessary to do an OEO conversion. 1. 5G DDR InfiniBand is referred to as IB_5G.10-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Card Overview On the other hand, the termination mode for all of the TXPs and MXPs, which is done at the electrical level, can be configured to be transparent. In this case, neither the Line nor the Section overhead is terminated. The cards can also be configured so that either Line or Section overhead can be terminated, or both can be terminated. Note The MXP_2.5G_10G card, by design, when configured in the transparent termination mode, actually does terminate some of the bytes. See Table 10-64 on page 10-143 for details. 10.1.1 Card Summary Table 10-1 lists and summarizes the functions of each TXP, TXPP, MXP, MXPP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP card. Table 10-1 Cisco ONS 15454 Transponder and Muxponder Cards Card Port Description For Additional Information TXP_MR_10G The TXP_MR_10G card has two sets of ports located on the faceplate. See the “10.3 TXP_MR_10G Card” section on page 10-13. TXP_MR_10E The TXP_MR_10E card has two sets of ports located on the faceplate. See the “10.4 TXP_MR_10E Card” section on page 10-16. TXP_MR_10E_C and TXP_MR_10E_L The TXP_MR_10E_C and TXP_MR_10E_L cards have two sets of ports located on the faceplate. See the “10.5 TXP_MR_10E_C and TXP_MR_10E_L Cards” section on page 10-21. TXP_MR_2.5G The TXP_MR_2.5G card has two sets of ports located on the faceplate. See the “10.6 TXP_MR_2.5G and TXPP_MR_2.5G Cards” section on page 10-25. TXPP_MR_2.5G The TXPP_MR_2.5G card has three sets of ports located on the faceplate. See the “10.6 TXP_MR_2.5G and TXPP_MR_2.5G Cards” section on page 10-25. MXP_2.5G_10G The MXP_2.5G_10G card has nine sets of ports located on the faceplate. See the “10.7 MXP_2.5G_10G Card” section on page 10-29. MXP_2.5G_10E The MXP_2.5G_10E card has nine sets of ports located on the faceplate. See the “10.7.4 MXP_2.5G_10E Card” section on page 10-33. MXP_2.5G_10E_C and MXP_2.5G_10E_L The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have nine sets of ports located on the faceplate. See the “10.8 MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards” section on page 10-40. MXP_MR_2.5G The MXP_MR_2.5G card has nine sets of ports located on the faceplate. See the “10.9 MXP_MR_2.5G and MXPP_MR_2.5G Cards” section on page 10-49. MXPP_MR_2.5G The MXPP_MR_2.5G card has ten sets of ports located on the faceplate. See the “10.9 MXP_MR_2.5G and MXPP_MR_2.5G Cards” section on page 10-49.10-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Card Overview MXP_MR_10DME_C and MXP_MR_10DME_L The MXP_MR_10DME_C and MXP_MR_10DME_L cards have eight sets of ports located on the faceplate. See the “10.10 MXP_MR_10DME_C and MXP_MR_10DME_L Cards” section on page 10-55. 40G-MXP-C The 40G-MXP-C card has five ports located on the faceplate. See the “10.11 40G-MXP-C Card” section on page 10-64. GE_XP and GE_XPE The GE_XP and GE_XPE cards have twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. See the “10.12 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards” section on page 10-71. 10GE_XP and 10GE_XPE The 10GE_XP and 10GE_XPE cards have two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. See the “10.12 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards” section on page 10-71. ADM-10G The ADM-10G card has 19 sets of ports located on the faceplate. See the “10.13 ADM-10G Card” section on page 10-96. OTU2_XP The OTU2_XP card has four ports located on the faceplate. See the “10.14 OTU2_XP Card” section on page 10-111. TXP_MR_10EX_C The TXP_MR_10EX_C card has two sets of ports located on the faceplate. See the “10.16 TXP_MR_10EX_C Card” section on page 10-121. MXP_2.5G_10EX_C The MXP_2.5G_10EX_C card has nine sets of ports located on the faceplate. See the “10.17 MXP_2.5G_10EX_C card” section on page 10-125. MXP_MR_10DMEX_C The MXP_MR_10DMEX_C card has eight sets of ports located on the faceplate. See the “10.18 MXP_MR_10DMEX_C Card” section on page 10-132. Table 10-1 Cisco ONS 15454 Transponder and Muxponder Cards (continued) Card Port Description For Additional Information10-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Card Overview 10.1.2 Card Compatibility Table 10-2 lists the platform and Cisco Transport Controller (CTC) software compatibility for each TXP, TXPP, MXP, MXPP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP card. Table 10-2 Platform and Software Release Compatibility for Transponder and Muxponder Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.2 TXP_MR_10G 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M TXP_MR_10E No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 TXP_MR_10E_C No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 TXP_MR_10E_L No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M TXP_MR_2.5G 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 TXPP_MR_2.5G 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_2.5G_10G 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M10-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Card Overview MXP_2.5G_10E No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_2.5G_10E_C No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_2.5G_10E_L No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M MXP_MR_2.5G No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXPP_MR_2.5G No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_MR_10DME_C No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_MR_10DME_L No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M Table 10-2 Platform and Software Release Compatibility for Transponder and Muxponder Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.210-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Card Overview GE_XP No No No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 10GE_XP No No No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 GE_XPE No No No No No No No No No 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 10GE_XPE No No No No No No No No No 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 ADM-10G No No No No No No No 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 OTU2_XP No No No No No No No No No 15454 -DW DM 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 Table 10-2 Platform and Software Release Compatibility for Transponder and Muxponder Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.210-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Safety Labels 10.2 Safety Labels This section explains the significance of the safety labels attached to some of the cards. The faceplates of the cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning labels before working on these cards. 10.2.1 Class 1 Laser Product Cards The MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, ADM-10G, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP cards have Class 1 lasers. The labels that appear on these cards are described in the following sections. 10.2.1.1 Class 1 Laser Product Label The Class 1 Laser Product label is shown in Figure 10-1. TXP_MR_10EX_C No No No No No No No No No No 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_2.5G_10EX_C No No No No No No No No No No 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 MXP_MR_10DMEX_ C No No No No No No No No No No 15454 -DW DM 15454 -DWD M, 15454 -M2, 15454 -M6 40G-MXP-C No No No No No No No No No No No 15454 -DWD M, 15454 -M2, 15454 -M6 Table 10-2 Platform and Software Release Compatibility for Transponder and Muxponder Cards Card Name R4.5 R4.6 R4.7 R5.0 R6.0 R7.0 R7.2 R8.0 R8.5 R9.0 R9.1 R9.210-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Safety Labels Figure 10-1 Class 1 Laser Product Label Class 1 lasers are products whose irradiance does not exceed the Maximum Permissible Exposure (MPE) value. Therefore, for Class 1 laser products the output power is below the level at which it is believed eye damage will occur. Exposure to the beam of a Class 1 laser will not result in eye injury and can therefore be considered safe. However, some Class 1 laser products might contain laser systems of a higher Class but there are adequate engineering control measures to ensure that access to the beam is not reasonably likely. Anyone who dismantles a Class 1 laser product that contains a higher Class laser system is potentially at risk of exposure to a hazardous laser beam 10.2.1.2 Hazard Level 1 Label The Hazard Level 1 label is shown in Figure 10-2. This label is displayed on the faceplate of the cards. Figure 10-2 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. 10.2.1.3 Laser Source Connector Label The Laser Source Connector label is shown in Figure 10-3. Figure 10-3 Laser Source Connector Label This label indicates that a laser source is present at the optical connector where the label has been placed. CLASS 1 LASER PRODUCT 145952 HAZARD LEVEL 1 65542 9663510-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Safety Labels 10.2.1.4 FDA Statement Label The FDA Statement labels are shown in Figure 10-4 and Figure 10-5. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 10-4 FDA Statement Label Figure 10-5 FDA Statement Label 10.2.1.5 Shock Hazard Label The Shock Hazard label is shown in Figure 10-6. Figure 10-6 Shock Hazard Label This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself. 10.2.2 Class 1M Laser Product Cards The TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, and 40G-MXP-C cards have Class 1M lasers. 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 2007 6554110-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Safety Labels The labels that appear on these cards are described in the following subsections. 10.2.2.1 Class 1M Laser Product Statement The Class 1M Laser Product statement is shown in Figure 10-7. Figure 10-7 Class 1M Laser Product Statement Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam. Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can be harmful to the eye if the beam is viewed using magnifying optical instruments. 10.2.2.2 Hazard Level 1M Label The Hazard Level 1M label is shown in Figure 10-8. This label is displayed on the faceplate of the cards. Figure 10-8 Hazard Level Label The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in accordance with IEC60825-1 Ed.1.2. 10.2.2.3 Laser Source Connector Label The Laser Source Connector label is shown in Figure 10-9. CAUTION HAZARD LEVEL 1M INVISIBLE LASER RADIATION DO NOT VIEW DIRECTLY WITH NON-ATTENUATING OPTICAL INSTRUMENTS λ = = 1400nm TO 1610nm 145953 HAZARD LEVEL 1M 14599010-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Safety Labels Figure 10-9 Laser Source Connector Label This label indicates that a laser source is present at the optical connector where the label has been placed. 10.2.2.4 FDA Statement Label The FDA Statement labels are shown in Figure 10-10 and Figure 10-11. These labels show compliance to FDA standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2. Figure 10-10 FDA Statement Label Figure 10-11 FDA Statement Label 10.2.2.5 Shock Hazard Label The Shock Hazard label is shown in Figure 10-12. 96635 96634 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JULY 26, 2001 282324 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE NO.50, DATED JUNE 24, 200710-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10G Card Figure 10-12 Shock Hazard Label This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself. 10.3 TXP_MR_10G Card (Cisco ONS 15454 only) The TXP_MR_10G processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). It provides one 10-Gbps port per card that can be provisioned for an STM-64/OC-192 short reach (1310-nm) signal, compliant with ITU-T G.707, ITU-T G.709, ITU-T G.691, and Telcordia GR-253-CORE, or a 10GBASE-LR signal compliant with IEEE 802.3. The TXP_MR_10G card is tunable over two neighboring wavelengths in the 1550-nm, ITU 100-GHz range. It is available in 16 different versions, each of which covers two wavelengths, for a total coverage of 32 different wavelengths in the 1550-nm range. Note ITU-T G.709 specifies a form of forward error correction (FEC) that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected. The trunk port operates at 9.95328 Gbps (or 10.70923 Gbps with ITU-T G.709 Digital Wrapper/FEC) and at 10.3125 Gbps (or 11.095 Gbps with ITU-T G.709 Digital Wrapper/FEC) over unamplified distances up to 80 km (50 miles) with different types of fiber such as C-SMF or dispersion compensated fiber limited by loss and/or dispersion. Caution Because the transponder has no capability to look into the payload and detect circuits, a TXP_MR_10G card does not display circuits under card view. Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10G card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10G card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10G card. 6554110-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10G Card You can install TXP_MR_10G cards in Slots 1 to 6 and 12 to 17 and provision this card in a linear configuration. TXP_MR_10G cards cannot be provisioned as a bidirectional line switched ring (BLSR)/Multiplex Section - Shared Protection Ring (MS-SPRing), a path protection/single node control point (SNCP), or a regenerator. They can only be used in the middle of BLSR/MS-SPRing and 1+1 spans when the card is configured for transparent termination mode. The TXP_MR_10G port features a 1550-nm laser for the trunk port and a 1310-nm laser for the for the client port and contains two transmit and receive connector pairs (labeled) on the card faceplate. The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting. Figure 10-13 shows the TXP_MR_10G faceplate and block diagram.10-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10G Card Figure 10-13 TXP_MR_10G Faceplate and Block Diagram For information on safety labels for the card, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. 10.3.1 Automatic Laser Shutdown The Automatic Laser Shutdown (ALS) procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds and is user-configurable. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. uP bus Serial bus uP Flash RAM Optical transceiver 145948 Framer/FEC/DWDM processor Client interface DWDM trunk (long range) Optical transceiver Client interface STM-64/OC-192 SR-1 optics modules or 10GBASE-LR B a c k p l a n e DWDM trunk STM-64/OC-192 10G MR TXP 1530.33 - 1531.12 FAIL ACT/STBY SF TX RX CLIENT 1530.33 1531.12 DWDM TX RX ! MAX INPUT POWER LEVEL - 8 dBm10-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E Card 10.3.2 TXP_MR_10G Card-Level Indicators Table 10-3 lists the three card-level LEDs on the TXP_MR_10G card. 10.3.3 TXP_MR_10G Port-Level Indicators Table 10-4 lists the four port-level LEDs in the TXP_MR_10G card. 10.4 TXP_MR_10E Card The TXP_MR_10E card is a multirate transponder for the ONS 15454 platform. The card is fully backward compatible with the TXP_MR_10G card. It processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side) that is tunable over four wavelength channels (spaced at 100 GHz on the ITU grid) in the C band and tunable over eight wavelength channels (spaced at 50 GHz on the ITU grid) in the L band. There are eight versions of the C-band card, with each version covering four wavelengths, for a total coverage of 32 wavelengths. There are five versions of the L-band card, with each version covering eight wavelengths, for a total coverage of 40 wavelengths. Table 10-3 TXP_MR_10G Card-Level Indicators Card-Level LED Description FAIL LED (Red) Red 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 Green (Active) Amber (Standby) Green indicates that the card is operational (one or both ports active) and ready to carry traffic. Amber indicates that the card is operational and in standby (protect) mode. SF LED (Amber) Amber indicates a signal failure or condition such as loss of signal (LOS), loss of frame (LOF), or high bit error rates (BERs) on one or more of the card’s ports. The amber SF LED is also illuminated if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the LED turns off. Table 10-4 TXP_MR_10G Port-Level Indicators Port-Level LED Description Green Client LED The green Client LED indicates that the client port is in service and that it is receiving a recognized signal. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal. Green Wavelength 1 LED Each port supports two wavelengths on the DWDM side. Each wavelength LED matches one of the wavelengths. This LED indicates that the card is configured for Wavelength 1. Green Wavelength 2 LED Each port supports two wavelengths on the DWDM side. Each wavelength LED matches one of the wavelengths. This LED indicates that the card is configured for Wavelength 2.10-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E Card You can install TXP_MR_10E cards in Slots 1 to 6 and 12 to 17 and provision the cards in a linear configuration, BLSR/MS-SPRing, path protection/SNCP, or a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode. The TXP_MR_10E card features a 1550-nm tunable laser (C band) or a 1580-nm tunable laser (L band) for the trunk port and a separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port. Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10E card must be installed in Slots 6, 7, 12 or 13) On its faceplate, the TXP_MR_10E card contains two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled. 10.4.1 Key Features The key features of the TXP_MR_10E card are: • A tri-rate client interface (available through the ONS-XC-10G-S1 XFP, ordered separately) – OC-192 (SR1) – 10GE (10GBASE-LR) – 10G-FC (1200-SM-LL-L) • OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping • The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting. 10.4.2 Faceplate and Block Diagram Figure 10-14 shows the TXP_MR_10E faceplate and block diagram.10-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E Card Figure 10-14 TXP_MR_10E Faceplate and Block Diagram For information on safety labels for the card, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10E card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10E card. 10.4.3 Client Interface The client interface is implemented with a separately orderable XFP module. The module is a tri-rate transceiver, providing a single port that can be configured in the field to support an OC-192 SR-1 (Telcordia GR-253-CORE) or STM-64 I-64.1 (ITU-T G.691) optical interface, as well as 10GE LAN PHY (10GBASE-LR), 10GE WAN PHY (10GBASE-LW), or 10G FC signals. The client side XFP pluggable module supports LC connectors and is equipped with a 1310-nm laser. 10.4.4 DWDM Trunk Interface On the trunk side, the TXP_MR_10E card provides a 10-Gbps STM-64/OC-192 interface. There are four tunable channels available in the 1550-nm band or eight tunable channels available in the 1580-nm band on the 50-GHz ITU grid for the DWDM interface. The TXP_MR_10E card provides 3R (retime, reshape, uP bus Serial bus uP Flash RAM Optical transceiver 131186 Framer/FEC/DWDM processor FAIL ACT/STBY SF 10 Gb/s TP 1538.19 1538.98 Client interface DWDM trunk (long range) Optical transceiver Client interface STM-64/OC-192 or 10GE (10GBASE-LR) or 10G-FC (1200-SM-LL-L) B a c k p l a n e TX RX RX TX DWDM trunk STM-64/OC-192 4 tunable channels (C-band) or 8 tunable channels (L-band) on the 100-GHz ITU grid10-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E Card and regenerate) transponder functionality for this 10-Gbps trunk interface. Therefore, the card is suited for use in long-range amplified systems. The DWDM interface is complaint with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The DWDM trunk port operates at a rate that is dependent on the input signal and the presence or absence of the ITU-T G.709 Digital Wrapper/FEC. The possible trunk rates are: • OC192 (9.95328 Gbps) • OTU2 (10.70923 Gbps) • 10GE (10.3125 Gbps) or 10GE into OTU2 (ITU G.sup43 11.0957 Gbps) • 10G FC (10.51875 Gbps) or 10G FC into OTU2 (nonstandard 11.31764 Gbps) The maximum system reach in filterless applications without the use of optical amplification or regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is given for informational purposes. It is subject to change. 10.4.5 Enhanced FEC (E-FEC) Feature A key feature of the TXP_MR_10E is the availability to configure the forward error correction in three modes: NO FEC, FEC, and E-FEC. The output bit rate is always 10.7092 Gbps as defined in ITU-T G.709, but the error coding performance can be provisioned as follows: • NO FEC—No forward error correction • FEC—Standard ITU-T G.975 Reed-Solomon algorithm • E-FEC—Standard ITU-T G.975.1 I.7 algorithm, which is a super FEC code Note The E-FEC of the ONS 15454 and Cisco ASR 9000 are not compatible. 10.4.6 FEC and E-FEC Modes As client side traffic passes through the TXP_MR_10E card, it can be digitally wrapped using FEC mode, E-FEC mode, or no error correction at all. The FEC mode setting provides a lower level of error detection and correction than the E-FEC mode setting of the card. As a result, using E-FEC mode allows higher sensitivity (lower optical signal-to-noise ratio [OSNR]) with a lower bit error rate than FEC mode. E-FEC enables longer distance trunk-side transmission than with FEC. The E-FEC feature is one of three basic modes of FEC operation. FEC can be turned off, FEC can be turned on, or E-FEC can be turned on to provide greater range and lower BER. The default mode is FEC on and E-FEC off. E-FEC is provisioned using CTC. Caution Because the transponder has no visibility into the data payload and detect circuits, the TXP_MR_10E card does not display circuits under the card view. 10.4.7 Client-to-Trunk Mapping The TXP_MR_10E card can perform ODU2-to-OCh mapping, which allows operators to provision data payloads in a standard way across 10-Gbps optical links. 10-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E Card Digital wrappers that define client side interfaces are called Optical Data Channel Unit 2 (ODU2) entities in ITU-T G.709. Digital wrappers that define trunk side interfaces are called Optical Channels (OCh) in ITU-T G.709. ODU2 digital wrappers can include Generalized Multiprotocol Label Switching (G-MPLS) signaling extensions to ITU-T G.709 (such as Least Significant Part [LSP] and Generalized Payload Identifier [G-PID] values) to define client interfaces and payload protocols. 10.4.8 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. 10.4.9 TXP_MR_10E Card-Level Indicators Table 10-5 lists the three card-level LEDs on the TXP_MR_10E card. 10.4.10 TXP_MR_10E Port-Level Indicators Table 10-6 lists the two port-level LEDs in the TXP_MR_10E card. Table 10-5 TXP_MR_10E 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or both ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-6 TXP_MR_10E Port-Level Indicators Port-Level LED Description Green Client LED The green Client LED indicates that the client port is in service and that it is receiving a recognized signal. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E_C and TXP_MR_10E_L Cards 10.5 TXP_MR_10E_C and TXP_MR_10E_L Cards TXP_MR_10E_L: (Cisco ONS 15454 only) The TXP_MR_10E_C and TXP_MR_10E_L cards are multirate transponders for the ONS 15454 platform. The cards are fully backward compatible with the TXP_MR_10G and TXP_MR_10E cards. They processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). The TXP_MR_10E_C is tunable over the entire set of C-band wavelength channels (82 channels spaced at 50 GHz on the ITU grid). The TXP_MR_10E_L is tunable over the entire set of L-band wavelength channels (80 channels spaced at 50 GHz on the ITU grid) and is particularly well suited for use in networks that employ DS fiber or SMF-28 single-mode fiber. The advantage of these cards over previous versions (TXP_MR_10G and TXP_MR_10E) is that there is only one version of each card (one C-band version and one L-band version) instead of several versions needed to cover each band. You can install TXP_MR_10E_C and TXP_MR_10E_L cards in Slots 1 to 6 and 12 to 17 and provision the cards in a linear configuration, BLSR/MS-SPRing, path protection/SNCP, or a regenerator. The cards can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the cards are configured for transparent termination mode. The TXP_MR_10E_C and TXP_MR_10E_L cards feature a universal transponder 2 (UT2) 1550-nm tunable laser (C band) or a UT2 1580-nm tunable laser (L band) for the trunk port and a separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port. Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10E_C or TXP_MR_10E-L card is required to be installed in a high-speed slot (slot 6, 7, 12, or 13) On its faceplate, the TXP_MR_10E_C and TXP_MR_10E_L cards contain two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled. 10.5.1 Key Features The key features of the TXP_MR_10E_C and TXP_MR_10E_L cards are: • A tri-rate client interface (available through the ONS-XC-10G-S1 XFP, ordered separately): – OC-192 (SR1) – 10GE (10GBASE-LR) – 10G-FC (1200-SM-LL-L) • A UT2 module tunable through the entire C band (TXP_MR_10E_C card) or L band (TXP_MR_10E_L card). The channels are spaced at 50 GHz on the ITU grid. • OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping. • The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.10-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E_C and TXP_MR_10E_L Cards 10.5.2 Faceplates and Block Diagram Figure 10-15 shows the TXP_MR_10E_C and TXP_MR_10E_L faceplates and block diagram. Figure 10-15 TXP_MR_10E_C and TXP_MR_10E_L Faceplates and Block Diagram For information on safety labels for the cards, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E_C or TXP_MR_10E_L card in a loopback on the trunk port. Do not use direct fiber loopbacks with the cards. Using direct fiber loopbacks causes irreparable damage to the cards. 10.5.3 Client Interface The client interface is implemented with a separately orderable XFP module. The module is a tri-rate transceiver, providing a single port that can be configured in the field to support an OC-192 SR-1 (Telcordia GR-253-CORE) or STM-64 I-64.1 (ITU-T G.691) optical interface, as well as 10GE LAN PHY (10GBASE-LR), 10GE WAN PHY (10GBASE-LW), or 10G-FC signals. The client side XFP pluggable module supports LC connectors and is equipped with a 1310-nm laser. uP bus Serial bus uP Flash RAM Optical transceiver 134975 Framer/FEC/DWDM processor Client interface DWDM trunk (long range) Optical transceiver Client interface STM-64/OC-192 or 10GE (10GBASE-LR) or 10G-FC (1200-SM-LL-L) B a c k p l a n e DWDM trunk STM-64/OC-192 82 tunable channels (C-band) or 80 tunable channels (L-band) on the 50-GHz ITU grid FAIL ACT/STBY SF 10E MR TXP L TX RX RX TX FAIL ACT/STBY SF 10E MR TXP C TX RX RX TX10-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E_C and TXP_MR_10E_L Cards 10.5.4 DWDM Trunk Interface On the trunk side, the TXP_MR_10E_C and TXP_MR_10E_L cards provide a 10-Gbps STM-64/OC-192 interface. There are 80 tunable channels available in the 1550-nm C band or 82 tunable channels available in the 1580-nm L band on the 50-GHz ITU grid for the DWDM interface. The TXP_MR_10E_C and TXP_MR_10E_C cards provide 3R transponder functionality for this 10-Gbps trunk interface. Therefore, the card is suited for use in long-range amplified systems. The DWDM interface is compliant with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The DWDM trunk port operates at a rate that is dependent on the input signal and the presence or absence of the ITU-T G.709 Digital Wrapper/FEC. The possible trunk rates are: • OC192 (9.95328 Gbps) • OTU2 (10.70923 Gbps) • 10GE (10.3125 Gbps) or 10GE into OTU2 (ITU G.sup43 11.0957 Gbps) • 10G-FC (10.51875 Gbps) or 10G-FC into OTU2 (nonstandard 11.31764 Gbps) The maximum system reach in filterless applications without the use of optical amplification or regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is given for informational purposes. It is subject to change. 10.5.5 Enhanced FEC (E-FEC) Feature A key feature of the TXP_MR_10E_C and TXP_MR_10E_L cards is the availability to configure the forward error correction in three modes: NO FEC, FEC, and E-FEC. The output bit rate is always 10.7092 Gbps as defined in ITU-T G.709, but the error coding performance can be provisioned as follows: • NO FEC—No forward error correction • FEC—Standard ITU-T G.975 Reed-Solomon algorithm • E-FEC—Standard ITU-T G.975.1 I.7 algorithm, which is a super FEC code 10.5.6 FEC and E-FEC Modes As client side traffic passes through the TXP_MR_10E_C and TXP_MR_10E_L cards, it can be digitally wrapped using FEC mode, E-FEC mode, or no error correction at all. The FEC mode setting provides a lower level of error detection and correction than the E-FEC mode setting of the card. As a result, using E-FEC mode allows higher sensitivity (lower OSNR) with a lower bit error rate than FEC mode. E-FEC enables longer distance trunk-side transmission than with FEC. The E-FEC feature is one of three basic modes of FEC operation. FEC can be turned off, FEC can be turned on, or E-FEC can be turned on to provide greater range and lower BER. The default mode is FEC on and E-FEC off. E-FEC is provisioned using CTC. Caution Because the transponder has no visibility into the data payload and detect circuits, the TXP_MR_10E_C and TXP_MR_10E_L cards do not display circuits under the card view. 10-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10E_C and TXP_MR_10E_L Cards 10.5.7 Client-to-Trunk Mapping The TXP_MR_10E_C and TXP_MR_10E_L cards can perform ODU2-to-OCh mapping, which allows operators to provision data payloads in a standard way across 10-Gbps optical links. Digital wrappers that define client side interfaces are called ODU2 entities in ITU-T G.709. Digital wrappers that define trunk side interfaces are called OCh in ITU-T G.709. ODU2 digital wrappers can include G-MPLS signaling extensions to ITU-T G.709 (such as LSP and G-PID values) to define client interfaces and payload protocols. 10.5.8 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details regarding ALS provisioning for the TXP_MR_10E_C and TXP_MR_10E_L cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. 10.5.9 TXP_MR_10E_C and TXP_MR_10E_L Card-Level Indicators Table 10-7 lists the three card-level LEDs on the TXP_MR_10E_C and TXP_MR_10E_L cards. 10.5.10 TXP_MR_10E_C and TXP_MR_10E_L Port-Level Indicators Table 10-8 lists the two port-level LEDs in the TXP_MR_10E_C and TXP_MR_10E_L cards. Table 10-7 TXP_MR_10E _C and TXP_MR_10E_L 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or both ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-8 TXP_MR_10E_C and TXP_MR_10E_L Port-Level Indicators Port-Level LED Description Green Client LED The green Client LED indicates that the client port is in service and that it is receiving a recognized signal. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_2.5G and TXPP_MR_2.5G Cards 10.6 TXP_MR_2.5G and TXPP_MR_2.5G Cards The TXP_MR_2.5G card processes one 8-Mbps to 2.488-Gbps signal (client side) into one 8-Mbps to 2.5-Gbps, 100-GHz DWDM signal (trunk side). It provides one long-reach STM-16/OC-48 port per card, compliant with ITU-T G.707, ITU-T G.709, ITU-T G.957, and Telcordia GR-253-CORE. The TXPP_MR_2.5G card processes one 8-Mbps to 2.488-Gbps signal (client side) into two 8-Mbps to 2.5-Gbps, 100-GHz DWDM signals (trunk side). It provides two long-reach STM-16/OC-48 ports per card, compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE. The TXP_MR_2.5G and TXPP_MR_2.5G cards are tunable over four wavelengths in the 1550-nm, ITU 100-GHz range. They are available in eight versions, each of which covers four wavelengths, for a total coverage of 32 different wavelengths in the 1550-nm range. Note ITU-T G.709 specifies a form of FEC that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it, and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected. The trunk/line port operates at up to 2.488 Gbps (or up to 2.66 Gbps with ITU-T G.709 Digital Wrapper/FEC) over unamplified distances up to 360 km (223.7 miles) with different types of fiber such as C-SMF or higher if dispersion compensation is used. Caution Because the transponder has no capability to look into the payload and detect circuits, a TXP_MR_2.5G or TXPP_MR_2.5G card does not display circuits under card view. The TXP_MR_2.5G and TXPP_MR_2.5G cards support 2R (retime, regenerate) and 3R (retime, reshape, and regenerate) modes of operation where the client signal is mapped into a ITU-T G.709 frame. The mapping function is simply done by placing a digital wrapper around the client signal. Only OC-48/STM-16 client signals are fully ITU-T G.709 compliant, and the output bit rate depends on the input client signal. Table 10-9 shows the possible combinations of client interfaces, input bit rates, 2R and 3R modes, and ITU-T G.709 monitoring. Table 10-9 2R and 3R Mode and ITU-T G.709 Compliance by Client Interface Client Interface Input Bit Rate 3R vs. 2R ITU-T G.709 OC-48/STM-16 2.488 Gbps 3R On or Off DV-6000 2.38 Gbps 2R — 2 Gigabit Fibre Channel (2G-FC)/fiber connectivity (FICON) 2.125 Gbps 3R1 On or Off High-Definition Television (HDTV) 1.48 Gbps 2R — Gigabit Ethernet (GE) 1.25 Gbps 3R On or Off 1 Gigabit Fibre Channel (1G-FC)/FICON 1.06 Gbps 3R On or Off OC-12/STM-4 622 Mbps 3R On or Off OC-3/STM-1 155 Mbps 3R On or Off Enterprise System Connection (ESCON) 200 Mbps 2R — SDI/D1/DVB-ASI video 270 Mbps 2R —10-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_2.5G and TXPP_MR_2.5G Cards Note ITU-T G.709 and FEC support is disabled for all the 2R payload types in the TXP_MR_2.5G and TXPP_MR_2.5G cards. The output bit rate is calculated for the trunk bit rate by using the 255/238 ratio as specified in ITU-T G.709 for OTU1. Table 10-10 lists the calculated trunk bit rates for the client interfaces with ITU-T G.709 enabled. For 2R operation mode, the TXP_MR_2.5G and TXPP_MR_2.5G cards have the ability to pass data through transparently from client side interfaces to a trunk side interface, which resides on an ITU grid. The data might vary at any bit rate from 200-Mbps up to 2.38-Gbps, including ESCON, DVB-ASI, ISC-1, and video signals. In this pass-through mode, no performance monitoring (PM) or digital wrapping of the incoming signal is provided, except for the usual PM outputs from the SFPs. Similarly, this card has the ability to pass data through transparently from the trunk side interfaces to the client side interfaces with bit rates varying from 200-Mbps up to 2.38-Gbps. Again, no PM or digital wrapping of received signals is available in this pass-through mode. For 3R operation mode, the TXP_MR_2.5G and TXPP_MR_2.5G cards apply a digital wrapper to the incoming client interface signals (OC-N/STM-N, 1G-FC, 2G-FC, GE). PM is available on all of these signals except for 2G-FC, and varies depending upon the type of signal. For client inputs other than OC-48/STM-16, a digital wrapper might be applied but the resulting signal is not ITU-T G.709 compliant. The card applies a digital wrapper that is scaled to the frequency of the input signal. The TXP_MR_2.5G and TXPP_MR_2.5G cards have the ability to take digitally wrapped signals in from the trunk interface, remove the digital wrapper, and send the unwrapped data through to the client interface. PM of the ITU-T G.709 OH and SONET/SDH OH is implemented. ISC-1 Compat 1.06 Gbps 2R Off ISC-3 1.06 or 2.125 Gbps 2R — ETR_CLO 16 Mbps 2R — 1. No monitoring Table 10-9 2R and 3R Mode and ITU-T G.709 Compliance by Client Interface (continued) Client Interface Input Bit Rate 3R vs. 2R ITU-T G.709 Table 10-10 Trunk Bit Rates With ITU-T G.709 Enabled Client Interface ITU-T G.709 Disabled ITU-T G.709 Enabled OC-48/STM-16 2.488 Gbps 2.66 Gbps 2G-FC 2.125 Gbps 2.27 Gbps GE 1.25 Gbps 1.34 Gbps 1G-FC 1.06 Gbps 1.14 Gbps OC-12/STM-3 622 Mbps 666.43 Mbps OC-3/STM-1 155 Mbps 166.07 Mbps10-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_2.5G and TXPP_MR_2.5G Cards 10.6.1 Faceplate Figure 10-16 shows the TXP_MR_2.5G and TXPP_MR_2.5G faceplates. Figure 10-16 TXP_MR_2.5G and TXPP_MR_2.5G Faceplates For information on safety labels for the cards, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. 10.6.2 Block Diagram Figure 10-17 shows a block diagram of the TXP_MR_2.5G and TXPP_MR_2.5G cards. CLIENT 2.5G MR TXP-P 1530.33 - 1532.68 2.5G MR TXP 1530.33 - 1532.68 FAIL ACT/STBY SF HAZARD LEVEL 1M TX RX DWDM A RX TX DWDM B RX TX ! MAX INPUT POWER LEVEL - 8 dBm CLIENT ! MAX INPUT POWER LEVEL - 8 dBm FAIL ACT/STBY SF HAZARD LEVEL 1M TX RX RX TX DWDM 14594610-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_2.5G and TXPP_MR_2.5G Cards Figure 10-17 TXP_MR_2.5G and TXPP_MR_2.5G Block Diagram Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the TXP_MR_2.5G and TXPP_MR_2.5G cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_2.5G and TXPP_MR_2.5G cards. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_2.5G and TXPP_MR_2.5G cards. You can install TXP_MR_2.5G and TXPP_MR_2.5G cards in Slots 1 to 6 and 12 to 17. You can provision this card in a linear configuration. TXP_MR_10G and TXPP_MR_2.5G cards cannot be provisioned as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. They can be used in the middle of BLSR/MS-SPRing or 1+1 spans only when the card is configured for transparent termination mode. The TXP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm laser for the client port. It contains two transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors for optical cable termination. The TXPP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser (depending on the SFP) for the client port and contains three transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors for optical cable termination. 10.6.3 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details regarding ALS provisioning for the TXP_MR_2.5G and TXPP_MR_2.5G cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. SFP Client Switch Switch Driver Tunable Laser Switch Cross Switch Limiting Amp Limiting Amp Main APD+TA Protect APD+TA Mux Demux Mux Demux Mux Demux CPU Main ASIC Protect FPGA ASIC SCL FPGA SCL BUS 2R Tx path Trunk Out 2R Rx path CELL BUS CPU I/F CELL BUS DCC CPU to GCC 9663610-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card 10.6.4 TXP_MR_2.5G and TXPP_MR_2.5G Card-Level Indicators Table 10-11 lists the three card-level LEDs on the TXP_MR_2.5G and TXPP_MR_2.5G cards. 10.6.5 TXP_MR_2.5G and TXPP_MR_2.5G Port-Level Indicators Table 10-12 lists the four port-level LEDs on the TXP_MR_2.5G and TXPP_MR_2.5G cards. 10.7 MXP_2.5G_10G Card (Cisco ONS 15454 only) The MXP_2.5G_10G card multiplexes/demultiplexes four 2.5-Gbps signals (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). It provides one extended long-range STM-64/OC-192 port per card on the trunk side (compliant with ITU-T G.707, ITU-T G.709, ITU-T G.957, and Telcordia GR-253-CORE) and four intermediate- or short-range OC-48/STM-16 ports per card on the client side. The port operates at 9.95328 Gbps over unamplified distances up to 80 km (50 miles) with different types of fiber such as C-SMF or dispersion compensated fiber limited by loss and/or dispersion. Table 10-11 TXP_MR_2.5G and TXPP_MR_2.5G 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or both ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-12 TXP_MR_2.5G and TXPP_MR_2.5G Port-Level Indicators Port-Level LED Description Green Client LED The green Client LED indicates that the client port is in service and that it is receiving a recognized signal. Green DWDM LED (TXP_MR_2.5G only) The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal. Green DWDM A LED (TXPP_MR_2.5G only) The green DWDM A LED indicates that the DWDM A port is in service and that it is receiving a recognized signal. Green DWDM B LED (TXPP_MR_2.5G only) The green DWDM B LED indicates that the DWDM B port is in service and that it is receiving a recognized signal.10-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card Client ports on the MXP_2.5G_10G card are also interoperable with SONET OC-1 (STS-1) fiber optic signals defined in Telcordia GR-253-CORE. An OC-1 signal is the equivalent of one DS-3 channel transmitted across optical fiber. OC-1 is primarily used for trunk interfaces to phone switches in the United States. There is no SDH equivalent for SONET OC-1. The MXP_2.5G_10G card is tunable over two neighboring wavelengths in the 1550-nm, ITU 100-GHz range. It is available in 16 different versions, each of which covers two wavelengths, for a total coverage of 32 different wavelengths in the 1550-nm range. Note ITU-T G.709 specifies a form of FEC that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected. The port can also operate at 10.70923 Gbps in ITU-T G.709 Digital Wrapper/FEC mode. Caution Because the transponder has no capability to look into the payload and detect circuits, an MXP_2.5G_10G card does not display circuits under card view. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10G card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10G card. Using direct fiber loopbacks causes irreparable damage to the MXP_2.5G_10G card. You can install MXP_2.5G_10G cards in Slots 1 to 6 and 12 to 17. Caution Do not install an MXP_2.5G_10G card in Slot 3 if you have installed a DS3/EC1-48 card in Slots 1or 2. Likewise, do not install an MXP_2.5G_10G card in Slot 17 if you have installed a DS3/EC1-48 card in Slots 15 or 16. If you do, the cards will interact and cause DS-3 bit errors. You can provision this card in a linear configuration. MXP_2.5G_10G cards cannot be provisioned as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. They can be used in the middle of BLSR/MS-SPRing or 1+1 spans only when the card is configured for transparent termination mode. The MXP_2.5G_10G port features a 1550-nm laser on the trunk port and four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses a dual LC connector on the trunk side and SFP connectors on the client side for optical cable termination. Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit. Figure 10-18 shows the MXP_2.5G_10G faceplate.10-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card Figure 10-18 MXP_2.5G_10G Faceplate For information on safety labels for the card, see the “10.2.1 Class 1 Laser Product Cards” section on page 10-8. Figure 10-19 shows a block diagram of the MXP_2.5G_10G card. CLIENT DWDM 1 2 4x 2.5G 10G MXP 1530.33 - 1531.12 FAIL ACT/STBY SF TX RX TX RX 3 TX RX 4 TX RX ! MAX INPUT POWER LEVEL - 8 dBm TX RX 1530.33 1531.12 14594510-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card Figure 10-19 MXP_2.5G_10G Card Block Diagram 10.7.1 Timing Synchronization The MXP_2.5G_10G card is synchronized to the TCC2/TCC2P/TCC3 clock during normal conditions and transmits the ITU-T G.709 frame using this clock. The TCC2/TCC2P/TCC3 card can operate from an external building integrated timing supply (BITS) clock, an internal Stratum 3 clock, or from clock recovered from one of the four valid client clocks. If clocks from both TCC2/TCC2P/TCC3 cards are not available, the MXP_2.5G_10G card switches automatically (with errors, not hitless) to an internal 19.44 MHz clock that does not meet SONET clock requirements. This will result in a clock alarm. 10.7.2 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details regarding ALS provisioning for the MXP_2.5G_10G card, refer to the Cisco ONS 15454 DWDM Procedure Guide. 10.7.3 MXP_2.5G_10G Card-Level Indicators Table 10-13 describes the three card-level LEDs on the MXP_2.5G_10G card. uP bus uP Flash RAM ASIC Optical Transceiver STM-64 / OC-192 9.953, 10.3125, 10.709, or 11.095 Gbps SCI 83659 B a c k p l a n e Optical Transceiver STM-64 / OC-192 9.95328 or 10.70923 Gbps Framer/FEC/DWDM Processor DWDM (Trunk) Client10-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card 10.7.3.1 MXP_2.5G_10G Port-Level Indicators Table 10-14 describes the four port-level LEDs on the MXP_2.5G_10G card. 10.7.4 MXP_2.5G_10E Card The faceplate designation of the card is “4x2.5G 10E MXP.” The MXP_2.5G_10E card is a DWDM muxponder for the ONS 15454 platform that supports full transparent termination the client side. The card multiplexes four 2.5 Gbps client signals (4 x OC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The MXP_2.5G_10E provides wavelength transmission service for the four incoming 2.5 Gbps client interfaces. The MXP_2.5G_10E muxponder passes all SONET/SDH overhead bytes transparently. The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up generic communications channels (GCCs) for data communications, enable FEC, or facilitate performance monitoring. Table 10-13 MXP_2.5G_10G 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-14 MXP_2.5G_10G Port-Level Indicators Port-Level LED Description Green Client LED (four LEDs) The green Client LED indicates that the client port is in service and that it is receiving a recognized signal. The card has four client ports, and so has four Client LEDs. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal. Green Wavelength 1 LED Each port supports two wavelengths on the DWDM side. Each wavelength LED matches one of the wavelengths. This LED indicates that the card is configured for Wavelength 1. Green Wavelength 2 LED Each port supports two wavelengths on the DWDM side. Each wavelength LED matches one of the wavelengths. This LED indicates that the card is configured for Wavelength 2.10-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card The MXP_2.5G_10E works with optical transport network (OTN) devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “10.7.7 Multiplexing Function” section on page 10-36. The MXP_2.5G_10E card is not compatible with the MXP_2.5G_10G card, which does not support full transparent termination. You can install MXP_2.5G_10E cards in Slots 1 to 6 and 12 to 17. You can provision this card in a linear configuration, as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode. The MXP_2.5G_10E features a 1550-nm laser on the trunk port and four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses a dual LC connector on the trunk side and uses SFP modules on the client side for optical cable termination. The SFP pluggable modules are short reach (SR) or intermediate reach (IR) and support an LC fiber connector. Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit. 10.7.4.1 Key Features The MXP_2.5G_10E card has the following high level features: • Four 2.5 Gbps client interfaces (OC-48/STM-16) and one 10 Gbps trunk. The four OC-48 signals are mapped into a ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing. • Onboard E-FEC processor: The processor supports both standard Reed-Solomon (RS, specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. A new block code (BCH) algorithm implemented in E-FEC allows recovery of an input BER up to 1E-3. • Pluggable client interface optic modules: The MXP_2.5G_10E card has modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957). • High level provisioning support: The MXP_2.5G_10E card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software. • Link monitoring and management: The MXP_2.5G_10E card uses standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its overhead bytes transparently. • Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network.10-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card • Automatic timing source synchronization: The MXP_2.5G_10E normally synchronizes from the TCC2/TCC2P/TCC3/TNC/TSC card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TSC is not available, the MXP_2.5G_10E automatically synchronizes to one of the input client interface clocks. • Configurable squelching policy: The card can be configured to squelch the client interface output if there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the card manages multiplex section alarm indication signal (MS-AIS) insertion. 10.7.5 Faceplate Figure 10-20 shows the MXP_2.5G_10E faceplate. Figure 10-20 MXP_2.5G_10E Faceplate For information on safety labels for the card, see the “10.2.1 Class 1 Laser Product Cards” section on page 10-8. Figure 10-21 shows a block diagram of the MXP_2.5G_10E card. 145937 FAIL ACT/STBY SF 4x2.5 10 E MxP 530.33- 1550.12 RX TX TX RX TX RX TX RX TX RX Client LEDs DWDM LED10-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card Figure 10-21 MXP_2.5G_10E Block Diagram 10.7.6 Client Interfaces The MXP_2.5G_10E provides four intermediate- or short-range OC-48/STM-16 ports per card on the client side. Both SR-1 or IR-1 optics can be supported and the ports use SFP connectors. The client interfaces use four wavelengths in the 1310-nm, ITU 100-MHz-spaced, channel grid. 10.7.6.1 DWDM Interface The MXP_2.5G_10E serves as an OTN multiplexer, transparently mapping four OC-48 channels asynchronously to ODU1 into one 10-Gbps trunk. The DWDM trunk is tunable for transmission over four wavelengths in the 1550-nm, ITU 100-GHz spaced channel grid. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10E card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10E card. Using direct fiber loopbacks causes irreparable damage to the MXP_2.5G_10E card. 10.7.7 Multiplexing Function The muxponder is an integral part of the reconfigurable optical add/drop multiplexer (ROADM) network. The key function of MXP_2.5G_10E is to multiplex 4 OC-48/STM16 signals onto one ITU-T G.709 OTU2 optical signal (DWDM transmission). The multiplexing mechanism allows the signal to be terminated at a far-end node by another MXP_2.5G_10E card. Termination mode transparency on the muxponder is configured using OTUx and ODUx OH bytes. The ITU-T G.709 specification defines OH byte formats that are used to configure, set, and monitor frame alignment, FEC mode, section monitoring, tandem connection monitoring, and termination mode transparency. uP bus Serial bus Processor Onboard Flash memory RAM Optical transceiver 115357 FEC/ Wrapper Processor (G.709 FEC) E-FEC DWDM (trunk) 10GE (10GBASE-LR) SR-1 (short reach/intra-office) or IR-1 (intermediate range) SFP client optics modules Optical transceiver Optical transceiver Optical transceiver Optical transceiver B a c k p l a n e10-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card The MXP_2.5G_10E card performs ODU to OTU multiplexing as defined in ITU-T G.709. The ODU is the framing structure and byte definition (ITU-T G.709 digital wrapper) used to define the data payload coming into one of the SONET/SDH client interfaces on MXP_2.5G_10E. The term ODU1 refers to an ODU that operates at 2.5-Gbps line rate. On the MXP_2.5G_10E, there are four client interfaces that can be defined using ODU1 framing structure and format by asserting a ITU-T G.709 digital wrapper. The output of the muxponder is a single 10-Gbps DWDM trunk interface defined using OTU2. It is within the OTU2 framing structure that FEC or E-FEC information is appended to enable error checking and correction. 10.7.8 Timing Synchronization The MXP_2.5G_10E card is synchronized to the TCC2/TCC2P/TCC3/TNC/TSC clock during normal conditions and transmits the ITU-T G.709 frame using this clock. No holdover function is implemented. If neither TCC2/TCC2P/TCC3/TNC/TSC clock is available, the MXP_2.5G_10E switches automatically (hitless) to the first of the four valid client clocks with no time restriction as to how long it can run on this clock. The MXP_2.5G_10E continues to monitor the TCC2/TCC2P/TCC3/TNC/TSC card. If a TCC2/TCC2P/TCC3/TNC/TSC card is restored to working order, the MXP_2.5G_10E reverts to the normal working mode of running from the TCC2/TCC2P/TCC3/TNC/TSC clock. If there is no valid TCC2/TCC2P/TCC3/TNC/TSC clock and all of the client channels become invalid, the card waits (no valid frames processed) until one of the TCC2/TCC2P/TCC3/TNC/TSC cards supplies a valid clock. In addition, the card is allowed to select the recovered clock from one active and valid client channel and supply that clock to the TCC2/TCC2P/TCC3/TNC/TSC card. 10.7.9 Enhanced FEC (E-FEC) Capability The MXP_2.5G_10E can configure the FEC in three modes: NO FEC, FEC, and E-FEC. The output bit rate is always 10.7092 Gbps as defined in ITU-T G.709, but the error coding performance can be provisioned as follows: • NO FEC—No FEC • FEC—Standard ITU-T G.975 Reed-Solomon algorithm • E-FEC—Standard ITU-T G.975.1 I.7, two orthogonally concatenated BCH super FEC code. This FEC scheme contains three parameterizations of the same scheme of two orthogonally interleaved BCH. The constructed code is decoded iteratively to achieve the expected performance. 10.7.10 FEC and E-FEC Modes As client side traffic passes through the MXP_2.5G_10E card, it can be digitally wrapped using FEC mode error correction or E-FEC mode error correction (or no error correction at all). The FEC mode setting provides a lower level of error detection and correction than the E-FEC mode setting of the card. As a result, using E-FEC mode allows higher sensitivity (lower OSNR) with a lower BER than FEC mode. E-FEC enables longer distance trunk-side transmission than with FEC. The E-FEC feature is one of three basic modes of FEC operation. FEC can be turned off, FEC can be turned on, or E-FEC can be turned on to provide greater range and lower BER. The default mode is FEC on and E-FEC off. E-FEC is provisioned using CTC.10-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card 10.7.11 SONET/SDH Overhead Byte Processing The card passes the incoming SONET/SDH data stream and its overhead bytes for the client signal transparently. The card can be provisioned to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. 10.7.12 Client Interface Monitoring The following parameters are monitored on the MXP_2.5G_10E card: • Laser bias current is measured as a PM parameter • LOS is detected and signaled • Transmit (TX) and receive (RX) power are monitored The following parameters are monitored in real time mode (one second): • Optical power transmitted (client) • Optical power received (client) In case of loss of communication (LOC) at the DWDM receiver or far-end LOS, the client interface behavior is configurable. AIS can be invoked or the client signal can be squelched. 10.7.13 Wavelength Identification The card uses trunk lasers that are wave-locked, which allows the trunk transmitter to operate on the ITU grid effectively. Table 10-15 describes the required trunk transmit laser wavelengths. The laser is tunable over eight wavelengths at 50-GHz spacing or four at 100-GHz spacing. Table 10-15 MXP_2.5G_10E Trunk Wavelengths Band Wavelength (nm) 30.3 1530.33 30.3 1531.12 30.3 1531.90 30.3 1532.68 34.2 1534.25 34.2 1535.04 34.2 1535.82 34.2 1536.61 38.1 1538.19 38.1 1538.98 38.1 1539.77 38.1 1540.56 42.1 1542.14 42.1 1542.9410-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10G Card 10.7.14 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details regarding ALS provisioning for the MXP_2.5G_10E card, refer to the Cisco ONS 15454 DWDM Procedure Guide. 10.7.15 Jitter For SONET and SDH signals, the MXP_2.5G_10E card complies with Telcordia GR-253-CORE, ITU-T G.825, and ITU-T G.873 for jitter generation, jitter tolerance, and jitter transfer. See the “10.21 Jitter Considerations” section on page 10-142 for more information. 10.7.16 Lamp Test The MXP_2.5G_10E card supports a lamp test function that is activated from the ONS 15454 front panel or through CTC to ensure that all LEDs are functional. 42.1 1543.73 42.1 1544.53 46.1 1546.12 46.1 1546.92 46.1 1547.72 46.1 1548.51 50.1 1550.12 50.1 1550.92 50.1 1551.72 50.1 1552.52 54.1 1554.13 54.1 1554.94 54.1 1555.75 54.1 1556.55 58.1 1558.17 58.1 1558.98 58.1 1559.79 58.1 1560.61 Table 10-15 MXP_2.5G_10E Trunk Wavelengths (continued) Band Wavelength (nm)10-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards 10.7.17 Onboard Traffic Generation The MXP_2.5G_10E card provides internal traffic generation for testing purposes according to pseudo-random bit sequence (PRBS), SONET/SDH, or ITU-T G.709. 10.7.18 MXP_2.5G_10E Card-Level Indicators Table 10-16 describes the three card-level LEDs on the MXP_2.5G_10E card. 10.7.19 MXP_2.5G_10E Port-Level Indicators Table 10-17 describes the port-level LEDs on the MXP_2.5G_10E card. 10.8 MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards MXP_2.5G_10E_L: (Cisco ONS 15454 only) The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are DWDM muxponders for the ONS 15454 platform that support transparent termination mode on the client side. The faceplate designation of the cards is “4x2.5G 10E MXP C” for the MXP_2.5G_10E_C card and “4x2.5G 10E MXP L” for the MXP_2.5G_10E_L card. The cards multiplex four 2.5-Gbps client signals (4 x OC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The MXP_2.5G_10E_C and Table 10-16 MXP_2.5G_10E 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-17 MXP_2.5G_10E Port-Level Indicators Port-Level LED Description Green Client LED (four LEDs) A green Client LED indicates that the client port is in service and that it is receiving a recognized signal. The card has four client ports, and so has four Client LEDs. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards MXP_2.5G_10E_L cards provide wavelength transmission service for the four incoming 2.5 Gbps client interfaces. The MXP_2.5G_10E_C and MXP_2.5G_10E_L muxponders pass all SONET/SDH overhead bytes transparently. The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards work with OTN devices defined in ITU-T G.709. The cards support ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “10.8.5 Multiplexing Function” section on page 10-44. The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode. You can install MXP_2.5G_10E_C and MXP_2.5G_10E_L cards in Slots 1 to 6 and 12 to 17. You can provision a card in a linear configuration, as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The cards can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the cards are configured for transparent termination mode. The MXP_2.5G_10E_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The MXP_2.5G_10E_L features a tunable 1580-nm L-band laser on the trunk port. The laser is tunable across 80 wavelengths on the ITU grid, also with 50-GHz spacing. Each card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The cards uses dual LC connectors on the trunk side and use SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector. Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit. 10.8.1 Key Features The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have the following high level features: • Four 2.5 Gbps client interfaces (OC-48/STM-16) and one 10 Gbps trunk. The four OC-48 signals are mapped into a ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing. • Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. A new BCH algorithm implemented in E-FEC allows recovery of an input BER up to 1E-3. • Pluggable client interface optic modules: The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957). • High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.10-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards • Link monitoring and management: The cards use standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The cards pass the incoming SDH/SONET data stream and its overhead bytes transparently. • Control of layered SONET/SDH transport overhead: The cards are provisionable to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. • Automatic timing source synchronization: The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards normally synchronize from the TCC2/TCC2P/TCC3 card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3 is not available, the cards automatically synchronize to one of the input client interface clocks. • Configurable squelching policy: The cards can be configured to squelch the client interface output if there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion. • The cards are tunable across the full C band (MXP_2.5G_10E_C) or full L band (MXP_2.5G_10E_L), thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band. 10.8.2 Faceplate Figure 10-22 shows the MXP_2.5G_10E_C and MXP_2.5G_10E_L faceplates and block diagram. 10-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards Figure 10-22 MXP_2.5G_10E _C and MXP_2.5G_10E_L Faceplates and Block Diagram For information on safety labels for the cards, see the “10.2.1 Class 1 Laser Product Cards” section on page 10-8. 10.8.3 Client Interfaces The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards provide four intermediate- or short-range OC-48/STM-16 ports per card on the client side. Both SR-1 and IR-1 optics can be supported and the ports use SFP connectors. The client interfaces use four wavelengths in the 1310-nm, ITU 100-GHz-spaced, channel grid. 10.8.4 DWDM Interface The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards serve as OTN multiplexers, transparently mapping four OC-48 channels asynchronously to ODU1 into one 10-Gbps trunk. For the MXP_2.5G_10E_C card, the DWDM trunk is tunable for transmission over the entire C band and for the MXP_2.5G_10E_L card, the DWDM trunk is tunable for transmission over the entire L band. Channels are spaced at 50-GHz on the ITU grid. FAIL ACT/STBY SF 4x2.5 10 E MXP C RX TX TX RX TX RX TX RX TX RX FAIL ACT/STBY SF 4x2.5 10 E MXP L RX TX TX RX TX RX TX RX TX RX RAM Processor 145941 Optical transceiver Optical transceiver Optical transceiver Optical transceiver Optical transceiver B a c k p l a n e FEC/ Wrapper E-FEC Processor (G.709 FEC) Serial bus uP bus Onboard Flash memory Client LEDs DWDM LED SR-1 (short reach/intra-office) or IR-1 (intermediate range) SFP client optics modules DWDM (trunk) 10GE (10GBASE-LR)10-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the cards. Using direct fiber loopbacks causes irreparable damage to the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards. 10.8.5 Multiplexing Function The muxponder is an integral part of the ROADM network. The key function of the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards is to multiplex four OC-48/STM16 signals onto one ITU-T G.709 OTU2 optical signal (DWDM transmission). The multiplexing mechanism allows the signal to be terminated at a far-end node by another similar card. Transparent termination on the muxponder is configured using OTUx and ODUx OH bytes. The ITU-T G.709 specification defines OH byte formats that are used to configure, set, and monitor frame alignment, FEC mode, section monitoring, tandem connection monitoring, and transparent termination mode. The MXP_2.5G_10E and MXP_2.5G_10E_L cards perform ODU to OTU multiplexing as defined in ITU-T G.709. The ODU is the framing structure and byte definition (ITU-T G.709 digital wrapper) used to define the data payload coming into one of the SONET/SDH client interfaces on the cards. The term ODU1 refers to an ODU that operates at 2.5-Gbps line rate. On the cards, there are four client interfaces that can be defined using ODU1 framing structure and format by asserting a ITU-T G.709 digital wrapper. The output of the muxponder is a single 10-Gbps DWDM trunk interface defined using OTU2. It is within the OTU2 framing structure that FEC or E-FEC information is appended to enable error checking and correction. 10.8.6 Timing Synchronization The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are synchronized to the TCC2/TCC2P/TCC3 clock during normal conditions and transmit the ITU-T G.709 frame using this clock. No holdover function is implemented. If neither TCC2/TCC2P/TCC3 clock is available, the card switches automatically (hitless) to the first of the four valid client clocks with no time restriction as to how long it can run on this clock. The card continues to monitor the TCC2/TCC2P/TCC3 card. If a TCC2/TCC2P/TCC3 card is restored to working order, the card reverts to the normal working mode of running from the TCC2/TCC2P/TCC3 clock. If there is no valid TCC2/TCC2P/TCC3 clock and all of the client channels become invalid, the card waits (no valid frames processed) until one of the TCC2/TCC2P/TCC3 cards supplies a valid clock. In addition, the card is allowed to select the recovered clock from one active and valid client channel and supply that clock to the TCC2/TCC2P/TCC3 card. 10.8.7 Enhanced FEC (E-FEC) Capability The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards can configure the FEC in three modes: NO FEC, FEC, and E-FEC. The output bit rate is always 10.7092 Gbps as defined in ITU-T G.709, but the error coding performance can be provisioned as follows: • NO FEC—No FEC • FEC—Standard ITU-T G.975 Reed-Solomon algorithm10-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards • E-FEC—Standard ITU-T G.975.1 I.7, two orthogonally concatenated BCH super FEC code. This FEC scheme contains three parameterizations of the same scheme of two orthogonally interleaved block codes (BCH). The constructed code is decoded iteratively to achieve the expected performance. 10.8.8 FEC and E-FEC Modes As client side traffic passes through the card, it can be digitally wrapped using FEC mode error correction or E-FEC mode error correction (or no error correction at all). The FEC mode setting provides a lower level of error detection and correction than the E-FEC mode setting of the card. As a result, using E-FEC mode allows higher sensitivity (lower OSNR) with a lower BER than FEC mode. E-FEC enables longer distance trunk-side transmission than with FEC. The E-FEC feature is one of three basic modes of FEC operation. FEC can be turned off, FEC can be turned on, or E-FEC can be turned on to provide greater range and lower BER. The default mode is FEC on and E-FEC off. E-FEC is provisioned using CTC. 10.8.9 SONET/SDH Overhead Byte Processing The card passes the incoming SONET/SDH data stream and its overhead bytes for the client signal transparently. The card can be provisioned to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. 10.8.10 Client Interface Monitoring The following parameters are monitored on the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards: • Laser bias current is measured as a PM parameter. • LOS is detected and signaled. • Rx and Tx power are monitored. The following parameters are monitored in real time mode (one second): • Optical power transmitted (client) • Optical power received (client) In case of LOC at the DWDM receiver or far-end LOS, the client interface behavior is configurable. AIS can be invoked or the client signal can be squelched. 10.8.11 Wavelength Identification The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. Both the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards implement the UT2 module. The MXP_2.5G_10E_C card uses a C-band version of the UT2 and the MXP_2.5G_10E_L card uses an L-band version. Table 10-18 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10E_C card. The laser is tunable over 82 wavelengths in the C band at 50-GHz spacing on the ITU grid.10-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards Table 10-18 MXP_2.5G_10E_C Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.38910-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards Table 10-19 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10E_L card. The laser is fully tunable over 80 wavelengths in the L band at 50-GHz spacing on the ITU grid. 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 10-18 MXP_2.5G_10E_C Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table 10-19 MXP_2.5G_10E_L Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 190.85 1570.83 41 188.85 1587.46 2 190.8 1571.24 42 188.8 1587.88 3 190.75 1571.65 43 188.75 1588.30 4 190.7 1572.06 44 188.7 1588.73 5 190.65 1572.48 45 188.65 1589.15 6 190.6 1572.89 46 188.6 1589.57 7 190.55 1573.30 47 188.55 1589.99 8 190.5 1573.71 48 188.5 1590.41 9 190.45 1574.13 49 188.45 1590.83 10 190.4 1574.54 50 188.4 1591.26 11 190.35 1574.95 51 188.35 1591.68 12 190.3 1575.37 52 188.3 1592.10 13 190.25 1575.78 53 188.25 1592.52 14 190.2 1576.20 54 188.2 1592.95 15 190.15 1576.61 55 188.15 1593.37 16 190.1 1577.03 56 188.1 1593.79 17 190.05 1577.44 57 188.05 1594.22 18 190 1577.86 58 188 1594.64 19 189.95 1578.27 59 187.95 1595.06 20 189.9 1578.69 60 187.9 1595.49 21 189.85 1579.10 61 187.85 1595.91 22 189.8 1579.52 62 187.8 1596.34 23 189.75 1579.93 63 187.75 1596.7610-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards 10.8.12 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details regarding ALS provisioning for the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards, see the Cisco ONS 15454 DWDM Procedure Guide. 10.8.13 Jitter For SONET and SDH signals, the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards comply with Telcordia GR-253-CORE, ITU-T G.825, and ITU-T G.873 for jitter generation, jitter tolerance, and jitter transfer. See the “10.21 Jitter Considerations” section on page 10-142 for more information. 10.8.14 Lamp Test The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards support a lamp test function that is activated from the ONS 15454 front panel or through CTC to ensure that all LEDs are functional. 24 189.7 1580.35 64 187.7 1597.19 25 189.65 1580.77 65 187.65 1597.62 26 189.6 1581.18 66 187.6 1598.04 27 189.55 1581.60 67 187.55 1598.47 28 189.5 1582.02 68 187.5 1598.89 29 189.45 1582.44 69 187.45 1599.32 30 189.4 1582.85 70 187.4 1599.75 31 189.35 1583.27 71 187.35 1600.17 32 189.3 1583.69 72 187.3 1600.60 33 189.25 1584.11 73 187.25 1601.03 34 189.2 1584.53 74 187.2 1601.46 35 189.15 1584.95 75 187.15 1601.88 36 189.1 1585.36 76 187.1 1602.31 37 189.05 1585.78 77 187.05 1602.74 38 189 1586.20 78 187 1603.17 39 188.95 1586.62 79 186.95 1603.60 40 188.9 1587.04 80 186.9 1604.03 Table 10-19 MXP_2.5G_10E_L Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)10-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_2.5G and MXPP_MR_2.5G Cards 10.8.15 Onboard Traffic Generation The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards provide internal traffic generation for testing purposes according to PRBS, SONET/SDH, or ITU-T G.709. 10.8.16 MXP_2.5G_10E_C and MXP_2.5G_10E_L Card-Level Indicators Table 10-20 describes the three card-level LEDs on the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards. 10.8.17 MXP_2.5G_10E and MXP_2.5G_10E_L Port-Level Indicators Table 10-21 describes the port-level LEDs on the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards. 10.9 MXP_MR_2.5G and MXPP_MR_2.5G Cards The MXP_MR_2.5G card aggregates a mix and match of client Storage Area Network (SAN) service client inputs (GE, FICON, Fibre Channel, and ESCON) into one 2.5 Gbps STM-16/OC-48 DWDM signal on the trunk side. It provides one long-reach STM-16/OC-48 port per card and is compliant with Telcordia GR-253-CORE. Table 10-20 MXP_2.5G_10E_C and MXP_2.5G_10E_L 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-21 MXP_2.5G_10E_C and MXP_2.5G_10E_L Port-Level Indicators Port-Level LED Description Green Client LED (four LEDs) A green Client LED indicates that the client port is in service and that it is receiving a recognized signal. The card has four client ports, and so has four Client LEDs. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_2.5G and MXPP_MR_2.5G Cards Note In Software Release 7.0 and later, two additional operating modes have been made available to the user: pure ESCON (all 8 ports running ESCON), and mixed mode (Port 1 running FC/GE/FICON, and Ports 5 through 8 running ESCON). When the card is part of a system running Software Release 6.0 or below, only one operating mode, (FC/GE) is available for use. The 2.5-Gbps Multirate Muxponder–Protected–100 GHz–Tunable 15xx.xx-15yy.yy (MXPP_MR_2.5G) card aggregates various client SAN service client inputs (GE, FICON, Fibre Channel, and ESCON) into one 2.5 Gbps STM-16/OC-48 DWDM signal on the trunk side. It provides two long-reach STM-16/OC-48 ports per card and is compliant with ITU-T G.957 and Telcordia GR-253-CORE. Because the cards are tunable to one of four adjacent grid channels on a 100-GHz spacing, each card is available in eight versions, with 15xx.xx representing the first wavelength and 15yy.yy representing the last wavelength of the four available on the card. In total, 32 DWDM wavelengths are covered in accordance with the ITU-T 100-GHz grid standard, G.692, and Telcordia GR-2918-CORE, Issue 2. The card versions along with their corresponding wavelengths are shown in Table 10-22. The muxponders are intended to be used in applications with long DWDM metro or regional unregenerated spans. Long transmission distances are achieved through the use of flat gain optical amplifiers. The client interface supports the following payload types: • 2G FC • 1G FC • 2G FICON • 1G FICON • GE • ESCON Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a maximum limit of 2.5 Gbps. Table 10-22 Card Versions Card Version Frequency Channels at 100 GHz (0.8 nm) Spacing 1530.33–1532.68 1530.33 nm 1531.12 nm 1531.90 nm 1532.68 nm 1534.25–1536.61 1534.25 nm 1535.04 nm 1535.82 nm 1536.61 nm 1538.19–1540.56 1538.19 nm 1538.98 nm 1539.77 nm 1540.56 nm 1542.14–1544.53 1542.14 nm 1542.94 nm 1543.73 nm 1544.53 nm 1546.12–1548.51 1546.12 nm 1546.92 nm 1547.72 nm 1548.51 nm 1550.12–1552.52 1550.12 nm 1550.92 nm 1551.72 nm 1552.52 nm 1554.13–1556.55 1554.13 nm 1554.94 nm 1555.75 nm 1556.55 nm 1558.17–1560.61 1558.17 nm 1558.98 nm 1559.79 nm 1560.61 nm10-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_2.5G and MXPP_MR_2.5G Cards Table 10-23 shows the input data rate for each client interface, and the encapsulation method. The current version of the ITU-T Transparent Generic Framing Procedure (GFP-T) G.7041 supports transparent mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, and FICON. In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed serializer/deserializer (SERDES) is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel. Table 10-24 shows some of the mix and match possibilities on the various client ports. The table is intended to show the full client payload configurations for the card. Table 10-23 MXP_MR_2.5G and MXPP_MR_2.5G Client Interface Data Rates and Encapsulation Client Interface Input Data Rate ITU-T GFP-T G.7041 Encapsulation 2G FC 2.125 Gbps Yes 1G FC 1.06 Gbps Yes 2G FICON 2.125 Gbps Yes 1G FICON 1.06 Gbps Yes GE 1.25 Gbps Yes ESCON 0.2 Gbps Yes Table 10-24 Client Data Rates and Ports Mode Port(s) Aggregate Data Rate 2G FC 1 2.125 Gbps 1G FC 1, 2 2.125 Gbps 2G FICON 1 2.125 Gbps 1G FICON 1, 2 2.125 Gbps GE 1, 2 2.5 Gbps 1G FC ESCON (mixed mode) 1 5, 6, 7, 8 1.06 Gbps 0.8 Gbps 1.86 Gbps total 1G FICON ESCON (mixed mode) 1 5, 6, 7, 8 1.06 Gbps 0.8 Gbps 1.86 Gbps total GE ESCON (mixed mode) 1 5, 6, 7, 8 1.25 Gbps 0.8 Gbps Total 2.05 Gbps ESCON 1, 2, 3, 4, 5, 6, 7, 8 1.6 Gbps10-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_2.5G and MXPP_MR_2.5G Cards 10.9.1 Performance Monitoring GFP-T performance monitoring (GFP-T PM) is available via remote monitoring (RMON), and trunk PM is managed according to Telcordia GR-253-CORE and ITU G.783/826. Client PM is achieved through RMON for FC and GE. 10.9.2 Distance Extension A buffer-to-buffer credit management scheme provides FC flow control. With this feature enabled, a port indicates the number of frames that can be sent to it (its buffer credit), before the sender is required to stop transmitting and wait for the receipt of a “ready” indication The MXP_MR_2.5G and MXPP_MR_2.5 cards support FC credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.2 miles) for 1G FC and up to 800 km (497.1 miles) for 2G FC. The feature can be enabled or disabled. 10.9.3 Slot Compatibility You can install MXP_MR_2.5G and MXPP_MR_2.5G cards in Slots 1 to 6 and 12 to 17. The TCC2/TCC2P/TCC3/TNC/TSC card is the only other card required to be used with these muxponder cards. Cross-connect cards do not affect the operation of the muxponder cards. 10.9.4 Interoperability with Cisco MDS Switches You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_2.5G and MXPP_MR_2.5G cards, which allows the MDS Fabric Manager to create a link association between that SAN port and a SAN port on a Cisco MDS 9000 switch. 10.9.5 Client and Trunk Ports The MXP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser (depending on the SFP) for the client ports. The card contains eight 12.5 degree downward tilt SFP modules for the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual-LC connector with a 45 degree downward angle. The MXPP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser (depending on the SFP) for the client port. The card contains eight 12.5 degree downward tilt SFP modules for the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on the faceplate. There are two trunk port connectors (one for working and one for protect). Each is a dual-LC connector with a 45-degree downward angle. 10.9.6 Faceplates Figure 10-23 shows the MXP_MR_2.5G and MXPP_MR_2.5G faceplates.10-53 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_2.5G and MXPP_MR_2.5G Cards Figure 10-23 MXP_MR_2.5G and MXPP_MR_2.5G Faceplates For information on safety labels for the cards, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. 10.9.7 Block Diagram Figure 10-24 shows a block diagram of the MXP_MR_2.5G card. The card has eight SFP client interfaces. Ports 1 and 2 can be used for GE, FC, FICON, or ESCON. Ports 3 through 8 are used for ESCON client interfaces. There are two SERDES blocks dedicated to the high-speed interfaces (GE, FC, FICON, and ESCON) and two SERDES blocks for the ESCON interfaces. A FPGA is provided to support different configurations for different modes of operation. This FPGA has a Universal Test and MXP_MR_2.5G MXPP_MR_2.5G 124077 MXP MR 2.5G 15xx.xx 15xx.xx FAIL ACT/STBY SF MXPP MR 2.5G 15xx.xx 15xx.xx RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX DWDMA DWDMB FAIL ACT/STBY SF RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX DWDM RX TX10-54 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_2.5G and MXPP_MR_2.5G Cards Operations Physical Interface for ATM (UTOPIA) interface. A transceiver add/drop multiplexer (TADM) chip supports framing. Finally, the output signal is serialized and connected to the trunk front end with a direct modulation laser. The trunk receive signal is converted into an electrical signal with an avalanche photodiode (APD), is deserialized, and is then sent to the TADM framer and FPGA. The MXPP_MR_2.5G is the same, except a 50/50 splitter divides the power at the trunk interface. In the receive direction, there are two APDs, two SERDES blocks, and two TADM framers. This is necessary to monitor both the working and protect paths. A switch selects one of the two paths to connect to the client interface. Figure 10-24 MXP_MR_2.5G and MXPP_MR_2.5G Block Diagram Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_MR_2.5G and MXPP_MR_2.5G cards in a loopback configuration on the trunk port. Do not use direct fiber loopbacks with the MXP_MR_2.5G and MXPP_MR_2.5G cards. Using direct fiber loopbacks causes irreparable damage to the MXP_MR_2.5G and MXPP_MR_2.5G cards. 10.9.8 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details regarding ALS provisioning for the MXP_MR_2.5G and MXPP_MR_2.5G cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. SFP 1 SFP 6 SFP 5 SFP 4 SFP 3 SFP 2 SFP 8 SERDES FPGA (for FC, GE, FICON, ESCON, PCS, B2B, GFP-T) SERDES SFP 7 High-speed SERDES QDR SRAM TADM framer Laser APD Serializer Deserializer ESCON ESCON ESCON ESCON ESCON ESCON Trunk interface 134986 GE, FC, FICON, ESCON GE, FC, FICON, ESCON10-55 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards 10.9.9 MXP_MR_2.5G and MXPP_MR_2.5G Card-Level Indicators Table 10-25 lists the card-level LEDs on the MXP_MR_2.5G and MXPP_MR_2.5G cards. 10.9.10 MXP_MR_2.5G and MXPP_MR_2.5G Port-Level Indicators Table 10-26 lists the port-level LEDs on the MXP_MR_2.5G and MXPP_MR_2.5G cards. 10.10 MXP_MR_10DME_C and MXP_MR_10DME_L Cards MXP_MR_10DME_L: (Cisco ONS 15454 only) Table 10-25 MXP_MR_2.5G and MXPP_MR_2.5G Card-Level Indicators Card-Level LED Description FAIL LED (Red) Red 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 Green (Active) Amber (Standby) Green indicates that the card is operational (one or both ports active) and ready to carry traffic. Amber indicates that the card is operational and in standby (protect) mode. SF LED (Amber) Amber indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also illuminated if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the LED turns off. Table 10-26 MXP_MR_2.5G and MXPP_MR_2.5G Port-Level Indicators Port-Level LED Description Client LEDs (eight LEDs) Green indicates that the port is carrying traffic (active) on the interface. Amber indicates that the port is carrying protect traffic (MXPP_MR_2.5G). Red indicates that the port has detected a loss of signal. DWDM LED (MXP_MR_2.5G) Green (Active) Red (LOS) Green indicates that the card is carrying traffic (active) on the interface. A red LED indicates that the interface has detected an LOS or LOC. DWDMA and DWDMB LEDs (MXPP_MR_2.5G) Green (Active) Amber (Protect Traffic) Red (LOS) Green indicates that the card is carrying traffic (active) on the interface. When the LED is amber, it indicates that the interface is carrying protect traffic in a splitter protection card (MXPP_MR_2.5G). A red LED indicates that the interface has detected an LOS or LOC.10-56 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards The MXP_MR_10DME_C and MXP_MR_10DME_L cards aggregate a mix of client SAN service client inputs (GE, FICON, and Fibre Channel) into one 10.0 Gbps STM-64/OC-192 DWDM signal on the trunk side. It provides one long-reach STM-64/OC-192 port per card and is compliant with Telcordia GR-253-CORE and ITU-T G.957. The cards support aggregation of the following signal types: • 1-Gigabit Fibre Channel • 2-Gigabit Fibre Channel • 4-Gigabit Fibre Channel • 1-Gigabit Ethernet • 1-Gigabit ISC-Compatible (ISC-1) • 2-Gigabit ISC-Peer (ISC-3) Note On the card faceplates, the MXP_MR_10DME_C and MXP_MR_10DME_L cards are displayed as 10DME_C and 10DME_L, respectively. Caution The card can be damaged by dropping it. Handle it safely. The MXP_MR_10DME_C and MXP_MR_10DME_L muxponders pass all SONET/SDH overhead bytes transparently. The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_MR_10DME_C and MXP_MR_10DME_L cards work with the OTN devices defined in ITU-T G.709. The cards support ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “10.7.7 Multiplexing Function” section on page 10-36. Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a maximum limit of 10 Gbps. You can install MXP_MR_10DME_C and MXP_MR_10DME_L cards in Slots 1 to 6 and 12 to 17. Note The MXP_MR_10DME_C and MXP_MR_10DME_L cards are not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode. The MXP_MR_10DME_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The MXP_MR_10DME_L features a tunable 1580-nm L-band laser on the trunk port. The laser is tunable across 80 wavelengths on the ITU grid, also with 50-GHz spacing. Each card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The cards uses dual LC connectors on the trunk side and use SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.10-57 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards Table 10-27 shows the input data rate for each client interface, and the encapsulation method. The current version of the GFP-T G.7041 supports transparent mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, ISC, and FICON. In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed SERDES is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the high-speed SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel. There are two FPGAs on each MXP_MR_10DME_C and MXP_MR_10DME_L, and a group of four ports is mapped to each FPGA. Group 1 consists of Ports 1 through 4, and Group 2 consists of Ports 5 through 8. Table 10-28 shows some of the mix and match possibilities on the various client data rates for Ports 1 through 4, and Ports 5 through 8. An X indicates that the data rate is supported in that port. GFP-T PM is available through RMON and trunk PM is managed according to Telcordia GR-253-CORE and ITU G.783/826. Client PM is achieved through RMON for FC and GE. A buffer-to-buffer credit management scheme provides FC flow control. With this feature enabled, a port indicates the number of frames that can be sent to it (its buffer credit), before the sender is required to stop transmitting and wait for the receipt of a “ready” indication The MXP_MR_10DME_C and MXP_MR_10DME_L cards support FC credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.1 miles) for 1G FC, up to 800 km (497.1 miles) for 2G FC, or up to 400 km (248.5 miles) for 4G FC. The feature can be enabled or disabled. The MXP_MR_10DME_C and MXP_MR_10DME_L cards feature a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser (depending on the SFP) for the client ports. The cards contains eight 12.5 degree downward tilt SFP modules for the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual-LC connector with a 45 degree downward angle. Table 10-27 MXP_MR_10DME_C and MXP_MR_10DME_L Client Interface Data Rates and Encapsulation Client Interface Input Data Rate GFP-T G.7041 Encapsulation 2G FC 2.125 Gbps Yes 1G FC 1.06 Gbps Yes 2G FICON/2G ISC-Compatible (ISC-1)/ 2G ISC-Peer (ISC-3) 2.125 Gbps Yes 1G FICON/1G ISC-Compatible (ISC-1)/ 1G ISC-Peer (ISC-3) 1.06 Gbps Yes Gigabit Ethernet 1.25 Gbps Yes Table 10-28 Supported Client Data Rates for Ports 1 through 4 and Ports 5 through 8 Port (Group 1) Port (Group 2) Gigabit Ethernet 1G FC 2G FC 4G FC 1 5 X XXX 2 6 X X —— 3 7 X XX— 4 8 X X ——10-58 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards The throughput of the MXP_MR_10DME_C and MXP_MR_10DME_L cards is affected by the following parameters: • Distance extension—If distance extension is enabled on the card, it provides more throughput but more latency. If distance extension is disabled on the card, the buffer to buffer credits on the storage switch affects the throughput; higher the buffer to buffer credits higher is the throughput. Note For each link to operate at the maximum throughput, it requires a minimum number of buffer credits to be available on the devices which the link connects to. The number of buffer credits required is a function of the distance between the storage switch extension ports and the link bandwidth, that is, 1G, 2G, or 4G. These buffer credits are provided by either the storage switch (if distance extension is disabled) or by both the storage switch and the card (if distance extension is enabled). • Forward Error Correction (FEC)—If Enhanced FEC (E-FEC) is enabled on the trunk port of the card, the throughout is significantly reduced in comparison to standard FEC being set on the trunk port. Note If distance extension is enabled on the card, the FEC status does not usually affect the throughput of the card. • Payload size—The throughput of the card decreases with decrease in payload size. The resultant throughput of the card is usually the combined effect of the above parameters. 10.10.1 Key Features The MXP_MR_10DME_C and MXP_MR_10DME_L cards have the following high-level features: • Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. A new BCH algorithm implemented in E-FEC allows recovery of an input BER up to 1E-3. • Pluggable client interface optic modules: The MXP_MR_10DME_C and MXP_MR_10DME_L cards have modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957). • Y-cable protection: Supports Y-cable protection between the same card type only, on ports with the same port number and signal rate. See the “10.19.1 Y-Cable Protection” section on page 10-139 for more detailed information. • High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software. • ALS: A safety mechanism used in the event of a fiber cut. For details regarding ALS provisioning for the MXP_MR_10DME_C and MXP_MR_10DME_L cards, refer to the Cisco ONS 15454 DWDM Procedure Guide.10-59 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards • Link monitoring and management: The cards use standard OC-48 OH bytes to monitor and manage incoming interfaces. The cards pass the incoming SDH/SONET data stream and its OH bytes transparently. • Control of layered SONET/SDH transport overhead: The cards are provisionable to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. • Automatic timing source synchronization: The MXP_MR_10DME_C and MXP_MR_10DME_L cards normally synchronize from the TCC2/TCC2P/TCC3 card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3 is not available, the cards automatically synchronize to one of the input client interface clocks. Note MXP_MR_10DME_C and MXP_MR_10DME_L cards cannot be used for line timing. • Configurable squelching policy: The cards can be configured to squelch the client interface output if there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion. • The cards are tunable across the full C band (MXP_MR_10DME_C) or full L band (MXP_MR_10DME_L), thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band. • You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_10DME_C and MXP_MR_10DME_L cards, which allows the MDS Fabric Manager to create a link association between that SAN port and a SAN port on a Cisco MDS 9000 switch. • From Software Release 9.0, the fast switch feature of MXP_MR_10DME_C and MXP_MR_10DME_L cards along with the buffer-to-buffer credit recovery feature of MDS switches, prevents reinitialization of ISL links during Y-cable switchovers. 10.10.2 Faceplate Figure 10-25 shows the MXP_MR_10DME_C and MXP_MR_10DME_L faceplates and block diagram.10-60 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards Figure 10-25 MXP_MR_10DME_C and MXP_MR_10DME_L Faceplates and Block Diagram For information on safety labels for the cards, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the cards. Using direct fiber loopbacks causes irreparable damage to the MXP_MR_10DME_C and MXP_MR_10DME_L cards. 10.10.3 Wavelength Identification The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. Both the MXP_MR_10DME_C and MXP_MR_10DME_L cards implement the UT2 module. The MXP_MR_10DME_C card uses a C-band version of the UT2 and the MXP_MR_10DME_L card uses an L-band version. 10DME-C FAIL ACT/STBY SF 145767 RX TX 1 RX TX 2 RX TX 3 RX TX 4 RX TX 1 RX TX 2 RX TX 3 RX TX 4 DWDM RX TX 10DME-L FAIL ACT/STBY SF RX TX 1 RX TX 2 RX TX 3 RX TX 4 RX TX 1 RX TX 2 RX TX 3 RX TX 4 DWDM RX TX SPF 1/1 4G FC SerDes 1 x QDR 2M x 36bit Burst4 1/2/4G-FC B2B Credit Mgt FPGA Framer G.709/FEC OTN MXP UT2 Data path 5x I/O 5x I/O SPF 2/1 SPF 3/1 CPU Core FPGA Power supply DCC/GCC CPUC bus SPF 4/1 SPF 6/1 4G FC SerDes 1/2/4G-FC B2B Credit Mgt FPGA 5x I/O 5x I/O SPF 7/1 SPF 8/1 SPF 9/1 Client ports Group 1 Group 210-61 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards Table 10-29 describes the required trunk transmit laser wavelengths for the MXP_MR_10DME_C card. The laser is tunable over 82 wavelengths in the C band at 50-GHz spacing on the ITU grid. Table 10-29 MXP_MR_10DME_C Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.57810-62 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards Table 10-30 describes the required trunk transmit laser wavelengths for the MXP_MR_10DME_L card. The laser is fully tunable over 80 wavelengths in the L band at 50-GHz spacing on the ITU grid. 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 10-29 MXP_MR_10DME_C Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table 10-30 MXP_MR_10DME_L Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 190.85 1570.83 41 188.85 1587.46 2 190.8 1571.24 42 188.8 1587.88 3 190.75 1571.65 43 188.75 1588.30 4 190.7 1572.06 44 188.7 1588.73 5 190.65 1572.48 45 188.65 1589.15 6 190.6 1572.89 46 188.6 1589.57 7 190.55 1573.30 47 188.55 1589.99 8 190.5 1573.71 48 188.5 1590.41 9 190.45 1574.13 49 188.45 1590.83 10 190.4 1574.54 50 188.4 1591.26 11 190.35 1574.95 51 188.35 1591.68 12 190.3 1575.37 52 188.3 1592.10 13 190.25 1575.78 53 188.25 1592.52 14 190.2 1576.20 54 188.2 1592.95 15 190.15 1576.61 55 188.15 1593.37 16 190.1 1577.03 56 188.1 1593.79 17 190.05 1577.44 57 188.05 1594.22 18 190 1577.86 58 188 1594.64 19 189.95 1578.27 59 187.95 1595.06 20 189.9 1578.69 60 187.9 1595.49 21 189.85 1579.10 61 187.85 1595.9110-63 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DME_C and MXP_MR_10DME_L Cards 10.10.4 MXP_MR_10DME_C and MXP_MR_10DME_L Card-Level Indicators Table 10-31 describes the three card-level LEDs on the MXP_MR_10DME_C and MXP_MR_10DME_L cards. 22 189.8 1579.52 62 187.8 1596.34 23 189.75 1579.93 63 187.75 1596.76 24 189.7 1580.35 64 187.7 1597.19 25 189.65 1580.77 65 187.65 1597.62 26 189.6 1581.18 66 187.6 1598.04 27 189.55 1581.60 67 187.55 1598.47 28 189.5 1582.02 68 187.5 1598.89 29 189.45 1582.44 69 187.45 1599.32 30 189.4 1582.85 70 187.4 1599.75 31 189.35 1583.27 71 187.35 1600.17 32 189.3 1583.69 72 187.3 1600.60 33 189.25 1584.11 73 187.25 1601.03 34 189.2 1584.53 74 187.2 1601.46 35 189.15 1584.95 75 187.15 1601.88 36 189.1 1585.36 76 187.1 1602.31 37 189.05 1585.78 77 187.05 1602.74 38 189 1586.20 78 187 1603.17 39 188.95 1586.62 79 186.95 1603.60 40 188.9 1587.04 80 186.9 1604.03 Table 10-30 MXP_MR_10DME_L Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table 10-31 MXP_MR_10DME_C and MXP_MR_10DME_L 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off.10-64 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card 10.10.5 MXP_MR_10DME_C and MXP_MR_10DME_L Port-Level Indicators Table 10-32 describes the port-level LEDs on the MXP_MR_10DME_C and MXP_MR_10DME_L cards. 10.11 40G-MXP-C Card The 40G-MXP-C card aggregates a variety of client service inputs (GigabitEthernet, Fibre Channel, OTU2, OTU2e, and OC192) into one 40.0 Gbps OTU3/OTU3e signal on the trunk side. The 40G-MXP-C card supports aggregation of the following signals: • With overclock enabled on the trunk port: – 10-Gigabit Fibre Channel – OTU2e • With overclock disabled on the trunk port: – 8-Gigabit Fibre Channel – 10-GigabitEthernet LAN-Phy (GFP framing) – 10-GigabitEthernet LAN-Phy (WIS framing) – OC-192/STM-64 – OTU2 Caution Handle the card with care. Dropping or misuse of the card could result in permanent damage. The 40G-MXP-C muxponder passes all SONET/SDH overhead bytes transparently, section, or line termination. Table 10-32 MXP_MR_10DME_C and MXP_MR_10DME_L Port-Level Indicators Port-Level LED Description Port LED (eight LEDs, four for each group, one for each SFP) Green/Red/Amber/Off When green, the port LED indicates that the client port is either in service and receiving a recognized signal (that is, no signal fail), or Out of Service and Maintenance (OOS,MT or locked, maintenance) and the signal fail and alarms are being ignored. When red, the port LED indicates that the client port is in service but is receiving a signal fail (LOS). When amber, the port LED indicates that the port is provisioned and in a standby state. When off, the port LED indicates that the SFP is either not provisioned, out of service, not properly inserted, or the SFP hardware has failed. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-65 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate performance monitoring. The 40G-MXP-C card work with the OTN devices defined in ITU-T G.709. The card supports ODTU23 multiplexing, an industry standard method for asynchronously mapping client payloads into a digitally wrapped envelope. See the “10.7.7 Multiplexing Function” section on page 10-36. You can install and provision the 40G-MXP-C card in a linear configuration in: • Slots 1 to 5 and 12 to 16 in ONS 15454 DWDM chassis • Slot 2 in ONS 15454 M2 chassis • Slots 2 to 6 in ONS 15454 M6 chassis The 40G-MXP-C card client port interoperates with all the existing TXP/MXP (OTU2 trunk) cards. The 40G-MXP-C card client port does not interoperate with OTU2_XP card when the signal rate is OTU1e (11.049 Gbps) and the “No Fixed Stuff” option is enabled on the trunk port of OTU2_XP card. For OTU2 and OTU2e client protocols, Enhanced FEC (EFEC) is not supported in Port 1 of the 40G-MXP-C card. Table 10-33 lists the FEC configuration supported on OTU2/OTU2e protocol for 40G-MXP-C card. When setting up the card for the first time, or when the card comes up after clearing the LOS-P condition due to fiber cut, the trunk port of the 40G-MXP-C card takes a about six minutes to lock a signal. The trunk port of the 40G-MXP-C card raises an OTUK-LOF alarm when the card is comes up. The alarm clears when the trunk port locks the signal. When protection switch occurs on the 40G-MXP-C card, the recovery from PSM protection switch takes about 3 to 4 minutes. The 40G-MXP-C card is tunable over C-band on the trunk port. The 40G-MXP-C card supports pluggable XFPs on the client ports on the card faceplate. The card uses dual LC connectors on the trunk side, and XFP modules on the client side for optical cable termination. The XFP pluggable modules are SR, LR, MM, DWDM, or CWDM and support an LC fiber connector. The 40G-MXP-C card contains four XFP modules for the client interfaces. For optical termination, each XFP uses two LC connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual-LC connector facing downward at 45 degrees. Table 10-34 shows the input data rate for each client interface. Table 10-33 40G-MXP-C Client Interface Data Rates 40G-MXP-C Client Port FEC Configuration Supported on OTU2/OTU2e Client Protocol Port 1 Only Standard FEC Port 2 Standard and Enhanced FEC Port 3 Standard and Enhanced FEC Port 4 Standard and Enhanced FEC Table 10-34 40G-MXP-C Client Interface Input Data Rates Client Interface Input Data Rate 8-Gigabit Fibre Channel 8.48 Gbps 10-Gigabit Fibre Channel 10.519 Gbps 10-GigabitEthernet LAN-Phy 10.312 Gbps10-66 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card 10.11.1 Key Features The 40G-MXP-C card comprises of the following key features: • The 40G-MXP-C card uses the RZ-DQPSK 40G modulation format. • Onboard E-FEC processor: The E-FEC functionality improves the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (239,255) correction algorithm. A new BCH algorithm implemented (according to G.975.1 I.7) in E-FEC allows recovery of an input BER up to 1E-3. The 40G-MXP-C card supports both standard RS (specified in ITU-T G.709) and E-FEC standard, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. • Y-cable protection: Supports Y-cable protection between the same card type only, on ports with the same port number and signal rate. For more information on Y-cable protection, see “10.19 Y-Cable and Splitter Protection” section on page 10-139. Note Y-cable cannot be created on 10 GE port when WIS framing is enabled on the 40G-MXP-C card. • Unidirectional regeneration: The 40G-MXP-C card supports unidirectional regeneration configuration. Each 40G-MXP-C card in the configuration regenerates the signal received from another 40G-MXP-C card in one direction. Note When you configure the 40G-MXP-C card in Unidirectional Regen mode, ensure that the payload is not configured on pluggable port modules of the 40G-MXP-C card. Figure 10-26 shows a typical unidirectional regeneration configuration. Figure 10-26 40G-MXP-C Cards in Unidirectional Regeneration Configuration • High level provisioning support: The cards are initially provisioned using Cisco Transport Planner software. Subsequently, the card can be monitored and provisioned using CTC software. 10-GigabitEthernet WAN-Phy 9.953 Gbps OC-192/STM-64 9.953 Gbps OTU2 10.709 Gbps OTU2e 11.096 Gbps Table 10-34 40G-MXP-C Client Interface Input Data Rates (continued) Client Interface Input Data Rate 278759 Client DWDM System DWDM System 40G-MXP-C 40G-MXP-C 40G-MXP-C 40G-MXP-C Client DWDM Trunk DWDM Trunk DWDM Trunk DWDM Trunk10-67 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card • Automatic Laser Shutdown (ALS): A safety mechanism used in the event of a fiber cut. The Auto Restart ALS option is supported only for OC192/STM64 and OTU2 payloads. The Manual Restart ALS option is supported for all payloads. For more information on ALS provisioning for the 40G-MXP-C card, see the Cisco ONS 15454 DWDM Procedure Guide. • Control of layered SONET/SDH transport overhead: The cards are provisionable to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. • Automatic timing source synchronization: The 40G-MXP-C card synchronizes to the TCC2/TCC2P/TCC3/TNC/TSC card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TSC card is not available, the cards automatically synchronize to one of the input client interface clocks. • Squelching policy: The cards are set to squelch the client interface output if there is LOS at the DWDM receiver, or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion. • The card is tunable across the full C band wavelength. 10.11.2 Faceplate and Block Diagram Figure 10-27 shows the 40G-MXP-C card faceplate and block diagram.10-68 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card Figure 10-27 40G-MXP-C Faceplate and Block Diagram For information on safety labels for the cards, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the cards. Using direct fiber loopbacks causes irreparable damage to the 40G-MXP-C card. 10.11.3 Wavelength Identification The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. The 40G-MXP-C card implements the UT2 module. The 40G-MXP-C card uses a C-band version of the UT2. Table 10-35 lists the required trunk transmit laser wavelengths for the 40G-MXP-C card. The laser is tunable over 82 wavelengths in the C band at 50-GHz spacing on the ITU grid. 278757 XFP XFP XFP XFP MSA 100 40 G FEC/EF EC Trunk module TDC EDFA XFP Child card Tx Rx Trunk 4x XFI SFI 5.1 interface Threshold control 40G-MXP-C FAIL ACT/STBY SF XFP1 XFP2 XFP3 XFP4 TRUNK RX 2 TX RX 1 TX RX 3 TX RX 4 TX TRUNK TX MX RX HAZARD LEVEL 1 COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No.50, DATED JUNE 24, 200710-69 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card Table 10-35 40G-MXP-C Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.38910-70 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards 40G-MXP-C Card 10.11.4 40G-MXP-C Card-Level Indicators Table 10-36 describes the three card-level indicators on the 40G-MXP-C card. 10.11.5 40G-MXP-C Card Port-Level Indicators Table 10-37 describes the port-level indicators on the 40G-MXP-C card. 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 10-35 40G-MXP-C Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table 10-36 40G-MXP-C Card-Level Indicators Card-Level Indicator 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off.10-71 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are Gigabit Ethernet Xponders for the ONS 15454 ANSI and ETSI platforms. Note GE_XPE card is the enhanced version of the GE_XP card and 10GE_XPE card is the enhanced version of the 10GE_XP card. The cards aggregate Ethernet packets received on the client ports for transport on C-band trunk ports that operate on a 100-GHz grid. The trunk ports operate with ITU-T G.709 framing and either FEC or E-FEC. The GE_XP and 10GE_XP cards are designed for bulk point-to-point transport over 10GE LAN PHY wavelengths for Video-on-Demand (VOD), or broadcast video across protected 10GE LAN PHY wavelengths. The GE_XPE and 10GE_XPE cards are designed for bulk GE_XPE or 10GE_XPE point-to-point, point-to-multipoint, multipoint-to-multipoint transport over 10GE LAN PHY wavelengths for Video-on-Demand (VOD), or broadcast video across protected 10GE LAN PHY wavelengths. You can install and provision the GE_XP, and GE_XPE cards in a linear configuration in: • Slots 1 to 5 and 12 to 16 in ONS 15454 DWDM chassis • Slot 2 in ONS 15454 M2 chassis • Slots 2 to 6 in ONS 15454 M6 chassis The 10GE_XP and 10GE_XPE cards can be installed in Slots 1 through 6 or 12 through 17. The GE_XP and GE_XPE are double-slot cards with twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The 10GE_XP and 10GE_XPE are single-slot cards with two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The client ports support SX, LX, and ZX SFPs and SR and 10GBASE-LR XFPs. (LR2 XFPs are not supported.) The trunk ports support a DWDM XFP. Table 10-37 40G-MXP-C Card Port-Level Indicators Port-Level Indicator Description Port LED (eight LEDs, four for each group, one for each XFP) Green/Red/Amber/Off The green port LED indicates that the client port is either in service and receiving a recognized signal (that is, no signal fail), or Out of Service and Maintenance (OOS,MT or locked, maintenance) and the signal fail and alarms are being ignored. The red port LED indicates that the client port is in service but is receiving a signal fail (LOS). The amber port LED indicates that the port is provisioned and in a standby state. The port LED, when switched off, indicates that the SFP is either not provisioned, out of service, not properly inserted, or the SFP hardware failed. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-72 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards The RAD pluggables (ONS-SC-E3-T3-PW= and ONS-SC-E1-T1-PW=) do not support: • No loopbacks (Terminal or Facility) • RAI (Remote Alarm Indication) alarm • AIS and LOS alarm Caution A fan-tray assembly (15454E-CC-FTA for the ETSI shelf, or 15454-CC-FTA for the ANSI shelf) must be installed in a shelf where a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed. GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can be provisioned to perform different Gigabit Ethernet transport roles. All the cards can work as Layer 2 switches. However, the 10GE_XP and 10GE_XPE cards can also perform as a 10 Gigabit Ethernet transponders (10GE TXP mode), and the GE_XP and GE_XPE can perform as a 10 Gigabit Ethernet or 20 Gigabit Ethernet muxponders (10GE MXP or 20GE MXP mode). Table 10-38 shows the card modes supported by each card. Note Changing the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card mode requires the ports to be in a OOS-DSBL (ANSI) or Locked, disabled (ETSI) service state. In addition, no circuits can be provisioned on the cards when the mode is being changed. 10.12.1 Key Features The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have the following high-level features: • Link Aggregation Control Protocol (LACP) that allows you to bundle several physical ports together to form a single logical channel. • Ethernet Connectivity Fault Management (CFM) protocol that facilitates proactive connectivity monitoring, fault verification, and fault isolation. Table 10-38 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Modes Card Mode Cards Description Layer 2 Ethernet switch GE_XP 10GE_XP GE_XPE 10GE_XPE Provides capability to switch between any two ports irrespective of client or trunk port. Supported Ethernet protocols and services include 1+1 protection, QoS (Quality of Service), CoS (Class of Service), QinQ, MAC learning, MAC address retrieval, service provider VLANs (SVLANs), IGMP snooping and Multicast VLAN Registration (MVR), link integrity, and other Ethernet switch services. 10GE TXP 10GE_XP 10GE_XPE Provides a point-to-point application in which each 10 Gigabit Ethernet client port is mapped to a 10 Gigabit Ethernet trunk port. 10GE MXP 20GE MXP GE_XP GE_XPE Provides the ability to multiplex the twenty Gigabit Ethernet client ports on the card to one or both of its 10 Gigabit Ethernet trunk ports. The card can be provisioned as a single MXP with twenty Gigabit Ethernet client ports mapped to one trunk port (Port 21) or as two MXPs with ten Gigabit Ethernet client ports mapped to a trunk port (Ports 1 to 10 mapped to Port 21, and Ports 11-20 mapped to Port 22).10-73 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards • Ethernet Operations, Administration, and Maintenance (OAM) protocol that facilitates link monitoring, remote failure indication, and remote loopback. • Resilient Ethernet Protocol (REP) that controls network loops, handles link failures, and improves convergence time. • Configurable service VLANs (SVLANs) and customer VLANs (CVLANs). • Ingress rate limiting that can be applied on both SVLANs and CVLANs. You can create SVLAN and CVLAN profiles and can associate a SVLAN profile to both UNI and NNI ports; however, you can associate a CVLAN profile only to UNI ports. • CVLAN rate limiting that is supported for QinQ service in selective add mode. • Differentiated Services Code Point (DSCP) to class of service (CoS) mapping that you can configure for each port. You can configure the CoS of the outer VLAN based on the incoming DSCP bits. This feature is supported only on GE_XPE and 10GE_XPE cards. • Ports, in Layer 2 switch mode, can be provisioned as network-to-network interfaces (NNIs) or user-network interfaces (UNIs) to facilitate service provider to customer traffic management. • Broadcast drop-and-continue capability for VOD and broadcast video applications. • Gigabit Ethernet MXP, TXP, and Layer 2 switch capability over the ONS 15454 DWDM platform. • Compatible with the ONS 15454 ANSI high-density shelf assembly, the ONS 15454 ETSI shelf assembly, ONS 15454 ETSI high-density shelf assembly, ONS 15454 M2, and the ONS 15454 M6 shelf assemblies. Compatible with TCC2, TCC2P, TCC3, TNC, and TSC cards. • Far-End Laser Control (FELC) that is supported on copper SFPs from Release 8.52 and later releases. For more information on FELC, see the “10.20 Far-End Laser Control” section on page 10-142. • Layer 2 switch mode that provides VLAN translation, QinQ, ingress CoS, egress QoS, Fast Ethernet protection switching, and other Layer 2 Ethernet services. • Interoperable with TXP_MR_10E and TXP_MR_10E_C cards. Also interoperable with Cisco Catalyst 6500 and Cisco 7600 series Gigabit Ethernet, 10 GE interfaces and CRS-1 10GE interfaces. • The GE_XP and GE_XPE cards have twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The 10GE_XP and 10GE_XPE cards have two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The client Gigabit Ethernet signals are mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing when configured in one of the MXP modes (10GE MXP or 20GE MXP). • ITU-T G.709 framing with standard Reed-Soloman (RS) (255,237) FEC. Performance monitoring and ITU-T G.709 Optical Data Unit (ODU) synchronous and asynchronous mapping. E-FEC with ITU-T G.709 ODU and 2.7 Gbps with greater than 8 dB coding gain. • IEEE 802.3 frame format that is supported for 10 Gigabit Ethernet interfaces. The minimum frame size is 64 bytes. The maximum frame size is user-provisionable. • MAC learning capability in Layer 2 switch mode. • MAC address retrieval in cards provisioned in the L2-over-DWDM mode. • When a port is in UNI mode, tagging can be configured as transparent or selective. In transparent mode, only SVLANs in the VLAN database of the node can be configured. In selective mode, a CVLAN- to-SVLAN relationship can be defined. • Layer 2 VLAN port mapping that allows the cards to be configured as multiple Gigabit Ethernet TXPs and MXPs. • Y-cable protection is configurable in TXP and MXP modes.10-74 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards • Two protection schemes are available in Layer 2 mode. They are: – 1+1 protection—Protection scheme to address card, port, or shelf failures for client ports. – Fast Automatic Protection—Protection scheme to address card, port, or shelf failures for trunk ports. • End-to-end Ethernet link integrity. • Pluggable client interface optic modules (SFPs and XFPs)—Client ports support tri-rate SX, LX, and ZX SFPs, and 10-Gbps SR1 XFPs. • Pluggable trunk interface optic modules; trunk ports support the DWDM XFP. • Internet Group Management Protocol (IGMP) snooping that restricts the flooding of multicast traffic by forwarding multicast traffic to those interfaces where a multicast device is present. • Multicast VLAN Registration (MVR) for applications using wide-scale deployment of multicast traffic across an Ethernet ring-based service provider network. • Ingress CoS that assigns a CoS value to the port from 0 (highest) to 7 (lowest) and accepts CoS of incoming frames. • Egress QoS that defines the QoS capabilities for the egress port. • MAC address learning that facilitates switch processing. • Storm Control that limits the number of packets passing through a port. You can define the maximum number of packets allowed per second for the following types of traffic: Broadcast, Multicast, and Unicast. The threshold for each type of traffic is independent and the maximum number of packets allowed per second for each type of traffic is 16777215. 10.12.2 Protocol Compatibility list Table 10-39 lists the protocol compatibility for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. 10.12.3 Faceplate and Block Diagram Figure 10-28 shows the GE_XP faceplate and block diagram. The GE_XPE faceplate and block diagram looks the same. Table 10-39 Protocol Compatibility List for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Protocol L1 1+1 FAPS IGMP REP LACP CFM EFM L1 No Yes Yes No No Yes No 1+1 No Yes Yes No No Yes No FAPS Yes Yes Yes No No Yes No IGMP Yes Yes Yes Yes No Yes No REP No No No Yes No Yes No LACP No No No No No No No CFM Yes Yes Yes Yes Yes No No EFM No No No No No No No10-75 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Figure 10-28 GE_XP and GE_XPE Faceplates and Block Diagram The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two trunk ports. The GE_XP and GE_XPE trunk ports are displayed as follows: • Trunk 1 and Trunk 2 on the faceplate • 21-1 and 22-1 on CTC • 21 (Trunk) and 22 (Trunk) on the Optics Thresholds table Figure 10-29 shows the 10GE_XP faceplate and block diagram. The 10 GE_XPE faceplate and block diagram looks the same. FAIL ACT SF GE-XP 1 TX RX 2 TX RX 3 TX RX 4 TX RX 5 TX RX 6 TX RX 7 TX RX 8 TX RX 9 TX RX 10 TX RX 11 TX RX 12 TX RX 13 TX RX 14 TX RX 15 TX RX 16 TX RX 17 TX RX 18 TX RX 19 TX RX 20 TX RX TX RX 2 TRUNK 1 CONSOLE T2 T1 TX RX ! MAX INPUT POWER LEVEL CLIENT: +3dBm TRUNK: +1dBm HAZARD LEVEL 1 159052 12GE Client ports CONN 8GE Client ports XAUI to SF14 XAUI to SF14 FEC SERDES XFP WDM FEC SERDES XFP WDM MPC8270 core Power supply Clocking BCM 5650x SCL FPGA COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No.50, DATED JULY 26, 2001 Client Ports 9-14 Client GE Ports 1-8 GE Client Ports 15-20 Trunk GE Ports 1-2 10GE BCM 5650x with Ethernet ASIC10-76 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Figure 10-29 10GE_XP and 10GE_XPE Faceplates and Block Diagram The 10GE_XP and 10GE_XPE card trunk ports are displayed as follows: • Trunk 1 and Trunk 2 on the faceplate • 3-1 and 4-1 on CTC • 3 (Trunk) and 4 (Trunk) on the Optics Thresholds table For information on safety labels for the cards, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the cards. Using direct fiber loopbacks causes irreparable damage to the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. ! MAX INPUT POWER LEVEL CLIENT: +3dBm TRUNK: +1dBm HAZARD LEVEL 1 10GE XP RX 2 TX TRUNK RX 1 TX RX 2 TX CLIENT RX 1 TX COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No.50, DATED JULY 26, 2001 FAIL ACT SF CONSOLE 159053 159053 XFP XAUI SERDES XFP XAUI SERDES XAUI to SF14 XAUI to SF14 FEC SERDES XFP WDM FEC SERDES XFP WDM MPC8270 core Power supply Clocking BCM 5650x with Ethernet ASIC SCL FPGA Client Ports 1-2 10GE Trunk Ports 1-2 10GE10-77 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.4 Client Interface The client interface is implemented with separately orderable SFP or XFP modules. The client interfaces support the following tri-rate SFPs and XFPs using dual LC connectors and multimode fiber: • SFP - GE/1G-FC/2G-FC - 850 nm - MM - LC (PID ONS-SE-G2F-SX) • SFP - GE/1G-FC/2G-FC 1300 nm - SM - LC (PID ONS-SE-G2F-LX) • SFP - GE/1G-FC/2G-FC 1300 nm - SM - LC (PID ONS-SE-G2F-ZX) • SFP - 10/100/1000Base-T - Copper (PID ONS-SE-ZE-EL) Intra office up to 100; Cable: RJ45 STP CAT5, CAT5E, and CAT6 • SFP - 1000Base BX D/Gigabit Ethernet 1550 nm - SM - LC (PID ONS-SE-GE-BXD) • SFP - 1000Base BX U/Gigabit Ethernet 1550 nm - SM - LC (PID ONS-SE-GE-BXU) • SFP - Fast Ethernet 1310 nm - SM - LC (PID ONS-SI-100-LX10) • SFP - Fast Ethernet 1310 nm - MM - LC (PID ONS-SI-100-FX) • SFP - Fast Ethernet over DS1/E1 - SM - LC (PID ONS-SC-EOP1) (GE_XPE only) • SFP - Fast Ethernet over DS3/E3 - SM - LC (PID ONS-SC-EOP3) (GE_XPE only) • SFP - E1/DS1 over Fast Ethernet - SM - LC (PID ONS-SC-E1-T1-PW) (GE_XPE only) • SFP - E3/DS3 PDH over Fast Ethernet - SM - LC (PID ONS-SC-E3-T3-PW) (GE_XPE only) Note The resommended topology for using ONS-SC-E1-T1-PW and ONS-SC-E3-T3-PW SFPs is shown in Figure 10-30. Figure 10-30 Recommended Topology for Using ONS-SC-E1-T1-PW and ONS -SC-E3-T3-PW SFPs The client interfaces support the following dual-rate XFP using dual LC connectors and single-mode fiber: • XFP - OC-192/STM-64/10GE/10-FC/OTU2 - 1310 SR - SM LC (PID: ONS-XC-10G-S1) • XFP - 10GE - 1550 nm - SM - LC (PID ONS-XC-10G-L2) • XFP - 10GE - 1550 nm - SM - LC (PID ONS-XC-10G-C) Note If ONS-XC-10G-C XFP is used on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards on client port 1, the maximum temperature at which the system qualifies is +45 degree Celsius. 249504 Network A with Internal Timing Network B with LoopbackTiming Node A Ethernet Network ONS-SC-E1-T1-PW or ONS-SC-E3-T3-PW on Port n of GE_XPE Card in Node A with Loopback Timing ONS-SC-E1-T1-PW or ONS-SC-E3-T3-PW on Port n of GE_XPE Card in Node B with AdaptiveTiming Node B10-78 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards The client interfaces support the following multimode XFP using dual LC connectors and multi-mode fiber: • XFP - OC-192/10GFC/10GE - 850 nm MM LC (PID ONS-XC-10G-SR-MM) 10.12.5 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card-Level Indicators Table 10-40 describes the three card-level LEDs on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. 10.12.6 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Port-Level Indicators Table 10-41 describes the port-level LEDs on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. Table 10-40 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE 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 LED Green (Active) If the ACT LED is green, the card is operational (one or more ports active) and ready to carry traffic. Amber SF LED The amber SF LED indicates that a signal failure or condition such as LOS, LOF, or high BERs is present one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-41 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Port-Level Indicators Port-Level LED Description Port LEDs Green/Red/Amber/Off Green—The client port is either in service and receiving a recognized signal (that is, no signal fail), or Out of Service and Maintenance (OOS,MT or locked, maintenance) in which case the signal fail and alarms will be ignored. Red—The client port is in service but is receiving a signal fail (LOS). Amber—The port is provisioned and in a standby state. Off—The SFP is either not provisioned, out of service, not properly inserted, or the SFP hardware has failed. Green DWDM LED Green—The green DWDM LED indicates that the DWDM port is in service and receiving a recognized signal (that is, no signal fail), or Out of Service and Maintenance (OOS,MT or locked, maintenance) in which case the signal fail and alarms will be ignored. Red—The client port is in service but is receiving a signal fail (LOS). Amber—The port is provisioned and in a standby state. Off—The SFP is either not provisioned, out of service, not properly inserted, or the SFP hardware has failed.10-79 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.7 DWDM Trunk Interface The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two 10 Gigabit Ethernet trunk ports operating at 10 Gigabit Ethernet (10.3125 Gbps) or 10 Gigabit Ethernet into OTU2 (nonstandard 11.0957 Gbps). The ports are compliant with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The ports are capable of carrying C-band and L-band wavelengths through insertion of DWDM XFPs. Forty channels are available in the 1550-nm C band 100-GHz ITU grid, and forty channels are available in the L band. The maximum system reach in filterless applications without the use of optical amplification or regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is given for informational purposes. It is subject to change. 10.12.8 Configuration Management The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards support the following configuration management parameters: • Port name—User-assigned text string. • Admin State/Service State—Administrative and service states to manage and view port status. • MTU—Provisionable maximum transfer unit (MTU) to set the maximum number of bytes per frames accepted on the port. • Mode—Provisional port mode, either Autonegotiation or the port speed. • Flow Control—Flow control according to IEEE 802.1x pause frame specification can be enabled or disabled for TX and RX ports. • Bandwidth—Provisionable maximum bandwidth allowed for the port. • Ingress CoS—Assigns a CoS value to the port from 0 (highest) to 7 (lowest) and accepts CoS of incoming frames. • Egress QoS—Defines the QoS capabilities at the egress port. • NIM—Defines the port network interface management type based on Metro Ethernet Forum specifications. Ports can be defined as UNI or NNI. • MAC Learning—MAC address learning to facilitate switch processing. • VLAN tagging provided according to the IEEE 802.1Q standard. Note When the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are provisioned in a MXP or TXP mode, only the following parameters are available: Port Name, State, MTU, Mode, Flow control, and Bandwidth. 10.12.9 Security GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card ports can be provisioned to block traffic from a user-defined set of MAC addresses. The remaining traffic is normally switched. You can manually specify the set of blocked MAC addresses for each port. Each port of the card can receive traffic from a limited predefined set of MAC addresses. The remaining traffic will be dropped. This capability is a subset of the Cisco IOS “Port Security” feature. 10-80 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.10 Card Protection The following section describes various card protection schemes available for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. 10.12.10.1 1+1 Protection 1+1 protection of GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards is provided in the Layer 2 (L2) card mode to protect against client port and card failure. 1+1 protection is supported in both single shelf and multishelf setup. This means that the working card can be in one shelf and the protect card can be in another shelf of a multishelf setup. Communication between the two cards is across 10 Gigabit Ethernet interconnection interface using Ethernet packets. The Inter link (ILK) trunk or internal pathcord must be provisioned on both the cards. This link is used to transmit protection switching messages and data. For information on how to provision ILK or internal patchcords, refer Cisco ONS 15454 DWDM Procedure Guide. Note With 1+1 protection mechanisms, the switch time of a copper SFP is 1 second. With 1+1 protection, ports on the protect card can be assigned to protect the corresponding ports on the working card. A working card must be paired with a protect card of the same type and number of ports. The protection takes place on the port level, and any number of ports on the protect card can be assigned to protect the corresponding ports on the working card. To make the 1+1 protection scheme fully redundant, enable L2 protection for the entire VLAN ring. This enables Fast Automatic Protection Switch (FAPS). The VLAN configured on the 1+1 port must be configured as protected SVLAN. For information on how to enable FAPS, see Cisco ONS 15454 DWDM Procedure Guide. 1+1 protection can be either revertive or nonrevertive. With nonrevertive 1+1 protection, when a failure occurs and the signal switches from the working card to the protect card, the signal remains on the protect card until it is manually changed. Revertive 1+1 protection automatically switches the signal back to the working card when the working card comes back online. 1+1 protection uses trunk ports to send control traffic between working and protect cards. This trunk port connection is known as ILK trunk ports and can be provisioned via CTC. For information on how to provision an ILK link, see “DLP-G460 Provision an ILK Link” in the Cisco ONS 15454 DWDM Procedure Guide. The standby port can be configured to turn ON or OFF but the traffic coming to and from the standby port will be down. If the laser is ON at the standby port, the other end port (where traffic originates) will not be down in a parallel connection. Traffic is blocked on the standby port. 1+1 protection is bidirectional and nonrevertive by default; revertive switching can be provisioned using CTC. For information on how to provision the cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. 10.12.10.2 Y-Cable Protection The GE_XP and GE_XPE cards support Y-cable protection when they are provisioned in 10 Gigabit Ethernet or 20 Gigabit Ethernet MXP card mode. The 10GE_XP and 10GE_XPE cards support Y-cable protection when they are provisioned in 10GE TXP card mode. Two cards can be joined in a Y-cable protection group with one card assigned as the working card and the other defined as the protection card. This protection mechanism provides redundant bidirectional paths. See the “10.19.1 Y-Cable Protection” section on page 10-139 for more detailed information. The Y-cable protection mechanism is 10-81 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards provisionable and can be set ON or OFF (OFF is the default mode). When a signal fault is detected (LOS, LOF, SD, or SF on the DWDM receiver port in the case of ITU-T G.709 mode) the protection mechanism software automatically switches between paths. Y-cable protection also supports revertive and nonrevertive mode. 10.12.10.3 Layer 2 Over DWDM Protection When the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards are in L2-over-DWDM card mode, protection is handled by the hardware at the Layer 1 and Layer 2 levels. Fault detection and failure propagation is communicated through the ITU-T G.709 frame overhead bytes. For protected VLANs, traffic is flooded around the 10 Gigabit Ethernet DWDM ring. To set up the Layer 2 protection, you identify a node and the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE port that is to serve as the master node and port for the VLAN ring on the card view Provisioning > Protection tab. If a failure occurs, the node and port are responsible for opening and closing VLAN loops. Note The Forced option in the Protection drop-down list converts all the SVLANs to protected SVLANs irrespective of the SVLAN protection configuration in the SVLAN database. This is applicable to a point-to-point linear topology. The SVLAN protection must be forced to move all SVLANs, including protected and unprotected SVLANs, to the protect path irrespective of provisioned SVLAN attributes. A FAPS switchover happens in the following failure scenarios: • DWDM line failures caused by a fiber cut • Unidirectional failure in the DWDM network caused by a fiber cut • Fiber pull on the master card trunk port followed by a hard reset on the master card • Hard reset on the master card • Hard reset on the slave card • An OTN failure is detected (LOS, OTUK-LOF, OTUK-LOM, OTUK-LOM, OTUK-SF, or OTUK-BDI on the DWDM receiver port in the case of ITU-T G.709 mode) • Trunk ports are moved to OOS,DSBLD (Locked,disabled) state • Improper removal of XFPs A FAPS switchover does not happen in the following scenarios: • Slave card trunk port in OOS,DSBLD (Locked,disabled) state followed by a hard reset of the slave card • OTN alarms raised on the slave card trunk port followed by a hard reset of the slave card 10.12.11 IGMP Snooping As networks increase in size, multicast routing becomes critically important as a means to determine which segments require multicast traffic and which do not. IP multicasting allows IP traffic to be propagated from one source to a number of destinations, or from many sources to many destinations. Rather than sending one packet to each destination, one packet is sent to the multicast group identified by a single IP destination group address. GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can learn upto a maximum of 1024 multicast groups. This includes groups on all the VLANs. Internet Group Management Protocol (IGMP) snooping restricts the flooding of multicast traffic by forwarding multicast traffic to those interfaces where a multicast device is present.10-82 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards When the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card receives an IGMP leave group message from a host, it removes the host port from the multicast forwarding table after generating group specific queries to ensure that no other hosts interested in traffic for the particular group are present on that port. Even in the absence of any “leave” message, the cards have a timeout mechanism to update the group table with the latest information. After a card relays IGMP queries from the multicast router, it deletes entries periodically if it does not receive any IGMP membership reports from the multicast clients. In a multicast router, general queries are sent on a VLAN when Protocol Independent Multicast (PIM) is enabled on the VLAN. The GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card forwards queries to all ports belonging to the VLAN. All hosts interested in this multicast traffic send Join requests and are added to the forwarding table entry. The Join requests are forwarded only to router ports. By default, these router ports are learned dynamically. However, they can also be statically configured at the port level in which case the static configuration overrides dynamic learning. For information on interaction of IGMP with other protocols, see the 10.12.2 Protocol Compatibility list. 10.12.11.1 IGMP Snooping Guidelines and Restrictions The following guidelines and restrictions apply to IGMP snooping on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards: • IGMP snooping V2 is supported as specified in RFC 4541. • IGMP snooping V3 is not supported and the packets are flooded in the SVLAN. • Layer 2 multicast groups learned through IGMP snooping are dynamic. • GE_XP and 10GE_XP cards support IGMP snooping on 128 stacked VLANs and GE_XPE and 10GE_XPE cards support up to 256 stacked VLANs that are enabled. • IGMP snooping can be configured per SVLAN or CVLAN. By default, IGMP snooping is disabled on all SVLANs and CVLANs. • IGMP snooping on CVLAN is enabled only when: – MVR is enabled. – UNI ports are in selective add and selective translate modes. For each UNI port, a CVLAN must be specified for which IGMP snooping is to be enabled. • IGMP snooping can be enabled only on one CVLAN per port. If you enable IGMP snooping on CVLAN, you cannot enable IGMP snooping on the associated SVLAN and vice versa. The number of VLANs that can be enabled for IGMP snooping cannot exceed 128. • When IGMP snooping is enabled on double-tagged packets, CVLAN has to be the same on all ports attached to the same SVLAN. • When IGMP snooping is working with the Fast Automatic Protection Switch (FAPS) in a ring-based setup, it is advisable to configure all NNI ports as static router ports. This minimizes the multicast traffic hit when a FAPS switchover occurs. The following conditions are raised from IGMP snooping at the card: • MCAST-MAC-TABLE-FULL—This condition is raised when the multicast table is full and a new join request is received. This table is cleared when at least one entry gets cleared from the multicast table after the alarm is raised. • MCAST-MAC-ALIASING—This condition is raised when there are multiple L3 addresses that map to the same L2 address in a VLAN. This is a transient condition.10-83 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards For more information on severity level of these conditions and procedure to clear these alarms, refer to the Cisco ONS 15454 Troubleshooting Guide. 10.12.11.2 Fast-Leave Processing Note Fast-Leave processing is also known as Immediate-Leave. IGMP snooping Fast-Leave processing allows the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE to remove an interface that sends a leave message from the forwarding table without first sending group specific queries to the interface. When you enable IGMP Fast-Leave processing, the card immediately removes a port from the IP multicast group when it detects an IGMP, version 2 (IGMPv2) leave message on that port. 10.12.11.3 Static Router Port Configuration Multicast-capable ports are added to the forwarding table for every IP multicast entry. The card learns of such ports through the PIM method. 10.12.11.4 Report Suppression Report suppression is used to avoid a storm of responses to an IGMP query. When this feature is enabled, a single IGMP report is sent to each multicast group in response to a single query. Whenever an IGMP snooping report is received, report suppression happens if the report suppression timer is running. The Report suppression timer is started when the first report is received for a general query. Then this time is set to the response time specified in general query. 10.12.11.5 IGMP Statistics and Counters An entry in a counter contains multicasting statistical information for the IGMP snooping capable GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. It provides statistical information about IGMP messages that have been transmitted and received. IGMP statistics and counters can be viewed via CTC from the Performance > Ether Ports > Statistics tab. This information can be stored in the following counters: • cisTxGeneralQueries—Number of general queries transmitted through an interface. • cisTxGroupSpecificQueries—Total group specific queries transmitted through an interface. • cisTxReports—Total membership reports transmitted through an interface. • cisTxLeaves—Total Leave messages transmitted through an interface. • cisRxGeneralQueries—Total general queries received at an interface. • cisRxGroupSpecificQueries—Total Group Specific Queries received at an interface. • cisRxReports—Total Membership Reports received at an interface. • cisRxLeaves—Total Leave messages received at an interface. • cisRxValidPackets—Total valid IGMP packets received at an interface. • cisRxInvalidPackets—Total number of packets that are not valid IGMP messages received at an interface.10-84 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.12 Multicast VLAN Registration Multicast VLAN Registration (MVR) is designed for applications using wide-scale deployment of multicast traffic across an Ethernet-ring-based service provider network (for example, the broadcast of multiple television channels over a service-provider network). MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. It allows the single multicast VLAN to be shared in the network while subscribers remain in separate VLANs. MVR provides the ability to continuously send multicast streams in the multicast VLAN, but to isolate the streams from the subscriber VLANs for bandwidth and security reasons. MVR assumes that subscriber ports subscribe and unsubscribe (“Join” and “Leave”) these multicast streams by sending out IGMP Join and Leave messages. These messages can originate from an IGMP version-2-compatible host with an Ethernet connection. MVR operates on the underlying mechanism of IGMP snooping. MVR works only when IGMP snooping is enabled. The card identifies the MVR IP multicast streams and their associated MAC addresses in the card forwarding table, intercepts the IGMP messages, and modifies the forwarding table to include or remove the subscriber as a receiver of the multicast stream, even though the receivers is in a different VLAN than the source. This forwarding behavior selectively allows traffic to cross between different VLANs. Note When MVR is configured, the port facing the router must be configured as NNI in order to allow the router to generate or send multicast stream to the host with the SVLAN. If router port is configured as UNI, the MVR will not work properly. 10.12.13 MAC Address Learning The GE_XPE and 10 GE_XPE cards support 32K MAC addresses. MAC address learning can be enabled or disabled per SVLAN on GE_XPE and 10 GE_XPE cards. The cards learn the MAC address of packets they receive on each port and add the MAC address and its associated port number to the MAC address learning table. As stations are added or removed from the network, the GE_XPE and 10 GE_XPE cards update the MAC address learning table, adding new dynamic addresses and aging out those that are currently not in use. MAC address learning can be enabled or disabled per SVLAN. When the configuration is changed from enable to disable, all the related MAC addresses are cleared. The following conditions apply: • If MAC address learning is enabled on per port basis, the MAC address learning is not enabled on all VLANs, but only on VLANs that have MAC address learning enabled. • If per port MAC address learning is disabled then the MAC address learning is disabled on all VLANs, even if it is enabled on some of the VLAN supported by the port. • If the per port MAC address learning is configured on GE-XP and 10 GE-XP cards, before upgrading to GE-XPE or 10 GE-XPE cards, enable MAC address learning per SVLAN. Failing to do so disables MAC address learning. 10.12.14 MAC Address Retrieval MAC addresses learned can be retrieved or cleared on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards provisioned in L2-over-DWDM mode. The MAC addresses can be retrieved using the CTC or TL1 interface.10-85 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards GE_XPE and 10GE_XPE cards support 32K MAC addresses and GE_XP and 10GE_XP cards support 16K MAC addresses. To avoid delay in processing requests, the learned MAC addresses are retrieved using an SVLAN range. The valid SVLAN range is from 1 to 4093. The MAC addresses of the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can also be retrieved. The card MAC addresses are static and are used for troubleshooting activities. One MAC address is assigned to each client, trunk, and CPU ports of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. These internal MAC addresses can be used to determine if the packets received on the far-end node are generated by GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. For MAC address retrieval, the following conditions apply: • The cards must be provisioned in L2-over-DWDM mode. • MAC address learning must be enabled per SVLAN on GE_XPE or 10 GE_XPE cards. • MAC address learning must be enabled per port on GE_XP or 10 GE_XP cards. For information on how to retrieve or clear MAC addresses learned, refer to the “Provision Transponder and Muxponder Cards” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 10.12.15 Link Integrity The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card support end-to-end Ethernet link integrity. This capability is integral to providing an Ethernet private line service and correct operation of Layer 2 and Layer 3 protocols on the attached Ethernet devices. The link integrity feature propagates a trunk fault on all the affected SVLAN circuits in order to squelch the far end client interface. Ethernet-Advanced IP Services (E-AIS) packets are generated on a per-port/SVLAN basis. An E-AIS format is compliant with ITU Y.1731. Note E-AIS packets are marked with a CoS value of 7 (also called .1p bits). Ensure that the network is not overloaded and there is sufficient bandwidth for this queue in order to avoid packet drops. When link integrity is enabled on a per-port SVLAN basis, E-AIS packets are generated when the following alarms are raised; • LOS-P • OTUKLOF/LOM • SIGLOSS • SYNCHLOSS • OOS • PPM not present When link integrity is enabled, GE_XP and 10 GE_XP card supports up to128 SVLANs and GE_XPE, 10 GE_XPE can support up to 256 SVLANs. 10.12.16 Ingress CoS Ingress CoS functionality enables differentiated services across the GE_XPE and 10GE_XPE cards. A wide range of networking requirements can be provisioned by specifying the class of service applicable to each transmitted traffic. 10-86 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards When a CVLAN is configured as ingress CoS, the per-port settings are not considered. A maximum of 128 CVLAN and CoS relationships can be configured. 10.12.17 CVLAN Rate Limiting CVLAN rate limiting is supported on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. CVLAN rate limiting is supported for QinQ service in selective add mode. The following limitations and restrictions apply to CVLAN rate limiting: • CVLAN rate limiting is not supported for the following service types: – Selective translate mode – Transparent mode – Selective double add mode – Selective translate add mode – Untagged packets – CVLAN range – Services associated with the channel group • CVLAN rate limiting and SVLAN rate limiting cannot be applied to the same service instance. • Pseudo-IOS command line interface (PCLI) is not supported for CVLAN rate limiting. • A VLAN profile with Link Integrity option enabled cannot be used to perform CVLAN rate limiting. • On GE_XP and 10 GE_XP cards, CVLAN rate limiting can be applied to up to 128 services. However, the number of provisionable CVLAN rate limiting service instances is equal to 192 minus the number of SVLAN rate limiting service instances present on the card (subject to a minimum of 64 CVLAN rate limiting service instances). • On GE_XPE and 10 GE_XPE cards, CVLAN rate limiting can be applied to up to 256 services. However, the number of provisionable CVLAN rate limiting service instances is equal to 384 minus the number of SVLAN rate limiting service instances present on the card (subject to a minimum of 128 CVLAN rate limiting service instances). 10.12.18 DSCP to CoS Mapping DSCP to CoS mapping can be configured for each port. You can configure the CoS of the outer VLAN based on the incoming DSCP bits. This feature is supported only on GE_XPE and 10GE_XPE cards. PCLI is not supported for DSCP to CoS mapping. DSCP to CoS mapping is supported for the following service types: – Selectice add mode – Selective translate mode – Transparent mode – Selective double add mode – Selective translate add mode – Untagged packets – CVLAN range10-87 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards – Services associated with the channel group 10.12.19 Link Aggregation Control Protocol Link Aggregation Control Protocol (LACP) is part of the IEEE802.3ad standard that allows you to bundle several physical ports together to form a single logical channel. LACP allows a network device such as a switch to negotiate an automatic bundling of links by sending LACP packets to the peer device. LACP allows you to form a single Layer 2 link automatically from two or more Ethernet links. This protocol ensures that both ends of the Ethernet link are functional and agree to be members of the aggregation group before the link is added to the group. LACP must be enabled at both ends of the link to be operational. For more information on LACP, refer to the IEEE802.3ad standard. For information on interaction of LACP with other protocols, see the 10.12.2 Protocol Compatibility list. 10.12.19.1 Advantages of LACP LACP provides the following advantages: • High-speed network that transfers more data than any single port or device. • High reliability and redundancy. If a port fails, traffic continues on the remaining ports. • Hashing algorithm that allows to apply load balancing policies on the bundled ports. 10.12.19.2 Functions of LACP LACP performs the following functions in the system: • Maintains configuration information to control aggregation. • Exchanges configuration information with other peer devices. • Attaches or detaches ports from the link aggregation group based on the exchanged configuration information. • Enables data flow when both sides of the aggregation group are synchronized. 10.12.19.3 Modes of LACP LACP can be configured in the following modes: • On — Default. In this mode, the ports do not exchange LACP packets with the partner ports. • Active — In this mode, the ports send LACP packets at regular intervals to the partner ports. • Passive — In this mode, the ports do not send LACP packets until the partner sends LACP packets. After receiving the LACP packets from the partner ports, the ports send LACP packets. 10.12.19.4 Parameters of LACP LACP uses the following parameters to control aggregation: • System Identifier—A unique identification assigned to each system. It is the concatenation of the system priority and a globally administered individual MAC address.10-88 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards • Port Identification—A unique identifier for each physical port in the system. It is the concatenation of the port priority and the port number. • Port Capability Identification—An integer, called a key, that identifies the capability of one port to aggregate with another port. There are two types of keys: – Administrative key—The network administrator configures this key. – Operational key—The LACP assigns this key to a port, based on its aggregation capability. • Aggregation Identifier—A unique integer that is assigned to each aggregator and is used for identification within the system. 10.12.19.5 Unicast Hashing Schemes LACP supports the following unicast hashing schemes: • Ucast SA VLAN Incoming Port • Ucast DA VLAN Incoming Port • Ucast SA DA VLAN Incoming port • Ucast Src IP TCP UDP • Ucast Dst IP TCP UDP • Ucast Src Dst IP TCP UDP Note Unicast hashing schemes apply to unicast traffic streams only when the destination MAC address is already learned by the card. Hence, MAC learning must be enabled to support load balancing as per the configured hashing scheme. If the destination MAC address is not learned, the hashing scheme is Ucast Src Dst IP TCP UDP. 10.12.19.6 Supported LACP Features The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards support the following LACP features as per the IEEE802.3ad standard: • DLP-G611 Create a Channel Group Using CTC • DLP-G612 Modify the Parameters of the Channel Group Using CTC • DLP-G613 Add or Remove Ports to or from an Existing Channel Group Using CTC • DLP-G614 Delete a Channel Group Using CTC See the Cisco ONS 15454 DWDM Procedure Guide for information on these procedures. 10.12.19.7 LACP Limitations and Restrictions The LACP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions: • Hot standby link state is not supported on the channel group. • Marker protocol generator is not supported. • ALS cannot be configured on the channel group. • Loopback configuration cannot be applied on the channel group.10-89 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.20 Ethernet Connectivity Fault Management Ethernet Connectivity Fault Management (CFM) is part of the IEEE 802.1ag standard. The Ethernet CFM is an end-to-end per service instance that supports the Ethernet layer Operations, Administration, and Management (OAM) protocol. It includes proactive connectivity monitoring, link trace on a per service basis, fault verification, and fault isolation for large Ethernet metropolitan-area networks (MANs) and WANs. CFM is disabled on the card by default. CFM is enabled on all the ports by default. For more information on CFM, refer to the IEEE 802.1ag standard. For information on interaction of CFM with other protocols, see the 10.12.2 Protocol Compatibility list. The following sections contain conceptual information about Ethernet CFM. 10.12.20.1 Maintenance Domain A maintenance domain is an administrative domain that manages and administers a network. You can assign a unique maintenance level (from 0 to 7) to define the hierarchical relationship between domains. The larger the domain, the higher the maintenance level for that domain. For example, a service provider domain would be larger than an operator domain and might have a maintenance level of 6, while the operator domain maintenance level would be 3 or 4. Maintenance domains cannot intersect or overlap because that would require more than one entity to manage it, which is not allowed. Domains can touch or nest if the outer domain has a higher maintenance level than the nested domain. Maintenance levels of nesting domains must be communicated among the administrating organizations. For example, one approach would be to have the service provider assign maintenance levels to operators. The CFM protocol supports up to eight maintenance domains on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. 10.12.20.2 Maintenance Association A maintenance association identifies a service within the maintenance domain. You can have any number of maintenance associations within each maintenance domain. The CFM protocol supports up to 1500 maintenance associations on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. Note Each maintenance association is mapped to a maintenance domain. This mapping is done to configure a Maintenance End Point (MEP). The CFM protocol supports up to 1000 mappings on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. 10.12.20.3 Maintenance End Points Maintenance End Points (MEPs) reside at the edge of the maintenance domain and are active elements of the Ethernet CFM. MEPs transmit Continuity Check messages at periodic intervals and receive similar messages from other MEPs within a domain. MEPs also transmit Loopback and Traceroute messages at the request of the administrator. MEPs confine CFM messages within the boundary of a maintenance domain through the maintenance level. There are two types of MEPs: • Up (Inwards, towards the bridge) • Down (Outwards, towards the wire).10-90 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards You can create up to 255 MEPs and MIPs together on GE_XP and 10GE_XP cards. You can create up to 500 MEPs and MIPs together on GE_XPE and 10GE_XPE cards. The MEP continuity check database (CCDB) stores information that is received from other MEPs in the maintenance domain. The card can store up to 4000 MEP CCDB entries. 10.12.20.4 Maintenance Intermediate Points Maintenance Intermediate Points (MIPs) are internal to the maintenance domain and are passive elements of the Ethernet CFM. They store information received from MEPs and respond to Linktrace and Loopback CFM messages. MIPs forward CFM frames received from MEPs and other MIPs, drop all CFM frames at a lower level, and forward all CFM frames at a higher level. You can create up to 255 MEPs and MIPs together on GE_XP and 10GE_XP cards. You can create up to 500 MEPs and MIPs together on GE_XPE and 10GE_XPE cards. The MIP CCDB maintains the information received for all MEPs in the maintenance domain. The card can store up to 4000 MIP CCDB entries. 10.12.20.5 CFM Messages The Ethernet CFM on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards supports the following messages: • Continuity Check—These messages are exchanged periodically among MEPs. They allow MEPs to discover other MEPs within a domain and allow MIPs to discover MEPs. These messages are confined to a domain. • Loopback—These messages are unicast messages that a MEP transmits, at the request of an administrator, to verify connectivity to a specific maintenance point. A reply to a loopback message indicates whether a destination is reachable. • Traceroute—These messages are multicast messages that a MEP transmits, at the request of an administrator, to track the path to a destination MEP. 10.12.20.6 Supported CFM Features The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards support the following Ethernet CFM features as per the IEEE 802.1ag standard: • DLP-G621 Enable or Disable CFM on the Card Using CTC • DLP-G622 Enable or Disable CFM for Each Port Using CTC • DLP-G623 Create a Maintenance Domain Profile Using CTC • DLP-G625 Create a Maintenance Association Profile Using CTC • DLP-G628 Map a Maintenance Association Profile to a Maintenance Domain Profile Using CTC • DLP-G629 Create a MEP Using CTC • DLP-G631 Create a MIP Using CTC • DLP-G633 Ping MEP Using CTC • DLP-G634 Traceroute MEP Using CTC See the Cisco ONS 15454 DWDM Procedure Guide for information on these procedures.10-91 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.20.7 CFM Limitations and Restrictions The CFM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions: • CFM is not supported on channel groups. • CFM is not enabled on ptotected ports running REP, FAPS, and 1+1. • Y.1731 enhancements including AIS, LCK, and performance monitoring messages along with CFM are not supported. • IEEE CFM MIB is not supported. • L1 and CFM are mutually exclusive on a SVLAN because LI and CFM use the same MAC address. • MAC security and CFM are mutually exclusive on the card due to hardware resource constraints. 10.12.21 Ethernet OAM The Ethernet OAM protocol is part of the IEEE 802.3ah standard and is used for installing, monitoring, and troubleshooting Ethernet MANs and Ethernet WANs. This protocol relies on an optional sublayer in the data link layer of the OSI model. The Ethernet OAM protocol was developed for Ethernet in the First Mile (EFM) applications. The terms Ethernet OAM and EFM are interchangeably used and both mean the same. Normal link operation does not require Ethernet OAM. You can implement Ethernet OAM on any full-duplex point-to-point or emulated point-to-point Ethernet link for a network or part of a network (specified interfaces). OAM frames, called OAM Protocol Data Units (OAM PDUs), use the slow protocol destination MAC address 0180.c200.0002. OAM PDUs are intercepted by the MAC sublayer and cannot propagate beyond a single hop within an Ethernet network. Ethernet OAM is disabled on all interfaces by default. When Ethernet OAM is enabled on an interface, link monitoring is automatically turned on. For more information on Ethernet OAM protocol, refer to IEEE 802.3ah standard. For information on interaction of Ethernet OAM with other protocols, see the 10.12.2 Protocol Compatibility list. 10.12.21.1 Components of the Ethernet OAM Ethernet OAM consists of two major components, the OAM Client and the OAM Sublayer. 10.12.21.1.1 OAM Client The OAM client establishes and manages the Ethernet OAM on a link. The OAM client also enables and configures the OAM sublayer. During the OAM discovery phase, the OAM client monitors the OAM PDUs received from the remote peer and enables OAM functionality. After the discovery phase, the OAM client manages the rules of response to OAM PDUs and the OAM remote loopback mode. 10.12.21.1.2 OAM Sublayer The OAM sublayer presents two standard IEEE 802.3 MAC service interfaces: • One interface facing toward the superior sublayers, which include the MAC client (or link aggregation). • Other interface facing toward the subordinate MAC control sublayer.10-92 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards The OAM sublayer provides a dedicated interface for passing OAM control information and OAM PDUs to and from the client. 10.12.21.2 Benefits of the Ethernet OAM Ethernet OAM provides the following benefits: • Competitive advantage for service providers • Standardized mechanism to monitor the health of a link and perform diagnostics 10.12.21.3 Features of the Ethernet OAM The Ethernet OAM protocol has the following OAM features: • Discovery—Identifies devices in the network and their OAM capabilities. The Discovery feature uses periodic OAM PDUs to advertise the OAM mode, configuration, and capabilities. An optional phase allows the local station to accept or reject the configuration of the peer OAM entity. • Link Monitoring—Detects and indicates link faults under a variety of conditions. It uses the event notification OAM PDU to notify the remote OAM device when it detects problems on the link. • Remote Failure Indication—Allows an OAM entity to convey the failure conditions to its peer through specific flags in the OAM PDU. • Remote Loopback—Ensures link quality with a remote peer during installation or troubleshooting. 10.12.21.4 Ethernet OAM Supported Features The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards support the following Ethernet OAM features as per the IEEE 802.3ah standard: • DLP-G639 Enable or Disable EFM for Each Port Using CTC • DLP-G640 Configure EFM Parameters Using CTC • DLP-G641 Configure EFM Link Monitoring Parameters Using CTC • DLP-G642 Enable Remote Loopback for Each Port Using CTC See the Cisco ONS 15454 DWDM Procedure Guide for information on these procedures. 10.12.21.5 Ethernet OAM Limitations and Restrictions The Ethernet OAM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions: • CFM, REP, link integrity, LACP, FAPS, IGMP on SVLAN and L2 1+1 protection are not supported with EFM. • IEEE EFM MIB is not supported. • EFM cannot be enabled or disabled at the card level. • Unidirectional functionality is not supported. • Errored Symbol Period, Rx CRC errors, Tx CRC errors are not supported. • OAM PDUs are limited to 1 frame per second. • Dying Gasp and critical events are not supported.10-93 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Note Dying Gasp RFI is not generated on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. However, if the peer device sends a dying gasp RFI, the card detects it and raises an alarm. 10.12.22 Resilient Ethernet Protocol The Resilient Ethernet Protocol (REP) is a protocol used to control network loops, handle link failures, and improve convergence time. REP performs the following tasks: • Controls a group of ports connected in a segment. • Ensures that the segment does not create any bridging loops. • Responds to link failures within the segment. • Supports VLAN load balancing. For information on interaction of REP with other protocols, see the 10.12.2 Protocol Compatibility list. 10.12.22.1 REP Segments A REP segment is a chain of ports connected to each other and configured with a segment ID. Each segment consists of regular segment ports and two edge ports. A GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card can have up to 2 ports that belong to the same segment, and each segment port can have only one external neighbor port. A segment protects only against a single link failure. Any more failures within the segment result in loss of connectivity. 10.12.22.2 Characteristics of REP Segments REP segments have the following characteristics: • If all the ports in the segment are operational, one port blocks traffic for each VLAN. If VLAN load balancing is configured, two ports in the segment control the blocked state of VLANs. • If any port in the segment is not operational, all the other operational ports forward traffic on all VLANs to ensure connectivity. • In case of a link failure, the alternate ports are immediately unblocked. When the failed link comes up, a logically blocked port per VLAN is selected with minimal disruption to the network. 10.12.22.3 REP Port States Ports in REP segments take one of three roles or states: Failed, Open, or Alternate. • A port configured as a regular segment port starts as a failed port. • When the neighbor adjacencies are determined, the port transitions to the alternate port state, blocking all the VLANs on the interface. Blocked port negotiations occur and when the segment settles, one blocked port remains in the alternate role and all the other ports become open ports. • When a failure occurs in a link, all the ports move to the failed state. When the alternate port receives the failure notification, it changes to the open state, forwarding all VLANs.10-94 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 10.12.22.4 Link Adjacency Each segment port creates an adjacency with its immediate neighbor. Link failures are detected and acted upon locally. If a port detects a problem with its neighbor, the port declares itself non-operational and REP converges to a new topology. REP Link Status Layer (LSL) detects its neighbor port and establishes connectivity within the segment. All VLANs are blocked on an interface until the neighbor port is identified. After the neighbor port is identified, REP determines the neighbor port that must be the alternate port and the ports that must forward traffic. Each port in a segment has a unique port ID. When a segment port starts, the LSL layer sends packets that include the segment ID and the port ID. A segment port does not become operational if the following conditions are satisfied: • No neighbor port has the same segment ID or more than one neighbor port has the same segment ID. • The neighbor port does not acknowledge the local port as a peer. 10.12.22.5 Fast Reconvergence REP runs on a physical link and not on per VLAN. Only one hello message is required for all VLANs that reduces the load on the protocol. REP Hardware Flood Layer (HFL) is a transmission mechanism that floods packets in hardware on an admin VLAN. HFL avoids the delay that is caused by relaying messages in software. HFLis used for fast reconvergence in the order of 50 to 200 milliseconds. 10.12.22.6 VLAN Load Balancing You must configure two edge ports in the segment for VLAN load balancing. One edge port in the REP segment acts as the primary edge port; the other edge port as the secondary edge port. The primary edge port always participates in VLAN load balancing in the segment. VLAN load balancing is achieved by blocking certain VLANs at a configured alternate port and all the other VLANs at the primary edge port. 10.12.22.7 REP Configuration Sequence You must perform the following tasks in sequence to configure REP: • Configure the REP administrative VLAN or use the default VLAN 1. The range of REP admin VLAN is 1 to 4093. VLAN 4094 is not allowed. • Add ports to the segment in interface configuration mode. • Enable REP on ports and assign a segment ID to it. REP is disabled on all ports by default. The range of segment ID is 1 to 1024. • Configure two edge ports in the segment; one port as the primary edge port and the other as the secondary edge port. • If you configure two ports in a segment as the primary edge port, for example, ports on different switches, REP selects one of the ports to serve as the primary edge port based on port priority. The Primary option is enabled only on edge ports. • Configure the primary edge port to send segment topology change notifications (STCNs) and VLAN load balancing to another port or to other segments. STCNs and VLAN load balancing configurations are enabled only for edge ports.10-95 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Note A port can belong to only one segment. Only two ports can belong to the same segment. Both the ports must be either regular ports or edge ports. However, if the No-neighbor port is configured, one port can be an edge port and another port can be a regular port. 10.12.22.8 REP Supported Interfaces REP supports the following interfaces: • REP is supported on client (UNI) and trunk (NNI) ports. • Enabling REP on client ports allows protection at the access or aggregation layer when the cards are connected to the L2 network. • Enabling REP on trunk ports allows protection at the edge layer when the cards are connected in a ring. 10.12.22.9 REP Limitations and Restrictions The REP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions: • Fast re-convergence and VLAN load balancing are not supported on UNI ports in transparent mode. • Native VLAN is not supported. • CFM, EFM, link integrity, LACP, FAPS, and L2 1+1 protection are not supported on ports that are configured as part of REP segment and vice versa. • NNI ports cannot be configured as the primary edge port or blocking port at the access or aggregation layer. • Only three REP segments can be configured on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. • Consider the following configuration: More than one REP closed segment is configured on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards and the same HFL admin VLAN is enabled on the switches. If two different segments are configured on more than one common switch, the following consequences happen. – Layer 1 loop – Flooding of HFL packets across segments if one REP segment fails – Segment goes down due to LSL time out even if the segment does not have faults Hence, it is recommended not to configure two different segments on more than one common switch. • Consider the following configuration: – VLAN Load Balancing is configured on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards by specifying the VLB preempt delay. – Primary and secondary edge ports are configured on the same switch. – HFL or LSL is activated. This configuration leads to high convergence time during manual premption, VLB activation, and deactivation (400 to 700 milliseconds).10-96 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card 10.13 ADM-10G Card The ADM-10G card operates on ONS 15454 SONET, ONS 15454 SDH, ONS 15454 M2, ONS 15454 M6, and DWDM networks to carry optical signals and Gigabit Ethernet signals over DWDM wavelengths for transport. The card aggregates lower bit-rate client SONET or SDH signals (OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or Gigabit Ethernet) onto a C-band tunable DWDM trunk operating at a higher OC-192/STM-64 rate. In a DWDM network, the ADM-10G card transports traffic over DWDM by mapping Gigabit Ethernet and SONET or SDH circuits onto the same wavelength with multiple protection options. You can install and provision the ADM-10G card in a linear configuration in: • Slots 1 to 5 and 12 to 16 in standard and high-density ONS 15454 ANSI shelves (15454-SA-ANSI or 15454-SA-HD), the ETSI ONS 15454 standard shelf assembly, or the ONS 15454 ETSI high-density shelf assembly • Slot 2 in ONS 15454 M2 chassis • Slots 2 to 6 in ONS 15454 M6 chassis Caution Fan-tray assembly 15454E-CC-FTA (ETSI shelf)/15454-CC-FTA (ANSI shelf) must be installed in a shelf where the ADM-10G card is installed. The card is compliant with ITU-T G.825 and ITU-T G.783 for SDH signals. It supports concatenated and nonconcatenated AU-4 mapped STM-1, STM-4, and STM-16 signals as specified in ITU-T G.707. The card also complies with Section 5.6 of Telcordia GR-253-CORE and supports synchronous transport signal (STS) mapped OC-3, OC-12, and OC-48 signals as specified in the standard. The client SFP and trunk XFP are compliant with interface requirements in Telcordia GR-253-CORE, ITU-T G.957 and/or ITU-T G.959.1, and IEEE 802.3. 10.13.1 Key Features The ADM-10G card has the following high-level features: • Operates with the TCC2, TCC2P, TCC3, TNC, or TSC. • Interoperable with TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10EX_C, and OTU2_XP cards. • Has built-in OC-192/STM-64 add/drop multiplexing function including client, trunk, and STS cross-connect. • Supports both single-card and double-card (ADM-10G peer group) configuration. • Supports path protection/SNCP on client and trunk ports for both single-card and double-card configuration. The card does not support path protection/SNCP between a client port and a trunk port. Path protection/SNCP is supported only between two client ports or two trunk ports. • Supports 1+1 protection on client ports for double-card configuration only. • Supports SONET, SDH, and Gigabit Ethernet protocols on client SFPs. • Supports XFP DWDM trunk interface single wavelengths. • Returns zero bit errors when a TCC2/TCC2P/TCC3/TNC/TSC card switches from active to standby or when manual or forced protection switches occur. • Has 16 SFP-based client interfaces (gray, colored, coarse wavelength division multiplexing (CWDM), and DWDM optics available).10-97 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card • Supports STM1, STM4, STM16, and Gigabit Ethernet client signals (8 Gigabit Ethernet maximum). • Has one XFP-based trunk interface supporting E-FEC/FEC and ITU-T G.709 for double-card configuration. • Has two XFP-based trunk interface supporting E-FEC/FEC and ITU-T G.709 for single-card configuration. • Has two SR XFP interlink interfaces supporting redundancy connection with protection board and pass-through traffic for double-card configuration. • Supports frame-mapped generic framing procedure (GFP-F) and LEX mapping for Ethernet over SONET or SDH. • Can be installed or pulled from operation, in any slot, without impacting other service cards in the shelf. • Supports client to client hairpinning, that is, creation of circuits between two client ports for both single-card and double-card configuration. See the “10.13.11 Circuit Provisioning” section on page 10-104 for more detailed information. 10.13.2 ADM-10G POS Encapsulation, Framing, and CRC The ADM-10G card supports Cisco EoS LEX (LEX) and generic framing procedure framing (GFP-F) encapsulation on 8 POS ports corresponding to 8 GigE ports (Port 1 to Port 8) in both single-card and double-card (ADM-10G peer group) configuration. You can provision framing on the ADM-10G card as either the default GFP-F or LEX framing. With GFP-F framing, you can configure a 32-bit cyclic redundancy check (CRC) or none (no CRC) (the default). LEX framing supports 16-bit or 32-bit CRC configuration. The framing type cannot be changed when there is a circuit on the port. On the CTC, navigate to card view and click the Provisioning > Line> Ethernet Tab. To see the various parameters that can be configured on the ethernet ports, see “CTC Display of ethernet Port Provisioning Status”. Parameters such as, admin state, service state, framing type, CRC, MTU and soak time for a port can be configured. It is possible to create an end-to-end circuit between equipment supporting different kinds of encapsulation (for example, LEX on one side and GFP-F on other side). But, under such circumstances, traffic does not pass through, and an alarm is raised if there is a mismatch. 10.13.2.1 POS Overview Ethernet data packets need to be framed and encapsulated into a SONET/SDH frame for transport across the SONET/SDH network. This framing and encapsulation process is known as packet over SONET/SDH (POS). The Ethernet frame comes into the ADM-10G card on a standard Gigabit Ethernet port and is processed through the card’s framing mechanism and encapsulated into a POS frame. When the POS frame exits, the ADM-10G card is in a POS circuit, and this circuit is treated as any other SONET circuit (STS) or SDH circuit (VC) in the ONS node. It is cross-connected and rides the SONET/SDH signal out the port of an optical card and across the SONET/SDH network. The destination of the POS circuit is a card or a device that supports the POS interface. Data packets in the destination card frames are removed and processed into ethernet frames. The Ethernet frames are then sent to a standard Ethernet port of the card and transmitted onto an Ethernet network.10-98 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card 10.13.2.2 POS Framing Modes A POS framing mode is the type of framing mechanism employed by the ADM-10G card to frame and encapsulate data packets into a POS signal. These data packets were originally encapsulated in Ethernet frames that entered the standard Gigabit Ethernet interface of the ADM-10G card. 10.13.2.2.1 GFP-F Framing The GFP-F framing represent standard mapped Ethernet over GFP-F according to ITU-T G.7041. GFP-F defines a standard-based mapping of different types of services onto SONET/SDH. GFP-F maps one variable length data packet onto one GFP packet. GFP-F comprises of common functions and payload specific functions. Common functions are those shared by all payloads. Payload-specific functions are different depending on the payload type. GFP-F is detailed in the ITU recommendation G.7041. 10.13.2.2.2 LEX Framing LEX encapsulation is a HDLC frame based Cisco Proprietary protocol, where the field is set to values specified in Internet Engineering Task Force (IETF) RFC 1841. HDLC is one of the most popular Layer 2 protocols. The HDLC frame uses the zero insertion/deletion process (commonly known as bit stuffing) to ensure that the bit pattern of the delimiter flag does not occur in the fields between flags. The HDLC frame is synchronous and therefore relies on the physical layer to provide a method of clocking and synchronizing the transmission and reception of frames. The HDLC framing mechanism is detailed in the IETF’s RFC 1662, “PPP in HDLC-like Framing.” 10.13.2.3 GFP Interoperability The ADM-10G card defaults to GFP-F encapsulation that is compliant with ITU-T G.7041. This mode allows the card to operate with ONS 15310-CL, ONS 15310-MA, ONS 15310-MA SDH, or ONS 15454 data cards (for example, ONS 15454 CE100T-8 or ML1000-2 cards). GFP encapsulation also allows the ADM-10G card to interoperate with other vendors Gigabit Ethernet interfaces that adhere to the ITU-T G.7041 standard. 10.13.2.4 LEX Interoperability The LEX encapsulation is compliant with RFC 1841. This mode allows the card to operate with ONS 15310-CL, ONS 15310-MA, ONS 15310-MA SDH, or ONS 15454 data cards (for example, G1000-4/G1K-4 cards, CE-1000-4, ONS 15454 CE100T-8 or ML1000-2 cards). 10.13.3 Faceplate Figure 10-31 shows the ADM-10G card faceplate.10-99 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card Figure 10-31 ADM-10G Card Faceplate and Block Diagram 10.13.4 Port Configuration Rules ADM-10G card client and trunk port capacities are shown in Figure 10-32. FAIL ACT SF ADM-10G ILK1 TRK2/ILK2 TRK1 12 11 10 9 8 7 654 3 2 1 TX RX TX RX TX RX 16 15 14 13 TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX COMPLIES WITH 21 CFR 1040.10 AND 1040.11 EXCEPT FOR DEVIATIONS PURSUANT TO LASER NOTICE No.50, DATED JULY 26, 2001 SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP 10G SONET/SDH framer-pointer processor 10xGE MAC 10G GFP-over SONET/SDH framer 10G SONET/SDH framer-pointer processor 2 G.709-FEC framer 1 G.709-FEC framer 2 XFP DWDM TRUNK ILK XFP ILK XFP VCAT RLDR switch CPU-Core SCL FPGA alarm cpld alarm cpld Main board Daughter card 4 x OC48/STM16 4 x OC3/OC12 or 4 x STM1/STM4 12 x OC3/OC12 or 12 x STM1/STM4 10G SONET/SDH framer-pointer processor 3 10G SONET/SDH framer-pointer processor 4 13 SFP 14 15 16 12 11 10 9 8 7 6 5 4 3 2 1 SFP SFP SFP switch STS-1 cross-connect HAZARD LEVEL 1 250482 19 17 1810-100 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card Figure 10-32 ADM-10G Card Port Capacities Port 17 acts as trunk2 or ILK1 interface based on single-card or double-card configuration. 10.13.5 Client Interfaces The ADM-10G card uses LC optical port connectors and, as shown in Figure 10-32, supports up to 16 SFPs that can be utilized for OC-N/STM-N traffic. Eight of the SFPs can be used for Gigabit Ethernet. The interfaces can support any mix of OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or Gigabit Ethernet of any reach, such as SX, LX, ZX, SR, IR, or LR. The interfaces support a capacity of: • 4 x OC-48/STM-16 • 16 x OC-12/STM-4 • 16 x OC-3/STM-1 • 8 x GE The supported client SFPs and XFPs are: • Gray SFPs – 1000Base-SX SFP 850 nm (ONS-SE-G2F-SX=) – 1000Base-LX SFP 1310 nm (ONS-SE-G2F-LX=) – OC48/STM16 IR1, OC12/STM4 SR1, OC3/STM1 SR1, GE-LX multirate SFP 1310 nm (ONS-SE-Z1=) – OC3/STM1 IR1, OC12/STM4 IR1 multirate SFP 1310 nm (ONS-SI-622-I1=) – OC48/STM16 SR1 SFP 1310 nm (ONS-SI-2G-S1=) – OC48/STM16 IR1 SFP 1310 nm (ONS-SI-2G-I1=) – OC48/STM16, 1550 LR2, SM LC (ONS-SE-2G-L2=) GE G r ay SFP 1 13 14 15 16 ILK1/ TRK2(17) ILK2/ TRK2(18) TRK1 (19) 2 3 4 5 6 7 8 9 10 11 12 GE G r ay SFP GE G r ay SFP GE OC48/OC12/OC3 OC48/OC12/OC3 OC48/OC12/OC3 OC48/OC12/OC3 STM16/STM4/STM1 STM16/STM4/STM1 STM16/STM4/STM1 STM16/STM4/STM1 G r ay SFP G r ay SFP G r ay XFP *Gray/ DWDM XFP D WDM XFP O TU2/OC192/STM64 *OTU2/OC192/STM64 G r ay SFP G r ay SFP G r ay SFP GE G r ay SFP GE G r ay SFP GE G r ay SFP GE G r ay SFP or or or or or or or or or or or or or or or or or or or or G r ay SFP G r ay SFP G r ay SFP OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 OC12/OC3 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 STM4/STM1 G r ay SFP OC192/STM64 243481 *DWDM XFP and OTU2 is supported only when Port 18 is configured as a trunk interface. 10-101 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card • Colored DWDM SFPs – 1000Base-ZX SFP 1550 nm (ONS-SI-GE-ZX=) – OC3/STM1 LR2 SFP 1550 nm (ONS-SI-155-L2=) – OC48/STM16 LR2 SFP 1550 nm (ONS-SI-2G-L2=) – OC48/STM16 SFP (ONS-SC-2G-xx.x) Note xx.x = 28.7 to 60.6. ONS-SC-2G-28.7, ONS-SC-2G-33.4, ONS-SC-2G-41.3, ONS-SC-2G-49.3, and ONS-SC-2G-57.3 are supported from Release 8.5 and later. • CWDM SFPs – OC48/STM16/GE CWDM SFP (ONS-SC-Z3-xxxx) • XFPs – OC-192/STM-64/10GE XFP 1550 nm (ONS-XC-10G-I2) 10.13.6 Interlink Interfaces Two 2R interlink interfaces, called ILK1 (Port 17) and ILK2 (Port 18), are provided for creation of ADM-10G peer groups in double-card configurations. In a single-card configuration, Port 17 (OC-192/STM-64) and Port 18 (OC-192/STM-64 or OTU2 payload) must be configured as trunk interfaces. In a double-card configuration (ADM-10G peer group), Ports 17 and 18 must be configured as ILK1 and ILK2 interfaces, respectively. Physically cabling these ports between two ADM-10G cards, located on the same shelf, allows you to configure them as an ADM-10G peer group.The ILK ports carry 10 Gb of traffic each. The interlink interfaces support STM64 SR1 (ONS-XC-10G-S1=) and 10GE BASE SR (ONS-XC-10G-SR-MM=) XFPs. 10.13.7 DWDM Trunk Interface The ADM-10G card supports OC-192/STM-64 signal transport and ITU-T G.709 digital wrapping according to the ITU-T G.709 standard.The ADM-10G card supports three trunk XFPs: • Two DWDM trunks, and one trunk interface in a single-card configuration. • One DWDM trunk XFP in a double-card configuration. The supported DWDM trunk XFPs are: • 10G DWDM (ONS-XC-10G-xx.x=) (colored XFP) • STM64 SR1 (ONS-XC-10G-S1=) (gray XFP) 10.13.8 Configuration Management When using OC-48/STM-16 traffic, some contiguous port configurations, listed in Table 10-42, are unavailable due to hardware limitations. This limitation does not impact the Gigabit Ethernet payload.10-102 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card Note The ADM-10G card cannot be used in the same shelf with SONET or SDH cross-connect cards. Note The total traffic rate for each trunk cannot exceed OC-192/STM-64 on each ADM-10G card, or for each ADM-10G peer group. Note Gigabit Ethernet is supported on Ports 1 through 8. Ports 9 through Port 12 support only OC-3/STM-1 or OC-12/STM-4. Additionally, the following guidelines apply to the ADM-10G card: • Trunk Port 17 supports OC-192/STM-64. • Trunk Ports 18 and 19 support OC-192/STM-64 and OTU2. • The interlink port supports OC-192/STM-64. • Up to six ADM-10G cards can be installed in one shelf. • Up to 24 ADM-10G cards can be installed per network element (NE) regardless of whether the card is installed in one shelf or in multiple shelves. • The card can be used in all 15454-SA-ANSI and 15454-SA-HD shelves as well as ETSI ONS 15454 standard and high-density shelves. • A lamp test function can be activated from CTC to ensure that all LEDs are functional. • The card can operate as a working protected or working nonprotected card. • In a redundant configuration, an active card hardware or software failure triggers a switch to the standby card. This switch is detected within 10 ms and is completed within 50 ms. • ADM-10G cards support jumbo frames with MTU sizes of 64 to 9,216 bytes; the maximum is 9,216. • After receiving a link or path failure, the ADM-10G card can shut down only the downstream Gigabit Ethernet port. Note In ADM-10G cards, the Gigabit Ethernet port does not support flow control. Table 10-42 OC-48/STM-16 Configuration Limitations OC-48/STM-16 Port Number Ports Restricted from Optical Traffic OC-48/STM-16 on Port 13 No OC-N/STM-N on Port 1 through Port 3 OC-48/STM-16 on Port 14 No OC-N/STM-N on Port 4 through Port 6 OC-48/STM-16 on Port 15 No OC-N/STM-N on Port 7 through Port 9 OC-48/STM-16 on Port 16 No OC-N/STM-N on Port 10 through Port 1210-103 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card 10.13.9 Security The ADM-10G card that an SFP or XFP is plugged into implements the Cisco Standard Security Code Check Algorithm that keys on the vendor ID and serial number. If a pluggable port module (PPM) is plugged into a port on the card but fails the security code check because it is not a Cisco PPM, a minor NON-CISCO-PPM alarm is raised. If a PPM with a nonqualified product ID is plugged into a port on this card—that is, the PPM passes the security code as a Cisco PPM but it has not been qualified for use on the ADM-10G card— a minor UNQUAL-PPM alarm is raised. 10.13.10 Protection The ADM-10G card supports 1+1 and SONET path protection and SDH SNCP protection architectures in compliance with Telcordia GR-253-CORE, Telcordia GR-1400-CORE, and ITU-T G.841 specifications. 10.13.10.1 Circuit Protection Schemes The ADM-10G card supports path protection/SNCP circuits at the STS/VC4 (high order) level and can be configured to switch based on signal degrade calculations. The card supports path protection/SNCP on client and trunk ports for both single-card and double-card configuration. Note The ADM-10G card supports path protection/SNCP between client ports and trunk port 17. The card does not support path protection/SNCP between client ports and trunk ports 18 or 19. The card does not support path protection/SNCP between port 17 and trunk ports 18 and 19. The card allows open-ended path protection/SNCP configurations incorporating other vendor equipment. In an open-ended path protection/SNCP, you can specify one source point and two possible endpoints (or two possible source points and one endpoint) and the legs can include other vendor equipment. The source and endpoints are part of the network discovered by CTC. For detailed information about path protection configurations and SNCPs, refer to the Cisco ONS 15454 Reference Manual. 10.13.10.2 Port Protection Schemes The ADM-10G card supports unidirectional and bidirectional 1+1 APS protection schemes on client ports for double-card configuration (ADM-10G peer group) only. 1+1 APS protection scheme is not supported in single-card configuration. For 1+1 optical client port protection, you can configure the system to use any pair of like facility interfaces that are on different cards of the ADM-10G peer group. For information on optical port protection, refer to the Cisco ONS 15454 Reference Manual. 10.13.10.3 Flexible Protection Mechanism The ADM-10G card can be provisioned as unidirectional path switched ring (UPSR2 ) or subnetwork connection protection (SNCP) on both Trunk and client side. UPSR or SNCP is supported both in single and double card operation. The ADM-10G card supports up to 288 unprotected high-order (HO) cross connect circuits and up to 192 protected (UPSR or SNCP) per card, resulting in 1728/1152 HO cross 10-104 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card connect circuits per shelf. The HO cross connect circuits provide grooming capabilities for STS level connections, such as STS-1, STS-3c, STS-9c, STS-12c, and STS-24c (CCAT or VCAT) with STS1 level granularity. When installed in a typical central-office bay assembly, a shelf can support up to 5178/3456 HO bidirectional cross connect circuits. 10.13.11 Circuit Provisioning The ADM-10G card supports STS circuit provisioning both in single-card and double-card (ADM-10G peer group) configuration. The card allows you to create STS circuits between: • Client and trunk ports • Two trunk ports • Two client ports (client-to-client hairpinning) Note Circuits between two trunk ports are called pass-through circuits. For an ADM-10G card in single-card configuration, if you are creating STS circuits between two client ports, the following limitation must be considered: • Gigabit Ethernet to Gigabit Ethernet connections are not supported. For an ADM-10G card that is part of an ADM-10G peer group, if you are creating STS circuits between two client ports or between client and trunk ports, the following limitations must be considered: • Gigabit Ethernet to Gigabit Ethernet connections are not supported. • Optical channel (OC) to OC, OC to Gigabit Ethernet, and Gigabit Ethernet to OC connections between two peer group cards are supported. Peer group connections use interlink port bandwidth, hence, depending on the availability/fragmentation of the interlink port bandwidth, it may not be possible to create an STS circuit from the Gigabit Ethernet/OC client port to the peer card trunk port. This is because, contiguous STSs (that is, STS-3c, STS-12c, STS-24c, and so on) must be available on the interlink port for circuit creation. Note There are no limitations to create an STS circuit between two trunk ports. 10.13.12 ADM-10G CCAT and VCAT Characteristics The ADM-10G card supports high-order (HO) contiguous concatenation (CCAT) and HO virtual concatenation (VCAT) circuits on 8 GigE ports (Port 1 to Port 8) in both single-card and double-card (ADM-10G peer group) configuration. To enable end-to-end connectivity in a VCAT circuit that traverses through a third-party network, you can use Open-Ended VCAT circuit creation. For more details, refer to the “Create Circuits and Provisionable Patchcords” chapter in the Cisco ONS 15454 Procedure Guide. The ADM-10G card supports flexible non-LCAS VCAT groups (VCGs). With flexible VCGs, the ADM-10G can perform the following operations: 2. 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. Cisco does not recommend using its path protection feature in any particular topological network configuration. 10-105 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card • Add or remove members from groups • Put members into or out of service, which also adds/removes them from the group • Add or remove cross-connect circuits from VCGs Any operation on the VCG member is service effecting (for instance, adding or removing members from the VCG). Adding or removing cross-connect circuits is not service-affecting, if the associated members are not in the group The ADM-10G card allows independent routing and protection preferences for each member of a VCAT circuit. You can also control the amount of VCAT circuit capacity that is fully protected, unprotected, or uses Protection Channel Access (PCA) (when PCA is available). Alarms are supported on a per-member as well as per virtual concatenation group (VCG) basis. The ADM-10G card supports both automatic and manual routing for VCAT circuit, that is, all members are manually or automatically routed. Bidirectional VCAT circuits are symmetric, which means that the same number of members travel in each direction. With automatic routing, you can specify the constraints for individual members; with manual routing, you can select different spans for different members. Two types of automatic and manual routing are available for VCAT members: common fiber routing and split routing. The ADM-10G card supports VCAT common fiber routing and VCAT split fiber (diverse) routing. With VCAT split fiber routing, each member can be routed independently through the SONET or SDH or DWDM network instead of having to follow the same path as required by CCAT and VCAT common fiber routing. This allows a more efficient use of network bandwidth, but the different path lengths and different delays encountered may cause slightly different arrival times for the individual members of the VCG. The VCAT differential delay is this relative arrival time measurement between members of a VCG. The maximum tolerable VCAT split fiber routing differential delay for the ADM-10G card is approximately 55 milliseconds. A loss of alignment alarm is generated if the maximum differential delay supported is exceeded. The differential delay compensation function is automatically enabled when you choose split fiber routing during the CTC circuit configuration process. CCAT and VCAT common fiber routing do not enable or need differential delay support. Caution Protection switches with switching time of less than 60 milliseconds are not guaranteed with the differential delay compensation function enabled. The compensation time is added to the switching time. Note For TL1, EXPBUFFERS parameter must be set to ON in the ENT-VCG command to enable support for split fiber routing. Available Circuit Sizes Table 10-43 and Table 10-44 show the circuit sizes available for the ADM-10G card. Table 10-43 Supported SONET Circuit Sizes of ADM-10G card on ONS 15454 CCAT VCAT High Order STS-1 STS-1-1nV (n= 1 to 21) STS-3c STS-3c-mv (m= 1 to 7) STS-6c10-106 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card 10.13.13 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. Intermediate Path Performance Monitoring Intermediate path performance monitoring (IPPM) allows a node to monitor the constituent channel of an incoming transmission signal. You can enable IPPM for STS/VC-4s payload on OCn and Trunk ports of ADM-10G card. The IPPM is complaint with GR253/G.826. Software Release 9.2 and higher enables the ADM-10G card to monitor the near-end and far-end PM data on individual STS/VC-4 payloads by enabling IPPM. After provisioning IPPM on the card, service providers can monitor large amounts of STS/VC-4 traffic through intermediate nodes, thus making troubleshooting and maintenance activities more efficient. IPPM occurs only on STS/VC-4 paths that have IPPM enabled, and TCAs are raised only for PM parameters on the selected IPPM paths. For a CCAT circuit, you can enable IPPM only on the first STS/VC-4 of the concatenation group. For a VCAT circuit, you can enable IPPM independently on each member STS/VC-4 of the concatenation group. Pointer Justification Count Performance Monitoring Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on SONET networks. When a network is out of synchronization, jitter and wander occur on the transported signal. Excessive wander can cause terminating equipment to slip. STS-9c STS-12c STS-24c Table 10-44 Supported SDH Circuit Sizes of ADM-10G card on ONS 15454 SDH CCAT VCAT High Order VC-4 VC-4-mv (m= 1 to 7) VC-4-2c VC-4-3c VC-4-4c VC-4-8c Table 10-43 Supported SONET Circuit Sizes of ADM-10G card on ONS 15454 CCAT VCAT High Order10-107 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses the encryption key, causing data to be transmitted again. Pointers provide a way to align the phase variations in STS and VC4 payloads. The STS payload pointer is located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE) called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss. There are positive (PPJC) and negative (NPJC) pointer justification count parameters. PPJC is a count of path-detected (PPJC-PDET-P) or path-generated (PPJC-PGEN-P) positive pointer justifications. NPJC is a count of path-detected (NPJC-PDET-P) or path-generated (NPJC-PGEN-P) negative pointer justifications depending on the specific PM name. PJCDIFF is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. PJCS-PDET-P is a count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P is a count of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN. A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means that the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS-1. You must enable PPJC and NPJC performance monitoring parameters for ADM-10Gcard. In CTC, the count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the card view Provisioning tab. Performance Monitoring Parameter Definitions This section describes the STS and VC-4 path performance monitoring parameters that ADM-10G card support. Table 10-45 lists the STS near-end path performance monitoring parameters. Table 10-45 STS Near-end Path Performance Monitoring Parameters Parameter Definition CV-P Near-End STS Path Coding Violations (CV-P) is a count of BIP errors detected at the STS path layer (that is, using the B3 byte). Up to eight BIP errors can be detected per frame; each error increments the current CV-P second register. ES-P Near-End STS Path Errored Seconds (ES-P) is a count of the seconds when at least one STS path BIP error was detected. An AIS Path (AIS-P) defect (or a lower-layer, traffic-related, near-end defect) or a Loss of Pointer Path (LOP-P) defect can also cause an ES-P. SES-P Near-End STS Path Severely Errored Seconds (SES-P) is a count of the seconds when K (2400) or more STS path BIP errors were detected. An AIS-P defect (or a lower-layer, traffic-related, near-end defect) or an LOP-P defect can also cause an SES-P. 10-108 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card Table 10-46 gives the VC-4 near-end path performance monitoring parameters definition that ADM-10G card support. UAS-P Near-End STS Path Unavailable Seconds (UAS-P) is a count of the seconds when the STS path was unavailable. An STS path becomes unavailable when ten consecutive seconds occur that qualify as SES-Ps, and continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-Ps. FC-P Near-End STS Path Failure Counts (FC-P) is a count of the number of near-end STS path failure events. A failure event begins when an AIS-P failure, an LOP-P failure, a UNEQ-P failure, or a Section Trace Identifier Mismatch Path (TIM-P) failure is declared. A failure event also begins if the STS PTE that is monitoring the path supports Three-Bit (Enhanced) Remote Failure Indication Path Connectivity (ERFI-P-CONN) for that path. The failure event ends when these failures are cleared. PPJC-PDET-P Positive Pointer Justification Count, STS Path Detected (PPJC-PDET-P) is a count of the positive pointer justifications detected on a particular path in an incoming SONET signal. 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. NPJC-PDET-P Negative Pointer Justification Count, STS Path Detected (NPJC-PDET-P) is a count of the negative pointer justifications detected on a particular path in an incoming SONET signal. NPJC-PGEN-P Negative Pointer Justification Count, STS Path Generated (NPJC-PGEN-P) is a count of the negative pointer justifications generated for a particular path to reconcile the frequency of the SPE with the local clock. PJCDIFF-P Pointer Justification Count Difference, STS Path (PJCDIFF-P) is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. That is, PJCDiff-P is equal to (PPJC-PGEN-P - NPJC-PGEN-P) - (PPJC-PDET-P - NPJC-PDET-P). PJCS-PDET-P Pointer Justification Count Seconds, STS Path Detect (NPJCS-PDET-P) is a count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P Pointer Justification Count Seconds, STS Path Generate (PJCS-PGEN-P) is a count of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN. Table 10-45 STS Near-end Path Performance Monitoring Parameters Parameter Definition10-109 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card Table 10-46 VC-4 Near-end Path Performance Monitoring Parameters Parameter Definition HP-EB High-Order Path Errored Block (HP-EB) indicates that one or more bits are in error within a block. HP-BBE High-Order Path Background Block Error (HP-BBE) is an errored block not occurring as part of an SES. HP-ES High-Order Path Errored Second (HP-ES) is a one-second period with one or more errored blocks or at least one defect. HP-SES High-Order Path Severely Errored Seconds (HP-SES) is a one-second period containing 30 percent or more errored blocks or at least one defect. SES is a subset of ES. HP-UAS High-Order Path Unavailable Seconds (HP-UAS) is a count of the seconds when the VC path was unavailable. A high-order path becomes unavailable when ten consecutive seconds occur that qualify as HP-SESs, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as HP-SESs. HP-BBER High-Order Path Background Block Error Ratio (HP-BBER) is the ratio of BBE to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs. HP-ESR High-Order Path Errored Second Ratio (HP-ESR) is the ratio of errored seconds to total seconds in available time during a fixed measurement interval. HP-SESR High-Order Path Severely Errored Second Ratio (HP-SESR) is the ratio of SES to total seconds in available time during a fixed measurement interval. HP-PPJC-PDET High-Order, Positive Pointer Justification Count, Path Detected (HP-PPJC-Pdet) is a count of the positive pointer justifications detected on a particular path on an incoming SDH signal. HP-NPJC-PDET High-Order, Negative Pointer Justification Count, Path Detected (HP-NPJC-Pdet) is a count of the negative pointer justifications detected on a particular path on an incoming SDH signal. HP-PPJC-PGEN High-Order, Positive Pointer Justification Count, Path Generated (HP-PPJC-Pgen) is a count of the positive pointer justifications generated for a particular path. HP-NPJC-PGEN High-Order, Negative Pointer Justification Count, Path Generated (HP-NPJC-Pgen) is a count of the negative pointer justifications generated for a particular path. HP-PJCDIFF High-Order Path Pointer Justification Count Difference (HP-PJCDiff) is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. That is, HP-PJCDiff is equal to (HP-PPJC-PGen - HP-NPJC-PGen) - (HP-PPJC-PDet - HP-NPJC-PDet).10-110 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards ADM-10G Card 10.13.14 ADM-10G Card-Level Indicators Table 10-47 describes the card-level LEDs on the ADM-10G card. 10.13.15 ADM-10G Card Port-Level Indicators Table 10-48 describes the port-level LEDs on the ADM-10G card. Note Client or trunk ports can each be in active or standby mode as defined in the related section for each specific protection type. For example, fiber-switched protection has active or standby trunk ports; 1+1 APS protection has active or standby client ports, and client 1+1 protection does not utilize active or standby ports. HP-PJCS-PDET High-Order Path Pointer Justification Count Seconds (HP-PJCS-PDet) is a count of the one-second intervals containing one or more HP-PPJC-PDet or HP-NPJC-PDet. HP-PJCS-PGEN High-Order Path Pointer Justification Count Seconds (HP-PJCS-PGen) is a count of the one-second intervals containing one or more HP-PPJC-PGen or HP-NPJC-PGen. Table 10-46 VC-4 Near-end Path Performance Monitoring Parameters Parameter Definition Table 10-47 ADM-10G Card-Level Indicators Card-Level LED Description ACT LED Green (Active) Amber (Standby) Green indicates that the card is operational (one or both ports active) and ready to carry traffic. Amber indicates that the card is operational and in standby (protect) mode. 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. It the card is inserted in a slot that is preprovisioned for a different card, this LED flashes until a Missing Equipment Attribute (MEA) condition is raised. You might also need to replace the card if the red FAIL LED persists. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BER errors on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off.10-111 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card 10.14 OTU2_XP Card The OTU2_XP card is a single-slot card with four ports with XFP-based multirate (OC-192/STM-64, 10GE, 10G FC, IB_5G) Xponder for the ONS 15454 ANSI and ETSI platforms. The OTU2_XP card supports multiple configurations. Table 10-49 describes the different configurations supported by the OTU2_XP card and the ports that must be used for these configurations. All the four ports are ITU-T G.709 compliant and support 40 channels (wavelengths) at 100-GHz channel spacing in the C-band (that is, the 1530.33 nm to 1561.42 nm wavelength range). The OTU2_XP card can be installed in Slots 1 through 6 or 12 through 17. The OTU2_XP card supports SONET SR1, IR2, and LR2 XFPs, 10GE BASE SR, SW, LR, LW, ER, EW, and ZR XFPs, and 10G FC MX-SN-I and SM-LL-L XFPs. Table 10-48 ADM-10G Card Port-Level LED Indications Port-Level Status Tri-color LED Description The port-level LED is active and unprotected. • If a port is in OOS/locked state for any reason, the LED is turned off. • If a port is in IS/unlocked state and the PPM is preprovisioned or is physically equipped with no alarms, the LED is green. • If a port is in IS state and the PPM is physically equipped but does have alarms, the LED is red. The port-level LED is in standby. • If a port is in OOS/locked state for any reason, the LED is turned off. • If a port is in the IS/unlocked state and the PPM is preprovisioned or is physically equipped with no alarms, the LED is amber. • If a port is in IS state and physically equipped but does have alarms, the LED is red. Table 10-49 OTU2_XP Card Configurations and Ports Configuration Port 1 Port 2 Port 3 Port 4 2 x 10G transponder Client port 1 Client port 2 Trunk port 1 Trunk port 2 2 x 10G standard regenerator (with enhanced FEC (E-FEC) only on one port) Trunk port 1 Trunk port 2 Trunk port 1 Trunk port 2 10 GE LAN Phy to WAN Phy Client port Client port in transponder or trunk port in regenerator configuration Trunk port Trunk port in transponder or regenerator configuration 1 x 10G E-FEC regenerator (with E-FEC on two ports) Not used Not used Trunk port Trunk port 1 x 10G splitter protected transponder Client port Not used Trunk port (working) Trunk port (protect)10-112 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card Caution Fan-tray assembly 15454E-CC-FTA (ETSI shelf)/15454-CC-FTA (ANSI shelf) must be installed in a shelf where the OTU2_XP card is installed. 10.14.1 Key Features The OTU2_XP card has the following high-level features: • 10G transponder, regenerator, and splitter protection capability on the ONS 15454 DWDM platform. • Compatible with the ONS 15454 ANSI high-density shelf assembly, the ETSI ONS 15454 shelf assembly, and the ETSI ONS 15454 high-density shelf assembly. Compatible with TCC2/TCC2P/ TCC3/TNC/TSC cards. • Interoperable with TXP_MR_10E and TXP_MR_10E_C cards. • Four port, multirate (OC-192/STM-64, 10G Ethernet WAN Phy, 10G Ethernet LAN Phy, 10G Fibre Channel, IB_5G) client interface. The client signals are mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing. • ITU-T G.709 framing with standard Reed-Soloman (RS) (255,237) FEC. Performance monitoring and ITU-T G.709 Optical Data Unit (ODU) synchronous mapping. Enhanced FEC (E-FEC) with ITU-T G.709 ODU with greater than 8 dB coding gain. • The trunk rate remains the same irrespective of the FEC configuration. The error coding performance can be provisioned as follows:: – FEC—Standard ITU-T G.709. – E-FEC—Standard ITU-T G.975.1 I.7. • IEEE 802.3 frame format supported for 10 Gigabit Ethernet interfaces. The minimum frame size is 64 bytes. The maximum frame size is user-provisionable. • Supports fixed/no fixed stuff mapping (insertion of stuffing bytes) for 10G Ethernet LAN Phy signals (only in transponder configuration). • Supports 10G Ethernet LAN Phy to 10G Ethernet WAN Phy conversion on Ports 1 (client port) and 3 (trunk port). • Supports 10G Ethernet LAN Phy to WAN Phy conversion using CTC and TL1. When enabled on the OTU2_XP card, the first Channel (Ports 1 and 3) supports LAN to WAN conversion. The second channel carries normal 10GE, 10G FC, and OC192/STM64 traffic. • The LAN Phy to WAN Phy conversion functions in accordance to WAN Interface Sublayer (WIS) mechanism as defined by IEEE802.3ae (IEEE Std 802.3ae-2002, Amendment to CSMA/CD). • Default configuration is transponder, with trunk ports configured as ITU-T G.709 standard FEC. • In transponder or regenerator configuration, if one of the ports is configured the corresponding port is automatically created. • In regenerator configuration, only Ports 3 and 4 can be configured as E-FEC. Ports 1 and 2 can be configured only with standard FEC. • When port pair 1-3 or 2-4 is configured as regenerator (that is, card mode is standard regenerator), the default configuration on Ports 3 and 4 is automatically set to standard FEC. • When Ports 3 and 4 are configured as regenerator (that is, card mode is E-FEC regenerator), the default configuration on both these ports is automatically set to E-FEC.10-113 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card • In splitter protected transponder configuration, the trunk ports (Ports 3 and 4) are configured as ITU-T G.709 standard FECor E-FEC. • Supports protection through Y-cable protection scheme. Note When enabled, the 10G Ethernet LAN Phy to WAN Phy conversion feature does not support Y-cable protection on the LAN to WAN interface (ports 1 and 3). • Client ports support SONET SR1, IR2, and LR2 XFPs, 10GE BASE SR, SW, LR, LW, ER, EW, and ZR XFPs, and 10G FC MX-SN-I and SM-LL-L XFPs. • Following are the OTU2 link rates that are supported on the OTU2_XP trunk port: – Standard G.709 (10.70923 Gbps) when the client is provisioned as “SONET” (including 10G Ethernet WAN PHY) (9.95328 Gbps). – G.709 overclocked to transport 10GE as defined by ITU-T G. Sup43 Clause 7.2 (11.0491 Gbps) when the client is provisioned as “10G Ethernet LAN Phy” (10.3125 Gbps) with “No Fixed Stuff” enabled. – G.709 overclocked to transport 10GE as defined by ITU-T G. Sup43 Clause 7.1 (11.0957 Gbps) when the client is provisioned as “10G Ethernet LAN Phy” (10.3125 Gbps) with “No Fixed Stuff” disabled. – G.709 proprietary overclocking mode to transport 10G FC (11.3168 Gbps) when the client is provisioned as “10G Fiber Channel” (10.518 Gbps). – Proprietary rate at the trunk when the client is provisioned as IB_5G. • The MTU setting is used to display the ifInerrors and OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting. 10.14.2 Faceplate and Block Diagram Figure 10-33 shows the OTU2_XP card faceplate and block diagram.10-114 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card Figure 10-33 OTU2_XP Card Faceplate and Block Diagram Note The Swan FPGA is automatically loaded when the LAN Phy to WAN Phy conversion feature is enabled on the OTU2_XP card. The Barile FPGA is automatically loaded when the LAN Phy to WAN Phy conversion feature is disabled on the OTU2_XP card. 241984 SERDES G.709-FEC framer SERDES Barile FPGA SWAN FPGA XFP 1 XFP 3 SERDES G.709-FEC framer SERDES MPC8360 core Power supply Clocking XFP 2 SCL FPGA XFP 410-115 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card 10.14.3 OTU2_XP Card-Level Indicators Table 10-50 describes the card-level LEDs on the OTU2_XP card. 10.14.4 OTU2_XP Port-Level Indicators Table 10-51 describes the PPM port-level LEDs on the OTU2_XP card for both client and trunk ports. Note Client or trunk ports can each be in active or standby mode as defined in the related section for each specific protection type. For example, fiber-switched protection has active or standby trunk ports; 1+1 APS protection has active or standby client ports, and client 1+1 protection does not utilize active or standby ports. Table 10-50 OTU2_XP Card-Level Indicators Card-Level LED Description Red FAIL LED The 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. If the card is inserted in a slot that is preprovisioned for a different card, this LED flashes until a Missing Equipment Attribute (MEA) condition is raised. You might also need to replace the card if the red FAIL LED persists. ACT LED Green (Active) If the ACT LED is green, the card is operational (one or more ports active) and ready to carry traffic. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BER errors on one or more of the card ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-51 OTU2_XP PPM Port-Level Indicators Port-Level Status Tri-color LED Description The port-level LED is active and unprotected. • If a port is in OOS/locked state for any reason, the LED is turned off. • If a port is in IS/unlocked state and the PPM is preprovisioned or is physically equipped with no alarms, the LED is green. • If a port is in IS state and the PPM is physically equipped but does have alarms, the LED is red. The port-level LED is in standby. • If a port is in OOS/locked state for any reason, the LED is turned off. • If a port is in the IS/unlocked state and the PPM is preprovisioned or is physically equipped with no alarms, the LED is amber. • If a port is in IS state and physically equipped but does have alarms, the LED is red.10-116 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card 10.14.5 OTU2_XP Card Interface The OTU2_XP card is a multi-functional card that operates in different configurations, such as transponder, standard regenerator, E-FEC regenerator, and 10G Ethernet LAN Phy to WAN Phy conversion mode. The OTU2_XP card acts as a protected transponder, when the 10G Ethernet LAN Phy to WAN Phy is in splitter protected transponder configuration mode. Depending on the configuration of the OTU2_XP card, the ports act as client or trunk ports (see Table 10-49). This following section describes the client and trunk rates supported on the OTU2_XP card for different card configurations: 10.14.5.1 Client Interface In transponder and 10G Ethernet LAN Phy to WAN Phy card configurations, Ports 1 and 2 act as client ports and in splitter protected transponder configuration, Port 1 acts as a client port. For these card configurations, the client rates supported are: • OC-192/STM-64 • 10G Ethernet WAN Phy • 10G Ethernet LAN Phy • 10G Fibre Channel • IB_5G 10.14.5.2 Trunk Interface In transponder, 10G Ethernet LAN Phy to WAN Phy, and splitter protected transponder card configurations, Ports 3 and 4 act as trunk ports. For these card configurations, the trunk rates supported are: • OC-192/STM-64 • 10G Ethernet WAN Phy • 10G Ethernet LAN Phy • 10G Fibre Channel • OTU2 G.709 • Proprietary rate at the trunk when the client is provisioned as IB_5G. In standard regenerator card configuration, all four ports act as trunk ports and in E-FEC regenerator configuration, Ports 3 and 4 act as the trunk ports. For these card configurations, the trunk rate supported is OTU2 G.709 Note The above mentioned OTU2 signal must be an OC-192/STM-64, 10G Ethernet WAN Phy, 10G Ethernet LAN Phy, or 10G Fibre Channel signal packaged into an OTU2 G.709 frame. Additionally, the standard regenerator and E-FEC regenerator configuration supports an OTU2 signal that is OTU2 has been generated by multiplexing four ODU1 signals.10-117 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card 10.14.6 Configuration Management The OTU2_XP card supports the following configuration management parameters: • Card Configuration—Provisionable card configuration: Transponder, Standard Regen, Enhanced FEC, or Mixed, or 10G Ethernet LAN Phy to WAN Phy. • Port Mode—Provisionable port mode when the card configuration is set as Mixed. The port mode can be chosen as either Transponder or Standard Regen for each port pair (1-3 and 2-4). For card configurations other than Mixed, CTC automatically sets the port mode depending on the selected card configuration. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the port pair (1-3) as 10G Ethernet LAN Phy to WAN Phy. Port pair (2-4) in 10G Ethernet LAN Phy to WAN Phy mode is selected as Transponder or Standard Regen. • Termination Mode—Provisionable termination mode when the card configuration is set as either Transponder or Mixed. The termination mode can be chosen as Transparent, Section, or Line. For Standard Regen and Enhanced FEC card configurations, CTC automatically sets the termination mode as Transparent. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the Termination Mode of port pair (1-3) as Line. You cannot provision the Termination Mode parameter. • AIS/Squelch—Provisionable AIS/Squelch mode configuration when the card configuration is set as either Transponder or Mixed. The termination mode configuration can be chosen as AIS or Squelch. For Standard Regen and Enhanced FEC card configurations, CTC automatically sets the termination mode configuration as AIS. For 10G Ethernet LAN Phy to WAN Phy mode, the CTC automatically selects the AIS/Squelch of port pair (1-3) as Squelch. You cannot provision the AIS/Squelch parameter. Note When you choose the 10G Ethernet LAN Phy to WAN Phy conversion, the Termination mode is automatically set to LINE. The AIS/Squelch is set to SQUELCH and ODU Transparency is set to Cisco Extended Use for Ports 1 and 3. • Regen Line Name—User-assigned text string for regeneration line name. • ODU Transparency—Provisionable ODU overhead byte configuration, either Transparent Standard Use or Cisco Extended Use. See the “10.14.10 ODU Transparency” section on page 10-120 for more detailed information. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the ODU Transparency as Cisco Extended Use. You cannot provision the ODU Transparency parameter. • Port name—User-assigned text string. • Admin State/Service State—Administrative and service states to manage and view port status. • ALS Mode—Provisionable ALS function. • Reach—Provisionable optical reach distance of the port. • Wavelength—Provisionable wavelength of the port. • AINS Soak—Provisionable automatic in-service soak period. 10.14.7 OTU2_XP Card Configuration Rules The following rules apply to OTU2_XP card configurations: • When you preprovision the card, port pairs 1-3 and 2-4 come up in the default Transponder configuration.10-118 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card • The port pairs 1-3 and 2-4 can be configured in different modes only when the card configuration is Mixed. If the card configuration is Mixed, you must choose different modes on port pairs 1-3 and 2-4 (that is, one port pair in Transponder mode and the other port pair in Standard Regen mode). • If the card is in Transponder configuration, you can change the configuration to Standard Regen or Enhanced FEC. • If the card is in Standard Regen configuration and you have configured only one port pair, then configuring payload rates for the other port pair automatically changes the card configuration to Mixed, with the new port pair in Transponder mode. • If the card is in Standard Regen configuration, you cannot directly change the configuration to Enhanced FEC. You have to change to Transponder configuration and then configure the card as Enhanced FEC. • If the card is in Enhanced FEC configuration, Ports 1 and 2 are disabled. Hence, you cannot directly change the configuration to Standard Regen or Mixed. You must remove the Enhanced FEC group by moving the card to Transponder configuration, provision PPM on Ports 1 and 2, and then change the card configuration to Standard Regen or Mixed. • If the card is in Standard Regen or Enhanced FEC configuration, you cannot change the payload rate of the port pairs. You have to change the configuration to Transponder, change the payload rate, and then move the card configuration back to Standard Regen or Enhanced FEC. • If any of the affected ports are in IS (ANSI) or Unlocked-enabled (ETSI) state, you cannot change the card configuration. • If IB_5G payload has to be provisioned, the NE Default should match the values listed in the Table 10-52. For more information on editing the NE Default values, see the “NTP-G135 Edit Network Element Defaults” task. • If the card is changed to 10G Ethernet LAN Phy to WAN Phy, the first PPM port is deleted and replaced by a 10G Ethernet port; the third PPM port is deleted and automatically replaced with OC192/STM64 (SONET/SDH) port. The third PPM port is automatically deleted and the third PPM port is replaced with OC192/STM64 (SONET/SDH). Table 10-53 provides a summary of transitions allowed for the OTU2_XP card configurations. Table 10-52 OTU2_XP Card Configuration for IB_5G Payload Provisioning Parameter NE Default Name Value FEC OTU2-XP.otn.otnLines.FEC Standard ITU-T G.709 OTN OTU2-XP.otn.otnLines.G709OTN Enable Termination Mode OTU2-XP.config.port.TerminationMode Transparent ODU Transparency OTU2-XP.config.port.OduTransparency Cisco Extended Use AIS/Squelch OTU2-XP.config.port.AisSquelchMode Squelch Table 10-53 Card Configuration Transition Summary Card Configuration Transition To Transponder Standard Regen Enhanced FEC Mixed 10G Ethernet LAN Phy to WAN Phy Transponder — Yes Yes Yes Yes Standard Regen Yes — No Yes Yes10-119 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card 10.14.8 Security The OTU2_XP card, when an XFP is plugged into it, implements the Cisco Standard Security Code Check Algorithm that keys on vendor ID and serial number. If a PPM is plugged into a port on the card but fails the security code check because it is not a Cisco PPM, a NON-CISCO-PPM Not Reported (NR) condition occurs. If a PPM with a nonqualified product ID is plugged into a port on this card, that is, the PPM passes the security code as a Cisco PPM but it has not been qualified for use on the OTU2_XP card, a UNQUAL-PPM NR condition occurs. 10.14.9 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds. The on and off pulse duration is user-configurable. For details on ALS provisioning for the card, refer to the Cisco ONS 15454 DWDM Procedure Guide. Enhanced FEC Yes No — No No Mixed Yes Yes No — Yes 10G Ethernet LAN Phy to WAN Phy Yes Yes No The 10G Ethernet LAN Phy to WAN Phy to Mixed is supported if the Port pair 1-3 is chosen as Transponder. The 10G Ethernet LAN Phy to WAN Phy to Mixed is not supported if the Port pair 1-3 is chosen as Standard Regen. — Table 10-53 Card Configuration Transition Summary (continued) Card Configuration Transition To Transponder Standard Regen Enhanced FEC Mixed 10G Ethernet LAN Phy to WAN Phy10-120 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards OTU2_XP Card 10.14.10 ODU Transparency A key feature of the OTU2_XP card is the ability to configure the ODU overhead bytes (EXP bytes and RES bytes 1 and 2) using the ODU Transparency parameter. The two options available for this parameter are: • Transparent Standard Use—ODU overhead bytes are transparently passed through the card. This option allows the OTU2_XP card to act transparently between two trunk ports (when the card is configured in Standard Regen or Enhanced FEC). • Cisco Extended Use—ODU overhead bytes are terminated and regenerated on both ports of the regenerator group. The ODU Transparency parameter is configurable only for Standard Regen and Enhanced FEC card configuration. For Transponder card configuration, this parameter defaults to Cisco Extended Use and cannot be changed. Note The Forward Error Correction (FEC) Mismatch (FEC-MISM) alarm will not be raised on OTU2_XP card when you choose Transparent Standard Use. 10.14.11 Protection The OTU2_XP card supports Y-cable and splitter protection. Y-cable protection is provided at the client port level. Splitter protection is provided at the trunk port level. 10.14.11.1 Y-Cable Protection The OTU2_XP card supports Y-cable protection on client ports when it is provisioned in the transponder card configuration. Two cards can be joined in a Y-cable protection group with one card assigned as the working card and the other defined as the protection card. This protection mechanism provides redundant bidirectional paths. See the “10.19.1 Y-Cable Protection” section on page 10-139 for more detailed information. When a signal fault is detected (LOS, LOF, SD, or SF on the DWDM receiver port in the case of ITU-T G.709 mode) the protection mechanism software automatically switches between paths. Note When the 10G Ethernet LAN Phy to WAN Phy conversion feature is enabled, Y-cable protection is not supported on the LAN to WAN interface (ports 1 and 3). 10.14.11.2 Splitter Protection The OTU2_XP card supports splitter protection on trunk ports that are not part of a regenerator group (see Table 10-49 for port details). You can create and delete splitter protection groups in OTU2_XP card. In splitter protection method, a client injects a single signal into the client RX port. An optical splitter internal to the card then splits the signal into two separate signals and routes them to the two trunk TX ports. See the “10.19.2 Splitter Protection” section on page 10-141 for more detailed information. In the splitter protected 10G Ethernet LAN Phy to WAN Phy mode, AIS-P and LOP-P acts as trigger (when G.709 is enabled) for the Protection Switch, in addition to the existing switching criteria. The STS parameters such as, SF /SD thresholds, Path PM thresholds, and Path Trace is set for the working path (Port 3). The same parameters are also applicable for the protected path (Port 4).10-121 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MLSE UT 10.15 MLSE UT The maximum likelihood sequence estimation (MLSE) based universal transponder (UT) modules are added to the TXP_MR_10EX_C, MXP_2.5G_10EX_C, and MXP_MR_10DMEX_C cards to support the error decorrelator functionality to enhance system performance. 10.15.1 Error Decorrelator The MLSE feature uses the error decorrelator functionality to reduce the chromatic dispersion (CD) and polarization mode dispersion (PMD), thereby extending the transmission range on the trunk interface. You can enable or disable the error decorrelator functionality using CTC or TL1. The dispersion compensation unit (DCU) is also used to reduce CD and PMD. The MLSE-based UT module helps to reduce CD and PMD without the use of a DCU. 10.16 TXP_MR_10EX_C Card The TXP_MR_10EX_C card is a multirate transponder for the ONS 15454 platform. The card is fully backward compatible with TXP_MR_10E_C cards (only when the error decorrelator is disabled in the CTC on the TXP_MR_10EX_C card). It processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). The TXP_MR_10EX_C card is tunable over the 82 channels of C-band (82 channels spaced at 50 GHz on the ITU grid). You can install TXP_MR_10EX_C card in Slots 1 to 6 and 12 to 17. The card can be provisioned in linear, BLSR/MS-SPRing, path protection/SNCP configurations or as a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode. The TXP_MR_10EX_C card features an MLSE-based Universal Transponder 1550-nm tunable laser and a separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port. Note The PRE FEC BER performance of the TXP_MR_10EX_C card may be significantly low when compared to the TXP_MR_10E card. However, this does not affect the Post FEC BER performance, but could possibly affect any specific monitoring application that relies on the PRE FEC BER value (for example, protection switching). In this case, the replacement of TXP_MR_10E card with the TXP_MR_10EX_C may not work properly. Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10EX_C card must be installed in a high-speed slot (slot 6, 7, 12, or 13) On its faceplate, the TXP_MR_10EX_C card contains two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled. 10.16.1 Key Features The key features of the TXP_MR_10EX_C card are: • A multi-rate client interface (available through the ONS-XC-10G-S1 XFP, ordered separately):10-122 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10EX_C Card – OC-192 (SR1) – 10GE (10GBASE-LR) – 10G-FC (1200-SM-LL-L) – (ONS-XC-10G-S1 version 3 only) IB_5G • An MLSE-based UT module tunable through 82 channels of C-band. The channels are spaced at 50 GHz on the ITU grid. • OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping. • Proprietary rate at the trunk when the client is provisioned as IB_5G. • The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting. 10.16.2 Faceplate and Block Diagram Figure 10-34 shows the TXP_MR_10EX_C faceplate and block diagram. Figure 10-34 TXP_MR_10EX_C Faceplate and Block Diagram uP bus Serial bus uP Flash RAM Optical transceiver 247063 Framer/FEC/DWDM processor Client interface DWDM trunk (long range) Optical transceiver B a c k p l a n e FAIL ACT/STBY SF 10E MR TXP L TX RX RX TX DWDM trunk STM-64/OC-192 82 tunable channels (C-band) on the 50-GHz ITU Client interface STM-64/OC-192 or 10GE (10GBASE-LR) or 10G-FC (1200-SM-LL-L)10-123 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10EX_C Card For information on safety labels for the card, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10EX_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with this card, because they can cause irreparable damage to the card. 10.16.3 Client Interface The client interface is implemented with a separately orderable XFP module. The module is a tri-rate transceiver, providing a single port that can be configured in the field to support an OC-192 SR-1 (Telcordia GR-253-CORE) or STM-64 I-64.1 (ITU-T G.691) optical interface, as well as 10GE LAN PHY (10GBASE-LR), 10GE WAN PHY (10GBASE-LW), 10G-FC signals, or IB_5G signals. The client-side XFP pluggable module supports LC connectors and is equipped with a 1310-nm laser. 10.16.4 DWDM Trunk Interface On the trunk side, the TXP_MR_10EX_C card provides a 10-Gbps STM-64/OC-192 interface. In the 1550-nm C-band on the 50-GHz ITU grid for the DWDM interface, 82 tunable channels are available. The TXP_MR_10EX_C card provides 3R transponder functionality for this 10-Gbps trunk interface. Therefore, the card is suited for use in long-range amplified systems. The DWDM interface is compliant with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The DWDM trunk port operates at a rate that depends on the input signal and the presence of the ITU-T G.709 Digital Wrapper/FEC. The possible trunk rates are: • OC192 (9.95328 Gbps) • OTU2 (10.70923 Gbps) • 10GE (10.3125 Gbps) or 10GE into OTU2 (ITU G.sup43 11.0957 Gbps) • 10G-FC (10.51875 Gbps) or 10G-FC into OTU2 (nonstandard 11.31764 Gbps) • Proprietary rate at the trunk when the client is provisioned as IB_5G. The maximum system reach in filterless applications without the use of optical amplification or regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is given for informational purposes. It is subject to change. Note You cannot disable ITU-T G.709 on the trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled. 10.16.5 Enhanced FEC (E-FEC) Feature A key feature of the TXP_MR_10EX_C card is the availability to configure the forward error correction feature in two modes: FEC and E-FEC. The output bit rate is always 10.7092 Gbps as defined in ITU-T G.709, but the error coding performance can be provisioned as follows: • FEC—Standard ITU-T G.975 Reed-Solomon algorithm • E-FEC—Standard ITU-T G.975.1 I.7 algorithm, (a super FEC code)10-124 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards TXP_MR_10EX_C Card 10.16.6 FEC and E-FEC Modes As client-side traffic passes through the TXP_MR_10EX_C card, it can be digitally wrapped using FEC mode or E-FEC mode. The FEC mode setting provides a lower level of error detection and correction than the E-FEC mode setting of the card. As a result, using E-FEC mode allows higher sensitivity (lower OSNR) with a lower bit error rate than FEC mode. E-FEC enables longer distance trunk-side transmission than with FEC. The E-FEC feature is one of three basic modes of FEC operation. FEC can be turned on, or E-FEC can be turned on to provide greater range and lower BER. The default mode is FEC on and E-FEC off. E-FEC is provisioned using CTC. Caution Because the transponder has no visibility into the data payload and detect circuits, the TXP_MR_10EX_C card does not display circuits under the card view. 10.16.7 Client-to-Trunk Mapping The TXP_MR_10EX_C card can perform ODU2-to-OCh mapping, which allows operators to provision data payloads in a standard way across 10-Gbps optical links. Digital wrappers that define client-side interfaces are called ODU2 entities in ITU-T G.709. Digital wrappers that define trunk-side interfaces are called OCh in ITU-T G.709. ODU2 digital wrappers can include G-MPLS signaling extensions to ITU-T G.709 (such as LSP and G-PID values) to define client interfaces and payload protocols. 10.16.8 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds and is user-configurable. For details regarding ALS provisioning for the TXP_MR_10EX_C card, refer to the Cisco ONS 15454 DWDM Procedure Guide. 10.16.9 TXP_MR_10EX_C Card-Level Indicators Table 10-54 lists the card-level LEDs on the TXP_MR_10EX_C card. Table 10-54 TXP_MR_10EX_C 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.10-125 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card 10.16.10 TXP_MR_10EX_C Port-Level Indicators Table 10-55 lists the port-level LEDs on the TXP_MR_10EX_C card. 10.17 MXP_2.5G_10EX_C card The MXP_2.5G_10EX_C card is a DWDM muxponder for the ONS 15454 platform that supports transparent termination mode on the client side. The faceplate designation of the card is “4x2.5G 10EX MXP.” The card multiplexes four 2.5-Gbps client signals (4xOC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The card provides wavelength transmission service for the four incoming 2.5-Gbps client interfaces. The MXP_2.5G_10EX_C muxponder passes all SONET/SDH overhead bytes transparently. The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_2.5G_10EX_C card works with OTN devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “10.8.5 Multiplexing Function” section on page 10-44. The MXP_2.5G_10EX_C card is not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode. You can install the MXP_2.5G_10EX_C card in slots 1 to 6 and 12 to 17. You can provision a card in a linear configuration, a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode. The MXP_2.5G_10EX_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs ACT/STBY LED Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or both ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-54 TXP_MR_10EX_C Card-Level Indicators (continued) Card-Level LED Description Table 10-55 TXP_MR_10EX _C Port-Level Indicators Port-Level LED Description Green Client LED The green Client LED indicates that the client port is in service and that it is receiving a recognized signal. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-126 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card (labeled) on the card faceplate. The card uses dual LC connectors on the trunk side and SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector. Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode, which are necessary to provision the 4xOC-48 OCHCC circuit. 10.17.1 Key Features The MXP_2.5G_10EX_C card has the following high-level features: • Four 2.5-Gbps client interfaces (OC-48/STM-16) and one 10-Gbps trunk. The four OC-48 signals are mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing. • Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. • Pluggable client-interface optic modules: The MXP_2.5G_10EX_C card has modular interfaces. Two types of optic modules can be plugged into the card. These modules include an OC-48/STM-16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range of up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957). • High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software. • Link monitoring and management: The card uses standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its overhead bytes transparently. • Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. • Automatic timing source synchronization: The MXP_2.5G_10EX_C card normally synchronizes from the TCC2/TCC2P/TCC3/TNC/TSC card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TSC is not available, the card automatically synchronize to one of the input client-interface clocks. • Configurable squelching policy: The card can be configured to squelch the client interface output if LOS occurs at the DWDM receiver or if a remote fault occurs. In the event of a remote fault, the card manages MS-AIS insertion. • The card is tunable across the full C-band, thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band. • The MTU setting is used to display the ifInerrors and OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.10-127 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card 10.17.2 Faceplate Figure 10-35 shows the MXP_2.5G_10EX_C faceplate and block diagram. Figure 10-35 MXP_2.5G_10EX_C Faceplate and Block Diagram For information on safety labels for the card, see the “10.2.1 Class 1 Laser Product Cards” section on page 10-8. 10.17.3 Client Interfaces The MXP_2.5G_10EX_C card provides four intermediate- or short-range OC-48/STM-16 ports per card on the client side. Both SR-1 and IR-1 optics can be supported and the ports use SFP connectors. The client interfaces use four wavelengths in the 1310-nm, ITU 100-GHz-spaced, channel grid. FAIL ACT/STBY SF 4x2.5 10 E MXP L RX TX TX RX TX RX TX RX TX RX RAM Processor 247064 Optical transceiver Optical transceiver Optical transceiver Optical transceiver Optical transceiver B a c k p l a n e FEC/ Wrapper E-FEC Processor (G.709 FEC) Serial bus uP bus Onboard Flash memory SR-1 (short reach/intra-office) or IR-1 (intermediate range) SFP client optics modules DWDM (trunk) 10GE (10GBASE-LR)10-128 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card 10.17.4 DWDM Interface The MXP_2.5G_10EX_C card serves as OTN multiplexers, transparently mapping four OC-48 channels asynchronously to ODU1 into one 10-Gbps trunk. For the MXP_2.5G_10EX_C card, the DWDM trunk is tunable for transmission over the entire C-band. Channels are spaced at 50-GHz on the ITU grid. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the card in a loopback on the trunk port. Do not use direct fiber loopbacks with the card, because they can cause irreparable damage to the MXP_2.5G_10EX_C card. Note You cannot disable ITU-T G.709 on the trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled. 10.17.5 Multiplexing Function The muxponder is an integral part of the ROADM network. The key function of the MXP_2.5G_10EX_C card is to multiplex four OC-48/STM-16 signals onto one ITU-T G.709 OTU2 optical signal (DWDM transmission). The multiplexing mechanism allows the signal to be terminated at a far-end node by another similar card. Transparent termination on the muxponder is configured using OTUx and ODUx OH bytes. The ITU-T G.709 specification defines OH byte formats that are used to configure, set, and monitor frame alignment, FEC mode, section monitoring, tandem connection monitoring, and transparent termination mode. The MXP_2.5G_10EX_C card performs ODU to OTU multiplexing as defined in ITU-T G.709. The ODU is the framing structure and byte definition (ITU-T G.709 digital wrapper) used to define the data payload coming into one of the SONET/SDH client interfaces on the card. The term ODU1 refers to an ODU that operates at 2.5-Gbps line rate. On the card, four client interfaces can be defined using ODU1 framing structure and format by asserting an ITU-T G.709 digital wrapper. The output of the muxponder is a single 10-Gbps DWDM trunk interface defined using OTU2. It is within the OTU2 framing structure that FEC or E-FEC information is appended to enable error checking and correction. 10.17.6 Timing Synchronization The MXP_2.5G_10EX_C card is synchronized to the TCC2/TCC2P /TCC3/TNC/TSC clock during normal conditions and transmits the ITU-T G.709 frame using this clock. No holdover function is implemented. If neither TCC2/TCC2P/TCC3/TNC/TSC clock is available, the card switches automatically (hitless) to the first of the four valid client clocks with no time restriction as to how long it can run on this clock. The card continues to monitor the TCC2/TCC2P/TCC3/TNC/TSC card. If a TCC2/TCC2P/TCC3/TNC/TSC card is restored to working order, the card reverts to the normal working mode of running from the TCC2/TCC2P/TCC3/TNC/TSC clock. If no valid TCC2/TCC2P/TCC3/TNC/TSC clock is available and all of the client channels become invalid, the card waits (no valid frames processed) until one of the TCC2/TCC2P/TCC3/TNC/TSC cards supplies a valid clock. In addition, the card is allowed to select the recovered clock from one active and valid client channel and supply that clock to the TCC2/TCC2P/TCC3/TNC/TSC card.10-129 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card 10.17.7 Enhanced FEC (E-FEC) Capability The MXP_2.5G_10EX_C card can configure the FEC in two modes: FEC and E-FEC. The output bit rate is always 10.7092 Gbps as defined in ITU-T G.709, but the error coding performance can be provisioned as follows: • FEC—Standard ITU-T G.975 Reed-Solomon algorithm • E-FEC—Standard ITU-T G.975.1 I.7, two orthogonally concatenated BCH super FEC codes. This FEC scheme contains three parameterizations of the same scheme of two orthogonally interleaved block codes (BCH). The constructed code is decoded iteratively to achieve the expected performance. 10.17.8 FEC and E-FEC Modes As client-side traffic passes through the card, it can be digitally wrapped using FEC mode error correction or E-FEC mode error correction. The FEC mode setting provides a lower level of error detection and correction than the E-FEC mode setting of the card. As a result, using E-FEC mode allows higher sensitivity (lower OSNR) with a lower BER than FEC mode. E-FEC enables longer distance trunk-side transmission than with FEC. The E-FEC feature is one of three basic modes of FEC operation. FEC can be turned on, or E-FEC can be turned on to provide greater range and lower BER. The default mode is FEC on and E-FEC off. E-FEC is provisioned using CTC. 10.17.9 SONET/SDH Overhead Byte Processing The card passes the incoming SONET/SDH data stream and its overhead bytes for the client signal transparently. The card can be provisioned to terminate regenerator section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. 10.17.10 Client Interface Monitoring The following parameters are monitored on the MXP_2.5G_10EX_C card: • Laser bias current is measured as a PM parameter. • LOS is detected and signaled. • Rx and Tx power are monitored. The following parameters are monitored in real-time mode (one second): • Optical power transmitted (client) • Optical power received (client) In the case of LOC at the DWDM receiver or far-end LOS, the client interface behavior is configurable. AIS can be invoked or the client signal can be squelched.10-130 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card 10.17.11 Wavelength Identification The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. The MXP_2.5G_10EX_C card implements the MLSE-based UT module. The MXP_2.5G_10EX_C card uses a C-band version of the UT2. Table 10-56 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10EX_C card. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid. Table 10-56 MXP_2.5G_10EX_C Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.95910-131 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_2.5G_10EX_C card 10.17.12 Automatic Laser Shutdown The ALS procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds and is user-configurable. For details regarding ALS provisioning for the MXP_2.5G_10EX_C card, see the Cisco ONS 15454 DWDM Procedure Guide. 10.17.13 Jitter For SONET and SDH signals, the MXP_2.5G_10EX_C card complies with Telcordia GR-253-CORE, ITU-T G.825, and ITU-T G.873 for jitter generation, jitter tolerance, and jitter transfer. See the “10.21 Jitter Considerations” section on page 10-142 for more information. 10.17.14 Lamp Test The MXP_2.5G_10EX_C card supports a lamp test function that is activated from the ONS 15454 front panel or through CTC to ensure that all LEDs are functional. 10.17.15 Onboard Traffic Generation The MXP_2.5G_10EX_C card provides internal traffic generation for testing purposes according to PRBS, SONET/SDH, or ITU-T G.709. 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 10-56 MXP_2.5G_10EX_C Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)10-132 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card 10.17.16 MXP_2.5G_10EX_C Card-Level Indicators Table 10-57 describes the card-level LEDs on the MXP_2.5G_10EX_C card. 10.17.17 MXP_2.5G_10EX_C Port-Level Indicators Table 10-58 describes the port-level LEDs on the MXP_2.5G_10EX_C card. 10.18 MXP_MR_10DMEX_C Card The MXP_MR_10DMEX_C card aggregates a mix of client SAN service-client inputs (GE, FICON, and Fibre Channel) into one 10-Gbps STM-64/OC-192 DWDM signal on the trunk side. It provides one long-reach STM-64/OC-192 port per card and is compliant with Telcordia GR-253-CORE and ITU-T G.957. The card supports aggregation of the following signal types: • 1-Gigabit Fibre Channel • 2-Gigabit Fibre Channel • 4-Gigabit Fibre Channel • 1-Gigabit Ethernet • 1-Gigabit ISC-Compatible (ISC-1) • 2-Gigabit ISC-Peer (ISC-3) Table 10-57 MXP_2.5G_10EX_C 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off. Table 10-58 MXP_2.5G_10E_C and MXP_2.5G_10E_L Port-Level Indicators Port-Level LED Description Green Client LED (four LEDs) A green Client LED indicates that the client port is in service and that it is receiving a recognized signal. The card has four client ports, and so has one Client LED for each port. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-133 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card Caution The card can be damaged by dropping it. Handle it carefully. The MXP_MR_10DMEX_C muxponder passes all SONET/SDH overhead bytes transparently. The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_MR_10DMEX_C card works with the OTN devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “10.7.7 Multiplexing Function” section on page 10-36. Note You cannot disable ITU-T G.709 on the trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled. Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a maximum limit of 10 Gbps. You can install the MXP_MR_10DMEX_C card in slots 1 to 6 and 12 to 17. Note The MXP_MR_10DMEX_C card is not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode. The MXP_MR_10DMEX_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. Each card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors on the trunk side and SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector. Table 10-59 shows the input data rate for each client interface, and the encapsulation method. The current version of the GFP-T G.7041 supports transparent mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, ISC, and FICON. In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed SERDES is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the high-speed SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel. Table 10-59 MXP_MR_10DMEX_C Client Interface Data Rates and Encapsulation Client Interface Input Data Rate GFP-T G.7041 Encapsulation 2G FC 2.125 Gbps Yes 1G FC 1.06 Gbps Yes 2G FICON/2G ISC-Compatible (ISC-1)/ 2G ISC-Peer (ISC-3) 2.125 Gbps Yes10-134 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card The MXP_MR_10DMEX_C card includes two FPGAs, and a group of four ports is mapped to each FPGA. Group 1 consists of Ports 1 through 4, and Group 2 consists of Ports 5 through 8. Table 10-60 shows some of the mix and match possibilities on the various client data rates for Ports 1 through 4, and Ports 5 through 8. An X indicates that the data rate is supported in that port. GFP-T PM is available through RMON and trunk PM is managed according to Telcordia GR-253-CORE and ITU G.783/826. Client PM is achieved through RMON for FC and GE. A buffer-to-buffer credit management scheme provides FC flow control. With this feature enabled, a port indicates the number of frames that can be sent to it (its buffer credit), before the sender is required to stop transmitting and wait for the receipt of a “ready” indication. The MXP_MR_10DMEX_C card supports FC credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.1 miles) for 1G FC, up to 800 km (497.1 miles) for 2G FC, or up to 400 km (248.5 miles) for 4G FC. The feature can be enabled or disabled. The MXP_MR_10DMEX_C card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser (depending on the SFP) for the client ports. The card contains eight 12.5-degree downward-tilt SFP modules for the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual-LC connector with a 45-degree downward angle. 10.18.1 Key Features The MXP_MR_10DMEX_C card has the following high-level features: • Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. • Pluggable client-interface optic modules: The MXP_MR_10DMEX_C card has modular interfaces. Two types of optics modules can be plugged into the card. These modules include an OC-48/STM-16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and 1G FICON/1G ISC-Compatible (ISC-1)/ 1G ISC-Peer (ISC-3) 1.06 Gbps Yes Gigabit Ethernet 1.25 Gbps Yes Table 10-59 MXP_MR_10DMEX_C Client Interface Data Rates and Encapsulation (continued) Client Interface Input Data Rate GFP-T G.7041 Encapsulation Table 10-60 Supported Client Data Rates for Ports 1 through 4 and Ports 5 through 8 Port (Group 1) Port (Group 2) Gigabit Ethernet 1G FC 2G FC 4G FC 1 5 X XXX 2 6 X X —— 3 7 X XX— 4 8 X X ——10-135 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card intra-office applications) and an IR-1 interface with a range of up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957). • Y-cable protection: The card supports Y-cable protection between the same card type only, on ports with the same port number and signal rate. See the “10.19.1 Y-Cable Protection” section on page 10-139 for more detailed information. • High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software. • ALS: This safety mechanism is used in the event of a fiber cut. For details regarding ALS provisioning for the MXP_MR_10DMEX_C card, refer to the Cisco ONS 15454 DWDM Procedure Guide. • Link monitoring and management: The card uses standard OC-48 OH(overhead) bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its OH(overhead) bytes transparently. • Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network. • Automatic timing source synchronization: The MXP_MR_10DMEX_C card normally synchronizes from the TCC2/TCC2P/TCC3/TNC/TSC card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TSC is not available, the card automatically synchronizes to one of the input client-interface clocks. Note MXP_MR_10DMEX_C card cannot be used for line timing. • Configurable squelching policy: The card can be configured to squelch the client-interface output if LOS occurs at the DWDM receiver or if a remote fault occurs. In the event of a remote fault, the card manages MS-AIS insertion. • The card is tunable across the full C-band, thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band. • You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_10DMEX_C card, which allows the MDS Fabric Manager to create a link association between that SAN port and a SAN port on a Cisco MDS 9000 switch. 10.18.2 Faceplate Figure 10-36 shows the MXP_MR_10DMEX_C faceplate and block diagram.10-136 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card Figure 10-36 MXP_MR_10DMEX_C Faceplate and Block Diagram For information on safety labels for the card, see the “10.2.2 Class 1M Laser Product Cards” section on page 10-10. Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the card in a loopback on the trunk port. Do not use direct fiber loopbacks with the card, because they can cause irreparable damage to the MXP_MR_10DMEX_C card. 10.18.3 Wavelength Identification The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. The MXP_MR_10DMEX_C card uses a C-band version of the MLSE-based UT module. 10DME-C FAIL ACT/STBY SF 247065 RX TX 1 RX TX 2 RX TX 3 RX TX 4 RX TX 1 RX TX 2 RX TX 3 RX TX 4 DWDM RX TX SPF 1/1 4G FC SerDes 1 x QDR 2M x 36bit Burst4 1/2/4G-FC B2B Credit Mgt FPGA Framer G.709/FEC OTN MXP UT2 5x I/O 5x I/O SPF 2/1 SPF 3/1 CPU Core FPGA Power supply SPF 4/1 SPF 6/1 4G FC SerDes 1/2/4G-FC B2B Credit Mgt FPGA 5x I/O 5x I/O SPF 7/1 SPF 8/1 SPF 9/1 Client ports Group 1 Group 210-137 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card Table 10-61 describes the required trunk transmit laser wavelengths for the MXP_MR_10DMEX_C card. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid. Table 10-61 MXP_MR_10DMEX_C Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.57810-138 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards MXP_MR_10DMEX_C Card 10.18.4 MXP_MR_10DMEX_C Card-Level Indicators Table 10-62 describes the card-level LEDs on the MXP_MR_10DMEX_C card. 10.18.5 MXP_MR_10DMEX_C Port-Level Indicators Table 10-63 describes the port-level LEDs on the MXP_MR_10DMEX_C card. 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table 10-61 MXP_MR_10DMEX_C Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table 10-62 MXP_MR_10DMEX_C 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 Green (Active) Amber (Standby) If the ACT/STBY LED is green, the card is operational (one or more ports active) and ready to carry traffic. If the ACT/STBY LED is amber, the card is operational and in standby (protect) mode. Amber SF LED The amber SF LED indicates a signal failure or condition such as LOS, LOF, or high BERs on one or more of the card’s ports. The amber SF LED is also on if the transmit and receive fibers are incorrectly connected. If the fibers are properly connected and the link is working, the light turns off.10-139 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Y-Cable and Splitter Protection 10.19 Y-Cable and Splitter Protection Y-cable and splitter protection are two main forms of card protection that are available for TXP, MXP, and Xponder (GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP) cards when they are provisioned in TXP or MXP mode. Y-cable protection is provided at the client port level. Splitter protection is provided at the trunk port level. Note GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards use VLAN protection when they are provisioned in L2-over-DWDM mode. For information, see the “10.12.10.3 Layer 2 Over DWDM Protection” section on page 10-81. The ADM-10G card uses path protection and 1+1 protection. For more information, see the “10.13.10 Protection” section on page 10-103. 10.19.1 Y-Cable Protection Y-cable protection is available for the following ONS 15454 TXP, MXP, and Xponder cards: • TXP_MR_10G • TXP_MR_10E • TXP_MR_2.5G • 40G-TXP-C • MXP_2.5G_10G • MXP_2.5G_10E • MXP_2.5G_10E_C • MXP_2.5G_10E_L • MXP_MR_2.5G • MXP_MR_10DME_C • MXP_MR_10DME_L Table 10-63 MXP_MR_10DMEX_C Port-Level Indicators Port-Level LED Description Port LED (eight LEDs, four for each group, one for each SFP) Green/Red/Amber/Off When green, the port LED indicates that the client port is either in service and receiving a recognized signal (that is, no signal fail), or the port is in Out of Service and Maintenance (OOS,MT or locked, maintenance) state and the signal fail and alarms are being ignored. When red, the port LED indicates that the client port is in service but is receiving a signal fail (LOS). When amber, the port LED indicates that the port is provisioned and in a standby state. When off, the port LED indicates that the SFP is either not provisioned, out of service, not properly inserted, or the SFP hardware has failed. Green DWDM LED The green DWDM LED indicates that the DWDM port is in service and that it is receiving a recognized signal.10-140 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Y-Cable and Splitter Protection • 40G-MXP-C • GE_XP and GE_XPE (when in 10GE or 20GE MXP card mode) • 10GE_XP and 10GE_XPE (when in 10GE TXP card mode) • OTU2_XP (when in Transponder card configuration) To create Y-cable protection, you create a Y-cable protection group for two TXP, MXP, or Xponder cards using the CTC software, then connect the client ports of the two cards physically with a Y-cable. The single client signal is sent into the RX Y-cable and is split between the two TXP, MXP, or Xponder cards. The two TX signals from the client side of the TXP, MXP, or Xponder cards are combined in the TX Y-cable into a single client signal. Only the active card signal passes through as the single TX client signal. The other card must have its laser turned off to avoid signal degradation where the Y-cable joins. When an MXP_MR_2.5G, MXP_MR_10DME_C, or MXP_MR_10DME_L card that is provisioned with Y-cable protection is used on a storage ISL link (FC1G, FC2G, FC4G, FICON1G, FICON2G, or FICON4G), a protection switchover resets the standby port to active. This reset reinitialises the end-to-end link to avoid any link degradation caused due to loss of buffer credits during switchover and results in an end-to-end traffic hit of 15 to 20 seconds. When using the MXP_MR_10DME_C or MXP_MR_10DME_L card, enable the fast switch feature and use it with a Cisco MDS storage switch to avoid this 15 to 20 second traffic hit. When enabling fast switch on the MXP_MR_10DME_C or MXP_MR_10DME_L card, ensure that the attached MDS switches have the buffer-to-buffer credit recovery feature enabled. You can also use the TXP_MR_2.5G card to avoid this 15 to 20 second traffic hit. When a Y-cable protection switchover occurs, the storage ISL link does not reinitialize and results in an end-to-end traffic hit of less than 50ms. Note Y-cable connectors will not work with copper SFPs because Y-cables are made up of optical connectors and there is no way to physically connect them to a copper SFP. Y-cable protection is not supported on IB_5G. Note There is a traffic hit of upto a couple hundred milliseconds on the MXP_MR_2.5G and MXP_MR_10DME cards in Y-cable configuration when a fiber cut or SFP failure occurs on one of the client ports. Note The OTU2_XP and 40E-MXP-C card cannot implement Y-cable protection for the client ports in 10 GE LAN PHY mode. Hence, a pair of OTU2_XP cards is used at each end in pass-through mode (Transponder mode with G.709 disabled) to implement Y-cable protection. The 40E-MXP-CE card can implement Y-cable protection without the OTU2_XP card for the client ports in LAN PHY GFP mode. However, the 40E-MXP-CE card cannot implement Y-cable protection without the OTU2_XP card for the client ports in LAN PHY WIS mode. Note If you create a GCC on either card of the protect group, the trunk port stays permanently active, regardless of the switch state. When you provision a GCC, you are provisioning unprotected overhead bytes. The GCC is not protected by the protect group. Figure 10-37 on page 10-141 shows the Y-cable signal flow.10-141 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Y-Cable and Splitter Protection Note Loss of Signal–Payload (LOS-P) alarms, also called Incoming Payload Signal Absent alarms, can occur on a split signal if the ports are not in a Y-cable protection group. Note Removing an SFP from the client ports of a card in a Y-cable protection group card causes an IMPROPRMVL (PPM) alarm. The working port raises the IMPROPRMVL alarm and the protected port raises the IMPROPRMVL alarm. The severity on the client ports is changed according to the protection switch state. Figure 10-37 Y-Cable Protection 10.19.2 Splitter Protection Splitter protection, shown in Figure 10-38, is provided with TXPP cards, MXPP cards., and OTU2_XP cards (on trunk ports that are not part of a regenerator group). You can create and delete splitter protection groups in OTU2_XP card. To implement splitter protection, a client injects a single signal into the client RX port. An optical splitter internal to the card then splits the signal into two separate signals and routes them to the two trunk TX ports. The two signals are transmitted over diverse optical paths. The far-end MXPP or TXPP card uses an optical switch to choose one of the two trunk RX port signals and injects it into the TX client port. When using splitter protection with two MXPP or TXPP cards, there are two different optical signals that flow over diverse paths in each direction. In case of failure, the far-end switch must choose the appropriate signal using its built-in optical switch. The triggers for a protection switch are LOS, LOF, SF, or SD. Client "Working" card (TXP or MXP) "Protection" card (TXP or MXP) Y cables TX RX Working Protect Client Port Trunk Port Client Port Trunk Port 12408010-142 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Far-End Laser Control Figure 10-38 Splitter Protection 10.20 Far-End Laser Control The 15454 DWDM cards provide a transparent mode that accurately conveys the client input signal to the far-end client output signal. The client signal is normally carried as payload over the DWDM signals. Certain client signals, however, cannot be conveyed as payload. In particular, client LOS or LOF cannot be carried. Far-end laser control (FELC) is the ability to convey an LOS or LOF from the near-end client input to the far-end client output. If an LOS is detected on the near-end client input, the near-end trunk sets the appropriate bytes in the OTN overhead of the DWDM line. These bytes are received by the far-end trunk, and cause the far-end client laser to be turned off. When the laser is turned off, it is said to be squelched. If the near-end LOS clears, the near-end trunk clears the appropriate bytes in the OTN overhead, the far-end detects the changed bytes, and the far-end client squelch is removed. FELC also covers the situation in which the trunk port detects that it has an invalid signal; the client is squelched so as not to propagate the invalid signal. Payload types with the 2R mode preclude the use of OTN overhead bytes. In 2R mode, an LOS on the client port causes the trunk laser to turn off. The far end detects the LOS on its trunk receiver and squelches the client. FELC is not provisionable. It is always enabled when the DWDM card is in transparent termination mode. However, FELC signaling to the far-end is only possible when ITU-T G.709 is enabled on both ends of the trunk span. 10.21 Jitter Considerations Jitter introduced by the SFPs used in the transponders and muxponders must be considered when cascading several cards. With TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, and TXP_MR_10E cards, several transponders can be cascaded before the cumulative jitter violates the jitter specification. The recommended limit is 20 cards. With TXP_MR_10G cards, you can also cascade several cards, although the recommended limit is 12 cards. With MXP_2.5G_10G and MXP_2.5G_10E Client Protected Card Working Protect Client Port RX TX Splitter Switch Trunk Port Trunk Port 12407910-143 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards Termination Modes cards, any number of cards can be cascaded as long as the maximum reach between any two is not exceeded. This is because any time the signal is demultiplexed, the jitter is eliminated as a limiting factor. The maximum reach between one transponder and the other must be halved if a Y cable is used. For more information on Y-cable operation, see the “10.19.1 Y-Cable Protection” section on page 10-139. 10.22 Termination Modes Transponder and muxponder cards have various SONET and SDH termination modes that can be configured using CTC (see the “Provision Transponder and Muxponder Cards” chapter in the Cisco ONS 15454 DWDM Procedure Guide). The termination modes are summarized in Table 10-64. For TXP and MXP cards, adhere to the following conditions while DCC termination provisioning: • For SDCC/RS-DCC provisioning, the card should be in the Section/RS-DCC or Line/MS-DCC termination mode. • For LDCC/MS-DCC provisioning, the card should be in the Line/MS-DCC termination mode. Table 10-64 Termination Modes Cards Termination Mode Description All TXP, MXP, and OTU2_XP cards, with the exception of the MXP_2.5G_10G card (see next section of this table) Transparent Termination All the bytes of the payload pass transparently through the cards. Section Termination The SONET transport overhead (TOH) section bytes and the SDH regenerator section overhead (SOH) bytes are terminated. None of these SOH bytes are passed through. They are all regenerated, including the SONET TOH section DCC (SDCC) bytes and the SDH regenerator section DCC (RS-DCC) bytes. In the section termination mode, the SONET TOH line and SDH multiplex section overhead bytes are passed transparently. Line Termination In line termination mode, the section and line overhead bytes for SONET and the overhead bytes for the SDH multiplex and regenerator sections are terminated. None of the overhead bytes are passed through. They are all regenerated, including the SONET SDCC and line DCC (LDCC) bytes and the SDH RS-DCC and multiplexer section DCC (MS-DCC) bytes. MXP_2.5G_10G1 1. Clients operating at the OC48/STM16 rate are multiplexed into an OC192/STM64 frame before going to OTN or DWDM. Transparent Termination All client bytes pass transparently except the following: B1 is rebuilt, S1 is rewritten, A1 to A2 are regenerated, and H1 to H3 are regenerated. Section Termination The SONET TOH section bytes and the SDH regenerator section overhead bytes are terminated. None of these section overhead bytes are passed through. They are all regenerated, including the SONET TOH section DCC bytes and the SDH RS-DCC bytes. In the section termination mode, the SONET TOH line and SDH multiplex section overhead bytes are passed transparently. Line Termination In the line termination mode, the section and line overhead bytes for SONET and the overhead bytes for the SDH multiplex and regenerators sections are terminated. None of the overhead bytes are passed through. They are all regenerated, including the SONET SDCC and LDCC bytes and the SDH RS-DCC and MS-DCC bytes.10-144 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 10 Transponder and Muxponder Cards SFP and XFP Modules For more information on enabling termination modes, see the procedures for changing card setting in the “Provision Transponder and Muxponder Cards” chapter of the Cisco ONS 15454 DWDM Procedure Guide. 10.23 SFP and XFP Modules SFPs and 10-Gbps SFPs (XFPs) are integrated fiber optic transceivers that provide high-speed serial links from a port or slot to the network. For more information on SFPs/XFPs and for a list of SFPs/XFPs supported by the transponder and muxponder cards, see the Installing the GBIC, SFP, and XFP Optics Modules in Cisco ONS Platforms. In CTC, SFPs/XFPs are called pluggable port modules (PPMs). To provision SFPs/XFPs and change the line rate for multirate PPMs, see the Cisco ONS 15454 DWDM Procedure Guide.CHAPTER 11-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 11 Node Reference This chapter explains the ONS 15454 dense wavelength division multiplexing (DWDM) node types that are available for the ONS 15454. The DWDM node type is determined by the type of amplifier and filter cards that are installed in an ONS 15454. The chapter also explains the DWDM automatic power control (APC), reconfigurable optical add/drop multiplexing (ROADM) power equalization, span loss verification, and automatic node setup (ANS) functions. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Note In this chapter, “OPT-BST” refers to the OPT-BST, OPT-BST-E, OPT-BST-L cards, and to the OPT-AMP-L and OPT-AMP-17-C cards when they are provisioned in OPT-LINE (optical booster) mode. “OPT-PRE” refers to the OPT-PRE card and to the OPT-AMP-L and OPT-AMP-17-C cards provisioned in OPT-PRE (preamplifier) mode. Chapter topics include: • 11.1 DWDM Node Configurations, page 11-1 • 11.2 Supported Node Configurations for OPT-RAMP-C and OPT-RAMP-CE Cards, page 11-34 • 11.3 Supported Node Configurations for PSM Card, page 11-38 • 11.4 Multishelf Node, page 11-42 • 11.5 Optical Sides, page 11-44 • 11.6 Configuring Mesh DWDM Networks, page 11-53 • 11.7 DWDM Node Cabling, page 11-74 • 11.8 Automatic Node Setup, page 11-90 • 11.9 DWDM Functional View, page 11-96 • 11.10 DWDM Network Functional View, page 11-106 11.1 DWDM Node Configurations The ONS 15454 supports the following DWDM node configurations: hub, terminal, optical add/drop multiplexing (OADM), reconfigurable OADM (ROADM), anti-amplified spontaneous emission (anti-ASE), line amplifier, optical service channel (OSC) regeneration line, multishelf nodes, and node 11-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations configurations for mesh networks. All node configurations can be provisioned with C-band or L-band cards except the OADM and anti-ASE nodes. These nodes require AD-xB-xx.x or AD-xC-xx.x cards, which are C-band only. All node configurations can be single-shelf or multishelf. Note The Cisco TransportPlanner tool creates a plan for amplifier placement and proper node equipment. Note To support multiple optical sides in mesh DWDM networks, east and west are no longer used to reference the left and right sides of the ONS 15454 shelf. If a network running a previous software release is upgraded to this release, west will be mapped to A and east to B. In two-sided nodes, such as a hub or ROADM node, Side A refers to Slots 1 through 6 and Side B refers to Slots 12 through 17. Terminal nodes have one side labeled “A,” regardless of which slots have cards installed. For more information about configuring the ONS 15454 in mesh DWDM networks, see the “11.6 Configuring Mesh DWDM Networks” section on page 11-53. 11.1.1 Terminal Node A terminal node is a single ONS 15454 node equipped with two TCC2/TCC2P/TCC3/TNC/TSC cards and one of the following combinations: • One 32MUX-O card and one 32DMX-O card • One 32WSS card and either a 32DMX or a 32DMX-O card • One 40-WSS-C or 40-WSS-CE card and one 40-DMX-C or 40-DMX-CE card • One 40-MUX-C and one 40-DMX-C or 40-DMX-CE card • One 80-WXC-C card, one 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel, and one 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN (ONS 15216 40 or 48-channel mux/demux patch panel), and 15216-MD-ID-50 or 15216-MD-48-CM • One 40-SMR1-C and one 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel • One 40-SMR2-C and one 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel Note Although it is recommended that you use the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel along with the 40-SMR1-C and 40-SMR2-C cards, you can alternatively use the 40-MUX-C and 40-DMX-C cards instead of the 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel. Cards in the terminal nodes can be installed in Slots 1 through 6 or Slots 12 through 17. The side where cards are installed is always assigned as Side A. Figure 11-1 shows an example of a terminal configuration with a 2MUX-O card installed. The channel flow for a terminal node is the same as the hub node (Figure 11-28).11-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-1 Terminal Node Configuration With 32MUX-O Cards Installed Figure 11-2 shows an example of a terminal configuration with a 40-WSS-C card installed. OPT-BST OPT-PRE 32MUX-O DCU Air ramp Available 32DMX-O TCC2/TCC2P/TCC3 OSCM AIC-I Available TCC2/TCC2P/TCC3 Available Available Available Available Available Available 24909511-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-2 Terminal Node Configuration with 40-WSS-C Cards Installed Figure 11-3 shows an example of a terminal configuration with a 40-MUX-C card installed. OPT-BST or OSC-CSM OPT-PRE or TXP/MXP 40-WSS-C DCM-xxx Air ramp DCM-xxx 40-DMX-C TCC2/TCC2P/TCC3 OSCM or Blank AIC-I Blank TCC2/TCC2P/TCC3 Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP 249104 Blank or TXP/MXP or MS-ISC-100T Blank or TXP/MXP or MS-ISC-100T11-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-3 Terminal Node with 40-MUX-C Cards Installed Figure 11-4 shows an example of a terminal configuration with a 40-SMR1-C card installed. OPT-BST or OSC-CSM OPT-PRE or TXP/MXP DCM-xxx Air ramp DCM-xxx 40-DMX-C 40-MUX-C Blank or TXP/MXP TCC2/TCC2P/TCC3 OSCM or Blank AIC-I Blank TCC2/TCC2P/TCC3 Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP 249105 Blank or TXP/MXP or MS-ISC-100T Blank or TXP/MXP or MS-ISC-100T11-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-4 Terminal Node with 40-SMR1-C Card Installed - Cisco ONS 15454 and Cisco ONS 15454 M6 Figure 11-5 shows an example of a terminal configuration with 40-SMR1-C and booster amplifier cards installed. 248993 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available Available 40-SMR1-C LCD Cisco ONS 15454 Cisco ONS 15454 M6 Available Available Cable guide Air filter 15216 Odd Patch Panel Booster 40-SMR1-C DCM-xxx Air Ramp DCM-xxx Av TCC2 ailable Available Available Available Available Available Available Available OSCM M AIC-I Empty TCC2 S-ISC MS-ISC 15216 Odd Patch Panel Fan Tray Fibre Routing Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-5 Terminal Node with 40-SMR1-C and Booster Amplifier Cards Installed - Cisco ONS 15454 and Cisco ONS 15454 M6 Note When you use the 40-SMR1-C card along with a booster amplifier, the OSCM card must be connected to the booster amplifier. Figure 11-6 shows an example of a terminal configuration with a 40-SMR2-C card installed. 248992 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available 40-SMR1-C Booster (A) LCD Cisco ONS 15454 M6 Available Available Cable guide Air filter 15216 Odd Patch Panel Cisco ONS 15454 Booster 40-SMR1-C DCM-xxx Air Ramp DCM-xxx Av TCC2 ailable Available Available Available Available Available Available Available OSCM M AIC-I Empty TCC2 S-ISC MS-ISC 15216 Odd Patch Panel Fan Tray Fibre Routing Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-6 Terminal Node with 40-SMR2-C Card Installed - Cisco ONS 15454 and Cisco ONS 15454 M6 11.1.2 OADM Node An OADM node is a single ONS 15454 node equipped with cards installed on both sides and at least one AD-xC-xx.x card or one AD-xB-xx.x card and two TCC2/TCC2P/TCC3/TNC/TSC cards. This configuration supports 32 channels. In an OADM node, channels can be added or dropped independently from each direction and then passed through the reflected bands of all OADMs in the DWDM node (called express path). They can also be passed through one OADM card to another OADM card without using a TDM ITU-T line card (called optical pass-through) if an external patchcord is installed. Unlike express path, an optical pass-through channel can be converted later to an add/drop channel in an altered ring without affecting another channel. OADM amplifier placement and required card placement is determined by the Cisco TransportPlanner tool or your site plan. OADM nodes can be amplified or passive. In amplified OADMs, booster and preamplifier cards are installed on bode sides of the node. Figure 11-7 shows an example of an amplified OADM node configuration. In addition, OADM nodes can be asymmetric. Amplifiers may be installed in one side, but not the other. Or preamplifiers may be installed in one side, and a booster in the other. 248994 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available Available 40-SMR2-C LCD Cisco ONS 15454 M6 Available Available Cable guide Air filter 15216 Odd Patch Panel Cisco ONS 15454 40-SMR2-C Available DCM-xxx Air Ramp DCM-xxx Av TCC2 ailable Available Available Available Available Available Available Available OSCM M AIC-I Empty TCC2 S-ISC MS-ISC 15216 Odd Patch Panel Fan Tray Fibre Routing Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-7 Amplified OADM Node Configuration Example Figure 11-8 shows an example of the channel flow on the amplified OADM node. Since the 32-wavelength plan is based on eight bands (each band contains four channels), optical adding and dropping can be performed at the band level and/or at the channel level (meaning individual channels can be dropped). OPT-BST OPT-PRE OADM or mux/demux DCU Air ramp DCU OADM or mux/demux OADM or mux/demux OADM TCC2/TCC2P/TCC3 OSCM AIC-I OSCM TCC2/TCC2P/TCC3 OADM OADM or mux/demux OADM or mux/demux OADM or mux/demux OPT-PRE OPT-BST 24909611-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-8 Amplified OADM Node Channel Flow Example 11.1.3 ROADM Node A ROADM node adds and drops wavelengths without changing the physical fiber connections. A ROADM node is equipped with two TCC2/TCC2P/TCC3/TNC/TSC cards and one of the following combinations: • Two 32WSS cards and optionally, two 32DMX or 32DMX-O cards • Two 40-WSS-C or 40-WSS-CE cards and optionally, two 40-DMX-C or 40-DMX-CE cards • Two 40-SMR1-C cards and two 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (ONS 15216 40 or 48-channel mux/demux) patch panels • Two 40-SMR2-C cards and two 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (ONS 15216 40 or 48-channel mux/demux) patch panels • Two 80-WXC-C cards and two 15216-MD-40-ODD, 15216-EF-40-ODD, 15216-MD-48-ODD, 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panels Note Although it is recommended that you use the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel along with the 40-SMR1-C and 40-SMR2-C cards, you can alternatively use the 40-MUX-C and 40-DMX-C cards instead of the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel. Transponders (TXPs) and muxponders (MXPs) can be installed in Slots 6 and 12 and, if amplification is not used, in any open slot. OPT-PRE 4-ch demux 4MD-xx.x OPT-PRE OPT-BST Line Line 96427 OPT-BST DCU DCU OSCM TCC TCC2 OSCM AIC-I AD-yB-xx.x AD-1C-xx.x AD-1C-xx.x AD-yB-xx.x By Ch Ch By 4-ch mux 4-ch demux 4MD-xx.x 4-ch mux11-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Note Although not required, 32DMX-O can be used in a ROADM node. Cisco TransportPlanner automatically chooses the demultiplexer card that is best for the ROADM node based on the network requirements. Figure 11-9 shows an example of an amplified ROADM node configuration with 32DMX cards installed. Figure 11-9 ROADM Node with 32DMX Cards Installed Figure 11-10 shows an example of an amplified ROADM node configuration with 40-WSS-C cards installed. OPT-PRE OPT-BST 32WSS DCU W Air ramp DCU E 32DMX Available TCC2/TCC2P/TCC3 OSCM AIC-I OSCM TCC2/TCC2P/TCC3 Available 32DMX 32WSS OPT-BST OPT-PRE 24909811-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-10 ROADM Node with 40-WSS-C Cards Installed Figure 11-11 shows an example of a ROADM node with 40-SMR1-C cards installed. 249103 OPT-BST or OSC-CSM OPT-PRE or TXP/MXP 40-WSS-C DCM-xxx Air ramp DCM-xxx 40-DMX-C Blank or TXP/MXP or MS-ISC-100T TCC2/TCC2P/TCC3 OSCM or Blank AIC-I OSCM or Blank TCC2/TCC2P/TCC3 Blank or TXP/MXP or MS-ISC-100T 40-DMX-C 40-WSS-C OPT-PRE or TXP/MXP OPT-BST or OSC-CSM11-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-11 ROADM Node with 40-SMR1-C Cards Installed - Cisco ONS 15454 and Cisco ONS 15454 M6 Figure 11-12 shows an example of a ROADM node with 40-SMR1-C and booster amplifier cards installed. 248990 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available Available 40-SMR1-C LCD Cisco ONS 15454 Cisco ONS 15454 M6 40-SMR1-C Available Cable guide Air filter 15216 Odd Patch Panel 15216 Odd Patch Panel 40-SMR1-C Available DCM-xxx Air Ramp DCM-xxx Av TCC2 ailable Available Available Available Available Available 40-SMR1-C Available OSCM OSCM M AIC-I TCC2 S-ISC MS-ISC 15216 Odd Patch Panel 15216 Odd Patch Panel Fan Tray Fibre Routing Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-12 ROADM Node with 40-SMR1-C and Booster Amplifier Cards Installed - Cisco ONS 15454 and Cisco ONS 15454 M6 Note When you use the 40-SMR1-C card along with a booster amplifier, the OSCM card must be connected to the booster amplifier. Figure 11-13 shows an example of a ROADM node with 40-SMR2-C cards installed. 248992 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available 40-SMR1-C Booster (A) LCD Cisco ONS 15454 M6 Available Available Cable guide Air filter 15216 Odd Patch Panel Cisco ONS 15454 Booster 40-SMR1-C DCM-xxx Air Ramp DCM-xxx Av TCC2 ailable Available Available Available Available Available Available Available OSCM M AIC-I Empty TCC2 S-ISC MS-ISC 15216 Odd Patch Panel Fan Tray Fibre Routing Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-13 ROADM Node with 40-SMR2-C Cards Installed - 15454 - Cisco ONS 15454 and Cisco ONS 15454 M6 248991 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available Available 40-SMR2-C LCD Cisco ONS 15454 Cisco ONS 15454 M6 40-SMR2-C Available Cable guide Air filter 15216 Odd Patch Panel 15216 Odd Patch Panel 40-SMR2-C Available DCM-xxx Air Ramp DCM-xxx Av TCC2 ailable Available Available Available Available Available Available 40-SMR2-C OSCM OSCM M AIC-I TCC2 S-ISC MS-ISC Fibre Routing Panel 15216 Odd Patch Panel 15216 Odd Patch Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan Tray 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-14 shows the layout of a 80-channel colored two-degree ROADM node. Figure 11-14 80-Channel Colored Two-Degree ROADM Node 248861 Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P Available Available Preamplifier Booster Available Available OSCM OSCM 8 AIC-I TCC2P 0-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray 15216 Even Patch Panel 15216 Odd Patch Panel 15216 Even Patch Panel 1 15216 Odd Patch Panel 1 2 2 1 1 2 2 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel 2 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel11-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations The 80-WXC-C cards are inserted in Slots 3 and 14, and function in the bidirectional mode. Figure 11-15 shows the layout of an ONS 15454 M6 80-channel colored two-degree ROADM node. Figure 11-15 ONS 15454 M6 80-Channel Colored Two-degree ROADM Node 333812 Shelf 2 ECU 1 2 3 4567 8 Fan tray 15216 Odd Patch Panel Shelf 1 15216 Even Patch Panel TNC/TSC Booster Preamplifier 80-WXC-C TNC/TSC Power module LCD Power module Available Available ECU 1 2 3 4567 8 Fan tray 15216-MD-40-ODD 15216-MD-40-EVEN TNC/TSC Preamplifier Booster 80-WXC-C TNC/TSC Power module LCD Power module Available Available Cable guide Cable guide Air filter Air filter 15216 Odd Patch Panel 15216 Even Patch Panel 1 2 1 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel 2 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-16 shows the layout of an 80-channel n-degree ROADM node with omni-directional side. Figure 11-16 80-Channel n-degree ROADM node with Omni-directional Side 248865 Preamplifier Preamplifier DCM-xxx Air ramp DCM-xxx Any other side TCC2 OSCM OSCM 8 AIC-I TCC2 0-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray 15216 Even Patch Panel 15216 Odd Patch Panel 1 2 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel 2 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel11-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-17 shows the layout of an ONS 15454 M6 80-channel n-degree ROADM node with omni-directional side. Figure 11-17 ONS 15454 M6 80-Channel n-degree ROADM node with Omni-directional Side Figure 11-18 shows the layout of a 40-channel n-degree ROADM node with a 40-WXC-C based colorless side. 248882 ECU 1 2 3 4567 8 Fan tray 15216 Even Patch Panel 15216 Odd Patch Panel TNC/TSC TNC/TSC Power module Power module Preamplifier Preamplifier 80-WXC-C LCD Available Available Cable guide Air filter 1 2 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel 2 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel11-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-18 40-Channel n-degree ROADM Node with 40-WXC-C Based Colorless Side The 80-WXC-C cards are connected to the ADD/DROP ports of the 40-WXC-C card and function as colorless multiplexer and demultiplexer units. 248858 Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P Available Available Available Available OSCM 8 AIC-I Empty TCC2P 0-WXC-C 8 40-WXC-C 0-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray11-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-19 shows the layout of a 40-channel four-degree ROADM node with a 40-SMR2-C based colorless side. Figure 11-19 40-Channel Four-degree ROADM Node with 40-SMR2-C Based Colorless Side The 80WXC-C (multiplexer) card is inserted in Slot 3 and the 80-WXC-C (demultiplexer) card is inserted in Slot 5. The 80-WXC-C cards are connected to the ADD/DROP ports of the 40-SMR2-C card and function as the colorless multiplexer and demultiplexer units. 248878 DCM-xxx Air ramp DCM-xxx TCC2P OSC-CSM OSC-CSM 40-SMR2-C 40-SMR2-C 40-SMR2-C 40-SMR2-C Available Available OSCM OSCM 8 AIC-I TCC2P 0-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray 15216 Odd Patch Panel 15216 Odd Patch Panel 15216 Odd Patch Panel 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-20 shows the layout for an 80-channel colorless ROADM node. Figure 11-20 80-Channel Colorless ROADM Node An 80 channel colorless two-degree ROADM node requires the following cards: 80-WXC-C, 15216-MD-40-ODD, 15216-EF-40-ODD, 15216-MD-48-ODD, 15216-MD-40-EVEN, 15216-EF-40-EVEN, 15216-MD-48-EVEN, preamplifiers, and boosters. The 80-WXC-C cards can be used at two levels; level1 (L1) and level2 (L2). The L1 80WXC-C (multiplexer) card is inserted in Slot 3 and the L1 80-WXC-C (demultiplexer) card is inserted in Slot 5. The L2 80WXC-C (multiplexer) card is inserted in Slot 12 and the L2 80-WXC-C (demultiplexer) card is inserted in Slot 14. 248863 Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P Available Available 8 Empty AIC-I Empty TCC2P 0-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C Fiber routing ranel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P Available Available OSCM OSCM 8 AIC-I TCC2P 0-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray Side A Side B 15216 Odd Patch Panel 15216 Even Patch Panel 15216-MD-40-ODD 15216-MD-40-EVEN 15216Odd Patch Panel 15216 Even Patch Panel 1 2 1 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel 2 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-21 shows an example of the optical signal flow in an 80-channel colorless two-degree ROADM node from Side A to Side B using 80-WXC-C cards. The optical signal flow from Side B to Side A follows an identical path. Figure 11-21 80-Channel Colorless Two-degree ROADM Node 248860 1x9 DMX L2 1x9 DMX L1 1x9 MUX L2 1x9 DMX L2 1x9 MUX L2 1x9 MUX L1 1x9 MUX L1 1x9 DMX L1 P Booster Side A Side B OSC Booster OSC DMX-E DMX-O MUX-E MUX-O DMX-O DMX-E MUX-O MUX-E P 1 The booster on Side A receives the composite optical signal. It separates the optical service channel from the optical payload and sends the payload to the preamplifier on Side A. 2 The preamplifier compensates for chromatic dispersion, amplifies the optical payload and sends it to the L1 80-WXC-C card (demultiplexer). 3 Up to eight colorless ports are available on the L1 80-WXC-C card if no colored wavelength is terminated. In Figure 11-21, two EAD ports are connected to 40-DMX-C or 40-DMX-CE cards, 15216-MD-40-ODD, 15216-EF-40-ODD, 15216-MD-48-ODD, 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN units where the colored odd and even wavelengths are dropped. The express wavelengths are sent to the L1 80-WXC-C card (multiplexer) on Side B where the wavelengths are multiplexed with other colored or colorless wavelengths. 4 The L1-80-WXC-C card on Side B sends the composite signal to the booster on Side B. 5 The booster on Side B receives the composite optical signal, adds the optical service channel to the optical payload and sends it to the transmission line. 6 It is possible to configure more colorless ports by cascading the 80-WXC-C cards at two levels. For example, to get 14 colorless ports connect one of the EAD ports of the L1 80-WXC-C card to another 80-WXC-C cards at level 2. There are five colorless ports on the L1 80-WXC-C card and nine colorless ports on the L2 80-WXC-C card. To achieve an 80 channel colorless configuration, connect nine L2 80-WXC-C cards to the nine EAD ports of the L1 80-WXC-C card.11-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-22 shows the layout for an 80-channel colorless ROADM node with OPT-RAMP-C cards. Figure 11-22 80-Channel Colorless ROADM Node with OPT-RAMP-C Card 248874 Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P OSCM OSCM 8 AIC-I TCC2P 0-WXC-C OPT-RAMP-C 80-WXC-C 80-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray Side A Side B 15216-MD-40-ODD 15216-MD-40-EVEN Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P OSCM OSCM 8 AIC-I TCC2P 0-WXC-C OPT-RAMP-C 80-WXC-C 80-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray 15216 Odd Patch Panel 15216 Even Patch Panel 15216 Even Patch Panel 15216 Odd Patch Panel 1 2 1 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel 2 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-23 shows an example of an ONS 15454 M6 80-channel two degree colorless ROADM node. Figure 11-23 ONS 15454 M6 80-Channel Two-degree Colorless ROADM Node The L1 80WXC-C (multiplexer) card is inserted in Slot 4 and the L1 80-WXC-C (demultiplexer) is inserted in Slot 6. The L2 80WXC-C (multiplexer) card is inserted in Slot 2 and the L2 80-WXC-C (demultiplexer) is inserted in Slot 4. 248873 Shelf 1 Shelf 2 ECU 1 2 3 4567 8 Fan tray 15216-MD-40-ODD 15216-MD-40-EVEN TNC/TSC Booster Preamplifier 80-WXC-C TNC/TSC Power module Power module 80-WXC-C LCD ECU 1 2 3 4567 8 Fan tray 15216 Odd Patch Panel 15216 Even Patch Panel TNC/TSC Preamplifier Booster 80-WXC-C TNC/TSC Power module Power module 80-WXC-C LCD Cable guide Air filter Cable guide Air filter 15216 Odd Patch Panel 15216 Even Patch Panel 1 2 1 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel 2 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-24 shows an example of a ROADM optical signal flow from Side A to Side B using the 32WSS or 40-WSS-C cards. The optical signal flow from Side B to Side A follows an identical path through the Side B OSC-CSM and 32WSS or 40-WSS-C cards. In this example, OSC-CSM cards are installed, hence OPT-BSTs are not needed. Figure 11-24 ROADM Optical Signal Flow Example Using 32WSS or 40-WSS-C Card Figure 11-25 shows an example of an ROADM optical signal flow from Side A to Side B using the 40-SMR1-C card. The optical signal flow from Side B to Side A follows an identical path through the Side B booster and 40-SMR1-C card. 1 The OSC-CSM receives the optical signal. It separates the optical service channel from the optical payload and sends the payload to the OPT-PRE module. 2 The OPT-PRE compensates for chromatic dispersion, amplifies the optical payload, and sends it to the 32WSS or 40-WSS-C/40-WSS-CE. 3 The 32WSS or 40-WSS-C/40-WSS-CE splits the signal into two components. The 80 percent component is sent to the DROP-TX port and the 20 percent component is sent to the EXP-TX port. 4 The drop component goes to the 32DMX card or 40-DMX-C/40-DMX-CE card where it is demultiplexed and dropped. 5 The express wavelength aggregate signal goes to the 32WSS or 40-WSS-C/40-WSS-CE on the other side where it is demultiplexed. Channels are stopped or forwarded based upon their switch states. Forwarded wavelengths are merged with those coming from the ADD path and sent to the OSC-CSM module. 6 The OSC-CSM combines the multiplexed payload with the OSC and sends the signal out the transmission line. 32-ch demux Side B OSC-CSM 115228 Side A OSC-CSM OSC Side B 32WSS Side A 32WSS 80/20 Side B 32DMX Add Add Drop 2 slots 1 slot Side B OPT-PRE Side B Line Side A OPT-PRE Side A Line 32-ch demux Side A 32DMX Drop 1 slot 32R_OAM 80/20 2 slots 32R_OAM 1 1 2 2 3 3 5 5 6 6 4 4 OSC11-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-25 ROADM Optical Signal Flow Example Using 40-SMR1-C Card 11.1.4 Hub Node A hub node is a single ONS 15454 node equipped with two TCC2/TCC2P/TCC3/TNC/TSC cards and one of the following combinations: • Two 32MUX-O cards and two 32DMX-O or 32DMX cards • Two 32WSS cards and two 32DMX or 32DMX-O cards 1 The booster receives the optical signal. It separates the optical service channel from the optical payload and sends the payload to the preamplifier module within the 40-SMR1-C card. 2 The preamplifier module compensates for chromatic dispersion, amplifies the optical payload, and sends it to the 70/30 splitter within the 40-SMR1-C card. 3 The 70/30 splitter splits the signal into two components. The 70 percent component is sent to the DROP-TX port and the 30 percent component is sent to the EXP-TX port. 4 The drop component goes to the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD card where it is demultiplexed and dropped. 5 The express wavelength aggregate signal goes to the 40-SMR1-C card on the other side where it is demultiplexed. Channels are stopped or forwarded based upon their switch states. Forwarded wavelengths are merged with those coming from the ADD path and sent to the booster module. 6 The booster combines the multiplexed payload with the OSC, amplifies it, and sends the signal out the transmission line. 276454 Side B Booster OSC Side B Line Side B 40-SMR1-C Side A 40-SMR1-C Side A Booster OSC Side A Line Side B MUX 15216-MD-40-ODD 70/30 70/30 Side A DMX 15216-MD-40-ODD Side B DMX 15216-MD-40-ODD Side A MUX 15216-MD-40-ODD Drop Drop 1 2 4 5 5 6 3 2 3 4 6 111-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations • Two 40-WSS-C or 40-WSS-CE cards and two 40-DMX-C or 40DMX-CE cards • Two 40-SMR1-C and two 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (ONS 15216 40 or 48-channel mux/demux patch panel) • Two 40-SMR2-C and two 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD Note Although it is recommended that you use the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD card along with the 40-SMR1-C and 40-SMR2-C cards, you can alternatively use the 40-MUX-C and 40-DMX-C cards instead of the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD card. Note The configuration for a hub node using 40-SMR1-C or 40-SMR2-C cards is identical to the ROADM node, except that there is no patchcord connecting the two 40-SMR1-C or 40-SMR2-C cards. For more details on the ROADM node configuration, see the “11.1.3 ROADM Node” section on page 11-10. Note The 32WSS/40-WSS-C/40-WSS-CE and 32DMX/32DMX-L/40-DMX-C/ 40-DMX-CE cards are normally installed in ROADM nodes, but they can also be installed in hub and terminal nodes. If the cards are installed in a hub node, the 32WSS/32WSS-L/ 40-WSS-C/40-WSS-CE express ports (EXP RX and EXP TX) are not cabled. A dispersion compensation unit (DCU) can also be added, if necessary. Figure 11-26 shows a hub node configuration with 32MUX-O and 32DMX-O cards installed. 11-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-26 Hub Node Configuration Example with 32-Channel C-Band Cards Figure 11-27 shows a 40-channel hub node configuration with 40-WSS-C cards installed. OPT-BST W OPT-PRE W 32MUX-O DCU Air ramp DCU 32DMX-O TCC2/TCC2P/TCC3 OSCM W AIC-I OSCM E TCC2/TCC2P/TCC3 32DMX-O 32MUX-O OPT-PRE E OPT-BST E 24909411-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-27 Hub Node Configuration Example with 40-WSS-C Cards Figure 11-28 shows the channel flow for a hub node. Up to 32 channels from the client ports are multiplexed and equalized onto one fiber. Then, multiplexed channels are transmitted to the OPT-BST amplifier. The OPT-BST output is combined with an output signal from the OSCM card and transmitted to the other side. Received signals are divided between the OSCM card and an OPT-PRE card. Dispersion compensation is applied to the signal received by the OPT-PRE amplifier, and it is then sent to the 32DMX-O card, which demultiplexes and attenuates the input signal. OPT-BST or OSC-CSM OPT-PRE or TXP/MXP 40-WSS-C DCM-xxx Air ramp DCM-xxx 40-DMX-C TCC2/TCC2P/TCC3 OSCM or Blank AIC-I Blank TCC2/TCC2P/TCC3 Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP Blank or TXP/MXP 249102 Blank or TXP/MXP or MS-ISC-100T Blank or TXP/MXP or MS-ISC-100T11-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-28 Hub Node Channel Flow Example 11.1.5 Anti-ASE Node In a mesh ring network, the ONS 15454 requires a node configuration that prevents ASE accumulation and lasing. An anti-ASE node can be created by configuring a hub node or an OADM node with some modifications. No channels can travel through the express path, but they can be demultiplexed and dropped at the channel level on one side and added and multiplexed on the other side. The hub node is the preferred node configuration when some channels are connected in pass-through mode. For rings that require a limited number of channels, combine AD-xB-xx.x and 4MD-xx.x cards, or cascade AD-xC-xx.x cards. See Figure 11-8 on page 11-10. Figure 11-29 shows an anti-ASE node that uses all wavelengths in the pass-through mode. Use Cisco TransportPlanner to determine the best configuration for anti-ASE nodes. Client equipment 32DMX-0 32MUX-0 32MUX-0 32DMX-0 OPT-PRE OPT-BST OPT-PRE West side East side OPT-BST Line Line 96426 DCU OSCM TCC TCC2 OSCM AIC-I DCU11-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-29 Anti-ASE Node Channel Flow Example 11.1.6 Line Amplifier Node A line amplifier node is a single ONS 15454 node that is used to amplify the optical signal in long spans. The line amplifier node can be equipped with one of the following sets of cards: • Two OPT-PRE cards, two OPT-BST cards, and two OSCM cards • Two OPT-PRE cards and two OSC-CSM cards • Two OPT-AMP-17-C cards and two OSCM cards • Two OPT-AMP-C cards and two OSCM cards Attenuators might also be required between each preamplifier and OPT-BST amplifier to match the optical input power value and to maintain the amplifier gain tilt value. Two OSCM cards are connected to the OPT-BST cards to multiplex the OSC signal with the pass-though channels. If the node does not contain a booster card, OSC-CSM cards must be installed instead of OSCM cards. Figure 11-30 shows an example of a line amplifier node configuration using OPT-BST, OPT-PRE, and OSCM cards. 4-ch demux 4MD-xx.x Line Express path open Line 96429 DCU DCU OSCM TCC TCC2 OSCM AIC-I B1 Ch Ch B1 4-ch mux 4-ch demux 4MD-xx.x 4-ch mux11-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Configurations Figure 11-30 Line Amplifier Node Configuration Example - Cisco ONS 15454 M6 and Cisco ONS 15454 M2 11.1.7 OSC Regeneration Node The OSC regeneration node is added to the DWDM networks for two purposes: • To electrically regenerate the OSC channel whenever the span links are 37 dB or longer and payload amplification and add/drop capabilities are not present. Cisco TransportPlanner places an OSC regeneration node in spans longer than 37 dB. The span between the OSC regeneration node and the next DWDM network site cannot be longer than 31 dB. • To add data communications network (DCN) capability wherever needed within the network. OSC regeneration nodes require two OSC-CSM cards, as shown in Figure 11-31. The cards are installed in each side of the shelf. 248987 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available Preamplifier (A) Booster (A) LCD Cisco ONS 15454 M6 LCD Booster (B) Preamplifier (B) Cable guide 1 2 3 TNC/TSC Preamplifier (B) Preamplifier (A) Cisco ONS 15454 M2 LCD 1 2 3 TNC/TSC OPT-AMP-C (B) OPT-AMP-C (A) Air filter11-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for OPT-RAMP-C and OPT-RAMP-CE Cards Figure 11-31 OSC Regeneration Line Node Configuration Example - Cisco ONS 15454, Cisco ONS 15454 M6, and Cisco ONS 15454 M2 Figure 11-32 shows the OSC regeneration line node signal flow. Figure 11-32 OSC Regeneration Line Node Flow 11.2 Supported Node Configurations for OPT-RAMP-C and OPT-RAMP-CE Cards The OPT-RAMP-C and OPT-RAMP-CE cards can be equipped in the following network element type configurations: • C-band odd systems: 248988 ECU 1 2 3 4567 8 Fan tray TNC/TSC TNC/TSC Power module Power module Available Available Available OSC-CSM (A) LCD Cisco ONS 15454 M6 Cisco ONS 15454 M2 OSC-CSM (B) Available Cable guide LCD 1 2 3 TNC/TSC OSC-CSM (B) OSC-CSM-C (A) Air filter Cisco ONS 15454 OSC-CSM Available DCU Air Ramp DCU Av TCC2/TCC2P ailable Available Available Available Available Available OSC-CSM Available Available Available Av AIC-I TCC2/TCC2P ailable Available Fan Tray Fibre Routing Panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 115255 Fiber Fiber Fiber Fiber Side B OSC-CSM Side A OSC-CSM Side B Side A COM-TX Line-TX Side B Side A COM-RX Line-RX Side B Side A COM-RX Side B Side A Side B Side A Side B Side A COM-TX11-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for OPT-RAMP-C and OPT-RAMP-CE Cards – C-band terminal site with 32-MUX-O and 32-DMX-O cards – C-band hub node with 32-MUX-O and 32-DMX-O cards – C-band fixed OADM node – C-band line site – C-band 32-channel reconfigurable OADM (ROADM) – C-band terminal site using a 32-WSS and 32-DMX cards – C-band flexible terminal site using AD-xC cards – C-band hub node using a 32-WSS and 32-DMX cards – C-band 40-channel ROADM – C-band terminal site using a 40-WSS-C and 40-DMX-C cards – C-band terminal site using 40-MUX-C and 40-DMX-C cards – C-band hub node using a 40-WSS-C and 40-DMX-C cards – C-band up to 4 degree mesh node – C-band up to 8 degree mesh node – C-band multiring/mesh with MMU node – C-band 4 degree multiring/mesh node (MMU based) • C-band odd and even systems: – C-band 64-channel terminal site – C-band 72-channel terminal site – C-band 80-channel terminal site – C-band 64-channel hub site – C-band 72-channel hub site – C-band 80-channel hub site – C-band 64-channel ROADM site – C-band 72-channel ROADM site – C-band 80-channel ROADM site The following amplifier cards are defined as booster or preamplifiers: • Booster: – OPT-BST – OPT-BST-E – OPT-AMP-17-C – OPT-AMP-C • Preamplifier: – OPT-PRE – OPT-AMP-C – OPT-BST – OPT-BST-E11-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for OPT-RAMP-C and OPT-RAMP-CE Cards Note When the booster is not needed, it must be replaced with an OSC-CSM card. The maximum number of shelves that can be aggregated in a multishelf node are: • Eight, if the MS-ISC-100T switch card is used. • Twelve, if an external Catalyst 2950 switch is used. 11.2.1 OPT-RAMP-C or OPT-RAMP-CE Card in an Add/Drop Node When the OPT-RAMP-C or OPT-RAMP-CE card is equipped in an add/drop node, the booster amplifier is mandatory and cannot be replaced by an OSC-CSM card. The preamplifier is an OPT-BST, OPT-BST-E, or OPT-AMP-C card, and must be cabled as an unidirectional card. Note that the COM-TX and LINE-RX ports must not be used for any other connections. If a single module ROADM 40-SMR-1-C is used as an add/drop card, a preamplifier is not required. If a single module ROADM 40-SMR-2-C is used as an add/drop card, both the preamplifier and booster are not required. Figure 11-33 shows the OPT-RAMP-C or OPT-RAMP-CE card in an add/drop node. Figure 11-33 OPT-RAMP-C or OPT-RAMP-CE Card in an Add/Drop Node When required, a DCN extension can be used on A/D Side (i) in Figure 11-33. Side (i) in Figure 11-33 can be equipped with the following cards: • WSS + DMX • AD-xC • 40-WXC-C or 80-WXC-C + MUX + DMX • Single module ROADM 11.2.2 OPT-RAMP-C or OPT-RAMP-CE Card in a Line Site Node with Booster Amplification The OPT-RAMP-C or OPT-RAMP-CE card can be equipped in a line site node with a booster amplifier in the following configurations: OSCM DCU OPT-RAMP A/D Side (i) Side (i) Booster 247380 DCU Pump Pre-amp11-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for OPT-RAMP-C and OPT-RAMP-CE Cards • OPT-BST and OPT-BST-E can be used as booster in a line site node with OPT-RAMP-C or OPT-RAMP-CE. The booster cards need to be cabled as bidirectional units. Figure 11-34 shows the OPT-RAMP-C or OPT-RAMP-CE card in a line site configuration. Figure 11-34 OPT-RAMP-C Card or OPT-RAMP-CE Card in a Line Site Configuration • The OPT-AMP-C can be used as a booster in a line site node with OPT-RAMP-C or OPT-RAMP-CE and needs to be cabled as a bidirectional unit. An additional DCU unit can be equipped between the OPT-AMP-C DC ports. Figure 11-35 shows a line site configured with OPT-AMP-C card and an additional DCU unit. Figure 11-35 Line Site Configured with OPT-AMP-C • A line site can be configured with OPT-RAMP-C or OPT-RAMP-CE card on one side only. Figure 11-36 shows the line site configured with OPT-RAMP-C or OPT-RAMP-CE on side A only. The booster is configured on side B. OSCM DCU OPT-RAMP Side B Booster Booster OPT-RAMP 247377 OSCM DCU Pump Pump OSCM DCU OPT-RAMP Side B Booster OPT-RAMP 247378 OSCM DCU DCU Pump Pump OPT-AMP-C11-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for PSM Card Figure 11-36 Line Site with OPT-RAMP-C or OPT-RAMP-CE On One Side In all configurations, the booster amplifier facing the OPT-RAMP-C or OPT-RAMP-CE card is mandatory for safety reasons. 11.3 Supported Node Configurations for PSM Card The PSM card supports the following node configurations: • 11.3.1 Channel Protection • 11.3.2 Multiplex Section Protection • 11.3.3 Line Protection • 11.3.4 Standalone 11.3.1 Channel Protection In a channel protection configuration, the PSM card is used in conjunction with a TXP/MXP card. The PSM card in a channel protection configuration can be used in any site apart from a terminal site. Figure 11-37 shows the DWDM functional view of a PSM card in channel protection configuration. OSCM DCU OPT-RAMP Side A Side B Booster 247379 DCU Pump OPT-AMP-C OSCM11-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for PSM Card Figure 11-37 PSM Channel Protection Configuration In this configuration, the COM-RX and COM-TX ports of the PSM card are connected to the TXP/MXP trunk ports. This configuration is applicable to an n-degree MSTP node, for example, a two-degree ROADM, an n-degree ROADM, or an OADM node. The example block diagram shows a two-degree node with Side A and Side B as the two sides. The Side A and Side B fiber-stage block can be DWDM cards that are used to amplify transmitted or received signal (see the “11.5.1.1 Fiber Stage” section on page 11-45 for the list of cards). The Side A and Side B add/drop stage block can be DWDM cards that can add and drop traffic (see the “11.5.1.2 A/D Stage” section on page 11-47 for the list of cards). In the transmit direction, the traffic originating from a TXP/MXP trunk port is split by the PSM card on to the W-TX and P-TX ports. The W-TX and P-TX ports are connected to the ADD-RX ports of the add/drop stage cards in Side A and Side B respectively. The add/drop stage cards multiplex traffic on Side A and Side B line ports that become the working and protect paths respectively. In the receive direction, the W-RX and P-RX ports of the PSM card are connected to the DROP-TX ports of the add/drop stage cards on Side A and Side B respectively. The add/drop stage cards demultiplex traffic received from Side A and Side B line ports that are the working and protect paths respectively. The PSM card selects one of the two input signals on the W-RX and P-RX ports to be transmitted to the COM-RX port of the PSM card. Note All traffic multiplexed or demultiplexed by the two add/drop stage cards is not protected. Fiber stage card COM-RX COM-TX COM-TX COM-RX EXP-RX DROP-TX ADD-RX Fiber stage card Side A Side A Side B Side B TXP/MXP TX RX Trunk port Working path Protect path W-RX PSM LINE-RX LINE-TX A/D stage card A/D stage card EXP-TX EXP-RX EXP-TX COM-RX COM-TX COM-RX COM-TX LINE-RX LINE-TX ADD-RX DROP-TX W-TX P-TX P-RX COM-RX COM-TX 1X2 Switch 50/50 Splitter 24308711-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for PSM Card 11.3.2 Multiplex Section Protection The PSM card performs multiplex section protection when connected between a multiplexer/demultiplexer card in a terminal site. The multiplexer/demultiplexer stage can be built using WSS and DMX or 40MUX and 40DMX cards. The terminal sites can be 50/100 Ghz band. The number of supported channels can therefore be 32/40 or 72/80. Figure 11-38 shows the block diagram of a PSM card in multiplex section protection configuration. Figure 11-38 PSM Multiplex Section Protection Configuration In the transmit direction, the traffic originating from a TXP trunk port is multiplexed by the Side A multiplexer. The PSM card splits traffic on to the W-TX and P-TX ports, which are independently amplified by two separated booster amplifiers. In the receive direction, the signal on the line ports is preamplified by two separate preamplifiers and the PSM card selects one of the two input signals on the W-RX and P-RX ports to be transmitted to the COM-RX port of the PSM card. The received signal is then demultiplexed to a TXP card. The presence of a booster amplifier is not mandatory. However, if a DCN extension is used, the W-TX and P-TX ports of the PSM card can be connected directly to the line. The presence of a preamplifier is also not mandatory. Note The PSM card cannot be used with Raman amplification in a line protection or section protection configuration. 11.3.3 Line Protection In a line protection configuration, the working and protect ports of the PSM card are connected directly to the external line. This configuration is applicable to any MSTP node that is configured as a terminal site. The multiplexer/demultiplexer stage can be built using WSS and DMX, 40MUX and 40DMX, COM-TX COM-RX ADD-RX DROP-TX Side A Mux/Demux Working Path Amplifier TXP/MXP TX RX Trunk port Working path Protect path W-RX PSM COM-RX COM-TX LINE-RX LINE-TX W-TX P-RX P-TX COM-TX COM-RX 1X2 Switch 50/50 Splitter Protect Path Amplifier COM-RX COM-TX LINE-RX LINE-TX 24308811-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Supported Node Configurations for PSM Card 40-SMR1-C and 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD, or 40-SMR2-C and 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD units. The terminal sites can be 50/100 Ghz band. The number of supported channels can therefore be 32/40 or 72/80. Figure 11-39 shows the block diagram of a PSM card in line protection configuration. Figure 11-39 PSM Line Protection Configuration In the transmit direction, the traffic originating from a transponder trunk port is multiplexed by the Side A multiplexer and amplified by a booster amplifier. The Line-TX port of the amplifier is connected to the COM-RX port of the PSM card. The PSM card splits traffic received on the COM-RX port on to the W-TX and P-TX ports, which form the working and protect paths. In the receive direction, the PSM card selects one of the two input signals on the W-RX and P-RX ports to be transmitted to the COM-RX port of the PSM card. The received signal is then preamplified and demultiplexed to the TXP card. The presence of a booster amplifier is not mandatory. However, if a DCN extension is used, the COM-RX port of the PSM card is connected to the multiplex section. The presence of a preamplifier is also not mandatory; the COM-TX port of the PSM card can be connected to the demultiplexer. Note The PSM card cannot be used with Raman amplification in a line protection or section protection configuration. 11.3.4 Standalone In a standalone configuration, the PSM card can be equipped in any slot and supports all node configurations. In this configuration, the PSM card provides only basic functionality, such as, protection against a fiber cut, optical safety, and automatic laser shutdown (ALS). It does not provide other functionalities such as, automatic power control (APC), automatic node setup (ANS), network and node alarm correlation, circuit management, and so on. COM-TX COM-RX ADD-RX DROP-TX TXP/MXP Side A Mux/Demux TX RX Trunk port Working path Protect path W-RX PSM W-TX P-RX P-TX COM-TX COM-RX 1X2 Switch 50/50 Splitter LINE-RX COM-TX LINE-TX COM-RX Side A Amplifier 24308911-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Multishelf Node 11.4 Multishelf Node In a multishelf configuration, the ONS 15454-M6 node or the ONS 15454-DWDM node with TCC3 card as the node controller can manage up to 29 subtending shelves as a single entity. The subtending shelves can be 15454-M6 or 15454-DWDM. The node controller is the main shelf with the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards running the multishelf functions. Each subtending shelf must be equipped with TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards, which run the shelf functions. For internal data exchange between the node controller shelf and subtending shelves, the node controller shelf must be equipped with redundant MS-ISC-100T cards or, as an alternative, the Catalyst 2950 switch. We recommend that you use the MS-ISC-100T cards. If using the Catalyst 2950, it is installed on one of the multishelf racks. All subtending shelves must be located in the same site at a maximum distance of 100 meters or 328 feet from the Ethernet switches used to support the communication LAN. Figure 11-40 shows an example of a multishelf node configuration. Figure 11-40 Multishelf Node Configuration 145236 Air Ramp Storage Air Ramp PDP Air Ramp "Y" Cable 15216 "Y" Cable 15216 Storage DCU 15216 Patch panel Patch panel MSTP - TXP/MXP MSTP - DWDM ETSI MSTP - TXP/MXP or MSPP MSTP - TXP/MXP Air Ramp MSTP - TXP/MXP Air Ramp MSTP - TXP/MXP ETSI MSTP - TXP/MXP or MSPP MSTP - TXP/MXP Air Ramp MSTP - TXP/MXP Air Ramp MSTP - TXP/MXP11-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Multishelf Node A multishelf node has a single public IP address for all client interfaces (Cisco Transport Controller [CTC], Transaction Language One [TL1], Simple Network Management Protocol [SNMP], and HTTP); a client can only connect to the node controller shelf, not to the subtending shelves. The user interface and subtending shelves are connected to a patch panel using straight-through (CAT-5) LAN cables. The node controller shelf has the following functions: • IP packet routing and network topology discovery at the node controller level. • Open Shortest Path First (OSPF) centralized on the node controller shelf. The subtending shelves have the following functions: • Overhead circuits are not routed within a multishelf node but are managed at the subtending controller shelf only. To use overhead bytes, the AIC-I must be installed on the subtending shelf where it is terminated. • Each subtending shelf will act as a single shelf node that can be used as a timing source line, TCC/TCC2P/TCC3/TNC/TSC clock, or building integrated timing supply (BITS) source line. 11.4.1 Multishelf Node Layout Multishelf configurations are configured by Cisco TransportPlanner and are automatically discovered by the CTC software. In a typical multishelf installation, all optical units are equipped on the node controller shelf and TXP/MXP cards are equipped in the aggregated subtended shelves. In addition, all empty slots in the node controller shelf can be equipped with TXP/MXP cards. In a DWDM mesh network, up to eight optical sides can be configured with client and optical cards installed in different shelves to support mesh and ring-protected signal output. Note When a DWDM ring or network has to be managed through a Telcordia operations support system (OSS), every node in the network must be set up as multi-shelf. OLA sites and nodes with one shelf must be set up as "multi-shelf stand-alone" to avoid the use of LAN switches. 11.4.2 DCC/GCC/OSC Terminations A multishelf node provides the same communication channels as a single-shelf node: • OSC links terminate on OSCM/OSC-CSM cards. Two links are required between each ONS 15454 node. An OSC link between two nodes cannot be substituted by an equivalent generic communications channel/data communications channel (GCC/DCC) link terminated on the same pair of nodes. OSC links are mandatory and they can be used to connect a node to a gateway network element (GNE). • GCC/DCC links terminate on TXP/MXP cards. The maximum number of DCC/GCC/OSC terminations that are supported in a multishelf node is 48. Note Optical Service Channel can be created on the OC3 port of the TNC card.11-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides 11.5 Optical Sides From a topological point of view, all DWDM units equipped in an MSTP node belongs to a side. A side can be identified by a letter (A, B, C, D, E, F, G, or H), or by the ports (called as side line ports, see 11.5.2 Side Line Ports, page 11-47) that are physically connected to the spans. An MSTP node can be connected to a maximum of 8 different spans. Each side identifies one of the spans the MSTP node is connected to. Note Side A and Side B replace “west” and “east” when referring to the two sides of the ONS 15454 shelf. Side A refers to Slots 1 through 6 (formerly “west”), and Side B refers to Slots 12 through 17 (formerly “east”). The line direction port parameter, East-to-West and West-to-East, has been removed. Sides are viewed and managed from the Provisioning > WDM-ANS > Optical Sides tab in CTC. 11.5.1 Optical Side Stages All MSTP nodes can be modelled according to Figure 11-41. Figure 11-41 Interconnecting Sides Conceptual View According to Figure 11-41, each MSTP node side includes DWDM units that can be conceptually divided into three stages. • Fiber stage—The set of DWDM cards with ports that directly or indirectly face the span. • A/D stage—The add/drop stage. 159460 Fiber Stage Side A A/D Stage Side E Interconnecting sides I/F TXP/MXP Stage Side F Side B Side G Side C Side H Side D11-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides • TXP/MXP stage—The virtual grouping of all TXP or MXP cards with signals multiplexed or demultiplexed to and from the physical fiber stage. 11.5.1.1 Fiber Stage The fiber stage includes DWDM cards that are used to amplify transmitted or received signals and cards that are used to add optical supervision channels. The fiber stage cards are: • Booster amplifier cards that directly connect to the span, such as: – OPT-BST – OPT-BST-E – OPT-BST-L – OPT-AMP-C, when provisioned in OPT-LINE (booster amplifier) mode – OPT-AMP-L, when provisioned in OPT-LINE (booster amplifier) mode – OPT-AMP-17-C, when provisioned in OPT-LINE (booster amplifier) mode • Preamplifier cards, such as: – OPT-PRE – OPT-AMP-C, when provisioned in OPT-PRE (preamplifier) mode – OPT-AMP-L, when provisioned in OPT-PRE (preamplifier) mode – OPT-AMP-17-C, when provisioned in OPT-PRE (preamplifier) mode • OSC cards, such as: – OSCM – OSC-CSM • OPT-RAMP-C card Table 11-1 shows the commonly deployed fiber stage layouts supported by DWDM mesh nodes. In the table, OPT-BST includes the OPT-BST, OPT-BST-E, and OPT-BST-L cards. OPT-AMP includes the OPT-AMP-L and OPT-AMP-17-C cards configured in either OPT-PRE or OPT-LINE mode. Note In the table, L and C suffix is not reported because C-band and L-band amplifiers cannot be mixed in the same layout.11-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides Table 11-1 Supported Fiber Stage Configurations Layout Cards Configurations A OPT-BST <-> OPT-PRE/OPT-AMP (OPT-PRE mode) • OPT-BST OSC ports connected to OSCM OSC ports or OSC-CSM LINE ports • OPT-BST LINE ports connected to the span • OPT-BST COM-TX ports connected to OPT-AMP (OPT-PRE mode) or OPT-PRE COM-RX ports • OPT-AMP (OPT-PRE mode) or OPT-PRE LINE-TX or COM-TX ports connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM-RX port in a ROADM node) • OPT-BST COM-RX ports connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM-TX port in a ROADM node) B OPT-AMP (OPT-BST mode) <-> OPT-PRE/OPT-AMP (OPT-PRE mode) • OPT-AMP (BST) OSC ports connected to OSCM OSC ports or OSC-CSM LINE ports • OPT-AMP (BST) LINE ports connected to the span • OPT-AMP (BST) COM-TX ports connected to OPT-AMP (PRE)/OPT-PRE COM-RX ports • OPT-AMP (PRE)/OPT-PRE LINE-TX/COM-TX port connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM-RX port in a ROADM node) • OPT-AMP (BST) COM-RX port connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM-TX port in a ROADM node) C OSC-CSM <-> OPT-PRE/OPT-AMP(OPT-PRE mode) • OSC-CSM LINE ports connected to the span • OSC-CSM COM-TX ports connected to OPT-AMP COM-RX ports • OPT-AMP(PRE)/OPT-PRE LINE-TX/COM-TX port connected to the next stage (for example, 40-WSS-C/40-WSS-CE COM-RX ports in ROADM) • OSC-CSM COM-RX port connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM-TX port in a ROADM node) D OPT-BST • OPT-BST OSC ports connected to OSCM OSC ports or OSC-CSM LINE ports • OPT-BST LINE ports connected to the span • OPT-BST COM ports connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM port in a ROADM node) 11-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides 11.5.1.2 A/D Stage The A/D stage includes DWDM cards that can add and drop traffic. The A/D stage is divided into three node types: • Mesh nodes—ONS 15454 nodes configured in multishelf mode can connect to eight different sides. For more detail on mesh node, see 11.6 Configuring Mesh DWDM Networks, page 11-53. • Legacy—Half of a ROADM node or an OADM node with cascaded AD-xB-xx-x or AD-xC-xx.x cards • Non-A/D—A line node or a side that does not have A/D capability is included in the A/D stage Stages are built by active cards and patchcords. However, the interconnecting sides are completed by the mesh patch panels (four-degree patch panel or eight-degree patch panel) in mesh nodes, or by patchcords connected to EXP-RX/EXP-TX ports in legacy nodes. 11.5.2 Side Line Ports Side line ports are ports that are physically connected to the spans. Side line ports can be: • All ports terminating the fiber stage and physically labeled as LINE, such as ports on the following cards: – Booster amplifier (OPT-BST, OPT-BST-E, or OPT-BST-L cards, and the OPT-AMP-C, OPT-AMP-L, or OPT-AMP-17-C cards when provisioned in OPT-LINE mode) – OSC-CSM – OPT-RAMP-C • All ports that can be physically connected to the external span using DCN terminations, such as: – Booster amplifier LINE-RX and LINE-TX ports – OSC-CSM LINE-RX and LINE-TX ports – 40-WXC-C COM-RX and COM-TX ports – MMU EXP-A-RX and EXP-A-TX ports • All ports that can be physically connected to the external span using DCN terminations in a line node, such as: E OPT-AMP (OPT-BST mode) • OPT-AMP OSC ports connected to OSCM OSC ports or OSC-CSM LINE ports • OPT-AMP LINE ports connected to the span • OPT-AMP COM ports connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM port in a ROADM node) F OSC-CSM • OSC-CSM LINE ports connected to the span • OSC-CSM COM ports connected to the next stage (for example, a 40-WSS-C/40-WSS-CE COM port in a ROADM node) Table 11-1 Supported Fiber Stage Configurations (continued) Layout Cards Configurations11-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides – Preamplifier (OPT-PRE card and the OPT-AMP-C, OPT-AMP-L, or OPT-AMP-17-C cards when provisioned in OPT-PRE mode) COM-RX and COM-TX ports – Booster amplifier COM-TX port – OSC-CSM COM-TX port • All ports that can be physically connected to the external span using DCN terminations in a 40-channel MUX/DMX terminal node, such as: – 40-MUX-C COM-TX port – 40-DMX-C COM-RX port • All ports that can be physically connected to the external span when PSM cards implement line protection: – PSM W-TX and W-RX ports – PSM P-TX and P-RX ports Note PSM card will support two sides A(w) and A(p). 11.5.3 Optical Side Configurations You can use the following Side IDs depending on the type of node layout: • In legacy nodes (that is, a node with no provisioned or installed 40-WXC-C cards), the permissible Side IDs are only A and B. • In four-degree mesh nodes with four or less 40-WXC-C cards installed, the permissible Side IDs are A, B, C, and D. • In eight-degree mesh nodes with eight or less 40-WXC-C cards installed, the allowed Side IDs are A, B, C, D, E, F, G, and H. The system automatically assigns Side IDs when you import the CTP XML configuration file into CTC. You can create a side manually using CTC or TL1 if the following conditions are met: • You use a permissible side identifier, A through H. • The shelf contains a TX and an RX side line port (see the “11.5.2 Side Line Ports” section on page 11-47). • The side line ports are not connected to an internal patchcord. Note We do not recommend that you manually create or modify ONS 15454 optical sides. The following tables show examples of how the system automatically assigns Side IDs for common DWDM layouts. Table 11-2 shows a standard ROADM shelf with Sides A and B provisioned. The shelf is connected to seven shelves containing TXP, MXP, ADM-10G, GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.11-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides Table 11-3 shows a protected ROADM shelf. In this example, Side A and B are Slots 1 through 6 in Shelves 1 and 2. 40-WSS-C/40-WSS-CE/40-DMX-C or 40-WSS-CE/40-DMX-CE cards are installed in Sides A and B. Slots 12 through 17 in Shelves 1 and 2 contain TXP, MXP, ADM-10G, GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. Table 11-4 shows a four-degree mesh node. Side A is Shelf 1, Slots 1 through 6. Side B and C are Shelf 2, Slots 1 through 6 and 12 through 17, and Side D is Shelf 3, Slots 1 through 6. 40-WXC-C cards in line termination mode are installed in Sides A through D. Table 11-2 Multishelf ROADM Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WSS+DMX A WSS+DMX B 2 TXP/MXP — TXP/MXP — 3 TXP/MXP — TXP/MXP — 4 TXP/MXP — TXP/MXP — 5 TXP/MXP — TXP/MXP — 6 TXP/MXP — TXP/MXP — 7 TXP/MXP — TXP/MXP — 8 TXP/MXP — TXP/MXP — Table 11-3 Multishelf Protected ROADM Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WSS+DMX A TXP/MXP — 2 WSS+DMX B TXP/MXP — 3 TXP/MXP n/a TXP/MXP — 4 TXP/MXP n/a TXP/MXP — 5 TXP/MXP n/a TXP/MXP — 6 TXP/MXP n/a TXP/MXP — 7 TXP/MXP n/a TXP/MXP — 8 TXP/MXP n/a TXP/MXP — Table 11-4 Multishelf Four-Degree Mesh Node Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC Line Termination A TXP/MXP — 2 WXC Line Termination B WXC Line Termination C 3 WXC Line Termination D TXP/MXP — 4 TXP/MXP n/a TXP/MXP —11-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides Table 11-5 shows a protected four-degree mesh node example. In the example, Sides A through D are assigned to Slots 1 through 6 in Shelves 1 through 4. Table 11-6 shows a protected four-degree mesh node example. In the example, Sides A through D are assigned to Slots 1 through 4 in Shelves 1 through 4, and TXP, MXP, ADM-10G, GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards are installed in Shelves 1 through 4, Slots 12-17, and Shelves 5 through 8, Slots 1 through 6 and 12 through 17. 5 TXP/MXP n/a TXP/MXP — 6 TXP/MXP n/a TXP/MXP — 7 TXP/MXP n/a TXP/MXP — 8 TXP/MXP n/a TXP/MXP — Table 11-4 Multishelf Four-Degree Mesh Node Layout Example (continued) Shelf Slots 1–6 Side Slots 12–17 Side Table 11-5 Multishelf Four-Degree Protected Mesh Node Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC Line Termination A TXP/MXP — 2 WXC Line Termination B TXP/MXP — 3 WXC Line Termination C TXP/MXP — 4 WXC Line Termination D TXP/MXP — 5 TXP/MXP — TXP/MXP — 6 TXP/MXP — TXP/MXP — 7 TXP/MXP — TXP/MXP — 8 TXP/MXP — TXP/MXP — Table 11-6 Multishelf Four-Degree Protected Mesh Node Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC Line Termination A TXP/MXP — 2 WXC Line Termination B TXP/MXP — 3 WXC Line Termination C TXP/MXP — 4 WXC Line Termination D TXP/MXP — 5 TXP/MXP — TXP/MXP — 6 TXP/MXP — TXP/MXP —11-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides Table 11-7 shows a four-degree mesh node provisioned as an upgrade. In the example, Sides A through D are assigned to Slots 1 through 4. and 12 through 17 in Shelves 1and 2. 40-WXC-C cards in XC termination mode are installed in Sides A and B, and 40-WXC-C cards in line termination mode are installed in Sides C and D. Table 11-8 shows an eight-degree mesh node. In the example, Sides A through H are assigned to Slots 1 through 6 in Shelf 1, Slots 1 through 6 and 12 through 17 in Shelves 2 through 4, and Slots 1 through 6 in Shelf 5. 40-WXC-C cards in line termination mode are installed in Sides A through H. 7 TXP/MXP — TXP/MXP — 8 TXP/MXP — TXP/MXP — Table 11-6 Multishelf Four-Degree Protected Mesh Node Layout Example (continued) Shelf Slots 1–6 Side Slots 12–17 Side Table 11-7 Multishelf Four-Degree Mesh Node Upgrade Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC XC Termination A WXC XC Termination B 2 WXC Line Termination C WXC Line Termination D 3 TXP/MXP — TXP/MXP — 4 TXP/MXP — TXP/MXP — 5 TXP/MXP — TXP/MXP — 6 TXP/MXP — TXP/MXP — 7 TXP/MXP — TXP/MXP — 8 TXP/MXP — TXP/MXP — Table 11-8 Multishelf Eight-Degree Mesh Node Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC Line Termination A TXP/MXP — 2 WXC Line Termination B WXC Line Termination C 3 WXC Line Termination D WXC Line Termination E 4 WXC Line Termination F WXC Line Termination G 5 WXC Line Termination H TXP/MXP — 6 TXP/MXP — TXP/MXP — 7 TXP/MXP — TXP/MXP — 8 TXP/MXP — TXP/MXP —11-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Optical Sides Table 11-9 shows another eight-degree mesh node. In the example, Sides A through H are assigned to Slots 1 through 6 in all shelves (Shelves 1 through 8). 40-WXC-C cards in line termination mode are installed in Sides A through H. Table 11-10 shows a four-degree mesh node with a user-defined side. Because the software assigns sides consecutively, and because the mesh node is four-degrees, the side assigned to Shelf 5, Slots 1 through 6 is “Unknown.” Table 11-9 Multishelf Four-Degree Mesh Node Upgrade Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC Line Termination A TXP/MXP — 2 WXC Line Termination B TXP/MXP — 3 WXC Line Termination C TXP/MXP — 4 WXC Line Termination D TXP/MXP — 5 WXC Line Termination E TXP/MXP — 6 WXC Line Termination F TXP/MXP — 7 WXC Line Termination G TXP/MXP — 8 WXC Line Termination H TXP/MXP — Table 11-10 Multishelf Four-Degree Mesh Node User-Defined Layout Example Shelf Slots 1–6 Side Slots 12–17 Side 1 WXC Line Termination A TXP/MXP — 2 TXP/MXP — WXC Line Termination C 1 1. User-defined 3 WXC Line Termination D TXP/MXP — 4 TXP/MXP — TXP/MXP — 5 WXC Line Termination U 2 2. Unknown TXP/MXP — 6 TXP/MXP — TXP/MXP — 7 TXP/MXP — TXP/MXP — 8 TXP/MXP — TXP/MXP —11-53 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks 11.6 Configuring Mesh DWDM Networks ONS 15454 shelves can be configured in mesh DWDM networks using the 40-WXC-C or 80-WXC-C wavelength cross-connect cards and four-degree patch panel or eight-degree patch panels. Mesh DWDM networks can also be configured using the 40-SMR2-C cards and the four-degree patch panel. ONS 15454 DWDM mesh configurations can be up to four degrees (four optical directions) when the four-degree patch panel is installed, and up to eight degrees (eight optical directions) when the eight-degree patch panel is installed. Two mesh node types are available, the line termination mesh node and the cross-connect (XC) termination mesh node. Note Mesh nodes using the 40-WXC-C or 80-WXC-C card requires multishelf management. 11.6.1 Line Termination Mesh Node Using 40-WXC-C Cards The line termination mesh node is installed in native Software Release 9.2 mesh networks. Line termination mesh nodes can support between one and eight line terminations. Each line direction requires the following cards: 40-WXC-C, 40-MUX-C, 40-DMX-C or 40-DMX-CE, a preamplifier and a booster. Within this configuration, the following substitutions can be used: • The 40-MUX-C cards can be replaced with 40-WSS-C/40-WSS-CE cards. • The OPT-BST cards can be replaced with OPT-AMP-17-C (in OPT-BST mode) and/or OPT-BST-E cards. • The OPT-PRE can be replaced with an OPT-AMP-17-C (in OPT-LINE mode) card. Each side of the line termination mesh node is connected as follows: • The 40-WXC-C COM-RX port is connected to the preamplifier output port. • The 40-WXC-C COM-TX port is connected to the booster amplifier COM-RX port. • The 40-WXC-C DROP TX port is connected to the 40-DMX-C or 40-DMX-CE COM-RX port. • The 40-WXC-C ADD-RX port is connected to the 40-MUX-C COM-TX port. • The 40-WXC-C EXP-TX port is connected to the mesh patch panel. • The 40-WXC-C EXP-RX port is connected to the mesh patch panel. Figure 11-42 shows one shelf from a line termination node.11-54 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-42 Line Termination Mesh Node Shelf Figure 11-43 shows a functional block diagram of one line termination side using 40-WXC-C and 40-MUX-C cards. OPT-BST OPT-PRE 40-WXC-C DCU-xxx Air ramp DCU-xxx 40-MUX-C 40-DMX-C TCC2/TCC2P/TCC3 OSCM AIC-I OSCM TCC2/TCC2P/TCC3 40-DMX-C 40-MUX-C 40-WXC-C OPT-PRE OPT-BST 24910111-55 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-43 Line Termination Mesh Node Side—40-MUX-C Cards Figure 11-44 shows a functional block diagram line termination side using 40-WXC-C and 40-WSS-C cards. 40WXC 40-DMX-C Drop Add to/from PP-MESH-4 or PP-MESH-8 OPT-PRE AMP-BST 159332 OSCM DCM 40-MUX-C 70/3011-56 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-44 Line Termination Mesh Node Side—40-WSS-C Cards Figure 11-45 shows a functional block diagram of a node that interconnects a ROADM with MMU cards with two native line termination mesh sides. 40-WXC-C 40-DMX-C Drop Add OPT-PRE AMP-BST 159333 OSCM DCM 40-WSS-C 70/30 70/30 to/from PP-MESH-4 or PP-MESH-811-57 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-45 Line Termination Mesh Nodes—ROADM With MMU Cards 159336 ADD OPT-PRE OPT-BST Line OSCM DCM xxWSS MMU 70/30 xxDMX DROP xxDMX DROP 40-DMX-C DROP 40-DMX-C DROP 40-MUX-C ADD 40-MUX-C ADD ADD OPT-BST Line DCN Extension OSCM TCC TCC OPT-PRE DCM xxWSS MMU 70/30 OPT-PRE OPT-BST Line OSCM DCM OPT-BST Line OSCM OPT-PRE DCM 40-WXC-C Node A Node B 40-WXC-C 40-WXC-C AMP-17-C PP-MESH-4 AMP-17-C 70/30 40-WXC-C 70/3011-58 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks 11.6.1.1 40-Channel Omni-directional n-degree ROADM Node Any side in the line termination mesh node can be configured as an omni-directional side. The side that is configured as the omni-directional side is connected to a local multiplexer and demultiplexer that can add or drop traffic to or from any of the node directions. In Figure 11-46 side D is configured as the omni-directional side. Wavelengths from the local multiplexer on side D is routed to sides A, B, or C by the patch panel. Wavelengths from sides A, B, or C can be dropped on side D. The maximum number of omni-directional channels is 40. Figure 11-46 40-Channel Omni-directional Four-Degree ROADM Node 11.6.1.2 40-Channel Colorless n-Degree ROADM Node Any side in the line termination mesh node can be configured as a colorless side where any wavelength can be added or dropped. The side that is configured as the colorless side is connected to two 80-WXC-C cards configured as a multiplexer and demultiplexer respectively. In Figure 11-47 side D is configured as the colorless side. The 80-WXC-C cards are connected to the add and drop ports of the 40-WXC-C cards and function as a colorless multiplexer and demultiplexer. A combination of wavelengths from any of the nine ports is sent to the common output port of the 80-WXC-C card (multiplexer) that is connected to the 40-WXC-C card. The wavelengths entering the 40-WXC-C card are sent to the common input port of the 80-WXC-C card (demultiplexer) and dropped at any of the nine output ports. 40-WXC-C 40-WXC-C 40-WXC-C 40-WXC-C PP-MESH-4 248859 A C D B P P DMX MUX11-59 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-47 40-Channel Colorless Four-Degree ROADM Node 11.6.1.3 40-Channel Colorless and Omni-directional n-Degree ROADM Node Any side in the line termination mesh node can be configured as a colorless and omni-directional side. The side that is configured as the colorless and omni-directional side is connected to a multiplexer (80-WXC-C) and demultiplexer (80-WXC-C) that can add or drop traffic to or from any of the node directions. Figure 11-48 shows the layout of a 40-channel n-degree ROADM node with colorless and omni-directional side. Colorless side 40-WXC-C 40-WXC-C 40-WXC-C 40-WXC-C 80-WXC-C 80-WXC-C PP-MESH-4 248856 A C D B11-60 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-48 40-Channel n-Degree ROADM Node with Colorless and Omni-directional Side In Figure 11-49 side D is configured as the colorless and omni-directional side. A combination of wavelengths from any of the nine ports is sent to the common output port of the 80-WXC-C card (multiplexer) and then routed to the preamplifier. The preamplifier sends the wavelengths to the 40-WXC-C card that is connected to the patch panel. The patch panel routes the wavelengths to sides A, B, or C. Wavelengths from sides A, B, or C are dropped on side D. The incoming wavelengths from the 40-WXC-C card are sent to the preamplifier. The preamplifer amplifies the signal and sends it to the common input port of the 80-WXC-C card (demultiplexer). The wavelengths are then dropped at any of the nine output ports. 248876 DCM-xxx Air ramp DCM-xxx TCC2P Available Available Available Available Preamplifier Preamplifier 8 Empty AIC-I Empty TCC2P 0-WXC-C 80-WXC-C 40-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray11-61 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-49 40-Channel Colorless and Omni-directional Four-Degree ROADM Node 11.6.2 Line Termination Mesh Node Using 80-WXC-C Cards Line termination mesh nodes using 80- WXC-C cards can support between one and eight line terminations. Each line direction requires the following units: 80-WXC-C, 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD, and 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN, 15216-MD-ID-50 or 15216-MD-48-CM, a preamplifier, and a booster. • The OPT-BST cards can be replaced with OPT-AMP-17-C (in OPT-BST mode) or OPT-BST-E cards. • The OPT-PRE can be replaced with an OPT-AMP-17-C (in OPT-LINE mode) card. Each side of the line termination mesh node is connected as follows: • The 80-WXC-C COM-RX port is connected to the preamplifier output port. • The 80-WXC-C COM port is connected to the booster amplifier COM-RX port. • The 80-WXC-C DROP TX port is connected to the COM-RX (ODD+EVEN-RX) port of 15216-MD-ID-50 or 15216-MD-48-CM. The ODD-TX port of the 15216-MD-ID-50 or 15216-MD-48-CM is connected to the COM-RX port of 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD; and the EVEN-TX port of the 15216-MD-ID-50 or 15216-MD-48-CM is connected to the COM-RX port of 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN. • The 80-WXC-C AD port is connected to the COM-TX (ODD+EVEN-TX) port of 15216-MD-ID-50 or 15216-MD-48-CM. The ODD-RX port of the 15216-MD-ID-50 or 15216-MD-48-CM is connected to the COM-TX port of 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD; and the EVEN-RX port of the 15216-MD-ID-50 or 15216-MD-48-CM is connected to the COM-TX port of 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN. 80-WXC-C 40-WXC-C 40-WXC-C 40-WXC-C 40-WXC-C 80-WXC-C PP-MESH-4 248857 A C D B P P11-62 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks • The 80-WXC-C EXP-TX port is connected to the mesh patch panel. Figure 11-50 shows the layout for a line termination node. Figure 11-50 Line Termination Node Figure 11-51 shows the functional block diagram of a four-degree line termination mesh node using 80-WXC-C, 15216-MD-40-ODD, 15216-EF-40-ODD, 15216-MD-48-ODD, 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN. All the 80-WXC-C cards are in bidirectional mode. Wavelengths entering from side(i) can be routed to any of the other n-1 sides where n is defined by the PP MESH type. 248881 Booster Preamplifier DCM-xxx Air ramp DCM-xxx TCC2P Available Available Preamplifier Booster Available Available OSCM OSCM 8 AIC-I TCC2P 0-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray 15216 Odd Patch Panel 15216 Odd Patch Panel 15216 Even Patch Panel 15216 Even Patch Panel PP-MESH-4 1 1 2 2 1 15216-MD-40-EVEN, 15216-EF-40-EVEN, or 15216-MD-48-EVEN patch panel 2 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-63 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-51 Four-Degree Line Termination Mesh Node Functional Diagram 11.6.2.1 80-Channel Omni-directional n-degree ROADM Node Any side in the line termination mesh node can be configured as a omni-directional side. The side that is configured as the omni-directional side is connected to a local multiplexer and demultiplexer that can add or drop traffic to or from any of the node directions. In Figure 11-52, side D is configured as the omni-directional side. Wavelengths from the local multiplexer on side D are routed to sides A, B, or C by the patch panel. Wavelengths from sides A, B, or C are dropped on side D. 248880 PP-MESH-4 80-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C A C D B11-64 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-52 80-Channel Omni-directional Four-Degree ROADM Node 11.6.2.2 80-Channel Colorless n-degree ROADM Node Any side in the line termination mesh node can be configured as a colorless side where any wavelength can be added or dropped. The side that is configured as the colorless side is connected to two 80-WXC-C cards configured as a multiplexer and demultiplexer respectively. In Figure 11-53, side D is configured as the colorless side. The 80-WXC-C cards are connected to the add and drop ports of the 80-WXC-C cards as a colorless multiplexer and demultiplexer. A combination of wavelengths from any of the nine ports is sent to the common output port of the 80-WXC-C card (multiplexer) that is connected to the 80-WXC-C card. The wavelengths entering the 80-WXC-C card is passed to the common input port of the 80-WXC-C card (demultiplexer) and dropped at any of the nine output ports. 248864 DMX MUX 80-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C PP-MESH-4 A C D B P P11-65 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-53 80-Channel Colorless Four-Degree ROADM Node 11.6.2.3 80-Channel Colorless and Omni-directional n-Degree ROADM Node Any side in the line termination mesh node can be configured as a colorless and omni-directional side. The side that is configured as the colorless and omni-directional side is connected to a multiplexer (80-WXC-C) and demultiplexer (80-WXC-C) that can add or drop traffic to or from any of the node directions. Figure 11-54 shows the layout of a 80-channel n-degree ROADM node with colorless and omnidirectional side. 249086 PP-MESH-4 80-WXC-C 80-WXC-C 80-WXC-C Colorless side 80-WXC-C 80-WXC-C 80-WXC-C A C D B11-66 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-54 80-Channel n-degree ROADM Node with Colorless and Omnidirectional Side In Figure 11-55 side D is configured as the colorless and omni-directional side. A combination of wavelengths from any of the nine ports is sent to the common output port of the 80-WXC-C card (multiplexer) and is then routed to the preamplifier. The preamplifier sends the wavelengths to the 80-WXC-C card that is connected to the patch panel. The patch panel routes the wavelengths to sides A, B, or C. Wavelengths from sides A, B, or C can be dropped on side D. The incoming wavelengths from the 80-WXC-C card are sent to the preamplifier. The preamplifer amplifies the signal and sends it to the common input port of the 80-WXC-C card (demultiplexer). The wavelengths are then dropped at any of the nine output ports. 248875 DCM-xxx Air ramp DCM-xxx TCC2P Available Available Available Available Preamplifier Preamplifier OSCM OSCM 8 AIC-I TCC2P 0-WXC-C 80-WXC-C 80-WXC-C Fiber routing panel 1 2 3 4567 8 9 10 11 12 13 14 15 16 17 Fan tray11-67 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-55 80-Channel Colorless and Omni-directional Four-Degree ROADM Node 11.6.3 Line Termination Mesh Node Using 40-SMR2-C Cards Line termination mesh nodes using the 40-SMR2-C cards can support between one and four line terminations. Each line direction requires the 40-SMR2-C and 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD cards. Although it is recommended that you use the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD card along with the 40-SMR2-C card, you can alternatively use the 40-MUX-C and 40-DMX-C cards instead of the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD card. Each side of the line termination mesh node is connected as follows: • The 40-SMR2-C LINE-RX port is connected to the external line. • The 40-SMR2-C LINE-TX port is connected to the external line. • The 40-SMR2-C DROP TX port is connected to the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (or 40-DMX-C) COM-RX port. • The 40-SMR2-C ADD-RX port is connected to the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (or 40-DMX-C) COM-TX port. • The 40-SMR2-C EXP-TX port is connected to the mesh patch panel. • The 40-SMR2-C EXPi-RX (where i = 1, 2, 3) port is connected to the mesh patch panel. Figure 11-56 shows the layout for a line termination node. PP-MESH-4 248862 A C D B P P 80-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C 80-WXC-C11-68 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-56 Line Termination Mesh Node Shelf Figure 11-57 shows the functional block diagram of a four-degree line termination mesh node using 40-SMR2-C, 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD, and 15454-PP-4-SMR patch panel. 276455 40-SMR2-C 40-SMR2-C DCM-xxx DCM-xxx Av TCC2 ailable OSC-CSM Available Available OSC-CSM 40-SMR2-C 40-SMR2-C Available OSCM OSCM M AIC-I TCC2 S-ISC MS-ISC Fibre Routing Panel 15216 Odd Patch Panel 15216 Odd Patch Panel 15216 Odd Patch Panel 15216 Odd Patch Panel 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Air Ramp Fan Tray 1 1 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD patch panel11-69 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-57 Four-Degree Line Termination Mesh Node Functional Diagram 11.6.4 XC Termination Mesh Node The XC termination mesh node, shown in Figure 11-58, is the second mesh node type. It is used to upgrade a non-mesh node to a mesh node or to interconnect two non-mesh nodes. The XC termination mesh nodes contain the following cards: • 40-WXC-C cards • OPT-AMP-17-C cards configured in OPT-PRE mode The XC termination mesh node is connected as follows: • The 40-WXC-C COM-RX port is connected to the MMU EXP-A-TX port. • The 40-WXC-C COM-TX port is connected to the MMU EXP-A-RX port. • The 40-WXC-C EXP-TX port is connected to the OPT-AMP-17-C COM-RX port. • The 40-WXC-C EXP-RX port is connected to the OPT-AMP-17-C COM-TX port. • The 40-WXC-C EXP-TX port is connected to the mesh patch panel. • The 40-WXC-C EXP-RX port is connected to the mesh patch panel. 276461 40-SMR2-C 40-SMR2-C 40-SMR2-C 40-SMR2-C 15454-PP-4-SMR MUX DDMUX DCU MUX MUX DCU MUX DDMUX DCU MUX MUX DCU 3 4 1 211-70 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-58 XC Termination Mesh Node Shelf 11.6.5 Mesh Patch Panels and Shelf Layouts ONS 15454 mesh topologies require the installation of a four-degree patch panel, PP-MESH-4 (for 40-WXC-C cards) or 15454-PP-4-SMR (for 40-SMR2-C cards) or an eight-degree patch panel, PP-MESH-8 (for 40-WXC-C cards). If the four-degree patch panel is installed, mesh topologies of up to four degrees can be created. If the eight-degree patch panel is installed, mesh topologies of up to eight degrees can be created. The four-degree patch panel contains four 1x4 optical splitters, and the eight-degree patch panel contains eight 1x8 splitters. Each mesh patch panel contains a 2x8 splitter that is used for the test access transmit and receive ports. Figure 11-59 shows a block diagram for the PP-MESH-4 patch panel. OPT-AMP-xx OPT-AMP-xx 40-WXC-C 40-WXC-C 40-WXC-C DCU-xxx Air ramp DCU-xxx TCC2 Blank Blank Blank TCC2 40-WXC-C OPT-AMP-xx OPT-AMP-xx 15970011-71 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-59 PP-MESH-4 Patch Panel Block Diagram At the mesh patch panel, the signal is split into four signals (if a four-degree patch panel is used) or eight signals (if an eight-degree patch panel is used). Figure 11-60 shows the signal flow at the four-degree PP-MESH-4 patch panel. 40-WXC-C cards connect to the four-degree patch panel at the EXP TX and COM RX ports. Figure 11-60 PP-MESH-4 Patch Panel Signal Flow 159335 EXP TX to all directions COM RX from all directions Test Access TX Ports Test Access RX Port 2x4 splitter #4 1x4 splitters LC connector MPO connector 159334 40-WXC-C Test Access RX Port Test Access TX Ports PP-MESH-4 EXP TX COM RX 40-WXC-C EXP TX COM RX 40-WXC-C EXP TX COM RX 40-WXC-C EXP TX COM RX11-72 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks The mesh patch panels interconnect 40-WXC-C cards to create mesh networks, including four-degree and eight-degree mesh topologies. In addition, shelves with 40-WXC-C cards can be configured with mesh patch panels to create multiring, MMU-based mesh nodes. 40-WXC-C cards can be installed in ROADM nodes with MMU cards to upgrade a two-degree MMU-based ROADM node into four-degree or eight-degree mesh nodes. Figure 11-61 shows the block diagram of the four-degree 15454-PP-4-SMR patch panel connected to one 40-SMR2-C card. The 40-SMR2-C cards connect to the 15454-PP-4-SMR patch panel at the EXP RX ports. Figure 11-61 15454-PP-4-SMR Patch Panel Block Diagram You can use the 15454-PP-4-SMR patch panel to connect upto four 40-SMR2-C cards in a four-degree mesh node. The optical splitters inside the patch panel forward the output signal (EXP-TX port) of the 40-SMR2-C card on each side of the mesh node to the input port of the 40-SMR2-C cards on the other three sides of the mesh node. The 4x1 WXC block inside the 40-SMR2-C card selects which wavelength from which side must be propagated at the output of each side. Figure 11-60 shows the signal flow at the four-degree 15454-PP-4-SMR patch panel. 40-SMR2-C cards connect to the four-degree patch panel at the EXP-TX and EXP-RX ports. 276456 OSC-TX DC-TX DC-RX DROP-TX OSC-RX ADD-RX 6 ports OCM Block LINE TX LINE RX MONTX EXP-D EXP-B EXP-C EDFA 1 (Variable Gain) EDFA 2 (Fixed Gain) 30% 70% OSC DROP PD2 PD3 PD4 TAP TAP PD5 TAP PD8 PD7 OSC ADD TAP TAP TAP TAP PD6 4x1 WXC Block PD1 TAP TAP In D C B A In D C B A In C B A D In B A D C 4x PP 1x4 1x4 1x4 1x4 EXP-A11-73 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Configuring Mesh DWDM Networks Figure 11-62 15454-PP-4-SMR Patch Panel Signal Flow 11.6.6 Using a Mesh Node With Omni-Directional Add/Drop Section Normally, multidegree mesh node use four or eight 40-WXC-C cards and a four-degree or eight-degree patch panel. Each of the 40-WXC-C cards uses a 40-MUX-C card to add wavelengths going to the span and a 40-DMX-C card to drop wavelengths coming in from the span. The 40-MUX-C and 40-DMX-C cards are connected to only one of the node directions. These cards can add/drop traffic only to/from the side that is associated to the 40-WXC-C card. The omni-directional configuration allows you to install a local multiplexer/demultiplexer that can add/drop traffic to/from any of the node directions. Figure 11-63 shows an example of how to set up a omni-directional add/drop configuration. By setting up a NE as shown in the figure, it is possible to connect the transmit ports of TXP or MXP cards to a 40-MUX-C card and then connect the output of the 40-MUX-C card to an OPT-BST card. The OPT-BST card then connects to a preferred 40-WXC-C card in the four-degree or eight-degree ROADM node (40-WXC-C connected to port 4 of PP-MESH-4, as shown in the figure). The patch panel splits the traffic coming from the OPT-BST card in all the node directions, through the software configuration. The wavelengths entering the 40-WXC-C cards (ports 1, 2, and 3) can be selectively sent out in any desired outbound direction. In the inbound direction, the patch panel on the preferred 40-WXC-C card, splits any of the wavelengths entering the NE through the 40-WXC-C cards (ports 1, 2, and 3). Through the software configuration, the wavelength can be passed to an OPT-PRE card or stopped. This whole configuration can be managed using a single IP address An example of using a mesh node for omni-directional add/drop section is shown in Figure 11-63. 276457 40-SMR2-C Test Access RX Port Test Access TX Ports EXP A EXP B EXP C EXP D 40-SMR2-C 40-SMR2-C 40-SMR2-C 15454-PP-4-SMR 11-74 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-63 Mesh Node With Omni-Directional Add/Drop Section 11.7 DWDM Node Cabling DWDM node cabling is specified by the Cisco TransportPlanner Internal Connections table. The following sections provide examples of the cabling that you will typically install for common DWDM node types. Note The cabling illustrations shown in the following sections are examples. Always install fiber-optic cables based on the Cisco TransportPlanner Internal Connections table for your site. 11.7.1 OSC Link Termination Fiber-Optic Cabling OSC link termination cabling include the following characteristics: • The OPT-BST and OSC-CSM cards are the only cards that directly interface with the line (span) fiber. • The OSCM card only carries optical service channels, not DWDM channels. • The OSCM and OSC-CSM cards cannot both be installed on the same side of the shelf (Side B or Side A). You can have different cards on each side, for example an OSCM card on Side A and an OSC-CSM card on Side B.11-75 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling • When an OPT-BST card and an OSC-CSM card are both used on the same side of the node, the OPT-BST card combines the supervision channel with the DWDM channels and the OSC-CSM card acts as an OSCM card; it does not carry DWDM traffic. • If an OPT-BST and an OSCM card are installed on Side B, the Side B OPT-BST OSC RX port is connected to the Side B OSCM TX port, and the Side B OPT-BST OSC TX port is connected to the Side B OSCM RX port. • If an OPT-BST and an OSC-CSM card are installed on Side B, the Side B OPT-BST OSC RX port is connected to the Side B OSC-CSM LINE TX port, and the Side B OPT-BST OSC TX port is connected to the Side B OSC-CSM LINE RX port. • If an OPT-BST and an OSCM card are installed on Side A, the Side A OPT-BST OSC TX port is connected to the Side A OSCM RX port, and the Side A OPT-BST OSC RX port is connected to the Side A OSCM TX port. • If an OPT-BST and an OSC-CSM card are installed on Side A, the Side A OPT-BST OSC TX port is connected to the Side A OSC-CSM LINE RX port, and the Side A OPT-BST OSC RX port is connected to the Side A OSC-CSM LINE TX port. Figure 11-64 shows an example of OSC fibering for a hub node with OSCM cards installed.11-76 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-64 Fibering OSC Terminations—Hub Node with OSCM Cards 1 Side A OPT-BST LINE RX to Side B OPT-BST or OSC-CSM LINE TX on adjacent node 5 Side B OSCM TX to Side B OPT-BST OSC RX 115710 DCU-xxx West DCU-xxx East FAIL ACT SF INPUT 1 INPUT 2 INPUT 3 INPUT 4 OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 RING CALL LOCAL OW RING CALL EXPRESS OW CONTACT STATUS OPT AIC BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OSCM FAIL ACT SF UC RX TX OSCM FAIL ACT SF UC RX TX 32DMX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 TX 54.1 - 58.1 RX COM 32DMX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 TX 54.1 - 58.1 RX COM 32MUX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 RX 54.1 - 58.1 TX COM MON 32MUX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 RX 54.1 - 58.1 TX COM MON TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT RX TX RX TX 1 2 7 8 3 4 5 6 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-77 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling 11.7.2 Hub Node Fiber-Optic Cabling The following rules generally apply to hub node cabling: • The Side A OPT-BST or OSC-CSM card common (COM) TX port is connected to the Side A OPT-PRE COM RX port or the Side A 32DMX-O/40-DMX-C/40-DMX-CE COM RX port. • The Side A OPT-PRE COM TX port is connected to the Side A 32DMX-O/40-DMX-C/40-DMX-CE COM RX port. • The Side A 32MUX-O/32WSS/32WSS-L COM TX port is connected to the Side A OPT-BST or Side A OSC-CSM COM RX port. • The Side B 32MUX-O/32WSS/32WSS-L COM TX port is connected to the Side B OPT-BST or Side B OSC-CSM COM RX port. • The Side B OPT-BST or Side B OSC-CSM COM TX port is connected to the Side B OPT-PRE COM RX port or the Side B 32DMX-O/32DMX COM RX port. • The Side B OPT-PRE COM TX port is connected to the Side B 32DMX-O/32DMX COM RX port. Figure 11-65 shows an example of a hub node with cabling. In the example, OSCM cards are installed. If OSC-CSM cards are installed, they are usually installed in Slots 1 and 17. 2 Side A OPT-BST LINE TX to Side B OPT-BST or OSC-CSM LINE RX on adjacent node 6 Side B OSCM RX to Side B OPT-BST OSC TX 3 Side A OPT-BST OSC TX to Side A OSCM RX 7 Side B OPT-BST LINE TX to Side A OPT-BST or OSC-CSM LINE RX on adjacent node 4 Side A OPT-BST OSC RX to Side A OSCM TX 8 Side B OPT-BST LINE RX to Side A OPT-BST or OSC-CSM LINE TX on adjacent node11-78 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-65 Fibering a Hub Node 1 Side A DCU TX to Side A OPT-PRE DC RX1 6 Side B 32DMX-O COM RX to Side B OPT-PRE COM TX 2 Side A DCU RX to Side A OPT-PRE DC TX1 7 Side B 32MUX-O COM TX to Side B OPT-BST COM RX 115422 DCU-xxx West DCU-xxx East FAIL ACT SF INPUT 1 INPUT 2 INPUT 3 INPUT 4 OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 RING CALL LOCAL OW RING CALL EXPRESS OW CONTACT STATUS OPT AIC BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OSCM FAIL ACT SF UC RX TX OSCM FAIL ACT SF UC RX TX 32DMX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 TX 54.1 - 58.1 RX COM 32DMX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 TX 54.1 - 58.1 RX COM 32MUX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 RX 54.1 - 58.1 TX COM MON 32MUX-0 FAIL ACT SF 30.3 - 34.2 38.1 - 42.1 46.1 - 50.1 RX 54.1 - 58.1 TX COM MON TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT RX TX RX TX 3 1 2 9 10 4 5 6 7 8 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-79 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling 11.7.3 Terminal Node Fiber-Optic Cabling The following rules generally apply to terminal node cabling: • A terminal site has only one side (as compared to a hub node, which has two sides). The terminal side can be either Side B or Side A. • The terminal side OPT-BST or OSC-CSM card COM TX port is connected to the terminal side OPT-PRE COM RX port or the 32DMX-O/40-DMX-C/40-DMX-CE COM RX port. • The terminal side OPT-PRE COM TX port is connected to the terminal side 32DMX-O/40-DMX-C/40-DMX-CE COM RX port. • The terminal side 32MUX-O/40-MUX-C COM TX port is connected to the terminal side OPT-BST or OSC-CSM COM RX port. 11.7.4 Line Amplifier Node Fiber-Optic Cabling The following rules generally apply to line amplifier node cabling: • The line amplifier node layout allows all combinations of OPT-PRE and OPT-BST cards and allows you to use asymmetrical card choices in Side A-to-Side B and Side B-to-Side A configurations. For a given line direction, you can configure the four following possibilities: – Only preamplification (OPT-PRE) – Only booster amplification (OPT-BST) – Both preamplification and booster amplification (where a line amplifier node has amplification in at least one direction) – Neither preamplification nor booster amplification • If a Side A OPT-PRE card is installed: – The Side A OSC-CSM or OPT-BST COM TX is connected to the Side A OPT-PRE COM RX port. – The Side A OPT-PRE COM TX port is connected to the Side B OSC-CSM or OPT-BST COM RX port. • If a Side A OPT-PRE card is not installed, the Side A OSC-CSM or OPT-BST COM TX port is connected to the Side B OSC-CSM or OPT-BST COM RX port. • If a Side B OPT-PRE card is installed: – The Side B OSC-CSM or OPT-BST COM TX port is connected to the Side B OPT-PRE COM RX port. 3 Side A OPT-BST COM TX to Side A OPT-PRE COM RX 8 Side B OPT-PRE COM RX to Side B OPT-BST COM TX 4 Side A OPT-BST COM RX to Side A 32MUX-O COM TX 9 Side B DCU TX to Side B OPT-PRE DC RX1 5 Side A OPT-PRE COM TX to Side A 32DMX-O COM RX 10 Side B DCU RX to Side B OPT-PRE DC TX1 1. If a DCU is not installed, a 4-dB attenuator loop, +/– 1 dB must be installed between the OPT-PRE DC ports.11-80 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling – The Side B OPT-PRE COM TX port is connected to the Side A OSC-CSM or OPT-BST COM RX port. • If an Side B OPT-PRE card is not installed, the Side B OSC-CSM or OPT-BST COM TX port is connected to the Side A OSC-CSM or OPT-BST COM RX port. Figure 11-66 shows an example of a line amplifier node with cabling. Figure 11-66 Fibering a Line Amplifier Node 115423 DCU-xxx West DCU-xxx East FAIL ACT SF INPUT 1 INPUT 2 INPUT 3 INPUT 4 OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 RING CALL LOCAL OW RING CALL EXPRESS OW CONTACT STATUS OPT AIC BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OSCM FAIL ACT SF UC RX TX OSCM FAIL ACT SF UC RX TX TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT RX TX RX TX 1 2 7 8 4 5 3 6 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-81 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling 11.7.5 OSC Regeneration Node Fiber-Optic Cabling The following rules generally apply to OSC regeneration node cabling: • The Side A OSC-CSM COM TX port connects to the Side B OSC-CSM COM RX port. • The Side A OSC-CSM COM RX port connects to the Side B OSC-CSM COM TX port. • Slots 2 through 5 and 12 through 16 can be used for TXP and MXP cards. Figure 11-67 shows an example of an OSC regeneration node with cabling. 1 Side A DCU TX to Side A OPT-PRE DC RX1 1. If a DCU is not installed, a 4-dB attenuator loop, +/– 1 dB, must be installed between the OPT-PRE DC ports. 5 Side A OPT-BST COM RX to Side B OPT-PRE COM TX 2 Side A DCU RX to Side A OPT-PRE DC TX1 6 Side A OPT-BST COM RX to Side B OPT-PRE COM TX 3 Side A OPT-BST COM TX to Side A OPT-PRE COM RX 7 Side B DCU TX to Side B OPT-PRE DC RX1 4 Side A OPT-PRE COM TX to Side B OPT-BST COM RX 8 Side B DCU RX to Side B OPT-PRE DC TX111-82 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-67 Fibering an OSC Regeneration Node 115484 FAIL ACT SF INPUT 1 INPUT 2 INPUT 3 INPUT 4 OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 RING CALL LOCAL OW RING CALL EXPRESS OW CONTACT STATUS TCC2 AIC FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT OSC CSM FAIL ACT SF UC RX MON TX RX COM TX RX LINE TX OSC CSM FAIL ACT SF UC RX MON TX RX COM TX RX LINE TX 1 2 5 6 3 4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-83 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling 11.7.6 Amplified or Passive OADM Node Fiber-Optic Cabling The two sides of the OADM node do not need to be symmetrical. On each side, Cisco TransportPlanner can create one of the following four configurations: • OPT-BST and OPT-PRE • OSC-CSM and OPT-PRE • Only OSC-CSM • Only OPT-BST Note Amplified OADM nodes contain OPT-PRE cards and/or OPT-BST cards. Passive OADM nodes do not. Both contain add/drop channel or band cards. The following rules generally apply for OADM node express path cabled connections: • TX ports should only be connected to RX ports. • EXP ports are connected only to COM ports in between AD-xC-xx.x or AD-xB-xx.x cards that all belong to Side B (that is, they are daisy-chained). • EXP ports are connected only to COM ports in between AD-xC-xx.x or AD-xB-xx.x cards that all belong to Side A (that is, they are daisy-chained). • The EXP port of the last AD-xC-xx.x or AD-xB-xx.x card on Side A is connected to the EXP port of the first AD-xC-xx.x or AD-xB-xx.x card on Side B. • The OPT-BST COM RX port is connected to the nearest (in slot position) AD-xC-xx.x or AD-xB-xx.x COM TX port. • The OPT-PRE COM TX port is connected to the nearest (in slot position) AD-xC-xx.x or AD-xB-xx.x COM RX port. • If OADM cards are located in adjacent slots, the TCC2/TCC2P/TCC3/TNC/TSC card assumes that they are connected in a daisy-chain between the EXP ports and COM ports as noted previously. • The first Side A AD-xC-xx.x or AD-xB-xx.x card COM RX port is connected to the Side A OPT-PRE or OSC-CSM COM TX port. • The first Side A AD-xC-xx.x or AD-xB-xx.x card COM TX port is connected to the Side A OPT-BST or OSC-CSM COM RX port. • The first Side B AD-xC-xx.x or AD-xB-xx.x card COM RX port is connected to the Side B OPT-PRE or OSC-CSM COM TX port. 1 Side A OSC-CSM LINE RX to Side B OSC-CSM or OPT-BST LINE TX on adjacent node 4 Side A OSC-CSM COM RX to Side B OSC-CSM COM TX 2 Side A OSC-CSM LINE TX to Side B OSC-CSM or OPT-BST LINE RX on adjacent node 5 Side B OSC-CSM LINE RX to Side A OSC-CSM or OPT-BST LINE TX on adjacent node 3 Side A OSC-CSM COM TX to Side B OSC-CSM COM RX 6 Side B OSC-CSM LINE TX to Side A OSC-CSM or OPT-BST LINE RX on adjacent node11-84 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling • The first Side B AD-xC-xx.x or AD-xB-xx.x card COM TX port is connected to the Side B OPT-BST or OSC-CSM RX port. • If a Side A OPT-PRE is present, the Side A OPT-BST or OSC-CSM COM TX port is connected to the Side A OPT-PRE COM RX port. • If a Side B OPT-PRE is present, the Side B OPT-BST or OSC-CSM COM TX port is connected to the Side B OPT-PRE COM RX port. The following rules generally apply for OADM node add/drop path cabled connections: • AD-xB-xx.x add/drop (RX or TX) ports are only connected to the following ports: – 4MD-xx.x COM TX or 4MD-xx.x COM RX ports – Another AD-xB-xx.x add/drop port (a pass-through configuration) • An AD-xB-xx.x add/drop band port is only connected to a 4MD-xx.x card belonging to the same band. • For each specific AD-xB-xx.x card, the add and drop ports for that band card are connected to the COM TX and COM RX ports of the same 4MD-xx.x card. • The AD-xB-xx.x and 4MD-xx.x cards are located in the same side (the connected ports all have the same line direction). The following rules generally apply for OADM node pass-through path cabled connections: • Pass-through connections are only established between add and drop ports on the same band or channel and in the same line direction. • AD-xC-xx.x or AD-xB-xx.x add/drop ports must be connected to other AD-xC-xx.x or AD-xB-xx.x add/drop ports (as pass-through configurations). • Add (RX) ports must be connected to drop (TX) ports. • 4MD-xx.x client input/output ports must be connected to other 4MD-xx.x client input/output ports. • A Side A AD-xB-xx.x drop (TX) port is connected to the corresponding Side A 4MD-xx.x COM RX port. • A Side A AD-xB-xx.x add (RX) port is connected to the corresponding Side A 4MD-xx.x COM TX port. • An Side B AD-xB-xx.x drop (TX) port is connected to the corresponding Side B 4MD-xx.x COM RX port. • An Side B AD-xB-xx.x add (RX) port is connected to the corresponding Side B 4MD-xx.x COM TX port. Figure 11-68 shows an example of an amplified OADM node with AD-1C-xx.x cards installed. Note Figure 11-68 is an example. Always install fiber-optic cables based on the Cisco TransportPlanner Internal Connections table for your site.11-85 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-68 Fibering an Amplified OADM Node 1 Side A DCU TX to Side A OPT-PRE DC RX1 9 Side A AD-1C-xx.x EXP RX to Side B AD-1C-xx.x EXP TX 2 Side A DCU RX to Side A OPT-PRE DC TX1 10 Side B TXP_MR_2.5G DWDM RX to Side B AD-1C-xx.x (15xx.xx) TX 3 Side A OPT-BST COM TX to Side A OPT-PRE COM RX 11 Side B TXP_MR_2.5G DWDM TX to Side B AD-1C-xx.x (15xx.xx) RX 115424 DCU-xxx West DCU-xxx East OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DCC TX OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OSCM FAIL ACT SF UC RX TX TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT OSCM FAIL ACT SF UC RX TX TXP MR 2.5G FAIL ACT SF RX CLIENT DWDM TX RX TX TXP MR 2.5G FAIL ACT SF RX CLIENT DWDM TX RX TX RX TX RX TX AD-1C -XX.X FAIL ACT SF RX 15xx.xx TX RX EXP TX RX COM TX FAIL ACT SF RX 15xx.xx TX RX EXP TX RX COM TX AD-1C -XX.X FAIL ACT INPUT/OUTPUT AIC-I PWR A B ACC EOW LOW RING RING DCC-B DCC-A UDC-B UDC-A 1 2 4 5 13 12 15 16 3 14 6 7 10 11 8 9 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-86 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-69 shows an example of a passive OADM node with two AD-1C-xx.x cards installed. 4 Side A OPT-BST COM RX to Side A AD-1C-xx.x COM TX 12 Side B AD-1C-xx.x COM RX to OPT-PRE COM TX 5 Side A OPT-PRE COM TX to Side A AD-1C-xx.x COM RX 13 Side B AD-1C-xx.x COM TX to OPT-BST COM RX 6 Side A AD-1C-xx.x (15xx.xx) RX to Side A TXP_MR_2.5G DWDM TX 14 Side B OPT-PRE COM RX to Side B OPT-BST COM TX 7 Side A AD-1C-xx.x (15xx.xx) TX to Side A TXP_MR_2.5G DWDM RX 15 Side B DCU TX to Side B OPT-PRE DC RX1 8 Side A AD-1C-xx.x EXP TX to Side B AD-1C-xx.x EXP RX 16 Side B DCU RX to Side B OPT-PRE DC TX1 1. If a DCU is not installed, a 4-dB attenuator loop, +/ 1 dB, must be installed between the OPT-PRE DC ports.11-87 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-69 Fibering a Passive OADM Node 1 Side A OSC-CSM COM TX to Side A AD-1C-xx.x COM RX 4 Side A OSC-CSM EXP RX to Side B AD-1C-xx.x EXP TX 2 Side A OSC-CSM COM RX to Side A AD-1C-xx.x COM TX 5 Side B AD-1C-xx.x COM TX to Side B OSC-CSM COM RX 3 Side A OSC-CSM EXP TX to Side B AD-1C-xx.x EXP RX 6 Side B AD-1C-xx.x COM RX to Side B OSC-CSM COM TX 115425 FAIL ACT SF INPUT 1 INPUT 2 INPUT 3 INPUT 4 OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 RING CALL LOCAL OW RING CALL EXPRESS OW CONTACT STATUS OSC AIC CSM FAIL ACT SF UC RX MON TX RX COM TX RX LINE TX OSC CSM FAIL ACT SF UC RX MON TX RX COM TX RX LINE TX TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT AD-1C -XX.X FAIL ACT SF RX 15xx.xx TX RX EXP TX RX COM TX AD-1C -XX.X FAIL ACT SF RX 15xx.xx TX RX EXP TX RX COM TX 1 2 3 4 5 6 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-88 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling 11.7.7 ROADM Node Fiber-Optic Cabling The following rules generally apply to ROADM node cabling: • The Side A OPT-BST or OSC-CSM COM TX port is connected to the Side A OPT-PRE COM RX port. • The Side A OPT-PRE COM TX port is connected to the Side A 32WSS COM RX port. • The Side A OPT-BST or OSC-CSM COM RX port is connected to the Side A 32WSS COM TX port. • The Side A OPT-BST (if installed) OSC TX port is connected to the Side A OSCM RX port. • The Side A OPT-BST (if installed) OSC RX port is connected to the Side A OSCM TX port. • The Side A 32WSS EXP TX port is connected to the Side B 32WSS EXP RX port. • The Side A 32WSS EXP RX port is connected to the Side B 32WSS EXP TX port. • The Side A 32WSS DROP TX port is connected to the Side A 32DMX COM RX port. • The Side A 40-WSS-C/40-WSS-CE DROP TX port is connected to the Side A 40-DMX-C or 40-DMX-CE COM RX port. • The Side B OPT-BST or OSC-CSM COM TX port is connected to the Side B OPT-PRE COM RX port. • The Side B OPT-PRE COM TX port is connected to the Side B 32WSS COM RX port. • The Side B OPT-BST or OSC-CSM COM RX port is connected to the Side B 32WSS COM TX port. • The Side B OPT-BST (if installed) OSC TX port is connected to the Side B OSCM RX port. • The Side B OPT-BST (if installed) OSC RX port is connected to the Side B OSCM TX port. • The Side B 32WSS DROP TX port is connected to the Side B 32DMX COM RX port. • The Side B 40-WSS-C/40-WSS-CE DROP TX port is connected to the Side B 40-DMX-C or 40-DMX-CE COM RX port. Figure 11-70 shows an example of an amplified ROADM node with cabling. Note Figure 11-70 is an example. Always install fiber-optic cables based on the Cisco TransportPlanner Internal Connections table for your site.11-89 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Node Cabling Figure 11-70 Fibering a ROADM Node 1 Side A DCU TX to Side A OPT-PRE DC RX1 8 Side A 32WSS EXP RX to Side B 32WSS EXP TX 2 Side A DCU RX to Side A OPT-PRE DC TX1 9 Side B 32DMX COM RX to Side B 32WSS DROP TX 3 Side A OPT-BST COM TX to Side A OPT-PRE COM RX 10 Side B 32WSS COM RX to Side B OPT-PRE COM TX 115473 DCU-xxx West DCU-xxx East FAIL ACT SF INPUT 1 INPUT 2 INPUT 3 INPUT 4 OUTPUT 1 OUTPUT 2 OUTPUT 3 OUTPUT 4 RING CALL LOCAL OW RING CALL EXPRESS OW CONTACT STATUS OPT AIC BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OPT BST FAIL ACT SF RX MON TX RX COM TX RX OSC TX RX LINE TX OPT PRE FAIL ACT SF MON RX COM TX RX DC TX OSCM FAIL ACT SF UC RX TX OSCM FAIL ACT SF UC RX TX TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT TCC2 FAIL SF PWR A B CRIT MAJ MIN REM SYNC ACO ACO LAMP TEST RS-232 TCP/IP LINK ACT RX TX RX TX FAIL ACT SF 54.1-60.6 46.1-52.5 38.1-44.5 30.3-36.6 DROP TX EXP RX TX COM RX TX ADD RX 32WSS FAIL ACT SF 54.1-60.6 46.1-52.5 38.1-44.5 30.3-36.6 DROP TX EXP RX TX COM RX TX ADD RX 32WSS FAIL ACT SF 32DMX 54.1-60.6 46.1-52.5 38.1-44.5 30.3-36.6 COM RX TX FAIL ACT SF 32DMX 54.1-60.6 46.1-52.5 38.1-44.5 30.3-36.6 COM RX TX 32DMX 32DMX 3 1 2 13 14 7 8 4 5 11 10 6 9 12 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 P P + +11-90 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Automatic Node Setup 11.8 Automatic Node Setup Automatic node setup (ANS) is a TCC2/TCC2P/TCC3/TNC/TSC function that adjusts values of the variable optical attenuators (VOAs) on the DWDM channel paths to equalize the per channel power at the amplifier input. This power equalization means that at launch, all channels have the same amplifier power, independent of the input signal on the client interface and independent of the path crossed by the signal inside the node. This equalization is needed for two reasons: • Every path introduces a different penalty on the signal that crosses it. • Client interfaces add their signal to the ONS 15454 DWDM ring with different power levels. To support ANS, integrated VOAs and photodiodes are provided in the following cards: • AD-xB-xx.x card express and drop paths • AD-xC-xx.x card express and add paths • 4MD-xx.x card add paths • 32MUX-O card add paths • 32WSS/40-WSS-C/40-WSS-CE/40-WXC-C/80-WXC-C add, drop, and pass through paths • 32DMX-O card drop paths • 32DMX, 40-DMX-C, 40-DMX-CE card input port • 40-MUX-C card output port • 40-SMR1-C/40-SMR2-C add, drop, and pass through ports • PSM card input and output ports (both working and protect path) Optical power is equalized by regulating the VOAs. Based on the expected per channel power, ANS automatically calculates the VOA values by: • Reconstructing the different channel paths. • Retrieving the path insertion loss (stored in each DWDM transmission element). VOAs operate in one of three working modes: • Automatic VOA Shutdown—In this mode, the VOA is set at maximum attenuation value. Automatic VOA shutdown mode is set when the channel is not provisioned to ensure system reliability in the event that power is accidentally inserted. • Constant Attenuation Value—In this mode, the VOA is regulated to a constant attenuation independent from the value of the input signal. Constant attenuation value mode is set on VOAs associated to aggregated paths. 4 Side A 32WSS COM TX to Side A OPT-BST COM RX 11 Side B 32WSS COM TX to Side B OPT-BST COM RX 5 Side A 32WSS COM RX to Side A OPT-PRE COM TX 12 Side B OPT-BST COM TX to Side B OPT-PRE COM RX 6 Side A 32DMX COM RX to Side A 32WSS DROP TX 13 Side B DCU RX to Side B OPT-PRE DC TX1 7 Side A 32WSS EXP TX to Side B 32WSS EXP RX 14 Side B DCU TX to Side B OPT-PRE DC RX1 1. If a DCU is not installed, a 4-dB attenuator loop, +/–1 dB must be installed between the OPT-PRE DC ports.11-91 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Automatic Node Setup • Constant Power Value—In this mode, the VOA values are automatically regulated to keep a constant output power when changes occur to the input power signal. This working condition is set on VOAs associated to a single channel path. ANS calculates the following VOA provisioning parameters: • Target attenuation • Target power Optical patchcords are passive devices that are modeled by the two termination points, each with an assigned slot and port. If user-provisioned optical patchcords exist, ANS checks if the new connection is feasible according to internal connection rules. If the user connection violates one of the rules, ANS returns a denied message. ANS requires the expected wavelength to be provisioned. When provisioning the expected wavelength, the following rules apply: • The card family generically characterizes the card name, and not the particular wavelengths supported (for example, AD-2C-xx.x for all two-channel OADMs). • At the provisioning layer, you can provision a generic card for a specific slot using CTC or TL1. • Wavelength assignment is done at the port level. • An equipment mismatch alarm is raised when a mismatch between the identified and provisioned value occurs. The default value for the provisioned attribute is AUTO. ONS 15454 ANS parameters set the values required for the node to operate successfully. Cisco TransportPlanner calculates the ANS parameters based on the requirements for a planned network. Cisco TransportPlanner exports the parameters to an ASCII, NE update file. When the NE update file is imported in CTC, the Provisioning > WDM-ANS > Provisioning tab is populated with the ANS parameters to provision the node for the network. These ANS parameters can be modified. All the ANS parameters are mapped to the physical ports of the cards. ANS parameters can also be manually added or deleted in the Provisioning tab. The ranges for the values of the ANS parameters is shown in Table 11-11. For more information on how to add an ANS parameter, refer to the “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide. Note The Provisioning > WDM-ANS > Provisioning tab in CTC is empty if the NE update file is not imported. Note It is recommended that you use the Cisco TransportPlanner NE Update file to provision the ANS parameters instead of manually adding all the parameters in CTC. ANS provisioning parameters must be manually changed by Cisco qualified personnel only. Setting incorrect ANS provisioning (either as preamplifier or booster input power thresholds) may impact traffic. Table 11-11 Ranges and Values for the ANS Parameters ANS Parameter Range/Value OSC LOS Threshold -50.0 to +30.0 dBm Channel LOS Threshold -50.0 to +30.0 dBm Amplifier Working Mode Control Power, Control Gain, Fixed Gain Amplifier Gain 0.0 to 40.0 dB Amplifier Tilt -15.0 to +15.0 dB OSC Power -24.0 to 0.0 dBm11-92 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Automatic Node Setup ANS parameters can be viewed in the node view Provisioning > WDM-ANS > Provisioning tab, as shown in Figure 11-71. Figure 11-71 WDM-ANS Provisioning The Provisioning > WDM-ANS > Provisioning tab presents the following information: • Selector—Presents the ANS parameters in a tree view based on physical position. Clicking the + or – expands or collapses individual tree elements. Clicking a tree element displays the element parameters in the table on the right. For example, clicking the node name at the top displays all the node ANS parameters or clicking Slot 1 (PSM) displays the PSM amplifier parameters only. The ANS parameters can be sorted according to physical position. • Parameter—Displays the ANS parameter name. • Origin—Indicates how the parameter was calculated: – Imported—The value was set by importing the CTP XML file. Raman Ratio 0.0 to 100.0% Raman Total Power 100 to 450 mW Power -30.0 to +50 dBm WXC Dithering 0 to 33 Min Expected Span Loss 0.0 to 60.0 dB Max Expected Span Loss 0.0 to 60.0 dB VOA Attenuation 0 to 30 dB Table 11-11 Ranges and Values for the ANS Parameters ANS Parameter Range/Value11-93 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Automatic Node Setup – Provisioned—The value was manually provisioned. – Automatic—The value is automatically calculated by the system using the Raman provisioning wizard. For more information on how to provision using a wizard, see the “DLP-G468 Configure the Raman Pump Using an Installation Wizard” task in the Cisco ONS 15454 DWDM Procedure Guide. • Value—Displays the ANS parameter value. The values can be modified manually, although manually modifying the ANS parameters is not recommended. • Note—Displays information for parameters that could not be calculated, that is, parameters with Unknown appearing in the Value column. • Port —Displays the port value. Port is represented as Slot.Port. • Active Value —Displays the active parameter value. The active value cannot be modified manually. When you modify the parameter value in the Value field, the active value is updated with the modified value after you run ANS. The Provisioning > WDM-ANS > Port Status tab presents the following information: • Port—Displays the port value. The port is represented as Slot.Port. • Parameter—Displays the ANS parameter name. • Result—After you run ANS, one of the following statuses is provided for each ANS parameter in the Result column: – Success - Changed—The parameter setpoint was recalculated successfully. – Success - Unchanged—The parameter setpoint did not need recalculation. – Unchanged - Port in IS state—ANS could not modify the setpoint because the port is in IS state. – Fail - Out of Range—The calculated setpoint is outside the expected range. – Fail - Missing Input Parameter—The parameter could not be calculated because the required provisioning data is unknown or unavailable. – Not Applicable State—Ports are not in use. • Value—Displays the parameter value. • Set By—Displays the application that sets this parameter. This field can take the following values: – ANS – APC – Circuit Creation – Raman Wizard. A parameter could be set by more than one application. For example, VOA Attenuation parameter could be set by both ANS and APC. In this case, individual entries will be displayed for ANS and APC. • Last Change—Displays the date and time when the parameter was last modified. 11.8.1 Raman Setup and Tuning Raman amplification occurs in the optical fiber and the consequent Raman gain depends on the characteristics of the span (attenuator presence, fiber type, junctions, etc.). As two Raman pumps at two different wavelengths are used to stimulate the Raman effect, not only is the total signal power 11-94 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Automatic Node Setup calculation significant, but the right mix of power to ensure gain flatness is crucial. These setpoints of the total Raman power and Raman ratio can be configured on the OPT-RAMP-C or OPT-RAMP-CE card in three ways: • Raman installation wizard • CTP XML file • CTC/TL1 interface For information on how to configure the setpoints on the OPT-RAMP-C or OPT-RAMP-CE card, see the Cisco ONS 15454 DWDM Procedure Guide. Raman amplification on OPT-RAMP-C or OPT-RAMP-CE cards depends on the optical fiber installed. Therefore, Raman total power and Raman ratio values calculated using the Raman installation wizard via CTC is more accurate than the values provisioned by loading the CTP XML file. For this reason, the value provisioned using the wizard cannot be overridden by the CTP XML file. However, the values provisioned using the wizard or the CTP XML file can be overriden by manually provisioning the parameters. When the Raman installation is completed, a report of the status of Raman configuration on a node in the OPT-RAMP-C or OPT-RAMP-CE card can be viewed in the Maintenance > Installation tab when you are in card view. The Installation tab displays the following fields: • User—Name of user who configured the Raman pump. • Date—Date when the Raman pump was configured. • Status – Raman Not Tuned—The OPT-RAMP-C or OPT-RAMP-CE card was provisioned but ANS was not launched. – Tuned by ANS—ANS was run successfully and the basic ANS parameters were applied. – Tuned by Wizard—The Raman installation wizard was run successfully without errors. – Tuned by User Acceptance—The Raman installation wizard was completed with errors and the user accepted the values that the wizard calculated. – Raman is Tuning—The Raman installation wizard is running. • S1Low (dBm)—See Table 11-12. • S1High (dBm)—See Table 11-12. • S2Low (dBm)—See Table 11-12. • S2High (dBm)—See Table 11-12. • Power (mW)—Total Raman power setpoints. • Ratio—Raman pump ratio setpoint. • Gain—Expected Raman gain that the wizard calculated. • Actual Tilt—Expected Raman tilt that the wizard calculated. • Fiber Cut Recovery—Status of the fiber cut restoration. – Executed—The restore procedure was completed successfully. – Pending—The restore procedure is not complete. – Failed—The system failed to execute the procedure. • Fiber Cut Date—Date when the fiber cut occured.11-95 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Automatic Node Setup The Raman pump is equipped with two different Raman pumps transmitting powers (P1 and P2) at two different wavelengths 1 and 2. During installation, the two pumps alternatively turn ON and OFF at two different power values. 1 and 2 signals are used as probes at the end of spans to measure Raman gain efficiency of the two Raman pumps separately. The example in Figure 11-72 shows the Raman gain on an OPT-RAMP-C or OPT-RAMP-CE card in Node B that was measured by setting the wavelength and power measurements as follows: 1=1530.33 nm signal probe at Node A 2=1560.61 nm signal probe at Node A P1 = 1425 nm power at Node B P2 = 1452 nm power at Node B Plow = 100 mW Phigh = 280 mW Pmin = 8 mW Pmax = 450 mW Figure 11-72 Raman Gain on Node B The S1low, S1high, S2low, and S2low values in the Maintenance > Installation tab are based on the power values read on the LINE-RX port of Node B. λ λ λ λ λ λ 247381 OSC Add Node A Node B Pump Add OSC Drop Pump Drop Pump Drop OSC LINE-RX Drop RAMAN-TX RAMAN-RX RAMAN-RX RAMAN-TX COM-TX COM-RX COM-RX COM-TX DC-RX OSC-RX OSC-TX OSC-RX LINE-TX Probe signals Raman signals Raman Pump Probe signal power LINE-RX LINE-TX DC-TX DC-TX DC-RX PD4 PD5 PD7 PD6 PD3 PD4 PD10 PD12 PD12 PD10 PD3 PD1 PD1 PD6 OSC-TX PD7 PD5 Pump Add OSC Add11-96 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View 11.9 DWDM Functional View DWDM functional view offers a graphical view of the DWDM cards and the internal connections between them in an MSTP node. The functional view also shows cards and connections for multidegree MSTP nodes (up to eight sides). To navigate to the functional view of a DWDM node, use the following navigational path in CTC when you are in node view: Provisioning > WDM-ANS > Internal Patchcords > Functional View An example of the functional view for an eight-sided node is shown in Figure 11-73. Table 11-12 Example of Raman Power Measurements Input P1 P2 Raman Power at Node B 1=1530.33 nm at Node A Plow = 100 mW Pmin = 8 mW S1low Phigh = 250 mW Pmin = 8 mW S1high 2=1560.61 nm at Node A Pmin = 8 mW Plow = 100 mW S2low Pmin = 8 mW Phigh = 250 mW S2low λ λ11-97 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View Figure 11-73 Functional View for an Eight-Sided Node 11.9.1 Navigating Functional View The functional view has two main panes. The upper pane contains a tree view of the shelves and a graphical view of the shelf equipment. The lower pane describes alarms and circuits in a tabular format. The upper pane in Figure 11-73 is divided into a left pane and a right pane. The left pane shows a tree structure view of the shelf or shelves in the MSTP system. You can expand the tree view of a shelf to show the slot usage in that shelf. The right pane is a graphical view of the sides in the shelf. In the case of Figure 11-73, there are eight sides (A through H). Side A is located as shown in the figure. All of the cards in each side are grouped together. 240752 Side A Fit to View Zoom Out Zoom In Select11-98 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View The meanings of the icons in the upper right corner are as follows: • Select—use this icon to select a graphical element in the graphical view pane. • Patchcord—Use this icon to create an internal patchcord between cards. Note The Patchcord icon is not functional for Software Release 8.5. • Zoom In/Zoom Out—Use these icons to zoom in or zoom out in the graphical display pane. • Fit to View—Use this icon to have the graphical view fit the space available on your screen. The bottom pane can be used to display alarms (using the Alarms tab) or Circuits (using the Circuits tab). Clicking the Alarms tab displays the same information as the Alarms tab in the network, node, or card view. Clicking the Circuits tab displays the same information as the Alarms tab in the network, node, or card view. 11.9.2 Using the Graphical Display This section explains how to use the graphical portion of the display to gather information about the cards and ports. 11.9.2.1 Displaying a Side Double-click a side to show the details of that side. For example, if you double-click Side A in Figure 11-73, the result is as shown in Figure 11-74. Figure 11-74 Side A Details 2 3 4 7 6 8 9 5 1 24075911-99 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View The green arrows in the diagram represent the DWDM optical path within the selected side. The optical path in this instance is summarized as follows: 1. The light enters the OPT-BST card LINE-RX port from the optical span. 2. The path continues out of the OPT-BST card COM-TX port to the COM-RX port of the OPT-PRE card. 3. The OPT-PRE card sends the optical signal out of its COM-TX port to the 40-WXC COM-RX input port. 4. The 40-WXC card sends the signal to be locally dropped out of its DROP-TX port to the 40-DMX/40-DMX-CE card COM-RX port. 5. The 40-DMX/40-DMX-CE card sends the dropped signal out on one of its multifiber push on (MPO) connectors to the block labeled MPO. When you expand the MPO block (double-click it or right-click it and select Down), you will see a muxponder (MUX) card inside the MPO block. One of the eight optical fibers in the MPO cable is connected to the MUX trunk port. 6. The optical signal from the trunk port of the MXP card inside the MPO block enters the 40-MUX card at one of its five MPO connectors. 7. The 40-MUX card sends the optical signal out of its COM-TX port to the ADD-RX port of the 40-WXC card. 8. The added signal from the MXP gets sent out on the COM-TX port of the 40-WXC card to the COM-RX port of the OPT-BST card. 9. Finally, the OPT-BST card sends the optical signal out onto the span from its LINE-TX port. 11.9.2.2 Displaying Card Information In the functional view graphical pane, you can double-click a card to bring up the usual CTC card view. You can also move the mouse over a card to display information about the card. For example, when the mouse is placed over the OPT-BST card in Side A, the tooltip text displays sh1/s1 (OPT-BST), indicating that the OPT-BST card for Side A is located in Shelf 1, Slot 1. See Figure 11-75.11-100 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View Figure 11-75 Side A OPT-BST Card Shelf and Slot Information 11.9.2.3 Displaying Port Information Move the mouse over a port on a card to display information about the port. For example, when the mouse is placed over the top left port of the 40-MUX card in Side A, the tooltip text displays CARD_PORT-BAND-1-RX, indicating that the 40-MUX port being pointed to is for the first band of wavelengths (wavelengths 1 to 8) to be added into the optical path at the 40-MUX card. These wavelengths come into the 40-MUX card from a transponder (TXP) or muxponder (MXP) on an MPO connector, which contains eight integrated optical fibers. See Figure 11-76.11-101 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View Figure 11-76 Side A 40-MUX Port Information 11.9.2.4 Displaying Patchcord Information Move the mouse over a patchcord to see the state of the output and input port associated with that patchcord. See Figure 11-77.11-102 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View Figure 11-77 Patchcord Input and Output Port State Information 11.9.2.5 Displaying MPO Information To show the details inside an MPO block, double-click it or right-click it and select Down. When the detailed view is visible, right-click inside the MPO block and select Upper View to collapse the block. When you move the mouse over the MPO block, the associated wavelengths are displayed as a tool tip (see Figure 11-78).11-103 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View Figure 11-78 MPO Information 11.9.2.6 Alarm Box Information Within the side display, an alarm box is shown that gives the alarm count for the Critical, Major, and Minor alarms that affect that side. This alarm summary is only for the side, and is different from the alarms under the Alarms tab, where all of the alarms for the system are summarized. If an alarm under the Alarms tab appears that has to do with Side A, for example, only the appropriate alarm count in the Alarm box for Side A is incremented. The alarm counts in the Alarm boxes for the other nodes (B through H) are not incremented. In the graphical view of a side, the card icon or port icon changes color to reflect the severity of an alarm associated with the card (red, orange, or yellow). The color of the MPO block reflects the color of highest alarm severity for the elements in the MPO block. 11.9.2.7 Transponder and Muxponder Information All of the TXP and MXP cards connected with patchcords are grouped together under the MPO icon. In the node shown in Figure 11-73, there is an MXP card in Side A that is connected to the 40-MUX card and to the 40-DMX/40-DMX-CE card. The MXP card is connected through the 40-MUX card to the add port on the 40-WXC card and it is also connected through the 40-DMX/40-DMX-CE card to the drop port on the 40-WXC card. To view the connections to the MXP card from the 40-MUX card, double-click the MPO icon. Figure 11-79 shows the MPO icon before double-clicking it and Figure 11-80 shows the result after double-clicking it. Note In the case of a protected TXP (TXPP) or MXP (MXPP) card, the card icon has a label indicating the active trunk and the protected trunk.11-104 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View Figure 11-79 Side A MPO Connection to an MXP Before Double-Clicking Figure 11-80 Side A MPO Connection to an MXP After Double-Clicking 11.9.2.8 Changing the Views When you right-click inside of a side view, a shortcut menu allows you to do the following (see Figure 11-81): • Fit to View—Fits the side view into the available display space. • Delete Side—Deletes the selected side. • Rotate Left—Rotates the side 90 degrees counterclockwise (all connections are maintained). • Rotate Right—Rotates the side 90 degrees clockwise (all connections are maintained). • Horizontal Flip—Flips the side horizontally (all connections are maintained). • Vertical Flip—Flips the side vertically (all connections are maintained). After you have selected Fit to View for a side, you can right-click in the side view to bring up a new menu with the following selections (see Figure 11-82): • Go to Upper View—Returns to the previous view. MPO block 240760 MXP card MPO connector 24076111-105 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Functional View • Perform AutoLayout—Optimizes the placement of the cards and the connections between them. Figure 11-81 Side A View Options Figure 11-82 Side A View Options (after Selecting Fit to View) 11.9.2.9 Selecting Circuits When the Circuits tab is selected, the circuits for the functional view are shown. The patchcord lines in the graphical display are normally black in color. A patchcord line becomes green only when you select a circuit associated with the patchcord that carries the selected circuit. 11.9.2.10 Displaying Optical Path Power To show the optical power present in an optical path, move the mouse over the desired optical path (green line). A tooltip shows the power along the optical path in dBm (see Figure 11-83).11-106 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Network Functional View Figure 11-83 Optical Path Power 11.10 DWDM Network Functional View The DWDM Network Functional View (NFV) displays a graphical representation of the circuit connections, optical power, and alarms in the DWDM network. The NFV allows you to view the circuit connections and flow of data at the network level. The NFV also helps to find an alternate network path if there is a loss of signal in the network. The NFV offers dual options to view the network: • Graphical view—Displays the circuit connections, optical power, and alarms of a circuit through a graphical representation. To view the graphical display of the circuit connections, select the circuit listed in the upper left pane. Click dB, SL, and PV button on the toolbar to view the optical power of the selected circuit, span loss of the desired span, and insertion loss of the patchchord respectively. For more information refer to 11.10.2 Using the Graphical Display, page 11-108. • Viewing the circuit details in tabular format—The circuit connections, optical power, and alarms of a circuit are displayed in a tabular format (seen in the left pane of the Network Functional View). For more information refer to 11.10.2.2 Selecting the Circuit, page 11-109. For information on how to view optical power values and alarms of the circuit selected in the Network Functional View, see the “View Optical Power Values and Alarms Using the Network Functional View” task in the Cisco ONS 15454 DWDM Procedure Guide.11-107 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Network Functional View 11.10.1 Navigating Network Functional View This section explains how to navigate to the network functional view (NFV). To navigate to the NFV, go to the network view in the CTC and click the FV button on the toolbar. The DWDM Network Functional View window opens. The NFV is similar to the DWDM functional view in its graphical layout and behavior at the node level. For additional information, see “11.9 DWDM Functional View” section on page 11-96. The network functional view has two main panes (Figure 11-84): • Left pane—Is divided into an upper pane and a lower pane. The upper pane has three tabs that are listed in Table 11-13, and the lower pane displays the graphical overview of the network. • Right pane—Displays the graphical view of all the nodes and devices in the network. You can hide or close the upper and lower panes, and view only the network map in the NFV. Click the Close button on the title bar to close the pane or click the Toggle auto-hide button on the title bar to hide the pane. Click the Reset To Default button on the toolbar to restore (or view) all the panes. Table 11-13 Circuits, Optical Power, and Alarms tab Tab Description Circuits Displays the lists of circuits for the nodes present in the network. Optical Power Displays the optical link and span loss of the circuits. This tab lists the aggregated power-in and power-out of all the internal patchcords for the nodes that have the functional view open. Alarms Displays the alarms of all the circuits for the nodes present in the network.11-108 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Network Functional View Figure 11-84 DWDM Network Functional View 11.10.2 Using the Graphical Display This section explains how to use the graphical display to gather information on circuits, optical power, and alarms for the nodes. To expand a node, click on the network functional view graph and Press F2. The node opens in a double zoom mode and you can read the power information in the zoom out view. Click F2 again to zoom-in or return to the normal view. Additionally, to zoom-in and zoom-out the graph on the network functional view, press the Ctrl key and scroll up and down with the scroll wheel on your mouse. Click Reset Nodes Zoom button on the toolbar to reset the graphical view to the default zoom size. The keystroke commands provide the keyboard shortcuts for graphical control of the NFV. To access the keystroke commands, click Help > Keystroke commands. Note To open and view the nodes in the network functional view, right-click the node and choose Open Node FV. Or double-click on the Node to open the node FV. To navigate to the node level, right-click FV > Node FV. To close all the opened nodes in the FV, click Close Expanded Nodes button on the toolbar. To zoom-in and zoom-out of the open node, press the Ctrl key and scroll up and down with the scroll wheel on your mouse. 274373 Circuits, Optical Power, and Alarms Tabs Title bar Toggle auto-hide Upper Pane Lower Pane Right Pane PV dB Reset Nodes Zoom Close Expanded Nodes Reset To Default SL Refresh Button11-109 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Network Functional View When you have multiple node FVs opened, you cannot view the graphical details of the individual node due to overlapping of the map. To avoid overlapping of the map, do the following: 1. Select the entire expanded node (all sides), and move it out of the map (to the desired location). To select the entire node, click on the title bar of the node and Press Ctrl A. 2. Move the individual sides of the node one-by-one back to the proper position inside the network map. To move the individual sides of the node, select the side and move it to the desired location. 11.10.2.1 Displaying Optical Power The NFV toolbar has the following buttons that displays the optical power information of the circuits: • dB (Power)—Click the dB button on the toolbar to view the optical power information of the circuits. The optical power in the optical path in dBm is displayed in the power balloon. You can view the aggregated power only for those nodes that have the FV open. To open the node FV, right-click the node and choose Open Node FV. It also shows the per channel estimated power of the ports of the selected circuit. Right-click the internal patchcord link and select Flip Power Balloons to view the power balloon of the selected patchcord. The power balloon is flipped and you can see the power details of the selected patchcord without overlapping. • SL (Span Loss)—Click the SL button to see the loss of signal of the desired span. • PV (Patchcord Verification)—Click the PV button to display the insertion loss of the patchcord. The PV calculates the input and output power of the patchcord. You can view the insertion loss of the patchchord only for those nodes that have the FV open. To open the node FV, right-click the node and choose Open Node FV. The insertion loss should not exceed 2dBm. The patchcord lines are colored to indicate the insertion loss: – Red—Indicates that the insertion loss of the patchcords exceeded 2dBm. – White—Indicates that the system was not able to calculate the insertion loss of the patchcord. – Black—Indicates that the insertion loss of the patchcords is within the limit and not more than 2dBm. Note Click Refresh on the toolbar, to refresh the optical power and span loss information. The optical power and span loss information is calculated and is refreshed in the graphical display and optical power table. 11.10.2.2 Selecting the Circuit The Circuit tab in the NFV allows you to view the available circuits in the network. Click the Circuit tab to view the list of circuits in the selected network. Choose the circuit from the list to view the circuit level information. A graphical display of the selected circuit and the impacted span is visible in the map. Additionally, you can view the general information (type, source, and destination), status (IS,OOS [ANSI] or unlocked, locked [ETSI]), and physical connection details (wavelength, direction, and span) of the selected circuit. The circuit can be in any of the following states: • DISCOVERED • PARTIAL • DISCOVERED_TL1 • PARTIAL_TL111-110 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference DWDM Network Functional View When you switch the selection between the circuits, and if both the circuits are in DISCOVERED_TL1 state, the circuit details of the new selection is not displayed (it may still show the previously selected circuit details). If you find that the current selection is not refreshed, do either of the following: • Deselect the selected circuit before selecting the another circuit. Or • Update all the selected circuits using the Reconfigure Circuit option. Go to CTC Tools > Circuits > Reconfigure Circuits menu to reconfigure the selected circuits. During reconfiguration, CTC reassembles all connections of the selected circuits and VCAT members into circuits based on path size, direction, and alignment. Note If the information does not refresh when you switch the selection between the circuits in OCH_CC and its OCH_TRAIL (and vice-versa), follow the suggestion provided on how to view the current selection if the screen is not refreshed. To view the optical power and alarm details of a circuit, click Circuit and select the circuit name from the list to view the following details: • Optical Power—To view the optical power of the selected circuit, click the Optical Power tab. You can view the optical link status and the span loss of the selected circuit. • Alarms—To view the alarms of the selected circuit, click the Alarms tab. If a card has one or more alarms (that is part of the selected circuit), the node turns either yellow or red, depending on the severity of the alarm. The alarm in red indicates a major alarm and yellow indicates a minor alarm. If there is an alarm present in the card that is not part of the selected circuit, then the node appears gray. If a node has alarms that is not part of the selected circuits, then the alarms are not listed in the table, but the node is colored in the graphical view (right pane). Note At the circuit level, you can view both the node and network level information. 11.10.2.3 Exporting Reports You can also export the NFV reports of circuit level information in HTML or JPEG format. The export operation creates two files, an HTML and a JPEG format of the NFV information. The .jpg file provides a graphical representation of the site layout. For more information on exporting the reports, see the “Export Network Functional View Reports” task in the Cisco ONS 15454 DWDM Procedure Guide.11-111 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Non-DWDM (TDM) Networks 11.11 Non-DWDM (TDM) Networks Non-DWDM (TDM) Networks take synchronous and asynchronous signals and multiplexes them to a single higher bit rate for transmission at a single wavelength over fiber. When the node is configured as a Non-DWDM Network, the supported MSTP cards — amplifiers, transponders, and muxponders, are used in the standalone mode. MSTP applications like Circuit Provisioning, NLAC and APC are not supported in amplified TDM networks. For more information on how to configure a node as a Non-DWDM network, see the “NTP-G320 Configure the Node as a Non-DWDM Network” section in “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide. When the node is configured as a Not-DWDM network, all the amplifiers are configured by default with the following values: • Working mode = Control Gain • Channel Power Ref. = +1dBm. Booster(LINE) amplifiers enable optical safety when used in Non-DWDM. ALS configuration is set to “Auto Restart” by default. A manual restart request is therefore needed to turn up the bidirectional link, in addition with an appropriated cabling (bi-directional) of LINE TX/RX ports. In NOT-DWDM mode, you must configure significant optical parameters and thresholds before launching the ANS application. For information on how to configure the amplifier, see the “DLP-G693 Configure the Amplifier” section in “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide. For information on how to configure the PSM behavior, see the “DLP-G694 Configure the PSM” section in “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide. When the ANS application is launched, amplifier ports move into IS state and Gain Setpoint is automatically calculated by the card, after initial APR cycle. Gain Setpoint must be equal to MAX [Min Gain Setpoint of the card ; (Power Ref-Pinput)]; where Pinput is the optical power value at the ingress port (COM-RX) of the amplification stage.11-112 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 11 Node Reference Non-DWDM (TDM) NetworksCHAPTER 12-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 12 Network Reference This chapter explains the Cisco ONS 15454 dense wavelength division multiplexing (DWDM) network applications and topologies. The chapter also provides network-level optical performance references. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Note In this chapter, “OPT-BST” refers to the OPT-BST, OPT-BST-E, OPT-BST-L cards, and to the OPT-AMP-L, OPT-AMP-C, and OPT-AMP-17-C cards when they are provisioned in OPT-LINE (optical booster) mode. “OPT-PRE” refers to the OPT-PRE card and to the OPT-AMP-L, OPT-AMP-C, and OPT-AMP-17-C cards provisioned in OPT-PRE (preamplifier) mode. Note OPT-BST-L, 32WSS-L, 32DMX-L, and OPT-AMP-L cards can be installed only in L-band compatible nodes and networks. OPT-BST, OPT-BST-E, 32WSS, 32DMX, 40-DMX-C, 40-DMX-CE, 40-MUX-C, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 40-SMR1-C, 40-SMR2-C, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C and OPT-RAMP-CE cards can be installed only in C-band compatible nodes and networks. Chapter topics include: • 12.1 Network Applications, page 12-2 • 12.2 Network Topologies, page 12-2 • 12.5 Network Topologies for the OPT-RAMP-C and OPT-RAMP-CE Cards, page 12-18 • 12.6 Network Topologies for the PSM Card, page 12-19 • 12.7 Optical Performance, page 12-19 • 12.8 Automatic Power Control, page 12-20 • 12.9 Power Side Monitoring, page 12-24 • 12.10 Span Loss Verification, page 12-25 • 12.11 Network Optical Safety, page 12-27 • 12.12 Network-Level Gain—Tilt Management of Optical Amplifiers, page 12-40 • 12.13 Optical Data Rate Derivations, page 12-46 • 12.14 Even Band Management, page 12-4812-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Applications 12.1 Network Applications Cisco ONS 15454 nodes can be provisioned for metro core DWDM network applications. Metro core networks often include multiple spans and amplifiers, so the optical signal-to-noise ratio (OSNR) is the limiting factor for channel performance. Within DWDM networks, the ONS 15454 uses a communications protocol, called Node Services Protocol (NSP), to communicate with other nodes. NSP automatically updates nodes whenever a change in the network occurs. Each ONS 15454 DWDM node can: • Identify other ONS 15454 DWDM nodes in the network. • Identify the different types of DWDM networks. • Identify when the DWDM network is complete and when it is incomplete. 12.2 Network Topologies The ONS 15454 DWDM network topologies include ring networks, linear networks, mesh networks, interconnected rings and spurs. 12.2.1 Ring Networks Ring networks support hubbed, multi-hubbed, any-to-any, and mesh traffic topologies. 12.2.1.1 Hubbed Traffic Topology In the hubbed traffic topology (Figure 12-1), a hub node terminates all the DWDM channels. A channel can be provisioned to support protected traffic between the hub node and any node in the ring. Both working and protected traffic use the same wavelength on both sides of the ring. Protected traffic can also be provisioned between any pair of optical add/drop multiplexing (OADM) nodes, except that either the working or the protected path must be regenerated in the hub node. Protected traffic saturates a channel in a hubbed topology, that is, no channel reuse is possible. However, the same channel can be reused in different sections of the ring by provisioning unprotected multihop traffic. From a transmission point of view, this network topology is similar to two bidirectional point-to-point links with OADM nodes. For more information about hub nodes, see the “11.1.4 Hub Node” section on page 11-27.12-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies Figure 12-1 Hubbed Traffic Topology 12.2.1.2 Multihubbed Traffic Topology A multihubbed traffic topology (Figure 12-2) is based on the hubbed traffic topology, except that two or more hub nodes are added. Protected traffic can only be established between the two hub nodes. Protected traffic can be provisioned between a hub node and any OADM node only if the allocated wavelength channel is regenerated through the other hub node. Multihop traffic can be provisioned on this ring. From a transmission point of view, this network topology is similar to two or more point-to-point links with OADM nodes. Hub Amplified OADM Passive OADM Line amplifier 90995 Amplified OADM Passive OADM Amplified OADM OSC OSC12-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies Figure 12-2 Multihubbed Traffic Topology 12.2.1.3 Any-to-Any Traffic Topology The any-to-any traffic topology (Figure 12-3) contains only reconfigurable OADM (ROADM) nodes (with or without optical service channel [OSC] regeneration) or optical amplifier nodes. This topology potentially allows you to route every wavelength from any source to any destination node inside the network. See the “11.1.3 ROADM Node” section on page 11-10 for more information. Hub Hub Passive OADM Line amplifier 90998 Amplified OADM Passive OADM Amplified OADM OSC OSC12-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies Figure 12-3 Any-to-Any Traffic Topology 12.2.1.4 Meshed Traffic Topology The meshed traffic topology (Figure 12-4) does not use hubbed nodes; only amplified and passive OADM nodes are present. Protected traffic can be provisioned between any two nodes; however, the selected channel cannot be reused in the ring. Unprotected multihop traffic can be provisioned in the ring. A meshed ring must be designed to prevent amplified spontaneous emission (ASE) lasing. This is done by configuring a particular node as an anti-ASE node. An anti-ASE node can be created in two ways: • Equip an OADM node with 32MUX-O cards and 32DMX-O cards. This solution is adopted when the total number of wavelengths deployed in the ring is higher than ten. OADM nodes equipped with 32MUX-O cards and 32DMX-O cards are called full OADM nodes. • When the total number of wavelengths deployed in the ring is lower than ten, the anti-ASE node is configured by using an OADM node where all the channels that are not terminated in the node are configured as “optical pass-through.” In other words, no channels in the anti-ASE node can travel through the express path of the OADM node. For more information about OADM nodes, see the “11.1.2 OADM Node” section on page 11-8. For more information about anti-ASE nodes, see the “11.1.5 Anti-ASE Node” section on page 11-31. ROADM ROADM ROADM 115730 ROADM ROADM ROADM OSC OSC12-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies Figure 12-4 Meshed Traffic Topology 12.2.2 Linear Networks Linear configurations are characterized by the use of two terminal nodes, east and west. The 32-channel terminal nodes can be equipped with a 32MUX-O card and a 32DMX-O card, or with a 32WSS card and a 32DMX or 32DMX-O card. The 40-channel terminal nodes can be equipped with a 40-MUX-C card and a 40-DMX-C/40-DMX-CE card, a 40-WSS-C/40-WSS-CE card with a 40-DMX-C/40-DMX-CE card, or a 40-SMR1-C/40-SMR2-C card with a 15216-MD-40-ODD card. OADM or line amplifier nodes can be installed between the two terminal nodes. Only unprotected traffic can be provisioned in a linear configuration. Figure 12-5 shows five ONS 15454 nodes in a linear configuration with an amplified and a passive OADM node. Figure 12-5 Linear Configuration with an OADM Node Figure 12-6 shows five ONS 15454 nodes in a linear configuration without an OADM node. See the “11.1.1 Terminal Node” section on page 11-2 for more information. Anti-ASE Amplified OADM Passive OADM Line amplifier 90997 Amplified OADM Passive OADM Amplified OADM OSC OSC Line amplifier Passive OADM 90996 West terminal Amplified OADM East terminal OSC OSC12-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies Figure 12-6 Linear Configuration without an OADM Node A single-span link is a type of linear configuration characterized by a single-span link with preamplification and post-amplification. A single-span link is also characterized by the use of two terminal nodes, east and west. Only unprotected traffic can be provisioned on a single-span link. Figure 12-7 shows two ONS 15454s in a single-span link. Eight channels are carried on one span. Single-span link losses apply to OC-192/STM-64 LR ITU cards. The optical performance values are valid assuming that the sum of the OADM passive node insertion losses and the span losses does not exceed 35 dB. Figure 12-7 Single-Span Link 12.2.3 Mesh Networks A mesh network can be native or multiring. In a native mesh network (Figure 12-8), any combination of four-degree and eight-degree mesh nodes can work together. Four-degree mesh nodes transmit an optical signal in four directions, while an eight-degree mesh node transmits an optical signal in eight directions. For additional information about mesh nodes, see the “11.6 Configuring Mesh DWDM Networks” section on page 11-53. The intermediate nodes are ROADM nodes. In a mesh node, all wavelengths can be routed through four (four-degree mesh node) to eight (eight-degree mesh node) different optical line termination ports using a 40-WXC-C, 80-WXC-C, or 40-SMR2-C card without any optical-electrical-optical (OEO) regeneration. It is possible to combine 40-WSS-C/40-WSS-CE, 40-WXC-C, 40-SMR2-C, and 32WSS cards in the same mesh network without impacting system performance. For nodes equipped with 32WSS cards, the maximum system capacity is 32 channels. Terminal sites are connected to the mesh network as a spur. Line amplifier 96639 West terminal East terminal OSC OSC Line amplifier Line amplifier 90999 West terminal East terminal ~130/150 km OSC OSC12-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies Figure 12-8 Mesh Network In a multiring mesh network (Figure 12-9), several rings are connected with four-degree or eight-degree mesh nodes. The intermediate ROADM nodes are equipped with MMU cards. All wavelengths can be routed among two or more rings using a 40-WXC-C or 40-SMR2-C card without any optical-electrical-optical (OEO) regeneration. As in a native mesh network, it is possible to combine 40-WSS-C/40-WSS-CE, 40-WXC-C, 40-SMR2-C, and 32WSS cards in the same multiring network without impacting system performance. For nodes equipped with 32WSS cards, maximum system capacity is limited to 32 channels. A terminal node is connected to a multiring node as a spur. For information on node configurations for both native mesh and multiring networks, see the “11.6 Configuring Mesh DWDM Networks” section on page 11-53. 159494 OLA Terminal N-degree mesh N-degree mesh N-degree mesh N-degree mesh N-degree mesh N-degree mesh N-degree mesh ROADM ROADM ROADM ROADM Terminal12-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings Figure 12-9 Multiring Network 12.3 Interconnected Rings The interconnected ring configuration allows you to connect two different nodes using external ports to allow traffic flow between different subnets. In Figure 12-10, the main ring consists of nodes R, R1, and R2 and the tributary ring consists of nodes r, r1, and r2. It is possible to connect more than one tributary ring to the main ring at the same point. Node R of the main ring can forward wavelengths to the node r of the tributary ring and vice-versa. Node R is either a colorless and omni-directional n-degree ROADM node (Figure 12-11) or a two-degree colorless ROADM node (Figure 12-12) equipped with 80-WXC-C cards. See the “11.6 Configuring Mesh DWDM Networks” section on page 11-53 for more information about colorless and omni-directional n-degree ROADM nodes and two-degree colorless ROADM nodes. Node r of the tributary ring is a two-degree ROADM node equipped with 40-SMR1-C, 40-SMR2-C, 40-WSS-C, or 40-WSS-CE cards. OTS PPCs are provisioned between the EAD ports of the 80-WXC-C card on node R and the EXP or ADD/DROP ports of the 40-SMR1-C, 40-SMR2-C, 40-WSS-C, or 40-WSS-CE cards on node r. All the nodes are managed by different IP addresses. 249103 OPT-BST or OSC-CSM OPT-PRE or TXP/MXP 40-WSS-C DCM-xxx Air ramp DCM-xxx 40-DMX-C Blank or TXP/MXP or MS-ISC-100T TCC2/TCC2P/TCC3 OSCM or Blank AIC-I OSCM or Blank TCC2/TCC2P/TCC3 Blank or TXP/MXP or MS-ISC-100T 40-DMX-C 40-WSS-C OPT-PRE or TXP/MXP OPT-BST or OSC-CSM12-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings Figure 12-10 Interconnected Rings Figure 12-11 Colorless and Omni-directional n- Degree ROADM Node 248900 B R1 R2 R1 r1 r2 r A C c D d a b Main ring Node interconnections Tributary ring 80-WXC-C PP-MESH-4 249088 A C D B P P Connection to tributary ring node (r)12-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings Figure 12-12 Colorless Two-Degree ROADM Node 12.3.1 Interconnected Ring Scenarios In the following sections, three interconnected ring scenarios are given: 12.3.1.1 Scenario A: Interconnect Traffic from Tributary Ring to Main Ring without Local Add/Drop in the Tributary Ring In scenario A-1(Figure 12-13), node R is a three-degree colorless and omni-directional ROADM node and node r is a two-degree 40-SMR1-c based ROADM node. The EAD ports of the 80-WXC-C cards on node R are connected to the ADD/DROP ports of the 40-SMR1-C card on node r. Traffic from node r can be routed to side A or B of node R. Traffic from side a cannot be added or dropped at node r but can be routed to side b using the express path. 249085 1x9 DMX L2 1x9 DMX L1 1x9 MUX L2 1x9 DMX L2 1x9 MUX L2 1x9 MUX L1 1x9 MUX L1 1x9 DMX L1 P Booster Connection to tributary ring node (r) Side A Side B OSC Booster OSC DMX-E DMX-O MUX-E MUX-O DMX-O DMX-E MUX-O MUX-E P12-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings Figure 12-13 Interconnected Ring - Scenario A-1 In scenario A-2 (Figure 12-14), node R is a two-degree colorless ROADM node and node r is a two-degree 40-SMR1-C based ROADM node. The EAD ports of the 80-WXC-C cards on node R are connected to the ADD/DROP ports of the 40-SMR1-C card on node r. Traffic from node r can be routed to one side of node R. For example, traffic can be routed from side a to side A or from side b to side B. Traffic from side a cannot be added or dropped at node r but can be routed to side b using the express path. Figure 12-14 Interconnected Ring - Scenario A-2 PP-MESH-4 248896 A A R r B C D a b c d a b B R r P P C-rx D-rx C-tx D-tx Main Ring Traffic c-rx d-tx d-rx c-tx 248895 A A R r B C D a b c d a b B R r C-tx D-rx C-rx D-tx d-tx d-rx c-rx c-tx Main Ring Traffic Booster Booster Tributary Ring Traffic P P12-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings 12.3.1.2 Scenario B: Interconnect Traffic from Tributary Ring to Main Ring with Local Add/Drop in the Tributary Ring In scenario B-1(Figure 12-15), node R is a three-degree colorless and omni-directional ROADM node and node r is a hub node with two terminal sides equipped with 40-SMR1-C or 40-WSS-C cards. The EAD ports of the 80-WXC-C cards on node R are connected to the EXP ports of the 40-SMR1-C or40-WSS-C card on node r. Traffic from node r can be routed to side A or B of node R. Traffic local to the tributary ring can be added or dropped at node r. For example, traffic from side a can be dropped at node r but cannot be routed to side b since the EXP ports are not available. Figure 12-15 Interconnected Ring - Scenario B-1 In scenario B-2 (Figure 12-16), node R is a two-degree colorless ROADM node and node r is a hub node with two terminal sides equipped with 40-SMR1-C or 40-WSS-C cards. The EAD ports of the 80-WXC-C cards on node R are connected to the EXP ports of the 40-WSS-C card on node r. Traffic from node r can be routed to one side of node R. For example, traffic can be routed from side a to side A or from side b to side B. Traffic local to the tributary ring can be added or dropped at node r. For example, traffic from side a can be dropped at node r but cannot be routed to side b since the EXP ports are not available. PP-MESH-4 248896 A A R r B C D a b c d a b B R r P P C-rx D-rx C-tx D-tx Main Ring Traffic c-rx d-tx d-rx c-tx12-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings Figure 12-16 Interconnected Ring - Scenario B-2 12.3.1.3 Scenario C: Interconnect Traffic Between Tributary Rings Using the Main Ring In scenario C-1(Figure 12-17), nodes R1 and R2 are n-degree colorless and omni-directional ROADM nodes. Node r is a terminal site. The EXP ports of the 40-SMR-1C card in node r are connected to the EAD ports of the 80-WXC-C card in nodes R1 and R2. Traffic from node r is routed to side A and B of nodes R1 and R2. Traffic local to the tributary ring can be added or dropped at node r. 248897 a b r c-rx d-tx d-rx c-tx A B R C-tx D-rx C-rx D-tx Booster Booster P P A R r B C D a b c d Main Ring Traffic12-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Interconnected Rings Figure 12-17 Interconnected Ring - Scenario C-1 In scenario C-2(Figure 12-18), node R is an n-degree colorless and omni-directional ROADM node with 2 omni-directional sides. Nodes r1 and r2 are hub sites. The ADD/DROP ports of 40-SMR-1-C cards in node r1 and r2 are connected to the EAD ports of 80-WXC-C cards in node R. Traffic can be routed from node r1 to node r2 through node R. Traffic local to the tributary ring can be added or dropped at node r1 and r2. Figure 12-18 Interconnected Ring - Scenario C-2 PP-MESH-4 248898 A A A R R R1 r r r r R2 B C B c a a B R P P C-rx C-tx c-rx c-tx Main Ring Tributary Ring r PP-MESH-4 248899 A a b B R r1 P P C-rx D-rx a b r2 P P C-tx D-tx F-rx F-rx E-tx E-tx A R r1 B C D E F a b r2 a b c d c d Main Ring Traffic Tributary Interring Traffic Tributary Interring Traffic Traffic Tributary to Main12-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Spur Configuration 12.4 Spur Configuration Remote terminal sites can be connected to the main network using a spur. In a spur configuration, the multiplexer (MUX) and demultiplexer (DMX) units associated with one of the sides of node R in the main network (Figure 12-19) are moved to the remote terminal site T. This helps to aggregate traffic from the terminal site. The MUX and DMX units in terminal site T are connected to node R with a single fibre couple. Node R is a n-degree ROADM node equipped with 40-SMR1-C, 40-SMR2-C, or 80-WXC-C cards. Traffic from terminal site T can be routed to side A or side B on node R. Amplification on the spur link is not allowed. PSM is not supported on terminal site T. Figure 12-19 Spur 12.4.1 Spur Configuration Scenarios In the following sections, three spur scenarios are provided: 12.4.1.1 Scenario A: Spur Configuration without 15454 Chassis in RemoteTerminal T In Figure 12-20, node R is a two-degree ROADM node equipped with 40-SMR1-C card. The remote terminal site T does not have a 15454 chassis and is not shown in the network map in CTC. The terminal site is built using passive MUX and DMX units. All OCHNC circuits originating from 40-SMR1-C on Side A of node R to the remote terminal site are terminated on 40-SMR1-C ADD/DROP ports. A T B Spur 249089 R H R12-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Spur Configuration Figure 12-20 Scenario A: Spur Without 15454 Chassis in RemoteTerminal T 12.4.1.2 Scenario B: Spur Configuration with Passive MUX and DMX Units in Remote Terminal T In Figure 12-21, node R is a two-degree ROADM node equipped with 40-SMR1-C card. The terminal site T is built with a 15454 chassis equipped with TXP units and passive MUX and DMX units. Terminal site T is connected to node R on the network map in CTC. All OCHNC circuits originating from 40-SMR1-C on Side A of node R to the remote site are terminated on 40-SMR1-C ADD/DROP ports. OCHCC and OCHTRAIL circuits are supported on the TXP units in terminal site T. Figure 12-21 Scenario B: Spur With Passive MUX and DMX Units in Remote Terminal T 249090 40-SMR-1-C T Side A node R Booster DMX MUX 249091 40-SMR-1-C T TXP TXP TXP TXP TXP TXP TXP TXP Side A node R Booster DMX MUX12-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies for the OPT-RAMP-C and OPT-RAMP-CE Cards 12.4.1.3 Scenario C: Spur Configuration with Active MUX and DMX Units in Remote Terminal T In Figure 12-22, node R is a two-degree ROADM node equipped with 40-SMR1-C card. The terminal site T is built with a 15454 chassis equipped with TXP units and active MUX and DMX units. Terminal site T is connected to node R on the network map in CTC. DCN extension is supported between the ADD/DROP ports of 40-SMR1-C and the COM ports of the active MUX and DMX units. OCHNC circuits are terminated on the CHAN ports of the MUX and DMX units of terminal site T. OCHCC and OCHTRAIL circuits are supported on the TXP units in terminal site T. Figure 12-22 Scenario C: Spur with Active MUX and DMX Units in Remote Terminal T 12.5 Network Topologies for the OPT-RAMP-C and OPT-RAMP-CE Cards The OPT-RAMP-C or OPT-RAMP-CE card can be equipped in any of the following network topologies: • Open (hubbed) ring network • Multi-hubbed ring network • Closed (meshed) ring network • Any-to-any ring network • Linear network topology • Point-to-point linear network topology • Multi-ring network • Mesh network • Hybrid network For more information about the OPT-RAMP-C or OPT-RAMP-CE card, see Chapter 4, “Optical Amplifier Cards.”. 249091 40-SMR-1-C T TXP TXP TXP TXP TXP TXP TXP TXP Side A node R Booster DMX MUX12-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Topologies for the PSM Card 12.6 Network Topologies for the PSM Card The PSM card is supported in the following network topologies: • The PSM card in a channel protection configuration is supported in all network topologies except linear networks as it is not possible to configure a working and protect path. • The PSM card in a multiplex section protection configuration is supported in linear point-to-point network topologies. • The PSM card in a line protection configuration is supported in the following network topologies: – Linear point-to-point in a single span network (if the OSC card is used). – Linear point-to-point multispan network when a DCN extension is used (on all spans). In this case, the maximum number of span links can be divided into three according to the DCN extension optical safety requirements. • The PSM card in a standalone configuration is supported in all network topologies. 12.7 Optical Performance This section provides optical performance information for ONS 15454 DWDM networks. The performance data is a general guideline based upon the network topology, node type, client cards, fiber type, number of spans, and number of channels. The maximum number of nodes that can be in an ONS 15454 DWDM network is 16. The DWDM topologies and node types that are supported are shown in Table 12-1. Table 12-1 Supported Topologies and Node Types Number of Channels Fiber Topologies Node Types 32 channels SMF-281 E-LEAF2 TW-RS3 1. SMF-28 = single-mode fiber 28. 2. E-LEAF = enhanced large effective area fiber. 3. TW-RS = TrueWave reduced slope fiber. Ring Linear Linear without OADM Hub Active OADM Passive OADM Terminal Line OSC regeneration 16 channels SMF-28 Ring Linear Linear without OADM Hub Active OADM Passive OADM Terminal Line OSC regeneration 8 channels SMF-28 Linear without OADM Terminal Line12-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Automatic Power Control 12.8 Automatic Power Control The ONS 15454 automatic power control (APC) feature performs the following functions: • Maintains constant per channel power when desired or accidental changes to the number of channels occur. Constant per channel power increases optical network resilience. • Compensates for optical network degradation (aging effects). • Simplifies the installation and upgrade of DWDM optical networks by automatically calculating the amplifier setpoints. Note APC algorithms manage the optical parameters of the OPT-BST, OPT-PRE, OPT-AMP-17-C, 32DMX, 40-DMX-C, 40-DMX-CE, 40-SMR1-C, 40-SMR2-C, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, and 32DMX-L cards. Amplifier software uses a control gain loop with fast transient suppression to keep the channel power constant regardless of any changes in the number of channels. Amplifiers monitor the changes to the input power and change the output power proportionately according to the calculated gain setpoint. The shelf controller software emulates the control output power loop to adjust for fiber degradation. To perform this function, the TCC2/TCC2P/TCC3/TNC/TSC needs to know the channel distribution, which is provided by a signaling protocol, and the expected per channel power, which you can provision. The TCC2/TCC2P/TCC3/TNC/TSC card compares the actual amplifier output power with the expected amplifier output power and modifies the setpoints if any discrepancies occur. 12.8.1 APC at the Amplifier Card Level In constant gain mode, the amplifier power out control loop performs the following input and output power calculations, where G represents the gain and t represents time. Pout (t) = G * Pin (t) (mW) Pout (t) = G + Pin (t) (dB) In a power-equalized optical system, the total input power is proportional to the number of channels. The amplifier software compensates for any variation of the input power due to changes in the number of channels carried by the incoming signal. Amplifier software identifies changes in the read input power in two different instances, t1 and t2, as a change in the traffic being carried. The letters m and n in the following formula represent two different channel numbers. Pin/ch represents the input power per channel. Pin (t1)= nPin/ch Pin (t2) = mPin/ch Amplifier software applies the variation in the input power to the output power with a reaction time that is a fraction of a millisecond. This keeps the power constant on each channel at the output amplifier, even during a channel upgrade or a fiber cut. The per channel power and working mode (gain or power) are set by automatic node setup (ANS). The provisioning is conducted on a per-side basis. A preamplifier or a booster amplifier facing Side i is provisioned using the Side i parameters present in the node database, where i - A, B, C, D, E, F, G, or H. Starting from the expected per channel power, the amplifiers automatically calculate the gain setpoint after the first channel is provisioned. An amplifier gain setpoint is calculated in order to make it equal to the loss of the span preceding the amplifier itself. After the gain is calculated, the setpoint is no longer 12-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Automatic Power Control changed by the amplifier. Amplifier gain is recalculated every time the number of provisioned channels returns to zero. If you need to force a recalculation of the gain, move the number of channels back to zero. 12.8.2 APC at the Shelf Controller Layer Amplifiers are managed through software to control changes in the input power caused by changes in the number of channels. The software adjusts the output total power to maintain a constant per channel power value when the number of input channel changes. Changes in the network characteristics have an impact on the amplifier input power. Changes in the input power are compensated for only by modifying the original calculated gain, because input power changes imply changes in the span loss. As a consequence, the gain to span loss established at amplifier start-up is no longer satisfied, as shown in Figure 12-23. Figure 12-23 Using Amplifier Gain Adjustment to Compensate for System Degradation In Figure 12-23, Node 1 and Node 2 are equipped with booster amplifiers and preamplifiers. The input power received at the preamplifier on Node 2 (Pin2) depends on the total power launched by the booster amplifier on Node1, Pout1(n) (where n is the number of channels), and the effect of the span attenuation (L) between the two nodes. Span loss changes due to aging fiber and components or changes in operating conditions. The power into Node 2 is given by the following formula: Pin2 = LPout1(n) The phase gain of the preamplifier on Node 2 (GPre-2) is set during provisioning in order to compensate for the span loss so that the Node 2 preamplifier output power (Pout-Pre-2) is equal to the original transmitted power, as represented in the following formula: Pout-Pre-2 = L x GPre-2 x Pout1(n) In cases of system degradation, the power received at Node 2 decreases due to the change of span insertion loss (from L to L'). As a consequence of the preamplifier gain control working mode, the Node 2 preamplifier output power (Pout-Pre-2) also decreases. The goal of APC at the shelf controller layer is simply to detect if an amplifier output change is needed because of changes in the number of channels or to other factors. If factors other than changes in the number of channels occur, APC provisions a new gain at the Node 2 preamplifier (GPre-2') to compensate for the new span loss, as shown in the formula: GPre-2' = GPre-2 (L/ L') = GPre-2 + [Pout-Pre-2 –Exp(Pout-Pre-2)] Generalizing on the above relationship, APC is able to compensate for system degradation by adjusting working amplifier gain or variable optical attenuation (VOA) and to eliminate the difference between the power value read by the photodiodes and the expected power value. The expected power values are calculated using: • Provisioned per channel power value • Channel distribution (the number of express, add, and drop channels in the node) • ASE estimation 159501 Node 1 G1 Node 2 G2 P P L out1 P in2 out212-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Automatic Power Control Channel distribution is determined by the sum of the provisioned and failed channels. Information about provisioned wavelengths is sent to APC on the applicable nodes during circuit creation. Information about failed channels is collected through a signaling protocol that monitors alarms on ports in the applicable nodes and distributes that information to all the other nodes in the network. ASE calculations purify the noise from the power level reported from the photodiode. Each amplifier can compensate for its own noise, but cascaded amplifiers cannot compensate for ASE generated by preceding nodes. The ASE effect increases when the number of channels decreases; therefore, a correction factor must be calculated in each amplifier of the ring to compensate for ASE build-up. APC is a network-level feature that is distributed among different nodes. An APC domain is a set of nodes that is controlled by the same instance of APC at the network level. An APC domain optically identifies a portion of the network that can be independently regulated. An optical network can be divided into several different domains, with the following characteristics: • Every domain is terminated by two node sides. The node sides terminating domains are: – Terminal node (any type) – ROADM node – Hub node – Cross-connect (XC) termination mesh node – Line termination mesh node • APC domains are shown in both Cisco Transport Controller (CTC) and Transaction Language One (TL1). • In CTC, domains are shown in the network view and reported as a list of spans. Each span is identified by a node/side pair, for example: APC Domain Node_1 Side A, Node_4 Side B + Span 1: Node_1 Side A, Node_2 Side B + Span 2: Node_2 Side A, Node_3 Side B + Span 3: Node_3 Side A, Node_4 Side B • APC domains are not refreshed automatically; instead, they are refreshed using a Refresh button. Inside a domain, the APC algorithm designates a master node that is responsible for starting APC hourly or every time a new circuit is provisioned or removed. Every time the master node signals APC to start, gain and VOA setpoints are evaluated on all nodes in the network. If corrections are needed in different nodes, they are always performed sequentially following the optical paths starting from the master node. APC corrects the power level only if the variation exceeds the hysteresis thresholds of +/– 0.5 dB. Any power level fluctuation within the threshold range is skipped since it is considered negligible. Because APC is designed to follow slow time events, it skips corrections greater than 3 dB. This is the typical total aging margin that is provisioned during the network design phase. After you provision the first channel or the amplifiers are turned up for the first time, APC does not apply the 3 dB rule. In this case, APC corrects all the power differences to turn up the node. To avoid large power fluctuations, APC adjusts power levels incrementally. The maximum power correction is +/– 0.5 dB. This is applied to each iteration until the optimal power level is reached. For example, a gain deviation of 2 dB is corrected in four steps. Each of the four steps requires a complete APC check on every node in the network. APC can correct up to a maximum of 3 dB on an hourly basis. If degradation occurs over a longer time period, APC compensates for it by using all margins that you provision during installation. If no margin is available, adjustments cannot be made because setpoints exceed the ranges. APC communicates the event to CTC, Cisco Transport Manager (CTM), and TL1 through an APC Fail condition. APC clears the APC fail condition when the setpoints return to the allowed ranges.12-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Automatic Power Control APC can be manually disabled. In addition, APC automatically disables itself when: • An Hardware Fail (HF) alarm is raised by any card in any of the domain nodes. • A Mismatch Equipment Alarm (MEA) is raised by any card in any of the domain nodes. • An Improper Removal (IMPROPRMVL) alarm is raised by any card in any of the domain nodes. • Gain Degrade (GAIN-HDEG), Power Degrade (OPWR-HDEG), and Power Fail (PWR-FAIL) alarms are raised by the output port of any amplifier card in any of the domain nodes. • A VOA degrade or fail alarm is raised by any of the cards in any of the domain nodes. • The signaling protocol detects that one of the APC instances in any of the domain nodes is no longer reachable. The APC state (Enable/Disable) is located on every node and can be retrieved by the CTC or TL1 interface. If an event that disables APC occurs in one of the network nodes, APC is disabled on all the other nodes and the APC state changes to DISABLE - INTERNAL. The disabled state is raised only by the node where the problem occurred to simplify troubleshooting. APC raises the following minor, non-service-affecting alarms at the port level in CTC, TL1, and Simple Network Management Protocol (SNMP): • APC Out of Range—APC cannot assign a new setpoint for a parameter that is allocated to a port because the new setpoint exceeds the parameter range. • APC Correction Skipped—APC skipped a correction to one parameter allocated to a port because the difference between the expected and current values exceeds the +/– 3 dB security range. • APC Disabled—APC is disabled, either by a user or internal action. After the error condition is cleared, the signaling protocol enables APC on the network and the APC DISABLE - INTERNAL condition is cleared. Because APC is required after channel provisioning to compensate for ASE effects, all optical channel network connection (OCHNC) and optical channel client connection (OCHCC) circuits that you provision during the disabled APC state are kept in the Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS) (ANSI) or Unlocked-disabled,automaticInService (ETSI) service state until APC is enabled. OCHNCs and OCHCCs automatically go into the In-Service and Normal (IS-NR) (ANSI) or Unlocked-enabled (ETSI) service state only after APC is enabled. 12.8.3 Managing APC The APC status is indicated by four APC states shown in the node view status area: • Enabled—APC is enabled. • Disabled—APC was disabled manually by a user. • Disable - Internal—APC has been automatically disabled for an internal cause. • Not Applicable—The node is provisioned to Not DWDM, which does not support APC. You can view the APC information and disable and enable APC manually on the Maintenance > DWDM > APC tab. Caution When APC is disabled, aging compensation is not applied and circuits cannot be activated. Do not disable APC unless it is required for specific maintenance or troubleshooting tasks. Always enable APC as soon as the tasks are completed. The APC subtab provides the following information:12-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Power Side Monitoring • Position—The slot number, card, and port for which APC information is shown. • Last Modification—Date and time APC parameter setpoints were last modified. • Parameter—The parameter that APC last modified. • Last Check—Date and time APC parameter setpoints were last verified. • Side—The side where the APC information for the card and port is shown. • State—The APC state. A wrong use of maintenance procedures (for example, the procedures to be applied in case of fiber cut repair) can lead the system to raise the APC Correction Skipped alarm. The APC Correction Skipped alarm strongly limits network management (for example, a new circuit cannot be turned into IS). The Force APC Correction button helps to restore normal conditions by clearing the APC Correction Skipped alarm. The Force APC Correction button must be used under the Cisco TAC surveillance since its misuse can lead to traffic loss. The Force APC Correction button is available in the Card View > Maintenance > APC tab pane in CTC for the following cards: • OPT-PRE • OPT-BST-E • OPT-BST • OPT-AMP-C • OPT-AMP-17C • AD-xB • AD-xC • 40-SMR1-C • 40-SMR2-C This feature is not available for the TL1 interface. 12.9 Power Side Monitoring DWDM nodes allow you to view the side power levels on the Maintenance > DWDM > Side Power Monitoring > Optical Side n tab, where n is A, B, C, D(Figure 12-24). Each existing channel will have an IN and OUT power on each node side in the case of bidirectional circuits. OUT indicates the power on the output port with respect to the side to which it is referred to. It is the last port of the side before the first amplified port in the direction going from the node to the span or the output port of the side itself if there are no amplified ports. IN indicates the power on the input port with respect to the side to which is referred to. It is the first port of the side after the last amplified port in the direction going from the span to the node or the input port of the side itself if there are no amplified ports.12-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Span Loss Verification Figure 12-24 ROADM Power Monitoring Subtab 12.10 Span Loss Verification Span loss measurements can be performed from the Maintenance > DWDM > WDM Span Check tab. The CTC span check compares the far-end OSC power with the near-end OSC power. A Span Loss Out of Range condition is raised when the measured span loss is higher than the maximum expected span loss. It is also raised when the measured span loss is lower than the minimum expected span loss and the difference between the minimum and maximum span loss values is greater than 1 dB. The minimum and maximum expected span loss values are calculated by Cisco TransportPlanner for the network and imported into CTC. However, you can manually change the minimum and expected span loss values. CTC span loss measurements provide a quick span loss check and are useful whenever changes to the network occur, for example after you install equipment or repair a broken fiber. CTC span loss measurement resolutions are: • +/– 1.5 dB for measured span losses between 0 and 25 dB • +/– 2.5 dB for measured span losses between 25 and 38 dB For ONS 15454 span loss measurements with higher resolutions, an optical time domain reflectometer (OTDR) must be used. 12-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Span Loss Verification Note From Software Release 9.0 onwards, span loss measurement is performed using C-band channels (whenever available), instead of OSC signals. Software Release 9.0 is not interoperable with earlier releases that are only OSC-based. Therefore, span loss measurement cannot be done on a span if the adjacent nodes are running different software releases; for example one node running Software Release 8.0 or an earlier release and the second node running Software Release 9.0 or a later release. 12.10.1 Span Loss Measurements on Raman Links Span loss measurement when Raman amplification is active is less accurate than a standard link as it is based on a mathematical formula that uses the Raman noise and Raman gain. Span loss on a Raman link is measured in the following states: • Automatically during Raman link setup (without Raman amplification) • Automatically during fiber cut restore (without Raman amplification) • Periodically or upon request (with Raman amplification) CTC reports three values in the Maintenance > DWDM > WDM Span Check tab: • Current Span Measure with Raman—Estimated span loss with Raman pump turned ON. • Wizard Span Measure with Raman Off—Span loss with Raman pump turned OFF, during Raman installation. • Last Span Measure with Raman—Span loss after a fiber cut restoration procedure. Measurements are performed automatically on an hourly basis. A Span Loss Out of Range condition is raised under the following conditions: • Span loss is greater than the maximum expected span loss + resolution • Span loss is less than the minimum expected span loss – resolution The minimum and maximum expected span loss values are calculated by Cisco Transport Planner for the network and imported into CTC. However, you can manually change the minimum and maximum expected span loss values. Note During Raman installation using a wizard, the Span Loss Out of Range alarm is not raised when the out of range condition is raised. In such a case, the wizard fails and an error message is displayed, and the span is not tuned. CTC span loss measurements provide a quick span loss check and are useful whenever changes to the network occur, for example after you install equipment or repair a broken fiber. CTC span loss measurement resolutions are: • +/– 1.5 dB for span loss measurements between 0 and 26 dB • +/– 2.0 dB for span loss measurements between 26 and 31 dB • +/– 3.0 dB for span loss measurements between 31 and 34 dB • +/– 4.0 dB for span loss measurements between 34 and 36 dB12-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety 12.11 Network Optical Safety If a fiber break occurs on the network, automatic laser shutdown (ALS) automatically shuts down the OSCM and OSC-CSM OSC laser output power and the optical amplifiers contained in the OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C, OPT-RAMP-CE, 40-SMR1-C, and 40-SMR2-C cards, and the TX VOA in the protect path of the PSM card (in line protection configuration only). (Instead, the PSM active path will use optical safety mechanism implemented by the booster amplifier or OSC-CSM card that are mandatory in the line protection configuration.) The Maintenance > ALS tab in CTC card view provide the following ALS management options for OSCM, OSC-CSM, OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C, OPT-RAMP-CE, 40-SMR1-C, 40-SMR2-C, and PSM (on the protect path, only in line protection configuration) cards: • Disable—ALS is off. The OSC laser transmitter and optical amplifiers are not automatically shut down when a traffic outage loss of signal (LOS) occurs. • Auto Restart—ALS is on. The OSC laser transmitter and optical amplifiers automatically shut down when traffic outages (LOS) occur. It automatically restarts when the conditions that caused the outage are resolved. Auto Restart is the default ALS provisioning for OSCM, OSC-CSM, OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C, OPT-RAMP-CE, 40-SMR1-C, 40-SMR2-C, and PSM (on the protect path, only in line protection configuration) cards. • Manual Restart—ALS is on. The OSC laser transmitter and optical amplifiers automatically shut down when traffic outages (LOS) occur. However, the laser must be manually restarted when conditions that caused the outage are resolved. • Manual Restart for Test—Manually restarts the OSC laser transmitter and optical amplifiers for testing. 12.11.1 Automatic Laser Shutdown When ALS is enabled on OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C, OPT-RAMP-CE, 40-SMR1-C, 40-SMR2-C, PSM (on the protect path, only in line protection configuration), OSCM, OSC-CSM, and TNC cards, a network safety mechanism will occur in the event of a system failure. ALS provisioning is also provided on the transponder (TXP) and muxponder (MXP) cards. However, if a network uses ALS-enabled OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C, OPT-RAMP-CE, 40-SMR1-C, 40-SMR2-C, PSM (on the protect path, only in line protection configuration), OSCM, and OSC-CSM cards, ALS does not need to be enabled on the TXP cards or MXP cards. ALS is disabled on TXP and MXP cards by default and the network optical safety is not impacted. If TXP and MXP cards are connected directly to each other without passing through a DWDM layer, ALS should be enabled on them. The ALS protocol goes into effect when a fiber is cut, enabling some degree of network point-to-point bidirectional traffic management between the cards. If ALS is disabled on the OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, OPT-RAMP-C, OPT-RAMP-CE, 40-SMR1-C, 40-SMR2-C, PSM (on the protect path, only in line protection configuration), OSCM, and OSC-CSM cards (the DWDM network), ALS can be enabled on the TXP and MXP cards to provide laser management in the event of a fiber break in the network between the cards.12-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety 12.11.2 Automatic Power Reduction Automatic power reduction (APR) is controlled by the software and is not user configurable. During amplifier restart after a system failure, the amplifier (OPT-BST, for example) operates in pulse mode and an APR level is activated so that the Hazard Level 1 power limit is not exceeded. This is done to ensure personnel safety. When a system failure occurs (cut fiber or equipment failure, for example) and ALS Auto Restart is enabled, a sequence of events is placed in motion to shut down the amplifier laser power, then automatically restart the amplifier after the system problem is corrected. As soon as a loss of optical payload and OSC is detected at the far end, the far-end amplifier shuts down. The near-end amplifier then shuts down because it detects a loss of payload and the OSC shuts down due to the far-end amplifier shutdown. At this point, the near end attempts to establish communication to the far end using the OSC laser transmitter. To do this, the OSC emits a two-second pulse at very low power (maximum of 0 dBm) and waits for a similar two-second pulse in response from the far-end OSC laser transmitter. If no response is received within 100 seconds, the near end tries again. This process continues until the near end receives a two-second response pulse from the far end, indicating the system failure is corrected and full continuity in the fiber between the two ends exists. After the OSC communication is established, the near-end amplifier is configured by the software to operate in pulse mode at a reduced power level. It emits a nine-second laser pulse with an automatic power reduction to +8 dBm. (For 40-SMR1-C and 40-SMR2-C cards, the pulse is not +8 dBm but it is the per channel power setpoint.) This level assures that Hazard Level 1 is not exceeded, for personnel safety, even though the establishment of successful OSC communication is assurance that any broken fiber is fixed. If the far-end amplifier responds with a nine-second pulse within 100 seconds, both amplifiers are changed from pulse mode at reduced power to normal operating power mode. For a direct connection between TXP or MXP cards, when ALS Auto Restart is enabled and the connections do not pass through a DWDM layer, a similar process takes place. However, because the connections do not go through any amplifier or OSC cards, the TXP or MXP cards attempt to establish communication directly between themselves after a system failure. This is done using a two-second restart pulse, in a manner similar to that previously described between OSCs at the DWDM layer. The power emitted during the pulse is below Hazard Level 1. APR is also implemented on the PSM card (on the protect path, only in line protection configuration). In the PSM line protection configuration, when a system failure occurs on the working path (cut fiber or equipment failure, for example), the ALS and APR mechanisms are implemented by the booster amplifier or the OSC-CSM card. Alternately, when a system failure occurs on the protect path, and ALS Auto Restart is enabled on the PSM card, a sequence of events is placed in motion to shut down the TX VOA on the protect path, and then automatically restart it after the system failure is corrected. During protect path restart, the TX VOA on the protect path operates in pulse mode and limits the power to maximum +8 dBm so that the Hazard Level 1 power limit is not exceeded on protect TX path. When ALS is disabled, the warning Statement 1056 is applicable. Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not view directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm may pose an eye hazard. Statement 1056 Note If you must disable ALS, verify that all fibers are installed in a restricted location. Enable ALS immediately after finishing the maintenance or installation process.12-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety Note For the line amplifier to start up automatically, disable the ALS on the terminal node that is unidirectional. 12.11.3 Network Optical Safety on OPT-RAMP-C and OPT-RAMP-CE Cards Optical safety on the OPT-RAMP-C and OPT-RAMP-CE cards is implemented in the RAMAN-TX and COM-TX ports. RAMAN-TX will report safety settings associated to the Raman pump while the COM-TX port will report safety settings associated with the embedded EDFA. 12.11.3.1 RAMAN-TX Settings on Raman Pump The Raman pump is automatically turned off as soon as the LOS alarm is detected on the LINE-RX port. The Raman pump is automatically turned on at APR power every 100 secs for a duration of 9 seconds at a pulse power of at 8 dBm, as soon as the LINE-RX port is set to IS-NR/unlocked-enabled. Note Optical safety cannot be disabled on the OPT-RAMP-C and OPT-RAMP-CE cards and cannot be disabled on OSCM cards when connected to a OPT-RAMP-C or OPT-RAMP-CE card. The system periodically verifies if the signal power is present on the LINE-RX port. If signal power is present, the following occurs: • Pulse duration is extended. • Raman pumps are turned on at APR power, if the laser was shut down. The Raman power is then moved to setpoint if power is detected for more than 10 seconds. During Automatic Laser Restart (ALR) the safety is enabled. The laser is automatically shut down if LOS is detected on the receiving fiber. In general Raman pump turns on only when Raman signals are detected. However, the Raman pump can be configured to turn on to full power even when OSC power is detected for more than 9 seconds on OSC-RX port. 12.11.3.2 COM-TX Safety Setting on EDFA EDFA is shutdown automatically under the following conditions: • The Raman pumps shut down. • An LOS-P alarm is detected on the COM-RX port. If EDFA was shut down because of Raman pump shut down, the EDFA restarts by automatically turning on the EDFA lasers as soon as the Raman loop is closed. • Pulse duration: 9 seconds • Pulse power: 8 dB (maximum APR power foreseen by safety regulation) • Exit condition: Received power detected on the DC-RX port at the end of APR pulse. If power is detected on DC-RX (so DCU is connected) EDFA moves to set-point; otherwise, it keeps 9 dB as the output power at restart • EDFA moves to the power set point when power is detected on the DC-RX port. If EDFA was shutdown because of an LOS-P alarm. The EDFA restarts by automatically turning on the EDFA laser as soon as an LOS-P alarm on the COM-RX port is cleared, and the Raman loop is closed.12-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety • Pulse duration: 9 seconds • Pulse power: 8 dB (maximum APR power foreseen by safety regulation) • Exit condition: Received power detected on the LINE-RX port at the end of the APR pulse Warning All ONS 15454 users must be properly trained on laser safety hazards in accordance with IEC 60825-2, or ANSI Z136.1. 12.11.4 Fiber Cut Scenarios In the following paragraphs, four ALS scenarios are given: • 12.11.4.1 Scenario 1: Fiber Cut in Nodes Using OPT-BST/OPT-BST-E Cards, page 12-30 • 12.11.4.2 Scenario 2: Fiber Cut in Nodes Using OSC-CSM Cards, page 12-32 • 12.11.4.3 Scenario 3: Fiber Cut in Nodes Using OPT-BST-L Cards, page 12-34 • 12.11.4.4 Scenario 4: Fiber Cut in Nodes Using OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C (OPT-LINE Mode), 40-SMR1-C, or 40-SMR2-C Cards, page 12-35 • 12.11.4.5 Scenario 5: Fiber Cut in Nodes Using DCN Extension, page 12-37 • 12.11.4.6 Scenario 6: Fiber Cut in Nodes Using OPT-RAMP-C or OPT-RAMP-CE Cards, page 12-39 12.11.4.1 Scenario 1: Fiber Cut in Nodes Using OPT-BST/OPT-BST-E Cards Figure 12-25 shows nodes using OPT-BST/OPT-BST-E cards with a fiber cut between them.12-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety Figure 12-25 Nodes Using OPT-BST/OPT-BST-E Cards Two photodiodes at Node B monitor the received signal strength for the optical payload and OSC signals. When the fiber is cut, an LOS is detected at both of the photodiodes. The AND function then indicates an overall LOS condition, which causes the OPT-BST/OPT-BST-E transmitter, OPT-PRE transmitter, and OSCM lasers to shut down. This in turn leads to an LOS for both the optical payload and OSC at Node A, which causes Node A to turn off the OSCM, OPT-PRE transmitter, and OPT-BST/OPT-BST-E transmitter lasers. The sequence of events after a fiber cut is as follows (refer to the numbered circles in Figure 12-25): 1. Fiber is cut. 2. The Node B power monitoring photodiode detects a Loss of Incoming Payload (LOS-P) on the OPT-BST/OPT-BST-E card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 3. On the OPT-BST/OPT-BST-E card, the simultaneous LOS-O and LOS-P detection triggers a command to shut down the amplifier. CTC reports an LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 4. The OPT-BST/OPT-BST-E card amplifier is shut down within one second. 5. The OSCM laser is shut down. 6. The OPT-PRE card automatically shuts down due to a loss of incoming optical power. 7. The Node A power monitoring photodiode detects a LOS-O on the OPT-BST/OPT-BST-E card and the OSCM card detects a LOS (OC3) at the SONET layer. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 8. The Node A power monitoring photodiode detects a LOS-P on the OPT-BST/OPT-BST-E card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. OPT-BST/OPT-BST-E OPT-BST/OPT-BST-E P P P OSCM P P OSCM = power monitoring photodiode = logical AND function Node A Side B Node B Side A X 11 1 7 13 10 9 8 12 6 2 3 4 5 2 8 120988 OPT-PRE OPT-PRE12-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety 9. On the OPT-BST/OPT-BST-E, the simultaneous LOS-O and LOS-P detection triggers a command to shut down the amplifier. CTC reports an LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 10. The OPT-BST/OPT-BST-E card amplifier is shut down within one second. 11. The OSCM laser is shut down. 12. The Node A OPT-PRE card automatically shuts down due to a loss of incoming optical power. When the fiber is repaired, either an automatic or manual restart at the Node A OPT-BST/OPT-BST-E transmitter or at the Node B OPT-BST/OPT-BST-E transmitter is required. A system that has been shut down is reactivated through the use of a restart pulse. The pulse is used to signal that the optical path has been restored and transmission can begin. For example, when the far end, Node B, receives a pulse, it signals to the Node B OPT-BST/OPT-BST-E transmitter to begin transmitting an optical signal. The OPT-BST/OPT-BST-E receiver at Node A receives that signal and signals the Node A OPT-BST/OPT-BST-E transmitter to resume transmitting. Note During a laser restart pulse, APR ensures that the laser power does not exceed Class 1 limits. See the “12.11.2 Automatic Power Reduction” section on page 12-28 for more information about APR. 12.11.4.2 Scenario 2: Fiber Cut in Nodes Using OSC-CSM Cards Figure 12-26 shows nodes using OSC-CSM cards with a fiber cut between them.12-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety Figure 12-26 Nodes Using OSC-CSM Cards Two photodiodes at the Node B OSC-CSM card monitor the received signal strength for the received optical payload and OSC signals. When the fiber is cut, LOS is detected at both of the photodiodes. The AND function then indicates an overall LOS condition, which causes the Node B OSC laser to shut down and the optical switch to block traffic. This in turn leads to LOS for both the optical payload and OSC signals at Node A, which causes Node A to turn off the OSC laser and the optical switch to block outgoing traffic. The sequence of events after a fiber cut is as follows (refer to the numbered circles in Figure 12-26): 1. Fiber is cut. 2. The Node B power monitoring photodiode detects a LOS-P on the OSC-CSM card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 3. On the OSC-CSM, the simultaneous LOS-O and LOS-P detection triggers a change in the position of the optical switch. CTC reports a LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 4. The optical switch blocks outgoing traffic. 5. The OSC laser is shut down. 6. The Node A power monitoring photodiode detects a LOS-O on the OSC-CSM card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 7. The Node A power monitoring photodiode detects a LOS-P on the OSC-CSM card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. OSC-CSM P P P OSC OSC-CSM P P OSC = power monitoring photodiode = logical AND function Node A Side B Node B Side A X 11 1 9 8 7 10 6 2 3 4 5 2 7 12098712-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety 8. On the OSC-CSM, the simultaneous LOS-O and LOS-P detection triggers a change in the position of the optical switch. CTC reports a LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 9. The OSC laser is shut down. 10. The optical switch blocks outgoing traffic. When the fiber is repaired, either an automatic or manual restart at the Node A OSC-CSM card OSC or at the Node B OSC-CSM card OSC is required. A system that has been shut down is reactivated through the use of a restart pulse. The pulse indicates the optical path is restored and transmission can begin. For example, when the far-end Node B receives a pulse, it signals to the Node B OSC to begin transmitting its optical signal and for the optical switch to pass incoming traffic. The OSC-CSM at Node A then receives the signal and tells the Node A OSC to resume transmitting and for the optical switch to pass incoming traffic. 12.11.4.3 Scenario 3: Fiber Cut in Nodes Using OPT-BST-L Cards Figure 12-27 shows nodes using OPT-BST-L cards with a fiber cut between them. Figure 12-27 Nodes Using OPT-BST-L Cards Two photodiodes at Node B monitor the received signal strength for the optical payload and OSC signals. When the fiber is cut, an LOS is detected at both of the photodiodes. The AND function then indicates an overall LOS condition, which causes the OPT-BST-L transmitter and OSCM lasers to shut down. This OPT-BST-L OPT-BST-L P P P OSCM P P OSCM = power monitoring photodiode = logical AND function Node A Side B Node B Side A X 11 1 7 13 10 9 8 12 6 2 3 4 5 2 8 145950 OPT-AMP-L OPT-AMP-L12-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety in turn leads to an LOS for both the optical payload and the OSC at Node A, which causes Node A to turn off the OSCM OSC transmitter and OPT-BST-L amplifier lasers. The sequence of events after a fiber cut is as follows (refer to the numbered circles in Figure 12-27): 1. Fiber is cut. 2. The Node B power monitoring photodiode detects an LOS-P on the OPT-BST-L card. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 3. On the OPT-BST-L card, the simultaneous LOS-O and LOS-P detection triggers a command to shut down the amplifier. CTC reports an LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 4. The OPT-BST-L card amplifier is shut down within one second. 5. The OSCM laser is shut down. 6. The OPT-AMP-L, OPT-AMP-C, or OPT-AMP-17-C card automatically shuts down due to a loss of incoming optical power. 7. The Node A power monitoring photodiode detects an LOS-O on the OPT-BST-L card and the OSCM card detects an LOS (OC3) at the SONET layer. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 8. The Node A power monitoring photodiode detects an LOS-P on the OPT-BST-L card. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 9. On the OPT-BST-L, the simultaneous LOS-O and LOS-P detection triggers a command to shut down the amplifier. CTC reports an LOS alarm (loss of continuity), while the LOS-O and LOS-P are demoted. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 10. The OPT-BST-L card amplifier is shut down within one second. 11. The OSCM laser is shut down. 12. The Node A OPT-AMP-L, OPT-AMP-C, or OPT-AMP-17-C card automatically shuts down due to an LOS for the incoming optical power. When the fiber is repaired, either an automatic or manual restart at the Node A OPT-BST-L transmitter or at the Node B OPT-BST-L transmitter is required. A system that has been shut down is reactivated through the use of a restart pulse. The pulse indicates the optical path is restored and transmission can begin. For example, when the far end, Node B, receives a pulse, it signals to the Node B OPT-BST-L transmitter to begin transmitting an optical signal. The OPT-BST-L receiver at Node A receives that signal and signals the Node A OPT-BST-L transmitter to resume transmitting. Note During a laser restart pulse, APR ensures that the laser power does not exceed Class 1 limits. See the “12.11.2 Automatic Power Reduction” section on page 12-28 for more information about APR. 12.11.4.4 Scenario 4: Fiber Cut in Nodes Using OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C (OPT-LINE Mode), 40-SMR1-C, or 40-SMR2-C Cards Figure 12-28 shows nodes using OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C (in OPT-LINE mode), 40-SMR1-C, or 40-SMR2-C cards with a fiber cut between them. 12-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety Note A generic reference to the OPT-AMP card refers to the OPT-AMP-L, OPT-AMP-17-C, OPT-AMP-C, 40-SMR1-C, or 40-SMR2-C cards. Figure 12-28 Nodes Using OPT-AMP Cards Two photodiodes at Node B monitor the received signal strength for the optical payload and OSC signals. When the fiber is cut, an LOS is detected at both of the photodiodes. The AND function then indicates an overall LOS condition, which causes the OPT-AMP card amplifier transmitter and OSCM card OSC lasers to shut down. This in turn leads to an LOS for both the optical payload and OSC at Node A, which causes Node A to turn off the OSCM card OSC and OPT-AMP card amplifier lasers. The sequence of events after a fiber cut is as follows (refer to the numbered circles in Figure 12-28): 1. Fiber is cut. 2. The Node B power monitoring photodiode detects an LOS-P on the OPT-AMP card. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 3. On the OPT-AMP card, the simultaneous LOS-O and LOS-P detection triggers a command to shut down the amplifier. CTC reports an LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 4. The OPT-AMP card amplifier is shut down within one second. 5. The OSCM card laser is shut down. OPT-AMP-L OPT-AMP-L P P P OSCM P P OSCM = power monitoring photodiode = logical AND function Node A Side B Node B Side A X 10 1 7 9 8 11 6 2 3 4 5 2 8 14594912-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety 6. The Node A power monitoring photodiode detects an LOS-O on the OPT-AMP card and the OSCM card detects an LOS (OC3) at the SONET layer. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 7. The Node A power monitoring photodiode detects an LOS-P on the OPT-AMP card. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 8. On the OPT-AMP card, the simultaneous LOS-O and LOS-P detection triggers a command to shut down the amplifier. CTC reports an LOS alarm (loss of continuity), while LOS-O and LOS-P are demoted. For more information on alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 9. The OPT-AMP card amplifier is shut down within one second. 10. The OSCM card laser is shut down. When the fiber is repaired, either an automatic or manual restart at the Node A OPT-AMP card transmitter or at the Node B OPT-AMP card transmitter is required. A system that has been shut down is reactivated through the use of a restart pulse. The pulse indicates that the optical path is restored and transmission can begin. For example, when the far end, Node B, receives a pulse, it signals to the Node B OPT-AMP card transmitter to begin transmitting an optical signal. The OPT-AMP card receiver at Node A receives that signal and signals the Node A OPT-AMP card transmitter to resume transmitting. Note During a laser restart pulse, APR ensures that the laser power does not exceed Class 1 limits. See the “12.11.2 Automatic Power Reduction” section on page 12-28 for more information about APR. 12.11.4.5 Scenario 5: Fiber Cut in Nodes Using DCN Extension Figure 12-29 shows a fiber cut scenario for nodes that do not have OSC connectivity. In the scenario, references to the OPT-BST cards refers to the OPT-BST, OPT-BST-L, OPT-BST-E, OPT-AMP-L, OPT-AMP-C, OPT-AMP-17-C, 40-SMR1-C, and 40-SMR2-C cards when provisioned in OPT-LINE mode.12-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety Figure 12-29 Fiber Cut With DCN Extension Two photodiodes at Node B monitor the received signal strength for the optical payload. When the fiber is cut, an LOS is detected on the channel photodiode while the other one never gets a signal because the OSC is not present. The AND function then indicates an overall LOS condition, which causes the OPT-BST amplifier transmitter to shut down. This in turn leads to a LOS for the optical payload at Node A, which causes Node A to turn off the OPT-BST amplifier lasers. The sequence of events after a fiber cut is as follows (refer to the numbered circles in Figure 12-29): 1. Fiber is cut. 2. The Node B power monitoring photodiode detects an LOS on the OPT-BST card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide for LOS troubleshooting procedures. 3. On the OPT-BST card, the LOS detection triggers a command to shut down the amplifier. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide for alarm troubleshooting procedures. 4. The OPT-BST card amplifier is shut down within one second. 5. The Node A power monitoring photodiode detects a LOS on the OPT-BST card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide for alarm troubleshooting procedures. 6. On the OPT-BST, the LOS detection triggers a command to shut down the amplifier. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. 7. The OPT-BST card amplifier is shut down within one second. When the fiber is repaired, a manual restart with 9 sec restart pulse time (MANUAL RESTART) is required at the Node A OPT-BST transmitter and at the Node B OPT-BST transmitter. A system that has been shut down is reactivated through the use of a 9 sec restart pulse. The pulse indicates that the optical path is restored and transmission can begin. P P P = power monitoring photodiode = logical AND function X 7 1 6 5 2 3 4 159799 Node A Side B Node B Side A12-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network Optical Safety For example, when the far end, Node B, receives a pulse, it signals to the Node B OPT-BST transmitter to begin transmitting an optical signal. The OPT-BST receiver at Node A receives that signal and signals the Node A OPT-BST transmitter to resume transmitting. Note During a laser restart pulse, APR ensures that the laser power does not exceed Class 1 limits. See the “12.11.2 Automatic Power Reduction” section on page 12-28 for more information about APR. 12.11.4.6 Scenario 6: Fiber Cut in Nodes Using OPT-RAMP-C or OPT-RAMP-CE Cards Figure 12-30 shows a fiber cut scenario for nodes that do not have OSC connectivity. In this scenario, OPT-RAMP-C or OPT-RAMP-CE cards are provisioned in OPT-LINE mode. Figure 12-30 Nodes Using OPT-RAMP-C or OPT-RAMP-CE Cards The following types of photodiodes monitor the received signal strength for the optical payload: • OSC-RX photodiodes • LINE-RX C-band photodiode • Line-TX Raman pump photodiode • COM-RX C-band photodiode The sequence of events after a fiber cut is as follows (refer to the numbered circles in Figure 12-30): 1. Fiber is cut in the direction of Node B to Node A. 2. On Node A, the RAMAN-RX port detects an LOS-R alarm on the OPT-RAMP-C or OPT-RAMP-CE card. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide for LOS-R troubleshooting procedures. 3. On the OPT-RAMP-C or OPT-RAMP-CE card, the LOS-R alarm triggers a command to shut down the Raman pump on Node A. LINE-TX Raman remnant pump photodiode OSC-RX photodiode LINE-RX C-band photodiode COM-RX C-band photodiode 1 8 4 3 2 272075 Raman pumps Embedded EDFA Node A Node B 7 9 10 11 14 1512-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network-Level Gain—Tilt Management of Optical Amplifiers 4. On Node B, the RAMAN-RX port detects an LOS-R alarm. 5. The LOS-R alarm triggers a command to shut down the Raman pump on Node B. 6. Simultaneously, an LOS alarm is detected on Node B, LINE-RX port. 7. The LOS alarm triggers a command to shut down the embedded EDFA. 8. The LINE-RX port detects a LOS alarm and causes the booster amplifier to shut down. 9. On Node A, the LINE-RX port detects a LOS alarm and triggers a command to shut down the embedded EDFA and then the Booster amplifier. Automatic Laser Restart (ALR) on the Raman pump is detected as soon as the fiber is restored. This turns both the Raman pumps to ON state, on both nodes. When power on the Raman pump is restored, it turns on the embedded EDFA also. The booster amplifiers on both Node A and Node B detects power on LINE-RX port. This restarts the booster amplifier. Once the APR cycle is completed, all the lasers move to full power. Note During a laser restart pulse, APR ensures that the laser power does not exceed Class 1 limits. See the “12.11.2 Automatic Power Reduction” section on page 12-28 for more information about APR. 12.12 Network-Level Gain—Tilt Management of Optical Amplifiers The ability to control and adjust per channel optical power equalization is a principal feature of ONS 15454 DWDM metro core network applications. A critical parameter to assure optical spectrum equalization throughout the DWDM system is the gain flatness of erbium-doped fiber amplifiers (EDFAs). Two items, gain tilt and gain ripple, are factors in the power equalization of optical amplifier cards such as the OPT-BST and OPT-PRE. Figure 12-31 shows a graph of the amplifier output power spectrum and how it is affected by gain tilt and gain ripple.12-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network-Level Gain—Tilt Management of Optical Amplifiers Figure 12-31 Effect of Gain Ripple and Gain Tilt on Amplifier Output Power Gain ripple and gain tilt are defined as follows: • Gain ripple is random and depends on the spectral shape of the amplifier optical components. • Gain tilt is systematic and depends on the gain setpoint (Gstp) of the optical amplifier, which is a mathematical function F(Gstp) that relates to the internal amplifier design. Gain tilt is the only contribution to the power spectrum disequalization that can be compensated at the card level. A VOA internal to the amplifier can be used to compensate for gain tilt. An optical spectrum analyzer (OSA) is used to acquire the output power spectrum of an amplifier. The OSA shows the peak-to-peak difference between the maximum and minimum power levels, and takes into account the contributions of both gain tilt and gain ripple. Note Peak-to-peak power acquisition using an OSA cannot be used to measure the gain tilt, because gain ripple itself is a component of the actual measurement. 12.12.1 Gain Tilt Control at the Card Level The OPT-BST and OPT-PRE amplifier cards have a flat output (gain tilt = 0 dB) for only a specific gain value (Gdesign), based on the internal optical design (see Figure 12-32). -4 -2 0 2 4 1530.3 1560.6 Wavelength [nm] Gain Tilt Amplifier Output Spectrum 1550 Gain Ripple Per-Channel power [dB] 13439312-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network-Level Gain—Tilt Management of Optical Amplifiers Figure 12-32 Flat Gain (Gain Tilt = 0 dB) If the working gain setpoint of the amplifier is different from Gdesign, the output spectrum begins to suffer a gain tilt variation. In order to compensate for the absolute value of the increase of the spectrum tilt, the OPT-BST and OPT-PRE cards automatically adjust the attenuation of the VOA to maintain a flat power profile at the output, as shown in Figure 12-33. Figure 12-33 Effect of VOA Attenuation on Gain Tilt The VOA attenuator automatic regulation guarantees (within limits) a zero tilt condition in the EDFA for a wide range of possible gain setpoint values. -3 -2 0 1 1528 1536 1544 1552 1560 -1 Gdesign  VOAatt = 0dB 2 -3 -2 0 1 1528 1536 1544 1552 1560 Wavelength [nm] Gain Tilt = 0 dB -1 Gdesign VOAatt = 0 dB Gain Ripple ~ 2dB 2 134394 Per Channel Power [dB] -6 -4 -2 0 2 4 1528 1536 1544 1552 1560 Wavelength [nm] -6 -4 -2 0 2 4 1528 1536 1544 1552 1560 Wavelength [nm] G < Gdesign VOAatt adjustment VOAat = 0dB VOAatt = Gdesign - G Per Channel Power [dB] 13439512-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network-Level Gain—Tilt Management of Optical Amplifiers Table 12-2 shows the flat output gain range limits for the OPT-BST and OPT-PRE cards, as well as the maximum (worst case) values of gain tilt and gain ripple expected in the specific gain range. If the operating gain value is outside of the range shown in Table 12-2, the EDFA introduces a tilt contribution for which the card itself cannot directly compensate. This condition is managed in different ways, depending the amplifier card type: • OPT-BST—The OPT-BST amplifier is, by design, not allowed to work outside the zero tilt range. Cisco TransportPlanner network designs use the OPT-BST amplifier card only when the gain is less than or equal to 20 dB. • OPT-PRE—Cisco TransportPlanner allows network designs even if the operating gain value is equal to or greater than 21 dB. In this case, a system-level tilt compensation strategy is adopted by the DWDM system. A more detailed explanation is given in 12.12.2 System Level Gain Tilt Control, page 12-43. 12.12.2 System Level Gain Tilt Control System level gain tilt control for OPT-PRE cards is achievable with two main scenarios: • Without an ROADM node • With an ROADM node 12.12.2.1 System Gain Tilt Compensation Without ROADM Nodes When an OPT-PRE card along a specific line direction (Side A-to-Side B or Side B-to-Side A) is working outside the flat output gain range (G > 21 dB), the unregulated tilt is compensated for in spans that are not connected to ROADM nodes by configuring an equal but opposite tilt on one or more of the amplifiers in the downstream direction. The number of downstream amplifiers involved depends on the amount of tilt compensation needed and the gain setpoint of the amplifiers that are involved. See Figure 12-34. Table 12-2 Flat Output Gain Range Limits Amplifier Card Type Flat Output Gain Range Gain Tilt (Maximum) Gain Ripple (Maximum) OPT-BST G < 20 dB 0.5 dB 1.5 dB OPT-PRE G < 21 dB 0.5 dB 1.5 dB12-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network-Level Gain—Tilt Management of Optical Amplifiers Figure 12-34 System Tilt Compensation Without an ROADM Node The proper Tilt Reference value is calculated by Cisco TransportPlanner and inserted in the Installation Parameter List imported during the node turn-up process (see the “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide). For both OPT-PRE and OPT-BST cards, the provisionable Gain Tilt Reference range is between –3 dB and +3 dB. During the ANS procedure, the Tilt value for the OPT-BST or OPT-PRE card is provisioned by the TCC2/TCC2P/TCC3/TNC/TSC card (see Figure 12-35). The provisioned Tilt Reference Value is reported in the CTC OPT-PRE or OPT-BST card view (in the Provisioning > Opt. Ampli. Line > Parameters > Tilt Reference tab). OPT-BST GOPT-PRE > 21dB Unregulated Tilt SPAN 1= 25 dB SPAN 2= 15 dB OPT-PRE DCU Tilt Reference 0 Provisioned Tilt 134396 =12-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Network-Level Gain—Tilt Management of Optical Amplifiers Figure 12-35 Cisco TransportPlanner Installation Parameters 12.12.2.2 System Gain Tilt Compensation With ROADM Nodes When a ROADM node is present in the network, as shown in Figure 12-36, a per channel dynamic gain equalization can be performed. Both gain tilt and gain ripple are completely compensated using the following techniques: • Implementing the per channel VOAs present inside the 32WSS card • Operating in Power Control Mode with the specific power setpoint designed by Cisco TransportPlanner12-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Optical Data Rate Derivations Figure 12-36 System Tilt Compensation With an ROADM Node 12.13 Optical Data Rate Derivations This section discusses the derivation of several data rates commonly used in optical networking. 12.13.1 OC-192/STM-64 Data Rate (9.95328 Gbps) The SONET OC-1 rate is 51.84 Mbps. This rate results from a standard SONET frame, which consists of 9 rows of 90 columns of 8-bit bytes (810 bytes total). The transmission rate is 8000 frames per second (125 microseconds per frame). This works out to 51.84 Mbps, as follows: (9) x (90 bytes/frame) x (8 bits/byte) x (8000 frames/sec) = 51.84 Mbps OC-192 is 192 x 51.84 Mbps = 9953.28 Mbps = 9.95328 Gbps STM-64 is an SDH rate that is equivalent to the SONET OC-192 data rate. 12.13.2 10GE Data Rate (10.3125 Gbps) 10.3125 Gbps is the standard 10 Gbps Ethernet LAN rate. The reason the rate is higher than 10.000 Gbps is due to the 64-bit to 66-bit data encoding. The result is 10 Gbps x 66/64 = 10.3125 Gbps. The reason for 64-bit to 66-bit encoding is to ensure that there are adequate data transitions to ensure proper operation of a clock and data recovery circuit at the far end. Additionally, the encoding assures a data stream that is DC balanced. 12.13.3 10G FC Data Rate (10.51875 Gbps) The Fibre Channel rate is based on the OC-192 rate of 9.95328 Gbps, with the addition of 64-bit to 66-bit encoding and WAN Interconnect Sublayer (WIS) overhead bytes. SPAN 1= 25 dB DCU 32 WSS SPAN 2 SPAN3 SPAN4 OPT-BST GOPT-PRE > 21dB Unregulated Tilt SPAN 1= 25 dB OPT-PRE Per-channel Tilt Reference = 0 Power Equalization 32 WSS SPAN 2 SPAN3 SPAN4 13439712-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Optical Data Rate Derivations The rate is derived from the basic 9.95328 Gbps OC-192 rate. First, it has the 64-bit to 66-bit encoding added, which brings it to the 10.3125 Gbps rate (10 Gbps x 66/64 = 10.3125 Gbps). Beyond that, the WIS overhead is added, which is an additional two percent on top of the 10.3125 Gbps. This yields: 10.3125 Gbps x .02 = 0.20625 Gbps 10.3125 Gbps + 0.20625 Gbps = 10.51875 Gbps 12.13.4 ITU-T G.709 Optical Data Rates To understand optical networking data rates, an understanding of the ITU-T G.709 frame structure, shown in Figure 12-37, is needed. Figure 12-37 ITU-T G.709 Frame Structure Each of the sub-rows in Figure 12-37 contains 255 bytes. Sixteen are interleaved horizontally (16 x 255 = 4080). This is repeated four times to make up the complete ITU-T G.709 frame. The Reed Solomon (RS) (255,239) designation indicates the forward error correction (FEC) bytes. There are 16 FEC, or parity, bytes. The ITU-T G.709 protocol uses one overhead byte and 238 data bytes to compute 16 parity bytes to form 255 byte blocks—the RS (255,239) algorithm. Interleaving the information provides two key advantages. First, the encoding rate of each stream is reduced relative to the line transmission rate and, second, it reduces the sensitivity to bursts of error. The interleaving combined with the inherent correction strength of the RS (255,239) algorithm enables the correction of transmission bursts of up to 128 consecutive errored bytes. As a result, the ITU-T G.709 contiguous burst error correcting capability is enhanced 16 times above the capacity of the RS(255,239) algorithm by itself. ITU-T G.709 defines the Optical Transport Unit 2 (OTU2) rate as 10.70923 Gbps. ITU-T G.709 defines three line rates: 1. 2,666,057.143 kbps—Optical Transport Unit 1 (OTU1) 159457 Sub Row 3 1 239 240 255 Info Bytes RS (255, 239) Sub Row 2 Info Bytes RS (255, 239) Sub Row 1 Rows: 1 2 3 4 Columns: 1 17 3825 4080 Info Bytes RS (255, 239) Info Bytes Payload FEC12-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Even Band Management 2. 10,709,225.316 kbps—Optical Transport Unit 2 (OTU2) 3. 43,018,413.559 kbps—Optical Transport Unit 3 (OTU3) The OTU2 rate is higher than OC-192 because the OTU2 has to carry overhead and FEC bytes in its frame; the bits must be sent faster to carry the payload information at the OC-192 rate. The ITU-T G.709 frame has two parts. Two are similar to a SDH/SONET frame: 1. Overhead area for operation, administration, and maintenance functions 2. Payload area for customer data In addition, the ITU-T G.709 frame also includes FEC bytes. 12.13.4.1 OC-192 Packaged Into OTU2 G.709 Frame Data Rate (10.70923 Gbps) In this case, an OC-192 frame is being transported over a OTU2 G.709 frame, which adds the benefit of FEC. The OC-192 data rate (9.95328 Gbps) must increase in order to transport more bytes (OC-192 plus ITU-T G.709 overhead plus ITU-T G.709 FEC bytes) in the same amount of time. In an OTU2 transmission, 237 of the 255 bytes are OC-192 payload. This means the resultant data rate is: 9.95328 x 255/237 = 10.70923 Gbps 12.13.4.2 10GE Packaged Into OTU2 G.709 Frame Data Rate (Nonstandard 11.0957 Gbps) Encapsulating Ethernet data into an OTU2 G.709 frame is considered nonstandard. The goal is to add the benefit of ITU-T G.709 encapsulation to achieve better burst error performance. However, this means adding overhead and FEC bytes, so more bytes must be transmitted in the same amount of time, so the data rate must increase. The new date rate is: 10.3215 x 255/237 = 11.0957 Gbps 12.13.4.3 10G FC Packaged Into OTU2 G.709 Frame Data Rate (Nonstandard 11.31764 Gbps) Encapsulating Fibre Channel in an OTU2 frame is considered nonstandard. The rate is higher than the 10.51875 rate because OTU2 includes FEC bytes. The bits must run at a faster rate so that the payload is provided at the standard Fibre Channel rate. The rate is: 10.51875 x 255/237 = 11.31764 Gbps 12.14 Even Band Management With the introduction of the following cards, it is now possible to transport 72, 80, 104, or 112 wavelength channels in the same network: • 40-WSS-CE (40-channel Wavelength Selective Switch, C-band, even channels) • 40-DMX-CE (40-channel Demultiplexer, C-band, even channels) By using these new cards along with the 40-WSS-C and 40-DMX-C cards (which handle 40 C-band odd channels), the 32WSS and 32DMX cards (which handle 32 C-band odd channels), and the 32WSS-L and 32DMX-L (which handle 32 L-band odd channels), it is possible to cover 80 C-band channels (40 even and 40 odd channels) and 32 L-band odd channels, for a maximum of 112 channels. The following channel coverage combinations are possible: • 72 C-band channels, using the 32WSS, 32DMX, 40-WSS-CE, and 40-DMX-CE cards12-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Even Band Management • 80 C-band channels, using the 40-WSS-C, 40-DMX-C, 40-WSS-CE, and 40-DMX-CE cards • 104 channels (32 L-band odd channels and 72 C-band channels), using the 32WSS-L and 32DMX-L cards as a set to cover 32 L-band odd channels and the 32WSS, 32DMX, 40-WSS-CE, and 40-DMX-CE cards as a set to cover 72 C-band odd and even channels • 112 channels (32 L-band odd channels and 80 C-band even channels), using the 32WSS-L and 32DMX-L cards as a set to cover 32 L-band odd channels and the 40-WSS-C, 40-DMX-C, 40-WSS-CE, and 40-DMX-CE, cards as a set to cover 80 C-band odd and even channels The following node topologies are available for even channel management or odd-plus-even channel management: • Terminal node • Hub node • ROADM node • OSC regeneration and optical line amplification node The external ONS 15216-ID-50 module is a 50 GHz/100GHz optical interleaver/deinterleaver that is required to combine or separate odd and even C-band channels. This module increases capacity by combining two optical data streams into a single, more densely spaced stream. The module can be used in multiplexer mode to combine two 100-GHz optical signal streams into one 50-GHz stream, and in demultiplexer mode to separate the 50-GHz stream into two 100-GHz streams. The ONS 15216-SC-CL module is an external C-band and L-band splitter/combiner module that combines and separates the C-band odd/even channels and the L-band odd channels. An example of a 104-channel C-band plus L-band ROADM node is shown in Figure 12-38 on page 12-50. There are 72 C-band even channels and 32 L-band odd channels. The signal flow from the left side of the diagram to the right side is given in the following steps. The signal flow from the right side to the left is identical. 1. All the C-band and L-band signals enter the ONS 15216-SC-CL. 2. When the signals exit the ONS 15216-SC-CL, the 72 C-band even and odd channel signals are sent to the upper set of blocks and the 32 L-band odd channel signals are sent to the lower set of blocks. 3. The 72 C-band even and odd channel signals pass through a preamplifier, then through an ONS 15261-ID-50 and wavelength selective switch (WSS). Only the channels to be dropped are sent to the demultiplexer (DMX) block. There are two such sets of blocks, one set for the 32 odd C-band channels, and one set for the 40 even C-band channels. 4. The 32 L-band odd channel signals pass through a preamplifier, then through two 32-channel wavelength selective switch (32WSS-L) cards. Only the channels to be dropped are sent to the 32-channel demultiplexer (32DMX-L) card. 5. At the upper set of blocks, the ONS 15261-ID-50 deinterleaves the 32 C-band odd channels from the 40 C-band even channels. The 32 C-band odd channels are routed through the top blocks (two 32WSS cards and one 32DMX card), while the 40 C-band even channels are routed through the lower blocks (two 40-WSS-CE cards and one 40-DMX-CE card). 6. When a signal enters a 32WSS-L or 40-WSS-CE card, it is split. Part of the signal (the channels that are to be dropped) goes to the32 DMX-L card or 40-DMX-CE card so that channels can be dropped for use by the client equipment. The other part of the signal goes to the next 32WSS-L card or 40_DMX-CE card, where the channels can be passed through or blocked, and channels can be added to the stream from the client equipment.12-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Even Band Management 7. After the channels leave the last 32WSS-L card or 40-WSS-CE card, the C-band even and odd channels are interleaved back into a single stream by the ONS 15216-ID-50 module, sent through a booster amplifier, and then they enter the ONS 15216-SC-CL module, where they are combined with the L-band signals from the lower set of blocks and sent out onto the optical fiber. Figure 12-38 104-Channel C-Band plus L-Band ROADM Node Interleaver/Deinterleaver (ONS 15216-ID-50) Interleaver/Deinterleaver (ONS 15216-ID-50) C-Band/L-Band Splitter/Combiner (ONS 15216-SC-CL) 40-WSS-CE 40-DMX-CE 1 40 1 40 Add Even Channels Drop Even Channels . . . . . . . . . . . . . . 32WSS 32DMX 1 32 1 32 Add Odd Channels Drop Odd Channels . . . . . . . . . . . . . . 32WSS 32DMX 1 32 . . . . . . . Add Odd Channels 1 32 Drop Odd Channels . . . . . . . 32WSS-L 32DMX-L 1 32 1 32 Add Odd Channels Drop Odd Channels . . . . . . . . . . . . . . 32WSS-L 32DMX-L 1 32 . . . . . . . Add Odd Channels 1 32 Drop Odd Channels . . . . . . . 40-WSS-CE 40-DMX-CE 1 40 . . . . . . . Add Even Channels 1 40 Drop Even Channels . . . . . . . Preamp Preamp Booster Amplifier Preamp Booster Amplifier Booster Amplifier Preamp Booster Amplifier C-Band/L-Band Splitter/Combiner (ONS 15216-SC-CL) C-Band Even and Odd Channels C-Band Even and Odd Channels L-Band Odd Channels L-Band Odd Channels 24063812-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Even Band Management An example of a 112-channel C-band plus L-band ROADM node is shown in Figure 12-39. It operates in a similar manner to the 104-channel ROADM node shown in Figure 12-38 on page 12-50, except that there are 40 odd C-band channels instead of 32. Figure 12-39 112-Channel C-Band plus L-Band ROADM Node Interleaver/Deinterleaver (ONS 15216-ID-50) Interleaver/Deinterleaver (ONS 15216-ID-50) C-Band/L-Band Splitter/Combiner (ONS 15216-SC-CL) 40-WSS-CE 40-DMX-CE 1 40 1 40 Add Even Channels Drop Even Channels . . . . . . . . . . . . . . 40-WSS-C 40-DMX-C 1 32 1 40 Add Odd Channels Drop Odd Channels . . . . . . . . . . . . . . 40-WSS-C 40-DMX-C 1 40 . . . . . . . Add Odd Channels 1 40 Drop Odd Channels . . . . . . . 32WSS-L 32DMX-L 1 32 1 32 Add Odd Channels Drop Odd Channels . . . . . . . . . . . . . . 32WSS-L 32DMX-L 1 32 . . . . . . . Add Odd Channels 1 32 Drop Odd Channels . . . . . . . 40-WSS-CE 40-DMX-CE 1 40 . . . . . . . Add Even Channels 1 40 Drop Even Channels . . . . . . . Preamp Preamp Booster Amplifier Preamp Booster Amplifier Booster Amplifier Preamp Booster Amplifier C-Band/L-Band Splitter/Combiner (ONS 15216-SC-CL) C-Band Even and Odd Channels C-Band Even and Odd Channels L-Band Odd Channels L-Band Odd Channels 24063912-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 12 Network Reference Wavelength Drifted Channel Automatic Shutdown 12.15 Wavelength Drifted Channel Automatic Shutdown The wavelength drifted channel automatic shutdown feature detects wavelength instability or wavelength drift in the Trunk-TX port of the card connected to an MSTP multiplexer. The channel photodiode or optical channel monitor (OCM) associated with a variable optical attenuator (VOA) is used to detect the power fluctuation. The wavelength drifted channel automatic shutdown feature is supported on 40-SMR1-C, 40-SMR2-C, 80-WXC-C, 40-WXC-C, and 40-WSS-C cards. The 40-WSS and 40-WXC cards do not detect the power fluctuation on their ADD ports because the Add Photodiode is located before the filtering stage. The 40-SMR1-C, 40-SMR2-C, and 80-WXC-C cards have the OCM devices installed on the ADD port. The OCM device detects the wavelength sensitive signal so that an alarm is raised on the ADD port at the source node. The power fluctuation is detected on different ports for each card. Table 12-3 lists the ports on which the power fluctuation is detected: The detection mechanism leverages on the repeated crossing of the embedded OPT-PWR-DEG-LOW threshold value associated to the port. When the card exceeds the OPT-PWR-DEG-LOW threshold value 16 times in 24 hours, the WVL-DRIFT-CHAN-OFF alarm is raised. For more information on severity level of the conditions and procedure to clear the alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. Note The automatic shutdown of a channel when the WVL-DRIFT-CHAN-OFF is raised will be implemented in later releases. Table 12-3 Detection of Power Fluctuation Card Port Circuit 40-SMR1-C 40-SMR2-C LINE-TX ADD/DROP EXP/PT 80-WXC-C COM-TX ADD/DROP EXP/PT 40-WXC-C COM-TX ADD/DROP EXP/PT 40-WSS-C CHAN-RX ADD/DROP PT PTCHAPTER 13-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 13 Optical Channel Circuits and Virtual Patchcords Reference This chapter explains the Cisco ONS 15454 dense wavelength division multiplexing (DWDM) optical channel (OCH) circuit types and virtual patchcords that can be provisioned on the ONS 15454. Circuit types include the OCH client connection (OCHCC), the OCH trail, and the OCH network connection (OCHNC). Virtual patchcords include internal patchcords and provisionable (external) patchcords (PPCs). This chapter also describes 13.3 End-to-End SVLAN Circuit that can be created between GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. Note Unless otherwise specified, “ONS 15454" refers to both ANSI and ETSI shelf assemblies. 13.1 Optical Channel Circuits The ONS 15454 DWDM optical circuits provide end-to-end connectivity using three OCH circuit types: • Optical Channel Network Connections (OCHNC) • Optical Channel Client Connections (OCHCC) • Optical Channel Trails (OCH Trails) A graphical representation of OCH circuits is shown in Figure 13-1. Figure 13-1 Optical Channel Circuits R-OADM Transponder Muxponder Transponder R OADM R-OADM Muxponder To client To client R OADM DWDM Network OCH NC OCH Trail OCH CC 33333313-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Optical Channel Circuits 13.1.1 OCHNC Circuits OCHNC circuits establish connectivity between two optical nodes on a specified C-band wavelength. The connection is made through the ports present on the wavelength selective switches, multiplexers, demultiplexer, and add/drop cards. In an OCHNC circuit, the wavelength from a source OCH port ingresses to a DWDM system and then egresses from the DWDM system to the destination OCH port. The source and destination OCH port details are listed in Table 13-1. Note When the 40-SMR1-C or 40-SMR2-C card operates along with the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (ONS 15216 40 or 48-channel mux/demux), the OCH ports on the patch panel are the endpoints of the OCHNC circuit. When the 40-SMR1-C or 40-SMR2-C card operates along with the 40-MUX-C and 40-DMX-C cards, the endpoints of the OCHNC circuit are on the MUX/DMX cards. Table 13-1 OCHNC Ports Card Source Ports Destination Ports 32WSS 32WSS-L 40-WSS-C 40-WSS-CE ADD-RX — 32MUX-O 40-MUX-C CHAN-RX — 32DMX-O 32DMX 32DMX-L 40-DMX-C 40-DMX-CE — CHAN-TX 4MD AD-1C-xx.x AD-4C-xx.x CHAN-RX CHAN-TX 40-SMR1-C 40-SMR2-C ADD-RX DROP-TX 15216-MD-40-ODD 15216-MD-40-EVEN CHAN-RX CHAN-TX 15216-EF-40-ODD 15216-EF-40-EVEN CHAN-RX CHAN-TX 15216-MD-48-ODD 15216-MD-48-EVEN CHAN-RX CHAN-TX13-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Optical Channel Circuits 13.1.2 OCHCC Circuits OCHCC circuits extend the OCHNC to create an optical connection from the source client port to the destination client port of the TXP/MXP cards. An OCHCC circuit represents the actual end-to-end client service passing through the DWDM system. Each OCHCC circuit is associated to a pair of client or trunk ports on the transponder (TXP), muxponder (MXP), GE_XP (in layer-1 DWDM mode), 10GE_XP (in layer-1 DWDM mode), or ITU-T line card. The OCHCCs can manage splitter protection as a single protected circuit. However, for the Y-Cable protection, two OCHCC circuits and two protection groups are required. 13.1.3 OCH Trail Circuits OCH trail circuits transport the OCHCCs. The OCH trail circuit creates an optical connection from the source trunk port to the destination trunk port of the Transponder (TXP), Muxponder (MXP), GE_XP, 10GE_XP, or ITU-T line card. The OCH trail represents the common connection between the two cards, over which all the client OCHCC circuits, SVLAN circuits or STS circuits are carried. Once an OCHCC is created, a corresponding OCH Trail is automatically created. If the OCHCC is created between two TXP, MXP, GE_XP, or 10GE_XP cards, two circuits are created in the CTC. These are: One OCHCC (at client port endpoints) One OCH trail (at trunk port endpoints) If the OCHCC is created between two TXPP or two MXPP cards, three circuits are created in the CTC. These are: • One OCHCC (at client port endpoints) • Two OCH Trails (at trunk port endpoints) One for the working and other for the protect trunk. Note On a TXP, MXP, and GE_XP card (in layer 1 DWDM mode), additional OCHCC circuits are created over the same OCH trail. Note On a TXP, MXP, GE_XP (in layer 1 DWDM mode), and 10GE_XP (in layer 1 DWDM mode) card, the OCH trail cannot be created independently, and is created along with the first OCHCC creation on the card. However, on a GE_XP card (in layer-2 DWDM mode), 10GE_XP card (in layer-2 DWDM mode), and ADM_10G card, an OCH trail can be created between the trunk ports for the upper layer circuits (SVLAN in GE_XP/10GE_XP and STS in ADM_10G). No OCHCC is supported in these cases. If the OCHCC is created between two ITU-T line cards, only one trunk port belongs to the OCHCC at each end of the circuit. Table 13-2 lists the ports that can be OCHCC and OCH trail endpoints.13-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Optical Channel Circuits Figure 13-2 shows the relationships and optical flow between the OCHCC, OCH trail, and OCHNC circuits. Figure 13-2 Optical Channel Management Table 13-2 OCHCC and OCH Trail Ports Card OCHCC OCH Trail TXPs MXPs GE_XP 10GE_XP ADM-10G Any client port Any trunk port ITU-T line cards: • OC48/STM64 EH • OC192 SR/STM64 • MRC-12 • MRC-2.5-12 • MRC-2.5G-4 Any trunk port Any trunk port OCHCC Optical Shelf STS/VT Back Panel OCN Line Card TXP/MXP ITU-T Line Card OCN Port Back Panel Trunk Port Trunk Port Client Port 159473 LINE TX LINE RX OCH RX OCH TX OCHNC OCH Trail Optical Shelf LINE TX LINE RX OCH RX OCH TX 13-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Optical Channel Circuits 13.1.4 Administrative and Service States OCHCCs, OCH trails, and OCHNCs occupy three different optical layers. Each OCH circuit has its own administrative and service states. The OCHCCs impose additional restrictions on changes that can be made to client card port administrative state. The OCHCC service state is the sum of the OCHCC service state and the OCH trail service state. When creating an OCHCC circuit, you can specify an initial state for both the OCHCC and the OCH trail layers, including the source and destination port states. The ANSI/ETSI administrative states for the OCHCC circuits and connections are: • IS/Unlocked • IS,AINS/Unlocked,AutomaticInService • OOS,DSBLD/Locked,disabled OCHCC service states and source and destination port states can be changed independently. You can manually modify client card port states in all traffic conditions. Setting an OCHCC circuit to OOS,DSBLD/Locked,disabled state has no effect on OCHCC client card ports. An OCH trail is created automatically when you create an OCHCC. OCH trails can be created independently between OCH-10G cards and GE_XP and 10GE_XP when they are provisioned in Layer 2 Over DWDM mode. The OCH trail ANSI/ETSI administrative states include: • IS/Unlocked • IS,AINS/Unlocked,automaticInService • OOS,DSBLD/Locked,disabled You can modify OCH trail circuit states from the Edit Circuit window. Placing an OCH trail OOS,DSBLD/Locked,disabled causes the following state changes: • The state of the OCH trail ports changes to OOS,DSBLD/Locked,disabled. • The OCHNC state changes to OOS,DSBLD/Locked,disabled. Changing the OCH trail state to IS,AINS/Unlocked,automaticInService causes the following state changes: • The state of the OCH trail trunk ports changes to IS/Unlocked. • The OCHNC state changes to IS,AINS/Unlocked,automaticInService. The OCH trail service state is the sum of the OCHCC trunk port state and the OCHNC (if applicable) state. Changing the client card trunk ports to OOS,DSBLD/Locked,disabled when the OCH trail state IS/Unlocked will cause the OCH trail state to change to OOS,DSBLD/Locked,disabled and its status to change to Partial. The OCHNC circuit states are not linked to the OCHCC circuit states. The administrative states for the OCHNC circuit layer are: • IS,AINS/Unlocked,AutomaticInService • OOS,DSBLD/Locked,disabled When you create an OCHNC, you can set the target OCHNC circuit state to IS/Unlocked or OOS,DSBLD/Locked,disabled. You can create an OCHNC even if OCHNC source and destination ports are OOS,MT/Locked,maintenance. The OCHNC circuit state will remain OOS-AU,AINS/Unlocked-disabled,automaticInService until the port maintenance state is removed. During maintenance or laser shutdown, the following behavior occurs: 13-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Optical Channel Circuits • If OCHNCs or their end ports move into an AINS/AutomaticInService state because of user maintenance activity on an OCHCC circuit (for example, you change an optical transport section (OTS) port to OOS,DSBLD/Locked,disabled), Cisco Transport Controller (CTC) suppresses the loss of service (LOS) alarms on the TXP, MXP, GE_XP, 10GE_XP, or ITU-T line card trunk ports and raises a Trail Signal Fail condition. Line card trunk port alarms are not changed, however. • If TXP client or trunk port are set to OOS,DSBLD/Locked,disabled state (for example, a laser is turned off) and the OCH trunk and OCH filter ports are located in the same node, the OCH filter LOS alarm is demoted by a Trail Signal Fail condition. OCHCCs are associated with the client card end ports. Therefore, the following port parameters cannot be changed when they carry an OCHCC: • Wavelength • Service (or payload type) • Splitter protection • ITU-T G.709 • Forward error correction (FEC) • Mapping Certain OCHCC parameters, such as service type, service size, and OCHNC wavelength can only be modified by deleting and recreating the OCHCC. If the OCHCC has MXP end ports, you can modify services and parameters on client ports that are not allocated to the OCHCC. Some client port parameters, such as Ethernet frame size and distance extension, are not part of an OCHCC so they can be modified if not restricted by the port state. For addition information about administrative and service states, see Appendix B, “Administrative and Service States.” 13.1.5 Creating and Deleting OCHCCs To create an OCHCC, you must know the client port states and their parameters. If the client port state is IS/Unlocked, OCHCC creation will fail if the OTN line parameters (ITU-T G.709, FEC, signal fail bit error rate (SF BER), and signal degrade bit error rate (SD BER) on the OCHCC differ from what is provisioned on the trunk port. The port state must be changed to OOS-DSLB/Locked,disabled in order to complete the OCHCC. If you delete an OCHCC, you can specify the administrative state to apply to the client card ports. For example, you can have the ports placed in OOS,DSBLD/Locked,disabled state after an OCHCC is deleted. If you delete an OCHCC that originates and terminates on MXP cards, the MXP trunk port states can only be changed if the trunk ports do not carry other OCHCCs. 13.1.6 OCHCCs and Service and Communications Channels Although optical service channels (OSCs), generic communications channels (GCCs), and data communications channels (DCCs) are not managed by OCHCCs, the following restrictions must be considered when creating or deleting OCHCCs on ports with service or communication channels: • Creating an OCHCC when the port has a service or a communications channel is present—OCHCC creation will fail if the OCHCC parameters are incompatible with the GCC/DCC/GCC. For example, you cannot disable ITU-T G.709 on the OCHCC if a GCC carried by the port requires the parameter to be enabled. 13-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Virtual Patchcords • Creating a service or communications channel on ports with OCHCCs—OCHCC creation will fail if the GCC/DCC/GCC parameters are incompatible with the OCHCC. • Deleting an OCHCC on ports with service or communications channels—If an OSC/GCC/DCC is present on a TXP, MXP, GE_XP, 20GE_XP, or ITU-T line card client or trunk port, you cannot set these ports to the OOS,DSBLD/Locked,disabled state after the OCHCC circuit is deleted. 13.2 Virtual Patchcords The TXP, MXP, TXPP, MXPP, GE_XP, 10GE_XP, and ADM-10G client ports and DWDM filter ports can be located in different nodes or in the same single-shelf or multishelf node. ITU-T line card trunk ports and the corresponding DWDM filter ports are usually located in different nodes. OCHCC provisioning requires a virtual patchcord between the client card trunk ports and the DWDM filter ports. Depending on the physical layout, this can be an internal patchcord or a provisionable (external) patchcord (PPC). Both patchcord types are bidirectional. However, each direction is managed as a separate patchcord. Internal patchcords provide virtual links between the two sides of a DWDM shelf, either in single-shelf or multishelf mode. They are viewed and managed in the Provisioning > WDM-ANS > Internal Patchcords tab. When the NE update file is imported in CTC, the Provisioning > WDM-ANS > Internal Patchcord tab is populated with the internal patchcords. When you create an internal patchcord manually, the Internal Patchcord Creation wizard prompts you to choose one of the following internal patchcord types: • Trunk to Trunk (L2)—Creates an internal patchcord between two trunk ports (in NNI mode) of a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card provisioned in the L2-over-DWDM mode. • OCH-Trunk to OCH-Filter—Creates an internal patchcord between the trunk port of a TXP, MXP, GE_XP, 10GE_XP, or ITU-T line card, and an OCH filter card (wavelength selective switch, multiplexer, or demultiplexer). • OCH-Filter to OCH-Filter—Creates an internal patchcord between a MUX input port and a DMX output port. • OTS to OTS—Creates an internal patchcord between two OTS ports. • Optical Path—Creates an internal patchcord between two optical cards, or between an optical card and a passive card. Note If a Side-to-Side PPC is created between nodes, it will no longer function if the node Security Mode mode is enabled (see the “DLP-G264 Enable Node Security Mode” task in the Cisco ONS 15454 DWDM Procedure Guide). When the Secure mode is enabled, it is no longer possible for the DCN extension feature to use the LAN interface to extend the internal network (due to the network isolation in this configuration mode). The result is that the topology discovery on the Side-to-Side PPC no longer operates. Table 13-3 shows the internal patchcord Trunk (L2), OCH trunk, OCH filter, and OTS/OCH ports.13-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Virtual Patchcords Table 13-3 Internal Patchcord Ports Card Trunk (L2) Port OCH Trunk Ports OCH Filter Ports OTS/OCH Ports GE_XP 10GE_XP GE_XPE 10GE_XPE Trunk port in NNI mode Any trunk port — — TXPs MXPs ADM-10G ITU-T line cards — Any trunk port — — OPT-BST OPT-BST-E OPT-BST-L — — — COM-TX COM-RX OSC-TX OSC-RX OPT-AMP-17-C OPT-AMP-L — — — COM-TX COM-RX OSC-TX1 OSC-RX1 DC-TX1 DC-RX1 OPT-PRE — — — COM-TX COM-RX DC-TX DC-RX OSCM OSC-CSM — — — COM-TX COM-RX OSC-TX OSC-RX 32MUX 32MUX-O 40-MUX-C — — Any CHAN RX port COM-TX 32DMX 32DMX-L 32DMX-O 40-DMX-C 40-DMX-CE — — Any CHAN TX port COM-RX13-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Virtual Patchcords 32WSS 32WSS-L 40-WSS-C 40-WSS-CE — — Any ADD port COM-TX COM-RX EXP-TX EXP-RX DROP-TX 40-WXC-C — — — ADD-RX DROP-TX COM TX COM RX 80-WXC-C — — — EAD i, i=1 to 8 AD COM COM-RX DROP-TX EXP-TX MMU — — — EXP A TX EXP A RX 40-SMR2-C — — — ADD-RX DROP-RX EXP-TX EXPi-RX 40-SMR1-C — — — ADD-RX DROP-RX EXP-TX EXP-RX LINE-RX LINE-TX TDC-CC TDC-FC — — — DC-RX DC-TX XT-40G XM-40G — Any trunk port — — PASSIVE-MD-40-ODD PASSIVE-MD-40-EVEN — — Any CHAN TX port COM-RX COM-TX PASSIVE-MD-ID-50 PASSIVE-15216-ID-50 — — — COM-RX COM-TX Table 13-3 Internal Patchcord Ports (continued) Card Trunk (L2) Port OCH Trunk Ports OCH Filter Ports OTS/OCH Ports13-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Virtual Patchcords PPCs are created and managed from the network view Provisioning > Provisionable Patchcord (PPC) tab (Figure 13-3), or from the node view (single-shelf mode) or multiself view (multishelf mode) Provisioning > Comm Channel > PPC tab. Figure 13-3 Network View Provisionable Patchcords Tab PPCs are required when the TXP, MXP, GE_XP, 10GE_XP, ADM-10G, or ITU-T line card is installed in a different node than the OCH filter ports. They can also be used to create OTS-to-OTS links between shelves that do not have OSC connectivity. PPCs are routable and can be used to discover network topologies using Open Shortest Path First (OSPF). GCCs and DCCs are not required for PPC creation. When you create a PPC, the PPC Creation wizard asks you to choose one of the following PPC types: PASSIVE-PP-4-SMR PASSIVE-PP-MESH-4 PASSIVE-PP-MESH-8 — — — EXP-RX EXP-TX PASSIVE_DCU — — — DC-RX DC-TX 1. When provisioned in OPT-PRE mode. Table 13-3 Internal Patchcord Ports (continued) Card Trunk (L2) Port OCH Trunk Ports OCH Filter Ports OTS/OCH Ports13-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Virtual Patchcords • Client/Trunk to Client/Trunk (L2)—Creates a PPC between two client or trunk ports (in NNI mode) on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards provisioned in the L2-over-DWDM mode. • Client/Trunk to Client/Trunk—Creates a PPC between two client or trunk ports on TXP, MXP, GE_XP, 10GE_XP, ADM_10G, or ITU-T line cards. • Side to Side (OTS)—Creates a PPC between two OTS ports that belong to a Side. This option establishes data communications network (DCN) connectivity between nodes that do not have OSCM or OSC-CSM cards installed and therefore do not have OSC connectivity. CTC selects the OTS ports after you choose the origination and termination sides. • OCH Trunk to OCH Filter—Creates a PPC between a OCH trunk port on a TXP, MXP, GE_XP, 10GE_XP, ADM-10G, or ITU-T line card and an OCH filter port on a multiplexer, demultiplexer, or wavelength selective switch card. Table 13-4 shows the PPC Client/Trunk (L2), Client/Trunk, OTS, and OCH Filter ports. Table 13-4 Provisionable Patchcord Ports Card Client/Trunk (L2) Port Client/Trunk Port OTS Port OCH Filter Port GE_XP 10GE_XP GE_XPE 10GE_XPE Client or trunk port in NNI mode Any trunk port — — TXPs MXPs ADM-10G ITU-T line cards — Any trunk port — — OPT-BST OPT-BST-E OPT-BST-L — — COM RX1 LINE RX LINE TX — OPT-AMP-17-C OPT-AMP-L — — COM RX2 COM TX3 LINE RX3 LINE TX3 — OPT-PRE — — COM RX4 COM TX4 — OSC-CSM — — COM RX1 LINE RX LINE TX — 32MUX 32MUX-O 40-MUX-C — — — Any CHAN RX port13-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference Virtual Patchcords 13.2.1 PPC Provisioning Rules For Client/Trunk to Client/Trunk (L2) PPCs, the following provisioning rules and conditions apply: • The card must be provisioned in the L2-over-DWDM mode. • The client or trunk ports must be in the NNI mode. • PPCs can be created only between NNI ports of the same size (1GE-1GE or 10GE-10GE). For Client/Trunk to Client/Trunk PPCs, the following provisioning rules and conditions apply: • Patchcords can be created on preprovisioned or physically installed cards. • Trunk-to-trunk connections require compatible wavelengths if the port is equipped. A check is automatically performed during patchcord provisioning to ensure wavelength compatibility of ports. 32DMX 32DMX-L 32DMX-O 40-DMX-C 40-DMX-CE — — — Any CHAN TX port 32WSS 32WSS-L 40-WSS-C 40-WSS-CE — — — Any ADD port 40-WXC-C — — COM RX COM TX — 80-WXC-C — — EAD i, i=1 to 8 AD COM COM-RX DROP-TX EXP-TX — 40-SMR1-C 40-SMR2-C — — LINE RX LINE TX — MMU — — EXP A RX EXP A TX — 1. Line nodes only. 2. When card mode is OPT-PRE. 3. When card mode is OPT-LINE. 4. Line nodes with two OPT-PRE cards and no BST cards installed. Table 13-4 Provisionable Patchcord Ports (continued) Card Client/Trunk (L2) Port Client/Trunk Port OTS Port OCH Filter Port13-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference End-to-End SVLAN Circuit • For connections involving one or more preprovisioned ports, no compatibility check is performed. For OCH Trunk to OCH Filter PPCs, the following provisioning rules and conditions apply: • GCC and DCC links are not required to create a PPC. • PPCs can be created for preprovisioned or physically installed cards. • OCH trunk and OCH filter ports must be on the same wavelength. CTC checks the ports for wavelength compatibility automatically during PPC provisioning. • For OC-48/STM-16 and OC-192/STM-64 ITU-T line cards, the wavelength compatibility check is performed only when the cards are installed. The check is not performed for preprovisioned cards. • For all other preprovisioned cards, a wavelength compatibility check is not performed if card is set to first tunable wavelength. The wavelength is automatically provisioned on the port, according to the add/drop port that you chose when you created the PPC. 13.3 End-to-End SVLAN Circuit An end-to-end SVLAN circuit can be created between GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards through a wizard in CTC. SVLAN circuits created this way are only a snapshot of the SVLAN settings (NNI and QinQ) of each card in the network. If an end-to-end SVLAN circuit is created via CTC and the SVLAN settings of the cards are changed manually, CTC does not update the SVLAN circuit created with the new settings. To update the SVLAN circuit in CTC, the circuit must be refreshed. However, any changes made to subtended OCH trail circuits are reflected in the SVLAN circuit in CTC. If an OCH trail becomes incomplete and the current SVLAN circuit snapshot has some SVLAN circuits that are using it, they remain incomplete. If the snapshot contains incomplete SVLAN circuits and an OCH trail circuit becomes available, the incomplete SVLAN circuit snapshot in CTC appears to be complete. When the destination port of the SVLAN circuit facing the router is configured as a NNI client port, the outgoing ethernet packets do not drop the SVLAN tag when they exit the MSTP network allowing the router to determine the origin of the ethernet packet. SVLAN circuits are stateless circuits; an administrative or service state need not be set. Note During SVLAN provisioning, if a SVLAN circuit span using UNI ports in transparent mode is over subscribed, a warning message is displayed. However, the circuit is created. This is supported on channel groups on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. 13.3.1 End-to-End SVLAN Provisioning Rules The following provisioning rules and conditions apply to end-to-end SVLAN circuits: • GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards must be provisioned in L2-over-DWDM mode. • SVLAN database must be loaded with the SVLAN. • SVLAN circuits are routed through OCH trail circuits or PPC; Client/Trunk to Client/Trunk (L2). Therefore, before creating an SVLAN circuit, make sure that the subtended OCH trail circuits between GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards or PPC links are created. • For protected SVLAN circuits, create a ring (through OCH trail circuits), define a master node, and enable the protection role.13-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 13 Optical Channel Circuits and Virtual Patchcords Reference End-to-End SVLAN Circuit For information on how to create end-to-end SVLAN circuit, see the “NTP-G203 Create End to End SVLAN Circuits” procedure in the Cisco ONS 15454 DWDM Procedure Guide.CHAPTER 14-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 14 Cisco Transport Controller Operation This chapter describes operations of the Cisco Transport Controller (CTC), the software interface for Cisco ONS 15454, Cisco ONS 15454 M2, and Cisco ONS 15454 M6 shelf assemblies. For CTC setup and login information, refer to the Cisco ONS 15454 DWDM Procedure Guide. Note Unless otherwise specified, ONS 15454, ONS 15454 M2, and ONS 15454 M6 refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 14.1 CTC Software Delivery Methods, page 14-1 • 14.2 CTC Installation Overview, page 14-2 • 14.3 PC and UNIX Workstation Requirements, page 14-3 • 14.4 ONS 15454 Connections, page 14-5 • 14.5 CTC Window, page 14-8 • 14.6 Using the CTC Launcher Application to Manage Multiple ONS Nodes, page 14-19 • 14.7 TCC2/TCC2P/TCC3/TNC/TSC Card Reset, page 14-22 • 14.8 TCC2/TCC2P/TCC3/TNC/TSC Card Database, page 14-23 • 14.9 Software Revert, page 14-23 14.1 CTC Software Delivery Methods ONS 15454, ONS 15454 M2, and ONS 15454 M6 provisioning and administration is performed using the CTC software. CTC is a Java application that resides on the control cards: TCC2/TCC2P/TCC3/TNC/TSC. CTC is downloaded to your workstation the first time you log into 15454-DWDM, 15454-M2, or 15454-M6 shelf assemblies with a new software release using the web interface. You can also log into CTC using the CTC launcher application (StartCTC.exe). Refer to the “14.6 Using the CTC Launcher Application to Manage Multiple ONS Nodes” section on page 14-19 for more information.14-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Installation Overview 14.1.1 CTC Software Installed on the TCC2/TCC2P/TCC3/TNC/TSC Card The CTC software is preloaded on the TCC2/TCC2P/TCC3/TNC/TSC cards; therefore, you do not need to install software on these cards. When a new CTC software version is released, use the release-specific software upgrade document to upgrade the ONS 15454, 15454-M2, or 15454-M6 software on the TCC2/TCC2P/TCC3/TNC/TSC cards. When you upgrade the CTC software, the control cards store the new CTC version as the protect CTC version. When you activate the new CTC software, the control cards store the older CTC version as the protect CTC version, and the newer CTC release becomes the working version. You can view the software versions that are installed on an ONS 15454, 15454-M2, or 15454-M6 shelf assemblies by selecting the Maintenance > Software tabs in node view (single-shelf mode) or multishelf view (multishelf mode). Select the Maintenance > Software tabs in network view to display the software versions installed on all the network nodes. 14.1.2 CTC Software Installed on the PC or UNIX Workstation CTC software is downloaded from the TCC2/TCC2P/TCC3/TNC/TSC cards and installed on your computer automatically after you connect to the ONS 15454, 15454-M2, or 15454-M6 with a new software release for the first time. Downloading the CTC software files automatically ensures that your computer is running the same CTC software version as the TCC2/TCC2P/TCC3/TNC/TSC cards you are accessing. The CTC files are stored in the temporary directory designated by your computer operating system. Click the Delete CTC Cache button to remove files stored in the temporary directory. If the files are deleted, they download the next time you connect to ONS 15454, 15454-M2, or 15454-M6. Downloading the Java archive (JAR) files for CTC takes several minutes depending on the bandwidth of the connection between your workstation and ONS 15454, 15454-M2, or 15454-M6. For example, JAR files downloaded from a modem or a data communications channel (DCC) network link require more time than JAR files downloaded over a LAN connection. During network topology discovery, CTC polls each node in the network to determine which one contains the most recent version of the CTC software. If CTC discovers a node in the network that has a more recent version of the CTC software than the version you are currently running, CTC generates a message stating that a later version of the CTC has been found in the network and offers to install the CTC software upgrade. After the node view appears, you can upgrade CTC by using the Tools > Update CTC menu option. If you have network discovery disabled, CTC will not seek more recent versions of the software. Unreachable nodes are not included in the upgrade discovery. Note Upgrading the CTC software will overwrite your existing software. You must restart CTC after the upgrade is complete. 14.2 CTC Installation Overview To connect to ONS 15454, 15454-M2, or 15454-M6 using CTC, you enter the IP address in the URL field of Microsoft Internet Explorer. After connecting to ONS 15454, 15454-M2, or 15454-M6, the following occurs automatically: 1. A CTC launcher applet is downloaded from the TCC2/TCC2P/TCC3/TNC/TSC card to your computer.14-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation PC and UNIX Workstation Requirements 2. The launcher determines whether your computer has a CTC release matching the release on the TCC2/TCC2P/TCC3/TNC/TSC card. 3. If the computer does not have CTC installed, or if the installed release is older than the TCC2/TCC2P/TCC3/TNC/TSC card’s version, the launcher downloads the CTC program files from the TCC2/TCC2P/TCC3/TNC/TSC card. 4. The launcher starts CTC. The CTC session is separate from the web browser session, so the web browser is no longer needed. Always log into nodes having the latest software release. If you log into an ONS 15454, 15454-M2, or 15454-M6 that is connected with older versions of CTC, or to Cisco ONS 15327s or Cisco ONS 15600s, CTC files are downloaded automatically to enable you to interact with those nodes. The CTC file download occurs only when necessary, such as during your first login. You cannot interact with nodes on the network that have a software version later than the node that you used to launch CTC. Each ONS 15454, 15454-M2, or 15454-M6 can handle up to five concurrent CTC sessions. CTC performance can vary, depending upon the volume of activity in each session, network bandwidth, and TCC2/TCC2P/TCC3/TNC/TSC card load. Note You can also use TL1 commands to communicate with ONS 15454, 15454-M2, or 15454-M6 through VT100 terminals and VT100 emulation software, or you can telnet to ONS 15454, 15454-M2, or 15454-M6 using TL1 ports 2361 and 3083. Refer to the Cisco ONS SONET TL1 Command Guide or Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Command Guide for a comprehensive list of TL1 commands. 14.3 PC and UNIX Workstation Requirements To use CTC for ONS 15454, 15454-M2, or 15454-M6, your computer must have a web browser with the correct Java Runtime Environment (JRE) installed. The correct JRE for each CTC software release is included on the ONS 15454, 15454-M2, or 15454-M6 software CD. If you are running multiple CTC software releases on a network, the JRE installed on the computer must be compatible with the different software releases. When you change the JRE version on the JRE tab, you must exit and restart CTC for the new JRE version to take effect. Table 14-1 shows JRE compatibility with ONS 15454 software releases. Table 14-1 JRE Compatibility ONS Software Release JRE 1.2.2 Compatible JRE 1.3 Compatible JRE 1.4 Compatible JRE 5.0 Compatible JRE 1.6 Compatible ONS 15454 Release 4.5 No Yes No No No ONS 15454 Release 4.6 No Yes Yes No No ONS 15454 Release 4.7 No No Yes No No ONS 15454 Release 5.0 No No Yes No No ONS 15454 Release 6.0 No No Yes No No ONS 15454 Release 7.0 No No Yes Yes No ONS 15454 Release 7.2 No No Yes Yes No ONS 15454 Release 8.0 No No No Yes No ONS 15454 Release 8.5 No No No Yes No14-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation PC and UNIX Workstation Requirements Note To avoid network performance issues, Cisco recommends managing a maximum of 50 nodes concurrently with CTC. The 50 nodes can be on a single DCC or split across multiple DCCs. Cisco does not recommend running multiple CTC sessions when managing two or more large networks. To manage more than 50 nodes, Cisco recommends using Cisco Transport Manager (CTM). If you do use CTC to manage more than 50 nodes, you can improve performance by adjusting the heap size; see the “General Troubleshooting” chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide. You can also create login node groups; see the “Connect the PC and Log Into the GUI” chapter of the Cisco ONS 15454 DWDM Procedure Guide. Table 14-2 lists the requirements for PCs and UNIX workstations. In addition to the JRE, the Java plug-in is also included on the ONS 15454 software CD. ONS 15454 Release 9.0 No No No Yes No ONS 15454 Release 9.1 No No No Yes No ONS 15454 Release 9.2 No No No No Yes Table 14-1 JRE Compatibility (continued) ONS Software Release JRE 1.2.2 Compatible JRE 1.3 Compatible JRE 1.4 Compatible JRE 5.0 Compatible JRE 1.6 Compatible Table 14-2 Computer Requirements for CTC Area Requirements Notes Processor (PC only) Pentium 4 processor or equivalent A faster CPU is recommended if your workstation runs multiple applications or if CTC manages a network with a large number of nodes and circuits. RAM 1 GB RAM or more A minimum of 1 GB is recommended if your workstation runs multiple applications or if CTC manages a network with a large number of nodes and circuits. Hard drive 20 GB hard drive with 250 MB of free space required CTC application files are downloaded from the TCC2/TCC2P/TCC3/TNC/TSC to your computer. These files occupy around 100MB (250MB to be safer) or more space depending on the number of versions in the network.14-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation ONS 15454 Connections 14.4 ONS 15454 Connections You can connect to the ONS 15454, 15454-M2, or 15454-M6 shelf assemblies in multiple ways. Operating System • PC: Windows 2000, Windows XP, Windows Vista, Windows 7, Windows Server 2003, Windows Server 2008 • Workstation: Solaris Version 9 or 10 on an UltraSPARC-III or faster processor, with a minimum of 1 GB RAM and 250 MB of available hard drive space • Apple Mac OS X. CTC needs to be installed using the CacheInstaller available on the CCO or the ONS CD Use the latest Patch/Service Pack released by the OS vendor. Check with the vendor for the information about the latest Patch/Service Pack. Java Runtime Environment JRE 1.6 JRE 1.6 is installed by the CTC Installation Wizard included on the ONS 15454, 15454-M2, or 15454-M6 software CD. JRE 1.6 provides enhancements to the CTC’s performance, especially for large networks with numerous circuits. We recommend that you use JRE 1.6 for networks with Software R9.2 nodes. If CTC must be launched directly from nodes running software R7.0 or R7.2, we recommend JRE 1.4.2 or JRE 5.0. If CTC must be launched directly from nodes running software R5.0 or R6.0, we recommend JRE 1.4.2. If CTC must be launched directly from nodes running software earlier than R5.0, we recommend JRE 1.3.1_02. Web browser • PC: Internet Explorer 6.x, 7.x, 8.x • UNIX Workstation: Mozilla 1.7 • MacOS-X PC: Safari For the PC, use JRE 1.6 with any supported web browser. The supported browser can be downloaded from the Web. Cable User-supplied CAT-5 straight-through cable with RJ-45 connectors on each end to connect the computer to ONS 15454, 15454-M2, or 15454-M6 directly or through a LAN. User-supplied cross-over CAT-5 cable to the DCN port on the ONS 15454 patch panel or to the Catalyst 2950 (multishelf mode). — Table 14-2 Computer Requirements for CTC (continued) Area Requirements Notes14-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation ONS 15454 Connections (ONS 15454) You can connect your PC directly to the ONS 15454 shelf using the RJ-45(LAN) port on the faceplate of TCC2/TCC2P/TCC3 card or using the backplane RJ-45 LAN port. (ONS 15454 M6) You can connect your PC directly to the ONS 15454 M6 shelf using the RJ-45(LAN) port on the faceplate of TNC/TSC card or using the EMS RJ-45 port or using the RJ-45 Craft port. The EMS RJ-45 port and RJ-45 Craft port are present on the external connection unit (ECU). (ONS 15454 M2) You can connect your PC directly to the ONS 15454 M2 shelf using the RJ-45(LAN) port on the faceplate of TNC/TSC card or using the EMS RJ-45 port on the power module. For the ANSI shelf, you can connect using the LAN pins on the backplane (the ETSI shelf provides a LAN connection through the RJ-45 jack on the MIC-T/C/P Front Mount Electrical Connection [FMEC]). Alternatively, you can 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. Table 14-3 lists the connection methods and requirements for ONS 15454, 15454-M2, or 15454-M6 shelves. Note The TNC/TSC card supports multi-shelf connections through three FE RJ45 connections on the ECU. The TNC card supports one GE connection for CRS-1 router through the SFP port on the card. This SFP port can act as a secondary OSC supporting only FE and GE interfaces. The TNC/TSC card in ONS 15454 M6 shelf can connect to CTC through the EMS RJ-45 port or Craft port on the ECU. The TNC/TSC card in ONS 15454 M2 shelf can connect to CTC through the EMS RJ-45 port on the power module.14-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation ONS 15454 Connections Table 14-3 Connection Methods for ONS 15454, ONS 15454 M2, and ONS 15454 M6 Method Description Requirements Local craft Refers to onsite network connections between the CTC computer and the ONS 15454, 15454-M2, or 15454-M6 using one of the following: • The RJ-45 (LAN) port on the TCC2/TCC2P/TCC3/TNC/TSC card • The RJ-45 (LAN) port on the patch panel (multishelf mode) • Port 23 or 24 of the Catalyst 3560-V2-24TS-SD and 2950 (multishelf mode) • The LAN pins on the 15454-DWDM backplane (ANSI) • The RJ-45 jack on the MIC-T/C/P FMEC (ETSI) • (ONS 15454 M6) EMS RJ-45 port on the ECU • (ONS 15454 M6) RJ-45 Craft port on the ECU • (ONS 15454 M2) EMS RJ-45 port on the power module • A hub or switch to which the ONS 15454 is connected If you do not use Dynamic Host Configuration Protocol (DHCP), you must change the computer IP address, subnet mask, and default router, or use automatic host detection. Corporate LAN Refers to a connection to the ONS 15454, 15454-M2, or 15454-M6 through a corporate or network operations center (NOC) LAN. • The ONS 15454, 15454-M2, or 15454-M6 must be provisioned for LAN connectivity, including IP address, subnet mask, and default gateway. • The ONS 15454, 15454-M2, or 15454-M6 must be physically connected to the corporate LAN. • The CTC computer must be connected to the corporate LAN that has connectivity to ONS 15454, 15454-M2, or 15454-M6.14-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window 14.5 CTC Window When you log into a single-shelf ONS 15454, 15454-M2, or 15454-M6, the CTC window appears in node view (Figure 14-1). When you log into a multishelf ONS 15454 or 15454-M6, meaning that two or more ONS 15454 or 15454-M6 shelves are configured to operate as one node, the multishelf view (Figure 14-2) appears in the CTC window. The window includes a menu bar, a toolbar, and a top and bottom pane. The top pane provides status information about the selected objects and a graphic of the current view. The bottom pane provides tabs and subtabs to view ONS 15454 information and perform ONS 15454 provisioning and maintenance tasks. From the CTC window, you can display the other ONS 15454 views. In single-shelf mode, these are the network, node, and card views. In multishelf mode, these are the network, multishelf, shelf, and card views. TL1 Refers to a connection to the ONS 15454, 15454-M2, or 15454-M6 using TL1 rather than CTC. TL1 sessions can be started from CTC, or you can use a TL1 terminal. The physical connection can be a craft connection, corporate LAN, or a TL1 terminal. Refer to the Cisco ONS SONET TL1 Reference Guide or the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Reference Guide. Remote Refers to a connection made to the ONS 15454, 15454-M2, or 15454-M6 using a modem. • A modem must be connected to the ONS 15454, 15454-M2, or 15454-M6. • The modem must be provisioned for the ONS 15454, 15454-M2, or 15454-M6. To run CTC, the modem must be provisioned for Ethernet access. Table 14-3 Connection Methods for ONS 15454, ONS 15454 M2, and ONS 15454 M6 Method Description Requirements14-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window Figure 14-1 Node View (Default Login View for Single-Shelf Mode) 249384 Menu bar Tool bar Status area Graphic area Status bar Sub tabs Tabs Top pane Bottom pane14-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window Figure 14-2 Multishelf View (Default Login View for Multishelf Mode) 14.5.1 Summary Pane The Summary pane on the left has the following fields: • Node Addr—IP address of the node. • Booted—The Booted field indicates one of the following: – Date and time of the node reboot. The node reboot is caused by complete power cycle, software upgrade, or software downgrade. – Date and time of reset of the control cards one after the other. • User—Login user name. • Authority—Security level of users. The possible security levels are Retrieve, Maintanence, Provisioning, and Superuser. • SW Version—CTC software version. • Defaults—Name provided to identify the defaults list.14-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window 14.5.2 Node View (Multishelf Mode), Node View (Single-Shelf Mode), and Shelf View (Multishelf Mode) Node view, shown in Figure 14-1, is the first view that appears after you log into a single-shelf ONS 15454. Multishelf view, shown in Figure 14-2, is the first view that appears after you log into a multishelf ONS 15454. The login node is the first node shown, and it is the “home view” for the session. Multishelf view and node view allow you to manage one ONS 15454 node. The status area shows the node name; IP address; session boot date and time; number of Critical (CR), Major (MJ), and Minor (MN) alarms; name and security level of the current logged-in user; software version; and network element default setup. (On ONS 15454 and 15454-M6) In a multishelf mode, up to 30 shelves operate as a single node. Note The reason for extending the number of subtending shelves to 30 is to accommodate and manage the new optical and DWDM cards that operate in the even band frequency grid. When you open a shelf from multishelf view, shelf view appears, which looks similar to node view but does not contain the tabs and subtabs that are used for node-level operations. 14.5.2.1 CTC Card Colors The graphic area of the CTC window depicts the ONS 15454 shelf assembly. The colors of the cards in the graphic reflect the real-time status of the physical card and slot (Table 14-4). On the ONS 15454 ETSI, the colors of the FMEC cards reflect the real-time status of the physical FMEC cards. Table 14-5 lists the FMEC card colors. The FMEC ports shown in CTC do not change color. Note You cannot preprovision FMECs. Table 14-4 Multishelf View (Multishelf Mode), Node View (Single-Shelf Mode), and Shelf View (Multishelf Mode) Card Colors Card Color Status Gray Slot is not provisioned; no card is installed. Violet Slot is provisioned; no card is installed. White Slot is provisioned; a functioning card is installed. Yellow Slot is provisioned; a Minor alarm condition exists. Orange Slot is provisioned; a Major alarm condition exists. Red Slot is provisioned; a Critical alarm exists.14-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window The wording on a card in node view (single-shelf mode) or shelf view (multishelf mode) shows the status of a card (Active, Standby, Loading, or Not Provisioned). Table 14-6 lists the card statuses. Port color in card view, node view (single-shelf mode), and shelf view (multishelf mode) indicates the port service state. Table 14-7 lists the port colors and their service states. For more information about port service states, see Appendix B, “Administrative and Service States.” Table 14-5 Multishelf View (Multishelf Mode) and Node View (Single-Shelf Mode) FMEC Color Upper Shelf FMEC Color Status White Functioning card is installed. Yellow Minor alarm condition exists. Orange (Amber) Major alarm condition exists. Red Critical alarm exists. Table 14-6 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Card Statuses Card Status Description Act Card is active. Sty Card is in standby mode. Ldg Card is resetting. NP Card is not present. Table 14-7 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Card Port Colors and Service States Port Color Service State Description Cyan (blue) Out-of-Service and Management, Loopback (OOS-MA,LPBK) (ANSI) Locked-enabled,loopback (ETSI) Port is in a loopback state. On the card in node or shelf view, a line between ports indicates that the port is in terminal or facility loopback (see Figure 14-3 and Figure 14-4). Traffic is carried and alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. Cyan (blue) Out-of-Service and Management, Maintenance (OOS-MA,MT) (ANSI) Locked-enabled,maintenance (ETSI) Port is out-of-service for maintenance. Traffic is carried and loopbacks are allowed. Alarm reporting is suppressed. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. Use this service state for testing or to suppress alarms temporarily. Change the state to IS-NR/Unlocked-enabled; OOS-MA,DSBLD/Locked-enabled,disabled; or OOS-AU,AINS/Unlocked-disabled,automaticInService when testing is complete.14-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window Figure 14-3 Terminal Loopback Indicator Figure 14-4 Facility Loopback Indicator 14.5.2.2 Multishelf View Card Shortcuts If you move your mouse over cards in the multishelf view graphic, popups display additional information about the card including the card type; the card status (active or standby); the type of alarm, such as Critical, Major, or Minor (if any); the alarm profile used by the card; and for transponder (TXP) or muxponder (MXP) cards, the wavelength of the dense wavelength division multiplexing (DWDM) port. 14.5.2.3 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Card Shortcuts If you move your mouse over cards in the node view (single-shelf mode) or shelf view (multishelf mode) graphic, popups display additional information about the card including the card type; the card status (active or standby); the type of alarm, such as Critical, Major, or Minor (if any); the alarm profile used by the card; and for TXP or MXP cards, the wavelength of the DWDM port. Right-click a card to reveal a shortcut menu, which you can use to open, reset, delete, or change a card. Right-click a slot to preprovision a card (that is, provision a slot before installing the card). Gray Out-of-Service and Management, Disabled (OOS-MA,DSBLD) (ANSI) Locked-enabled,disabled (ETSI) The port is out-of-service and unable to carry traffic. Loopbacks are not allowed in this service state. Green In-Service and Normal (IS-NR) (ANSI) Unlocked-enabled (ETSI) The port is fully operational and performing as provisioned. The port transmits a signal and displays alarms; loopbacks are not allowed. Violet Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS) (ANSI) Unlocked-disabled,automaticInService (ETSI) The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in this service state for the duration of the soak period. After the soak period ends, the port service state changes to IS-NR/Unlocked-enabled. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. The AINS port will automatically transition to IS-NR/Unlocked-enabled when a signal is received for the length of time provisioned in the soak field. Table 14-7 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Card Port Colors and Service States Port Color Service State Description14-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window 14.5.2.4 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Port Shortcuts If you move your mouse over the ports in the node view (single-shelf mode) or shelf view (multishelf mode), the popup message displays information about the port type, service state, and the alarm profile used by the port. For example, the popup message displays "((EXP-RX-1-4) Service State: IS-NR, Alarm Profile: Inherited)". 14.5.2.5 Card View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Port Shortcuts If you right-click the ports in the card view (single-shelf mode or multishelf mode), the popup message displays the side information along with shelf, slot, and port information. For example, the popup message displays "Shelf 1, Slot 3 (40 SMR2 C), Port EXP-TX 1-1, Side C". 14.5.2.6 Multishelf View Tabs Table 14-8 lists the tabs and subtabs available in the multishelf view. The actions on these tabs apply to the multishelf node and its subtending shelves. 14.5.2.7 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Tabs Table 14-9 lists the tabs and subtabs available in node view (single-shelf mode) or shelf view (multishelf mode). Table 14-8 Multishelf View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the multishelf node and updates them in real time. — Conditions Displays a list of standing conditions on the multishelf node. — History Provides a history of multishelf node alarms including the date, 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. Session, Node Circuits Creates, deletes, edits, and maps circuits. Circuits, Rolls Provisioning Provisions the ONS 15454 multishelf node. General, Network, OSI, Security, SNMP, Comm Channels, Alarm Profiles, Defaults, WDM-ANS Inventory Provides inventory information (part number, serial number, and Common Language Equipment Identification [CLEI] codes) for cards installed on all shelves in the multishelf node. Allows you to delete and reset cards and change the card service state. — Maintenance Performs maintenance tasks for the multishelf node. Database, Network, OSI, Software, Diagnostic, Audit, DWDM14-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window 14.5.3 Network View Network view allows you to view and manage ONS 15454, 15454-M2, or 15454-M6 that have DCC connections to the node that you logged into and any login node groups you have selected (Figure 14-5). Table 14-9 Node View (Single-Shelf Mode) or Shelf View (Multishelf Mode) Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the node or shelf and updates them in real time. — Conditions Displays a list of standing conditions on the node or shelf. — History Provides a history of node or shelf alarms including the date, 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. Session, Node Circuits Creates, deletes, edits, and maps circuits. Circuits, Rolls Provisioning Provisions the ONS 15454 single-shelf or multishelf node. Single-shelf mode: General, Network, OSI, Security, SNMP, Comm Channels, Alarm Profiles, Defaults, WDM-ANS Multishelf mode: General, Protection, Timing, Alarm Profiles Inventory Provides inventory information (part number, serial number, and CLEI codes) for cards installed in the single-shelf or multishelf node. Allows you to delete and reset cards and change the card service state. Note Each card has bootstrap and boot code. After the card is upgraded using the boot code upgrade procedure, the bootstrap version is displayed in the Inventory tab in CTC; However, the boot code version is not displayed in the Inventory tab. — Maintenance Performs maintenance tasks for the single-shelf or multishelf node. Single-shelf mode: Database, Network, OSI, Software, Diagnostic, Audit, DWDM Multishelf mode: Protection, Overhead XConnect, Diagnostic, Timing14-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window Figure 14-5 Network in CTC Network View 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. A Superuser can set up the logical network view feature, which enables each user to see the same network view. 14.5.3.1 Network View Tabs Table 14-10 lists the tabs and subtabs available in network view. 96939 Bold letters indicate login node, asterisk indicates topology host Icon color indicates node status Dots indicate selected node Table 14-10 Network View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the network and updates them in real time. — Conditions Displays a list of standing conditions on the network. — History Provides a history of network alarms including date, type, and severity of each alarm. — Circuits Creates, deletes, edits, filters, and searches for network circuits. —14-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window 14.5.3.2 CTC Node Colors The color of a node in network view, shown in Table 14-11, indicates the node alarm status. 14.5.3.3 DCC Links The lines show DCC connections between the nodes (Table 14-12). DCC connections can be green (active) or gray (fail). The lines can also be solid (circuits can be routed through this link) or dashed (circuits cannot be routed through this link). Circuit provisioning uses active/routable links. Selecting a node or span in the graphic area displays information about the node and span in the status area. 14.5.3.4 Link Consolidation CTC provides the ability to consolidate the DCC, generic communications channel (GCC), optical transmission section (OTS), and PPC links shown in the network view into a more streamlined view. Link consolidation allows you to condense multiple inter-nodal links into a single link. The link Provisioning Provisions security, alarm profiles, bidirectional line switched rings (BLSRs) (ANSI), multiplex section-shared protection rings (MS-SPRing) (ETSI), and overhead circuits. Security, Alarm Profiles, BLSR (ANSI), MS-SPRing (ETSI), Overhead Circuits, Provisionable Patchcords Maintenance Displays the type of equipment and the status of each node in the network; displays working and protect software versions; and allows software to be downloaded. Software Table 14-10 Network View Tabs and Subtabs (continued) Tab Description Subtabs Table 14-11 Node Status Shown in Network View Color Alarm Status Green No alarms Yellow Minor alarms Orange Major alarms Red Critical alarms Gray with Unknown# Node initializing for the first time (CTC displays Unknown# because CTC has not discovered the name of the node yet) Table 14-12 DCC Colors Indicating State in Network View Color and Line Style State Green and solid Active/Routable Green and dashed Active/Nonroutable Gray and solid Failed/Routable Gray and dashed Failed/Nonroutable14-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation CTC Window consolidation sorts links by class, meaning that all DCC links are consolidated together, for example.You can access individual links within consolidated links using the right-click shortcut menu.Each link has an associated icon (Table 14-13). Note Link consolidation is only available on non-detailed maps. Non-detailed maps display nodes in icon form instead of detailed form, meaning that the nodes appear as rectangles with ports on the sides. Refer to the Cisco ONS 15454 DWDM Procedure Guide for more information about consolidated links. 14.5.4 Card View The card view provides information about individual ONS 15454 cards. Use this window to perform card-specific maintenance and provisioning. A graphic showing the ports on the card is shown in the graphic area. The status area displays the node name, slot, number of alarms, card type, equipment type, card status (active or standby), card service state if the card is present, and port service state (described in Table 14-7 on page 14-12). The information that appears and the actions that you can perform depend on the card. For more information about card service states, refer to Appendix B, “Administrative and Service States.” Note CTC provides a card view for all cards except the TCC2/TCC2P/TCC3/TSC cards. Use the card view tabs and subtabs shown in Table 14-14 to provision and manage the ONS 15454. The subtabs, fields, and information shown under each tab depend on the card type selected. Table 14-13 Link Icons Icon Description DCC icon GCC icon OTS icon PPC icon Table 14-14 Card View Tabs and Subtabs Tab Description Subtabs Alarms Lists current alarms (CR, MJ, MN) for the card and updates them in real time. — Conditions Displays a list of standing conditions on the card. —14-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation Using the CTC Launcher Application to Manage Multiple ONS Nodes 14.6 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 9.2 CDs for Cisco ONS products. You can use CTC Launcher to log into multiple ONS nodes that are running CTC Software Release 3.3 or higher, without using a web browser. The CTC launcher application provides an advantage particularly when you have more than one NE version on the network, because it allows you to pick from all available CTC software versions. It also starts more quickly than the browser version of CTC and has a dedicated node history list. History Provides a history of card alarms including date, object, port, and severity of each alarm. Session (displays alarms and events for the current session), Card (displays alarms and events retrieved from a fixed-size log on the card) Circuits Creates, deletes, edits, and search circuits. — Provisioning Provisions an ONS 15454 card. DS-N and OC-N cards: Line, Line Thresholds (different threshold options are available for DS-N and OC-N cards), Elect Path Thresholds, SONET Thresholds, SONET STS, Alarm Profiles TXP and MXP cards: Card, Line, Line Thresholds, Optics Thresholds, OTN, Alarm Profiles DWDM cards (subtabs depend on card type): Optical Line, Optical Chn, Optical Amplifier, Parameters, Optics Thresholds, Alarm Profiles Maintenance Performs maintenance tasks for the card. Loopback, Info, Protection, J1 Path Trace, AINS Soak (options depend on the card type), Automatic Laser Shutdown Performance (Not available for the AIC-I cards) Performs performance monitoring for the card. DS-N and OC-N cards: no subtabs TXP and MXP cards: Optics PM, Payload PM, OTN PM DWDM cards (subtabs depend on card type): Optical Line, Optical Chn, Optical Amplifier Line, OC3 Line, Parameters, Optics Thresholds Inventory (40-WSS, 40-WXC, OPT-PRE and OPT-BST cards) Displays an Inventory screen of the ports. — Table 14-14 Card View Tabs and Subtabs (continued) Tab Description Subtabs14-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation Using the CTC Launcher Application to Manage Multiple ONS Nodes CTC Launcher provides two connection options. The first option is used to connect to ONS NEs that have an IP connection to the CTC computer. The second option is used to connect to ONS NEs that reside behind third party, OSI-based GNEs. For this option, CTC Launcher creates a TL1 tunnel to transport the TCP traffic through the OSI-based GNE. The TL1 tunnel transports the TCP traffic to and from ONS ENEs through the OSI-based GNE. TL1 tunnels are similar to the existing static IP-over-CLNS tunnels, GRE, and Cisco IP, that can be created at ONS NEs using CTC. (Refer to the Cisco ONS product documentation for information about static IP-over-CLNS tunnels.) However, unlike the static IP-over-CLNS tunnels, TL1 tunnels require no provisioning at the ONS ENE, the third-party GNE, or DCN routers. All provisioning occurs at the CTC computer when the CTC Launcher is started. Figure 14-6 shows examples of two static IP-over-CLNS tunnels. A static Cisco IP tunnel is created from ENE 1 through other vendor GNE 1 to a DCN router, and a static GRE tunnel is created from ONS ENE 2 to the other vender, GNE 2. For both static tunnels, provisioning is required on the ONS ENEs. In addition, a Cisco IP tunnel must be provisioned on the DCN router and a GRE tunnel provisioned on GNE 2. Figure 14-6 Static IP-Over-CLNS Tunnels Figure 14-7 shows the same network using TL1 tunnels. Tunnel provisioning occurs at the CTC computer when the tunnel is created with the CTC Launcher. No provisioning is needed at ONS NEs, GNEs, or routers. Other vendor GNE 1 Other vendor GNE 2 Central office IP+ OSI IP-over-CLNS tunnel IP-over-CLNS tunnel IP OSI/DCC OSI/DCC IP/DCC IP/DCC 140174 IP DCN CTC Tunnel provisioning Tunnel provisioning ONS ENE 1 ONS ENE 2 Tunnel provisioning Tunnel provisioning14-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation Using the CTC Launcher Application to Manage Multiple ONS Nodes Figure 14-7 TL1 Tunnels 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. Because they use TL1 for TCP transport, they are more secure. TL1 tunnels also provide better flow control. On the other hand, IP over CLNS tunnels require less overhead and usually provide a slight performance edge over TL1 Tunnels (depending on network conditions). TL1 tunnels do not support all IP applications such as SNMP and RADIUS Authentication. Table 14-15 shows a comparison between the two types of tunnels. Other vendor GNE 1 Other vendor GNE 2 Central office IP + OSI TL1 tunnel IP OSI/DCC OSI/DCC IP/DCC IP/DCC Tunnel provisioning 140175 IP DCN CTC ONS ENE 1 ONS ENE 2 TL1 tunnel Table 14-15 TL1 and Static IP-Over-CLNS Tunnels Comparison Category Static IP-Over-CLNS TL1 Tunnel Comments Setup Complex Simple Requires provisioning at ONS NE, GNE, and DCN routers. For TL1 tunnels, provisioning is needed at CTC computer. Performance Best Average to good Static tunnels generally provide better performance than TL1 tunnels, depending on TL1 encoding used. LV+Binary provides the best performance. Other encoding will produce slightly slower TL1 tunnel performance. Support all IP applications Yes No TL1 tunnels do not support SNMP or RADIUS Server IP applications. ITU Standard Yes No Only the static IP-over-CLNS tunnels meet ITU standards. TL1 tunnels are new. Tunnel traffic control Good Very good Both tunnel types provide good traffic control Security setup Complex No setup needed Static IP-over-CLNS tunnels require careful planning. Because TL1 tunnels are carried by TL1, no security provisioning is needed.14-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation TCC2/TCC2P/TCC3/TNC/TSC Card Reset TL1 tunnel specifications and general capabilities include: • Each tunnel generally supports between six to eight ENEs, depending on the number of tunnels at the ENE. • Each CTC session can support up to 32 tunnels. • The TL1 tunnel database is stored locally in the CTC Preferences file. • Automatic tunnel reconnection when the tunnel goes down. • Each ONS NE can support at least 16 concurrent tunnels. 14.7 TCC2/TCC2P/TCC3/TNC/TSC Card Reset You can soft reset the TCC2/TCC2P/TCC3/TNC/TSC card by using CTC or by physically resetting the card (a hard reset). A soft reset reboots the TCC2/TCC2P/TCC3/TNC/TSC card and reloads the operating system and the application software. Additionally, a hard reset temporarily removes power from the TCC2/TCC2P/TCC3/TNC/TSC card and clears all the buffer memory. You can apply a soft reset from CTC to either an active or standby TCC2/TCC2P/TCC3/TNC/TSC card without affecting traffic. If you need to perform a hard reset on an active TCC2/TCC2P/TCC3/TNC/TSC card, put the TCC2/TCC2P/TCC3/TNC/TSC card into standby mode first by performing a soft reset. Note Hard reset can also be performed on the TNC/TSC card through CTC and TL1 interface. Before performing the hard reset, bring the TNC/TSC card to maintenance mode. When you reset the standby TCC2/TCC2P/TCC3/TNC/TSC card, the system traffic is not affected. When you reset the active TCC2/TCC2P/TCC3/TNC/TSC card, traffic switches to the standby card if the standby card is present and in the ready standby state. If the standby card is not in the ready standby state, traffic does not switch, and results in loss of system traffic and management connectivity until the card reboots completely. Potential to breach DCN from DCC using IP. Possible Not possible A potential exists to breach a DCN from a DCC using IP. This potential does not exist for TL1 tunnels. IP route management Expensive Automatic For static IP-over-CLNS tunnels, route changes require manual provisioning at network routers, GNEs, and ENEs. For TL1 tunnels, route changes are automatic. Flow control Weak Strong TL1 tunnels provide the best flow control. Bandwidth sharing among multiple applications Weak Best — Tunnel lifecycle Fixed CTC session TL1 tunnels are terminated when the CTC session ends. Static IP-over-CLNS tunnels exist until they are deleted in CTC. Table 14-15 TL1 and Static IP-Over-CLNS Tunnels Comparison (continued) Category Static IP-Over-CLNS TL1 Tunnel Comments14-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation TCC2/TCC2P/TCC3/TNC/TSC Card Database Caution When you reset the TNC/TSC card on the ONS 15454 or 15454-M6 shelves in simplex control mode, loss of management connectivity happens until the card reboots. The system traffic loss may occur depending on the line card and traffic type. Note (Cisco ONS 15454 shelf) When a CTC reset is performed on an active TCC2/TCC2P/TCC3 card, the AIC-I card goes through an initialization process and also resets because it is controlled by the active TCC2/TCC2P/TCC3 card. 14.8 TCC2/TCC2P/TCC3/TNC/TSC Card Database When dual TCC2/TCC2P/TCC3/TNC/TSC cards are installed in the ONS 15454, 15454-M2, or 15454-M6 shelves, each TCC2/TCC2P/TCC3/TNC/TSC card hosts a separate database; therefore, the protect card database is available if the database on the working TCC2/TCC2P/TCC3/TNC/TSC card fails. You can also store a backup version of the database on the workstation running CTC. This operation should be part of a regular ONS 15454, 15454-M2, or 15454-M6 maintenance program at approximately weekly intervals, and should also be completed when preparing ONS 15454, 15454-M2, or 15454-M6 for a pending natural disaster, such as a flood or fire. The TNC card provides 4GB of nonvolatile database storage for communication, provisioning, and system control. This allows full database recovery during power failure. The configuration details are stored in the database of the TCC2/TCC2P/TCC3/TNC/TSC card. The database restore from a TNC card to a TSC card or vice versa is not supported. Note The following parameters are not backed up and restored: node name, IP address, mask and gateway, and Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up database with a different node name, the circuits map to the new node name. We recommend keeping a record of the old and new node names. 14.9 Software Revert When you click the Activate button after a software upgrade, the TCC2/TCC2P/TCC3/TNC/TSC card copies the current working database and saves it in a reserved location in the TCC2/TCC2P/TCC3/TNC/TSC card flash memory. If later during the upgrade you need to revert to the original working software load from the protect software load, the saved database installs automatically. You do not need to restore the database manually or recreate circuits. The revert feature is useful if the maintenance window in which you were performing an upgrade closes while you are still upgrading CTC software. You can revert to the protect software load without losing traffic. During the next maintenance window, you can complete the upgrade and activate the new software load. Circuits created or provisioning done after you activate a new software load (upgrade to a higher release) will be lost with a revert. The database configuration at the time of activation is reinstated after a revert. (This does not apply to maintenance reverts, such as Software R5.0.1 to Software R5.0.2, because maintenance releases retain the database during activation.) 14-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 14 Cisco Transport Controller Operation Software Revert Caution Cisco does not recommend reverting after changing provisioning on the node. Depending upon the particular provisioning, reverting in this case can be traffic affecting. To perform a supported (non-service-affecting) revert from a software release that you have just activated, the release you revert to must have been working at the time you first activated the new software on that node. Because a supported revert automatically restores the node configuration at the time of the previous activation, any configuration changes made after activation will be lost when you revert the software. Downloading the software release that you are upgrading to a second time after you have activated the new load ensures that no actual revert to a previous load can take place (the TCC2/TCC2P/TCC3/TNC/TSC resets, but it does not affect the traffic and does not change your database). Note To perform a supported software upgrade or revert, you must consult the specific upgrade document and release notes for the release you are upgrading to (or reverting from).CHAPTER 15-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 15 Security Reference This chapter provides information about Cisco ONS 15454 users and security. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 15.1 User IDs and Security Levels, page 15-1 • 15.2 User Privileges and Policies, page 15-2 • 15.3 Audit Trail, page 15-8 • 15.4 RADIUS Security, page 15-9 15.1 User IDs and Security Levels The Cisco Transport Controller (CTC) ID is provided with the ONS 15454 system, but the system does not display the user ID when you sign into CTC. This ID can be used to set up other ONS 15454 users. You can have up to 500 user IDs on one ONS 15454. Each CTC or TL1 user can be assigned one of the following security levels: • Retrieve—Users can retrieve and view CTC information but cannot set or modify parameters. • Maintenance—Users can access only the ONS 15454 maintenance options. • Provisioning—Users can access provisioning and maintenance options. • Superusers—Users can perform all of the functions of the other security levels as well as set names, passwords, and security levels for other users. See Table 15-3 on page 15-7 for idle user timeout information for each security level. By default, multiple concurrent user ID sessions are permitted on the node, that is, multiple users can log into a node using the same user ID. However, you can provision the node to allow only a single login per user and prevent concurrent logins for all users. Note You must add the same user name and password to each node the user accesses.15-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference User Privileges and Policies Note Maintenance, Provisioning, and Superusers must be properly trained on the hazards of laser safety and be aware of safety-related instructions, labels, and warnings. Refer to the Cisco Optical Products Safety and Compliance Information document for a current list of safety labels and warnings, including laser warnings. Refer to IEC 60825-2 for international laser safety standards, or to ANSI Z136.1 for U.S. laser safety standards. The Cisco ONS 15454 DWDM Procedure Guide explains how users can disable laser safety during maintenance or installation; when following these procedures, adhere to all posted warnings and cautions to avoid unsafe conditions or abnormal exposure to optical radiation. 15.2 User Privileges and Policies This section lists user privileges for each CTC task and describes the security policies available to Superusers for provisioning. 15.2.1 User Privileges by CTC Task Table 15-1 shows the actions that each user privilege level can perform in node view. Table 15-1 ONS 15454 Security Levels—Node View CTC Tab Subtab [Subtab]:Actions Retrieve Maintenance Provisioning Superuser Alarms — Synchronize/Filter/Delete Cleared Alarms XX X X Conditions — Retrieve/Filter X X X X History Session Filter X X X X Node Retrieve/Filter X X X X Circuits Circuits Create/Edit/Delete — — X X Filter/Search X X X X Rolls Complete/ Force Valid Signal/ Finish —— X X15-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference User Privileges and Policies Provisioning General General: Edit — — Partial1 X Multishelf Config: Edit — — — X Network General: Edit — — — X Static Routing: Create/Edit/ Delete —— X X OSPF: Create/Edit/Delete — — X X RIP: Create/Edit/Delete — — X X Proxy: Create/Edit/Delete — — — X Firewall: Create/Edit/Delete — — — X OSI Main Setup:Edit — — — X TARP: Config: Edit — — — X TARP: Static TDC: Add/Edit/Delete —— X X TARP: MAT: Add/Edit/Remove — — X X Routers: Setup: Edit — — — X Routers: Subnets: Edit/Enable/Disable —— X X Tunnels: Create/Edit/Delete — — X X Table 15-1 ONS 15454 Security Levels—Node View (continued) CTC Tab Subtab [Subtab]:Actions Retrieve Maintenance Provisioning Superuser15-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference User Privileges and Policies Security Users: Create/Delete/Clear Security Intrusion Alarm —— — X Users: Change Same user Same user Same user All users Active Logins: View/Logout/ Retrieve Last Activity Time —— — X Policy: Edit/View — — — X Access: Edit/View — — — X RADIUS Server: Create/Edit/Delete/Move Up/M ove Down/View —— — X Legal Disclaimer: Edit — — — X SNMP Create/Edit/Delete — — X X Browse trap destinations X X X X Comm Channels SDCC: Create/Edit/Delete — — X X LDCC: Create/Edit/Delete — — X X GCC: Create/Edit/Delete — — X X OSC: Create/Edit/Delete — — X X PPC: Create/Edit/Delete — — X X LMP: General: Edit X X X X LMP: Control Channels: Create/Edit/Delete —— — X LMP: TE Links: Create/Edit/Delete —— — X LMP: Data Links: Create/Edit/Delete —— — X Alarm Profiles Load/Store/Delete2 —— X X New/Compare/Available/Usage X X X X Defaults Edit/Import — — — X Reset/Export X X X X WDM-ANS Provisioning: Edit — — — X Provisioning: Reset X X X X Internal Patchcords: Create/Edit/Delete/Commit/ Default Patchcords —— X X Port Status: Launch ANS — — — X Node Setup: Setup/Edit X X X X Optical Side: Create/Edit/Delete X X X X Inventory — Delete — — X X Reset — X X X Table 15-1 ONS 15454 Security Levels—Node View (continued) CTC Tab Subtab [Subtab]:Actions Retrieve Maintenance Provisioning Superuser15-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference User Privileges and Policies Table 15-2 shows the actions that each user privilege level can perform in network view. Maintenance Database Backup — X X X Restore — — — X Network Routing Table: Retrieve X X X X RIP Routing Table: Retrieve X X X X OSI IS-IS RIB: Refresh X X X X ES-IS RIB: Refresh X X X X TDC: TID to NSAP/Flush Dynamic Entries —X X X TDC: Refresh X X X X Software Download/Cancel — X X X Activate/Revert — — — X Diagnostic Node Diagnostic Logs — — X X Audit Retrieve — — — X Archive — — X X DWDM APC: Run/Disable/Refresh — X X X WDM Span Check: Retrieve Span Loss values/ Edit/Reset XX X X ROADM Power Monitoring: Refresh XX X X PP-MESH Internal Patchcord: Refresh XX X X Install Without Metro Planner: Retrieve Installation values XX X X All Facilities: Mark/Refresh X X X X 1. A Provisioning user cannot change node name, contact, location and AIS-V insertion on STS-1 signal degrade (SD) parameters. 2. The action buttons in the subtab are active for all users, but the actions can be completely performed only by the users assigned with the required security levels. Table 15-1 ONS 15454 Security Levels—Node View (continued) CTC Tab Subtab [Subtab]:Actions Retrieve Maintenance Provisioning Superuser Table 15-2 ONS 15454 Security Levels—Network View CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser Alarms — Synchronize/Filter/Delete cleared alarms XX X X Conditions — Retrieve/Filter X X X X History — Filter X X X X15-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference User Privileges and Policies 15.2.2 Security Policies Superusers can provision security policies on the ONS 15454. These security policies include idle user timeouts, password changes, password aging, and user lockout parameters. In addition, Superusers can access the ONS 15454 through the TCC2/TCC2P/TCC3 RJ-45 port, the backplane LAN connection, or both. Circuits Circuits Create/Edit/Delete — — X X Filter/Search X X X X Rolls Complete/ Force Valid Signal/ Finish —— X X Provisioning Security Users: Create/Delete/Clear Security Intrusion Alarm —— — X Users: Change Same User Same User Same User All Users Active logins: Logout/Retrieve Last Activity Time —— — X Policy: Change — — — X Alarm Profiles New/Load/Store/Delete1 —— X X Compare/Available/Usage X X X X BLSR (ANSI) MS-SPRing (ETSI) Create/Edit/Delete/Upgrade — — X X Overhead Circuits Create/Delete/Edit/Merge — — X X Search X X X X Provisionable Patchcords (PPC) Create/Edit/Delete — — X X Server Trails Create/Edit/Delete — — X X VLAN DB Profile Load/Store/Merge/Circuits X X X X Add/Remove Rows — — X X Maintenance Software Download/Cancel — X X X Diagnostic OSPF Node Information: Retrieve/Clear XX X X APC Run APC/Disable APC — — — X Refresh X X X X 1. The action buttons in the subtab are active for all users, but the actions can be completely performed only by the users assigned with the required security levels. Table 15-2 ONS 15454 Security Levels—Network View (continued) CTC Tab Subtab [Subtab]: Actions Retrieve Maintenance Provisioning Superuser15-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference User Privileges and Policies 15.2.2.1 Superuser Privileges for Provisioning Users Superusers can grant permission to Provisioning users to perform a set of tasks. The tasks include retrieving audit logs, restoring databases, clearing PMs, and activating and reverting software loads. These privileges can be set only through CTC network element (NE) defaults, except the PM clearing privilege, which can be granted to Provisioning users using CTC Provisioning> Security > Access tabs. For more information on setting up Superuser privileges, refer to the Cisco ONS 15454 DWDM Procedure Guide. 15.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 15-3. 15.2.2.3 User Password, Login, and Access Policies Superusers can view real-time lists of users who are logged into CTC or TL1 user logins by node. Superusers can also provision the following password, login, and node access policies: • Password length, expiration and reuse—Superusers can configure the password length by using NE defaults. The password length, by default, is set to a minimum of six and a maximum of 20 characters. You can configure the default values in CTC node view with the Provisioning > NE Defaults > Node > security > password Complexity tabs. The minimum length can be set to eight, ten or twelve characters, and the maximum length to 80 characters. The password must be a combination of alphanumeric (a-z, A-Z, 0-9) and special (+, #,%) characters, where at least two characters are nonalphabetic and at least one character is a special character. Superusers can specify when users must change their passwords and when they can reuse them. • Locking out and disabling users—Superusers can provision the number of invalid logins that are allowed before locking out users and the length of time before inactive users are disabled. The number of allowed lockout attempts is set to the number of allowed login attempts. • Node access and user sessions—Superusers can limit the number of CTC sessions one user can have, and they can prohibit access to the ONS 15454 using the LAN or TCC2/TCC2P/TCC3 RJ-45 connections. In addition, a Superuser can select secure shell (SSH) instead of Telnet at the CTC Provisioning > Security > Access tabs. SSH is a terminal-remote host Internet protocol that uses encrypted links. It provides authentication and secure communication over unsecure channels. Port 22 is the default port and cannot be changed. Table 15-3 ONS 15454 Default User Idle Times Security Level Idle Time Superuser 15 minutes Provisioning 30 minutes Maintenance 60 minutes Retrieve Unlimited15-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference Audit Trail 15.3 Audit Trail The Cisco ONS 15454 maintains a Telcordia GR-839-CORE-compliant audit trail log that resides on the TCC2/TCC2P/TCC3/TNC/TSC card. Audit trails are useful for maintaining security, recovering lost transactions and enforcing accountability. Accountability refers to tracing user activities; that is, associating a process or action with a specific user. This record shows who has accessed the system and what operations were performed during a given period of time. The log includes authorized Cisco logins and logouts using the operating system command line interface, CTC, and TL1; the log also includes FTP actions, circuit creation/deletion, and user/system generated actions. Event monitoring is also recorded in the audit log. An event is defined as the change in status of an element within the network. External events, internal events, attribute changes, and software upload/download activities are recorded in the audit trail. The audit trail is stored in persistent memory and is not corrupted by processor switches, resets or upgrades. However, if a user pulls both TCC2/TCC2P/TCC3/TNC/TSC cards, the audit trail log is lost. 15.3.1 Audit Trail Log Entries Table 15-4 contains the columns listed in Audit Trail window. Audit trail records capture the following activities: • User—Name of the user performing the action • Host—Host from where the activity is logged • Device ID—IP address of the device involved in the activity • Application—Name of the application involved in the activity • Task—Name of the task involved in the activity (view a dialog box, apply configuration, and so on) • Connection Mode—Telnet, Console, Simple Network Management Protocol (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—Denotes whether the event is Success/Failure type • Message Details—Description of the change Table 15-4 Audit Trail Window Columns Heading Explanation Date Date when the action occurred Num Incrementing count of actions User User ID that initiated the action P/F Pass/Fail (whether or not the action was executed) Operation Action that was taken15-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference RADIUS Security 15.3.2 Audit Trail Capacities The system is able to store 640 log entries.When this limit is reached, the oldest entries are overwritten with new events. When the log server is 80 percent full, an AUD-LOG-LOW condition is raised and logged (by way of Common Object Request Broker Architecture [CORBA]/CTC). When the log server reaches a maximum capacity of 640 entries and begins overwriting records that were not archived, an AUD-LOG-LOSS condition is raised and logged. This event indicates that audit trail records have been lost. Until the user off-loads the file, this event occurs only once regardless of the amount of entries that are overwritten by the system. 15.4 RADIUS Security Superusers can configure nodes to use Remote Authentication Dial In User Service (RADIUS) authentication. RADIUS uses a strategy known as authentication, authorization, and accounting (AAA) for verifying the identity of, granting access to, and tracking the actions of remote users. To configure RADIUS authentication, refer to the Cisco ONS 15454 DWDM Procedure Guide. RADIUS server supports IPv6 addresses and can process authentication requests from a GNE or an ENE that uses IPv6 addresses. 15.4.1 RADIUS Authentication RADIUS is a system of distributed security that secures remote access to networks and network services against unauthorized access. RADIUS comprises three components: • A protocol with a frame format that utilizes User Datagram Protocol (UDP)/IP • A server • A client The server runs on a central computer typically at the customer's site, while the clients reside in the dial-up access servers and can be distributed throughout the network. An ONS 15454 node operates as a client of RADIUS. The client is responsible for passing user information to designated RADIUS servers, and then acting on the response that is returned. RADIUS servers are responsible for receiving user connection requests, authenticating the user, and returning all configuration information necessary for the client to deliver service to the user. The RADIUS servers can act as proxy clients to other kinds of authentication servers. Transactions between the client and RADIUS server are authenticated through the use of a shared secret, which is never sent over the network. In addition, any user passwords are sent encrypted between the client and RADIUS server. This eliminates the possibility that someone snooping on an unsecured network could determine a user's password. 15.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 server15-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 15 Security Reference RADIUS Security 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 than the shared secret used between the RADIUS proxy and the RADIUS server. Shared secrets are used to verify that RADIUS messages, with the exception of the Access-Request message, are sent by a RADIUS-enabled device that is configured with the same shared secret. Shared secrets also verify that the RADIUS message has not been modified in transit (message integrity). The shared secret is also used to encrypt some RADIUS attributes, such as User-Password and Tunnel-Password. When creating and using a shared secret: • Use the same case-sensitive shared secret on both RADIUS devices. • Use a different shared secret for each RADIUS server-RADIUS client pair. • To ensure a random shared secret, generate a random sequence at least 22 characters long. • You can use any standard alphanumeric and special characters. • You can use a shared secret of up to 128 characters in length. To protect your server and your RADIUS clients from brute force attacks, use long shared secrets (more than 22 characters). • Make the shared secret a random sequence of letters, numbers, and punctuation and change it often to protect your server and your RADIUS clients from dictionary attacks. Shared secrets should contain characters from each of the three groups listed in Table 15-5. The stronger your shared secret, the more secure the attributes (for example, those used for passwords and encryption keys) that are encrypted with it. An example of a strong shared secret is 8d#>9fq4bV)H7%a3-zE13sW$hIa32M#m Timing > Report tab show current timing information for an ONS 15454, including the timing mode, clock state and status, switch type, and reference data. Caution 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. The OC3 port of the TNC/TSC card can be set as the timing reference. In the ONS 15454 M2 shelf, BITS-2 is not supported. 16.2 Network Timing Figure 16-1 shows an ONS 15454 network timing setup example. Node 1 is set to external timing. Two timing references are set to BITS. These are Stratum 1 timing sources wired to the BITS input pins on the Node 1 backplane. The third reference is set to internal clock. The BITS output pins on the backplane of Node 3 are used to provide timing to outside equipment, such as a digital access line access multiplexer. In the example, Slots 5 and 6 contain the trunk (span) cards. Timing at Nodes 2, 3, and 4 is set to line, and the timing references are set to the trunk cards based on distance from the BITS source. Reference 1 is set to the trunk card closest to the BITS source. At Node 2, Reference 1 is set to Slot 5 because it is connected to Node 1. At Node 4, Reference 1 is set to Slot 6 because it is connected to Node 1. At Node 3, Reference 1 could be either trunk card because they are at an equal distance from Node 1. 16-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 16 Timing Reference Synchronization Status Messaging Figure 16-1 ONS 15454 Timing Example 16.3 Synchronization Status Messaging Synchronization status messaging (SSM) is a SDH and SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET Line layer or on S1 byte of the SDH section overhead. They enable SONET or SDH devices to automatically select the highest quality timing reference and to avoid timing loops. 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 SSM for the ONS 15454 or the ONS 15454 SDH, consult your timing reference documentation to determine which message set to use. Table 16-1 shows the SDH message set. Node 4 Timing Line Ref 1: Slot 6 Ref 2: Slot 5 Ref 3: Internal (ST3) Node 2 Timing Line Ref 1: Slot 5 Ref 2: Slot 6 Ref 3: Internal (ST3) Node 1 Timing External Ref 1: BITS1 Ref 2: BITS2 Ref 3: Internal (ST3) Node 3 Timing Line Ref 1: Slot 5 Ref 2: Slot 6 Ref 3: Internal (ST3) BITS1 out BITS2 out BITS1 source BITS2 source Third party equipment 34726 Slot 5 Slot 5 Slot 5 Slot 5 Slot 6 Slot 6 Slot 6 Slot 616-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 16 Timing Reference Synchronization Status Messaging Table 16-2 and Table 16-3 on page 16-4 show the Generation 1 and Generation 2 message sets for SONET. Table 16-1 SDH SSM Message Set Message Quality Description G811 1 Primary reference clock STU 2 Sync traceability unknown G812T 3 Transit node clock traceable G812L 4 Local node clock traceable SETS 5 Synchronous equipment DUS 6 Do not use for timing synchronization Table 16-2 SSM Generation 1 Message Set Message Quality Description PRS 1 Primary reference source—Stratum 1 STU 2 Synchronization traceability unknown ST2 3 Stratum 2 ST3 4 Stratum 3 SMC 5 SONET minimum clock ST4 6 Stratum 4 DUS 7 Do not use for timing synchronization RES — Reserved; quality level set by user Table 16-3 SSM Generation 2 Message Set Message Quality Description PRS 1 Primary reference source—Stratum 1 STU 2 Synchronization traceability unknown ST2 3 Stratum 2 TNC 4 Transit node clock ST3E 5 Stratum 3E ST3 6 Stratum 3 SMC 7 SONET minimum clock ST4 8 Stratum 4 DUS 9 Do not use for timing synchronization RES — Reserved; quality level set by userCHAPTER 17-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 17 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. The chapter shows common Cisco ONS 15454 IP network configurations and includes detailed data communications network (DCN) case studies that are based on actual ONS 15454 installations. The chapter provides information about the ONS 15454 IP routing table, external firewalls, and open gateway network element (GNE) networks. Although ONS 15454 DCN communication is based on IP, ONS 15454 nodes can be networked to equipment that is based on the Open System Interconnection (OSI) protocol suites. This chapter also describes the ONS 15454 OSI implementation and provides scenarios that show how the ONS 15454 can be networked within a mixed IP and OSI environment. This chapter does not provide a comprehensive explanation of IP networking concepts and procedures, nor does it provide IP addressing examples to meet all networked scenarios. For ONS 15454 networking setup instructions, refer to the “Turn Up a Node” chapter of the Cisco ONS 15454 DWDM Procedure Guide. Note Unless otherwise specified, in this chapter “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 17.1 IP Networking Overview, page 17-2 • 17.2 IP Addressing Scenarios, page 17-2 • 17.3 DCN Case Studies, page 17-23 • 17.4 DCN Extension, page 17-37 • 17.5 Routing Table, page 17-39 • 17.6 External Firewalls, page 17-41 • 17.7 Open GNE, page 17-42 • 17.8 TCP/IP and OSI Networking, page 17-45 • 17.9 Link Management Protocol, page 17-49 • 17.10 IPv6 Network Compatibility, page 17-54 • 17.11 IPv6 Native Support, page 17-54 • 17.12 Integration with Cisco CRS-1 Routers, page 17-57 • 17.13 Photonic Path Trace, page 17-6117-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Networking Overview • 17.14 Shared Risk Link Group, page 17-62 • 17.15 Proactive Protection Regen, page 17-63 Note To connect ONS 15454s to an IP network, you must work with a LAN administrator or other individual at your site who has IP networking training and experience. 17.1 IP Networking Overview ONS 15454s can be connected in many different ways within an IP environment: • They can be connected to LANs through direct connections or a router. • IP subnetting can create ONS 15454 node groups that allow you to provision nodes in a network that are not connected with a data communications channel (DCC). • Different IP functions and protocols can be used to achieve specific network goals. For example, Proxy Address Resolution Protocol (ARP) enables one LAN-connected ONS 15454 to serve as a gateway for ONS 15454s that are not connected to the LAN. • Static routes can be created to enable connections among multiple CTC sessions with ONS 15454s that reside on the same subnet with multiple CTC sessions. • ONS 15454s can be connected to Open Shortest Path First (OSPF) networks so ONS 15454 network information is automatically communicated across multiple LANs and WANs. • The ONS 15454 proxy server can control the visibility and accessibility between CTC computers and ONS 15454 element nodes. 17.2 IP Addressing Scenarios ONS 15454 IP addressing generally has nine common scenarios or configurations. Use the scenarios as building blocks for more complex network configurations. Table 17-1 provides a general list of items to check when setting up ONS 15454s in IP networks. Table 17-1 General ONS 15454 IP Troubleshooting Checklist Item What to Check Link integrity Verify that link integrity exists between: • CTC computer and network hub/switch • ONS 15454s (backplane [ANSI] or MIC-C/T/P [ETSI] wire-wrap pins or RJ-45 port) and network hub/switch • Router ports and hub/switch ports ONS 15454 hub/switch ports If connectivity problems occur, set the hub or switch port that is connected to the ONS 15454 to 10 Mbps half-duplex. Ping Ping the node to test connections between computers and ONS 15454s.17-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios 17.2.1 Scenario 1: CTC and ONS15454s on Same Subnet Scenario 1 shows a basic ONS 15454 LAN configuration (Figure 17-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 17-1 Scenario 1: CTC and ONS 15454s on Same Subnet (ANSI and ETSI) 17.2.2 Scenario 2: CTC and ONS15454s Connected to a Router In Scenario 2, the CTC computer resides on a subnet (192.168.1.0) and attaches to LAN A (Figure 17-2). The ONS 15454s reside on a different subnet (192.168.2.0) and attach to LAN B. A router connects LAN A to LAN B. The IP address of router interface A is set to LAN A (192.168.1.1), and the IP address of router interface B is set to LAN B (192.168.2.1). The routers each have a subnet mask of 255.255.255.0. IP addresses/subnet masks Verify that ONS 15454 IP addresses and subnet masks are set up correctly. Optical connectivity Verify that ONS 15454 optical trunk ports are in service and that a DCC is enabled on each trunk port. Table 17-1 General ONS 15454 IP Troubleshooting Checklist (continued) Item What to Check CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = N/A Host Routes = N/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.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN A Ring 12424417-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios On the CTC computer, the default gateway is set to router interface A. If the LAN uses Dynamic Host Configuration Protocol (DHCP), the default gateway and IP address are assigned automatically. In the Figure 17-2 example, a DHCP server is not available. Figure 17-2 Scenario 2: CTC and ONS 15454s Connected to Router (ANSI and ETSI) 17.2.3 Scenario 3: Using Proxy ARP to Enable an ONS15454 Gateway ARP matches higher-level IP addresses to the physical addresses of the destination host. It uses a lookup table (called ARP cache) to perform the translation. When the address is not found in the ARP cache, a broadcast is sent out on the network with a special format called the ARP request. If one of the machines on the network recognizes its own IP address in the request, it sends an ARP reply back to the requesting host. The reply contains the physical hardware address of the receiving host. The requesting host stores this address in its ARP cache so that all subsequent datagrams (packets) to this destination IP address can be translated to a physical address. Proxy ARP enables one LAN-connected ONS 15454 to respond to the ARP request for ONS 15454s not connected to the LAN. (ONS 15454 proxy ARP requires no user configuration.) For this to occur, the DCC-connected ONS 15454s must reside on the same subnet as the LAN-connected (gateway) ONS 15454 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/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 Default Router = N/A Host Routes = N/A ONS 15454 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A ONS 15454 #3 IP Address 192.168.2.30 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A LAN B LAN A Int "A" Int "B" Ring 12424517-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios ONS 15454. When a LAN device sends an ARP request to an ONS 15454 that is not connected to the LAN, the gateway ONS 15454 (the one connected to the LAN) returns its MAC address to the LAN device. The LAN device then sends the datagram for the remote ONS 15454 to the MAC address of the proxy ONS 15454. The proxy ONS 15454 uses its routing table to forward the datagram to the non-LAN ONS 15454. Scenario 3 is similar to Scenario 1, but only one ONS 15454 (Node 1) connects to the LAN (Figure 17-3). Two ONS 15454s (Node 2 and Node 3) connect to ONS 15454 Node 1 through the section DCC. Because all three ONS 15454s are on the same subnet, proxy ARP enables ONS 15454 Node 1 to serve as a gateway for ONS 15345 Node 2 and Node 3. Note This scenario assumes all CTC connections are to Node 1. If you connect a laptop to either ONS 15454 Node 2 or Node 3, network partitioning occurs; neither the laptop or the CTC computer can see all nodes. If you want laptops to connect directly to end network elements (ENEs), you must create static routes (see the “17.2.5 Scenario 5: Using Static Routes to Connect to LANs” section on page 17-8) or enable the ONS 15454 proxy server (see “17.2.7 Scenario 7: Provisioning the ONS 15454 Proxy Server” section on page 17-12). Be aware that: • GNE and ENE 15454 proxy ARP is disabled. • There is exactly one proxy ARP server on any given Ethernet segment; however, there might be more than one server in an ANSI or ETSI topology. • The proxy ARP server does not perform the proxy ARP function for any node or host that is on the same Ethernet segment. • It is important in Figure 17-3 that the CTC workstation be located within the same subnet and on the same Ethernet segment as the proxy ARP server.17-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-3 Scenario 3: Using Proxy ARP (ANSI and ETSI) You can also use proxy ARP to communicate with hosts attached to the craft Ethernet ports of DCC-connected nodes (Figure 17-4). The node with an attached host must have a static route to the host. Static routes are propagated to all DCC peers using OSPF. The existing proxy ARP node is the gateway for additional hosts. Each node examines its routing table for routes to hosts that are not connected to the DCC network but are within the subnet. The existing proxy server replies to ARP requests for these additional hosts with the node MAC address. The existence of the host route in the routing table ensures that the IP packets addressed to the additional hosts are routed properly. Other than establishing a static route between a node and an additional host, no provisioning is necessary. The following restrictions apply: • Only one node acts as the proxy ARP server for any given additional host. • A node cannot be the proxy ARP server for a host connected to its Ethernet port. In Figure 17-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 can be set up as an additional host. CTC Workstation IP Address 192.168.1.100 Subnet Mark at CTC Workstation 255.255.255.0 Default Gateway = N/A ONS 15454 #2 IP Address 192.168.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/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 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN A Ring 12424617-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-4 Scenario 3: Using Proxy ARP with Static Routing (ANSI and ETSI) 17.2.4 Scenario 4: Default Gateway on CTC Computer Scenario 4 is similar to Scenario 3, but Nodes 2 and 3 reside on different subnets, 192.168.2.0 and 192.168.3.0, respectively (Figure 17-5). Node 1 and the CTC computer are on subnet 192.168.1.0. Proxy ARP is not used because the network includes different subnets. For the CTC computer to communicate with Nodes 2 and 3, Node 1 is entered as the default gateway on the CTC computer. CTC Workstation IP Address 192.168.1.100 Subnet Mark at CTC Workstation 255.255.255.0 Default Gateway = N/A ONS 15454 #2 IP Address 192.168.1.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = Destination 192.168.1.100 Mask 255.255.255.0 Next Hop 192.168.1.10 ONS 15454 #3 IP Address 192.168.1.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = Destination 192.168.1.31 Mask 255.255.255.255 Next Hop 192.168.1.30 ONS 152xx IP Address 192.168.1.31 Subnet Mask 255.255.255.0 LAN A Ring 12424717-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-5 Scenario 4: Default Gateway on a CTC Computer (ANSI and ETSI) 17.2.5 Scenario 5: Using Static Routes to Connect to LANs Static routes are used for two purposes: • To connect ONS 15454s to CTC sessions on one subnet connected by a router to ONS 15454s residing on another subnet. (These static routes are not needed if OSPF is enabled. Scenario 6 shows an OSPF example.) • To enable multiple CTC sessions among ONS 15454s residing on the same subnet. In Figure 17-6, one CTC residing on subnet 192.168.1.0 connects to a router through interface A (the router is not set up with OSPF). ONS 15454s residing on different subnets are connected through Node 1 to the router through interface B. Because Nodes 2 and 3 are on different subnets, proxy ARP does not enable Node 1 as a gateway. To connect to CTC computers on LAN A, a static route is created on Node 1. ONS 15454 #1 IP Address 192.168.1.10 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A 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 ONS 15454 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #3 IP Address 192.168.3.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN A Ring 12424817-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-6 Scenario 5: Static Route With One CTC Computer Used as a Destination (ANSI and ETSI) The destination and subnet mask entries control access to the ONS 15454s: • If a single CTC computer is connected to a router, enter the complete CTC “host route” IP address as the destination with a subnet mask of 255.255.255.255. • If CTC computers on a subnet are connected to a router, enter the destination subnet (in this example, 192.168.1.0) and a subnet mask of 255.255.255.0. • If all CTC computers are connected to a router, enter a destination of 0.0.0.0 and a subnet mask of 0.0.0.0. Figure 17-7 shows an example. The IP address of router interface B is entered as the next hop, and the cost (number of hops from source to destination) is 2. 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 ONS 15454 #2 IP Address 192.168.3.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes Destination 192.168.1.0 Mask 255.255.255.0 Next Hop 192.168.2.1 Cost = 2 ONS 15454 #3 IP Address 192.168.4.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" Ring 12424917-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-7 Scenario 5: Static Route With Multiple LAN Destinations (ANSI and ETSI) 17.2.6 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. Each link state router captures the link state “advertisements” and puts them together to create a topology of the entire network or area. From this database, the router calculates a routing table by constructing a shortest path tree. Routes are recalculated when topology changes occur. ONS 15454s use the OSPF protocol in internal ONS 15454 networks for node discovery, circuit routing, and node management. You can enable OSPF on the ONS 15454s so that the ONS 15454 topology is sent to OSPF routers on a LAN. Advertising the ONS 15454 network topology to LAN routers 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 #1 IP Address of interface ”A” to LAN “A” 192.168.1.1 IP Address of interface “B” to LAN “B” 192.168.2.1 Subnet Mask 255.255.255.0 ONS 15454 #2 IP Address 192.168.2.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 ONS 15454 #3 IP Address 192.168.2.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" Ring 124250 Static Routes Destination 0.0.0.0 Mask 0.0.0.0 Next Hop 192.168.2.1 Cost = 2 LAN C LAN D Router #3 Router #217-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios eliminates the need to manually enter static routes for ONS 15454 subnetworks. Figure 17-8 shows a network enabled for OSPF. Figure 17-9 shows the same network without OSPF. Static routes must be manually added to the router for CTC computers on LAN A to communicate with Nodes 2 and 3 because these nodes reside on different subnets. OSPF divides networks into smaller regions, called areas. An area is a collection of networked end systems, routers, and transmission facilities organized by traffic patterns. Each OSPF area has a unique ID number, known as the area ID. Every OSPF network has one backbone area called “area 0.” All other OSPF areas must connect to area 0. When you enable an ONS 15454 OSPF topology for advertising to an OSPF network, you must assign an OSPF area ID in decimal format to the ONS 15454 network. An area ID is a “dotted quad” value that appears similar to an IP address. Coordinate the area ID number assignment with your LAN administrator. All DCC-connected ONS 15454s should be assigned the same OSPF area ID. Note It is recommended that the number of ONS 15454s in an OSPF area be limited, because this allows faster loading into a CTC an is less likely to incur any problems. Figure 17-8 Scenario 6: OSPF Enabled (ANSI and ETSI) 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 ONS 15454 #2 IP Address 192.168.3.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes = N/A ONS 15454 #3 IP Address 192.168.4.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" Ring 12425117-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-9 Scenario 6: OSPF Not Enabled (ANSI and ETSI) 17.2.7 Scenario 7: Provisioning the ONS15454 Proxy Server The ONS 15454 proxy server is a set of functions that allows you to network ONS 15454s in environments where visibility and accessibility between ONS 15454s and CTC computers must be restricted. For example, you can set up a network so that field technicians and network operations center (NOC) personnel can both access the same ONS 15454s while preventing the field technicians from accessing the NOC LAN. To do this, one ONS 15454 is provisioned as a GNE and the other ONS 15454s are provisioned as end ENEs. The GNE ONS 15454 tunnels connections between CTC computers and ENE ONS 15454s, providing management capability while preventing access for non-ONS 15454 management purposes. ONS 15454 #1 IP Address 192.168.2.10 Subnet Mask 255.255.255.0 Default Router = 192.168.2.1 Static Routes Destination = 192.168.1.100 Mask = 255.255.255.255 Next Hop = 192.168.2.1 Cost = 2 CTC Workstation IP Address 192.168.1.100 Subnet Mask 255.255.255.0 Default Gateway = 192.168.1.1 Host Routes = N/A Router IP Address of interface “A” to LAN A 192.168.1.1 IP Address of interface “B” to LAN B 192.168.2.1 Subnet Mask 255.255.255.0 Static Routes = Destination 192.168.3.20 Next Hop 192.168.2.10 Destination 192.168.4.30 Next Hop 192.168.2.10 ONS 15454 #2 IP Address 192.168.3.20 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A ONS 15454 #3 IP Address 192.168.4.30 Subnet Mask 255.255.255.0 Default Router = N/A Static Routes = N/A LAN B LAN A Int "A" Int "B" Ring 12425217-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios 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 17-3 on page 17-17 and Table 17-4 on page 17-17) depend on whether the packet arrives at the ONS 15454 DCC or TCC2/TCC2P/TCC3/TNC/TSC Ethernet interface. • Processes Simple Network Time Protocol (SNTP) and Network Time Protocol (NTP) requests. ONS 15454 ENEs can derive time-of-day from an SNTP/NTP LAN server through the GNE ONS 15454. • Processes Simple Network Management Protocol version 1 (SNMPv1) traps. The GNE ONS 15454 receives SNMPv1 traps from the ENE ONS 15454s and forwards or relays the traps to SNMPv1 trap destinations or ONS 15454 SNMP relay nodes. The ONS 15454 proxy server is provisioned using the Enable proxy server on port check box on the Provisioning > Network > General tab. If checked, the ONS 15454 serves as a proxy for connections between CTC clients and ONS 15454s that are DCC-connected to the proxy ONS 15454. The CTC client establishes connections to DCC-connected nodes through the proxy node. The CTC client can connect to nodes that it cannot directly reach from the host on which it runs. If not selected, the node does not proxy for any CTC clients, although any established proxy connections continue until the CTC client exits. In addition, you can set the proxy server as an ENE or a GNE: • External Network Element (ENE)—If set as an ENE, the ONS 15454 neither installs nor advertises default or static routes that go through its Ethernet port. However, an ENE does install and advertise routes that go through the DCC. CTC computers can communicate with the ONS 15454 using the TCC2/TCC2P/TCC3/TNC/TSC craft port, but they cannot communicate directly with any other DCC-connected ONS 15454. In addition, firewall is enabled, which means that the node prevents IP traffic from being routed between the DCC and the LAN port. The ONS 15454 can communicate with machines connected to the LAN port or connected through the DCC. However, the DCC-connected machines cannot communicate with the LAN-connected machines, and the LAN-connected machines cannot communicate with the DCC-connected machines. A CTC client using the LAN to connect to the firewall-enabled node can use the proxy capability to manage the DCC-connected nodes that would otherwise be unreachable. A CTC client connected to a DCC-connected node can only manage other DCC-connected nodes and the firewall itself. • Gateway Network Element (GNE)—If set as a GNE, the CTC computer is visible to other DCC-connected nodes and firewall is enabled. • SOCKS Proxy-only—If Proxy-only is selected, firewall is not enabled. CTC can communicate with any other DCC-connected ONS 15454s. Note If you launch CTC against a node through a Network Address Translation (NAT) or Port Address Translation (PAT) router and that node does not have proxy enabled, your CTC session starts and initially appears to be fine. However CTC never receives alarm updates and disconnects and reconnects every two minutes. If the proxy is accidentally disabled, it is still possible to enable the proxy during a reconnect cycle and recover your ability to manage the node, even through a NAT/PAT firewall. Note ENEs that belong to different private subnetworks do not need to have unique IP addresses. Two ENEs that are connected to different GNEs can have the same IP address. However, ENEs that connect to the same GNE must always have unique IP addresses.17-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-10 shows an ONS 15454 proxy server implementation. A GNE ONS 15454 is connected to a central office LAN and to ENE ONS 15454s. The central office LAN is connected to a NOC LAN, which has CTC computers. The NOC CTC computer and craft technicians must both be able to access the ONS 15454 ENEs. However, the craft technicians must be prevented from accessing or seeing the NOC or central office LANs. In the example, the ONS 15454 GNE is assigned an IP address within the central office LAN and is physically connected to the LAN through its LAN port. ONS 15454 ENEs are assigned IP addresses that are outside the central office LAN and given private network IP addresses. If the ONS 15454 ENEs are collocated, the craft LAN ports could be connected to a hub. However, the hub should have no other network connections. Figure 17-10 Scenario 7: ONS 15454 Proxy Server with GNE and ENEs on the Same Subnet (ANSI and ETSI) Table 17-2 shows recommended settings for ONS 15454 GNEs and ENEs in the configuration shown in Figure 17-10. Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15454 Gateway NE 10.10.10.100/24 ONS 15454 End NE 10.10.10.250/24 ONS 15454 End NE 10.10.10.150/24 ONS 15454 End NE 10.10.10.200/24 124253 Local/Craft CTC 192.168.20.20 Ethernet Optical Fiber Table 17-2 ONS 15454 Gateway and End NE Settings Setting ONS 15454 Gateway NE ONS 15454 End NE OSPF Off Off17-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-11 shows the same proxy server implementation with ONS 15454 ENEs on different subnets. The ONS 15454 GNEs and ENEs are provisioned with the settings shown in Table 17-2. Figure 17-11 Scenario 7: ONS 15454 Proxy Server with GNE and ENEs on Different Subnets (ANSI and ETSI) SNTP server (if used) SNTP server IP address Set to ONS 15454 GNE IP address SNMP (if used) SNMPv1 trap destinations Set SNMPv1 trap destinations to ONS 15454 GNE, port 391 Table 17-2 ONS 15454 Gateway and End NE Settings (continued) Setting ONS 15454 Gateway NE ONS 15454 End NE 124254 Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15454 Gateway NE 10.10.10.100/24 ONS 15454 End NE 192.168.10.250/24 ONS 15454 End NE 192.168.10.150/24 ONS 15454 End NE 192.168.10.200/24 Local/Craft CTC 192.168.20.20 Ethernet Optical Fiber 17-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-12 shows the same proxy server implementation with ONS 15454 ENEs in multiple rings. Figure 17-12 Scenario 7: ONS 15454 Proxy Server With ENEs on Multiple Rings (ANSI and ETSI) Table 17-3 shows the rules the ONS 15454 follows to filter packets for the firewall when nodes are configured as ENEs and GNEs. If the packet is addressed to the ONS 15454, additional rules (shown in Table 17-4) are applied. Rejected packets are silently discarded. 124255 Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15454 Gateway NE 10.10.10.100/24 ONS 15454 End NE 192.168.10.250/24 ONS 15454 End NE 192.168.10.150/24 ONS 15454 End NE 192.168.10.200/24 Ethernet Optical Fiber ONS 15454 Gateway NE 10.10.10.200/24 ONS 15454 End NE 192.168.80.250/24 ONS 15454 End NE 192.168.60.150/24 ONS 15454 End NE 192.168.70.200/2417-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios If you implement the proxy server, note that all DCC-connected ONS 15454s on the same Ethernet segment must have the same gateway setting. Mixed values produce unpredictable results, and might leave some nodes unreachable through the shared Ethernet segment. If nodes become unreachable, correct the setting by performing one of the following: • Disconnect the craft computer from the unreachable ONS 15454. Connect to the ONS 15454 through another network ONS 15454 that has a DCC connection to the unreachable ONS 15454. • Disconnect all DCCs to the node by disabling them on neighboring nodes. Connect a CTC computer directly to the ONS 15454 and change its provisioning. 17.2.8 Scenario 8: Dual GNEs on a Subnet The ONS 15454 provides GNE load balancing, which allows CTC to reach ENEs over multiple GNEs without the ENEs being advertised over OSPF. This feature allows a network to quickly recover from the loss of GNE, even if the GNE is on a different subnet. If a GNE fails, all connections through that GNE fail. CTC disconnects from the failed GNE and from all ENEs for which the GNE was a proxy, and then reconnects through the remaining GNEs. GNE load balancing reduces the dependency on the launch GNE and DCC bandwidth, both of which enhance CTC performance. Note Dual GNEs do not need special provisioning Figure 17-13 shows a network with dual GNEs on the same subnet. Table 17-3 Proxy Server Firewall Filtering Rules Packets Arriving At: Are Accepted if the Destination IP Address is: TCC2/TCC2P/TCC3 /TNC/TSC Ethernet interface • The ONS 15454 itself • The ONS 15454’s subnet broadcast address • Within the 224.0.0.0/8 network (reserved network used for standard multicast messages) • Subnet mask = 255.255.255.255 DCC interface • The ONS 15454 itself • Any destination connected through another DCC interface • Within the 224.0.0.0/8 network Table 17-4 Proxy Server Firewall Filtering Rules Packets Arriving At: Are Rejected If: TCC2/TCC2P/TCC3 /TNC/TSC Ethernet interface • User Datagram Protocol (UDP) packets addressed to the SNMP trap relay port (391) DCC interface • Transmission Control Protocol (TCP) packets addressed to the proxy server port (1080)17-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-13 Scenario 8: Dual GNEs on the Same Subnet (ANSI and ETSI) 124256 Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 ONS 15454 Gateway NE 10.10.10.100/24 ONS 15454 End NE 10.10.10.250/24 ONS 15454 Gateway NE 10.10.10.150/24 ONS 15454 End NE 10.10.10.200/24 Local/Craft CTC 192.168.20.20 Ethernet Optical Fiber17-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-14 shows a network with dual GNEs on different subnets. Figure 17-14 Scenario 8: Dual GNEs on Different Subnets (ANSI and ETSI) 17.2.9 Scenario 9: IP Addressing with Secure Mode Enabled The TCC2, TCC2P, TCC3, TNC, and TSC cards default to repeater mode. In this mode, the front and back Ethernet (LAN) ports share a single MAC address and IP address. TCC2P, TCC3, TNC, and TSC cards allow you to place a node in secure mode, which prevents a front-access craft port user from accessing the LAN through the backplane port. Secure mode can be locked, which prevents the mode from being altered. To place a node in secure mode or to lock secure node, refer to the “Manage the Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 17.2.9.1 Secure Mode Behavior Changing a TCC2P, TCC3, TNC, or TSC node from repeater mode to secure mode allows you to provision two IP addresses for the ONS 15454 and causes the node to assign the ports different MAC addresses. In secure mode, one IP address is provisioned for the ONS 15454 backplane LAN port, and 124257 Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.0/24 10.20.10.0/24 Interface 0/0 10.10.20.1 Router A Interface 0/1 10.10.10.1 Interface 0/2 10.20.10.1 ONS 15454 Gateway NE 10.10.10.100/24 ONS 15454 End NE 192.168.10.250/24 ONS 15454 Gateway NE 10.20.10.100/24 ONS 15454 End NE 192.168.10.200/24 Local/Craft CTC 192.168.20.20 Ethernet Optical Fiber17-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios the other IP address is provisioned for the card Ethernet port. Both addresses reside on different subnets, providing an additional layer of separation between the craft access port and the ONS 15454 LAN. If secure mode is enabled, the IP addresses provisioned for the backplane LAN port and card Ethernet port must follow general IP addressing guidelines and must reside on different subnets from each other. In secure mode, the IP address assigned to the backplane LAN port becomes a private address, which connects the node to an operations support system (OSS) through a central office LAN or private enterprise network. A Superuser can configure the node to hide or reveal the backplane's LAN IP address in CTC, the routing table, or TL1 autonomous message reports. In repeater mode, a node can be a GNE or ENE. Placing the node into secure mode automatically turns on SOCKS proxy and defaults the node to GNE status. However, the node can be changed back to an ENE. In repeater mode, an ENE’s SOCKS proxy can be disabled—effectively isolating the node beyond the LAN firewall—but it cannot be disabled in secure mode. To change a node’s GNE or ENE status and disable the SOCKS proxy, refer to the “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Procedure Guide. Caution Enabling secure mode causes the TCC2P, TCC3, TNC, and TSC cards to reboot; the card reboot affects traffic. Note The secure mode option does not appear in CTC if TCC2 cards are installed. If one TCC2 and one TCC2P card are installed in a node, secure mode will appear in CTC but it cannot be modified. Note If both front and backplane access ports are disabled in an ENE and the node is isolated from DCC communication (due to user provisioning or network faults), the front and backplane ports are automatically reenabled. Figure 17-15 shows an example of secure mode ONS 15454 nodes with front-access Ethernet port addresses that reside on the same subnet. 17-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-15 Scenario 9: ONS 15454 GNE and ENEs on the Same Subnet with Secure Mode Enabled Figure 17-16 shows an example of ONS 15454 nodes connected to a router with secure mode enabled. In each example, the node’s port address (node address) resides on a different subnet from the node backplane addresses. Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.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 Backplane - 10.10.10.250/24 TCC2P - 176.20.20.30/24 ONS 15454 ENE 10.10.10.150/24 - Backplane 176.20.20.10/24 - TCC2P ONS 15454 ENE 10.10.10.200/24 - Backplane 176.20.20.20/24 - TCC2P 124679 Local/Craft CTC 176.20.20.50 Ethernet SONET17-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IP Addressing Scenarios Figure 17-16 Scenario 9: ONS 15454 GNE and ENEs on Different Subnets with Secure Mode Enabled 17.2.9.2 Secure Node Locked and Unlocked Behavior Secure mode can be locked or unlocked on a node operating in secure mode. The default status is unlocked, and only a Superuser can issue a lock. When secure mode is locked, the node’s configuration (including Ethernet port status) and lock status cannot be changed by any network user. To have a secure node’s lock removed, contact Cisco Technical Support to arrange a Return Material Authorization (RMA) for the shelf assembly. See the “Obtaining Documentation and Submitting a Service Request” section on page lxx as needed. Enabling a lock makes a permanent change to the shelf’s EEPROM. A node’s configuration lock is maintained if the active TCC2P, TCC3, TNC, or TSC card’s database is reloaded. For example, if you attempt to load an unlocked node database onto a locked node’s standby TCC2P, TCC3, TNC, or TSC card for transfer to the active TCC2P, TCC3, TNC, or TSC card (an action that is not recommended), the unlocked node’s status (via the uploaded database) will not override the node’s lock status. If you attempt to load a locked database onto the standby TCC2P, TCC3, TNC, or TSC card of an unlocked secure node, the active TCC2P, TCC3, TNC, or TSC card will upload the database. If the uploaded defaults indicate a locked status, this will cause the node to become locked. If a software load has been customized before a lock is enabled, all lockable provisioning features are permanently set to the customized NE defaults provided in the load and cannot be changed by any user. 71674 Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.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 Backplane - 192.168.10.250/24 TCC2P - 176.20.20.30/24 ONS 15454 ENE 192.168.10.150/24 - Backplane 176.20.20.10/24 - TCC2P ONS 15454 ENE 192.168.10.200/24 - Backplane 176.20.20.20/24 - TCC2P Local/Craft CTC 176.20.20.50 Ethernet SONET17-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies 17.3 DCN Case Studies The ONS 15454 network is managed over the IP DCN and the optical service channels (OSCs), DCCs, and generic communications channels (GCCs). ONS 15454s perform many of the same functions as Layer 3 routers because they manage traffic between the DCN network management system (NMS) and the dense wavelength division multiplexing (DWDM) optical networks. This section provides case studies that show different ways an ONS 15454 network can be implemented within the DCN. The case studies are based on actual field installations. They include the network problem, the network topology created to solve it, IP addressing examples, and strengths and weaknesses of the solution. Routing principles followed throughout the case studies include: • If the ONS 15454 is connected to a DCN router, the default gateway points to the router. • If the default gateway must advertise to the OSC/DCC/GCC network, a static route is added for the default gateway. • If the network element (NE) is not connected to a DCN router, the default gateway is set to 0.0.0.0. 17.3.1 SOCKS Proxy Settings SOCKS proxy (described in the “17.2.7 Scenario 7: Provisioning the ONS 15454 Proxy Server” section on page 17-12) enables the ONS 15454 to serve as a proxy for connections between CTC clients and ONS 15454 nodes connected by OSCs, GCCs, or DCCs. Although SOCKS proxy can make DCN implementations easier, it should not be used when any of the following conditions exist: • Network management is based on SNMP and SNMP traps. The ONS 15454 can proxy SNMP traps, but if a redundant DCN connection is required, trap duplication on the network management platform will occur. • Telnet and debug session are required. These are not possible over SOCKS proxy. • Direct IP connectivity to every node is required. If these conditions are not present and no requirement to have direct IP connectivity to every node exists (that is, management is performed using CTC and/or Cisco Transport Manager [CTM]), Cisco recommends that you use the SOCKS proxy only option for all nodes that connect to a DCN router. 17.3.2 OSPF Activating OSPF (described in the “17.2.6 Scenario 6: Using OSPF” section on page 17-10) on the ONS 15454 LAN interface is another option that can be used to create resilient DCN connections. However, this option can only be enabled if every element in the network, from the NEs to the NOC, runs OSPF. This is not always possible, for example, the DCN connections might be on a public network out of the control of the organization using the ONS 15454 network. If you are considering enabling OSPF on the LAN, the following limitations must be considered: • If OSPF is enabled on the LAN, the internal OSC/DCC/GCC OSPF area cannot be 0.0.0.0. • The ONS 15454 can act as an OSPF area border gateway and support OSPF virtual links. However, virtual links cannot pass over the OSC/DCC/GCC network. If all elements in the DCN network are not running OSPF, enabling OSPF on the LAN is very difficult without creating isolated areas and/or segmentation of OSPF area 0. However, if the DCN network is a full OSPF network, enabling OSPF on the LAN might be employed for resilient DCN networks.17-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies 17.3.3 Management of Non-LAN Connected Multishelf Node When using dense wavelength division multiplexing (DWDM) multishelf management feature to subtend shelves from a node controller shelf, the Node Controller must be specially provisioned in case it does not have direct LAN reachability. Non-LAN connected Multishelf nodes are not manageable from CTC unless SOCKS Proxy is enabled on the node. In a GNE/ENE firewall configuration, non-LAN connected network elements must be set up as end network elements (ENEs) if Firewall is required. If firewall is not required on the non-LAN connected Multishelf node, then the node must be set up as SOCKS Proxy LAN-connected network elements (LNEs) can be set up as gateway network elements (GNEs) or as SOCKS proxies, depending upon network security requirements. If the GNE/ENE firewall feature is required, the LNE must be set up as a GNE. If the design does not require the firewall feature but does require all-IP networking, the LNE must be set up as a SOCKS proxy. For procedures to provision a node or shelf as a GNE, ENE or SOCKS proxy, refer to the Cisco ONS 15454 DWDM Procedure Guide. 17.3.4 DCN Case Study 1: Ring Topology with Two Subnets and Two DCN Connections DCN Case Study 1 (Figure 17-17) shows an ONS 15454 ring (DWDM or SONET/SDH). The ring is divided into two subnets and has two DCN connections for resiliency. Figure 17-17 DCN Case Study 1: ONS 15454 Ring with Two Subnets and Two DCN Connections 159495 192.168.100.0/24 192.168.200.0/24 Node 2 .79 Node 1 .80 Router 1 Router 2 .1 .1 .1 .1 .121 .2 .2 192.168.10.0/24 NOC router NMS .113 NOC LAN 10.58.46.64/26 192.168.20.0/24 Node 3 .78 Node 4 .7717-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies During normal operation, this configuration balances the management traffic load over the two available DCN connections. If one of the two DCN connections fails, the second DCN connection maintains accessibility so NE management can continue. However, if complete IP connectivity is required, for example, for SNMP when SOCKS proxy cannot be used, connection resilience is difficult to achieve because: • The ONS 15454 does not support route overloading. Configuring different routers with different costs for the same network destination is not possible. • The ONS 15454 always tries to route traffic on the LAN interface when its link is up, and the link on the NE connected to DCN router is always up. • If the DCN connection fails, the route is longer available. One solution is to create a generic routing encapsulation (GRE) tunnel to logically connect the remote Router 1 and remote Router 2 using the OSC/DCC/GCC network (Figure 17-18). With the GRE tunnel, both remote routers have an alternate path to reach the NOC network in case of DCN failure. However, the alternate path might become overloaded on the routing tables, resulting in higher costs. Figure 17-18 DCN Case Study 1: ONS 15454 Ring with Two Subnets, Two DCN Connections, and GRE Tunnel 17.3.4.1 DCN Case Study 1 IP Configuration The following sections show sample IP configuration at the routers and ONS 15454 nodes in DCN Case Study 1. 17.3.4.1.1 NOC Router Configuration Interface configuration: interface Ethernet0/0 ip address 10.58.46.121 255.255.255.192 no ip directed-broadcast ! interface Ethernet1/0 159496 192.168.100.0/24 192.168.30.0/24 GRE Tunnel 192.168.200.0/24 Router 1 Router 2 .1 .1 .1 .1 .121 .2 .2 .1 .2 192.168.10.0/24 NOC router NMS .113 NOC LAN 10.58.46.64/26 192.168.20.0/2417-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies ip address 192.168.20.1 255.255.255.0 no ip directed-broadcast ! interface Ethernet2/0 ip address 192.168.10.1 255.255.255.0 no ip directed-broadcast ! Static routes with alternate paths at different costs: ip classless ip route 192.168.100.0 255.255.255.0 192.168.10.2 ip route 192.168.100.0 255.255.255.0 192.168.20.2 10 ip route 192.168.200.0 255.255.255.0 192.168.20.2 ip route 192.168.200.0 255.255.255.0 192.168.10.2 10 17.3.4.1.2 Router 1 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.10.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.1 255.255.255.0 no ip directed-broadcast ! GRE tunnel interface configuration: interface Tunnel0 ip address 192.168.30.1 255.255.255.0 tunnel source Ethernet1/0 tunnel destination 192.168.200.1 Static routes with alternate paths at different costs: ip classless ip route 0.0.0.0 0.0.0.0 192.168.10.1 ip route 10.0.0.0 255.0.0.0 192.168.10.1 ip route 10.0.0.0 255.0.0.0 Tunnel0 10 ip route 192.168.200.0 255.255.255.0 Tunnel0 10 ip route 192.168.200.1 255.255.255.255 192.168.100.80 Note the host route to the peer Router 2 (192.168.200.1) points to the ONS 15454 network (through 192.168.100.80). This is required to set up the GRE tunnel. In this configuration, only the external route to 10.0.0.0 (that includes the NOC network) is overloaded with the alternate path. However, overloading might occur on this last-resort route. 17.3.4.1.3 Router 2 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.20.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.200.1 255.255.255.0 no ip directed-broadcast17-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies GRE tunnel interface configuration: interface Tunnel0 ip address 192.168.30.2 255.255.255.0 tunnel source Ethernet1/0 tunnel destination 192.168.100.1 Static routes with alternate paths at different costs: ip classless ip route 0.0.0.0 0.0.0.0 192.168.20.1 ip route 10.0.0.0 255.0.0.0 192.168.20.1 ip route 10.0.0.0 255.0.0.0 Tunnel0 10 ip route 192.168.100.0 255.255.255.0 Tunnel0 10 ip route 192.168.100.1 255.255.255.255 192.168.200.77 The host routing path to the Router 1 (192.168.100.1) points to the ONS 15454 network (by 192.168.200.77). This is required to set up the GRE tunnel. In this configuration, only the external route to 10.0.0.0 (that includes the NOC network) is overloaded with the alternate path. However, overloading the last-resort route might occur. Table 17-5 shows network settings on the four ONS 15454 nodes. The static routes are created so the DCN-connected nodes advertise their capability to act as last-resort routers. 17.3.4.2 DCN Case Study 1 Limitations DCN Case Study 1 shows how a GRE tunnel can be created between two routers to create DCN connection resiliency. While the resiliency is a benefit, when a DCN failure forces traffic to the GRE tunnel, the path calculated by the ONS 15454 OSPF algorithm running in the OSC/DCC/GCC network is no longer the shortest one. Subsequently, the round-trip delay time (RTT) might increase significantly because the DCN protection in this configuration is transparent to the ONS 15454 network. The ONS 15454 continues to use the same routing table. In addition, if a DCN failure occurs, the routing path that uses the GRE tunnel adds additional latency because of the number and length of OSC/DCC/GCC spans that the tunnel has to travel over the ONS 15454 network. This latency makes this DCN Case Study 1 solution difficult to scale to large networks. If this solution is used and the network grows significantly, a larger number of DCN-connected NEs are required. For example, the common rule in ONS 15454 DCN design is that all nodes should be within five section data communications channel (LDCC)/regeneration section DCC (RS-DCC/OSC or eight line DCC (LDCC) /multiplex section DCC (MS-DCC) spans from the network attached node. If Case Study 1 design is implemented, the maximum span numbers should be cut in half. However, if the DCN Case Study 1 design is used in networks that have full IP routing, have connectivity to every NE, and require only CTC/CTM management, the SOCKS proxy feature can be used to provide the same DCN connectivity resilience. Table 17-5 DCN Case Study 1 Node IP Addresses Node IP Address/Mask Default Gateway Static Routes: Destination/Mask – Next Hop Node 1 192.168.100.80/24 192.168.100.1 0.0.0.0/0 – 192.168.100.1 Node 2 192.168.100.79/24 0.0.0.0 — Node 3 192.168.100.78/24 0.0.0.0 — Node 4 192.168.100.77/24 192.168.100.1 0.0.0.0/0 – 192.168.200.117-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies 17.3.5 DCN Case Study 2: Linear Topology with DCN Connections on Both Ends DCN Case Study 2, shown in Figure 17-19, shows a four-node linear topology with DCN connectivity at both ends. Figure 17-19 DCN Case Study 2: ONS 15454 Linear Topology with DCN Connections at Both Ends To maintain DCN resilience, static routes are used and a GRE tunnel is created between Router 1 and Router 2 over the DCC/OSC/GCC optical link. In this example, all ONS 15454s are part of the same subnet. Therefore, the Router 1 and Router 2 static route tables have more entries because alternate paths must be configured for every host. 17.3.5.1 DCN Case Study 2 IP Configurations The following sections provide sample IP configurations at routers and ONS 15454 nodes in DCN Case Study 2. 17.3.5.1.1 NOC Router IP Configuration Interface configuration: interface Ethernet0/0 ip address 10.58.46.121 255.255.255.192 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.20.1 255.255.255.0 no ip directed-broadcast ! interface Ethernet2/0 ip address 192.168.10.1 255.255.255.0 no ip directed-broadcast ! 159497 Router 1 Router 2 .1 .2 .1 .1 .121 .2 .2 192.168.10.0/24 NOC router NMS .113 NOC LAN 10.58.46.64/26 192.168.20.0/24 Node 1 .80 Node 2 .79 Node 3 .78 Node 4 .7717-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies Static routes with alternate paths at different costs: ip classless ip route 192.168.100.0 255.255.255.0 192.168.10.2 ip route 192.168.100.0 255.255.255.0 192.168.20.2 100 ip route 192.168.100.77 255.255.255.255 192.168.20.2 ip route 192.168.100.77 255.255.255.255 192.168.10.2 10 ip route 192.168.100.78 255.255.255.255 192.168.20.2 ip route 192.168.100.78 255.255.255.255 192.168.10.2 10 ip route 192.168.100.79 255.255.255.255 192.168.10.2 ip route 192.168.100.79 255.255.255.255 192.168.20.2 10 ip route 192.168.100.80 255.255.255.255 192.168.10.2 ip route 192.168.100.80 255.255.255.255 192.168.20.2 10 17.3.5.1.2 Router 1 IP Configuration Site 1 router interface: interface Ethernet0/0 ip address 192.168.10.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.1 255.255.255.0 no ip directed-broadcast GRE tunnel interface configuration: interface Tunnel0 ip address 192.168.30.1 255.255.255.0 tunnel source Ethernet1/0 tunnel destination 192.168.100.2 Static routes with alternate paths at different costs: ip classless ip route 0.0.0.0 0.0.0.0 192.168.10.1 ip route 10.0.0.0 255.0.0.0 192.168.10.1 ip route 10.0.0.0 255.0.0.0 Tunnel0 10 ip route 192.168.100.2 255.255.255.255 192.168.100.80 Note that the host routing path to the peer DCN router (Site 2, 192.168.100.2) points to the ONS 15454 network (by 192.168.100.80) that is required to set up the GRE tunnel. In this configuration, only the external route to 10.0.0.0 (that include the NOC network) is overloaded with the alternate path, but overloading of the last-resort route might also occur. 17.3.5.1.3 Router 2 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.20.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.2 255.255.255.0 no ip directed-broadcast GRE tunnel interface configuration: interface Tunnel0 ip address 192.168.30.2 255.255.255.0 tunnel source Ethernet1/017-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies tunnel destination 192.168.100.1 Static routes with alternate paths at different costs: ip classless ip route 0.0.0.0 0.0.0.0 192.168.20.1 ip route 10.0.0.0 255.0.0.0 192.168.20.1 ip route 10.0.0.0 255.0.0.0 Tunnel0 10 ip route 192.168.100.1 255.255.255.255 192.168.100.77 Note that the host route to the Router 1 (192.168.100.1) points to the ONS 15454 network (by 192.168.200.77). This is required to set up the GRE tunnel. In this configuration, only the external route to 10.0.0.0 (that includes the NOC network) is overloaded with the alternate path. However, overloading the last-resort route might also occur. Table 17-6 shows network settings on the four ONS 15454 nodes. The static routes are created so the DCN-connected nodes advertise their capability to act as last-resort routers. 17.3.5.2 DCN Case Study 2 Limitations The linear configuration in DCN Case Study 2 does not effectively protect the management network communication for every fiber failure because the DCN router is not notified of the failures. Therefore, it continues to send packets on the low-cost path. This problem does not occur in ring topologies where the fiber failure is internally protected from the optical ring network. However, the OSPF dynamic routing protocol can be used over the DCN network to provide a solution to this problem. An OSPF configuration is shown in DCN Case Study 3. 17.3.6 DCN Case Study 3: Linear Topology with DCN Connections on Both Ends Using OSPF Routing DCN Case Study 3 is the same linear topology as DCN Case Study 2 except OSPF routing is used on the DCN network. This requires the OSPF active on LAN option, located on the node view (single-shelf mode) or multishelf view (multishelf mode) Provisioning > Network > OSPF tab, to be enabled at the end ONS 15454 nodes. In addition, OSPF must be running between Router 1, Router 2, and the NOC router. Because the DCN connection usually passes over a public network where OSPF is not always an option, the connection between Router 1, Router 2, and the NOC router is configured as a GRE tunnel so OSPF can run on the tunnel itself. Figure 17-20 shows the linear configuration with the separate OSPF areas, the tunnel connections, and the required OSPF virtual link. (The physical connections where the tunnels are passed are not shown in the figure because they are not directly part of the actual routing path.) Table 17-6 DCN Case Study 2 Node IP Addresses Node IP Address/Mask Default Gateway Static Routes: Destination/Mask – Next Hop Node 1 192.168.100.80/24 192.168.100.1 0.0.0.0/0 – 192.168.100.1 Node 2 192.168.100.79/24 0.0.0.0 — Node 3 192.168.100.78/24 0.0.0.0 — Node 4 192.168.100.77/24 192.168.100.1 0.0.0.0/0 – 192.168.200.117-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies Figure 17-20 DCN Case Study 3: ONS 15454 Linear Topology with DCN Connections at Both Ends Using OSPF 17.3.6.1 DCN Case Study 3 IP Configurations The following sections provide sample IP configurations at routers and ONS 15454 nodes for DCN Case Study 3. 17.3.6.1.1 NOC Router IP Configuration Interface configuration: interface Ethernet0/0 ip address 10.58.46.121 255.255.255.192 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.20.1 255.255.255.0 no ip directed-broadcast 159498 Router 1 Router 2 .1 .2 .121 .2 Tunnel110 .2 Tunnel210 .1 Tunnel110 .1 Tunnel210 192.168.100.0/24 Area 1 Area 100 Area 200 Area 0 NOC router NMS .113 NOC LAN 10.58.46.64/26 Node 1 .80 Node 2 .79 Node 3 .78 Node 4 .77 192.168.110.0/24 192.168.210.0/2417-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies ! interface Ethernet2/0 ip address 192.168.10.1 255.255.255.0 no ip directed-broadcast ! interface Loopback0 ip address 1.1.1.1 255.255.255.0 no ip directed-broadcast ! GRE tunnel interface configuration: interface Tunnel110 ip address 192.168.110.1 255.255.255.0 tunnel source Ethernet2/0 tunnel destination 192.168.10.2 ! interface Tunnel210 ip address 192.168.210.1 255.255.255.0 tunnel source Ethernet1/0 tunnel destination 192.168.20.2 ! OSPF routing configuration: router ospf 1 network 1.1.1.0 0.0.0.255 area 0 network 10.0.0.0 0.255.255.255 area 0 network 192.168.110.0 0.0.0.255 area 100 network 192.168.210.0 0.0.0.255 area 200 area 100 virtual-link 192.168.100.80 area 200 virtual-link 192.168.100.77 ! Note that the OSPF virtual link to the end ONS 15454s is created to connect the DCC/OSC/GCC OSPF area 1 to the backbone area 0. No static routes are defined on the NOC router. 17.3.6.1.2 Router 1 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.10.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.1 255.255.255.0 no ip directed-broadcast GRE tunnel interface configuration: interface Tunnel110 ip address 192.168.110.2 255.255.255.0 tunnel source Ethernet0/0 tunnel destination 192.168.10.1 ! OSPF and static routing configuration: router ospf 1 log-adjacency-changes network 192.168.100.0 0.0.0.255 area 100 network 192.168.110.0 0.0.0.255 area 100 !17-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies ip classless ip route 0.0.0.0 0.0.0.0 192.168.10.1 17.3.6.1.3 Router 2 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.20.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.2 255.255.255.0 no ip directed-broadcast GRE tunnel interface configuration: interface Tunnel210 ip address 192.168.210.2 255.255.255.0 tunnel source Ethernet0/0 tunnel destination 192.168.20.1 ! OSPF and static routing configuration: router ospf 1 network 192.168.100.0 0.0.0.255 area 200 network 192.168.210.0 0.0.0.255 area 200 ! ip classless ip route 0.0.0.0 0.0.0.0 192.168.20.1 Table 17-7 shows network settings on the four ONS 15454 nodes. The static routes are created so the DCN-connected nodes can advertise their capability to act as last-resort routers. Table 17-7 DCN Case Study 3 Node IP Addresses Node IP Address/Mask Default Gateway OSPF Configuration Node 1 192.168.100.80/24 192.168.100.1 DCC/OSC/GCC area: 0.0.0.1 LAN area: 0.0.0.100 OSPF Area Range Table: • 192.168.100.79/32 - Area 0.0.0.1 • 192.168.100.78/32 - Area 0.0.0.1 • 192.168.100.77/32 - Area 0.0.0.1 Virtual Link Table: 1.1.1.1 Node 2 192.168.100.79/24 0.0.0.0 DCC/OSC/GCC area: 0.0.0.1 OSPF disabled on LAN17-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies The OSPF virtual link requires its neighbor to be indicated with its router ID, not the physical or tunnel interface connected to the network. Using a loopback interface on the NOC router makes the router ID selection independent from real interface IP address. 17.3.6.2 DCN Case Study 3 Limitations DCN Case Study 3 shows that OSPF can provide better DCN resilience and more efficient routing choices, which results in better performance. OSPF also provides better network scalability. Some limitations of using OSPF include: • OSPF introduces additional complexity, for example, provisioning the OSPF virtual links and advertisement on the ONS 15454s and routers requires thought and planning. • OSPF must be enabled on the DCN connection between the NOC and the site routers. This can also be done through GRE tunnels, as shown in this case study. • Planning and thought must be given to the separation of the OSPF areas. Creation of virtual links to overcome the limitations described in the “17.3.2 OSPF” section on page 17-23 and to avoid isolated areas and segmentation in the backbone area requires planning as well. 17.3.7 DCN Case Study 4: Two Linear Cascaded Topologies With Two DCN Connections DCN Case Study 4, shown in Figure 17-21, extends the simple linear topology shown in DCN Case Study 3. However in this example, two linear DCN connections go to the same site router and all the ONS 15454s are in the same subnet. A GRE tunnel logically connects the remote Router 1 and Router 2 over the OSC/DCC/GCC network, which is similar to the DCN Case Study 1 configuration (Figure 17-18). The GRE tunnel provides the remote routers with an alternate path to reach the NOC network in case a DCN failure occurs. However, the alternate paths might overload the router routing tables and carry a higher cost because all alternate paths are host-based due to the fact the ONS 15454s reside in the same subnet. Node 3 192.168.100.78/24 0.0.0.0 DCC/OSC/GCC area: 0.0.0.1 OSPF disabled on LAN Node 4 192.168.100.77/24 192.168.100.1 DCC/OSC/GCC area: 0.0.0.1 LAN area: 0.0.0.200 OSPF Area Range Table: • 192.168.100.80/32 - Area 0.0.0.1 • 192.168.100.79/32 - Area 0.0.0.1 • 192.168.100.78/32 - Area 0.0.0.1 Virtual Link Table: 1.1.1.1 Table 17-7 DCN Case Study 3 Node IP Addresses (continued) Node IP Address/Mask Default Gateway OSPF Configuration17-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies Figure 17-21 DCN Case Study 4: Two Linear Cascaded Topologies with Two DCN Connections 17.3.7.1 DCN Case Study 4 IP Configurations The following sections provide sample IP configurations at the routers and ONS 15454 nodes for DCN Case Study 4. 17.3.7.1.1 NOC Router IP Configuration Interface configuration: interface Ethernet0/0 ip address 10.58.46.121 255.255.255.192 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.20.1 255.255.255.0 no ip directed-broadcast ! interface Ethernet2/0 ip address 192.168.10.1 255.255.255.0 no ip directed-broadcast ! Static routes with alternate paths at different costs: ip classless ip route 192.168.100.0 255.255.255.0 192.168.10.2 ip route 192.168.100.0 255.255.255.0 192.168.20.2 100 ip route 192.168.100.77 255.255.255.255 192.168.20.2 10 ip route 192.168.100.77 255.255.255.255 192.168.10.2 20 ip route 192.168.100.78 255.255.255.255 192.168.20.2 ip route 192.168.100.78 255.255.255.255 192.168.10.2 10 ip route 192.168.100.79 255.255.255.255 192.168.20.2 159499 Router 1 Router 2 .1 .2 .1 .1 .121 .2 .2 192.168.10.0/24 192.168.100.0/24 NOC router NMS .113 NOC LAN 10.58.46.64/26 192.168.20.0/24 Node 1 .80 Node 2 .79 Node 3 .78 Node 4 .7717-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Case Studies ip route 192.168.100.79 255.255.255.255 192.168.10.2 10 ip route 192.168.100.80 255.255.255.255 192.168.10.2 ip route 192.168.100.80 255.255.255.255 192.168.20.2 10 ip route 192.168.200.0 255.255.255.0 192.168.20.2 ip route 192.168.200.0 255.255.255.0 192.168.10.2 100 17.3.7.1.2 Router 1 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.10.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.1 255.255.255.0 no ip directed-broadcast GRE tunnel interface configuration: interface Tunnel0 ip address 192.168.30.1 255.255.255.0 tunnel source Ethernet1/0 tunnel destination 192.168.100.2 Static routes with alternate paths at different costs: ip classless ip route 0.0.0.0 0.0.0.0 192.168.10.1 ip route 10.0.0.0 255.0.0.0 192.168.10.1 ip route 10.0.0.0 255.0.0.0 Tunnel0 10 ip route 192.168.100.2 255.255.255.255 192.168.100.80 ip route 192.168.100.77 255.255.255.255 Tunnel0 20 ip route 192.168.100.78 255.255.255.255 Tunnel0 10 ip route 192.168.100.79 255.255.255.255 Tunnel0 10 Note that the host routing path to the peer DCN router (Router 2, 192.168.100.2) points to the ONS 15454 network (by 192.168.100.80). This is required to set up the GRE tunnel. In this configuration, only the external route to 10.0.0.0 (that includes the NOC network) is overloaded with the alternate path. However, overloading of the last-resort route could also occur. 17.3.7.1.3 Router 2 IP Configuration Interface configuration: interface Ethernet0/0 ip address 192.168.20.2 255.255.255.0 no ip directed-broadcast ! interface Ethernet1/0 ip address 192.168.100.2 255.255.255.0 no ip directed-broadcast GRE tunnel interface configuration: interface Tunnel0 ip address 192.168.30.2 255.255.255.0 tunnel source Ethernet1/0 tunnel destination 192.168.100.1 Static routes with alternate paths at different costs: ip classless ip route 0.0.0.0 0.0.0.0 192.168.20.117-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Extension ip route 10.0.0.0 255.0.0.0 192.168.20.1 ip route 10.0.0.0 255.0.0.0 Tunnel0 10 ip route 192.168.100.1 255.255.255.255 192.168.100.79 ip route 192.168.100.80 255.255.255.255 Tunnel0 10 Note that the host routing path to the peer DCN router (Router, IP 192.168.100.1) points to the ONS 15454 network (by 192.168.200.79). This is required to set up the GRE tunnel. In this configuration, only the external route to 10.0.0.0 (that include the NOC network) is overloaded with the alternate path. However, overloading the last-resort route is also possible. Table 17-8 shows network settings on the four ONS 15454 nodes. The static routes are created so the DCN-connected nodes can advertise their capability to act as last-resort routers. 17.3.7.2 DCN Case Study 4 Limitations Many limitations described in the “17.3.4.2 DCN Case Study 1 Limitations” section on page 17-27 also apply to this case study. However, the problems are less acute because of the DCN connection in the middle of the optical network. For DWDM networks, increased latency might became a problem if the linear topology has many spans with intermediate line amplifier or optical add/drop multiplexing (OADM) nodes, which is sometimes done to cover long-distance connections. In this case, when one DCN fails, management packets for nodes near the middle of the span travel 1.5 times the complete point-to-point connection. The normal routing figure is 0.5. The full connection length of a GRE tunnel is used as an alternate routing path. 17.4 DCN Extension ONS 15454 DWDM networks require a communication channel to exchange data among the different nodes within the network. Until Software Release 7.0, the only usable channel was the optical service channel (OSC) provided by the OSCM and OSC-CSM cards. In a long DWDM metro network, usage of OSC channel adds limitations in terms of cost and performance because the OSC channel maximum loss is 37 dB. The primary aim of the DCN extension feature is to remove the OSC constraint and leverage on already available external DCN or traffic matrix that allows nodes to be reached without using an OSC channel. You can connect two nodes in a DWDM network without using an OSC channel in the following two methods: • Using external DCN • Using GCC/DCC Table 17-8 DCN Case Study 4 Node IP Addresses Node IP Address/Mask Default Gateway Static Routes: Destination/Mask – Next Hop Node 1 192.168.100.80/24 192.168.100.1 0.0.0.0/0 – 192.168.100.1 192.168.100.1/32 – 192.168.100.80 Node 2 192.168.100.79/24 192.168.100.2 192.168.100.2/32 – 192.168.100.79 Node 3 192.168.100.78/24 192.168.100.2 0.0.0.0/0 – 192.168.100.2 Node 4 192.168.100.77/24 0.0.0.0 —17-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity DCN Extension The following sections describe the different communication methods and the factors to be considered while provisioning the connectivity. 17.4.1 Network Using OSC Figure 17-22 shows a point-to-point network that uses OSC as the communication channel. Figure 17-22 Network Using OSC In a network using OSC channel, it is possible to supervise all the nodes from the network operations center (NOC) and all nodes can communicate with each other using the OSC channel. Network topology discovery is automatic when you use an OSC channel. 17.4.2 Network Using External DCN Figure 17-23 shows a point-to-point network that uses external DCN as the communication channel. Figure 17-23 Network Using External DCN In a network using external DCN, it is possible to supervise all the nodes from the network operations center (NOC) and all nodes can communicate with each other using external DCN. The NOC is connected to each node through the external DCN. Since nodes do not have OSC connectivity, you must DCN CTC/Management OSC Node A Node B 273877 CTC/Management OTS to OTS PPC Virtual connection Node A Node B 273878 DCN Node connection relies on DCN17-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Routing Table create an OTS-to-OTS PPC between the nodes. The OTS-to-OTS PPC creates a DCN connection between the nodes. Refer to the “Create Circuits and Provisionable Patchcords” chapter in the Cisco ONS 15454 DWDM Procedure Guide for instructions on how to provision an OTS-to-OTS PPC. 17.4.3 Network Using GCC/DCC Figure 17-24 shows a point-to-point network that uses GCC/DCC as the communication channel. Figure 17-24 Network Using GCC/DCC In a network using GCC/DCC, one ONS 15454 node (for example, Node A) is provisioned as a gateway network element (GNE). The NOC is connected only to the GNE. It is possible to supervise all the nodes from the network operations center (NOC) and all nodes can communicate with each other using GCC/DCC. However in such a network, because of the absence of the embedded OSC channel, discovery of the network topology is not automatic. You must manually provision the adjacency of nodes in order to configure the correct topology. Refer to the “Create Circuits and Provisionable Patchcords” chapter in the Cisco ONS 15454 DWDM Procedure Guide for instructions on how to provision DCN extension for a network using GCC/DCC. 17.5 Routing Table ONS 15454 routing information is displayed 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. • Usage—Shows the number of times the listed route has been used. • Interface—Shows the ONS 15454 interface used to access the destination. Values are: – motfcc0—The ONS 15454 Ethernet interface, that is, the RJ-45 jack on the TCC2/TCC2P/TCC3 and, for ANSI shelves, the LAN 1 pins on the backplane or, for ETSI shelves, the LAN connection on the MIC-C/T/P. OTS to OTS PPC GCC Virtual connection Node connection relies on GCC/DCC DCN CTC/Management Node A Node B 27387917-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Routing Table – pdcc0—An SDCC or RS-DCC interface, that is, an OC-N/STM-N trunk card identified as the SDCC or RS-DCC termination. – lo0—A loopback interface. Table 17-9 shows sample routing entries for an ONS 15454. Entry 1 shows the following: • Destination (0.0.0.0) is the default route entry. All undefined destination network or host entries on this routing table are mapped to the default route entry. • Mask (0.0.0.0) is always 0 for the default route. • Gateway (172.20.214.1) is the default gateway address. All outbound traffic that cannot be found in this routing table or is not on the node’s local subnet is sent to this gateway. • Interface (motfcc0) indicates that the ONS 15454 Ethernet interface is used to reach the gateway. Entry 2 shows the following: • Destination (172.20.214.0) is the destination network IP address. • Mask (255.255.255.0) is a 24-bit mask, meaning all addresses within the 172.20.214.0 subnet can be a destination. • Gateway (172.20.214.92) is the gateway address. All outbound traffic belonging to this network is sent to this gateway. • Interface (motfcc0) indicates that the ONS 15454 Ethernet interface is used to reach the gateway. Entry 3 shows the following: • Destination (172.20.214.92) is the destination host IP address. • Mask (255.255.255.255) is a 32 bit mask, meaning only the 172.20.214.92 address is a destination. • Gateway (127.0.0.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.255) is a 32 bit mask, meaning only the 172.20.214.93 address is a destination. • Gateway (0.0.0.0) means the destination host is directly attached to the node. • Interface (pdcc0) indicates that a DCC interface is used to reach the destination host. Entry 5 shows a DCC-connected node that is accessible through a node that is not directly connected: • Destination (172.20.214.94) is the destination host IP address. Table 17-9 Sample Routing Table Entries Entry Destination Mask Gateway Usage Interface 1 0.0.0.0 0.0.0.0 172.20.214.1 265103 motfcc0 2 172.20.214.0 255.255.255.0 172.20.214.92 0 motfcc0 3 172.20.214.92 255.255.255.255 127.0.0.1 54 lo0 4 172.20.214.93 255.255.255.255 0.0.0.0 16853 pdcc0 5 172.20.214.94 255.255.255.255 172.20.214.93 16853 pdcc017-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity External Firewalls • Mask (255.255.255.255) is a 32-bit mask, meaning only the 172.20.214.94 address is a destination. • Gateway (172.20.214.93) indicates that the destination host is accessed through a node with IP address 172.20.214.93. • Interface (pdcc0) indicates that a DCC interface is used to reach the gateway. 17.6 External Firewalls This section provides sample access control lists for external firewalls. Table 17-10 lists the ports that are used by the TCC2/TCC2P/TCC3/TNC/TSC. Table 17-10 Ports Used by the TCC2/TCC2P/TCC3/TNC/TSC Port Function Action1 1. D = deny, NA = not applicable, OK = do not deny 0 Never used D 20 FTP D 21 FTP control D 22 SSH D 23 Telnet D 80 HTTP D 111 SUNRPC NA 161 SNMP traps destinations D 162 SNMP traps destinations D 513 rlogin D 683 CORBA IIOP OK 1080 Proxy server (socks) D 2001-2017 I/O card Telnet D 2018 DCC processor on active TCC2/TCC2P/TCC3/TNC/TSC D 2361 TL1 D 3082 Raw TL1 D 3083 TL1 D 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 OK17-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Open GNE The following access control list (ACL) example shows a firewall configuration when the proxy server gateway setting is not enabled. In the example, the CTC workstation's address is 192.168.10.10. and the ONS 15454 address is 10.10.10.100. The firewall is attached to the GNE, so inbound is CTC to the GNE and outbound is from the GNE to CTC. The CTC Common Object Request Broker Architecture (CORBA) Standard constant is 683 and the TCC CORBA Default is TCC Fixed (57790). access-list 100 remark *** Inbound ACL, CTC -> NE *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq www access-list 100 remark *** allows initial contact with ONS 15454 using http (port 80) *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq 57790 access-list 100 remark *** allows CTC communication with ONS 15454 GNE (port 57790) *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 established access-list 100 remark *** allows ACKs back from CTC to ONS 15454 GNE *** access-list 101 remark *** Outbound ACL, NE -> CTC *** access-list 101 remark access-list 101 permit tcp host 10.10.10.100 host 192.168.10.10 eq 683 access-list 101 remark *** allows alarms etc., from the 15454 (random port) to the CTC workstation (port 683) *** access-list 100 remark access-list 101 permit tcp host 10.10.10.100 host 192.168.10.10 established access-list 101 remark *** allows ACKs from the 15454 GNE to CTC *** The following ACL example shows a firewall configuration when the proxy server gateway setting is enabled. As with the first example, the CTC workstation address is 192.168.10.10 and the ONS 15454 address is 10.10.10.100. The firewall is attached to the GNE, so inbound is CTC to the GNE and outbound is from the GNE to CTC. CTC CORBA Standard constant is 683 and TCC CORBA Default is TCC Fixed (57790). access-list 100 remark *** Inbound ACL, CTC -> NE *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq www access-list 100 remark *** allows initial contact with the 15454 using http (port 80) *** access-list 100 remark access-list 100 permit tcp host 192.168.10.10 host 10.10.10.100 eq 1080 access-list 100 remark *** allows CTC communication with the 15454 GNE (port 1080) *** access-list 100 remark access-list 101 remark *** Outbound ACL, NE -> CTC *** access-list 101 remark access-list 101 permit tcp host 10.10.10.100 host 192.168.10.10 established access-list 101 remark *** allows ACKs from the 15454 GNE to CTC *** 17.7 Open GNE The ONS 15454 can communicate with non-ONS nodes that do not support Point-to-Point Protocol (PPP) vendor extensions or OSPF type 10 opaque link-state advertisements (LSA), both of which are necessary for automatic node and link discovery. An open GNE configuration allows a GCC-based network to function as an IP network for non-ONS nodes. To configure an open GNE network, you can provision GCC terminations to include a far-end, non-ONS node using either the default IP address of 0.0.0.0 or a specified IP address. You provision a far-end, non-ONS node by checking the Far End is Foreign check box during GCC creation. The default 0.0.0.0 IP address allows the far-end, non-ONS node to identify itself with any IP address; if you set an IP address other than 0.0.0.0, a link is established only if the far-end node identifies itself with that IP address, providing an extra level of security. 17-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Open GNE By default, the proxy server only allows connections to discovered ONS peers and the firewall blocks all IP traffic between the GCC network and LAN. You can, however, provision proxy tunnels to allow up to 12 additional destinations for SOCKS version 5 connections to non-ONS nodes. You can also provision firewall tunnels to allow up to 12 additional destinations for direct IP connectivity between the GCC network and LAN. Proxy and firewall tunnels include both a source and destination subnet. The connection must originate within the source subnet and terminate within the destination subnet before either the SOCKS connection or IP packet flow is allowed. A proxy connection is allowed if the CTC client is in a source subnet and the requested destination is in the destination subnet. Firewall tunnels allow IP traffic to route between the node Ethernet and pdcc interfaces. An inbound Ethernet packet is allowed through the firewall if its source address matches a tunnel source and its destination matches a tunnel destination. An inbound pdcc packet is allowed through the firewall if its source address matches a tunnel destination and its destination address matches a tunnel source. Tunnels only affect TCP and UDP packets. The availability of proxy and/or firewall tunnels depends on the network access settings of the node: • If the node is configured with the proxy server enabled in GNE or ENE mode, you must set up a proxy tunnel and/or a firewall tunnel. • If the node is configured with the proxy server enabled in proxy-only mode, you can set up proxy tunnels. Firewall tunnels are not allowed. • If the node is configured with the proxy server disabled, neither proxy tunnels nor firewall tunnels are allowed. Figure 17-25 shows an example of a foreign node connected to the GCC network. Proxy and firewall tunnels are useful in this example because the GNE would otherwise block IP access between the PC and the foreign node.17-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Open GNE Figure 17-25 Proxy and Firewall Tunnels for Foreign Terminations Figure 17-26 shows a remote node connected to an ENE Ethernet port. Proxy and firewall tunnels are useful in this example because the GNE would otherwise block IP access between the PC and foreign node. This configuration also requires a firewall tunnel on the ENE. Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.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.250/24 Non-ONS node Foreign NE 130.94.122.199/28 ONS 15454 ENE 10.10.10.150/24 ONS 15454 ENE 10.10.10.200/24 124261 Local/Craft CTC 192.168.20.20 Ethernet Optical Fiber17-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity TCP/IP and OSI Networking Figure 17-26 Foreign Node Connection to an ENE Ethernet Port 17.8 TCP/IP and OSI Networking ONS 15454 DCN communication is based on the TCP/IP protocol suite. However, ONS 15454s can also be networked with equipment that uses the OSI protocol suite. While TCP/IP and OSI protocols are not directly compatible, they do have the same objectives and occupy similar layers of the OSI reference model. For detailed information about OSI protocols, processes, and scenarios, refer to the “Management Network Connectivity” chapter in the ONS 15454 Reference Manual. OSI/MultiService Transport Platform (MSTP) scenarios are provided in the following sections. In OSI/MSTP Scenario 1 (Figure 17-27), an SDCC or RS-DCC carries an OC-N/STM-N signal from an OSI-based third-party NE to a transponder (TXP) or muxponder (MXP) card on an ONS NE. It is carried by GCC to a TXP/MXP card on another MSTP NE and then by SDCC or RS-DCC to a second third-party NE. This scenario requires TXPs/MXPs whose client interfaces can be provisioned in section or line termination mode. These include: • TXP_MR_2.5 and TXPP_MR_2.5 (when equipped with OC-N/STM-N SFPs) • TXP_MR_10G and TXP_MR_10E (when the client is configured as OC-192/STM-64) • MXP_2.5_10G and MXP_2.5_10E Remote CTC 10.10.20.10 10.10.20.0/24 10.10.10.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.250/24 ONS 15454 ENE 10.10.10.150/24 ONS 15454 ENE 10.10.10.200/24 124262 Local/Craft CTC 192.168.20.20 Ethernet Optical Fiber Non-ONS node Foreign NE 130.94.122.199/2817-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity TCP/IP and OSI Networking OSI has to be carried or tunneled to the other TXP/MXP card through an OSC termination, GCC termination, or both. The third-party NMS has OSI connectivity to its NEs with the MSTP ONS NE serving as the GNE for third-party vendor, OSI-based SONET equipment. Figure 17-27 OSI/MSTP Scenario 1 OSI/MSTP Scenario 2 (Figure 17-28) is similar to Scenario 1, except the MSTP NEs do not have connectivity to an OSI NMS. Third party OSI based NMS OSC OSC GCC OSC OSC SDCC/RS-DCC SDCC/RS-DCC OSI over SDCC/RS-DCC OSI over SDCC/RS-DCC TXP/MXP TXP/MXP Other vendor SONET/SDH Other vendor SONET/SDH DCN (IP/OSI) MSTP GNE MSTP MSTP MSTP 13765617-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity TCP/IP and OSI Networking Figure 17-28 OSI/MSTP Scenario 2 OSI/MSTP Scenario 3 (Figure 17-29) shows the following: • OSI is carried over an SDCC or RS-DCC termination. • OSI has to be carried or tunneled to the other peer TXP/MXP through an OSC termination, GCC termination, or both. • An OSS has IP connectivity to all the NEs. • The MSTP NE is a GNE for the third-party OSI-based SONET NEs. The MSTP NEs perform all mediation functions. OSC OSC OSC OSC SDCC/RS-DCC SDCC/RS-DCC OSI over SDCC/RS-DCC OSI over SDCC/RS-DCC TXP/MXP TXP/MXP Other vendor SONET/SDH Other vendor SONET/SDH MSTP MSTP MSTP MSTP 13765717-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity TCP/IP and OSI Networking Figure 17-29 OSI/MSTP Scenario 3 OSI/MSTP Scenario 4 (Figure 17-30) shows the following: • OSI is carried over an SDCC or RS-DCC termination. • OSI has to be carried or tunneled to the other peer TXP/MXP through an OSC termination, GCC termination, or both • An OSS has IP connectivity to all the NEs through third-party NE network. • The MSTP NE is a GNE for the third-party OSI-based SONET NEs. The MSTP NEs perform all mediation functions. • The third-party vendor NE is a GNE for the Cisco MSTP network. IP OSS OSC OSC GCC OSC OSC SDCC/RS-DCC SDCC/RS-DCC OSI over SDCC/RS-DCC OSI over SDCC/RS-DCC TXP/MXP TXP/MXP Other vendor SONET/SDH Other vendor SONET/SDH DCN (IP) MSTP GNE MSTP MSTP MSTP 13765817-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Link Management Protocol Figure 17-30 OSI/IP Scenario 4 17.9 Link Management Protocol This section describes Link Management Protocol1 (LMP) management and configuration. To troubleshoot specific alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. To configure LMP, refer to the Cisco ONS 15454 DWDM Procedure Guide. Note CTM support is not required for LMP. LMP is used to establish traffic engineering (TE) links between Cisco ONS 15454 nodes or between Cisco ONS 15454 nodes and selected non-Cisco nodes that use vendor-specific hardware. 17.9.1 Overview LMP manages TE links between nodes through the use of control channels. TE links are designed to define the most efficient paths possible for traffic to flow over a network and through the Internet. Traffic engineering encompasses traffic management, capacity management, traffic measurement and modeling, OSC OSC GCC OSC OSC SDCC/RS-DCC SDCC/RS-DCC OSI over SDCC/RS-DCC OSI over SDCC/RS-DCC TXP/MXP TXP/MXP Other vendor SONET/SDH Other vendor SONET/SDH DCN (IPP over CLNS tunnel) MSTP GNE MSTP MSTP MSTP 137659 CTM 1. The LMP protocol is specified by the IETF in an Internet-Draft, draft-ietf-ccamp-lmp-10.txt, which was published as a Proposed Standard, RFC 4204, (http://www.ietf.org/rfc/rfc4204.txt), on 2005-10-28.17-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Link Management Protocol network modeling, and performance analysis. Traffic engineering methods include call routing, connection routing, quality of service (QoS) resource management, routing table management, and capacity management. LMP manages TE links between peer nodes, such as two optical cross-connect (OXC) nodes. Peer nodes have equivalent signaling and routing. LMP also manages TE links between a node such as an OXC and an adjacent optical line system (OLS) node. An example of an OLS node is an ONS 15454 DWDM node. Networks with routers, switches, OXC nodes, DWDM OLS nodes, and add/drop multiplexers (ADM) use a common control plane such as Generalized Multiprotocol Label Switching (GMPLS) to provision resources and provide network survivability using protection and restoration techniques. LMP is part of the GMPLS protocol suite. A single TE link can be formed from several individual links. Management of TE links can be accomplished with in-band messaging, as well as with out-of-band methods. The following material describes the LMP between a pair of nodes that manages TE links. LMP accomplishes the following: • Maintains control channel connectivity • Verifies the physical connectivity of the data links • Correlates the link property information • Suppresses downstream alarms • Localizes link failures for protection/restoration purposes in multiple types of networks DWDM networks often use Multiprotocol Label Switching (MPLS) and GMPLS as common-control planes to control how packets are routed through the network. LMP manages the control channel that must exist between nodes for routing, signaling, and link management. For a control channel to exist, each node must have an IP interface that is reachable from the other node. Together, the IP interfaces form a control channel. The interface for the control messages does not have to be the same interface as the one for the data. 17.9.1.1 MPLS MPLS provides a mechanism for engineering network traffic patterns that is independent of routing tables and routing protocols. MPLS assigns short labels to network packets that describe how to forward the packets through the network. The traditional Layer 3 forwarding mechanism requires each hop to analyze the packet header and determine the next hop based on routing table lookup. With MPLS, the analysis of the packet header is performed just once, when a packet enters the MPLS cloud. The packet is then assigned to a stream known as a Label Switch Path (LSP), which is identified with a label. The short, fixed-length label is an index into a forwarding table, which is more efficient than the traditional routing table lookup at each hop. Using MPLS, both the control protocol (used to manage the LSPs) and user data can be carried over the same bearer interfaces. 17.9.1.2 GMPLS GMPLS is based on MPLS, with protocol extensions to support additional technologies, including time division multiplexing (TDM) slots (such as SONET and SDH), wavelength division multiplexing (WDM) wavelengths at Layer 1, and fiber. For MPLS, the control traffic (signaling and routing) can run over bearer interfaces. This is not the case with GMPLS, where a separate control channel is used. The GMPLS control channel is managed with LMP. With GMPLS, the control channels between two adjacent nodes do not need to use the same physical medium as the data links between those nodes.17-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Link Management Protocol 17.9.2 Configuring LMP Configuring LMP consists of the following four topics: • Control channel management • TE link management • Link connectivity verification • Fault management 17.9.2.1 Control Channel Management Control channel management establishes and maintains control channels between adjacent nodes. Control channels use a Config message exchange and a fast keep-alive mechanism between the nodes. The latter is required if lower-level mechanisms are not available to detect control-channel failures. A maximum of four LMP control channels can be supported. The nodes initially exchange configuration messages (Config, ConfigAck, and ConfigNack), which are used to exchange identifiers and negotiate parameters for the keep-alive protocol. The nodes then perform a continuous rapid exchange of Hello messages, which are used to monitor the health on the channel. Note The identifiers are Local Node Id, Remote Node Id, Local Control Channel Id, and Remote Control Channel Id. The parameters are the HelloInterval and the HelloDeadInterval. LMP out-of-fiber and LMP out-of-band control channels are supported and terminated on the shelf. An out-of-fiber control channel includes using the control plane network (Ethernet) for the control channel because Ethernet is separate from the fiber used for the data plane. An out-of-band control channel includes using overhead bytes, such as the SDCC and LDCC bytes, for the control channel because overhead bytes are separate from the payload. In-band means that the control messages are in the same channel as the data messages; therefore, out-of-band refers to overhead bytes in the same fiber, separate circuits dedicated to control messages in the same fiber (SONET/SDH circuits), or separate wavelengths in the same fiber (DWDM). Note Overhead bytes are SDCC or LDCC for SONET networks, RS-DCC or MS-DCC for SDH networks, and GCC or OSC for DWDM networks. Out-of-band implies in-fiber, but not in-band. In-fiber means that the control messages are in the same fiber as the data messages, and includes both in-band and out-of-band. Out-of-fiber means that the control messages take a path separate from the data plane. This includes separate fiber and Ethernet. The control channel management for a peer node to OLS link is the same as that for a link between two peer nodes. Note The software supports gracefully taking a control channel down for administration purposes (refer to Section 3.2.3 of the IETF LMP document). However, there is no provision for a graceful restart (refer to Section 8 of RFC 4204). • Graceful means that the nodes participating in the control channel agree that the link should go down. To gracefully take down a control channel, the node sets the ControlChannelDown flag in its messages to the other node until either the HelloDeadInterval expires or the other node sends a 17-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Link Management Protocol message back with the ControlChannelDown flag set. In either case, the node then stops sending messages for this control channel. Before a control channel is taken down, there should be a backup control channel in place that can be used to manage the data links. • Non-graceful means that one of the nodes just stops sending messages. The other side would declare a failure after the HelloDeadInterval, but would continue to send Hello messages to see if the control channel will come back up. 17.9.2.2 TE Link Management LMP ensures that links are grouped into TE links and that the properties of those links are the same at both endpoints. This is called TE link management, or link property correlation. Link property correlation is used to synchronize the TE link properties and verify the TE link configuration. The link property correlation function of LMP aggregates one or more data links into a TE link and synchronizes the properties of the TE link with the neighbor node. The procedure starts by sending a LinkSummary message to the neighbor. The LinkSummary message includes the local and remote Link Identifier, a list of all data links that make up the TE link, and various link properties. It is mandatory that a LinkSummaryAck or LinkSummaryNack message be sent in response to the receipt of a LinkSummary message, indicating agreement or disagreement with the link properties. Note A maximum of 256 LMP TE links is supported. 17.9.2.3 Link Connectivity Verification Link connectivity verification is not supported in this release, but might be supported in the future. 17.9.2.4 Fault Management Fault management is particularly useful when the control channels are physically diverse from the data links. It is used for rapid notification regarding the status of one or more TE-link data channels. The use of fault management is negotiated as part of the TE link’s LinkSummary exchange. Data links and TE link failures can be rapidly isolated and fault management supports both unidirectional and bidirectional LSPs. Transparent devices are useful because traditional methods for monitoring the health of allocated data links might no longer be appropriate. Instead, fault detection is delegated to the physical layer (for example, loss of light or optical monitoring of the data) instead of Layer 2 or Layer 3. Fault management uses the ChannelStatus, ChannelStatusAck, ChannelStatusRequest, and ChannelStatusResponse messages. Note The LMP Channel Activation/Deactivation Indication procedures are not supported; they are described in the IETF LMP document, Sections 6.4 and 6.5.17-53 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Link Management Protocol 17.9.3 LMP WDM LMP manages traffic engineering links between peer nodes (nodes that are peers in signaling and/or routing). The purpose of the LMP WDM extensions2 is to allow LMP to be used between an OXC node and an adjacent DWDM OLS node. Figure 17-31 illustrates the relationship between LMP and LMP-WDM. OXC 1 and OXC 2 are peer nodes whose control channel is managed with LMP. LMP-WDM manages the control channel between an OXC node and an OLS node. Figure 17-31 LMP and LMP-WDM Relationship When the two OLS nodes can communicate their configuration and the current state of their optical link to the two peer nodes (OXC 1 and OXC 2) through LMP-WDM, network usability is improved through the reduction of manual configuration and enhanced fault detection and recovery. 17.9.4 LMP Network Implementation Figure 17-32 shows a network-level LMP implementation. It is an IP-plus-optical network, with end-to-end routing based on MPLS and GMPLS. The primary network components are: • Routers – Cisco Carrier Router System (CSR) – Cisco Gigabit Switch Router (GSR) • An OXC node • Ultra long-haul (ULH) DWDM equipment LMP and other features allow the Cisco ONS 15454 DWDM node to fulfill the ULH DWDM role. Figure 17-32 illustrates the relationship between the network components. 2. LMP-WDM extensions that allow management of links between a peer node and an adjacent OLS node are described in the following IETF document: Internet-Draft, draft-ietf-ccamp-lmp-wdm-03.txt, published as a Proposed Standard, RFC 4209 (http://www.ietf.org/rfc/rfc4209.txt), 2005-11-1 OXC 1 OLS 1 OLS 2 OXC 2 LMP-WDM LMP-WDM LMP 15193717-54 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IPv6 Network Compatibility Figure 17-32 LMP System Implementation 17.10 IPv6 Network Compatibility IPv6 simplifies IP configuration and administration and has a larger address space than IPv4 to support the future growth of the Internet and Internet related technologies. It uses 128-bit addresses as against the 32-bit used in IPv4 addresses. Also, IPv6 gives more flexibility in designing newer addressing architectures. Cisco ONS 15454 DWDM 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 DWDM, and the client workstation. NAT-PT is a migration tool that helps users transition from IPv4 networks to IPv6 networks. NAT-PT is defined in RFC-2766. IPv4 and IPv6 nodes communicate with each other using NAT-PT by allowing both IPv6 and IPv4 stacks to interface between the IPv6 DCN and the IPv4 DCC networks. Note IPv6 is supported on Cisco ONS 15454 DWDM Software R8.0 and later with an external NAT-PT router. 17.11 IPv6 Native Support Cisco ONS 15454 DWDM Software R9.0 and later supports native IPv6. ONS 15454 DWDM can be managed over IPv6 DCN networks by enabling the IPv6 feature. After you enable IPv6 in addition to IPv4, you can use CTC, TL1, and SNMP over an IPv6 DCN to manage ONS 15454 DWDM. Each NE can be assigned an IPv6 address in addition to the IPv4 address. You can access the NE by entering the IPv4 address, an IPv6 address or the DNS name of the device. The IPv6 address is assigned only on the LAN interface of the NE. DCC/GCC interfaces use the IPv4 address. Router (Cisco CRS) Router (Cisco CRS) OXC OXC OXC OXC Cisco ONS 15454 MSTP TXP Mux/Demux Cisco ONS 15454 MSTP TXP Mux/Demux Cisco ONS 15454 MSTP TXP Mux/Demux Cisco ONS 15454 MSTP TXP Mux/Demux LSP 1 LSP 2 LMP LMP LMP LMP-WDM LMP-WDM 15193617-55 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IPv6 Native Support By default, when IPv6 is enabled, the node processes both IPv4 and IPv6 packets on the LAN interface. If you want to process only IPv6 packets, you need to disable IPv4 on the node. Before you disable IPv4, ensure that IPv6 is enabled and the node is not in multishelf mode. Figure 17-33 shows how an IPv6 DCN interacts with and IPv4 DCC. Figure 17-33 IPv6-IPv4 Interaction You can manage MSTP multishelf nodes over IPv6 DCN. RADIUS, FTP, SNTP, and other network applications support IPv6 DCN. To enable IPv6 addresses, you need to make the necessary configuration changes from the CTC or TL1 management interface. After you enable IPv6, you can start a CTC or TL1 session using the provisioned IPv6 address. The ports used for all IPv6 connections to the node are the same as the ports used for IPv4. An NE can either be in IPv6 mode or IPv4 mode. In IPv4 mode, the LAN interface does not have an IPv6 address assigned to it. An NE, whether it is IPv4 or IPv6, has an IPv4 address and subnet mask. TCC2/TCC2P/TCC3/TNC/TSC cards do not reboot automatically when you provision an IPv6 address, but a change in IPv4 address initiates a TCC2/TCC2P/TCC3/TNC/TSC card reset. Table 17-11 describes the differences between an IPv4 node and an IPv6 node. 270827 IPv6 DCN DCC IPv4 Network ENE C IPv6 Address: 3ffe:b00:ffff:1::4 IPv4 Address: 10.10.10.20 ENE B IPv6 Address: 3ffe:b00:ffff:1::3 IPv4 Address: 10.10.10.10 GNE A IPv6 Address: 3ffe:b00:ffff:1::5 IPv4 Address: 10.10.20.40 ENE D IPv6 Address: 3ffe:b00:ffff:1::6 IPv4 Address: 10.10.20.30 NMS IPv6 Address: 3ffe:b00:ffff:1::2 Table 17-11 Differences Between an IPv6 Node and an IPv4 Node IPv6 Node IPv4 Node Has both IPv6 address and IPv4 address assigned to its craft Ethernet interface. Does not have an IPv6 address assigned to its craft Ethernet interface. The default router has an IPv6 address for IPv6 connectivity, and an IPv4 address for IPv4 connectivity. The default router has an IPv4 address. Cannot enable OSPF on LAN. Cannot change IPv4 NE to IPv6 NE if OSPF is enabled on the LAN. Can enable OSPF on the LAN. Cannot enable RIP on the LAN. Cannot change IPv4 NE to IPv6 NE if RIP is enabled on the LAN. Can enable static routes/RIP on the LAN.17-56 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity IPv6 Native Support 17.11.1 IPv6 Enabled Mode The default IP address configured on the node is IPv4. You can use either CTC or the TL1 management interface to enable IPv6. For more information about enabling IPv6 from the CTC interface, see the Cisco ONS 15454 DWDM Procedure Guide. For more information about enabling IPv6 using TL1 commands, see the Cisco ONS 15454 TL1 Command Guide. 17.11.2 IPv6 Disabled Mode You can disable IPv6 either from the CTC or from the TL1 management interface. For more information about disabling IPv6 from the CTC interface, see the Cisco ONS 15454 DWDM Procedure Guide. For more information about disabling IPv6 using TL1 commands, see the Cisco ONS 15454 TL1 Command Guide. 17.11.3 IPv6 in Non-secure Mode In non-secure mode, IPv6 is supported on the front and the rear Ethernet interfaces. You can start a CTC or TL1 session using the IPv6 address provisioned on the on the front and rear ports of the NE. 17.11.4 IPv6 in Secure Mode In secure mode, IPv6 is only supported on the rear Ethernet interface. The front port only supports IPv4 even if it is disabled on the rear Ethernet interface. For more information about provisioning IPv6 addresses in secure mode, see the Cisco ONS 15454 DWDM Procedure Guide. For more information on secure mode behavior, see section 17.2.9 Scenario 9: IP Addressing with Secure Mode Enabled, page 17-19. 17.11.5 IPv6 Limitations IPv6 has the following configuration restrictions: • You can provision an NE as IPv6 enabled only if the node is a SOCKS-enabled or firewall-enabled GNE/ENE. • IPSec is not supported. • OSPF/RIP cannot be enabled on the LAN interface if the NE is provisioned as an IPv6 node. • Static route/firewall/proxy tunnel provisioning is applicable only to IPv4 addresses even if the IPv6 is enabled. Not supported on static routes, proxy tunnels, and firewall tunnels. Supported on static routes, proxy tunnels, and firewall tunnels. Routing decisions are based on the default IPv6 router provisioned. Table 17-11 Differences Between an IPv6 Node and an IPv4 Node IPv6 Node IPv4 Node17-57 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Integration with Cisco CRS-1 Routers • In secure mode, IPv6 is supported only on the rear Ethernet interface. IPv6 is not supported on the front port. • ONS platforms use NAT-PT internally for providing IPv6 native support. NAT-PT uses the IPv4 address range 128.x.x.x for packet translation. Do not use the 128.x.x.x address range when you enable IPv6 feature. 17.12 Integration with Cisco CRS-1 Routers This section describes the integration of a Cisco ONS 15454 DWDM node with a Cisco CRS-1 router. To provision end-to-end circuit connectivity between a DWDM node and a Cisco CRS-1 router, refer to Cisco ONS 15454 DWDM Procedure Guide. This feature provides end-to-end circuit provisioning from one Cisco CRS-1 router to another Cisco CRS-1 router passing through an MSTP network (without using GMPLS). In other words, you can use CTC to create an OCH trail circuit that includes the Cisco CRS-1 nodes involved in the MSTP network. With this feature, circuit provisioning is extended to the physical layer interface module (PLIM) trunk ports of the Cisco CRS-1 router. Note Cisco ONS Software Release 9.1 supports only Cisco CRS-1 router using Cisco IOS XR Software Release 3.9.0. If you have an earlier version of the Cisco IOS XR software, you cannot configure LMP on the Cisco CRS-1 router, and the router will be visible as an unknown node in the CTC network view. For more information about the Cisco CRS-1 router, refer to the documentation set available at http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html. 17.12.1 Card Compatibility The following Cisco CRS-1 DWDM PLIMs support this feature: • 4-10GE-ITU/C • 1OC768-ITU/C • 1OC768-DSPK The following ONS 15454 DWDM cards support this feature: • 32MUX-O • 32DMX-O • 32WSS • 32DMX • 40-DMX-C • 40-DMX-CE • 40-MUX-C • 40-WSS-C • 40-WSS-CE17-58 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Integration with Cisco CRS-1 Routers 17.12.2 Node Management Figure 17-34 depicts a typical network that includes DWDM nodes and Cisco CRS-1 routers. Figure 17-34 Cisco ONS 15454 DWDM Node and Cisco CRS-1 Router Network 17.12.2.1 Physical Connections The ONS 15454 DWDM node can be connected to CTC using multiple ways, as described in the “14.4 ONS 15454 Connections” section on page 14-5. The Cisco CRS-1 router must be connected to CTC through TCP/IP, using an Ethernet interface. There must be two physical connections between the DWDM node and the Cisco CRS-1 router for: • LMP provisioning—through the 10-Mbps Ethernet interface provided by the TCC2P card (on the Cisco ONS 15454 side) and the RP card (on the Cisco CRS-1 router side). • 10-Gbps and 40-Gbps traffic—through the fiber connection provided from the OCH ports of the multiplexer, demultiplexer, or WSS cards (on the Cisco ONS 15454 side) and from the PLIM trunk ports (on the Cisco CRS-1 router side). You must use LC connectors on both the Cisco ONS 15454 side and the Cisco CRS-1 router side. 17.12.2.2 CTC Display The CTC network view displays Cisco CRS-1 routers that have LMP control channels to the DWDM node that you logged in to, and to the DWDM nodes with DCC connections to the login node (Figure 17-35). When a data link has been established, the network view also displays the link between the Cisco CRS-1 router and the DWDM node. IP/MPLS Internal Interface WDM cloud 270861 XML or CLI XML or CLI CRS1_A CRS1_B LMP A OCH Trail Circuit Z LMP MSTP MSTP IP/MPLS CTC17-59 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Integration with Cisco CRS-1 Routers Figure 17-35 Cisco CRS-1 Router in CTC Network View The color of the Cisco CRS-1 router in the network view depends on the Cisco CRS-1 router alarm status. The color of the link between the DWDM node and the Cisco CRS-1 router depends on the link status. For more information on node and link colors, see the “14.5.3.2 CTC Node Colors” section on page 14-17 and the “14.5.3.3 DCC Links” section on page 14-17. 17.12.3 Circuit Management This section describes LMP provisioning and optical channel (OCH) trail circuit provisioning on the DWDM node and the Cisco CRS-1 router. 17.12.3.1 LMP Provisioning To provision end-to-end circuit connectivity from one Cisco CRS-1 router to another Cisco CRS-1 router passing through a DWDM network, you must configure LMP on the OCH ports of the first and last DWDM nodes (those adjacent to the Cisco CRS-1 router) and on the PLIM trunk ports of the Cisco CRS-1 router. Configuring LMP involves creating control channels, TE links, and data links. CTC primarily uses data links to discover circuit routes. For each 10-Gbps or 40-Gbps fiber between the Cisco CRS-1 router and the DWDM node, you must create a TE link and a data link. You must have a dedicated TE link for each data link because the Cisco CRS-1 router does not support link bundling (aggregation of one or more data links into a single TE link). When the port association is correct (checked using the LinkSummary message), the operational state of the data link transitions to Up–Free. 17-60 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Integration with Cisco CRS-1 Routers During creation of data links between the OCH ports of the DWDM node and the PLIM trunk ports of the Cisco CRS-1 router, CTC performs lambda tuning, that is, CTC automatically tunes the PLIM trunk port wavelength to match the supported wavelength on the OCH ports of the DWDM node. For more information on LMP, see the “17.9 Link Management Protocol” section on page 17-49. You can configure LMP on the DWDM node and the Cisco CRS-1 router through CTC. For details on configuring LMP, refer to Cisco ONS 15454 DWDM Procedure Guide. 17.12.3.2 OCH Trail Circuit Provisioning After you have provisioned LMP on the DWDM nodes and the Cisco CRS-1 routers, you can create an OCH trail circuit from one Cisco CRS-1 router to another Cisco CRS-1 router passing through an MSTP network. The endpoints (source and destination) of the OCH trail circuit must be Cisco CRS-1 routers. CTC does not allow mixed nodes (Cisco CRS-1 router to DWDM node) for OCH trail circuits. As part of OCH trail circuit creation, you must also define the following optical transport network (OTN) line parameters on both endpoints of the circuit: • ITU-T G.709 • Forward error correction (FEC) • Signal fail bit error rate (SF BER) • Signal degrade bit error rate (SD BER) After you define the source and destination nodes for the OCH trail circuit, CTC evaluates the circuit for a valid route between the two endpoints. If a valid route exists, CTC creates the required connections on all the impacted nodes. 17.12.4 Cisco CRS-1 Router Management from CTC After you have provisioned LMP on the Cisco CRS-1 router and the DWDM node, the Cisco CRS-1 router gets displayed in the CTC network view. You can view active alarms, performance monitoring (PM) parameters, and the software version of the Cisco CRS-1 router from CTC. To view PM parameters for a specific PLIM port, right-click the Cisco CRS-1 router in CTC network view and choose Show Router Port Status > rack/slot/module/port (Figure 17-36). 17-61 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Photonic Path Trace Figure 17-36 Cisco CRS-1 Router PM Parameters To view all the active alarms, right-click the Cisco CRS-1 router in CTC network view and choose Show Active Alarms. Note The Loss of Signal (LOS) alarm is not reported as critical for the Cisco CRS-1 router, whereas, it is reported as critical for the ONS 15454 node. To avoid this inconsistency, you can use Cisco Craft Works Interface (CWI) to manually change the severity for the LOS alarm of the Cisco CRS-1 router. To view the software version, click the Maintenance > Software tabs in the CTC network view. The working software version for each node is listed in the Working Version column. 17.13 Photonic Path Trace Photonic Path Trace (PPT) is a protocol that validates an optical path in an ONS 15454 MSTP network. PPT performs evidence-based path validation and identifies nodes in case of provisioning failure. PPT uses the power levels on each port to validate the path. For every node in the optical path, PPT reports the power levels against the threshold values in the form of a histogram. The histogram is displayed in the Photonic Path Trace tab of the Edit Circuit window in CTC. For each node, a set of power values collected from all the traversed ports is displayed in the histogram (Figure 17-37).17-62 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Shared Risk Link Group Figure 17-37 Photonic Path Trace Note An OCHNC or OCH trail circuit must exist on the optical path on which PPT is started. For information on how to start PPT on an optical path, see the “Turn Up a Network” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 17.14 Shared Risk Link Group SRLG is a unique 32 bit number that can be assigned to a link or DWDM node. This number can be used as an identifier of a link or a group of resources that may fail. A set of links constitute a SRLG if they share a resource (for example, a common fiber) whose failure causes the other links of the group to fail too. Therefore, the links in the group have a shared risk. A link can belong to multiple SRLGs. SRLG information is an unordered list of SRLGs that the link belongs to that is used by the router layer for making routing decisions. For example, if a router traverses through a diverse path, the path computation ensures that routing does not go through links sharing the same SRLG. There are two types of SRLGs, unique and additional. Every link or DWDM node must be assigned a unique SRLG attribute. Additional SRLGs for DWDM nodes or links are optional and can be defined in CTC. The additional SRLGs for a link compute the additional risks associated with the link. A list of additional SRLGs for a link can be defined in the Additional Span SRLG information attribute in CTC. This list can contain upto 20 SRLGs.17-63 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Proactive Protection Regen When the SRLG value of a DWDM node or link is changed, the SRLG attributes are updated for all the relevant router ports. When a new router-based OCH trail is created, the SRLG information of the DWDM nodes and links that are part of the newly created circuit is automatically communicated to the source and destination router. SRLG information can also be synchronized when the SRLG values on the router ports differ from the SRLG values on the DWDM nodes. The SRLG information can be viewed as consolidated or detailed reports in CTC. For more information about provisioning SRLGs on DWDM nodes and links, refer to the “Turn Up a Network” chapter in the Cisco ONS 15454 DWDM Procedure Guide. 17.15 Proactive Protection Regen When an optical signal degrades in a DWDM network, the downstream router is unaware of it. When the FEC limit is reached, there is traffic interruption with significant packet loss and an LOF alarm is raised. The LOF alarm triggers a Fast Reroute (FRR) mechanism in the router layer that switches traffic to a backup path. The Proactive Protection Regen feature achieves a hitless switchover before the traffic is interrupted by triggering an FRR to backup paths before the LOF alarm is raised. Proactive protection regen can be enabled on the OTU2_XP card ports when the card is used as a regenerator in Standard regen or Enhanced FEC mode. Proactive protection regen can also be configured during creation of OCH trail circuits between two Cisco CRS-1 routers. As soon as the BER of the optical signal between the upstream router and the ONS node exceeds the trigger threshold value for the duration set as the trigger window, a PPR-FDI alarm is generated by the ONS node. The PPR-FDI alarm is sent to the downstream router which in turn triggers the switchover to the backup path. The downstream router then sends the PPR-BDI alarm to the upstream router to switch to the backup path. For more information about configuring proactive protection regen on OTU2_XP cards and OCH trails in CTC, refer to the “Provision Transponder and Muxponder Cards” chapter in the Cisco ONS 15454 DWDM Procedure Guide.17-64 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 17 Management Network Connectivity Proactive Protection RegenCHAPTER 18-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 18 Alarm and TCA Monitoring and Management This chapter describes Cisco Transport Controller (CTC) alarm and threshold crossing alert (TCA) monitoring and management. To troubleshoot specific alarms, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 18.1 Overview, page 18-1 • 18.2 Alarm Counts on the LCD for a Node, Slot, or Port, page 18-2 • 18.3 Alarm Display, page 18-2 • 18.4 Alarm Severities, page 18-8 • 18.5 Alarm Profiles, page 18-9 • 18.6 External Alarms and Controls, page 18-12 • 18.7 Alarm Suppression, page 18-14 • 18.8 Multishelf Configuration Alarming, page 18-15 • 18.9 Threshold Crossing Alert Suppression, page 18-16 18.1 Overview CTC detects and reports alarms generated by the Cisco ONS 15454 and the larger network. You can use CTC to monitor and manage alarms at the card, node, or network level. Default alarm severities conform to the Telcordia GR-474-CORE standard, but you can set alarm severities in customized alarm profiles or suppress CTC alarm reporting. For a detailed description of the standard Telcordia categories employed by Optical Networking System (ONS) nodes, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide. Note ONS 15454 alarms can also be monitored and managed through Transaction Language One (TL1) or a network management system (NMS).18-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Counts on the LCD for a Node, Slot, or Port 18.2 Alarm Counts on the LCD for a Node, Slot, or Port You can view node, slot, or port-level alarm counts and summaries using the buttons on the ONS 15454 LCD panel. The Slot and Port buttons toggle between display types; the Slot button toggles between node display and slot display, and the Port button toggles between slot and port views. Pressing the Status button after you choose the display mode changes the display from alarm count to alarm summary. 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 18-1 shows the LCD panel layout. Note In an ONS 15454 M2 shelf assembly, the LCD panel and the Slot, Port, and Status buttons are present on the fan-tray assembly. In an ONS 15454 M6 shelf assembly, the LCD is a separate unit installed above the external connection unit (ECU); the Slot, Port, and Status buttons are present on the LCD unit. Figure 18-1 ONS 15454 Shelf LCD Panel 18.3 Alarm Display In the card, node, or network CTC view, click the Alarms tab to display the alarms for that card, node, or network. The Alarms window shows alarms in compliance with Telcordia GR-253-CORE. This means that if a network problem causes two alarms, such as loss of frame (LOF) and loss of signal (LOS), CTC only shows the LOS alarm in this window because it supersedes the LOF and replaces it. The Path Width column in the Alarms and Conditions tabs expands on the alarmed object information contained in the access identifier (AID) string (such as “STS-4-1-3”) by giving the number of STSs contained in the alarmed path. For example, the Path Width tells you whether a critical alarm applies to an STS1 or an STS48c. The column reports the width as a 1, 3, 6, 12, 48, etc. as appropriate, understood to be “STS-N.” Table 18-1 lists the column headings and the information recorded in each column. FAN FAIL Slot 8/18/03 04.06-002L-10 24˚C 97758 CRIT MAJ MIN Status Port Table 18-1 Alarm Column Descriptions Column Information Recorded Num Sequence number of the original alarm. (The column is hidden by default; to view it, right-click a column and choose Show Column > Num.) Ref Reference number of the original alarm. (The column is hidden by default; to view it, right-click a column and choose Show Column > Ref.)18-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Display Table 18-2 lists the color codes for alarm and condition severities. 18.3.1 Viewing Alarms by Time Zone By default, alarms and conditions are displayed with the time stamp of the CTC workstation where you are viewing them. However, you can set the node to report alarms (and conditions) using the time zone where the node is located. New Indicates a new alarm; to change this status, click either the Synchronize button or the Delete Cleared Alarms button. Date Date and time of the alarm. Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.) Object TL1 access identifier (AID) for the alarmed object; for an STSmon or VTmon, this is the monitored STS or VT. Eqpt Type If an alarm is raised on a card, the card type in this slot. Slot If an alarm is raised on a card, the slot where the alarm occurred [appears only in network and node view (single-shelf mode) or shelf view (multishelf mode)]. Port If an alarm is raised on a card, the port where the alarm is raised; for STSTerm and VTTerm, the port refers to the upstream card it is partnered with. Path Width Indicates how many STSs are contained in the alarmed path. This information complements the alarm object notation, which is explained in the Cisco ONS 15454 DWDM Troubleshooting Guide Sev Severity level: CR (Critical), MJ (Major), MN (minor), NA (Not Alarmed), NR (Not Reported). ST Status: R (raised), C (clear), T (transient). SA When checked, indicates a service-affecting alarm. Cond The error message/alarm name; these names are alphabetically defined in the Cisco ONS 15454 DWDM Troubleshooting Guide. Description Description of the alarm. Table 18-1 Alarm Column Descriptions (continued) Column Information Recorded Table 18-2 Color Codes for Alarms and Condition Severities Color Description Red Raised Critical (CR) alarm Orange Raised Major (MJ) alarm Yellow Raised Minor (MN) alarm Magenta (pink) Raised Not Alarmed (NA) condition Blue Raised Not Reported (NR) condition White Cleared (C) alarm or condition18-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Display 18.3.2 Controlling Alarm Display You can control the display of the alarms shown on the Alarms window. Table 18-3 shows the actions you can perform in the Alarms window. 18.3.3 Filtering Alarms The alarm display can be filtered to prevent display of alarms with certain severities or alarms that occurred between certain dates and times. You can set the filtering parameters by clicking the Filter button at the bottom-left of the Alarms window. You can turn the filter on or off by clicking the Filter tool at the bottom-right of the window. CTC retains your filter activation setting. For example, if you turn the filter on and then log out, CTC keeps the filter active the next time you log in. 18.3.4 Conditions Tab The Conditions window displays retrieved fault conditions. A condition is a fault or status detected by ONS 15454 hardware or software. When a condition occurs and continues for a minimum period, CTC raises a condition, which is a flag showing that this particular condition currently exists on the ONS 15454. The Conditions window shows all conditions that occur, including those that are superseded. For instance, if a network problem causes two alarms, such as LOF and LOS, CTC shows both the LOF and LOS conditions in this window (even though LOS supersedes LOF). Having all conditions visible can Table 18-3 Alarm Display Button/Check Box/Tool Action Filter button Allows you to change the display on the Alarms window to show only alarms that meet a certain severity level, occur in a specified time frame, or reflect specific conditions. For example, you can set the filter so that only critical alarms display in the window. If you enable the Filter feature by clicking the Filter button in one CTC view, such as node view (single-shelf mode) or shelf view (multishelf mode), it is enabled in the others as well (card view and network view). Synchronize button Updates the alarm display. Although CTC displays alarms in real time, the Synchronize button allows you to verify the alarm display. This is particularly useful during provisioning or troubleshooting. Delete Cleared Alarms button Deletes, from the view, alarms that have been cleared. AutoDelete Cleared Alarms check box If checked, CTC automatically deletes cleared alarms. Filter tool Enables or disables alarm filtering in the card, node, or network view. When enabled or disabled, this state applies to other views for that node and for all other nodes in the network. For example, if the Filter tool is enabled in the node (default login) view Alarms window, the network view Alarms window and card view Alarms window also show the tool enabled. All other nodes in the network also show the tool enabled.18-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Display be helpful when troubleshooting the ONS 15454. If you want to retrieve conditions that obey a root-cause hierarchy (that is, LOS supersedes and replaces LOF), you can exclude the same root causes by checking the “Exclude Same Root Cause” check box in the window. Fault conditions include reported alarms and Not Reported or Not Alarmed conditions. Refer to the trouble notifications information in the Cisco ONS 15454 DWDM Troubleshooting Guide for more information about alarm and condition classifications. 18.3.5 Controlling the Conditions Display You can control the display of the conditions on the Conditions window. Table 18-4 shows the actions you can perform in the window. 18.3.5.1 Retrieving and Displaying Conditions The current set of all existing conditions maintained by the alarm manager can be seen when you click the Retrieve button. The set of conditions retrieved is relative to the CTC view. For example, if you click the button while displaying the node view (single-shelf mode) or shelf view (multishelf mode), node-specific conditions appear. If you click the button while displaying the network view, all conditions for the network (including ONS 15454 nodes and other connected nodes) appear, and the card view shows only card-specific conditions. You can also set a node to display conditions using the time zone where the node is located, rather than the time zone of the PC where they are being viewed. 18.3.5.2 Conditions Column Descriptions Table 18-5 lists the Conditions window column headings and the information recorded in each column. Table 18-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. Filter Allows you to change the Conditions window display to only show the conditions that meet a certain severity level or occur in a specified time frame. For example, you can set the filter so that only critical conditions display on the window. There is a Filter button on the lower-right of the window that allows you to enable or disable the filter feature. Exclude Same Root Cause Retrieves conditions that obey a root-cause hierarchy (LOS supersedes and replaces LOF). Table 18-5 Conditions Column Description Column Information Recorded Date Date and time of the condition. Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.)18-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Display 18.3.5.3 Filtering Conditions The condition display can be filtered to prevent display of conditions (including alarms) with certain severities or that occurred between certain dates. You can set the filtering parameters by clicking the Filter button at the bottom-left of the Conditions window. You can turn the filter on or off by clicking the Filter tool at the bottom-right of the window. CTC retains your filter activation setting. For example, if you turn the filter on and then log out, CTC keeps the filter active the next time your user ID is activated. 18.3.6 Viewing History The History window displays historic alarm or condition data for the node or for your login session. You can chose to display only alarm history, only events, or both by checking check boxes in the History > Shelf window. You can view network-level alarm and condition history, such as for circuits, for all the nodes visible in network view. At the node level, you can see all port (facility), card, STS, and system-level history entries for that node. For example, protection-switching events or performance-monitoring threshold crossings appear here. If you double-click a card, you can view all port, card, and STS alarm or condition history that directly affects the card. Note In the Preference dialog General tab, the Maximum History Entries value only applies to the Session window. Different views of CTC display different kinds of history: • The History > Session window is shown in network view, node view (single-shelf mode) or shelf view (multishelf mode), and card view. It shows alarms and conditions that occurred during the current user CTC session. Object TL1 AID for the condition object. For an STSmon or VTmon, the object. Eqpt Type Card type in this slot. Slot Slot where the condition occurred (appears only in network and node view). Port Port where the condition occurred. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with. Path Width Width of the data path. Sev1 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 Cisco ONS 15454 DWDM Troubleshooting Guide. Description Description of the condition. 1. All alarms, their severities, and service-affecting statuses are also displayed in the Condition tab unless you choose to filter the alarm from the display using the Filter button. Table 18-5 Conditions Column Description (continued) Column Information Recorded18-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Display • The History > Shelf window is only shown in node view (single-shelf mode) or shelf view (multishelf mode). It shows the alarms and conditions that occurred on the node since CTC software was operated on the node. • The History > Card window is only shown in card view. It shows the alarms and conditions that occurred on the card since CTC software was installed on the node. Tip Double-click an alarm in the History window to display the corresponding view. For example, double-clicking a card alarm takes you to card view. In network view, double-clicking a node alarm takes you to node view (single-shelf mode) or shelf view (multishelf mode). 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. 18.3.6.1 History Column Descriptions Table 18-6 lists the History window column headings and the information recorded in each column. Table 18-6 History Column Description Column Information Recorded Num Num (number) is the quantity of alarm messages received, and is incremented automatically as alarms occur to display the current total of received error messages. (The column is hidden by default; to view it, right-click a column and choose Show Column > Num.) Ref Ref (reference) is a unique identification number assigned to each alarm to reference a specific alarm message that is displayed. (The column is hidden by default; to view it, right-click a column and choose Show Column > Ref.) Date Date and time of the condition. Node Shows the name of the node where the condition or alarm occurred. (Visible in network view.) Object TL1 AID for the condition object. For an STSmon or VTmon, the object. Slot Slot where the condition occurred [only displays in network view and node view (single-shelf mode) or shelf view (multishelf mode)]. Port Port where the condition occurred. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with. Path Width Width of the data path. Sev Severity level: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA), Not Reported (NR). ST Status: raised (R), cleared (C), or transient (T). SA Indicates a service-affecting alarm (when checked). Cond Condition name. Description Description of the condition. Eqpt Type Card type in this slot.18-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Severities 18.3.6.2 Retrieving and Displaying Alarm and Condition History You can retrieve and view the history of alarms and conditions, including transient conditions (passing notifications of processes as they occur) in the CTC History window. The information in this window is specific to the view where it is shown (that is, network history in the network view, node history in the node view (single-shelf mode) or shelf view (multishelf mode), and card history in the card view). The node and card history views are each divided into two tabs. In node view (single-shelf mode) or shelf view (multishelf mode), when you click the Retrieve button, you can see the history of alarms, conditions, and transients that have occurred on the node in the History > Node window, and the history of alarms, conditions, and transients that have occurred on the node during your login session in the History > Session window. In the card-view history window, after you retrieve the card history, you can see the history of alarms, conditions, and transients 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. 18.3.7 Alarm History and Log Buffer Capacities The ONS 15454 alarm history log, stored in the TCC2/TCC2P/TCC3/TNC/TSC RSA memory, contains four categories of alarms. These include: • CR severity alarms • MJ severity alarms • MN severity alarms • the combined group of cleared, Not Alarmed severity, and Not Reported severity alarms Each category can store between 4 and 640 alarm chunks, or entries. In each category, when the upper limit is reached, the oldest entry in the category is deleted. The capacity is not user-provisionable. CTC also has a log buffer, separate from the alarm history log, that pertains to the total number of entries displayed in the Alarms, Conditions, and History windows. The total capacity is provisionable up to 5,000 entries. When the upper limit is reached, the oldest entries are deleted. 18.4 Alarm Severities ONS 15454 alarm severities follow the Telcordia GR-474-CORE standard, so a condition might be Alarmed (at a severity of Critical [CR], Major [MJ], or Minor [MN]), Not Alarmed (NA), or Not Reported (NR). These severities are reported in the CTC software Alarms, Conditions, and History windows at all levels: network, shelf, and card. ONS equipment provides a standard profile named Default listing all alarms and conditions with severity settings based on Telcordia GR-474-CORE and other standards, but users can create their own profiles with different settings for some or all conditions and apply these wherever desired. (See the “18.5 Alarm Profiles” section on page 18-9.) For example, in a custom alarm profile, the default severity of a carrier loss (CARLOSS) alarm on an Ethernet port could be changed from major to critical. The profile allows setting to Not Reported or Not Alarmed, as well as the three alarmed severities. Critical and Major severities are only used for service-affecting alarms. If a condition is set as Critical or Major by profile, it will raise as Minor alarm in the following situations: • In a protection group, if the alarm is on a standby entity (the side not carrying traffic)18-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Profiles • If the alarmed entity has no traffic provisioned on it, no service is lost Because of this possibility of being raised at two different levels, the alarm profile pane shows Critical as CR / MN and Major as MJ / MN. 18.5 Alarm Profiles The alarm profiles feature allows you to change default alarm severities by creating unique alarm profiles for individual ONS 15454 ports, cards, or nodes. A created alarm profile can be applied to any node on the network. Alarm profiles can be saved to a file and imported elsewhere in the network, but the profile must be stored locally on a node before it can be applied to the node, its cards, or its cards’ ports. 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-CORE severities. The reserved Inherited profile allows port alarm severities to be governed by the card-level severities, or card alarm severities to be determined by the node-level severities. If one or more alarm profiles have been stored as files from elsewhere in the network onto the local PC or server hard drive where CTC resides, you can utilize as many profiles as you can physically store by deleting and replacing them locally in CTC so that only eight are active at any given time. 18.5.1 Creating and Modifying Alarm Profiles Alarm profiles are created in the network view using the node view (single-shelf mode) or shelf view (multishelf mode) Provisioning > Alarm Profiles tabs. A default alarm severity following Telcordia GR-474-CORE standards is preprovisioned for every alarm. After loading the default profile or another profile on the node, you can clone a profile to create custom profiles. After the new profile is created, the Alarm Profiles window shows the original profile (frequently Default) and the new profile. Note The alarm profile list contains a master list of alarms that is used for a mixed node network. Some of these alarms might not be used in all ONS nodes. Note The Default alarm profile list contains alarm and condition severities that correspond when applicable to default values established in Telcordia GR-474-CORE. Note All default or user-defined severity settings that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in non-service-affecting situations as defined in Telcordia GR-474-CORE. Tip To see the full list of profiles, including those available for loading or cloning, click the Available button. You must load a profile before you can clone it. Note Up to 10 profiles, including the two reserved profiles (Inherited and Default) can be stored in CTC.18-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Profiles Wherever it is applied, the Default alarm profile sets severities to standard Telcordia GR-474-CORE 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. If you choose the Inherited profile from the network view, the severities at the lower levels (node and card) are copied from this selection. You do not have to apply a single severity profile to the node-, card-, and port-level alarms. Different profiles can be applied at different levels. You could use the inherited or default profile on a node and on all cards and ports, but apply a custom profile that downgrades an alarm on one particular card. For example, you might choose to downgrade an OC-N unequipped path alarm (UNEQ-P) from Critical (CR) to Not Alarmed (NA) on an optical card because this alarm raises and then clears every time you create a circuit. UNEQ-P alarms for the card with the custom profile would not display on the Alarms tab (but they would still be recorded on the Conditions and History tabs.) When you modify severities in an alarm profile: • All Critical (CR) or Major (MJ) default or user-defined severity settings are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474. • Default severities are used for all alarms and conditions until you create a new profile and apply it. The Load and Store buttons are not available for Retrieve and Maintenance users. The Delete and Store options will only display nodes to delete profiles from or store profiles to if the user has provisioning permission for those nodes. If the user does not have the proper permissions, CTC greys out the buttons and they are not available to the user. 18.5.2 Alarm Profile Buttons The Alarm Profiles window displays six buttons at the bottom of the screen. Table 18-7 lists and describes each of the alarm profile buttons and their functions. 18.5.3 Alarm Profile Editing Table 18-8 lists and describes the five profile-editing options available when you right-click an alarm item in the profile column (such as Default). Table 18-7 Alarm Profile Buttons Button Description New Creates a new profile. Load Loads a profile to a node or a file. Store Saves profiles on a node (or nodes) or in a file. Delete Deletes profiles from a node. Compare Displays differences between alarm profiles (for example, individual alarms that are not configured equivalently between profiles). Available Displays all profiles available on each node. Usage Displays all entities (nodes and alarm subjects) present in the network and which profiles contain the alarm. Can be printed.18-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Profiles 18.5.4 Alarm Severity Options To change or assign alarm severity, left-click the alarm severity you want to change in the alarm profile column. Seven severity levels appear for the alarm: • Not Reported (NR) • Not Alarmed (NA) • Minor (MN) • Major (MJ) • Critical (CR) • Use Default • Inherited Inherited and Use Default severity levels only appear in alarm profiles. They do not appear when you view alarms, history, or conditions. 18.5.5 Row Display Options In the network or node view (single-shelf mode) or shelf view (multishelf mode), the Alarm Profiles window (Alarm Profile Editor for node view) displays three check boxes at the bottom of the window: • Only show service-affecting severities—If unchecked, the editor shows severities in the format sev1/sev2 where sev1 is a service-affecting severity and sev2 is not service-affecting. If checked, the editor only shows sev1 alarms. • Hide reference values—Highlights alarms with nondefault severities by clearing alarm cells with default severities. • Hide identical rows—Hides rows of alarms that contain the same severity for each profile. 18.5.6 Applying Alarm Profiles In CTC node view (single-shelf mode) or shelf view (multishelf mode), 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. A card-level alarm profile applies to all ports on the card except ports that have their own profiles. Table 18-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. Reset Restores a profile to its previous state or to the original state (if it has not yet been applied). Remove Removes a profile from the table editor.18-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management External Alarms and Controls At the node level, you can apply profile changes on a card-by-card basis or set a profile for the entire node. At the card-level view, you can apply profile changes on a port-by-port basis or set alarm profiles for all ports on that card. 18.6 External Alarms and Controls External alarm inputs can be provisioned on the Alarm Interface Controller–International (AIC-I) card for external sensors such as an open door and flood sensors, temperature sensors, and other environmental conditions. External control outputs on these two cards allow you to drive external visual or audible devices such as bells and lights. They can control other devices such as generators, heaters, and fans. Up to 12 external alarm inputs and four external controls are available with the AIC-I card. If you also provision the alarm extension panel (AEP), there are 32 inputs and 16 outputs. The AEP is compatible with the ONS 15454 ANSI shelf only. It is not compatible with the ONS 15454 ETSI shelf. 18.6.1 External Alarms You can provision each alarm input separately. Provisionable characteristics of external alarm inputs include: • Alarm Type—List of alarm types. • Severity—CR, MJ, MN, NA, and NR. • Virtual Wire—The virtual wire associated with the alarm. • Raised When—Open means that the normal condition is no current flowing through the contact, and the alarm is generated when current does flow; closed means that 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). Note If you provision an external alarm to raise when a contact is open, and you have not attached the alarm cable, the alarm will remain raised until the alarm cable is connected. Note When you provision an external alarm, the alarm object is ENV-IN-nn. The variable nn refers to the external alarm’s number, regardless of the name you assign. 18.6.2 External Controls You can provision each alarm output separately. Provisionable characteristics of alarm outputs include: • Control type. • Trigger type (alarm or virtual wire). • Description for CTC display. • Closure setting (manually or by trigger). If you provision the output closure to be triggered, the following characteristics can be used as triggers:18-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management External Alarms and Controls – Local NE alarm severity—A chosen alarm severity (for example, major) and any higher-severity alarm (in this case, critical) causes output closure. – Remote NE alarm severity—Similar to local NE alarm severity trigger setting, but applies to remote alarms. – Virtual wire entities—You can provision an alarm that is input to a virtual wire to trigger an external control output. 18.6.3 Virtual Wires Provisioning the AIC and AIC-I card provides a “virtual wires” option used to route external alarms and controls from different nodes to one or more alarm collection centers. In Figure 18-2, smoke detectors at Nodes 1, 2, 3, and 4 are assigned to Virtual Wire #1, and Virtual Wire #1 is provisioned as the trigger for an external bell at Node 1. Figure 18-2 External Alarms and Controls Using a Virtual Wire When using AIC virtual wires, you can: • Assign different external devices to the same virtual wire. • Assign virtual wires as the trigger type for different external controls. ONS 15454 Node 1 Virtual Wire #1 is external control trigger Virtual Wire #1 Smoke detector Bell Smoke detector ONS 15454 Node 2 ONS 15454 Node 3 ONS 15454 Node 4 Virtual Wire #1 Virtual Wire #1 Virtual Wire #1 = External alarm = External control Smoke detector Smoke detector 4474318-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Alarm Suppression 18.7 Alarm Suppression The following sections explain alarm suppression features for the ONS 15454. 18.7.1 Alarms Suppressed for Maintenance When you place a port in OOS,MT administrative state, this raises the alarm suppressed for maintenance (AS-MT) alarm in the Conditions and History windows and causes subsequently raised alarms for that port to be suppressed. Note AS-MT can be seen in the Alarms window as well if you have set the Filter dialog box to show NA severity events. 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). When you place the port back into IS,AINS administrative state, the AS-MT alarm is resolved in all three windows. Suppressed alarms remain raised in the Conditions window until they are cleared. 18.7.2 Alarms Suppressed by User Command In the node view (single-shelf mode) or shelf view (multishelf mode) Provisioning > Alarm Profiles tabs > Alarm Behavior tabs, the ONS 15454 has an alarm suppression option that clears raised alarm messages for the node, chassis, one or more slots (cards), or one or more ports. Using this option raises the alarms suppressed by user command, or AS-CMD alarm. The AS-CMD alarm, like the AS-MT alarm, appears in the Conditions, and History windows. Suppressed conditions (including alarms) appear only in the Conditions window--showing their normal severity in the Sev column. When the Suppress Alarms check box is unchecked, the AS-CMD alarm is cleared from all three windows. Note AS-MT can be seen in the Alarms window as well if you have set the Filter dialog box to show NA severity events. A suppression command applied at a higher level does not supersede a command applied at a lower level. For example, applying a node-level alarm suppression command makes all raised alarms for the node appear to be cleared, but it does not cancel out card-level or port-level suppression. Each of these conditions can exist independently and must be cleared independently. Caution Use alarm suppression with caution. If multiple CTC or TL1 sessions are open, suppressing the alarms in one session suppresses the alarms in all other open sessions.18-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Multishelf Configuration Alarming 18.8 Multishelf Configuration Alarming Multishelf systems can share a single IP address among shelves and also correlate optical signal alarms. Ethernet alarm-raising for this configuration also differs from alarm-raising for single-shelf configurations. This section explains how alarms are viewed on a multishelf configuration, how alarm locations are determined, and how multishelf alarming differs from single-shelf alarming. 18.8.1 Viewing Multishelf Alarmed Entities The multishelf view in CTC shows which slots are occupied in each shelf of the configuration (Figure 18-3). Figure 18-3 Navigating to Shelf View from Multishelf View You can determine where an alarm is raised by viewing the Object column. The entry there (for example, FAC-1-3-1) tells you the entity (“fac,” or facility), shelf, slot, and port. In shelf view, the Alarms and Conditions tabs also contain a Shelf column that indicates where the alarmed card is located. 18.8.2 Multishelf-Specific Alarming The following sections explain how Ethernet communication alarms and correlated multishelf alarms are processed in the ONS 15454 DWDM system.18-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Threshold Crossing Alert Suppression 18.8.2.1 Ethernet Communication Alarms The Ethernet interface card (MS-ISC) that is required for multishelf configurations does not raise traditional Ethernet alarms, such as CARLOSS, that apply to transponder (TXP) or muxponder (MXP) client ports. Instead, MS-ISC card alarms are raised on the shelf as EQPT alarms. These alarms include Duplicate Shelf ID (DUP-SHELF-ID) and Shelf Communication Failure (SHELF-COMM-FAIL). 18.8.2.2 Multishelf Correlated Alarms ITU-T G.798-based alarm correlation simplifies alarm reporting for DWDM channels. Communication failures including Loss of Signal (LOS), Loss of Signal Payload (LOS-P), and Optical Power Receive Fail-Loss of Light (OPWR-LFAIL) generate multiple conditions at each affected node and channel. Correlation simplifies troubleshooting because a single alarm is reported for each root cause. (The original alarms retain their severity in the Conditions window.) The Payload Missing Indication (PMI) condition is raised at the far end to correlate optical multiplex section (OMS) and optical transmission section (OTS) communication failures. A single PMI condition is sent when every channel on the aggregated port is lost, that is, when there are no pass-through channels or active added channels in service. If there are added channels on the node, the Forward Defect Indication (FDI) condition is raised at the near end to indicate there are no pass-through optical channels (OCH) in service. 18.9 Threshold Crossing Alert Suppression This section describes threshold crosssing alert (TCA) suppression on TXP and MXP cards when they are installed in a DWDM node. 18.9.1 Overview Threshold default settings define the default cumulative values (thresholds) beyond which a TCA will be raised. TCAs make it possible to monitor the network and detect errors early. The following thresholds are monitored for TXP and MXP cards: • Optical Thresholds • ITU-T G.709 Thresholds • SONET and SDH Thresholds • FEC Thresholds Threshold defaults are defined for near end and/or far end and at 15-minute or one-day intervals. When LOS-P, LOS, or LOF alarms occur on the TXP./MXP cards, different TCAs are suppressed. Which TCAs are suppressed by an alarm depends on how the trunk is configured (ITU-T G.709, SONET, or SDH). The reason for suppressing the TCAs after the alarm occurs is to prevent a flood of TCAs after a system failure. TCA suppression does not extend to optical thresholds such as OPR (optical power received). Optical threshold TCAs can effectively be suppressed by setting their thresholds to the maximum value.TCA suppression also does not extend to client ports; it only applies to TXP and MXP trunk ports when they are configured as ITU-T G.709, SONET, or SDH. TCA suppression does not extend to 10GE payloads.18-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Threshold Crossing Alert Suppression Note Suppressed TCAs are not reported as Not Reported (NR) conditions. As a result, suppressed TCAs do not appear in the CTC Conditions tab and they cannot be retrieved with the RTRV-COND TL1 command. 18.9.2 G.709, SONET, and SDH TCA Groups This section lists the TCAs that are suppressed for each alarm. TCA suppression is determined by how framing is configured for TXP and MXP trunks. Table 18-9 lists the TCAs for each type of trunk framing and alarm.18-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Threshold Crossing Alert Suppression Table 18-9 TCA Suppression Groups Alarm TXP/MXP Trunk Framing TCA Suppressed LOS-P and LOF G.709 BBE-SM ES-SM SES-SM UAS-SM FC-SM ESR-SM SESR-SM BBER-SM BBE-PM ES-PM SES-PM UAS-PM FC-PM ESR-PM SESR-PM BBER-PM BIT-EC UNC-WORDS18-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Threshold Crossing Alert Suppression LOS or LOF SONET ES-S SES-S SEFS-S CV-S ES-L SES-L UAS-L CV-L FC-L LOS or LOF SDH RS-ES RS-ESR RS-SES RS-SESR RS-BBR RS-BBER RS-UAS RS-EB MS-ES MS-ESR MS-SES MS-SESR MS-BBR MS-BBER MS-UAS MS-EB Table 18-9 TCA Suppression Groups (continued) Alarm TXP/MXP Trunk Framing TCA Suppressed18-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 18 Alarm and TCA Monitoring and Management Threshold Crossing Alert SuppressionCHAPTER 19-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 19 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 transponder, muxponder, and dense wavelength division multiplexing (DWDM) cards in the Cisco ONS 15454 including optical amplifier, multiplexer, demutiplexer, optical add/drop multiplexer (OADM), and optical service channel (OSC) cards. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. For information about enabling and viewing PM values, refer to the Cisco ONS 15454 DWDM Procedure Guide. Chapter topics include: • 19.1 Threshold Performance Monitoring, page 19-2 • 19.2 TNC Card Performance Monitoring, page 19-2 • 19.3 Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring, page 19-7 • 19.4 DWDM Card Performance Monitoring, page 19-23 • 19.5 Optics and 8b10b PM Parameter Definitions, page 19-27 • 19.6 ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions, page 19-28 • 19.7 Full RMON Statistics PM Parameter Definitions, page 19-30 • 19.8 FEC PM Parameter Definitions, page 19-33 • 19.9 SONET PM Parameter Definitions, page 19-34 • 19.10 SDH PM Parameter Definitions, page 19-35 • 19.11 Pointer Justification Count Performance Monitoring, page 19-37 Note For additional information regarding PM parameters, refer to ITU G.826, ITU-T G.8021, ITU G.709, Telcordia documents GR-1230-CORE, GR-820-CORE, GR-499-CORE, and GR-253-CORE, and the ANSI T1.231 document entitled Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring.19-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Threshold Performance Monitoring 19.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 about provisioning card thresholds, such as line and path thresholds, refer to the Cisco ONS 15454 DWDM Procedure Guide. During the accumulation cycle, if the current value of a PM parameter reaches or exceeds its corresponding threshold value, a threshold crossing alert (TCA) is generated by the node and is displayed by CTC. TCAs provide early detection of performance degradation. When a threshold is crossed, the node continues to count the errors during a given accumulation period. If zero is entered as the threshold value, generation of TCAs is disabled but performance monitoring continues. Note Due to memory limitations and the number of TCAs generated by different platforms, you can manually add or modify the following two properties to the platform property file (CTC.INI for Windows and .ctcrc for UNIX) to fit the need: • ctc.15xxx.node.tr.lowater=yyy (where xxx is platform and yyy is the number of the lowater mark. The default lowater mark is 25.) • ctc.15xxx.node.tr.hiwater=yyy (where xxx is platform and yyy is the number of the hiwater mark. The default hiwater mark is 50.) If the number of the incoming TCA is greater than the hiwater mark, the node will keep the latest lowater mark and discard older ones. Change the threshold if the default value does not satisfy your error monitoring needs. For example, customers with a critical OC192/STM64 transponder installed for 911 calls must guarantee the best quality of service on the line; therefore, they lower all thresholds on the client side so that the slightest error raises a TCA. Note When LOS, LOS-P, or LOF alarms occur on TXP and MXP trunks, ITU-T G.709/SONET/SDH TCAs are suppressed. For details, see Chapter 18, “Alarm and TCA Monitoring and Management.” 19.2 TNC Card Performance Monitoring (Cisco ONS 15454 M2 and ONS 15454 M6 only) This section lists the PM parameters and RMONs supported by TNC card. Note Optics PM and Payload PM are not supported in TSC card.19-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring TNC Card Performance Monitoring 19.2.1 Optics PM Window The Optics PM window lists the parameters for the TNC card. The Optics PM window provides buttons to change the statistical values shown. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. In the Historical PM subtab, the Clear button sets the values on the card to zero. All counters on the card are cleared. The Help button activates context sensitive help. Table 19-1 lists the optics PM parameters. 19.2.2 Payload PM Window The Payload PM subtabs are: Ethernet, SONET, Statistics, Utilization, and History. The following buttons function the same on all of the tabs. Not all tabs have all of these buttons. • The Refresh button manually refreshes statistics. • The Auto-Refresh button sets a time interval at which automatic refresh occurs. • The Baseline button resets the displayed statistics values to zero. Table 19-1 Optics PM Parameters Optics PM Parameters Definition Laser Bias (Min,%) Minimum Laser Bias Current (Laser Bias Min) is the minimum percentage of laser bias current during the PM time interval. Laser Bias (Avg,%) Average Laser Bias Current (Laser Bias Avg) is the average percentage of laser bias current during the PM time interval. Laser Bias (Max,%) Maximum Laser Bias Current (Laser Bias Max) is the maximum percentage of laser bias current during the PM time interval. Rx Optical Pwr (Min,dBm) Minimum Receive Optical Power (Rx Optical Pwr Min, dBm) is the minimum received optical power during the PM time interval. Rx Optical Pwr (Avg,dBm) Average Receive Optical Power (Rx Optical Pwr Avg, dBm) is the average received optical power during the PM time interval. Rx Optical Pwr (Max,dBm) Maximum Receive Optical Power (Rx Optical Pwr Max, dBm) is the maximum received optical power during the PM time interval. Tx Optical Pwr (Min,dBm) Minimum Transmit Optical Power (Tx Optical Pwr Min, dBm) is the minimum optical power transmitted during the PM time interval. Tx Optical Pwr (Avg,dBm) Average Transmit Optical Power (Tx Optical Pwr Avg, dBm) is the average optical power transmitted during the PM time interval. Tx Optical Pwr (Max,dBm) Maximum Transmit Optical Power (Tx Optical Pwr Max, dBm) is the maximum optical power transmitted during the PM time interval.19-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring TNC Card Performance Monitoring • (Statistics window only) The Clear button allows you to set the values to zero for displayed statistics, all statistics for a port, and all statistics for all optical ports on a card. • The Help button activates context sensitive help. Table 19-2 lists the payload ethernet PM parameters. Table 19-3 lists the payload SONET PM parameters. Table 19-2 Payload Ethernet PM Parameters Payload Ethernet PM Parameters IfInOctets rxTotalPkts ifInUcastPkts ifInMulticastPkts ifInBroadcastPkts ifInErrors ifOutOctets txTotalPkts ifOutUcastPkts ifOutMulticastPkts ifOutBroadcastPkts dot3StatsAlignmentErrors dot3StatsFCSErrors dot3StatsFrameTooLong etherStatsUndersizePkts etherStatsFragments etherStatsPkts64Octets etherStatsPkts65to127Octets etherStatsPkts128to255Octets etherStatsPkts256to511Octets etherStatsPkts512to1023Octets etherStatsPkts1024to1518Octets etherStatsBroadcastPkts etherStatsMulticastPkts etherStatsOversizePkts etherStatsJabbers etherStatsOctets Table 19-3 Payload SONET PM Parameters Payload SONET PM Parameters Definition 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). Up to eight section BIP errors can be detected per STS-N frame; each error increments the current CV-S second register. 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. SES-S Section Severely Errored Seconds (SES-S) is a count of the seconds when K (see Telcordia GR-253 for value) or more section-layer BIP errors were detected or an SEF or LOS defect was present. 19-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring TNC Card Performance Monitoring Table 19-4 lists the payload SDH PM parameters. SEFS-S Severely Errored Framing Seconds (SEFS-S) is a count of the seconds when an SEF defect was present. An SEF defect is expected to be present during most seconds when an LOS or loss of frame (LOF) defect is present. However, there can be situations when the SEFS-S parameter is only incremented based on the presence of the SEF defect. CV-L Line Coding Violation (CV-L) indicates the number of coding violations occurring on the line. This parameter is a count of bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the accumulation period. ES-L Line Errored Seconds (ES-L) is a count of the seconds containing one or more anomalies (BPV + EXZ) and/or defects (that is, loss of signal) on the line. SES-L Line Severely Errored Seconds (SES-L) is a count of the seconds containing more than a particular quantity of anomalies (BPV + EXZ > 44) and/or defects on the line. UAS-L Line Unavailable Seconds (UAS-L) is a count of the seconds when the line is unavailable. A line becomes unavailable when ten consecutive seconds occur that qualify as SES-Ls, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-Ls. FC-L Line Failure Count (FC-L) is a count of the number of near-end line failure events. A failure event begins when an Alarm Indication Signal Line (AIS-L) failure is declared or when a lower-layer, traffic-related, near-end failure is declared. This failure event ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period where it begins. Table 19-3 Payload SONET PM Parameters Payload SONET PM Parameters Definition19-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring TNC Card Performance Monitoring 19.2.3 RMONs Supported by TNC Card Table 19-5 lists the full RMON statistics that are supported by the TNC card. Table 19-4 Payload SDH PM Parameters Payload SONET PM Parameters Definition EB Errored block indicates that one or more bits are in error within a block. BBE Background block error shows the number of background block errors recorded during the PM time interval. ES Errored Seconds shows the number of errored seconds recorded during the PM time interval. SES Severely Errored Seconds shows the severely errored seconds recorded during the PM time interval. UAS Unavailable Seconds shows the unavailable seconds recorded during the PM time interval. ESR Errored Seconds Ratio shows the severely errored seconds ratio recorded during the PM time interval. SESR Severely Errored Seconds Ratio shows the severely errored seconds ratio recorded during the PM time interval. BBER Background Block Errors Ratio shows the background block errors ratio recorded during the PM time interval. Table 19-5 Full RMON Statistics on TNC Card Full RMON Statistics ifInOctets rxTotalPkts ifInUcastPkts ifInMulticastPkts ifInBroadcastPkts ifInErrors ifOutOctets txTotalPkts ifOutMulticastPkts ifOutBroadcastPkts dot3StatsAlignmentErrors dot3StatsFCSErrors dot3StatsFrameTooLong etherStatsUndersizePkts etherStatsFragments etherStatsPkts64Octets etherStatsPkts65to127Octets etherStatsPkts128to255Octets etherStatsPkts256to511Octets etherStatsPkts512to1023Octets etherStatsPkts1024to1518Octets etherStatsBroadcastPkts etherStatsMulticastPkts etherStatsOversizePkts etherStatsJabbers etherStatsOctets19-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring 19.3 Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring This section lists PM parameters for transponder cards (TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L), muxponder cards (MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME-C, MXP_MR_10DME-L, and 40G-MXP-C), Xponder cards (GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP), and ADM-10G card. The transponder, muxponder, Xponder, and ADM-10G PM parameters are divided into Optics PM, Payload PM, and OTN PM tabs. The tabs displayed vary depending on the card installed. For more information, see the “19.3.1 Optics PM Window” section on page 19-9, the “19.3.2 Payload PM Window” section on page 19-10, or the “19.3.3 OTN PM Window” section on page 19-17. Note For the OTU2_XP card, if the PPM is not deleted properly from the CTC (but physically removed), the PMs continue to increase (even if the PPM is not present). To ensure the PMs do not increase when the PPM is not present, change the Service State of the PPM port to OOS (ANSI) or locked (ETSI) and move it back to IS (ANSI) or Unlocked (ETSI) state. For ONS 15454 ANSI nodes, Figure 19-1 shows where overhead bytes detected on the application-specific integrated circuits (ASICs) produce PM parameters for the TXP_MR_10G card. The remaining transponder, muxponder, Xponder, and ADM-10G cards perform similarly to this illustration.19-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Figure 19-1 ONS 15454 ANSI Node PM Read Points for TXP_MR_10G Card For ONS 15454 ETSI nodes, Figure 19-2 shows where overhead bytes detected on the ASICs produce PM parameters for the TXP_MR_10G card. The remaining transponder, muxponder, Xponder, and ADM-10G cards perform similarly to this illustration. ONS 15454 TXP Card ASIC SONET PMs CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L Client PMs 90329 OTN G.709 PMs BBE-SM ES-SM SES-SM UAS-SM FC-SM ESR-SM SESR-SM BBER-SM BBE-PM ES-PM SES-PM UAS-PM FC-PM ESR-PM SESR-PM BBER-PM OTN FEC PMs Bit Errors Uncorrectable Word PMs read on trunk Client Tx/Rx Sonet 10GE Optics PMs Trunk Tx/Rx Optics PMs CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L19-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Figure 19-2 ONS 15454 ETSI Node PM Read Points on TXP_MR_10G Cards 19.3.1 Optics PM Window The Optics PM window lists parameters at the trunk and client side for all transponder, muxponder, Xponder (GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP), and ADM-10G cards. The Optics PM window provides buttons to change the statistical values shown. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. In the Historical PM subtab, the Clear button sets the values on the card to zero. All counters on the card are cleared. The Help button activates context sensitive help. Table 19-6 lists the trunk-side and client-side optics PM parameters. ONS 15454 SDH TXP Card ASIC SDH PMs RS-ES RS-ESR RS-SES RS-SESR RS-BBE RS-BBER RS-UAS RS-EB MS-ES MS-ESR MS-SES MS-SESR MS-BBE MS-BBER MS-UAS MS-EB Client PMs 110724 OTN G.709 PMs BBE-SM ES-SM SES-SM UAS-SM FC-SM ESR-SM SESR-SM BBER-SM BBE-PM ES-PM SES-PM UAS-PM FC-PM ESR-PM SESR-PM BBER-PM OTN FEC PMs Bit Errors Corrected Uncorrectable Word PMs read on trunk Client Tx/Rx SDH 10GE Optics PMs Trunk Tx/Rx Optics PMs RS-ES RS-ESR RS-SES RS-SESR RS-BBE RS-BBER RS-UAS RS-EB MS-ES MS-ESR MS-SES MS-SESR MS-BBE MS-BBER MS-UAS MS-EB19-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring 19.3.2 Payload PM Window The Payload PM window subtabs change depending on the card provisioning. For more information about provisioning TXP, MXP, and Xponder cards, refer to the “Provision Transponder and Muxponder Cards” chapter in the Cisco ONS 15454 DWDM Procedure Guide. Possible Payload PM subtabs are: SONET, SDH, Statistics, Utilization, and History. The following buttons function the same on all of the tabs. Not all tabs have all of these buttons. • The Refresh button manually refreshes statistics. • Auto-Refresh sets a time interval at which automatic refresh occurs. • The Baseline button resets the displayed statistics values to zero. • (Statistics window only) The Clear button allows you to set the values to zero for displayed statistics, all statistics for a port, and all statistics for all optical ports on a card. Table 19-6 Trunk-Side and Client-Side Optics PM Parameters Trunk-Side/Client-Side Optics PM Parameters Definition Laser Bias (Avg,%) Average Laser Bias Current (Laser Bias Avg) is the average percentage of laser bias current during the PM time interval. Laser Bias (Max,%) Maximum Laser Bias Current (Laser Bias Max) is the maximum percentage of laser bias current during the PM time interval. Laser Bias (Min,%) Minimum Laser Bias Current (Laser Bias Min) is the minimum percentage of laser bias current during the PM time interval. Link Status Indicates if the Fibre Channel link is receiving a valid Fibre Channel signal (carrier) from the attached Fibre Channel device. Up means present, and down means not present. Rx Optical Pwr (Min,dBm) Minimum Receive Optical Power (Rx Optical Pwr Min, dBm) is the minimum received optical power during the PM time interval. Rx Optical Pwr (Avg,dBm) Average Receive Optical Power (Rx Optical Pwr Avg, dBm) is the average received optical power during the PM time interval. Rx Optical Pwr (Max,dBm) Maximum Receive Optical Power (Rx Optical Pwr Max, dBm) is the maximum received optical power during the PM time interval. Tx Optical Pwr (Min,dBm)1 1. On the trunk side, this PM is not available for the following cards: TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, and MXPP_MR_2.5G. Minimum Transmit Optical Power (Tx Optical Pwr Min, dBm) is the minimum optical power transmitted during the PM time interval. Tx Optical Pwr (Avg,dBm)1 Average Transmit Optical Power (Tx Optical Pwr Avg, dBm) is the average optical power transmitted during the PM time interval. Tx Optical Pwr (Max,dBm)1 Maximum Transmit Optical Power (Tx Optical Pwr Max, dBm) is the maximum optical power transmitted during the PM time interval. 19-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring • The Help button activates context sensitive help. For a list of the payload PM provisioning options for all transponder, muxponder, and Xponder cards, refer to the Cisco ONS 15454 DWDM Procedure Guide. The options selected in the Provisioning tab can affect the parameters displayed in the Performance > Payload PM tab. Table 19-7 lists the PM parameter types that appear when a particular port type is provisioned for a transponder or muxponder card. 19.3.2.1 Payload PM SONET/SDH Window Table 19-8 lists SONET/SDH layer near-end and far-end PM parameters listed in the card view on the Performance > Payload PM > SONET or SDH tab. SONET/SDH layer PMs are available when the client type is set to OC3/STM1, OC12/STM4, or OC48/STM16 on the TXP_MR_2.5G or when OC192/STM64 is set on the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, ADM-10G, or OTU2_XP card on ONS 15454 SONET nodes or ONS 15454 SDH nodes. OC48/STM16 trunk PMs are available on MXP_MR_2.5G and MXPP_MR_2.5G cards on ONS 15454 SONET or ONS 15454 SDH nodes. OC48/STM16 client PMs are available on MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, and MXP_2.5G_10E_L cards on ONS 15454 SONET or ONS 15454 SDH nodes. Table 19-7 Transponder, Muxponder, and Xponder Port Type PM Provisioning Options If this Port Type is Provisioned1 1. The port type is provisioned from card view on the Provisioning > Pluggable Port Modules tab. For pluggable port module (PPM) provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. The Following PM Types are Activated2 2. Performance monitoring parameters are displayed from the card view on the Performance tab. SONET/SDH (including 10G Ethernet WAN Phy) OC3/STM1 OC12/STM4 OC48/STM16 OC192/STM64 SONET or SDH PMs 40G Ethernet LAN Phy 10G Ethernet LAN Phy 10G FiberChannel 8G FiberChannel ONE_GE FC1G FC2G FC1G ISL FC2G ISL FICON1G FICON2G FICON1G ISL FICON2G ISL ISC COMPAT ISC PEER Full remote monitoring (RMON) statistics ESCON DV6000 SDI_D1_VIDEO HDTV PASS_THRU ETR_CLO Payload PMs are not applicable to 2R port types.19-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring OC192/STM64 client PMs are available on 40G-MXP-C card on ONS 15454 SONET or ONS 15454 SDH nodes. For PM definitions, see Table 19-36 on page 19-34 and Table 19-37 on page 19-35. 19.3.2.2 Payload PM Statistics Window Table 19-8 lists the 10 Gigabit Ethernet (10 GE) payload statistics that are available on the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, ADM-10G, and OTU2_XP cards. PPM provisioning must be completed in card view, on the Provisioning > Pluggable Port Modules tab for 10 GE to be enabled. For PPM provisioning procedures, see the Cisco ONS 15454 DWDM Procedure Guide. The parameters are listed in card view on the Performance > Payload PM > Statistics tab. For 10 GE payload definitions, see Table 19-34 on page 19-30. Note Utilization PMs are also available per port. Table 19-8 ONS 15454 SONET/SDH Layer Far-End and Near-End PMs SONET Layer Far-End (FE)1, 2 1. Applicable to optical channel (OCH) and Client (CLNT) facilities. 2. For MXP_MR_2.5G and MXPP_MR_2.5G cards, these parameters are shown in the Performance > Payload PM > SONET PM tabs in the card view. Layer Near-End1, 2 Note CV-LFE ES-LFE FC-LFE SES-LFE UAS-LFE CV-L CV-S ES-L ES-S FC-L SES-L SES-S SEF-S UAS-L Applicable standard is Telcordia GR-253. SDH MS-BBE MS-BBER MS-EB MS-ES MS-ESR MS-SES MS-SESR MS-UAS RS-BBE RS-BBER RS-EB RS-ES RS-ESR RS-SES RS-SESR RS-UAS MS-BBE MS-BBER MS-EB MS-ES MS-ESR MS-SES MS-SESR MS-UAS Applicable standard is Telcordia GR-253.19-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Table 19-10 lists the payload statistics that are available on the ADM-10G card. The parameters are listed in card view on the Performance > Payload PM > Statistics tab. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. Table 19-9 Full RMON Statistics on TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP Cards Full RMON Statistics dot3StatsFCSErrors dot3StatsFrameTooLong ifInUcastPkts ifInBroadcastPkts ifInErrors ifInErrorsBytePkts ifInFramingErrorPkts ifInJunkInterPkts ifInMulticastPkts ifInOctets ifOutBroadcastPkts ifOutMulticastPkts ifOutOctets rxTotalPkts Time Last Cleared txTotalPkts etherStatsBroadcastPkts etherStatsCRCAlignErrors etherStatsFragments etherStatsJabbers etherStatsMulticastPkts etherStatsOctets etherStatsOversizePkts etherStatsPkts64Octets etherStatsPkts65to127Octets etherStatsPkts128to255Octets etherStatsPkts256to511Octets etherStatsPkts512to1023Octets etherStatsPkts1024to1518Octets etherStatsUndersizePkts rxControlFrames rxPauseFrames rxUnknownOpcodeFrames Table 19-10 Full RMON Statistics on ADM-10G Card Full RMON Statistics dot3StatsFCSErrors dot3StatsFrameTooLong dot3StatsInPauseFrames dot3StatsOutPauseFrames dot3StatsControlInUnknownOpCodes ifInMulticastPkts ifInBroadcastPkts ifInErrors ifInErrorsBytePkts ifInOctets ifOutOctets rxTotalPkts txTotalPkts ifInErrors gfpStatsRxCRCErrors gfpStatsRxSBitErrors ifInPayloadCrcErrors gfpStatsLFDRaisedgfpStatsRxFrame gfpStatsTxOctets gfpStatsRxMBitErrors gfpStatsRxTypeInvalid etherStatsBroadcastPkts etherStatsFragments etherStatsJabbers etherStatsMulticastPkts etherStatsOversizePkts etherStatsPkts64Octets etherStatsPkts65to127Octets etherStatsPkts128to255Octets etherStatsPkts256to511Octets etherStatsPkts512to1023Octets etherStatsPkts1024to1518Octets etherStatsUndersizePkts19-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Table 19-11 lists the payload PM parameters that are available on the TXP_MR_2.5G and the TXPP_MR_2.5G cards when the ONE_GE or FC1G client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27 and the “19.7 Full RMON Statistics PM Parameter Definitions” section on page 19-30. Note Payload PM is not available for the 2FC client type. Table 19-12 lists the payload PM parameters that are available on the OTU2_XP card when the 10G FC client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27 and the “19.7 Full RMON Statistics PM Parameter Definitions” section on page 19-30. For payload definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27 and the “19.7 Full RMON Statistics PM Parameter Definitions” section on page 19-30. Table 19-13 lists the payload PM parameters that are available on the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the ONE_GE or the FC1G client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27 and the “19.7 Full RMON Statistics PM Parameter Definitions” section on page 19-30. Table 19-11 Gigabit Ethernet (GE) or Fibre Channel (FC) Payload PMs for the TXP_MR_2.5G and TXPP_MR_2.5G Cards GE or FC Payload Performance Parameters 8b/10bDataOrderedSets 8b/10bIdleOrderedSets 8b/10bNonIdleOrderedSets 8b/10bStatsEncodingDispErrors ifInErrors rxTotalPkts Table 19-12 10G Fibre Channel (FC) Payload PMs for the OTU2_XP Card 10G FC Payload Performance Parameters rxTotalPkts mediaIndStatsRxFramesTruncated mediaIndStatsRxFramesTooLong mediaIndStatsRxFrameBadCRC ifInOctects ifInErros19-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Table 19-14 lists the FC client-side payload PM parameters. FC payload PMs are available on the FC port on both the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the FC1G client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the “19.7 Full RMON Statistics PM Parameter Definitions” section on page 19-30. Table 19-15 lists the Transparent Generic Framing Procedure (GFP-T) payload PMs. The GFP-T payload PMs are available on the GFP port on both the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the ONE_GE or the 1 FC client type is enabled. GFP-T payload PMs are also available on the client port on both the MXP_MR_2.5G and the MXPP_MR_2.5G cards when the 1 FC client type is enabled. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. For payload definitions, see the “19.7 Full RMON Statistics PM Parameter Definitions” section on page 19-30. Table 19-13 ONE_GE or FC1G Payload PMs for the MXP_MR_2.5G and MXPP_MR_2.5G Cards ONE_GE or FC1G Payload Performance Parameters 8b10bInvalidOrderedSets 8b10bStatsEncodingDispErrors ifInDiscards ifInErrors ifInOctets ifOutDiscards ifOutOctets mediaIndStatsRxFramesBadCRC mediaIndStatsRxFramesTooLong mediaIndStatsRxFramesTruncated mediaIndStatsTxFramesBadCRC rxTotalPkts txTotalPkts Table 19-14 FC1G Payload PMs on the Client Side FC1G Payload PMs on the Client Port fcStatsLinkRecoveries fcStatsRxCredits fcStatsTxCredits fcStatsZeroTxCredits gfpStatsRoundTripLatencyUSec gfpStatsRxDistanceExtBuffers gfpStatsTxDistanceExtBuffers19-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring 19.3.2.3 MXP_MR_2.5G/MXPP_MR_2.5G Payload Utilization Window The Payload PM Utilization window in the card view Performance > Payload> Utilization tab shows the percentage of transmit (Tx) and receive (Rx) line bandwidth used by the ports during consecutive time segments. This tab cannot be viewed unless the appropriate PPM port type is provisioned. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. The Utilization window provides an Interval list that enables you to set time intervals of 15 minutes or 1 day. Line utilization is calculated with the following formulas: Rx = (inOctets + inPkts * 20) * 8 / 100% interval * maxBaseRate Tx = (outOctets + outPkts * 20) * 8 / 100% interval * maxBaseRate The interval is defined in seconds. The maxBaseRate is defined by raw bits per second in one direction for the port (that is, 1 Gbps). The maxBaseRate for MXP_MR_2.5G and MXPP_MR_2.5G cards is shown for the ONS 15454 nodes in Table 19-16. Note Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity. Table 19-15 GFP-T Payload PMs GFP-T Payload PMs on the GFP Port gfpStatsCSFRaised gfpStatsLFDRaised gfpStatsRxCRCErrors gfpStatsRxMBitErrors gfpStatsRxSBitErrors gfpStatsRxTypeInvalid gfpStatsRxFrame gfpStatsTxFrame gfpStatsRxSblkCRCErrors gfpStatsRxOctets gfpStatsTxOctets gfpRxCmfFrame gfpTxCmfFrame Table 19-16 maxBaseRate for STS and VC Circuits STS/VC maxBaseRate STS-1/VC3 51840000 STS-3c/VC4 155000000 STS-6c/VC4-2c 311000000 STS-12c/VC4-4c 62200000019-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring 19.3.2.4 Payload History Window The Payload PM History window in the card view Performance > Payload > History tab lists past statistics for the previous time intervals. This tab cannot be viewed unless the appropriate PPM port type is provisioned. For PPM provisioning procedures, refer to the Cisco ONS 15454 DWDM Procedure Guide. 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 19-17. 19.3.3 OTN PM Window The OTN tab has an ITU-T G.709 PM subtab and an FEC PM subtab. Both subtabs provide buttons to change the statistical values shown in the Performance tab. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval at which automatic refresh occurs. The Baseline button resets the displayed statistics values to zero. The Statistics window also has a Clear button. The Clear button sets the values on the card to zero. All counters on the card are cleared. The Help button activates context sensitive help. For more information about provisioning optical transport network (OTN) settings, refer to the Cisco ONS 15454 DWDM Procedure Guide. Table 19-18 lists the OTN PM provisioning options for all transponder, muxponder, Xponder (GE_XP, 10GE_XP, GE_XPE, 10GE_XPE), and ADM-10G cards. The options selected in the Provisioning tab affects the parameters displayed in the Performance > OTN PM tab. Table 19-17 History Statistics per Time Interval Time Interval Number of Intervals Displayed 15 minutes 32 (current and previous) 1 day (24 hours) 2 (current and previous) Table 19-18 Transponder, Muxponder, and Xponder PM Provisioning Options Card OTN Provisioning1 MXPP_MR_2.5G — MXP_2.5G_10E G.709 FEC FEC Thresholds MXP_2.5G_10E_C G.709 FEC FEC Thresholds MXP_2.5G_10E_L G.709 FEC FEC Thresholds MXP_2.5G_10G G.709 FEC FEC Thresholds MXP_MR_2.5G — MXP_MR_10DME_C G.709 FEC FEC Thresholds19-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring MXP_MR_10DME_L G.709 FEC FEC Thresholds 40G-MXP-C G.709 FEC Thresholds Trail Trace Identifier TXPP_MR_2.5G G.709 FEC FEC Thresholds TXP_MR_10E G.709 FEC FEC Thresholds TXP_MR_10E_C G.709 FEC FEC Thresholds TXP_MR_10E_L G.709 FEC FEC Thresholds TXP_MR_10G G.709 FEC FEC Thresholds TXP_MR_2.5G G.709 FEC FEC Thresholds ADM-10G G.709 FEC FEC Thresholds GE_XP G.709 FEC FEC Thresholds 10GE_XP G.709 FEC FEC Thresholds GE_XPE G.709 FEC FEC Thresholds 10GE_XPE G.709 FEC FEC Thresholds OTU2_XP G.709 FEC FEC Thresholds 1. OTN provisioning is performed from card view on the Provisioning > OTN > OTN Lines, G.709 Thresholds, and FEC Thresholds tabs. Table 19-18 Transponder, Muxponder, and Xponder PM Provisioning Options (continued) Card OTN Provisioning119-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Table 19-19 lists the OTN trunk-side PM parameters listed on the G.709 tab. OTN PMs are available when ITU G.709 is enabled from the card view Provisioning > OTN > OTN Lines tab. OTN PMs are not available on MXP_MR_2.5G and MXPP_MR_2.5G cards. For ITU G.709 section and path monitoring PM definitions, see the “19.6 ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions” section on page 19-28. Table 19-20 lists the forward error correction (FEC) PM parameters. FEC PMs are available when ITU-T G.709 is enabled and FEC is set to standard or enhanced. These parameters are provisioned from the card view Provisioning > OTN > OTN Lines tab. FEC PMs are not available on MXP_MR_2.5G and MXPP_MR_2.5G cards. For PM definitions, see the “19.8 FEC PM Parameter Definitions” section on page 19-33. Table 19-21 lists ONS 15454 optics and 8b10b PM parameters. For ONS 15454 optics and 8b10b definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. Table 19-19 ITU G.709 OTN Trunk-Side PMs OTN Layer (Near End and Far End)1 1. Applicable to OCH facility. Note BBE-SM BBER-SM ES-SM ESR-SM FC-SM SES-SM SESR-SM UAS-SM FC-SM ITU G.709 standard section monitoring ITU-T G.8021 BBE-PM BBER-PM ES-PM ESR-PM FC-PM SES-PM SESR-PM UAS-PM ITU G.709 standard path monitoring ITU-T G.8021 Table 19-20 FEC OTN Trunk-Side PMs FEC Trunk-Side PMs FEC (Near End)1 1. Applicable to OCH facility. Bit Errors BIT-EC Uncorrectable Words UNC-WORDS19-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring 19.3.4 Ether Ports PM Window CTC provides Ethernet port performance information, including line-level parameters, port bandwidth consumption, and historical Ethernet statistics. The Ethernet performance information is divided into the Statistics, Utilization, and History tabbed windows within the card view Performance tab window. For more information about provisioning ether ports, refer to the Cisco ONS 15454 DWDM Procedure Guide. 19.3.4.1 Ether Port Statistics Window The Ethernet 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. Table 19-22 defines the Ethernet Port statistics parameters. Table 19-21 ONS 15454 Optics and 8b10b PMs Optics (Near End)1 1. The TXP_MR_2.5G and TXPP_MR_2.5G card Enterprise System Connection (ESCON) payload does not support optics PMs on the client port due to Small Form-factor Pluggable (SFP)-imposed restrictions. 8B10B (Near End)2 2. Applicable to TXP_MR_2.5G and TXPP_MR_2.5G cards only. LBCL-AVG LBCL-MAX LBCL-MIN OPT-AVG OPT-MAX OPT-MIN OPR-AVG OPR-MAX OPR-MIN CGV DCG IOS IPC NIOS VPC Table 19-22 E-Series Ethernet Statistics Parameters Parameter Definition Time Last Cleared A time stamp indicating the last time statistics were reset. ifInOctets Number of bytes received since the last counter reset. rxTotalPkts Number of received packets. ifInUcastPkts Number of unicast packets received since the last counter reset. ifInMulticastPkts Number of multicast packets received since the last counter reset. ifInDiscards The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free buffer space. ifOutOctets Number of bytes transmitted since the last counter reset. txTotalPkts Number of transmitted packets. 19-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring ifOutMulticastPkts Number of multicast packets transmitted. ifOutBroadcastPkts Number of broadcast packets transmitted. ifOutDiscards Number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their transmission. A possible reason for discarding such packets could be to free up buffer space. ifOurErrors Number of outbound packets or transmission units that could not be transmitted because of errors. 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. dot3StatsFrameTooLong A count of frames received on a particular interface that exceed the maximum permitted frame size. 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. etherStatsFragments The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Note It is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits. etherStatsPkts64Octets The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets). etherStatsPkts65to127Oct ets The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). etherStatsPkts128to255O ctets The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). etherStatsPkts256to511O ctets The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). etherStatsPkts512to1023 Octets The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). etherStatsPkts1024to1518 Octets The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). etherStatsBroadcastPkts The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets. Table 19-22 E-Series Ethernet Statistics Parameters (continued) Parameter Definition19-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring Note In certain congestion scenarios in GE_XP and 10GE_XP cards, dropped packets are counted both in ingress (IfIndiscards) and egress interface (IfOutDiscards) interface. As a result of this, some dropped packets are counted twice. The dropped packets on ingress interface can be ignored under this scenario. 19.3.4.2 Ether Ports 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. However, if the E-Series port is set to autonegotiate the mode (Auto), this field shows the result of the link negotiation between the E-Series and the peer Ethernet device attached directly to the E-Series port. The Utilization window provides an Interval drop-down list that enables you to set time intervals of 1 minute, 15 minutes, 1 hour, and 1 day. Line utilization is calculated with the following formulas: Rx = (inOctets + inPkts * 20) * 8 / 100% interval * maxBaseRate Tx = (outOctets + outPkts * 20) * 8 / 100% interval * maxBaseRate The interval is defined in seconds. The maxBaseRate is defined by raw bits per second in one direction for the Ethernet port (that is, 1 Gbps). 19.3.4.3 Ether Ports History Window The Ether Port 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 19-23. The parameters are defined in Table 19-22 on page 19-20. etherStatsMulticastPkts 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. etherStatsOversizePkts The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. Note that for tagged interfaces, this number becomes 1522 bytes. etherStatsJabbers The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). etherStatsOctets The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets. etherStatsCRCAlignError s The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error). Table 19-22 E-Series Ethernet Statistics Parameters (continued) Parameter Definition19-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring DWDM Card Performance Monitoring 19.4 DWDM Card Performance Monitoring The following sections define PM parameters and definitions for the ONS 15454 OPT-PRE, OPT-BST, OPT-BST-L, OPT-AMP-L, OPT-AMP-17-C, 32MUX-O, 32DMX-O, 32DMX, 32DMX-L, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 40-DMX-C, 40-DMX-CE, 40-MUX-C, 40-SMR1-C, 40-SMR2-C, 4MD-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x, OSCM, OSC-CSM, 32WSS, and 32WSS-LDWDM cards. 19.4.1 Optical Amplifier Card Performance Monitoring Parameters The PM parameters for the OPT-PRE, OPT-AMP-L, OPT-AMP-17-C, OPT-BST, and OPT-BST-L cards are listed Table 19-24. For ONS 15454 optics definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. 19.4.2 Multiplexer and Demultiplexer Card Performance Monitoring Parameters The PM parameters for the 32MUX-O, 32WSS, 32WSS-L, 32DMX, 32DMX-L, 32DMX-O, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 40-DMX-C, 40-DMX-CE, 40-MUX-C, 40-SMR1-C, and 40-SMR2-C cards are listed in Table 19-25. For ONS 15454 optics definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. 19.4.3 4MD-xx.x Card Performance Monitoring Parameters The PM parameters for the 4MD-xx.x cards are listed in Table 19-26. For ONS 15454 optics definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. Table 19-23 Ethernet History Statistics per Time Interval Time Interval Number of Previous Intervals Displayed 1 minute 60 15 minutes 32 1 hour 24 1 day (24 hours) 7 Table 19-24 Optical PM Parameters for Optical Amplifier Cards Optical Line Optical Amplifier Line OPT OPR Table 19-25 Optical PM Parameters of Multiplexer and Demultiplexer Cards Optical Channel Optical Line OPR OPT19-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring DWDM Card Performance Monitoring 19.4.4 OADM Channel Filter Card Performance Monitoring Parameters The PM parameters for the AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x cards are listed in Table 19-27. For ONS 15454 optics definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. 19.4.5 OADM Band Filter Card Performance Monitoring Parameters The PM parameters for the AD-1B-xx.x and AD-4B-xx.x cards are listed in Table 19-28. For ONS 15454 optics definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. 19.4.6 Optical Service Channel Card Performance Monitoring Parameters For ONS 15454 ANSI nodes, Figure 19-3 shows where overhead bytes detected on the ASICs produce PM parameters for the OSCM and OSC-CSM cards. Table 19-26 Optical PM Parameters for 4MD-xx.x Cards Optical Channel Optical Band OPR OPT Table 19-27 Optical PM Parameters for AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards Optical Channel Optical Line OPR OPT Table 19-28 Optical PM Parameters for AD-1B-xx.x and AD-4B-xx.x Cards Optical Line Optical Band OPR OPT19-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring DWDM Card Performance Monitoring Figure 19-3 ONS 15454 ANSI Node PM Read Points on OSCM and OSC-CSM Cards For ONS 15454 ETSI nodes, Figure 19-4 shows where overhead bytes detected on the ASICs produce PM parameters for the OSCM and OSC-CSM cards. ONS Node OSCM/OSC-CSM OCEAN ASIC DCN to TCC2 OSC (OC-3) 2EOW to AIC Other Overhead FE 100BaseT CV-S ES-S SES-S SEFS-S CV-L ES-L SES-L UAS-L FC-L PMs read on OCEAN ASIC 9665019-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring DWDM Card Performance Monitoring Figure 19-4 ONS 15454 ETSI Node PM Read Points on OSCM and OSC-CSM Cards The ONS 15454 ANSI node PM parameters for the OSCM and OSC-CSM cards are listed in Table 19-29. For PM definitions, see the “19.9 SONET PM Parameter Definitions” section on page 19-34. For optics PM definitions, see the “19.5 Optics and 8b10b PM Parameter Definitions” section on page 19-27. ONS SDH Node OSCM/OSC-CSM OCEAN ASIC DCN to TCC2 OSC (STM-1) 2EOW to AIC Other Overhead FE 100BaseT RS-EB RS-BBE RS-ES RS-SES MS-EB MS-BBE MS-ES MS-SES MS-UAS PMs read on OCEAN ASIC 96708 Table 19-29 ANSI OSCM/OSC-CSM (OC3) Card PMs Section (Near End)1 1. Applicable to OC3 Line (Near End/Far End)1 Optics (Near End)2 2. Applicable to OTS facilities CV-S ES-S SEF-S SES-S CV-L ES-L FC-L SES-L UAS-L OPWR Table 19-30 ETSI OSCM and OSC-CSM Card PMs Regeneration Section (Near End) Multiplex Section (Near End/Far End) Optics (Near End) RS-BBE RS-EB RS-ES RS-SES MS-BBE MS-EB MS-ES MS-SES MS-UAS OPT19-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Optics and 8b10b PM Parameter Definitions 19.5 Optics and 8b10b PM Parameter Definitions Table 19-31 on page 19-27 lists Cisco ONS 15454 optics and 8b10b PM parameter definitions. Table 19-31 ONS 15454 Optics and 8b10b PM Parameter Definitions Parameter Definition 8b10bDataOrderedSets 8b10b takes 8 bits of data and sends it as 10 bits, which allows control information to be sent along with the data. DataOrderedSets is a count of data ordered sets. 8b10bErrors 8b10b takes 8 bits of data and sends it as 10 bits, which allows control information to be sent along with the data. Errors is a count of 10b errors received by the serial or deserializer (serdes 8b/10b). 8b10bIdleOrderedSets 8b10b takes 8 bits of data and sends it as 10 bits, which allows control information to be sent along with the data. IdleOrderedSets is a count of idle ordered sets. 8b10bInvalidOrderedSets 8b10b takes 8 bits of data and sends it as 10 bits, which allows control information to be sent along with the data. InvalidOrderedSets is a count of the received invalid work errors. 8b10bNonIdleOrderedSets 8b10b takes 8 bits of data and sends it as 10 bits, which allows control information to be sent along with the data. NonIdleOrderedSets is a count of ordered sets that are not idle. 8b10bStatsEncodingDispErrors 8b10b takes 8 bits of data and sends it as 10 bits, which allows control information to be sent along with the data. StatsEncodingDispErrors is a count of the received disparity errors. BIE The number of bit errors (BIE) corrected in the DWDM trunk line during the PM time interval. BIT-EC The number of Bit Errors Corrected (BIT-EC) in the DWDM trunk line during the PM time interval. CGV Code Group Violations (CGV) is a count of received code groups that do not contain a start or end delimiter. DCG Date Code Groups (DCG) is a count of received data code groups that do not contain ordered sets. IOS Idle Ordered Sets (IOS) is a count of received packets containing idle ordered sets. IPC Invalid Packets (IPC) is the count of received packets that contain errored data code groups that have start and end delimiters. LBCL-AVG Laser Bias Current Line-Average (LBCL-AVG) is the average percentage of laser bias current. LBCL-MAX Laser Bias Current Line-Maximum (LBCL-MAX) is the maximum percentage of laser bias current. LBCL-MIN Laser Bias Current Line-Minimum (LBCL-MIN) is the minimum percentage of laser bias current.19-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions 19.6 ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions Table 19-34 defines the ITU G.709 and ITU-T G.8021 section monitoring trunk-side PM parameters. For more information, see the “19.3 Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring” section on page 19-7. LOFC Loss of Frame Count (LOFC) is a count of the lost frames. NIOS Non-Idle Ordered Sets (NIOS) is a count of received packets containing non-idle ordered sets. OPR Optical Power Received (OPR) is the measure of average optical power received as a percentage of the nominal OPR. OPR-AVG Average Receive Optical Power (OPR-AVG) is the average received optical power measured in dBm. OPR-MAX Maximum Receive Optical Power (OPR-MAX) is the maximum received optical power measured in dBm. OPR-MIN Minimum Receive Optical Power (OPR-MIN) is the minimum received optical power measured in dBm. OPT Optical Power Transmitted (OPT) is the average optical power transmitted as a percentage of the nominal OPT. OPT-AVG Average Transmit Optical Power (OPT-AVG) is the average transmitted optical power measured in dBm. OPT-MAX Maximum Transmit Optical Power (OPT-MAX) is the maximum transmitted optical power measured in dBm. OPT-MIN Minimum Transmit Optical Power (OPT-MIN) is the minimum transmitted optical power measured in dBm. OPWR-AVG Optical Power - Average (OPWR-AVG) is the measure of average optical power on the unidirectional port. OPWR-MAX Optical Power - Maximum (OPWR-MAX) is the measure of maximum value of optical power on the unidirectional port. OPWR-MIN Optical Power - Minimum (OPWR-MIN) is the measure of minimum value of optical power on the unidirectional port. UNC-WORDS Uncorrectable Words (UNC-WORDS) is the number of uncorrectable words detected in the DWDM trunk line during the PM time interval. VPC Valid Packets (VPC) is a count of received packets that contain non-errored data code groups that have start and end delimiters. Table 19-31 ONS 15454 Optics and 8b10b PM Parameter Definitions (continued) Parameter Definition19-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring ITU G.709 and ITU-T G.8021 Trunk-Side PM Parameter Definitions Table 19-33 defines the ITU G.709 path monitoring trunk-side PM parameters. For more information, see the “19.3 Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring” section on page 19-7. Table 19-32 ITU G.709 and ITU-T G.8021 Section Monitoring PM Definitions Parameter Definition BBE-SM Section Monitoring Background Block Errors (BBE-SM) shows the number of background block errors recorded in the OTN section during the PM time interval. BBER-SM Section Monitoring Background Block Errors Ratio (BBER-SM) shows the background block errors ratio recorded in the OTN path during the PM time interval. ES-SM Section Monitoring Errored Seconds (ES-SM) shows the errored seconds recorded in the OTN section during the PM time interval. ESR-SM Section Monitoring Errored Seconds Ratio (ESR-SM) shows the severely errored seconds ratio recorded in the OTN section during the PM time interval. FC-SM Section Monitoring Failure Counts (FC-SM) shows the failure counts recorded in the OTN section during the PM time interval. SES-SM Section Monitoring Severely Errored Seconds (SES-SM) shows the severely errored seconds recorded in the OTN section during the PM time interval. SESR-SM Section Monitoring Severely Errored Seconds Ratio (SESR-SM) shows the severely errored seconds ratio recorded in the OTN section during the PM time interval. UAS-SM Section Monitoring Unavailable Seconds (UAS-SM) shows the unavailable seconds recorded in the OTN section during the PM time interval. Table 19-33 ITU G.709 Path Monitoring PM Definitions Parameter Definition BBE-PM Path Monitoring Background Block Errors (BBE-PM) shows the number of background block errors recorded in the OTN path during the PM time interval. BBER-PM Path Monitoring Background Block Errors Ratio (BBER-PM) shows the background block errors ratio recorded in the OTN path during the PM time interval. ES-PM Path Monitoring Errored Seconds (ES-PM) shows the errored seconds recorded in the OTN path during the PM time interval. ESR-PM Path Monitoring Errored Seconds Ratio (ESR-PM) shows the severely errored seconds ratio recorded in the OTN path during the PM time interval. FC-PM Path Monitoring Failure Counts (FC-PM) shows the failure counts recorded in the OTN path during the PM time interval.19-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Full RMON Statistics PM Parameter Definitions 19.7 Full RMON Statistics PM Parameter Definitions Table 19-34 defines the MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and 40G-MXP-C card full RMON statistics PM parameters. For more information, see the “19.3 Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring” section on page 19-7. SES-PM Path Monitoring Severely Errored Seconds (SES-PM) shows the severely errored seconds recorded in the OTN path during the PM time interval. SESR-PM Path Monitoring Severely Errored Seconds Ratio (SESR-PM) shows the severely errored seconds ratio recorded in the OTN path during the PM time interval. UAS-PM Path Monitoring Unavailable Seconds (UAS-PM) shows the unavailable seconds recorded in the OTN path during the PM time interval. Table 19-33 ITU G.709 Path Monitoring PM Definitions (continued) Parameter Definition Table 19-34 Full RMON Statistics PM Definitions Parameter Definition dot3StatsFCSErrors The number of frames with frame check errors. dot3StatsFrameTooLong The number of packets at least 64 octets long, without a bad Frame Check Sequence (FCS), where the 802.3 length/type field did not match the computed DATA field length. etherStatsBroadcastPkts The number of broadcast packets, excluding multicast packets, that are 64–16376 octets in length, and have a valid FCS. etherStatsCRCAlignErrors The number of packets that are 64–1518 octets in length without an integral number of octets, or with a bad FCS. etherStatsFragments The number of packets less than 64 octets long that do not have an integral number of octets or that have a bad FCS. etherStatsJabbers The number of octets of data, including bad packets, that were received on the network. etherStatsMulticastPkts The number of multicast packets, excluding broadcast packets, that are 64–16376 octets in length, and have a valid FCS. etherStatsOctets The number in bytes of received packets, including bad packets and excluding framing bits except for FCS bytes. etherStatsOversizePkts The number of packets more than 16376 octets long that have a valid FCS. etherStatsPkts64Octets The number of packet received, including error packets, that are 64 octets in length. etherStatsPkts65to127Octets The number of packets received, including error packets, that are 65–127 octets in length.19-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Full RMON Statistics PM Parameter Definitions etherStatsPkts128to255Octets The number of packets received, including error packets, that are 128–255 octets in length. etherStatsPkts256to511Octets The number of packets received, including error packets, that are 256–511 octets in length. etherStatsPkts512to1023Octets The number of packets received, including error packets, that are 512–1023 octets in length. etherStatsPkts1024to1518Octets The number of packets received, including error packets, that are 1024–1518 octets in length. etherStatsUndersizePkts The number of packets less than 64 octets long that have a valid FCS. fcStatsLinkRecoveries The number of link recoveries. fcStatsRxCredits The number of current receive buffer to buffer credits. fcStatsTxCredits The number of current transmit buffer to buffer credits. fcStatsZeroTxCredits This is a count that increments when the FC/FICON Tx credits go from a nonzero value to zero. gfpStatsLFDRaised The number of loss of frame delineation (LFD) raised. gfpStatsRoundTripLatencyUSec Round trip delay for the end-to-end Fibre Channel transport in microseconds. gfpStatsRxCRCErrors The number of packets received with a payload FCS error. gfpStatsRxCSFRaised Received GFP loss of client character synchronization (LOCCS). gfpStatsRxDistanceExtBuffers The number of receive buffer credit for GFP-T (valid only if distance extension is enabled). gfpStatsRxMBitErrors The received multibit errored core header count (cHEC). gfpStatsRxSBitErrors The received single-bit errored cHEC. gfpStatsRxSblkCRCErrors The number of packets received with a payload FCS error. Sblk stands for super block in the GFP payload. gfpStatsRxTypeInvalid Received invalid type. gfpStatsTxDistanceExtBuffers The number of transmit buffer credit for GFP-T (valid only if distance extension is enabled). ifInUcastPkts The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. inInMulticastPkts The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. ifInBroadcastPkts The number of packets delivered to a higher sublayer and addressed to a broadcast address at this sublayer. Table 19-34 Full RMON Statistics PM Definitions (continued) Parameter Definition19-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Full RMON Statistics PM Parameter Definitions ifInDiscards The number of inbound packets that were chosen to be discarded even though no errors were detected, to prevent them from being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free buffer space. ifInErrors The number of inbound packets (or transmission units) that contained errors preventing them from being delivered to a higher-layer protocol. ifInErrorBytePkts The number of received packets with an error symbol detected. ifInFramingErrorPkts The number of received packets with a control symbol other than an error detected. ifInJunkInterPkts The number of interpacket gaps between valid start symbols during which a symbol other than idle is detected, including packets of length 1–8 octets. ifInMulticastPkts The total number of multicast frames received error-free. ifInOctets The number of bytes received since the last counter reset. ifOutBroadcastPkts The number of packets requested by higher-level protocols and addressed to a broadcast address at this sublayer, including those not transmitted. ifOutDiscards The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free buffer space. ifOutMulticastPkts The number of multicast frames transmitted error-free. ifOutOctets The number of bytes transmitted since the last counter reset. InvalidCRCError A count of invalid cyclic redundancy checks (CRCs). mediaIndStatsRxFramesBadCRC The number of received frames with a CRC error. mediaIndStatsRxFramesTooLong The number of received frames that are too long. mediaIndStatsRxFramesTruncated The number of received frames that are too small. mediaIndStatsTxFramesBadCRC The number of transmitted frames with a CRC error. Running Disparity Count A count of errors that affect the disparity of the received data stream. rxControlFrames The number of MAC control packets that are type 0x8808 and contain at least 64 octets in length. rxFrames A count of the number of frames received without errors. rxLinkReset (Only for FC Mode) A count of the received link resets. rxPauseFrames The number of received 802.x paused frames. rxTotalPkts The number of received packets. rxUnknownOpcodeFrames Number of packets of at least 64 octets in length and type 0x8808, with opcode not equal to 1. Time Last Cleared A time stamp indicating the last time statistics were reset. Table 19-34 Full RMON Statistics PM Definitions (continued) Parameter Definition19-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring FEC PM Parameter Definitions 19.8 FEC PM Parameter Definitions Table 19-35 defines the MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L card FEC PM parameters. For more information, see the “19.3 Transponder, Muxponder, Xponder, and ADM-10G Card Performance Monitoring” section on page 19-7. txBytes A count of the number of bytes transmitted from the frame since the last counter reset. txFrames A count of the number of transmitted frames. txTotalPkts The number of transmitted packets. 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. dot3StatsFrameTooLong A count of frames received on a particular interface that exceed the maximum permitted frame size. dot3StatsInPauseFrames A count of frames received on this interface with an opcode indicating the PAUSE operation. dot3StatsOutPauseFrames A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. 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. mediaIndStatsTxFramesTooLong Total number of transmitted data frames that are less than 5 bytes. This value is a part of HDLC and GFP port statistics. mediaIndStatsTxFramesTruncated Number of transmitted data frames that exceed the MTU. This value is part of HDLC and GFP port statistics. gfpStatsRxFrame Total number of received data frames. gfpStatsTxFrame Total number of transmitted data frames. gfpStatsRxOctets Total number of GFP data octets received. gfpStatsTxOctets Total number of GFP data octets transmitted. gfpRxCmfFrame — gfpTxCmfFrame — Table 19-34 Full RMON Statistics PM Definitions (continued) Parameter Definition19-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring SONET PM Parameter Definitions 19.9 SONET PM Parameter Definitions Table 19-36 gives definitions for each type of SONET PM parameter available on an ONS 15454 ANSI node. These parameters become available when the client type is set to OC-3, OC-12, or OC-48 on a TXP_MR_2.5G or TXPP_MR_2.5G card, OC-192 on a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or ADM-10G card. The OC-48 client PM is available on MXP_2.5_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_10DME_C, and MXP_MR_10DME_L cards. The OC-48 trunk PM is available on MXP_MR_2.5G and MXPP_MR_2.5G cards. Table 19-35 FEC PM Definitions Parameter Definition Bit Errors Bit Errors are the number of bit errors corrected. FEC (NE) FEC enables correction and detection of errors along the optical links where OTN and FEC are provisioned. FEC uses Reed Solomon code RS (255,239) encoding. The FEC field is found in Rows 1 to 4 and Columns 3835 to 4080. It will contain either the Reed-Solomon RS(255,239) codes, or if FEC is disabled, fixed stuff bytes (zeros). Note The FEC PM information can be found in the card view Performance > OTN PM tab. FEC must be enabled on the transponder units in order for FEC PM values to be reported. UNC-Words Uncorrectable Words (UNC-Words) occur when FEC detects and corrects errors to deliver a 7 to 8 dB improvement in the signal-to-noise ratio (also called margin). For ITU G.709, the FEC code used is Reed-Solomon RS (255, 239). Table 19-36 SONET PM Parameters Parameter Definition CV-L Line Coding Violation (CV-L) indicates the number of coding violations occurring on the line. This parameter is a count of bipolar violations (BPVs) and excessive zeros (EXZs) occurring over 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). Up to eight section BIP errors can be detected per STS-N frame; each error increments the current CV-S second register. ES-L Line Errored Seconds (ES-L) is a count of the seconds containing one or more anomalies (BPV + EXZ) and/or defects (that is, loss of signal) on the line. 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.19-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring SDH PM Parameter Definitions 19.10 SDH PM Parameter Definitions Table 19-37 gives definitions for each type of SDH PM parameter available on an ONS 15454 ETSI node. These parameters become available when the client type is set to STM-1, STM-4, or STM-16 on a TXP_MR_2.5G or TXPP_MR_2.5G card, STM-64 on a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or ADM-10G card. The STM-16 client PM is available on MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_MR_10DME_C, and MXP_MR_10DME_L cards. The STM-16 trunk PM is available on MXP_MR_2.5G and MXPP_MR_2.5G cards. FC-L Line Failure Count (FC-L) is a count of the number of near-end line failure events. A failure event begins when an Alarm Indication Signal Line (AIS-L) failure is declared or when a lower-layer, traffic-related, near-end failure is declared. This failure event ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period where it begins. SEF-S Severely Errored Framing Seconds (SEFS-S) is a count of the seconds when an SEF defect was present. An SEF defect is expected to be present during most seconds when an LOS or loss of frame (LOF) defect is present. However, there can be situations when the SEFS-S parameter is only incremented based on the presence of the SEF defect. Note The RTRV-PM- command does not retrieve SEFS counter for OC192/STM64 payloads on ADM-10G, 40G/40E (TXP/MXP), and OTU2-XP cards. SES-L Line Severely Errored Seconds (SES-L) is a count of the seconds containing more than a particular quantity of anomalies (BPV + EXZ > 44) and/or defects on the line. SES-S Section Severely Errored Seconds (SES-S) is a count of the seconds when K (see Telcordia GR-253 for value) or more section-layer BIP errors were detected or an SEF or LOS defect was present. UAS-L Line Unavailable Seconds (UAS-L) is a count of the seconds when the line is unavailable. A line becomes unavailable when ten consecutive seconds occur that qualify as SES-Ls, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as SES-Ls. Table 19-36 SONET PM Parameters (continued) Parameter Definition Table 19-37 SDH PM Parameters Parameter Definition MS-BBE Multiplex Section Background Block Error (MS-BBE) is an errored block not occurring as part of an SES. MS-BBER Multiplex Section Background Block Error Ratio (MS-BBER) is the ratio of BBE to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs. MS-EB Multiplex Section Errored Block (MS-EB) indicates that one or more bits are in error within a block.19-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring SDH PM Parameter Definitions MS-ES Multiplex Section Errored Second (MS-ES) is a one-second period with one or more errored blocks or at least one defect. MS-ESR Multiplex Section Errored Second Ratio (MS-ESR) is the ratio of errored seconds to total seconds in available time during a fixed measurement interval. MS-SES Multiplex Section Severely Errored Second (MS-SES) is a one-second period that contains 30 percent or more errored blocks or at least one defect. SES is a subset of ES. For more information, refer to ITU-T G.829 Section 5.1.3. MS-SESR Multiplex Section Severely Errored Second ratio (MS-SESR) is the ratio of SES to total seconds in available time during a fixed measurement interval. MS-UAS Multiplex Section Unavailable Seconds (MS-UAS) is a count of the seconds when the section was unavailable. A section becomes unavailable when ten consecutive seconds occur that qualify as MS-SESs, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as MS-SESs. When the condition is entered, MS-SESs decrement and then count toward MS-UAS. RS-BBE Regenerator Section Background Block Error (RS-BBE) is an errored block not occurring as part of an SES. RS-BBER Regenerator Section Background Block Error Ratio (RS-BBER) is the ratio of BBE to total blocks in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs. RS-EB Regenerator Section Errored Block (RS-EB) indicates that one or more bits are in error within a block. RS-ES Regenerator Section Errored Second (RS-ES) is a one-second period with one or more errored blocks or at least one defect. RS-ESR Regenerator Section Errored Second Ratio (RS-ESR) is the ratio of errored seconds to total seconds in available time during a fixed measurement interval. RS-SES Regenerator Section Severely Errored Second (RS-SES) is a one-second period which contains 30 percent or more errored blocks or at least one defect. SES is a subset of ES. RS-SESR Regenerator Section Severely Errored Second Ratio (RS-SESR) is the ratio of SES to total seconds in available time during a fixed measurement interval. RS-UAS Regenerator Section Unavailable Second (RS-UAS) is a count of the seconds when the regenerator section was unavailable. A section becomes unavailable when ten consecutive seconds occur that qualify as RS-UASs, and it continues to be unavailable until ten consecutive seconds occur that do not qualify as RS-UASs. Table 19-37 SDH PM Parameters (continued) Parameter Definition19-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Pointer Justification Count Performance Monitoring 19.11 Pointer Justification Count Performance Monitoring For the MultiService Transport Platform (MSTP), only the MXP_2.5G_10G card uses pointer justification counts. Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on networks. When a network is out of synchronization, jitter and wander occur on the transported signal. Excessive wander can cause terminating equipment to slip. Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses the encryption key, causing data to be transmitted again. For ONS 15454 ANSI nodes, pointers provide a way to align the phase variations in STS and VT payloads. The STS payload pointer is located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE) called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss. For ONS 15454 ETSI nodes, pointers provide a way to align the phase variations in VC4 payloads. The VC4 payload pointer is located in the H1 and H2 bytes of the AU pointers section and is a count of the number of bytes the VC4 path overhead (POH) J1 byte is away from the H3 byte, not including the section overhead bytes. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the VC4 POH called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss. There are positive (PPJC) and negative (NPJC) pointer justification count parameters. PPJC is a count of path-detected (PPJC-PDET-P) or path-generated (PPJC-PGEN-P) positive pointer justifications. NPJC is a count of path-detected (NPJC-PDET-P) or path-generated (NPJC-PGEN-P) negative pointer justifications depending on the specific PM name. PJCDIFF is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. PJCS-PDET-P is a count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P is a count of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN. A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means that the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. For ONS 15454 SONET nodes, positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS-1. For ONS 15454 SDH nodes, positive pointer adjustments occur when the frame rate of the path overhead (POH) is too slow in relation to the rate of the VC4. In CTC, the count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the card view Provisioning tab.19-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 19 Performance Monitoring Pointer Justification Count Performance MonitoringCHAPTER 20-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 20 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 DWDM Procedure Guide. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. Chapter topics include: • 20.1 SNMP Overview, page 20-1 • 20.2 Basic SNMP Components, page 20-3 • 20.3 SNMP External Interface Requirement, page 20-4 • 20.4 SNMP Version Support, page 20-4 • 20.5 SNMP Message Types, page 20-5 • 20.6 SNMP Management Information Bases, page 20-6 • 20.7 SNMP Trap Content, page 20-15 • 20.8 SNMPv1/v2 Community Names, page 20-22 • 20.9 SNMP in Multishelf Management, page 20-22 • 20.10 SNMPv1/v2 Proxy Over Firewalls, page 20-24 • 20.11 SNMPv3 Proxy Configuration, page 20-25 • 20.12 Remote Monitoring, page 20-25 20.1 SNMP Overview SNMP is an application-layer communication protocol that allows ONS 15454 network devices to exchange management information among these systems and with other devices outside the network. Through SNMP, network administrators can manage network performance, find and solve network problems, and plan network growth. Up to 10 SNMP trap destinations and five concurrent Cisco Transport Controller (CTC) user sessions are allowed per node. The ONS 15454 uses SNMP for asynchronous event notification to a network management system (NMS). ONS SNMP implementation uses standard Internet Engineering Task Force (IETF) management information bases (MIBs) to convey node-level inventory, fault, and performance management 20-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Overview information for generic DS-1, DS-3, SONET, and Ethernet read-only management. SNMP allows a generic SNMP manager such as HP OpenView Network Node Manager (NNM) or Open Systems Interconnection (OSI) NetExpert to be utilized for limited management functions. The Cisco ONS 15454 supports SNMP Version 1 (SNMPv1), SNMP Version 2c (SNMPv2c), and SNMP Version 3 (SNMPv3). As compared to SNMPv1, SNMPv2c includes additional protocol operations and 64-bit performance monitoring support. SNMPv3 provides authentication, encryption, and message integrity and is more secure. This chapter describes the SNMP versions and describes the configuration parameters for the ONS 15454. Note In Software Release 8.0 and later, you can retrieve automatic in service (AINS) state and soak time through the SNMP and Transaction Language One (TL1) interfaces. Note The CERENT-MSDWDM-MIB.mib, CERENT-FC-MIB.mib, and CERENT-GENERIC-PM-MIB.mib in the CiscoV2 directory support 64-bit performance monitoring counters. The SNMPv1 MIB in the CiscoV1 directory does not contain 64-bit performance monitoring counters, but supports the lower and higher word values of the corresponding 64-bit counter. The other MIB files in the CiscoV1 and CiscoV2 directories are identical in content and differ only in format. 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 of what and number of hops in the node, etc. The SNMP management interface supports the IEEE 802.3 LAG MIB. Figure 20-1 illustrates the basic layout idea of an SNMP-managed network. Figure 20-1 Basic Network Managed by SNMP 5258220-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Basic SNMP Components 20.2 Basic SNMP Components In general terms, an SNMP-managed network consists of a management system, agents, and managed devices. A management system such as HP OpenView executes monitoring applications and controls managed devices. Management systems execute most of the management processes and provide the bulk of memory resources used for network management. A network might be managed by one or several management systems. Figure 20-2 illustrates the relationship between the network manager, the SNMP agent, and the managed devices. Figure 20-2 Example of the Primary SNMP Components 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. Figure 20-3 illustrates SNMP agent get-requests that transport data to the network management software. Management Entity Agent Management Database Agent NMS Management Database Managed Devices Agent Management Database 3393020-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP External Interface Requirement Figure 20-3 Agent Gathering Data from a MIB and Sending Traps to the Manager The SNMP agent captures data from MIBs, which are device parameter and network data repositories, or from error or change traps. A managed element—such as a router, access server, switch, bridge, hub, computer host, or network element (such as an ONS 15454)—is accessed through the SNMP agent. Managed devices collect and store management information, making it available through SNMP to other management systems having the same protocol compatibility. 20.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 can upload RFC 3273 SNMP MIB variables in the etherStatsHighCapacityTable, etherHistoryHighCapacityTable, or mediaIndependentTable. 20.4 SNMP Version Support The ONS 15454 supports SNMPv1 and SNMPv2c traps and get requests. The ONS 15454 SNMP MIBs define alarms, traps, and status. Through SNMP, NMS applications can query a management agent for data from functional entities such as Ethernet switches and SONET multiplexers using a supported MIB. Note ONS 15454 MIB files in the CiscoV1 and CiscoV2 directories are almost identical in content except for the difference in 64-bit performance monitoring features. The CiscoV2 directory contains three MIBs with 64-bit performance monitoring counters:. CERENT-MSDWDM-MIB.mib, CERENT-FC-MIB.mib, and CERENT-GENERIC-PM-MIB.mib The CiscoV1 directory does not contain any 64-bit counters, but it does support the lower and higher word values used in 64-bit counters. The two directories also have somewhat different formats. 20.4.1 SNMPv3 Support Cisco ONS 15454 Software R9.0 and later supports SNMPv3 in addition to SNMPv1 and SNMPv2c. SNMPv3 is an interoperable standards-based protocol for network management. SNMPv3 provides secure access to devices by a combination of authentication and encryption packets over the network based on the User Based Security Model (USM) and the View-Based Access Control Model (VACM). • User-Based Security Model—The User-Based Security Model (USM) uses the HMAC algorithm for generating keys for authentication and privacy. SNMPv3 authenticates data based on its origin, and ensures that the data is received intact. SNMPv1 and v2 authenticate data based on the plain text community string, which is less secure when compared to the user-based authentication model. get, get-next, get-bulk Network device get-response, traps 32632 SNMP Manager NMS MIB SNMP Agent20-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Message Types • View-Based Access Control Model—The view-based access control model controls the access to the managed objects. RFC 3415 defines the following five elements that VACM comprises: – Groups—A set of users on whose behalf the MIB objects can be accessed. Each user belongs to a group. The group defines the access policy, notifications that users can receive, and the security model and security level for the users. – Security level—The access rights of a group depend on the security level of the request. – Contexts—Define a named subset of the object instances in the MIB. MIB objects are grouped into collections with different access policies based on the MIB contexts. – MIB views—Define a set of managed objects as subtrees and families. A view is a collection or family of subtrees. Each subtree is included or excluded from the view. – Access policy—Access is determined by the identity of the user, security level, security model, context, and the type of access (read/write). The access policy defines what SNMP objects can be accessed for reading, writing, and creating. Access to information can be restricted based on these elements. Each view is created with different access control details. An operation is permitted or denied based on the access control details. You can configure SNMPv3 on a node to allow SNMP get and set access to management information and configure a node to send SNMPv3 traps to trap destinations in a secure way. SNMPv3 can be configured in secure mode, non-secure mode, or disabled mode. SNMP, when configured in secure mode, only allows SNMPv3 messages that have the authPriv security level. SNMP messages without authentication or privacy enabled are not allowed. When SNMP is configured in non-secure mode, it allows SNMPv1, SNMPv2, and SNMPv3 message types. 20.5 SNMP Message Types The ONS 15454 SNMP agent communicates with an SNMP management application using SNMP messages. Table 20-1 describes these messages. Table 20-1 ONS 15454 SNMP Message Types Operation Description get-request Retrieves a value from a specific variable. get-next-request Retrieves the value following the named variable; this operation is often used to retrieve variables from within a table. With this operation, an SNMP manager does not need to know the exact variable name. The SNMP manager searches sequentially to find the needed variable from within the MIB. get-response Replies to a get-request, get-next-request, get-bulk-request, or set-request sent by an NMS. get-bulk-request Fills the get-response with up to the max-repetition number of get-next interactions, similar to a get-next-request. set-request Provides remote network monitoring (RMON) MIB. trap Indicates that an event has occurred. An unsolicited message is sent by an SNMP agent to an SNMP manager.20-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases 20.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. 20.6.1 IETF-Standard MIBs for the ONS 15454 Table 20-2 lists the IETF-standard MIBs implemented in the ONS 15454 SNMP agents. First compile the MIBs in Table 20-2, then compile the MIBs in Table 20-3. Caution If you do not compile MIBs in the correct order, one or more might not compile correctly. Table 20-2 IETF Standard MIBs Implemented in the ONS 15454 System RFC1 Number Module Name Title/Comments — IANAifType-MIB.mib Internet Assigned Numbers Authority (IANA) ifType 1213 RFC1213-MIB-rfc1213.mib Management Information Base for Network 1907 SNMPV2-MIB-rfc1907.mib Management of TCP/IP-based Internets: MIB-II Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) 1253 RFC1253-MIB-rfc1253.mib OSPF Version 2 Management Information Base 1493 BRIDGE-MIB-rfc1493.mib Definitions of Managed Objects for Bridges (This defines MIB objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network [LAN] segments.) 2819 RMON-MIB-rfc2819.mib Remote Network Monitoring Management Information Base 2737 ENTITY-MIB-rfc2737.mib Entity MIB (Version 2) 2233 IF-MIB-rfc2233.mib Interfaces Group MIB using SNMPv2 2358 EtherLike-MIB-rfc2358.mib Definitions of Managed Objects for the Ethernet-like Interface Types 2493 PerfHist-TC-MIB-rfc2493.mib Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals 2495 DS1-MIB-rfc2495.mib Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types 2496 DS3-MIB-rfc2496.mib Definitions of Managed Object for the DS3/E3 Interface Type 2558 SONET-MIB-rfc2558.mib Definitions of Managed Objects for the SONET/SDH Interface Type 2674 P-BRIDGE-MIB-rfc2674.mib Q-BRIDGE-MIB-rfc2674.mib Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions 20-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases 20.6.2 Proprietary ONS15454 MIBs Each ONS 15454 is shipped with a software CD containing applicable proprietary MIBs. Table 20-3 lists the proprietary MIBs for the ONS 15454. 3273 HC-RMON-MIB The MIB module for managing remote monitoring device implementations, augmenting the original RMON MIB as specified in RFC 2819 and RFC 1513 and RMON-2 MIB as specified in RFC 2021 CISCO-DOT3-OAM-MIB A Cisco proprietary MIB defined for IEEE 802.3ah ethernet OAM. 3413 SNMP-NOTIFICATION-MIB Defines the MIB objects that provide mechanisms to remotely configure the parameters used by an SNMP entity for generating notifications. 3413 SNMP-TARGET-MIB Defines the MIB objects that provide mechanisms to remotely configure the parameters that are used by an SNMP entity for generating SNMP messages. 3413 SNMP-PROXY-MIB Defines MIB objects that provide mechanisms to remotely configure the parameters used by a proxy forwarding application. 3414 SNMP-USER-BASED-SM-MIB The management information definitions for the SNMP User-Based Security Model. 3415 SNMP-VIEW-BASED-ACM-M IB The management information definitions for the View-Based Access Control Model for SNMP. 1. RFC = Request for Comment Table 20-2 IETF Standard MIBs Implemented in the ONS 15454 System (continued) RFC1 Number Module Name Title/Comments Table 20-3 ONS 15454 Proprietary MIBs MIB Number Module Name 1 CERENT-GLOBAL-REGISTRY.mib 2 CERENT-TC.mib 3 CERENT-454.mib 4 CERENT-GENERIC.mib (not applicable to ONS 15454) 5 CISCO-SMI.mib 6 CISCO-VOA-MIB.mib 7 CERENT-MSDWDM-MIB.mib 8 CERENT-OPTICAL-MONITOR-MIB.mib 9 CERENT-HC-RMON-MIB.mib 10 CERENT-ENVMON-MIB.mib 11 CERENT-GENERIC-PM-MIB.mib 20-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases 12 BRIDGE-MIB.my 13 CERENT-454-MIB.mib 14 CERENT-ENVMON-MIB.mib 15 CERENT-FC-MIB.mib 16 CERENT-GENERIC-MIB.mib 17 CERENT-GENERIC-PM-MIB.mib 18 CERENT-GLOBAL-REGISTRY.mib 19 CERENT-HC-RMON-MIB.mib 20 CERENT-IF-EXT-MIB.mib 21 CERENT-MSDWDM-MIB.mib 22 CERENT-OPTICAL-MONITOR-MIB.mib 23 CERENT-TC.mib 24 CISCO-IGMP-SNOOPING-MIB.mib 25 CISCO-OPTICAL-MONITOR-MIB.mib 26 CISCO-OPTICAL-PATCH-MIB.mib 27 CISCO-SMI.mib 28 CISCO-VOA-MIB.mib 29 CISCO-VTP-MIB.mib 30 INET-ADDRESS-MIB.mib 31 OLD-CISCO-TCP-MIB.my 32 OLD-CISCO-TS-MIB.my 33 RFC1155-SMI.my 34 RFC1213-MIB.my 35 RFC1315-MIB.my 36 BGP4-MIB.my 37 CERENT-454-MIB.mib 38 CERENT-ENVMON-MIB.mib 39 CERENT-FC-MIB.mib 40 CERENT-GENERIC-MIB.mib 41 CERENT-GENERIC-PM-MIB.mib 42 CERENT-GLOBAL-REGISTRY.mib 43 CERENT-HC-RMON-MIB.mib 44 CERENT-IF-EXT-MIB.mib 45 CERENT-MSDWDM-MIB.mib 46 CERENT-OPTICAL-MONITOR-MIB.mib Table 20-3 ONS 15454 Proprietary MIBs MIB Number Module Name20-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases 47 CERENT-TC.mib 48 CISCO-CDP-MIB.my 49 CISCO-CLASS-BASED-QOS-MIB.my 50 CISCO-CONFIG-COPY-MIB.my 51 CISCO-CONFIG-MAN-MIB.my 52 CISCO-ENTITY-ASSET-MIB.my 53 CISCO-ENTITY-EXT-MIB.my 54 CISCO-ENTITY-VENDORTYPE-OID-MI 55 CISCO-FRAME-RELAY-MIB.my 56 CISCO-FTP-CLIENT-MIB.my 57 CISCO-HSRP-EXT-MIB.my 58 CISCO-HSRP-MIB.my 59 CISCO-IGMP-SNOOPING-MIB.mib 60 CISCO-IMAGE-MIB.my 61 CISCO-IP-STAT-MIB.my 62 CISCO-IPMROUTE-MIB.my 63 CISCO-MEMORY-POOL-MIB.my 64 CISCO-OPTICAL-MONITOR-MIB.mib 65 CISCO-OPTICAL-PATCH-MIB.mib 66 CISCO-PING-MIB.my 67 CISCO-PORT-QOS-MIB.my 68 CISCO-PROCESS-MIB.my 69 CISCO-PRODUCTS-MIB.my 70 CISCO-RTTMON-MIB.my 71 CISCO-SMI.mib 72 CISCO-SMI.my 73 CISCO-SYSLOG-MIB.my 74 CISCO-TC.my 75 CISCO-TCP-MIB.my 76 CISCO-VLAN-IFTABLE-RELATIONSHI 77 CISCO-VOA-MIB.mib 78 CISCO-VTP-MIB.mib 79 CISCO-VTP-MIB.my 80 ENTITY-MIB.my 81 ETHERLIKE-MIB.my Table 20-3 ONS 15454 Proprietary MIBs MIB Number Module Name20-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases 82 HC-PerfHist-TC-MIB.my 83 HC-RMON-MIB.my 84 HCNUM-TC.my 85 IANA-RTPROTO-MIB.my 86 IANAifType-MIB.my 87 IEEE-802DOT17-RPR-MIB.my 88 IEEE8023-LAG-MIB.my 89 IF-MIB.my 90 IGMP-MIB.my 91 INET-ADDRESS-MIB.my 92 IPMROUTE-STD-MIB.my 93 OSPF-MIB.my 94 PIM-MIB.my 95 RMON-MIB.my 96 RMON2-MIB.my 97 SNMP-FRAMEWORK-MIB.my 98 SNMP-NOTIFICATION-MIB.my 99 SNMP-TARGET-MIB.my 100 SNMPv2-MIB.my 101 SNMPv2-SMI.my 102 SNMPv2-TC.my 103 TCP-MIB.my 104 TOKEN-RING-RMON-MIB.my 105 UDP-MIB.my 106 BRIDGE-MIB-rfc1493.mib 107 DS1-MIB-rfc2495.mib 108 DS3-MIB-rfc2496.mib 109 ENTITY-MIB-rfc2737.mib 110 EtherLike-MIB-rfc2665.mib 111 HC-RMON-rfc3273.mib 112 HCNUM-TC.mib 113 IANAifType-MIB.mib 114 IF-MIB-rfc2233.mib 115 INET-ADDRESS-MIB.mib 116 P-BRIDGE-MIB-rfc2674.mib Table 20-3 ONS 15454 Proprietary MIBs MIB Number Module Name20-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases Note If you cannot compile the proprietary MIBs correctly, log into the Technical Support Website at http://www.cisco.com/techsupport or call Cisco TAC (800) 553-2447. Note When SNMP indicates that the wavelength is unknown, it means that the corresponding card (MXP_2.5G_10E, TXP_MR_10E, MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G) works with the first tunable wavelength. For more information about MXP and TXP cards, see Chapter 10, “Transponder and Muxponder Cards.” 20.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. The MIB objects can be used to obtain threshold values, current performance monitoring (PM) counts, and historic PM statistics for each kind of monitor and any supported interval at the near end and far end. Previously existing MIBs in the ONS 15454 system provide some of these counts. For example, SONET interface 15-minute current PM counts and historic PM statistics are available using the SONET-MIB. DS-1 and DS-3 counts and statistics are available through the DS1-MIB and DS-3 MIB respectively. The 117 PerfHist-TC-MIB-rfc2493.mib 118 Q-BRIDGE-MIB-rfc2674.mib 119 RFC1213-MIB-rfc1213.mib 120 RFC1253-MIB-rfc1253.mib 121 RIPv2-MIB-rfc1724.mib 122 RMON-MIB-rfc2819.mib 123 RMON2-MIB-rfc2021.mib 124 RMONTOK-rfc1513.mib 125 SNMP-FRAMEWORK-MIB-rfc2571.mib 126 SNMP-MPD-MIB.mib 127 SNMP-NOTIFY-MIB-rfc3413.mib 128 SNMP-PROXY-MIB-rfc3413.mib 129 SNMP-TARGET-MIB-rfc3413.mib 130 SNMP-USER-BASED-SM-MIB-rfc3414.mib 131 SNMP-VIEW-BASED-ACM-MIB-rfc3415.mib 132 SNMPv2-MIB-rfc1907.mib 133 SONET-MIB-rfc2558.mib Table 20-3 ONS 15454 Proprietary MIBs MIB Number Module Name20-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases generic MIB provides these types of information and also fetches threshold values and single-day statistics. In addition, the MIB supports optics and dense wavelength division multiplexing (DWDM) threshold and performance monitoring information. The CERENT-GENERIC-PM-MIB is organized into three different tables: • cerentGenericPmThresholdTable • cerentGenericPmStatsCurrentTable • cerentGenericPmStatsIntervalTable The cerentGenericPmThresholdTable is used to obtain the threshold values for the monitor types. It is indexed based on the following items: • Interface index (cerentGenericPmThresholdIndex) • Monitor type (cerentGenericPmThresholdMonType). The syntax of cerentGenericPmThresholdMonType is type cerentMonitorType, defined in CERENT-TC.mib. • Location (cerentGenericPmThresholdLocation). The syntax of cerentGenericPmThresholdLocation is type cerentLocation, defined in CERENT-TC.mib. • Time period (cerentGenericPmThresholdPeriod). The syntax of cerentGenericPmThresholdPeriod is type cerentPeriod, defined in CERENT-TC.mib. Threshold values can be provided in 64-bit and 32-bit formats. (For more information about 64-bit counters, see the “20.12.2 HC-RMON-MIB Support” section on page 20-27.) The 64-bit values in cerentGenericPmThresholdHCValue can be used with agents that support SNMPv2. The two 32-bit values (cerentGenericPmThresholdValue and cerentGenericPmThresholdOverFlowValue) can be used by NMSs that only support SNMPv1. Due to the 64-bit counter, the negative values for cerentGenericPmThresholdHCValue are displayed as large positive integers. If the cerentGenericPmThresholdOverFlowValue is less than zero, it indicates that the cerentGenericPmThresholdHCValue is representing a negative value. The objects compiled in the cerentGenericPmThresholdTable are shown in Table 20-4. The second table within the MIB, cerentGenericPmStatsCurrentTable, compiles the current performance monitoring (PM) values for the monitor types. The table is indexed based on interface index (cerentGenericPmStatsCurrentIndex), monitor type (cerentGenericPmStatsCurrentMonType), location (cerentGenericPmStatsCurrentLocation) and time period (cerentGenericPmStatsCurrentPeriod). The 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. The cerentGenericPmStatsCurrentTable validates the current PM value using the cerentGenericPmStatsCurrentValid object and registers the number of valid intervals with historical PM statistics in the cerentGenericPmStatsCurrentValidIntervals object. Table 20-4 cerentGenericPmThresholdTable Index Objects Information Objects cerentGenericPmThresholdIndex cerentGenericPmThresholdValue cerentGenericPmThresholdMonType cerentGenericPmThresholdOverFlowValue cerentGenericPmThresholdLocation cerentGenericPmThresholdHCValue cerentGenericPmThresholdPeriod —20-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases PM values are provided in 64-bit and 32-bit formats. The 64-bit values in cerentGenericPmStatsCurrentHCValue can be used with agents that support SNMPv2. The two 32-bit values (cerentGenericPmStatsCurrentValue and cerentGenericPmStatsCurrentOverFlowValue) can be used by NMS that only support SNMPv1. Due to the 64-bit counter, the negative values for cerentGenericPmStatsCurrentHCValue are displayed as large positive integers. If the cerentGenericPmStatsCurrentOverFlowValue is less than zero, it indicates that the cerentGenericPmStatsCurrentHCValue is representing a negative value. The cerentGenericPmStatsCurrentTable is shown in Table 20-5. The third table in the MIB, cerentGenericPmStatsIntervalTable, obtains historic PM values for the monitor types. It validates the current PM value in the cerentGenericPmStatsIntervalValid object. This table is indexed based on interface index (cerentGenericPmStatsIntervalIndex), monitor type (cerentGenericPMStatsIntervalMonType), location (cerentGenericPmStatsIntervalLocation), and period (cerentGenericPmStatsIntervalPeriod). The syntax of cerentGenericPmStatsIntervalIndex is type cerentLocation, defined in CERENT-TC.mib. The syntax of cerentGenericPmStatsIntervalMonType is type cerentMonitor, defined in CERENT-TC.mib. The syntax of cerentGernicPmStatsIntervalPeriod is type cerentPeriod, defined in CERENT-TC.mib. The table provides historic PM values in 64-bit and 32-bit formats. The 64-bit values contained in the cerentGenericPmStatsIntervalHCValue table can be used with SNMPv2 agents. The two 32-bit values (cerentGenericPmStatsIntervalValue and cerentGenericPmStatsIntervalOverFlowValue) can be used by SNMPv1 NMS. Due to the 64-bit counter, the negative values for cerentGenericPmStatsIntervalHCValue are displayed as large positive integers. If the cerentGenericPmStatsIntervalOverFlowValue is less than zero, it indicates that the cerentGenericPmStatsIntervalHCValue is representing a negative value. The cerentGenericPmStatsIntervalTable is shown in Table 20-6. Table 20-5 32-Bit cerentGenericPmStatsCurrentTable Index Objects Informational Objects cerentGenericPmStatsCurrentIndex cerentGenericPmStatsCurrentValue cerentGenericPmStatsCurrentMonType cerentGenericPmStatsCurrentOverFlowValue cerentGenericPmStatsCurrentLocation cerentGenericPmStatsCurrentHCValue cerentGenericPmStatsCurrentPeriod cerentGenericPmStatsCurrentValidData — cerentGenericPmStatsCurrentValidIntervals Table 20-6 32-Bit cerentGenericPmStatsIntervalTable Index Objects Informational Objects cerentGenericPmStatsIntervalIndex cerentGenericPmStatsIntervalValue cerentGenericPmStatsIntervalMonType cerentGenericPmStatsIntervalOverFlowValue cerentGenericPmStatsIntervalLocation cerentGenericPmStatsIntervalHCValue cerentGenericPmStatsIntervalPeriod cerentGenericPmStatsIntervalValidData cerentGenericPmStatsIntervalNumber —20-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Management Information Bases 20.6.4 MIBs Supported in GE-XP, 10GE-XP, GE-XPE, 10GE-XPE Cards A comprehensive list of supported MIBs for the GE-XP, 10GE-XP, GE-XPE, and 10GE-XPE cards can be found in the MIBs README.txt file. You can also locate and download MIBs for Cisco platforms, Cisco IOS releases, and feature sets, using the Cisco MIB Locator at the following URL: http://www.cisco.com/go/mibs Table 20-7 lists traps supported in GE-XP, 10GE-XP, GE-XPE, and 10GE-XPE cards 20.6.5 MIBs Supported in TNC and TSC Cards (Cisco ONS 15454 M2 and ONS 15454 M6 only) You can locate and download MIBs for Cisco platforms, Cisco IOS releases, and feature sets, using the Cisco MIB Locator at the following URL: http://www.cisco.com/go/mibs Table 20-8 lists the MIBs supported in the TNC card. Table 20-9 lists the MIBs supported in the TSC card. Table 20-7 Traps Supported in GE-XP, 10GE-XP, GE-XPE, and 10GE-XPE Cards Trap Name Description multicastMacAddressAliasing Multicast mac address aliasing multicastMacAddressTableFull Multicast mac address table full fastAutomaticProtectionSwitching Fast Automatic Protection Switching fastAutomaticProtectionSwitchingConfigMismatch Fast automatic protection switching config mismatch Table 20-8 MIBs Supported in TNC Card MIB Number MIB Module 1 CERENT-454-MIB.mib 2 CERENT-ENVMON-MIB.mib 3 CERENT-GENERIC-MIB.mib 4 CERENT-GENERIC-PM-MIB.mib 5 CERENT-OPTICAL-MONITOR-MIB.mib 6 CERENT-GENERIC-MIB.mib 7 CERENT-MSDWDM-MIB.mib Table 20-9 MIBs Supported in TSC Card MIB Number MIB Module 1 CERENT-454-MIB.mib 2 CERENT-GENERIC-MIB.mib20-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content 20.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.). • Severity and service effect of the alarm (critical, major, minor, or event; service-affecting or non-service-affecting). • Date and time stamp showing when the alarm occurred. 20.7.1 Generic and IETF Traps The ONS 15454 supports the generic IETF traps listed in Table 20-10. Table 20-10 Supported Generic IETF Traps Trap From RFC No. MIB Description coldStart RFC1907-MIB Agent up, cold start. warmStart RFC1907-MIB Agent up, warm start. authenticationFailure RFC1907-MIB Community string does not match. newRoot RFC1493/ BRIDGE-MIB Sending agent is the new root of the spanning tree. topologyChange RFC1493/ BRIDGE-MIB A port in a bridge has changed from Learning to Forwarding or Forwarding to Blocking. entConfigChange RFC2737/ ENTITY-MIB The entLastChangeTime value has changed. dsx1LineStatusChange RFC2495/ DS1-MIB The value of an instance of dsx1LineStatus has changed. The trap can be used by an NMS to trigger polls. When the line status change results from a higher-level line status change (for example, a DS-3), no traps for the DS-1 are sent. dsx3LineStatusChange RFC2496/ DS3-MIB The value of an instance of dsx3LineStatus has changed. This trap can be used by an NMS to trigger polls. When the line status change results in a lower-level line status change (for example, a DS-1), no traps for the lower-level are sent. risingAlarm RFC2819/ RMON-MIB The SNMP trap that is generated when an alarm entry crosses the rising threshold and the entry generates an event that is configured for sending SNMP traps. fallingAlarm RFC2819/ RMON-MIB The SNMP trap that is generated when an alarm entry crosses the falling threshold and the entry generates an event that is configured for sending SNMP traps.20-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content 20.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 20-11. For each group (such as Group A), all traps within the group are associated with all of its variable bindings. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description A dsx1LineStatusChange (from RFC 2495) (1) dsx1LineStatus This variable indicates the line status of the interface. It contains loopback, failure, received alarm and transmitted alarm information. (2) dsx1LineStatusLastChange The value of MIB II’s sysUpTime object at the time this DS1 entered its current line status state. If the current state was entered prior to the last proxy-agent reinitialization, the value of this object is zero. (3) cerent454NodeTime The time that an event occurred. (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. B dsx3LineStatusChange (from RFC 2496) (1) dsx3LineStatus This variable indicates the line status of the interface. It contains loopback state information and failure state information. (2) dsx3LineStatusLastChange The value of MIB II's sysUpTime object at the time this DS3/E3 entered its current line status state. If the current state was entered prior to the last reinitialization of the proxy-agent, then the value is zero. (3) cerent454NodeTime The time that an event occurred.20-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content B (cont.) (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. C coldStart (from RFC 1907) (1) cerent454NodeTime The time that the event occurred. warmStart (from RFC 1907) (2) cerent454AlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service-affecting statuses are Service-Affecting and Non-Service Affecting. newRoot (from RFC) (3) snmpTrapAddress The address of the SNMP trap. topologyChange (from RFC) — — entConfigChange (from RFC 2737) — — authenticationFailure (from RFC 1907) — — D1 risingAlarm (from RFC 2819) (1) alarmIndex This variable uniquely identifies each entry in the alarm table. When an alarm in the table clears, the alarm indexes change for each alarm listed. (2) alarmVariable The object identifier of the variable being sampled. (3) alarmSampleType The method of sampling the selected variable and calculating the value to be compared against the thresholds. (4) alarmValue The value of the statistic during the last sampling period. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description20-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content D1 (cont.) (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. A single event is also generated if the first sample after this entry is greater than or equal to this threshold. (6) cerent454NodeTime The time that an event occurred. (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. (8) snmpTrapAddress The address of the SNMP trap. D2 fallingAlarm (from RFC 2819) (1) alarmIndex This variable uniquely identifies each entry in the alarm table. When an alarm in the table clears, the alarm indexes change for each alarm listed. (2) alarmVariable The object identifier of the variable being sampled. (3) alarmSampleType The method of sampling the selected variable and calculating the value to be compared against the thresholds. (4) alarmValue The value of the statistic during the last sampling period. (5) alarmFallingThreshold When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event is generated. A single is also generated if the first sample after this entry is less than or equal to this threshold. (6) cerent454NodeTime The time that an event occurred. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description20-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content D2 (cont.) (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. (8) snmpTrapAddress The address of the SNMP trap. E failureDetectedExternal ToTheNE (from CERENT-454-mib) (1) cerent454NodeTime The time that an event occurred. (2) cerent454AlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service-affecting statuses are Service-Affecting and Non-Service Affecting. (3) cerent454AlarmObjectType The entity that raised the alarm. The NMS should use this value to decide which table to poll for further information about the alarm. (4) cerent454AlarmObjectIndex Every alarm is raised by an object entry in a specific table. This variable is the index of objects in each table; if the alarm is interface-related, this is the index of the interface in the interface table. (5) cerent454AlarmSlotNumber The slot of the object that raised the alarm. If a slot is not relevant to the alarm, the slot number is zero. (6) cerent454AlarmPortNumber The port of the object that raised the alarm. If a port is not relevant to the alarm, the port number is zero. (7) cerent454AlarmLineNumber The object line that raised the alarm. If a line is not relevant to the alarm, the line number is zero. (8) cerent454AlarmObjectName The TL1-style user-visible name that uniquely identifies an object in the system. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description20-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content E (cont.) (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. If there is no additional information, the value is zero. (10) snmpTrapAddress The address of the SNMP trap. F performanceMonitor ThresholdCrossingAlert (from CERENT-454-mib) (1) cerent454NodeTime The time that an event occurred. (2) cerent454AlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service-affecting statuses are Service-Affecting and Non-Service Affecting. (3) cerent454AlarmObjectType The entity that raised the alarm. The NMS should use this value to decide which table to poll for further information about the alarm. (4) cerent454AlarmObjectIndex Every alarm is raised by an object entry in a specific table. This variable is the index of objects in each table; if the alarm is interface-related, this is the index of the interface in the interface table. (5) cerent454AlarmSlotNumber The slot of the object that raised the alarm. If a slot is not relevant to the alarm, the slot number is zero. (6) cerent454AlarmPortNumber The port of the object that raised the alarm. If a port is not relevant to the alarm, the port number is zero. (7) cerent454AlarmLineNumber The object line that raised the alarm. If a line is not relevant to the alarm, the line number is zero. (8) cerent454AlarmObjectName The TL1-style user-visible name that uniquely identifies an object in the system. (9) cerent454ThresholdMonitorType This object indicates the type of metric being monitored. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description20-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP Trap Content F (cont.) (10) cerent454ThresholdLocation Indicates whether the event occurred at the near or far end. (11) cerent454ThresholdPeriod Indicates the sampling interval period. (12) cerent454ThresholdSetValue The value of this object is the threshold provisioned by the NMS. (13) cerent454ThresholdCurrentValue — (14) cerent454ThresholdDetectType — (15) snmpTrapAddress The address of the SNMP trap. G All other traps (from CERENT-454-MIB) not listed above (1) cerent454NodeTime The time that an event occurred. (2) cerent454AlarmState The alarm severity and service-affecting status. Severities are Minor, Major, and Critical. Service-affecting statuses are Service-Affecting and Non-Service Affecting. (3) cerent454AlarmObjectType The entity that raised the alarm. The NMS should use this value to decide which table to poll for further information about the alarm. (4) cerent454AlarmObjectIndex Every alarm is raised by an object entry in a specific table. This variable is the index of objects in each table; if the alarm is interface-related, this is the index of the interface in the interface table. (5) cerent454AlarmSlotNumber The slot of the object that raised the alarm. If a slot is not relevant to the alarm, the slot number is zero. (6) cerent454AlarmPortNumber The port of the object that raised the alarm. If a port is not relevant to the alarm, the port number is zero. (7) cerent454AlarmLineNumber The object line that raised the alarm. If a line is not relevant to the alarm, the line number is zero. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description20-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMPv1/v2 Community Names 20.8 SNMPv1/v2 Community Names Community names are used to group SNMP trap destinations. All ONS 15454 trap destinations can be provisioned as part of SNMP communities in CTC. When community names are assigned to traps, the ONS 15454 treats the request as valid if the community name matches one that is provisioned in CTC. In this case, all agent-managed MIB variables are accessible to that request. If the community name does not match the provisioned list, SNMP drops the request. 20.9 SNMP in Multishelf Management When using the dense wavelength division multiplexing (DWDM) multishelf management feature to subtend shelves from a node controller shelf, SNMP for the subtended shelves must be specially provisioned. All shelves within a multishelf configuration share the node controller’s ID and IP address. Thus, the only way to route SNMP messages to or from subtended shelves is by using proxy ARP. The cerent454MultishelfEnabled object ID (OID) can be used to determine whether the node is single shelf or multishelf. To view the OID, use the snmpwalk node IP addressifDescr SNMP command in global configuration mode. This command output displays the OID as _x/y/z where x = Shelf number (for a multishelf node) y = Card slot number z = Card port number. The following example shows how to obtain the OID using the snmpwalk node IP addressifDescr SNMP command. Router(config)# snmpwalk 192.0.2.1 ifDescr RFC1213-MIB::ifDescr.1 = STRING: "motfcc0" RFC1213-MIB::ifDescr.6 = STRING: "pdcc0" RFC1213-MIB::ifDescr.7 = STRING: "pdcc1" RFC1213-MIB::ifDescr.8 = STRING: "pdcc2" RFC1213-MIB::ifDescr.9 = STRING: "pdcc3" RFC1213-MIB::ifDescr.10 = STRING: "pdcc4" RFC1213-MIB::ifDescr.11 = STRING: "pdcc5" RFC1213-MIB::ifDescr.12 = STRING: "pdcc6" RFC1213-MIB::ifDescr.13 = STRING: "pdcc7" RFC1213-MIB::ifDescr.14 = STRING: "pdcc8" RFC1213-MIB::ifDescr.15 = STRING: "pdcc9" RFC1213-MIB::ifDescr.16 = STRING: "pdcc10" G (cont.) (8) cerent454AlarmObjectName The TL1-style user-visible name that uniquely identifies an object in the system. (9) snmpTrapAddress The address of the SNMP trap. Table 20-11 Supported ONS 15454 SNMPv2 Trap Variable Bindings (continued) Group Trap Name(s) Associated with Variable Binding Number SNMPv2 Variable Bindings Description20-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMP in Multishelf Management RFC1213-MIB::ifDescr.17 = STRING: "pdcc11" RFC1213-MIB::ifDescr.18 = STRING: "pdcc12" RFC1213-MIB::ifDescr.19 = STRING: "pdcc13" RFC1213-MIB::ifDescr.20 = STRING: "pdcc14" RFC1213-MIB::ifDescr.21 = STRING: "pdcc15" RFC1213-MIB::ifDescr.22 = STRING: "pdcc16" RFC1213-MIB::ifDescr.23 = STRING: "pdcc17" RFC1213-MIB::ifDescr.24 = STRING: "pdcc18" RFC1213-MIB::ifDescr.25 = STRING: "pdcc19" RFC1213-MIB::ifDescr.26 = STRING: "pdcc20" RFC1213-MIB::ifDescr.27 = STRING: "pdcc21" RFC1213-MIB::ifDescr.28 = STRING: "pdcc22" RFC1213-MIB::ifDescr.29 = STRING: "pdcc23" RFC1213-MIB::ifDescr.30 = STRING: "pdcc24" RFC1213-MIB::ifDescr.31 = STRING: "pdcc25" RFC1213-MIB::ifDescr.32 = STRING: "pdcc26" RFC1213-MIB::ifDescr.33 = STRING: "pdcc27" RFC1213-MIB::ifDescr.34 = STRING: "pdcc28" RFC1213-MIB::ifDescr.35 = STRING: "pdcc29" RFC1213-MIB::ifDescr.36 = STRING: "pdcc30" RFC1213-MIB::ifDescr.37 = STRING: "pdcc31" RFC1213-MIB::ifDescr.38 = STRING: "pdcc32" RFC1213-MIB::ifDescr.39 = STRING: "pdcc33" RFC1213-MIB::ifDescr.40 = STRING: "pdcc34" RFC1213-MIB::ifDescr.41 = STRING: "pdcc35" RFC1213-MIB::ifDescr.42 = STRING: "pdcc36" RFC1213-MIB::ifDescr.43 = STRING: "pdcc37" RFC1213-MIB::ifDescr.44 = STRING: "pdcc38" RFC1213-MIB::ifDescr.45 = STRING: "pdcc39" RFC1213-MIB::ifDescr.46 = STRING: "pdcc40" RFC1213-MIB::ifDescr.47 = STRING: "pdcc41" RFC1213-MIB::ifDescr.48 = STRING: "pdcc42" RFC1213-MIB::ifDescr.49 = STRING: "pdcc43" RFC1213-MIB::ifDescr.50 = STRING: "pdcc44" RFC1213-MIB::ifDescr.51 = STRING: "pdcc45" RFC1213-MIB::ifDescr.52 = STRING: "pdcc46" RFC1213-MIB::ifDescr.53 = STRING: "pdcc47" RFC1213-MIB::ifDescr.54 = STRING: "pdcc48" RFC1213-MIB::ifDescr.55 = STRING: "pdcc49" RFC1213-MIB::ifDescr.56 = STRING: "pdcc50" RFC1213-MIB::ifDescr.57 = STRING: "pdcc51" RFC1213-MIB::ifDescr.58 = STRING: "pdcc52" RFC1213-MIB::ifDescr.59 = STRING: "pdcc53" RFC1213-MIB::ifDescr.60 = STRING: "pdcc54" RFC1213-MIB::ifDescr.61 = STRING: "pdcc55" RFC1213-MIB::ifDescr.62 = STRING: "pdcc56" RFC1213-MIB::ifDescr.63 = STRING: "pdcc57" RFC1213-MIB::ifDescr.64 = STRING: "pdcc58" RFC1213-MIB::ifDescr.65 = STRING: "pdcc59" RFC1213-MIB::ifDescr.66 = STRING: "pdcc60" RFC1213-MIB::ifDescr.67 = STRING: "pdcc61" RFC1213-MIB::ifDescr.68 = STRING: "pdcc62" RFC1213-MIB::ifDescr.69 = STRING: "pdcc63" RFC1213-MIB::ifDescr.70 = STRING: "pdcc64" RFC1213-MIB::ifDescr.71 = STRING: "pdcc65" RFC1213-MIB::ifDescr.72 = STRING: "pdcc66" RFC1213-MIB::ifDescr.73 = STRING: "pdcc67" RFC1213-MIB::ifDescr.74 = STRING: "pdcc68" RFC1213-MIB::ifDescr.75 = STRING: "pdcc69" RFC1213-MIB::ifDescr.76 = STRING: "pdcc70" RFC1213-MIB::ifDescr.77 = STRING: "pdcc71" RFC1213-MIB::ifDescr.78 = STRING: "pdcc72" RFC1213-MIB::ifDescr.79 = STRING: "pdcc73" RFC1213-MIB::ifDescr.80 = STRING: "pdcc74"20-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMPv1/v2 Proxy Over Firewalls RFC1213-MIB::ifDescr.81 = STRING: "pdcc75" RFC1213-MIB::ifDescr.82 = STRING: "pdcc76" RFC1213-MIB::ifDescr.83 = STRING: "pdcc77" RFC1213-MIB::ifDescr.84 = STRING: "pdcc78" RFC1213-MIB::ifDescr.85 = STRING: "pdcc79" RFC1213-MIB::ifDescr.86 = STRING: "pdcc80" RFC1213-MIB::ifDescr.257 = STRING: "fog_1_36" RFC1213-MIB::ifDescr.8194 = STRING: "TenGigabitEthernet2/1" RFC1213-MIB::ifDescr.8195 = STRING: "TenGigabitEthernet2/2" RFC1213-MIB::ifDescr.8196 = STRING: "TenGigabitEthernet2/3" RFC1213-MIB::ifDescr.8197 = STRING: "TenGigabitEthernet2/4" RFC1213-MIB::ifDescr.12290 = STRING: "dwdm-cli_2/3/1" RFC1213-MIB::ifDescr.12291 = STRING: "dwdm-cli_2/3/2" RFC1213-MIB::ifDescr.12292 = STRING: "dwdm-trk_2/3/3" RFC1213-MIB::ifDescr.12293 = STRING: "dwdm-trk_2/3/4" RFC1213-MIB::ifDescr.12294 = STRING: "TenGigabitEthernet3/1" RFC1213-MIB::ifDescr.12295 = STRING: "TenGigabitEthernet3/2" RFC1213-MIB::ifDescr.12296 = STRING: "TenGigabitEthernet3/3" RFC1213-MIB::ifDescr.12297 = STRING: "TenGigabitEthernet3/4" RFC1213-MIB::ifDescr.147458 = STRING: "GigabitEthernet36/1" RFC1213-MIB::ifDescr.147459 = STRING: "GigabitEthernet36/2" RFC1213-MIB::ifDescr.147502 = STRING: "TenGigabitEthernet36/45" RFC1213-MIB::ifDescr.147503 = STRING: "TenGigabitEthernet36/46" RFC1213-MIB::ifDescr.147504 = STRING: "TenGigabitEthernet36/47" RFC1213-MIB::ifDescr.147505 = STRING: "TenGigabitEthernet36/48" RFC1213-MIB::ifDescr.147554 = STRING: "ds1_36/1" RFC1213-MIB::ifDescr.147555 = STRING: "ds1_36/2" LAN-connected network elements (LNEs) can be set up as gateway network elements (GNEs) or as SOCKS proxies, depending upon network security requirements. If the GNE/ENE firewall feature is required, the LNE must be set up as a GNE. If the design does not require the firewall feature but does require all-IP networking, the LNE must be set up as a SOCKS proxy. In a GNE/ENE firewall configuration, nonconnected network elements must be set up as end network elements (ENEs). With a SOCKS configuration, subtended nodes communicate with the proxy server by IP. For procedures to provision a node or shelf as a GNE, ENE or SOCKS proxy, refer to the Cisco ONS 15454 DWDM Procedure Guide. 20.10 SNMPv1/v2 Proxy Over Firewalls SNMP and NMS applications have traditionally been unable to cross firewalls used for isolating security risks inside or from outside networks. CTC enables network operations centers (NOCs) to access performance monitoring data such as RMON statistics or autonomous messages across firewalls by using an SMP proxy element installed on a firewall. The application-level proxy transports SNMP protocol data units (PDU) between the NMS and NEs, allowing requests and responses between the NMS and NEs and forwarding NE autonomous messages to the NMS. The proxy agent requires little provisioning at the NOC and no additional provisioning at the NEs. The firewall proxy is intended for use in a gateway network element-end network element (GNE-ENE) topology with many NEs through a single NE gateway. Up to 64 SNMP requests (such as get, getnext, or getbulk) are supported at any time behind single or multiple firewalls. The proxy interoperates with common NMS such as HP OpenView. For security reasons, the SNMP proxy feature must be enabled at all receiving and transmitting NEs to function. For instructions to do this, refer to the Cisco ONS 15454 DWDM Procedure Guide.20-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP SNMPv3 Proxy Configuration 20.11 SNMPv3 Proxy Configuration The GNE can act as a proxy for the ENEs and forward SNMP requests to other SNMP entities (ENEs) irrespective of the types of objects that are accessed. For this, you need to configure two sets of users, one between the GNE and NMS, and the other between the GNE and ENE. In addition to forwarding requests from the NMS to the ENE, the GNE also forwards responses and traps from the ENE to the NMS. The proxy forwarder application is defined in RFC 3413. Each entry in the Proxy Forwarder Table consists of the following parameters: • Proxy Type—Defines the type of message that may be forwarded based on the translation parameters defined by this entry. If the Proxy Type is read or write, the proxy entry is used for forwarding SNMP requests and their response between the NMS and the ENE. If the Proxy Type is trap, the entry is used for forwarding SNMP traps from the ENE to the NMS. • Context Engine ID/Context Name—Specifies the ENE to which the incoming requests should be forwarded or the ENE whose traps should be forwarded to the NMS by the GNE. • TargetParamsIn—Points to the Target Params Table that specifies the GNE user who proxies on behalf of an ENE user. When the proxy type is read or write, TargetParamsIn specifies the GNE user who receives requests from an NMS, and forwards requests to the ENE. When the proxy type is trap, TargetParamsIn specifies the GNE user who receives notifications from the ENE and forwards them to the NMS. TargetParamsIn and the contextEngineID or the contextName columns are used to determine the row in the Proxy Forwarder Table that could be used for forwarding the received message. • Single Target Out—Refers to the Target Address Table. After you select a row in the Proxy Forwarder Table for forwarding, this object is used to get the target address and the target parameters that are used for forwarding the request. This object is used for requests with proxy types read or write, which only requires one target. • Multiple Target Out (Tag)—Refers to a group of entries in the Target Address Table. Notifications are forwarded using this tag. The Multiple Target Out tag is only relevant when proxy type is Trap and is used to send notifications to one or more NMSs. 20.12 Remote Monitoring The ONS 15454 incorporates RMON to allow network operators to monitor Ethernet card performance and events. The RMON thresholds are user-provisionable in CTC. Refer to the Cisco ONS 15454 DWDM Procedure Guide for instructions. Note Typical RMON operations, other than threshold provisioning, are invisible to the CTC user. 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. 20-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring 20.12.1 64-Bit RMON Monitoring over DCC The ONS 15454 DCC is implemented over the IP protocol, which is not compatible with Ethernet. The system builds Ethernet equipment History and Statistics tables using HDLC statistics that are gathered over the DCC (running point-topoint protocol, or PPP). RMON DCC monitoring (for both IP and Ethernet) monitors the health of remote DCC connections. RMON DCC contains two MIBs for DCC interfaces. They are: • cMediaIndependentTable—standard, rfc3273; the proprietary extension of the HC-RMON MIB used for reporting statistics • cMediaIndependentHistoryTable—proprietary MIB used to support history 20.12.1.1 Row Creation in MediaIndependentTable The SetRequest PDU for creating a row in the mediaIndependentTable should contain all the values required to activate a row in a single set operation along with an assignment of the status variable to createRequest (2). The SetRequest PDU for entry creation must have all the object IDs (OIDs) carrying an instance value of 0. That is, all the OIDs should be of the type OID.0. In order to create a row, the SetRequest PDU should contain the following: • mediaIndependentDataSource and its desired value • mediaIndependentOwner and its desired value (The size of mediaIndependentOwner is limited to 32 characters.) • mediaIndependentStatus with a value of createRequest (2) The mediaIndependentTable creates a row if the SetRequest PDU is valid according to the above rules. When the row is created, the SNMP agent decides the value of mediaIndependentIndex. This value is not sequentially allotted or contiguously numbered. It changes when an Ethernet interface is added or deleted. The newly created row will have mediaIndependentTable value of valid (1). If the row already exists, or if the SetRequest PDU values are insufficient or do not make sense, the SNMP agent returns an error code. Note mediaIndependentTable entries are not preserved if the SNMP agent is restarted. The mediaIndependentTable deletes a row if the SetRequest PDU contains a mediaIndependentStatus with a value of invalid (4). The varbind’s OID instance value identifies the row for deletion. You can recreate a deleted row in the table if desired. 20.12.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. In order to create a row, the SetRequest PDU should contain the following: • cMediaIndependentHistoryControlDataSource and its desired value • cMediaIndependentHistoryControlOwner and its desired value • cMediaIndependentHistoryControlStatus with a value of createRequest (2)20-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring 20.12.2 HC-RMON-MIB Support For the ONS 15454, the implementation of the high-capacity remote monitoring information base (HC-RMON-MIB, or RFC 3273) enables 64-bit support of existing RMON tables. This support is provided with the etherStatsHighCapacityTable and the etherHistoryHighCapacityTable. An additional table, the mediaIndependentTable, and an additional object, hcRMONCapabilities, are also added for this support. All of these elements are accessible by any third-party SNMP client should have the ability to upload RFC 3273 SNMP MIB variables in the etherStatsHighCapacityTable, etherHistoryHighCapacityTable, or mediaIndependentTable. 20.12.3 Ethernet Statistics RMON Group The Ethernet Statistics group contains the basic statistics monitored for each subnetwork in a single table called the etherStatsTable. 20.12.3.1 Row Creation in etherStatsTable The SetRequest PDU for creating a row in this table should contain all the values needed to activate a row in a single set operation, and an assigned status variable to createRequest. The SetRequest PDU object ID (OID) entries must all carry an instance value, or type OID, of 0. In order to create a row, the SetRequest PDU should contain the following: • The etherStatsDataSource and its desired value • The etherStatsOwner and its desired value (size of this value is limited to 32 characters) • The etherStatsStatus with a value of createRequest (2) The etherStatsTable creates a row if the SetRequest PDU is valid according to the above rules. When the row is created, the SNMP agent decides the value of etherStatsIndex. This value is not sequentially allotted or contiguously numbered. It changes when an Ethernet interface is added or deleted. The newly created row will have etherStatsStatus value of valid (1). If the etherStatsTable row already exists, or if the SetRequest PDU values are insufficient or do not make sense, the SNMP agent returns an error code. Note EtherStatsTable entries are not preserved if the SNMP agent is restarted. 20.12.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. 20.12.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. If required, a deleted row can be recreated.20-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring 20.12.3.4 64-Bit etherStatsHighCapacity Table The Ethernet statistics group contains 64-bit statistics in the etherStatsHighCapacityTable, which provides 64-bit RMON support for the HC-RMON-MIB. The etherStatsHighCapacityTable is an extension of the etherStatsTable that adds 16 new columns for performance monitoring data in 64-bit format. There is a one-to-one relationship between the etherStatsTable and etherStatsHighCapacityTable when rows are created or deleted in either table. 20.12.4 History Control RMON Group The History Control group defines sampling functions for one or more monitor interfaces in the historyControlTable. The values in this table, as specified in RFC 2819, are derived from the historyControlTable and etherHistoryTable. 20.12.4.1 History Control Table The RMON is sampled at one of four possible intervals. Each interval or period contains specific history values (also called buckets). Table 20-12 lists the four sampling periods and corresponding buckets. The historyControlTable maximum row size is determined by multiplying the number of ports on a card by the number of sampling periods. For example, a card that contains 24 ports when multiplied by periods allows 96 rows in the table. A card that contains 14 ports when multiplied by four periods allows 56 table rows. 20.12.4.2 Row Creation in historyControlTable The SetRequest PDU must be able to activate a historyControlTable row in one single-set operation. In order to do this, the PDU must contain all needed values and have a status variable value of 2 (createRequest). All OIDs in the SetRequest PDU should be type OID.0 type for entry creation. To create a SetRequest PDU for the historyControlTable, the following values are required: • The historyControlDataSource and its desired value • The historyControlBucketsRequested and it desired value • The historyControlInterval and its desired value • The historyControlOwner and its desired value • The historyControlStatus with a value of createRequest (2) The historyControlBucketsRequested OID value is ignored because the number of buckets allowed for each sampling period, based upon the historyControlInterval value, is already fixed. Table 20-12 lists these variables. Table 20-12 RMON History Control Periods and History Categories Sampling Periods (historyControlValue Variable) Total Values or Buckets (historyControl Variable) 15 minutes 32 24 hours 7 1 minute 60 60 minutes 2420-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring The historyControlInterval value cannot be changed from the four allowed choices. If you use another value, the SNMP agent selects the closest smaller time period from the set buckets. For example, if the set request specifies a 25-minute interval, this falls between the 15-minute (32 bucket) variable and the 60-minute (24 bucket) variable. The SNMP agent automatically selects the lower, closer value, which is 15 minutes, so it allows 32 buckets. If the SetRequest PDU is valid, a historyControlTable row is created. If the row already exists, or if the SetRequest PDU values do not make sense or are insufficient, the SNMP agent does not create the row and returns an error code. 20.12.4.3 Get Requests and GetNext Requests These PDUs are not restricted. 20.12.4.4 Row Deletion in historyControl Table To delete a row from the table, the SetRequest PDU should contain a historyControlStatus value of 4 (invalid). A deleted row can be recreated. 20.12.5 Ethernet History RMON Group The ONS 15454 implements the etherHistoryTable as defined in RFC 2819. The group is created within the bounds of the historyControlTable and does not deviate from the RFC in its design. 20.12.5.1 64-Bit etherHistoryHighCapacityTable 64-bit Ethernet history for the HC-RMON-MIB is implemented in the etherHistoryHighCapacityTable, which is an extension of the etherHistoryTable. The etherHistoryHighCapacityTable adds four columns for 64-bit performance monitoring data. These two tables have a one-to-one relationship. Adding or deleting a row in one table will also change the other. 20.12.6 Alarm RMON Group The Alarm group consists of the alarmTable, which periodically compares sampled values with configured thresholds and raises an event if a threshold is crossed. This group requires the implementation of the event group, which follows this section. 20.12.6.1 Alarm Table The NMS uses the alarmTable to determine and provision network performance alarmable thresholds. 20.12.6.2 Row Creation in alarmTable To create a row in the alarmTable, the SetRequest PDU must be able to create the row in one single-set operation. All OIDs in the SetRequest PDU should be type OID.0 type for entry creation. The table has a maximum number of 256 rows. To create a SetRequest PDU for the alarmTable, the following values are required:20-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring • The alarmInterval and its desired value • The alarmVariable and its desired value • The alarmSampleType and its desired value • The alarmStartupAlarm and its desired value • The alarmOwner and its desired value • The alarmStatus with a value of createRequest (2) If the SetRequest PDU is valid, a historyControlTable row is created. If the row already exists, or if the SetRequest PDU values do not make sense or are insufficient, the SNMP agent does not create the row and returns an error code. In addition to the required values, the following restrictions must be met in the SetRequest PDU: • The alarmOwner is a string of length 32 characters. • The alarmRisingEventIndex always takes value 1. • The alarmFallingEventIndex always takes value 2. • The alarmStatus has only two values supported in SETs: createRequest (2) and invalid (4). • The AlarmVariable is of the type OID.ifIndex, where ifIndex gives the interface this alarm is created on and OID is one of the OIDs supported in Table 20-13. Table 20-13 OIDs Supported in the AlarmTable No. Column Name OID Status 1 ifInOctets {1.3.6.1.2.1.2.2.1.10} — 2 IfInUcastPkts {1.3.6.1.2.1.2.2.1.11} — 3 ifInMulticastPkts {1.3.6.1.2.1.31.1.1.1.2} Unsupported in E100/E1000 4 ifInBroadcastPkts {1.3.6.1.2.1.31.1.1.1.3} Unsupported in E100/E1000 5 ifInDiscards {1.3.6.1.2.1.2.2.1.13} Unsupported in E100/E1000 6 ifInErrors {1.3.6.1.2.1.2.2.1.14} — 7 ifOutOctets {1.3.6.1.2.1.2.2.1.16} — 8 ifOutUcastPkts {1.3.6.1.2.1.2.2.1.17} — 9 ifOutMulticastPkts {1.3.6.1.2.1.31.1.1.1.4} Unsupported in E100/E1000 10 ifOutBroadcastPkts {1.3.6.1.2.1.31.1.1.1.5} Unsupported in E100/E1000 11 ifOutDiscards {1.3.6.1.2.1.2.2.1.19} Unsupported in E100/E1000 12 Dot3StatsAlignmentErrors {1.3.6.1.2.1.10.7.2.1.2} — 13 Dot3StatsFCSErrors {1.3.6.1.2.1.10.7.2.1.3} — 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.13} — 20 Dot3StatsCarrierSenseErrors {1.3.6.1.2.1.10.7.2.1.11} Unsupported in E100/E100020-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring 20.12.6.3 Get Requests and GetNext Requests These PDUs are not restricted. 20.12.6.4 Row Deletion in alarmTable To delete a row from the table, the SetRequest PDU should contain an alarmStatus value of 4 (invalid). A deleted row can be recreated. Entries in this table are preserved if the SNMP agent is restarted. 20.12.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. 20.12.7.1 Event Table The eventTable is read-only and unprovisionable. The table contains one row for rising alarms and another for falling ones. This table has the following restrictions: • The eventType is always log-and-trap (4). 21 Dot3StatsSQETestErrors {1.3.6.1.2.1.10.7.2.1.6} Unsupported in E100/E1000 22 etherStatsUndersizePkts {1.3.6.1.2.1.16.1.1.1.9} — 23 etherStatsFragments {1.3.6.1.2.1.16.1.1.1.11} — 24 etherStatsPkts64Octets {1.3.6.1.2.1.16.1.1.1.14} — 25 etherStatsPkts65to127Octets {1.3.6.1.2.1.16.1.1.1.15} — 26 etherStatsPkts128to255Octets {1.3.6.1.2.1.16.1.1.1.16} — 27 etherStatsPkts256to511Octets {1.3.6.1.2.1.16.1.1.1.17} — 28 etherStatsPkts512to1023Octets {1.3.6.1.2.1.16.1.1.1.18} — 29 etherStatsPkts1024to1518Octets {1.3.6.1.2.1.16.1.1.1.19} — 30 EtherStatsBroadcastPkts {1.3.6.1.2.1.16.1.1.1.6} — 31 EtherStatsMulticastPkts {1.3.6.1.2.1.16.1.1.1.7} — 32 EtherStatsOversizePkts {1.3.6.1.2.1.16.1.1.1.10} — 33 EtherStatsJabbers {1.3.6.1.2.1.16.1.1.1.12} — 34 EtherStatsOctets {1.3.6.1.2.1.16.1.1.1.4} — 35 EtherStatsCollisions {1.3.6.1.2.1.16.1.1.1.13} — 36 EtherStatsCollisions {1.3.6.1.2.1.16.1.1.1.8} — 37 EtherStatsDropEvents {1.3.6.1.2.1.16.1.1.1.3} Unsupported in E100/E1000 and G1000 Table 20-13 OIDs Supported in the AlarmTable (continued) No. Column Name OID Status20-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Chapter 20 SNMP Remote Monitoring • The eventCommunity value is always a zero-length string, indicating that this event causes the trap to be despatched to all provisioned destinations. • The eventOwner column value is always “monitor.” • The eventStatus column value is always valid(1). 20.12.7.2 Log Table The logTable is implemented exactly as specified in RFC 2819. The logTable is based upon data that is locally cached in a controller card. If there is a controller card protection switch, the existing logTable is cleared and a new one is started on the newly active controller card. The table contains as many rows as provided by the alarm controller.A-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 APPENDIX A Hardware Specifications This appendix contains hardware and software specifications for the ONS 15454 ANSI and ETSI shelf assemblies and cards. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. The following sections are included: • A.1 ONS 15454, ONS 15454 M2, and ONS 15454 M6 Shelf Specifications, page A-1 • A.2 General Card Specifications, page A-2 • A.3 Common Control Card Specifications, page A-4 • A.4 Optical Service Channel Cards, page A-11 • A.5 Optical Amplifier Cards, page A-13 • A.6 PSM (Protection Switching Module) Card Specifications, page A-19 • A.7 Multiplexer and Demultiplexer Cards, page A-20 • A.8 Reconfigurable Optical Add/Drop Cards, page A-22 • A.9 Optical Add/Drop Cards, page A-44 • A.10 Transponder and Muxponder Card Specifications, page A-54 • A.11 TDC-CC and TDC-FC Card Specifications, page A-99 • A.12 Mesh Patch Panel Specifications, page A-100 • A.13 SFP and XFP Specifications, page A-102 • A.14 Patch Panel Specifications, page A-102 A.1 ONS15454, ONS 15454 M2, and ONS 15454 M6 Shelf Specifications For information on shelf bandwidth; list of topologies; Cisco Transport Controller (CTC) specifications; the LAN, Transaction Language One (TL1), modem, and alarm specifications; timing, power, and environmental specifications; and shelf dimensions, refer to Appendix A, Hardware Specifications” in the “Cisco ONS 15454 Hardware Installation Guide”.A-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications General Card Specifications A.2 General Card Specifications This section provides power specifications and temperature ranges for all ONS 15454 cards. A.2.1 Power Table A-1 provides power consumption information for the ONS 15454 cards. Table A-1 Individual Card Power Requirements (Typical Values at 25 degrees C) Card Type Card Name (Power in Watts) Amperes at –48 V BTU/Hr. Common Control Cards TCC2/TCC2P/TCC3 26 0.54 89 TNC 45 0.94 153 TSC 38 0.79 129 AIC-I 8 0.17 28 AEP 3 (from +5 VDC from AIC-I) 10 MIC-A/P 0.13 via TCC2/TCC2P/TCC3 0.44 MIC-C/T/P 0.38 via TCC2/TCC2P/TCC3 1.29 MS-ISC-100T 53 1.10 181.0 Optical Service Channel Cards OSCM 23 0.48 79 OSC-CSM 24 0.5 82 Optical Amplifier Cards OPT-PRE 30 0.63 103 OPT-BST 30 0.63 103 OPT-BST-E 30 0.63 103 OPT-BST-L 25 0.52 86 OPT-AMP-L 32 0.67 110 OPT-AMP-17-C 40 0.83 137 OPT-AMP-C 40 0.83 137 OPT-RAMP-C 50 1.04 171 OPT-RAMP-CE 40 0.83 137 PSM Card PSM 20 0.41 69 Multiplexer and Demultiplexer Cards 32MUX-O 16 0.33 55 32DMX-O 16 0.33 55 4MD-xx.x 17 0.35 58.0A-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications General Card Specifications ROADM Cards 32DMX 15 0.31 52 32DMX-L 15 0.31 52 32WSS 50 1.04 171 32WSS-L 43 0.90 147 40-MUX-C 35 0.73 120 40-DMX-C 35 0.73 120 40-DMX-CE 35 0.73 120 40-WSS-C 73 1.53 250 40-WSS-CE 73 1.53 250 40-WXC-C 30 0.63 103 80-WXC-C 20 0.42 69 40-SMR1-C 35 0.73 120 40-SMR2-C 40 0.83 137 MMU 7 0.15 24 Optical Add/Drop Cards AD-1C-xx.x 17 0.35 58.0 AD-2C-xx.x 17 0.35 58.0 AD-4C-xx.x 17 0.35 58.0 AD-1B-xx.x 17 0.35 58.0 AD-4B-xx.x 17 0.35 58.0 Transponder and Muxponder Cards TXP_MR_10G 35 0.73 120 TXP_MR_10E 50 1.05 171 TXP_MR_10E_C 50 1.05 171 TXP_MR_10E_L 50 1.05 171 TXP_MR_10EX_C 42 0.88 144 TXP_MR_2.5G 35 0.73 120 TXPP_MR_2.5G 50 1.05 171 MXP_2.5G_10G 50 1.05 171 MXP_2.5G_10E 50 1.05 171 MXP_2.5G_10E_C 50 1.05 171 MXP_2.5G_10E_L 50 1.05 171 MXP_2.5G_10EX_C 50 1.05 171 MXP_MR_2.5G 50 1.05 171 MXPP_MR_2.5G 50 1.05 171 Table A-1 Individual Card Power Requirements (continued)(Typical Values at 25 degrees C) Card Type Card Name (Power in Watts) Amperes at –48 V BTU/Hr.A-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications A.2.2 Temperature • Operating temperature: – Long term: 0 to 40 degrees Celsius (32 to 104 degrees Fahrenheit) – Short term: Functionality is guaranteed at -5 to 55 degrees Celsius (23 to 131 degrees Fahrenheit), according to GR-63 Issue 3 The indicated temperatures are the ambient ones in which the shelf can be placed. A.3 Common Control Card Specifications This section provides specifications for the TCC2, TCC2P, TCC3, TNC, TSC, AIC, and AIC-I cards, the alarm expansion panel (AEP), the MIC-A/P and MIC-C/T/P FMECs, and the MS-ISC-100T card. For compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. A.3.1 TCC2 Card Specifications The TCC2 card has the following specifications: • CTC software – Interface: EIA/TIA-232 (local craft access, on TCC2 faceplate) – Interface: 10BaseT LAN (on TCC2 faceplate) – Interface: 10BaseT LAN (through the backplane) • Synchronization – Stratum 3, per Telcordia GR-253-CORE – Free running access: Accuracy +/– 4.6 ppm – Holdover stability: 3.7 x 10-7 per day including temperature (< 255 slips in first 24 hours) – Reference: External BITS, line, internal Transponder and Muxponder Cards MXP_MR_10DME_C 60 1.25 205 MXP_MR_10DME_L 60 1.25 205 MXP_MR_10DMEX_ C 60 1.25 205 40G-MXP-C 112 2.34 383 ADM-10G 135 2.81 461 OTU2_XP 71 1.48 243 TDCU Cards TDC-CC 8 0.17 28 TDC-FC 8 0.17 28 Table A-1 Individual Card Power Requirements (continued)(Typical Values at 25 degrees C) Card Type Card Name (Power in Watts) Amperes at –48 V BTU/Hr.A-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications • Supply voltage monitoring – Both supply voltage inputs are monitored. – Normal operation: –40.5 to –56.7 V – Undervoltage: Major alarm – Overvoltage: Major alarm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 235 mm (9.250 in.) – Weight not including clam shell: 0.7 kg (1.5 lb) A.3.2 TCC2P Card Specifications The TCC2P card has the following specifications: • CTC software – Interface: EIA/TIA-232 (local craft access, on TCC2P faceplate) – Interface: 10BaseT LAN (on TCC2P faceplate) – Interface: 10BaseT LAN (through the backplane) • Synchronization – Stratum 3, per Telcordia GR-253-CORE – Free running access: Accuracy +/– 4.6 ppm – Holdover stability: 3.7 * 10 exp – 7 per day including temperature (< 255 slips in first 24 hours) – Reference: External BITS, line, internal • Supply voltage monitoring – Both supply voltage inputs are monitored. – Normal operation: –40.5 to –56.7 V (in –48 VDC systems) – Undervoltage: Major alarm – Overvoltage: Major alarm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – 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-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications A.3.3 TCC3 Card Specifications The TCC3 card has the following specifications: • CTC software – Interface: EIA/TIA-232 (local craft access, on TCC3 faceplate) – Interface: 10BaseT LAN (on TCC3 faceplate) – Interface: 10BaseT LAN (through the backplane) • Synchronization – Stratum 3, per Telcordia GR-253-CORE – Free running access: Accuracy +/– 4.6 ppm – Holdover stability: 3.7 * 10 exp – 7 per day including temperature (< 255 slips in first 24 hours) – Reference: External BITS, line, internal • Supply voltage monitoring – Both supply voltage inputs are monitored. – Normal operation: –40.5 to –56.7 V (in –48 VDC systems) – Undervoltage: Major alarm – Overvoltage: Major alarm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – 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.3.4 TNC Card Specifications (Cisco ONS 15454 M2 and Cisco ONS 15454 M6) The TNC card has the following specifications: • CTC software – Interface: EIA/TIA-232 (local craft access, on TNC faceplate) – Interface: 10BaseT LAN (on TNC faceplate) – Interface: 10BaseT LAN (through the external connection unit for EMS, CT, MSM, VoIP, UDC and Line Cards) – Two SFP interfaces to support Optical Service Channels (OC-3/STM-1 or FE/GE) • Synchronization – Stratum 3, per Telcordia GR-253-CORE – Free running access: Accuracy +/– 4.6 ppm – Holdover stability: 3.7 * 10 exp – 7 per day including temperature (< 255 slips in first 24 hours) – Reference: External BITS, line, internalA-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications • Supply voltage monitoring – Both the input supply voltages are monitored. – Normal operation: –40.5 to –56.7 V (in –48 VDC systems) – AC input voltage range: Undervoltage TH 90V histeresis 5V; Overvoltage TH 254V histeresis 10V – Undervoltage: Major alarm – Overvoltage: Major alarm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 1.6 lb (0.8 kg) A.3.5 TSC Card Specifications (ONS 15454 M2 and ONS 15454 M6) The TSC card has the following specifications: • CTC software – Interface: EIA/TIA-232 (local craft access, on TSC faceplate) – Interface: 10BaseT LAN (on TSC faceplate) – Interface: 10BaseT LAN (through the external connection unit for EMS, CT, MSM, VoIP, UDC and Line Cards) • Synchronization – Stratum 3, per Telcordia GR-253-CORE – Free running access: Accuracy +/– 4.6 ppm – Holdover stability: 3.7 * 10 exp – 7 per day including temperature (< 255 slips in first 24 hours) – Reference: External BITS, line, internal • Supply voltage monitoring – Both the input supply voltages are monitored. – Normal operation: –40.5 to –56.7 V (in –48 VDC systems) – AC input voltage range: Undervoltage TH 90V histeresis 5V; Overvoltage TH 254V histeresis 10V – Undervoltage: Major alarm – Overvoltage: Major alarm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm)A-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications – Weight not including clam shell: 1.6 lb (0.8 kg) A.3.6 AIC-I Card Specifications The AIC-I card has the following specifications: • Alarm inputs – Number of inputs: 12 without AEP, 32 with AEP – Opto-coupler isolated – Label customer provisionable – Severity customer provisionable – Common 32 V output for all alarm inputs – Each input limited to 2 mA – Termination: Wire-wrap on backplane without AEP, on AEP connectors with AEP • Alarm outputs – Number of outputs: 4 (user configurable as inputs) without AEP, 16 with AEP – Switched by opto MOS (metal oxide semiconductor) – Triggered by definable alarm condition – Maximum allowed open circuit voltage: 60 VDC – Maximum allowed closed circuit current: 100 mA – Termination: Wire-wrap on backplane without AEP, on AEP connectors with AEP • Express orderwire/local orderwire (EOW/LOW) – ITU-T G.711, ITU-T G.712, Telcordia GR-253-CORE – A-law, mu-law Note Due to the nature of mixed coding, in a mixed-mode (A-law/mu-law) configuration, the orderwire is not ITU-T G.712 compliant. – Orderwire party line – Dual tone, multifrequency (DTMF) signaling • User data channel (UDC) – Bit rate: 64 kbps, codirectional – ITU-T G.703 – Input/output impedance: 120 ohm – Termination: RJ-11 connectors • Data communications channel (DCC) – Bit rate: 576 kbps – EIA/TIA-485/V11 – Input/output impedance: 120 ohm – Termination: RJ-45 connectorsA-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications • ACC connection for additional alarm interfaces – Connection to AEP • Power monitoring alarming states: – Power failure (0 to –38 VDC) – Undervoltage (–38 to –40.5 VDC) – Overvoltage (beyond –56.7 VDC) • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Weight: 1.8 lb (0.82 kg) A.3.7 AEP Specifications (ANSI only) The AEP has the following specifications: • Alarm inputs – Number of inputs: 32 – Optocoupler isolated – Label customer provisionable – Severity customer provisionable – Common 32 V output for all alarm inputs – Each input limited to 2 mA – 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.703 Annex B • Dimensions of AEP board – Height: 20 mm (0.79 in.) – Width: 330 mm (13.0 in.) – Depth: 89 mm (3.5 in.) – Weight: 0.18 kg (0.4 lb) A-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Common Control Card Specifications A.3.8 MIC-A/P FMEC Specifications (ETSI only) The MIC-A/P FMEC card has the following specifications: • Power supply input BATTERY B – System supply voltage: Nominal –48 VDC Tolerance limits: –40.5 to –57.0 VDC – Connector: 3WK3 Combo-D power cable connector • Alarm outputs – Voltage (open contact): Maximum 60 VDC – Current (closed contact): Maximum 250 mA – Connector: 62-pin DB connector (common for inputs/outputs) • Alarm inputs – Voltage (open contact): Maximum 60 VDC – Current (closed contact): Maximum 2 mA – Connector: 62-pin DB connector (common for inputs/outputs) • Dimensions – Height: 182 mm (7.165 in.) – Width: 31.88 mm (1.255 in.) – Depth: 92 mm (3.62 in.) – Depth with backplane connector: 98 mm (3.87 in.) – Weight not including clam shell: 0.2 kg (0.5 lb) A.3.9 MIC-C/T/P FMEC Specifications (ETSI only) The MIC-C/T/P FMEC card has the following specifications: • Power supply input BATTERY A – System supply voltage: Nominal –48 VDC Tolerance limits: –40.5 to –57.0 VDC – Connector: 3WK3 Combo-D power cable connector • Timing connector – Frequency: 2.048 MHz +/–10 ppm – Signal level: 0.75 to 1.5 V – Impedance: 75 ohms +/–5 percent (switchable by jumper to high impedance > 3 kohms) Note 120 ohms balanced impedance is possible with external matching cable. – Cable attenuation: Up to 6 dB at 2 MHz – Connectors: 1.0/2.3 miniature coax connector • System management serial port:A-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Service Channel Cards – System management serial port craft interface – Modem port (for future use) – Connectors: 8-pin RJ-45 • System management LAN port connectors: – Signal: IEEE 802.3 10BaseT – Connectors: 8-pin RJ-45 • Dimensions – Height: 182 mm (7.165 in.) – Width: 31.88 mm (1.255 in.) – Depth: 92 mm (3.62 in.) – Depth with backplane connector: 98 mm (3.87 in.) – Weight not including clam shell: 0.2 kg (0.5 lb) A.3.10 MS-ISC-100T Card Specifications The MS-ISC-100T card has the following specifications: • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – 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.4 Optical Service Channel Cards This section provides specifications for the OSCM and OSC-CSM cards. A.4.1 OSCM Card Specifications The OSCM card has the following specifications: • Line – Bit rate: 155 Mbps – Code: Scrambled non-return to zero (NRZ) – Loopback modes: None – Connector: Duplex LC • Transmitter optical service channel (OSC) signal – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –5 dBm A-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Service Channel Cards – Nominal wavelength: 1510-nm +/–10 nm – Variable optical attenuator (VOA) necessary in the transmit path to adjust the in-fiber optical power level • Receiver OSC signal – Maximum receiver level: –8 dBm at 10–10 bit error rate (BER) – Minimum receiver level: –40 dBm at 10–10 BER – Span budget: 40-dB span budget (about 150 km assuming fiber path loss equals 0.25 dB/km) – Jitter tolerance: Telcordia GR-253/G.823 compliant • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.4.2 OSC-CSM Card Specifications The OSC-CSM card has the following specifications: • Line – Bit rate: 155 Mbps – Code: Scrambled NRZ – Loopback modes: None – Connector: Duplex LC • Transmitter OSC signal – Maximum transmitter output power: –2 dBm – Minimum transmitter output power: –24 dBm – Nominal wavelength: 1510-nm +/–10 nm – VOA is necessary in the transmit path to adjust the in-fiber optical power level • Receiver OSC signal – Maximum receiver level: –8 dBm at 10–10 BER – Minimum receiver level: –40 dBm at 10–10 BER – Span loss budget: 35-dB span budget (approximately 140 km assuming that the fiber path loss is equal to 0.25 dB/km) – Jitter tolerance: Telcordia GR-253/G.823 compliant • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm)A-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Amplifier Cards A.5 Optical Amplifier Cards This section provides specifications for the OPT-PRE amplifier, OPT-BST amplifier, OPT-BST-E amplifier, OPT-BST-L amplifier, OPT-AMP-L preamplifier (configurable as a preamplifier or booster amplifier), OPT-AMP-C amplifier (configurable as a preamplifier or booster amplifier), OPT-AMP-17-C, and OPT-RAMP-C amplifier cards. A.5.1 OPT-PRE Amplifier Card Specifications The OPT-PRE amplifier card has the following specifications: • Optical characteristics: – Total operating wavelength range: 1530 to 1561.3 nm – Gain ripple (peak to valley): 1.5 dB – Mid-access loss (MAL) range (for dispersion compensation unit [DCU]): 3 to 9 dB – Gain range: 5 to 38.5 dBm in constant power mode, 5 to 28 dBm in constant gain mode – Minimum gain (standard range): 5.0 dBm – Maximum gain (standard range with programmable gain tilt): 21 dBm – Maximum gain (extended range with uncontrolled gain tilt): 38.5 dBm – Gain and power regulation over/undershoot: 0.5 dB – Limited maximum output power: 17.5 dBm – Maximum output power (with full channel load): 17 dB – Minimum output power (with one channel): –2 dBm – Input power (Pin) range at full channel load: –21.5 to 12 dBm – Input power (Pin) range at single channel load: –39.5 to –6 dBm – Noise figure at G3 21 dB = 6.5 dB – OSC filter drop (channels) insertion loss maximum: 1 dB – OSC filter drop (OSC) insertion loss maximum: 1.8 dB – OSC filter add (OSC) insertion loss maximum: 1.3 dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (240 mm) A.5.2 OPT-BST Amplifier Card Specifications The OPT-BST amplifier card has the following specifications: • Optical characteristics: – Total operating wavelength range: 1530 to 1561.3 nmA-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Amplifier Cards – Gain ripple (peak to valley): 1.5 dB – Gain range: 5 to 20 dBm with programmable gain tilt – Gain and power regulation over/undershoot: 0.5 dB – Limited maximum output power: 17.5 dBm – Maximum output power (with full channel load): 17 dB – Minimum output power (with one channel): –2 dBm – Input power (Pin) range at full channel load: –3 to 12 dBm – Input power (Pin) range at single channel load: –21 to –6 dBm – Noise figure at G3 20 dB = 6 dB – OSC filter drop (channels) insertion loss maximum: 1 dB – OSC filter drop (OSC) insertion loss maximum: 1.8 dB – OSC filter add (OSC) insertion loss maximum: 1.3 dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (240 mm) A.5.3 OPT-BST-E Amplifier Card Specifications The OPT-BST-E amplifier card has the following specifications: • Optical characteristics: – Total operating wavelength range: 1530 to 1561.3 nm – Gain ripple (peak to valley): 1.8 dB – Gain range: 8 to 23 dB with programmable gain tilt – Extended gain range: 23 to 26 dB with gain tilt uncontrolled – Gain and power regulation over/undershoot: 0.5 dB – Limited maximum output power: 20.5 dBm – Maximum output power (with full channel load): 20 dB – Minimum output power (with one channel): –0 dBm – Input power (Pin) range at full channel load: –6 to 12 dBm – Input power (Pin) range at single channel load: –26 to –8 dBm – Noise figure at G3 23 dB = 6 dB – OSC filter drop (channels) insertion loss maximum: 1 dB – OSC filter drop (OSC) insertion loss maximum: 1.8 dB – OSC filter add (OSC) insertion loss maximum: 1.3 dB – Optical connectors: LC-UPC/2 • DimensionsA-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Amplifier Cards – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (240 mm) A.5.4 OPT-BST-L Amplifier Card Specifications The OPT-BST-L amplifier card has the following specifications: • Optical characteristics: – Total operating wavelength range: 1570.0 to 1605.0 nm – Gain ripple (peak to valley): 1.5 dB – Gain range: 8 to 20 dB with programmable gain tilt – Extended gain range: 20 to 27 dB with gain tilt uncontrolled – Gain and power regulation over/undershoot: 0.5 dB – Limited maximum output power: 10 dBm – Maximum output power (with full channel load): 17 dB – Minimum output power (with one channel): –1 dBm – Input power (Pin) range at full channel load: –10 to 9 dBm – Input power (Pin) range at single channel load: –37 to –18 dBm – Noise figure at G3 20 dB = 7.5 dB – Insertion loss (Line RX to OSC TX): 0.3 to 1.8 dB – Insertion loss (Line RX to COM TX): 0.3 to 1.0 dB – Insertion loss (OSC RX to LINE TX): 0.3 to 1.3 dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (240 mm) A.5.5 OPT-AMP-L Preamplifier Card Specifications The OPT-AMP-L card has the following specifications: • Optical characteristics: – DWDM channel wavelength plan, 100 GHz, 4 skip 1, ITU-T wavelength grid channels 71 (1602.3 nm) to 90 (1570.4 nm) – DWDM channel wavelength plan, 50 GHz, 8 skip 2, ITU-T wavelength grid channels 70.5 (1602.7 nm) to 90 (1570.4 nm) – Channel spacing: 100 and 50 GHz – Total operating wavelength range 1570.0 - 1605.0 nm – Gain ripple (peak to valley): 1.5 dBA-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Amplifier Cards – Standard gain range: 12 to 24 dB – Extended gain range (uncontrolled gain tilt): 24 to 35 dB – Gain and power regulation over/undershoot: 0.5 dB – Minimum output power (with one channel): +2 dBm – Maximum power output (standard or extended gain range): 20 dB – Input power range (full channel load): –15 to 8 dB – Input power range (single channel load): –40 to –17 – Noise figure at G3 20 dB = 8.9 dB – Insertion loss (Line RX to OSC TX): 0.3 to 1.8 dB – Insertion loss (Line RX to COM TX): 0.3 to 1.0 dB – Insertion loss (OSC RX to LINE TX): 0.3 to 1.3 dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (240 mm) A.5.6 OPT-AMP-17-C Amplifier Card Specifications The OPT-AMP-17-C card has the following specifications: • Optical characteristics: – DWDM channel wavelength plan: 80 channels at 50 GHz spacing, 1530.33 nm to 1561.83 nm – Channel spacing: 50 GHz – Total operating wavelength range 1529.0 to 1562.5 nm – Gain ripple (peak to valley): 1.5 dB – Gain range: 14 to 23 dB – Optimal gain (gain tilt = 0): 17 dB – Gain and power regulation over/undershoot: 0.5 dB – Minimum output power (with one channel): –2 dBm – Maximum power output (standard or extended gain range): 17.5 dBm – Input power range (full channel load): –6 to 3 dBm – Input power range (single channel load): –28 to –19 dBm – Noise figure at G=17dB = 6 dB maximum – Insertion loss (Line RX to OSC TX): 0.3 to 1.8 dB – Insertion loss (Line RX to COM TX): 0.3 to 1.0 dB – Insertion loss (OSC RX to LINE TX): 0.3 to 1.3 dB – Optical connectors: LC-UPC/2 • DimensionsA-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Amplifier Cards – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.5.7 OPT-AMP-C Amplifier Card Specifications The OPT-AMP-C amplifier card has the following specifications: • Optical characteristics: – Total operating wavelength range: 1529.0 to 1562.5 nm – Gain ripple (peak to valley): 1.2 dB – Gain range: 12 to 24 dB with programmable gain tilt – Extended gain range: 24 to 35 dB with gain tilt uncontrolled – Gain and power regulation over/undershoot: 0.5 dB – Limited maximum output power: 20.5 dBm – Maximum output power (with full channel load): 20 dBm – Minimum output power (with one channel): –2 dBm – Input power (Pin) at full channel load: –15 dBm minimum – Input power (Pin) range at single channel load: –40 to –17 dBm – Noise figure at G3 20 dB: 7.6 dB – Insertion loss (Line RX to OSC TX): 0.3 to 1.8 dB – Insertion loss (Line RX to COM TX): 0.3 to 1.0 dB – Insertion loss (OSC RX to LINE TX): 0.3 to 1.3 dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 8.66 in. (220.1 mm) A.5.8 OPT-RAMP-C Amplifier Card Specifications The OPT-RAMP-C amplifier card has the following specifications: • Raman pump – Raman pump 1 wavelength: 1425 nm – Raman pump 2 wavelength: 1452 nm – Total Raman Pump power - Line-RX port: 500 mW – Operating range Raman Pump power - Line-RX port: min 100 mW, max 4502 mW – Raman pump laser class: 3B • Embedded EDFAA-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Amplifier Cards – Total operating signal wavelength range: 1529 to 1562.5 nm – EDFA nominal gain value (Line RX to DC-TX): 14 dB – EDFA gain settable range: 8 to 20 dB – EDFA Output Power range - DC-TX (Full Channel load): 17.53 dBm – VOA attenuation range: 0 to 25 dB – Gain and power regulation over/undershoot: 0.5 dB – EDFA laser class: 1M – Maximum EDFA output power: 17.5 dBm – Minimum output power (with one channel): –10 dBm – Input power (Pin) at full channel load: –3 dBm to +9 dBm – Input power (Pin) range at single channel load: –24dBm to –10 dBm – Noise figure at G 14 dB: 7.5 dB – Insertion loss (Line TX to OSC TX): 0.3 to 2.0 dB – Insertion loss (Line RX to COM TX): 0.3 to 1.0 dB – Insertion loss (OSC RX to LINE RX): 0.3 to 1.8 dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 12.65 in. (332 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 8.665 in. (220.1 mm) A.5.9 OPT-RAMP-CE Amplifier Card Specifications The OPT-RAMP-CE amplifier card has the following specifications: • Raman pump – Raman pump 1 wavelength: 1425 nm – Raman pump 2 wavelength: 1452 nm – Total Raman pump power - LINE-RX port: 500 mW – Operating range Raman pump power - LINE-RX port: min 100 mW, max 450 mW – Raman pump laser class: 3B • Embedded EDFA – Total operating signal wavelength range: 1529 to 1562.5 nm – EDFA nominal gain value (LINE-RX to DC-TX): 11 dB – EDFA gain settable range: 5 to 17 dB – EDFA Output power range - DC-TX (Full Channel load): 20.2 dBm – VOA attenuation range: 0 to 25 dB – Gain and power regulation over/undershoot: 0.5 dB – EDFA laser class: 1MA-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications PSM (Protection Switching Module) Card Specifications – Maximum EDFA output power: 20.5 dBm – Minimum output power (with one channel): –10 dBm – Input power (Pin) at full channel load: 15 dBm (maximum) – Input power (Pin) range at single channel load: –27dBm (minimum) – Noise figure at G 11 dB: 7 dB – Insertion loss (LINE-RX to MON-RX):22 to 26 dB – Insertion loss (LINE-TX to OSC-TX): 1.5 dB – Insertion loss (OSC-RX to LINE-RX): 0.7 to 1.7 dB – Insertion loss (LINE-TX to COM-RX): 0.6 to 1.0 dB – Insertion loss (LINE-TX to PD12): 1.7dB – Insertion loss (OSC-RX to LINE-RX): 0.7 to 1.7dB – Optical connectors: LC-UPC/2 • Dimensions – Height: 13.11 in. (333 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.88 in. (251 mm) A.6 PSM (Protection Switching Module) Card Specifications The PSM card has the following specifications: • Wavelength: – Total operating signal wavelength range (C-band range): 1529.0 – 1562.5 nm – OSC wavelength range: 1500 – 1520 nm – L-band range: 1570 - 1605 nm • Optical – Insertion loss: • COM-RX to W-TX and P-TX: 4.6 dB • W-RX and P-RX to COM-TX: 2.3 dB – Insertion loss ripple: 0.2 dB – Maximum optical input power: 300mW – Polarization dependent loss: 0.2 dB – Optical switches state setting time: 5 ms – VOA attenuation setting time in open loop: 20 ms – VOA attenuation setting time in closed loop: 500 ms (applicable to VOA in RX only) – VOA attenuation range: 0 - 15 dB • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included)A-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Multiplexer and Demultiplexer Cards – Depth: 8.66 in. (220.1 mm) A.7 Multiplexer and Demultiplexer Cards This section provides specifications for the 32MUX-O, 32DMX-O, and 4MD-xx.x cards. A.7.1 32MUX-O Card Specifications The 32MUX-O card optical specifications are listed in Table A-2. Note For power specifications, see Table A-1 on page A-2. The 32MUX-O card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.7.2 32DMX-O Card Specifications The 32DMX-O card optical specifications are listed in Table A-3. Note For power specifications, see Table A-1 on page A-2. Table A-2 32MUX-O Optical Specifications Parameter Note Condition Min Max Unit Transmit (Tx) filter shape (–1 dB bandwidth) All standard operating procedures (SOP) and within whole operating temperature range In 1/32—Out beginning of life (BOL) +/–180 +/–300 pm In 1/32—Out end of life (EOL) +/–160 +/–300 pm Insertion loss All SOP and within whole operating temperature range In 1/32—Out BOL 4 8.0 dB In 1/32—Out EOL 4 8.5 dB VOA dynamic range — — 25 — dB Optical monitor tap-splitting ratio on monitor port Optical monitor port with respect to output port in multiplexer only — 19 21 dB Maximum optical input power — — 300 — mWA-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Multiplexer and Demultiplexer Cards The 32DMX-O card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.7.3 4MD-xx.x Card Specifications The 4MD-xx.x card optical specifications are listed in Table A-4. Note For power specifications, see Table A-1 on page A-2. Table A-3 32DMX-O Optical Specifications Parameter Note Condition Min Max Unit Receive (Rx) filter shape (–1 dB bandwidth) All SOP and within whole operating temperature range In 1/32—Out BOL +/–180 +/–300 pm In 1/32—Out EOL +/–160 +/–300 pm Insertion loss All SOP and within whole operating temperature range In 1/32—Out BOL 4 8.0 dB In 1/32—Out EOL 4 8.5 dB VOA dynamic range — — 25 — dB Maximum optical input power — — 300 — mW Table A-4 4MD-xx.x Optical Specifications Parameter Note Condition Min Max Unit Trx filter shape (–0.5 dB bandwidth TrxBW2 ) All SOP and within whole operating temperature range COM Rx—xx.xx Tx COM Rx—yy.yy Tx COM Rx—zz.zz Tx COM Rx—kk.kk Tx +/–180 — pm xx.xx Rx—COM Tx yy.yy Rx—COM Tx zz.zz Rx—COM Tx kk.kk Rx—COM Tx Insertion loss demultiplexer section All SOP and within whole operating temperature range COM Rx—xx.xx Tx — 1.9 dB COM Rx—yy.yy Tx — 2.4 dB COM Rx—zz.zz Tx — 2.8 dB COM Rx—kk.kk Tx — 3.3 dBA-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 4MD-xx.x card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8 Reconfigurable Optical Add/Drop Cards This section provides specifications for the 32DMX, 32DMX-L, 32WSS, 32WSS-L, 40-MUX-C, 40-DMX-C, 40-DMX-CE, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 40-SMR1-C, 40-SMR2-C, and MMU cards. A.8.1 32DMX Card Specifications The 32DMX card optical specifications are listed in Table A-5. Note For power specifications, see Table A-1 on page A-2. Insertion loss multiplexer section All SOP and within whole operating temperature range (two connectors included) xx.xx Rx—COM Tx — 3.6 dB yy.yy Rx—COM Tx — 3.2 dB zz.zz Rx—COM Tx — 3.0 dB kk.kk Rx—COM Tx — 2.6 dB VOA dynamic range — — 25 — dB Maximum optical input power — — 300 — mW Table A-4 4MD-xx.x Optical Specifications (continued) Parameter Note Condition Min Max Unit Table A-5 32DMX Optical Specifications Parameter Note Condition Min Typical Max Units –1 dB bandwidth All SOP and within whole operating temperature range, connectors included, and for maximum VOA operating attenuation. COM RX => TX 1, 32 (OUT) +/–110 — — pm –3 dB bandwidth +/–200 — — pm Insertion loss All SOP, and within whole operating temperature range, connectors included. COM RX => TX 1, 32 — — 5.5 dBA-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 32DMX channel plan is shown in Table A-6. All 32DMX client interfaces must comply with this plan. VOA dynamic range — COM RX => TX 1, 32 25 — — dB Maximum optical input power — — 300 — — mW Table A-5 32DMX Optical Specifications (continued) Parameter Note Condition Min Typical Max Units Table A-6 32DMX Channel Plan Channel Number Band Channel ID Frequency (GHz) Wavelength (nm) 1 1 30.3 195.9 1530.33 2 31.2 195.8 1531.12 3 31.9 195.7 1531.90 4 32.6 195.6 1532.68 5 2 34.2 195.4 1534.25 6 35.0 195.3 1535.04 7 35.8 195.2 1535.82 8 36.6 195.1 1536.61 9 3 38.1 194.9 1538.19 10 38.9 194.8 1538.98 11 39.7 194.7 1539.77 12 40.5 194.6 1540.56 13 4 42.1 194.4 1542.14 14 42.9 194.3 1542.94 15 43.7 194.2 1543.73 16 44.5 194.1 1544.53 17 5 46.1 193.9 1546.12 18 46.9 193.8 1546.92 19 47.7 193.7 1547.72 20 48.5 193.6 1548.51 21 6 50.1 193.4 1550.12 22 50.9 193.3 1550.92 23 51.7 193.2 1551.72 24 52.5 193.1 1552.52A-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 32DMX card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.2 32DMX-L Card Specifications The 32DMX-L card optical specifications are listed in Table A-5. Note For power specifications, see Table A-1 on page A-2. 25 7 54.1 192.9 1554.13 26 54.9 192.8 1554.94 27 55.7 192.7 1555.75 28 56.5 192.6 1556.55 29 8 58.1 192.4 1558.17 30 58.9 192.3 1558.98 31 59.7 192.2 1559.79 32 60.6 192.1 1560.61 Table A-6 32DMX Channel Plan (continued) Channel Number Band Channel ID Frequency (GHz) Wavelength (nm) Table A-7 32DMX -L Optical Specifications Parameter Note Condition Min Typical Max Units –1 dB bandwidth All SOP and within whole operating temperature range, connectors included, and for maximum VOA operating attenuation. COM RX => TX 1, 32 (OUT) +/–100 — — pm –3 dB bandwidth +/–199 — — pm Insertion loss All SOP, and within whole operating temperature range, connectors included. COM RX => TX 1, 32 — — 5.8 dB VOA dynamic range — COM RX => TX 1, 32 25 — — dB Maximum optical input power — — 300 — — mWA-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 32DMX-L channel plan is shown in Table A-8. All 32DMX-L client interfaces must comply with this plan. The 32DMX-L card has the following additional specifications: Table A-8 32DMX-L Channel Plan Band ID Channel Label Frequency (THz) Wavelength (nm) B77.8 77.8 190 1577.86 78.6 189.9 1578.69 79.5 189.8 1579.52 80.3 189.7 1580.35 B81.1 81.1 189.6 1581.18 82.0 189.5 1582.02 82.8 189.4 1582.85 83.6 189.3 1583.69 B84.5 84.5 189.2 1584.53 85.3 189.1 1585.36 86.2 189 1586.20 87.0 188.9 1587.04 B87.8 87.8 188.8 1587.88 88.7 188.7 1588.73 89.5 188.6 1589.57 90.4 188.5 1590.41 B91.2 91.2 188.4 1591.26 92.1 188.3 1592.10 92.9 188.2 1592.95 93.7 188.1 1593.79 B94.6 94.6 188 1594.64 95.4 187.9 1595.49 96.3 187.8 1596.34 97.1 187.7 1597.19 B98.0 98.0 187.6 1598.04 98.8 187.5 1598.89 99.7 187.4 1599.75 00.6 187.3 1600.60 B01.4 01.4 187.2 1601.46 02.3 187.1 1602.31 03.1 187 1603.17 04.0 186.9 1604.03A-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.3 32WSS Card Specifications The 32WSS card optical specifications are listed in Table A-9. Note For power specifications, see Table A-1 on page A-2. The 32WSS channel plan is shown in Table A-10. All 32WSS client interfaces must comply with this plan. Table A-9 32WSS Optical Specifications Parameter Note Condition Min Typical Max Units –0.25 dB bandwidth All SOP and within whole operating temperature range, connectors included, and for maximum VOA operating attenuation. EXP RX => COM TX +/–/95 — — pm –0.5 dB bandwidth +/–115 — — pm –1.0 dB bandwidth +/–135 — — pm –0.25 dB bandwidth Add 1, 32 => COM TX +/–115 — — pm –0.5 dB bandwidth +/–135 — — pm –1.0 dB bandwidth +/–160 — — pm Insertion loss All SOP, any optical switch state, and within whole operating temperature range, connectors included. EXP RX => COM TX — — 11.3 dB — COM RX => EXP TX — — 1.5 dB — Add 1, 32 => COM TX — — 7.6 dB — COM RX => DROP TX 6 — 8.5 dB VOA dynamic range — EXP RX => COM TX 20 — — dB — Add 1, 32 => COM TX 25 — — dB Maximum optical input power — — 300 — — mWA-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 32WSS card has the following additional specifications: • Dimensions Table A-10 32WSS Channel Plan Channel Number Band Channel ID Frequency (GHz) Wavelength (nm) 1 1 30.3 195.9 1530.33 2 31.2 195.8 1531.12 3 31.9 195.7 1531.90 4 32.6 195.6 1532.68 5 2 34.2 195.4 1534.25 6 35.0 195.3 1535.04 7 35.8 195.2 1535.82 8 36.6 195.1 1536.61 9 3 38.1 194.9 1538.19 10 38.9 194.8 1538.98 11 39.7 194.7 1539.77 12 40.5 194.6 1540.56 13 4 42.1 194.4 1542.14 14 42.9 194.3 1542.94 15 43.7 194.2 1543.73 16 44.5 194.1 1544.53 17 5 46.1 193.9 1546.12 18 46.9 193.8 1546.92 19 47.7 193.7 1547.72 20 48.5 193.6 1548.51 21 6 50.1 193.4 1550.12 22 50.9 193.3 1550.92 23 51.7 193.2 1551.72 24 52.5 193.1 1552.52 25 7 54.1 192.9 1554.13 26 54.9 192.8 1554.94 27 55.7 192.7 1555.75 28 56.5 192.6 1556.55 29 8 58.1 192.4 1558.17 30 58.9 192.3 1558.98 31 59.7 192.2 1559.79 32 60.6 192.1 1560.61A-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards – Height: 12.65 in. (321.3 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.4 32WSS-L Card Specifications The 32WSS-L card optical specifications are listed in Table A-11. Note For power specifications, see Table A-1 on page A-2. The 32WSS-L channel plan is shown in Table A-12. All 32WSS-L client interfaces must comply with this plan. Table A-11 32WSS-L Optical Specifications Parameter Note Condition Min Typical Max Units –0.1 dB bandwidth All SOP and within whole operating temperature range, connectors included, and for maximum VOA operating attenuation. EXP RX => COM TX — +/–/57 — pm –0.25 dB bandwidth +/–/61 +/–/89 — –0.5 dB bandwidth +/–91 +/–/116 — –1.0 dB bandwidth +/–135 +/–/149 — –0.1 dB bandwidth Add 1, 32 => COM TX +/–32 +/–/69 — –0.25 dB bandwidth +/–98 +/–/129 — –0.5 dB bandwidth +/–135 +/–/161 — –1.0 dB bandwidth +/–160 +/–/201 — Insertion loss All SOP, any optical switch state, and within whole operating temperature range, connectors included. EXP RX => COM TX — 9.7 11.3 dB COM RX => EXP TX — 1.4 1.6 dB Add 1, 32 => COM TX — 6.2 8.0 dB COM RX => DROP TX 6.0 8.0 8.5 dB VOA dynamic range — EXP RX => COM TX 20 25 — dB — Add 1, 32 => COM TX 25 25 — dB Maximum optical input power — — 300 — — mWA-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 32WSS-L card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) Table A-12 32WSS-L Channel Plan Band ID Channel Label Frequency (THz) Wavelength (nm) B77.8 77.8 190 1577.86 78.6 189.9 1578.69 79.5 189.8 1579.52 80.3 189.7 1580.35 B81.1 81.1 189.6 1581.18 82.0 189.5 1582.02 82.8 189.4 1582.85 83.6 189.3 1583.69 B84.5 84.5 189.2 1584.53 85.3 189.1 1585.36 86.2 189 1586.20 87.0 188.9 1587.04 B87.8 87.8 188.8 1587.88 88.7 188.7 1588.73 89.5 188.6 1589.57 90.4 188.5 1590.41 B91.2 91.2 188.4 1591.26 92.1 188.3 1592.10 92.9 188.2 1592.95 93.7 188.1 1593.79 B94.6 94.6 188 1594.64 95.4 187.9 1595.49 96.3 187.8 1596.34 97.1 187.7 1597.19 B98.0 98.0 187.6 1598.04 98.8 187.5 1598.89 99.7 187.4 1599.75 00.6 187.3 1600.60 B01.4 01.4 187.2 1601.46 02.3 187.1 1602.31 03.1 187 1603.17 04.0 186.9 1604.03A-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.5 40-MUX-C Card Specifications The 40-MUX-C card optical specifications are listed in Table A-13. Note For power specifications, see Table A-1 on page A-2. The 40-MUX-C card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.6 40-DMX-C Card Specifications The 40-DMX-C card optical specifications are listed in Table A-14. Note For power specifications, see Table A-1 on page A-2. Table A-13 40-MUX-C Card Optical Specifications Parameter Note Condition Min Max Unit Transmit (Tx) filter shape All standard operating procedures (SOP) and within whole operating temperature range –1 dB bandwidth, RX 1, 40 => COM TX +/–100 — pm –3 dB bandwidth, RX 1, 40 => COM TX +/–199 — pm Insertion loss All SOP and within whole operating temperature range RX 1, 40 => COM TX 5.8 dB VOA dynamic range — RX 1, 40 => COM TX 25 — dB Maximum optical input power — — 300 — mWA-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 40-DMX-C card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.7 40-DMX-CE Card Specifications The 40-DMX-CE card optical specifications are listed in Table A-15. Note For power specifications, see Table A-1 on page A-2. Table A-14 40-DMX-C Card Optical Specifications Parameter Note Condition Min Max Unit Receive (Rx) filter shape All SOP and within whole operating temperature range –1 dB bandwidth, COM RX => TX 1, 40 (OUT) +/–100 — pm –3 dB bandwidth, COM RX => TX 1, 40 (OUT) +/–199 — pm Insertion loss All SOP and within whole operating temperature range COM RX => TX 1, 40 — 5.8 dB VOA dynamic range — COM RX => TX 1, 40 25 — dB Maximum optical input power — — 300 — mW Table A-15 40-DMX-CE Card Optical Specifications Parameter Note Condition Min Max Unit Receive (Rx) filter shape All SOP and within whole operating temperature range –1 dB bandwidth, COM RX => TX 1, 40 (OUT) +/–100 — pm –3 dB bandwidth, COM RX => TX 1, 40 (OUT) +/–199 — pm Insertion loss All SOP and within whole operating temperature range COM RX => TX 1, 40 — 5.8 dBA-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 40-DMX-CE card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) A.8.8 40-WSS-C Card Specifications The 40-WSS-C card optical specifications are listed in Table A-16. Note For power specifications, see Table A-1 on page A-2. VOA dynamic range — COM RX => TX 1, 40 25 — dB Maximum optical input power — — 300 — mW Table A-15 40-DMX-CE Card Optical Specifications (continued) Parameter Note Condition Min Max Unit Table A-16 40-WSS-C Optical Specifications Parameter Note Condition Min Max Unit Channel grid: –0.1 dB All SOP and within whole operating temperature range EXP_RX to COM_ TX — — pm Channel grid: –0.25 dB +/– 61 — pm Channel grid: –0.5 dB +/– 91 — pm Channel grid: –1.0 dB +/– 135 — pm Channel grid: –0.1 dB All SOP and within whole operating temperature range EXP_RX to COM_ TX +/– 32 — pm Channel grid: –0.25 dB +/– 98 — pm Channel grid: –0.5 dB +/– 135 — pm Channel grid: –1.0 dB +/– 160 — pmA-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 40-WSS-C card channel grid is listed in Table A-17. Insertion loss All SOP and within whole operating temperature range EXP_RX to COM_ TX — 7.5 dB EXP_RX to COM_ TX — 2.3 dB EXP_RX to COM_ TX — 6.0 dB EXP_RX to COM_ TX — 6.8 dB VOA dynamic range — EXP_RX to COM_ TX 20 — dB EXP_RX to COM_ TX 25 — dB Maximum optical input power — — 300 — mW Table A-16 40-WSS-C Optical Specifications (continued) Parameter Note Condition Min Max Unit Table A-17 40-WSS-C Channel Grid Band ID Channel Label Frequency (THz) Wavelength (nm) B30.3 30.3 195.9 1530.33 31.1 195.8 1531.12 31.9 195.7 1531.90 32.6 195.6 1532.68 33.4 195.5 1533.47 B34.2 34.2 195.4 1534.25 35.0 195.3 1535.04 35.8 195.2 1535.82 36.6 195.1 1536.61 37.4 195.0 1537.4 B38.1 38.1 194.9 1538.19 38.9 194.8 1538.98 39.7 194.7 1539.77 40.5 194.6 1540.56 41.3 194.5 1541.35A-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 40-WSS-C card has the following additional specifications: • Dimensions – Height: 8.66 in. (220 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 1.42 in. (36 mm) A.8.9 40-WSS-CE Card Specifications The 40-WSS-CE card optical specifications are listed in Table A-18. B42.1 42.1 194.4 1542.14 42.9 194.3 1542.94 43.7 194.2 1543.73 44.5 194.1 1544.53 45.3 194.0 1545.32 B46.1 46.1 193.9 1546.12 46.9 193.8 1546.92 47.7 193.7 1547.72 48.5 193.6 1548.51 49.3 193.5 1549.32 B50.1 50.1 193.4 1550.12 50.9 193.3 1550.92 51.7 193.2 1551.72 52.5 193.1 1552.52 53.3 193.0 1553.33 54.1 54.1 192.9 1544.13 54.9 192.8 1544.94 55.7 192.7 1555.75 56.5 192.6 1556.55 57.3 192.5 1557.36 B58.1 58.1 192.4 1558.17 58.9 192.3 1558.98 59.7 192.2 1559.79 60.6 192.1 1560.61 61.4 192.0 1561.42 Table A-17 40-WSS-C Channel Grid (continued) Band ID Channel Label Frequency (THz) Wavelength (nm)A-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards Note For power specifications, see Table A-1 on page A-2. The 40-WSS-CE card channel grid is listed in Table A-19. Table A-18 40-WSS-C Card Optical Specifications Parameter Note Condition Min Max Unit Channel grid: –0.1 dB All SOP and within whole operating temperature range EXP RX greater than or equal to COM TX — — pm Channel grid: –0.25 dB +/– 61 — pm Channel grid: –0.5 dB +/– 91 — pm Channel grid: –1.0 dB +/– 135 — pm Channel grid: –0.1 dB All SOP and within whole operating temperature range Add 1, 40 greater than or equal to COM TX +/– 32 — pm Channel grid: –0.25 dB +/– 98 — pm Channel grid: –0.5 dB +/– 135 — pm Channel grid: –1.0 dB +/– 160 — pm Insertion loss All SOP and within whole operating temperature range EXP RX greater than or equal to COM TX — 7.5 dB COM RX greater than or equal to EXP TX — 2.3 dB Add 1, 40 greater than or equal to COM TX — 6.0 dB COM RX greater than or equal to DROP TX — 6.8 dB VOA dynamic range — EXP RX greater than COM TX 20 — dB Add 1, 40 greater than or equal to COM TX 25 — dB Maximum optical input power — — 300 — mWA-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards Table A-19 40-WSS-C Card Channel Grid Band ID Channel Label Frequency (THz) Wavelength (nm) B30.7 30.7 195.85 1530.72 31.5 195.75 1531.51 32.3 195.65 1532.29 33.1 195.55 1533.07 33.9 195.45 1533.86 B34.6 34.6 195.35 1534.64 35.4 195.25 1535.43 36.2 195.15 1536.22 37.0 195.05 1537.00 37.8 194.95 1537.79 B38.6 38.6 194.85 1538.58 39.4 194.75 1539.37 40.1 194.65 1540.16 40.9 194.55 1540.95 41.8 194.45 1541.75 B42.5 42.5 194.35 1542.54 43.3 194.25 1543.33 44.1 194.15 1544.13 44.9 194.05 1544.92 45.7 193.95 1545.72 B46.5 46.5 193.85 1546.52 47.3 193.75 1547.32 48.1 193.65 1548.11 48.9 193.55 1548.91 49.7 193.45 1549.72 B50.5 50.5 193.35 1550.52 51.3 193.25 1551.32 52.1 193.15 1552.12 52.9 193.05 1552.93 53.7 192.95 1553.73 B54.4 54.4 192.85 1554.54 55.3 192.75 1555.34 56.1 192.65 1556.15 56.9 192.55 1556.96 57.8 192.45 1557.77A-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The 40-WSS-CE card has the following additional specifications: • Dimensions – Height: 8.66 in. (220 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 1.42 in. (36 mm) A.8.10 40-WXC-C Card Specifications The 40-WXC-C card optical specifications are listed in Table A-20. Note For power specifications, see Table A-1 on page A-2. The 40-WXC-C card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) for a standard DWDM unit B58.6 58.6 192.35 1558.58 59.4 192.25 1559.39 60.2 192.15 1560.20 61.0 192.05 1561.01 61.8 191.95 1561.83 Table A-19 40-WSS-C Card Channel Grid (continued) Band ID Channel Label Frequency (THz) Wavelength (nm) Table A-20 40-WXC-C Optical Specifications Parameter Note Condition Min Max Unit Channel bandwidth: –0.25 dB All SOP and within whole operating temperature range All paths — — GHz Channel bandwidth: –0.5 dB +/- 20.5 — GHz Channel bandwidth: –1.5 dB — — GHz Channel bandwidth: –03.0 dB +/- 37.5 — GHz Insertion loss All SOP and within whole operating temperature range All paths — 8.5 dB VOA dynamic range — All paths 20 — dB Maximum optical input power — — 300 — mWA-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) for a standard DWDM unit A.8.11 80-WXC-C Card Specifications The 80-WXC-C card optical specifications are listed in Table A-21. Note For power specifications, see Table A-1 on page A-2. The 80-WXC-C card has the following additional specifications: • Dimensions – Height: 13.11 in. (333 mm) for a standard DWDM unit Table A-21 80-WXC-C Card Optical Specifications Parameter Note Condition Min Max Unit Channel grid 50 GHz spaced standard ITU Grid and Channel Zero at 1529.55nm (196 THz) 191.95 196.00 THz Operating Wavelength Bandwidth All SOP; and within whole operating temperature range; connectors included and for minimum operating attenuation All paths +/- 12.5 — GHz Channel bandwidth: –0.25 dB Vendor provided 1 1. Use the value provided by the third-party vendor. — GHz Channel bandwidth: –0.5 dB +/- 12.5 — Channel bandwidth: –1.5 dB +/- 17 — Channel bandwidth: –03.0 dB Vendor provided 1 — Insertion loss All SOP; any optical switch state and within whole operating temperature range; connectors included and for minimum attenuation All paths 2.0 7.0 dB VOA dynamic range — All paths 25 — dB Maximum optical input power — All ports 500 — mWA-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth:9.88 in. (251 mm) for a standard DWDM unit A.8.12 40-SMR1-C Card Specifications The 40-SMR1-C card optical specifications are listed in Table A-22. Note For power specifications, see Table A-1 on page A-2. The EDFA1 amplifier within the 40-SMR1-C card has the following specifications: • Optical characteristics (specified from LINE-RX to EXP-TX) – Total operating wavelength range: 1530 to 1561.5 nm – Gain ripple (peak to valley): 1.2 dB – Mid-access loss (MAL) range (for dispersion compensation unit [DCU]): 0 to 9 dB Table A-22 40-SMR1-C Optical Specifications Parameter Note Condition Min Max Unit Channel bandwidth: –0.25 dB All SOP and within whole operating temperature range, connectors included, and for maximum VOA operating attenuation All WXC paths (ADD-RX to LINE-TX and EXP-RX to LINE-TX) — — pm Channel bandwidth: –0.5 dB +/- 160 — pm Channel bandwidth: –1.5 dB — — pm Channel bandwidth: –3.0 dB +/- 240 — pm Insertion loss All SOP, any optical switch state, and within whole operating temperature range, connectors included All WXC paths (ADD-RX to LINE-TX and EXP-RX to LINE-TX) 2.0 8.1 dB All SOP, within whole operating temperature range, connectors included DROP-TX with respect to EXP-TX — 5.3 dB VOA dynamic range — All WXC paths (ADD-RX to LINE-TX and EXP-RX to LINE-TX) 20 — dB DROP-TX — 25 dB Maximum optical input power Total power sum of all ports — 500 — mWA-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards – Gain range: 7 to 38 dB – Minimum gain (standard range): 7.0 dB – Maximum gain (standard range with programmable gain tilt): 21 dB – Maximum gain (extended range with uncontrolled gain tilt): 38 dB – Gain and power regulation over/undershoot: 0.5 dB – Maximum output power (with full channel load): 17 dBm – Minimum output power (with one channel): -5 dBm – Input power (pin) range at full channel load: -21 to 12 dBm – Input power (pin) range at single channel load: -43 to -10 dBm – Noise figure at G = 21 dB = 7.5 dB The OSC filter within the 40-SMR1-C card has the following specifications: • OSC filter drop (OSC) insertion loss maximum: 1.8 dB • OSC filter add (OSC) insertion loss maximum: 1.3 dB The 40-SMR1-C card has the following additional specifications: • Dimensions – Height: 13.11 in. (333 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.88 in. (251 mm) A.8.13 40-SMR2-C Card Specifications The 40-SMR2-C card optical specifications are listed in Table A-23. Note For power specifications, see Table A-1 on page A-2. Table A-23 40-SMR2-C Optical Specifications Parameter Note Condition Min Max Unit Channel bandwidth: –0.25 dB All SOP and within whole operating temperature range, connectors included, and for maximum VOA operating attenuation All WXC paths (ADD-RX to WXC output, EXP1-RX to WXC output, EXP2-RX to WXC output, and EXP3-RX to WXC output) — — pm Channel bandwidth: –0.5 dB +/- 160 — pm Channel bandwidth: –1.5 dB — — pm Channel bandwidth: –3.0 dB +/- 240 — pmA-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The EDFA1 amplifier within the 40-SMR2-C card has the following specifications: • Optical characteristics (specified from LINE-RX to EXP-TX) – Total operating wavelength range: 1530 to 1561.5 nm – Gain ripple (peak to valley): 1.2 dB – Mid-access loss (MAL) range (for dispersion compensation unit [DCU]): 0 to 9 dB – Gain range: 7 to 38 dBm in constant gain mode – Minimum gain (standard range): 7.0 dBm – Maximum gain (standard range with programmable gain tilt): 21 dBm – Maximum gain (extended range with uncontrolled gain tilt): 38 dBm – Gain and power regulation over/undershoot: 0.5 dB – Maximum output power (with full channel load): 17 dBm – Minimum output power (with one channel): -5 dBm – Input power (pin) range at full channel load: -21 to 12 dBm – Input power (pin) range at single channel load: -43 to -10 dBm – Noise figure at G= 21 dB = 7.5 dB The EDFA2 amplifier within the 40-SMR2-C card has the following specifications: • Optical characteristics (specified from WXC output to LINE-TX) Insertion loss All SOP, any optical switch state, and within whole operating temperature range, connectors included All WXC paths (ADD-RX to WXC output, EXP1-RX to WXC output, EXP2-RX to WXC output, and EXP3-RX to WXC output) 2.0 7 dB All SOP, within whole operating temperature range, connectors included DROP-TX with respect to EXP-TX — 5.3 dB VOA dynamic range — All WXC paths (ADD-RX to WXC output, EXP1-RX to WXC output, EXP2-RX to WXC output, and EXP3-RX to WXC output) 20 — dB DROP-TX — 25 dB Maximum optical input power Total power sum of all ports — 500 — mW Table A-23 40-SMR2-C Optical Specifications (continued) Parameter Note Condition Min Max UnitA-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards – Total operating wavelength range 1530.0 to 1561.5 nm – Gain ripple (peak to valley): 1.2 dB – Gain range: 13 to 26 dB – Optimal gain (gain tilt = 0): 17 dB – Gain and power regulation over/undershoot: 0.5 dB – Minimum output power (with one channel): -5 dBm – Input power range (full channel load): -9 to 4 dBm – Input power range (single channel load): -31 to -18 dBm – Noise figure at G=17dB = 6 dB maximum The OSC filter within the 40-SMR2-C card has the following specifications: • OSC filter drop (OSC) insertion loss maximum: 1.8 dB • OSC filter add (OSC) insertion loss maximum: 1.3 dB The 40-SMR2-C card has the following additional specifications: • Dimensions – Height: 13.11 in. (333 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.88 in. (251 mm) A.8.14 MMU Card Specifications The MMU card optical specifications are listed in Table A-24. Note For power specifications, see Table A-1 on page A-2. Table A-24 MMU Optical Specifications Parameter Note Condition Min Typical Max Units Operating bandwidth All SOP, any optical switch state, and within whole operating temperature range, connectors included. All paths 1500 — 1605 nmA-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Reconfigurable Optical Add/Drop Cards The MMU card has the following additional specifications: • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 8.66 in. (220.1 mm) Insertion loss All SOP, any optical switch state, and within whole operating temperature range, connectors included. EXP RX => COM TX — — 7.0 dB EXP A RX => COM TX — — 2.3 dB COM RX => EXP TX — — 0.8 dB COM RX => EXP A TX — — 14.8 dB Wavelength dependent losses All SOP, any optical switch state, and within whole operating temperature range, connectors included. C-band only — — 0.3 dB L-band only — — 0.3 dB C and L bands — — 0.5 dB Polarization dependent loss (PDL) — C-band only — — 0.2 dB — L-band only — — 0.2 dB — C and L bands — — 0.3 dB Chromatic dispersion All paths –20 — +20 ps/nm Polarization mode dispersion (PMD) — All paths — — 0.1 ps Optical power reading resolution — All photodiodes (both real and virtual) — — 0.1 dB Optical power reading precision — –0.1 — 0.1 dB Directivity All SOP, any optical switch state, and within whole operating temperature range, connectors included. EXP RX => EXP A RX 40 — — dB EXP RX => EXP B RX 40 — — dB EXP A RX => EXP B RX 40 — — dB Return loss — — 40 — — dB Maximum optical input power Maximum handling power — 500 — — mW Table A-24 MMU Optical Specifications (continued) Parameter Note Condition Min Typical Max UnitsA-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards A.9 Optical Add/Drop Cards This section provides specifications for the AD-IC-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, and AD-4B-xx.x cards. A.9.1 AD-1C-xx.x Card Specifications Table A-25 lists the AD-1C-xx.x optical specifications. The AD-1C-xx.x card optical input and output power varies with amplifier output levels and the class of transponder interfaces used. See Table 8-3 on page 8-4 through Table 8-7 on page 8-7 for this information. The AD-1C-xx.x card has the following additional specifications: • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.0 in. (228.6 mm) A.9.2 AD-2C-xx.x Card Specifications Table A-26 lists the AD-2C-xx.x optical specifications. Table A-25 AD-1C-xx.x Card Optical Specifications Parameter Note Condition Min Max Unit Trx filter shape (–0.5 dB bandwidth) TrxBW2 All SOP and within whole operating temperature range COM Rx—xx.xx Tx xx.xx Rx—COM Tx +/–180 — pm Rfx filter shape (–0.5 dB bandwidth) RfxBW2 All SOP and within whole operating temperature range COM Rx—Exp Tx Exp Rx—COM Tx +/–180 — pm Insertion loss (drop section) All SOP and within whole operating temperature range (two connectors included) COM Rx—xx.xx Tx — 2.0 dB Insertion loss (express section) VOA at minimum attenuation; all SOP and within whole operating temperature range (two connectors included) COM Rx—Exp Tx Exp Rx—COM Tx — 2.4 or 1.2 dB Insertion loss (add section) VOA at minimum attenuation; all SOP and within whole operating temperature range (two connectors included) xx.xx Rx—COM Tx — 2.6 dB VOA dynamic range — — 30 — dB Maximum optical input power — — 300 — mWA-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards The AD-2C-xx.x card optical input and output power varies with amplifier output levels and the class of transponder interfaces used. See Table 8-3 on page 8-4 through Table 8-7 on page 8-7 for this information. The AD-2C-xx.x has the following additional specifications: • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.0 in. (228.6 mm) A.9.3 AD-4C-xx.x Card Specifications Table A-27 lists the AD-4C-xx.x optical specifications. Table A-26 AD-2C-xx.x Card Optical Specifications Parameter Note Condition Min Max Unit Trx filter shape (–0.5 dB bandwidth) TrxBW2 All SOP and within whole operating temperature range COM Rx—xx.xx Tx COM Rx—yy.yy Tx +/–180 — pm xx.xx Rx—COM Tx yy.yy Rx—COM Tx +/–180 — Rfx filter shape (–0.5 dB bandwidth) RfxBW2 All SOP and within whole operating temperature range COM Rx—Exp Tx Exp Rx—COM Tx +/–180 — pm Insertion loss (drop section) All SOP and within whole operating temperature range (two connectors included) COM Rx—xx.xx Tx — 2.0 dB COM Rx—yy.yy Tx — 2.4 dB Insertion loss (express section) VOA at minimum attenuation; all SOP and within whole operating temperature range (two connectors included) COM Rx—Exp Tx — 2.7 dB Exp Rx—COM Tx — 1.6 dB Insertion loss (add section) VOA at minimum attenuation; all SOP and within whole operating temperature range (two connectors included) xx.xx Rx—COM Tx — 3.1 dB yy.yy Rx—COM Tx — 2.7 dB VOA dynamic range — — 30 — dB Maximum optical input power — — 300 — mWA-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards The AD-4C-xx.x card optical input and output power varies with amplifier output levels and the class of transponder interfaces used. See Table 8-3 on page 8-4 through Table 8-7 on page 8-7 for this information. The AD-4C-xx.x has the following additional specifications: • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.0 in. (228.6 mm) Table A-27 AD-4C-xx.x Optical Specifications Parameter Note Condition Min Max Unit Channel grid See Table A-28. The channel plan for the AD-4C-xx.x card is identical to the channel plan for the AD-1B-xx.x card. — — —— Trx filter shape (–0.5 dB bandwidth) TrxBW2 All SOP and within whole operating temperature range COM Rx—xx.xx Tx COM Rx—yy.yy Tx COM Rx—zz.zz Tx COM Rx—kk.kk Tx xx.xx Rx—COM Tx yy.yy Rx—COM Tx +/–180 — pm Rfx filter shape (–1 dB bandwidth) RfxBW2 All SOP and within whole operating temperature range COM Rx—Exp Tx Exp Rx—COM Tx — — pm Insertion loss (drop section) All SOP and within whole operating temperature range (two connectors included) COM Rx—xx.xx Tx — 5.5 dB COM Rx—yy.yy Tx — 5.0 dB COM Rx—zz.zz Tx — 4.5 dB COM Rx—kk.kk Tx — 4.1 dB Insertion loss (express section) VOA at minimum attenuation; all SOP and within whole operating temperature range (two connectors included) COM Rx—Exp Tx — 2.7 dB Exp Rx—COM Tx — 1.2 dB Insertion loss (add section) VOA at minimum attenuation; all SOP and within whole operating temperature range (two connectors included) xx.xx Rx—COM Tx — 3.9 dB yy.yy Rx—COM Tx — 4.3 dB zz.zz Rx—COM Tx — 4.5 dB kk.kk Rx—COM Tx — 4.9 dB VOA dynamic range — — 30 — dB Maximum optical input power — — 300 — mWA-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards A.9.4 AD-1B-xx.x Card Specifications Table A-28 lists the unit names, band IDs, channel IDs, frequencies, and wavelengths assigned to the eight versions of the AD-1B-xx.x card. Table A-28 AD-1B-xx.x Channel Allocation Plan by Band Unit Name Band ID Channel ID Frequency (GHz) Wavelength (nm) AD-1B-30.3 B30.3 30.3 195.9 1530.33 30.7 195.85 1530.72 31.1 195.8 1531.12 31.5 195.75 1531.51 31.9 195.7 1531.90 32.2 195.65 1532.29 32.6 195.6 1532.68 33.3 195.55 1533.07 AD-1B-34.2 B34.2 34.2 195.4 1534.25 34.6 195.35 1534.64 35.0 195.3 1535.04 35.4 195.25 1535.43 35.8 195.2 1535.82 36.2 195.15 1536.22 36.6 195.1 1536.61 37.0 195.05 1537.00 AD-1B-38.1 B38.1 38.1 194.9 1538.19 38.5 194.85 1538.58 38.9 194.8 1538.98 39.3 194.75 1539.37 39.7 194.7 1539.77 40.1 194.65 1540.16 40.5 194.6 1540.56 40.9 194.55 1540.95 AD-1B-42.2 B42.1 42.1 194.4 1542.14 42.5 194.35 1542.54 42.9 194.3 1542.94 43.3 194.25 1543.33 43.7 194.2 1543.73 44.1 194.15 1544.13 44.5 194.1 1544.53 44.9 194.05 1544.92A-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards Table A-29 lists AD-1B-xx.x optical specifications. AD-1B-46.1 B46.1 46.1 193.9 1546.12 46.5 193.85 1546.52 46.9 193.8 1546.92 47.3 193.75 1547.32 47.7 193.7 1547.72 48.1 193.65 1548.11 48.5 193.6 1548.51 48.9 193.55 1548.91 AD-1B-50.1 B50.1 50.1 193.4 1550.12 50.5 193.35 1550.52 50.9 193.3 1550.92 51.3 193.25 1551.32 51.7 193.2 1551.72 52.1 193.15 1552.12 52.5 193.1 1552.52 52.9 193.05 1552.93 AD-1B-54.1 B54.1 54.1 192.9 1554.13 54.5 192.85 1554.54 54.9 192.8 1554.94 55.3 192.75 1555.34 55.7 192.7 1555.75 56.1 192.65 1556.15 56.5 192.6 1556.96 56.9 192.55 1556.96 AD-1B-58.1 B58.1 58.1 192.4 1558.17 58.5 192.35 1558.58 58.9 192.3 1558.98 59.3 192.25 1559.39 59.7 192.2 1559.79 60.2 192.15 1560.20 60.6 192.1 1560.61 61.0 192.05 1561.01 Table A-28 AD-1B-xx.x Channel Allocation Plan by Band (continued) Unit Name Band ID Channel ID Frequency (GHz) Wavelength (nm)A-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards Table A-30 lists the range of wavelengths for the receive (express) band. The AD-1B-xx.x card optical input and output power varies with amplifier output levels and the class of transponder interfaces used. See Table 8-3 on page 8-4 through Table 8-7 on page 8-7 for this information. The AD-1B-xx.x card has the following additional specifications: Table A-29 AD-1B-xx.x Optical Specifications Parameter Note Condition Min Max Unit –1 dB bandwidth All SOP and within whole operating environmental range COM Rx—Band Tx Band Rx—COM Tx 3.6 — nm –1 dB bandwidth All SOP and within whole operating temperature range COM Rx—Exp Tx Exp Rx—COM Tx See Table A-30. nm Insertion loss (drop section) All SOP and within whole operating environmental range; two connectors included, VOA set at minimum attenuation COM Rx—Band Tx — 3.0 dB Insertion loss (express section) All SOP and within whole operating environmental range; two connectors included Exp Rx—COM Tx — 1.6 dB All SOP and within whole operating environmental range; two connectors included, VOA set at its minimum attenuation COM Rx—Exp Tx — 2.2 dB Insertion loss (add section) All SOP and within whole operating environmental range; two connectors included Band Rx—COM Tx — 2.2 dB VOA dynamic range — — 30 — dB Maximum optical input power — — 300 — mW Table A-30 AD-1B-xx.x Transmit and Receive Dropped Band Wavelength Ranges Tx (Dropped) Band Rx (Express) Band Left Side (nm) Right Side (nm) B30.3 — Wavelengths 1533.825 or higher B34.2 Wavelengths 1533.395 or lower Wavelengths 1537.765 or higher B38.1 Wavelengths 1537.325 or lower Wavelengths 1541.715 or higher 42.1 Wavelengths 1541.275 or lower Wavelengths 1545.695 or higher 46.1 Wavelengths 1545.245 or lower Wavelengths 1549.695 or higher 50.1 Wavelengths 1549.235 or lower Wavelengths 1553.705 or higher 54.1 Wavelengths 1553.255 or lower Wavelengths 1557.745 or higher 58.1 Wavelengths 1557.285 or lower —A-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.0 in. (228.6 mm) A.9.5 AD-4B-xx.x Card Specifications Table A-31 lists the unit names, band IDs, channel IDs, frequencies, and wavelengths assigned to the two versions of the card.A-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards Table A-31 AD-4B-xx.x Channel Allocation Plan by Band Unit Name Band ID Channel ID Frequency (GHz) Wavelength (nm) AD-4B-30.3 B30.3 30.3 195.9 1530.33 30.7 195.85 1530.72 31.1 195.8 1531.12 31.5 195.75 1531.51 31.9 195.7 1531.90 32.2 195.65 1532.29 32.6 195.6 1532.68 33.3 195.55 1533.07 B34.2 34.2 195.4 1534.25 34.6 195.35 1534.64 35.0 195.3 1535.04 35.4 195.25 1535.43 35.8 195.2 1535.82 36.2 195.15 1536.22 36.6 195.1 1536.61 37.0 195.05 1537.00 B38.1 38.1 194.9 1538.19 38.5 194.85 1538.58 38.9 194.8 1538.98 39.3 194.75 1539.37 39.7 194.7 1539.77 40.1 194.65 1540.16 40.5 194.6 1540.56 40.9 194.55 1540.95 B42.1 42.1 194.4 1542.14 42.5 194.35 1542.54 42.9 194.3 1542.94 43.3 194.25 1543.33 43.7 194.2 1543.73 44.1 194.15 1544.13 44.5 194.1 1544.53 44.9 194.05 1544.92A-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards Table A-32 lists AD-4B-xx.x optical specifications. AD-4B-46.1 B46.1 46.1 193.9 1546.12 46.5 193.85 1546.52 46.9 193.8 1546.92 47.3 193.75 1547.32 47.7 193.7 1547.72 48.1 193.65 1548.11 48.5 193.6 1548.51 48.9 193.55 1548.91 B50.1 50.1 193.4 1550.12 50.5 193.35 1550.52 50.9 193.3 1550.92 51.3 193.25 1551.32 51.7 193.2 1551.72 52.1 193.15 1552.12 52.5 193.1 1552.52 52.9 193.05 1552.93 B54.1 54.1 192.9 1554.13 54.5 192.85 1554.54 54.9 192.8 1554.94 55.3 192.75 1555.34 55.7 192.7 1555.75 56.1 192.65 1556.15 56.5 192.6 1556.96 56.9 192.55 1556.96 B58.1 58.1 192.4 1558.17 58.5 192.35 1558.58 58.9 192.3 1558.98 59.3 192.25 1559.39 59.7 192.2 1559.79 60.2 192.15 1560.20 60.6 192.1 1560.61 61.0 192.05 1561.01 Table A-31 AD-4B-xx.x Channel Allocation Plan by Band (continued) Unit Name Band ID Channel ID Frequency (GHz) Wavelength (nm)A-53 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Optical Add/Drop Cards Table A-33 lists the range of wavelengths for the receive (express) band. Table A-32 AD-4B-xx.x Optical Specifications Parameter Note Condition Min Max Unit –1 dB bandwidth All SOP and within whole operating environmental range COM Rx—Band Tx Band Rx—COM Tx 3.6 — nm –1 dB bandwidth All SOP and within whole operating temperature range COM Rx—Exp Tx Exp Rx—COM Tx Refer to Table A-33. nm Insertion loss (drop section) All SOP and within whole operating environmental range; two connectors included, VOA set at minimum attenuation COM Rx—Band Tx 30.3/46.1 — 2.9 dB COM Rx—Band Tx 34.2/50.1 — 3.3 dB COM Rx—Band Tx 38.1/54.1 — 3.8 dB COM Rx—Band Tx 42.1/58.1 — 4.5 dB Insertion loss (express section) All SOP and within whole operating environmental range; two connectors included Exp Rx—COM Tx — 4.9 dB All SOP and within whole operating environmental range; two connectors included, VOA set at its minimum attenuation COM Rx—Exp Tx — 3 dB Insertion loss (add section) All SOP and within whole operating environmental range; two connectors included Band Rx 30.3/46.1—COM Tx — 3.5 dB Band Rx 34.2/50.1—COM Tx — 2.8 dB Band Rx 38.1/54.1—COM Tx — 2.3 dB Band Rx 42.1/58.1—COM Tx — 1.8 dB VOA dynamic range — — 30 — dB Maximum optical input power — — 300 — mW Table A-33 AD-4B-xx.x Transmit and Receive Dropped Band Wavelength Ranges Tx (Dropped) Band Rx (Express) Band Left Side (nm) Right Side (nm) B30.3 — Wavelengths 1533.825 or higher B34.2 Wavelengths 1533.395 or lower Wavelengths 1537.765 or higher B38.1 Wavelengths 1537.325 or lower Wavelengths 1541.715 or higher B42.1 Wavelengths 1541.275 or lower Wavelengths 1545.695 or higherA-54 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications The AD-4B-xx.x card optical input and output power varies with amplifier output levels and the class of transponder interfaces used. See Table 8-3 on page 8-4 through Table 8-7 on page 8-7 for this information. The AD-4B-xx.x has the following additional specifications: • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.0 in. (228.6 mm) A.10 Transponder and Muxponder Card Specifications This section provides specifications for the TXP_MR_10G, MXP_2.5G_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10EX_C, MXP_2.5G_10E, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_10EX_C, MXP_MR_10DME_C, MXP_MR_10DME_L, MXP_MR_10DMEX_C, 40G-MXP-C, ADM-10G, and OTU2_XP cards. For compliance information, refer to the Cisco Optical Transport Products Safety and Compliance Information document. A.10.1 TXP_MR_10G Card Specifications The TXP_MR_10G card has the following specifications: • Line (trunk side) – Bit rate: 9.95328 Gbps for OC-192/STM-64 10.70923 Gbps with ITU-T G.709 Digital Wrapper/forward error correction (FEC) 10.3125 Gbps for 10 Gigabit Ethernet (GE) 11.095 Gbps with ITU-T G.709 Digital Wrapper/FEC over 10 GE – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: 1000 ps/nm – Loopback modes: Terminal and facility B46.1 Wavelengths 1545.245 or lower Wavelengths 1549.695 or higher B50.1 Wavelengths 1549.235 or lower Wavelengths 1553.705 or higher B54.1 Wavelengths 1553.255 or lower Wavelengths 1557.745 or higher B58.1 Wavelengths 1557.285 or lower — Table A-33 AD-4B-xx.x Transmit and Receive Dropped Band Wavelength Ranges (continued) Tx (Dropped) Band Rx (Express) Band Left Side (nm) Right Side (nm)A-55 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10G card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10G card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10G card. – Connectors: LC – Compliance Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.691 • Transmitter (trunk side) – Maximum transmitter output power: +3.5 dBm – Minimum transmitter output power: +2.5 dBm – Transmitter: Lithium Niobate (LN) external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of TXP_MR_10G (16 card versions, each covering two wavelengths): – 1530.33 to 1531.12 nm (two wavelengths) – 1531.90 to 1532.68 nm (two wavelengths) – 1534.25 to 1535.04 nm (two wavelengths) – 1535.82 to 1536.61 nm (two wavelengths) – 1538.19 to 1538.98 nm (two wavelengths) – 1539.77 to 1540.56 nm (two wavelengths) – 1542.14 to 1542.94 nm (two wavelengths) – 1543.73 to 1544.53 nm (two wavelengths) – 1546.12 to 1546.92 nm (two wavelengths) – 1547.72 to 1548.51 nm (two wavelengths) – 1550.12 to 1550.92 nm (two wavelengths) – 1551.72 to 1552.52 nm (two wavelengths) – 1554.13 to 1554.94 nm (two wavelengths) – 1555.75 to 1556.55 nm (two wavelengths) – 1558.17 to 1558.98 nm (two wavelengths) – 1559.79 to 1560.61 nm (two wavelengths) • Receiver (trunk side): – Receiver input power (no FEC, unamplified, 23 dB optical signal-to-noise ratio [OSNR], BER 1 * 10 exp – 12): –8 to –21 dBm – Receiver input power (no FEC, unamplified, 23 dB OSNR, at +/– 1000 ps/nm BER 1 * 10 exp – 12): –8 to –19 dBm – Receiver input power (no FEC, amplified, 19 dB OSNR, BER 1 * 10 exp – 12): –8 to –20 dBmA-56 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver input power (no FEC, amplified, 19 dB OSNR, at +/– 1000 ps/nm BER 1 * 10 exp – 12):–8 to –18 dBm – Receiver input power (FEC, unamplified, 23 dB OSNR, BER 8 * 10 exp – 5): –8 to –24 dBm – Receiver input power (FEC, unamplified, 23 dB OSNR, at +/– 1000 ps/nm, BER 8 * 10 exp – 5): –8 to –22 dBm – Receiver input power (FEC, amplified, 9 dB OSNR, BER 8 * 10 exp – 5): –8 to –18 dBm – Receiver input power (FEC, unamplified, 11 dB OSNR, at +/– 800 ps/nm, BER 8 * 10 exp – 5): –8 to –18 dBm • Line (client side) – Bit rate: 9.95328 Gbps or 10.3125 Gbps – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: Compliant with SR-1 specification for OC-192. In the case of 10 GE, the allowance is up to 10 km of single-mode fiber (SMF) dispersion. – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: 1290 to 1330 nm – Nominal wavelength: 1310 nm – Transmitter: Distributed feedback (DFB) laser • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: avalanche photodiode (APD) – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.2 MXP_2.5G_10G Card Specifications The MXP_2.5G_10G card has the following specifications: • Line (trunk side) A-57 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Bit rate: 9.95328 Gbps for OC-192/STM-64 10.70923 Gbps with ITU-T G.709 Digital Wrapper/FEC – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: 1000 ps/nm – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10G card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10G card. Using direct fiber loopbacks causes irreparable damage to the MXP_2.5G_10G card. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +3.5 dBm – Minimum transmitter output power: +2.5 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of MXP_2.5G_10G (16 card versions, each covering two wavelengths): – 1530.33 to 1531.12 nm (two wavelengths) – 1531.90 to 1532.68 nm (two wavelengths) – 1534.25 to 1535.04 nm (two wavelengths) – 1535.82 to 1536.61 nm (two wavelengths) – 1538.19 to 1538.98 nm (two wavelengths) – 1539.77 to 1540.56 nm (two wavelengths) – 1542.14 to 1542.94 nm (two wavelengths) – 1543.73 to 1544.53 nm (two wavelengths) – 1546.12 to 1546.92 nm (two wavelengths) – 1547.72 to 1548.51 nm (two wavelengths) – 1550.12 to 1550.92 nm (two wavelengths) – 1551.72 to 1552.52 nm (two wavelengths) – 1554.13 to 1554.94 nm (two wavelengths) – 1555.75 to 1556.55 nm (two wavelengths) – 1558.17 to 1558.98 nm (two wavelengths)A-58 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – 1559.79 to 1560.61 nm (two wavelengths) • Receiver (trunk side) – Receiver input power (no FEC, unamplified, 23 dB OSNR, BER 1 * 10 exp – 12): –8 to –21 dBm – Receiver input power (no FEC, unamplified, 23 dB OSNR, at +/– 1000 ps/nm BER 1 * 10 exp – 12): –8 to –19 dBm – Receiver input power (no FEC, amplified, 19 dB OSNR, BER 1 * 10 exp – 12): –8 to –20 dBm – Receiver input power (no FEC, amplified, 19 dB OSNR, at +/– 1000 ps/nm BER 1 * 10 exp – 12): –8 to –18 dBm – Receiver input power (FEC, unamplified, 23 dB OSNR, BER 8 * 10 exp – 5): –8 to –24 dBm – Receiver input power (FEC, unamplified, 23 dB OSNR, at +/– 1000 ps/nm, BER 8 * 10 exp – 5): –8 to –22 dBm – Receiver input power (FEC, amplified, 9 dB OSNR, BER 8 * 10 exp – 5): –8 to –18 dBm – Receiver input power (FEC, unamplified, 11 dB OSNR, at +/– 800 ps/nm, BER 8 * 10 exp – 5): –8 to –18 dBm • Line (client side) – Bit rate: 2.48832 Gbps – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: Compliant with SR-1 specification for OC-192. In the case of 10 GE, allowance is up to 10 km of SMF fiber of dispersion. – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side): Depends on the Small Form-factor Pluggable (SFP) that is used. • Receiver (client side): Depends on the SFP that is used. • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.3 TXP_MR_2.5G and TXPP_MR_2.5G Card Specifications The TXP_MR_2.5G and TXPP_MR_2.5G cards have the following specifications: • Line (trunk side) – Bit rate: 2.488 Gbps for OC-48/STM-16 2.66 Gbps with ITU-T G.709 Digital Wrapper/FEC – Code: Scrambled NRZ A-59 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: 5400 ps/nm – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the TXP_MR_2.5G and TXPP_MR_2.5G cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_2.5G and TXPP_MR_2.5G cards. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_2.5G and TXPP_MR_2.5G cards. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +1 dBm – Minimum transmitter output power: –4.5 dBm – Transmitter: Direct modulated laser – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths of TXP_MR_2.5G and TXPP_MR_2.5G (eight card versions): ITU grid blue band: 1530.334 to 1544.526 nm (four card versions covering four wavelengths each) ITU grid red band: 1546.119 to 1560.606 nm (four card versions covering four wavelengths each) • Receiver (trunk side, see Table A-34) – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion Table A-34 TXP_MR_2.5G/TXPP_MR_2.5G Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm resolution bandwidth (RBW) FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity Chromatic Dispersion Tolerance 22 dB Off - 2R < 10 exp – 12 N/A – 9 to – 24 dBm — 22 dB Off - 2R < 10 exp – 12 N/A – 9 to – 21 dBm +/– 3300ps/nm 21 dB Off - 3R < 10 exp – 12 N/A – 9 to – 30 dBm — 22 dB Off - 3R < 10 exp – 12 N/A – 9 to – 30 dBm +/– 1800ps/nm 23 dB Off - 3R < 10 exp – 12 N/A – 9 to – 30 dBm +/– 5400ps/nm 12 dB Standard- 3R < 10 exp – 5 < 10 exp – 15 – 9 to – 25 dBm — 12 dB Standard- 3R < 10 exp – 5 < 10 exp – 15 – 9 to – 24 dBm +/– 1800ps/nm 12 dB Standard- 3R < 10 exp – 5 < 10 exp – 15 – 9 to – 23 dBm +/– 5400ps/nm 21 dB Standard- 3R < 10 exp – 5 < 10 exp – 15 – 9 to – 31 dBm — A-60 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Line (client side) – Bit rate: 8 Mbps to 2.488 Gbps – Code: Scrambled NRZ – Fiber: Based on SFP (1310-nm single-mode or 850-nm multimode) – Maximum chromatic dispersion allowance: Based on SFP – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: Based on SFP – Nominal wavelength: Based on SFP – Transmitter: Based on SFP • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 850nm to 1605 nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.4 MXP_MR_2.5G and MXPP_MR_2.5G Card Specifications The MXP_MR_2.5G and MXPP_MR_2.5G cards have the following specifications: • Payload configuration – FC1G—Fibre Channel 1.06 Gbps – FC2G—Fibre Channel 2.125 Gbps – FICON1G—Fiber connectivity 1.06 Gbps (IBM signal) – FICON2G—Fiber connectivity 2.125 Gbps (IBM signal) – ESCON—Enterprise System Connection 200 Mbps – ONE_GE—One Gigabit Ethernet 1.125 GbpsA-61 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Mixed configurations up to maximum line rate of 2.5 Gbps (for example, if you have a port configured for FC2G, you cannot use another port at the same time). See the “10.9 MXP_MR_2.5G and MXPP_MR_2.5G Cards” section on page 10-49 for more information on mixed-mode operation. • Client ports: 8x SFP • Performance monitoring (PM) for all interfaces • Buffer-to-buffer credit management for distance extension • Line (trunk side) – Bit rate: 2.488 Gbps for OC-48/STM-16 – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: 6000 ps/nm – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_MR_2.5G and MXPP_MR_2.5G cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_MR_2.5G and MXPP_MR_2.5G cards. Using direct fiber loopbacks causes irreparable damage to the MXP_MR_2.5G and MXPP_MR_2.5G cards. – Connectors: LC • Transmitter (trunk side) – Transmit power: +3 +/– 1 dBm with MXP_MR_2.5G card, and +/– 1 dBm with MXPP_MR_2.5G card – 50-GHz DWDM migration ready (the wavelength deviation is less than +/– 0.040 nm through wavelocker deployment) – Four-channel wavelength tunability at 100-GHz spacing – Transmitter maximum return reflectance: –27 dB – Chromatic dispersion allowance: 5400 ps/nm, giving an optical power penalty < 2.0 dB – Minimum side mode suppression ratio: 30 dB – Transmitter is a direct modulated laser – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths of the TXP_MR_2.5G and TXPP_MR_2.5G cards (eight card versions): – ITU grid blue band: 1530.334 to 1544.526 nm (four card versions, four wavelengths each) – ITU grid red band: 1546.119 to 1560.606 nm (four card versions, four wavelengths each) • Receiver (trunk side, see Table A-35) A-62 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver sensitivity –28 dBm, BER 1 * 10 exp – 12 – Receiver overload is equal to or exceeds –8 dBm – Receiver maximum reflectance of –27 dB • Line (client side) – Bit rate: 200Mbps or 1.06 Gbps to 2.125 Gbps per client – Code: Scrambled NRZ – Fiber: Based on SFP (1310-nm single-mode or 850-nm multimode) – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: Based on SFP – Nominal wavelength: Based on SFP – Transmitter: Based on SFP • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm or 850nm • Dimensions – Height: 12.650 in. (321.3 mm) Table A-35 MXP_MR_2.5G/MXPP_MR_2.5G Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity Chromatic Dispersion Tolerance 17 dB N/A < 10 exp – 12 N/A – 9 to – 23 dBm — 17 dB N/A < 10 exp – 12 N/A – 9 to – 22 dBm +/– 1800 ps/nm 17 dB N/A < 10 exp – 12 N/A – 9 to – 21 dBm +/– 5400 ps/nm 18 dB N/A < 10 exp – 12 N/A – 9 to – 23 dBm +/– 1800 ps/nm 19 dB N/A < 10 exp – 12 N/A – 9 to – 23 dBm +/– 5400 ps/nm 21 dB N/A < 10 exp – 12 N/A – 9 to – 30 dBm — 21 dB N/A < 10 exp – 12 N/A – 9 to – 29 dBm +/– 1800 ps/nm 21 dB N/A < 10 exp – 12 N/A – 9 to – 28 dBm +/– 5400 ps/nm 22 dB N/A < 10 exp – 12 N/A – 9 to – 30 dBm +/– 1800 ps/nm 23 dB N/A < 10 exp – 12 N/A – 9 to – 30 dBm +/– 5400 ps/nmA-63 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 2.25 lb (1.02 kg) A.10.5 MXP_2.5G_10E Card Specifications The MXP_2.5G_10E card has the following specifications: • Line (trunk side) – Bit rate: 10.70923 Gbps (in ITU-T G.709 Digital Wrapper/FEC mode) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1200 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10E card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10E card. Using direct fiber loopbacks causes irreparable damage to the MXP_2.5G_10E card. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of MXP_2.5G_10E (eight card versions): ITU grid blue band: – 1530.33 to 1533.07 nm (four channels) – 1534.25 to 1537.00 nm (four channels) – 1538.19 to 1540.95 nm (four channels) – 1542.14 to 1544.92 nm (four channels) ITU grid red band: – 1546.12 to 1548.92 nm (four channels) – 1550.12 to 1552.93 nm (four channels) – 1554.13 to 1556.96 nm (four channels) – 1558.17 to 1561.01 nm (four channels)A-64 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-36) – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion • Line (client side) – Bit rate: 2.5 Gbps per port (OC-48/STM-16) – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 12 ps/nm (SR SFP version) – Loopback modes: Terminal and facility – Connectors: LC (optical) • Transmitter (client side): Depends on the SFP that is used. • Receiver (client side): Depends on the SFP that is used. • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.6 MXP_2.5G_10E_C Card Specifications The MXP_2.5G_10E_C card has the following specifications: • Line (trunk side) – Bit rate: 10.70923 Gbps (in ITU-T G.709 Digital Wrapper/FEC mode) Table A-36 MXP_2.5G_10E Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 2. Receiver filter bandwidth greater than or equal to 180 pm (at – 3 dBm) Chromatic Dispersion Tolerance 30 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm +/– 1200 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm +/– 1000 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 22 dBm — 17 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 15 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm — 15 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 14 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm —A-65 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1200 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10E_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10E_C card. Using direct fiber loopbacks causes irreparable damage to the card. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of MXP_2.5G_10E_C card: There is a single version of the MXP_2.5G_10E_C card. It is tunable across 82 wavelengths in the C-band frequency plan, with channels on the ITU 50-GHz grid, as shown in Table A-37. Table A-37 MXP_2.5G_10E_C Card Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918A-66 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-38) 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table A-37 MXP_2.5G_10E_C Card Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table A-38 MXP_2.5G_10E_C Card Receiver Trunk Side Specifications OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion Tolerance 30 dB Off < 10 exp – 12 N/A – 8 to – 18 dBm +/– 1200 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 18 dBm +/– 1000 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 18 dBm —A-67 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications 17 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 15.5 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm — 14 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm Table A-38 MXP_2.5G_10E_C Card Receiver Trunk Side Specifications (continued) OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion ToleranceA-68 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm • Line (client side) – Bit rate: 2.5 Gbps per port (OC-48/STM-16) – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 12 ps/nm (SR SFP version) – Loopback modes: Terminal and facility – Connectors: LC (optical) • Transmitter (client side): Depends on the SFP that is used. • Receiver (client side): Depends on the SFP that is used. • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.7 MXP_2.5G_10E_L Card Specifications The MXP_2.5G_10E_L card has the following specifications: • Line (trunk side) – Bit rate: 10.70923 Gbps (in ITU-T G.709 Digital Wrapper/FEC mode) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1200 ps/nm (specified penalty) – Loopback modes: Terminal and facility 12 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm — 1. OSNR defined with 0.1 nm RBW 2. Receiver filter bandwidth 32.5GHz (at - 3 dB) Table A-38 MXP_2.5G_10E_C Card Receiver Trunk Side Specifications (continued) OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion ToleranceA-69 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10E_L card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10E_L card. Using direct fiber loopbacks causes irreparable damage to the card. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of MXP_2.5G_10E_L card: There is a single version of the MXP_2.5G_10E_L card. It is tunable across 80 wavelengths in the L band frequency plan, with channels on the ITU 50-GHz grid, as shown in Table A-39. Table A-39 MXP_2.5G_10E_L Card Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 190.85 1570.83 41 188.85 1587.46 2 190.8 1571.24 42 188.8 1587.88 3 190.75 1571.65 43 188.75 1588.30 4 190.7 1572.06 44 188.7 1588.73 5 190.65 1572.48 45 188.65 1589.15 6 190.6 1572.89 46 188.6 1589.57 7 190.55 1573.30 47 188.55 1589.99 8 190.5 1573.71 48 188.5 1590.41 9 190.45 1574.13 49 188.45 1590.83 10 190.4 1574.54 50 188.4 1591.26 11 190.35 1574.95 51 188.35 1591.68 12 190.3 1575.37 52 188.3 1592.10 13 190.25 1575.78 53 188.25 1592.52 14 190.2 1576.20 54 188.2 1592.95 15 190.15 1576.61 55 188.15 1593.37 16 190.1 1577.03 56 188.1 1593.79 17 190.05 1577.44 57 188.05 1594.22 18 190 1577.86 58 188 1594.64A-70 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-40) 19 189.95 1578.27 59 187.95 1595.06 20 189.9 1578.69 60 187.9 1595.49 21 189.85 1579.10 61 187.85 1595.91 22 189.8 1579.52 62 187.8 1596.34 23 189.75 1579.93 63 187.75 1596.76 24 189.7 1580.35 64 187.7 1597.19 25 189.65 1580.77 65 187.65 1597.62 26 189.6 1581.18 66 187.6 1598.04 27 189.55 1581.60 67 187.55 1598.47 28 189.5 1582.02 68 187.5 1598.89 29 189.45 1582.44 69 187.45 1599.32 30 189.4 1582.85 70 187.4 1599.75 31 189.35 1583.27 71 187.35 1600.17 32 189.3 1583.69 72 187.3 1600.60 33 189.25 1584.11 73 187.25 1601.03 34 189.2 1584.53 74 187.2 1601.46 35 189.15 1584.95 75 187.15 1601.88 36 189.1 1585.36 76 187.1 1602.31 37 189.05 1585.78 77 187.05 1602.74 38 189 1586.20 78 187 1603.17 39 188.95 1586.62 79 186.95 1603.60 40 188.9 1587.04 80 186.9 1604.03 Table A-39 MXP_2.5G_10E_L Card Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table A-40 MXP_2.5G_10E_L Card Receiver Trunk Side Specifications OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion Tolerance 30 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm +/– 1200 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm +/– 1000 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 22 dBm — 17 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 15.5 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm — 15 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nmA-71 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1570 to 1604 nm • Line (client side) – Bit rate: 2.5 Gbps per port (OC-48/STM-16) – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 12 ps/nm (SR SFP version) – Loopback modes: Terminal and facility – Connectors: LC (optical) • Transmitter (client side): Depends on the SFP that is used. • Receiver (client side): Depends on the SFP that is used. • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.8 MXP_2.5G_10EX_C Card Specifications The MXP_2.5G_10EX_C card has the following specifications: • Line (trunk side) – Bit rate: 10.70923 Gbps (in ITU-T G.709 Digital Wrapper/FEC mode) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1600 ps/nm (specified penalty) – Loopback modes: Terminal and facility 13 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm — 1. OSNR defined with 0.1 nm RBW 2. Receiver filter bandwidth greater than or equal to 180 pm (at – 3 dBm) Table A-40 MXP_2.5G_10E_L Card Receiver Trunk Side Specifications (continued) OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion ToleranceA-72 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10EX_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10EX_C card. Using direct fiber loopbacks causes irreparable damage to the card. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of MXP_2.5G_10EX_C card: There is a single version of the MXP_2.5G_10EX_C card. It is tunable across 82 wavelengths in the C-band frequency plan, with channels on the ITU 50-GHz grid, as shown in Table A-37. Table A-41 MXP_2.5G_10EX_C Card Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.12 3 195.90 1530.334 44 193.85 1546.52 4 195.85 1530.725 45 193.80 1546.92 5 195.80 1531.116 46 193.75 1547.32 6 195.75 1531.507 47 193.70 1547.72 7 195.70 1531.898 48 193.65 1548.11 8 195.65 1532.290 49 193.60 1548.51 9 195.60 1532.681 50 193.55 1548.91 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.72 12 195.45 1533.86 53 193.40 1550.12 13 195.40 1534.250 54 193.35 1550.52 14 195.35 1534.643 55 193.30 1550.92 15 195.30 1535.036 56 193.25 1551.32 16 195.25 1535.429 57 193.20 1551.72 17 195.20 1535.822 58 193.15 1552.12 18 195.15 1536.216 59 193.10 1552.52A-73 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-42) 19 195.10 1536.609 60 193.05 1552.93 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.13 23 194.90 1538.186 64 192.85 1554.54 24 194.85 1538.581 65 192.80 1554.94 25 194.80 1538.976 66 192.75 1555.34 26 194.75 1539.371 67 192.70 1555.75 27 194.70 1539.766 68 192.65 1556.15 28 194.65 1540.162 69 192.60 1556.55 29 194.60 1540.557 70 192.55 1556.96 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.17 33 194.40 1542.142 74 192.35 1558.58 34 194.35 1542.539 75 192.30 1558.98 35 194.30 1542.936 76 192.25 1559.39 36 194.25 1543.333 77 192.20 1559.79 37 194.20 1543.730 78 192.15 1560.20 38 194.15 1544.128 79 192.10 1560.61 39 194.10 1544.526 80 192.05 1561.01 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table A-41 MXP_2.5G_10EX_C Card Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table A-42 TMXP_2.5G_10EX_C Card Receiver Trunk Side Specifications OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion Tolerance PMD tolerance 16 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm +/– 1600 ps/nm — 15 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm — — TBD Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm — 3 12.5 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm — —A-74 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm • Line (client side) – Bit rate: 2.5 Gbps per port (OC-48/STM-16) – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 12 ps/nm (SR SFP version) – Loopback modes: Terminal and facility – Connectors: LC (optical) • Transmitter (client side): Depends on the SFP that is used. • Receiver (client side): Depends on the SFP that is used. • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.9 MXP_MR_10DME_C Card Specifications The MXP_MR_10DME_C card has the following specifications: • Payload configuration – FC1G—Fibre Channel 1.06 Gbps – FC2G—Fibre Channel 2.125 Gbps 17 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm +/- 4000 ps/nm — 15.2 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm +/- 2500 ps/nm — 17.4 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm 3 1. OSNR defined with 0.1 nm RBW 2. Receiver filter bandwidth 32.5GHz (at - 3 dBm) 3. PMD = 30 ps; DGD = 90 ps, hence PMD = 3000 ps^2 Table A-42 TMXP_2.5G_10EX_C Card Receiver Trunk Side Specifications (continued) OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion Tolerance PMD toleranceA-75 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – FC4G—Fibre Channel 4.25 Gbps – FICON1G—Fiber connectivity 1.06 Gbps (IBM signal) – FICON2G—Fiber connectivity 2.125 Gbps (IBM signal) – FICON4G—Fiber connectivity 4.25 Gbps (IBM signal) – ISC compatibility – ISC peer 1G – ISC peer 2G – ONE_GE—One Gigabit Ethernet 1.125 Gbps – Mixed configurations up to maximum line rate of 10.0 Gbps. See the “10.10 MXP_MR_10DME_C and MXP_MR_10DME_L Cards” section on page 10-55 for more information on mixed-mode operation. • Client ports: 8x SFP • Line (trunk side) – Bit rate: 9.952 Gbps for OC-192/STM-64 – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_MR_10DME_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_MR_10DME_C cards. Using direct fiber loopbacks causes irreparable damage to the MXP_MR_10DME_C cards. – Connectors: LC • Transmitter (trunk side) – Minimum output power: +3 dBm – Maximum output power: +6 dBm – Minimum Single-Mode Suppression Ratio (SMSR): 30 dB – Minimum optical extinction ratio: 10 dB – 41 wavelength tunability at 100-GHz spacing – Receiver maximum return reflectance (Rx return loss): –27 dB – Chromatic dispersion allowance: 5400 ps/nm, giving an optical power penalty < 2.0 dB – Minimum side mode suppression ratio: 30 dB – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. – For available wavelengths for the MXP_MR_10DME_C card, see Table 10-29 on page 10-61. • For the receiver trunk side, see Table A-43:A-76 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm • Line (client side) – Bit rate: 1.06 Gbps to 4.25 Gbps per client – Code: Scrambled NRZ – Fiber: Based on SFP (1310-nm single-mode or 850-nm multimode) – Maximum chromatic dispersion allowance: Based on SFP – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: Based on SFP – Nominal wavelength: Based on SFP – Transmitter: Based on SFP • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm or 850nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) Table A-43 MXP_MR_10DME_C Card Receiver Trunk Side Specifications FEC Applications OSNR1 1. OSNR defined with 0.5 nm RBW Pre-FEC BER Post-FEC BER Input Power Sensitivity Chromatic Dispersion Tolerance Power Penalty OSNR Penalty None 23 dB < 10 exp – 12 — –8 to –20 dBm +/– 1200 ps/nm 2 dBm — 19 dB < 10 exp – 12 — –9 to –22 dBm +/– 1000 ps/nm 2 dBm — FEC 10 dB < 10 exp – 5 < 10 exp – 15 –8 to –18 dBm +/– 800 ps/nm — 1.5 dB Enhanced FEC 19 dB < 10 exp – 4 < 10 exp – 15 –8 to –26 dBm +/– 800 ps/nm 2 dBm 2 dB 8 dB < 10 exp – 4 < 10 exp – 15 –8 to –18 dBm +/– 800 ps/nm 2 dBm 1.5 dBA-77 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Weight not including clam shell: 2.25 lb (1.02 kg) A.10.10 MXP_MR_10DME_L Card Specifications The MXP_MR_10DME_L card has the following specifications: • Payload configuration – FC1G—Fibre Channel 1.06 Gbps – FC2G—Fibre Channel 2.125 Gbps – FC4G—Fibre Channel 4.25 Gbps – FICON1G—Fiber connectivity 1.06 Gbps (IBM signal) – FICON2G—Fiber connectivity 2.125 Gbps (IBM signal) – FICON4G—Fiber connectivity 4.25 Gbps (IBM signal) – ISC compatibility – ISC peer 1G – ISC peer 2G – ONE_GE—One Gigabit Ethernet 1.125 Gbps – Mixed configurations up to maximum line rate of 10.0 Gbps. See the “10.10 MXP_MR_10DME_C and MXP_MR_10DME_L Cards” section on page 10-55 for more information on mixed-mode operation. • Client ports: 8x SFP • Line (trunk side) – Bit rate: 9.952 Gbps for OC-192/STM-64 – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_MR_10DME_L card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_MR_10DME_L cards. Using direct fiber loopbacks causes irreparable damage to the MXP_MR_10DME_L cards. – Connectors: LC • Transmitter (trunk side) – Minimum output power: +3 dBm – Maximum output power: +6 dBm – Minimum SMSR: 30 dB – Minimum optical extinction ratio: 10.5 dB – 40 wavelength tunability at 100-GHz spacing, 80 wavelength tunability at 50-GHz spacing – Receiver maximum return reflectance (Rx return loss): –27 dB – Chromatic dispersion allowance: 5400 ps/nm, giving an optical power penalty < 2.0 dBA-78 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Minimum side mode suppression ratio: 30 dB – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. – For the currently available wavelengths for the MXP_MR_10DME_L card, see Table 10-30 on page 10-62. • Table A-44 provides the receiver trunk side specifications: – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1570 to 1604 nm • Line (client side) – Bit rate: 1.06 Gbps to 4.25 Gbps per client – Code: Scrambled NRZ – Fiber: Based on SFP (1310-nm single-mode or 850-nm multimode) – Maximum chromatic dispersion allowance: Based on SFP – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: Based on SFP – Nominal wavelength: Based on SFP – Transmitter: Based on SFP • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 Table A-44 MXP_MR_10DME_L Card Receiver Trunk Side Specifications FEC Applications OSNR1 1. OSNR defined with 0.5 nm RBW Pre-FEC BER Post-FEC BER Input Power Sensitivity Chromatic Dispersion Tolerance Power Penalty OSNR Penalty None 23 dB < 10 exp – 12 — –8 to –19 dBm +/– 1200 ps/nm 2 dBm — 19 dB < 10 exp – 12 — –9 to –19 dBm +/– 1000 ps/nm 2 dBm — FEC 10 dB < 10 exp – 5 < 10 exp – 15 –8 to –18 dBm +/– 800 ps/nm — 1.5 dB Enhanced FEC 19 dB < 10 exp – 4 < 10 exp – 15 –8 to –26 dBm +/– 800 ps/nm — 2 dB 8 dB < 10 exp – 4 < 10 exp – 15 –8 to –18 dBm +/– 800 ps/nm — 1.5 dBA-79 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm or 850nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 2.25 lb (1.02 kg) A.10.11 MXP_MR_10DMEX_C Card Specifications The MXP_MR_10DMEX_C card has the following specifications: • Payload configuration – FC1G—Fibre Channel 1.06 Gbps – FC2G—Fibre Channel 2.125 Gbps – FC4G—Fibre Channel 4.25 Gbps – FICON1G—Fiber connectivity 1.06 Gbps (IBM signal) – FICON2G—Fiber connectivity 2.125 Gbps (IBM signal) – FICON4G—Fiber connectivity 4.25 Gbps (IBM signal) – ISC compatibility – ISC peer 1G – ISC peer 2G – ONE_GE—One Gigabit Ethernet 1.125 Gbps – Mixed configurations up to maximum line rate of 10.0 Gbps. • Client ports: 8x SFP • Line (trunk side) – Bit rate: 9.952 Gbps for OC-192/STM-64 – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_MR_10DMEX_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_MR_10DMEX_C cards. Using direct fiber loopbacks causes irreparable damage to the MXP_MR_10DMEX_C cards. – Connectors: LC • Transmitter (trunk side) A-80 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Minimum output power: +3 dBm – Maximum output power: +7 dBm – Minimum Single-Mode Suppression Ratio (SMSR): 30 dB – Minimum optical extinction ratio: 10 dB – 41 wavelength tunability at 100-GHz spacing – Receiver maximum return reflectance (Rx return loss): –27 dB – Chromatic dispersion allowance: 5400 ps/nm, giving an optical power penalty < 2.0 dB – Minimum side mode suppression ratio: 30 dB – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. – For available wavelengths for the MXP_MR_10DMEX_C card, see Table 10-29 on page 10-61. • For the receiver trunk side, see Table A-45: – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm • Line (client side) – Bit rate: 1.06 Gbps to 4.25 Gbps per client Table A-45 MXP_MR_10DMEX_C Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 2. Receiver filter bandwidth 32.5GHz (at - 3 dBm) Chromatic Dispersion Tolerance PMD tolerance 16 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm +/– 1600 ps/nm — 15 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm — — TBD Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm — 3 3. PMD = 30 ps; DGD = 90 ps, hence PMD = 3000 ps^2 12.5 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm — — 17 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm +/- 4000 ps/nm — 15.2 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm +/- 2500 ps/nm — 17.4 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm 3A-81 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Code: Scrambled NRZ – Fiber: Based on SFP (1310-nm single-mode or 850-nm multimode) – Maximum chromatic dispersion allowance: Based on SFP – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: Based on SFP – Nominal wavelength: Based on SFP – Transmitter: Based on SFP • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm or 850nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 2.25 lb (1.02 kg) A.10.12 TXP_MR_10E Card Specifications The TXP_MR_10E card has the following specifications: • Line (trunk side) – Bit rate: OC-192/STM-64 (9.95328 Gbps), OTU2 (10.70923 Gbps), 10GE (10.3125 Gbps), 10GE into OTU2 (non-standard 11.0957 Gbps), 10G FC (10.51875 Gbps), or 10G FC into OTU2 (non-standard 11.31764 Gbps) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1200 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10E card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10E card.A-82 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm for C-band and +2 dBm for L-band – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of TXP_MR_10E: C-band frequency plan (eight card versions, each with four tunable channels on the ITU 100-GHz grid): – 1530.33 to 1533.07 nm (four channels) – 1534.25 to 1537.00 nm (four channels) – 1538.19 to 1540.95 nm (four channels) – 1542.14 to 1544.92 nm (four channels) – 1546.12 to 1548.92 nm (four channels) – 1550.12 to 1552.93 nm (four channels) – 1554.13 to 1556.96 nm (four channels) – 1558.17 to 1561.01 nm (four channels) L-band frequency plan (five card versions, each with eight tunable channels on the ITU 50-GHz grid): – 1577.44 to 1580.35 nm (eight channels) – 1580.77 to 1583.69 nm (eight channels) – 1584.11 to 1587.04 nm (eight channels) – 1587.46 to 1590.41 nm (eight channels) – 1590.83 to 1593.79 nm (eight channels) • Receiver (trunk side, see Table A-46) Table A-46 TXP_MR_10E Card Receiver Trunk Side Specifications OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion Tolerance 30 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm +/– 1200 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm + – 1000 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 22 dBm — 17 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 15 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm —A-83 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion • Line (client side): – 10-Gigabit Small Form-factor Pluggable (XFP)-based SR – Bit rate: 10GE (10.3125 Gbps), 10G FC (10.51875 Gbps), or STM-64/OC-192 – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 6.6 ps/nm – Loopback modes: Terminal and facility – Connectors: LC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.957, ITU-T G.691 • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: 1290 to 1330 nm – Nominal wavelength: 1310 nm – Transmitter: DFB laser • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) 15 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 14 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm — 1. OSNR defined with 0.1 nm RBW 2. Receiver filter bandwidth greater than or equal to 180 pm (at – 3 dBm) Table A-46 TXP_MR_10E Card Receiver Trunk Side Specifications (continued) OSNR1 FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 Chromatic Dispersion ToleranceA-84 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications A.10.13 TXP_MR_10E_C Card Specifications The TXP_MR_10E_C card has the following specifications: • Line (trunk side) – Bit rate: OC-192/STM-64 (9.95328 Gbps), OTU2 (10.70923 Gbps), 10GE (10.3125 Gbps), 10GE into OTU2 (non-standard 11.0957 Gbps), 10G FC (10.51875 Gbps), or 10G FC into OTU2 (non-standard 11.31764 Gbps) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1200 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10E_C card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10E_C card. – Connectors: LC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.957, and ITU-T G.709 • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of TXP_MR_10E_C card: There is a single version of the TXP_MR_10E_C card. It is tunable across 82 wavelengths in the C-band frequency plan, with channels on the ITU 50-GHz grid, as shown in Table A-47. Table A-47 TXP_MR_10E_C Card Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.119 3 195.90 1530.334 44 193.85 1546.518 4 195.85 1530.725 45 193.80 1546.917 5 195.80 1531.116 46 193.75 1547.316 6 195.75 1531.507 47 193.70 1547.715A-85 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications 7 195.70 1531.898 48 193.65 1548.115 8 195.65 1532.290 49 193.60 1548.515 9 195.60 1532.681 50 193.55 1548.915 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.71 12 195.45 1533.86 53 193.40 1550.116 13 195.40 1534.250 54 193.35 1550.517 14 195.35 1534.643 55 193.30 1550.918 15 195.30 1535.036 56 193.25 1551.319 16 195.25 1535.429 57 193.20 1551.721 17 195.20 1535.822 58 193.15 1552.122 18 195.15 1536.216 59 193.10 1552.524 19 195.10 1536.609 60 193.05 1552.926 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.134 23 194.90 1538.186 64 192.85 1554.537 24 194.85 1538.581 65 192.80 1554.940 25 194.80 1538.976 66 192.75 1555.343 26 194.75 1539.371 67 192.70 1555.747 27 194.70 1539.766 68 192.65 1556.151 28 194.65 1540.162 69 192.60 1556.555 29 194.60 1540.557 70 192.55 1556.959 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.173 33 194.40 1542.142 74 192.35 1558.578 34 194.35 1542.539 75 192.30 1558.983 35 194.30 1542.936 76 192.25 1559.389 36 194.25 1543.333 77 192.20 1559.794 37 194.20 1543.730 78 192.15 1560.200 38 194.15 1544.128 79 192.10 1560.606 39 194.10 1544.526 80 192.05 1561.013 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table A-47 TXP_MR_10E_C Card Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)A-86 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-48) – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm • Line (client side): – XFP-based SR – Bit rate: 10GE (10.3125 Gbps), 10G FC (10.51875 Gbps), or STM-64/OC-192 – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 6.6 ps/nm – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: 1290 to 1330 nm – Nominal wavelength: 1310 nm – Transmitter: DFB laser • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm Table A-48 TXP_MR_10E _C Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 2. Receiver filter bandwidth 32.5GHz (at - 3 dB) Chromatic Dispersion Tolerance 30 dB Off < 10 exp – 12 N/A – 8 to – 18 dBm +/– 1200 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 18 dBm + – 1000 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 18 dBm — 17 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 15.5 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm — 14 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 12 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm —A-87 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.14 TXP_MR_10E_L Card Specifications The TXP_MR_10E_L card has the following specifications: • Line (trunk side) – Bit rate: OC-192/STM-64 (9.95328 Gbps), OTU2 (10.70923 Gbps), 10GE (10.3125 Gbps), 10GE into OTU2 (non-standard 11.0957 Gbps), 10G FC (10.51875 Gbps), or 10G FC into OTU2 (non-standard 11.31764 Gbps) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1200 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E_L card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10E_L card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10E_L card. – Connectors: LC • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +2 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of TXP_MR_10E_L card: There is a single version of the TXP_MR_10E_L card. It is tunable across 80 wavelengths in the L band frequency plan, with channels on the ITU 50-GHz grid, as shown in Table A-49.A-88 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications Table A-49 TXP_MR_10E_L Card Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 190.85 1570.83 41 188.85 1587.46 2 190.8 1571.24 42 188.8 1587.88 3 190.75 1571.65 43 188.75 1588.30 4 190.7 1572.06 44 188.7 1588.73 5 190.65 1572.48 45 188.65 1589.15 6 190.6 1572.89 46 188.6 1589.57 7 190.55 1573.30 47 188.55 1589.99 8 190.5 1573.71 48 188.5 1590.41 9 190.45 1574.13 49 188.45 1590.83 10 190.4 1574.54 50 188.4 1591.26 11 190.35 1574.95 51 188.35 1591.68 12 190.3 1575.37 52 188.3 1592.10 13 190.25 1575.78 53 188.25 1592.52 14 190.2 1576.20 54 188.2 1592.95 15 190.15 1576.61 55 188.15 1593.37 16 190.1 1577.03 56 188.1 1593.79 17 190.05 1577.44 57 188.05 1594.22 18 190 1577.86 58 188 1594.64 19 189.95 1578.27 59 187.95 1595.06 20 189.9 1578.69 60 187.9 1595.49 21 189.85 1579.10 61 187.85 1595.91 22 189.8 1579.52 62 187.8 1596.34 23 189.75 1579.93 63 187.75 1596.76 24 189.7 1580.35 64 187.7 1597.19 25 189.65 1580.77 65 187.65 1597.62 26 189.6 1581.18 66 187.6 1598.04 27 189.55 1581.60 67 187.55 1598.47 28 189.5 1582.02 68 187.5 1598.89 29 189.45 1582.44 69 187.45 1599.32 30 189.4 1582.85 70 187.4 1599.75 31 189.35 1583.27 71 187.35 1600.17 32 189.3 1583.69 72 187.3 1600.60 33 189.25 1584.11 73 187.25 1601.03 34 189.2 1584.53 74 187.2 1601.46 35 189.15 1584.95 75 187.15 1601.88A-89 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-50) – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1570 to 1604 nm • Line (client side): – XFP-based SR – Bit rate: 10GE (10.3125 Gbps), 10G FC (10.51875 Gbps), or STM-64/OC-192 – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 6.6 ps/nm – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm 36 189.1 1585.36 76 187.1 1602.31 37 189.05 1585.78 77 187.05 1602.74 38 189 1586.20 78 187 1603.17 39 188.95 1586.62 79 186.95 1603.60 40 188.9 1587.04 80 186.9 1604.03 Table A-49 TXP_MR_10E_L Card Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table A-50 TXP_MR_10E Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 2. Receiver filter bandwidth greater than or equal to 180 pm (at – 3 dBm) Chromatic Dispersion Tolerance 30 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm +/– 1200 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 20 dBm + – 1000 ps/nm 26 dB Off < 10 exp – 12 N/A – 8 to – 22 dBm — 17 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 15.5 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 18 dBm — 15 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm +/– 800 ps/nm 13 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 18 dBm —A-90 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Center wavelength: 1290 to 1330 nm – Nominal wavelength: 1310 nm – Transmitter: DFB laser • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.15 TXP_MR_10EX_C Card Specifications The TXP_MR_10EX_C card has the following specifications: • Line (trunk side) – Bit rate: OC-192/STM-64 (9.95328 Gbps), OTU2 (10.70923 Gbps), 10GE (10.3125 Gbps), 10GE into OTU2 (non-standard 11.0957 Gbps), 10G FC (10.51875 Gbps), or 10G FC into OTU2 (non-standard 11.31764 Gbps) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: +/– 1600 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10EX_C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10EX_C card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10EX_C card. – Connectors: LC – Compliance: Telcordia GR-253-CORE, ITU-T G.707, ITU-T G.957, and ITU-T G.709 • Transmitter (trunk side) – Maximum transmitter output power: +6 dBm – Minimum transmitter output power: +3 dBm – Transmitter: LN external modulator transmitter – Wavelength stability (drift): +/– 25 picometers (pm)A-91 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of TXP_MR_10EX_C card: There is a single version of the TXP_MR_10EX_C card. It is tunable across 82 wavelengths in the C-band frequency plan, with channels on the ITU 50-GHz grid, as shown in Table A-51. Table A-51 TXP_MR_10EX_C Card Trunk Wavelengths Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) 1 196.00 1529.55 42 193.95 1545.72 2 195.95 1529.94 43 193.90 1546.12 3 195.90 1530.334 44 193.85 1546.52 4 195.85 1530.725 45 193.80 1546.92 5 195.80 1531.116 46 193.75 1547.32 6 195.75 1531.507 47 193.70 1547.72 7 195.70 1531.898 48 193.65 1548.11 8 195.65 1532.290 49 193.60 1548.51 9 195.60 1532.681 50 193.55 1548.91 10 195.55 1533.073 51 193.50 1549.32 11 195.50 1533.47 52 193.45 1549.72 12 195.45 1533.86 53 193.40 1550.12 13 195.40 1534.250 54 193.35 1550.52 14 195.35 1534.643 55 193.30 1550.92 15 195.30 1535.036 56 193.25 1551.32 16 195.25 1535.429 57 193.20 1551.72 17 195.20 1535.822 58 193.15 1552.12 18 195.15 1536.216 59 193.10 1552.52 19 195.10 1536.609 60 193.05 1552.93 20 195.05 1537.003 61 193.00 1553.33 21 195.00 1537.40 62 192.95 1553.73 22 194.95 1537.79 63 192.90 1554.13 23 194.90 1538.186 64 192.85 1554.54 24 194.85 1538.581 65 192.80 1554.94 25 194.80 1538.976 66 192.75 1555.34 26 194.75 1539.371 67 192.70 1555.75 27 194.70 1539.766 68 192.65 1556.15 28 194.65 1540.162 69 192.60 1556.55 29 194.60 1540.557 70 192.55 1556.96A-92 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Receiver (trunk side, see Table A-48) – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm 30 194.55 1540.953 71 192.50 1557.36 31 194.50 1541.35 72 192.45 1557.77 32 194.45 1541.75 73 192.40 1558.17 33 194.40 1542.142 74 192.35 1558.58 34 194.35 1542.539 75 192.30 1558.98 35 194.30 1542.936 76 192.25 1559.39 36 194.25 1543.333 77 192.20 1559.79 37 194.20 1543.730 78 192.15 1560.20 38 194.15 1544.128 79 192.10 1560.61 39 194.10 1544.526 80 192.05 1561.01 40 194.05 1544.924 81 192.00 1561.42 41 194.00 1545.32 82 191.95 1561.83 Table A-51 TXP_MR_10EX_C Card Trunk Wavelengths (continued) Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm) Table A-52 TXP_MR_10E _C Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 2. Receiver filter bandwidth 32.5GHz (at - 3 dBm) Chromatic Dispersion Tolerance PMD tolerance 16 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm +/– 1600 ps/nm — 15 dB Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm — — TBD Standard < 10 exp – 5 < 10 exp – 15 – 8 to – 20 dBm — 3 3. PMD = 30 ps; DGD = 90 ps, hence PMD = 3000 ps^2 12.5 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm — — 17 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm +/- 4000 ps/nm — 15.2 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm +/- 2500 ps/nm — 17.4 dB Enhanced < 7 x 10 exp – 4 < 10 exp – 15 – 8 to – 20 dBm 3A-93 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Line (client side): – XFP-based SR – Bit rate: 10GE (10.3125 Gbps), 10G FC (10.51875 Gbps), or STM-64/OC-192 – Code: Scrambled NRZ – Fiber: 1310-nm single-mode – Maximum chromatic dispersion allowance: 6.6 ps/nm – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: –1 dBm – Minimum transmitter output power: –6 dBm – Center wavelength: 1290 to 1330 nm – Nominal wavelength: 1310 nm – Transmitter: DFB laser • Receiver (client side) – Maximum receiver level: –1 dBm at BER 1 * 10 exp – 12 – Minimum receiver level: –14 dBm at BER 1 * 10 exp – 12 – Receiver: APD – Link loss budget: 8 dB minimum, at BER = 1 * 10 exp – 12 – Receiver input wavelength range: 1290 to 1605 nm • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 3.1 lb (1.3 kg) A.10.16 40G-MXP-C Card Specifications The 40G-MXP-C card has the following specifications: • Payload configuration – FC8G—Fibre Channel 8.50 Gbps – FC10G—Fiber Channel 10.519 Gbps – FICON10G—Fiber connectivity 10.519 Gbps – OC192/STM64/10GE WAN-Phy—9.953 Gbps – 10-GE LAN-Phy—10.312 Gbps – OTU2 (OC192/STM64/10GE WAN-Phy)—10.709 Gbps – OTU2e (10GE LAN-Phy)—11.096 GbpsA-94 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Client ports: 4 X SFP • Line (trunk side) – Bit rate: 43.018 Gbps for OTU3, 44.57 Gbps for OTU3e – Code: RZ-DQPSK 40G – Fiber: 1550-nm single-mode – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the 40G-MXP-C card in a loopback on the trunk port. Do not use direct fiber loopbacks with the 40G-MXP-C cards. Using direct fiber loopbacks causes irreparable damage to the 40G-MXP-C cards. – Connectors: LC • Transmitter (trunk side) – Minimum output power: –2 dBm – Maximum output power: +2 dBm – Minimum Single-Mode Suppression Ratio (SMSR): 35 dB – Minimum optical extinction ratio: 25 dB – Wavelength tunability (total 82 wavelengths) at 50-GHz spacing – Receiver maximum return reflectance (Rx return loss): –27 dB – Chromatic dispersion allowance: 750 ps/nm, giving an optical OSNR penalty < 2.0 dB – Minimum side mode suppression ratio: 30 dB – Wavelength stability (drift): +/– 25 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. – For wavelengths available for the 40G-MXP-C card, see Table 10-29 on page 10-61. • Receiver (trunk side) – Receiver: PIN – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion – Receiver input wavelength range: 1529 to 1562 nm Table A-53 lists the trunk side specifications of the receiver. Table A-53 40G-MXP-C Card Receiver (Trunk) Side Specifications FEC Applications OSNR1 Pre-FEC BER Post-FEC BER Input Power Sensitivity Chromatic Dispersion Tolerance Power Penalty OSNR Penalty FEC 12 dB < 10 exp – 5 < 10 exp – 15 –8 to –20 dBm +/– 750 ps/nm — 2 dB Enhanced FEC 19 dB < 10 exp – 3 < 10 exp – 15 –8 to –24 dBm +/– 750 ps/nm 2 dBm — 8 dB < 10 exp – 3 < 10 exp – 15 –8 to –20 dBm +/– 750 ps/nm — 2 dBA-95 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Line (client side) – Bit rate: 8.50 Gbps to 11.096 Gbps per client – Code: NRZ 40G – Fiber: Based on SFP (1310-nm single-mode or 850-nm multimode) – Maximum chromatic dispersion allowance: Based on XFP – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (client side) – Maximum transmitter output power: Based on XFP – Minimum transmitter output power: Based on XFP – Center wavelength: Based on XFP – Nominal wavelength: Based on XFP – Transmitter: Based on XFP • Receiver (client side) – Maximum receiver level: Based on XFP – Minimum receiver level: Based on XFP – Receiver: Based on XFP – Link loss budget: Based on XFP – Receiver input wavelength range: Based on XFP • Environmental Exception – Short term ambient temperature: Functionality is guaranteed, according to GR-63 Issue 3 for the thermal cycles except for the temperature values which are -5 to 45 degrees Celsius (23 to 113 degrees Fahrenheit) instead of -5 to 55 degrees Celsius (23 to 131 degrees Fahrenheit). • Dimensions – Height: 12.650 in. (321.3 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.000 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight excluding clam shell: 7.7 lb (3.5 kg) A.10.17 ADM-10G Card Specifications The ADM-10G card has the following specifications: • Line – Bit rate: OC-3/STM-1 (155.520 Mb/s); OC-12/STM-3 (622.08 Mb/s); OC-48/STM-16 (2488.32 Mb/s); OC-192/STM-64 (9.95328 Gbps) – Code: Scrambled NRZ 1. OSNR defined with 0.5 nm RBWA-96 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Fiber: 1310-nm single-mode for ONS-XC-10GS1 XFP or 1530.33 to 1554.94-nm single-mode for ONS-XC-10G-xx.x XFP – Maximum chromatic dispersion allowance: up to 3600 ps/nm – Loopback modes: Terminal, facility, and cross-connect – Connectors: LC • Transmitter (trunk side) – Transmitter: LN external modulator transmitter – Maximum transmitter output power: Depends on XFP that is used – Minimum transmitter output power: Depends on XFP that is used – Wavelength stability (drift): +/– 25 picometers (pm) • Receiver (trunk side) – Receiver: APD – Receiver input wavelength range: Depends on XFP that is used – Receiver sensitivity: depends on XFP that is used – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion • Dimensions – Height: 12.65 in. (321.3 mm) – Width: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.00 in. (228.6 mm) – Depth with backplane connector: 9.250 in. (235 mm) – Weight not including clam shell: 5.07 lb (2.3 kg) A.10.18 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Specifications The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have the following specifications: • Line (trunk side) – Bit rate: 11.1 Gbps (in ITU-T G.709 Digital Wrapper/FEC mode) or 10.3125 Gbps (in ITU-T G.709 Digital Wrapper/FEC mode disabled) – Code: Scrambled NRZ – Fiber: 1550-nm single-mode – Maximum chromatic dispersion allowance: – 500 to 1600 ps/nm (specified penalty) – Loopback modes: Terminal and facility Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the GE_XP and GE_XPE card in a loopback on the trunk port. Do not use direct fiber loopbacks with the GE_XP and GE_XPE card. Using direct fiber loopbacks causes irreparable damage to the GE_XP and GE_XPE card. – Connectors: LC • Transmitter (trunk side) A-97 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications – Maximum transmitter output power: +3 dBm – Minimum transmitter output power: -1 dBm – Transmitter: EML laser – Wavelength stability (drift): +/– 100 picometers (pm) Note An optical device on the card keeps the laser wavelength locked as closely as possible to the ITU nominal value. The allowed drift is +/– 25 pm. • Currently available wavelengths and versions of GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE: C Band, 100 GHz spacing. • Receiver (trunk side, see Table A-54) – Receiver: APD – Link loss budget: 24 dB minimum, with no dispersion or 22 dB optical path loss at BER = 1 * 10 exp – 12 including dispersion • Line (client side) – Bit rate: 1.125Gbps (GE) or 10.3125Gbps (10GE) – Code: Scrambled NRZ – Fiber: 1310-nm single-mode or 850-nm multimode – Maximum chromatic dispersion allowance: 12 ps/nm (SR SFP version) – Loopback modes: Terminal and facility – Connectors: LC (optical) • Transmitter (client side): Depends on the SFP that is used. • Receiver (client side): Depends on the SFP that is used. Table A-54 GE_XP and GE_XPE Card Receiver Trunk Side Specifications OSNR1 1. OSNR defined with 0.1 nm RBW FEC Type Pre-FEC BER Post-FEC BER Input Power Sensitivity2 2. Receiver filter bandwidth greater than or equal to 180 pm (at – 3 dBm) Chromatic Dispersion Tolerance 30 dB Off 1.00E – 12 N/A – 7 to – 23 dBm — 30 dB Off 1.00E – 12 N/A – 7 to – 20 dBm – 500 to 1600 ps/nm 24 dB Off 1.00E – 12 N/A – 7 to – 18 dBm — 27 dB Off 1.00E – 12 N/A – 7 to – 18 dBm – 500 to 1600 ps/nm 18 dB Standard 1.00E – 05 1.00E – 15 – 7 to – 18 dBm — 19 dB Standard 1.00E – 05 1.00E – 15 – 7 to – 18 dBm – 500 to 1600 ps/nm 30 dB Enhanced 1.00E – 04 1.00E – 15 – 7 to – 27 dBm — 30 dB Enhanced 1.00E – 04 1.00E – 15 – 7 to – 24 dBm – 500 to 1600 ps/nm 15 dB Enhanced 1.00E – 04 1.00E – 15 – 7 to – 18 dBm — 15 dB Enhanced 1.00E – 04 1.00E – 15 – 7 to – 18 dBm – 500 to 1600 ps/nmA-98 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Transponder and Muxponder Card Specifications • Environmental – Power consumption: 95.00 W (maximum), 2 A at -48 V for GE_XP and GE_XPE cards – Power consumption: 80.00 W (maximum), 1.67 A at -48 V for 10GE_XP and 10GE_XPE cards • Dimensions – Height: 12.992 in. (330 mm) – Width: 10GE_XP and 10GE_XPE: 0.921 in. (23.4 mm) GE_XP and GE_XPE: 1.866 in. (47.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.448 in. (240 mm) – Weight not including clam shell: 10GE-XP and 10GE_XPE, 1.04 kg; GE-XP and GE_XPE, 1.36 kg. A.10.19 OTU2_XP Card Specifications The OTU2_XP card has the following specifications: • Line – Bit rate: OC-192/STM-64 (9.95328 Gbps), 10GE (10.3125 Gbps), or 10G FC (10.51875 Gbps) – Code: Scrambled NRZ – Fiber: 1310-nm single-mode for ONS-XC-10GS1 XFP or 1530.33-nm to 1561.42-nm single-mode for ONS-XC-10G-xx.x XFP – Maximum chromatic dispersion allowance: Depends on the XFP that is used – Loopback modes: Terminal and facility – Connectors: LC • Transmitter (trunk side) – Transmitter: EML – Maximum transmitter output power: Depends on the XFP that is used – Minimum transmitter output power: Depends on the XFP that is used – Wavelength stability (drift): Depends on the XFP that is used • Receiver (trunk side) – Receiver: APD – Receiver input wavelength range: Depends on XFP that is used – Receiver sensitivity: Depends on XFP that is used – Link loss budget: Depends on XFP that is used • Dimensions – Height: 13.043 in. (331.3 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 9.413 in. (239.1 mm) – Depth with backplane connector: 9.909 in. (251.7 mm) – Weight not including clam shell: 2.38 lb (1.08 kg)A-99 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications TDC-CC and TDC-FC Card Specifications A.11 TDC-CC and TDC-FC Card Specifications The TDC-CC and TDC-FC card specifications are as follows: • Wavelength – Total operating signal wavelength range (C-band range): 1529.0 - 1562.5 nm • Optical – Insertion loss — DC-RX to DC-TX: Maximum 12.5 for TDC-CC and 9.5 for TDC-FC @ 1545.32 nm at room temperature • Wavelength dependant loss: 0.8 dB max – Maximum optical input power: 200mW – Polarization dependent loss: 0.2 dB max • Dimensions – Height: 12.65 in. (332 mm) – Width: 0.921 in. (23.4 mm) (The dimension of the finger gasket is not included) – Depth: 8.66 in. (220.1 mm) – Depth with backplane connector: 235 mm (9.250 in) – Weight not including clam shell: • TDC-CC—1.26 Kg • TDC-FC—1.14 Kg • The TDC-CC and TDC-FC tunable CD values are listed in Table A-55. Table A-55 TDC-CC and TDC-FC Tunable CD Value Unit Configuration TDC-CC [ps/nm] TDC-FC [ps/nm] 0 0 1 0 2 1 -110 -45 2 -220 -90 3 -330 -135 4 -440 -180 5 -550 -225 6 -660 -270 7 -770 -315 8 -880 -360 9 -990 -405 10 -1100 -450 11 -1210 -495 12 -1320 -540 13 -1430 -585 14 -1540 -630 15 -1650 -675A-100 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Mesh Patch Panel Specifications A.12 Mesh Patch Panel Specifications This section provides specifications for the PP-MESH-4, PP-MESH-8, and 15454-PP-4-SMR patch panels. A.12.1 PP-MESH-4 Patch Panel Specifications The PP-MESH-4 patch panel optical specifications are listed in Table A-56. The PP-MESH-4 patch panel has the following additional specifications: • Environmental – Operating temperature: +23 to +149 degrees Fahrenheit (–5 to +65 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing • Dimensions – Height: 17.42 in. (442.5 mm) – Width: 3.457 in. (87.8 mm) – Depth: 11.025 in. (280 mm) 1. The default value of the TDC-CC CD value for Coarse Unit is 0. 2. The default value of the TDC-FC value for Fine Unit is 0. Table A-56 PP-MESH-4 Patch Panel Optical Specifications Parameter Note Condition Min Max Unit Wavelength range — — 1530 1570 nm Insertion loss 1 2 1. Under all SOPs and all operating environmental conditions 2. Values are referenced with connector loss (LC=0.3 dB, MPO=0.5dB) — In all the wavelength ranges (local ADD or test access RX to EXP TX, COM RX to EXP TX, COM RX to test access TX) — 7.5 dB Insertion Loss Uniformity1 2 — In all the wavelength ranges — 0.9 dB Polarization dispersion loss (PDL) 1 — — — 0.3 dB Polarization mode dispersion (PMD) 1 — — — 0.1 dB Optical Return Loss 1 — — 50 — dB Directivity 1 — — 50 — dBA-101 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications Mesh Patch Panel Specifications A.12.2 PP-MESH-8 Patch Panel Specifications The PP-MESH-8 patch panel optical specifications are listed in Table A-57. The PP-MESH-8 patch panel has the following additonal specifications: • Environmental – Operating temperature: +23 to +149 degrees Fahrenheit (–5 to +65 degrees Celsius) – Operating humidity: 5 to 95 percent, noncondensing • Dimensions – Height: 17.42 in. (442.5 mm) – Width: 3.457 in. (87.8 mm) – Depth: 11.025 in. (280 mm) A.12.3 15454-PP-4-SMR Patch Panel Specifications The 15454-PP-4-SMR patch panel optical specifications are listed in Table A-58. Table A-57 PP-MESH-8 Patch Panel Optical Specifications Parameter Note Condition Min Max Unit Wavelength range — — 1530 1570 nm Insertion loss 1 2 1. Under all SOPs and all operating environmental conditions 2. Values are referenced with connector loss (LC=0.3 dB, MPO=0.5dB) — In all the wavelength ranges (local ADD or test access RX to EXP TX, COM RX to EXP TX, COM RX to test access TX) — 10.6 dB Insertion loss uniformity 1 2 — In all the wavelength ranges — 1.3 dB PDL 1 — — — 0.5 dB PMD 1 — — — 0.1 dB Optical Return Loss 1 — — 50 — dB Directivity 1 — — 50 — dB Table A-58 15454-PP-4-SMR Patch Panel Optical Specifications Parameter Note Condition Min Max Unit Wavelength range All SOP within operating temperature range — 1520 1570 nmA-102 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix A Hardware Specifications SFP and XFP Specifications The 15454-PP-4-SMR patch panel has the following additional specifications: • Environmental – Operating temperature: +23 to +149 degrees Fahrenheit (–5 to +65 degrees Celsius) A.13 SFP and XFP Specifications Note The CC-FTA fan tray is mandatory if CWDM SFPs and DWDM SFPs are used on MSTP units. Note Use hardware version 2.0 DWDM SFP for MSTP units. See the Installing the GBIC, SFP, and XFP Optics Modules in Cisco ONS Platforms for SFP and XFP specifications. A.14 Patch Panel Specifications For information on 15216 40-Channel Mux/Demux Patch Panel specifications, refer to the “Patch Panel Specifications” section in the “Installing Cisco ONS 15216 40-Channel Mux/Demux Patch Panel” guide. For information on 15454-PP-4-SMR Patch Panel specifications, refer to the “Patch Panel Specifications” section in the “Installing Cisco ONS 15454-PP-4-SMR Patch Panel” guide. Insertion loss All SOP within operating temperature range, wavelength range, from each input port of any MPO connector to any output port including two MPO connections — 5.5 7.5 dB Insertion loss uniformity 1 — — 0.5 dB Insertion loss ripple — — 0.2 dB Chromatic dispersion — — +/- 5 ps/nm PDL — — 0.1 dB PMD — — 0.1 dB Optical return loss — 50 — dB Directivity — 50.0 — dB 1. Defined as the difference between theinsertion loss values of any of the four branches of each 1x4 coupler. Table A-58 15454-PP-4-SMR Patch Panel Optical Specifications (continued) Parameter Note Condition Min Max UnitB-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 APPENDIX B Administrative and Service States This appendix describes the administrative and service states for Cisco ONS 15454 dense wavelength division multiplexing (DWDM) cards, optical payload ports, out-of-band optical service channel (OSC) ports, optical channel network connections (OCHNCs), and transponder/muxponder cards and ports. States for 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. B.1 Service States Service states include a Primary State (PST), a Primary State Qualifier (PSTQ), and one or more Secondary States (SST). Table B-1 lists the ANSI and ETSI service state PSTs and PSTQs supported by the ONS 15454. Table B-2 defines the ANSI and ETSI SSTs supported by the ONS 15454. Table B-1 ONS 15454 Service State Primary States and Primary State Qualifiers ANSI Primary State, Primary State Qualifier ETSI Primary State, Primary State Qualifier Definition IS-NR (In-Service and Normal) Unlocked-enabled The entity is fully operational and will perform as provisioned. OOS-AU (Out-of-Service and Autonomous) Unlocked-disabled The entity is not operational because of an autonomous event. OOS-AUMA (Out-of-Service and Autonomous Management) Locked-disabled The entity is not operational because of an autonomous event and has also been manually removed from service. OOS-MA (Out-of-Service and Management) Locked-enabled The entity has been manually removed from service.B-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Administrative States B.2 Administrative States Administrative states are used to manage service states. Administrative states consist of a PST and an SST. Table B-3 lists the ANSI and ETSI administrative states supported by the ONS 15454. See Table B-2 for SST definitions. Note A change in the administrative state of an entity does not change the service state of supporting or supported entities. Table B-2 ONS 15454 Secondary States ANSI Secondary State ETSI Secondary State Definition AINS automaticInService The entity is delayed before transitioning to the IS-NR (ANSI)/Unlocked-enabled (ETSI) service state. The transition to IS-NR/Unlocked-enabled depends on correction of conditions. Alarm reporting is suppressed, but traffic is carried. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the Cisco Transport Controller (CTC) Conditions tab or by using the TL1 RTRV-COND command. DSBLD disabled The entity was manually removed from service and does not provide its provisioned functions. All services are disrupted; unable to carry traffic. FLT failed The entity has a raised alarm or condition. MEA mismatchOfEquipment An improper card is installed. For example, an installed card is not compatible with the card preprovisioning or the slot. This SST applies only to cards. MT maintenance The entity has been manually removed from service for a maintenance activity but still performs its provisioned functions. Alarm reporting is suppressed, but traffic is carried. Raised fault conditions, whether or not their alarms are reported, can be retrieved on the CTC Conditions tab or by using the TL1 RTRV-COND command. SWDL softwareDownload The card is involved in a software and database download. This SST applies only to cards. UAS unassigned The card is not provisioned in the database. This SST applies only to cards. UEQ (Unequipped) notInstalled The card is not physically present (that is, an empty slot). This SST applies only to cards. Table B-3 ONS 15454 Administrative States ANSI Administrative State (PST,SST) ETSI Administrative State (PST,SST) Definition IS Unlocked Puts the entity in service. IS,AINS Unlocked,automaticInService Puts the entity in automatic in-service.B-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3 Service State Transitions This section describes the transition from one service state to the next state for DWDM shelves, cards, optical payload ports, OSC ports, OCHNCs, and transponder/muxponder cards and ports. A service state transition is based on the action performed on the entity and any autonomous activity. Note When an entity is put in the OOS,MT administrative state, the ONS node suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnOOS-MTPorts (ANSI) or NODE.general.ReportLoopbackConditionsOnPortsInLocked,Maintenance (ETSI) to TRUE on the NE Defaults tab. B.3.1 DWDM Shelf Service State Transitions Table B-4 lists ANSI and ETSI service state transitions for shelf entities. OOS,DSBLD Locked,disabled Removes the entity from service and disables it. OOS,MT Locked,maintenance Removes the entity from service for maintenance. Table B-3 ONS 15454 Administrative States (continued) ANSI Administrative State (PST,SST) ETSI Administrative State (PST,SST) Definition Table B-4 ONS 15454 Shelf Service State Transitions Current Service State Action Next Service State OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Connect a shelf. IS-NR (ANSI) Unlocked-enabled (ETSI) Connect an invalid shelf. OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Add a shelf. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Disconnect a shelf. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Add a shelf. IS-NR (ANSI) Unlocked-enabled (ETSI)B-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3.2 DWDM Card Service State Transitions Table B-5 lists ANSI and ETSI service state transitions for AD-1B-xx.x, AD-4B-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, OSC-CSM, OSCM, OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-PRE, OPT-AMP-17-C, OPT-AMP-17-C, 4MD-xx.x, 32WSS, 32WSS-L, 32MUX-O, 32DMX, 32DMX-L, 32DMX-O, 40-MUX-C, 40-DMX-C, 40-DMX-CE, 40-WSS-C, 40-WSS-CE, 40-WXC-C, and 80-WXC-C cards. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) Connect a shelf. IS-NR (ANSI) Unlocked-enabled (ETSI) Connect an invalid shelf. OOS-AU,AINS & MEA (ANSI) Unlocked-disabled,automaticInService & mismatchOfEquipment (ETSI) Delete a shelf. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Connect a shelf. IS-NR (ANSI) Unlocked-enabled (ETSI) Connect an invalid shelf. OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Delete a shelf. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) IS-NR (ANSI) Unlocked-enabled (ETSI) Delete a shelf. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Disconnect a shelf. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Disconnect a shelf. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) OOS-AUMA,AINS & MEA (ANSI) Locked-disabled,automaticInService & mismatchOfEquipment (ETSI) Disconnect a shelf. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Disconnect a shelf. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Delete a shelf. OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Table B-4 ONS 15454 Shelf Service State Transitions (continued) Current Service State Action Next Service StateB-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions Table B-5 ONS 15454 Optical Unit Service State Transitions Current Service State Action Next Service State IS-NR (ANSI) Unlocked-enabled (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Reset the card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Alarm/condition is raised. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) OOS-AU,AINS & MEA (ANSI) Unlocked-disabled,automaticInService & mismatchOfEquipment (ETSI) Pull the card. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) Delete the card. If the card is valid: • OOS-AUMA,UAS (ANSI) • Locked-disabled,unassigned (ETSI) If the card is invalid: • OOS-AUMA,MEA & UAS (ANSI) • Locked-disabled,mismatchOfEquipment & unassigned (ETSI) OOS-AU,AINS & SWDL (ANSI) Unlocked-disabled,automaticInService & softwareDownload (ETSI) Restart completed. IS-NR (ANSI) Unlocked-enabled (ETSI) OOS-AU,AINS & MEA (ANSI) Unlocked-disabled,automaticInService & mismatchOfEquipment (ETSI) Pull the card. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) Insert a valid card. OOS-AU,AINS & SWDL (ANSI) Unlocked-disabled,automaticInService & softwareDownload (ETSI) Insert an invalid card. OOS-AU,AINS & MEA (ANSI) Unlocked-disabled,automaticInService & mismatchOfEquipment (ETSI) Delete the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI)B-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,unequipped (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Reset the card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Delete the card. If the card is valid: • OOS-AUMA,UAS (ANSI) • Locked-disabled,unassigned (ETSI) If the card is invalid: • OOS-AUMA,MEA & UAS (ANSI) • Locked-disabled,mismatchOfEquipment & unassigned (ETSI) OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Restart completed. IS-NR (ANSI) Unlocked-enabled (ETSI) OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Insert a valid card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Insert an invalid card. OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Delete the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Table B-5 ONS 15454 Optical Unit Service State Transitions (continued) Current Service State Action Next Service StateB-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Pull the card. OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Change the administrative state to IS (ANSI) or Unlocked (ETSI). OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Reset the card. OOS-AUMA,MT & SWDL (ANSI) Locked-disabled,maintenance & softwareDownload (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Pull the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Provision the card. OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) OOS-AUMA,MT & SWDL (ANSI) Locked-disabled,maintenance & softwareDownload (ETSI) Restart completed. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) OOS-AUMA,MEA & MT (ANSI) Locked-disabled,mismatchOfEquipment & maintenance (ETSI) Pull the card. OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Pull the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Provision an invalid card. OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Provision a valid card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Insert a valid card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Insert an invalid card. OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Preprovision a card. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) Table B-5 ONS 15454 Optical Unit Service State Transitions (continued) Current Service State Action Next Service StateB-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3.3 Optical Payload Port Service State Transitions Table B-6 lists the ANSI and ETSI optical payload port service state transitions. Table B-6 ONS 15454 Optical Payload Port Service State Transitions Current Service State Action Next Service State IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) The OCHNC end-to-end path no longer exists. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Alarm/condition is raised. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) All required OCHNC connections exist. IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Alarm/condition is raised. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Alarm/condition is cleared. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port or cross-connect in the IS (ANSI) or Unlocked (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port or cross-connect in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port or cross-connect in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI)B-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port or cross-connect in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port or cross-connect in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port or cross-connect in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) Release the loopback. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,LPBK & MT (ANSI) Locked-enabled,loopback & maintenance (ETSI) OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port or cross-connect in the IS (ANSI) or Unlocked-enabled (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port or cross-connect in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port or cross-connect in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port or cross-connect in a loopback. OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) Table B-6 ONS 15454 Optical Payload Port Service State Transitions (continued) Current Service State Action Next Service StateB-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3.4 OSC Port Service State Transitions Table B-7 lists the ANSI and ETSI OSC port service state transitions. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Alarm/condition is raised. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Table B-6 ONS 15454 Optical Payload Port Service State Transitions (continued) Current Service State Action Next Service State Table B-7 ONS 15454 OSC Port Service State Transitions Current Service State Action Next Service State IS-NR (ANSI) Unlocked-enabled (ETSI) Delete the OSC. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Alarm/condition is raised. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Create the OSC. IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Alarm/condition is raised. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI)B-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Alarm/condition is cleared. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the IS (ANSI) or Unlocked (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the IS (ANSI) or Unlocked-enabled (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in a loopback. OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) Table B-7 ONS 15454 OSC Port Service State Transitions (continued) Current Service State Action Next Service StateB-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3.5 OCHNC, OCHCC, and OCH-Trail Service State Transitions Table B-8 lists the ANSI and ETSI OCHNC, OCHCC, and OCH-Trail service state transitions. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Alarm/condition is raised. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Table B-7 ONS 15454 OSC Port Service State Transitions (continued) Current Service State Action Next Service State Table B-8 ONS 15454 OCHNC Service State Transitions Current Service State Action Next Service State IS-NR (ANSI) Unlocked-enabled (ETSI) Put the connection in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Alarm/condition is raised. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the connection in the IS (ANSI) or Unlocked (ETSI) administrative state. IS-NR (ANSI) Unlocked-enabled (ETSI) Alarm/condition is raised. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Alarm/condition is cleared. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the IS (ANSI) or Unlocked (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI)B-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3.6 Transponder/Muxponder Card Service State Transitions Table B-9 lists ANSI and ETSI transponder and muxponder card service state transitions. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) Release the loopback. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,LPBK & MT (ANSI) Locked-enabled,loopback & maintenance (ETSI) OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the IS (ANSI) or Unlocked-enabled (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in a loopback. OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the connection in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Table B-8 ONS 15454 OCHNC Service State Transitions (continued) Current Service State Action Next Service StateB-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions Table B-9 ONS 15454 Transponder/Muxponder Card Service State Transitions Current Service State Action Next Service State IS-NR (ANSI) Unlocked-enabled (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Reset the card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Alarm/condition is raised. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) OOS-AU,AINS & MEA (ANSI) Unlocked-disabled,automaticInService & mismatchOfEquipment (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-AUMA,MEA & MT (ANSI) Locked-disabled,mismatchOfEquipment & maintenance (ETSI) Pull the card. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) Delete the card. If the card is valid: • OOS-AUMA,UAS (ANSI) • Locked-disabled,unassigned (ETSI) If the card is invalid: • OOS-AUMA,MEA & UAS (ANSI) • Locked-disabled,mismatchOfEquipment & unassigned (ETSI) OOS-AU,AINS & SWDL (ANSI) Unlocked-disabled,automaticInService & softwareDownload (ETSI) Restart completed. IS-NR (ANSI) Unlocked-enabled (ETSI) Pull the card. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI)B-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) Insert a valid card. OOS-AU,AINS & SWDL (ANSI) Unlocked-disabled,automaticInService & softwareDownload (ETSI) Insert an invalid card. OOS-AU,AINS & MEA (ANSI) Unlocked-disabled,automaticInService & mismatchOfEquipment (ETSI) Delete the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,unequipped (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Reset the card. OOS-AU,SWDL (ANSI) Unlocked-disabled,softwareDownload (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) OOS-AU,MEA (ANSI) Unlocked-disabled,mismatchOfEquipment (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Unlocked-disabled,notInstalled (ETSI) Delete the card. If the card is valid: • OOS-AUMA,UAS (ANSI) • Locked-disabled,unassigned (ETSI) If the card is invalid: • OOS-AUMA,MEA & UAS (ANSI) • Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) Table B-9 ONS 15454 Transponder/Muxponder Card Service State Transitions (continued) Current Service State Action Next Service StateB-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AU,SWDL (ANSI) Locked-disabled,softwareDownload (ETSI) Restart completed. IS-NR (ANSI) Unlocked-enabled (ETSI) Pull the card. OOS-AU,UEQ (ANSI) Locked-disabled,notInstalled (ETSI) OOS-AU,UEQ (ANSI) Locked-disabled,notInstalled (ETSI) Insert a valid card. OOS-AU,SWDL (ANSI) Locked-disabled,softwareDownload (ETSI) Insert an invalid card. OOS-AU,MEA (ANSI) Locked-disabled,mismatchOfEquipment (ETSI) Delete the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Change the administrative state to OOS,MT (ANSI) or Locked,maintenance (ETSI). OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Pull the card. OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Change the administrative state to IS (ANSI) or Unlocked (ETSI). OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Reset the card. OOS-AUMA,MT & SWDL (ANSI) Locked-disabled,maintenance & softwareDownload (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) Table B-9 ONS 15454 Transponder/Muxponder Card Service State Transitions (continued) Current Service State Action Next Service StateB-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AUMA,MEA & MT (ANSI) Locked-disabled,mismatchOfEquipment & maintenance (ETSI) Change the administrative state to IS (ANSI) or Unlocked (ETSI). OOS-AU,MEA (ANSI) Locked-disabled,mismatchOfEquipment (ETSI) Pull the card. OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) Delete the card. If the card is valid: • OOS-AUMA,UAS (ANSI) • Locked-disabled,unassigned (ETSI) If the card is invalid: • OOS-AUMA,MEA & UAS (ANSI) • Locked-disabled,mismatchOfEquipment & unassigned (ETSI) OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Pull the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Provision the card. OOS-AU,MEA (ANSI) Locked-disabled,mismatchOfEquipment (ETSI) OOS-AUMA,MT & SWDL (ANSI) Locked-disabled,maintenance & softwareDownload (ETSI) Restart completed. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Pull the card. OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) Change the administrative state to IS (ANSI) or Unlocked (ETSI). OOS-AU,UEQ (ANSI) Locked-disabled,notInstalled (ETSI) Insert a valid card. OOS-AUMA,MT & SWDL (ANSI) Locked-disabled,maintenance & softwareDownload (ETSI) Insert an invalid card. OOS-AUMA,MEA & MT (ANSI) Locked-disabled,mismatchOfEquipment & maintenance (ETSI) Delete the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Table B-9 ONS 15454 Transponder/Muxponder Card Service State Transitions (continued) Current Service State Action Next Service StateB-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions B.3.7 Transponder/Muxponder Port Service State Transitions Table B-10 lists the ANSI and ETSI transponder and muxponder port service state transitions. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Pull the card. OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Provision an invalid card. OOS-AU,MEA (ANSI) Locked-disabled,mismatchOfEquipment (ETSI) Provision a valid card. OOS-AU,SWDL (ANSI) Locked-disabled,softwareDownload (ETSI) OOS-AUMA,UAS & UEQ (ANSI) Locked-disabled,unassigned & notInstalled (ETSI) Insert a valid card. OOS-AU,SWDL (ANSI) Locked-disabled,softwareDownload (ETSI) Insert an invalid card. OOS-AUMA,MEA & UAS (ANSI) Locked-disabled,mismatchOfEquipment & unassigned (ETSI) Preprovision a card. OOS-AU,AINS & UEQ (ANSI) Unlocked-disabled,automaticInService & notInstalled (ETSI) OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Change the administrative state to IS (ANSI) or Unlocked (ETSI). IS-NR (ANSI) Unlocked-enabled (ETSI) Delete the card. OOS-AUMA,UAS (ANSI) Locked-disabled,unassigned (ETSI) Pull the card. OOS-AUMA,MT & UEQ (ANSI) Locked-disabled,maintenance & notInstalled (ETSI) Reset the card. OOS-AUMA,MT & SWDL (ANSI) Locked-disabled,maintenance & softwareDownload (ETSI) Alarm/condition is raised. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Table B-9 ONS 15454 Transponder/Muxponder Card Service State Transitions (continued) Current Service State Action Next Service StateB-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions Table B-10 ONS 15454 Transponder/Muxponder Port Service State Transitions Current Service State Action Next Service State IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Alarm/condition is raised. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the IS (ANSI) or Unlocked (ETSI) administrative state. IS-NR1 (ANSI) Unlocked-enabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Alarm/condition is raised. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Alarm/condition is cleared. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the IS (ANSI) or Unlocked (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI)B-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Alarm/condition is cleared. IS-NR (ANSI) Unlocked-enabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) Release the loopback. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,LPBK & MT (ANSI) Locked-enabled,loopback & maintenance (ETSI) OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) Alarm/condition is cleared. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the IS (ANSI) or Unlocked-enabled (ETSI) administrative state. OOS-AU,FLT (ANSI) Unlocked-disabled,failed (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS & FLT (ANSI) Unlocked-disabled,automaticInService & failed (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in a loopback. OOS-AUMA,FLT & LPBK & MT (ANSI) Locked-disabled,failed & loopback & maintenance (ETSI) Table B-10 ONS 15454 Transponder/Muxponder Port Service State Transitions (continued) Current Service State Action Next Service StateB-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in the IS (ANSI) or Unlocked (ETSI) administrative state. IS-NR1 (ANSI) Unlocked-enabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the OOS,MT (ANSI) or Locked,maintenance (ETSI) administrative state. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) OOS-MA,LPBK & MT (ANSI) Locked-enabled,loopback & maintenance (ETSI) Release the loopback. OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Table B-10 ONS 15454 Transponder/Muxponder Port Service State Transitions (continued) Current Service State Action Next Service StateB-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix B Administrative and Service States Service State Transitions OOS-MA,MT (ANSI) Locked-enabled,maintenance (ETSI) Put the port in the IS (ANSI) or Unlocked (ETSI) administrative state. IS-NR1 Unlocked-enabled (ETSI) Put the port in the IS,AINS (ANSI) or Unlocked,automaticInService (ETSI) administrative state. OOS-AU,AINS (ANSI) Unlocked-disabled,automaticInService (ETSI) Put the port in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) administrative state. OOS-MA,DSBLD (ANSI) Locked-enabled,disabled (ETSI) Put the port in loopback. OOS-MA,LPBK & MT2 3 (ANSI) Locked-enabled,loopback & maintenance (ETSI) Alarm/condition is raised. OOS-AUMA,FLT & MT (ANSI) Locked-disabled,failed & maintenance (ETSI) 1. The transponder and muxponder cards have both client and trunk ports. To bring up service, it is not necessary for both the client side and trunk side to be in the IS-NR (ANSI)/Unlocked-enabled (ETSI) service state. 2. In a client-side facility loopback, the client port is in the OOS-MA,LPBK & MT (ANSI)/Locked-enabled,loopback and maintenance (ETSI) service state and the remaining client and trunk ports can be in any other service state. In a client-side terminal loopback on transponder cards, the client port is in the OOS-MA,LPBK & MT service state and the trunk ports are in IS-NR (ANSI)/Unlocked-enabled (ETSI). For client-side terminal loopbacks on muxponder cards, the client port is in the OOS-MA,LPBK & MT service state and the remaining client and trunk ports can be in any service state. 3. In a trunk-side facility loopback, the trunk port is in the OOS-MA,LPBK & MT (ANSI)/Locked-enabled,loopback and maintenance (ETSI) service state and the remaining client and trunk ports can be in any other service state. In a trunk-side terminal loopback, the trunk port is in the OOS-MA,LPBK & MT (ANSI)/Locked-enabled,loopback and maintenance (ETSI) service state and the client ports are in IS-NR (ANSI)/Unlocked-enabled (ETSI) for complete loopback functionality. This type of loopback affects all client ports because it is performed on the aggregate signal. Table B-10 ONS 15454 Transponder/Muxponder Port Service State Transitions (continued) Current Service State Action Next Service StateC-1 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 APPENDIX C Pseudo Command Line Interface Reference This chapter describes Pseudo-IOS command line interface (PCLI) for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies. C.1 Understanding PCLI PCLI provides an IOS-like command line interface for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards in Layer 2 (L2) mode. PCLI employs the Cisco IOS Modular QoS CLI (MQC). PCLI is a text interface from where you can operate, provision and retrieve GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card information. PCLI runs on the Timing, Communications, and Control (TCC) of the node controller, to access card level information. PCLI acts as a Corba client and provides the same provisioning mechanisms as CTC or TL1. PCLI can be accessed via CTC by selecting Tools > Open Pseudo IOS Connection menu option or right-click on the node in the Network View and select Open Pseudo IOS Connection. To access the PCLI text interface use Telnet, or SSH to open a shell session to connect to a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card and input IOS-like commands. To access PCLI from Windows XP, enter the following command at the Windows command prompt: telnet To access PCLI from Solaris 8, enter the following command: ssh –p telnet The PCLI shell supports the 454 multi-shelf architecture. Multi-shelf supports 16 shelves with each shelf containing 17 slots. The GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards can be inserted in any Input/Output (IO) slot or shelf. PCLI also provides a command to virtually connect to a specified shelf/slot. However, connection to a non-Xponder slot or to an Xponder slot that is not in L2 mode is not supported. PCLI supports a maximum of 16 concurrent login sessions per node controller. A session can be cancelled by logging out of the PCLI session or when the idle timer times out. Note PCLI adheres to the idle user timeout period security policy set via CTC or TL1.C-2 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference PCLI Command Modes Note For information on viewing security policies, refer the task, “DLP-G189 Change Security Policy for Multiple Nodes” in the Cisco ONS 15454 DWDM Procedure Guide. If a PCLI session on a node using a given port number is open, the port number used by the PCLI session cannot be changed. When connecting in a Non-Secure state to a node and a port, use the configured port number for non-secured mode only, and when connecting via a Secure state to a node and a port, use the configured port number for Secure mode. C.1.1 PCLI Security PCLI supports configurable secure or unsecure access with a configurable port number per access mechanism. Use CTC to view or modify these settings. The default access state is “Non-secure” and the default port number is “65000”. PCLI supports an unsecured connection via Telnet and a secure connection via Secure Shell (SSH) by using existing system authentication, authorization and accounting (AAA) mechanisms. Login with user/password that is configured at the Network Element (NE). Use CTC or TL1 to manage user accounts. Note If you have logged in to a PCLI connection in an Non-Secure state and change the connection via CTC to a Secure one (or vice versa), the Non-Secure state in PCLI (or Secure, as the case may be) is closed once the CTC configuration is completed. For information on setting the access states (Non-secure or Secure), refer Cisco ONS 15454 DWDM Procedure Guide. C.2 PCLI Command Modes The PCLI supports eight different command modes. Each command mode can be accessed by specifying a command. The prompt changes to reflect the new command mode that you are in. Consequently, the set of valid commands changes to reflect the sub-commands that are allowed within that mode. The following section shows supported PCLI commands for each command mode. C.2.1 Common Commands The following commands are common across all command modes. • ?—Enter a question mark (?) at the system prompt to display a list of commands available in each command mode. • !— Enter an exclamation symbol (!) at the system prompt to add comments. • exit—Enter exit at the system prompt to exit from the mode you are currently in. C.2.2 User EXEC Mode Prompt: (>)C-3 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference PCLI Command Modes After a successful login, the system goes to User Executive (EXEC) command mode. Most PCLI commands in the User EXEC mode do not change system operation. The User EXEC mode allows you to work on multiple GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards during a single session while restricting the view at any given time to a single card in a specific shelf and slot. This mode displays system wide parameters that span all cards in the node. The following commands are supported in the User EXEC mode: • enable shelf/slot • show modules • show users C.2.3 Privileged EXEC Mode Prompt: (#) In general, the Privileged EXEC commands allow you to connect to remote devices, perform basic tests, and lists system information. Most CLI commands in Privileged EXEC mode do not change or modify provisioning and system operation. The most common EXEC commands are show commands and are used to display configuration or operational data, and do not have capability to modify provisioning. To enter privileged EXEC mode, use the enable shelf/slot command. The following commands are part of Privileged EXEC mode: • configure terminal • reload • show startup-config • show users • show ip igmp snooping groups vlan vlanid • show interfaces • show ethernet service instance name • show vlan profiles • show vlans • show modules • show controllers type port • show history • show policy-maps • show policy-map name • show policy-map type port • show lacp [detail] • ethernet oam remote-loopback • show ethernet oam discovery • show ethernet oam statistics • show ethernet oam status • show ethernet oam summaryC-4 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference PCLI Command Modes • clear ethernet cfm • clear ethernet cfm statistics • show ethernet cfm domain • show ethernet cfm maintenance-points local • show ethernet cfm maintenance-points • show ethernet cfm mpdb • show ethernet cfm statistics • show interfaces rep • show rep topology C.2.4 Global Configuration Mode Prompt: Node Name# (Config) Enter global configuration mode from privileged EXEC mode. Global configuration commands generally apply to the whole system rather than just one protocol or interface. You can enter other configuration sub modes listed in this section from global configuration mode. To enter global configuration mode, use the configure terminal command. Note The node name can be configured by using CTC. Select Node view > General > General > Node Name The following commands are part of global configuration mode: • interface channel-group • ethernet cfm ieee • ethernet cfm domain • ethernet cfm service • mac-address-table learning vlan vlanid • [no] mac-address-table learning interface type port • [no] vlan vlan-id • interface gigabitethernet port • interface tengigabitethernet port • policy-map name • [no] mvr • mvr vlan • mvr group ip address count • rep admin svlan C.2.5 VLAN Configuration Mode Prompt: (config-vlan)C-5 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference PCLI Command Modes Enter VLAN configuration mode from global configuration mode. You can configure parameters for an individual VLAN. To enter VLAN configuration mode, use the vlan command. The following commands are part of VLAN configuration mode: • name vlan name • protected • ip igmp snooping • ip igmp snooping immediate-leave • ip igmp snooping report-suppression C.2.6 Interface Configuration Mode Prompt: (config-if) Enter interface configuration mode from global configuration mode. In this mode and other interface sub modes, a wide variety of capabilities are supported. You can configure provisioning on a specific module interface, i.e. port. To enter interface configuration mode, use the interface gigabitethernet port or interface tengigabitethernet port command. The following commands are part of interface configuration mode: • channel-group channel-number mode chanlgrp-mode • channel-group channel-number hash chanlgrp-hash • channel-group channel-number expected speed chanlgrp-speed • description description • ethernet oam • ethernet oam mode • ethernet oam link-monitor frame • ethernet oam link-monitor frame-period • ethernet oam link-monitor frame-seconds • ethernet oam link-monitor high-threshold • ethernet oam remote-failure link-fault • ethernet cfm mip • ethernet cfm mep • ethernet cfm interface • rep segment • rep stcn • rep preempt delay • rep preempt • rep preempt segment • rep block portC-6 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference PCLI Command Modes • shutdown • mtu bytes • speed auto|1000, 10000 • flowcontrol on|off • switchport mode trunk • switchport mode dot1q-tunnel • service-policy input name • service-policy output name • service instance ethernet name • l2protocol-tunnel • [no] switchport port-security mac-address mac-address • ip igmp snooping mrouter C.2.7 Service Instance Configuration Mode Prompt: (config-if-srv) Service instance configuration mode is a sub mode of the interface configuration mode and can be used to define service instances, i.e. Ethernet Flow Points (EFPs). EFPs are specific to a particular interface. Multiple EFPs can be strung together to make an Ethernet Virtual Circuit (EVC). The encapsulation commands can be used in any combination to implement flexible EFPs. However, the dot1q and untagged commands must be used for selective mode translations, and the default command must be used for transparent mode translations. The following restrictions apply to encapsulation commands: • Selective and transparent mode apply to a whole port and are mutually exclusive. • Encapsulation default is for transparent translations. Only one transparent service instance is allowed per port. • Encapsulation untagged is for selective translation with no cvlan tag. If the operation is DOUBLE_ADD (rewrite ingress tag push dot1q second-dot1q ), only one service instance is allowed per port. To enter service instance configuration mode, use the service instance ethernet name command. The following commands are part of service instance configuration mode: • encapsulation default • encapsulation dot1q first cvlan last cvlan • encapsulation untagged • service-policy input name • bridge-domain svlan Note The encapsulation and rewrite commands are work together. These commands take effect only if the following sequence is followed: 1. Enter the encapsulation command.C-7 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference PCLI Command Modes 2. Enter the rewrite command. Note A service instance cannot be edited once user exits the service instance configuration mode. To make changes to any of these parameters, delete the service instance and recreate it. C.2.8 Policy Map Configuration Mode Prompt: (config-pmap) Enter policy map configuration mode from global configuration mode by using the policy-map command to create a policy map or modify an existing policy map. This mode is part of the quality-of-service (QoS) feature. To attach a QoS policy to a specific interface, you must enter interface configuration mode from global configuration mode by identifying the interface and then using the service-policy command to attach an existing policy. QoS policy map provisioning can be accessed across multiple GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. To enter policy map configuration mode, enter the policy-map name command from the global config mode. The following commands are part of policy map configuration mode: • police cir percent % bc bytes be bytes • set cos number • wrr-queue cos-map queue-id cos1 … cosn • wrr-queue queue-id weight 1-16 bandwidth percent % C.2.9 VLAN Profile Config Mode Prompt: (config-profile) VLAN profile configuration mode can be used to provision the parameters for a VLAN profile. A VLAN profile can later be applied to multiple VLANs. VLAN profile provisioning can be accessed across multiple GE cards. To enter VLAN profile configuration mode, use the vlan profile name command from the global config mode. The following commands are part of VLAN profile configuration mode: • police cir percent % bc bytes be bytesC-8 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference enable shelf/slot enable shelf/slot To enter privileged EXEC mode, use the enable command in user EXEC mode. enable shelf/slot Syntax Description Command Modes User EXEC Usage Guidelines Use this command to enter privileged configuration mode. Entering privileged EXEC mode enables the use of privileged commands. Note the prompt for user EXEC mode is the greater than symbol (>), and the prompt for privileged EXEC mode is the hash symbol (#). Examples MSTP-176> enable 2/12 MSTP-176# shelf/slot Shelf and slot number.C-9 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference configure terminal configure terminal To enter global configuration mode, use the configure terminal command in privileged EXEC mode. configure terminal Syntax Description This command has no arguments or keywords. Command Modes Privileged EXEC Usage Guidelines Use this command to enter global configuration mode. After you enter the configure terminal command, the system prompt changes from # to (config)#, indicating that the card is now in global configuration mode. To leave global configuration mode and return to privileged EXEC mode, type exit. Examples MSTP-176# configure terminal MSTP-176(config)#C-10 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show modules show modules To display summary information (shelf/slot/port, equipment type, service state) of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card, use the show modules command in User EXEC and privileged EXEC mode. show modules Syntax Description This command has no arguments or keywords. Command Default No default behavior or values. Command Modes User EXEC and Privileged EXEC Examples The following is sample output of the show modules command: MSTP-176# show modules Shelf/Slot/Port EquipType ServiceState 1/NA/NA BIC_UNKNOWN IS-NR 1/1 /NA XP_GE_LINE_CARD IS-NR 1/1 /1 PPM_1_PORT OOS-AU,AINS&UEQ 1/1 /2 PPM_1_PORT OOS-AU,AINS&UEQ 1/1 /8 PPM_1_PORT OOS-AU,AINS&UEQ 1/1 /9 PPM_1_PORT OOS-AU,AINS&UEQ 1/1 /11 PPM_1_PORT IS-NR 1/1 /15 PPM_1_PORT IS-NR 1/1 /16 PPM_1_PORT OOS-AU,AINS&UEQ MSTP-176#C-11 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show vlans show vlans To display VLAN information, use the show vlans command in privileged EXEC mode. show vlans Syntax Description This command has no arguments or keywords. Command Default No default behavior or values Command Modes Privileged EXEC Examples The following is sample output of the show vlans command which shows the status of 1+1 protection, MAC address learning, IGMP snooping, immediate leave, and report suppression on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card for a given VLAN. MSTP-176# show vlans IGMP VLAN Name Prot MAC Learn Enable Immed Suppress 2 F F F F T 50 F F F F F 100 F F T F T 101 F F F F T MSTP-176#C-12 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show interfaces show interfaces To display port level parameters and statistics of interfaces configured on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE, use the show interfaces command in privileged EXEC mode. show interfaces Syntax Description This command has no arguments or keywords. Defaults Privileged EXEC Examples The following is sample output of the show interfaces command. The output in the example depends on the type and number of interfaces in the card. For this reason only a part of the output is shown. MSTP-176# show interfaces Port 22 (Trunk), Port name: Admin State: ADMIN_IS, Service State: IS_NR Reach: LR, Wavelength: WV_1310, AIS Action: NONE Flow Control: DISABLED, Duplex Mode: FULL, Speed: SPEED_10G, MTU: 9700 NI Mode: NNI, MAC Learning: DISABLED, IGMP Static Router Port: DISABLED Ingress CoS: 0, Ethertype Inner/Outer: 8100/8100, Egress QoS: DISABLED Committed Info Rate: 100, Burst Size Committed/Excess: BCKT_4K/BCKT_4K ifInOctets: 196928, rxTotalPkts: 2896, ifInUcastPkts: 0 ifInMulticastPkts: 2896, ifInBroadcastPkts: 0 ifInDiscards: 0, ifOutOctets: 448072424, txTotalPkts: 132911365 ifOutMulticastPkts: 132911359, ifOutBroadcastPkts: 0 ifOutDiscards: 0, ifOutErrors: 0 dot3StatsAlignmentErrors: 0, dot3StatsFCSErrors: 0 dot3StatsFrameTooLong: 0, dot3StatsControlInUnknownOpCodes: 0 dot3StatsInPauseFrames: 0, dot3StatsOutPauseFrames: 0 etherStatsUndersizePkts: 0, etherStatsFragments: 0 etherStatsPkts: 132914261, etherStatsPkts64Octets: 0 65-127 Octets: 132914247, 128-255 Octets: 0 256-511 Octets: 0, 512-1023 Octets: 0 1024-1518 Octets: 0, 1519-1522: 0 etherStatsBroadcastPkts: 0, etherStatsMulticastPkts: 132914255 etherStatsOversizePkts: 0, etherStatsJabbers: 0 etherStatsOctets: 448269352, etherStatsCRCAlignErrors: 0 etherStatsOctets: 448269352, etherStatsCRCAlignErrors: 0 ifHCInOctets: 196928, ifHCInUcastPkts: 0 ifHCInMulticastPkts: 2896, ifHCInBroadcastPkts: 0 ifHCOutOctets: 448072424, ifHCOutMulticastPkts: 132911359 ifHCOutBroadcastPkts: 0, etherStatsHighCapacityPkts: 132914261 etherStatsHighCapacityOctets: 448269352 etherStatsHighCapacityPkts64Octets: 0 etherStatsHighCapacityPkts65to127Octets: 132914247 etherStatsHighCapacityPkts128to255Octets: 0 etherStatsHighCapacityPkts256to511Octets: 0 etherStatsHighCapacityPkts512to1023Octets: 0 etherStatsHighCapacityPkts1024to1518Octets: 0 cisRxReports: 2854, cisRxLeaves: 2 cisTxReports: 0, cisTxLeaves: 2 cisTxGeneralQueries: 2251, cisTxGroupSpecificQueries: 6 cisRxGeneralQueries: 35, RxGroupSpecificQueries 5 cisRxValidPackets: 2896, cisRxInvalidPackets: 0 MSTP-176#C-13 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show policy-maps show policy-maps To display all policy maps in the node, use the show policy-maps command. Syntax Description This command has no arguments or keywords. Defaults Privileged EXEC Examples The following example displays all the policy maps on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards: MSTP-176# show policy-map Policy Name: port1 Policy Type: SERVICE INSTANCE CoS: 2 Policy Name: cos3 Policy Type: INGRESS Ingress CoS: 3 Committed Info Rate: 80 Committed Burst Size: 1 Excess Burst Size: 2 Excess Info Rate: 100 MSTP-176# C-14 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show policy-map name show policy-map name To display the information of an unnamed class, use the show policy-map command in privileged EXEC mode. show policy-map name Syntax Description Defaults Existing policy map configurations are displayed. Command Modes Privileged EXEC Examples The show policy-map command displays the configuration of a service policy map that was created using the policy-map name command. The following example displays the contents of policy map “pmapegress” on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card: MSTP-176# show policy-maps pmapegress Policy Name: pmapegress Policy Type: EGRESS CoS: 0 Queue: 0 Bandwidth: 15 Weight: 1 CoS: 1 Queue: 1 Bandwidth: 100 Weight: 1 CoS: 2 Queue: 2 Bandwidth: 100 Weight: 1 CoS: 3 Queue: 3 Bandwidth: 100 Weight: 1 CoS: 4 Queue: 4 Bandwidth: 100 Weight: 1 CoS: 5 Queue: 5 Bandwidth: 100 Weight: 1 CoS: 6 Queue: 6 Bandwidth: 100 Weight: 1 CoS: 7 Queue: 7 Bandwidth: 100 Weight: 1 MSTP-176# name (Optional) The name of the service policy map whose complete configuration is to be displayed. The name can be a maximum of 31 characters.C-15 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show policy-map type port show policy-map type port To display all the policy maps configured on the port, use the show policy-map type port in privileged EXEC mode. show policy-map type port Syntax Description Command Default This command has no default behavior or values. Command Modes Privileged EXEC Usage Guidelines The show policy-map type port command displays the configuration of classes on the specified interface. Examples This section provides sample output of a typical show policy-map type port command. The output in the example depends on the type, number of interfaces and options enabled on the card. For this reason only a part of the output is shown and may vary. MSTP-176# show policy-map int g 1 Policy Name: ingress Policy Type: INGRESS Ingress CoS: 3 Committed Info Rate: 50 Committed Burst Size: 4K Excess Burst Size: 4K Policy Name: new Policy Type: EGRESS CoS: 0 Queue: 0 Bandwidth: 100 Weight: 1 CoS: 1 Queue: 1 Bandwidth: 90 Weight: 2 CoS: 2 Queue: 0 Bandwidth: 100 Weight: 1 CoS: 3 Queue: 3 Bandwidth: 100 Weight: 1 CoS: 4 Queue: 4 Bandwidth: 100 Weight: 1 CoS: 5 Queue: 5 Bandwidth: 100 Weight: 1 CoS: 6 Queue: 6 Bandwidth: 100 Weight: 1 CoS: 7 Queue: 7 Bandwidth: 100 Weight: 1 MSTP-176# type port Interface type and port number.C-16 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show controllers type port show controllers type port To display information about Small Form-factor Pluggable (SFP) installed, use the show controllers type port command in privileged EXEC mode. show controllers type port Syntax Description Defaults No defaults Command Modes Privileged EXEC Examples This section provides sample output of a typical show controllers type port command. MSTP-176# show controllers g 2 Port 22 SFP is Present Equipment Type : 1GE/1FC/2FC-1310nm HW Part Number : 10-2273-01 HW Revision : A Serial Number : FNS1032J435 CLEI Code : WMOTB17AAA Product ID : ONS-SE-G2F-LX Version ID : V01 MSTP-176# type port Interface type and port number.C-17 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show vlan profiles show vlan profiles To display the parameters of all configured VLANs or one VLAN (if the VLAN ID or name is specified), use the show vlan profiles command in privileged EXEC mode. Note A vlan profile is a named set of vlan attributes. A profile can be associated to a VLAN ID on an interface. A profile can be attached to multiple vlan/interface pairs. show vlan profiles Command Modes Privileged EXEC Examples The following example shows the output of the show vlan profiles command: MSTP-176# show vlan profiles Name CIR BC PIR BE LinkIntegrity a_profile 100 4 100 4 F d_profile 200 4 100 4 T e_profile 300 4 100 4 F v_profile 400 4 100 4 T MSTP-176#C-18 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show vlan profiles name show vlan profiles name To display the parameters of all configured VLANs or one VLAN (if the VLAN ID or name is specified), use the show vlan profiles name command in privileged EXEC mode. Syntax Description Note A vlan profile is a named set of vlan attributes. A profile can be associated to a VLAN ID on an interface. A profile can be attached to multiple vlan/interface pairs. Command Modes Privileged EXEC Examples The following example shows the output of the show vlan profiles name command: MSTP-176# show vlan profiles a_profile Name CIR BC PIR BE LinkIntegrity a_profile 100 4 100 4 F name Displays information about a single VLAN identified by VLAN name.C-19 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet service instance name show ethernet service instance name To display information about ethernet customer service instances, use the show ethernet service instance name command in privileged EXEC mode. show ethernet service instance name Syntax Description Command Modes Privileged EXEC Usage Guidelines This command is useful for system monitoring and troubleshooting. Examples The following is an example of output from the show ethernet service instance command: MSTP-176# show ethernet service instance Identifier Interface CE-Vlans 222 FastEthernet0/1 untagged,1-4093 10 FastEthernet0/2 222 FastEthernet0/2 200 333 FastEthernet0/2 default 10 FastEthernet0/3 300 11 FastEthernet0/3 10 FastEthernet0/4 300 10 FastEthernet0/6 untagged,1-4093 10 FastEthernet0/7 untagged,1-4093 10 FastEthernet0/8 untagged,1-4093 10 FastEthernet0/9 untagged 20 FastEthernet0/9 222 FastEthernet0/11 300-350,900-999 333 FastEthernet0/11 100-200,1000,1999-4093 222 FastEthernet0/12 20 333 FastEthernet0/12 10 10 FastEthernet0/13 10 20 FastEthernet0/13 20 30 FastEthernet0/13 30 200 FastEthernet0/13 222 200 FastEthernet0/14 200,222 300 FastEthernet0/14 333 555 FastEthernet0/14 555 name Displays service instance information of the specified service instance.C-20 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show users show users To display information about the active users on the node, use the show users command in user EXEC or privileged EXEC mode. show users Syntax Description This command has no arguments or keywords. Command Modes User EXEC or Privileged EXEC Usage Guidelines This command displays user name, security level, aaplications users are using and login time of all users on the node. Examples The following is a sample output of the show users command: MSTP-176# show users User1, SUPERUSER, PCLI, loginTime:05.13.2000 10:08:29 User2, SUPERUSER, EMS, loginTime:05.13.2000 10:05:27 User3, SUPERUSER, EMS, loginTime:05.13.2000 09:39:35 User4, SUPERUSER, EMS, loginTime:05.13.2000 07:35:18 MSTP-176#C-21 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference reload reload To reset a card, use the reload command in privileged EXEC mode. reload Syntax Description This command has no arguments or keywords. Command Modes Privileged EXEC Usage Guidelines This command resets the card that is currently used. Examples The following is a sample output of the reload command: MSTP-176> reload Warning! Resetting this card may impact traffic. Please confirm (yes/no): n Command cancelled. MSTP-176>C-22 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show history show history To list the commands you have entered in the current session (in all modes), use the show history command. show history Syntax Description This command has no arguments or keywords. Command Modes All modes Usage Guidelines The show history command provides a record of commands you have entered. The history buffer records 100 commands. The show history command can be used with the help of certain keys as shown in Table C-1. Examples The following is a sample output from the show history command, which lists the commands the user has entered in privileged EXEC mode for this session: MSTP-176# show history help show users show history MSTP-176# Table C-1 History Keys Card Port Description Ctrl-P or Up Arrow11 1. The arrow keys function only with ANSI-compatible terminals. Recalls commands in the history buffer in a backward sequence, beginning with the most recent command. Repeat the key sequence to recall successively older commands. Ctrl-N or Down Arrow1 Returns to more recent commands in the history buffer after recalling commands with Ctrl-P or the Up Arrow. Repeat the key sequence to recall successively more recent commands. C-23 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show startup-config show startup-config To display the current configuration of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card, use the show startup-config command in privileged EXEC mode. The start-up config and the running-config are the same. show startup-config Syntax Description This command has no arguments or keywords. Command Modes Privileged EXEC Command Default No defaults Examples The following partial sample output displays the configuration file named startup-config: MSTP-176# show startup-config interface tengigabitethernet 22 speed 10000 mtu 9700 flowcontrol off switchport mode trunk switchport dot1q ethertype 8100 switchport dot1q ethertype inner 8100 no ip igmp snooping mrouter switchport port-security mac-address blocked no l2protocol-tunnel link integrity action none service instance ethernet no shutdown vlan profile a no link integrity police cir percent 100 pir percent 100 bc 4 be 4 no mac-address-table learning interface gigabitethernet 11 no mac-address-table learning interface gigabitethernet 13 no mac-address-table learning interface tengigabitethernet 21 no mac-address-table learning interface tengigabitethernet 22 end MSTP-176#C-24 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ip igmp snooping groups vlan vlanid show ip igmp snooping groups vlan vlanid To display the multicast groups that were learned through Internet Group Management Protocol (IGMP) on a given SVLAN/MVLAN, use the show ip igmp groups vlan vlanid in privileged EXEC mode. show ip igmp groups vlan vlanid Syntax Description Command Modes Privileged EXEC Command Default No defaults. Examples The following partial sample output displays the multicast groups for VLAN 10: MSTP-176# show ip igmp sn gr vlan 128 MCAST IP ADDR VLAN Ports 224.1.1.1 128 ETHER(99)/SH-1/SL-13/PRT-2 224.1.1.2 128 ETHER(99)/SH-1/SL-13/PRT-2 224.1.1.3 128 ETHER(99)/SH-1/SL-13/PRT-2 MSTP-176# vlanid VLAN ID range is 1 to 4093. C-25 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show lacp [detail] show lacp [detail] To display detailed LACP information from the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards, use the show lacp command in privileged EXEC mode. show lacp [detail] Syntax Description Command Default None Command Modes Privileged EXEC (#) Usage Guidelines If you omit the detail keyword, basic LACP information is shown. Examples The following is a sample output for the show lacp command: MSTP-176# show lacp Flags: S - Device is requesting Slow LACPDUs F - Device is requesting Fast LACPDUs A - Device is in Active mode P - Device is in Passive mode Link state can be: bndl: active in an aggregation hot-sby: In hot standby mode (Not supported) susp: LACP not up down: link is not available ________________________________________________________________________________ Channel Group 1 ________________________________________________________________________________ Actor Port Flags State LACP Port Admin Oper Port Number Priority Key Key State Phy21 SP down 32768 1 0 0x44 -------------------------------------------------------------------------------- Partner Oper Flags State LACP Port Admin Oper Port Port # Priority Key Key State Phy21 0 SP down 0 0 0 0x0 ________________________________________________________________________________ MSTP-176# detail Shows the detailed LACP information.C-26 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam remote-loopback ethernet oamremote-loopback To turn on or off the remote loopback function on an EFM interface, use the ethernet oam remote-loopback command in privileged EXEC mode. This command does not have a no form. ethernet oam remote-loopback {start|stop} {interface number} Syntax Description Command Default By default, the remote loopback function is turned off. Command Modes Privileged EXEC (#) Usage Guidelines When the remote loopback function is enabled on an EFM interface, traffic passed on this interface is discarded by the remote interface. Examples The following example shows how to start a remote loopback session on a specific interface: MSTP-176# ethernet oam remote-loopback start interface 8 start Starts the remote loopback operation. stop Stops the remote loopback operation. interface Specifies an Ethernet interface. number Number of the Ethernet interface. If the operation is start, the range of number is 1 to 20; if the operation is stop, the range of number is 21 to 22.C-27 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet oam discovery show ethernet oam discovery To display discovery information for all EFM interfaces or for a specific EFM interface, use the show ethernet oam discovery command in privileged EXEC mode. show ethernet oam discovery [interface number] Syntax Description Command Default None Command Modes Privileged EXEC (#) Usage Guidelines This command displays the following information pertaining to Ethernet OAM discovery: • Remote device which is directly connected to this device • Local and remote OAM configuration and capability • Local and remote OAM mode • Remote platform identity • State of the local discovery state machine If an interface is specified, only data pertaining to the OAM peer on that interface is displayed; otherwise, data for all OAM peers on all interfaces is displayed. Examples The following example shows how to display discovery information for a specific EFM interface. MSTP-176# show ethernet oam discovery Interface-22: Local client ------------ Administrative configurations: Mode: active Link monitor: (on) Remote loopback: supported Mtu size: 1500 Operational status: Port status: active send Loopback status: no loopback PDU revision: 0 Remote client ------------- Remote Ethernet OAM client has not been found! MSTP-176# interface Specifies an Ethernet interface. number Number of the Ethernet interface. The number ranges from 1 to 22.C-28 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet oam statistics show ethernet oam statistics To display detailed information about the EFM packets, use the show ethernet oam statistics command in privileged EXEC mode. show ethernet oam statistics [interface number] Syntax Description Command Default None Command Modes Privileged EXEC (#) Usage Guidelines This command displays the following statistics: • Rx/Tx OAM Protocol Data Unit (PDU) counters • Link monitoring events, including event logs, if available • Remote fault detection events • Remote loopback events Examples The following example shows how to display information for a specific interface: MSTP-176# show ethernet oam statistics interface 22 Interface-22: Counters: --------- Information OAMPDU Tx: 1 Information OAMPDU Rx: 0 Unique Event Notification OAMPDU Tx: 0 Unique Event Notification OAMPDU Rx: 0 Duplicate Event Notification OAMPDU TX: 0 Duplicate Event Notification OAMPDU RX: 0 Loopback Control OAMPDU Tx: 0 Loopback Control OAMPDU Rx: 0 Variable Request OAMPDU Tx: 0 Variable Request OAMPDU Rx: 0 Variable Response OAMPDU Tx: 0 Variable Response OAMPDU Rx: 0 Cisco OAMPDU Tx: 0 Cisco OAMPDU Rx: 0 Unsupported OAMPDU Tx: 0 Unsupported OAMPDU Rx: 0 Frames Lost due to OAM: 0 Local Faults: ------------- 1 Link Fault records interface Specifies an Ethernet interface. number Number of the Ethernet interface. The number ranges from 1 to 22.C-29 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet oam statistics Total link faults: 1 Time stamp: 1271800854d 0 Dying Gasp records 0 Critical Event records Remote Faults: -------------- 0 Link Fault records 0 Dying Gasp records 0 Critical Event records Local event logs: ----------------- 0 Errored Symbol Period records 0 Errored Frame records 0 Errored Frame Period records 0 Errored Frame Second records Remote event logs: ------------------ 0 Errored Symbol Period records 0 Errored Frame records 0 Errored Frame Period records 0 Errored Frame Second records MSTP-176#C-30 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet oam status show ethernet oam status To display EFM configurations for all interfaces or for a specific interface, use the show ethernet oam status command in privileged EXEC mode. show ethernet oam status [interface number] Syntax Description Command Default None Command Modes Privileged EXEC (#) Usage Guidelines Use this command to display the runtime settings of link monitoring and general OAM operations for all the interfaces or for a specific interface. OAM must be operational on the interfaces before you use this command. Examples The following example shows how to display EFM configurations for a specific interface: MSTP-176# show ethernet oam status interface 22 Interface-22: General ------- Admin state: enabled Mode: active PDU rate: 1 packet per 1 second Link timeout: 5 seconds High threshold action: error block interface Link fault action: error block interface Link Monitoring --------------- Status: Frame Error Window: 10 x 100 milliseconds Low threshold: 10 error frame(s) High threshold: 10 error frame(s) Frame Period Error Window: 1000 x 10000 frames Low threshold: 9 error frame(s) High threshold: 10 error frame(s) Frame Seconds Error Window: 100 x 100 milliseconds Low threshold: 1 error second(s) High threshold: none MSTP-176# interface Specifies an Ethernet interface. number Number of the Ethernet interface. The number ranges from 1 to 22.C-31 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet oam summary show ethernet oam summary To display the active EFM sessions on a device, use the show ethernet oam summary command in privileged EXEC mode. show ethernet oam summary Syntax Description This command has no arguments or keywords. Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to display the active EFM sessions on a device: MSTP-176# show ethernet oam summary Symbols: * - Master Loopback State, # - Slave Loopback State & - Error Block State Capability codes: L - Link Monitor, R - Remote Loopback U - Unidirection, V - Variable Retrieval Local Remote Interface MAC Address OUI Mode Capability Interface-22 MSTP-176#C-32 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference clear ethernet cfm clear ethernet cfm To clear the Maintenance Intermediate Point (MIP) and Maintenance End Point (MEP) database in CFM, use the clear ethernet cfm maintenance-points remote command in privileged EXEC mode. clear ethernet cfm maintenance-points remote Syntax Description This command has no arguments or keywords. Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to clear MIP and MEP database: MSTP-176# clear ethernet cfm maintenance-points remoteC-33 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference clear ethernet cfm statistics clear ethernet cfm statistics To clear the CFM statistics, use the clear ethernet cfm statistics command in privileged EXEC mode. clear ethernet cfm statistics Syntax Description This command has no arguments or keywords. Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to clear the CFM statistics: MSTP-176# clear ethernet cfm statisticsC-34 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet cfm domain show ethernet cfm domain To display brief information or detailed information about CFM maintenance domains and services configured under the domains, use the show ethernet cfm domain in privileged EXEC mode. show ethernet cfm domain [brief | domain_name] Syntax Description Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to display detailed information about a specific CFM maintenance domain: MSTP-176# show ethernet cfm domain test_domain Domain Name: test_domain Level:2 Attached to MAProfile: maprofile1 VlanId:150 CCEnabled: True MSTP-176# brief Displays brief information about CFM maintenance domains. domain_name Name of the maintenance domain.C-35 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet cfm maintenance-points local show ethernet cfm maintenance-points local To display the maintenance points configured on a device, use the show ethernet cfm maintenance-points local command in privileged EXEC mode. show ethernet cfm maintenance-points local [mip [level level] [service vlan] | mep [domain domain_name] [service vlan]] Syntax Description Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to display all the maintenance points configured on a device: MSTP-176# show ethernet cfm maintenance-points local Local MEP Configuration Local MIP Configuration Port: 1 SvlanId :150 level:2 MSTP-176# level Maintenance level. The level range is from 0 to 7. vlan VLAN range. The VLAN range is from 1 to 4093. domain_name Name of the maintenance domain.C-36 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet cfm maintenance-points show ethernet cfm maintenance-points To display information about remote maintenance point domains, use the show ethernet cfm maintenance-points remote in privileged EXEC mode. show ethernet cfm maintenance-points remote [domain domain_name] [service vlan]] Syntax Description Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to display information about remote maintenance point domains: MSTP-176# show ethernet cfm maintenance-points remote domain test_domain service 6 Maintenance Domain Name: test_domain level:6 Domain Name: ma6 VlanId:6 MPId:34 Remote MAC: 22:22:22:22:31:34 Incoming Port:21 ccLifeTime: 3500 ageOfLastCC: 266 MSTP-176# domain_name Name of the maintenance domain. vlan VLAN range. The VLAN range is from 1 to 4093.C-37 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet cfm mpdb show ethernet cfm mpdb To display the output of the Ethernet CFM MIP database, use the show ethernet cfm mpdb command in privileged EXEC mode. show ethernet cfm mpdb [level level] [service vlan] Syntax Description Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to displays the output of the CFM MIP database: MSTP-176# show ethernet cfm mpdb level 6 service 6 Level: 6 VlanId:6 MPId:34 Remote MAC: 22:22:22:22:31:34 Ingress Port:21 archiveTimer: 6003500 MSTP-176# level Maintenance level. The level range is from 0 to 7. vlan VLAN range. The VLAN range is from 1 to 4093.C-38 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show ethernet cfm statistics show ethernet cfm statistics To display the CFM statistics, use the show ethernet cfm statistics command in privileged EXEC mode. show ethernet cfm statistics [domain domain_name] [service vlan] Syntax Description Command Default None Command Modes Privileged EXEC (#) Examples The following example shows how to display the CFM statistics: MSTP-176# show ethernet cfm statistics domain test_domain service 6 Domain Name: test_domain VlanId:6 mpId:6 Ccm transmitted:70268 ccmRececived: 583 ccRecvSeqErr: 1 Lt Unexpected recv:0 lbr transmitted: 0 lbr rcvd in order: 0 Lbr Recvd Seq Error:0 lbr rcvd bad msdu: 0 MSTP-176# domain_name Name of the maintenance domain. vlan VLAN range. The VLAN range is from 1 to 4093.C-39 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show interfaces rep show interfaces rep To display REP configuration and status for a specific interface or for all interfaces, use the show interfaces rep command in privileged EXEC mode. show interfaces [interface_name] rep [detail] Syntax Description Command Default None Command Modes Privileged EXEC (#) Examples The following is a sample output for the show interfaces rep command: MSTP-176# show interfaces rep detail Phy1 REP enabled Segment-id: 2 (Preferred) PortID: 00000019076cb77a Preferred flag: Yes Operational Link Status: NO_NEIGHBOR Current Key: 00000019076cb77a5bdd Port Role: Fail No Ext Neighbor Blocked VLAN: 1-4094 Rcvd VLAN: Admin-svlan: 0 Admin-cvlan: 0 Preempt Delay Timer: disabled LSL Ageout Timer: 5000 ms VLAN load balancing: disabled STCN Propagate to: none LSL PDU rx: 0, tx: 102 HFL PDU rx: 0, tx: 0 BPA TLV rx: 0, tx: 0 BPA (STCN, LSL) TLV rx: 0, tx: 0 BPA (STCN, HFL) TLV rx: 0, tx: 0 EPA-ELECTION TLV rx: 0, tx: 0 EPA-COMMAND TLV rx: 0, tx: 0 EPA-INFO TLV rx: 0, tx: 0 MSTP-176# interface_name REP configuration and status for a specific physical interface or port channel ID. detail Displays detailed REP configuration and status information.C-40 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference show rep topology show rep topology To display REP topology information for a segment or for all the segments (including the primary and secondary edge ports in the segment), use the show rep topology command in privileged EXEC mode. show rep topology [segment id] [archive] [detail] Syntax Description Command Default None Command Modes Privileged EXEC (#) Usage Guidelines The archive keyword is useful for troubleshooting a link failure. Examples The following is a sample output for the show rep topologycommand: MSTP-176# show rep topology BridgeName PortName Edge Role ------------------- ---------- ---- ---- 10.64.106.37-s1 Phy1 FailNoNbr MSTP-176# segment id Displays the REP topology information for a specific segment. The ID range is from 1 to 1024. archive Displays the previous topology of the segment. detail Displays detailed REP topology information.C-41 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference interface channel-group interface channel-group To create a channel group on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, use the interface channel-group command in global configuration mode. interface channel-group chanlgrp-num Syntax Description Command Default No channel groups are created. Command Modes Global Configuration (config) Examples The following example shows how to create a channel group with id 7: MSTP-176(config)# interface channel-group 7 chanlgrp-num ID of the channel group. The channel group range is as follows: • 1 to 11 on the GE_XP and GE_XPE cards. • 1 to 2 on the 10GE_XP and 10GE_XPE cards.C-42 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet cfm ieee ethernet cfm ieee To enable CFM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, use the ethernet cfm ieee command in global configuration mode. To disable CFM on the card, use the no form of this command. ethernet cfm ieee [no] ethernet cfm ieee Syntax Description This command has no arguments or keywords. Command Default None Command Modes Global configuration (config) Examples The following example shows how to enable CFM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards: MSTP-176# ethernet cfm ieeeC-43 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet cfm domain ethernet cfm domain To create a maintenance domain, use the ethernet cfm domain in global configuration mode. ethernet cfm domain domain_name level level [no] ethernet cfm domain domain_name level level Syntax Description Command Default No maintenance domain is created. Command Modes Global configuration (config) Examples The following example shows how to create a maintenance domain with level 4: MSTP-176# ethernet cfm domain test_domain level 4 domain_name level Name of the maintenance domain Maintenance level. The level range is from 0 to 7C-44 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet cfm service ethernet cfm service To attach the maintenance association to a maintenance domain, use the ethernet cfm service command in global configuration mode. ethernet cfm service service_name vlan vlan [no] ethernet cfm service service_name vlan vlan Syntax Description Command Modes Global configuration (config) Examples The following example shows how to attach a maintenance association to a maintenance domain: MSTP-176# ethernet cfm service service name vlan 100 service_name Name of the service identified by the maintenance association. vlan VLAN range. The VLAN range is from 1 to 4093.C-45 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference rep admin svlan rep admin svlan To configure the REP administrative VLAN to transmit hardware flood layer (HFL) messages, use the rep admin svlan command in global configuration mode. To return to the default configuration with VLAN 1 as the administrative VLAN, use the no form of this command. rep admin svlan svlanid no rep admin svlan Syntax Description Command Default The default administrative VLAN is VLAN 1. Command Modes Global configuration (config) Usage Guidelines If the REP administrative VLAN is not configured, the default is VLAN 1. There can be only one administrative VLAN on a switch and on a segment. Examples The following example shows how to configure the REP administrative VLAN: MSTP-176(config)# rep admin svlan 4000 svlanid SVLAN identifier. The SVLAN range is from 1 to 4093.C-46 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference mac-address-table learning vlan vlanid mac-address-table learning vlan vlanid Use the mac-address-table learning vlan global configuration command to enable MAC address learning on a VLAN. Use the no form of this command to disable MAC address learning on a VLAN to control which VLANs can learn MAC addresses. mac-address-table learning vlan vlanid no mac-address-table learning vlan Syntax Description Command Modes Global configuration Command Default By default, MAC address learning is disabled on all VLANs. Usage Guidelines Customers in a service provider network can tunnel a large number of MAC addresses through the network and fill the available MAC address table space. When you control MAC address learning on a VLAN, you can manage the available MAC address table space by controlling which VLANs, and therefore which ports, can learn MAC addresses. Examples An example to enable MAC address learning on VLAN 10 is shown: MSTP-176# mac-address-table learning vlan 10 MSTP-176# vlanid VLAN ID range is 1 to 4093.C-47 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference [no] mac-address-table learning interface type port [no] mac-address-table learning interface type port Use the mac-address-table learning interface type port global configuration command to specify interface based learning of MAC addresses. Syntax Description Command Modes Global configuration Command Default None Usage Guidelines None Examples This example shows how to enable MAC-address learning on an interface: MSTP-176# mac-address-table learning interface gig 1 MSTP-176# type/port Interface type, and the port number. C-48 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference [no] vlan vlan-id [no] vlan vlan-id To add a VLAN and enter config-VLAN submode, use the vlan command. Use the no form of this command to delete the VLAN. vlan vlan-id Syntax Description Command Modes Global configuration Command Default None Usage Guidelines None Examples This example shows how to add a new VLAN and to enter config-VLAN submode: MSTP-176# (config)# vlan 2 MSTP-176# (config-vlan)# vlan-id VLAN ID.C-49 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference interface gigabitethernet port interface gigabitethernet port To enter gigabit ethernet (GigE) interface configuration, use the interface gigabitethernet command in the appropriate configuration mode. interface gigabitethernet port Syntax Description Command Modes Global configuration Command Default Usage Guidelines Examples This example shows how to enter Gigabit Ethernet interface on port 2: MSTP-176(config)# interface gigabitethernet 2 MSTP-176(config-if)# port Enter port number 1-20.C-50 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference interface tengigabitethernet port interface tengigabitethernet port To enter ten gigabit ethernet (10 GigE) interface configuration, use the interface tengigabitethernet command in the appropriate configuration mode. interface tengigabitethernet port Syntax Description Command Modes Global configuration Command Default Usage Guidelines Examples This example shows how to enter 10GigE interface on port 21: MSTP-176(config)# interface tengigabitethernet 21 MSTP-176(config-if)# port Enter port number 21-22.C-51 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference policy-map name policy-map name To configure the Quality of Service (QoS) policy map, use the policy-map command. Use the no form of this command to delete a policy map. policy-map name [no] policy-map name Syntax Description Command Modes Global configuration Command Default None Usage Guidelines None Examples This example shows how to create a QoS policy for ingress traffic on an interface command: MSTP-176(config)# policy map pmap MSTP-176(config-pmap)# police cir percent 60 pir percent 80 bc 4 be 16 MSTP-176(config-pmap)# set cos 8 MSTP-176(config-pmap)# service-policy input servpol1 MSTP-176# end name Policy map name.C-52 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference [no] mvr [no] mvr Use the mvr global configuration command to enable the multicast VLAN registration (MVR) feature on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE. Use the [no] mvr form of this command to disable MVR and its options. mvr group ip-address vlan vlan-id [no] mvr group ip-address vlan vlan-id Command Modes Global Configuration Command Default MVR is disabled by default. Usage Guidelines A maximum of 256 MVR multicast groups can be configured on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE. MVR can be enabled only after the multi-group address and VLAN are configured. Examples This example shows how to configure 228.1.23.4 as an IP multicast address: MSTP-176(config)# mvr group 228.1.23.4 This example shows how to set VLAN 2 as the multicast VLAN: MSTP-176(config)# mvr vlan 2 This example shows how to enable MVR: MSTP-176(config)# mvr This example shows how to disable MVR: MSTP-176(config)# no mvrC-53 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference mvr vlan mvr vlan To specify the VLAN (SVLAN) to act as a multicast VLAN, use the mvr vlan command. All ports must belong to this VLAN. mvr vlan svlan Syntax Description Command Modes Global Configuration Command Default By default MVR is disabled on a SVLAN. Usage Guidelines None Examples This example shows how to set a VLAN to act as the multicast VLAN: MSTP-176(config)# mvr vlan 22 svlan SVLAN ID.C-54 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference mvr group ip address count mvr group ip address count To configure an IP multicast address on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card, use the count parameter to configure a contiguous series of MVR group addresses. Any multicast data sent to this address is sent to all source ports on the switch and all receiver ports that have elected to receive data on that multicast address. Each multicast address would correspond to one television channel. mvr group ip address count Syntax Description Command Modes Global Configuration (config) Command Default By default MVR is disabled on a SVLAN. Examples The following example shows how to configure two contiguous MVR address groups: MSTP-176(config)# mvr group 228.1.23.4 2 count The range for count is 1 to 256.C-55 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet cfm cc_interval interval ethernet cfm cc_interval interval To configure the value of the Continuity Check timer (CC timer), use the ethernet cfm cc_interval command in CFM maintenance association configuration mode. ethernet cfm cc_interval interval [no] ethernet cfm cc_interval interval Syntax Description Command Default The default configuration is 1 second. Command Modes CFM Maintenance Association configuration (config-ecfm-srv) Examples The following example shows how to set the value of the CC timer to 10 seconds: MSTP-176(config-ecfm-srv)# ethernet cfm cc_interval 10s interval Continuity Check timer interval. The interval values are 1 second, 10 seconds, and 1 minute.C-56 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference service service_name service service_name To configure the service name for the maintenance association, use the service service_name command in CFM maintenance association configuration mode. service service_name Syntax Description Command Modes CFM Maintenance Association configuration (config-ecfm-srv) Examples The following example shows how to configure a CFM service: MSTP-176(config-ecfm-srv)# service service name service_name Service name of the maintenance association.C-57 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference continuity-check continuity-check To enable the CC timer for the maintenance association profile, use the continuity-check command in CFM maintenance association configuration mode. To disable the CC timer for the maintenance association profile, use the no form of this command. continuity-check [no] continuity-check Syntax Description This command has no arguments or keywords. Command Default Continuity check is disabled by default. Command Modes CFM Maintenance Association configuration (config-ecfm-srv) Examples The following example shows how to enable the CC timer for the maintenance association profile: MSTP-176(config-ecfm-srv)# continuity-checkC-58 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference name vlan name name vlan name To configure the VLAN, use the name vlan name command in VLAN interface configuration mode. name vlan name Syntax Description Command Modes VLAN interface configuration Command Default By default, no name is assigned to a VLAN. Usage Guidelines Names with blank spaces can be provided by enclosing the name within double quotes. Examples The following example shows how to set the VLAN name: MSTP-176(config-vlan)# name MYVLAN name Specify the name of the VLAN.C-59 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference protected protected To enables or disable Fast Automatic Protection Switching (FAPS) on the specified SVLAN, use the protected command. protected [no] protected Syntax Description This command has no arguments or keywords. Command Modes VLAN interface configuration Command Default By default, FAPS is disabled on all SVLANs. Examples The following example shows how to configure the card for protection: MSTP-176(config-vlan)# protectedC-60 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ip igmp snooping ip igmp snooping To enable IGMP snooping, use the ip igmp snooping command. Use the no form of this command to disable IGMP snooping. ip igmp snooping no ip igmp snooping Syntax Description This command has no arguments or keywords. Command Default By default, IGMP snooping is disabled on all SVLANs. Command Modes VLAN interface configuration Usage Guidelines Before you can enable IGMP snooping configure the VLAN interface for multicast routing. Examples This example shows how to enable IGMP snooping: MSTP-176(config-vlan)# ip igmp snooping MSTP-176(config-vlan)# C-61 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ip igmp snooping immediate-leave ip igmp snooping immediate-leave To enable IGMPv2 snooping immediate-leave processing on all existing VLAN interfaces, use the ip igmp snooping immediate-leave command. Use the no form of this command to disable immediate-leave processing. ip igmp snooping immediate-leave no ip igmp snooping immediate-leave Syntax Description This command has no arguments or keywords. Defaults By default, IGMP snooping immediate leave is disabled on all SVLANs. Command Modes VLAN interface configuration Usage Guidelines The immediate-leave feature is supported only with IGMP version 2. Examples This example shows how to enable IGMP immediate-leave processing: MSTP-176(config-vlan)# ip igmp snooping immediate-leave MSTP-176(config-vlan)# C-62 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ip igmp snooping report-suppression ip igmp snooping report-suppression To enable report suppression, use the ip igmp snooping report-suppression command. Use the no form of this command to disable report suppression and forward the reports to the multicast devices. ip igmp snooping report-suppression no igmp snooping report-suppression Syntax Description This command has no arguments or keywords. Defaults By default, IGMP snooping report-suppression is disabled on all SVLANs. Command Modes VLAN interface configuration Examples This example shows how to enable report suppression: MSTP-176(config-vlan)# ip igmp snooping report-suppression MSTP-176(config-vlan)# This example shows how to disable report suppression: MSTP-176(config-vlan)# )# no ip igmp snooping report-suppression MSTP-176(config-vlan)# C-63 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference channel-group channel-number mode chanlgrp-mode channel-group channel-number mode chanlgrp-mode To configure the mode for the channel group on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, use the channel-group channel-number mode chanlgrp-mode command in interface configuration mode. To set the channel group mode to active, use the no form of this command. channel-group channel-number mode chanlgrp-mode [no] channel-group channel-number mode chanlgrp-mode Syntax Description Command Default The channel group mode is set to active. Command Modes Interface Configuration (config-if) Examples The following example shows how to change the channel group mode to passive: MSTP-176(config-if)# channel-group 6 mode passive channel-number Number of the channel group. chanlgrp-mode Mode of the channel group. The channel group mode values are active, passive, and manual.C-64 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference channel-group channel-number hash chanlgrp-hash channel-group channel-number hash chanlgrp-hash To configure the hashing algorithm for the channel group on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, use the channel-group channel-number hash chanlgrp-hash command in interface configuration mode. channel-group channel-number hash chanlgrp-hash [no] channel-group channel-number hash chanlgrp-hash Syntax Description Command Default The hashing algorithm is set to to sa-da-incoming. Command Modes Interface Configuration (config-if) Examples The following example shows how to change the hashing algorithm for the channel group mode to src-ip-tcp-udp: MSTP-176(config-if)# channel-group 2 hash src-ip-tcp-udp channel-number Number of the channel group. chanlgrp-hash Hashing algorithm for the channel group. The channel group hash values are sa-incoming, da-incoming, sa-da-incoming, src-ip-tcp-udp, dst-ip-tcp-udp, and src-dst-ip-tcp-udp.C-65 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference channel-group channel-number expected speed chanlgrp-speed channel-group channel-number expected speed chanlgrp-speed To change the expected speed of the channel group on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, use the channel-group channel-number expected speed chanlgrp-speed command in interface configuration mode. channel-group channel-number expected speed chanlgrp-speed [no] channel-group channel-number expected speed chanlgrp-speed Syntax Description Command Default The default expected speed is 1000. Command Modes Interface Configuration (config-if) Examples The following example shows how to change the expected speed for the channel group to 100: MSTP-176(config-if)# channel-group 2 expected speed 100 channel-number Number of the channel group. chanlgrp-speed Expected speed of the channel group. The channel group speed values are 10, 100, and 1000.C-66 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference description description description description To specify the port name, use the description command in interface configuration mode. description Syntax Description Command Modes Interface configuration Usage Guidelines To view the ports on an interface, use the show interfaces command in privileged EXEC mode. Examples This example shows how to specify a port name: MSTP-176(config-if)# description 5p The following partial sample output displays the port name that was set: MSTP-176# show interface Port 2 (Client), Port name: 5p Admin State: ADMIN_OOS_DSBLD, Service State: OOS_MA_DSBLD Reach: REACH_UNKNOWN, Wavelength: WV_UNKNOWN, AIS Action: NONE Flow Control: DISABLED, Duplex Mode: FULL, Speed: SPEED_AUTO, MTU: 9700 NI Mode: UNI, MAC Learning: DISABLED, IGMP Static Router Port: DISABLED Ingress CoS: 0, Ethertype Inner/Outer: 8100/8100, Egress QoS: DISABLED Committed Info Rate: 100, Burst Size Committed/Excess: BCKT_4K/BCKT_4K Failed to get PM counters for this port MSTP-176# description Port name can be a maximum of 32 charactersC-67 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam ethernet oam To enable EFM on an interface, use the ethernet oam command in interface configuration mode. To disable EFM on an interface, use the no form of this command. ethernet oam [no] ethernet oam Syntax Description This command has no arguments or keywords. Command Default EFM is disabled by default. Command Modes Interface Configuration (config-if) Usage Guidelines When EFM is configured on an interface, the default mode of the EFM client is active. When the EFM mode is enabled on two interfaces passing traffic, both interfaces cannot be in passive mode. Both interfaces can be in active mode, and one can be in active mode and the other in passive mode. Examples The following example shows how to enable EFM on an interface: MSTP-176(config-if)# ethernet oamC-68 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam mode ethernet oammode To configure the EFM mode (active or passive) and the timeout parameter, use the ethernet oam command in interface configuration mode. To return to the default configuration, use the no form of this command. ethernet oam [mode {active | passive} | timeout seconds] [no] ethernet oam [mode {active | passive} | timeout seconds] Syntax Description Command Default EFM mode is active by default. Command Modes Interface Configuration (config-if) Usage Guidelines When EFM is configured on an interface, the default mode of the EFM client is active. When the EFM mode is enabled on two interfaces passing traffic, both interfaces cannot be in passive mode. Both interfaces can be in active mode, and one can be in active mode and the other in passive mode. Examples The following example shows how to set the EFM mode as passive with 25 seconds as timeout period: MSTP-176(config-if)# ethernet oam mode passive timeout 25 mode Sets the EFM client mode. active Sets the EFM client mode to active after the interface was previously placed in passive mode. The default mode is active. passive Sets the EFM client mode to passive. In passive mode, a device cannot initiate discovery, inquire about variables, or set loopback mode. timeout Specifies the amount of time, in seconds, after which a device declares its EFM peer to be nonoperational and resets its state machine. seconds Number of seconds of the timeout period. The range is from 2 to 30 seconds. The default is 5.C-69 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam link-monitor frame ethernet oam link-monitor frame To configure an error frame threshold or window on an EFM interface, use the ethernet oam link-monitor frame command in interface configuration mode. To remove the error frame threshold or window, use the no form of this command. ethernet oam link-monitor frame {threshold {high {none| high frames} | low {low frames}} | window milliseconds} [no] ethernet oam link-monitor frame {threshold {high {none| high frames} | low {low frames}} | window milliseconds} Syntax Description Command Default The ethernet oam link-monitor frame command is not configured. Command Modes Interface Configuration (config-if) Usage Guidelines The ethernet oam link-monitor frame command configures a number of error frames that triggers an action or a period of time in which error frames are counted. Examples The following example shows how to configure an EFM link-monitor frame window of 300 milliseconds: MSTP-176(config-if)# ethernet oam link-monitor frame window 300 threshold Sets the number of error frames at, above, or below which an action is triggered. high Sets a high error frame threshold in number of frames. High threshold must be greater than the low threshold. none Disables a high threshold. high-frames Integer in the range of 1 to 65535 that sets the high threshold in number of frames. There is no default. The high threshold must be configured. low Sets a low error frame threshold in number of frames. low-frames Integer in the range of 0 to 65535 that sets the low threshold in number of frames. The default is 1. window Sets a window and period of time during which error frames are counted. milliseconds Integer in the range of 10 to 600 that represents milliseconds in multiples of 100. The default is 10.C-70 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam link-monitor frame-period ethernet oam link-monitor frame-period To configure an error frame period on an EFM interface, use the ethernet oam link-monitor frame-period command in interface configuration mode. To remove the error frame period, use the no form of this command. ethernet oam link-monitor frame-period {threshold {high {none| high-frames} | low {low-frames}} | window frames} [no] ethernet oam link-monitor frame-period {threshold {high {none| high-frames} | low {low-frames}} | window frames} Syntax Description Command Default The ethernet oam link-monitor frame-period command is not configured. Command Modes Interface Configuration (config-if) Usage Guidelines The ethernet oam link-monitor frame-period command configures an error frame period in number of frames. When a high threshold is configured, it must be at least as same as the low threshold for frame errors. Examples The following example shows how to configure an EFM link-monitor frame-period window of 20000 frames: MSTP-176(config-if)# ethernet oam link-monitor frame-period window 2 The following example shows how to configure an EFM link-monitor frame-period low threshold of 500 frames: MSTP-176(config-if)# ethernet oam link-monitor frame-period threshold low 500 threshold Sets the number of error frames for the period at, above, or below which an action is triggered. high Sets a high threshold for the error frame period in number of frames. none Disables a high threshold. high-frames Integer in the range of 1 to 65535 that sets the high threshold in number of frames. There is no default. The high threshold must be configured. low Sets a low error frame threshold for the error frame period in number of frames. low-frames Integer in the range of 0 to 65535 that sets the low threshold in number of frames. The default is 1. window Sets a window and period of time during which error frames are counted. frames Integer in the range of 1 to 65535 that sets the window size in number of frames. Each value is a multiple of 10000. The default is 1000.C-71 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam link-monitor frame-seconds ethernet oam link-monitor frame-seconds To configure the frame-seconds period on an EFM interface, use the ethernet oam link-monitor frame-seconds command in interface configuration mode. To remove the frame-seconds period, use the no form of this command. ethernet oam link-monitor frame-seconds {threshold {high {none| high-frames} | low {low-frames}} | window milliseconds} [no] ethernet oam link-monitor frame-seconds {threshold {high {none| high-frames} | low {low-frames}} | window milliseconds} Syntax Description Command Default The ethernet oam link-monitor frame-seconds command is not configured. Command Modes Interface Configuration (config-if) Usage Guidelines The ethernet oam link-monitor frame-seconds command configures a number of error frames that triggers an action or a period of time in which error frames are counted. Examples The following example shows how to configure an EFM link-monitor frame-seconds window of 30000 milliseconds (30 seconds): MSTP-176(config-if)# ethernet oam link-monitor frame-seconds window 300 threshold Sets a number at, above, or below which an action is triggered. high Sets a high error frame-seconds threshold in number of seconds. none Disables a high threshold. high-frames Integer in the range of 1 to 900 that sets the high threshold in number of frames. There is no default. The high threshold must be configured. low Sets a low error frame-seconds threshold in number of seconds. low-frames Integer in the range of 0 to 900 that sets the low threshold in number of frames. The default is 1. window Sets a window and period of time during which error frames are counted. milliseconds Integer in the range of 100 to 9000 that represents a number of milliseconds in multiples of 100. The default is 100.C-72 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam link-monitor high-threshold ethernet oamlink-monitor high-threshold To configure a specific action to occur when a high threshold for an error is exceeded on an EFM interface, use the ethernet oam link-monitor high-threshold command in interface configuration mode. To remove the high-threshold action, use the no form of this command. ethernet oam link-monitor high-threshold action {none|disable-port} [no] ethernet oam link-monitor high-threshold action {none|disable-port} Syntax Description Command Default A high-threshold action is not configured. Command Modes Interface Configuration (config-if) Examples The following example shows how to configure the disable-port action to occur when the high threshold for an error is exceeded: MSTP-176(config-if)# ethernet oam link-monitor high-threshold action disable-port action Specifies the action taken when the high threshold for an error is exceeded. none Specifies that no action is taken. disable-port Performs an error-disable function on the interface.C-73 Cisco ONS 15454 DWDM Reference Manual, Release 9.2 78-19285-02 Appendix C Pseudo Command Line Interface Reference ethernet oam remote-failure link-fault ethernet oam remote-failure link-fault To configure the EFM Remote Failure Indication (RFI), use the ethernet oam remote-failure link-fault command in interface configuration mode. To remove the configuration, use the no form of this command. ethernet oam remote-failure link-fault action error-block-interface [no] ethernet oam remote-failure link-fault action error-block-interface Syntax Description Command Default The remote failure action is not configured. Command Modes Interface Configuration (config-if)