Cisco Prime Network

Table Of Contents

Cisco Prime Network 3.9 Release Notes

Introduction

New Features and Significant Changes in Prime Network 3.9

Prime Network Administration

Prime Network Vision

Change and Configuration Management

Prime Network Events and Fault Management

Report Manager

Mobile Technology Support in Prime Network 3.9

VNE Customization Builder

External Launch

Activation Changes

New Device Support Information

Open Bugs in Prime Network 3.9

Installation/Upgrade/High Availability Bugs

Device and Software Version Specific Bugs

Network Discovery Bugs

Technology-Related Bugs

Command Builder Bugs

Change and Configuration Management (CCM) Bugs

Fault Management Bugs

Path Trace Bugs

VNE Bugs

AVM/Unit Bugs

Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.9

Resolved Bugs

Closed Bugs

Related Documentation

Obtaining Documentation and Submitting a Service Request

Cisco Prime Network 3.9 Release Notes

---

This document contains the following sections:

•Introduction

•New Features and Significant Changes in Prime Network 3.9

•New Device Support Information

•Activation Changes

•Open Bugs in Prime Network 3.9

•Resolved Bugs

•Closed Bugs

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

Cisco Prime Network 3.9 provides service providers and other network operators with a comprehensive assurance and device management solution for IP next-generation networks (NGNs). It is offered as a standalone application and as a fully integrated component of the Cisco Prime IP NGN suite for customers needing end-to-end network management lifecycle capabilities.

Cisco Prime Network users can easily discover network elements (NEs), administer them, diagnose problems, and restore changed configurations. These monitoring, validating, troubleshooting, and administration tasks can be accomplished using the Prime Network GUI client applications.

This document provides information on the new and enhanced features introduced in Cisco Prime Network 3.9. It also lists the open and resolved bugs in this release.

All enhancements and new features are described in New Features and Significant Changes in Prime Network 3.9.

New Features and Significant Changes in Prime Network 3.9

The following topics describe the new features and enhancements in Prime Network 3.9:

•Prime Network Administration

•Prime Network Vision

•Change and Configuration Management

•Prime Network Events and Fault Management

•Report Manager

•Mobile Technology Support in Prime Network 3.9

•VNE Customization Builder

•External Launch

•Activation Changes

Prime Network Administration

These new Administration features are described in the Cisco Prime Network 3.9 Administrator Guide.

Event Notification Service

•For tickets or events included in an ENS, there are now options for choosing the type and severity.

•For the event source, there is an option to include or exclude events from the source.

Archiving and Purging

•Job purging can be configured so that jobs which do not comply to the configured policy are automatically purged. The administrator must configure this policy.

•Tickets older than a specified time and severity are automatically cleared by the system. This feature is disabled by default and can be enabled by selecting Event Management Settings >Auto-Clear Tickets.

Embedded Database

•The database backup time can be changed and rescheduled using emdbctl --change_backup_time.

VNE-Specific Features

•When a VNE is updated to a new driver, it is no longer necessary to restart Prime Network to apply the changes. Only the VNE has to be restarted.

•Newly-created VNEs will automatically use the driver from the latest installed DP (the newest DP that is installed on the gateway or unit).

Prime Network Vision

These new Vision features are described in the Cisco Prime Network 3.9 User Guide.

•The Tickets pane contains a Latest Events tab. It lists all network events generated by elements in the map, from the time the map was opened. Events are removed from the Latest Events tab after 6 hours or when a maximum of 15000 events is reached (oldest events are removed first).

•A new Scheduled Jobs GUI (Tools >Scheduled Jobs) allows Administrators to monitor scheduled reports and Command Builder jobs, and to reschedule a job if necessary.

Change and Configuration Management

These new Change and Configuration Management features are described in the Cisco Prime Network 3.9 User Guide.

•Support for Cisco ASR 5500 devices.

•Change and Configuration Management supports TFTP, SCP, and FTP for image baseline operation on the Application Control Engine (ACE) cards on Cisco 7600 series routers. (The image should be available in the Cisco 7600 supervisor module filesystem for the import operation.)

•Archived configurations can be exported to a server on a periodic basis.

•Backup jobs can be scheduled simultaneously for all devices in a device group. If devices are added to or deleted from the device group after job creation, Prime Network updates the job accordingly such that all the devices available in the group at the time of execution of the job are considered for backup.

