|
|
May 2001
These release notes provide information about Cisco Network Order Manager (CNOM) Release 1.2, which runs on the Cisco Element Management Framework (CEMF).
Use these release notes in conjunction with the Release Notes for Cisco Element Management Framework Version 3.0.4, the release notes for element managers that are installed with CNOM Release 1.2, and the release notes for Cisco IOS Release 12.0(S).
These release notes contain the following sections.
For information about installing the CNOM software, refer to the Cisco Network Order Manager Solution Guide.
CNOM Release 1.2 runs with the following element management systems:
CNOM Release 1.2 requires:
To calculate the system requirements for element managers running with CNOM:
1. Find the recommended system configuration for each of the element managers that will be running on the system as specified in its documentation.
2. Add the memory, disk, swap, and processor requirements specified for each element manager for the number of nodes being managed by that element manager.
CNOM Release 1.2 supports the management of the following entities in equipment managed by Cisco DSL Manager Release 3.3.1:
CNOM Release 1.2 supports the management of the following entities in equipment managed by Cisco Service Connection Manager Release 2.2(1):
CNOM Release 1.2 supports the following northbound integration methods:
CNOM Release 1.2 also provides the utility cemfql, which supports queries into the Cisco Element Manager Framework object model.
The following sections describe important limitations and restrictions that you should review before you use CNOM Release 1.2.
Many of the scripts supplied with CNOM Release 1.2 do not work if the product is installed in a directory other than /opt/cemf.
As a workaround, create a soft link between the actual installation directory and /opt/cemf. Use the following command:
% ln -s <actual_cemf_installation_dir> /opt/cemf
A requirement of the CEMF backup process is that you cannot perform any object deployments while the backup is taking place. Currently, this has to be enforced manually, but will be automatic in future CEMF patches.
 |
