Guest

Cisco IP Solution Center

Release Notes for Cisco IP Solution Center, 5.2.2

  • Viewing Options

  • PDF (300.6 KB)
  • Feedback
Release Notes for Cisco IP Solution Center, 5.2.2

Table Of Contents

Release Notes for Cisco IP Solution Center, 5.2.2

Contents

Introduction

System Recommendations

New Device and Platform Support

New and Changed Information for ISC 5.2.2

Common Infrastructure New Features

New Template Variables Support in ISC 5.2.2

Bridge Domain Support for GSR 12406 (VPLS)

Graphical User Interface Support

NBI Support

Configlet

Problems Fixed

Problems Fixed in ISC 5.2.2

Problems Fixed in ISC 5.2.1

Installation Notes

Version Supported

Upgrade Paths

Common Installation Steps

ISC 5.2.2 Patch Installation

Upgrade Repository to ISC 5.2.2

Note Regarding Location of ISC 5.1 and 5.2 Upgrade Tools

Uninstall

Important Notes

Known Caveats in Cisco IP Solution Center 5.2.2

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco IP Solution Center, 5.2.2


Cisco IP Solution Center (ISC) 5.2.2 is a maintenance release that additionally has new features to be added to ISC 5.2.


Note This ISC release includes Cisco MPLS Diagnostics Expert (MDE) 2.1.4.


All documentation, including this Release Notes for Cisco IP Solution Center, 5.2.2 document and any or all parts of the ISC 5.2 and 5.2.2 documentation sets, might be upgraded over time. Therefore, we recommend you access the ISC 5.2 and ISC 5.2.2 documentation sets at: http://www.cisco.com/go/isc. You can also navigate to this documentation set 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 manual to be used with ISC 5.2.2.

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

Problems Fixed

Installation Notes

Important Notes

Known Caveats in Cisco IP Solution Center 5.2.2

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

ISC 5.2.2 has new functionality added and changed since ISC 5.2 (see the "New and Changed Information for ISC 5.2.2" section) and fixes to problems (see the "Problems Fixed" section). ISC 5.2.2 includes Cisco MDE 2.1.4.

The system recommendations for ISC 5.2.2 (see the "System Recommendations" section) are based on those for ISC 5.2. The new devices and platforms supported in addition to those supported in ISC 5.2 are listed in the "New and Changed Information for ISC 5.2.2" section.

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

URLs for base information about ISC 5.2.2 and an overview and suggested reading order of these documents is given in the Cisco IP Solution Center Getting Started and Documentation Guide, 5.2 (http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.2/roadmap/docguide.html).

The ISC 5.2.2 documentation set includes ISC 5.2 documents and updated information for ISC 5.2.2 found in this Release Notes for Cisco IP Solution Center, 5.2.2. The entire documentation set is available in the "Related Documentation" section.

System Recommendations

The system recommendations and requirements are listed in Chapter 1, "System Recommendations" of the Cisco IP Solution Center Installation Guide, 5.2. This chapter also includes the network devices and related software supported with ISC 5.2.

The recommendation is to thoroughly review this list 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 "New Device and Platform Support" section.

New Device and Platform Support

New supported devices and platforms are as follows:

Table 1 Platform Certification Added in ISC 5.2.2 

Platform
IOS/XR Target
L3
L2
TE
MDE

CISCO 12K GSR

CISCO IOS-XR 3.8.2,3.8.4,3.9.0,3.9.1

Yes (PE)

Yes (PE)

Yes

Yes

CRS-1

CISCO IOS-XR 3.8.2,3.8.4,3.9.0,3.9.1

Yes (PE)

Yes (PE)

Yes

Yes

Cisco ASR9K

CISCO IOS-XR 3.9.0/3.9.1

Yes (PE)

not supported in ISC

Yes

Yes

ASR1K

CISCO IOS-XE-2.5

Yes (PE)

not supported in ISC

Yes

Yes

CISCO 7600

12.2(33)SRE1

Yes (PE)

Yes (PE)

Yes

Yes

CAT 4900M

12.2(53)SG1

not supported in ISC

Yes (UPE)

not supported in ISC

not supported in ISC

ME 6524

12.2(33)SXI

not supported in ISC

Yes (PE,UPE), For NPE, FlexUNI not supported

