Guest

Cisco Provisioning Center

Release Notes for Cisco Provisioning Center Release 3.0

  • Viewing Options

  • PDF (250.7 KB)
  • Feedback
Release Notes for Cisco Provisioning Center Release 3.0

Table Of Contents

Release Notes for Cisco Provisioning Center Release 3.0

Contents

Introduction

System Requirements

New and Changed Information

New Equipment Module

Enhanced Equipment Modules

Cisco 6400 Equipment Module

Cisco NI-1 DSLAM Equipment Module

Cisco NI-2 DSLAM Equipment Module

Cisco VPN Solutions Center Equipment Module

Cisco WAN Equipment Module

Enhanced Service Applications

Frame Relay Service Application

DSL Service Application

IP VPN Service Application

Major GUI Enhancements

Minor GUI Enhancements

Engine Enhancements

CORBA Interface

Migration

Security Enhancements

avupdate Enhancements

Important Information

Cisco WAN Manager Equipment Module

Cisco NI-2 DSLAM Equipment Module

Patches

Solaris 2.5.1

Solaris 2.6

CPC

Known Limitations

CPC Engine

IP VPN Service Applications

Cisco NI-1 DSLAM Equipment Module

Cisco NI-2 DSLAM Equipment Module

Cisco 6400 Equipment Module

Cisco WAN Manager Equipment Module

Cisco VPN Solutions Center Equipment Module

CPC Database

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Release Notes for Cisco Provisioning Center Release 3.0


These release notes describe the new features, important information, and known limitations for the Cisco Provisioning Center Release 3.0.

Contents

These release notes discuss the following topics:

New and Changed Information

Important Information

Known Limitations

Cisco Technical Assistance

Obtaining Documentation

Introduction

This document contains an updated set of Release Notes for the Cisco Provisioning Center Release 3.0. Its purpose is to outline the new features included in this release. This document serves as a roadmap and must be read in conjunction with the other CPC documents referenced below.

Cisco Provisioning Center Installation and Administration Guide

Cisco Provisioning Center User's Guide

Cisco Provisioning Center Programmer's Guide

Cisco Provisioning Center Programmer's Reference Guide

System Requirements

For more information about CPC system requirements, refer to the chapter titled "Initial Installation" in the Cisco Provisioning Center Installation and Administration Guide.

The Cisco VPN Solutions Center Equipment Module described in Chapter 9 of the Cisco Provisioning Center User's Guide also has the following requirements, as documented in the Release Notes for the Cisco VPN Solutions Center: MPLS Solution 1.0:

For PEs: Cisco IOS 12.0(5)T or later, using the Service Provider feature set. For ISL between the PE and CE, the Enterprise feature set is required.

For CEs: Cisco IOS 11.1 or greater. However, to include RTR support, use12.0(5)T or later, using the IP feature set (i-train).

New and Changed Information

The list below highlights all major new or changed functions and features of this release.

New Equipment Module

The Cisco NI-1 DSLAM Equipment Module is new to this release. This Equipment Module supports cross-connections and uses objects from ATM and DSL Resource Models. The NI-1 DSLAM Equipment Module communicates with the DSLAM directly using SNMP. This release supports:

CAP ADSL

quad SDSL

quad DMT2 ADSL cards

logical port creation

upload from hardware and files

UNI Resiliency.

The ATM and DSL Service Applications support the Cisco NI-1 DSLAM Equipment Module.

Enhanced Equipment Modules

Cisco 6400 Equipment Module

The 6400 upload supports backup RADIUS server upload.

This release supports limited concurrent Transactions. The limitations for concurrency are:

ACL/ACE: It will fail if performing operations on ACE objects (within ACL containment) and deleting the ACL object in the same transaction.

MHET/AggrKey/MtunnelDest: It will fail if performing operations on Aggrkey/MtunnelDes objects (within one MHET) and deleting the MHET object in the same transaction.

