![]() |
Table Of Contents
Release Notes for Cisco Prime Infrastructure Plug and Play Gateway Patch 1.2.1.8
Plug and Play Gateway Patch Installation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Prime Infrastructure Plug and Play Gateway Patch 1.2.1.8
First Published: September 27, 2013OL-30468-01This Release Notes document contains the following sections:
•
Obtaining Documentation and Submitting a Service Request
Introduction
The Cisco Prime Infrastructure Plug and Play Gateway Patch 1.2.1.8 provides support for the Cisco Prime Infrastructure Plug and Play application to download the bootstrap configuration.
Compatibility Information
System Requirements
For information on hardware requirements, see the "Prime Infrastructure Plug and Play 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.
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-1.2.1.8.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 1.2 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 patch install command to install the pnp-gateway-patch-1.2.1.8.tar.gz Plug and Play Gateway standalone patch. The following is a sample output of the pnp gateway patch upgrade:
pnp-server/admin#
pnp-server/admin# patch install pnp-gateway-patch-1.2.1.8.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 successfully
Initiating Application Patch installation...
Patch successfully installed
pnp-server/admin#
3.
Execute the pnp setup command to reconfigure the Plug and Play standalone server and start the plug and play process.
Caveats
This section lists the open and resolved caveats for Cisco Prime Infrastructure Release 1.2.1.8:
Open Caveats
•
CSCud61403
Symptom: An error message is displayed during the Plug and Play standalone server setup.
Condition: During the Plug and Play standalone server setup, when you run the pnp setup command, 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 being 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 disableWorkaround: Ignore the error message.
•
CSCuc47341
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 for 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 failure
status message that is displayed on Cisco Prime Infrastructure can be ignored.Resolved Caveats
•
CSCui18743
Symptoms: The username and password are clearly displayed in the log files.
Conditions: The Prime Infrastructure username and password are displayed in clear text when the Plug and Play Gateway log files are generated.
Workaround: There is no workaround.
•
CSCui47481
Symptoms: The Cisco Networking Service(CNS) ports hang.
Conditions: The CNS ports hang when the managed device's interfaces are flapping.
Workaround: There is no workaround.
Related Documentation
You can access the following additional Cisco Prime Infrastructure documentation on Cisco.com:
•
Cisco Prime Infrastructure 1.2 Quick Start Guide
•
Cisco Prime Infrastructure 1.2 User Guide
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.
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.