Guest

Cisco IP Solution Center

Release Notes for Cisco IP Solution Center, 5.2.1

  • Viewing Options

  • PDF (951.8 KB)
  • Feedback
Release Notes for Cisco IP Solution Center, 5.2.1

Table Of Contents

Release Notes for Cisco IP Solution Center, 5.2.1

Contents

Introduction

System Recommendations

New Device and Platform Support

IOS XR 3.7.2 on the ASR9000 Platform

IOS XR 3.8.1 on the Cisco 12000 (GSR) Series Routers

IOS XR 3.8.1 on the Cisco Carrier Routing System-1 (CRS-1) Series Routers

New and Changed Information for ISC 5.2.1

Common Infrastructure New Features

New DCPL Properties Supported in ISC 5.2.1

New Template Variables Support in ISC 5.2.1

Resolved Deadlock Error During Concurrent Modification of Service Requests

L2VPN and Carrier Ethernet New Features

Configuring an EVC/SVI Hybrid Scenario

Service Instance Name Support for FlexUNI/EVC Service Requests

FlexUNI/EVC Service Requests Referring to the Same VPN Can Have Different Core Types

Connect Name Limitation in FlexUNI/EVC Service Requests Resolved

New L2VPN-Related Template Variables

Restricting Spanning Tree Command for the ME3400 Device

Restricting Switchport Trunk Encapsulation dot1q Command on the CAT 6500

Support for IOS XR 3.7.2 Across All Blades on the ASR 9000 Platform Only

MPLS/L3 VPN New Features

Adding Independent IPv4 and IPv6 Route Targets for MPLS Service Requests

Multiple Neighbor and Peering with Bundled Physical Interface for IOS XR PE Devices

Outgoing Interface Name + Next Hop IP Address Support for Static Route Configuration

BGP Multipath Attribute Modification After Upgrade

Documentation Clarification on Editing the VRF and RD Overwrite Attributes in Service Requests

Traffic Engineering Management (TEM) New Features

Explicit Path Deletion

Link Deletion with Associated Objects Enhancement

API New Features

MPLS Provisioning

L2VPN and Carrier Ethernet Provisioning

FlexUNI/EVC Provisioning

Traffic Engineering Management Provisioning

Problems Fixed in ISC 5.2.1

Installation Notes

Version Supported

Upgrade Paths

Common Installation Steps

ISC 5.2.1 Patch Installation

Upgrade Repository to ISC 5.2.1

Note Regarding Location of ISC 5.1 and 5.2 Upgrade Tools

Uninstall

Important Notes

Known Caveats in Cisco IP Solution Center 5.2.1

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco IP Solution Center, 5.2.1


Cisco IP Solution Center (ISC) 5.2.1 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.1 document and any or all parts of the ISC 5.2 and 5.2.1 documentation sets, might be upgraded over time. Therefore, we recommend you access the ISC 5.2 and ISC 5.2.1 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.1.

The information in this Release Notes for Cisco IP Solution Center, 5.2.1 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.1

Problems Fixed in ISC 5.2.1

Installation Notes

Important Notes

Known Caveats in Cisco IP Solution Center 5.2.1

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

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