Does not support deletion of RADIUS object.

CPU-port can be uploaded as a logical port.

PPP over Ethernet and dynamic binding support.

Support for PPP termination and IP routing.

OC12 cards are now supported.

Multi-NRP delivery on one site within one Transaction is supported.

The NSP is allowed to be configured with a username.

The username and password can be configured as the same name.

Cisco NI-1 DSLAM Equipment Module

This release supports the following cards:

Table 1 NI-1 DSLAM Equipment Module Cards

Cisco Part Number
# of Ports
Description

6100NIM-1-1DS3-2

1

Cisco 6100 DS3 NIM

2xDS3 SHM

2

Dual-port DS3 subtend interface card

2xCAP

2

Two port ADSL card with CAP modulation

ATUC-4-DMT-DIR-1

4

6100 Quad DMT issue 2 ATU-C

STUC-4-2B1Q-DIR-1

4

Cisco 6100 Quad 2B1Q STU-C direct connect

4xFLEX

4

Quad port flexi (DMT) ATU-C


Cisco NI-2 DSLAM Equipment Module

This release supports the username configured on the DSLAM.

This release supports the username configured to be the same as the access password.

Bandwidth re-calculation implementation on DSL physical port is derived from the DSL profile.

This release supports the CPU port.

This Equipment Module checks for uniqueness of the network's and node's name.

The Upload feature has been enhanced as follows:

Recognizes 6130 and 6160 chassis type

Recognizes different 6130, 6160, and 6260 NI-2 cards

Recognizes different Line Cards and corresponding DSL port types (ADSL, SDSL, IDSL)

Uploads DMT, CAP, SDSL and IDSL profile parameters for the DSL Template object. New attributes were added to the DSL Template object to reflect the DMT, CAP, SDSL and IDSL parameters of the DSL profile

Configuration is improved to recognize the username prompt if it is configured on the DSLAM.

This release supports Network Timeout.

Cisco VPN Solutions Center Equipment Module

This release supports Cisco VPN Solutions Center 1.1 and 1.2.

The sub-interface number for PE and CE routers can be auto-generated.

ATM and Switch interface name is not case sensitive.

Labels are more descriptive for Profile Object viewers.

A new section is designated to directly handle connected logical ports to auto-generate VPI/VCI/DLCI.

Upload feature improved to handle default values.

Cisco WAN Equipment Module

This release supports CWM full version, which appears as a new field in the Network Object Viewer:

User must set the CWM full version to create networks.

After database migration, the user must set the CWM full version if migrating from an early release of CPC.

You no longer need to copy an upload tar file to the CWM machine and install stored procedures into the database. Instead, the CWM Equipment Module checks to see if stored procedures are installed, if not, the procedures are installed.

Enhanced Service Applications

Frame Relay Service Application

A new service has been added to the Frame Relay Service Application. This service appears under Service Application > Frame Relay Service Application > Frame Relay over ATM Service in the Tree Viewer. The Frame Relay over ATM service supports all FR-ATM interworking service parameters and allows you to specify all ATM relevant attributes when the FR-FR service passes through an ATM backbone. This new service is identical to the FR-ATM Interworking service except the specifications of the Z side endpoint and its connection ID values. The associated Java class for this object is:

com.syndesis.frrm.RFatServiceObject

The Frame Relay Service and the Frame Relay over ATM Service use the same database table so that a getList operation returns all Frame Relay services instances whether over an ATM backbone or not.

DSL Service Application

This release supports PPP-Termination for the Cisco 6400 Equipment Module.

IP configuration is supported in this release. An IP Connectivity Subscriber Connection Service Object has been added to this release.

The DSL L3 Connectivity contains the new attribute z_subifipmask. This attribute is used for L3 types (multi-hop) when a multi-hop in CNX is created.

The DSL L3 adapters are enhanced as follows:

DSL PAP Service Object: When the port field is filled in, in the subset viewer or object viewer, the interfacetype field automatically fills in the porttype for the selected port.

