|
|
Release Notes address closed issues, caveats, and new features for the Cisco ONS 15200. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to the documents listed in the "Related Documentation" section. For the most current version of the Release Notes for Cisco ONS 15200 Release 1.1, visit the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/ong/ons_200/ons15200/200relnt
December, 2001
New Features and Functionality
Obtaining Technical Assistance
This section documents changes that have been added to the Release Notes for Cisco ONS 15200 Release 1.1 since the production of the Cisco ONS 15200 System Software CD for Release 1.1.
There are no changes to the release notes.
The following new features and functionality have been added to the ONS 15200 Release 1.1 hardware and software.
Specification: Client Line Interface Port (CLIP) 3.5— 0 dBm; 3000 ps/nm dispersion tolerance, 2R/3R
This CLIP features a single transponder pair for all protocols, including SONET, SDH, Gigabit Ethernet, Fast Ethernet, ESCON, FICON, and Fiber Channel.
The distinction between protected and unprotected CLIPs is now removed for CLIP 3.5. This clip is defined in the software as either protected or unprotected. This reduces the number of CLIPs needed.
Each CLIP can now be controlled by one or two Network Control Boards (NCBs), enabling NCB redundancy.
The software now enables storage of Performance Monitoring (PM) data in the SNM. PMs are presented as a graph or table in the HTTP interface. You can also extract PM values to an external analysis program, such as a spreadsheet application.
Switching on FDI can now be enabled or disabled. This allows for automatic protection switching with FDI as a second optional switch criterion in addition to optical power.
The web browser now allows input. Web-administrator privileges correspond to those for the CLI-administrator.
SNTP support enables synchronization of the local time on the NCB with the SNTP-server time, adding clock precision.
Metro Planner is updated to reflect the new features in Release 1.1, including interoperability with Cisco ONS 15454 and 15216.
This section describes ONS 15200 system limitations.
Due to limited bandwidth in the internal data communication network, the Maintenance Manager (MM) is currently configured to manage only the CLIP modules on the local control area network (CAN) bus and CLIP modules connected directly to the local CLIP modules by QPP (i.e., a maximum distance of 1 CAN hop + 1 QPP hop).
Restrictions on running multiple MM sessions in a subnetwork apply because the last MM session started will, by default, tell all CLIP modules within its "realm" (one CAN + one QPP) that the latest MM session receives all alarm subscriptions (as a maintenance subscriber). Because there is only one maintenance subscriber allowed, the old one becomes an ex-subscriber.
The MCU has been tested for compliance to New Equipment Building System (NEBS) level 3. Both ONS 15252 and ONS 15201 have passed environmental testing that complies with European Telecommunications Standards Institute (ETSI) and all NEBS level 2 requirements. A complete report summarizing the results of these tests, performed by the Swedish environmental lab, SEMKO, also exists.
The simple network management protocol (SNMP) interface is read-only. This will be amended in the next main release of the ONS 15200 management software.
The alarm cut-off button on the Communication Interface Module (CIM) board currently has no function because the supporting software has not yet been implemented.
Performance monitoring can only be enabled for ten CLIPs simultaneously. The current PM state is stored on the CLIP and is automatically detected by the subnetwork manager when the CLIP is found. Performance monitoring will only work for the first ten clips found with the PM state set to "on."
The ONS 15200 only allows 8 simultaneous telnet sessions.
The ONS 15200 only allows 8 simultaneous FTP sessions.
Review the notes listed below before deploying the ONS 15200. Caveats with DDTS bug tracking numbers are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without DDTS bug tracking numbers are provided to point out procedural or situational considerations when deploying the product.
Detail: If you issue the command "commit network" in CLI while a user is simultaneously logged on via the web interface, the HTTP functionality of the NCB/SNM becomes disabled until the NCB is rebooted.
Workaround: Reboot the NCB.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: After you have configured a unit ID to SNM_1 or SNM_2, it is not possible to set the SNM back to "offline" mode ("-").
Workaround: FTP to the NCB and get the file snm.cfg. Open the file and remove the line defining the unit ID. Save the file to the NCB. Reboot the NCB.
Resolution: This issue will be resolved in a future release.
Component: SNM, web interface, command line interface (CLI), SNMP
Detail: CLI and WEB fail to clear alarms, though the present value is between lwt and hwt.
For example:
CLIP_348.dwdm.brxpower:Status Lowalarmvalue -23.2 dbmhat -8.0 dbmhwt -9.9 dbmlwt -28.0 dbmlat -30.0 dbmunit dbmpmvalue <uninitialized>Workaround: Perform an upload.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: When CLIPs are "pinged out," if you are primary or secondary manager of the CLIP, they are presented as not belonging to any SCU or MCU--they become "loose CLIPs."
A CLIP can become pinged out when you remove CIM, when you remove the CLIP from the NCB, or when the SNM/MM loses contact with the CLIP due to CAN or QPP problems.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: Simultaneously occurring QPPA and QPPB alarms are not reported with a severity of Major.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: In CLI, or in the web interface, you can create multiple MCUs or SCUs with the same name. When there are two or more MCUs with the same name, only one of these is configurable from the CLI.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: MM
Detail: MM does not display the current network status, as shown by the CIM alarm LEDs, in the graphical view of an MCU.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM, Web Interface
Detail: After you have clicked the apply button in the web interface password changing page, there is no confirmation that the password has successfully been changed. The web interface does not appear to have processed the command, but in fact the password is changed.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: Changing the MCU or SCU name in CLI or web interface will not automatically update remote NCBs.
Workaround: Reboot the remote NCBs.
Resolution: This issue will be resolved in a future release.
Component: SNM, Web Interface
Detail: The Daylight Savings Time (DLST) guiding format (dd:mm) given in the web interface for setting DLST is incorrect. The correct DLST format is
dd:mm,tt:mmWorkaround: Use CLI to set the DLST.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: When you issue the command "commit network" from the Configure Network level in CLI, then immediately issue the Exit command, and then Show Discrepancy, no inventory is expected to appear. However, some items, such as renamed CLIPs, renamed SNMs and the paths in which they appear, are displayed in the inventory.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: MM
Detail: It is not currently possible to set the data rate for a path via MM.
Workaround: Set the data rate for each CLIP in the path.
Resolution: This issue will be resolved in a future release.
Component: SNM, Web Interface
Detail: The month of October (10) is not accepted as a valid value in the web interface when setting the date and time. When you enter a "10" for the month you will receive an inappropriate error message.
Workaround: Use CLI to set the date and time.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: No records are displayed in the CLI event log when you enter the Read command.
Workaround: Exit the event log (use the Exit command) and open a new event log by typing "open
eventlog." Enter the Read command again.
Resolution: This issue will be resolved in a future release.
Component: SNM, Web Interface, CLI
Detail: When you log into an NCB and configure a CLIP module where the primary manager is set to none and the secondary manager is an NCB that you aren't currently logged into, the CLI and Web Interface erroneously display data.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM, Web Interface, CLI
Detail: The CLI and web interface command default user privilege levels should both be "guest." However, currently the CLI default level is guest, while the web default level is administrator.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM
Detail: When you log in to the NCB with a user name that is already in use, no error message is displayed. Instead, the NCB simply issues a new login-prompt, without explanation.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM, Web Interface, CLI
Detail: Duplicate paths may be displayed by CLI and the web interface. Some paths are found and defined from both ends; for example:
path_506_519path_519_506Workaround: None.
Resolution: This issue will be resolved in a future release.
The NCB board, located in Slot 17 of the MCU, contains two lithium batteries as follows:
These batteries must be replaced only with identical or equivalent batteries, as recommended by the manufacturer. Dispose of used batteries according to the manufacturer's instructions.
 |
