Guest

Cisco IP Solution Center

Release Notes for Cisco IP Solution Center, 5.0.1

  • Viewing Options

  • PDF (801.1 KB)
  • Feedback
Release Notes for Cisco IP Solution Center, 5.0.1

Table Of Contents

Release Notes for Cisco IP Solution Center, 5.0.1

Contents

Introduction

System Recommendations

New Device and Platform Support

L2VPN

MPLS VPN

MPLS Diagnostics Expert (MDE)

Traffic Engineering Management (TEM)

New and Changed Information

L2VPN and MPLS Updates

Command Language Interface (CLI) Display of IOS XR Configlets

L2VPN Updates

Configuring Transport Mode VLANs on IOS XR Devices

Discovery Limitation with L2VPN

MPLS Updates

6VPE Updates

Independent VRF Management

Multicast Routing for IPv4 on IOS XR Devices

Template Manager Updates

Searching

In Use Indicator

Deletion Validation

RBAC Support

MPLS Diagnostics Expert (MDE) Updates

MPLS Operation, Administration, and Maintenance (OAM) RFC

Loopback Name

New Observations

Problems Fixed in ISC 5.0.1

Installation Notes

Version Supported

Installation

Upgrading ISC 3.2.2 or Later Repositories to ISC 5.0.1

Uninstall

Important Notes

Known Caveats in Cisco IP Solution Center 5.0.1

Related Documentation

Obtaining Documentation and Submitting a Service Request


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.

Contents

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

Contents

Introduction

System Recommendations

New and Changed Information

Problems Fixed in ISC 5.0.1

Installation Notes

Important Notes

Known Caveats in Cisco IP Solution Center 5.0.1

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

Cisco IP Solution Center (ISC) 5.0.1 has new functionality added since ISC 5.0 (see the "New and Changed Information" section) and fixes to problems found in ISC 5.0.1 (see the "Problems Fixed in ISC 5.0.1" section). ISC 5.0.1 includes Cisco MPLS Diagnostics Expert (MDE) 2.1.1. The system recommendations for ISC 5.0.1 (see the "System Recommendations" section) are based on those for ISC 5.0. And the new devices and platforms supported in addition to those supported in ISC 5.0 are listed in the "New Device and Platform Support" section.

Steps for installing ISC 5.0.1 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 5.0.1, see the URL in the "Known Caveats in Cisco IP Solution Center 5.0.1" section.

URLs for base information about ISC 5.0 and an overview and suggested reading order of these documents is given in the Cisco IP Solution Center Getting Started and Documentation Guide, 5.0 (http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/roadmap/docguide.html). The ISC 5.0.1 documentation set includes ISC 5.0 documents and some updated information for ISC 5.0.1, as indicated in the "Related Documentation" section.

System Recommendations

The system recommendations and requirements listed in Chapter 1, "System Recommendations" of the Cisco IP Solution Center Installation Guide, 5.0
(http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/installation/guide/install.html) are also applicable to ISC 5.0.1.

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.

Additionally, the new devices and platforms supported are explained in the section, New Device and Platform Support.

New Device and Platform Support

New devices and platforms supported are as follows:

L2VPN

MPLS VPN

MPLS Diagnostics Expert (MDE)

Traffic Engineering Management (TEM)

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

Cisco IOS XR 3.6 support on the Cisco 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).

Cisco ASR 1000 Router Series operating in an N-PE role with IOS XE version 2.1.0 (discovered as a Cisco 7200 in ISC).

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" section

"L2VPN Updates" section

"MPLS Updates" section

"Template Manager Updates" section

"MPLS Diagnostics Expert (MDE) Updates" section

L2VPN and MPLS Updates

The new feature that is available for both L2VPN and MPLS in this release is explained in the section, "Command Language Interface (CLI) Display of IOS XR Configlets".

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

In addition to the new platform and device support, explained in the "L2VPN" section, the ISC 5.0.1 L2VPN updates since ISC 5.0 are explained in the section "Configuring Transport Mode VLANs on IOS XR Devices". Also, a discovery limitation using L2VPN is specified in the section, Discovery Limitation with L2VPN.

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.)

Discovery Limitation with L2VPN

When using Discovery with L2VPN, the following two limitations exist:

The User-Network Interface (UNI) type might be provisioned as a Port-Channel. However, the L2VPN point-to-point discovery does not recognize this configuration.

If you assign any router as a Provider (P) router during the role assignment step and that router contains virtual circuit (VC) configuration information, the discovery might fail.

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

Independent VRF Management

Multicast Routing for IPv4 on IOS XR Devices

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.

The 6VPE support for IOS XR release 3.5.2 (and later) added in this release is:

Definition of regular PE-CE service policy for IPv6 MPLS services.

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.

Support for PE-CE routing protocols: EIGRP, eBGP, and Static.

API support is also available for these 6VPE features.

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.

VRF information can exist without links pointing to it.

A VRF object can be modified, even if it is associated with links.

Route targets (RTs) can be added and removed without causing outages.


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.


Managing VRFs independently of physical links involves the following tasks, which are covered in detail in the Cisco IP Solution Center MPLS VPN User Guide, 5.0.1:

Creating, modifying, copying, and deleting VRF objects.

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

Defining links using the VRF object, PE, and optionally, templates.

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

In Use Indicator

Deletion Validation

RBAC Support


Note Details are explained in the Cisco IP Solution Center Infrastructure Reference, 5.0.1.


Searching

You can do the following by choosing Service Design > Templates:

You can search for data files of templates by description.

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

The search is case sensitive and wild card characters are supported.

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

You can search for service requests by data file or template name.

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

You can do the following by choosing Service Design > Templates:

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

You can do the following by choosing Service Design > Templates:

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

You can do the following by choosing Service Design > Templates:

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

Loopback Name

New Observations

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:

Summary - Interface <supplied name> does not exist on PE <PE name>.

Cause - An invalid PE interface has been specified.

Action - Return to test configuration and specify a valid interface.

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," describes all the customer-found problems that were 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

This section contains the following information:

Version Supported

Installation

Uninstall

Version Supported

ISC 5.0.1 supports either a clean installation (no previous version of ISC installed) or 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, 4.2.5, or 5.0. If you are upgrading from ISC 4.2.5 or earlier, you must first upgrade to ISC 5.0 before upgrading to ISC 5.0.1. The only upgrade path to ISC 5.0.1 is through ISC 5.0. 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.

Installation

You can upgrade 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, 4.2.5, or 5.0. (See the comments in the previous section, Version Supported, for the need to upgrade to ISC 5.0 before upgrading to ISC 5.0.1. After you have upgraded to ISC 5.0, if necessary, you can continue with the installation instructions in this section.) On the same server, execute the ISC 5.0.1 Upgrade Script, which is 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, 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.

Before proceeding to install ISC 5.0.1, be sure to back up your repository, as explained in Appendix C of the Cisco IP Solution Center Installation Guide, 5.0 (http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/installation/guide/install.html).

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).


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


Step 3 Prior to installing ISC 5.0.1, if you are upgrading, 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 -

Step 5 Execute the ISC product installation script:

cdrom> ./install.sh

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, make sure that ISC is shut down completely. Then do one of the following:

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

Save the ISC installation for possible uninstall purposes, as follows:

tar cvf <directory_name>.tar /opt/<directory_name>

Select this directory name in Step 8, Figure 3, "Specify Directory Location.

-or-

b. Install ISC 5.0.1 in the same directory with a new name.

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:

Save the ISC 5.0 installation for possible uninstall purposes, as follows:

tar cvf isc-5.0.tar /opt/isc-5.0

Rename the directory, as follows:

mv /opt/isc-5.0 /opt/isc-5.0.1

Select the directory /opt/isc-5.0.1 in Step 8, Figure 3, "Specify Directory Location."

-or-

c. Install ISC 5.0.1 in a separate directory.

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.

Create the new ISC 5.0.1 directory, as follows:

mkdir /opt/isc-5.0.1

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

cp -r /opt/<existingISCdirectory>/Repository /opt/isc-5.0.1

where: <existingISCdirectory> is the existing ISC directory, for example isc-5.0 for ISC 5.0.

Select the directory /opt/isc-5.0.1 in Step 8, Figure 3, "Specify Directory Location."

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.


