Cisco Cisco Prime Network 3.8
5
Cisco Prime Network 3.8.1 Release Notes
OL-26395-01
Installation and Upgrade Notes Specific to Prime Network 3.8.1
ps -ef | grep
network user
Rolling Back from Prime Network 3.8.1
Rollback is available if you encounter problems during the upgrade, or if you need to roll back to an
earlier version after the upgrade completes.
earlier version after the upgrade completes.
Note
If you are rolling back a gateway and one or more units are connected to the gateway, roll back the units
first, then the gateway. The rollback will remove redundant units from the registry and the
GoldenSource.
first, then the gateway. The rollback will remove redundant units from the registry and the
GoldenSource.
Complete the following procedure to roll back to Prime Network 3.8 or ANA 3.7.x:
Step 1
Verify that the Prime Network application is not running.
Step 2
Verify that the gateway and units are powered up and connected. That is, you can open an SSH session
between the gateway and all units.
between the gateway and all units.
Step 3
If your environment contains standby/NAT units, use Prime Network Administration to remove the
standby units from the gateway.
standby units from the gateway.
Step 4
Restore the backed-up database and start the database services and the listener. The database backup was
done during the upgrade process as the database table structure changes during the upgrade. In order for
the system to function correctly after a rollback, the old table structure must be recovered through a
database backup. To restore an external database, contact your database administrator. Do the following
to restore an embedded database:
done during the upgrade process as the database table structure changes during the upgrade. In order for
the system to function correctly after a rollback, the old table structure must be recovered through a
database backup. To restore an external database, contact your database administrator. Do the following
to restore an embedded database:
a.
Log into the gateway as network user.
b.
Change to the directory NETWORKHOME/Main/scripts/embedded_db:
# cd $ANAHOME/Main/scripts/embedded_db
c.
Execute the restoration script:
# emdbctl --restore
Note
After you restore the database, Prime Network tries to reboot. The reboot does not succeed and
an error appears in the gateway log that AVMs with a heap size of 6 GB cannot be configured.
You can ignore this message and continue with the next step.
an error appears in the gateway log that AVMs with a heap size of 6 GB cannot be configured.
You can ignore this message and continue with the next step.
Step 5
If rolling back to 3.8, save the ~/Main/.ana and ~/Main/.version files for all units outside of the Prime
Network home directory. If rolling back to 3.7.x, continue to
Network home directory. If rolling back to 3.7.x, continue to
.
Step 6
Uninstall and install 3.8 or 3.7.x unit (depending on the version you are rolling back to), but do not
configue the unit at this point.
configue the unit at this point.
Note
Make sure the unit’s user name and directory is same as the gateway.
Step 7
As the network user, go to the directory where the upgrade directory was copied during the upgrade
procedure and enter the following command to change to the upgrade directory:
procedure and enter the following command to change to the upgrade directory: