Release Notes for Cisco IP Solution Center, 5.0.1

Cisco IP Solution Center (ISC) 5.0.1 is a release with new functionality to be added to ISC 5.0.

All documentation, including this Release Notes for Cisco IP Solution Center, 5.0.1 document and any or all of the parts of the ISC 5.0 and ISC 5.0.1 documentation sets, might be upgraded over time. Therefore, we recommend you access the ISC 5.0 and ISC 5.0.1 documentation at: http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/tsd_products_support_series_home.html You can also navigate to this documentation by clicking Help on the Home Page of the ISC product.

The information in this Release Notes for Cisco IP Solution Center, 5.0.1 document gives you an overview of this release and helps you understand what has changed since ISC 5.0. Please read this document prior to reading any other manual for ISC.

Introduction

System Recommendations

The recommendation is to thoroughly review all this information before even planning your installation, to be sure you have all the hardware and software needed for a successful installation.

New Device and Platform Support

L2VPN

The new versions of Cisco IOS XR supported for L2VPN operating in the N-PE device role are:

•

Cisco IOS XR 3.5.2 support on the Cisco Carrier Routing System-1 (CRS-1) series routers

The new version of Cisco IOS software supported for L2VPN operating in the N-PE device role is Cisco IOS 12.2(33)SRC (supported on the Cisco 7600 series routers).

MPLS VPN

The new versions of Cisco IOS XR supported for MPLS VPN operating in the N-PE device role are:

•

Cisco IOS XR 3.5.2 support on the Cisco 12000 (GSR) and Cisco CRS-1 series routers

•

Cisco IOS XR 3.6 support on the Cisco 12000 (GSR) and Cisco CRS-1 series routers

The new version of Cisco IOS software supported for MPLS VPN operating in the N-PE device role is Cisco IOS 12.2(33)SRC (supported on the Cisco 7600 series routers).

MPLS Diagnostics Expert (MDE)

The new versions of Cisco IOS XR supported for MPLS Diagnostics Expert (MDE) are:

•

Cisco IOS XR 3.3 support on the Cisco 12000 (GSR) as a PE and a P router, and Cisco CRS-1 series routers as a PE and a P router

•

Cisco IOS XR 3.3.5 support on the Cisco CRS-1 series routers as a PE and a P router

•

Cisco IOS XR 3.6 support on the Cisco 12000 (GSR) as a PE and a P router, and Cisco CRS-1 series routers as a PE and a P router

The new version of Cisco IOS software supported for MDE operating in the N-PE device role is Cisco IOS 12.2(33)SRC (supported on the Cisco 7600 series routers).

Traffic Engineering Management (TEM)

The new versions of Cisco IOS XR supported for Traffic Engineering Management (TEM) are:

•

Cisco IOS XR 3.5.2 support on the Cisco 12000 (GSR) as a PE and a P router, and Cisco CRS-1 series routers as a PE and a P router

•

Cisco IOS XR 3.6 support on the Cisco 12000 (GSR) as a PE and a P router, and Cisco CRS-1 series routers as a PE and a P router

The new version of Cisco IOS software supported for TEM operating in the N-PE device role is Cisco IOS 12.2(33)SRC (supported on the Cisco 7600 series routers).

New and Changed Information

This section lists the new and changed functionality that was added or updated since ISC 5.0 to this ISC 5.0.1 release. The problems fixed are listed in the "Problems Fixed in ISC 5.0.1" section, and the new device and platforms supported are listed in the "New Device and Platform Support" section. The categories in this section are:

L2VPN and MPLS Updates

Command Language Interface (CLI) Display of IOS XR Configlets

By default, service requests for IOS XR devices log the configuration sent to the device in XML format. Therefore, when configlets are viewed for IOS XR devices, they are displayed in raw XML format. ISC now allows you to view the configlet in CLI format. You can enable this feature by setting the DCPL property: DCS/getCommitCLIConfigAfterDownload to true (the default setting). When this property is enabled, you can view the configlets for IOS XR devices in XML format, CLI format, or both.

L2VPN Updates

Configuring Transport Mode VLANs on IOS XR Devices

In ISC 5.0.1, for IOS XR devices that support the TransportMode command, you can configure transport mode VLANs on IOS XR devices independent of the service. Use the new Dynamic Component Properties Library (DCPL) property: Services/Common/pseudoWireVlanMode. When this property is set to true and an IOS XR device is selected, if the device supports the TransportMode command, Transport mode VLAN is configured. (See Appendix C, Property Settings, in the Cisco IP Solution Center Infrastructure Reference, 5.0.1.)

