These release notes provide information about Cisco Network Order Manager (CNOM) Release 1.3, which runs on the Cisco Element Management Framework (CEMF).
|Note CNOM Release 1.3 is designed to run with SCM 2.2(2). The release has not been fully tested with the Cisco DSL Manager (CDM) and the Cisco WAN Manager (CWM).|
Use these release notes in conjunction with the Release Notes for Cisco Element Management Framework Version 3.0.4 and the release notes for element managers that are installed with CNOM Release 1.3.
These release notes contain the following sections.
Following is a list of new features provided by CNOM Release 1.3:
MakeConnectionInvisiblepolicy hides a connection object, and the
MakeConnectionVisiblepolicy makes a hidden connection visible again. In addition, CNOM connect scripts now include a
-hideoption that you can use to hide the connection object created by the script.
ObjectsDeployPrimitive, which deploys multiple objects in a single call rather than one at a time.
CreateConnectionObjectto create the connection object in the connectionObjectsStore view.
For more information about these changes, see the Cisco Network Order Manager Solutions Guide.
The CNOM installation and upgrade procedures have been simplified. Beginning with CNOM Release 1.3, you no longer need to install several separate software packages. Instead, you run a single command that invokes an installation procedure which automatically installs all of the packages. See the Cisco Network Order Manager Solution Guide for instructions on installing or upgrading CNOM software.
CNOM Release 1.3 runs with the following Cisco element management systems:
To run CNOM Release 1.3, the following CEMF release and patches must be installed:
To calculate the system requirements for the element managers being used 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.
The following sections describe important limitations and restrictions that you should review before you use CNOM Release 1.3.
Many of the scripts supplied with CNOM Release 1.3 do not work if the product is installed in a directory other than
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
Instructions for upgrading CNOM software are included in Chapter 2 of the Cisco Network Order Manager Solution Guide. As you perform the upgrade, consider the following:
Work orders cannot be processed during a CEMF backup or restore. Previously, you had to stop CNOM before performing either. Now, you can use the CNOM Release 1.3 commands
./resumeOperation to suspend CNOM processing during a backup or restore, and resume CNOM operation when the process is complete. See the Cisco Network Order Manager Solution Guide for more information.
CNOM Release 1.3 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.3. For caveats affecting CNOM, but not caused by CNOM, the Caveat column lists the component causing the problem.
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.
The CNOM upgrade procedure displays error messages even though the upgrade is successful.
Workaround: Ignore the error messages.
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.
If you use the Cisco 6400 SCM to delete a connection from the connectionObjects view and then run the
If you use
Workaround: After you upgrade the package, use the
When you use the
The following sections list problems resolved in CNOM Release 1.3 and in earlier releases.
Following is a list of problems fixed in CNOM Release 1.3.
It no longer takes more time for the Cisco 6400 SCM Connection Policy to create connections as the number of connections increases.
Soft PVCs (SPVCs) created by CNOM no longer fail to appear in the SubtendPVC view.
connect_cdm script no longer fails to create an SPVC when you use the
You no longer need to be logged in as root the first time you create a connection in CNOM. You can now create the first connection and subsequent connections from a regular (non-root) login.
If you use the CDM Upload Configuration feature to restore connections in CDM, and you then use the
restoreCDMConnection policy to restore those same connections, the names of the connections in CDM views do not match the names in the CNOM connectionObjects view.
set_IMT script no longer fails when you run it multiple times.
A provisioning failure no longer causes a misleading error message to be displayed.
After you install or upgrade CNOM, the system no longer displays an incorrect component version for the DDMG package.
When you create an SPVC using CNOM, the SPVC object no longer fails to appear under the top chassis trunk port in the CDM GUI.
When there are more than 2000 connections, it no longer takes more than 1 minute to delete a single connection.
Following is a list of problems fixed in CNOM Release 1.2.
When you provision SPVC connections with CDM Release 3.3, CNOM no longer uses an incorrect Network Service Access Point (NSAP) address and the connection no longer fails to complete in the node.
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 crashes when you run two CNOM scripts that contain daSet at the same time.
Previously, you could not 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.
The Cisco Network Order Manager Solution Guide now contains instructions on how to access CNOM man pages. Those instructions appear in Chapter 2.
Previously, to configure CNOM to send messages to the syslog file, it was necessary to edit the /etc/syslog.conf file and restart the syslogd daemon. 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 two times for the changes to take effect. This is no longer necessary. The changes take effect the first time you run
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 attempted to reset CEMF. The Cisco Network Order Manager Solution Guide now indicates that the subtend package must be removed before you attempt 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 was added to the guide.
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.
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.
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 use the
-noSave option, the system no longer fails to write a record to the connectionsLog.log file.
The system no longer denies permission to run an executable file created by the
It is no longer necessary 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 you install or upgrade the CNOMSync package.
connect_atm script no longer fails to create an ATM connection in a single Cisco 6400 UAC chassis.
When you run the
restoreSCMATMConnection policy in an environment that contains 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 the proper location.
If a Connection template is applied to one or more connections, it is no longer possible to delete the template after you run the
The Cisco Network Order Manager Solution Guide now indicates that matching names are required for DSL technology profiles and their corresponding ATM QoS profiles.
It no longer takes more time to start up CEMF when several connections exist in the configuration.
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.
delete_QoS_profile no longer fails to delete an ATM QoS profile that was created through the SCM GUI.
disconnectSCM script no longer contains error statements in its success message.
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.
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 caveats fixed in previous CNOM releases.
An attribute format change for NSAP address in CDM no longer causes an incorrect value to be used in CDM SPVC creation. (Fixed in Release 1.0.5)
Connection failure in CDM no longer causes panic in
CDMDMMCtrllr process due to a message buffer being too small. (Fixed in Release 1.0.4)
After you execute
set_line_id several times, a CEMF backup no longer pauses indefinitely. (Fixed in Release 1.0.3)
When you run the bulk cdm connection script, memory leaks no longer occur on the CDM NOA module. (Fixed in Release 1.0.2)
Bulk_disconnect_atm script no longer deletes objects too slowly. The desired performance numbers are now set for disconnects. (Fixed in Release 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 email@example.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:
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:
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:
P1 and P2 level problems are defined as follows:
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: Thu Oct 24 05:36:38 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.