DSL PAD Service Object: When the service field is filled in, in the subset viewer or object viewer, the provider and servicetype fields automatically fill in the values from the selected service.

DSL Subscriber Service Object: When the subscriberport field is filled in, in the subset viewer or object viewer, the servicetype field automatically fills in the porttypevalue for the selected port. The adapter checks to see if another Subscriber SO is using the selected port (srsoid is empty).

DSL Subscriber Connection Service Object: When the lansap or l2tpsap fields are filled in, in the subset viewer or object viewer, the Provider, Service, PAP and servicetype fields automatically fill in the corresponding values from the lansap or l2tpsap.

DSL Subscriber Destination Service Object: When subscriberdestination or l2tpsap fields are filled in, in the subset viewer or object viewer, the Subscriber (for subscriberdestination) or Provider (for l2tpsap) automatically fill the values from the select objects. The adapter checks to see if the l2tpsap is one that has l2tptype=L2tpsap and subscriberdestination is defined for L2TP-Aggregation and has multidestination=True.

DSL L2TPTap Service Object: When a tunnel field is filled in, in the subset viewer or object viewer, the keyfield automatically fills the tunnel name from the selected l2tpsap. The adapter checks to see if a_tunnel has l2tptype=L2tpsap and nrp is set (not empty) and z_tunnel has l2tptype=L2tpsap.

IP VPN Service Application

This release supports creating IP Address Pools and IP Addresses.

This release supports service viewer functionality. Once the SIV Service Application is installed, you must run the vpkeymerger utility to add the new menu items implemented in this feature.

You can use Service discovery to create an IP address using SRVC data.

Service discovery uses an input file to discover IP Address Pools.

You can profile member connectivity using the Member Connectivity Profile object.

Major GUI Enhancements

The CPC GUI has been enhanced in this release.

The Paste Context button has been removed from the toolbar.

A new menu item titled "What's New" has been added under the Help Menu. Selecting this item produces a dialog box containing the new features included in this release.

The "About" menu item under Help now displays patch information.

Quicker navigation to Service/Node/Logical Port/Physical Port/Link/PVC Subset Viewer with pull-right menu items. These items can be accessed by selecting View > Subset Viewer > from the menu bar.

Enhancements to the Drag and Drop feature. The Drag and Drop feature allows you to drag and drop information into attribute fields (currently Object Viewer only) and view context.

A reorganized Tree Viewer:

New Network Admin folder for network and link creation.

New Network folder shows all the created networks.

New Service Application Profile folder contains profiles for each Service Application.

New Equipment Module Profile folder contains Service Element profiles for each Equipment Module.

Classes under Root are ordered by function instead of alphabetically.

The Tree Viewer automatically launches upon GUI startup and the Root folder automatically expands.

Added support for auto-sizing/placement of viewers and the window.

Quicker response time for aborting get list of the ATM/FR logical port Subset Viewers.

Full row pasting in the Subset Viewer.

Minor GUI Enhancements

The improved Service Diagram Viewer performs the following functions:

The title contains the name of the service.

You can delete the service that is displayed.

At most, one Service Diagram Viewer for each service can be displayed in the GUI

You have quicker access to logs.

The new log button in the Transaction Viewer displays the audit log.

Automatic pop-up of the audit log when a Transaction fails to apply.

A new audit log field has been added to the Transaction and Upload Request Object Viewer.

Three additional uses for the <Enter> key:

On a search filter field, performs a getList.

On an Object Viewer field, performs a save.

On a Schedule dialog field, performs a click on the OK button.

When performing a getList operation, the list count is displayed in the status panel.

The order of the toolbar buttons was rearranged to reduce user errors.

The column width of the Tree Viewer is larger.

The column width of the Subset Viewer is larger to accommodate large text strings when specifying endpoints for ATM and FR services.