not supported in ISC

not supported in ISC

CAT 4948

12.2(31)SGA11

not supported in ISC

Yes(UPE, PE-AGG)

not supported in ISC

not supported in ISC

CAT 6500

12.2(33)SXI

Yes (PE, MVRFCE)

Yes (PE,UPE)

not supported in ISC

not supported in ISC

CISCO 12K GSR

12.0(32)SY6

not supported in ISC

Yes (NPE), only VPLS supported

not supported in ISC

not supported in ISC


New and Changed Information for ISC 5.2.2

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

The categories in this section are:

Common Infrastructure New Features

Bridge Domain Support for GSR 12406 (VPLS)

Common Infrastructure New Features

All common infrastructure features are explained in the Cisco IP Solution Center Infrastructure Reference, 5.2.

The following infrastructure enhancements were added in ISC 5.2.2:

New Template Variables Support in ISC 5.2.2

New Template Variables Support in ISC 5.2.2

In addition to the previously supported template variables, found in Chapter 6, Service Design, of the Cisco IP Solution Center Infrastructure Reference, 5.2 and those listed in Release Notes for Cisco IP Solution Center, 5.2.1, new attributes introduced in this release are also supported as template variables. Discussion of these are found in sections of this release note covering new features for this release.

Table 2 FlexUNI/EVC Template Variables Added in ISC 5.2.2

Template Variable Name
Value Returned

$CARD_TYPE

Card type

$PE_OR_UNI_INTF_DESC

PE/UNI interface description

$UNI_SHUTDOWN

Uni shutdown

$UNI_SPEED

Uni speed

$UNI_PORT_SECURITY

Uni port security

$UNI_AGING

Uni aging

$STD_UNI

Standard UNI option

$USER_DEFINED_ACL_NAME

User-defined ACL name

$MAC_ACL_RANGE

MAC ACL range value

$UNI_VIOLATION_ACTION

UNI violation action

$TUNNEL_CDP_DROP_THRESHOLD

Tunnel CDP drop threshold value

$TUNNEL_VTP_DROP_THRESHOLD

Tunnel VTP drop threshold value

$TUNNEL_STP_DROP_THRESHOLD

Tunnel STP drop threshold value

$UPE_FACING_INTERFACE_NAME

PE facing interface name

$SYSTEM_MTU

System MTU

$STORM_CTL_BROADCAST_TRAFFIC

Broadcast traffic

$STORM_CTL_MULTICAST_TRAFFIC

Multicast traffic

$STORM_CTL_UNICAST_TRAFFIC

Unicast traffic


Table 3 L2VPN, MPLS, and VPLS Template Variable Added in ISC 5.2.2

Template Variable Name
Value Returned

$CARD_TYPE

Card type


Bridge Domain Support for GSR 12406 (VPLS)

All VPLS features, with the exception of the new features since ISC 5.2, are explained in detail in the Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0 or in Release Notes for Cisco IP Solution Center, 5.2.1.

The role of NPE is now supported in ISC for GSR 12406 running IOS 12.0(32) SY6.

This support is provided only for traditional VPLS ERMS (Ethernet Relay Multipoint Service) and EMS (Element Management Systems) services.

Graphical User Interface Support

A new Bridge Domain ID attribute is presented on the Link Attributes window of the service request.

This Bridge Domain ID attribute is displayed for GSR platforms running IOS only. It is not supported for other platforms. The attribute is filtered in the GUI for non-GSR platforms.

When a NPE (GSR platform) is used as a UNI device, standard UNI attributes are filtered and those will not be displayed on the GUI window.

When a UPE (non-GSR platform) is used as a UNI device, all standard UNI attributes will be displayed on the GUI window.

For EMS services, an UPE (non-GSR platform) must be used to create the service request with the GSR platform running IOS.

The Link Attributes window in Figure 1-1 shows the supported link attributes for VPLS service requests.

Figure 1-1 Link Attributes for VPLS Service Requests

NBI Support

The Bridge Domain ID attribute is also supported from the NBI.

In the following VPLS service request example, the Bridge Domain ID attribute is highlighted in bold.