Warning Failure to dispose of lithium batteries in accordance with the manufacturer's instructions could result in environmental damage. Failure to replace lithium batteries in accordance with the manufacturer's instructions could result in possible explosion. |
Component: MM, CLI, and Web Browser
Detail: Always change MCU backplane jumpers with the power off.
Component: MM, Web Interface
Detail: No NCB module status, other than the summary LED, is reported to the MM or Web Interface. The NCB module can be seen in the graphics but cannot be accessed.
Workaround: None.
Resolution: This issue is resolved in Release 1.1.
Component: SNM
Detail: New PM and Event log entries delete old entries. The PM and Event logs use a common wraparound memory.
Workaround: None
Resolution: This issue is resolved in Release 1.1.
Component: MM
Detail: No paths are detected in the MM at startup. This issue occurs in about 50% of startups.
Workaround: Restart the MM.
Resolution: This issue is resolved in Release 1.1.
Component: NEC
Detail: When both the "A" Rx power and the "B" Rx power are in the LA state, switchmode = automatic, and either of the two sides are "inhibited," the yellow warning LED is displayed instead of the expected red LED.
The wrong LED also displays for unprotected CLIPs (Rx power LA and "inhibited").
Workaround: None
Resolution: This issue is resolved in Release 1.1.
Component: SNM
Detail: When the Qeyton Database System (QDBS) in the SNM receives the same DCN address from many CLIPs with different serial numbers, the result could be several ghost paths. These ghost paths will remain in the system even after the address conflict is over.
 |
