Installing and Configuring Cisco Prime Access Registrar 6.0
Chapter 4 Upgrading Cisco Access Registrar Software
Downloads: This chapterpdf (PDF - 163.0KB) The complete bookPDF (PDF - 902.0KB) | Feedback

Upgrading Cisco Prime Access Registrar Software

Table Of Contents

Upgrading Cisco Prime Access Registrar Software

Software Pre-Upgrade Tasks

Disabling Replication

Backup Copy of Original Configuration

Backup SNMP Configuration

Upgrading Cisco Prime Access Registrar on Solaris

Upgrading Cisco Prime Access Registrar on Solaris on the Same Server

Upgrading Cisco Prime Access Registrar on Solaris on a New Server

Tasks in the Existing Server

Tasks in the New server.

Upgrading Cisco Prime Access Registrar on Linux

Upgrading Cisco Prime Access Registrar on Linux on the Same Server

Upgrading Cisco Prime Access Registrar on Linux on a New Server

Tasks in the Existing Server

Tasks in a New Server

Software Post-Upgrade Tasks

Removing Old VSA Names

VSA Update Script

Configuring SNMP

Restarting Replication


Upgrading Cisco Prime Access Registrar Software


Cisco Prime AR 6.0 supports software upgrades from previously installed Cisco Prime AR software while preserving the existing configuration database. Cisco Prime AR supports an upgrade path for both the Solaris or Linux versions of Cisco Prime AR software.


Note Configuration for Prepaid billing servers in Cisco Prime AR 3.0 will no longer work in Cisco Prime AR 6.0. If you have been using a Prepaid billing server in Cisco Prime AR 3.0 and are upgrading your software to Cisco Prime AR 6.0, you must remove the Prepaid billing server configuration before installing the Cisco Prime AR 6.0 software. Chapter 16, "Using Prepaid Billing," provides detailed instructions for configuring Prepaid billing services for Cisco Prime AR.



Caution Running the command mcdadmin -coi to import configuration data will cause the Cisco Prime AR 6.0 server to lose all session information.

This chapter contains the following sections:

Software Pre-Upgrade Tasks

Upgrading Cisco Prime Access Registrar on Solaris

Upgrading Cisco Prime Access Registrar on Linux

Software Post-Upgrade Tasks

Software Pre-Upgrade Tasks

This section describes the tasks that have to be followed before upgrading the Cisco Prime AR software. This section consists of the following subsections:

Disabling Replication

Backup Copy of Original Configuration

Backup SNMP Configuration

Disabling Replication

If you are using the Cisco Prime AR replication feature, you must disable it before you begin the upgrade process are the upgrade will fail. When completed, see "Restarting Replication" section for the correct way to restart replication.

To ensure that replication is disabled, complete the following steps:


Step 1 Login as admin and launch aregcmd.

Step 2 Change directory to /radius/replication and examine the RepType property.

cd /radius/replication