<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:ns0="http://www.cisco.com/cim-cx/2.0"
  xmlns:ns1="urn:CIM">
  <soapenv:Header>
     <!-- WaitTimeout has a default set in system properties.-->
     <ns0:message id="87855" timestamp="2002-12-13T14:55:38.885Z"
              Wait="true" WaitTimeout="60" sessiontoken="p36bttjwy1"/>
  </soapenv:Header>
  <soapenv:Body> 
    <ns1:performBatchOperation>
      <actions xsi:type="ns1:CIMActionList" 
                   soapenc:arrayType="ns1:CIMAction[]"> 
        <action>
          <actionName xsi:type="xsd:string">createInstance</actionName>
          <objectPath xsi:type="ns1:CIMObjectPath"> 
            <className xsi:type="xsd:string">ServiceOrder</className>
            <properties xsi:type="ns1:CIMPropertyList" 
                             soapenc:arrayType="ns1:CIMProperty[]">  
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">ServiceName</name>
                <value xsi:type="xsd:string">ServiceOrder257</value>
              </item>
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">CarrierId</name>
                <value xsi:type="xsd:string">322</value>
              </item>
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">DesiredDueDate</name>
                <value xsi:type="xsd:dateTime">2002-12-13T14:55:38.000Z</value>
              </item>
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">NumberOfRequests</name>
                <value xsi:type="xsd:string">1</value>
              </item>
              
            </properties>
          </objectPath>
        </action>
        <action>
          <actionName xsi:type="xsd:string">createInstance</actionName>
          <objectPath xsi:type="ns1:CIMObjectPath"> 
            <className xsi:type="xsd:string">ServiceRequest</className>
            <properties xsi:type="ns1:CIMPropertyList" 
                                   soapenc:arrayType="ns1:CIMProperty[]">  
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">RequestName</name>
                <value xsi:type="xsd:string">MYSR-1</value>
              </item>
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">Type</name>
                <value xsi:type="xsd:string">Vpls</value>
              </item>
            </properties>     
            <objectPath xsi:type="ns1:CIMObjectPath"> 
              <className xsi:type="xsd:string">ServiceRequestDetails</className>
              <properties xsi:type="ns1:CIMPropertyList"
                        soapenc:arrayType="ns1:CIMProperty[]">
                <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">ServiceDefinition</name>
                  <value xsi:type="xsd:string">ems-ce</value>
                  <qualifier xsi:type="xsd:string">
                    <name xsi:type="xsd:string">ServiceDefinitionType</name>
                    <value xsi:type="xsd:string">Vpls</value>
                  </qualifier>
                </item>
                <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">VPN</name>
                  <value xsi:type="xsd:string">DienshVPN1</value>
                </item>
              </properties>
              <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">VplsLink</className>
                <properties xsi:type="ns1:CIMPropertyList" 
                       soapenc:arrayType="ns1:CIMProperty[]">  
        
                  <!-- need to spedify Cpe and PE if ManualConfig is true -->
                  
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">NPC</name>
                    <value xsi:type="xsd:string">7</value>
                  </item>
                                     
                </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">LinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList"
                                       soapenc:arrayType="ns1:CIMProperty[]">
                               
			       <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">PE_Intf_Name</name>
                      <value xsi:type="xsd:string">FastEthernet1/0/2</value>
                    </item>
                
                    <!-- CE Information -->
                    <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">PE_Encap</name>
                      <value xsi:type="xsd:string">DOT1Q</value>
                    </item>
                    
                    <!-- Common Information -->
                    <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">PE_Intf_Desc</name>
                      <value xsi:type="xsd:string">Pe Intf Desc</value>
                    </item>
                    
                    <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">BRIDGE_DOMAIN_ID</name>
                      <value xsi:type="xsd:string">4500</value>
                    </item>
                    
                    <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">Autopick_Vlan_ID</name>
                      <value xsi:type="xsd:string">true</value>
                    </item>
                        
                  </properties>
                </objectPath>
                 
                </objectPath>
              </objectPath>
            </objectPath>
          </action>      
        </actions>
      </ns1:performBatchOperation>  
    </soapenv:Body>
</soapenv:Envelope>

The permitted value range for the BridgeDomain ID is 1-4294967295.

Configlet

The following is a sample configlet for bridge domain support on a GSR platform.