Note Using a custom install is highly recommended, especially when the repository involves a large number of devices and interfaces. In this case, in Step 12, also use Keep existing ISC repository.


Figure 1 Choose Installation Type

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 This field is only used when you are installing as root.


Figure 2 Choose ISC Owner


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.


Figure 3 Specify Directory Location

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.

Figure 4 Confirm Directory Removal

Step 10 If in Step 6 you chose express, proceed to Step 29. If you chose custom, then you must enter the location where you want temporary files stored, as shown in Figure 5, "Choosing the Directory for Temporary Files."

Figure 5 Choosing the Directory for Temporary Files

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.

Figure 6 Where to Store Database Files

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.

When you click Keep existing ISC repository, proceed to Step 13.


Note Using Keep existing ISC repository is recommended when you have a repository with a large number of devices and interfaces.


When you click Overwrite existing ISC repository, proceed to Step 14.

When you click Upgrade existing ISC repository, proceed to Step 15.

Figure 7 Repository Choices

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.


Note After you complete your installation and before you use ISC, to upgrade your repository, you must follow the steps in the "Upgrading ISC 3.2.2 or Later Repositories to ISC 5.0.1" section.


Click Next and proceed to Step 18.

Figure 8 Confirmation of Keeping Existing ISC Repository

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>.

Click Next and proceed to Step 18.

Figure 9 Confirmation of Overwriting Existing ISC Repository

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.

Click Next and proceed to Step 18.

Figure 10 Confirmation of Upgrading Your ISC Repository After Installation

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."

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.

Figure 12 Invalid Location of Upgrade Tool

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, 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.


Figure 13 Choosing a 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.

If you chose External Oracle in Step 13, proceed to Step 20.

Figure 14 Choosing a Database—Sybase

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 are upgrading, 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.


Figure 15 Choosing a Database—Oracle

Step 21 Because you chose External Oracle in Step 18, you must set the Oracle database User and Password values, as shown in Figure 16, "Specifying Database Credentials."

Figure 16 Specifying Database Credentials

Step 22 Specify the port used by the Naming Server, as shown in Figure 17, "Specify the Port Used by the Naming Server," then click Next.


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.


Figure 17 Specify the Port Used by the Naming Server

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.


Figure 18 Choose HTTP Port

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.



Note To configure the web access to ISC, you must set up the HTTPS port as explained in Step 36 and the Configuring HTTPS section in Chapter 2 of the Cisco IP Solution Center Installation Guide, 5.0.


Figure 19 Choose HTTPS Port

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.


Figure 20 Choose RVA Ports

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.


Figure 21 Choose TIBCO Port

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.

Figure 22 Setting Watermarks for Available Disk Space

Step 29 In Figure 23, "Setting E-mail Address for Receiving Watermark Information," to receive e-mail you must specify the following:

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.


Note This information can be updated by using the watchdog/diskspace properties in the DCPL. See Appendix C in the Cisco IP Solution Center Infrastructure Reference, 5.0.1.


Then click Next.

Figure 23 Setting E-mail Address for Receiving Watermark Information

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

Step 31 If the installation failed, you receive a failed message.

To review the log message, click Back.

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.

Step 34 Verify that ISC is properly installed, as follows:

a. Source the ISC environment file in the $ISC_HOME/bin directory:

If sh or ksh shell: . $ISC_HOME/bin/vpnenv.sh

If csh shell: source $ISC_HOME/bin/vpnenv.csh

b. 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:

wdclient status

For more information about WatchDog commands, see the Cisco IP Solution Center Infrastructure Reference, 5.0.1.

Step 35 If you are upgrading an ISC 3.2.2 or later repository, set the environment variable, and modify for your shell (this example is for csh shell):

setenv JVM_ARGS "-Xms128m -Xmx512m"

Then follow the steps in the "Upgrading ISC 3.2.2 or Later Repositories to ISC 5.0.1" section.

Step 36 If you want to set up secure web access by using HTTPS, see the "Configuring HTTPS" section in Chapter 2 of the Cisco IP Solution Center Installation Guide, 5.0. Then, proceed to Step 37.

Step 37 If you are logging in for the first time, proceed to the "Logging In for the First Time" section in Chapter 2 of the Cisco IP Solution Center Installation Guide, 5.0. Then, proceed to Step 38.