[ //localhost/Radius/Replication ]
RepType = None
RepTransactionSyncInterval = 60000
RepTransactionArchiveLimit = 100
RepIPAddress = 0.0.0.0
RepPort = 1645
RepSecret = NotSet
RepIsMaster = FALSE
RepMasterIPAddress = 0.0.0.0
RepMasterPort = 1645
Rep Members/

Make sure that RepType is set to None.

Step 3 If you make changes, issue the save command, then exit the aregcmd command interface.

Backup Copy of Original Configuration

The upgrade process displays a message like the following to indicate where a copy of your original configuration has been stored.


Note Running the command mcdadmin -coi to import configuration data will cause the Cisco Prime AR server to lose all session information.
Configuration files, like the tcl script file, are replaced with default files on upgrade. Hence, before upgrading, back up the existing file to prevent any loss of data. After upgrading, replace the /opt/CSCOar/scripts/radius/tcl/tclscript.tcl with the back up file.


###############################################################
#
#  A backup copy of your original configuration has been
#  saved to the file:
#
#    /opt/CSCOar/temp/10062.origconfig-backup
#
#  If you need to restore the original configuration,
#  enter the following command:
#
#    mcdadmin -coi /opt/CSCOar/temp/10062.origconfig-backup
#
###############################################################
 
   

Backup SNMP Configuration

If you choose not to use the SNMP features of Cisco Prime AR, the installation process is completed. To use SNMP features, complete the configuration procedure described in "Configuring SNMP" section.

If you have modified the snmpd.conf file in the /cisco-ar/ucd-snmp/share/snmp directory, you must back up this file before doing the upgrade process. The pkgrm removes the snmpd.conf file, even if it has been modified.

Upgrading Cisco Prime Access Registrar on Solaris

This section describes the Solaris upgrade processes on the same server and on a different server. This section consists of the following subsections:

Upgrading Cisco Prime Access Registrar on Solaris on the Same Server

Upgrading Cisco Prime Access Registrar on Solaris on a New Server

Upgrading Cisco Prime Access Registrar on Solaris on the Same Server

To upgrade the Solaris software on the same server:


Step 1 Ensure that you back up a copy of your original configuration.

See See Backing Up the Database.

Step 2 Ensure the replication is disabled.

See "Disabling Replication" section.

Step 3 If you have modified the snmpd.conf file in the /cisco-ar/ucd-snmp/share/snmp directory, you must back up this file before doing the upgrade process. The pkgrm removes the snmpd.conf file, even if it has been modified.

Step 4 If you have added any scripts or modified any existing scripts in /cisco-ar/scripts/radius directory, you must back up those files before doing the upgrade process. The pkgrm removes all scripts, even if it has been modified in the existing script.

Step 5 Remove the old software using the pkgrm command.

See "Uninstalling Cisco Prime Access Registrar Software on Solaris" section.

Step 6 If you plan to use the Cisco Prime AR SNMP features, disable the current Sun SNMP daemon and prevent the Sun SNMP daemon from restarting after a reboot.

Step 7 Decide where to install the Cisco Prime AR 6.0 software.

Step 8 Decide if you want to preserve your existing configuration database.

Preserving your existing configuration database is a compelling reason to upgrade rather than to start anew. The upgrade procedure in this chapter assumes you want to preserve your existing configuration.

Step 9 Copy the Cisco Prime AR 6.0 license file to a location on the Cisco Prime AR workstation directory such as /tmp.

For detailed information about the Cisco Prime AR license and how to install the license, see "Cisco Prime Access Registrar 6.0 Licensing" section.

Step 10 Use the pkgadd command to install the Cisco Prime AR 6.0 software.

For detailed information about using the pkgadd command to install Cisco Prime AR software, see Chapter 2 "Installing Cisco Prime Access Registrar 6.0."


Note Since you are upgrading, you will want to preserve your existing database.


Step 11 If you configured Cisco Prime AR to use SNMP prior to upgrading, after installing Cisco Prime AR 6.0 software, you must copy the snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory.

Step 12 After installing Cisco Prime AR 6.0, you must copy back the scripts to /cisco-ar/scripts/radius directory.

Step 13 Restart the Cisco Prime AR server using the following command:

/etc/init.d/arserver  restart


Upgrading Cisco Prime Access Registrar on Solaris on a New Server

To upgrade the Solaris software on a new server follow the following tasks:

Tasks in the Existing Server


Step 1 Ensure that you back up a copy of your original configuration.

See Backing Up the Database.

Step 2 Ensure the replication is disabled.

See "Disabling Replication" section.

Step 3 If you have modified the snmpd.conf file in the /cisco-ar/ucd-snmp/share/snmp directory, you must back up this file before doing the upgrade process. The pkgrm removes the snmpd.conf file, even if it has been modified.

See Backup SNMP Configuration.

Step 4 If you have added any scripts or modified any existing scripts in /cisco-ar/scripts/radius directory, you must back up those files before doing the upgrade process. The pkgrm removes some of the scripts, even if it has been modified in the existing script.


Note Configuration files, like the tcl script file, are replaced with default files on upgrade. Hence, before upgrading, back up the existing file to prevent any loss of data. After upgrading, replace the /opt/CSCOar/scripts/radius/tcl/tclscript.tcl with the back up file.


Step 5 Remove the old software using the pkgrm command. See "Upgrading Cisco Prime Access Registrar on Solaris" section.

Step 6 Tar the /opt/CSCOar/data directory to a temporary location such as /tmp.

Tasks in the New server.

Step 7 Untar the backup /opt/CSCOar/data directory. Copy the SNMP file, PKI directory, and the scripts to the installed base directory (/opt/CSCOar/).

Step 8 If you plan to use the Cisco Prime AR SNMP features, disable the current Sun SNMP daemon and prevent the Sun SNMP daemon from restarting after a reboot.

Step 9 Decide where to install the Cisco Prime AR 6.0 software.

Step 10 Copy the Cisco Prime AR 6.0 license file to a location on the Cisco Prime AR workstation directory such as /tmp.

For detailed information about the Cisco Prime AR license and how to install the license, see "Cisco Prime Access Registrar 6.0 Licensing" section.

Step 11 Use the pkgadd command to install the Cisco Prime AR 6.0 software.

For detailed information about using the pkgadd command to install Cisco Prime AR software, see Chapter 2 "Installing Cisco Prime Access Registrar 6.0."


Note Enter Y to preserve the local database.
Preserving your existing configuration database is a compelling reason to upgrade rather than to start a new. The upgrade procedure in this chapter assumes you should do to preserve your existing configuration.


Step 12 Stop the Cisco Prime AR server using the following command:

/opt/CSCOar/bin/arserver stop

Step 13 If you configured Cisco Prime AR to use SNMP prior to upgrading, after installing Cisco Prime AR 6.0 software, you must copy the snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory.

Step 14 After installing Cisco Prime AR, you must copy back the scripts to /cisco-ar/scripts/radius directory.

Step 15 Restart the Cisco Prime AR server using the following command:

/etc/init.d/arserver  restart


Upgrading Cisco Prime Access Registrar on Linux

This section describes the Solaris upgrade processes on the same server and on a different server. This section consists of the following subsections:

Upgrading Cisco Prime Access Registrar on Linux on the Same Server

Upgrading Cisco Prime Access Registrar on Linux on a New Server

Upgrading Cisco Prime Access Registrar on Linux on the Same Server

To upgrade the Linux software on the same server:


Step 1 Ensure that you back up a copy of your original configuration.

See Backing Up the Database.

Step 2 Ensure the replication is disabled.

See "Disabling Replication" section.

Step 3 If you have installed Cisco Prime AR with SIGTRAN_M3UA process, ensure that the host name is not set in the HostName/SourceIPAddress field as part of the SIGTRAN_M3UA server properties. Only IP address must be set as part of the server properties.

Step 4 If you have modified the snmpd.conf file in the /cisco-ar/ucd-snmp/share/snmp directory, you must back up this file before doing the upgrade process. The pkgrm removes the snmpd.conf file, even if it has been modified.


Note If you currently use the 3.5.2 Linux version, the uninstall-ar program removes /opt/CSCOar/data. Before you run the uninstall-ar program, copy the /opt/CSCOar/data directory to a temporary location such as /tmp. After you install the upgrade software, move the data directory back to /opt/CSCOar/data.


Step 5 If you have added any scripts or modified any existing scripts in /cisco-ar/scripts/radius directory, you must back up those files before doing the upgrade process.

Step 6 Remove the old software using the uninstall-ar command.

For detailed information about using the uninstall-ar command to remove Cisco Prime AR Linux software, see "Uninstalling Cisco Prime Access Registrar Software on Linux" section.

Step 7 If you plan to use the Cisco Prime AR SNMP features, disable the current SNMP daemon and prevent the SNMP daemon from restarting after a reboot.

Step 8 Decide where to install the Cisco Prime AR 6.0 software.

The default installation directory for Cisco Prime AR 6.0 software is /opt/CSCOar.

Step 9 Decide if you want to preserve your existing configuration database.

Preserving your existing configuration database is a compelling reason to upgrade rather than to start anew. The upgrade procedure in this chapter assumes you want to preserve your existing configuration.

Step 10 Copy the Cisco Prime AR 6.0 license file to a location on the Cisco Prime AR workstation directory such as /tmp.

Step 11 Install the Linux version of Cisco Prime AR 6.0 software.

Step 12 If you configured Cisco Prime AR to use SNMP prior to upgrading, after installing Cisco Prime AR 6.0 software, you must copy the snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory.

Step 13 After installing Cisco Prime AR, you must copy back the scripts to /cisco-ar/scripts/radius directory.

Step 14 Restart the Cisco Prime AR server using the following command:

/etc/init.d/arserver  restart


Upgrading Cisco Prime Access Registrar on Linux on a New Server

To upgrade the Linux software on a new server follow the following tasks:

Tasks in the Existing Server


Step 1 Ensure that you back up a copy of your original configuration.

See Backing Up the Database.

Step 2 Ensure the replication is disabled.

See "Disabling Replication" section.

Step 3 If you have installed Cisco Prime AR with SIGTRAN_M3UA process, ensure that the host name is not set in the HostName/SourceIPAddress field as part of the SIGTRAN_M3UA server properties. Only IP address must be set as part of the server properties.

Step 4 If you have modified the snmpd.conf file in the /cisco-ar/ucd-snmp/share/snmp directory, you must back up this file before doing the upgrade process. The pkgrm removes the snmpd.conf file, even if it has been modified.

See Backup SNMP Configuration.

Step 5 If you have added any scripts or modified any existing scripts in /cisco-ar/scripts/radius directory, you must back up those files before doing the upgrade process. The uninstall-ar removes some of the scripts, even if it has been modified in the existing script.


Note Configuration files, like the tcl script file, are replaced with default files on upgrade. Hence, before upgrading, back up the existing file to prevent any loss of data. After upgrading, replace the /opt/CSCOar/scripts/radius/tcl/tclscript.tcl with the back up file.


Step 6 Remove the old software using the uninstall-ar command.

For detailed information about using the uninstall-ar command to remove Cisco Prime AR Linux software, see "Uninstalling Cisco Prime Access Registrar Software on Linux" section.

Step 7 Tar the /opt/CSCOar/data directory to a temporary location such as /tmp.

Tasks in a New Server

Step 8 Untar the backup /opt/CSCOar/data directory. Copy the SNMP file, PKI directory, and the scripts to the installed base directory (/opt/CSCOar/).

Step 9 Decide where to install the Cisco Prime AR 6.0 software.

Step 10 Copy the Cisco Prime AR 6.0 license file to a location on the Cisco Prime AR workstation directory such as /tmp.

For detailed information about the Cisco Prime AR license and how to install the license, see "Cisco Prime Access Registrar 6.0 Licensing" section.

Step 11 Install the Linux version of Cisco Prime AR 6.0 software.

Step 12 If you configured Cisco Prime AR to use SNMP prior to upgrading, after installing Cisco Prime AR 6.0 software, you must copy the snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory.

Step 13 After installing Cisco Prime AR, you must copy back the scripts to /cisco-ar/scripts/radius directory.

Step 14 Restart the Cisco Prime AR server using the following command:

/etc/init.d/arserver  restart


Software Post-Upgrade Tasks

This section provides information about the tasks involved in the Cisco Prime AR software upgrade process. This section consists of the following subsections:

Removing Old VSA Names

VSA Update Script

Configuring SNMP

Restarting Replication

Removing Old VSA Names

The upgrade process provides an analysis of the configuration database, addition of new database elements, and a search for obsolete VSA names. When this is complete, a message like the following is displayed:

##############################################################
#
#   Sometimes VSAs get renamed from version to version of Cisco Prime AR.
#   The upgrade process does not automatically remove the
#   old names. The upgrade process has generated a script
#   to remove the old names. The script is located in:
#
#       /opt/CSCOar/temp/10062.manual-deletes
#
#   Review the script to make sure you are not using any of
#   these old VSAs. Modify your configuration and your
#   scripts to use the new names before you attempt to run
#   the script.
#
#   To run the removal script, type:
#
#       aregcmd -sf /opt/CSCOar/temp/10062.manual-deletes
#
##############################################################
 
   

At this point, you should examine the script produced by the upgrade process to make sure that your site is not using any of the old VSAs. In the example above, the script can be found at /opt/CSCOar/temp/10062.manual-deletes.


Note The number preceding manual.deletes is produced from the PID of the upgrade process.


Modify your configuration and your scripts to use the new names before you attempt to run the script generated by the upgrade process.

VSA Update Script

The upgrade process builds a script you can use to update VSAs in your system.

##############################################################
#
#   VSAs for the old Cisco Prime AR version are not updated
#   automatically. The upgrade process generated a script
#   to perform the update. The script is located in:
#
#       /opt/CSCOar/temp/10062.manual-changes
#
#   Review the script to make sure it does not conflict with
#   any of your VSA changes. Make sure you modify the script,
#   if necessary, before you attempt to run it.
#
#   To run the update script, type:
#
#       aregcmd -sf /opt/CSCOar/temp/10062.manual-changes
#
##############################################################
 
   

Step 1 Review the script and make sure that the changes it will make do not conflict with any changes you might have made to the VSAs. Modify the script if necessary.

Step 2 Record the location of the upgrade messages for future reference.

##############################################################
#
#  These upgrade messages are saved in:
#
#      /opt/CSCOar/temp/10062.upgrade-log
#
##############################################################
 
   

Configuring SNMP

After installing Cisco Prime AR 6.0 software with pkgadd, you must copy the already copied snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory. Restart the Cisco Prime AR server using the following command:

/etc/init.d/arserver  restart

Restarting Replication

Before you enable replication, you must first upgrade all replication slave servers to the same version of Access Registrar software as the master server. Do not enable replication on the master server until all slave servers have been upgraded.

Use the same process you used to upgrade the master server to upgrade any slave servers. If you retained your configuration on the master, retain the configuration on the slaves, too.

After the same version of Cisco Prime AR software has been installed on all slave servers, you can enable replication on the master server again. After enabling replication on the master server, you can enable replication on each of the slave servers.