•Images can be imported from all devices in a group. If devices are added to or deleted from the device group after job creation, Prime Network updates the import job accordingly such that all the devices available in the group at the time of execution of the job are considered.

•Change and Configuration Management supports import and export servers with IPv4 or IPv6 addresses.

Prime Network Events and Fault Management

These new Events and fault management features are described in the Cisco Prime Network 3.9 User Guide.

•A new Find mode is available for Prime Network Events GUI client. In this mode, events are only retrieved from the database when a user searches for those events. No other events are retrieved from the database. In this way, users can get the specific event information they need without having to wait for all the events to be retrieved from the database.

•By default, the Prime Network Events window now displays events from the past two hours instead of the past two days. This reduces the time it takes to display data in the window. Users can still search for specific events that are not currently displayed in the window.

•Ticket notes can be added, updated, or viewed.

•User audit information includes information on which ticket-related actions were carried out by specific users, and when the actions took place. External usernames (for example, Netcool) are displayed along with the Prime Network username.

•Tickets can be filtered by username of the person who acknowledged or cleared the ticket.

Report Manager

These new report features are described in the Cisco Prime Network 3.9 User Guide.

•New hardware reports in the Inventory Reports category:

–Hardware Summary Detailed—Provides detailed hardware information for each device.

–Hardware Summary (By Property)—Provides hardware information for each device based on a selected entity.

–Modules Summary (By Type)—Provides module information for each device filtered by module type.

•Reports can be scheduled to run immediately or at a later point in time (using the Scheduling tab in the Run Report dialog box). The reports can also be monitored using this same feature.

Mobile Technology Support in Prime Network 3.9

Prime Network 3.9 provides the following mobile technology support for Cisco Aggregation Service Router (ASR) 5000 series mobile gateways:

•Gateway General Packet Radio Service (GPRS) Support Node (GGSN)

•Access Point Name (APN)

•GPRS Tunneling Protocol (GTP) User Plane (GTPU)

GGSNs, APNs, and GTPUs are configured using command-line interface (CLI). They are grouped under the respective containers in the logical inventory. You can use Prime Network Vision to view the properties and characteristics of GGSNs, APNs, and GTPUs configured on the system.

VNE Customization Builder

These new VNE Customization Builder (VCB) features are described in the Cisco Prime Network 3.9 Customization Guide.

•System events are now generated for Add and Override operations performed using the VCB tool, and these events can be viewed in Prime Network Events.

•The SysOID of unsupported devices or modules now appears in the description of the Unsupported Device/module event. This makes it easier for users to retrieve the SysOID of the unsupported device (in order to add support for it using the VCB).

•Export of customizations is now supported in the VCB GUI. (Previously, export could only be done using the CLI.)

External Launch

These new external launch enhancements are described in the Cisco Prime Network 3.9 Customization Guide.

•NE IMO properties can be filtered, and external launch points can be applied to the properties that match the filter criteria.

•Ability to create an external launch point on a property of a contained IMO.

Activation Changes

Pre-defined activations are no longer shipped with Prime Network and no longer appear in the Activation window. If you require reference configuration examples, please contact Cisco Advanced Services. The Cisco Prime Network Activation 3.8 User Guide and Cisco Prime Network Activation 3.8 Customization Guide have been discontinued and relevant content has been moved into the Cisco Prime Network 3.9 Customization Guide.

New Device Support Information

---

Note Prime Network 3.8.x with Device Package 5.0 or later: After upgrading to Prime Network 3.9, you must install the latest Device Package (DP) from Cisco.com in order to have the same level of device support that you had in your earlier installation. This is because Prime Network 3.9 includes all of the support that is provided up to Prime Network 3.8.x with DP 4.0.

---

Prime Network 3.9 incorporates all the device support additions that were provided in Prime Network 3.8.x DP 4.0. To get the latest VNE support, please download and install the latest Prime Network 3.8.x DP from the Prime Network download site on Cisco.com.

For detailed information about new device support in Prime Network 3.9, please see Cisco Prime Network 3.9 Reference Guide.

Open Bugs in Prime Network 3.9

The following sections identify bugs that are open in Prime Network 3.9, according to the following criteria:

•All catastrophic and severe bugs (if any).

•Customer-found bugs.

