Cisco Prime Access Registrar 9.3 Installation Guide

Disabling Replication

If you are using the Prime Access Registrar replication feature, you must disable it before you begin the upgrade process otherwise 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 Log in 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.

Step 4 Restart the server.

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 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.

Backup MCD File

Prime Access Registrar will prompt you to upgrade from 32-bit to 64-bit architecture, when you upgrade from any earlier version to Prime Access Registrar 9.3. For successful upgrade from 32-bit to 64-bit, MCD backup is required. You must ensure that you take a backup of the MCD file using the following command before uninstalling the previous version:

Backup SNMP Configuration

To use SNMP features, complete the configuration procedure described in “Configuring SNMP” section in the “Configuring Cisco Prime Access Registrar” chapter of the Cisco Prime Access Registrar 9.3 Administrator Guide.

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. Uninstallation of Prime Access Registrar removes the snmpd.conf file, even if it has been modified.

Upgrading Cisco Prime Access Registrar on the Same Server

To upgrade the software on the same server:

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

See the “Backing Up the Database” section of the Cisco Prime Access Registrar 9.2 User Guide.

Step 2 Ensure the replication is disabled.

See “Disabling Replication” section.

Step 3 If you have installed Prime Access Registrar 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. Uninstallation of Prime Access Registrar 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 Prime Access Registrar software, see “Uninstalling Prime Access Registrar 9.3 Software” section.

Step 7 If you plan to use the Prime Access Registrar 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 Access Registrar software.

The default installation directory for Prime Access Registrar 9.3 software is /opt/CSCOar.

Note If you wish to install Prime Access Registrar in a different directory, you must create a softlink in the default directory to point to the installation directory.

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 Access Registrar license file to a location on the Prime Access Registrar workstation directory such as /tmp.

Step 11 Install the Cisco Prime Access Registrar software. For more information, see Common Installation Steps.

Step 12 During the installation process, you will be prompted to provide the following information for software upgrade:

• Whether to upgrade from 32-bit to 64-bit architecture. If you upgrade from any earlier version (prior to Prime Access Registrar 7.x) to Prime Access Registrar 9.3, the response must be y (Yes).

Note Sessions will not be upgraded when you upgrade Prime Access Registrar from 32-bit to 64-bit architecture.

• The location of the MCD backup file. For successful upgrade from 32-bit to 64-bit, MCD backup is required and you must specify the location of the backup file.

Step 13 If you configured Prime Access Registrar to use SNMP prior to upgrading, after installing Prime Access Registrar 9.3 software, you must copy the backed up snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory.

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

Step 15 Restart the Prime Access Registrar server using the following command:

/etc/init.d/arserver restart

Upgrading Cisco Prime Access Registrar 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 the “Backing Up the Database” section of the Cisco Prime Access Registrar 9.2 User Guide.

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 Prime Access Registrar Linux software, see “Uninstalling Prime Access Registrar 9.3 Software” section.

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

Tasks in a New Server

Step 8 Untar the backup of /opt/CSCOar/data and /opt/CSCOar/temp directories. 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 Access Registrar software.

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

For detailed information about the Prime Access Registrar license and how to install the license, see “Cisco Prime Access Registrar 9.3 Licensing” section.

Step 11 Install the Cisco Prime Access Registrar software. For more information, see Common Installation Steps.

Step 12 During the installation process, you will be prompted to provide the following information for software upgrade:

• Whether to upgrade from 32-bit to 64-bit architecture. If you upgrade from any earlier version (prior to Prime Access Registrar 7.x) to Prime Access Registrar 9.3, the response must be y (Yes).

Note Sessions will not be upgraded when you upgrade Prime Access Registrar from 32-bit to 64-bit architecture.

• The location of the MCD backup file. For successful upgrade from 32-bit to 64-bit, MCD backup is required and you must specify the location of the backup file.

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

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

Step 15 Restart the Prime Access Registrar server using the following command:

/etc/init.d/arserver restart

If you wish to upgrade Prime Access Registrar from an earlier version to 9.3 with Smart Licensing enabled:

– You must place the traditional license files for that version in the $INSTALLPATH/license folder and these licenses will be automatically upgraded to smart license. You need not configure them.

– You must ensure that only valid licenses are present in the installation path folder.

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:

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.

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.

Configuring SNMP

After installing Prime Access Registrar 9.3 software, you must copy the already copied snmpd.conf file back to the /cisco-ar/ucd-snmp/share/snmp directory. Restart the Prime Access Registrar 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 Prime Access Registrar 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.

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

Step 1 Log in as admin and launch aregcmd.

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

cd /radius/replication

Make sure that RepType is set to None.

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

Step 4 Restart the server.