NPE :
--------
l2 vfi L2iups_control manual
 vpn id 90002
 bridge-domain 100 
 neighbor 192.168.101.164 encapsulation mpls
 neighbor 192.168.101.163 encapsulation mpls
!

interface GigabitEthernet3/2.282
 encapsulation dot1Q 282
 bridge-domain 100

Problems Fixed

This section lists problems that were fixed since the ISC 5.2 release:

Problems Fixed in ISC 5.2.2

Problems Fixed in ISC 5.2.1

Problems Fixed in ISC 5.2.2

Customer-found problems that have been fixed in the ISC 5.2.2 release are indicated in Table 4. This includes ISC 5.1.1.1, 5.2.1.1, 5.1.1.10, 5.1.1.12, 5.1.1.13, 5.1.1.14, 5.2.1.2, 5.2.1.3, 5.2.1.4, and 5.2.0.3.

Table 4 Customer-found Problems Fixed in ISC 5.2.2 

CDETS Number
Subject
Infrastructure
 

CSCta31174

Not able to allocate IP addresses for /32 address pools.

CSCtc79206

Reconfigures already configured template.

CSCtf78429

Maximum 14 devices in a NPC ring. (Provisioning does not work properly when more than 14 devices are added to a NPC ring.)

CSCtf91078

Datafile cannot be deleted via the NBI. (SR has been decommissioned and purged when an attempt to delete the datafile was made via API.)

CSCtd60921

Template and negate template issue. (Modify of TempRep value in ISC-SR decom goes to Failed Deploy ForceTemDep=TRUE)

CSCtg58175

Datafile name has to allow dot (.) character through the GUI.

MPLS
 

CSCtb64945

L3 SR audit fails while running tests on 5.1 / IOS Eagle.

CSCte06427

Static routes not generated for MVRFCE type MPLS VPN SR.

CSCsv55547

VRF icon link navigates to CERC page.

CSCtc45073

VRF and RD Overwrite grayed out even with URD disabled.

CSCte40726

Variable for BGP Neighbor IP Address required.

CSCta56580

SR goes to Failed Deploy state with Multicast option enabled in ASR1K.

CSCtc15417

Error during decommissioning of SR on ME6524.

L2VPN
 

CSCte68671

VLAN ID returns to pool even if other SRs are still using it.

CSCsy55906

Media-type support for L2VPN SRs using ME-3400 devices as UPE.

CSCte43425

L2VPN LS SR deployment using Gig interface is missing some configlets.

CSCte43515

Decommissioning of L2VPN SR2 will remove the SR1 interface and P2P circuit.

CSCtf51059

Decommission fails on ES+ Cards due to cli "no bridge-domain".

CSCte69396

Bridge domain is created with the split-horizon option enabled.

CSCtf33491

FlexUNI/VPLS- Failed Audit due to "vpn id: not found".

CSCtf93036

Enabling L2 CDP tunneling protocol also enables CDP on UNI trunk.

CSCtg91802

Duplex command not generated by ISC for media type RJ45 and speed 1000.

CSCtg68273

Flexuni ISC allocating different Vlan IDs for two links terminating on the same NPE.

TEM
 

CSCsz72919

TE Admission SRs are not being discovered from device running Eagle IOS.

CSCtf86431

TEM provisioning tests are failing on IOS XR 3.8.3.


Problems Fixed in ISC 5.2.1

Customer-found problems that have been fixed in the ISC 5.2.1release are indicated in Table 5. This includes ISC 5.1.1.6, 5.1.1.8, 5.1.1.9, 5.2.0.1, and 5.2.0.2.

Table 5 Customer-found Problems Fixed in ISC 5.2.1 

CDETS Number
Subject
Infrastructure
 

CSCsy66777

Edit group error appears for user groups when roles are edited.

CSCtb78832

Error while viewing User Access Log Viewer.

CSCtd07397

Description field missing from templates.

CSCtd07406

Unique name issue for ATM connect in template.

MPLS
 

CSCsx11798

Failure to save the service request, if you create an MPLS service request with MVRFCE and BGP multipath attributes.

CSCsz84925

ISC 5.1 issues commands for no reason.

CSCtc49789

ISC 5.2 issues commands for no reason.

CSCta95607

Error while decommissioning an MPLS service request with MVRFCE and BGP multipath.

CSCtc35751

