Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IP Solution Center

Release Notes for Cisco IP Solution Center, 5.0.3

Downloads

Table Of Contents

Release Notes for Cisco IP Solution Center, 5.0.3

Contents

Introduction

System Recommendations

New Device and Platform Support

New and Changed Information Since ISC 5.0.2

L2VPN: Pseudowire Class Support for E-LINE Only

GUI Support

API Support

L2VPN: Deletion of Traffic Engineering (TE) Tunnel Not Allowed if Used in PseudoWireClass

L2VPN: Transport Mode VLAN with a DCPL Property

Problems Fixed in ISC 5.0.3

Installation Notes

Version Supported

Upgrade Paths

Uninstall

Important Notes

Known Caveats in Cisco IP Solution Center 5.0.3

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco IP Solution Center, 5.0.3

Cisco IP Solution Center (ISC) 5.0.3 is a follow-on maintenance release to ISC 5.0.2. This specific release concentrates on updates for Layer 2 VPN (L2VPN).

This release contains all the new functionality and problem fixes in ISC 5.0.2, see Release Notes for Cisco IP Solution Center, 5.0.2, and the new functionality and problem fixes specific to this ISC 5.0.3 release.

All documentation, including this Release Notes for Cisco IP Solution Center, 5.0.3 document and any or all of the parts of the ISC 5.0, ISC 5.0.1, ISC 5.0.2, and ISC 5.0.3 documentation sets, might be upgraded over time. Therefore, we recommend you access these documents 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 "Related Documentation" section gives the URL for the most current version of each document to be used with ISC 5.0.3.

The information in this Release Notes for Cisco IP Solution Center, 5.0.3 document gives you an overview of this release and helps you understand what has changed since ISC 5.0.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

•New and Changed Information Since ISC 5.0.2

•Problems Fixed in ISC 5.0.3

•Installation Notes

•Important Notes

•Known Caveats in Cisco IP Solution Center 5.0.3

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

Cisco IP Solution Center (ISC) 5.0.3 has new functionality added since ISC 5.0.2 (see the "New and Changed Information Since ISC 5.0.2" section) and fixes to problems and enhancements found in ISC 5.0.x releases (see the "Problems Fixed in ISC 5.0.3" section). The system recommendations for ISC 5.0.3 (see the "System Recommendations" section) are based on those for ISC 5.0.1 and ISC 5.0.2 (see the Release Notes for Cisco IP Solution Center, 5.0.1 and the Release Notes for Cisco IP Solution Center, 5.0.2, respectively). The new devices and platforms supported in addition to those supported in ISC 5.0.2 are listed in the "New Device and Platform Support" section.

The new functionality in ISC 5.0.3 is for L2VPN users.

Steps for installing ISC 5.0.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 5.0.3, see the URL in the "Known Caveats in Cisco IP Solution Center 5.0.3" 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.3 documentation set includes ISC 5.0 documents, some updated information for ISC 5.0.1, Release Notes for Cisco IP Solution Center, 5.0.2, and these Release Notes for Cisco IP Solution Center, 5.0.3 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.3.

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 Release Notes for Cisco IP Solution Center, 5.0.1, the Release Notes for Cisco IP Solution Center, 5.0.2, and in the section, New Device and Platform Support in this document.

New Device and Platform Support

ISC now supports IOS XR 3.6.1 on Cisco Carrier Routing System-1 (CRS-1) Series Routers for L2VPN.

New and Changed Information Since ISC 5.0.2

The ISC 5.0.2 functionality is included in this ISC 5.0.3 release. The new and changed information in ISC 5.0.2 was infrastructure updates: custom router login prompt and offline configuration collect mechanism; and MPLS Diagnostics Expert (MDE) 2.1.2 updates: MDE device selector GUI enhancement and MDE observations (CSCsi96376), which are all explained in detail in the Release Notes for Cisco IP Solution Center, 5.0.2.

In addition to the new IOS XR 3.6.1 support listed in the "New Device and Platform Support" section, ISC 5.0.3 has the following new and changed functionality that was added or updated since ISC 5.0.2:

