Guest

Cisco Prime Infrastructure

Release Notes for Cisco Prime Infrastructure, Release 2.0.0.30

  • Viewing Options

  • PDF (140.5 KB)
  • Feedback

Table of Contents

Release Notes for Cisco Prime Infrastructure Plug and Play Gateway Patch 2.0.0.30

Introduction

Compatibility Information

System Requirements

Installation Notes

Plug and Play Gateway Patch Installation

Caveats

Open Caveats

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Prime Infrastructure Plug and Play Gateway Patch 2.0.0.30

First Published: April 16, 2014

OL-27939-04

 

This Release Notes document contains the following sections:

Introduction

The Cisco Prime Infrastructure Plug and Play Gateway Patch 2.0.0.30 provides a resolution for the port hanging issue and also provides cns disconnection options.

Compatibility Information

Cisco Prime Infrastructure Plug and Play Gateway Patch Release
Cisco Prime Infrastructure Release-Supported Servers
Cisco Plug and Play Deployment Application-Supported Releases

2.0.0.30

2.0 and 2.1

2.0.0.28

1.2.1.8

1.3.2

2.0.0.28

1.2.1.5

1.3 or 1.3.1

2.0.0.19

System Requirements

For information on hardware requirements, see the “Prime Infrastructure Plug and Play Gateway Server Requirements” section of the Cisco Prime Infrastructure 2.0 Quick Start Guide .

The Cisco Prime Infrastructure Plug and Play Gateway 2.0.0.30 standalone server patch must be installed on the Cisco Prime Infrastructure Plug and Play Gateway Server 2.0. The system requirements are the same as that for the Cisco Prime Infrastructure 2.0 Plug and Play Gateway Server.

Installation Notes

This section contains instructions for installing the Cisco Prime Infrastructure Plug and Play Gateway.

Plug and Play Gateway Patch Installation

The Plug and Play Gateway standalone server patch is available in the pnp-gateway-patch-2.0.0.30.tar.gz file. The patch upgrade procedure requires an FTP or TFTP server containing the patch file.

You can access this server from the Cisco Prime Infrastructure 2.0 Plug and Play Gateway standalone server by following these steps:

1. Log in to the Plug and Play Gateway standalone server as admin user. The following is a sample output of the patch upgrade with the url FTP:

pnp-server login: admin
Password:
pnp-server/admin# configure
Enter configuration commands, one per line. End with CNTL/Z.
pnp-server/admin(config)# repository <repository_name>
pnp-server/admin(config-Repository)# url ftp://<SERVER_HOST_NAME>/<FOLDER_LOCATION>
pnp-server/admin(config-Repository)# user <USER_ID> password <OPTION> <PASSWORD>
pnp-server/admin(config-Repository)# exit
pnp-server/admin(config)# exit

2. Use the application upgrade command to install the pnp-gateway-patch-2.0.0.30.tar.gz Plug and Play Gateway standalone patch. The following is a sample output of the pnp gateway patch upgrade:

bgl-dt-ncs-vm64-228/admin# application upgrade pnp-packaging-2.0.0.30.tar.gz repository_name
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
Stage 3 of 7: Executing pre-install ...
-- complete.
Stage 4 of 7: Upgrading binaries ...
-- complete.
Restore the Version 2.0.0.30
Restoring on a new installation setup required
------------------------------------------------
Thu Mar 6 04:17:23 UTC 2014
Restore operation started
------------------------------------------------
Backup Filename used is /tmp/pnp_upgrade/20140306041647.pnp_backup.tar.gz
Upgrade from 2.0.0.28 setup required
 
Upgrade operation no automatic setup possible
Restore operation ended
------------------------------------------------
Starting application ...
-- complete.
 
Application upgrade successful

3. Exit from the current terminal (shell) and re-login as admin user.

4. Execute the pnp setup command to reconfigure the Plug and Play standalone server and start the plug and play process.


NoteTo enable the automatic event disconnection use the Plug and Play advanced setup option. Press ‘Y’ when prompted with “Turn down device connection after first successful configuration push (y/n)”. By default the option is set to ‘N’, which means the connection is disabled. To enable the automatic event disconnection use the Plug and Play advanced setup option. Press ‘Y’ when prompted with “Turn down device connection after first successful configuration push (y/n)”. By default the option is set to ‘N’, which means the connection is disabled.


Caveats

This section lists the open and resolved caveats for Cisco Prime Infrastructure Release 2.0.0.30:

Open Caveats

There are no open caveats for Cisco Prime Infrastructure Release 2.0.0.30.

Resolved Caveats

  • CSCum59876

Symptoms: Plug and Play Gateway must provide an option to disconnect the Cisco Networking System (CNS) connection once the CNS processing is completed.

Conditions: This option must be enabled only with a single configuration.

Workaround: This issue is resolved.

  • CSCui47481

Symptoms: The Plug and Play Gateway 11016 port hangs when all devices reconnect together.

Conditions: This condition occurs due to the tunnel rekey.

Workaround: This issue is resolved.

Related Documentation

You can access the following additional Cisco Prime Infrastructure documentation on Cisco.com:

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