Guest

Cisco IP Solution Center

Release Notes for Cisco IP Solution Center, 4.2.3

  • Viewing Options

  • PDF (422.1 KB)
  • Feedback
Release Notes for Cisco IP Solution Center, 4.2.3

Table Of Contents

Release Notes for
Cisco IP Solution Center, 4.2.3

Contents

Introduction

System Recommendations

Problems Fixed in ISC 4.2.3

Customer-found Problems Fixed Specifically in ISC 4.2.3

Customer-found Problems Fixed in ISC 4.2.2

Customer-found Problems Fixed in ISC 4.2.1

Installation Notes

Version Supported

Upgrade Paths

Uninstall

Important Notes

Known Problems in ISC 4.2.3

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for
Cisco IP Solution Center, 4.2.3


All documentation, including this Release Notes for Cisco IP Solution Center, 4.2.3 document and any or all of the parts of the Release 4.2 documentation set: http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/tsd_products_support_series_home.html might be upgraded.

Cisco IP Solution Center software is referred to as ISC.

This document gives you an overview of this maintenance release and helps you understand what has changed since ISC 4.2.2. Please read this document prior to reading any other manual for ISC.

Contents

The information in this document is organized into the following sections:

Contents

Introduction

System Recommendations

Problems Fixed in ISC 4.2.3

Installation Notes

Important Notes

Known Problems in ISC 4.2.3

Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

Cisco IP Solution Center (ISC) 4.2.3 is a maintenance release for ISC 4.2, which includes Cisco MPLS Diagnostics Expert (MDE) 2.0. The system recommendations for ISC 4.2.3 are based on those for ISC 4.2. To see these system recommendations, go to the "System Recommendations" section.

URLs for base information about ISC 4.2 and an overview and suggested reading order of these documents is given in the Cisco IP Solution Center Getting Started and Documentation Guide, 4.2 (http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/
products_documentation_roadmap09186a008069c214.html
).

Steps for installing ISC 4.2.3 are found in the "Installation Notes" section, and other important information is found in the "Important Notes" section. For problems that were found and might still exist in ISC 4.2.3, see the URL in the "Known Problems in ISC 4.2.3" section.

System Recommendations

The system recommendations and requirements are listed in Chapter 1, "System Recommendations" of the Cisco IP Solution Center Installation Guide, 4.2 (http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/
products_installation_guide_book09186a00806923f0.html)
.

The recommendation is to thoroughly review this information before even planning your installation, to be sure you have all the hardware and software you must successfully install.

Problems Fixed in ISC 4.2.3

Customer-found problems that were fixed in ISC 4.2.3 include those also fixed in the previous maintenance releases 4.2.1 and 4.2.2, all built on ISC 4.2. The information is presented as follows:

Customer-found Problems Fixed Specifically in ISC 4.2.3

Customer-found Problems Fixed in ISC 4.2.2

Customer-found Problems Fixed in ISC 4.2.1

Customer-found Problems Fixed Specifically in ISC 4.2.3

Table 1, "Customer-found Problems Fixed Specifically in ISC 4.2.3," describes all the customer-found problems that were fixed specifically in this maintenance release.

Table 1 Customer-found Problems Fixed Specifically in ISC 4.2.3 

CDETS Number
Subject

CSCsg38148

User is not allowed to create template variables.

CSCsg54407

Quality of Service (QoS) cannot use class-default and match.

CSCsg61446

Ethernet Wire Service (EWS) to Ethernet Relay Service (ERS) should not allow a VLAN set to 1.

CSCsg61453

Audit fails on optical port of M3400 when provisioned as a User-Network Interface (UNI).

CSCsg61458

Reference counting of a media access control (MAC) access control list (ACL) on a multi Service Request port is not working.

CSCsg61459

Maximum transmission unit (MTU) size changes breaks services.

CSCsh61460

Service Request details are repeatedly showing the wrong Service Request in the graphical user interface (GUI).

CSCsg61461

Clear the VLAN name field in the Service Request.

CSCsg61462

Aggregate-policer and class-map names have changed for the Cisco 3550.

CSCsg61756

Negating keepalive is not working.

CSCsg72849

Layer 2 (L2) Virtual Private LAN Service (VPLS) ERS decommission fails to remove the port security attributes from the UNI interface.

CSCsg87000

Cannot deploy multiple ERS QoS policies on a port 3400.

CSCsh26424

Any L2 VPLS ERS or EWS Service Request goes to Failed Audit state.

CSCsh28705

L2 VPLS Service Request goes to Invalid state with a provider edge router (PE) UNI interface description.

CSCsh34364

Redeployment of Service Request negates port for both Link Duplex and Speed None.

CSCsh34366

Decommission of ERS Service Request on a shared UNI removes port security and link attributes.

CSCsh34451

Provisioning a QoS Service Request where uplink is port-channel fails due to an input.xml error.

CSCsh37660

For ERS to EWS service, cannot create more than one service.