•"L2VPN: Pseudowire Class Support for E-LINE Only" section

•"L2VPN: Deletion of Traffic Engineering (TE) Tunnel Not Allowed if Used in PseudoWireClass" section

•"L2VPN: Transport Mode VLAN with a DCPL Property" section

L2VPN: Pseudowire Class Support for E-LINE Only

The Pseudowire class feature introduced in this release provides you with the capability to configure various attributes associated with a pseudowire that is deployed as part of an L2VPN service request on IOS XR capable devices. The pseudowire class feature supports configuration of the Encapsulation, Transport Mode, fallback options, and selection of a traffic engineering tunnel down which the pseudowire can be directed. For tunnel selection, you can select the tunnel using the ISC Traffic Engineering Management application if it is being used. Otherwise, you can specify the identifier of a tunnel that is already provisioned within the network.

You can use this functionality through:

•"GUI Support" section

•"API Support" section

GUI Support

This section explains the Graphical User Interface (GUI) support in the following subsections:

•"Pseudowire Class Creation" section

•"Pseudowire Class Association to an L2VPN Policy" section

•"Pseudowire Class Association to an L2VPN Service Request" section

•"Pseudowire Class Modification and How It Impacts L2VPN Service Requests" section

Pseudowire Class Creation

To use the GUI to create a pseudowire class, follow these steps:

Step 1 Navigate to Service Inventory > Inventory and Connection Manager > PseudoWireClass and you receive a window as shown in Figure 1.

Figure 1 Pseudowire Classes

Step 2 In Figure 1, click the Create button and you receive a window as shown in Figure 2.

Figure 2 Selecting a Tunnel ID

Step 3 In Figure 2, specify the following:

•Name (required) - Enter a valid PseudoWireClass name of less than 32 characters.

•Description (optional) - Enter a meaningful description of less than 128 characters.

•Encapsulation - Both choices in the drop-down list, DEFAULT and MPLS, currently default to MPLS.

•TransportMode - From the drop-down list, you can choose Ethernet, Vlan, or NONE.

Note ISC GUI does not support Transport Mode VLAN. You must use a Dynamic Component Properties Library (DCPL) property as explained in the "L2VPN: Transport Mode VLAN with a DCPL Property" section.

•Tunnel Id (optional) - You can manually enter in this field the identifier of a TE tunnel that has already been provisioned by ISC or that has been manually provisioned on the device. Otherwise, you can click on Select TE Tunnel and from the pop-up window, you can automatically populate the field by selecting a TE tunnel that has already been provisioned by ISC.

•Disable Fallback (required for IOS XR 3.6.1; optional for IOS XR 3.7) - Choose this option, dependent on your version of IOS XR.

Pseudowire Class Association to an L2VPN Policy

To use the GUI to associate a pseudowire class to an L2VPN policy, follow these steps:

Step 1 Navigate to Service Design > Policies.

Step 2 Click the Create button and from the drop-down list choose L2VPN (P2P) Policy. You receive a window as shown in Figure 3.

Figure 3 L2VPN (Point To Point) Policy Creation

Step 3 In Figure 3, in the Selection area, click the L2VPN on MPLS Core link. You receive a window as shown in Figure 4.

Note The option L2VPN on IP(L2TPv3) core is not relevant in this release.

Figure 4 L2VPN (Point To Point) Policy Creation

Step 4 From the window in Figure 4, for the Service Type, choose one of the following:

•L2VPN ERS (proceed to Step 5 to Step 8)

•L2VPN EWS (proceed to Step 9 to Step 12)

Note The Frame Relay and the ATM options are not relevant for this release.

Step 5 If you chose L2VPN ERS as the Service Type in Figure 4 and then clicked the Next button, you receive a window as in Figure 5.

Figure 5 L2VPN (Point To Point) Policy Editor—Use PseudoWireClass Check Box for ERS

Step 6 If you check the Use PseudoWireClass check box in Figure 5, you receive a window as shown in Figure 6, with the newly added PseudoWireClass field.

Figure 6 L2VPN (Point To Point) Policy Editor—PseudoWireClass Field for ERS

Step 7 In Figure 6, you can click the Select button for the PseudoWireClass field and from the pop-up window you can click the radio button for the PseudoWireClass of your choosing. Then click Select. Figure 6 is then updated with the chosen PseudoWireClass specified in that field.

Step 8 Click the Finish button in Figure 6 and you are finished.

Step 9 If you chose L2VPN EWS as the Service Type in Figure 4 and then clicked the Next button, you receive a window as in Figure 7.

Figure 7 L2VPN (Point To Point) Policy Editor—Use PseudoWireClass Check Box for EWS

Step 10 If you check the Use PseudoWireClass check box in Figure 7, you receive a window as shown in Figure 8, with the newly added PseudoWireClass field.

Figure 8 L2VPN (Point To Point) Policy Editor—PseudoWireClass Field for EWS

Step 11 In Figure 8, you can click the Select button for the PseudoWireClass field and from the pop-up window you can click the radio button for the PseudoWireClass of your choosing. Then click Select. Figure 8 is then updated with the chosen PseudoWireClass specified in that field.

Step 12 Click the Finish button in Figure 8 and you are finished.

Pseudowire Class Association to an L2VPN Service Request

If you did not associate a pseudowire class with the L2VPN policy or if you need to override the PseudoWireClass object that you selected in the "Pseudowire Class Association to an L2VPN Policy" section, follow these steps to use the GUI to associate a pseudowire class to an L2VPN Service Request:

Step 1 Navigate to Inventory > Inventory and Connection Manager > Service Requests to create a Service Request.

Step 2 Click on the link AC Attributes and you receive a window as shown in Figure 9, where you can change the PseudoWireClass name as explained in the "Pseudowire Class Association to an L2VPN Policy" section.

Figure 9 Override PseudoWireClass Object

Pseudowire Class Modification and How It Impacts L2VPN Service Requests

To use the GUI to modify a pseudowire class, follow these steps:

Step 1 Navigate to Service Inventory > Inventory and Connection Manager > PseudoWireClass.

Step 2 Select the pseudowire class you want to modify, as shown in Figure 1, and click Edit.

Step 3 Make your required changes and click Save.

Step 4 If the PseudoWireClass used in the L2VPN Service Request is modified with Transport Mode, Tunnel Id, and Disable Fallback values, a list of affected Service Requests appears as in Figure 10.

Figure 10 Affected Jobs

Step 5 In Figure 10, click:

•Save to update L2VPN Service Requests with the changed PseudoWireClass attributes.

•Save and Deploy to update L2VPN Service Requests with the changed PseudoWireClass attributes and deploy Service Requests that were previously in Deployed state.

API Support

To use the Application Programming Interface (API) for pseudowire class support, see the information in the following tables:

•Table 1, "API Support for PseudoWireClass Creation"

•Table 2, "API Support for PseudoWireClass Modification"

For API support for PseudoWireClass association to an L2VPN policy, use the API CreateL2VPNServiceDefn_EthernetEVCS_NO_CE.xml. For API support for PseudoWireClass association to an L2VPN service request, use the API CreateL2VPNServiceOrder_EVCS_NO_CE.xml. Both of these APIs can be found in the examples specified in the following note.

Note Examples of PseudoWireClass are available at: $<ISC_HOME>/resources/nbi/xml/examples/l2vpn. The applicable file names are CreatePWclass.xml, DeletePWClasss.xml, ModifyPWClass.xml, and ViewPWClass.xml.

Table 1 API Support for PseudoWireClass Creation 

Attribute Name
Sample API XML Snipplet
Value Ranges

Name

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string">Name</name>

<value xsi:type="xsd:string">Test</value> </item>

Up to 32 characters and no spaces

Description

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string">description</name>

<value xsi:type="xsd:string">true</value> </item>

Up to 128 characters

Encapsulation

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string">Encapsulation

</name><value xsi:type="xsd:string">MPLS</value>

</item>

DEFAULT