The log titled "Audit Log Log Viewer" now reads "Audit Log xxxx", where xxxx is an upload request number.

The same set of classes is kept in the Subset Viewer's context icon menu when a superclass/subclass is selected (Subset Viewer superclass feature).

Engine Enhancements

A new value has been added for CPC to auto-generate connection IDs. An input connection ID value of "-3" for VPI/VCI/DLCI can be specified on the A side of any service. This value prompts CPC to auto-generate the connection ID locally (as if a value of -1 was specified). This generated values becomes the preferred connection ID on every logical port including the Z side service endpoint throughout the rest of the path.

For example, for service endpoints A and Z within a single opaque network, a user entering a value of -3 for the A side VPI and VCI produces the following results:

A side VPI and VCI values are auto-generated (as if a value of -1 was entered).

The Z side VPI is identical to the A side VPI, and the Z side VCI is identical to the A side VCI. If these values are unavailable, the Z side values are auto-generated (as if a value of -1 was selected)

CORBA Interface

Overwriting the attributes of a PVC using the AttributeItemValueSeq method does not update the "vpn" field. This value can be set afterwards using the setValue method. This occurs because the vpn/md attributes are set before the parent, and consequently information from the parent overwrites those attributes in the object. To fix this problem, you must re-order the attributes so that vpn/md are set last.

Migration

CPC 1.2 (and further releases) uses Java Runtime Environment (JRE) version 1.1.6, while CPC 2.0 (and further releases) uses JRE version 1.2.1. JRE version 1.2.1 is installed as part of the CPC 3.0 installation. After migration from a CPC release prior to CPC 2.0, change user .profiles to point to the correct JRE version.

Security Enhancements

This release contains security enhancements that restrict which user account has access to the installed CPC file system. These enhancements are based on the following assumptions.

SYfinalizeInstall is invoked after the last component is installed.

The UNIX account used for installing (hereafter referred to "admin") has a umask set to 022.

The admin account is used to install both the client and the server software.

Based on the above assumptions, the following security enhancements are supported:

Only the admin user is able to successfully start and run the CPC server. No directories or files on the server installation (other than the user directory) has group or other write permissions.

The client installation has the same properties as the server installation, except that the user directory and the files contained within, have write permissions by both the admin user and the group that the admin user belongs to.

Combined server/client installations are treated as server installations.

avupdate Enhancements

The new avupdate utility specifies a temporary directory to be used to unpack .bin files. A new flag "-t", has been implemented for this purpose.

Important Information

Detailed CPC software version information can be found in the file $CCP_MNG/version_info/Manifest. This file may need to be referred to during any support calls.

Cisco WAN Manager Equipment Module

CPC names FR, ATM, and CBR logical ports in the same manner as the CWM Connection Manager. The following shows the mapping of logical port naming from CWM to CPC:

Circuit Type (Card)
CWM Attributes Used for Name
CPC Attributes Used for Name

Frame Relay (FRSM)

Slot_number.physical_port_number
(i.e. 8.8.1)

Slot_Number.PortNumber.starting_channel

Frame Relay (FRP/UFM)

Slot_number.logical_port_number

Slot Number.SV+Port Number

ATM (ALL)

Slot_number.logical_port_number
(i.e. 5.1)

Slot Number.SV+ Port Number

CBR (ALL)

Slot_number.physical_port_number
(i.e. 10.3.24)

Slot Number.PortNumber.starting_channel


Cisco NI-2 DSLAM Equipment Module

The TFTP server no longer needs to be enabled. It has been replaced with FTP in order to solve the security problems caused by TFTP set on the UNIX workstation. Two environment variables should be set in order to use FTP before starting CPC.

EXPORT C2_USER=username

EXPORT C2_PASSWORD=passsword

Where username and password are the CPC admin user login and password.

Support for the following NI-2 Cards:

Table 2 NI-2 DLSAM Equipment Module Cards

Cisco Part Number
Description