MPLS Updates

In addition to the new platform and device support, explained in the "MPLS VPN" section, the ISC 5.0.1 MPLS updates since ISC 5.0 are as follows:

6VPE Updates

Internet Protocol version 6 (IPv6) VPN management (referred to as 6VPE) is supported by ISC 5.0.1 on Cisco 12000 series and CRS-1 (Carrier Routing System) routers on IOS XR. This 6VPE functionality allows an IPv6 VPN to be created on an existing IPv4 MPLS core.

•

Creation, deployment, modification, and deletion of a regular PE-CE service request for IPv6 MPLS services.

•

Support for both Unmanaged CE and No CE scenarios in the service policy and service request creation.

Independent VRF Management

Independent VPN routing/forwarding instance (VRF) management provides the ability to create, deploy, and manage VRF objects independent of MPLS VPN links and service requests. This provides the following advantages:

•

You can directly deploy VRF information and templates on a PE device without being associated with an interface.

Note The traditional ISC VRF model is still supported for backward compatibility. The choice of which VRF model to use is available during MPLS VPN link creation.

•

Defining, modifying, decommissioning, and deleting a new type of service request, called a VRF service request.

•

Using deployed VRF objects with MPLS VPN links, using service policies and service requests.

•

Migrating traditional MPLS VPN service requests to the independent VRF model.

Multicast Routing for IPv4 on IOS XR Devices

Multicast VRF deployments for IOS XR devices are supported only for IPv4 (not IPv6 or IPv4+IPv6 deployments). There are no changes in the Graphical User Interface (GUI) (that is, Create VPN window) to support this feature. To enable support, the IOS multicast commands are mapped to equivalent IOS XR commands. Because there are no XML configurations to support multicast routing on IOS XR devices, ISC supports the IOS XR CLIs to enable multicast routing on IOS XR devices.

Template Manager Updates

The Template Manager has been updated to include the following new capabilities:

Searching

•

The search capability for templates and data files is enhanced so that you can search for text in the description field.

By choosing Service Inventory > Inventory and Connection Manager > Service Request, you can do the following:

•

The search capability for service requests is enhanced so you can view service requests associated with a given data file or template.

In Use Indicator

•

A new field indicates whether a given data file is associated with a service request.

•

The template manager can track the data file's usage across multiple service requests.

•

If a data file has associated templates, the indicator is a hyperlink. If you click that link, the list of associated service requests appears.

By choosing Service Inventory > Inventory and Connection Manager > Service Request, you can do the following:

•

A new field indicates whether a given service request has associated data files.

•

The indicator is a paper clip, which is a hyperlink. If you click that link, the list of associated data files appears.

Deletion Validation

•

If any data file selected for deletion is in use (that is, associated with a service request), a warning message indicating this appears and you have the opportunity to cancel the deletion.

•

If a folder or a template has a data file associated with a service request, a warning message is displayed when the folder or template is deleted.

RBAC Support

•

Role Based Access Control (RBAC) and more specifically, the Template resource, now control the template manager functions.

•

The permission setup of the Template resource determines the ability to view, create, modify, and delete templates.

By choosing Service Inventory > Inventory and Connection Manager > Service Request, you can do the following:

•

RBAC and more specifically, the AssociateTemplate resource, now controls the ability to associate templates with service requests.

•

The permission setup of the AssociateTemplate resource determines the ability to add and remove templates.

MPLS Diagnostics Expert (MDE) Updates

In addition to the new platform and device support, explained in the "MPLS Diagnostics Expert (MDE)" section, the ISC 5.0.1 MDE updates since ISC 5.0 are as follows:

MPLS Operation, Administration, and Maintenance (OAM) RFC

MPLS Diagnostics Expert (MDE) now diagnoses in Cisco devices and networks that use IETF RFC 4379 compliant Label Switched Path (LSP) ping and LSP traceroute. MDE continues to support the earlier draft (draft 3) available in Cisco IOS. You must use a consistent draft of LSP ping and traceroute across all devices in your network.

Loopback Name

In the MDE PE to PE core test, you can now enter the loopback IP address and you can enter the loopback name, which will be resolved to the IP address. If the entered loopback name does not exist on the router, the new Failure Scenario CF-001.002 is reported, as follows:

New Observations

An observation is displayed when troubleshooting of the Layer 3 VPN has been unable to find the cause of the failure and MDE has determined that IP connectivity is broken causing a Label Switched Path (LSP) failure. New in this release is an addition to the observation if there is no route to the remote PE in the Interior Gateway Protocol (IGP) route table of the local PE.

Problems Fixed in ISC 5.0.1