•Moderate, minor, and enhancement bugs that are considered likely to affect the customer's experience with Prime Network.

•Bugs that were fixed in previous releases of Prime Network but are still open in the current release because they were identified too late in the Prime Network 3.9 development cycle.

The open bugs have been grouped in the following categories:

•Installation/Upgrade/High Availability Bugs

•Device and Software Version Specific Bugs

•Network Discovery Bugs

•Technology-Related Bugs

•Command Builder Bugs

•Change and Configuration Management (CCM) Bugs

•Fault Management Bugs

•Path Trace Bugs

•VNE Bugs

•AVM/Unit Bugs

•Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.9

Installation/Upgrade/High Availability Bugs

Table 1 Installation/Upgrade/High Availability Bugs 

Bug ID	Description
CSCtz92844	Prime Network 3.9 installation with VMware_fence device fails
CSCua04712	Unit Installation fails when GW password is Admin123&
CSCua06195	When installing using GUI Unit is wrongly added as 0.0.0.1 in Prime Network GW
CSCua01831	ivne installer fails at the end of ANA 3.7.3 to Prime Network 3.9 upgrade
CSCua06423	An administrator user cannot manage map access of non-admin users/role Groups in Prime Central
CSCtz71592	Migration: Error while upgrading from 3.8.1 to 3.9 with a unit behind NAT
CSCua18258	Switchover fails in a DR setup
CSCua31425	After upgrading to 3.9, downloading the client exe file fails and an HTTP 404 message is received.
CSCtz78017	Upgrade backup fails.
CSCua39097	Unable to choose ipv6 address as the main ip interface when installing Prime Network on a full duplex unit.
CSCub43548	After uninstalling a GEO-HA environment, it was found that the Prime Network processes are still running in memory.

Device and Software Version Specific Bugs

Table 2 Device and Software Version Specific Bugs 

Bug ID	Description
CSCtg54230	For 7200 device, ATM IMA cards do not populate Loopback, Framing, or Scrambling values
CSCts79008	Memory usage information is missing in Nexus 5000 device
CSCtq36525	Wrong PID shown for transceiver/SFP modules for Nexus 7000 device
CSCtu24056	CPU usage attribute is not populated in the GUI for SCE2000
CSCtw65605	VEM module status shown as Unknown for Nexus1000V
CSCtw77988	ASR 9000 device: Missing bundle interface under Ethernet link aggregation in logical inventory
CSCty74187	ASR 5500 device, fan tray down service alarm is not cleared.
CSCty79971	ASR 5000 and ASR5500: When Virtual APN is deleted, it is still shown under main APN where it was referenced earlier

Network Discovery Bugs

Table 3 Network Discovery Bugs 

Bug ID	Description
CSCtw96705	Top navigation tool bar disappears
CSCtz80758	Unable to add vne with comma (",") in the telnet sequence

Technology-Related Bugs

Table 4 Technology-Related Bugs 

Bug ID	Description
CSCtr69267	Missing Bridge Domain awareness
CSCtx67922	Inconsistent behavior of the appearance of NetworkTPTunnels under EVC
CSCtr35459	Cannot create Command Builder on subinterface 03.7(03.01)PP00,03.7(02.01)PP01
CSCtx29563	IPSec tunnels do not have tunnel status
CSCty85223	Problem with parsing PLMNNetID object in XMLParser
CSCtz23017	IPSec tunnel does not show IP address when using unnumbered option
CSCtu27429	MPLS topology test is based on ip instead of LDP neighbors
CSCtz80712	No alarm on a static link when its end is down
CSCtx03184	Path tracer- L2 properties are not seen completely
CSCtx10166	Verification algorithm incorrect
CSCtx58626	STP model creates fake physical link between two routers
CSCtn63353	BFD and BGP events are not correlated to Bundle Interface Up/Down tickets
CSCts59855	Ethernet flow points inside a network VLAN are incorrectly calculated as VLAN edges even though they are connected to each other
CSCts39840	BGP Neighbor Loss syslog is not correlated to Device Unreachable ticket
CSCtr83226	Terminating Ethernet flow points under a switching entity that are not connected to another Ethernet flow point in the same NetworkVlan are not recognized as edges
CSCtr77298	Duplicate switching entities are created after deleting and then recreating a VLAN
CSCtk65010	Wrong serial connection through CDP in MLPPP technology
CSCtj30236	LAG link is not rediscovered after clearing and removing the ticket
CSCtr69267	Extra EVCs are created for network VLANs whose bridge domain (that contains a terminating Ethernet flow point) is not recognized
CSCtz86380	Port down alarm not cleared even though network event is resolved.
CSCtz80426	MPLS TP End Points are not attached to Pseudowire Edges in service view
CSCtz70997	MplsTETunnel linkdown on the mid point or tail does not correlate to the headend if the headend is an ASR 9000 device
CSCty09510	In Network Vision, "Channelization" configuration changes are not reflected.
CSCtw80566	Encapsulation value doesn't get modified even after stop and start VNE
CSCua00802	Missing STP link
CSCtu15772	Some VPNs are not deleted after deleting relevant VNEs
CSCua05419	Error in GUI reported "A data synchronization problem has been detected"

Command Builder Bugs

Table 5 Command Builder Bugs 

Bug ID	Description
CSCtx39154	Adding a command builder script to Logical Inventory sub-menus remains in running state

Change and Configuration Management (CCM) Bugs

Table 6 CCM Bugs 

Bug ID	Description
CSCty44789	Prime Network Change and Configuration Management allows the download of only two versions of ASR9K 4.2 images out of the four versions available on Cisco.com
CSCto02471	Gateway CPU consumption reaches 100% during Config backup of 10,000 VNEs
CSCua08248	Prime Network Change and Configuration Management uses the southboud IP of the unit server for file transfer between gatewayand unit

Fault Management Bugs

Table 7 Fault Management Bugs 

Bug ID	Description
CSCth36256	Cisco Prime Network generates two separate link down events when a port is disconnected and connected a few times
CSCtg96406	Tickets that contain alarm severities of both Cleared and Information have a severity of Cleared instead of Information
CSCsz61942	If you right-click a link in the VPN map view and choose Filter Ticket, no results are displayed
CSCtz63105	Invalid 'Link down due to oper down' ticket

Path Trace Bugs

Table 8 Path Trace Bugs 

Bug ID	Description
CSCtz57700	Path tracer does not show full path from source to destination (on CPT VNEs)
CSCtu15976	Pathtrace that should pass from a VLAN interface to a bridge stops at the VLAN interface
CSCtz68217	ARP Flood messages are filling the DA message queue

VNE Bugs

Table 9 VNE Bugs 

Bug ID	Description
CSCto31096	High CPU utilization on ASR 9000 device
CSCtr98822	ASR 5000 device: InterfaceTable-Input access list,Output access list+desc are blank
CSCth01054	Cisco 3750g fiber optic ports are modeled as RJ45 ports
CSCtj92252	For ISR 1800 device, VNE restarts due to software version change
CSCtr95939	For CRS device, CSC PathTrace fails
CSCty19414	TE-Tunnel down of IOS-XR devices do not correlate to Link-Down
CSCtz99804	ASR5000 and ASR5500: VRF interface under sites does not get updated on poll now
CSCua10049	ASR 5500: VRF interface is not reflected in Prime Network
CSCua05168	For 7600 device, VNEs are being moved to unsynchronized state
CSCua19364	ASR1K: POS channels and POS interfaces on CHOC12 card are not modeled
CSCtz62728	cevGsrSIP601 card showing incorrect status in Network Vision physical inventory
CSCua33524	UCS-Nexus adjacencies are not showing in Prime Network

AVM/Unit Bugs

Table 10 AVM/Unit Bugs 

Bug ID	Description
CSCth22846	Proxy for AVM 25 does not work in high availability (HA) scenarios
CSCua08070	Spelling/grammar errors in webcontrol script
CSCua24951	AVM becomes unreachable in a large CE setup

Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.9

The bugs listed in Table 11 were identified too late in the Prime Network 3.9 development cycle to be fixed for this release. The fixes for these bugs have been provided to customers running older versions of the product as needed and are scheduled for inclusion in the next release.

T

Table 11 Bugs Resolved in Earlier Releases but Still Open in Prime Network 3.9 