Step 38 Before you can use any of the licensed services, proceed to the "Installing License Keys" section in Chapter 2 of the Cisco IP Solution Center Installation Guide, 5.0. Then, proceed to Step 39.

Step 39 If you want to eventually use the Inventory Manager or the Topology Tool, your client machine must be set up properly. Proceed to the "Launching Topology Tool" section in Chapter 2 of the Cisco IP Solution Center Installation Guide, 5.0. This section explains what occurs and leads you to the launching explanations in the Cisco IP Solution Center Infrastructure Reference, 5.0.1. Then, proceed to Step 40.

Step 40 To uninstall ISC, proceed to the "Uninstall" section.


Note To determine if servers are installed correctly, use the WatchDog commands explained in the Cisco IP Solution Center Infrastructure Reference, 5.0.1.



Upgrading ISC 3.2.2 or Later Repositories to ISC 5.0.1

To upgrade your ISC 3.2.2 or later Repository, 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.


Upgrade your ISC 3.2.2 or later repository as follows:


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.

Step 2 Untar the upgrade tool tar file.

gzip -d < ISC501_UpgradeTool.tar.gz | tar xvf -

Step 3 Source the ISC environment files.

If sh or ksh shell: . $ISC_HOME/bin/vpnenv.sh

If csh shell: source $ISC_HOME/bin/vpnenv.csh

Step 4 Stop ISC.

stopall

Step 5 Run the upgrade script.

cd ISC501_UpgradeTool

./upgradeISCSchema.sh <ISC home>

where: <ISC home> is the full pathname of the ISC home directory.

Step 6 Check for a success or error message.



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

Uninstall the server as follows:


Step 1 Log in to the server.

Step 2 At the Solaris prompt, log in as the ISC owner.

Step 3 Go to the ISC installation directory.

Step 4 Source the environment, as follows:

For a sh or ksh shell:

. bin/vpnenv.sh

For a csh shell:

source bin/vpnenv.csh

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

uninstall.sh

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

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 Caveats in Cisco IP Solution Center 5.0.1

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

http://tools.cisco.com/Support/BugToolKit

You must log in to Cisco.com.

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.

Related Documentation

The entire documentation set for Cisco IP Solution Center, 5.0.1 can be accessed at:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/
tsd_products_support_series_home.html


Tip To cut and paste a two-line URL into the address field of your browser, you must cut and paste each line separately to get the entire URL without a break.


The following documents comprise the ISC 5.0.1 documentation set.

General documentation (in suggested reading order)

Cisco IP Solution Center Getting Started and Documentation Guide, 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/roadmap/docguide.html

Release Notes for Cisco IP Solution Center, 5.0.1.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0.2/release/notes/relnotes.html

Cisco IP Solution Center Installation Guide, 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/installation/guide/install.html

Cisco IP Solution Center Infrastructure Reference, 5.0.1.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0.1/infrastructure/reference/
guide/isc501ir.html

Cisco IP Solution Center System Error Messages, 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/system/messages/mess.html

Application and technology documentation (listed alphabetically)

Cisco IP Solution Center Metro Ethernet and L2VPN User Guide, 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/metro_ethernet/user/guide/
l2vpn.html

Cisco IP Solution Center MPLS VPN User Guide, 5.0.1.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0.1/mpls_vpn/user/guide/
mpls501.html

Cisco IP Solution Center Traffic Engineering Management User Guide, 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/traffic_management/user/
guide/tem.html

Cisco MPLS Diagnostics Expert 2.1 Failure Scenarios Guide on ISC 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/mpls_failure_scenarios/user/
guide/mdefsg.html

Cisco MPLS Diagnostics Expert 2.1 User Guide on ISC 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/mpls_diagnostics/user/guide/mde.html

API Documentation

Cisco IP Solution Center API Programmer Guide, 5.0.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0/developer/guide/api_gd.html

Cisco IP Solution Center API Programmer Reference, 5.0.

http://www.cisco.com/en/US/products/sw/netmgtsw/ps4748/
products_programming_reference_guides_list.html


Note All documentation might be upgraded over time. All upgraded documentation will be available at the same URLs specified in this document.


Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, 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