MPLS

TransportMode

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string">Encapsulation

</name><value xsi:type="xsd:string">MPLS</value>

</item>

NONE

Vlan

Ethernet

TunnelId (required when you want to use a TE tunnel in PseudoWireClass)

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string">TunnelId</name>

<value xsi:type="xsd:string">10</value> </item>

0-65535

DisableFallBack

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string">DisableFallBack</name>

<value xsi:type="xsd:string">false</value> </item>

true

false

IsTeTunnel (true is required when you want to use a TE tunnel in PseudoWireClass)

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string"> IsTeTunnel </name>

<value xsi:type="xsd:string">false</value> </item>

true

false

HeadTeRouterId (required when you want to use a TE tunnel in PseudoWireClass)

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string"> HeadTeRouterId </name>

<value xsi:type="xsd:string">10</value> </item>

Any number that indicates the value of the TE router identifier


Table 2 API Support for PseudoWireClass Modification 

Attribute Name
Sample API XML Snipplet
Value Ranges

DeployAffectedSrs (true indicates to Save; false indicates to Save and Deploy)

<item xsi:type="ns1:CIMProperty">

<name xsi:type="xsd:string"> DeployAffectedSrs </name>

<value xsi:type="xsd:string">false</value> </item>

true

false


L2VPN: Deletion of Traffic Engineering (TE) Tunnel Not Allowed if Used in PseudoWireClass

If a TE tunnel is chosen in Service Inventory > Inventory and Connection Manager > PseudoWireClass and you are trying to delete a selected TE tunnel from Service Inventory > Inventory and Connection Manager > Traffic Engineering Management, you receive the error message: Tunnel <ids> associated with Admission SR or Pseudowire cannot be deleted.

L2VPN: Transport Mode VLAN with a DCPL Property

When you want to configure a pseudowire transport mode to be VLAN, navigate to the Dynamic Component Properties Library (DCPL), Administration > Control Center > Hosts, check a check box for a specific host and click the Config button. Then navigate to the property Services\Common\pseudoWireVlanMode and set it to true. ISC then generates VLAN transport mode configuration for the pseudowire.

Note The transport-mode vlan is a deprecated command in IOS XR 3.6 and later. Thus, when a PseudoWireClass is selected for an IOS XR device and the DCPL property is also set to true, the transport-mode vlan command is not generated. PseudoWireClass and the transport-mode vlan command do not co-exist.

Note The value of the Services\Common\pseudoWireVlanMode DCPL property should not be changed during the life of a Service Request.

Problems Fixed in ISC 5.0.3

For problems fixed in ISC 5.0.1 see the Problems Fixed section of the Release Notes for Cisco IP Solution Center, 5.0.1.

Table 3, "Customer-found Problems Fixed in ISC 5.0.2," describes all the customer-found problems fixed in ISC 5.0.2.

Table 3 Customer-found Problems Fixed in ISC 5.0.2 

CDETS Number
Subject

API:

CSCsl57013

Multiple NBI sessions cause thread deadlock.

MPLS Diagnostics Expert (MDE):

CSCsi96376

Access Circuit Backdoor routing might be incorrectly identified as a problem with the Border Gateway Protocol (BGP) vpnv4 next-hop for a Virtual Private Network (VPN) route.

CSCso42483

MDE aborts during label-switched path (LSP) visualization when device interaction fails.


No additional customer-found problems were fixed in this ISC 5.0.3 release.

Installation Notes

This section contains the following information:

•Version Supported

•Upgrade Paths

•Uninstall

Version Supported

ISC 5.0.3 is a maintenance patch release that 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, 4.2.5, 5.0, 5.0.1, or 5.0.2.

Note To install the ISC 5.0.3 patch release, you must have ISC 5.0.1 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.

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, 4.1.2, 4.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, or 5.0, you must install ISC 5.0.1 first, as explained in the Release Notes for Cisco IP Solution Center, 5.0.1. After upgrading to ISC 5.0.1, download and install the ISC 5.0.3 maintenance patch located at http://www.cisco.com/pcgi-bin/tablebuild.pl/isc on the same server. If you are upgrading from ISC 5.0.2, you have already installed ISC 5.0.1 and only need to install the ISC 5.0.3 maintenance patch.

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.