NI-2-155MM-155MM

NI-2 OC3/STM1 Multi-Mode; 1 WAN, 1 Subtend

NI-2-155SM-DS3

NI-2 OC3/STM1 Multi-Mode; 1 WAN, 1 Subtend

NI-2-155MM-DS3

NI-2 OC3/STM1 Multi-Mode; 1 WAN, 1 Subtend

NI-2-155SM-155SM

NI-2 OC3/STM1 Multi-Mode; 1 WAN, 1 Subtend

NI-2-DS3-DS3

NI-2, 1 DS3 WAN, 2 DS3 Subtend

STUC-4-2B1Q-DIR

4-port SDSL Line Card

ATUC-4-FLEXIDMT, ATUC-4-FLEXICAP

4-port FLEXI ADSL configurable for DMT or CAP


The bandwidth values for the DSL Subscriber Service Subset Viewer are as follows:

Upstream Bandwidth must be less than or equal to the DSL Template upstream value (maximum fast path bit rate + maximum interleaved path bit rate).

Downstream Bandwidth must be less than or equal to the DSL Template downstream value (maximum fast path bit rate + maximum interleaved path bit rate).

If the DSL Template does not exist then an error "DSL Template does not exist" is displayed.

The Equipment Module should be pre-configured through telnet to have Traffic index commands as well as DSL profiles. The default profile "default" is present in the DSLAM.

Patches

For more information about installation, refer to the chapter titled "Initial Installation" in the Cisco Provisioning Center Installation and Administration Guide.

The following Solaris patches are required for CPC 3.0:

Solaris 2.5.1

patch 103566-43

patch 103627-10

patch 103640-28

Solaris 2.6

patch 105181-15

patch 105210-19

patch 105490-07

patch 10558-13

patch 105633-21

patch 105669-07

patch 106040-11

CPC

The following patches must be installed from the installation CD:

SRPatch001

SRPatch002

SRPatch501

CSPatch001

CSPatch501

CSPatch502

C1Patch501

C1Patch502

C2Patch001

C4Patch001

C4Patch002

C4Patch003

C4Patch501

C4Patch502

CVPatch501

SDLPatch001

SDLPatch002

SDLPatch003

SDLPatch501

SDLPatch502

VPIPatch001

VPIPatch002

VPIPatch003

The following additional patches, available from the CCO website, must also be installed:

SRPatch502

C1Patch503

C1Patch504

C1Patch505

C2Patch501

C4Patch503

CVPatch502

RFSOPatch501

SDLPatch503

SDLPatch504

VPIPatch501

From time to time, other applicable patches will also be posted to the CCO website.

Known Limitations

CPC Engine

Before running multiple FTI scripts concurrently, ensure that the configured limit for script managers is set to handle the concurrent sessions. To increase the number of concurrent sessions allowed by the script manager, perform the following procedure:


Step 1 Open the $CCP_CONFIG/syconfig file on the CPC Server host.

Step 2 Edit the SYSSN.syscriptmanagerLimit parameter to indicate the number of concurrent script managers. For example, to increase the number of concurrent sessions allowed by the script manager to 5, the parameter should read:

SYDDN.syscriptmanagerLimit = 5

Step 3 Save and exit the file.

Step 4 Invoke a reread of the configuration files:

SYnpt - r


IP VPN Service Applications

To run service discovery, perform the following steps:


Step 1 Create Provider and VPNNetwork using IP VPN Service Application.

Step 2 Use the Cisco VPN Solutions Center Equipment Module to upload the network created above.

Step 3 On the CPC Client run vpiservicediscovery

$CCP_REL/mng/utility/vpiservicediscovery


The IP VPN Service Application supports this Equipment Module using the IP resource model.

Improved the functionality to create an IP Address and an IP Address Pool through service discovery. To create an IP Address Pool:

$CCP_REL/mng/utility/vpiservicediscovery  poolFilename