The system recommendations for ISC 5.2.1 (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.1" section.

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

URLs for base information about ISC 5.2.1 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.1 documentation set includes ISC 5.2 documents and updated information for ISC 5.2.1 found in this Release Notes for Cisco IP Solution Center, 5.2.1. 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:

"IOS XR 3.7.2 on the ASR9000 Platform" section

"IOS XR 3.8.1 on the Cisco 12000 (GSR) Series Routers" section

"IOS XR 3.8.1 on the Cisco Carrier Routing System-1 (CRS-1) Series Routers" section

IOS XR 3.7.2 on the ASR9000 Platform

The following are supported:

L2VPN as a PE

MPLS/L3 VPN as a PE

TEM

MDE

IOS XR 3.8.1 on the Cisco 12000 (GSR) Series Routers

The following are supported:

MPLS/L3 VPN

TEM

MDE

L2VPN is not supported.

IOS XR 3.8.1 on the Cisco Carrier Routing System-1 (CRS-1) Series Routers

The following are supported:

L2VPN as a PE

MPLS/L3 VPN as a PE

TEM

MDE

New and Changed Information for ISC 5.2.1

This section lists the new and changed functionality that was added or updated since ISC 5.2 to this ISC 5.2.1 release. The problems fixed are listed in the "Problems Fixed in ISC 5.2.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:

Common Infrastructure New Features

This section includes the following new features:

New DCPL Properties Supported in ISC 5.2.1

New Template Variables Support in ISC 5.2.1

Resolved Deadlock Error During Concurrent Modification of Service Requests

L2VPN and Carrier Ethernet New Features

This section includes the following new features:

Configuring an EVC/SVI Hybrid Scenario

Service Instance Name Support for FlexUNI/EVC Service Requests

FlexUNI/EVC Service Requests Referring to the Same VPN Can Have Different Core Types

Connect Name Limitation in FlexUNI/EVC Service Requests Resolved

New L2VPN-Related Template Variables

Restricting Spanning Tree Command for the ME3400 Device

Restricting Switchport Trunk Encapsulation dot1q Command on the CAT 6500

Support for IOS XR 3.7.2 Across All Blades on the ASR 9000 Platform Only

MPLS/L3 VPN New Features

This section includes the following new features:

Adding Independent IPv4 and IPv6 Route Targets for MPLS Service Requests

Multiple Neighbor and Peering with Bundled Physical Interface for IOS XR PE Devices

Outgoing Interface Name + Next Hop IP Address Support for Static Route Configuration

BGP Multipath Attribute Modification After Upgrade

Documentation Clarification on Editing the VRF and RD Overwrite Attributes in Service Requests

"Traffic Engineering Management (TEM) New Features" section

This section includes the following new features:

"Explicit Path Deletion" section

"Link Deletion with Associated Objects Enhancement" section

API New Features

MPLS Provisioning

L2VPN and Carrier Ethernet Provisioning

FlexUNI/EVC Provisioning

Traffic Engineering Management Provisioning

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

New DCPL Properties Supported in ISC 5.2.1

New Template Variables Support in ISC 5.2.1

Resolved Deadlock Error During Concurrent Modification of Service Requests.

New DCPL Properties Supported in ISC 5.2.1

The following DPCL properties are introduced in the current release.

NegateTemplateDeploy

This DPCL property is located at the following location:

Provisioning\ProvDrv\NegateTemplateDeploy

If the value of this property is set to true, then the negate template will append or prepend, depending on the template association in the service request. If the value of this property is set to false, then the negate template will always prepend.

UniqueRTFeatureEnable

For details on the UniqueRTFeatureEnable DCPL property, see DCPL Property for Independent RTs.

New Template Variables Support in ISC 5.2.1

In addition to the previously supported template variables, found in Chapter 6, Service Design, of the Cisco IP Solution Center Infrastructure Reference, 5.2, 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.

Resolved Deadlock Error During Concurrent Modification of Service Requests

Occasionally, previous to ISC 5.2.1, the ISC GUI displayed the following error message:

ASA error - 306; Deadlock detected

This behavior was reported when users were concurrently deploying service requests associated with the same set of template/data file(s) through the GUI and API. The error message would appear when making modifications on different service requests and/or deploying them. The error was not specific to any particular editing function. The root cause of the problem was that service requests that shared common templates/data files were accessing a feature (introduced in ISC 5.0.1) that involved the addition of the In SR Use column in the Template DataFile Chooser window. As a result, multiple operations would attempt to access the same row in the table, resulting in the deadlock error message. To fix this problem, a change has been introduced in the behavior of text the In SR Use column.

Before ISC 5.2.1, if a data file was not associated with any service request(s) initially, the text in the In SR Use column was No (plain text, no hyperlink). Later, when the data file was associated with any service request(s), the text in the column was Yes. In this case, the text was a hyperlink, which when clicked would display a list of all service requests associated with the data file. When all associated services requests were subsequently no longer using the data file, the text in the column would revert to No.

Starting in ISC 5.2.1, if a data file is not associated with any service request(s) initially, the text in the In SR Use column is View, which is an active hyperlink. When any service request(s) are subsequently associated with the data file, if you click the View link, ISC displays a list of the associated service request(s) in a table. Later, if all associated service request(s) are no longer using the data file, the View hyperlink is still present, but clicking on it displays an empty table.

L2VPN and Carrier Ethernet New Features

All L2VPN and Carrier Ethernet 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, 5.2.

The following L2VPN and Carrier Ethernet enhancements were added in ISC 5.2.1:

Configuring an EVC/SVI Hybrid Scenario

Service Instance Name Support for FlexUNI/EVC Service Requests

FlexUNI/EVC Service Requests Referring to the Same VPN Can Have Different Core Types

Connect Name Limitation in FlexUNI/EVC Service Requests Resolved

New L2VPN-Related Template Variables

Restricting Spanning Tree Command for the ME3400 Device

Restricting Switchport Trunk Encapsulation dot1q Command on the CAT 6500

Support for IOS XR 3.7.2 Across All Blades on the ASR 9000 Platform Only

Configuring an EVC/SVI Hybrid Scenario

ISC supports a hybrid configuration for FlexUNI/EVC service requests. In a hybrid configuration, the forwarding commands (such as xconnect, associating to bridge domain, etc.) for one side of an attachment circuit can be configured under a service instance, and the xconnect configuration for the other side of the attachment circuit can be configured under a switch virtual interface (SVI).

This feature is supported through a new attribute, N-PE Pseudo-wire on SVI, available in the FlexUNI/EVC policy and service request workflows. The N-PE Pseudo-wire on SVI attribute is applicable for all connectivity types (PSEUDOWIRE, VPLS, and LOCAL), but a hybrid SVI configuration is possible only for pseudowire connectivity.

Table 1 shows various use cases for hybrid configuration for FlexUNI/EVC service requests.

Table 1 Use Cases for Hybrid Configuration for FlexUNI /EVC Service Requests

Use Bridge Domain
FlexUNI
N-PE Pseudowire on SVI
CLIs Generated

True

True

True

xconnect under VLAN interface.

Service instance under main interface.

True

True

False

xconnect under service instance.

Service instance under main interface.

False

True

N/A

xconnect under service instance.

Service instance under main interface.

True

False

True

xconnect under VLAN interface.

True

False

False

xconnect under subinterface.

False

False

False

xconnect under subinterface.


The following sections describe changes in the ISC GUI, discuss NBI support, and provide sample configlets for this feature.

FlexUNI/EVC Policy —Graphical User Interface Details

The N-PE Pseudowire on SVI attribute is available in the Interface Attributes window in the FlexUNI/EVC policy workflow. The feature is activated using a check box, as shown in Figure 1.

Figure 1 N-PE Pseudo-wire on SVI Attribute in the FlexUNI/EVC Policy Workflow

Usage notes:

If the N-PE Pseudo-wire on SVI check box is checked in the FlexUNI/EVI policy and service request, ISC generates forwarding commands under SVIs. If the check box is not checked, ISC generates forwarding commands under the service instance. For examples of these cases, see the section Sample Configlets.

If the Editable check box for N-PE Pseudo-wire on SVI is checked, you can modify it during the creation of the service request based on the policy (as per normal ISC behavior).

When MPLS Core Connectivity Type is set as VPLS, the N-PE Pseudo-wire on SVI attribute is always enabled in the policy.

When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy.

FlexUNI/EVC Service Request—Graphical User Interface Details.

The N-PE Pseudowire on SVI attribute is available in the Link Attributes section of the Standard UNI Details window in the FlexUNI/EVC service request workflow. The feature is activated using a check box, as shown in Figure 2.

Figure 2 N-PE Pseudo-wire on SVI Attribute in FlexUNI/EVC Service Request Workflow

Usage Notes:

If the N-PE Pseudowire on SVI check box is checked in the FlexUNI/EVI policy and service request, ISC generates forwarding commands under SVIs. If the check box is not checked, ISC generates forwarding commands under the service instance. For examples of these cases, see the section Sample Configlets.

If the Editable check box for N-PE Pseudo-wire on SVI is checked in the policy, you can modify it during the creation of the service request.

When MPLS Core Connectivity Type is set as VPLS, the N-PE Pseudo-wire on SVI attribute is always enabled in the policy and service request.

When MPLS Core Connectivity Type is set as LOCAL connectivity type, the N-PE Pseudo-wire on SVI attribute is always disabled in the policy and service request.

The N-PE Pseudo-wire on SVI attribute is not editable during the modification of a service request, but it is editable when adding a new link during the modification of a service request.

Northbound Interface (NBI)

The hybrid configuration for a FlexUNI/EVC service request is supported in the NBI. See FlexUNI/EVC Provisioning.

Sample Configlets

This section provides sample configlets for hybrid configurations using this feature.

In the first example, shown in Table 2, Configure with Bridge Domain and N-PE Pseudo-wire on SVI are both enabled on the N-PE. Key CLIs are shown in bold text.

Table 2 Sample Configlet 1

U-PE
N-PE
vlan 452
exit
!
interface FastEthernet1/0/10
no ip address
switchport trunk allowed vlan add 452
!
interface FastEthernet1/0/13
no spanning-tree bpdufilter enable
switchport
no keepalive
no ip address
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 452
switchport nonegotiate
vlan 3524
exit
!
ethernet evc Customer1_253
!
interface GigabitEthernet7/0/0
service instance 3 ethernet Customer1_253 
encapsulation dot1q 452
rewrite ingress tag pop 1 symmetric
bridge-domain 3524 split-horizon 
!
interface Vlan3524 
no ip address
description BD=T,SVI=T,Flex 
xconnect 22.22.22.22 52500 encapsulation mpls 
backup peer 22.22.22.22 52501 
no shutdown

In the second example, shown in Table 3, Configure with Bridge Domain and N-PE Pseudo-wire on SVI are both disabled on the N-PE. Key CLIs are shown in bold text.

Table 3 Sample Configlet 2

U-PE
N-PE
vlan 545
exit
!
interface FastEthernet1/0/10
no ip address
switchport trunk allowed vlan add 545
!
interface FastEthernet1/0/12
no spanning-tree bpdufilter enable
switchport
no keepalive
no ip address
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 545
switchport nonegotiate
mac access-group 
ISC-FastEthernet1/0/12 in
ethernet evc Customer1_248
!
interface GigabitEthernet7/0/0
service instance 2 ethernet Customer1_248 
encapsulation dot1q 545
rewrite ingress tag pop 1 symmetric 
xconnect 22.22.22.22 52498 encapsulation mpls 
backup peer 22.22.22.22 52499 

Service Instance Name Support for FlexUNI/EVC Service Requests

Prior to ISC 5.2.1, ISC did not allow you to manually set the service instance name within FlexUNI/EVC service requests. Instead, ISC autogenerated the service instance name in the following pattern: CustomerName_ServiceRequestJobID. Starting in ISC 5.2.1, ISC optionally allows you to provide the service instance name manually.

This feature is supported through a new attribute, AutoPick Service Instance Name, available in the FlexUNI/EVC policy and service request workflows.

The following sections describe changes in the ISC GUI, discuss NBI support, and provide sample configlets for this feature.

FlexUNI/EVC Policy —Graphical User Interface Details

The AutoPick Service Instance Name attribute is available in the FlexUNI Attributes window in the FlexUNI/EVC policy workflow. The feature is enabled using a check box, as shown in Figure 3

Figure 3 AutoPick Service Instance Name Attribute in the FlexUNI/EVC Policy Workflow

Usage Notes:

This attribute is optional.

If the Autopick Service Instance Name check box is checked, a service instance name is autogenerated by ISC when you create a service request based on the policy. If the check box is not checked, then you can enter a value during the service request workflow.

If the Editable check box for the Autopick Service Instance Name attribute is checked, you can modify the attribute during the creation of the service request based on the policy (as per normal ISC behavior).

FlexUNI/EVC Service Request—Graphical User Interface Details

The AutoPick Service Instance Name attribute and Service Instance Name text input field are available in the FlexUNI(EVC) Details window of the FlexUNI/EVC workflow, as shown in Figure 4.

Figure 4 AutoPick Service Instance Name Attribute in the FlexUNI/EVC Service Request Workflow

Usage Notes:

If the check box for the AutoPick Service Instance Name is checked, ISC autogenerates a value in the following pattern: CustomerName_ServiceRequestJobID. In this case, the Service Instance Name text field is disabled.

If AutoPick Service Instance Name is unchecked, you can manually enter a value in the Service Instance Name text field. The text string representing the service instance name must be 40 characters or less and contain no spaces. Other special characters are allowed.

If AutoPick Service Instance Name is unchecked and no service instance name is entered in the text field, then ISC does not generate the global ethernet evc evcname command in the device configuration generated by the service request.

Northbound Interface (NBI)

This feature is supported in the NBI. See FlexUNI/EVC Provisioning.

Sample Configlets

This section provides sample configlets using this feature.

The first example, shown in Table 4, shows a case in which the user does not enable AutoPick Service Instance Name and also leaves the Service Instance Name input field blank. In this case, the global command ethernet evc is not generated, while the command service instance 43 ethernet is generated. There is no Service Instance Name available and the Service Instance ID is 43. Key CLIs are shown in bold text.

Table 4 Configlet Example 1

U-PE
N-PE
!
vlan 566
exit
!
interface FastEthernet1/0/14
no spanning-tree bpdufilter enable
switchport
no keepalive
no ip address
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 566
switchport nonegotiate
no shutdown
mac access-group 
ISC-FastEthernet1/0/14 in
!
interface FastEthernet1/0/18
no ip address
switchport trunk allowed vlan 566
!
mac access-list extended 
ISC-FastEthernet1/0/14
deny any host 0100.0ccc.cccc
deny any host 0100.0ccc.cccd
deny any host 0100.0ccd.cdd0
deny any host 0180.c200.0000
permit any any
!
interface GigabitEthernet7/0/2
service instance 43 ethernet 
encapsulation dot1q 566
xconnect 1.1.1.1 453366 encapsulation mpls


The second example, shown in Table 5, shows a case in which the transport type is PSEUDOWIRE. Here, the user manually provided ServiceInst as the Service Instance Name. This is pushed onto the device, where the Service Instance ID is 3. Key CLIs are shown in bold text.

Table 5 Configlet Example 2

U-PE
N-PE
!
vlan 452
exit
!
interface FastEthernet1/0/10
no ip address
switchport trunk allowed vlan add 452
!
interface FastEthernet1/0/13
no spanning-tree bpdufilter enable
switchport
no keepalive
no ip address
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 452
switchport nonegotiate
mac access-group 
ISC-FastEthernet1/0/13 in

!
vlan 3524
exit
!
ethernet evc ServiceInst 
!
interface GigabitEthernet7/0/0
service instance 3 ethernet  ServiceInst 
encapsulation dot1q 452
rewrite ingress tag pop 1 symmetric
bridge-domain 3524 split-horizon
!
interface Vlan3524
no ip address
description BD=T,SVI=T,Flex
xconnect 22.22.22.22 52500 encapsulation 
mpls
backup peer 22.22.22.22 52501
no shutdown

The third example, shown in Table 6, shows a case in which the transport type is LOCAL. Here, the user manually provided service_int as the Service Instance Name. This is pushed onto the device, where the Service Instance IDs are 5 and 33, respectively. Key CLIs are shown in bold text.

Table 6 Configlet Example 3

U-PE
N-PE
vlan 45
exit
!
interface FastEthernet1/0/12
no ip address
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 45
!
interface FastEthernet1/0/14
no spanning-tree bpdufilter enable
switchport
no keepalive
no ip address
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 45
switchport nonegotiate
no shutdown
mac access-group 
ISC-FastEthernet1/0/14 in
!
mac access-list extended 
ISC-FastEthernet1/0/14
deny any host 0100.0ccc.cccc
deny any host 0100.0ccc.cccd
deny any host 0100.0ccd.cdd0
deny any host 0180.c200.0000
permit any any
ethernet evc  service_int 
!
interface GigabitEthernet1/0/6
no shutdown
service instance 5 ethernet service_int 
encapsulation dot1q 56
!
interface GigabitEthernet1/0/7
no shutdown
service instance 33 ethernet service_int 
 encapsulation dot1q 45
!
connect Customer2_195 GigabitEthernet1/0/7 
33 GigabitEthernet1/0/6


FlexUNI/EVC Service Requests Referring to the Same VPN Can Have Different Core Types

Before ISC 5.2.1, if you created a FlexUNI/EVC service request with a VPN and MPLS Core Connectivity Type LOCAL, you could not use the same VPN for other service requests with VPLS or PSEUDOWIRE core type. Starting with ISC 5.2.1, the same VPN can be used by service requests with LOCAL and PSEUDOWIRE core types. If a VPN for a service request is used with VPLS core type, the same VPN cannot be used for service requests with LOCAL or PSEUDOWIRE core type.

Connect Name Limitation in FlexUNI/EVC Service Requests Resolved

Before ISC 5.2.1, the connect name for a LOCAL core type was generated using the following format:

CustomerName_ServiceRequestJobID.

Because the device only accepts a maximum of 15 characters for the connect name, the autogenerated connect name would exceed 15 characters when the customer name was too long.

Starting with ISC 5.2.1, the connect name is generated using the following (new) format:

CustomerNameTruncatedToMaxPossibleCharacters_ServiceRequestJobID

For example, if the customer name is NorthAmericanCustomer and the service request job ID is 56345, the autogenerated connect name would be NorthAmer_56345.

The CLI generated would be:

connect NorthAmer_56345 GigabitEthernet7/0/5 11 GigabitEthernet7/0/4 18

In this case, 11 and 18 are service instance IDs.

New L2VPN-Related Template Variables

In ISC 5.2.1, the following template variables have been added and are available for use within templates for L2VPN services.

L2VPNSrJobId—Get job ID in L2VPN service requests.

VPLSSrJobId—Get job ID in VPLS service requests.

SR_JOB_ID—Get job ID in FlexUNI/EVC service requests.

L2VPNConnectName—Fetch unique ATM connection name with a combination of service_request_job_id + vpn_name, limited to 15 characters for L2VPN ATM-ATM service type.

Restricting Spanning Tree Command for the ME3400 Device

Support for Spanning Tree Protocol (STP) and the related commands is now available for the ME 3400 device. This is only for the port-type NNI and ENI on which STP has been enabled. The device does not support STP for port-type UNI and ENI when STP has not been enabled. Therefore, the spanning-tree bpdufilter enable CLI is restricted for the device ME3400 (according to the above conditions) for L2VPN policies.

Restricting Switchport Trunk Encapsulation dot1q Command on the CAT 6500

Previous releases of ISC (before version 5.2.1) generated the switchport trunk encapsulation dot1q CLI, which is not supported on the CAT 6500 running IOS 12.2(18) SXF16 with the 6548 line card. ISC 5.2.1 does not generate this CLI on this platform. This behavior only affects this particular platform and IOS version.

Support for IOS XR 3.7.2 Across All Blades on the ASR 9000 Platform Only

L2VPN features in L2VPN service requests are supported on the ASR 9000 platform running IOS XR 3.7.2.


Note Provisioning support for L2VPN for the platform and IOS XR version is only for EWS (EPL) and ERS (EVPL). VPLS and FlexUNI/EVC do not support IOS XR provisioning.


MPLS/L3 VPN New Features

All MPLS/L3 VPN features, with the exception of the new features since ISC 5.2, are explained in detail in the Cisco IP Solution Center MPLS VPN User Guide, 5.2.

The following MPLS/L3 VPN enhancements were added in ISC 5.2.1:

Adding Independent IPv4 and IPv6 Route Targets for MPLS Service Requests

Multiple Neighbor and Peering with Bundled Physical Interface for IOS XR PE Devices

Outgoing Interface Name + Next Hop IP Address Support for Static Route Configuration

BGP Multipath Attribute Modification After Upgrade

Documentation Clarification on Editing the VRF and RD Overwrite Attributes in Service Requests

Adding Independent IPv4 and IPv6 Route Targets for MPLS Service Requests

ISC supports independent IPv4 and IPv6 route targets (RTs) for CE routing communities (CERCs). This feature is only supported for IOS XR devices, as IPv6 is not supported in IOS. You can configure this feature when setting the PE VPN membership attributes in the VRF and VPN window of the service request creation workflow. A new attribute, CERC Type, provides a drop-down list in which you can specify the address family of the CERCs as IPv4, IPv6, or IPv4+IPv6 (dual-stacked).


Note This feature is enabled by setting a DCPL property. For more information about this see DCPL Property for Independent RTs.


The following sections describe changes in the ISC GUI; discuss NBI, DCPL, and template variable support; and provide sample configlets for this feature.

MPLS Service Request —Graphical User Interface Details

You specify the CERC Type attribute in the PE VPN Membership section of the MPLS Link Attributes Editor - VRF and VPN window of the MPLS service request workflow, as shown in Figure 5.

Figure 5 CERC Type Attribute in the PE VPN Membership Section of the MPLS Service Request Workflow

Usage notes:

During service request creation, you can specify the RT type of a CERC in the PE VPN Membership section of the VRF and VPN window. It is specified in a drop-down list in the CERC Type column. The list choices are:

IPv4. If you select IPv4, the corresponding CERC RTs are applied to the ipv4 address-family CLI in the device configuration.

IPv6. If you select IPv6, the corresponding CERC RTs are applied to the ipv6 address-family CLI in the device configuration.

IPv4+IPv6 (dual-stacked). If you select IPv4+IPv6, the same RTs are applied for both address families.

The choices available in the CERC Type drop-down list depend on the IP addressing scheme selected for the service request. This is determined by the IP Number Scheme attribute in the IP Addressing Scheme window of the MPLS Link Editor workflow.

If you select IPV4+IPV6 address family, at least one CERC type should be IPV4+IPV6 or two (or more) individual CERCs, with at least one of type IPv4 and the other(s) of type IPv6. If you do not do so, ISC generates an error.

If you select IPV4+IPV6 address family, the CERC type should be one of the following:

Single CERC: IPV4+IPV6

Two (or more) individual CERCs: At least one of type IPv4 and the other(s) of type IPv6

If you do not do this, ISC generates an error.

If an existing service request is deployed only for IPv4 and you later modify the service request as dual-stacked (IPv4+IPv6), ISC changes the tagging for the CERCs added based on the address family. This also applies to a case in which the service request is modified from IPv6 to dual-stacked (IPv4+IPv6).

When modifying a service request, if the CERC type is changed, you can add or remove CERCs/VPNs also.

If VPN association is set up at the policy level and specified as non-editable, then while creating a service request using this policy, the tagging of the CERC types is decided based on the address family which was chosen in the policy.

If an existing dual-stacked (IPv4+IPv6) service request is modified to the IPv4 or IPv6 address family, ISC automatically changes the CERC tagging to the selected address family.

ISC checks for other service requests on the same PE that are using the same VPN, to make sure that RTs being used by other service requests are not modified or removed.

The independent RTs for IPv4 and IPv6 feature is supported with the VRF and RD Overwrite option.

The independent RTs for IPv4 and IPv6 feature is only applicable for PE devices running IOS XR.

The independent RTs for IPv4 and IPv6 feature is not supported for MVRFCE service requests.

The independent RTs for IPv4 and IPv6 feature is not supported for independent VRF service requests and MPLS service requests using and independent VRF.

North Bound Interface (NBI)

This feature is supported in the NBI. See MPLS Provisioning.

DCPL Property for Independent RTs

The independent RTs for IPv4 or IPv6 feature is controlled through the DCPL property GUI\MplsVPN\UniqueRTFeatureEnable. The default value for this property is false. To use the independent RTs for IPv4 or IPv6 feature, you must set the DCPL property to true.

Controlling the feature through a DCPL property ensures that other customers' flows are not affected (that is, those who do not want to use this feature). Customers who desire to use this feature can enable it through the DCPL property.

Template Variables

The following template variables are supported for independent RTs:

MPLSExportRouteTargets—Template variable for export RTs under IPv4 address family.

MPLSImportRouteTargets—Template variable for import RTs under IPv4 address family.

MPLSExportRouteTargets_IPV6—Template variable for export RTs under IPv6 address family.

MPLSImportRouteTargets_IPV6—Template variable for import RTs under IPv6 address family.

The following example shows how the template variables might be used in a template file.

vrf MyVRF2
address-family ipv4 unicast
import route-target
#foreach($name in $MPLSImportRouteTargets)
$name
#end
export route-target
#foreach($name in $MPLSExportRouteTargets)
$name
#end
address-family ipv6 unicast
import route-target
#foreach($name in $MPLSImportRouteTargets_IPV6 )
$name
#end
export route-target
#foreach($name in $MPLSExportRouteTargets_IPV6 )
$name
#end 

Sample CLI Configlets

The following examples show CLI configlets for the specified independent RT configurations. All configlets are deployed on the PE device.

Example 1: CE-PE with CERC Type set as IPv4.

address-family ipv4 unicast 
  import route-target 
   7777:12345 
  export route-target 
   7777:12345   
 address-family ipv6 unicast 

Note If the CERC were tagged as IPv6, the RTs would be configured under ipv6 address-family.


Example 2: PE-CE with CERC Type set as IPv4+IPv6.

address-family ipv4 unicast 
  import route-target 
   7777:12345 
  export route-target 
   7777:12345 
address-family ipv6 unicast 
  import route-target 
   7777:123456 
  export route-target 
   7777:123456

Note If there were additional IPv4 or IPv6 CERCs selected and tagged, they would be incrementally added into the above format under the appropriate address-family CLIs.


Example 3: Adding More VPNs

When adding more VPNs to the configuration, then one VPN name shows up in the configlet with the the string -etc appended, as shown below.

vrf V872:vpn2-etc
address-family ipv4 unicast
import route-target
64512:1005
!
export route-target
64512:1005
!
!

Sample XML Configlets

The following is a sample XML configlet for PE-CE with CERC Type set as IPv4+IPv6. The configlet is deployed on the PE device. Key XML tags are shown in bold text.

<?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion="1" MinorVersion="0">
 <CLI>
<Configuration>
vrf V6:Verve_VPN32
address-family ipv6 unicast
import route-target <?xml version="1.0" encoding="UTF-8"?>
<Request MajorVersion="1" MinorVersion="0">
 <CLI>
<Configuration>
vrf V6:Verve_VPN32
address-family ipv6 unicast
import route-target 64512:25428
import route-target 64512:25429
export route-target 64512:25428
exit
interface GigabitEthernet0/3/0/2.3039
ipv6 address 10::12/24
ipv6 address 10::15/32
ipv6 address 15::20/28
</Configuration>
</CLI>
  <Set>
    <Configuration Source="CurrentConfig">
      <VRFTable>
        <VRF>
          <Naming>
            <Name>V6:Verve_VPN32</Name>
          </Naming>
          <Create>true</Create>
          <AFI_SAFITable>
            <AFI_SAFI>
              <Naming>
                <AFI>IPv4</AFI>
                <SAFI>Unicast</SAFI>
                <Topology>default</Topology>
              </Naming>
              <Create>true</Create>
              <BGP>
                <ImportRouteTargets>
                  <RouteTargetTable>
                    <RouteTarget>
                      <Naming>
                        <Type>AS</Type>
                        <AS>64512</AS>
                        <ASIndex>254288</ASIndex>
                      </Naming>
                      <True>true</True>
                    </RouteTarget>
                    <RouteTarget>
                      <Naming>
                        <Type>AS</Type>
                        <AS>64512</AS>
                        <ASIndex>254299</ASIndex>
                      </Naming>
                      <True>true</True>
                    </RouteTarget>
                  </RouteTargetTable>
                </ImportRouteTargets>
                <ExportRouteTargets>
                  <RouteTargetTable>
                    <RouteTarget>
                      <Naming>
                        <Type>AS</Type>
                        <AS>64512</AS>
                        <ASIndex>254288</ASIndex>
                      </Naming>
                      <True>true</True>
                    </RouteTarget>
                  </RouteTargetTable>
                </ExportRouteTargets>
              </BGP>
            </AFI_SAFI>
          </AFI_SAFITable>
        </VRF>
      </VRFTable>
    </Configuration>
  </Set>
</Request>

Multiple Neighbor and Peering with Bundled Physical Interface for IOS XR PE Devices

ISC provides the ability to provision multiple neighbor/multiple BGP peering on a bundled physical interface port channel for IOS XR PE devices. The bundled interface face feature is supported within MPLS policy creation and service request creation.

The following sections describe changes in the ISC GUI, discuss NBI and template variable support, and provide sample configlets for this feature.

Bundle Interface Support in MPLS Policy Creation—Graphical User Interface Details

You specify bundle interface support by choosing the Bundle-Ether choice in the drop-down list of the Interface Type attribute of the MPLS Policy Editor - Interface window within the MPLS policy creation workflow, as shown in Figure 6.

Figure 6 Interface Type Attribute in the Interface Window of the MPLS Policy Workflow

Usage notes:

While creating the policy, you have the option of selecting the interface type as Bundle-Ether for both the PE_CE and PE_NO_CE policies.

When you select the Interface Type as Bundle-Ether in the policy, only Bundle-Ether interfaces are shown in a service request based this policy.

Bundle Interface Support in MPLS Service Request Creation—Graphical User Interface Details

When you create a service request based on a policy in which the Interface Type attribute is set as Bundle-Ether, ISC displays only bundled interfaces in the PE Interface drop-down list in the MPLS Service Request Editor window, as shown in Figure 7.

Figure 7 PE Interface Selection in the MPLS Service Request Editor Window

Usage notes:

You can select a Bundle-Ether interface for an IOS XR device based on the interface type specified in the corresponding policy.

Bundle-Ether interfaces are only visible in the service request if one or more Bundle-Ether interfaces are pre-configured on the selected PE device. That is, port channel must be preconfigured on the device prior to creating the service request. Port channel interfaces are used for VRF termination.

Links can be IPv4 and/or IPv6. Note the following points:

On the Cisco Carrier Routing System One (CRS-1) router, both IPv4 and IPv6 links are supported. Multicast is not supported for IPv6. See the following link for more information:

http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/interfaces/command/reference/
hr38lbun.html#wp1410649

http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/multicast/configuration/guide/
mc38mcst.html#wp1168111

http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/multicast/configuration/guide/
mc38mcst.html#wp1290965

On the Cisco 12000 (also known as a Gigabit Switch Router or GSR), only IPv4 links are supported; this is a device restriction. See the following link for more information:

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/lnkbndl.html

The multiple neighbor and peering with bundled physical interface feature is not supported for MVRFCE service requests.

After a bundled interface has been selected, the Interface Name attribute the MPLS Link Attributes Editor - Interface window is set as a Bundle-Ether interface, as shown in Figure 8.

Figure 8 Interface Attributes in the MPLS Link Attributes Editor - Interface Window

Usage notes:

The Interface Name attribute provides a text field in which you can enter a subinterface value. The allowed range is from 0 to 2147483647. If you do not provide a subinterface number, ISC uses the VLAN ID number as the subinterface number.

The Interface Description text field is used to enter a description for the interface. This is an optional attribute.

The Shutdown Interface check box is used to configure the PE interface in a shutdown state. This is an optional attribute.

The PE Encapsulation attribute allows you to choose an encapsulation type for the PE interface. The choices in the drop-down list are determined by the interface type. For the Bundle-Ether interface type, the choices are DOT1Q and DEFAULT.

The VLAN ID attribute is required if the Auto-Pick VLAN ID check box is not checked. The value must be a value from 1 to 4094.

When the Auto-Pick VLAN ID attribute is checked, ISC autopicks the VLAN ID from the VLAN pool.

This feature is configured only on the PE device in the service request.

PE-CE links must be physical links.

Configurations are applied to each BGP neighbor.

North Bound Interface (NBI)

This feature is supported in the NBI. See MPLS Provisioning.

Template Variables

The following template variables are supported for the bundle interface feature:

PE_Intf_Name—PE interface name.

PE_Intf_Shutdown—PE interface shutdown.

PE_Intf_Desc—PE interface description.

PE_Intf_Encap—PE interface encapsulation.

PE_Vlan_ID—PE VLAN ID.

The following example shows how the template variables might be used in a template file.

interface $PE_Intf_Name
description $PE_Intf_Desc
vrf ISC521
ipv4 address 66.174.25.3 255.255.255.254
ipv6 address 2001:4888:10:100::3/64
$PE_Intf_Encap vlan $PE_Vlan_ID
!

Sample CLI Configlets

The following example is a CLI configlet for the bundle interface feature. The configlet is deployed on the PE device.

interface Bundle-Ether147
 description Bun
!
interface Bundle-Ether147.369
 description subbun
 vrf ISC521
 ipv4 address 66.174.25.3 255.255.255.254
 ipv6 address 2001:4888:10:100::3/64
 dot1q vlan 269
!

Sample XML Configlets

The following is a sample XML configlet for the bundle interface feature. The configlet is deployed on the PE device.

<InterfaceConfiguration>
     <Naming>
	<Active>act</Active>
	  <Name>Bundle-Ether147</Name>
        </Naming>
        <InterfaceVirtual>true</InterfaceVirtual>
	<Description>Bun</Description>
 </InterfaceConfiguration>

<InterfaceConfiguration>
     <Naming>
	<Active>act</Active>
	<Name>Bundle-Ether147.369</Name>
     </Naming>
     <InterfaceModeNonPhysical>Default</InterfaceModeNonPhysical>
	<Description>subbun</Description>
	<VRF MajorVersion="3" MinorVersion="3">ISC521</VRF>
	<IPV4Network MajorVersion="5" MinorVersion="0">
	   <Addresses>
		<Primary>
		   <IPAddress>66.174.25.3</IPAddress>
		    <Mask>255.255.255.254</Mask>
		</Primary>
	   </Addresses>
       </IPV4Network>
	<VLANSubConfiguration MajorVersion="2" MinorVersion="1">
	    <VLANIdentifier>
		<VlanType>VLANTypeDot1q</VlanType>
		 <FirstTag>269</FirstTag>
	    </VLANIdentifier>
   </VLANSubConfiguration>
</InterfaceConfiguration>

Outgoing Interface Name + Next Hop IP Address Support for Static Route Configuration

ISC provides the ability to specify the outgoing interface name and next hop IP address when creating MPLS service requests for STATIC routing protocol. You do this by choosing OUTGOING_INTF_NAME+NEXT_HOP_IPADDR from the drop-down list of the Next Hop Option attribute in the MPLS Link Attribute Editor - IPv4/IPv6 Routing Information window in the MPLS service creation workflow.


Note IPv6 is only supported on IOS XR devices. IOS does not currently support IPv6.


The following sections describe changes in the ISC GUI, discuss NBI and template variable support, and provide sample configlets for this feature.

Outgoing Interface Name + Next Hop IP Address Support for Static Route Configuration in MPLS Service Request Creation—Graphical User Interface Details

When you create a service request, you set the routing protocol attributes in the MPLS Link Attribute Editor - IPv4/IPv6 Routing Information window. When you set the Routing Protocol attribute to STATIC, the window displays related attributes, including the Next Hop Option, as shown in Figure 9.

Figure 9 Next Hop Option in the MPLS Link Attribute Editor - IPv4/IPv6 Routing Information Window

Usage notes:

The OUTGOING_INTF_NAME+NEXT_HOP_IPADDR selection the Next Hop Option drop-down list enables you to provide an outgoing interface name and next hop IP address. ISC supports this format for static route configuration in the following form:

network_address + outgoing_interface_name + next_hop_address

Example: 69.82.224.99/32 GigabitEthernet0/0/0/0 66.174.25.0.

This format is supported for:

PE_CE and PE_NO_CE service requests

IPv4 and IPv6 addressing

IOS and IOS XR devices

This feature is configured only on the PE device.

You can configure the network address by clicking the Edit button of Advertise Routes for CE attribute.

North Bound Interface (NBI)

This feature is supported in the NBI. See MPLS Provisioning.

Template Variables

The following template variables are supported.

IPv4 address family:

Advr_Routes_IP_Address—Network IPv4 address for IPv4 address family.

Advr_Routes_Metric—Metric value for IPv4 address family.

STATIC_NEXT_HOP_IP_ADDR—Next hop IPv4 IP address for IPv4 address family.

IPv6 address family:

Advr_Routes_IPV6_Address—Network IPv6 address for IPv6 address family.

Advr_Routes_Metric_IPV6—Metric value for IPv6 address family.

STATIC_NEXT_HOP_IPV6_ADDR—Next hop IPv6 IP address for IPv6 address family.

The following example shows how the template variables might be used in a template file for an IOS device:

ip route vrf V2:TempIOS $Advr_Routes_IP_Address 255.255.255.255 $PE_Intf_Name 
$STATIC_NEXT_HOP_IP_ADDR $Advr_Routes_Metric

The following example shows how the template variables might be used in a template file for an IOS XR device:

router static 
 vrf V21:TempIOSXR
  address-family ipv4 unicast
   $Advr_Routes_IP_Address $PE_Intf_Name $STATIC_NEXT_HOP_IP_ADDR  $Advr_Routes_Metric
  !
  address-family ipv6 unicast
   $Advr_Routes_IPV6_Address $PE_Intf_Name $STATIC_NEXT_HOP_IPV6_ADDR 
$Advr_Routes_Metric_IPV6

Sample CLI Configlets

The following is a sample CLI configlet for an IOS device. Key CLIs are shown in bold text.

router bgp 64512
address-family ipv4 vrf V14:July7_VPN
redistribute static
exit-address-family
!
ip route vrf V14:July7_VPN 15.18.16.17 255.255.255.255  GigabitEthernet0/3/0/0 10.12.16.19 
78 

The following is a sample CLI configlet for an IOS XR device. Key CLIs are shown in bold text.

router static
 vrf V7:techm_vpn
  address-family ipv4 unicast
   12.23.34.34/32  GigabitEthernet0/3/0/2 10.14.54.18 45 
 !
  address-family ipv6 unicast
   15:16:17:13:14:15:17:18/128 GigabitEthernet0/3/0/2  18:12:13:14:16:13:16:14
  !

Sample XML Configlets

The following is a sample XML configlet for IPv4 address family. Key CLIs are shown in bold text.

<VRF>
  <Naming>
   <VRFName>V1:VPN_June22</VRFName>
  </Naming>
  <AddressFamily>
   <VRFIPV4>
     <VRFUnicast>
      <VRFPrefixTable>
        <VRFPrefix>
         <Naming>
           <Prefix>
            <IPV4Address>10.77.66.58</IPV4Address>
           </Prefix>
           <Length>32</Length>
         </Naming>
         <VRFRouteTable>
           <VRFNexthopInfoTable>
            <VRFNexthopInfo>
              <Naming>
               <Interface>GigabitEthernet0/3/0/0</Interface> 
                 <Address>
                  <IPV4Address>10.12.16.19</IPV4Address>
                 </Address>
              </Naming>
              <Metric>48</Metric>
            </VRFNexthopInfo>
           </VRFNexthopInfoTable>
         </VRFRouteTable>
      </VRFPrefix>
      </VRFPrefixTable>
     </VRFUnicast>
   </VRFIPV4>
  </AddressFamily>
</VRF>

The following is a sample XML configlet for IPv6 address family. Key CLIs are shown in bold text.

<VRF>
 <Naming>
  <VRFName>V39:techm_vpn</VRFName>
 </Naming>
 <AddressFamily>
  <VRFIPV6> 
    <VRFUnicast>
     <VRFPrefixTable>
      <VRFPrefix>
       <Naming>
        <Prefix>
         <IPV6Address>10::19</IPV6Address>
        </Prefix>
         <Length>128</Length>
       </Naming>
       <VRFRouteTable>
        <VRFNexthopInfoTable>
         <VRFNexthopInfo>
          <Naming>
           <Interface>GigabitEthernet0/3/0/0</Interface> 
           <Address>
            <IPV6Address>45::10</IPV6Address>
           </Address>
          </Naming>
          <Metric>75</Metric>
         </VRFNexthopInfo>
        </VRFNexthopInfoTable>
       </VRFRouteTable>
      </VRFPrefix>
     </VRFPrefixTable>
    </VRFUnicast>
   </VRFIPV6>
 </AddressFamily>
</VRF>

BGP Multipath Attribute Modification After Upgrade

Currently, existing services in ISC 5.1 cannot modify BGP attributes that are marked as noneditable in existing policies. Therefore, when you create or modify service requests based on such noneditable policies, you cannot use the BGP multipath for IOS XR devices feature, which was introduced in ISC 5.2.

A workaround is now available for customers who want to use this feature. The workaround is included in the ISC 5.2.1 upgrade script.


Note This upgrade script change is non-optional. There is no specific user input required to execute it.


The workaround does the following:

Enables BGP Multipath attributes to appear in the GUI when creating or modifying a service request based on an existing policy.

Changes the parent attributes for BGP multipath in existing policies from noneditable to editable.

Documentation Clarification on Editing the VRF and RD Overwrite Attributes in Service Requests

Once a user specifies values to sub-attributes under the VRF and RD Overwrite attribute (that is, the VRF Name and RD Value attributes) and saves the MPLS service request, both of these fields are disabled and are no longer editable. This behavior was introduced in ISC 4.3.5 because changing the default values for the VRF Name and RD Value can alter or disable currently running service requests. Therefore, if these values need to be changed on a deployed service request, the workaround is that you must decommission and purge the service request and create a new service request. In the case of a new service request that has not yet been deployed, you must force purge the service request and then create a new service with new values.

Traffic Engineering Management (TEM) New Features

All TEM features, with the exception of the new features since ISC 5.2, are explained in detail in the Cisco IP Solution Center Traffic Engineering Management User Guide, 5.2.

The following TEM enhancements were added in ISC 5.2.1:

Explicit Path Deletion

Link Deletion with Associated Objects Enhancement.

Explicit Path Deletion

This release adds support for decommission of explicit paths when deleting/decommissioning primary/backup tunnels. This is only supported for IOS XR.

Whether an explicit path can be deleted in such situations depends on whether they are used by other global applications.

Explicit path deletion goes hand in hand with both SR tunnel deletion for primary managed/unmanaged tunnels, backup tunnels, and any non-conformant tunnels and is applicable to all path option types (STRICT, LOOSE, EXCLUDE).

An explicit path configuration will be automatically removed by ISC when the explicit path is no longer used by any tunnel in the system due to a change in tunnel configuration. This situation occurs when tunnels are deleted in ISC or when tunnels are rerouted in ISC.

When the explicit path configuration is removed from the device, the explicit path will still exist in the ISC database. Such explicit paths remaining in the ISC database can be reused.

Explicit path deletion is not applicable if the user reroutes or deletes the tunnel(s) outside ISC. When a transaction reroutes, deletes, or modifies a tunnel using ISC so that an explicit path is no longer used by any other tunnel, that explicit path configuration will automatically be removed from the device.

Link Deletion with Associated Objects Enhancement

The TE Link List window includes a delete function (the Delete button), which allows you to delete a TE link and the TE interfaces at each end of the link from the ISC repository. It automatically deletes all objects associated with the link deletion action itself, except for primary and backup tunnels traversing the link.

Feature highlights

All explicit paths associated with the link are deleted. If ISC cannot delete any of the paths as they are active with a tunne, then the deletion will fail and state which tunnels are still associated with it.

For the link deletion to be successful, primary and backup tunnels, which explicitly traverse through the link, will have to be manually rerouted/deleted. Tunnels with a dynamic path will not have to be manually rerouted.

Tunnels which offer link protection on the interfaces are deleted. If the tunnel is not offering link protection, the tunnel needs to be rerouted/deleted.

The link marked for deletion will be deleted from any SRLG it is associated with. Complete SRLG will not be deleted when one particular link is deleted, unless the link being deleted is the last one that it is a member of.

Any associated resource SR will be force purged as part of the deletion process.

If one of the interfaces of the link is a protected interface of a backup tunnel, either the tunnel is removed if this is the only protected interface, or if it has multiple protected interfaces, the protected interface is removed from the tunnel.

Link deletion is supported both on IOS and IOS-XR devices.

Restrictions

The TEM GUI prevents you from deleting a link if any TE object is still using that link.

It checks the following objects:

strict explicit paths

protected interfaces of backup tunnels

SRLGs

protected elements

TE resource SRs.

If there are any primary or backup tunnels traversing the path options, an error report will be displayed. Otherwise, a message will be displayed seeking confirmation that the above set of associated objects should be deleted.

Use Case

In this example, we will look at the procedure required when attempting to delete a link that could be traversed by primary or backup tunnels.

Use the following steps:


Step 1 Choose Service Inventory > Inventory and Connection Manager > Traffic Engineering Management > TE Links.

For an illustration, see the appendix on the Traffic Engineering Management GUI in the Cisco IP Solution Center Traffic Engineering Management User Guide, 5.2.

Step 2 Select a TE link by checking the corresponding check box.

Step 3 Click the Delete button.

Step 4 Two things can happen:

A tunnel with path option traverses the link: The link deletion will fail and you will be prompted to reroute or delete those tunnels before trying link deletion again. This will take you to the TE Links List page.

No tunnels with path option traverses the link: A list of TE associated objects will be displayed for that link and you will be prompted to confirm whether you agree to the automatic deletion of TE Link associated objects or have second thoughts and would like to cancel the link deletion transaction.

Step 5 After any necessary tunnels have been rerouted/deleted and link deletion is attempted, a list of objects that are still associated will be displayed.

Step 6 If you want to delete associated TE objects listed after rerouting/deleting primary tunnels, you will get directed to a new window showing the progress of the transaction only when there are tunnels offering backup link protection/protecting multiple interfaces. If there are no tunnels offering backup link protection/protecting multiple interfaces, you are directed to the TE Links window on successful/failure transaction from the associated TE objects list page.

See the note below on associated TE objects.

Step 7 After all the associated objects have been deleted, you will be directed to the TE Links window.


Note on Associated TE Objects

Associated TE objects can be any of the following:

strict explicit paths and loose explicit paths (with strict hop type) traversing the link;

backup tunnels offering link protection;


Note The link will be removed from any SRLGs (if SRLG has more than one link) or both the link and the SRLG will be removed if the link marked for deletion is the only one in the SRLG.


resource SRs;

protected elements.

The associated TE objects in the above list vary depending on the way the link is configured in TEM. For example, if associated TE objects have back tunnels offering link protection, it will direct to the Link Deletion in Progress window. Otherwise, the objects will be removed from the window showing the associated TE objects.

API New Features

This section describes new API features added since ISC 5.2. The existing ISC 5.2 API features are documented in detail in the Cisco IP Solution Center API Programmer Guide, 5.2 and the Cisco IP Solution Center API Programmer Reference, 5.2.

All new features in this release are also supported through APIs.

See the respective sections elsewhere in this document for information on how to use these features in the ISC graphical user interface.


Note Prior to ISC 5.0, XSD files were provided as part of an XML schema to check the validity of XML requests from client machines. However, since ISC 5.0 these XSD files have not been updated or supported.


The following API features have been added in this release:

MPLS Provisioning

L2VPN and Carrier Ethernet Provisioning

FlexUNI/EVC Provisioning.

MPLS Provisioning

This section describes MPLS API enhancements added in this release.

Support has been added for a number of attributes for the following MPLS features:

Independent IPv4/IPv6 route targets

Multiple neighboring/multiple BGP peering with bundled/physical interface

Static Route configuration.

For a more detailed description of these new MPLS features, see MPLS/L3 VPN New Features.

This section includes the following:

Service Definitions

Service Requests

Provisioning Example.

Service Definitions

An MPLS service definition defines attributes for the policy type (MPLSPolicyAttributes), and can include the CE routing community (CERC) membership and redistributed protocol information.

CERC membership defines the CE routing community for this policy and is represented by the VPN routing and forwarding tables (VRFs), and the redistributed protocols define the metric attributes.

No new service definitions have been added in this release.

For more information about how to set MPLS policy attributes and to see an illustration of a policy example, see the MPLS Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2.

Service Requests

An MPLS service request specifies the service definition, assigns device interfaces for the end-to-end wire connections, and the attachment circuit details.

An example of the properties supported for an MPLS VPN link can be seen in the schema diagram in the MPLS Provisioning chapter of the Cisco IP Solution Center API Programmer Guide, 5.2.

Examples of these three features are included below:

Independent route target example

Bundled/physical interface example

Static Route configuration example

Independent route target example

In this example, a service order is created with a unique route target for IPv4 and IPv6.

The attribute relevant for the unique route target example is CERC_RTTYPE (in bold below). The preferred values for CERC_RTTYPE tag are IPv4, IPv6 and dual. If the RT Type mentioned does not match with IPv4 or IPv6 or dual, it will throw an error.

Note the following:

The unique RT feature is supported only for IOS XR devices and only when the corresponding DCPL property is set to true.

When a service request is created, the RT Type of the CERCs mentioned in the CERC_MEMBERSHIP should be indicated.

When modifying a service request, a new CERC of RT Type can be added according to the address family only. Otherwise, it will throw error.

If the CERC_RTTYPE tag is not indicated when modifying the script, the newly added CERC will take RT Type as its address family.

When modifying a service request, the CERC_RTTYPE of an existing CERC can be modified.

When modifying a CERC of RT Type dual to IPv6, pass the CERC name with the RT Type to be modified.

Example:

cerc1=dual is the RT Type at the time the service request is created. This now needs to be changed to IPv6 and when modifying the script, pass cerc1=IPv6 in the CERC_RTTYPE tag. Then the cerc1 RT configuration will be changed to IPv6.

If a CERC needs to be deleted, specify the CERC name in deleteInstance. The specified CERC will be deleted.


Note When creating a service request for dual address family, the RT configuration can be IPv4 and IPv6, or dual. There should be two CERCs, one with IPv4 and another with IPv6, or one CERC with the RT configuration dual. If a service request is created for IPV4 address family, the RT configuration should be only IPv4, and if it is created for IPv6 address family, it should be only IPv6.


File: CreateMPLSServiceOrder_PE_NO_CE_IPV4_IPV6_Unique_RT.xml


<?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="90" 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">ServiceOrder253</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>
              <!--item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">Organization</name>
                <value xsi:type="xsd:string">NbiCustomer</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">Mpls</value>
              </item>
            </properties>     
            <objectPath xsi:type="ns1:CIMObjectPath"> 
              <className xsi:type="xsd:string">ServiceRequestDetails</className>
              <properties xsi:type="ns1:CIMPropertyList"
                        soapenc:arrayType="ns1:CIMProperty[]">
<!-- Policy Info -->            
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">ServiceDefinition</name>
                <value xsi:type="xsd:string">PE_NO_CE</value>
                <qualifier xsi:type="xsd:string">
                  <name xsi:type="xsd:string">ServiceDefinitionType</name>
                  <value xsi:type="xsd:string">Mpls</value>
                </qualifier>
              </item>
              </properties>
              <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">MplsVpnLink</className>
                <properties xsi:type="ns1:CIMPropertyList" 
                       soapenc:arrayType="ns1:CIMProperty[]">  
            
<!-- ManualConfig is needed when specifying PE-CE link and not using NPC -->
<!-- Device Info -->
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">ManualConfig</name>
                    <value xsi:type="xsd:string">true</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE</name>
                    <value xsi:type="xsd:string">CRS</value>
                  </item>

                </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">LinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList" 
soapenc:arrayType="ns1:CIMProperty[]">
                 
<!-- PE Intf Info  -->                 
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Name</name>
                    <value xsi:type="xsd:string">Bundle-Ether123</value>
                  </item>

                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Encap</name>
                    <value xsi:type="xsd:string">DOT1Q</value>
                  </item>
                  
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Vlan_ID</name>
                    <value xsi:type="xsd:string">1600</value>
                  </item>
                   <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">Autopick_Vlan_ID</name>
                    <value xsi:type="xsd:string">false</value>
                  </item>                

<!-- interface Addresses for IPV4 -->
                 
                 <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Address</name>
                    <value xsi:type="xsd:string">12.20.19.47/24</value>
                  </item>                 
                 
<!-- interface Addresses for IPV6 -->

                   <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Address_IPV6</name>
                    <value xsi:type="xsd:string">2009::47/32</value>
                  </item> 
                  
    			  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">Auto_Assign_IP_Address</name>
                    <value xsi:type="xsd:string">false</value>
                  </item>
                  
<!-- IPV4 Routing Protocol -->        
                    <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">PE_CE_Routing_Protocol</name>
                      <value xsi:type="xsd:string">STATIC</value>
                  </item>
                  
<!-- IPV6 Routing Protocol -->
             <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">PE_CE_IPv6_Routing_Protocol</name>
                      <value xsi:type="xsd:string">NONE</value>
                  </item>                   

<!-- CERC Type -->                  
				  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">CERC_RTTYPE</name>
                    <value xsi:type="xsd:string">cerc3=IPv4,cerc5=IPv6</value>
                  </item>                

                  
<!-- Enable RD Format -->
				
				<!--item xsi:type="ns1:CIMProperty">
	                <name xsi:type="xsd:string">RD_FORMAT</name>
	                <value xsi:type="xsd:string">RD_AS</value>
                  </item-->

               </properties>
              </objectPath>

<!-- CERC's -->
       
              <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">CERCMembership</className>
                <properties xsi:type="ns1:CIMPropertyList"
                                        soapenc:arrayType="ns1:CIMProperty[]">
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">CERC</name>
                    <value xsi:type="xsd:string">cerc3</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">IsHub</name>
                    <value xsi:type="xsd:string">true</value>
                  </item>
                </properties>
              </objectPath>
             
              <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">CERCMembership</className>
                <properties xsi:type="ns1:CIMPropertyList"
                                           soapenc:arrayType="ns1:CIMProperty[]">
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">CERC</name>
                    <value xsi:type="xsd:string">cerc5</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">IsHub</name>
                    <value xsi:type="xsd:string">true</value>
                  </item>
                </properties>
              </objectPath>

<!-- LinkTemplate example using template definition and direct input of template data 
(buffer method). The template data
                               is entered in the DataBuffer objectDef section -->
<!-- Template start here-->     
     
	
<!-- Template Ends Here -->
            </objectPath>

			<objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">MplsVpnLink</className>
                <properties xsi:type="ns1:CIMPropertyList" 
                       soapenc:arrayType="ns1:CIMProperty[]">  
            
<!-- ManualConfig is needed when specifying PE-CE link and not using NPC -->
<!-- Device Info -->
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">ManualConfig</name>
                    <value xsi:type="xsd:string">true</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE</name>
                    <value xsi:type="xsd:string">CRS</value>
                  </item>

                </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">LinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList" 
soapenc:arrayType="ns1:CIMProperty[]">
                 
<!-- PE Intf Info  -->                 
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Name</name>
                    <value xsi:type="xsd:string">Bundle-Ether123</value>
                  </item>

                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Encap</name>
                    <value xsi:type="xsd:string">DOT1Q</value>
                  </item>
                  
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Vlan_ID</name>
                    <value xsi:type="xsd:string">1600</value>
                  </item>
                   <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">Autopick_Vlan_ID</name>
                    <value xsi:type="xsd:string">false</value>
                  </item>                

<!-- interface Addresses for IPV4 -->
                 
                 <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_Intf_Address</name>
                    <value xsi:type="xsd:string">12.20.19.47/24</value>
                  </item>                 
                 
<!-- interface Addresses for IPV6 -->

			  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">Auto_Assign_IP_Address</name>
                    <value xsi:type="xsd:string">false</value>
                  </item>
                  
<!-- IPV4 Routing Protocol -->        
                    <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">PE_CE_Routing_Protocol</name>
                      <value xsi:type="xsd:string">STATIC</value>
                  </item>

<!-- IPV6 Routing Protocol -->
<!-- <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_CE_IPV6_Routing_Protocol</name>
                    <value xsi:type="xsd:string">EIGRP</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_EIGRP_AS_ID</name>
                    <value xsi:type="xsd:string">2369</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">CE_EIGRP_AS_ID</name>
                    <value xsi:type=:xsd:string">1526</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name 
xsi:type="xsd:string">PE_CE_Bandwidth_Metric_For_Redistribution</name>
                    <value xsi:type="xsd:string">6311</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name 
xsi:type="xsd:string">PE_CE_Delay_Metric_For_Redistribution</name>
                    <value xsi:type="xsd:string">5312</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name 
xsi:type="xsd:string">PE_CE_Reliability_Metric_For_Redistribution</name>
                    <value xsi:type="xsd:string">169</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name 
xsi:type="xsd:string">PE_CE_Loading_Metric_For_Redistribution</name>
                    <value xsi:type="xsd:string">147</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_CE_MTU_Metric_For_Redistribution</name>
                    <value xsi:type="xsd:string">864</value>
                  </item>

<!-- CERC Type -->                  
				 

<!-- Enable Multipath Loadsharing -->
                  
<!-- Enable RD Format -->
				

               </properties>
              </objectPath>

<!-- CERC's -->
       
              <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">CERCMembership</className>
                <properties xsi:type="ns1:CIMPropertyList"
                                        soapenc:arrayType="ns1:CIMProperty[]">
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">CERC</name>
                    <value xsi:type="xsd:string">multi-cerc3</value>
                  </item>
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">IsHub</name>
                    <value xsi:type="xsd:string">true</value>
                  </item>
                </properties>
              </objectPath>

<!-- LinkTemplate example using template definition and direct input of template data 
(buffer method). The template data
                               is entered in the DataBuffer objectDef section -->
<!-- TEmplate start here-->     
     
	
<!-- Template Ends Here -->
            </objectPath>

          </objectPath>
        </objectPath>
      </action>      
    </actions>
  </ns1:performBatchOperation>  
</soapenv:Body>
</soapenv:Envelope>

Bundled/physical interface example

This example describes a service definition for a bundle interface configuration. A policy is created with the interface type Bundle-Ether interface.The only change in this policy is the attribute PE_Intf_Type (in bold below), which is given as Bundle-ether123 (Bundle-Ethernet interface).

File: CreateMPLSServiceDefn_Bundle_PE_CE_IPV4_IPV6.xml


<?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>
   <ns0:message id="87855" timestamp="2002-12-13T14:55:38.885Z" 
                sessiontoken="p36bttjwy1"/>
  </soapenv:Header>
  <soapenv:Body> 
    <ns1:createInstance>
      <objectPath xsi:type="ns1:CIMObjectPath"> 
        <className xsi:type="xsd:string">ServiceDefinition</className>
        <properties xsi:type="ns1:CIMPropertyList" 
                    soapenc:arrayType="ns1:CIMProperty[]">  
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Name</name>
            <value xsi:type="xsd:string">Bundle_PE_CE_IPV4_IPV6</value> 
          </item>
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Type</name>
            <value xsi:type="xsd:string">Mpls</value> 
          </item>
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Remarks</name>
            <value xsi:type="xsd:string">data remarks</value> 
          </item>
</properties>
        <objectPath xsi:type="ns1:CIMObjectPath"> 
          <className xsi:type="xsd:string">ServiceDefinitionDetails</className>  
          <properties xsi:type="ns1:CIMPropertyList" 
                   soapenc:arrayType="ns1:CIMProperty[]">  
            <item xsi:type="ns1:CIMProperty">
              <name xsi:type="xsd:string">SubType</name>
              <value xsi:type="xsd:string">PE_CE</value>
            </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_CE_IP_Unnumbered</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>

<!-- PE Intf Info -->             
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_Intf_Type</name>
                <value xsi:type="xsd:string">Bundle-Ether</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_Intf_Desc</name>
                <value xsi:type="xsd:string" />
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
               <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_Intf_Format</name>
                <value xsi:type="xsd:string" />
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
               <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_Intf_Shutdown</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              
 				<item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">Autopick_Vlan_ID</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              
              
<!-- CE Intf Info -->                       
			 <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">CE_Intf_Type</name>
                <value xsi:type="xsd:string">ANY</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
	          <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">CE_Intf_Desc</name>
                <value xsi:type="xsd:string" />
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			 <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">CE_Intf_Format</name>
                <value xsi:type="xsd:string" />
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>

<!-- IP Address -->              
				<item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">Auto_Assign_IP_Address</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>

<!-- Routing Protocols IPv4 & IPV6 -->
				 <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_CE_Routing_Protocol</name>
                <value xsi:type="xsd:string">BGP</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
				
				<item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PE_CE_IPV6_Routing_Protocol</name>
                <value xsi:type="xsd:string">BGP</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
				 
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">Template_Enabled</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>

      </properties>

<!-- CERC -->
       <objectPath xsi:type="ns1:CIMObjectPath">
       <className xsi:type="xsd:string">MplsPolicyCercMembership</className>
        <properties xsi:type="ns1:CIMPropertyList"
                   soapenc:arrayType="ns1:CIMProperty[]">
         <item xsi:type="ns1:CIMProperty">
           <name xsi:type="xsd:string">CERC</name>
           <value xsi:type="xsd:string">cerc1</value>
         </item>
         <item xsi:type="ns1:CIMProperty">
            <name xsi:type="xsd:string">IsHub</name>
            <value xsi:type="xsd:string">true</value>
         </item>
      </properties>
     </objectPath>

  <!-- Templates -->

     </objectPath>
     </objectPath>
    </ns1:createInstance>
  </soapenv:Body>
</soapenv:Envelope>

Static Route configuration example

In this example XML script, the static route configuration is modified. The attribute Static_Next_Hop_Option is given the new value OUTGOING_INTF_NAME_NEXT_HOP_IPADDR when the service request is created.

The preferred values for Static_Next_Hop_Option are OUT_GOING_INTF_NAME, NEXT_HOP_IPADDR, and OUTGOING_INTF_NAME_NEXT_HOP_IPADDR..

In the PE_CE case, no values have been specified for Next Hop Ip Address. For PE_NO_CE, the Next Hop Ip Address value should be specified when selecting NEXT_HOP_IPADDR or OUTGOING_INTF_NAME_NEXT_HOP_IPADDR for Static_Next_Hop_Option.

File: ModifyMplsServiceOrder_StaticRoute.xml


<?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="90" 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.885Z</value>
        </item>
        <!--item xsi:type="ns1:CIMProperty">  
         <name xsi:type="xsd:string">Organization</name>
         <value xsi:type="xsd:dateTime">NbiCustomer</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">modifyInstance</actionName>
      <objectPath subAction="modifyInstance" 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-1</value>
       </item>
        <item xsi:type="ns1:CIMProperty"> 
         <name xsi:type="xsd:string">Type</name>
         <value xsi:type="xsd:string">Mpls</value>
        </item>
       </properties>  
       <objectPath subAction="modifyInstance" xsi:type="ns1:CIMObjectPath">
           <className xsi:type="xsd:string">ServiceRequestDetails</className>
            <keyProperties xsi:type="ns1:CIMKeyPropertyList"
                      soapenc:arrayType="ns1:CIMKeyProperty[]">
                   <item xsi:type="ns1:CIMProperty">
                     <name xsi:type="xsd:string">LocatorId</name>
                     <value xsi:type="xsd:string">340</value>
                   </item>
              </keyProperties>
              
              <objectPath subAction="modifyInstance" xsi:type="ns1:CIMObjectPath">
               <className xsi:type="xsd:string">MplsVpnLink</className>
                <keyProperties xsi:type="ns1:CIMKeyPropertyList"
                      soapenc:arrayType="ns1:CIMKeyProperty[]">
                   <item xsi:type="ns1:CIMProperty">
                     <name xsi:type="xsd:string">LocatorId</name>
                     <value xsi:type="xsd:string">340</value>
                   </item>
                    
               </keyProperties>
              
                <objectPath subAction="createInstance" xsi:type="ns1:CIMObjectPath">
               <className xsi:type="xsd:string">LinkAttrs</className>
                 <keyProperties xsi:type="ns1:CIMKeyPropertyList"
                      soapenc:arrayType="ns1:CIMKeyProperty[]">
                       <item xsi:type="ns1:CIMProperty">
                     <name xsi:type="xsd:string">LocatorId</name>
                     <value xsi:type="xsd:string">340</value>
                   </item> 
               </keyProperties> 
                <properties xsi:type="ns1:CIMPropertyList" 
soapenc:arrayType="ns1:CIMProperty[]">
      <!--Start Modification  -->
      
                    
                  <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">PE_CE_Routing_Protocol</name>
                    <value xsi:type="xsd:string">STATIC</value>
                  </item> 
                  
                 <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">Static_Next_Hop_Option</name>
                    <value 
xsi:type="xsd:string">OUTGOING_INTF_NAME_NEXT_HOP_IPADDR</value>
                  </item>
                 	 <item xsi:type="ns1:CIMProperty">
                    <name xsi:type="xsd:string">STATIC_NEXT_HOP_IP_ADDR</name>
                    <value xsi:type="xsd:string">2.22.29.28</value>
                  </item>
                  
      
          </properties>
             
        </objectPath> 
            

              </objectPath>
          </objectPath>        
       </objectPath>          
      </action>
    </actions>
   </ns1:performBatchOperation>
  </soapenv:Body> 
</soapenv:Envelope>

Related APIs

CreateMPLSServiceDefn_PE_NO_CE_IPV4_IPV6_Unique_RT.xml


Note CreateMPLSServiceDefn_PE_NO_CE_IPV4_IPV6_Unique_RT.xml is omitted from the build as the same result is obtained by creating a PE_NO_CE policy.


CreateMPLSServiceOrder_PE_CE_IPV4_IPV6_Unique_RT.xml

CreateMPLSServiceOrder_PE_NO_CE_IPV4_IPV6_Unique_RT.xml

ModifyMPLSServiceOrder_Unique_RT.xml

CreateMPLSServiceDefn_Bundle_PE_CE_IPV4_IPV6.xml

CreateMPLSServiceDefn_Bundle_PE_NO_CE_IPV4_IPV6.xml

CreateMPLSServiceOrder_Bundle_PE_CE_IPV4_IPV6.xml

ModifyMPLSServiceOrder_Bundle_PE_CE.xml

CreateMplsServiceOrder_StaticRoute_PE_CE.xml

CreateMPLSServiceOrder_StaticRoute_PE_NO_CE.xml

Provisioning Example

An end-to-end provisioning example is provided in the MPLS Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2. This example still applies with the added MPLS support in this release.

L2VPN and Carrier Ethernet Provisioning

In this release, the following L2VPN/Carrier Ethernet support has been added:

For a ME3400 device, Spanning Tree CLI is not generated through ISC from ISC 5.2.1 onwards.

For a CAT 6500 device, Switchport Encapsulation DOT1Q CLI is not generated through ISC from ISC 5.2.1 onwards.

Support for XR 3.7.2 across all blades on the ASR9000 platforms.

For further details on these new features from a GUI perspective, see L2VPN and Carrier Ethernet New Features.

For more detailed information about L2VPN and Carrier Ethernet in ISC, see the Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 5.2.

This section includes the following sections:

Service Definitions

Service Requests

Provisioning Example.

Service Definitions

No new service definitions have been added in this release.

Supported service definitions are listed in the L2VPN Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2).