Table 1 Customer-found Problems Fixed in ISC 5.0.1
CDETS Number	Subject
CSCsi21088	New U.S. daylight saving change in 2007 is not working.
CSCsi22136	MPLS audit error reported when static route uses metric 1 with no CE policy.
CSCsi24435	Template data file settings are retained from one Service Request to the next.
CSCsj13427	Template variables plus data files are not in sorted order.
CSCsj35593	Open Shortest Path First (OSPF) processes are mistakenly limited to 28 for PE-CE routing.
CSCsj42526	Need to be able to optionally disable the Select All Service Requests check box for non-admin users.
CSCsj45405	MPLS Diagnostics Expert (MDE) does not report Interior Gateway Protocol (IGP) routes missing when a Core IP ping failure occurs.
CSCsj89707	PE-PE test needs to accept a loopback name and to resolve it to an address.
CSCsk00839	Discovery fails for Traffic Engineering Management (TEM) when time stamps are used in IOS XR device prompts.
CSCsk01001	When creating Named Physical Circuits (NPCs) and trying to select an interface from a device, some interfaces are missing.
CSCsk37009	Unable to provision an asynchronous transfer mode (ATM) subinterface on Cisco 800 series routers.
CSCsk40839	When a description is entered in the VPN routing/forwarding instance (VRF) description field, the audit fails.
CSCsk51886	In MPLS Diagnostics Expert (MDE) Failure Scenario FS-026, null incorrectly appears, rather than the IOS or IOS XR command required to clear the specified prefix in the Recommended Action portion of the results.
CSCsk53209	Interface description should contain the Service Request identification number.
CSCsk75470	Unable to view task log details when using Secure Hypertext Transfer Protocol (HTTPS).
CSCsk76938	When a Service Request is modified to move between PEs, the max-paths command is incorrectly removed on the source.
CSCsk96439	IOS XR 3.6 support not available.
CSCsl03093	IPv6 options appear when selecting non-Ethernet interfaces.
CSCsl22111	Layer 3 Service Request using Named Physical Circuits (NPCs) does not save.
CSCsl22879	Unable to cleanly remove one interface from an IOS XR router that is running IPv4 Open Shortest Path First version 2 (OSPFv2). All interfaces are removed.
CSCsl24122	Point-to-Point Protocol (PPP) encapsulation rejected for IOS XR devices.
CSCsl29336	ISC is not properly cleaning up links.
CSCsl30131	Virtual type terminal (VTY) login to Cisco device fails when using custom username prompt.
CSCsl30519	No configuration file is created for multilink interfaces.
CSCsl92154	ISC needs to export extra template variable BGP_NBR_IP_ADDR

Installation Notes

Version Supported

ISC 5.0.1 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, 4.2.2, 4.2.3, 4.2.4, or 5.0 after ISC 5.0 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, 5.0.

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

Installation

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, 4.1.2, 4.2, 4.2.1, 4.2.2, 4.2.3, or 4.2.4, you must install ISC 5.0 first, as explained in the Cisco IP Solution Center Installation Guide, 5.0. On the same server, execute the ISC5.0 Upgrade Script, which is located on the product CD. After upgrading to ISC 5.0, download and install ISC 5.0.1, which is also located at http://www.cisco.com/cgi-bin/tablebuild.pl/isc.

To add ISC to your system, either as a new ISC customer or a customer upgrading from ISC 5.0, follow these steps:

Note The installer also checks for two kinds of disk space:

In the intended install location, you need 1.2 GB free for the binaries plus an extra 250 MB for log file growth and the installation of the Cisco CNS Configuration Engine 1.3.x, 1.4, 1.5, or 2.0 software.

In the database directory, you need 1 GB free. For large systems, you should have 4 to 5 GB of space. If the directory has less than 1.2 GB free, you can still install ISC, but you might run out of space.

Step 1

If upgrading, complete the discovery workflow. Otherwise, when you upgrade these previously initiated discovery workflows, the data discovered during that process might be lost.

Step 2

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 ISC 5.0.1 (isc-5.0.1.tar.gz).

Step 3

Prior to installing ISC 5.0.1, if you are upgrading from ISC 5.0, verify that you are logged in with the same username as the owner of your supported version of ISC.

Step 4

From the location where the isc-5.0.1.tar.gz file is located, use the following command to extract the installer:
gunzip -c isc-5.0.1.tar.gz | tar xf -

The ISC software is installed by default in the /opt/isc-5.0.1 directory or a directory set up as follows.

If you are upgrading ISC from ISC 5.0, make sure that ISC is shut down completely. Then do one of the following:

Install ISC 5.0.1 in the same directory with the same directory name as the existing ISC product, as follows:

For example, if you are upgrading from ISC 5.0 to ISC 5.0.1 and the ISC installation is under the directory /opt/isc-5.0, then install ISC 5.0.1 in the same directory and rename it to /opt/isc-5.0.1, with steps like the following:

For example, if you are upgrading from ISC 5.0 to ISC 5.0.1and the ISC 5.0 installation is under the directory /opt/isc-5.0, then install ISC 5.0.1 in a new directory /opt/isc-5.0.1, with steps like the following.

–

Copy the Repository from the ISC 5.0 directory to the new ISC 5.0.1 directory, as follows:

Step 6

In the next window, as shown in Figure 1, " Choose Installation Type," choose either the default express option or the custom option, then click Next.

When you click express, you have a minimal number of choices to make. When you click custom, you can specify various ports and locations and you can change the watermark level for available disk space.

Step 7

In the next window, shown in Figure 2, " Choose ISC Owner," enter the username that corresponds to the owner of your ISC installation.

Note If you enter an invalid name, you will receive a message indicating the name is invalid.

Step 8

Specify the location of the directory where you want to install, as shown in Figure 3, " Specify Directory Location," and then click Next. You can click Browse as an aid to finding an appropriate directory.

Note If you are not installing as root, you must have write permission for this directory.

Step 9

If in Step 8 you chose a directory that already exists, you proceed as follows. If you chose a new directory to be created, you proceed to Step 10.

In Figure 4, " Confirm Directory Removal," if the directory you chose already exists and you must click the default radio button Disapprove, you cannot proceed. You must click Back and return to Step 8.

Be very careful. If you click the radio button Approve, you will overwrite the contents in the existing directory. Click Next.

Step 11

Specify the Directory Name where you want database files to be stored, as shown in Figure 6, " Where to Store Database Files," and then click Next.

Step 12

If in Step 11 you chose a directory that already contains a repository, you have three options, as shown in Figure 7, " Repository Choices,": Keep existing ISC repository, Overwrite existing ISC repository, or Upgrade existing ISC repository. Then click Next to proceed. Otherwise proceed to Step 13.

Step 13

After choosing Keep existing ISC repository in Figure 7, " Repository Choices," you will be given the opportunity in Figure 8, " Confirmation of Keeping Existing ISC Repository," to Disapprove (the default). If you choose Approve, you will keep your existing ISC repository, which could be incompatible with this version of ISC.

Step 14

After choosing Overwrite existing ISC repository in Figure 7, " Repository Choices," you will be given the opportunity in Figure 9, " Confirmation of Overwriting Existing ISC Repository," to Disapprove (the default). If you choose Approve, you will overwrite the existing repository with an empty repository and your existing repository will be saved as $ISC_HOME/Repository.save.<timestamp>.

Step 15

After choosing Upgrade existing ISC repository in Figure 7, " Repository Choices," you will be given the opportunity in Figure 10, " Confirmation of Upgrading Your ISC Repository After Installation," to Disapprove (the default). If you choose Approve, you will overwrite the existing repository with an empty repository and your existing repository will be saved as $ISC_HOME/Repository.save.<timestamp>. Then your installation will proceed with a new empty repository.

Step 16

After you Approve to upgrade your existing Repository, enter the location of the Upgrade Tool, as shown in Figure 11, " Location of Upgrade Tool."

Step 17

If you inaccurately entered the location of the Upgrade Tool, you will receive a message as shown in Figure 12, " Invalid Location of Upgrade Tool," and you must return to Step 16 and enter the correct Upgrade Tool location.

Step 18

Choose the database you will use, as shown in Figure 13, " Choosing a Database". From the drop-down menu, choose either Embedded Sybase (Sybase ASA, 8.0.1 is embedded) or External Oracle. (Testing of ISC 5.0.1 has been done with Oracle Database 10g, Enterprise Edition Release 10.2.0.1.0 - 64 bit Production.) If you would like to use another version of Oracle 10g, see Oracle's compatibility information.) Then click Next.

Note If you are upgrading from ISC 5.0, make sure your ISC Repository has been imported to the Oracle Database 10g, Enterprise Edition Release 10.2.0.1.0 - 64 bit Production, as indicated in the Initial Configuration —Creating the ISC Owner section of Chapter 2 in the Cisco IP Solution Center Installation Guide, 5.0.

Note The embedded Sybase database is used for service-level agreement (SLA), independent of whether you are using Oracle as your database.

Step 19