VRF and RD Overwrite attribute gets automatically unchecked on navigating back and forth from the window in which it appears.

CSCtc15441

ISC allows a service request to be saved with the same PE and interface.

CSCsz47279

spanning-tree bpdufilter enable is being sent to ME3400, which should never occur.

CSCta16250

Issues when saving a MVRFCE service request.

CSCta78641

Error when saving link attributes. MPLS SR with CE side as FastEthernet and PE side as loopback interface.

CSCtb23496

Failed automatic provisioning while applying previously working API.

CSCtb26774

Resource Pool is incorrectly reported to be empty.

CSCtc38866

ASA error - 306; Deadlock detected.

CSCtc54481

Service request is decommissioned when VLAN int and VRF are removed in a different service request.

CSCta78641

Problem with MPLS SR with CE side as FastEthernet and PE as loopback interface.

L2VPN
 

CSCsz51060

L2VPN keepalive not supported for upgraded IOS release.

CSCta95683

E-line names populate incorrectly.

CSCtc02548

Service Instance Name accepts names containing spaces.

CSCtb07113

Unable to deploy L2 FlexUNI on interfaces with L3 subinterfaces.

CSCsz84925

ISC issues commands for no reason.

CSCtc54481

The decommissioning of a service request removes the VLAN int and VRF in a different service request.

CSCtb55270

EVC/SVI Hybrid scenario is not possible.

CSCtd03117

All FlexUNI/EVC SRs referring to the same VPN must have the same core type.

CSCtd07311

Connect Name in FlexUNI/EVC SR should be limited to 15 characters.

CSCtc98196

Error provisioning FlexUNI/EVC pseudowire SR.

CSCtb67687

L2 FlexUNI/EVC tests failing on ISC 5.2 / IOS Eagle / 7600-ES+20G3C.

MDE
 

CSCsv61706

MPLS Diagnostics Expert (MDE) produces incorrect results.

   
TEM
 

CSCtc51795

When deleting a link through the api with Loose/Exclude hop explicit path, both the link and the path are deleted.

CSCsz70077

The Close button in TE Protection Computation Results window has not been removed.


Installation Notes

This section contains the following information:

Version Supported

Upgrade Paths

Uninstall.

Version Supported

You can upgrade directly to ISC 5.2.2 from either ISC 5.2 and ISC 5.2.1. If you are upgrading from earlier releases, you need to first upgrade to ISC 5.2. The procedure for upgrading from earlier releases is documented in the Cisco IP Solution Center Installation Guide, 5.2.

Upgrade Paths

Whether you are installing ISC for the first time or are upgrading from an earlier ISC installation, use the following steps as they pertain to your situation.

This section includes the following:

Common Installation Steps

ISC 5.2.2 Patch Installation

Upgrade Repository to ISC 5.2.2

Note Regarding Location of ISC 5.1 and 5.2 Upgrade Tools

Common Installation Steps

Whether you have an ISC 5.2 or an ISC 5.2.1 repository, use the same upgrade procedure independent of whether your repository is a Sybase or an Oracle repository


Note A repository can be upgraded only once. If any issues arise during the upgrade, a new copy of the backed up repository is needed for subsequent upgrade attempts.



Note See the appendix Backup and Restore of ISC Repository and Standby System in the Cisco IP Solution Center Installation Guide, 5.2 before upgrading your repository.


Use the following steps to upgrade your repository to 5.2.2:


Step 1 If you are installing ISC for the first time, first install ISC 5.2 as documented in the Cisco IP Solution Center Installation Guide, 5.2.


Note The ISC-5.2 upgrade tool should not run while upgrading from ISC 5.2.1 to ISC 5.2.2.



Note During installation, choose Keep existing ISC repository and complete the installation.



Note To perform ISC 5.2.2 patch installation, you first have to install the 5.2.1 patch.


Step 2 If an existing ISC installation is running, enter the stopall command using these steps:

cd $ISC_HOME/bin/

source vpnenv.sh

./stopall

Step 3 Install the ISC 5.2.2 patch using the steps outlined in ISC 5.2.2 Patch Installation.

Step 4 Then run the upgrade tool using the steps outlined in Upgrade Repository to ISC 5.2.2.


ISC 5.2.2 Patch Installation