Service Requests

An L2VPN service request specifies a service definition, assigns device interfaces for the end-to-end wire connections, and specifies attachment circuit details.

For sample network diagrams and service request examples, see the L2VPN Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2.

Provisioning Example

An end-to-end provisioning example is provided in the L2VPN Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2.

FlexUNI/EVC Provisioning

The following FlexUNI/EVC enhancements have been added in this release:

Ability to configure an SVI/EVC Hybrid Scenario

Service Instance Name support for EVC/FlexUNI service requests.

For further details on these new features from a GUI perspective, see L2VPN and Carrier Ethernet New Features.

For more detailed information about FlexUNI/EVC in ISC, see the Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 5.2.

This section includes the following:

Service Definitions

Service Requests

Provisioning Example.

Service Definitions and Policy Examples

No new service definitions have been added in this release but support has been added for existing service definitions/policies.

Supported service definitions are listed in the FlexUNI/EVC Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2.

The following policy examples show how the new FlexUNI/EVC features are used:

Configuring an SVI/EVC Hybrid Scenario

Policy for specifying Service Instance Name for EVC/FlexUNI Service Requests.

Configuring an SVI/EVC Hybrid Scenario

In the following example, a FlexUNI/EVC service definition is created with the EVC/SVI Hybrid scenario. The attribute relevant for the EVC/SVI Hybrid scenario is XconnectOnSVI (in bold below), which in the example is set to true.

File: CreateEVCServiceDefn_PW_1.xml


<?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>
   <ns0:message id="87855" timestamp="2002-12-13T14:55:38.885Z" 
                sessiontoken="p36bttjwy1"/>
  </soapenv:Header>
  <soapenv:Body> 
    <ns1:createInstance>
      <objectPath xsi:type="ns1:CIMObjectPath"> 
        <className xsi:type="xsd:string">ServiceDefinition</className>
        <properties xsi:type="ns1:CIMPropertyList" 
                soapenc:arrayType="ns1:CIMProperty[]">  
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Name</name>
            <value xsi:type="xsd:string">doc_pw</value> 
          </item>
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Type</name>
            <value xsi:type="xsd:string">Evc</value> 
          </item>
         </properties>
          <objectPath xsi:type="ns1:CIMObjectPath"> 
            <className xsi:type="xsd:string">ServiceDefinitionDetails</className>  
            <properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">  
             <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">SubType</name>
                <value xsi:type="xsd:string">Evc</value>
              </item>
             <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">AccessType</name>
                  <value xsi:type="xsd:string">ETHERNET</value>
             </item>
               <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">TransportType</name>
                  <value xsi:type="xsd:string">PSEUDOWIRE</value>
             </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">StdUniPort</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">UniShutdown</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
        	  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">DirectConnect</name>
                <value xsi:type="xsd:string">false</value>
              </item>	
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutoPickEsiId</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutopickVCId</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutoPickBDVlanId</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">EnablePWRedundancy</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
		<!-- XConnect ON SVI-->
                   <item xsi:type="ns1:CIMProperty">
                      <name xsi:type="xsd:string">XconnectOnSVI</name>
                        <value xsi:type="xsd:string">true</value>
                           <qualifier xsi:type="ns1:CIMQualifier">
                  	      <name xsi:type="xsd:string">editable</name>
                             <value xsi:type="xsd:string">true</value>
                            </qualifier>
                        </item>  
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PwTunnelSelection</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutopickVCId</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
		 <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AllowBothTags</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PushOuter</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PushInner</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PopOuter</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PopInner</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">TranslateInner</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">TranslateOuter</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">UseEVC</name>
                <value xsi:type="xsd:string">false</value>
              </item>	
	       <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">UseBD</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
            <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">EncapsulationType</name>
                <value xsi:type="xsd:string">DOT1QTRUNK</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
            </properties>               
          </objectPath>
        </objectPath>
      </ns1:createInstance>
  </soapenv:Body>