The file "poolFilename" should be located in $CCP_REL/data/VPI in the format:

vpnname=text1; srname=text2
vpnname=text3; srname=text4

Sample file:

vpnname=Vic_VPN; srname=175.17.16.0/24;

Each line is used to create one pool.

The vpnname is the name of the VPN. Service discovery uses this name to find the Service Contract associated with that name. The attribute srname is the name of the IP pool that needs to be created.

Cisco NI-1 DSLAM Equipment Module

This release only supports version 2.4.1 of the Cisco NI-1 software.

One Transit Subscriber is created for each Subtended Port.

VCI range for VPI-1 on Subtended and WAN ports is restricted to 399 by CPC. The hardware supports a range of 0 to 1599.

You can create LPorts only on DSL PPorts.

This release does not support database migration.

Event logging is not supported with this Equipment Module.

After upload of an NI-1 network object, the status in the GUI does not change, regardless of whether the upload succeeded or failed.

Cisco NI-2 DSLAM Equipment Module

ATM cross-connections should have the traffic parameters of an existing ATM cross-connections object available in the IOSQoS object. This allows you to modify the DSL Physical port and provision an ATM cross-connection with the traffic parameters existing in the CPC database.

The CPC database should contain the Equipment Module information prior to provisioning.

Attempts to provision a cross-connection with the non-existent Traffic attribute will fail.

This release does not support database migration, NNI Resiliency, Event Log.

Cisco 6400 Equipment Module

During a multi-hop tunnel upload, password information can not be uploaded from the 6400. After the upload occurs, the existing multi-hop tunnel password is empty. If you want to use the existing multi-hop tunnel, you must manually provide password information for the tunnel.

For NPR Interval PVCs, if the CNX type is set to "other", CPC does not allow you to modify or delete this object. This object must be manually deleted from the NRP.

For single-hop tunnels, if the Dial Type is set to "other", CPC does not allow you to modify or delete this object. This object must be manually deleted from the RADIUS server.

If a user fails to delete an object, because of an error returned by the network interface, the GUI does not allow further attempts to delete the object.

NSP redundancy, NRP redundancy, and NLC redundancy are not supported. The IOS command used to discover the IP address of the NPR does not function when NRP's are configured to be redundant within the 6400 chassis. The default for the attribute c4_redundant is FALSE.

Node line cards other than DS3 and OC3 do not support service upload.

You cannot create a DSL Subscriber Connection object with a peak cell rate (PCR) less than the maximum cell rate (MCR) when created through the Cisco 6400.

This release does not support provisioning on the CPU port.

Cisco WAN Manager Equipment Module

Workaround

The following changes to the CPC User's Guide provide a workaround for the problem that prevents the CS Event Logger from creating its log file.

Event Logging and Daemon Installation.

In Step 2, replace the last two lines:

. /opt/cpc/Server/mng/utility/syccpovdef
export PS1="${LOGNAME}@$(hostname )"

with:

export CCP_REL=/opt/Activator/Server
export CCP_CONFIG=$CCP_REL/mng/config
export TCL_LIBRARY=$CCP_REL/data/AUTOLOAD
export CCP_TCL_LIBRARY=$TCL_LIBRARY
export PS1="<"'$LOGNAME'@'hostname'">"

Replace Step 7 with:

Step 7 In the Activator Server host runtime environment:

cd $CCP_REL/log/event
touch CSeventLog
chmod g+w CSeventLog

Notes

Because of CWM issues, some CPC attributes are not delivered to CWM. These attributes are:

Object
Field Names

FR Logical Port

DE Threshold

CBR-CBR and CBR-ATM Circuits

CBR Clock Mode Re-assembly size (octets)

All circuits

Trunks to avoid

Avoid ZCS trunks

ATM Logical Port

Override CAC


If upload fails due to a "-1" error, see the audit log for the corresponding upload request. The audit log provides you with information about which ports or circuits caused the error. A "-1" error in ports display the node_id, slot, and port in the following format:

node_id.l_slot.l_port - r_node_id.r_slot.r_port:bad_attribute_1bad_attribute_2

The PLCP and ATM Port Queue Configuration attributes in the Logical Port window are supported for CWM 9.2 and AUSM-8 cards only.

CWM 9.2.08 should have patch 9 or higher applied.

Uploaded IGX FRM cards show up as FRP cards in CPC. This has no impact on provisioning logical ports or circuits.

For CBR logical port and circuits the following default values are used:

Unstructured 4T1 port speed = 1536 kbps

Unstructured 8T1 port speed = 1544 kbps

While creating CBR or Frame Relay logical ports, first select the appropriate physical port. This allows for proper channel verification when the port is being saved.

CPC has defined two attributes for both CWM MIB attributes atmENdPointRateDown and atmEndPointRateUp. The first set of attributes are ATM resource attributes used for ABR.1 circuits. The second set are CWM specific and are used for ABR FS. Using ATM resource attributes for ABR FS results in a significant loss of granularity in conversion.

When creating CBR Services, the Service Application checks that both endpoints are structured or unstructured. If the endpoints are unstructured, the interface must be same (DS1, DS3, etc) and the port speed must be equal. If the endpoints are structured, the number of timeslots must be equal.

MGX 8850 feeder nodes should be configured so that the trap IP address matches the NWIP ATM IP address.

Occasionally, a circuit will appear in CWM as "incomplete." Incomplete circuits consume a VPI/VCI or DLCI value and cannot be uploaded by CPC. CPC may try to create circuits on the same port with the same VPI/DLCI values. This will fail in CWM. The incomplete circuit must be removed from CWM. There are several ways to accomplish this:

Delete the circuit through the CWM Connection Manger.

Delete the circuit through CLI.

Run user/users/svplus/bin/nodeResync "network IP Address"

Recreate the CWM database.

The error "First_digit:no such variable" may appear in a site error log while trying to provision a service. This indicates that the firmware for one of the switches has not been uploaded correctly from CWM. Re-install the firmware on the switch in question and re-upload nodes such that the attribute "Firmware Release Provision" in the Node window contains a valid value.

Depending on network load, CWM activity and other factors, network changes may not be stored in the CWM database for several minutes. A CPC upload performed in the interval before the network change is stored in the CWM database will result in the new network changes, such as the creation of new circuits, not being uploaded.

BXM and UXM trunk ports impose a minimum PCR of 50 and a minimum MCR of 6 on any PVC passing through the port in CWM 9.2. CPC does not detect this, so PVC provisioning may fail if the requested PCR or MCR is below the minimum value and the PVC passes through a BXM or UXM trunk port. The workaround is to increase the requested PCR to 50 or the MCR to 6.

For CWM, the length of a network name must not exceed 8 characters, and the length of a node name must not exceed 10 characters. Specifying a network/node name that is longer will force CWM to trim the name before storing it in CWM database. As a result, network/node upload would return no fabric/service information because the upload process cannot retrieve the network ID based on the longer network name.

Cisco VPN Solutions Center Equipment Module

In the CPC GUI, you are unable to modify "Create only" attributes. The attribute is blocked. If you use the FTI to modify a "Create Only" attribute, it returns a successful code, even though no modification appears in CPC and VPN Solutions Center.

This release does not support OSPF routing protocol. Any attempt to upload an SRVC with cvpecelinkprtcl=OSPFRoutingType, causes the "upload getter" to fail.

CPC Database

This release supports Informix release 7.3.0 UC11 or higher. Previous releases are not available from Informix.

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

http://www.cisco.com

http://www-china.cisco.com

http://www-europe.cisco.com

Documentation CD-ROM

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 as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered CCO users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

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, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

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

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:

http://www.cisco.com

Technical Assistance Center

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.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

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

Contacting TAC by Telephone

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:

P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.