Cisco Cisco Prime Infrastructure 2.1 설치 가이드
16
Installing the Plug and Play Gateway Patch
The Plug and Play Gateway standalone server patch is available in the pnp-gateway-patch-2.0.0.28.tar.gz file.
The patch upgrade procedure requires an FTP or TFTP server containing the patch file. You can access the server from the Cisco
Prime Infrastructure 1.2 Plug and Play Gateway standalone server.
Prime Infrastructure 1.2 Plug and Play Gateway standalone server.
Step 1
Log in to the Plug and Play Gateway standalone server as admin user.
Step 2
Create a repository in the configuration mode and execute the repository command by providing the repository name
and other details.
and other details.
Step 3
Use the patch install command to install the pnp-gateway-patch-2.0.0.28.tar.gz Plug and Play Gateway standalone
patch.
patch.
Step 4
Execute the pnp setup command to reconfigure the Plug and Play standalone server and start the plug and play
processes. For example:
processes. For example:
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
pnp-server/admin#
pnp-server/admin# patch install pnp-gateway-patch-2.0.0.28.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#
pnp-server/admin# pnp setup
Migrating to a New System
System migration is the preferred option for most upgrades of production installations. In most cases, you will need to supply
new server hardware to complete the migration.
new server hardware to complete the migration.
Note that, to use this path, you must be migrating from one of the release levels listed in
.
Step 1
Before you begin, remove any existing High Availability configuration from your primary and secondary Prime
Infrastructure servers. You can do this using either of the following options:
Infrastructure servers. You can do this using either of the following options:
•
Launch Prime Infrastructure, choose Administration > High Availability > HA Configuration, and click Remove.
•
Open a command-line interface session with the Prime Infrastructure server (see
in theCisco
Prime Infrastructure 2.1 Administrator Guide and run the ncs ha remove command.
Step 2
If you have not already done so: Set up a remote backup repository for the old host. For details, see
in the Cisco Prime Infrastructure 2.1 Administrator Guide.
Step 3
Take an application backup of the old host on the remote repository. For details, see
in
the Cisco Prime Infrastructure 2.1 Administrator Guide
Step 4
Install the new host as explained in
Step 5
Configure the new host to use the same remote backup repository as the old host.
Step 6
Restore the application backup on the remote repository to the new host, as explained in
in the Cisco Prime Infrastructure 2.1 Administrator Guide.