</soapenv:Envelope>

Policy for specifying Service Instance Name for EVC/FlexUNI Service Requests

The following example shows how to make a policy that specifies a service instance name for FlexUNI/EVC service requests. The attribute used to specify a service instance name in FlexUNI/EVC service requests is AutoPickEsiName (in bold below), which in the example is set to true.

File: CreateEVCServiceDefn_PW_2.xml


<?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>
   <ns0:message id="87855" timestamp="2002-12-13T14:55:38.885Z" 
                sessiontoken="p36bttjwy1"/>
  </soapenv:Header>
  <soapenv:Body> 
    <ns1:createInstance>
      <objectPath xsi:type="ns1:CIMObjectPath"> 
        <className xsi:type="xsd:string">ServiceDefinition</className>
        <properties xsi:type="ns1:CIMPropertyList" 
                soapenc:arrayType="ns1:CIMProperty[]">  
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Name</name>
            <value xsi:type="xsd:string">doc_pw</value> 
          </item>
          <item xsi:type="ns1:CIMProperty">  
            <name xsi:type="xsd:string">Type</name>
            <value xsi:type="xsd:string">Evc</value> 
          </item>
         </properties>
          <objectPath xsi:type="ns1:CIMObjectPath"> 
            <className xsi:type="xsd:string">ServiceDefinitionDetails</className>  
            <properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">  
             <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">SubType</name>
                <value xsi:type="xsd:string">Evc</value>
              </item>
             <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">AccessType</name>
                  <value xsi:type="xsd:string">ETHERNET</value>
             </item>
               <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">TransportType</name>
                  <value xsi:type="xsd:string">PSEUDOWIRE</value>
             </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">StdUniPort</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">UniShutdown</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
        	  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">DirectConnect</name>
                <value xsi:type="xsd:string">false</value>
              </item>	
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutoPickEsiId</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutopickVCId</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutoPickBDVlanId</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">EnablePWRedundancy</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
	      <item xsi:type="ns1:CIMProperty">
              	 <name xsi:type="xsd:string">AutoPickEsiName</name>
              	 <value xsi:type="xsd:string">true</value>
              	 <qualifier xsi:type="ns1:CIMQualifier">
              		<name xsi:type="xsd:string">editable</name>
              		<value xsi:type="xsd:string">true</value>
              	 </qualifier>
              </item >
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PwTunnelSelection</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AutopickVCId</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
		 <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">AllowBothTags</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PushOuter</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PushInner</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PopOuter</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">PopInner</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">TranslateInner</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
			  <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">TranslateOuter</name>
                <value xsi:type="xsd:string">false</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
              <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">UseEVC</name>
                <value xsi:type="xsd:string">false</value>
              </item>	
	       <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">UseBD</name>
                <value xsi:type="xsd:string">true</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>	
            <item xsi:type="ns1:CIMProperty">
                <name xsi:type="xsd:string">EncapsulationType</name>
                <value xsi:type="xsd:string">DOT1QTRUNK</value>
                <qualifier xsi:type="ns1:CIMQualifier">
                  <name xsi:type="xsd:string">editable</name>
                  <value xsi:type="xsd:string">true</value>
                </qualifier>
              </item>
            </properties>
          </objectPath>
        </objectPath>
      </ns1:createInstance>
  </soapenv:Body>