Note Ghost paths are easily recognized because they do not display a channel number. Ghost paths are displayed as clip_(). |
Workaround: Install CLIPs carefully, following the instructions in the manual, to avoid creating ghost paths. If you inadvertently create a ghost path, you can remove it by rebooting the SNM.
Resolution: This issue is resolved in Release 1.1.
Component: CLIP Module
Detail: Two single-channel unit (SCU) CLIP modules can be assigned the same address on the internal CAN bus when they are installed on separate CAN buses. When the buses are connected, these CLIP modules have the same address. This address conflict is not resolved in the current version.
False paths can be created as a consequence of the address conflict. These ghost paths can remain in the system even after the conflict is over.
Workaround: When adding an SCU is added to a CAN bus, connect it to the bus before powering it up. You must power off at least one of the CLIP modules before connecting the CAN buses. The CLIP module can then be restarted.
Component: CLIP Module
Detail: The ONS 15200 jitter transfer function is not compliant with International Telecommunications Union (ITU) recommendation G.958. The requirement for the cut-off frequency (f_c) parameter is 125 kHz for STM-1 and 2 MHz for STM-16.
The ONS 15200 has an f_c equal to 350 kHz and one equal to 5 MHz, respectively.
Resolution: This issue is resolved in Release 1.1.
For additional information on the Cisco ONS 15200, refer to the following documents.
Cisco ONS 15200 Product Description
Cisco ONS 15200 Module Handbook
Cisco ONS 15200 Installation, Setup, and Test Manual
Cisco ONS 15200 Maintenance Manager Installation and Operations Guide
Cisco ONS 15200 Web Interface Software User Manual
Cisco ONS 15200 Command Line Interface Manual
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Optical networking-related documentation, including the Cisco ONS 15200 Release Notes, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM, a member of the Cisco Connection Family, is updated as required. Therefore, it might be more current than printed documentation. To order additional copies of the Optical Networking Product Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www.europe.cisco.com.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the tool bar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. The toll-free Optical Networking Assistance number is 1 877 323-7368.
P1 and P2 level problems are defined as follows:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, FrameShare, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, ScriptBuilder, ScriptShare, SMARTnet, TransPath, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and Discover All That's Possible are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, GigaStack, IOS, IP/TV, LightStream, MICA, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0110R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Dec 10 11:44:31 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.