Caution Do not submit work orders during CEMF backup. Timeouts on the submitting system or serious CEMF data integrity issues may occur. |
Further, the work order view must be empty before the CEMF backup process starts. Inconsistencies may develop between the submitting system and CNOM when work orders that time out in the submitting system complete later in CNOM.
CNOM Release 1.2 does not support end-to-end connections between different devices. This means that you cannot use CNOM to set up a connection between a Cisco 6400 UAC and a DSLAM, or between two Cisco 6400 UACs through a WAN. You can, however, use CNOM to set up an end-to-end connection between subtended DSLAMs, or between multiple UACs in a local network.
Table 1 lists the open caveats for CNOM Release 1.2. For caveats affecting CNOM, but not caused by CNOM, the Caveat column lists the component causing the problem.
| Caveat | Description |
|---|---|
CSCdt20738 | Soft PVCs (SPVCs) created by CNOM appear in the ComponentManaged and connectionObjects views; they do not appear in the SubtendPVC view. Workaround: None. |
CSCdt23620 | When a DSLAM (chassis) with valid connections is decommissioned and then recommissioned, connection objects in the CDM GUI and in the Object Configuration window remain in the decommissioned state. Workaround: After you recommission the DSLAM, manually commission the connection objects. |
CSCdt23745 | You cannot use Workaround: Use |
CSCdt28067 | The CNOM upgrade procedure displays error messages even though the upgrade was successful. Workaround: Ignore the error messages. |
CSCdt32097 | You must be logged in as root to create the first connection; otherwise, subsequent connections fail. This is because the system uses the Workaround: Log in as root to create the first connection. |
CSCdt40751 | CNOM does not check the values of ATM QoS and WAN ATM QoS profile parameters; therefore, it is possible to create profiles with invalid values. Workaround: Be sure to specify valid values for profile parameters. Note that the WAN ATM QoS Profile window now lists valid ranges for parameters. |
CSCds45723 | The time it takes for the Cisco 6400 SCM Connection Policy to create connections increases as the number of connections increases. Workaround: None. |
CSCdt46308 | If you use the CDM Upload Configuration feature to restore connections in CDM, and then use Workaround: None. |
CSCdt57627 | If you use the Cisco 6400 SCM to delete a connection from the connectionObjects view and then run the Workaround: None. |
CSCdt58220 | The Workaround: None. |
CSCdt59728 | If you use Workaround: After you upgrade the package, use the |
CSCdt66426 | When you use the Workaround: None. |
CSCdt80497 | A provisioning failure displays a misleading error message. Workaround: None. |
CSCdt82762 | After you install or upgrade CNOM, the component version for the DDMG package is incorrect. Workaround: None. |
CSCdt95685 | When you create an SPVC using CNOM, the SPVC object does not appear under the top chassis trunk port in the CDM GUI. Workaround: None. |
CSCdu16411 | When there are more than 2000 connections, it takes more than one minute to delete a single connection. Workaround: None. |
The following sections list problems resolved in CNOM Release 1.2 and in earlier releases.
Following is a list of problems fixed by CNOM Release 1.2.
When you provision SPVC connections with CDM Release 3.3, CNOM no longer uses the wrong NSAP address and the connection no longer fails to complete in the node.
The disconnect_cdm script no longer fails to remove the connection from the ComponentManaged view.
The CNOM command connect_cdm no longer fails to create the connection and the error message is no longer confusing.
CDM no longer crashes when you run two CNOM scripts at the same time.
The system no longer hangs when you run two CNOM scripts that contain daSet at the same time.
Previously, there was no way to determine the valid values for parameters in the WAN ATM QoS profile. This information was added to Table E-1 in the Cisco Network Order Manager Solution Guide.
Previously, the Cisco Network Order Manager Solution Guide was missing instructions on how to make the CNOM manual pages available. Those instructions were added to Appendix A.
Previously, you had to edit the /etc/syslog.conf file and restart the syslogd daemon to configure CNOM to send messages to the syslog file. Now, however, the syslog facility is turned off by default.
Previously, when you updated a class configuration file in the directory /opt/cemf/config/CNOMSync/objectClasses, you had to run updateCNOMSync twice for the changes to take effect. You no longer have to do this; the changes take effect the first time you run updateCNOMSync.
The CNOM connect_scm script no longer fails to create the connection.
Previously, if you upgraded CNOM or CDM without first removing the Subtend package, the system crashed when you tried to reset CEMF. The Cisco Network Order Manager Solution Guide was updated to indicate that the subtend package must be removed before attempting an upgrade.
Previously, the Cisco Network Order Manager Solution Guide did not mention that the commands cemf install -r and cemf -install -s do not display package information for CNOMSync. This information has been added to the guide.
Running the disconnect_atm script no longer fails to remove all of the connection objects from the Map Viewer window in the GUI.
When you try to create an ATM connection with existing VPI/VCI values, the system no longer fails to display an error message.
The SyncLog.log file no longer fails to record information about ATM connections that are created or deleted through the SCM GUI.
When you use CDM to create a subscriber connection, CNOMSync no longer fails to record the creation of the corresponding PVC object.
When you use the GUI to delete a connection object from the connectionObjects view, the system no longer fails to record a message to the SyncLog.log file.
The disconnect_atm script no longer takes 4 minutes to disconnect a single ATM connection, and it no longer fails to remove all GUI subscriber objects in the Cisco6400Subscriber view.
The getConnectionData script no longer displays connection data for a failed connection.
CEMF no longer fails to restart after you install the CNOM packages DDMG, DDMGen, CNOMSync, and C6400DMM, and reset the database.
When you run the connect_atm script with the noSave option, the system no longer fails to write a record to the connectionsLog.log file. In addition, the system no longer writes a record to the SyncLog.log file.
The system no longer denies permission to run an executable file created by the getResoreWO script.
You no longer need to run Discover Subtends on a single chassis to create a connection.
Loading CNOM objects and views into the connectionObjects view no longer causes a CNOMsync core dump.
The system no longer displays an incorrect package version when you run cemf install -s after installing or upgrading the CNOMSync package.
The connect_atm script no longer fails to create an ATM connection in a single Cisco 6400 chassis.
When you run the restoreSCMATMConnection policy in an environment with multiple Cisco 6400 UACs, the connection objects are no longer restored under the egress port of the CLEC chassis. They are restored under the tie port of the CLEC chassis, which is where they should be restored.
If a Connection template is applied to one or more connections, it is no longer possible to delete the template after running the restoreSCMATMConnection policy.
The Cisco Network Order Manager Solution Guide did not indicate that matching names are required for DSL technology profiles and their corresponding ATM QoS profiles. That information has been added to the guide.
It no longer takes more time to start up CEMF when there are a lot of connections.
The create_QoS_profile script no longer fails to create an ATM QoS profile.
When you run the set_IMT script, the system no longer fails to log the work order in the connectionsLog.log file.
The script delete_QoS_profile no longer fails to delete an ATM QoS profile that was created through the SCM GUI.
The disconnectSCM script no longer contains error statements in its success message.
Previously, the disconnect_atm script removed a connection in CEMF but failed to remove the connection on the device if there were communication problems between CEMF and the device. Even though the connection still existed on the device (but not in the CEMF database), the script returned a success message.
The disconnect_atm script has been fixed. Now, if communication problems exist, and the system cannot access the device to remove the connection, the script returns an error message and does not remove the connection from the CEMF database.
Following is a list of CNOM bugs fixed in previous CNOM releases.
An attribute format change for NSAP address in CDM no longer causes the wrong value to be used in CDM SPVC creation. (Fixed in 1.0.5)
Connection failure in CDM no longer causes panic in CDMDMMCtrllr process due to a message buffer being too small. (Fixed in 1.0.4)
After executing set_line_id several times, CEMF backup no longer pauses indefinitely.
(Fixed in 1.0.3)
Memory leaks on the CDM NOA module no longer occur when you run the bulk cdm connection script. (Fixed in 1.0.2)
After executing set_line_id several times, CEMF backup no longer pauses indefinitely. (Fixed in 1.0.2)
The Bulk_disconnect_atm script no longer deletes objects too slowly. The desired performance numbers were not set for disconnects. (Fixed in 1.0.1)
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:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
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 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 numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, 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, 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 brands, names, or 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. (0104R)
Copyright ©2001, Cisco Systems, Inc.
All rights reserved.
Posted: Thu Oct 24 05:38:01 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.