Table Of Contents
Release Notes for Cisco IP Solution Center, 5.2
Cisco IP Solution Center (ISC) 5.2 is a follow-on release to ISC 5.1.
Note This ISC release includes an update to Cisco MPLS Diagnostics Expert (MDE) 2.1.4 from MDE 2.1.3.
All documentation, including this Release Notes for Cisco IP Solution Center, 5.2 document and any or all parts of the ISC 5.2 documentation set, might be upgraded over time. Therefore, we recommend you access the ISC 5.2 documentation set 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 5.2 product.
The information in this Release Notes for Cisco IP Solution Center, 5.2 document gives you an overview of this release and helps you understand it at a high level. After reading the Cisco IP Solution Center Getting Started and Documentation Guide, 5.2, please read this document prior to reading any other manual for ISC.
The information in this document is organized into the following sections:
ISC 5.2 is a follow-on release to ISC 5.1 with some functionality added and changed (see the "New and Changed Information for ISC 5.2" section) and problems fixed (see the "Problems Fixed in ISC 5.2" section).
URLs for base information about ISC 5.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).
ISC is a family of intelligent network management applications that helps reduce overall administration and management costs by providing automated resource management and rapid profile-based provisioning capabilities. ISC enables fast deployment and time to market of Multiprotocol Label Switching (MPLS) and Carrier Ethernet technologies. In addition, the ISC Traffic Engineering Management application is Cisco's exclusive planning and provisioning application for Cisco MPLS Traffic Engineering (MPLS-TE)-enabled routers. For Diagnostics, use MDE, which is an automated, decision tree analysis-based network management application that troubleshoots and diagnoses problems in MPLS Virtual Private Networks (VPNs). There are four separate applications in ISC 5.2, which can operate alone or as a suite in an L2/L3 Management Solution. These and Application Programing Interfaces (APIs) are all distributed on one product CD:
•Cisco ISC MPLS VPN Management (ISC:MPLS)
•Cisco ISC Layer 2 VPN and Carrier Ethernet Management (ISC:L2VPN/CE)
•Cisco ISC Traffic Engineering Management (ISC:TEM)
•Cisco MPLS Diagnostics Expert (MDE)
System Recommendations and Network Devices
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.
Note In the limited release ISC 5.0.4, which is included in this ISC 5.2 release, IOS XR 3.7.0 support was added for the Cisco Carrier Routing System-1 (CRS-1) Series Routers and Cisco 12000 (GSR) Series Routers for Layer 3 provisioning.
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.
New and Changed Information for ISC 5.2
ISC 5.2 is based on 5.1 with the addition of new and changed information that was introduced in ISC 5.1.1.x:
•ISC 5.1.1 (see the Release Notes for Cisco IP Solution Center, 5.1.1) - adds many updates for MPLS.
ISC 5.2 includes problems fixed since ISC 5.1 (see Problems Fixed in ISC 5.2).
Items specific to ISC 5.2 and from a limited ISC 5.0.4 release include the new and changed information, as follows:
This section includes the following new features:
This section includes the following new features:
This section includes the following new features:
API New Features
All API features, including the new features since ISC 5.1, are explained in detail in the Cisco IP Solution Center API Programmer Guide, 5.2 and the Cisco IP Solution Center API Programmer Reference, 5.2.
The following API enhancements were added in ISC 5.2:
API Traffic Engineering Management Support
The APIs now support Traffic Engineering Management (TEM), including bulk provisioning, updating, and deleting of Multiprotocol Label Switching Traffic Engineering (MPLS TE) objects.
API MPLS Enhanced Support
MPLS API support was added for the following:
•Border Gateway Protocol (BGP) route map for IOS
•Exterior Border Gateway Protocol (eBGP)— community strategy for additional route support
•eBGP—Site of Origin
•Open Shortest Path First (OSPF) to BGP redistribution
•Route Distinguisher (RD) format addition
For more information about these features, see the "MPLS New Features" section.
Common Infrastructure New Features
All common infrastructure features are explained in the Cisco IP Solution Center Infrastructure Reference, 5.2.
This section includes the new features for multiple components that were added specifically in this release:
Cisco Configuration Engine Version 3.0
In addition to the previously supported versions of the Cisco Configuration Engine that manage an IOS device, this release now also supports version 3.0. This is explained in Appendix A of the Cisco IP Solution Center Infrastructure Reference, 5.2.
MPLS VPN Template Variables
New MPLS VPN template variables have been added in this release. These are specified in Table 6-4 in Chapter 6 of the Cisco IP Solution Center Infrastructure Reference, 5.2.
MPLS New Features
All MPLS features, including the new features since ISC 5.1, are explained in detail in the Cisco IP Solution Center MPLS VPN User Guide, 5.2.
Note All new IOS XR-supported features are supported for IOS XR versions 3.6.2 and 3.7.1 only.
The following MPLS VPN enhancements were added specifically in ISC 5.2:
The following MPLS VPN enhancements were added in the limited release ISC 5.0.4:
Note These features are not supported for Multi-VPN routing/forwarding instance for Customer Edge device (MVRFCE) policies and service requests, with the exception of the OSPF to BGP Redistribution feature.
BGP Route Map for IOS
ISC now supports the addition of a route map field for IOS devices with BGP, as the PE to CE protocol. The IN and OUT route map name can be specified. If Site of Origin (SOO) is enabled in the service request level, the Route Map/Policy In text box is grayed out and the Route Map/Policy In value takes the name of the SOO during deployment time.
Carrier Supporting Carrier on IOS XR for the BGP Protocol
The Carrier Supporting Carrier (CSC) feature enables a service provider to carry the traffic of a different service provider across its MPLS network. In ISC, the customer carrier PE device is modeled as a CE device and the backbone carrier PE device is modeled as Network-facing Provider Edge (N-PE) device. An MPLS Service Request with the CSC option can be created with these PE and CE devices.
You can configure the CSC feature on IOS XR PE devices. The CSC service is applicable for the following PE-CE link configurations:
The CSC service is applicable for the BGP PE-CE routing protocol.
eBGP—Community Strategy for Additional Route Support
ISC now supports two additional route-policy commands. You can specify the "in" and "out" policy name in a text field. These attributes are set when BGP is chosen as the routing protocol in the policy.
Note This option is only available when the PE-CE routing protocol is BGP.
ISC allows the BGP neighbor send-community command to be configured on the PE device for both IOS and IOS XR. This is available for both IPv4 and IPv6 eBGP neighbors on IOS XR PE devices. The Standard, None, Extended, and Both attributes are supported.
Note This option is only available when the PE-CE routing protocol is BGP.
eBGP—Site of Origin
The ISC graphical user interface (GUI) previously supported eBGP Site of Origin for IOS. In this release, eBGP Site of Origin is additionally supported only for IPv4 eBGP neighbors on IOS XR PE devices.
IOS to IOS XR Migration
For assistance in migrating services deployed on IOS devices to IOS XR devices, contact Cisco Advanced Services.
IOS XR Support Added
The following features are no longer just supported on IOS. They are now also supported on IOS XR, with the stated exceptions:
•BGP Multipath Configuration
–The maximum number of paths supported for IOS is 1 to 32 and for IOS XR the maximum number of paths supported in 2 to 8.
–Subsuming is now introduced for modification of all services requests with shared multipath attributes. This is new for both IOS and IOS XR.
Note Import paths are supported in IOS but not in IOS XR.
•eBGP Advertisement Interval
Multilink Frame Relay Support
The MLFR interfaces are supported on IOS XR devices. As with the previous support for IOS devices, ISC does not set up the MLFR interface, ISC provisions the layer 3 service on the MLFR interface.
Multicast Support for IPv6
ISC allows the following on IOS XR PE devices running release 3.7.0 or later: a multicast VPN to be deployed on an IPv6 PE-CE link and multicast to be enabled during the creation of the VPN routing/forwarding instance (VRF) object.
When creating a VPN or a VRF object, you can enable multicast for IPv4, IPv6, or both. You can enter IPv6 addresses as static Rendezvous Point (RP) addresses if IPv6 multicast is enabled during the creation of a VPN or VRF object.
You can also modify an existing VPN or VRF object to enable multicast for IPv4, IPv6, or both. When IPv4 multicast is enabled, all deployed service requests containing IPv4 links of the same VPN or VRF are moved into Requested state.
In addition, you can specify within the MPLS service request whether you want to enable multicast for IPv4, IPv6, or both on a given MPLS link.
When IPv6 multicast is enabled, all deployed service requests containing IPv6 links of the same VPN or VRF are moved into Requested state. If IPv4 is previously configured and only IPv6 multicast is enabled in a VPN, only the service requests with IPv6 links are moved into Requested state.
You can modify an existing VPN or VRF object and add IPv6 static RP addresses when IPv6 multicast is enabled. Any service requests already in Deployed state are then moved to the Requested state.
You can create a service policy or an MPLS VPN link in the service request with IPv6 Numbered or IPv4+IPv6 Numbered as the IP addressing scheme and a multicast VPN or a VRF with multicast enabled.
Multiple IPv6 Address Configuration
ISC supports multiple IPv6 addresses on the PE interface for IOS XR PE devices.
OSPF to BGP Redistribution
ISC now supports redistribute OSPF addition of a route policy. Previously, this configuration was hard-coded. ISC supports taking the values from the GUI and putting them into the device configuration. Special characters are taken as is, with no GUI validation being performed.
The following features are supported only for IPv4 routing on IOS and IOS XR PE devices:
•Redistribute OSPF route policy
•Redistribute OSPF match internal
•Redistribute OSPF match external
The following warning messages can be displayed and work only for IOS XR PE devices:
•Keep OSPF process for the Interior Gateway Protocol (IGP) as a separate process
•DCPL property to set the maximum number of OSPF processes (mpls\ospfProcessLimit)
•OSPF process identifier (ID) check
OSPF Protocol—New Settings
You can specify an OSPF domain ID on a PE or you can use an OSPF domain ID from a VRF or VPN.
Remote 4-Byte BGP AS Number Support
ISC supports a remote 4-byte autonomous system (AS) number in the format [0-65535].[0-65535]. As an example: 100.65535. This remote 4-byte AS number is supported as a CE BGP AS number in a service policy and as a CE BGP AS number in a service request. If the platform does not support a remote 4-byte AS number, the service deployment fails.
The previously supported 2-byte integer values are also supported as valid AS number values.
Route Distinguisher Format Addition
You can now configure an RD in ipaddress format on IOS and IOS XR PE devices. For IOS XR, only the IPv4 address format is supported. The new RD format is supported for creation and modification of an independent VRF, a VRF service request, and an MPLS service request, not an MPLS policy.
Problems Fixed in ISC 5.2
Customer-found problems that were fixed in ISC 5.2 since ISC 5.1 are indicated in three tables, so those who have upgraded to different Maintenance Releases since ISC 5.1 can find what has been fixed since the upgrade. The information is presented as follows:
This ISC 5.2 release includes the ISC patch releases: 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, and 22.214.171.124. The list of CDETS fixed in these patches is included in the following tables.
Customer-found Problems Fixed Specifically in Limited Release ISC 5.0.4
Table 1, "Customer-found Problems Fixed Specifically in Limited Release ISC 5.0.4," describes all the customer-found problems that were fixed specifically in the ISC 5.0.4 Maintenance Release.
Customer-found Problems Fixed Specifically in ISC 5.1.1.x
Table 2, "Customer-found Problems Fixed Specifically in ISC 5.1.1.x," describes all the customer-found problems that were fixed specifically in the ISC 5.1.1 Maintenance Release and subsequent patches to this Maintenance Release.
Customer-found Problems Fixed Specifically in ISC 5.2
Table 3, "Customer-found Problems Fixed Specifically in ISC 5.2," describes all the customer-found problems that were fixed specifically in ISC 5.2.
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.2
To find known problems in Cisco IP Solution Center, use the following URL:
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.
The entire documentation set for Cisco IP Solution Center, 5.2 can be accessed at:
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 documentation set:
General documentation (in suggested reading order)
Application and technology documentation (listed alphabetically)
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:
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, 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, 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. (0903R)
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 © 2009 Cisco Systems, Inc. All rights reserved.