|
|
This document addresses caveats and known system limitations for Release 1.0 of the Cisco ONS 15200 system.
Obtaining Technical Assistance
Table 1 displays a brief listing of the new software features.
Software | New Feature |
Maintenance Manager Version 1.0 (1) | Initial release |
MetroPlanner Version 1.02 | Initial release |
Sub-Network Manager Version 1.0(1) (Includes Web-based Interface, SNMP, and Command Line Interface.) | Initial release |
This section describes the software caveats known to exist at the time of publication.
This section describes the CSCdt40095 caveat and known workarounds.
Command Line Interface, Maintenance Manager, SNMP, Web-based Interface
Performance monitoring of analog parameters in the system is not implemented according to specification. It is not possible to log data or present logged data. This does not affect the monitoring of traffic performance.
None.
This section describes the CSCdt27012 caveat and known workarounds.
SNMP.
Yellow alarm LED should be displayed for the DC power alarm at the Network Control Board (NCB) module.
None.
This section describes the CSCdt27015 caveat and known workarounds.
Command Line Interface, Maintenance Manager, SNMP, Web-based Interface
When the lower warning threshold (LWT) is set below the lower alarm threshold (LAT) of a threshold-crossing alarm, no alarms will be detected for that signal. Similarly, the higher warning threshold (HWT) must never be set above the higher alarm threshold (HAT).
None. The user must set alarm thresholds in the logical order.
This section describes the CSCdt27007 caveat and known workarounds.
Maintenance Manager, Web-based Interface
No NCB module status, other than the summary LED, is reported to the Maintenance Manager or Web-based Interface. The NCB module can be seen in the graphics, but cannot be reached.
None.
This section describes the CSCdt37672 caveat and known workarounds.
Client Line Interface Port (CLIP) module
When the QDBS gets the same DCN address from many CLIP modules with different serial number and is "generally confused," ghost paths remain in the system even when the address conflict has been resolved.
Ghost paths are easily recognized because they don't display a channel number. Ghost paths are displayed as clip_().
Reboot the NCB module to remove ghost paths as necessary.
This section describes the firmware caveats known to exist at the time of publication.
This section describes the CSCdt38994 caveat and known workarounds.
Client Line Interface Port (CLIP) module
Symptom: The ONS 15200 jitter transfer function is not compliant with ITU recommendation G.958.
Conditions: The requirement for the 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.
This caveat has no impact on the performance of the ONS 15200 system.
None.
This section describes the CSCdt37670 caveat and known workarounds.
Client Line Interface Port (CLIP) module
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 these buses are connected, these CLIP modules have the same address. This address conflict is not resolved in the current version 1.0(1).
Also, 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.
When an SCU is added to a CAN bus, it must be connected to the bus before it is powered up. At least one of the CLIP modules must be powered off before the CAN buses are connected. The CLIP module can then be restarted.
This section describes the ONS 15200 system limitations known to exist at the time of publication.
Due to limited bandwidth of the internal data communication network, the Maintenance Manager is currently configured to manage only the CLIP modules on the local 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).
It is currently not possible to have more than one of Network Control Board (NCB) module in a sub-network, because each NCB module will set itself up as 'primary subscriber'. The NCB module which was inserted last will be the only one receiving alarms, getting system data updated, etc.
There are currently restrictions in running multiple Maintenance Manager sessions in a sub-network. because the last Maintenance Manager session started will, by default, tell all CLIP modules within its "realm" (one CAN + one QPP) that it is to receive all subscriptions of alarms (as maintenance subscriber). Because there is only one maintenance subscriber allowed, the old one becomes an ex-subscriber.
In the current implementation, the MCUs are automatically labeled in the management software. The name is constructed from the sub-rack ID (two bits) read from the MCU backplane and from the internal data communication address. There is no way for the system to distinguish between different MCUs in different locations at the same hop distance (CAN+QPP) with identical backplane jumper settings. As a consequence, the non-distinguished MCUs are superimposed on each other, and if the same slot has been used in both MCUs, one of the CLIP modules will be put in a separate list of CLIP modules found but not associated to any MCU or SCU.
However, the two CLIP modules discussed above have different CAN addresses and CAN be individually managed from the SNM.
The system performs an automatic inventory of active optical paths between two CLIP modules by matching the DCN addresses of the CLIP modules. This procedure does not always work. As a consequence some paths never appear in the user interfaces (Command Line Interface, Web-based Interface, or Maintenance Manager).
This situation will only occur in configurations where there are optical paths between CLIP modules and neither CLIP module is on the CAN bus to which the management system is connected.
The graphics on the Maintenance Manager are updated slowly and, in some cases, flicker.
The equipment will be tested for compliance to NEBS level 3. The equipment has previously passed environmental testing that indicates that it will comply to ETSI and all NEBS level 2 requirements. It is expected that the system will also meet NEBS level 3 requirements, with the possible exception of the short term temperature requirements. A complete report summarizing the results of these tests, performed by the Swedish environmental lab, SEMKO, is available.
The SNMP interface is read-only. This will be amended in the next main release of the ONS 15200 management software.
The Network Control Board (NCB) module's real time clock does not have a battery backup.
In addition, the real time clock may have up to 5 minutes of deviation in a 24-hour period. This limitation is addressed in a furure revision of the NCB module.
In the current implementation, Cisco-style inventory data, read from the hardware, is presented incorrectly (random text) on the management interfaces. This will be corrected in a maintenance release.
The alarm cut-off button on the CIM board currently has no function because the supporting software has not yet been implemented.
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 Release Notes for Cisco ONS 15200 Release 1.0, 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 toolbar 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 Csco ONS 15200 product documentation.
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, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, 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 Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, 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. (0106R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Dec 10 11:48:39 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.