|
|
Release Notes address closed issues, caveats, and new features for the Cisco ONS 15200 Maintenance Manager (MM) software. For detailed information regarding features, capabilities, and software introduced with this maintenance 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/15200/15200rnt/index.htm
December, 2002
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.
This document is intended as a stand-alone document for those customers that only use MM for system management.
The following new features and functionality have been added to the ONS 15200 MM Software Release 1.1(3).
This section describes the new software features implemented in this maintenance release.
The Element ID has been replaced with the CLIP name to improve event log information.
Only the root cause of a fault is reported, subsequent fault(s) will be suppressed and displayed with normal, if read by the user.
Performance monitoring is not implemented in the Maintenance Manager. This will not be implemented in any future release.
The global alarms MM interface page now provides links to alarming CLIPs.
The main path view MM interface page now provides active path information.
The ping level broadcast depth, the logical distance from the maintenance manager access point in the system to the managed clips, is settable to one or two at launch of the software.
Setting the ping level to one means that only the CAN bus to which MM is connected can be observed and managed. Setting the ping level to two means that in addition, all clips with QPP paired to any of the clips on this CAN bus are accessible.
If used in intermediate nodes in systems with FDI switching, ping level has to be set to one. If not, it will interfere with the FDI function. It is recommended that ping level one be used.
A new overview exists in MM 1.1(3), where the optical power levels of all managed clips are presented. This is similar to the new view in the web browser interface.
The data rate of clips is now a settable parameter from MM. It can be set on both the clip and path levels.
This section describes ONS 15200 limitations and restrictions in systems only managed by MM.
Due to limited bandwidth in the internal data communication network, the 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). The new feature Settable Ping Level, has minimized this restriction.
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 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 is not implemented in the Maintenance Manager. This will not be implemented in any future release.
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.
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 may be resolved in a future release.
Component: MM software
Detail: The MM interface does not clear alarms even though the value is between lwt and hwt.
Workaround: Perform an upload.
Resolution: This issue may be resolved in a future release.
Component: Software documentation
Detail: When turning up a path between two CLIPs, it is possible that the clients may not be able to communicate with each other because of datarate mismatch.
Workaround: If you wish to change the CLIP datarate, always start with the CLIP that is the farthest away from the NCB.
It is preferable to remove the client input signal before changing data rate or to change the datarate on a path level rather than a CLIP level.
Resolution: This note will be added to the documentation in a future revision.
Component: NEC firmware
Detail: Some pairs of clips show toggling QPP alarms if the signal between them is Gigabit Ethernet, but
datarate is set to STM-16/OC-48 in the management interface (CLI). When the expected datarate is set incorrectly, the clock and data recovery function will not work. It will transmit noise, which will modulate the DWDM signal and thus disturb the QPP signal directly.
Workaround: Be sure to always set the datarate correctly.
Resolution: None.
Component: NEC firmware
Detail: Alarms are not cleared in WEB and CLI for values that are around 1.5 dB from thresholds in normal operating range. To avoid flickering alarms, threshold hysteresis is implemented. The present value is fluctuating above and below the threshold during the time of the hysteresis, 2 seconds.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: NEC firmware
Detail: The ONS 15200 system uses in-band signaling (QPP) for management communication. A protected CLIP transmits identical signals on both the alternative connections, including QPP. QPP is terminated/re-transmitted in each node, including the regenerator nodes. Unfortunately the QPP protocol definition does not currently include information, identifying to which of the alternative paths a message was addressed. Thus there is a possible addressing conflict. A further problem is that a protected CLIP assumes that it receives identical QPP messages on both the incoming QPP links, which is not the case when there are regenerating CLIPs along the alternative paths. The CLIP will randomly pick packets from either of the incoming links. Due to the above described problems it is not currently possible to manage a network with regeneration in protected paths.
Workaround: None in SNM 1.1(1). In 1.1(2) it is possible to set pinglevel to one, thereby limiting management to one CAN bus. An NCB is required in each node.
Resolution: This issue will be resolved in a future release.
Component: Clip-board
Detail: No CLEI label on clip front. All current clips are affected.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM-software
Detail: When an inhibit on a parameter is set, an alarm will be sent to all snms that are either primary or secondary and to the maintenance subscriber from the nec. When the reverse command no inhibit (CLI) or uninhibit (web) is given, only the interface from which the command was issued will change value. The other management interfaces (CLI, web) are unaffected.
Thus, uninhibit will not reach a second SNM if set from an SNM nor will uninhibit reach an SNM if set from MM.
Workaround: None.
Resolution: This issue will be resolved in a future release.
Component: SNM software
Detail: Several NCBs can be configured (configure snm snm_xxxxx) with identical unit ID. No check or negotiation is done by the SNM software to verify that the unit ID is not already used.
Workaround: Make sure each unit ID is only used once.
Resolution: This issue will be resolved in a future release.
Component: MM software
Detail: No throughput from the client side of the ONS 15200 system. The data rate of the two clips constituting a channel have been set to different data rates. This makes data transfer between the two client ports impossible. No alarm is given in maintenance manager, neither red nor yellow, on any level (global, path level, or clip level). This always occurs when the data rates on the two paired clips of a channel are not matched.
Workaround: The only workaround is to make sure the data rates are matched.
Resolution: This issue is not scheduled to be resolved in a future release.
Component: MM software
Detail: When an SNM/NCB that is inserted in an MCU and has been registered by MM 1.1(3) is removed from the MCU physically, no alarm is generated in MM. This is unlike the situation when a CLIP is pulled in a similar fashion and the alarm "equipment missing" is received if the CLIP parameter "inuse" is set to yes.
When the SNM/NCB hasn't replied to ping requests from MM in a predetermined time, the SNM/NCB is removed from the database in MM.
Workaround: Do not remove SNM/NCB when using MM. It is intended primarily for SCU usage in the field and should be feasible in most cases.
Resolution: This issue will be resolved in a future release.
Component: MM software
Detail: When a clip configuration is made from an SNM, the change will no transfer to a running MM. To update MM, you need to ask for an update or restart MM.
Workaround: None.
Resolution: This issue will not be resolved in a future release.
Component: MM software
Detail: It is not possible to set the data rate on a path via MM.
Workaround: Set the data rate on both clips.
Resolution: This issue is resolved in release 1.1(3).
Component: MM software
Detail: When an alarm is generated a yellow or red mark should appear in front of the overall event log and alarm.
Workaround: None.
Resolution: This issue is resolved in release 1.1(3).
Component: MM software
Detail: MM displays the QPPA/QPPB alarm with red alarm indicator under clip alarm and global alarm. A minor, yellow alarm indicator should be displayed.
Workaround: None.
Resolution: This issue is resolved in release 1.1(3).
Component: MM software
Detail: MM displays the FDI alarm with a red alarm indicator under clip alarm and global alarm. A minor, yellow alarm indicator should be displayed.
Workaround: None.
Resolution: This issue is resolved in release 1.1(3).
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. To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study 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, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, 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. (0203R)
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Dec 10 08:35:47 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.