If you chose Embedded Sybase in Step 18, enter the Database server name, as shown in Figure 14, " Choosing a Database—Sybase." The Database Port number is automatically updated. If you choose to change the database port number, enter your choice in the Database Port field. Click Next, and then proceed directly to Step 22.

Step 20

If you chose External Oracle in Step 18, you must enter the Database server name, the Database Port number, and the Oracle server instance identifier (SID), as shown in Figure 15, " Choosing a Database—Oracle." Otherwise, proceed directly to Step 22.

Note If you enter a Naming Port value less than 1024, the owner of the installation must be root. The owner of the installation is the user identified in Figure 2.

Step 23

Specify the port used by the HTTP server, as shown in Figure 18, " Choose HTTP Port," then click Next.

Note If you enter an HTTP Port value less than 1024, the owner of the installation must be root. The owner of the installation is the user identified in Figure 2.

Step 24

Specify the port used by the HTTP Over Secure Socket Layer (SSL) (HTTPS) server, as shown in Figure 19, " Choose HTTPS Port," then click Next.

Note If you enter an HTTPS Port value less than 1024, the owner of the installation must be root. The owner of the installation is the user identified in Figure 2.

Step 25

Specify the port used by the Rendezvous™ Agent (RVA). You must specify the RVA HTTP Port server, a TIBCO™ bus port used by ISC processes to communicate with each other. You must also specify the RVA Client Port, as shown in Figure 20, " Choose RVA Ports," then click Next.

Note If you enter an RVA HTTP Port or RVA Client Port value less than 1024, the owner of the installation must be root. The owner of the installation is the user identified in Figure 2.

Step 26

Specify the port used by TIBCO, as shown in Figure 21, " Choose TIBCO Port," then click Next.

Note If you enter a TIBCO Port value less than 1024, you must run ISC as root, the specification in Figure 2.

Step 27

When you click Next, the system checks whether any of the ports entered are duplicate port numbers. If duplicate port numbers are found, an error message indicates the two ports that have duplicate entries.

Step 28

You can reset the High and Low watermarks for available disk space, as shown in Figure 22, " Setting Watermarks for Available Disk Space." The defaults are 20% and 10% for High and Low respectively. Be sure the High watermark is a larger percentage than the Low watermark. When the High and Low watermarks are reached, you receive an e-mail indicating this, based upon setting your e-mail address correctly in Step 29.

•

In the first text field, specify the hostname of the Simple Mail Transfer Protocol (SMTP).

•

In the second text field, specify the username to display in the "From" field.

•

In the third text field, specify the e-mail address to be notified when High and Low watermarks are reached, which indicates the specified disk space availability has been reached.

•

In the fourth text field, specify the e-mail address to be notified when the ISC server restarts.

Step 30

The installation continues and the files are installed. The list of installation processes appears.

If there was truncation of data, reinstall and add two spaces at the end of each field for which you have modified the entry.

Step 32

If the installation was successful, you receive an Install Complete message. Even if you have a successful install, click Back to review the log to be sure there were no exceptions or failures. If data was truncated, reinstall and add two spaces at the end of each field for which you have modified the entry.

Step 33

The ISC server is started automatically after the installation is successful.

Before logging in, repeat the following command until the servers are in the started mode. If any server is reported as disabled, ISC is not installed or configured correctly:

Upgrading ISC 5.0 Repository to ISC 5.0.1

If you have an ISC 5.0 Repository, you use the same upgrade procedure steps independent of whether your repository is a Sybase or Oracle repository.

Note Before you upgrade your Repository, you must have followed the steps in the "Installation" section. You must have backed up your database, as explained Appendix C of the Cisco IP Solution Center Installation Guide, 5.0, and you must have followed all the steps and reached this section from the final step in your installation. A Repository can be upgraded only once. If there is any problem during upgrade, a new copy of the backed up Repository is needed for subsequent upgrade attempts.

Step 1

Get the upgrade package ISC501_UpgradeTool.tar.gz from http://www.cisco.com/cgi-bin/tablebuild.pl/isc and place it on the ISC Master machine in a directory where you can access the ISC environment.

Note After upgrading between ISC versions, you should ensure that the cache of the ISC client browser has been cleared or that your browser does not use the cache. This will ensure the latest ISC images and pages are returned.

Uninstall

Step 5

Remove ISC by entering the following command from a location outside the <ISC_HOME directory>:

This command removes all files from the installation directory. This command also removes the database and its contents. Database backups are not removed if they reside in a different directory from the installation directory.

Important Notes

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

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

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

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

Known Caveats in Cisco IP Solution Center 5.0.1

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.

Table Of Contents