Bug ID	Description
CSCto42504	In OSPF Neighbor for cases like Bundle-Ether Interface name - OSPF Neighbor down alarms do not correlate to Link down on IOX
CSCtr35459	Cannot create a command with Command Builder on selection of a row in Sub Interface table (Physical interface inventory)
CSCty26361	The ~/main/drivers directory on the Unit machine(s) is not updated following the installation of a new DP update.
CSCty38964	While managing GSR-IOX lab device it was noticed that VNE logs Java exception NotSerializableException
CSCtx27289	Unit doesn't copy jars after upgrade from the gateway
CSCtx28435	Internal process-to-process messages are dropped by Prime Network
CSCtx53085	Drop message events are seen in event vision, under the system tab
CSCtx68087	Client shows an exception pop-up while browsing the inventory
CSCtx28928	checkPatchInstallation.pl returns inaccurate error when unit is down.
CSCtx95573	When a trap contains varbind with value of hexadecimal (array of bytes) string the the value is not displayed correctly in the GUI.
CSCtx18641	-1 appears in Link down tickets location in addition to the source
CSCtx57553	Terms used in network-conf script (such as GW and Unit) do not match the documentation
CSCtr94015	Need to support a new Product type as "Packet Microwave" for the DragonWave devices
CSCtu18795	Soft property is not shown as a hyperlink

Resolved Bugs

Table 12 identifies bugs that were listed as open bugs in the Prime Network 3.8.1 release notes and have since been resolved.

Table 12 Resolved Bugs in Cisco Prime Network 3.9 

Bug ID	Description
CSCtj19233	Cisco RSP 720 removal redundancy state ticket is issued only after reinsertion.
CSCtw82586	Recommended Solaris patch update
CSCtq83852	User ana_xmp is removed and installation fails after second network-conf
CSCtr11676	After upgrade, AVM 11 starts with errors
CSCtt41552	Unit is not redefined after upgrade to Prime Network 3.8
CSCty36682	Unit becomes unreachable after installation
CSCts17077	Duplicate ports displayed on module
CSCtw61690	LSP endpoints role oper state of neighbor device not changed to 'DOWN'
CSCtw79231	EFP updates are not reflected immediately on ASR903 using Poll Now
CSCtx19245	Some activation scripts are not working for Nexus 7000 device
CSCtx02470	Some activation scripts are not working for Nexus 5010 device
CSCtx48077	VDC level Interface Scripts are failing in Nexus 7K
CSCtx86760	Wrong pluggable transceiver out tickets on GSR 12k IOX
CSCtx94475	Not all of the configured timeslots on ds0 are displayed
CSCty10686	Container status is Unknown on Fan and PWR modules
CSCtx67165	Some entries are missing in IPInterface table for Ethernet port
CSCtr47998	After reloading a Cisco 7600 device, all related IP interface down events are not cleared
CSCtl12886	Cisco ASR 9000 series power supply redundancy state and configured value are None
CSCty88281	Configuring the VPLS E-LAN activation on Cisco 7600 device fails if VFI is not existing.
CSCty88309	Network Activation script failed to create E-LAN VPLS neighbor on Cisco ASR9000 device.
CSCty87987	Network Activation will not work without removing the timestamp on Cisco ASR9000 device.
CSCts07862	DS0 bundle and BGP vrf tickets not correlated to Sonet interface down
CSCtu12098	Missing VPN links after moving VNE
CSCtt44445	Ethernet counters test disconnects links
CSCts45734	In VLAN view, a path trace that ends on a LAG port does not run
CSCto75365	BFD links are not removed from the GUI after clearing a BFD connectivity down ticket
CSCts40361	Duplicate MPLS-TP network service objects are not automatically removed
CSCts01836	Modification of destination and source port not reflected in Prime Network
CSCtj03925	Physical and Ethernet links disappear after moving and restarting AVM
CSCts15613	LSE and MPLS soft properties added to a VNE are not visible in Inventory window
CSCtx87994	ENS: Incorrect alarms mapped to alarm-type 651
CSCty24297	Detailed Traps report on Event Vision does not show the real device IP
CSCtz36312	Incorrect command to enable VNE Staggering mechanism.
CSCty42565	NAT unit seen as regular if other device answers with same private ip
CSCty90696	Cross launch of VCB from Manage in Suite mode does not work
CSCtr30287	Port down ticket is not cleared after the port is up
CSCto42504	In OSPF Neighbor for cases like Bundle-Ether Interface name - OSPF Neighbor down alarms do not correlate to Link down on IOX
CSCts96142	AVM 11 does not process any links for 15 min
CSCtx45445	RHCS: Wrong version validation of rpm
CSCts48120	MPLS LDP session up trap is not correlated to Link up ticket
CSCtu70278	Poll now does not update Clock, PTP on reduced polling VNE
CSCtu95760	Syslog "L2-SONET_LOCAL-4-ALARM: SONET0/1/2/0: LAIS" not supported
CSCtw51495	Exception upon executing preview for "AddHostName Script" on ASR901
CSCtw95044	Bridges on Cisco ASR5000 device are not modeled
CSCtx29511	Configuration changes are not updated on XR VNE with reduced polling
CSCtx67427	Configuration change not updated for channelized controllers
CSCtx87344	7600: Channelization is not modeled on CHOC12 or 48 card
CSCtx90642	MWR2900: VNE fails associate transceiver cefc FRU trap wt port connector
CSCtx93011	EFPs are not modeled correctly
CSCty18359	ASR 5K Image distribution fails when password has special characters
CSCty19685	Shutting down a VRRP interface moves the CRS VNE to unreachable state
CSCtw96596	Cold Start Trap appears twice in the ENS selection window
CSCtx76206	Bridges are not modeled in ASR903
CSCty35489	Unable to create telnet credential without user name
CSCtu14594	Unit servers at 100% cpu due to XBgpRouterIDAdvertiseMsg message flood
CSCtt98442	Some edge EFPs are associated to 2 VLANs, one of which is invalid
CSCtn76375	Trunk service link is disconnected after configuring a static VLAN mapping that includes an inner VLAN tag
CSCts63063	ISIS neighbor data is not created for both IPv4 and IPv6 address families
CSCto82042	After a P2MP tunnel's status changes from Up to Down, the change is not reflected in Prime Network
CSCts82544	Some OSPF interfaces and neighbors are not modeled for CRS device
CSCts63874	Incorrect BDF links might be discovered for a BDF configuration that has two of the same source IP addresses with different destinations
CSCtr37523	Links table may display links which have no context but are not marked as external
CSCtt44288	BGP does not model in Prime Network if the BGP AS number contains a dot
CSCtq61849	Activating Image Command Builder script fails
CSCtq94497	Multiple "Active IP interfaces found" events returned after shutting down an interface
CSCtl47169	Syslog ENVMON-OVERTEMP-2 is not processed by Prime Network
CSCtl23101	Moving AVMs operation fails; not all AVMs are moved between units
CSCtr81979	OSPF neighbor down event may not correlate to link down or interface status down event
CSCty28617	Warning message about incompatible drivers when installing Cisco-Others

