Step 1
| Deploy the
latest
Cisco Prime Network
Registrar
virtual appliance (with the new OS version) on the ESXi machine where the
existing
Cisco Prime Network
Registrar
virtual appliance resides.
|
Step 2
| Shut down
Cisco Prime Network
Registrar
on the existing virtual appliance. Use either /etc/init.d/nwreglocal stop or
/etc/init.d/nwregregion stop to stop the application, depending on whether you
are operating on a local or regional cluster.
|
Step 3
| Run
cnr_prepareforupgrade on the existing appliance.
|
Step 4
| Shut down the
virtual machine of the existing appliance.
|
Step 5
| The next few
steps will guide you through the process of copying the data disk (which
contains the Network Registrar databases) from the existing virtual appliance
to the new virtual appliance. You will use vSphere to make the copy. Ensure
that you have shut down both virtual appliances before copying.
|
Step 6
| Select the ESXi
platform in vSphere. It is not a particular virtual machine that you have to
select, but rather the container in which these virtual machines appear.
|
Step 7
| Select the
Configuration tab and click the
Storage link
under Hardware area. You can now see the datastores in the right hand window.
Determine the datastore in which the files for your virtual machines reside.
Note
|
You should
have selected the datastore when you deployed the virtual machines, if you have
more than one datastore. If you have only one, no selection was required at the
time of deployment.
|
|
Step 8
| Right-click the
datastore that contains the existing virtual machine. Select
Browse
Datastore.... A Datastore Browser is displayed which shows you the file
structure of your ESXi datastore.
Note
|
The
directories which you see in the Datastore Browser use the names given to the
virtual appliances when they were first deployed, which may or may not be the
current names of the virtual appliances. If you changed the name of a virtual
appliance after it was deployed, that name change will not be reflected in the
file structure in the datastore.
|
|
Step 9
| Select the
folder for the existing virtual appliance from the tree structure displayed at
the left pane of the Database Browser window. You can see the files which are
associated with the existing virtual appliance in the right pane of the
Database Browser window. Find the existing data disk from the list of files
displayed in the right pane. The name of the file of the existing data disk
ends with
_1.vmdk and
is the largest file in the virtual machine.
|
Step 10
| Right-click the
file you found in
Step 9 and
select
Copy.
|
Step 11
| Select the
folder of the new virtual appliance in the left pane of the Datastore Browser
window. You can see the files currently associated with the new virtual
appliance in the right pane of the window. Right-click in the right pane, and
not on a particular file, and select
Paste. Since
the file you are copying may be rather large, you can see a progress popup
which shows the copy progress. Close the Datastore Browser window when the copy
is complete.
|
Step 12
| Select the new
virtual appliance in the left pane of the vSphere client window and select
Edit virtual
machine settings. The Virtual Machine Properties window is displayed. The
Hardware tab is selected by default. If it is not, then select it.
|
Step 13
| Select Hard
disk 2 and click
Remove.
Accept the default
Removal
Option of
Remove from
virtual machine which does not delete the virtual disk file itself, but
rather just removes it from the virtual machine.
|
Step 14
| Select the new
virtual appliance again in the left pane of the vSphere client window and
select
Edit virtual
machine settings again. Click
Add in the
Virtual Machine Properties window to add the hard disk you copied from the
existing virtual machine.
The
Add
Hardware window is displayed.
|
Step 15
| Choose
Hard Disk
from the list of device types and click
Next.
|
Step 16
| Check the
Use an existing
virtual disk check box to allow you to use the virtual disk that you just
copied from the existing virtual appliance and click
Next.
|
Step 17
| Click
Browse to
locate the disk file path. Select the datastore where you placed the copy of
the virtual disk in the Browse Datastore window. Click
Open and you
can see the list of virtual machines on this datastore. Select the directory of
the new virtual appliance from the list and click
Open. You
can see the list of virtual disks in the directory for that virtual machine.
Probably two of them will be named the same as the new virtual machine, and one
of them will be named based on the existing virtual machine. Select the one
named for the existing virtual machine and click
OK. Click
Next.
|
Step 18
| Click
Next again
to accept the
Advanced
Options unchanged.
|
Step 19
| Click
Finish to
complete the operation.
This takes you
back to the Virtual Machine Properties window, and the list of hardware in the
virtual machine now has the
New Hard Disk
(adding) in the list. Click
OK to
finish.
You can now
start the new virtual machine. It will have the entire data disk of the
existing virtual machine.
Note
|
The virtual
machine with the upgraded operating system will pause during the boot process
and instruct you to upgrade the Cisco Prime Network Registrar database to match
the database version of the Cisco Prime Network Registrar application that
resides on the new virtual machine.
|
|
Step 20
| Run the file
and press return on the console to complete the boot process.
|
Step 21
| Log in as root
and run the displayed command.
After
boot completion, you should see your existing configuration running with the
new version of Cisco Prime Network Registrar on the new virtual machine.
|