To install the ISC 5.2.2 maintenance patch, follow these steps:


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



Step 1 Before upgrading to this ISC 5.2.2 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.2.2 Maintenance Release, be sure to back up your repository, as explained in Appendix C of the Cisco IP Solution Center Installation Guide, 5.2 (http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.2/installation/guide/install.html).

Step 3 Retrieve the ISC 5.2.2 Maintenance Release (isc-5.2.2-patch.tar.gz) from here.


Note If you have difficulties accessing the software from this location, please go to Cisco.com and choose Support->Download Software->Network Management->Routing and Switching Management->Cisco IP Solution Center Products.


Step 4 Prior to installing the ISC 5.2.2 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.2.2-patch.tar.gz file:

gunzip -c isc-5.2.2-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 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.2.2].

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

Step 10 Navigate to $ISC_HOME/bin.

Step 11 Enter the startwd command to restart ISC.


Upgrade Repository to ISC 5.2.2

This procedure uses the example of upgrading an ISC 5.2 repository to ISC 5.2.2. You can upgrade the ISC repository directly to ISC 5.2.2 from both ISC 5.2 and ISC 5.2.1.

When upgrading your repository from ISC 5.1 or an earlier version, see Note Regarding Location of ISC 5.1 and 5.2 Upgrade Tools and then use the same procedure as the following:


Step 1 Get the upgrade package ISC522_UpgradeTool.tar.gz and place it on the ISC Master machine in a directory where you can access the ISC environment:

cp -p /cdrom/cdrom0/ISC522_UpgradeTool.tar.gz /opt/isc-5.2.2

Step 2 Untar the upgrade tool tar file.

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

Step 3 Source the ISC environment files.

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

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

Step 4 Stop ISC:

stopall

Step 5 Run the upgrade script.

cd ISC522_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, ensure that the cache of the ISC client browser has been cleared or that your browser does not use the cache. This will ensure that the latest ISC images and pages are returned.



Note Regarding Location of ISC 5.1 and 5.2 Upgrade Tools

To upgrade your repository to ISC 5.2.2, you first need to run the ISC 5.1 Upgrade Tool in case of releases prior to ISC 5.1 or the ISC 5.2 Upgrade Tool in case of an ISC 5.1 repository.

The location for the ISC 5.1 and 5.2 upgrade tools have changed compared with the documentation for the previous ISC releases. You now need to access these tools from the respective CD-ROMs (ISC 5.1 Upgrade Tool used as an example):

/cdrom/cdrom0/ISC51_UpgradeTool.tar.gz

Uninstall

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


Note To retain your repository data, you will need to restore a previous ISC 5.2 backup as the uninstall script below does not roll back the 5.2.2 repository.



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

Step 2 If ISC 5.2.2 is running, navigate to the directory $ISC_HOME/patch/isc5.2.2-patch, where all the files replaced by the ISC 5.2.2 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/cgi-bin/tablebuild.pl/isc.

2. If an Oracle database is being used, it must be installed on a Solaris machine as Sybase by default will be bundled with the ISC installation.

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

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

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

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

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

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

You must log 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.2.2 can be accessed at:

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

or at:

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


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


The following documents comprise the ISC 5.2.2 documentation set:

General documentation (in suggested reading order)

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

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

Release Notes for Cisco IP Solution Center, 5.2.1.

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

Release Notes for Cisco IP Solution Center, 5.2.

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

Cisco IP Solution Center Installation Guide, 5.2.

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

Cisco IP Solution Center Infrastructure Reference, 5.2.

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

Cisco IP Solution Center System Error Messages, 5.2.

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

Application and technology documentation (listed alphabetically)

Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 5.2.

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

Cisco IP Solution Center MPLS VPN User Guide, 5.2.

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

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

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

Cisco MPLS Diagnostics Expert 2.1.4 Failure Scenarios Guide on ISC 5.2.

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

Cisco MPLS Diagnostics Expert 2.1.4 User Guide on ISC 5.2.

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

API Documentation

Cisco IP Solution Center API Programmer Guide, 5.2.

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

Cisco IP Solution Center API Programmer Reference, 5.2.

http://www.cisco.com/en/US/docs/net_mgmt/ip_solution_center/5.2/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, Obtaining Support, and Security Guidelines

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

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