Closed Bugs

Table 13 identifies bugs that were listed as open bugs in the Prime Network 3.8.1 Release Notes and have since been closed.

Table 13 Closed Bugs in Cisco Prime Network 3.9 

Bug ID	Description
CSCty16496	7600: STS3 or STS12 paths not modeled on OC12 or OC48 interfaces
CSCtx79524	CCM operations will fail on IPv4/IPv6 dual stack setup
CSCtr42741	In Admin mode, Prime Network Change and Configuration Management may copy the running configuration instead of the admin configuration
CSCti93564	Cannot start new AVM 100 on unit when unit with old AVM 100 is down
CSCtq04992	Free memory on the unit decreases over time.
CSCts33148	Fake links between ATM ports although flag 'topology/atm/enabled' false

Related Documentation

A complete list of the documentation, and hyperlinks directly to them, is provided in the Cisco Prime  Network 3.9 Documentation Overview.

Cisco Prime Network 3.9 Integration Developer Guide is available on the Prime Network Technology Center. This guide describes how to use Prime Network integration interfaces.

The Prime Network Technology Center is an online resource for additional downloadable Prime Network support content, including help for integration developers who use Prime Network application programming interfaces (APIs). The website provides information, guidance, and examples to help you integrate your applications with Prime Network. It also provides a platform for you to interact with subject matter experts. To view the information on the Prime Network Technology Center website, you must have a Cisco.com account with partner level access, or you must be a Prime Network licensee. You can access the Prime Network Technology Center at: http://developer.cisco.com/web/prime-network/home.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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

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

---

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

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

© 2012 Cisco Systems, Inc. All rights reserved.