</soapenv:Envelope>

Service Requests

A FlexUNI/EVC service request specifies the service definition, assigns device interfaces for the end-to-end wire connections, and the attachment circuit details.

For sample network diagrams and service request examples, see the FlexUNI/EVC Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2.

The following examples represent service requests that are created for the new features:

Configuring an SVI/EVC Hybrid Scenario Service Request

Specifying Service Instance Name for FlexUNI/EVC Service Requests.

Configuring an SVI/EVC Hybrid Scenario Service Request

The following is an example of how to configure a hybrid EVC/SVI scenario in a FlexUNI/EVC service request.

If XConnectOnSVI is enabled, the forwarding commands will be configured under SVI for both flex and non-flex. If it is disabled, the forwarding commands will be configured under service instance if it is a FlexUNI link. If the link is a non-flex link, these commands will be configured under a subinterface.

The attribute relevant for the EVC/SVI Hybrid scenario is XconnectOnSVI (in bold below), which in the example is set to true

File: CreateEVCServiceOrder_PW_1.xml


<?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="90" 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">2008-12-13T14:55:38.885Z</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">EvcSR-7</value>
              </item>
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">Type</name>
                <value xsi:type="xsd:string">Evc</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">L2_NBI_1</value>
                  <qualifier xsi:type="xsd:string">
                    <name xsi:type="xsd:string">ServiceDefinitionType</name>
                    <value xsi:type="xsd:string">Evc</value>
                  </qualifier>
                </item>
               <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">VPN</name>
                  <value xsi:type="xsd:string">vpn</value>
                </item>
                <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">AutopickVCID</name>
                  <value xsi:type="xsd:string">true</value>
                </item>			
                <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">UseBackupVCID</name>
                  <value xsi:type="xsd:string">true</value>
                </item>
                <item xsi:type="ns1:CIMProperty">  
                  <name xsi:type="xsd:string">UseSVI</name>
                  <value xsi:type="xsd:string">true</value>
                </item>
	        <item xsi:type="ns1:CIMProperty">  
                  <name xsi:type="xsd:string">Description</name>
                  <value xsi:type="xsd:string">BD=T,SVI = F Flex and SVI=T,Non-Flex 