CSCsh40247

Adding or removing a service policy on a QoS VPLS U-PE needs to handle multiple endpoints.

CSCsh42000

GUI error occurs when trying to import L2VPN on a Cisco 3400 using port-channel.

CSCsh43366

Incorrectly negates UNI link-speed and link-duplex for a shared UNI.

CSCsh46096

ISC QoS with no class-map entry causes the download to fail.

CSCsh50970

Unable to select an individual UNI for decommissioning a Service Request.

CSCsh50974

Port-channel capitalization of C in Channel causes an issue when deploying a Service Request.

CSCsh57634

Service Requests with extra multi-VPN routing and forwarding tables CE (MVRFCE) loopback addresses are causing failed deploys.

CSCsh62690

Incorrect behavior occurred when removing a VPN when using VPN routing/forwarding instance (VRF) overwrite.

CSCsh74099

Cisco Networking Services (CNS) server hangs when retrieving all devices from the database.When using CNS transport provisioning, it hangs in the Wait Deploy state.

CSCsh86564

Purging links from an imported Service Request causes an incorrect interface list.

CSCsh97764

Unable to deploy port-channel subinterface.

CSCsi43607

Failure when trying to create an MPLS Service Request with two links on the same provider edge router using the same VPN routing/forwarding instance.


Customer-found Problems Fixed in ISC 4.2.2

Table 2, "Customer Affecting Problems Fixed in ISC 4.2.2," describes all the customer-found problems and internally-found problems of customer importance that were fixed previously in ISC 4.2.2 and rolled into this ISC 4.2.3 Maintenance Release.

Table 2 Customer Affecting Problems Fixed in ISC 4.2.2 

CDETS Number
Subject

CSCse89624

When the allow vlan command line interface exceeds 255 characters, it causes a platform failure.

CSCsg74568

ATM over MPLS (ATMoMPLS) template fails with a NullPointerException from the function getExportedAttrs().

CSCsg74819

API does not support the ability to have multiple datafiles for the same template.

CSCsg85095

Templates incorrectly downloaded when a Service Request is in the INVALID state.

CSCsg99509

Unable to view an MPLS Service Request created through an API when using the script ViewMPLSRequest.xml.

CSCsh02733

ISC adds to the interface description, which can exceed the character limit.


Customer-found Problems Fixed in ISC 4.2.1

Table 3, "Customer-found Problems Fixed in ISC 4.2.1," describes all the customer-found problems that were fixed previously in ISC 4.21 and rolled into this ISC 4.2.3 Maintenance Release.

Table 3 Customer-found Problems Fixed in ISC 4.2.1 

CDETS Number
Subject

CSCsg37248

NullPointer exception is thrown while modifying or deleting a template from an MPLS VPN link using API.

CSCsg38148

4.1.2 and 4.2: User is not allowed to create template variables from the Data File Editor.

CSCsg39985

Virtual circuit descriptor (VCD) field in MPLS asynchronous transfer mode (ATM) Service Request Link Attribute screen is required but should be optional.

CSCsg42411

Deployment of the L3VPN Port-channel sends the no keepalive command.

CSCsg50337

ISC modifies the name of the Port-channel interface to Port-Channel interface fails due to case-sensitivity.

CSCsg59181

ISC Diagnostics Tool is bundled with the product instead of the previous implementation in which it was standalone on cisco.com.

CSCsg63412

ISC should have "Vlan" instead of "VLAN" to match the IOS representation.


Installation Notes

This section contains the following information:

Version Supported

Upgrade Paths

Uninstall

Version Supported

ISC 4.2.3 supports upgrading from ISC 3.2.2, 3.2.2.3, 3.2.2.5, 4.0, 4.0.1, 4.1, 4.1.1, 4.1.2, 4.2, 4.2.1, or 4.2.2 after ISC 4.2 is installed. If you are upgrading from a version of ISC prior to ISC 3.2.2, see Chapter 2 in the Cisco IP Solution Center Installation Guide, 4.2.

If you have an existing VPNSC 1.x or 2.x repository, you must migrate it to be able to use it with ISC 4.2. Get the migration package, including the documentation that lists limitations, from isc-mktg@cisco.com.

Upgrade Paths

If you are upgrading from ISC 3.2.2, 3.2.2.3, 3.2.2.5, 4.0, 4.0.1, 4.1, 4.1.1, or 4.1.2, you must install ISC 4.2 first, as explained in the Cisco IP Solution Center Installation Guide,4.2, and download the ISC 4.2 Upgrade Script, which is located at http://www.cisco.com/cgi-bin/tablebuild.pl/isc (where, in tablebuild.pl, the last character is the lower-case letter "l"), on the same server. After upgrading to ISC 4.2, download and install the ISC 4.2.3 maintenance patch, which is also located at http://www.cisco.com/cgi-bin/tablebuild.pl/isc.

