Upgrading Cisco IPICS

Transcription

1 CHAPTER3 If your Cisco IPICS server is running release 2.2(1)SR1, release 4.0(1), or release 4.0(2) you can upgrade your server to release 4.5(1). Tip To verify which versions of Cisco IPICS are compatible for upgrade, see Cisco IPICS Compatibility Matrix at ps6718/products_device_support_tables_list.html. This chapter contains information about upgrading your software to Cisco IPICS release 4.5(10 and other actions that you must take to fully complete this upgrade process and includes the following sections: Before You Begin, page 3-1, page 3-2 Using the Cisco Incident Dispatch Console with Cisco IPICS 4.5, page 3-16 Upgrading the Radio Descriptor, page 3-17 Before You Begin Be aware of the following guidelines, and perform one or more of the following suggested actions, before you upgrade your server software: Cisco recommends that you back up the database to a remote host. If you encounter problems during the upgrade, you can reinstall your current version of the Cisco IPICS software and restore your database from the remote 3-1

2 backup to return your system to its previous state. For information about backing up and restoring the Cisco IPICS database, refer to the Performing Cisco IPICS Backup and Restore Operations chapter in Cisco IPICS Server Administration Guide. You can set up a new version of the latest supported IDC so that the IDC download process is staged. Staging the IDC download alleviates the burden of long IDC downloads to all users at one time. For more information about this feature, refer to the Installing a New IDC Version Before You Upgrade Your Cisco IPICS Server section in the Performing Cisco IPICS System Administrator Tasks chapter in Cisco IPICS Server Administration Guide. Cisco IPICS retains existing attributes for channels, VTGs, and users during an upgrade. However, the default setting for the Allow Latch attribute is set to disabled (unchecked) when you create new channels or VTGs in this release. For more information about the Allow Latch attribute, refer to the Performing Cisco IPICS System Administrator Tasks chapter in Cisco IPICS Server Administration Guide. If you are upgrading from Cisco IPICS release 2.2(1)SR1, you will need a Cisco IPICS 4.5 license file. If you are upgrading Cisco IPICS 4.0(1) or 4.0(2), you will need a Cisco IPICS 4.5 license file if you upgrade to a different server or will implement new Cisco IPICS 4.5 features. Make sure to obtain the license file from Cisco or your Cisco partner. The following sections provide instructions for upgrading your Cisco IPICS software to release 4.5(1): Upgrading from Cisco IPICS Release 2.2(1)SR1, 4.0(1), or 4.0(2) in a Deployment without High Availability, page 3-3 Upgrading from Cisco IPICS release 4.0(1) or 4.0(2) on existing Servers in a Deployment with High Availability, page 3-6 Upgrading from Cisco IPICS release 4.0(1) or 4.0(2) and Migrating to New Servers in a Deployment with High Availability, page

3 Upgrading from Cisco IPICS Release 2.2(1)SR1, 4.0(1), or 4.0(2) in a Deployment without High Availability To upgrade from Cisco IPICS release 2.2(1)SR1, 4.0(1), or 4.0(2) to Cisco IPICS release 4.5(1) in a deployment without high availability, perform the following procedure. If your existing Cisco IPICS software is installed on a Cisco Multiservices Platform Series server, you can perform this upgrade on that server or migrate to a new Cisco Multiservices Platform Series server. If your existing Cisco IPICS software is installed on a MCS device, you must migrate to a supported Cisco Multiservices Platform Series server when you perform this upgrade. The following procedure provides instructions for each of these options. Procedure Step 1 Step 2 Step 3 From a client PC, take these actions to obtain the upgrade scripts and create an upgrade script disk (you must have a valid Cisco.com user ID and password before you can access this URL): a. Go to this URL: wid=7120 b. Click the Cisco IPICS Release 4.5 link. c. Click the Download button for ipics_upgrade_45_script.zip. d. Follow the onscreen instructions to download the upgrade script to your local drive. e. Unzip the zip file that you downloaded. The zip file contains three scripts. f. Copy each script to a CD or DVD. This disk is your upgrade script disk. Access the Cisco IPICS server via an SSH client or the Console window and log in as the Linux root user. Put the upgrade script disk in the disk drive and enter this command to mount it: [root]# mount /mnt/cdrom mount: block device /dev/hda is write-protected, mounting 3-3

4 Step 4 Step 5 Copy the script pre_ipics_db_upgrade_22_45 or pre_ipics_db_upgrade_40_45 on the upgrade script disk to the existing Cisco IPICS server under /root. Back up the existing Cisco IPICS database to a remote server by using the following command, where: backup_script_name is pre_ipics_db_upgrade_22_45 if you are upgrading from release 2.2(1)SR1, or pre_ipics_db_upgrade_40_45 if you are upgrading from release 4.0(1) or 4.0(2) remote_directory is the directory in which to save the database remote_host_ip is the IP address of the remote server root_password is the root password of that server Note You must save the file to a remote location because the file is deleted as part of the new operating system installation. Make sure that the directory in which to save the database exists and that it has sufficient space for the database. Do not save the file in the /tmp directory or in any directory under that directory. [root]#./backup_script_name remote_directory remote_host_ip root root_password The command saves the database backup to either of these files: dbspaces_ipics22.tgz If you are upgrading from release 2.2(1)SR1 dbspaces_ipics40.tgz If you are upgrading from release 4.0(1) or 4.0(2) For example, enter the following command, where rootpwd is the root password of the server (make sure to include the single quotes [ ]). In this example, the output is saved to the file dbspaces_ipics22.tgz. [root]#./pre_ipics_db_upgrade_22_45 /root root rootpwd Note The database backup process is different from the normal database backup that is available in the Cisco IPICS server. After you install Cisco IPICS release 4.5(1), the database backup file that you created is required to replicate your database in release 4.5(1). 3-4

5 Step 6 Step 7 Step 8 Step 9 Step 10 If your existing Cisco IPICS server is storing audio, image, and video files for use with the Cisco IPICS Dispatch Console, manually copy these files from the /documents folder on the Cisco IPICS server to a remote server. If the server that will run Cisco IPICS 4.5 is not running release 4.5 of the IPICS operating system, install that operating system as described in the Installing the IPICS Operating System on a Multiservices Platform Series Server section on page 2-7. If you installed release 4.5 of the IPICS operating system in Step 7, configure the server that you will use with IPICS 4.5(1) as described in the Configuring Server Parameters on the Multiservices Platform Series Server section on page Install Cisco IPICS 4.5(1) software as described in the Installing the Cisco IPICS Server Software section on page Take these actions to restore the Cisco IPICS database that you backed up earlier in this procedure: Note This process may take up to 30 minutes. Make sure that you allow time for the process to complete. a. Access the Cisco IPICS server on which you installed Cisco IPICS 4.5(1) via an SSH client or the Console window and log in as the Linux root user. b. Enter this command: [root]# cd /opt/cisco/ipics/database/bin c. Enter the following command, where: restore_script_name is ipics_db_upgrade_22_45 if you are upgrading from release 2.2(1)SR1, or ipics_db_upgrade_40_45 if you are upgrading from release 4.0(1) or 4.0(2) remote_directory is directory in which you backed up the database in Step 5 remote_host_ip is the IP address of the remote server to which you backed up the database root_password is the root password of remote server to which you backed up the database [root]#./restore_script_name remote_directory remote_host_ip root root password 3-5

6 Step 11 Step 12 As the restore operation executes, the system displays information about the process. When the restore operation completes, the Cisco IPICS server initializes. If you manually backed up audio, image, and video files in Step 6, take these actions: a. Manually copy these backed up files from the remote server to the /documents folder on the Cisco IPICS server. b. On the Cisco IPICS server, enter these commands to set required ownership and permissions for each audio, image, and video file: [root]# /bin/chown -R ipicsadmin:ipicsadmin /documents/* [root]# /bin/chmod -R 660 /documents/* Take these actions to upload the Cisco IPICS License file to the Cisco IPIC server: a. Use a Web browser to access the Cisco IPICS application and log in as the system administrator. The License Management page opens. b. From the License Management page, use the Browse button to locate the IPICS 4.5 Upgrade license file provided by Cisco, and choose that license file. The license file name appears in the License File field. c. Click the Upload button to copy the license file to the Cisco IPICS server. d. Click the Apply button to apply the license. Upgrading from Cisco IPICS release 4.0(1) or 4.0(2) on existing Servers in a Deployment with High Availability To upgrade from Cisco IPICS release 4.0(1) or 4.0(2) to Cisco IPICS release 4.5(1) on existing servers in a deployment with high availability, perform the following procedure. 3-6

7 Procedure Step 1 Step 2 Step 3 Take these actions to transfer the Cisco IPICS active state to the standby Cisco IPICS server: a. Log in to the Cisco IPICS Administration Console. b. Navigate to the Configuration > High Availability window. c. Click the HA Configuration tab. d. Click the Failover Now button. The standby server becomes the new active server and the active server becomes the standby server. From a client PC, take these actions to obtain the upgrade scripts and create an upgrade script disk (you must have a valid Cisco.com user ID and password before you can access this URL): a. Go to this URL: wid=7120 b. Click the Cisco IPICS Release 4.5 link. c. Click the Download button for ipics_upgrade_45_script.zip. d. Follow the onscreen instructions to download the upgrade script to your local drive. e. Unzip the zip file that you downloaded. The zip file contains three scripts. f. Copy each script to a CD or DVD. This disk is your upgrade script disk. Access the primary (now standby) Cisco IPICS server via an SSH client or the Console window and log in as the Linux root user. Note The primary server is now the standby server because you performed a failover earlier in this procedure. 3-7

8 Step 4 Put the upgrade script disk in the disk drive on the primary (standby) server and take these actions a. Enter this command to mount the disc: [root]# mount /mnt/cdrom mount: block device /dev/hda is write-protected, mounting b. Copy the pre_ipics_upgrade_40_45_disable_ha and the pre_ipics_db_upgrade_40_45 files on the upgrade script disk to the server under /root. c. Enter this command, which prevents the primary (standby) server from becoming active during the upgrade process: [root]#./pre_ipics_upgrade_40_45_disable_ha Step 5 Back up the existing Cisco IPICS database to a remote server by entering the following command primary (standby) server, where: remote_directory is the directory in which to save the database remote_host_ip is the IP address of the remote server root_password is the root password of that server Note You must save the file to a remote location because the file is deleted as part of the new operating system installation. Make sure that the directory in which to save the database exists and that it has sufficient space for the database. Do not save the file in the /tmp directory or in any directory under that directory. [root]#./pre_ipics_db_upgrade_40_45 remote_directory remote_host_ip root root_password The command saves the database backup to the file dbspaces_ipics40.tgz. For example, enter the following command, where rootpwd is the root password of the server (make sure to include the single quotes [ ]). In this example, the output is saved to the file dbspaces_ipics40.tgz. [root]#./pre_ipics_db_upgrade_40_45 /root root rootpwd 3-8

9 Note The database backup process is different from the normal database backup that is available in the Cisco IPICS server. After you install Cisco IPICS release 4.5(1), the database backup file that you created is required to replicate your database in release 4.5(1). Step 6 Step 7 Take these actions on the primary (standby) server: a. If the server is storing audio, image, and video files for use with the Cisco IPICS Dispatch Console, manually copy these files from the /documents folder on the Cisco IPICS server to a remote server. b. If the server is not running release 4.5 of the IPICS operating system, install that operating system as described in the Installing the IPICS Operating System on a Multiservices Platform Series Server section on page 2-7. c. If you installed release 4.5 of the IPICS operating system, configure the server as described in the Configuring Server Parameters on the Multiservices Platform Series Server section on page Set the IP address of this server to the same address that was used before you installed the operating system. d. Install Cisco IPICS 4.5(1) software on the server described in the Installing the Cisco IPICS Server Software section on page Take these actions to restore the Cisco IPICS database that you backed up earlier: Note This process may take up to 30 minutes. Make sure that you allow time for the process to complete. a. Access the server on which you installed the Cisco IPICS 4.5(1) software via an SSH client or the Console window and log in as the Linux root user. b. Enter this command: [root]# cd /opt/cisco/ipics/database/bin c. Enter the following command, where: remote_directory is directory in which you backed up the database in Step 5. remote_host_ip is the IP address of the remote server to which you backed up the database 3-9

10 root_password is the root password of remote server to which you backed up the database [root]#./ipics_db_upgrade_40_45 remote_directory remote_host_ip root root password Step 8 Step 9 Step 10 As the restore operation executes, the system displays information about the process. When the restore operation completes, the Cisco IPICS server initializes. If you manually backed up audio, image, and video files in Step 6, take these actions: a. Manually copy these backed up files from the remote server to the /documents folder on the server on which you installed the Cisco IPICS 4.5(1) software. b. On the server on which you installed the Cisco IPICS 4.5(1) software, enter these commands to set required ownership and permissions for each audio, image, and video file: [root]# /bin/chown -R ipicsadmin:ipicsadmin /documents/* [root]# /bin/chmod -R 660 /documents/* (Optional) If you will implement new Cisco IPICS 4.5 features, take the following actions to upload the Cisco IPICS License file to the server on which you installed the Cisco IPICS 4.5(1) software (this server will be the primary server when you reestablish HA): a. Use a Web browser to access the Cisco IPICS application and log in as the system administrator. The License Management page opens. b. From the License Management page, use the Browse button to locate the IPICS 4.5 Upgrade license file provided by Cisco, and choose that license file. Make sure to choose the appropriate license file for the primary server. The license file name appears in the License File field. c. Click the Upload button to copy the license file to the Cisco IPICS server. d. Click the Apply button to apply the license. Take these actions on the secondary (active) server: a. If the server is not running release 4.5 of the IPICS operating system, install that operating system as described in the Installing the IPICS Operating System on a Multiservices Platform Series Server section on page

11 Step 11 b. If you installed release 4.5 of the IPICS operating system, configure the server as described in the Configuring Server Parameters on the Multiservices Platform Series Server section on page Set the IP address of this server to the same address that was used before you installed the operating system. c. Install Cisco IPICS 4.5(1) software on the server described in the Installing the Cisco IPICS Server Software section on page d. Use a Web browser to access the Cisco IPICS application and log in as the system administrator. The License Management page opens. e. From the License Management page, use the Browse button to locate the IPICS 4.5 Upgrade license file provided by Cisco, and choose that license file. Make sure to choose the appropriate license file for the secondary server. The license file name appears in the License File field. f. Click the Upload button to copy the license file to the Cisco IPICS server. g. Click the Apply button to apply the license. Take these actions to configure the two servers on which you installed Cisco IPICS 4.5(1) as an HA pair. a. Use a Web browser to access the Cisco IPICS application on the server that is to be the primary Cisco IPICS server and log in as the system administrator b. Navigate to the Configuration > High Availability window. c. In the IP Address field, enter the IP address of the server that is to be the secondary Cisco IPICS server. d. In the User Password password field, enter the password of the Cisco IPICS administrator. e. Click Save. Do not configure options in the HA Configuration tab. You will perform additional configuration by using a script. f. Access the server that is to be the primary Cisco IPICS server via an SSH client or the Console window and log in as the Linux root user. g. Enter this command: [root]# cd /opt/cisco/ipics/database/bin 3-11

12 h. Enter this command: [root]#./post_ipics_upgrade_40_45_enable_ha For related information about high availability, see the Configuring and Managing Cisco IPICS High Availability section in Cisco IPICS Server Administration Guide. Upgrading from Cisco IPICS release 4.0(1) or 4.0(2) and Migrating to New Servers in a Deployment with High Availability To upgrade from Cisco IPICS release 4.0(1) or 4.0(2) to Cisco IPICS release 4.5(1) and to migrate to new servers in a deployment with high availability, perform the following procedure: Procedure Step 1 Step 2 From a client PC, take these actions to obtain the upgrade scripts and create an upgrade script disk (you must have a valid Cisco.com user ID and password before you can access this URL): a. Go to this URL: wid=7120 b. Click the Cisco IPICS Release 4.5 link. c. Click the Download button for ipics_upgrade_45_script.zip. d. Follow the onscreen instructions to download the upgrade script to your local drive. e. Unzip the zip file that you downloaded. The zip file contains three scripts. f. Copy each script to a CD or DVD. This disk is your upgrade script disk. Access the primary Cisco IPICS server via an SSH client or the Console window and log in as the Linux root user. 3-12

13 Step 3 Step 4 Step 5 Put the upgrade script disk in the disk drive and enter this command to mount it: [root]# mount /mnt/cdrom mount: block device /dev/hda is write-protected, mounting Copy the script pre_ipics_db_upgrade_40_45 on the upgrade script disk to the existing primary Cisco IPICS server under /root. Back up the existing Cisco IPICS database to a remote server by using the following command, where: remote_directory is the directory in which to save the database remote_host_ip is the IP address of the remote server root_password is the root password of that server Note You must save the file to a remote location because the file is deleted as part of the new operating system installation. Make sure that the directory in which to save the database exists and that it has sufficient space for the database. Do not save the file in the /tmp directory or in any directory under that directory. [root]#./pre_ipics_db_upgrade_40_45 remote_directory remote_host_ip root root_password The command saves the database backup to the file dbspaces_ipics40.tgz. For example, enter the following command, where rootpwd is the root password of the server (make sure to include the single quotes [ ]). In this example, the output is saved to the file dbspaces_ipics40.tgz. [root]#./pre_ipics_db_upgrade_40_45 /root root rootpwd Note The database backup process is different from the normal database backup that is available in the Cisco IPICS server. After you install Cisco IPICS release 4.5(1), the database backup file that you created is required to replicate your database in release 4.5(1). Step 6 If your existing primary Cisco IPICS server is storing audio, image, and video files for use with the Cisco IPICS Dispatch Console, manually copy these files from the /documents folder on the Cisco IPICS server to a remote server. 3-13

14 Step 7 Step 8 Step 9 Configure each new server that you will use with IPICS 4.5(1) as described in the Configuring Server Parameters on the Multiservices Platform Series Server section on page To minimize Cisco IPICS downtime, Cisco recommends that you configure the new servers with IP addresses that are different from those that are configured for the existing servers. If you want to configure the new servers with the same IP addresses as those that are configured for the existing servers, power off the existing servers or remove them from the network before you configure the new servers. Install Cisco IPICS 4.5(1) software on each new server as described in the Installing the Cisco IPICS Server Software section on page Take these actions to restore the Cisco IPICS database that you backed up earlier in this procedure to the new server that will be the primary Cisco IPICS server: Note This process may take up to 30 minutes. Make sure that you allow time for the process to complete. a. Access the new Primary Cisco IPICS server via an SSH client or the Console window and log in as the Linux root user. b. Enter this command: [root]# cd /opt/cisco/ipics/database/bin c. Enter the following command, where: remote_directory is directory in which you backed up the database in Step 5 remote_host_ip is the IP address of the remote server to which you backed up the database root_password is the root password of remote server to which you backed up the database [root]#./ipics_db_upgrade_40_45 remote_directory remote_host_ip root root password As the restore operation executes, the system displays information about the process. When the restore operation completes, the Cisco IPICS server initializes. 3-14

15 Step 10 Step 11 Step 12 If you manually backed up audio, image, and video files in Step 6, take these actions: a. Manually copy these backed up files from the remote server to the /documents folder on the primary Cisco IPICS server. b. On the primary Cisco IPICS server, enter these commands to set required ownership and permissions for each audio, image, and video file: [root]# /bin/chown -R ipicsadmin:ipicsadmin /documents/* [root]# /bin/chmod -R 660 /documents/* Take these actions to upload the Cisco IPICS License file to the primary Cisco IPICS server: a. Use a Web browser to access the Cisco IPICS application on the primary Cisco IPICS server and log in as the system administrator. The License Management page opens. b. From the License Management page, use the Browse button to locate the IPICS 4.5 Upgrade license file provided by Cisco, and choose that license file. Make sure to choose the appropriate license file for the primary server. The license file name appears in the License File field. c. Click the Upload button to copy the license file to the Cisco IPICS server. d. Click the Apply button to apply the license. Take these actions to upload the Cisco IPICS License file to the secondary Cisco IPICS server: a. Use a Web browser to access the Cisco IPICS application on the secondary Cisco IPICS server and log in as the system administrator. The License Management page opens. b. From the License Management page, use the Browse button to locate the IPICS 4.5 Upgrade license file provided by Cisco, and choose that license file. Make sure to choose the appropriate license file for the secondary server. The license file name appears in the License File field. c. Click the Upload button to copy the license file to the Cisco IPICS server. d. Click the Apply button to apply the license. 3-15

16 Using the Cisco Incident Dispatch Console with Cisco IPICS 4.5 Step 13 Configure the two new servers as an HA pair. For instructions, see the Configuring and Managing Cisco IPICS High Availability section in Cisco IPICS Server Administration Guide. Using the Cisco Incident Dispatch Console with Cisco IPICS 4.5 After you upgrade to Cisco IPICS 4.5(1), take these actions to enable Cisco IPICS Dispatch Console users to access Cisco IPICS from their client PCs: 1. Generate a new IDC installer as described in the Generating the IDC Installer section in Cisco IPICS Server Administration Guide. 2. (Recommended) Instruct Cisco IPICS Dispatch Console users to install the current version of the Cisco IPICS Dispatch Console on their client PCs. For instructions, see the Cisco IPICS Dispatch Console Installation, Configuration, and Maintenance chapter in Cisco IPICS Dispatch Console User Guide. 3. Instruct Cisco IPICS Dispatch Console users to install the current version of the Cisco IPICS Dispatch Console on their client PCs. For instructions, see the Cisco IPICS Dispatch Console Installation, Configuration, and Maintenance chapter in Cisco IPICS Dispatch Console User Guide. 3-16

17 Upgrading the Radio Descriptor Upgrading the Radio Descriptor After upgrading a 2.2(1)SR1 system to 4.5(1), you must upgrade all existing EF Johnson radio descriptors that have control functions defined by performing the following steps: Procedure Step 1 Step 2 Step 3 Open the EF Johnson descriptor in an editor and locate the block for control functions. The block is bounded by the following tags: <ControlFunctions> </ControlFunctions> Make a note of the control functions that are in the list and then delete the block. Copy and paste the following control functions block into the descriptor. <ControlFunctions> <Stateful shortname="mon" longname="monitor" description="set Monito r Mode" presentation="multiple"> <State shortname="on" longname="on" description="monitor mode is o n" user_selectable="true"> <SetMonitorMode value="on" /> <State shortname="off" longname="off" description="monitor mode is off" user_selectable="true"> <SetMonitorMode value="off" /> <State shortname="unkwn" longname="unknown" description="monitor m ode is in an unknown state" user_selectable="false"> <SetMonitorMode value="unknown" /> <State shortname="unsprt" longname="unsupported" description="moni tor mode is not supported" user_selectable="false"> 3-17

18 Upgrading the Radio Descriptor <SetMonitorMode value="unsupported" /> </Stateful> <Stateful shortname="rta" longname="repeater/talkaround" description ="Select Between Repeater and Talkaround Transmit Modes" presentation= "multiple"> <State shortname="rptr" longname="repeater" description="transmit mode is set to REPEATER" user_selectable="true"> <SetRepeaterTaMode value="repeater" /> <State shortname="ta" longname="talkaround" description="transmit mode is set to TALKAROUND" user_selectable="true"> <SetRepeaterTaMode value="talkaround" /> <State shortname="unkwn" longname="unknown" description="repeater/ Talkaround mode is in an unknown state" user_selectable="false"> <SetRepeaterTaMode value="unknown" /> <State shortname="unsprt" longname="unsupported" description="repe ater/ta mode selection is not supported" user_selectable="false"> <SetRepeaterTaMode value="unsupported" /> </Stateful> <Stateful shortname="scn" longname="scan" description="set Scan Mode " presentation="multiple"> 3-18

19 Upgrading the Radio Descriptor <Stateful shortname="on" longname="on" description="scan is on" us er_selectable="true"> <SetScanMode value="on" /> <Stateful shortname="off" longname="off" description="scan is off" user_selectable="true"> <SetScanMode value="off" /> <Stateful shortname="unkwn" longname="unknown" description="scan i s in an unknown state" user_selectable="false"> <SetScanMode value="unknown" /> <Stateful shortname="unsprt" longname="unsupported" description="s can is not supported" user_selectable="false"> <SetScanMode value="unsupported" /> </Stateful> <Stateful shortname="sec" longname="secure Tx Mode" description="sel ect Between Secure and Clear Transmit Modes" presentation="multiple"> <Stateful shortname="sec" longname="secure" description="secure tr ansmit mode is set to SECURE" user_selectable="true"> <SetSecureTxMode value="secure" /> <Stateful shortname="clr" longname="clear" description="secure tra nsmit mode is set to CLEAR" user_selectable="true"> 3-19

20 Upgrading the Radio Descriptor <SetSecureTxMode value="clear" /> <Stateful shortname="keyfl" longname="keyfail" description="keyfai l. Key required for encryption is not present" user_selectable="false" > <SetSecureTxMode value="keyfail" /> <Stateful shortname="noenc" longname="no_encrypt" description="no encryption module present" user_selectable="false"> <SetSecureTxMode value="no_encrypt" /> <Stateful shortname="msmtch" longname="mismatch" description="mism atch between user selected secure transmit mode and actual fixed/strap ped tx mode" user_selectable="false"> <SetSecureTxMode value="mismatch" /> <Stateful shortname="unkwn" longname="unknown" description="secure /Clear Transmit mode is in an unknown state" user_selectable="false"> <SetSecureTxMode value="unknown" /> <Stateful shortname="unsprt" longname="unsupported" description="e ncryption is not supported" user_selectable="false"> <SetSecureTxMode value="unsupported" /> </Stateful> 3-20

21 Upgrading the Radio Descriptor <Stateful shortname="pwr" longname="transmit Power Mode" description ="Change the transmit power level" presentation="multiple"> <Stateful shortname="high" longname="high" description="transmit p ower mode is set to HIGH" user_selectable="true"> <SetTxPowerMode value="high" /> <Stateful shortname="low" longname="low" description="transmit pow er mode is set to LOW" user_selectable="true"> <SetTxPowerMode value="low" /> <Stateful shortname="unkwn" longname="unknown" description="transm it power mode is in an unknown state" user_selectable="false"> <SetTxPowerMode value="unknown" /> <Stateful shortname="unsprt" longname="unsupported" description="t ransmit power mode selection is not supported" user_selectable="false" > <SetTxPowerMode value="unsupported" /> </Stateful> <Stateful shortname="emg" longname="emergency" description="enable/d isable Emergency Mode" presentation="multiple"> <Stateful shortname="on" longname="on" description="emergency mode is on" user_selectable="true"> <SetEmergencyMode value="on" /> 3-21

22 Upgrading the Radio Descriptor <Stateful shortname="off" longname="off" description="emergency mo de is off" user_selectable="true"> <SetEmergencyMode value="off" /> <Stateful shortname="unkwn" longname="unknown" description="emerge ncy mode is in an unknown state" user_selectable="false"> <SetEmergencyMode value="unknown" /> <Stateful shortname="unsprt" longname="unsupported" description="e mergency mode is not supported" user_selectable="false"> <SetEmergencyMode value="unsupported" /> </Stateful> </ControlFunctions> Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Each control function is bounded by a <Stateful> </Stateful> block. Refer to the original list of control functions to determine which functions are not needed, and then remove them from the newly pasted control functions block. Save the descriptor file. In the IPICS Server console, choose Configuration > Descriptors. Choose the modified descriptor and click Update. Choose the descriptor type and click Browse to locate and upload the file. Click Save. To ensure that all affected radios are updated with the new descriptor information, disable and then enable each radio, or restart the RCS service on the server. To restart the service, Access the Cisco IPICS server via an SSH client and log in as the Linux root user, then enter the following command: [root]# service ipics_rcs restart 3-22

23 Upgrading the Radio Descriptor Wait a few minutes before attempting to control any radio. 3-23

24 Upgrading the Radio Descriptor 3-24