created thru NBI</value>
                </item>
               </properties>
            <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">EvcLink</className>
				<properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">Npe</name>
                        <value xsi:type="xsd:string">iscind-7609-2</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">UniInftId</name>
                        <value xsi:type="xsd:string">GigabitEthernet7/0/8</value>
                      </item>
			    </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">EvcETHLinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">  
                    <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">UseServiceInst</name>
                      <value xsi:type="xsd:string">true</value>
                    </item>
                     <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">SystemMTU</name>
                      <value xsi:type="xsd:string">1563</value>
                    </item> 
                    <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickVlanId</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
		    <item xsi:type="ns1:CIMProperty">
                            <name xsi:type="xsd:string">XconnectOnSVI</name>
                            <value xsi:type="xsd:string">true</value>
		    </item>
                     </properties>
			    </objectPath>
			    <objectPath xsi:type="ns1:CIMObjectPath">
                    <className xsi:type="xsd:string">EvcServiceInstanceAttrs</className>
                    <properties xsi:type="ns1:CIMPropertyList"
                                    soapenc:arrayType="ns1:CIMProperty[]">
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">OuterVlanRange</name>
                        <value xsi:type="xsd:string">2611</value>
                      </item>  
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickServiceInstId</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>   
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">BothTags</name>
                        <value xsi:type="xsd:string">false</value>
                      </item>               
                      </properties>                  
                  </objectPath>
		  </objectPath>  
	      		  
	      		  <!-- L2Access Links -->
	      		  
	      		  <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">EvcLink</className>
				<properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">Upe</name>
                        <value xsi:type="xsd:string">iscind-3750-2</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">UniInftId</name>
                        <value xsi:type="xsd:string">FastEthernet1/0/4</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">NPC</name>
                        <value xsi:type="xsd:string">4</value>
                      </item>
			    </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">EvcETHLinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">  
                    <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">UseServiceInst</name>
                      <value xsi:type="xsd:string">false</value>
                    </item>
                    <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">SystemMTU</name>
                      <value xsi:type="xsd:string">1563</value>
                    </item>
                    <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickVlanId</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
					 <item xsi:type="ns1:CIMProperty">
                            <name xsi:type="xsd:string">XconnectOnSVI</name>
                            <value xsi:type="xsd:string">true</value>
					  </item> 
                  </properties>
			    </objectPath>
			    <objectPath xsi:type="ns1:CIMObjectPath">
                    <className xsi:type="xsd:string">EvcUNIProtocolTunnelAttrs</className>
                    <properties xsi:type="ns1:CIMPropertyList"
                                    soapenc:arrayType="ns1:CIMProperty[]">
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">ProtocolTunnelling</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">VtpDropThreshold</name>
                        <value xsi:type="xsd:string">10</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">CdpDropThreshold</name>
                        <value xsi:type="xsd:string">20</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">StpDropThreshold</name>
                        <value xsi:type="xsd:string">27</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">StpThreshold</name>
                        <value xsi:type="xsd:string">27</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">VtpThreshold</name>
                        <value xsi:type="xsd:string">2007</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">CdpThreshold</name>
                        <value xsi:type="xsd:string">2007</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">CdpEnable</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">VtpEnable</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                         <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">StpEnable</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                    </properties>                
                  </objectPath>  
                  <objectPath xsi:type="ns1:CIMObjectPath">
                    <className xsi:type="xsd:string">EvcUNIInterfaceAttrs</className>
                    <properties xsi:type="ns1:CIMPropertyList"
                                    soapenc:arrayType="ns1:CIMProperty[]">
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">PortSecurity</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">SpeedType</name>
                        <value xsi:type="xsd:string">100</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">DuplexType</name>
                        <value xsi:type="xsd:string">Half</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">Shutdown</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">MacAddress</name>
                        <value xsi:type="xsd:string">5</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">Aging</name>
                        <value xsi:type="xsd:string">201</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">ViolationActionType</name>
                        <value xsi:type="xsd:string">RESTRICT</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">BroadcastTraffic</name>
                        <value xsi:type="xsd:string">25</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">MulticastTraffic</name>
                        <value xsi:type="xsd:string">25</value>
                      </item>
                       <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">UnicastTraffic</name>
                        <value xsi:type="xsd:string">25</value>
                      </item>
                      </properties>                
                  </objectPath>
	      	  </objectPath>  
	      	</objectPath>
          </objectPath>
        </action>
      </actions>
    </ns1:performBatchOperation>
  </soapenv:Body> 
