Table Of Contents
Release Notes for Cisco Prime Infrastructure Plug and Play Gateway Patch 220.127.116.11
First Published: April 19, 2013OL-29537-01
This Release Notes document contains the following sections:
The Cisco Prime Infrastructure Plug and Play Gateway Patch 18.104.22.168 provides support for the Cisco Prime Infrastructure Plug and Play application to download the bootstrap configuration.
For information on hardware requirements, refer to the "Prime Infrastructure PnP Gateway Server Requirements" section of the Cisco Prime Infrastructure 1.2 Quick Start Guide.
The Cisco Prime Infrastructure Plug and Play Gateway 1.2.1 standalone server patch must be installed on the Cisco Prime Infrastructure Plug and Play Gateway server 1.2. The system requirements are the same as that for the Cisco Prime Infrastructure 1.2 Plug and Play Gateway server.
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-22.214.171.124.tar.gz file.
The patch upgrade procedure requires an FTP or TFTP server containing the patch file. This server must be reachable from the Cisco Prime Infrastructure 1.2 Plug and Play Gateway standalone server.
1. Log in to the Plug and Play Gateway standalone server as admin user.
2. Create a repository in the configuration mode and execute the repository command by providing the repository name and other details.
3. Use the patch install command to install the pnp-gateway-patch-126.96.36.199.tar.gz Plug and Play Gateway standalone patch.
4. Execute the pnp setup command to reconfigure the Plug and Play standalone server and start the plug and play processes.
The following is a sample output of the patch upgrade with the url FTP:pnp-server login: adminPassword:pnp-server/admin# configureEnter 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)# exitpnp-server/admin(config)# exitpnp-server/admin#pnp-server/admin# patch install pnp-gateway-patch-188.8.131.52.tar.gz pnp-patching-<VERSION>.tar.gz <repository_name>Save the current ADE-OS running configuration? (yes/no) [yes] ?Generating configuration...Saved the ADE-OS running configuration to startup successfullyInitiating Application Patch installation...Patch successfully installedpnp-server/admin#pnp-server/admin# pnp setup
Cisco Prime Infrastructure Plug and Play Gateway 1.2.1 is a mandatory patch that must be installed in Cisco Prime Infrastructure Plug and Play Gateway server 1.2 for the Cisco Prime Infrastructure Plug and Play functionality to work properly in Cisco Prime Infrastructure Release 1.3 or later (later release of 1.x).
This section lists the open and resolved caveats for Cisco Prime Infrastructure Release 184.108.40.206:
Symptom: An error message is displayed during the Plug and Play standalone server setup.
Condition: During the Plug and Play standalone server setup, when the pnp setup command is run, the Plug and Play Gateway on the standalone server tries to disable the local Plug and Play Gateway on Cisco Prime Infrastructure. This results in the Plug and Play Gateway in the standalone server not receiving the correct CLIs from Cisco Prime Infrastructue, and the following error message is displayed:Attempting to disable the local PnP Gateway in Prime Infrastructure Machine 10.104.105.170Enter the username to login to the Prime Infrastructure Machine: [admin]Enter the password to login to the Prime Infrastructure Machine:Unknown error <ncs pnp disable
Workaround: You can ignore the error message.
Symptom: The configuration CLI template fails on Cisco Prime Infrastructure even if the CLIs are pushed to the device.
Condition: When Cisco Prime Infrastructure deploys the configuration CLI template, in some cases, when the device displays warning messages, these warning messages are treated as failure by Cisco Prime Infrastructure.
Workaround: When you find that the configuration CLI template has failed on Cisco Prime Infrastructure, check the ifm_pnp logs to check the actual cause of the failure. If the logs do not show any invalid CLI strings and the warning message (from the device) can be viewed in the logs, the
config failurestatus shown on Cisco Prime Infrastructure can be ignored.
There are no resolved caveats for Cisco Prime Infrastructure Plug and Play Gateway Release 220.127.116.11.
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:
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.
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.
© 2013 Cisco Systems, Inc. All rights reserved.