If you are upgrading from a version of VPNSC or ISC prior to ISC 3.2.2, see Chapter 2 in the Cisco IP Solution Center Installation Guide, 4.2.


Note If you are using an Oracle database prior to Oracle 10, you must upgrade your Oracle installation and your Oracle database. The Oracle database supported with this release is 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production with the Partitioning, OLAP, and Data Mining options.


Then follow these steps:


Step 1 Before upgrading to this Maintenance Release, complete the discovery workflow. Otherwise, when you upgrade these previously initiated discovery workflows, the data discovered during that process might be lost.

Step 2 Before proceeding to install the ISC 4.2.3 Maintenance Release, be sure to back up your repository, as explained in Appendix C of the Cisco IP Solution Center Installation Guide, 4.2 (http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/
products_installation_guide_book09186a00806923f0.html)
.

Step 3 Go to http://www.cisco.com/cgi-bin/tablebuild.pl/isc (where, in tablebuild.pl, the last character is the lower-case letter "l") to retrieve the ISC 4.2.3 Maintenance Release (isc-4.2.3-maint.tar.gz).


Note Patches that use ISC 4.2.3 as the base will also be located at http://www.cisco.com/cgi-bin/tablebuild.pl/isc


Step 4 Prior to installing the ISC 4.2.3 Maintenance Release, verify that you have 100 MB of free space in the $ISC_HOME directory and that you are logged in with the same username as the owner of your supported version of ISC.

Step 5 Navigate to a directory other than $ISC_HOME.

Step 6 Use the following command to untar and unzip the appropriate isc-4.2.3-maint.tar.gz file:

gunzip -c isc-4.2.3-maint.tar.gz | tar xf -

Step 7 If ISC is running, use the following command to stop the database, name server, and WatchDog on the machine on which it is running:

$ stopall

Step 8 If you are running on ISC 3.2.2, 3.2.2.3, 3.2.2.5, 4.0, 4.0.1, 4.1, 4.1.1, or 4.1.2, install ISC 4.2, as documented in the Cisco IP Solution Center Installation Guide, 4.2.


Note Prior to installing ISC 4.2, if you are moving a repository from one machine to another, the schema upgrade fails unless the repository has been initialized on the new machine. This requires that you successfully run initdb.sh on the repository to update the host entry.


Step 9 Use the following command to run the patch installation script:

$ ./iscpatchinstall

a. When you run this script, you will be asked to ensure that you have followed the equivalent of Step 7, and as part of the installation, you will be asked to confirm the equivalent of Step 4.

b. To accept the default value for a prompt indicated in [ ], for example, [n] or [y], press Enter. To terminate the installer at any time, press Ctrl-C. Specifically you will be asked to enter a new path or press Enter for the default [/opt/isc-4.2].

c. At the end of the installation, you will receive a message that the patch installation is complete.


Note For all Cisco 7600 Series Routers, you must do a config collection to synchronize the Service Requests in the repository. This is needed because ISC changed the way it detects Cisco 7600 Series Routers hardware information.



Uninstall

To uninstall the ISC 4.2.3 Maintenance Release that was successfully installed by following the steps in the "Upgrade Paths" section, follow these steps:


Step 1 Log in with the same username as the owner of ISC.

Step 2 If ISC 4.2.3 is running, use the following command to stop the database, name server, and WatchDog on the machine on which it is running:

$ stopall

Step 3 Navigate to the directory $ISC_HOME/patch/isc4.2.3.0-patch, where all the files replaced by the ISC 4.2.3 Maintenance Release were stored.

Step 4 Use the following command to run the patch script to uninstall:

$ ./iscpatchrollback

a. When you run this script, you will be asked to ensure that you have followed the equivalent of Step 1 and Step 2.

b. To accept the default value for a prompt indicated in [ ], for example, [n] or [y], press Enter. To terminate the installer at any time, press Ctrl-C.

c. At the end of the uninstall, you will receive a message that the patch rollback is complete.


Important Notes

1. All ISC patches are available at: http://www.cisco.com/cgi-bin/tablebuild.pl/isc

2. The supported Sybase and Oracle databases behave differently. All GUI queries are case-insensitive for Sybase and case-sensitive for Oracle.

3. ISC does not work with pop-up blockers in a web browser. If you have pop-up blockers installed, disable them.

4. When using an external Oracle database, the embedded Sybase database is still automatically launched for SLA support.

5. For all APIs, the Service Request name is unique and therefore, each Create Service Request API call needs to maintain this uniqueness.

Known Problems in ISC 4.2.3

To find known problems in Cisco IP Solution Center, use the following URL:

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

You must log into CCO.

You can search for specific bugs or search for a range by product name. This tool enables you to query for keywords, severity, range, or version.

The results display bug ID and title, found-in version, fixed-in version, and status. The bug ID is a hyperlink to detailed information for the bug ID's product, component, severity, first found-in, and release notes.

The results could be displayed in a feature matrix or spreadsheet.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html