</soapenv:Envelope>

Specifying Service Instance Name for FlexUNI/EVC Service Requests

The following is an example of how to specify a service instance name for FlexUNI/EVC service requests. The attributes relevant for the Service Instance Name are ServiceInstName and AutoPickServiceInstName (both in bold below), which in the example are set to manualNameNBI4 and false respectively.

File: CreateEVCServiceOrder_PW_2.xml


<?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="90" 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">2008-12-13T14:55:38.885Z</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">EvcSR-7</value>
              </item>
              <item xsi:type="ns1:CIMProperty">  
                <name xsi:type="xsd:string">Type</name>
                <value xsi:type="xsd:string">Evc</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">GUI_PW</value>
                  <qualifier xsi:type="xsd:string">
                    <name xsi:type="xsd:string">ServiceDefinitionType</name>
                    <value xsi:type="xsd:string">Evc</value>
                  </qualifier>
                </item>
               <item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">VPN</name>
                  <value xsi:type="xsd:string">vpn-core-PW</value>
                </item>
                <!-- item xsi:type="ns1:CIMProperty">
                  <name xsi:type="xsd:string">AutopickVCID</name>
                  <value xsi:type="xsd:string">true</value>
                </item -->
                <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">UseSVI</name>
                      <value xsi:type="xsd:string">true</value>
                </item>
               </properties>
			   
            <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">EvcLink</className>
				<properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">
                        <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">Npe</name>
                        <value xsi:type="xsd:string">iscind-7609-2</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">UniInftId</name>
                        <value xsi:type="xsd:string">GigabitEthernet7/0/12</value>
                      </item>
			    </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">EvcETHLinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">  

                    <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">UseServiceInst</name>
                      <value xsi:type="xsd:string">true</value>
                    </item>
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickVlanId</name>
                        <value xsi:type="xsd:string">false</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">VlanID</name>
                        <value xsi:type="xsd:string">100</value>
                      </item>
                   </properties>
			    </objectPath>
			    <objectPath xsi:type="ns1:CIMObjectPath">
                    <className xsi:type="xsd:string">EvcServiceInstanceAttrs</className>
                    <properties xsi:type="ns1:CIMPropertyList"
                                    soapenc:arrayType="ns1:CIMProperty[]">
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">ServiceInstName</name>
                        <value xsi:type="xsd:string">manualNameNBI4</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickServiceInstName</name>
                        <value xsi:type="xsd:string">false</value>
                      </item> 
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickServiceInstId</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                      
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">OuterVlanRange</name>
                        <value xsi:type="xsd:string">256</value>
                      </item>

                     </properties>                  
                  </objectPath>
                    </objectPath>
              

   
            <objectPath xsi:type="ns1:CIMObjectPath">
                <className xsi:type="xsd:string">EvcLink</className>
				<properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">
                        <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">Npe</name>
                        <value xsi:type="xsd:string">iscind-7609-2</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">UniInftId</name>
                        <value xsi:type="xsd:string">GigabitEthernet7/0/13</value>
                      </item>
			    </properties>
                <objectPath xsi:type="ns1:CIMObjectPath">
                  <className xsi:type="xsd:string">EvcETHLinkAttrs</className>
                  <properties xsi:type="ns1:CIMPropertyList" 
                        soapenc:arrayType="ns1:CIMProperty[]">  

                    <item xsi:type="ns1:CIMProperty">  
                      <name xsi:type="xsd:string">UseServiceInst</name>
                      <value xsi:type="xsd:string">true</value>
                    </item>
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickVlanId</name>
                        <value xsi:type="xsd:string">false</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">VlanID</name>
                        <value xsi:type="xsd:string">100</value>
                      </item>
                   </properties>
			    </objectPath>
			    <objectPath xsi:type="ns1:CIMObjectPath">
                    <className xsi:type="xsd:string">EvcServiceInstanceAttrs</className>
                    <properties xsi:type="ns1:CIMPropertyList"
                                    soapenc:arrayType="ns1:CIMProperty[]">
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">ServiceInstName</name>
                        <value xsi:type="xsd:string">manualNameNBI4</value>
                      </item>
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickServiceInstName</name>
                        <value xsi:type="xsd:string">false</value>
                      </item> 
                      <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">AutoPickServiceInstId</name>
                        <value xsi:type="xsd:string">true</value>
                      </item>
                      
                     <item xsi:type="ns1:CIMProperty">
                        <name xsi:type="xsd:string">OuterVlanRange</name>
                        <value xsi:type="xsd:string">256</value>
                      </item>

                     </properties>                  
                  </objectPath>
                    </objectPath>
             			  
            </objectPath>
          </objectPath>
        </action>
      </actions>
    </ns1:performBatchOperation>
  </soapenv:Body> 
</soapenv:Envelope>

Provisioning Example

An end-to-end provisioning example is provided in the FlexUNI/EVC Provisioning chapter in the Cisco IP Solution Center API Programmer Guide, 5.2.

Traffic Engineering Management Provisioning

There are no API XML changes for Traffic Engineering Management (TEM) in this release.

However, there are behavioral API changes and the graphical user interface (GUI) changes are also supported through APIs. Note especially the issues highlighted below.

For further details on these new features from a GUI perspective, see Traffic Engineering Management (TEM) New Features.

For more detailed information about ISC TEM, see the Cisco IP Solution Center Traffic Engineering Management User Guide, 5.2.

Behavioral Change Relating to TEM Link Deletion

When performing link deletion using the API, all link-associated objects, which ISC can delete, are automatically removed.

If a tunnel with path option traverses the link, the link deletion will fail and you will be prompted to reroute or delete those tunnels.

Change for Explicit Path XMLs

Note that when using XMLs for creating explicit paths, the field Provisioning-Pref is mandatory.

Problems Fixed in ISC 5.2.1

Customer-found problems that have been fixed in this release are indicated in Table 7. 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 7 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 diagnostic expert produces incorrect re - MDE 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

ISC 5.2.1 is a maintenance release that supports upgrading only from ISC 5.2 and ISC 5.1.1.9.

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.1 Patch Installation

Upgrade Repository to ISC 5.2.1

Note Regarding Location of ISC 5.1 and 5.2 Upgrade Tools

Common Installation Steps

If you have an ISC 5.1.1.9 repository, use the same upgrade procedure as for the Sybase repository (see the section Restoring Your Sybase Repository to a New Server in the Cisco IP Solution Center Installation Guide, 5.2).

If you have an ISC 5.2 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.1:


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.1.1.9 to ISC 5.2.1.



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


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.1 patch using the steps outlined in ISC 5.2.1 Patch Installation.

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


ISC 5.2.1 Patch Installation

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


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



Step 1 Before upgrading to this ISC 5.2.1 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.1 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.1 Maintenance Release (isc-5.2.1-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.1 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.1-patch.tar.gz file:

gunzip -c isc-5.2.1-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.1].

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

This procedure uses the example of upgrading an ISC 5.2 repository to ISC 5.2.1. When upgrading your repository from ISC 5.1 or 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 ISC521_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/ISC521_UpgradeTool.tar.gz /opt/isc-5.2.1

Step 2 Untar the upgrade tool tar file.

gzip -d < ISC521_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 ISC521_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.1, 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.1 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.1 repository.



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

Step 2 If ISC 5.2.1 is running, navigate to the directory $ISC_HOME/patch/isc5.2.1-patch, where all the files replaced by the ISC 5.2.1 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. Both Oracle and Sybase must be installed on a Solaris machine.

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

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