Follow these steps:

Step 1 Before upgrading to this ISC 5.0.3 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 5.0.3 Maintenance Release, 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).

Note If you need to revert to your prior version of ISC, this backed up repository is the one you need to point to after uninstalling ISC 5.0.3. When you uninstall ISC 5.0.3, you do not remove modifications made to the repository in Step 12. Any Service Requests provisioned under ISC 5.0.3 will then need to be reprovisioned.

Step 3 Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/isc (where, in tablebuild.pl, the last character is the lower-case letter "l") to retrieve the ISC 5.0.3 Maintenance Release (isc-5.0.3-patch.tar.gz) and the database schema upgrade package (ISC503_UpgradeTool.tar.gz).

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

Step 4 Prior to installing the ISC 5.0.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 Source the ISC environment file in the $ISC_HOME/bin directory:

For sh, ksh, and variant shells: . $ISC_HOME/bin/vpnenv.sh

For csh and variant shells: source $ISC_HOME/bin/vpnenv.csh

Step 6 Navigate to a directory other than $ISC_HOME.

Step 7 Use the following command to untar and unzip the isc-5.0.3-patch.tar.gz file:

gunzip -c isc-5.0.3-patch.tar.gz | tar xf -

Step 8 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 9 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, 4.1.2, 4.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, or 5.0, install ISC 5.0.1, as documented in the Release Notes for Cisco IP Solution Center, 5.0.1.

Note Prior to installing ISC 5.0.1, 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.

Thus, when you are upgrading from an ISC version prior to ISC 5.0.3, you must have a running ISC installation on your new machine that is the same version as that on your old machine so that initdb.sh can be used to initialize your repository with the correct hostname.

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

$ ./iscpatchinstall

a. When you run this script, you are asked to ensure that you have followed the equivalent of Step 8, and as part of the installation, you are 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 are asked to enter a new path or press Enter for the default [<ISC_OWNER_HOME_DIR>/isc-5.0.1].

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

Step 11 Use the following command on the ISC server to untar and unzip the database schema upgrade package:

gunzip -c ISC503_UpgradeTool.tar.gz | tar xf -

The directory ISC503_UpgradeTool is created. Before you proceed, read the README file that is located in this directory.

Step 12 Use the following commands on the ISC server to use the upgrade tool:

cd ISC503_UpgradeTool

./upgradeISCSchema.sh <full path of ISC_HOME>

The log messages are printed on the window and written in the log file contained in the log directory under the directory ISC503_UpgradeTool.

Step 13 Navigate to $ISC_HOME/bin.

Step 14 Enter the startwd command to restart ISC.

Uninstall

To uninstall the ISC 5.0.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 5.0.3 is running, navigate to the directory $ISC_HOME/patch/isc5.0.3-patch, where all the files replaced by the ISC 5.0.3 Maintenance Release were stored.

Step 3 Source the ISC environment file in the $ISC_HOME/bin directory:

For sh, ksh, and variant shells: . $ISC_HOME/bin/vpnenv.sh

For csh and variant shells: source $ISC_HOME/bin/vpnenv.csh

Step 4 Use the following command to stop the database, name server, and WatchDog on the machine on which it is running:

$ stopall

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

$ ./iscpatchrollback

a. When you run this script, you are 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 receive a message that the patch rollback is complete.

Step 6 Navigate to $ISC_HOME/bin.

Step 7 Enter the startwd command to restart ISC.

Important Notes

1. All ISC patches are available at: http://www.cisco.com/pcgi-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.3

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

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

•Release Notes for Cisco IP Solution Center, 5.0.2.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.0.2/release/notes/relnotes.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.1/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/docs/net_mgmt/ip_solution_center/5.0/developer/reference/
xmlapi.zip

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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental

Copyright © 2008 Cisco Systems, Inc. All rights reserved.