Ipicsinstallguide

Cisco IPICS Server Installation and Upgrade Guide
Release 4.0(1)
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
Text Part Number: OL-21842-01
TTHE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco IPICS Server Installation and Upgrade Guide, Release 4.0(1) Copyright 2010 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface 7 Introduction 7 Audience 7 Organization 8 Document Notes and Conventions 8 Obtaining Documentation, Obtaining Support, and Security Guidelines 10
1
CHAPTER
Overview 1 Installation Overview 1 Installed Components 4 System Requirements 4
CHAPTER
Installing Cisco IPICS 1 Before You Begin 1 Obtaining the IP Addresses for Your Cisco IPICS System 2 Preinstallation Checklist 3 Installing the Cisco IPICS Operating System 7 Reinstalling the IPICS Operating System on the Multiservices Platform 11 Configuring Server Parameters on the Multiservices Platform 13 Installing the Cisco IPICS Server Software 16 Performing a Direct Cisco IPICS Server Software Installation 16 Performing a Remote Cisco IPICS Server Software Installation 21 Restarting or Shutting Down the Server 25
OL-21842-01
Contents
Preparing to Use Cisco IPICS 27 Checking the Installation 28 Managing Your Licenses and Certificates 29 Obtaining Your License File 30 Uploading the Cisco IPICS License Files 32 Viewing the License Summary Information 34 Tracking Your License Usage 35 Managing Time-Bound Licenses 37 Managing Server Certificates 40 Backing Up Server Certificates and Stores 40 Customizing and Generating a Self-Signed Server Certificate 41 Installing Third Party Certificates On the Cisco IPICS Server 43 Requesting a Third Party Certificate 44 Installing a Third Party Certificate 45 Converting DER Formatted Certificates to PEM Format 51 Modifying Network Settings 51
3
CHAPTER
Upgrading Cisco IPICS 1 Before You Begin 2 Performing a Direct Cisco IPICS Server Software Upgrade 2 Performing a Remote Cisco IPICS Server Software Upgrade 7 Upgrading the Radio Descriptor 12
CHAPTER
Uninstalling Cisco IPICS 1 Uninstalling the Cisco IPICS Server Software from the Server 2 Uninstalling the Cisco IPICS Server Software Remotely 3
OL-21842-01
Contents
CHAPTER
Troubleshooting Cisco IPICS Installation Issues 1 No Network Connectivity After Connecting the Ethernet Cable to Interface 1 on the Server 2 The Cisco IPICS Operating System Detects Unsupported Hardware 2 The Server Cannot Allocate Partitions 3 Troubleshooting Bad Interpreter: Permission Denied Errors 3 Troubleshooting Permission Denied Errors 4 SSH Loses Connectivity While You Perform a Remote Server Software Installation 5 You Cannot Connect to the Server By Using Your Browser 5 Cisco IPICS Displays an Authorization Error 11
GLOSSARY
INDEX
Cisco IPICS Server Installation and Upgrade Guide OL-21842-01
Contents
OL-21842-01
Preface
Introduction
This guide provides you with the information that you need to install the Cisco IP Interoperability and Collaboration System (hereafter referred to as Cisco IPICS) release software. System administrators should review the information in this document to learn how to prepare for the Cisco IPICS server software installation and recover from any errors that might occur during or after the installation.
Audience
This guide is designed for system administrators who install, configure, operate, and upgrade the Cisco IPICS operating system and the Cisco IPICS server software.
Preface Organization
Organization
This document is organized as follows: Chapter 1, Overview The introduction provides an overview of the Cisco IPICS software installation. This chapter also includes information about the system requirements for Cisco IPICS.
Chapter 2, Installing Cisco IPICS This chapter describes the steps that you need to follow to install the Cisco IPICS operating system and the Cisco IPICS server software and its components. Chapter 3, Upgrading Cisco IPICS Chapter 4, Uninstalling Cisco IPICS Chapter 5, Troubleshooting Cisco IPICS Installation Issues This chapter describes the steps that you need to follow to upgrade the Cisco IPICS server software. This chapter describes the steps that you follow to uninstall the Cisco IPICS server software. This chapter includes troubleshooting tips for server installation issues that you may encounter.
Document Notes and Conventions

This document uses the following conventions for instructions and information:
Note
Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.
Caution
This caution symbol means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
OL-21842-01
Preface Document Notes and Conventions
Table 1
Conventions
Convention boldface font italic font [ ]
Description Commands and keywords appear in boldface. Command input for which you supply the values appear in italics. Optional keywords and default responses to system prompts appear within square brackets. A choice of keywords (represented by x) appears in braces separated by vertical bars. You must select one. A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. Represent the key labeled Control. For example, when you read ^D or Ctrl-D, you should hold down the Control key while you press the D key. Examples of information displayed on the screen.
screen
{x | x | x}
string
^ or Ctrl
screen
font
boldface screen
font italic screen font
Information that you must enter is in boldface font. Arguments for which you supply values are in italic screen font.
Preface Obtaining Documentation, Obtaining Support, and Security Guidelines
Obtaining Documentation, Obtaining Support, and Security Guidelines

For information about obtaining documentation, submitting a service request, and gathering additional information, see the monthly Whats New in Cisco Product Documentation. This document also lists all new and revised Cisco technical documentation. It is available at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the Whats New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
10
OL-21842-01
CH A P T E R
Overview
This chapter provides an overview of the Cisco IPICS software installation. It also contains information about system requirements for the Cisco IPICS server software and the Cisco IPICS Dispatch Console (hereafter referred to as IDC) application. This chapter includes the following sections:

Installation Overview, page 1-1 Installed Components, page 1-4 System Requirements, page 1-4
Installation Overview
You can install the Cisco IPICS software on a supported Cisco Physical Security Multiservices Platform Series device or Cisco Media Convergence Server (MCS). The installation process includes the installation of the Cisco IPICS operating system and then the Cisco IPICS server software. All of the software that you need for Cisco IPICS is included in the installation package.
Note
For the latest information about supported platforms, see Cisco IPICS Compatibility Matrix at http://www.cisco.com/en/US/products/ps6718/products_device_support_tables_ list.html
1-1
Chapter 1 Installation Overview
Overview
You can perform the Cisco IPICS operating system software and Cisco IPICS server software installations in the same session, or you can install the operating system software in one session and then install the server software at a later time. The software that installs the Cisco IPICS operating system and Cisco IPICS server software is mostly automated, but it does require some user interaction to complete. Table 1-1 describes the steps that you need to perform to set up the installation of the Cisco IPICS operating system software.
Table 1-1 Cisco IPICS Operating System Setup
Step
1.
Description This procedure allows you to disable default features that may be incompatible with the Cisco IPICS operating system. This procedure overwrites the hard drive and installs files on the server. A progress window displays as the files are being installed. This procedure loads the operating system image in a process that is called firstboot. The Cisco IPICS operating system runs firstboot only once, just after the operating system is installed for the first time. You do not interact with the GRUB bootloader. This procedure allows you to set the password for the root user, who has access to all the commands and files in the Cisco IPICS server. This procedure allows you to set the IP addresses for the Ethernet interfaces, the Domain Name System (DNS) information, and the system date and time. This procedure allows you to log in to the Cisco IPICS server as the root user and check network connectivity. For more information about the steps that you need to follow to install the Cisco IPICS operating system software, see the Installing the Cisco IPICS Operating System section on page 2-7.
Cisco IPICS operating system setup utility Cisco IPICS operating system installation GRUB bootloader
2.
3.
4.
Password creation for the root user
5.
IP connectivity setup
6.
Root user login
1-2
OL-21842-01
Chapter 1
Overview Installation Overview
Table 1-2 describes the steps that you need to perform to set up the installation of the Cisco IPICS server software.
Table 1-2 Cisco IPICS Server Software Setup
Step
1.
Description This window displays the end user license agreement for the Cisco IPICS server software. You must accept this agreement to continue with the installation. This procedure permits you to create a password for the ipics user, who performs all administrative tasks in the Cisco IPICS Administration Console. This procedure enables you to create a password for the ipicsadmin user, who has the Cisco IPICS operating system privileges that are related to the database server files and folders. This window displays the progress of the installation and the Cisco IPICS files that the installer writes to the server. This installation also installs the Cisco IPICS policy engine (hereafter referred to as policy engine). This procedure creates a utility to uninstall the Cisco IPICS software. This procedure allows you to choose between restarting the server immediately or at a later time.
End user license agreement
2.
Password creation for the ipics user
3.
Password creation for the ipicsadmin user
4.
Package installation
5. 6.
Uninstaller creation Option to restart the server
For more information about the steps that you need to follow to install the Cisco IPICS server software, see the Installing the Cisco IPICS Server Software section on page 2-16.
1-3
Chapter 1 Installed Components
Overview
Installed Components
The Cisco IPICS installation includes the Cisco IPICS server software, with the following components:

Cisco IPICS Administration Console Cisco IPICS Data Store (IBM Informix Dynamic Server) Cisco IPICS Web Application Server (tomcat service) Cisco Security Agent (CSA)
System Requirements
Refer to the Cisco IPICS Compatibility Matrix for the list of hardware and software components that Cisco supports for use with Cisco IPICS.
1-4
OL-21842-01
CH A P T E R
Installing Cisco IPICS

This chapter describes the procedures that you need to follow to install the Cisco IPICS operating system and the Cisco IPICS server software. This chapter includes the following sections:

Before You Begin, page 2-1 Installing the Cisco IPICS Operating System, page 2-7 Reinstalling the IPICS Operating System on the Multiservices Platform, page 2-11 Configuring Server Parameters on the Multiservices Platform, page 2-13 Installing the Cisco IPICS Server Software, page 2-16 Restarting or Shutting Down the Server, page 2-25 Preparing to Use Cisco IPICS, page 2-27 Managing Server Certificates, page 2-40 Modifying Network Settings, page 2-51
Before You Begin

This section describes the activities that you must follow to prepare for the Cisco IPICS operating system and server installations and includes the following topics:

Obtaining the IP Addresses for Your Cisco IPICS System, page 2-2 Preinstallation Checklist, page 2-3
OL-21842-01
2-1
Chapter 2 Before You Begin
Obtaining the IP Addresses for Your Cisco IPICS System

To facilitate communications between your users, your Cisco IPICS system requires a pool of IP addresses that can be reached by all users in your network domain. The Cisco IPICS server requires a static, local IP address that is advertised on the network. Cisco IPICS end points, such as the IDC or Cisco Unified IP Phone, must have the static address of the Cisco IPICS server to maintain communications. Because Cisco IPICS converts analog push-to-talk (PTT) radio traffic to IP traffic, each radio channel gets mapped to an IP multicast address. Similarly, in hootnholler systems, each talk group gets mapped to an IP multicast address. Users on IP-connected devices, such as the IDC, can participate in these channels by connecting via a multicast IP address or by using a unicast remote connection through the Session Initiation Protocol (SIP). Cisco IPICS requires a multicast address for each of the following activities:

Creating a PTT channel Creating a talk group in a hootnholler system Activating a virtual talk group (VTG) Connecting a dial user into a channel or VTG
For ease of allocating IP addresses, it is helpful to obtain a subnet of IP addresses from which you can configure the devices that are part of that subnet. Cisco IPICS also requires an IP address for the loopback interface for the router media service (RMS). A loopback interface consists of two T1/E1 interfaces on the RMS that are connected by a short cable called a loopback cable. A loopback interface is used for voice signaling and media for any SIP-based connections with Cisco IPICS.
Note
Cisco recommends that you specifically configure the Loopback0 interface when there is more than one IP path to the RMS. However, you may configure an interface other than Loopback0 if specific criteria are met. For details about this criteria, refer to the Configuring the Cisco IPICS RMS Component appendix in the Cisco IPICS Server Administration Guide.
2-2
OL-21842-01
Chapter 2
Installing Cisco IPICS Before You Begin
Consult your network administrator to obtain IP addresses for the Cisco IPICS system, channels, VTGs, and the RMS. For information about configuring and using IP addresses with Cisco IPICS, and for more information about the RMS, refer to the Configuring the Cisco IPICS RMS Component appendix in the Cisco IPICS Server Administration Guide.
Preinstallation Checklist
Before you begin the installation, make sure that you perform the following tasks: Preinstallation Tasks Check that you have both CDs from the Cisco IPICS installation package. (Multiservices Platforms) Attach the power cable, monitor, keyboard, and mouse. Check that the power cords on your server and monitor are securely attached and plugged in to a power source. Attach an Ethernet network cable to the Ethernet 0 (eth0) port on your server.
Note
Checkoff
You must connect your network cable to the eth0 interface on your server. Generally, for servers that label their Ethernet interfaces as NIC 1 and NIC 2, connect the Ethernet cable to the NIC 1 interface; this interface is usually the eth0 interface. For servers that label their Ethernet interfaces as 1 and 2, consult the product documentation that you received with your server to determine how the server labels its interfaces. In all cases, it is a good practice to verify the location of the eth0 interface on your specific server before you proceed.
Make sure that you have at least 160 GB of hard disk space available in your Cisco IPICS server. Cisco strongly recommends that you attach an uninterruptible power supply (UPS) to your system and ensure that the UPS is operating correctly.
2-3
Preinstallation Tasks (continued) Check that your monitor cable connector is appropriate for the connector on the server. Video Graphics Array (VGA) analog and VGA digital are common connector types but are not compatible with each other without the proper adapter. Before you begin the installation process, check the power settings on your monitor to make sure that the display is not configured with any timeout values.
Note
Checkoff
If your display times out while you are performing the installation and you can no longer see the progress on your monitor, move your mouse to restore the display. Make sure that you do not press any keys on the keyboard in an effort to restore your display. Pressing keys without being able to view the information that displays on your monitor can cause undesirable results.
Ensure that you have obtained the IP address, subnet mask, default gateway, and DNS server (optional) information for the Cisco IPICS server from your network administrator. Check that you have obtained the Media Access Control (MAC) address for the eth0 interface of the Cisco IPICS server. Cisco IPICS uses the MAC address of the server to validate the Cisco IPICS license. For information about how to obtain the MAC address, see Step 24 in the Installing the Cisco IPICS Operating System section on page 2-7.
Note
In a system with multiple network interface cards (NICs), Cisco IPICS always uses the eth0 MAC address to validate the license, even if eth0 is disabled.
2-4
OL-21842-01
Chapter 2
Installing Cisco IPICS Before You Begin
Preinstallation Tasks (continued) If your network uses the Network Time Protocol (NTP), obtain the IP address or DNS name of the NTP server.
Note
Checkoff
You can configure NTP when you install the Cisco IPICS operating system software, or you can configure NTP after you install the Cisco IPICS software by using the ntpsetup command. For information about the ntpsetup command, refer to the Configuring NTP on the Cisco IPICS Server with the ntpsetup Tool section in the Using the Cisco IPICS CLI Tools and Service Commands chapter in the Cisco IPICS Troubleshooting Guide.
You can install a third party certificate to replace the Cisco IPICS self-signed certificate. For more information about installing third party certificates, see the Installing Third Party Certificates On the Cisco IPICS Server section on page 2-43. A third-party certificate is not required for use with Cisco IPICS. To ensure the functionality of Cisco IPICS, you should also perform the following tasks either before or after you install Cisco IPICS: Tasks Ensure that you have obtained multicast IP addresses for channels and VTGs. (If you do not have access to this information, contact your system administrator.) Check to make sure that the T1/E1 interfaces on the RMS are connected via a loopback cable. This cable is a short-length crossover cable with the following pinouts: 1-4, 2-5, 4-1, 5-2. One end of the cable is attached to each of the RJ-45 connectors on the T1/E1 interfaces for the RMS device. The connected interfaces are used for voice signaling and media for any SIP-based connections with Cisco IPICS. If you do not have a crossover cable, contact your authorized Cisco support representative for assistance to obtain one. Ensure that you have obtained an address for the RMS interfaces that are connected by a loopback cable. (If you do not have access to this information, contact your system administrator.) Checkoff
2-5
If you use the Cisco IPICS dial engine, which controls dial-in and dial-out functionality, ensure that you complete the following tasks before you use the dial engine: Tasks Ensure that you have the IP address, SIP listening port, and preferred transport type of your SIP provider. Support for SIP-based dial functionality is provided via Cisco Unified Communications Manager or a Cisco router that runs a supported version of Cisco IOS and Cisco Unified Communications Manager Express as the SIP provider. The policy engine requires that a SIP provider be configured in the customer network. For information about configuring a SIP provider, refer to the Cisco IPICS Server Administration Guide. If your SIP provider is Cisco Unified Communications Manager, determine the authentication credentials that Cisco IPICS uses when it initiates a call into Cisco Unified Communications Manager. Authentication is not required with Cisco Unified Communications Manager Express. Be sure that your SIP provider uses a supported version of Cisco Unified Communications Manager, Cisco IOS, and/or Cisco Unified Communications Manager Express. Refer to the Cisco IPICS Compatibility Matrix for the most updated list of supported hardware and software for use with Cisco IPICS. Determine how your Cisco IPICS system fits into the dial plan of your SIP provider. For example, determine the range of directory numbers (DNs) that must be routed from the SIP provider to the Cisco IPICS system. Checkoff
2-6
OL-21842-01
Chapter 2
Installing Cisco IPICS Installing the Cisco IPICS Operating System
Installing the Cisco IPICS Operating System

Follow the instructions in this section if you are installing Cisco IPICS on the Cisco Media Convergence Server (MCS). If you are installing Cisco IPICS on the Multiservices Platform, see the Configuring Server Parameters on the Multiservices Platform section on page 2-13. To install the Cisco IPICS operating system software on the MCS, follow these steps:
Procedure
Step 1 Step 2
Turn the server on by pushing the power button that is located on the front panel of the server. Insert the Cisco IPICS operating system installation CD into the server disk drive. The server begins to boot from the CD. When the system beeps, allow it to continue to boot from the CD. The Cisco IPICS operating system installation displays the CD version of the Cisco IPICS operating system and the option to overwrite the hard drive.
Step 3
To overwrite the hard drive and install the Cisco IPICS operating system files, follow these steps:
a.
When the system prompts you to overwrite the hard drive, enter Y and press Enter. The Cisco IPICS operating system Installation Progress window shows the progress of the installation. The operating system installer formats the file system and installs the software packages. When the process is complete, the server ejects the installation CD and opens the Installation Complete window.
Note
Do not press any keys, including the SysRq key, during the installation. Pressing the SysRq key causes a kernel panic condition on your server, which requires a hard reboot to fix.
Note
After the package installation is completed, the window may appear unresponsive or the screen may become blank. Wait while the system completes the background security processes.
2-7
Chapter 2 Installing the Cisco IPICS Operating System
b.
Remove the CD from the drive. Keep the installation CD in a safe location in the event that you need to reinstall the operating system.
c.
To view the technical information that relates to this release of the Cisco IPICS operating system, click Release Notes or press Alt+R. If your mouse begins to move erratically across your display, it may be due to the operating system loading an incorrect driver for your mouse. If you encounter this situation and it affects your ability to navigate with your mouse, use keyboard shortcuts to perform step c through Step e. Although the status window indicates that the installation is complete, you must complete several more tasks before you can install the Cisco IPICS server software. Make sure that you perform the remaining steps in this procedure to complete the Cisco IPICS operating system configuration.
d. e.
Click X or press Alt+C to close the window for the Release Notes. Click Exit or press Alt+E to close the window and reboot the server. During the bootup process, a GRUB window appears with the Cisco IPICS software installation highlighted.
Step 4
Press Enter to continue with the boot process. Alternatively, you can take no action when the GRUB window appears, and let the window time out. The system displays the Welcome window. At the Welcome window, click Next to display the Root Password window. Enter and confirm a password for the root user. The root user has access to all the files in the Cisco IPICS server. Cisco IPICS requires that you use strong passwords that include the following elements:

Step 5 Step 6
Minimum of 8 characters in length At least one upper case letter At least one upper case letter At least one number At least one of the following special characters: @[]^_`!"#$%&'()*+,-./:;{<|=}>~?
If you need to change the root password at a later date, you can log in to the Cisco IPICS server as the root user and change it by using the reset_pw command. For more information, refer to the Using the Cisco IPICS CLI Tools and Service Commands chapter in the Cisco IPICS Troubleshooting Guide.
2-8
OL-21842-01
Chapter 2
Installing Cisco IPICS Installing the Cisco IPICS Operating System
Step 7 Step 8
Click Next. Enter and confirm a password for the GRUB (boot loader) menu. The boot loader password enables access to the boot loader menu, which allows a system administrator to boot the server into single-user mode. Single-user mode is required to recover a lost root password. This password must contain at least 6 characters. Click Next. Enter a system user name and user full name, and enter and confirm a password. You must create a system user to perform administrative tasks on your server. This user password has the same requirements as the root password.
Step 9 Step 10
Step 11 Step 12 Step 13 Step 14 Step 15
Click Next to open the Network Setup window. In the Interface Settings area, enter the fully-qualified hostname, IP address, subnet mask, and gateway information in the specified fields. (Optional) In the DNS Information area in the Network Setup window, enter the IP address of your primary and secondary DNS server. Click Next to open the Timezone window. Choose the correct time zone for your area from the choices in the selection list. If your system clock uses Universal Coordinated Time (UTC), make sure that you check the System Clock uses UTC check box.
Step 16 Step 17
Click Next to open the Date and Time window. Choose one of the following options to set the system date and time:
If your network uses the Network Time Protocol (NTP), choose the Network Time Protocol tab and check the Enable Network Time Protocol check box. Enter the name or IP address of an NTP server in the Server field, and click Add. Repeat to add additional servers. To delete a server, choose the server, and click Delete. If you configure NTP on the server, your system administrator should provide instructions to the IDC users to also configure the Windows Time Service on their IDC client machines to enable synchronization between the IDC and the server logs. For detailed information about how to configure the Windows Time Service, refer to the Microsoft support site at http://support.microsoft.com/ and search for Article ID 307897.
2-9
Chapter 2 Installing the Cisco IPICS Operating System
If you install a time-bound license for your system, use caution when enabling NTP. Adjustments to the system date can cause Cisco IPICS to invalidate your license. For more information, see the Managing Time-Bound Licenses section on page 2-37.
Step 18 Step 19
If your network does not use NTP, choose the Date & Time tab and enter the current date and time in the appropriate fields.
Click Next to open the Finish Setup window. Click Next. The system processes an internal check list as it boots up. After the system has booted up, Cisco IPICS displays the following text:
Cisco IPICS hostname login:
where hostname represents the host name that you specified in step 12.
Step 20 Step 21 Step 22
Enter root in the hostname login field and press Enter. Enter the password that you created for the root user in step 6 and press Enter. To verify network connectivity, enter the following command:
[root]# ping destination-ip-address
where destination-ip-address represents the default gateway address or an IP address of another host on the network.
Step 23
Press Ctrl+C to stop the ping command. If the ping command is not successful, troubleshoot the network connectivity with your network administrator.
Step 24
Locate the hardware MAC address for the eth0 interface by following these steps:
a.
Enter the following command:

[root]# ifconfig eth0
The HWaddr field in the command output contains the MAC address for the eth0 interface. Make a note of the MAC address information for the eth0 interface so you can use it to obtain your license for Cisco IPICS.
b.
To log out of the server, enter the following command:

[root]# exit
2-10
OL-21842-01
Chapter 2
Installing Cisco IPICS Reinstalling the IPICS Operating System on the Multiservices Platform
The Cisco IPICS operating system installation is now complete, and you can continue with the installation of the Cisco IPICS server software. If you do not want to install Cisco IPICS immediately, you can resume the installation at a later time. To install the Cisco IPICS server software, see the Installing the Cisco IPICS Server Software section on page 2-16.
Reinstalling the IPICS Operating System on the Multiservices Platform

If you are installing Cisco IPICS on the Multiservices Platform, the Cisco IPICS operating system is already installed. Follow the instructions in this section if you need to reinstall the IPICS operating system for any reason. Before you begin, insert the hard drives into the drive bays, if necessary. MSP-1RU: Insert the drives from left to right. The drive numbering is as follows (looking at the front of the server): 1--2--3--4 MSP-2RU: Insert the drives from left to right. The drive numbering is as follows (looking at the front of the server): 3--6--9--12 2--5--8--11 1--4--7--10
Note
If you have issues with RAID after following the procedure in this section, reset the BIOS/RAID settings back to the factory defaults, and verify that the disk drives are in the correct bays.
2-11
Chapter 2 Reinstalling the IPICS Operating System on the Multiservices Platform
To reinstall the IPICS operating system on the Multiservices Platform, follow these steps:
Procedure
Step 1
(MSP-2RU only) Attach an external USB DVD player to the lower USB port on the back of the Multiservices Platform. Cisco has tested the Memorex MRX-530LE and Memorex 3202-3288 external USB DVD models; other DVD players may or may not work.
Step 2 Step 3
Power on the server and insert the IPICS 4.0 operating system DVD into the DVD player (internal player for the MSP-1RU or external player for the MSP-2RU). The server boots from the inserted DVD and begins the operating system installation. The installer configures RAID and reboots. Leave the DVD inserted and allow the server to complete the installation. If you see a prompt to select a driver during the operating system reinstallation, it may mean that the DVD player is not compatible. If you see a prompt to choose a language, power off the DVD player, power it back on, and then reboot the server to try the install again.
Step 4
When the installation finishes, the DVD is ejected and the server reboots.
Note
Some DVD players may pull the DVD drawer back into the player during the reboot process. If the DVD is not removed at this point, the server boots from the DVD again and attempts to reinstall the operating system. The installer will detect the previous operating system installation and prompt to continue (y/n). Answer n and restart the server without the DVD inserted.
Step 5
When the login prompt appears, follow the instructions in the Configuring Server Parameters on the Multiservices Platform section on page 2-13.
2-12
OL-21842-01
Chapter 2
Installing Cisco IPICS Configuring Server Parameters on the Multiservices Platform
Configuring Server Parameters on the Multiservices Platform

If you are installing Cisco IPICS on the Multiservices Platform, the Cisco IPICS operating system is already installed; however, you must configure server parameters, including hostname, IP address, gateway, netmask, and root password. The default IP address is: 192.168.1.2. If you need to reinstall the operating system for any reason, follow the instructions in the Reinstalling the IPICS Operating System on the Multiservices Platform section on page 2-11. To configure server parameters on the Cisco IPICS server, if the server is installed on the Multiservices Platform, follow these steps:
Procedure
Step 1 Step 2
Log in to the server as root with the default password ipics, and go to the /usr/local/bin directory. Execute the reconfigure command:
[root]# reconfigure
Step 3
Enter yes to the prompt that asks whether you want to reboot the server:
**** Reconfigure Server ****
To reconfigure this server from the default to custom values, the server must reboot. If you continue, when the server boots up, you will be presented with the firstboot screen and be required to enter the server networking information, date and time, optionally the NTP server information, and also the root and GRUB passwords. Responding "yes" to the prompt below will reboot this server. Do you want to reboot your server now? (yes/no) : [no] yes
Step 4
At the Welcome window, click Next to display the Root Password window.
2-13
Chapter 2 Configuring Server Parameters on the Multiservices Platform
Step 5
Enter and confirm a password for the root user. The root user has access to all the files in the Cisco IPICS server. Cisco IPICS requires that you use strong passwords that include the following elements:

Minimum of 8 characters in length At least one upper case letter At least one upper case letter At least one number At least one of the following special characters: @[]^_`!"#$%&'()*+,-./:;{<|=}>~?
If you need to change the root password at a later date, you can log in to the Cisco IPICS server as the root user and change it by using the reset_pw command. For more information, refer to the Using the Cisco IPICS CLI Tools and Service Commands chapter in the Cisco IPICS Troubleshooting Guide.
Step 6 Step 7
Click Next. Enter and confirm a password for the GRUB (boot loader) menu. The boot loader password enables access to the boot loader menu, which allows a system administrator to boot the server into single-user mode. Single-user mode is required to recover a lost root password. This password must contain at least 6 characters. Click Next. Enter a system user name and user full name, and enter and confirm a password. You must create a system user to perform administrative tasks on your server. This user password has the same requirements as the root password.
Step 8 Step 9
Step 10 Step 11 Step 12 Step 13 Step 14
Click Next to open the Network Setup window. In the Interface Settings area, enter the fully-qualified hostname, IP address, subnet mask, and gateway information in the specified fields. (Optional) In the DNS Information area in the Network Setup window, enter the IP address of your primary and secondary DNS server. Click Next to open the Timezone window. Choose the correct time zone for your area from the choices in the selection list. If your system clock uses Universal Coordinated Time (UTC), make sure that you check the System Clock uses UTC check box.
2-14
OL-21842-01
Chapter 2
Installing Cisco IPICS Configuring Server Parameters on the Multiservices Platform
Step 15 Step 16
Click Next to open the Date and Time window. Choose one of the following options to set the system date and time:
If your network uses the Network Time Protocol (NTP), choose the Network Time Protocol tab and check the Enable Network Time Protocol check box. Enter the name or IP address of an NTP server in the Server field, and click Add. Repeat to add additional servers. To delete a server, choose the server, and click Delete. If you configure NTP on the server, your system administrator should provide instructions to the IDC users to also configure the Windows Time Service on their IDC client machines to enable synchronization between the IDC and the server logs. For detailed information about how to configure the Windows Time Service, refer to the Microsoft support site at http://support.microsoft.com/ and search for Article ID 307897. If you install a time-bound license for your system, use caution when enabling NTP. Adjustments to the system date can cause Cisco IPICS to invalidate your license. For more information, see the Managing Time-Bound Licenses section on page 2-37.
Step 17 Step 18
If your network does not use NTP, choose the Date & Time tab and enter the current date and time in the appropriate fields.
Click Next to open the Finish Setup window. Click Next. The system processes an internal check list as it boots up. After the system has booted up, Cisco IPICS displays the following text:
Cisco IPICS hostname login:
where hostname represents the host name that you specified in step 12.
You can now continue with the installation of the Cisco IPICS server software. To install the Cisco IPICS server software, see the Installing the Cisco IPICS Server Software section.
2-15
Chapter 2 Installing the Cisco IPICS Server Software
Installing the Cisco IPICS Server Software

After you have successfully installed the Cisco IPICS operating system, you can install the Cisco IPICS server software by using one of the following methods:

Directly by using the installation CD at the Cisco IPICS server. Remotely by copying the installer file to the server and entering remote commands.
The Cisco IPICS server installation program uses a text-based interface and does not provide support for a graphical user interface (GUI). This installation procedure allows you to choose from the following install options:

InstallThis option installs the Cisco IPICS server software, including Cisco Security Agent (CSA). UpgradeThis option upgrades your server from a previous version of Cisco IPICS. For information about performing an upgrade of the Cisco IPICS server software, see Chapter 3, Upgrading Cisco IPICS.
Note
Be aware that the options that the installer displays may differ depending on the current software version that is running on your system. This section includes the following topics:

Performing a Direct Cisco IPICS Server Software Installation, page 2-16 Performing a Remote Cisco IPICS Server Software Installation, page 2-21
Performing a Direct Cisco IPICS Server Software Installation

If you have physical access to the Cisco IPICS server, you can install the server software directly from the server. To do so, you must have the Cisco IPICS installation CD that is included with your product package.
Note
Be aware that you must log in as the root user to perform the Cisco IPICS installation. If you attempt to run the installation from any other user ID, the installation returns an error and exits.
2-16
OL-21842-01
Chapter 2
Installing Cisco IPICS Installing the Cisco IPICS Server Software
Tip
To terminate the installation process at any point in time, press Ctrl+C. To install the Cisco IPICS server software directly from the server location, perform the following procedure:
Procedure
Step 1
Enter root in the hostname login: field in the terminal console; then, press Enter. Cisco IPICS prompts you for the password for the root user. Enter the password that you created for the root user in Step 6 in the Installing the Cisco IPICS Operating System section on page 2-7; then, press Enter. The Cisco IPICS operating system logs you in as the root user. Enter the free command and read the information that displays in the total column to check the total amount of installed memory. The Cisco IPICS installation requires a minimum of 2 GB of memory. The following example shows that there is a minimum of 2 GB of total memory in the server:
[root]# free total used free shared Mem: 2055340 881152 1174188 0 -/+ buffers/cache: 466604 1588736 Swap: 2048248 0 2048248 buffers 25520 cached 389028
Step 2
Step 3
If your server does not have sufficient memory, contact your Cisco representative to find out how you can purchase additional memory. Refer to the Cisco IPICS Compatibility Matrix for specific memory requirements.
Step 4 Step 5
Insert the Cisco IPICS installation CD into the CD drive of the Cisco IPICS server. Mount the contents of the CD onto the server by entering the following command:
[root]# mount /dev/cdrom /mnt/cdrom
Step 6
To navigate to the CD location, enter the following command:

[root]# cd /mnt/cdrom
2-17
Step 7
Verify the contents of the installation CD.

[root]# ls -ltr /mnt/cdrom total 563500 -r-xr-xr-x 1 root root 47322321 upgrade-idc-4.0(0.027).zip -r-xr-xr-x 1 root root 529616588 install-ipics-4.0.0.027.run -r-xr-xr-x 1 root root 7661 pre_ipics_db_upgrade_22_40 -r-xr-xr-x 1 root root 76279 [root]#
Feb 24 01:03 Feb 24 01:04 Feb 24 20:49 Feb 24 20:49 ipics_db_upgrade_22_40
The directory of the CD displays.

Step 8
Locate the installer file in the directory listing. The Cisco IPICS installer file has a .run file extension. To start the installation, enter the following command:
[root]# bash <installerfilename> .run
Step 9
where: <installerfilename>.run specifies the name of the installer file that you located in Step 7. Cisco IPICS begins the installation process. Text displays to inform you that you must read and accept the terms of the End User License Agreement (EULA) before you can proceed.
Step 10
Press Enter to display the EULA. The Cisco IPICS installer displays the EULA.
Step 11
Press the Spacebar to scroll through and view the EULA. To accept the terms of the EULA, enter y or yes to continue with the installation. You must accept the terms of the EULA to proceed.
Note
To terminate the installation while the EULA is being displayed, press Ctrl+C. The installation terminates after the installation program displays the entire EULA. Press q to bypass the EULA and terminate the installation process.
2-18
OL-21842-01
Chapter 2
The installation program prompts you to enter a password for the ipics user. The ipics user has the capability to perform all administration-related tasks via the Cisco IPICS Administration Console.
Step 12
Enter a password for the ipics user in the password field. To ensure a strong password, use a password that is at least eight characters long and contains at least one of each of the following characters:

One lower case letter One upper case letter One number One of the following special characters: @[]^_`!"#$%&'()*+,-./:;{<|=}>~?
Note
The installation program also creates a password for the informix Linux user by using a random algorithm. The informix user has full administrative permission to the Informix database instance and belongs to the ipics and informix linux groups. The ipics linux group includes permission to Cisco IPICS application-related folders, files, and scripts. The informix linux group includes full permission to the Cisco IPICS database server folders, files, and scripts. The password for this user ID never expires.
Step 13
Reenter the password; then, press Enter. The installation program prompts you to enter a password for the Cisco IPICS ipicsadmin (administrative) Linux user. That ipicsadmin user belongs to the ipics linux group. In addition, the ipicsadmin user has permission to read and write data from and/or to the Informix database.
Step 14
Enter a password in the password field to create the ipicsadmin user password. To ensure a strong password, use a password that is at least eight characters long and contains at least one of each of the following characters:

One lower case letter One upper case letter One number One of the following special characters: @[]^_`!"#$%&'()*+,-./:;{<|=}>~?
OL-21842-01
2-19
Note Step 15
The password for the ipicsadmin user never expires.
To begin the installation process, enter y or yes. The Cisco IPICS software begins the installation process. A progress bar displays to indicate the percentage of the installation that has completed.
Step 16
After the file installation completes, a message displays to inform you of the status. The following text is an example of the message that you might see when the installation has successfully completed.
"The installation has completed successfully." You can view the installation log file by navigating to the following directory: "/var/opt/CSCOipics/run/20061018092707/ipics-install-log.txt" To complete the installation, you must reboot your server. Do you want to reboot now? (YES/NO): [YES]
Step 17
Enter YES to reboot your server. The server reboots and your Cisco IPICS server becomes available.
Note
If you enter NO, complete the restart before you attempt to log in to Cisco IPICS. Cisco IPICS processes, such as the tomcat service and database server, do not start until you reboot the server. To reboot your server at a later time, follow the procedure in the Restarting or Shutting Down the Server section on page 2-25.
2-20
OL-21842-01
Chapter 2
Performing a Remote Cisco IPICS Server Software Installation

This section describes the procedure that you can follow to install Cisco IPICS from a PC that is remotely connected to the network. To install the Cisco IPICS server software from a remote location, perform the following procedure:
Procedure
Step 1
Transfer the installer file from the Cisco IPICS installation CD to the Cisco IPICS server. To do so, perform one of the following tasks:
Place the CD (or have someone place it for you) in the Cisco IPICS server and copy the installer file to the server. Follow the steps that are documented in Step 2 to perform this procedure. Place the CD in a PC and transfer the installer file to the Cisco IPICS server by using a Secure File Transfer Protocol (SFTP) client software program, such as Secure Shell (SSH) Client software (or similar software). Follow the steps that are documented in Step 3 to perform this procedure.
Note Step 2
You cannot install the IPICS operating system from a USB flash device.
To copy the installer file from the CD, perform the following steps:
a. b.
Insert the Cisco IPICS installation CD in the server disk drive. Choose Start > Programs > SSH Secure Shell > Secure Shell Client to remotely connect to the Cisco IPICS server.
Note
The SSH idle timeout value is 120 minutes (two hours). Therefore, make sure that you do not leave an SSH remotely-connected session inactive for more than two hours; otherwise, the session times out.
Tip
If you do not have Secure Shell Client installed on your PC, use another secure client program.
2-21
c.
Click Quick Connect to connect to the Cisco IPICS server. The Connect to Remote Host window displays. In the Host field, enter the DNS host name or the IP address for your Cisco IPICS server; then, press the Tab key. In the User Name field, enter root. Click Connect. The Enter Password window displays. Enter the password for the root user and click OK. The SSH Secure Shell Client software window displays. Mount the contents of the CD onto the server by entering the following command:
d. e. f.
g.
h.
[root]# mount /dev/cdrom /mnt/cdrom
Note
During the installation process, error messages, such as cdrom_decode_error, may display when you access the CD. You can ignore these messages, as they do not affect the installation or operation of the Cisco IPICS server. Navigate to the cdrom subfolder in the CD location by entering the following command:
i.
j.
To view the installer file, enter the following command:

[root]# ls -l

k.
Locate the installer file in the directory listing. The Cisco IPICS installer file has a .run file extension. Copy the installer file to the /root directory by entering the following command:
[root]# cp /mnt/cdrom/<installerfilename>.run /root
l.
2-22
OL-21842-01
Chapter 2
where: <installerfilename>.run represents the name of the .run file that was displayed in Step j. The installer file copies from the CD to the /root directory.
m.
Navigate from the /mnt/cdrom directory to an internal directory on your server by entering the following command:
[root]# cd <serverdirectory>
where: <serverdirectory> is any internal directory or subdirectory on your server.

n.
To unmount the installation CD and eject it from the disk drive, enter the following command:
[root]# eject
Note
Be aware that you must navigate away from the /mnt/cdrom directory and enter the eject command to unmount the contents of the CD and eject the CD from the server. If you try to eject the CD by pushing the eject button on the server, the CD will not eject.
Step 3
To transfer the file to the server from a remote location, follow these steps:
a. b.
Insert the Cisco IPICS installation CD in the CD drive of your PC. Choose Start > Programs > SSH Secure Shell > Secure File Transfer Client to open the Secure File Transfer Client.
Note
If you do not have Secure File Transfer Client installed on your PC, use another program that permits a secure file transfer session between your PC and the server. The SSH Secure Shell File Transfer Client window displays. The desktop of your PC displays in the left pane.
c.
Click Quick Connect to connect to the Cisco IPICS server. The Connect to Remote Host window displays. In the Host field, enter the DNS host name or the IP address for your Cisco IPICS server. Then, press the Tab key.
d.
OL-21842-01
2-23
e. f.
In the User Name field, enter root. Click Connect. The Enter Password window displays. Enter the password for the root user and click OK. The SSH Secure Shell File Transfer Client connects to the Cisco IPICS server and displays the contents of the /root directory in the right pane of the window.
g.
h.
In the left pane of the window, navigate to the folder on your PC that corresponds to the location of the Cisco IPICS installation CD (for example, My Computer\Compact Disk Z:). Double-click the CD folder to browse the contents of the CD. The contents of the CD displays. Double-click the cdrom subfolder to browse its contents. Locate the installer file in the cdrom subfolder on the CD. The installer file has an extension of .run. Drag the installer file from the left pane of the window to the right pane to initiate the copy procedure. A progress window displays while the file copies to the /root directory of the server. After the copy procedure completes, the installer file displays in the right pane.
i.
j. k.
l.
m. Step 4 Step 5 Step 6
Close the SSH Secure Shell File Transfer Client.
Open a terminal window to the Cisco IPICS server by using SSH Secure Shell Client software or similar software. In the User Name field, enter root. Click Connect. The Enter Password window displays. Enter the password for the root user and click OK. The SSH Secure Shell Client software window displays. To view the installer file, enter the following command:
[root]# ls -l
Step 7
Step 8
The contents of the /root directory display.

2-24
OL-21842-01
Chapter 2
Installing Cisco IPICS Restarting or Shutting Down the Server
Step 9
Locate the installer file in the directory listing. The Cisco IPICS installer file has a .run file extension. Change the access mode of the installer file by entering the following command:
[root]# chmod 550 <installerfilename>.run
Step 10
where: <installerfilename>.run represents the name of the installer file.
Note
Entering this command allows the root user ID to read and run the installer file.
Step 11
To run the installer from a SSH Secure Shell Client software (or similar software) window, follow the procedure as described in the Performing a Direct Cisco IPICS Server Software Installation section, starting with Step 9 on page 2-18.
Restarting or Shutting Down the Server

To restart the server, perform the following procedure:
Caution
Be aware that when you shut down or restart your server, all user communications terminate. In addition, Cisco IPICS logs out all users who are logged in to the Administration Console. Therefore, make sure that you only shut down or restart your server during a maintenance window or other period of system non-use.
Procedure
Step 1
Log in to the Cisco IPICS server with the root user ID by taking one of the following actions:
To log in to the server from the server console, follow these steps:
a. Log in to the server by entering root for the user name. b. When you are prompted, enter the root user password.
OL-21842-01
2-25
Chapter 2 Restarting or Shutting Down the Server
To log in to the server remotely, follow these steps:

a. Open a terminal window by using SSH Secure Shell Client software or
similar software.
b. Log in to the server by entering the IP address or host name of the server. c. Log in by using the root user ID by entering root for the user name. d. When you are prompted, enter the root user password.
A terminal window displays.

Step 2
To reboot the server, enter the following command:

[root]# reboot
The server reboots.
To shut down the server, perform the following procedure.
Note
Cisco recommends that you gracefully shut down the server by performing the following procedure in lieu of pressing the power button to shut down the server.
Procedure
Step 1
Log in to the Cisco IPICS server with the root user ID. A terminal window displays. To shut down the running processes in the server, enter the following command:
[root]# shutdown -h <time>
Step 2
where: <time> is the time, in seconds, that the shutdown script delays before it begins.
Tip
To immediately shut down the running processes, enter the following command:
[root]# shutdown -h now
2-26
OL-21842-01
Chapter 2
Installing Cisco IPICS Preparing to Use Cisco IPICS
The server terminates its running processes. If you are directly connected to the server, the console displays messages as each process terminates.
Step 3
Wait until the shutdown script completes; then, turn the server off by pushing the power button that is located on the front panel of the server. Before you turn off the server, verify that the shutdown script has completed by performing one of the following actions:
If you are directly connected to the server by a console connection, wait until the following text displays: Power down. If you are remotely connected to the server, wait approximately five minutes to allow all processes to safely terminate.
Note
You must manually turn off the server at the server location. You cannot turn off the server by entering CLI commands. The server shuts down.
Preparing to Use Cisco IPICS

After you complete the software installation, you must complete the following tasks before you can use Cisco IPICS:

Checking the Installation, page 2-28 Managing Your Licenses and Certificates, page 2-29 Viewing the License Summary Information, page 2-34
For more information about Cisco IPICS administration and configuration tasks, refer to the Cisco IPICS Server Administration Guide.
2-27
Chapter 2 Preparing to Use Cisco IPICS
Checking the Installation

Upon completion of the Cisco IPICS server software installation, you should be able to access the Cisco IPICS Administration Console by logging in via a supported browser. (There may be a delay of a few minutes before you can access the console.) You can access the Administration Console from any computer that meets these requirements:

Has IP connectivity to the Cisco IPICS server Windows XP SP2 and SP3, Internet Explorer 6 SP1 and Internet Explorer 7
Note
You must also download and install the NDP30SP2-KB967634-x86.exe patch from the Microsoft website. To access the Cisco IPICS Administration Console and check the installation, perform the following procedure:
Procedure
Step 1 Step 2
Open a supported Internet browser window on your PC. In the Address field, enter an HTTP over Secure Socket Layer (HTTPS) URL that contains either the static IP address or the DNS name that you established for your Cisco IPICS server in the Installing the Cisco IPICS Operating System section on page 2-7. Enter the URL in the following format: https://<ipaddress> | <dnsname> where: <ipaddress> is the IP address of the server and <dnsname> is the host name that you configured for the server. A Security Alert window displays.
2-28
OL-21842-01
Chapter 2
Note
The Security Alert window displays because Cisco IPICS ships with a self-signed certificate that is not issued by a Certificate Authority (CA). If you prefer to replace the self-signed certificate with a third party certificate that has been issued by a CA, follow the procedure in the Installing Third Party Certificates On the Cisco IPICS Server section on page 2-43.
Step 3 Step 4
Click Yes to close the window and access the login screen. Log in by using the ipics user ID and password.
Note
The ipics user ID is the application-level user ID that can perform all administration-related tasks by using the Administration Console.
The Administration > License Management window displays with a message that informs you to upload a license file before you can use the system.
To obtain your license file, see the Obtaining Your License File section on page 2-30. If you are not able to access Cisco IPICS from your browser, see the You Cannot Connect to the Server By Using Your Browser section on page 5-5.
Managing Your Licenses and Certificates

After you install Cisco IPICS, you can log in to the Administration Console, but you will not be able to use any features until you upload the license file. You use the Product Authorization Key (PAK) that was included in your Cisco IPICS product package to obtain a license file. The license that you purchased is based on the total number of the following licensable features:

The concurrent number of land mobile radio (LMR) ports The concurrent number of multicast ports The concurrent number of IDC users
2-29
The concurrent number of IP phone users The concurrent number of dial users The total number of ops views
Note
To enable the policy engine for use, you are required to obtain a separate license. The total number of LMR and multicast ports, IDC, IP phone, and dial users, and ops views cannot exceed the number that is specified in the license or licenses that you purchased. If you require additional licenses, contact your Cisco representative. This section includes the following topics:

Obtaining Your License File, page 2-30 Uploading the Cisco IPICS License Files, page 2-32
Obtaining Your License File

Your Cisco IPICS product package includes a Software License Claim Certificate that contains a PAK, which is uniquely created from your sales order. You use this key to obtain licenses for your Cisco IPICS installation. You can order your initial licenses any time after you begin the installation process.
Caution
Upgrades are supported only from Cisco IPICS release 2.2(1). Contact your authorized Cisco representative to obtain new licenses for Cisco IPICS release 4.0(1). To use your PAK to obtain your Cisco IPICS licenses, perform the following procedure:
Procedure
Step 1
Locate your Software License Claim Certificate that was included in your Cisco IPICS product package. Look for the PAK at the bottom of this certificate.
2-30
OL-21842-01
Chapter 2
Note
If you ordered your Cisco IPICS server software directly from Cisco, your package may include only one PAK. However, if you purchased Cisco IPICS through a distributor or reseller, you should have several individual packages, each with its own PAK. In this case, you must process all of your PAKs individually. Cisco sends you a license file for each one.
Step 2
Retrieve the MAC address that you noted during the Cisco IPICS operating system installation. If you misplaced the MAC address, complete Step 24 in the Installing the Cisco IPICS Operating System section on page 2-7 to obtain it.
Step 3
Order a license by accessing Cisco.com at the following URL: http://www.cisco.com/go/license You must have a valid Cisco.com user ID and password before you can access this URL. After you process your license order, Cisco.com sends you an e-mail with the license file as an attachment. If you processed several separate PAKs, Cisco.com sends you several e-mail responses with a license file attached to each one. When you upload these files, Cisco IPICS adds the licenses from each file and monitors your system activity based on the aggregated license files.
Step 4
Save the license file to your PC by performing the following steps:

a. b. c.
Open the e-mail that contains the license file attachment. Right-click the license file attachment in the e-mail. Click Save As. The Save Attachment window displays. Select the folder on your PC where you would like to download the license file. Ensure that the following values appear in the fields of the Save Attachment window:
The file name of the license appears with a .lic file type in the File name
d. e.
field.
All Files (*.*) appears in the Save as type field.
2-31
f.
Click Save. The e-mail program downloads the license file to your PC.
Note
Cisco IPICS does not support the editing or modification of the license file name or file type. If you change the license file name or use an extension other than .lic, you may invalidate your license and cause the system to become inoperable.
Step 5
Upload the Cisco IPICS license. See the Uploading the Cisco IPICS License Files section on page 2-32 for instructions about uploading the Cisco IPICS license file. After you upload your license file, the license manager processes the new licenses and updates the total number of licenses.
Step 6
If you require additional licenses, contact your distributor or reseller to purchase the licenses.
Uploading the Cisco IPICS License Files

After you receive your license file(s), you can upload them by accessing the Administration > License Management window in the Cisco IPICS Administration Console.
Note
When you upload a license file, Cisco IPICS places the file in the following directory: /root/tomcat/current/webapps/license To upload license file(s), perform the following procedure:
Procedure
Step 1
Open a supported browser window on your PC.
2-32
OL-21842-01
Chapter 2
Step 2
In the Address field in the browser, enter an HTTPS URL that contains either the IP address or the DNS name of your Cisco IPICS server in the following format: https://<ipaddress> | <dnsname> where: <ipaddress> is the IP address of the server and <dnsname> is the host name that you configured for the server. A Security Alert window displays. Click Yes to close the window and access the login screen. The Cisco IPICS Login window displays. Log in to the Cisco IPICS server by using the ipics user ID and password. The system prompts you to upload the license file.
Step 3
Step 4
Note
The system does not prompt you to upload a license file if you have previously uploaded a license file. If you are not prompted to upload the license file, navigate to Administration > License Management from the Server tab in the Administration Console.
The License Management window displays.

Click Browse, then navigate to the license file that you downloaded to your PC. Select the license file and click Open. Click Upload to upload the license file to the server. The license manager processes the new license. Click Apply. Cisco IPICS associates the license file with the server and restarts the license manager. The updated license information displays in the License Summary pane in the License Management window.
Step 8
Note
After you click Apply, there may be a delay of a few minutes before you can access the Administration Console.
Step 9
If you have more than one license file, repeat Step 5 through Step 8 until you have uploaded all license files.
2-33
Tip
Cisco recommends that you click Apply after you upload each license file, so that you can more easily track the progress of the upload process.
Note
Cisco IPICS does not overwrite older license files with newer license files. You can purchase additional features by obtaining a new license; when you upload and apply the new license, Cisco IPICS adds the new license features to the existing license features. As a best practice, Cisco recommends that you remove old license file(s) whenever license changes occur (such as when you replace a time-bound license with a permanent license). For information about deleting time-bound licenses, see the Deleting Older Time-Bound Licenses from the Server section on page 2-38.
Viewing the License Summary Information

From the Administration > License Management > Summary tab in the Administration Console, you can access the License Summary pane to view the licensed features for your system. This pane also displays license information for the Cisco IPICS Base Server License and the Policy Engine Base License. To understand how Cisco IPICS features use the available licensed features, see the Tracking Your License Usage section on page 2-35.
Note
The data that displays in the License browser window shows the usage at the time that the license window was last accessed. To view the most current license information, refresh your browser window. Make sure to refresh your browser window often and before you perform any server administration functions to ensure that you are working with the most current information. If you attempt to perform an administration update in a window that does not display the most current data, the update does not succeed, and Cisco IPICS displays an error. If you receive an error, refresh your browser window and retry the operation.
2-34
OL-21842-01
Chapter 2
This section includes the following topics:

Tracking Your License Usage, page 2-35 Managing Time-Bound Licenses, page 2-37
Tracking Your License Usage

Table 2-1 describes the criteria that Cisco IPICS uses to determine license usage for ports, IDCs, IP phones, the policy engine, and ops views.
Table 2-1 Cisco IPICS License Usage Criteria
Field Concurrent LMR Ports
Description An enabled channel or radio uses an LMR port license. After an administrator disables a channel or radio, the server releases the LMR license and makes it available for use. Associating a radio and channel selector combination with a channel does not affect license usage. Cisco IPICS bases license usage for channels on the unique combination of a multicast address and a location. If a channel uses two multicast addresses, the single channel uses two licenses. If an administrator removes one of the multicast addresses, the system releases one of the licenses so that the port now uses one license.
Concurrent Multicast Ports
An activated VTG uses a multicast port license. After an administrator deactivates a VTG, the server releases the multicast license and makes it available for use.
Note
Be aware that an inactive VTG uses a license when a policy triggers (activates) that VTG. Therefore, if the number of licenses has been exceeded, the policy is not able to activate the VTG. Make sure that the server has a sufficient number of licenses available for the configuration of policies.
Concurrent Cisco Unified IP Phone Users
An IP phone user uses a license each time that a user logs in to Cisco IPICS from an IP phone. If you use all IP phone licenses, additional IP phone users cannot dial into a channel or VTG.
2-35
Table 2-1
Cisco IPICS License Usage Criteria (continued)
Field
Description
Concurrent Dial The policy engine uses a license each time the dial engine Users performs a dial-in or dial-out action. If you use all dial user licenses, the dial engine cannot perform additional dial-in or dial-out actions. Concurrent Dispatch Console Silver Users This entry shows the number of concurrent users with silver licenses. A IDC user uses a license each time that the user logs in to a IDC session. If the same IDC user logs in to multiple IDC sessions from different IDC client machines, that user uses multiple licenses (one for each IDC session).
Note
If you use all of the available IDC licenses, Cisco IPICS interrupts IDC user access to the system. Make sure that you are aware of the current status of IDC licenses, and purchase and install additional licenses immediately if you use all of the available IDC licenses.
Concurrent Dispatch Console Platinum Users
This entry shows the number of concurrent users with platinum licenses. A IDC user uses a license each time that the user logs in to a IDC session. If the same IDC user logs in to multiple IDC sessions from different IDC client machines, that user uses multiple licenses (one for each IDC session).
Note
If you use all of the available IDC licenses, Cisco IPICS interrupts IDC user access to the system. Make sure that you are aware of the current status of IDC licenses, and purchase and install additional licenses immediately if you use all of the available IDC licenses.
Concurrent This entry shows the number of concurrent users with who Mobile Endpoint are accessing IDC from mobile endpoints. Users Note If you use all of the available IDC licenses, Cisco IPICS interrupts IDC user access to the system. Make sure that you are aware of the current status of IDC licenses, and purchase and install additional licenses immediately if you use all of the available IDC licenses.
2-36
OL-21842-01
Chapter 2
Table 2-1
Cisco IPICS License Usage Criteria (continued)
Field Cisco IPICS Ops View Cisco IPICS Base Server License Policy Engine Base License High Availability
Description If you have purchased a license that includes additional ops view functionality, each ops view that you create uses one license. License usage does not apply to this field. This field displays whether you have a base license for Cisco IPICS. License usage does not apply to this field. This field indicates whether you have a base license for the policy engine. License usage does not apply to this field. This field indicates whether you have a base license for high availability.
Managing Time-Bound Licenses

Cisco IPICS also includes support for time-bound licenses. Time-bound licenses, such as evaluation or demonstration licenses, differ from purchased (non-time-bound) licenses in that they include a preconfigured license expiration date. When a time-bound license is about to expire (about 30 days before expiration), Cisco IPICS displays a warning message to alert you of the upcoming expiration.
Note
If you install a more recent time-bound license on your server, you may see this warning message if additional unexpired time-bound licenses are installed and you have not dismissed this warning. To suppress this warning message, delete the older, unexpired licenses that are installed on your server. For more information, see the Deleting Older Time-Bound Licenses from the Server section on page 2-38.

When a license feature expires, the relevant functionality of that license becomes disabled. After your license expires, it remains valid for a maximum of 24 hours after the expiration date. (The server checks for expired licenses every 24 hours.)
2-37
After you install the Cisco IPICS server software, Cisco IPICS invalidates time-bound licenses when you change the system date to a date that is before the license start date. Invalid licenses cause the Cisco IPICS system to become inoperable.
Note
You must restart the license manager, or reboot the server, for system date changes to become effective.
To restart the license manager and revalidate the license(s), perform the following procedure:
Procedure
Step 1 Step 2
Open a terminal window and log in using the root user ID. Restart the license manager by entering the following command:
[root]# service ipics_lm restart
Step 3
To revalidate the license(s), navigate to Administration > License Management; then, click Apply to restart the license server.
Deleting Older Time-Bound Licenses from the Server

If you receive license expiration warning messages, and you have more than one unexpired time-bound license installed, you must delete the older time-bound licenses to suppress this warning message. To delete time-bound licenses, perform the following procedure:
Procedure
Step 1 Step 2
Open a terminal window and log in by using the root user ID. Navigate to the directory where Cisco IPICS stores the license files by entering the following command:
[root]# cd tomcat/current/webapps/license
2-38
OL-21842-01
Chapter 2
Step 3
View the license files by entering the following command:

[root]# ls -l *.lic
The license files display with the time and date that the license was last modified.
Step 4
Make a note of the licenses that you no longer need. The time and date that displays with the file information might assist you with determining which files you need to delete.
Step 5
Delete the unnecessary license files by entering the following command:

[root]# rm <licensefilename>.lic
where: <licensefilename>.lic is the name of the license file that you want to delete.
Caution
Make sure that you do not delete the cisco.opt file. This file is required for the correct operation of Cisco IPICS. Repeat Step 5 for each license file that you need to delete. Restart the server by entering the following command:
[root]# service ipics restart
Step 6 Step 7
Log in to the Administration Console by using the ipics user ID and navigate to the Administration > License Management window. To apply the license deletions to the system configuration, click Apply. If a message displays that indicates that a license is about to expire, click Dismiss Warnings.
2-39
Chapter 2 Managing Server Certificates
Managing Server Certificates

This section describes how to perform the following server certificate tasks:

Backing Up Server Certificates and Stores, page 2-40 Customizing and Generating a Self-Signed Server Certificate, page 2-41 Installing Third Party Certificates On the Cisco IPICS Server, page 2-43
To perform the tasks in this section, make sure that the following tools are available:
A Secure Shell (SSH) client, such as

SSH Tectia Client Putty SSH Cygwin ssh.
A Secure Copy (SCP) and/or Secure File Transfer Protocol (SFTP) client, such as
Putty pscp Putty sftp Cygwin scp Cygwin sftp WinSCP
Backing Up Server Certificates and Stores

Before generating and installing a server certificate, back up existing certificate files by performing the following steps:
Procedure
Step 1 Step 2
Use SSH to log in to the Cisco IPICS server as root. Change to the security directory and create a backup directory:
[root]# cd /opt/cisco/ipics/security/ [root]# mkdir backup
2-40
OL-21842-01
Chapter 2
Installing Cisco IPICS Managing Server Certificates
Step 3
Create a backup copy of the server.truststore.jks file, which includes all of the trusted certificates for the server.
[root@ipics-server]# cp -a server.truststore.jks backup/
Step 4
Create a backup copy of the server.keystore.p12 file, which contains the server private key:
[root@ipics-server]# cp -a server.keystore.p12 backup/
Step 5
Create backup copies of the certificate files:

[root@ipics-server]# cp -a *.pem backup/
Step 6
Create a backup copy of security properties files:

[root@ipics-server]# cp -a security.properties backup/
Customizing and Generating a Self-Signed Server Certificate

Because Cisco IPICS services are disrupted during generation and customization of a self-signed server certificate, Cisco recommends that you perform the following procedure during a maintenance window. Before doing so, back up any existing certificate files as described in the Backing Up Server Certificates and Stores section on page 2-40. To generate and customize a self-signed server certificate, perform the following steps:
Step 1 Step 2
Use SSH to log in to the Cisco IPICS server as root. Change to the security directory:
[root]# cd /opt/cisco/ipics/security/ cd /opt/cisco/ipics/security/
Step 3
If you plan to use a third party security certificate, customize the security properties for your company by editing the security.properties file and changing the parameters listed in Table 2-2.
2-41
Note the following:
The information that you enter may vary according to the CA that you use. For example, for the name of your state or province [x500StateName], VeriSign requires that you spell out the complete name rather than using the abbreviated form. The system requires that you use the same value for the private key password and the keystore password. If you enter different passwords, the Tomcat server cannot successfully restart. (When these passwords are the same, the system does not prompt you again for the key password.) If you change the passwords in the security.properties file, also update the password in the Tomcat server.xml file in /opt/cisco/ipics/tomcat/current/conf.
Customizing Security Properties
Table 2-2
Entry certValidity=1095 keySize=2048 keystorePassword=changeit privateKeyPassword=changeit truststorePassword=changeit x500OrginizationName=Cisco Systems, Inc. x500OrginizationalUnit=PSBU x500LocalityName=San Jose x500StateName=California x500Country=US x500Email=admin@ipics.cisco.com
Step 4
Description The number of days the certificate is valid. Key size, in bits. Sometimes referred to as encryption strength. Password for the key store (default is changeit). Password for the private key. Password for the trust store. Your company name. You company division. Your city. Your state or province. Your country (2 letter ISO code) Your e-mail address.
Stop all IPICS services:

[root@ipics-server]# service ipics stop-all
2-42
OL-21842-01
Chapter 2
Step 5
Remove the existing certificate

[root@ipics-server]# sudo -H -u ipicsadmin ./security-manager unsetup
Step 6
Generate a new set of self-signed certificates using the properties that you defined in Step 3.
[root@ipics-server]# sudo -H -u ipicsadmin ./security-manager setup
This command creates the following certificates: ca.cert.pem server.cert.pem server.csr.pem

Step 7
Local self-signed CA certificate) Server certificate, signed by the local CA Certificate signing request (CSR)
Start all IPICS services:

[root@ipics-server]# service ipics start-all
Note
Because the security-manger script shown in Step 6 does not restart all of the essential high availability processes, you must start all IPICS services to ensure system stability.
Installing Third Party Certificates On the Cisco IPICS Server

The Cisco IPICS server ships with a self-signed certificate. However, you may replace this certificate with a customer-specific, third party certificate that has been issued by a CA. A CA, as a trusted third party, issues and manages digital certificates that provide enhanced security by verifying the credentials of the user, organization, server, or other entity as specified in the certificate. VeriSign, Thawte, and Entrust are examples of CAs. The following topics include information about requesting a third party certificate and installing the certificate on the Cisco IPICS server:

Requesting a Third Party Certificate, page 2-44 Installing a Third Party Certificate, page 2-45 Converting DER Formatted Certificates to PEM Format, page 2-51
OL-21842-01
2-43
Requesting a Third Party Certificate

Because Cisco IPICS services are disrupted, Cisco recommends that you perform the following procedure during a maintenance window. Before doing so, back up any existing certificate files as described in the Backing Up Server Certificates and Stores section on page 2-40. To request a third party certificate, perform the following steps:
Procedure
Step 1
Follow Step 1 - Step 6 in the Installing Third Party Certificates On the Cisco IPICS Server section on page 2-43. Do not start the IPICS services, as described in step Step 7. Stop all IPICS services (in the event that any are running):
[root]# service ipics stop-all
Step 2
Depending on the Certificate Authority that you use, you may need to copy and paste the contents of the server.csr.pem file into your browser, or you may need to upload the CSR file to request the certificate.
Step 3
To the paste text into a browser:

a.
List the file contents:
[root]# cat server.csr.pem
b. Step 4
Paste CSR text into the CA web page.
If the CA does not accept the certificate request, make the requested modifications and then repeat this procedure.
When you receive the certificate from the CA, follow the procedure in Installing a Third Party Certificate section on page 2-45 to install the certificate.
2-44
OL-21842-01
Chapter 2
Installing a Third Party Certificate

Because Cisco IPICS services are disrupted when installing a third party certificate, Cisco recommends that you perform the following procedure during a maintenance window. Before doing so, back up any existing certificate files as described in the Backing Up Server Certificates and Stores section on page 2-40. To install a third party certificate on the server, perform the following procedure:
Procedure
Step 1
Depending on the format in which you receive the certificate, take one of the following actions:

If you receive the certificate file directly from the CA, rename the file to signed_server.cert.pem. If you receive the certificate enclosed in an email, create a new file named signed_server.cert.pem (this file must contain only the certificate contents of the email).
CAs may use different procedures to send root CA certificates. Some CAs embed the root CA certificate into the certificate that they provide to you; other CAs provide the root CA certificate separately. (The root CA certificate allows you to establish a chain of trust from the CA to the third party certificate on your server.)
Step 2
Depending on the format in which the CA provides the root CA certificate, take one of the following optional actions:

If you download the root CA certificate file directly from the CA website, rename the file to root_ca.cert.pem. If the CA provides the root CA certificate enclosed in a web page, create a new file named root_ca.cert.pem (the file must contain only the root CA certificate contents of the web page).
Step 3
(If applicable) Some CAs also provide an intermediate CA certificate. If so, then take one of the following actions:
If you download the intermediate CA certificate file directly from the Certificate Authority website, rename the file to intermediate_ca.cert.pem.
2-45
If the CA provides the intermediate CA certificate enclosed in a web page, create a new file named intermediate_ca.cert.pem (the file must contain only the intermediate CA certificate contents of the web page).
Step 4
The certificates must be in text (PEM) format. If you open the certificate files using a text editor, and you do not see
-----BEGIN CERTIFICATE-----
inside the certificate files, follow the steps in Converting DER Formatted Certificates to PEM Format section on page 2-51 before continuing.
Step 5
Upload all of the certificate files from the local workstation to the IPICS server:
C:\ scp *.pem root@<ipics-server-ip-addr>:/root/
Note
The contents of the /root directory on the IPICS server are unchanged and are therefore not affected by future upgrades to the system.
Step 6 Step 7
Use SSH to log in to the Cisco IPICS server as root. Change to the security directory:
[root]# cd /opt/cisco/ipics/security/
Step 8
Copy the certificate files to the security directory and set the correct file permissions:
[root@ipics-server]# cp /root/*.pem /opt/cisco/ipics/security/ [root]# chown ipicsadmin:ipics *.pem [root]# chmod 600 *.pem
Step 9
Concatenate all of the certificates from the Certificate Authority to form the server's certificate chain. The root CA certificate should come first, then the intermediate certificates (if applicable), and then the signed server certificate.
[root@ipics-server]# cat root_ca.cert.pem \ intermediate_ca.cert.pem \ signed_server.cert.pem > server.cert.pem
Step 10
Run the following commands to delete the existing entries from the trusted certificate store:
[root@ipics-server]# keytool -delete \ -keystore server.truststore.jks \ -storepass changeit \ -alias <ipics.server.ip.address>
2-46
OL-21842-01
Chapter 2
[root@ipics-server]# keytool -delete \ -keystore server.truststore.jks \ -storepass changeit \ -alias ipics@<ipics.server.ip.address>
Step 11
(If applicable) Import the intermediate CA certificate into the IPICS servers trust store. When prompted to trust this certificate, enter yes.
[root@ipics-server]# keytool -import \ -keystore server.truststore.jks \ -trustcacerts \ -storepass changeit \ -file intermediate_ca.cert.pem \ -alias intermediateCA Enter keystore password: ******** Owner: CN=VeriSign Trial Secure Server CA - G2, OU=Terms of use at https://www.verisign.com/cps/testca (c)09, OU="For Test Purposes Only. No assurances.", O="VeriSign, Inc.", C=US Issuer: CN=VeriSign Trial Secure Server Root CA - G2, OU="For Test Purposes Only. No assurances.", O="VeriSign, Inc.", C=US Serial number: 7e3bb784bbc654abd2b8d677ecc394a8 Valid from: Wed Apr 01 00:00:00 GMT 2009 until: Sun Mar 31 23:59:59 GMT 2019 Certificate fingerprints: MD5: 71:13:D9:3A:CD:21:F2:EE:9F:59:17:8D:A6:F9:AE:14 SHA1: BE:D1:D1:4E:25:A7:94:36:83:9E:4B:A7:CD:84:48:96:B7:0A:7F:B0 Signature algorithm name: SHA1withRSA Version: 3 Extensions: #1: ObjectId: 2.5.29.15 Criticality=true KeyUsage [ Key_CertSign Crl_Sign ] #2: ObjectId: 2.5.29.19 Criticality=true BasicConstraints:[ CA:true PathLen:0 ] #3: ObjectId: 2.5.29.14 Criticality=false SubjectKeyIdentifier [ KeyIdentifier [ 0000: 28 17 13 8A BD D6 A2 B5 DC 06 2C B7 B6 8E DA 10 (.........,..... 0010: 66 60 6E E5 f`n. ]
2-47
] #4: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false AuthorityInfoAccess [ [accessMethod: 1.3.6.1.5.5.7.48.1 accessLocation: URIName: http://ocsp.verisign.com] ] #5: ObjectId: 1.3.6.1.5.5.7.1.12 Criticality=false #6: ObjectId: 2.5.29.31 Criticality=false CRLDistributionPoints [ [DistributionPoint: [URIName: http://crl.verisign.com/SVRTrialRootG2.crl] ]] #7: ObjectId: 2.5.29.32 Criticality=false CertificatePolicies [ [CertificatePolicyId: [2.16.840.1.113733.1.7.21] [PolicyQualifierInfo: [ qualifierID: 1.3.6.1.5.5.7.2.1 qualifier: 0000: 16 24 68 74 74 70 73 3A 2F 2F 77 77 77 2E 76 65 .$https://www.ve 0010: 72 69 73 69 67 6E 2E 63 6F 6D 2F 63 70 73 2F 74 risign.com/cps/t 0020: 65 73 74 63 61 2F estca/ ]] ] ] #8: ObjectId: 2.5.29.35 Criticality=false AuthorityKeyIdentifier [ KeyIdentifier [ 0000: 48 19 E7 92 6F 92 9D 34 63 99 C0 F0 99 C8 D6 A5 H...o..4c....... 0010: 8C 8C 7F 65 ...e ] ] Trust this certificate? [no]: yes Certificate was added to keystore
Step 12
Import the signed server certificates into the IPICS server's trust store. Enter yes to trust the certificate. The output is similar to the output shown in Step 11.
[root@ipics-server]# keytool -import \ -keystore server.truststore.jks \ -trustcacerts \ -storepass changeit \ -file signed_server.cert.pem \ -alias <ipics.server.ip.address>
2-48
OL-21842-01
Chapter 2
Note
The following error message is shown if you do not install the required root CA certificate:
keytool error: java.lang.Exception: Failed to establish chain from repl
If you encounter this error, contact the Certificate Authority to locate the root CA certificate; then, repeat this procedure beginning with Step 4.
Step 13
Import the signed server certificates into the IPICS server's trust store. Enter yes to trust the certificate under a different alias name.
[root@ipics-server]# keytool -import \ -keystore server.truststore.jks \ -trustcacerts \ -storepass changeit \ -file signed_server.cert.pem \ -alias <IPICS@ipics.server.ip.address> Certificate already exists in keystore under alias <ipics.server.ip.address> Do you still want to add it? [no]: yes Certificate was added to keystore
Step 14
List the contents of the trusted certificate store and verify there are entries for all certificates:
[root@ipics-server]# keytool -list \ -keystore server.truststore.jks \ -storepass changeit Keystore type: JKS Keystore provider: SUN Your keystore contains 3 entries intermediateca, Mar 12, 2010, trustedCertEntry, Certificate fingerprint (MD5): 71:13:D9:3A:CD:21:F2:EE:9F:59:17:8D:A6:F9:AE:14 10.194.150.141, Mar 12, 2010, trustedCertEntry, Certificate fingerprint (MD5): 03:93:3C:B7:CB:07:30:24:93:0E:B2:24:FE:59:A7:C3 ipics@10.194.150.141, Mar 12, 2010, trustedCertEntry, Certificate fingerprint (MD5): 03:93:3C:B7:CB:07:30:24:93:0E:B2:24:FE:59:A7:C3
2-49
Step 15
Import the server's new certificate chain into the keystore.

[root@ipics-server]# openssl pkcs12 -export \ -in server.cert.pem \ -inkey server.privkey.pem \ -out server.keystore.p12 \ -passout pass:changeit
Note Step 16
This step does not display any output.
Verify that the certificate has been installed by executing the following command.
[root@ipics-server]# keytool -list -v \ -keystore server.keystore.p12 \ -storetype PKCS12 \ -storepass changeit | head -15
The system displays the certificate information. For example, if you installed the root CA, intermediate CA, and server certificate, the system display indicates that the keystore contains one entry with a chain length of 3.
Keystore type: PKCS12 Keystore provider: SunJSSE Your keystore contains 1 entry Alias name: 1 Creation date: Mar 11, 2010 Entry type: PrivateKeyEntry Certificate chain length: 3 ...
Step 17
Copy the CA public certificate to public folder for mobile clients:

[root@ipics-server]# cp -af root_ca.cert.pem /opt/cisco/ipics/tomcat/current/webapps/ipics_server/images/ca.crt
Step 18
Restart the IPICS server.

[root@ipics-server]# service ipics start-all
2-50
OL-21842-01
Chapter 2
Installing Cisco IPICS Modifying Network Settings
Converting DER Formatted Certificates to PEM Format

To convert DER formatted certificates to PEM format, perform the following steps:
Procedure
Step 1 Step 2
Use SSH to log in to the Cisco IPICS server as root. Use openssl to convert a certificate from PEM to DER format:
[root@ipics-server]# openssl x509 \ -in cert.der -inform DER \ -out cert.pem -outform PEM
Modifying Network Settings

You can modify network settings for the IPICS server from the command line on the IPICS server. To modify network settings, follow these steps:
Procedure
Step 1 Step 2
Access the IPICS server using an SSH client, and log in as root. Access the network configuration utility:
[root]# network_config
The following information and menu items are displayed.

**** NETWORK CONFIGURATION UTILITY v4.0 **** To change a network setting, enter the number that corresponds to the value that you want to change. When you are prompted, enter the new value. If you press Enter but do not specify a new value for items 1-4, the existing value remains. If you press Enter but do not specify a new value for items 5-7, the current value is deleted. Make sure that you select Apply to save your changes. ---------------------------------------------------------------------1. Host Name [ipics-smoke40-sec.cisco.com]
2-51
Chapter 2 Modifying Network Settings
2. IP Address [10.194.150.104] 3. Subnet Mask [255.255.255.128] 4. Gateway [10.194.150.1] Optional: 5. Primary DNS [171.70.168.183] 6. Secondary DNS [171.68.226.120] 7. Tertiary DNS [] ---------------------------------------------------------------------i. Import a previously saved configuration s. Save this configuration r. Reset to current server configuration a. Apply this configuration q. Quit Enter option:
Step 3 Step 4
Enter the number of the option you want to change, and follow the on-screen instructions. When you are finished making changes, use the alphabetic commands to apply the configuration to the IPICS server or save the configuration to a file. You can also use the numeric commands to import a previously saved configuration, or reset the current server configuration to the last saved version.
Step 5
Enter q to close the configuration utility.
2-52
OL-21842-01
CH A P T E R
Upgrading Cisco IPICS

If your Cisco IPICS server is running release 2.0(2), 2.0(2), or 2.1(1) SR1, you can upgrade your server to release 4.0(1) by using a Cisco-provided CD-ROM. If you are not sure about how to obtain the software for Cisco IPICS release 4.0(1), contact your Cisco representative for information.
Tip
To verify which versions of Cisco IPICS are compatible for upgrade, refer to the most recent version of the Cisco IPICS Compatibility Matrix at http://www.cisco.com/en/US/products/ps7026/ tsd_products_support_series_home.html This chapter contains information about upgrading your software to Cisco IPICS release 4.0(1) and other actions that you must take to fully complete this upgrade process and includes the following sections:

Before You Begin, page 3-2 Performing a Direct Cisco IPICS Server Software Upgrade, page 3-2 Performing a Remote Cisco IPICS Server Software Upgrade, page 3-7 Upgrading the Radio Descriptor, page 3-12
3-1
Before You Begin

Be aware of the following caveats, 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 the Cisco IPICS release 2.0(2) server software and restore your database from the remote 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 of the 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 the Cisco IPICS Server Administration Guide. Cisco IPICS retains existing attributes for channels, VTGs, and users during an upgrade. Note, however, that the default setting for the Allow Latch attribute is set to disabled (unchecked) when you create new channels or VTGs in release 4.0(1). For more information about the Allow Latch attribute, refer to the Performing Cisco IPICS System Administrator Tasks chapter in the Cisco IPICS Server Administration Guide.
Performing a Direct Cisco IPICS Server Software Upgrade

If you have physical access to the Cisco IPICS server, you can upgrade the server software directly from the server. To do so, you must have the Cisco IPICS release 4.0(1) installation CD that is included with your product package. Be aware that you must log in as the root user to perform the Cisco IPICS upgrade. If you attempt to run the upgrade from any other user ID, the upgrade program returns an error and exits.
3-2
OL-21842-01
Chapter 3
Upgrading Cisco IPICS Performing a Direct Cisco IPICS Server Software Upgrade
Note
To terminate the upgrade process at any point in time, press Ctrl+C. To upgrade the Cisco IPICS server software directly, perform the following procedure:
Procedure
Step 1
Insert and mount the 4.0 IPICS software application installation CD.
[root]# mount /mnt/cdrom mount: block device /dev/hda is write-protected, mounting [root]# ls -ltr /mnt/cdrom
total 563500 -r-xr-xr-x 1 -r-xr-xr-x 1 -r-xr-xr-x 1 -r-xr-xr-x 1 root root root root root 47322321 Feb 24 root 529616588 Feb 24 root 7661 Feb 24 root 76279 Feb 24 01:03 01:04 20:49 20:49 upgrade-idc-4.0(0.xxx).zip install-ipics-4.0.0.xxx.run pre_ipics_db_upgrade_22_40 ipics_db_upgrade_22_40
[root]#
Step 2 Step 3
Copy the script pre_ipics_db_upgrade_22_40 on the installation CD to the Release 2.2 server under /root. Back up the Release 2.2 database using the following command.
[root]# pre_ipics_db_upgrade_22_40 <remote directory> <remote host IP> <User name> <password>
For example:
[root]# pre_ipics_db_upgrade_22_40 /root 10.3.2.1 root rootpwd
The output is saved to the file dbspaces_ipics22.tgz.
Note
The database backup process is different from the normal database backup that is available in the IPICS server. After you install Cisco IPICS Release 4.0, the file from the special backup created in Release 2.2 (dbspaces_ipics22.tgz) is required to replicate your database in Release 4.0.
Step 4
Save the dbspaces_ipics22.tgz file to a remote location under the same name.
3-3
Chapter 3 Performing a Direct Cisco IPICS Server Software Upgrade
Note
You must save the file to a remote location because the file is deleted as part of the new operating system installation.
Install the IPICS 4.0 operating system as described in the Installing the Cisco IPICS Operating System section on page 2-7. Install IPICS 4.0 application software as described in the Installing the Cisco IPICS Server Software section on page 2-16. Create a temp directory in the root directory on the IPICS 4.0 server, set the owner and permissions, and then verify the settings:
[root]# cd /root [root]# mkdir /temp [root]# chown informix:ipics /root/temp [root]# chmod 0770 /root/temp [root]# ls -ltr temp .... drwxrwx--2 informix ipics 4096 Mar .... [root]#
2 22:32 temp
Step 8 Step 9
Use SFTP to copy the database file dbspaces_ipics22.tgz to the /root/temp directory on the IPICS server. Use the following command to run the IPICS database upgrade script, where serverip is the server IP address and rootpwd is the root password.
Note
This process may take up to 30 minutes. Make sure that you allow time for the process to complete.
[root]# ipics_db_upgrade_22_40 /root/temp serverip root rootpwd
Sample output:
[root]# pre_ipics_db_upgrade_22_40 /dbupgradebackup ipics-standby root Very_R00ty INFO : Archive process for database upgrade started at Wed Dec 16 06:41:30 PST 2009 INFO : Stopping IPICS services INFO : IPICS services stopped successfully INFO : Generating archive control files (may take a few minutes)
3-4
OL-21842-01
Chapter 3
Upgrading Cisco IPICS Performing a Direct Cisco IPICS Server Software Upgrade
INFO INFO INFO INFO
Archive control files created
: Backing up IPICS database files (may take a few minutes) : Verifying archive file... : Archive of IPICS database files created successfully -----------------------------------------------------compressed uncompressed ratio uncompressed_name 11054629 475449344 97.7% /tmp/dbspaces_ipics22.tar INFO : Remote copying archive file to root@ipics-standby:/dbupgradebackup/dbspaces_ipics22.tgz INFO : Remote copy completed INFO : Archive process for database upgrade completed successfully at Wed Dec 16 06:45:22 PST 200 9 INFO : Restarting IPICS services Starting Ipics Database: [ OK ] [root]# service ipics restart Stopping tomcat: [ OK ] ipics_tomcat: Removing ipicsadmin cron entry to disable 'check_tomcat' daemon RCS is stopped Stopping ippe_dial_engine: Starting ippe_dial_engine: Starting CVD: Starting RCS: Starting tomcat:
[ [
OK OK
] ]
Step 10
After the database has been restored and the server has initialized, log in to the IPICS application as system administrator using a web browser: http://serveripaddress The license upgrade page opens. Browse, find, and upload the IPICS 4.0 Upgrade license provided by Cisco. Choose IDC Management > IDC Installer. Click Save.
3-5
Chapter 3 Performing a Direct Cisco IPICS Server Software Upgrade
If the IDC 4.0 IDC upgrade installer package has been overwritten by restoration of the 2.2 database, you must reload the new R4.0 IDC upgrade package on the IPICS server by performing the following steps:
Procedure
Step 1 Step 2
Copy the upgrade-idc-4.0(x.x).zip file from the IPICS server to the PC that you are using to access the IPICS server. Install the upgrade package, responding yes to the upload prompt, as shown:
[root]# sh install-ipics-4.x.run -- -i idc Verifying package integrity... All good. Uncompressing The Cisco IPICS Installer............................................................. ...................................................................... .................... Checking your server Operating System version...Ok. This command uploads the new IDC version to the Cisco IPICS server. The Cisco IPICS server must restart to complete this operation. The installer will automatically restart the server if you respond Yes, when prompted. Note: Be aware that a restart automatically logs all users out of Cisco IPICS. Do you want to upload the new IDC version now? (yes/no): [?] yes The installer is extracting the idc.zip file... The installer is verifying upgrade-idc-4.0(0.033).zip... The upgrade-idc-4.0(0.033).zip file was extracted successfully. restarting ipics_tomcat.. The ipics_tomcat service was restarted successfully. The Cisco IPICS installer completed successfully.
Step 3
Verify that the IPICS service is now running:

[root]# service ipics status IPPE Dial Engine status: CVD process (pid 11847) is running... Engine process (pid 13377) is running... DMS (pid 11979) is running... Radio Control Service status:
3-6
OL-21842-01
Chapter 3
Upgrading Cisco IPICS Performing a Remote Cisco IPICS Server Software Upgrade
RCS (pid 12266) is running... Node Manager status: Node Manager (pid 13524) is running... Tomcat status: Tomcat process (PID = 21028) is running... [root]#
Step 4 Step 5
Log in to the IDC and choose IDC Management > IDC Installer. Click Save. The package is now ready for download from the IDC Home page.
Performing a Remote Cisco IPICS Server Software Upgrade

This section describes the procedure that you follow to upgrade the Cisco IPICS server software from a PC or other device that is remotely connected to the network. To upgrade the Cisco IPICS server software from a remote location, perform the following procedure:
Procedure
Step 1
Transfer the installer file from the Cisco IPICS installation CD to the Cisco IPICS server by performing one of the following tasks:
Place the CD (or have someone place it for you) in the Cisco IPICS server and copy the installer file to the server. Follow the steps that are documented in Step 2 to perform this procedure. Place the CD in a PC and transfer the installer file to the Cisco IPICS server by using an SFTP client software program, such as SSH Secure Shell Client software (or similar software). Follow the steps that are documented in Step 3 to perform this procedure. Insert the Cisco IPICS installation CD in the server disk drive.
Step 2
To copy the installer file from the CD, perform the following steps:
a.
3-7
Chapter 3 Performing a Remote Cisco IPICS Server Software Upgrade
b.
Choose Start > Programs > SSH Secure Shell > Secure Shell Client to remotely connect to the Cisco IPICS server.
Note
The SSH idle timeout value is 120 minutes (two hours). Therefore, make sure that you do not leave an SSH remotely-connected session inactive for more than two hours; otherwise, the session times out.
Tip
If you do not have Secure Shell Client installed on your PC, use another secure client program. Click Quick Connect to connect to the Cisco IPICS server. The Connect to Remote Host window displays. In the Host field, enter the DNS host name or the IP address for your Cisco IPICS server; then, press the Tab key. In the User Name field, enter root. Click Connect. The Enter Password window displays. Enter the password for the root user and click OK. The SSH Secure Shell Client software window displays. Mount the contents of the CD onto the server by entering the following command:
[root]# mount /mnt/cdrom
c.
d. e. f.
g.
h.
i.
Navigate to the cdrom subfolder in the CD location by entering the following command:
j.
To view the installer file, enter the following command:

[root]# ls -l

k.
Locate the installer file in the directory listing. The Cisco IPICS installer file has a .run file extension.
3-8
OL-21842-01
Chapter 3
l.
Copy the installer file to the /root directory by entering the following command:
[root]# cp /mnt/cdrom/<installerfilename>.run /root
where: <installerfilename>.run represents the name of the .run file that was displayed in Step j. The installer file copies from the CD to the /root directory.
m.
Navigate from the /mnt/cdrom directory to an internal directory on your server by entering the following command:
[root]# cd <serverdirectory>
where: <serverdirectory> is an internal directory or subdirectory on your server.

n.
To unmount the installation CD and eject it from the disk drive, enter the following command:
[root]# eject
Note
You must navigate away from the /mnt/cdrom directory and enter the eject command to unmount the contents of the CD and eject the CD from the server. If you try to eject the CD by pushing the eject button on the server, the CD will not eject. To continue with the upgrade, proceed to Step 4. Insert the Cisco IPICS installation CD in the CD drive of your PC. Choose Start > Programs > SSH Secure Shell > Secure File Transfer Client to open the Secure File Transfer Client.
o. Step 3
To transfer the file to the server from a remote location, follow these steps:
a. b.
Note
If you do not have Secure File Transfer Client installed on your PC, use another program that permits a secure file transfer session between your PC and the server.
3-9
Chapter 3 Performing a Remote Cisco IPICS Server Software Upgrade
The SSH Secure Shell File Transfer Client window displays. The desktop of your PC displays in the left pane.
c.
Click Quick Connect to connect to the Cisco IPICS server. The Connect to Remote Host window displays. In the Host field, enter the DNS host name or the IP address for your Cisco IPICS server. Then, press the Tab key. In the User Name field, enter root. Click Connect. The Enter Password window displays. Enter the password for the root user and click OK. The SSH Secure Shell File Transfer Client connects to the Cisco IPICS server and displays the contents of the /root directory in the right pane of the window.
d. e. f.
g.
h.
In the left pane of the window, navigate to the folder on your PC that corresponds to the location of the Cisco IPICS installation CD (for example, My Computer\Compact Disk Z:). Double-click the CD folder to browse the contents of the CD. The contents of the CD displays. Double-click the cdrom subfolder to browse its contents. Locate the installer file in the cdrom subfolder on the CD. The installer file has an extension of .run. Drag the installer file from the left pane of the window to the right pane to initiate the copy procedure. A progress window displays while the file copies to the /root directory of the server. After the copy procedure completes, the installer file displays in the right pane.
i.
j. k.
l.
m. Step 4 Step 5 Step 6
Close the SSH Secure Shell File Transfer Client.
Open a terminal window to the Cisco IPICS server by using SSH Secure Shell Client software or similar software. In the User Name field, enter root. Click Connect.
3-10
OL-21842-01
Chapter 3
The Enter Password window displays.

Step 7
Enter the password for the root user and click OK. The SSH Secure Shell Client software window displays. To view the installer file, enter the following command:
[root]# ls -l
Step 8
The contents of the /root directory display.

Step 9
Locate the installer file in the directory listing. The Cisco IPICS installer file has a .run file extension. Change the access mode of the installer file by entering the following command:
[root]# chmod 550 <installerfilename>.run
Step 10
where: <installerfilename>.run represents the name of the installer file.
Note
Step 11
Run the installer from a SSH Secure Shell Client software (or similar software) window by following the procedure as described in the Performing a Direct Cisco IPICS Server Software Upgrade section, starting with Step 9.
3-11
Chapter 3 Upgrading the Radio Descriptor
Upgrading the Radio Descriptor

After upgrading a 2.2 system to 4.0, you must upgrade all existing EF Johnson radio descriptors that have control functions defined by performing the following steps:
Procedure
Step 1
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>
Step 2 Step 3
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"> <Action type="pressed"> <Command> <SetMonitorMode value="ON" /> </Command> </Action> </State> <State shortName="OFF" longName="OFF" description="Monitor mode is off" user_selectable="true"> <Action type="pressed"> <Command> <SetMonitorMode value="OFF" /> </Command> </Action> </State> <State shortName="UNKWN" longName="UNKNOWN" description="Monitor m ode is in an unknown state" user_selectable="false"> <Action type="pressed"> <Command> <SetMonitorMode value="UNKNOWN" /> </Command> </Action> </State> <State shortName="UNSPRT" longName="UNSUPPORTED" description="Moni tor mode is not supported" user_selectable="false">
3-12
OL-21842-01
Chapter 3
Upgrading Cisco IPICS Upgrading the Radio Descriptor
<Action type="pressed"> <Command> <SetMonitorMode value="UNSUPPORTED" /> </Command> </Action> </State> </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"> <Action type="pressed"> <Command> <SetRepeaterTaMode value="REPEATER" /> </Command> </Action> </State> <State shortName="TA" longName="TALKAROUND" description="Transmit mode is set to TALKAROUND" user_selectable="true"> <Action type="pressed"> <Command> <SetRepeaterTaMode value="TALKAROUND" /> </Command> </Action> </State> <State shortName="UNKWN" longName="UNKNOWN" description="Repeater/ Talkaround mode is in an unknown state" user_selectable="false"> <Action type="pressed"> <Command> <SetRepeaterTaMode value="UNKNOWN" /> </Command> </Action> </State> <State shortName="UNSPRT" longName="UNSUPPORTED" description="Repe ater/TA mode selection is not supported" user_selectable="false"> <Action type="pressed"> <Command> <SetRepeaterTaMode value="UNSUPPORTED" /> </Command> </Action> </State> </Stateful> <Stateful shortName="SCN" longName="Scan" description="Set Scan Mode " presentation="multiple">
3-13
<Stateful shortName="ON" longName="ON" description="Scan is on" us er_selectable="true"> <Action type="pressed"> <Command> <SetScanMode value="ON" /> </Command> </Action> </State> <Stateful shortName="OFF" longName="OFF" description="Scan is off" user_selectable="true"> <Action type="pressed"> <Command> <SetScanMode value="OFF" /> </Command> </Action> </State> <Stateful shortName="UNKWN" longName="UNKNOWN" description="Scan i s in an unknown state" user_selectable="false"> <Action type="pressed"> <Command> <SetScanMode value="UNKNOWN" /> </Command> </Action> </State> <Stateful shortName="UNSPRT" longName="UNSUPPORTED" description="S can is not supported" user_selectable="false"> <Action type="pressed"> <Command> <SetScanMode value="UNSUPPORTED" /> </Command> </Action> </State> </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"> <Action type="pressed"> <Command> <SetSecureTxMode value="SECURE" /> </Command> </Action> </State> <Stateful shortName="CLR" longName="CLEAR" description="Secure tra nsmit mode is set to CLEAR" user_selectable="true"> <Action type="pressed"> <Command>
3-14
OL-21842-01
Chapter 3
<SetSecureTxMode value="CLEAR" /> </Command> </Action> </State> <Stateful shortName="KEYFL" longName="KEYFAIL" description="Keyfai l. Key required for encryption is not present" user_selectable="false" > <Action type="pressed"> <Command> <SetSecureTxMode value="KEYFAIL" /> </Command> </Action> </State> <Stateful shortName="NOENC" longName="NO_ENCRYPT" description="No encryption module present" user_selectable="false"> <Action type="pressed"> <Command> <SetSecureTxMode value="NO_ENCRYPT" /> </Command> </Action> </State> <Stateful shortName="MSMTCH" longName="MISMATCH" description="Mism atch between user selected secure transmit mode and actual fixed/strap ped tx mode" user_selectable="false"> <Action type="pressed"> <Command> <SetSecureTxMode value="MISMATCH" /> </Command> </Action> </State> <Stateful shortName="UNKWN" longName="UNKNOWN" description="Secure /Clear Transmit mode is in an unknown state" user_selectable="false"> <Action type="pressed"> <Command> <SetSecureTxMode value="UNKNOWN" /> </Command> </Action> </State> <Stateful shortName="UNSPRT" longName="UNSUPPORTED" description="E ncryption is not supported" user_selectable="false"> <Action type="pressed"> <Command> <SetSecureTxMode value="UNSUPPORTED" /> </Command> </Action> </State> </Stateful>
3-15
<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"> <Action type="pressed"> <Command> <SetTxPowerMode value="HIGH" /> </Command> </Action> </State> <Stateful shortName="LOW" longName="LOW" description="Transmit pow er mode is set to LOW" user_selectable="true"> <Action type="pressed"> <Command> <SetTxPowerMode value="LOW" /> </Command> </Action> </State> <Stateful shortName="UNKWN" longName="UNKNOWN" description="Transm it power mode is in an unknown state" user_selectable="false"> <Action type="pressed"> <Command> <SetTxPowerMode value="UNKNOWN" /> </Command> </Action> </State> <Stateful shortName="UNSPRT" longName="UNSUPPORTED" description="T ransmit power mode selection is not supported" user_selectable="false" > <Action type="pressed"> <Command> <SetTxPowerMode value="UNSUPPORTED" /> </Command> </Action> </State> </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"> <Action type="pressed"> <Command> <SetEmergencyMode value="ON" /> </Command> </Action> </State>
3-16
OL-21842-01
Chapter 3
<Stateful shortName="OFF" longName="OFF" description="Emergency mo de is off" user_selectable="true"> <Action type="pressed"> <Command> <SetEmergencyMode value="OFF" /> </Command> </Action> </State> <Stateful shortName="UNKWN" longName="UNKNOWN" description="Emerge ncy mode is in an unknown state" user_selectable="false"> <Action type="pressed"> <Command> <SetEmergencyMode value="UNKNOWN" /> </Command> </Action> </State> <Stateful shortName="UNSPRT" longName="UNSUPPORTED" description="E mergency mode is not supported" user_selectable="false"> <Action type="pressed"> <Command> <SetEmergencyMode value="UNSUPPORTED" /> </Command> </Action> </State> </Stateful> </ControlFunctions>
Step 4
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. Select the modified descriptor and click Update. Choose the descriptor type and click Browse to locate and upload the file. Click Save. To insure 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, use SSH to access the IPICS server as root, and then enter the following command:
[root]# service ipics_rcs restart
Step 5 Step 6 Step 7 Step 8 Step 9 Step 10
3-17
Wait a few minutes before attempting to control any radio.
3-18
OL-21842-01
CH A P T E R
Uninstalling Cisco IPICS

This chapter provides information about the procedures that you need to follow to uninstall the Cisco IPICS server software. You can perform the uninstallation procedure in one of the following ways:

From the Cisco IPICS server by using a terminal console From a remote PC on the network by using SSH Secure Shell Client software (or similar software) Uninstalling the Cisco IPICS Server Software from the Server, page 4-2 Uninstalling the Cisco IPICS Server Software Remotely, page 4-3
This chapter includes the following sections:

Note
The Cisco IPICS uninstallation procedure removes all of the components and directories that were created during the Cisco IPICS installation. If you intend to reinstall Cisco IPICS at a later time, Cisco recommends that you back up your database and log files before you begin the uninstallation process. For information about backing up files, refer to the Performing Cisco IPICS Backup and Restore Operations chapter of the Cisco IPICS Server Administration Guide.
4-1
Chapter 4 Uninstalling the Cisco IPICS Server Software from the Server
Note
Be aware that when you uninstall and reinstall the Cisco IPICS software, communications are temporarily disrupted. Upon reinstallation, Cisco IPICS disconnects VTGs and SIP-based IDC clients that were using RMS resources so that the voice ports become available for use.
Uninstalling the Cisco IPICS Server Software from the Server

To uninstall the Cisco IPICS software directly from the Cisco IPICS server, perform the following procedure:
Procedure
Step 1
Access the Cisco IPICS server by using a terminal console. Cisco IPICS displays the following text: Cisco IPICS hostname login: where: hostname specifies the host name of the Cisco IPICS server. Enter root in the hostname login: field; then, press Enter. Cisco IPICS prompts you for the password for the root user. Enter the password for the root user; then, press Enter. To navigate to the directory where the uninstaller file is located, enter the following command:
[root]# cd _uninstall_IPICS
Step 2
Step 3 Step 4
Step 5
To begin the uninstallation process, enter the following command:

[root]# bash uninstall-ipics
4-2
OL-21842-01
Chapter 4
Uninstalling Cisco IPICS Uninstalling the Cisco IPICS Server Software Remotely
The uninstallation program prompts you to confirm the uninstallation process by displaying the following text:
Do you want to remove Cisco IPICS software? (YES/NO):
Step 6
To confirm the uninstallation process, enter y or yes. Cisco IPICS begins the uninstallation process.
Note
Be aware that the Cisco IPICS uninstallation process permanently removes the Cisco IPICS software and deletes any Cisco IPICS configuration data that you have stored in the server. If you need to save your data, Cisco recommends that you first back up your data to a remote host before you uninstall the software. For more information about backing up your data, refer to the Performing Cisco IPICS Backup and Restore Operations chapter of the Cisco IPICS Server Administration Guide. After you have preserved a copy of your data, you can restart the uninstallation process.
The uninstaller begins to uninstall the Cisco IPICS components. After the uninstaller has finished removing the files, a message displays to prompt you to reboot the server.
Step 7
To reboot the system, enter y or yes. After the system reboots, the Cisco IPICS server software is removed.
Uninstalling the Cisco IPICS Server Software Remotely

To uninstall the Cisco IPICS server software from a PC on the network, perform the following procedure:
4-3
Chapter 4 Uninstalling the Cisco IPICS Server Software Remotely
Procedure
Step 1
Use SSH Secure Shell Client software (or similar software) to connect to the server from your local workstation by choosing Start > Programs > SSH Secure Shell > Secure Shell Client. The SSH Secure Shell Client software window displays. The desktop of your PC displays in the left pane.
Step 2
To open a window to enter the server IP address, click Quick Connect on the button menu. The Connect to Remote Host window displays. In the Host field, enter the IP address or the DNS name for your Cisco IPICS server. Then, press Tab. In the User Name field, enter root. Then, click Connect. The Enter Password window displays. Enter the root password; then, click OK. The SSH Secure Shell Client connects to the Cisco IPICS server and displays a command prompt for the root user.
Step 3 Step 4
Step 5
Step 6
To change directories, enter the following command:

[root]# cd _uninstall_IPICS
Step 7
To begin the uninstallation process, enter the following command:

[root]# bash uninstall-ipics
The uninstallation program prompts you to confirm the uninstallation process by displaying the following text:
Do you want to remove Cisco IPICS software? (YES/NO):
Step 8
To continue the uninstallation program, enter y or yes. Cisco IPICS begins the uninstallation process.
Caution
Be aware that the Cisco IPICS uninstallation process permanently removes the Cisco IPICS software and deletes any Cisco IPICS configuration data that you have stored in the server. If you need to save your data, Cisco recommends that you first back up your data to a remote host before you uninstall the software. For more information about backing up your data, refer to the Performing
4-4
OL-21842-01
Chapter 4
Uninstalling Cisco IPICS Uninstalling the Cisco IPICS Server Software Remotely
Cisco IPICS Backup and Restore Operations chapter of the Cisco IPICS Server Administration Guide. After you have preserved a copy of your data, you can restart the uninstallation process. The uninstaller begins to uninstall the Cisco IPICS components. After the uninstaller has finished removing the files, a message displays to prompt you to reboot the server.
Step 9
Enter y or yes to reboot the system. After the system reboots, the Cisco IPICS server software is removed. To close the SSH Secure Shell Client window, click X.
Step 10
4-5
Chapter 4 Uninstalling the Cisco IPICS Server Software Remotely
4-6
OL-21842-01
CH A P T E R
Troubleshooting Cisco IPICS Installation Issues

The issues that are described in this section may occur during, or as a result of, installing the Cisco IPICS operating system or the Cisco IPICS server software. Refer to the following sections in the Cisco IPICS Troubleshooting Guide for information about the following components of Cisco IPICS:
For information about troubleshooting the IDC application, refer to the Troubleshooting Tips for the IDC Application chapter in the Cisco IPICS Troubleshooting Guide For information about troubleshooting license issues, refer to the Troubleshooting License Issues section of the Troubleshooting the Cisco IPICS Server chapter in the Cisco IPICS Troubleshooting Guide. No Network Connectivity After Connecting the Ethernet Cable to Interface 1 on the Server, page 5-2 The Cisco IPICS Operating System Detects Unsupported Hardware, page 5-2 The Server Cannot Allocate Partitions, page 5-3 Troubleshooting Bad Interpreter: Permission Denied Errors, page 5-3 Troubleshooting Permission Denied Errors, page 5-4 SSH Loses Connectivity While You Perform a Remote Server Software Installation, page 5-5 You Cannot Connect to the Server By Using Your Browser, page 5-5 Cisco IPICS Displays an Authorization Error, page 5-11
This chapter includes the following sections:

OL-21842-01
5-1
Chapter 5 Troubleshooting Cisco IPICS Installation Issues No Network Connectivity After Connecting the Ethernet Cable to Interface 1 on the Server
No Network Connectivity After Connecting the Ethernet Cable to Interface 1 on the Server
Problem After you install the Cisco IPICS operating system software, you cannot connect your server to the network. The Ethernet cable is connected to Ethernet interface 1 on the server. The connection uses DHCP. Solution If your interfaces are labeled 1 and 2, the server might map the eth0 port
to interface 2. Connect the Ethernet cable to interface 2 on your server and try to reestablish connectivity, or consult your server documentation to determine the mapping scheme for the eth0 port.
Note
If your interfaces are labeled NIC 1 and NIC 2, connect the Ethernet cable to the NIC 1 interface.
The Cisco IPICS Operating System Detects Unsupported Hardware

Problem When you install the Cisco IPICS operating system software, a message
displays to inform you that the hardware platform is not supported.

Solution The installation program includes hardware detection logic that checks
for supported parameters on the server. If any of the parameters do not match with the information that is contained in the installation program, an unsupported hardware message displays. For instance, if you install the Cisco IPICS operating system on a supported server model that does not have the required amount of memory installed, the installation program detects an unsupported parameter. In this case, the server model is actually supported, but because there is insufficient memory to support Cisco IPICS, the message displays. Make sure that you check the Cisco IPICS Compatibility Matrix at the following URL for the most current versions of compatible hardware components, including memory requirements, and software versions for use with Cisco IPICS: http://www.cisco.com/en/US/products/ps7026/ tsd_products_support_series_home.html
5-2
OL-21842-01
Chapter 5
Troubleshooting Cisco IPICS Installation Issues The Server Cannot Allocate Partitions
The Server Cannot Allocate Partitions

Problem When you attempt to install the Cisco IPICS operating system software, the server displays the following error message:
Could not allocate requested partitions: Partitioning Failed: Could not allocate partitions Press OK to reboot system.
Solution You may encounter this error if the server does not have sufficient hard
disk space. Make sure that no hard disks have been removed from your server; your server must have 160 GB of hard disk space to function properly with the Cisco IPICS operating system. For more information, refer to the Cisco IPICS Compatibility Matrix.
Troubleshooting Bad Interpreter: Permission Denied Errors

Problem You attempt to install the Cisco IPICS server software by using the following command, and the installer displays a bad interpreter error that is similar to the following example:
[root]# ./ipics-installer.run ./ipics-installer.run -bash: ./ipics-installer.run: /bin/bash: bad interpreter: Permission denied
where: ipics-installer.run represents the name of the Cisco IPICS installer file that you are attempting to run.
Solution The shell interpreter script for the Cisco IPICS operating system
misinterprets the ./ command. To fix this problem, replace ./ with the bash command, as shown in the following example:
[root]# bash <name-of-installer-file>.run
where:
5-3
Chapter 5 Troubleshooting Permission Denied Errors
<name-of-installer-file>.run represents the name of the Cisco IPICS installer file that you are attempting to run.
Troubleshooting Permission Denied Errors

Problem When you start the Cisco IPICS server software installation, the installer displays a permission denied error message that is similar to the following example:
[root]# bash ipics-installer.run -bash: bash ipics-installer.run: Permission denied
where: ipics-installer.run represents the name of the Cisco IPICS installer file that you are attempting to run.
Solution The secure copy or SFTP program saved the .run file as a read-only file and the system cannot run the file. Modify the file to so that the system can run it, as shown in the following example:
[root] # chmod 550 <name-of-installer-file>.run
where: <name-of-installer-file>.run is the name of the Cisco IPICS installer file.
Note
5-4
OL-21842-01
Chapter 5
Troubleshooting Cisco IPICS Installation Issues SSH Loses Connectivity While You Perform a Remote Server Software Installation
SSH Loses Connectivity While You Perform a Remote Server Software Installation
Problem When you perform a remote installation of the Cisco IPICS server software, the SSH program loses connectivity with the server and the installation does not complete. Solution Reconnect to the server by using SSH; then, retry the remote server
software installation by performing the procedure in the Performing a Remote Cisco IPICS Server Software Installation section on page 2-21.
Note
Make sure that the SSH program has uninterrupted connectivity to the server while the installation program runs; even a momentary loss of connectivity can terminate the program.
You Cannot Connect to the Server By Using Your Browser

Problem After you install Cisco IPICS, you enter the IP address or the host name
for the Cisco IPICS server into a supported browser but you cannot contact the server.
Solution If you cannot connect to the Cisco IPICS server through a browser, one
of the following situations may have occurred:

You entered the incorrect IP address or DNS name for the Cisco IPICS server The tomcat service is not running The database server is not running A security setting on your computer has caused a required JavaScript add-on to become disabled
To diagnose the problem, perform the following procedure:
5-5
Chapter 5 You Cannot Connect to the Server By Using Your Browser
Procedure
Step 1
Make sure that the URL that you entered is correct by performing the following actions:

Ensure that you are using the secure HTTP URL, https:// in the URL address field. Check that you entered in to the browser the correct IP address for the Cisco IPICS server. If you entered the DNS name for the server, ensure that the DNS name is correct and that your network is able to resolve the DNS name. If you conclude that your network is not resolving the server DNS name correctly, enter the IP address in the URL address field.
Step 2
If you still cannot access the Administration Console, Log in to the Cisco IPICS server with the root user ID by performing one of the following actions:
Use a terminal console to log in to the server by following these steps:

a. Connect to the server by using a terminal console. a. Log in to the server by entering root for the user name. b. When you are prompted, enter the root user password.
Log in to the server remotely by following these steps:

a. Open a terminal window by using SSH Secure Shell Client software or
similar software.
b. Log in to the server by entering the IP address or host name of the server. c. Log in by using the root user ID by entering root for the user name. d. When you are prompted, enter the root user password.
Note
You might not be able to connect to the server remotely if your server is experiencing network connectivity problems; in this case, connect to the server by using a terminal console.
A terminal window displays.

Step 3
Ensure that the tomcat service is running by entering the following command:
[root]# service ipics_tomcat status
5-6
OL-21842-01
Chapter 5
Troubleshooting Cisco IPICS Installation Issues You Cannot Connect to the Server By Using Your Browser
Step 4
Perform one of the following actions, depending on the output that you receive:
If the tomcat service is running, you receive output that is similar to the following example:
[root]# service ipics_tomcat status Tomcat process (pid: 24025) is running on the system
If you receive output that indicates that the tomcat service is running, continue to Step 8.
If the tomcat service is not running, you receive output that is similar to the following example:
[root]# service ipics_tomcat status PID_SEARCH_RESULT= Tomcat is not running on the system.
If you receive output that indicates that the tomcat service is not running, restart the tomcat service and the policy engine by entering the following command:
[root]# service ipics restart
Note
Be aware that Cisco IPICS cancels any active dial-in or dial-out calls when you enter the service ipics restart command.
Step 5
If the tomcat service does not run after you restart it manually, perform the following actions:
a.
Check whether Cisco IPICS already installed the crontab file by entering the following command:
[root]# crontab -l -u ipicsadmin
Note
The crontab file runs a process that checks if the tomcat service and database are running, and starts them if they are not running. If the crontab command returns a message that is similar to the following message, the tomcatcron file already exists. Continue to Step 8.
[root]# crontab -l -u ipicsadmin #-------------------------------------------------------------#
b.
5-7
# Module: ipicsadmin.cron - Cisco IPICS cron file for user 'ipicsadmin' # # Usage: crontab < ipicsadmin.cron # # Environment Variables: # #--------------------------------------------------------------SHELL=/bin/sh MAILTO=root HOME=/opt/cisco/ipics/tomcat * * * * * /opt/cisco/ipics/bin/check_tomcat >> /opt/cisco/ipics/tomcat/current/logs/ipicsadmin_cron.log 2>&1
c.
If the crontab command returned a message such as no crontab for ipicsadmin, install the crontab file by entering the following command:
[root]# crontab /opt/cisco/ipics/cron/ipicsadmin.cron
Cisco IPICS installs the crontab file. Almost immediately, Cisco IPICS starts the tomcat service. You can then log in to the Administration Console by using your browser. For information about starting and restarting the Cisco IPICS tomcat service, see the Performing Tomcat Service Procedures section in the Troubleshooting Cisco IPICS Network Processes chapter in the Cisco IPICS Troubleshooting Guide.
Step 6
To check the status of the database, enter the following command:

[root]# onstat -
If the database is online and running, the command returns output that is similar to the following example.
IBM Informix Dynamic Server Version 10.00.UC1 00:16:14 -- 124036 Kbytes -- On-Line -- Up
If the database is not running, the command returns output that is similar to the following example.
shared memory not initialized for INFORMIXSERVER 'IPICSDBServer'
If the command output indicates that the database is not running, continue to Step 7.
5-8
OL-21842-01
Chapter 5
Troubleshooting Cisco IPICS Installation Issues You Cannot Connect to the Server By Using Your Browser
Step 7
If the database is not running, manually start the database server by entering the following command:
[root]# service ipics_db start
Step 8
To verify that the static IP address, subnet mask, and default gateway are properly configured, check your IP connectivity by entering the following command: ping <default gateway IP address> where: <default gateway IP address> represents the default gateway address for your network.
Step 9
If the ping command is not successful, unplug the network cable from interface 1 on the server and connect it to interface 2.
Note
Generally, for servers that label their Ethernet interfaces as NIC 1 and NIC 2, you connect the Ethernet cable to the NIC 1 interface; this interface is usually the eth0 interface. For servers that label their Ethernet interfaces as 1 and 2, it is possible that the eth0 interface is mapped to interface 2. Consult your server product documentation to confirm the interface mapping.
Step 10 Step 11
Retry Step 8 to verify server network connectivity. If the ping command is successful, log in to another server on the network and attempt to ping the Cisco IPICS server. If the ping command is not successful, troubleshoot the network connectivity with your network administrator.
5-9
Step 12
Check the security settings for the computer from which you are attempting to access the Administration Console.
Note
For enhanced security, Cisco recommends that you review and follow the recommendations that are included in the Windows XP Security Guide. To find this document, refer to the Microsoft support site at http://support.microsoft.com/ and search for Windows XP Security Guide.
When you follow the recommendations that are included in the Windows XP Security Guide and deny all add-ons, except those that are specifically allowed in the add-on list, you may encounter a problem where you cannot access the Cisco IPICS server Administration Console. This issue occurs when you use Internet Explorer from a PC that runs Microsoft Windows XP SP2 and have not enabled the JavaScript GUID in the add-on list. To resolve this issue and ensure proper operation from Internet Explorer, you must explicitly enable the following JavaScript GUID add-on on your IDC client machine: GUID: {F414C260-6AC0-11CF-B6D1-00AA00BBBB58} - JavaScript For detailed information about how to enable this add-on, refer to the Microsoft support site at http://support.microsoft.com/ and search for Article ID 555235.
Step 13
Retry accessing the server by entering the following URL in the supported browser: https://<ipaddress> | <dnsname> where: <ipaddress> or <dnsname> represents the IP address or DNS name of the server. If you still cannot access the server, contact your Cisco technical support representative for assistance.
5-10
OL-21842-01
Chapter 5
Troubleshooting Cisco IPICS Installation Issues Cisco IPICS Displays an Authorization Error
Cisco IPICS Displays an Authorization Error

Problem After installing Cisco IPICS, you log in to the Administration Console
and receive an authorization error.

Solution An authorization error may occur in one of the following circumstances:
You may have entered an incorrect user name or password The database server may not have started.
To resolve this problem, perform the following procedure:

Procedure
Step 1
Before you check the status of the database server, verify that you entered the correct user name and password, and that the Caps Lock setting is not on. If you confirm that you entered the correct login information for the Cisco IPICS Administration Console and still receive an authorization error, you must check the status of the database. Continue to Step 3.
Step 2
Access the Cisco IPICS server by using a terminal console. Cisco IPICS displays the following text: Cisco IPICS hostname login: with hostname being the host name of the Cisco IPICS server.
Step 3
Enter root in the hostname login: field and press Enter. Cisco IPICS prompts you for the password for the root user. Enter the password for the root user and press Enter. To check the status of the database, enter the following command:
[root] #onstat -
Step 4 Step 5
If the database is online and running, the command returns a response that is similar to the following example:
IBM Informix Dynamic Server Version 10.00.UC1 00:16:14 -- 124036 Kbytes -- On-Line -- Up
5-11
Chapter 5 Cisco IPICS Displays an Authorization Error
If the database is not running, the command returns a response that is similar to the following example:
shared memory not initialized for INFORMIXSERVER 'IPICSDBServer'
Step 6
If the database is not running, manually start the database by entering the following command:
[root] #service ipics_db start
5-12
OL-21842-01
GLOSSARY
A
activated
A VTG state that indicates that the SIP (unicast) line or multicast line is fully operational. The PTT and volume indicators appear highlighted. A VTG state that becomes effective when the Activate button is clicked. The Activate button appears highlighted while the other IDC buttons remain in an inactive state as the system attempts to activate and connect. This button toggles activate and deactivate functionality on the IDC. Click this button on the IDC to activate a channel (to call out); click it again to deactivate the channel. A virtual talk group (VTG) becomes active when Cisco IPICS commits global resources, such as a multicast address and any necessary dial-in peers, so that the participants in the VTG can communicate with each other. The graphical user interface (GUI) in the Cisco IPICS server software through which authorized Cisco IPICS users can manage and configure Cisco IPICS resources, events and VTGs. A radio system under one administrative control; also known as a management domain. This system is usually mapped to an agency.
activating
activation button
active virtual talk group
Administration Console
autonomous system
B
backward compatibility
The ability of newer radio equipment to operate within an older system infrastructure or to directly intercommunicate with an older radio unit. The term usually applies to digital radios that are also capable of analog signal transmission.
GL-1
Glossary
bandwidth
The difference between the highest and lowest frequencies that are available for network signals. The term also describes the rated throughput capacity of a specific network medium or protocol. Bandwidth specifies the frequency range that is necessary to convey a signal measured in units of hertz (Hz). For example, voice signals typically require approximately 7 kHz of bandwidth and data traffic typically requires approximately 50 kHz of bandwidth. A land station in the land mobile radio service. In the personal communication service, the common name for all the radio equipment that is located at one fixed location and used for serving one or several calls.
base station
C
CAI
common air interface. The standard for the digital wireless communications medium that is employed for P25-compliant radio systems and equipment. The standard for P25 Phase I incorporates Frequency Division Multiple Access (FDMA) technology. Radio terminology that defines a call as beginning at the moment that you press the transmit key and concluding when you release the transmit key. The term per call implies that some form of control causes the radio to select a specific frequency before it transmits audio. Some radios may be configured to automatically return to a predefined RF channel when the call ends. The delay that occurs when there is no idle channel or facility available to immediately process a call that arrives at an automatic switching device. The time that is required to establish a circuit-switched call between users or terminals. A wave that is suitable for modulation by an information-bearing signal. channel associated signaling. The transmission of signaling information within the voice channel. CAS signaling often is referred to as robbed-bit signaling because user bandwidth is being robbed by the network for other purposes.
call
call delay
call setup time
carrier CAS
GL-2
OL-21842-01
Glossary
channel
A communication path that is wide enough to permit a single RF transmission. Multiple channels can be multiplexed over a single cable in certain environments. There are many different types of channels in Cisco IPICS, including direct dial, 2-way, VTGs, and radio channels. Channels can be dynamically or statically allocated. Channels may have one or more channel connections that define the source for the channel. See PTT channel. The maximum possible information transfer rate through a channel, subject to specified constraints. One or more methods by which a content stream can be obtained. For instance, a particular channel may be found on several different multicast addresses in different locations and also on several different radios at different locations. A logical grouping of channels
channel capacity
channel connection
channel folder
channel select check Provides the ability to select or deselect the specified channel on the IDC for box audio transmission. channel spacing
The distance from the center of one channel to the center of the next-adjacent-channel. Typically measured in kilohertz. The software-based call-processing component of the Cisco IP telephony solution. Cisco Unified Communications Manager (CallManager) extends enterprise telephony features and functions to packet telephony network devices, such as Cisco Unified IP Phones, media processing devices, VoIP gateways, and multimedia applications. Cisco IP Interoperability and Collaboration System. The Cisco IPICS system provides an IP standards-based solution for voice interoperability by interconnecting voice channels, talk groups, and VTGs to bridge communications amongst disparate systems. Integrated with the Cisco IPICS server, this component enables telephony dial functionality and is responsible for the management and execution of policies and user notifications.
Cisco Unified Communications Manager (CallManager)
Cisco IPICS
Cisco IPICS policy engine
GL-3
Glossary
Cisco IPICS server
Provides the core functionality of the Cisco IPICS system. The Cisco IPICS server software runs on the Linux operating system on selected Cisco Media Convergence Server (MCS) platforms. The server software includes an incident management framework administration GUI that enables dynamic resource management for users, channels, and VTGs. The server also includes the Cisco IPICS policy engine, which enables telephony dial functionality and is responsible for the management and execution of policies and user notifications. A full-featured telephone that provides voice communication over an IP network. A user can participate in a PTT channel or VTG by using a Cisco Unified IP Phone as a PTT device. Provides threat protection for server and desktop computing systems (endpoints) by identifying, preventing, and eliminating known and unknown security threats. command-line interface. An interface that allows the user to interact with the operating system by entering commands and optional arguments. coder-decoder. 1. Integrated circuit device that typically uses pulse code modulation to transform analog signals into a digital bit stream and digital signals back into analog signals. 2. In Voice over IP, Voice over Frame Relay, and Voice over ATM, a DSP software algorithm that is used to compress/decompress speech or audio signals.
Cisco Unified IP Phone
Cisco Security Agent CLI
codec
conference of conferences conventional radio system COR
A conference that consists of two or more VTGs. A non-trunked system that is similar to telephone party-line in that the user determines availability by listening for an open channel. carrier operated relay. An electrical signal that is used to signal when a radio is receiving traffic. In radio communications, the geographical area that is within the range of, or that is covered by, a wireless radio system to enable service for radio communications. Also referred to as service delivery area.
coverage
GL-4
OL-21842-01
Glossary
D
delay time decrypt
The sum of waiting time and service time in a queue. Cryptographically restore ciphertext to the plaintext form it had before encryption. Reverse application of an encryption algorithm to encrypted data, thereby restoring that data to its original, unencrypted state. Scripts that the Cisco IPICS dial engine executes to provide the telephony user interface (TUI) for interaction with incoming and outgoing phone calls. A phone call that is dialed in to the policy engine. A feature that allows one dial-in user, at a time, to talk in a VTG or a channel. The telephony user interface provides this dial-in floor control feature to support dial-in users. It does not provide support for floor control for other PTT users. The phone number that is used by the policy engine and the SIP provider and configured in the Dial Information pane in the Ops Views window. Dialing this number provides user access to the telephony user interface. An action that invites selected user(s) to the selected VTG. A phone call that is dialed out by the policy engine to a phone user to invite the user in to a talk group.
decryption
dial engine scripts
dial-in dial-in floor control
dial number
dial out invite
dial peer
Addressable call endpoint. In Voice over IP, there are two kinds of dial peers: POTS and VoIP. A numeric identifier that is chosen by a Cisco IPICS user and stored in the user profile. Cisco IPICS uses this ID and a numeric password to authenticate a Cisco Unified IP Phone user. A technique for placing a digital data sequence on a carrier signal for subsequent transmission through a channel. Any tone that is sent without any summed or added tone. For example, adding a function tone with a low level guard tone may impact the recognition of the function tone. Contrast with mixed tones.
digit ID
digital modulation technique discrete tone
GL-5
Glossary
dispatcher
The Cisco IPICS dispatcher is responsible for setting up the VTGs, activating the VTGs to begin conferences, and adding and/or removing participants in inactive VTG and active VTGs. The dispatcher also monitors the active VTGs and events, can mute and unmute IDC users, as necessary, and manages policies, which activate/deactivate VTGs based on specific criteria and designated intervals. Policy management activities include create/modify/delete policies, view policies, execute policies, and activate privileges. digital service zero (0). Single timeslot on a DS1 (also known as T1) digital interfacethat is, a 64-kbps, synchronous, full-duplex data channel, typically used for a single voice connection on a PBX. dual tone multi-frequency. The signal to the phone company that you generate when you press keys on a telephone keypad. With DTMF, each key that you press on your phone (0 through 9, * and #) generates two tones of specific frequencies; one tone is generated from a high frequency group of tones and the other from a low frequency group. Voice gateways often strip these inband tones and present them out-of-band in SIP, H.323, or other messages. The controls that are used to preset radio characteristics so that channels are available to clients.
DS0
DTMF
dynamic radio channel (dynamic control)
dynamic regrouping A trunking system feature that allows multiple radios to be placed upon a
specific talk group without manual manipulation of the programming of the radios. Dynamic regrouping is initiated through a system control console and transmitted to the radio via the trunking systems control channel.
GL-6
OL-21842-01
Glossary
E
E&M
recEive and transMit (or ear and mouth). As the analog interface between a radio and the LMR gateway, the E&M interface provides voice signals from radio channels, which are then mapped to IP multicast or unicast. The E&M interface provides the most common form of analog trunking. 1. Trunking arrangement that is generally used for two-way switch-to-switch or switch-to-network connections. Cisco's analog E&M interface is an RJ-48 connector that allows connections to PBX trunk lines (tie lines). E&M also is available on E1 and T1 digital interfaces. 2. A type of signaling that is traditionally used in the telecommunications industry. Indicates the use of a handset that corresponds to the ear (receiving) and mouth (transmitting) component of a telephone.
e-lead
The ear portion of the E & M interface. The e-lead is the receive path of the LMR gateway. To convert plain text into an unintelligible form by using a cipher. To modify information into the required transmission format. Application of a specific algorithm so as to alter the appearance of data and make it incomprehensible to unauthorized users. An active VTG in the Cisco IPICS solution.
encipher encode encryption
event
F
FDM
frequency-division multiplexing. Technique whereby information from multiple channels can be allocated bandwidth on a single wire based on frequency. frequency-division multiple access. A a channel access method in which different conversations are separated onto different frequencies. FDMA is employed in narrowest bandwidth and multiple-licensed channel operations.
FDMA
GL-7
Glossary
FLEXlm
Cisco software that enforces licensing on certain systems; FLEXlm ensures that Cisco IPICS software will work only on the supported and licensed hardware. The standard mechanism for Push-to-Talk speaker arbitration. A logical grouping of information sent as a data link layer unit over a transmission medium. Often refers to the header and the trailer, used for synchronization and error control, that surround the user data contained in the unit. The terms cell, datagram, message, packet, and segment also describe logical information groupings at various layers of the OSI reference model. For a periodic function, frequency represents the number of cycles or events per unit of time. Frequency is used in several different contexts. For example, transmission frequency (the band on which the radio sends signals) or the frequency of an audible signal measured in hertz (Hz). All tone control operations require audible tones that fall within a narrow band of a specific frequency and at a specific volume (amplitude). Assignment that is given to a radio station to use a radio frequency or radio frequency channel under specified conditions. The repeated switching of frequencies during radio transmission according to a specified algorithm, intended to minimize unauthorized interception or jamming of telecommunications. Modulation technique in which signals of different frequencies represent different data values. The assignment to or use of the same radio frequency by two or more stations that are separated geographically or that use the frequency at different times. A tone that follows the high level guard tone and causes the radio to perform a specific function, such as selecting a new transmit frequency. Function tones are often referred to as F1, F2, F3, and so on. See preamble and high level guard tone.
floor control frame
frequency
frequency assignment frequency hopping
frequency modulation frequency sharing
function tone
GL-8
OL-21842-01
Glossary
G
gateway
Device that performs an application-layer conversion of information from one protocol stack to another. In Cisco IPICS, the gateway component includes LMR gateways, which functionality is usually installed as an additional feature in a supported Cisco router. LMR gateways provide voice interoperability between radio and non-radio networks by bridging radio frequencies to IP multicast streams. generic routing encapsulation. Tunneling protocol that can encapsulate a wide variety of protocol packet types inside IP tunnels, creating a virtual point-to-point link to Cisco routers at remote points over an IP internetwork. By connecting multiprotocol subnetworks in a single-protocol backbone environment, IP tunneling that uses GRE allows network expansion across a single-protocol backbone environment. GRE is generally used to route multicast traffic between routers. The most common guard tones are the high level guard tone (HLGT) and the low level guard tone (LLGT). The HLGT is used to alert the radio that a function tone follows. The LLGT is used as a hold tone or keying tone. See tone keyed.
GRE
guard tone
H
H.323
Defines a common set of codecs, call setup and negotiating procedures, and basic data transport methods to allow dissimilar communication devices to communicate with each other by using a standardized communication protocol. Refers to the higher frequency levels in the VHF band, typically 138-222 MHz.
high-band frequency
GL-9
Glossary
HLGT
high level guard done. Also known as awake tone. This tone is set at high volume and is usually the first tone in a preamble. It is used to alert the radio that another tone, usually a function tone, will follow. See guard tone. A communications system where the loudest and most recent talker or talkers are mixed into one multicast output stream. Also known as hootie, these networks provide always on multiuser conferences without requiring that users dial in to a conference. Cisco enables the Cisco Hoot 'n' Holler feature in specific Cisco IOS versions.
Hoot n Holler (Hootie)
I
IDC
Cisco IPICS Dispatch Console (IDC)A standalone PC-based software application that simulates a handheld radio to enable PTT functionality for PC users. This application enables Cisco IPICS IDC end-users, dispatch personnel, and administrators to participate in one or more channels/VTGs at the same time. The unique ID that the Cisco IPICS server generates for each IDC to track requests between the IDC and the server and to verify and manage concurrent IDC usage for licensing requirements. The tone that a radio may deliver on the m-lead to signal the LMR gateway that there is no incoming traffic. When the idle tone is removed, the LMR gateway deems all signals to be valid voice traffic. A VTG that is stored for use. The Cisco IPICS server stores inactive VTGs with the information that you enter so that they can be automatically activated by a policy or manually activated by a dispatcher. Traffic that is sent inband is included in the same stream as the real-time traffic protocol (RTP). Inband signals can be encoded signals and RFC 2833 signals. A software framework that includes an adaptable GUI to facilitate resources, such as users, radio channels, cameras, and sensor information, for delivery that is based upon policy or incident needs.
IDC ID
idle tone
inactive VTG
inband
incident management framework
GL-10
OL-21842-01
Glossary
informix linux group Members of this group have full permission to Cisco IPICS server folders, files,
and scripts that are related to the Informix database application. Members of this group include the informix and ipicsdba users.
informix user ID
The Cisco IPICS Linux user that belongs to both the informix linux group, which includes full permission to the Cisco IPICS database server folders, files, and scripts, and the ipics linux group, which includes permission to Cisco IPICS application-related folders, files, and scripts. In addition, this user has full administrative permission to the Informix database instance. Cisco IPICS creates this Linux system user ID and generates the password during the software installation process. The password for this user ID never expires. To access the informix user, log in to the Cisco IPICS server by using the root user ID; then, enter su - informix (superuser from root).
interference
The effect of unwanted energy due to one or a combination of emissions, radiation, or inductions upon reception in a radio communication system, manifested by any performance degradation, misinterpretation, or loss of information, which could be extracted in the absence of such unwanted energy. The capability of equipment manufactured by different vendors to communicate with each other successfully over a network. A policy that can be invoked only through the telephony user interface and can include only the invite to VTG action. After joining a talk group, a user can access the breakout menu and invoke invitation policies. The talk group that this user has joined is the talk group that the invited users join. A version of the dial out invite action where users to be invited are preconfigured but the VTG that they are invited to depends on which VTG the invoker of the policy is dialed into. The Cisco IPICS Linux user that, as part of the ipics linux group, has full permission to the Cisco IPICS server folders, files, and scripts that are related to the Cisco IPICS application and database backup and restore operations. In addition, the ipicsadmin user has permission to read and write data from and/or to the Informix database. Cisco IPICS creates this Linux system user ID during the software installation process. The password for this user ID never expires.
interoperability
invitation policy
invite to VTG
ipicsadmin user ID
GL-11
Glossary
ipicsdba user ID
The Cisco IPICS Linux user that belongs to both the informix linux group, which includes full permission to the Cisco IPICS database server folders, files, and scripts, and the ipics linux group, which includes permission to Cisco IPICS application-related folders, files, and scripts. In addition, the ipicsdba user has permission to read data, write data, create tables, and create databases in the Informix database instance. Cisco IPICS creates this Linux system user ID and generates the password during the software installation process. The password for this user ID never expires. To access the ipicsdba user, log in to the Cisco IPICS server by using the root user ID; then, enter su - ipicsdba (superuser from root).
ipics linux group
Members of this group have full permission to Cisco IPICS server folders, files, and scripts that are related to the Cisco IPICS application and database backup and restore operations. Members of this group include the ipicsadmin, ipicsdba, and informix users. The Cisco IPICS application-level user ID that can perform all administration-related tasks via the Cisco IPICS Administration Console. Cisco IPICS creates this web-based user ID during the software installation process. IP Security. A framework of open standards that provides data confidentiality, data integrity, and data authentication between participating peers. IPSec provides these security services at the IP layer. IPSec uses IKE to handle the negotiation of protocols and algorithms based on local policy and to generate the encryption and authentication keys to be used by IPSec. IPSec can protect one or more data flows between a pair of hosts, between a pair of security gateways, or between a security gateway and a host.
ipics user ID
IPSec
K
keepalive
A message that is sent by one network device to inform another network device that the virtual circuit between the two devices is still active.
GL-12
OL-21842-01
Glossary
key
The parameter that defines an encryption code or method. Key (a radio) causes the radio to transmit. See tone keyed.
kilohertz (kHz)
A unit of frequency that denotes one thousand Hz.
L
latch linear modulation
The IDC functionality that allows a Cisco IPICS user to lock in a PTT channel. A radio frequency transmission technique that provides the physical transport layer of a radio system. This technology is compatible in digital and analog system environments and supports channel bandwidths of 5 kHz to 50 kHz. low level guard tone. This tone is used as a hold tone or keying tone. See guard tone. Land Mobile Radio. A Land Mobile Radio (LMR) system is a collection of portable and stationary radio units that are designed to communicate with each other over predefined frequencies. They are deployed wherever organizations need to have instant communication between geographically dispersed and mobile personnel. This term is often used interchangeably between a handheld or vehicle-mounted device and a stationary transmitter. Stationary devices are typically referred to as base stations. Cisco IPICS leverages the Cisco Hoot 'n' Holler feature, which is enabled in specific Cisco IOS versions, to provide radio integration into the Cisco IPICS solution. LMR is integrated by providing an ear and mouth (E&M) interface to a radio or other PTT devices, such as Nextel phones. Configured as a voice port, this interface provides the appropriate electrical interface to the radio. You configure this voice port with a connection trunk entry that corresponds to a voip dial peer, which in turn associates the connection to a multicast address. This configuration allows you to configure a corresponding channel in Cisco IPICS, using the same multicast address, which enables Cisco IPICS to provide communication paths between the desired endpoints.
LLGT
LMR
GL-13
Glossary
LMR gateway
Land Mobile Radio gateway. Refers to the router E&M interface that converts IP traffic from digital to analog for use by radios. In Cisco IPICS, location signifies reachability; meaning, channels or users who are associated with the same location can communicate with each other without additional network configuration. Location may refer to a physical or virtual location, as defined in the server.
location
low-band frequency Lower frequency levels in the VHF band, typically 2550 MHz.
M
megahertz (MHz) mixed tone
A unit of frequency denoting one million Hz. Two tones that are mixed together. DTMF is an example of a mixed tone. To be transmitted properly, tone signals must be mixed with the LLGT. See DTMF. The mouth portion of the E&M interface. The m-lead is the transmit path of the LMR gateway. The process, or result of the process, of varying a characteristic of a carrier in accordance with an information-bearing signal. Single packets that are copied by the network and sent to a specific subset of network addresses. Multicast refers to communications that are sent between a single sender and multiple recipients on a network. A single address that may refer to multiple network devices. Cisco IPICS uses this type of connection to enable the IDC to directly tune in to the multicast channel. Multicast address/port combinations are also used by gateways and RMS components. Multicast IP addresses that are defined as part of a multicast pool. Cisco IPICS allocates a multicast address from this pool of resources when a dispatcher activates a VTG.
m-lead
modulation
multicast
multicast address multicast address/port
multicast pool
GL-14
OL-21842-01
Glossary
multiplexing
The combination of two or more information channels on to a common transmission medium. In electrical communications, the two basic forms of multiplexing are time-division multiplexing (TDM) and frequency-division multiplexing (FDM). the telephony user interface or the Cisco IPICS administration console.
multipurpose policy A policy that can include any of the supported actions; may be invoked through
multiselect buttons
Provides the ability to select or deselect all channels on the IDC for audio transmission. The functionality that enables a dispatcher to mute a IDC user from talking or transmitting voice on one or more channels. The dispatcher can mute the microphone of the user or both the microphone and the speaker. A national or regional channel that has been set aside for use only in mutual aid interoperability situations. Restrictions and guidelines governing usage usually apply.
mute
mutual aid channel
N
narrowband channels National Public Safety Planning Advisory Committee
Channels that occupy less than 20 kHz. The committee that was established to conduct nationwide planning and allocation for the 821824 MHz and 866869 MHz bands.
The United States executive branch agency that serves as the principal advisor National Telecommunication to the president on telecommunications and information policies and that is and Information responsible for managing the federal governments use of the radio spectrum. Administration
near end
The device or devices that are physically connected to the Ethernet or an RS-232 link. Compare with far end, which refers to devices on the other side of the broadcast. A base station that is connected to an LMR gateway is a near end device while a handheld radio that receives over-the-air signals from the base station is a far end device.
GL-15
Glossary
network NAT
An interconnection of communications entities. Network Address Translation. Provides a mechanism for translating addresses that are not globally unique into globally routable addresses for connection to the Internet. A VTG state that becomes effective when the Activate button is clicked a second time (to deactivate the channel) or if the connection terminates. No IDC buttons appear highlighted. An action that notifies selected user(s) via email, SMS, pager, or phone. The necessary IDs and phone numbers are configured in the communication preferences for each user. Notifications that are sent via the phone require user authentication before the notification prompt is heard. An email, SMS, pager, or phone call that is placed to a user for the purpose of sending a notification message.
not activated
notification
O
offline mode
When the connection to the server goes offline, the IDC enters offline mode. Offline mode enables continuous communication during periods of server downtime. Using offline mode requires at least one successful login to the server. The Cisco IPICS operator is responsible for setting up and managing users, configuring access privileges, and assigning user roles and ops views. operational view. A Cisco IPICS feature that provides the ability to organize users, user groups, channels, channel groups, VTGs, and policies into different user-definable views across multiple organizations or agencies that normally would not share resources. While ops views are maintained separately by the Cisco IPICS system administrator and/or ops view administrator, this functionality also allows multiple entities to use one Cisco IPICS server to enable resource sharing across multiple ops views, according to business need.
operator
ops view
GL-16
OL-21842-01
Glossary
ops view administrator
The ops view administrator capabilities include managing and monitoring the activity logs that are filtered by ops views and accessible in the Administration Console (Administration > Activity Log Management) window. over-the-air re-keying. Provides the ability to update or modify over radio frequency the encryption keys that are programmed in a mobile or portable radio.
OTAR
P
packet
A logical grouping of information that includes a header that contains control information. Usually also includes user data. The process of routing and transferring data by using addressed packets so that a channel is occupied during the transmission of the packet only. Upon completion of the transmission, the channel is made available for the transfer of other traffic. Protocol Independent Multicast. Multicast routing architecture that allows the addition of IP multicast routing on existing IP networks. PIM is unicast routing protocol independent and can be operated in two modes: PIM dense mode and PIM sparse mode. One of the two PIM operational modes. PIM dense mode is data-driven and resembles typical multicast routing protocols. Packets are forwarded on all outgoing interfaces until pruning and truncation occurs. In dense mode, receivers are densely populated, and it is assumed that the downstream networks want to receive and will probably use the datagrams that are forwarded to them. The cost of using dense mode is its default flooding behavior. Sometimes called dense mode PIM or PIM DM.
packet switching
PIM
PIM dense mode
GL-17
Glossary
PIM sparse mode
One of the two PIM operational modes. PIM sparse mode tries to constrain data distribution so that a minimal number of routers in the network receive it. Packets are sent only if they are explicitly requested at the RP (rendezvous point). In sparse mode, receivers are widely distributed, and the assumption is that downstream networks will not necessarily use the datagrams that are sent to them. The cost of using sparse mode is its reliance on the periodic refreshing of explicit join messages and its need for RPs. Sometimes called sparse mode PIM or PIM SM. Policies include one or more actions that execute sequentially and can be manually activated via the Cisco IPICS administration console or the telephony user interface. Cisco IPICS provides support for multiple policy types. A channel that can be set up by the dispatcher and configured as a designated channel; that is, a channel that is always open to enable your interaction with the dispatcher. An indicator of policy execution success or failure. The Cisco IPICS administration console provides a status for each action under a policy, A web programming paradigm for customizing the interface and functionality of a client application. The sequence of tones that precede a transmission. The preamble generally includes the HLGT and the function tone. A set of unique rules that specify a sequence of actions that are necessary to perform a communications function. Push-to-talk. A signal to a radio transmitter that causes the transmission of radio frequency energy. The action that keys a radio or causes the radio to transmit. On the Cisco router, the e-lead, or key tone, is used to signal the radio to transmit.
policy
policy channel
policy execution status portalization
preamble
protocol
PTT
PTT channel
A channel consists of a single unidirectional or bidirectional path for sending and/or receiving signals. In the Cisco IPICS solution, a channel represents one LMR gateway port that maps to a conventional radio physical radio frequency (RF) channel.
GL-18
OL-21842-01
Glossary
PTT channel button
The button on the IDC that you click with your mouse, or push, and hold to talk. You can use the latch functionality on this button to talk on one or more channels at the same time. A logical grouping of available PTT channels that can be used for categorization.
PTT channel group
Q
QoS
quality of service. A measurement of performance for a transmission system, including transmission quality and service availability. Represents a set of items that are arranged in sequence. Queues are used to store events occurring at random times and to service them according to a prescribed discipline that may be fixed or adaptive. In a radio communication system, the queuing delay specifies the time between the completion of signaling by the call originator and the arrival of a permission to transmit to the call originator.
queue
queuing delay
R
radio channel
Represents an assigned band of frequencies sufficient for radio communication. The bandwidth of a radio channel depends upon the type of transmission and its frequency tolerance. desired channel without manual intervention. Refers to a serial control entity.
radio control service The logical element in the Cisco IPICS system that can tune a radio to the
radio equipment
Any equipment or interconnected system or subsystem of equipment (both transmission and reception) that is used to communicate over a distance by modulating and radiating electromagnetic waves in space without artificial guide. This equipment does not include microwave, satellite, or cellular telephone equipment. The indicator on the IDC that blinks green when traffic is being received.
receive indicator
GL-19
Glossary
remote connection
Cisco IPICS uses this type of connection to provide SIP-based trunking into the RMS component, which is directly tuned into the multicast channel. radio frequency. Any frequency within the electromagnetic spectrum that is normally associated with radio wave propagation. RF generally refers to wireless communications with frequencies below 300 GHz. The Internet Engineering Task Force (IETF) specification that describes how to carry DTMF signaling, other tone signals, and telephony events in RTP packets. Using RFC 2833 a packet can be compactly composed to play a series of tones, including DTMF, in a specific sequence that includes specified durations and volume levels. An analog device that amplifies an input signal regardless of its nature (analog or digital). Also, a digital device that amplifies, reshapes, retimes, or performs a combination of any of these functions on a digital input signal for retransmission. router media service. Component that enables the Cisco IPICS IDC to remotely attach to a VTG. It also provides support for remotely attaching (combining) two or more VTGs through its loopback functionality. The RMS mixes multicast channels in support of VTGs and it also mixes IDC SIP-based (unicast) connections to a multicast channel or VTG. The RMS can be installed as a stand-alone component (RMS router) or as an additional feature that is installed in the LMR gateway.
RF
RFC 2833
RF repeater
RMS
root user ID
The Cisco IPICS Linux user that has access to all files in the Cisco IPICS server. Strong passwords are enforced and Linux operating system password expiration rules apply to this user ID. Real-Time Transport Procotol. Commonly used with IP networks to provide end-to-end network transport functions for applications that transmit real-time data, such as audio, video, or simulation data, over multicast or unicast network services. Real-time Transport Control Protocol. The standard for notifying senders and receivers of important events or transmission statistics. The most common forms of RTCP are the sender report and the receiver report.
RTP
RTCP
GL-20
OL-21842-01
Glossary
S
scanning
A subscriber unit feature that automatically allows a radio to change channels or talk groups to enable a user to listen to conversations that are occurring on different channels or talk groups. The audio prompts that the dial engine scripts play out during execution and which callers hear when they are interacting with the telephony user interface. A channel that is connected to a radio that provides secure (encrypted or scrambled) communications on the Common Air Interface (CAI) side of the radio. (The level of security that is configured in the data network determines the security of the communications between the LMR gateway and a network attached device, such as a IDC or Cisco Unified IP Phone.) An attribute that is set in the server to indicate that a channel is secure. A PTT channel that is configured as secure cannot be combined with unsecure channels in a VTG.
script prompts
secure channel
serial controlled radio
A type of control for a radio that uses out-of-band signaling (usually RS-232). See radio control service.
service delivery area See coverage. signal
The detectable transmitted energy that carries information from a transmitter to a receiver. Skins form the appearance of the IDC. In Cisco IPICS, skins are customizable and available in various options, including 4-channel and 8-channel mouse and touch screen formats. The procedure that is used to determine the active audio stream in a Push-to-Talk system.
skin
speaker arbitration
GL-21
Glossary
spectrum
The usable radio frequencies in the electromagnetic distribution. The following frequencies have been allocated to the public safety community: High HF 2529.99 MHz Low VHF 3050 MHz High VHF 150174 MHz Low UHF 406.1420/450470 MHz UHF TV Sharing 470512 MHz 700 MHz 764776/794806 MHz 800 MHz 806824/851869 MHz.
spoken names
The recorded names that are used for entities, such as channels, channel groups, VTGs, users, user groups, ops views, and policies. The names can be recorded through the policy engine or externally-recorded .wav files that can be uploaded into the system. An electric circuit that stops input to a radio receiver when the signal being received is too weak to be anything but noise.
squelch
statically configured Every stream of data that flows to the LMR gateway can be applied with a tone control preamble and/or guard tone by using a static configuration in the LMR gateway.
When traffic is sent on a multicast address, the radio automatically switches (because of the preamble) to the specific radio channel that is requested by the tone control sequence.
stored VTG subchannel
Also referred to as inactive VTG. A channel that shares the same multicast address as another channel or channels. These multiple source streams (channels) may be present on a single radio channel. On the IDC, you access these channels by pressing the channel selector buttons on the radio channel. A mobile or portable radio unit that is used in a radio system.
subscriber unit
GL-22
OL-21842-01
Glossary
system administrator
The Cisco IPICS system administrator is responsible for installing and setting up Cisco IPICS resources, such as servers, routers, multicast addresses, locations, and PTT channels. The system administrator also creates ops views, manages the Cisco IPICS licenses and IDC versions, and monitors the status of the system and its users via the activity log files. mobile radio system. Architectures may include single site, multi-site, simulcast, multicast, or voting receiver systems.
system architecture The design principles, physical structure, and functional organization of a land
T
T1
Digital WAN carrier facility. T1 transmits DS-1-formatted data at 1.544 Mbps through the telephone-switching network, using alternate mark inversion (AMI) or binary 8 zero suppression (B8ZS) coding. Allows mapping from multicast to unicast so that unicast phone calls can be patched into an LMR or into other multicast audio streams. A loopback is composed of two of the available T1 interfaces. A VTG or a channel. A subgroup of radio users who share a common functional responsibility and, under normal circumstances, only coordinate actions among themselves and do not require radio interface with other subgroups.
T1 loopback
talk group
TCP
Transmission Control Protocol. A connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack. time division multiple access. Type of multiplexing where two or more channels of information are transmitted over the same link by allocating a different time interval (slot or slice) for the transmission of each channel; that is, the channels take turns to use the link. A device capable of sending, receiving, or sending and receiving information over a communications channel.
TDMA
terminal
GL-23
Glossary
throughput
The number of bits, characters, or blocks passing through a data communications system, or a portion of that system. A joint effort between government and industry to develop voice and data technical standards for the next generation of public safety radios. The process of using inband tone sequences to change the behavior of a radio end point. An inband tone can be used to control functions, such as modifying (retuning) the radio frequency (RF channel), changing the transmit power level, and monitoring a channel. The most basic form of tone control (tone keyed) is used to key the radio. With the Cisco IPICS solution, the radio that is being controlled is directly connected to the LMR gateway E&M leads. A specific form of a function tone. The tone that is used to signal the radio to select a frequency. These audible tone frequencies are generated in the router and combined in a specific sequence to perform a tone control function. A tone keyed radio requires the presence of a specific tone on the incoming analog (e-lead) port. Without this tone, the radio cannot transmit. The tone is generally used to prevent spurious transmission that may occur because of injected noise. Any form of over-the-air audible signals that are intended to terminate at the far end. Examples include alerting tones, DTMF tones, and paging tones. On some of the IDC skins, this indicator blinks red when traffic is being transmitted. A time-based event that invokes a policy on a scheduled basis, without manual intervention. A physical and logical connection between two switches across which network traffic travels. In telephony, a trunk is a phone line between two central offices (COs) or between a CO and a PBX. Systems with full feature sets in which all aspects of radio operation, including RF channel selection and access, are centrally managed.
TIA/EIA-102 standards tone control
tone frequency
tone keyed
tone signaling
transmit indicator
trigger
trunk
trunked (system)
GL-24
OL-21842-01
Glossary
trunked radio system
Integrates multiple channel pairs into a single system. When a user wants to transmit a message, the trunked system automatically selects a currently unused channel pair and assigns it to the user, decreasing the probability of having to wait for a free channel. telephony user interface. The telephony interface that the dial engine provides to enable callers to perform tasks, such as joining talk groups and invoking policies. To change the current send and receive frequencies on a radio. This task is usually accomplished via a preset with some form of radio control.
TUI
tune (a radio)
U
user
The Cisco IPICS user may set up personal login information, download the IDC application, customize the IDC skin, and specify communication preferences that are used to configure audio devices. By using a predefined user ID and profile, the user can participate in PTT channels and VTGs by using the IDC, supported models of Cisco Unified IP Phones, and the Public Switched Telephone Network (PSTN) via the telephony dial functionality of the Cisco IPICS IP policy engine. Users may have one or more Cisco IPICS roles, such as system administrator, ops view administrator, operator or dispatcher. Specifies point-to-point transmission, or a message sent to a single network destination.
unicast
V
VAD
Voice Activity Detection. When VAD is enabled on a voice port or on a dial peer, only audible speech is transmitted over the network. When VAD is enabled on Cisco IPICS, the IDC only sends voice traffic when it detects your voice. A virtual channel is similar to a channel but a radio system may not be attached. By creating a virtual channel, participants who do not use physical handheld radios to call into a VTG become enabled by using the IDC application or a supported Cisco Unified IP Phone model.
virtual channel
GL-25
Glossary
voice interoperability voice replay
Voice interoperability enables disparate equipment and networks to successfully communicate with each other. A feature that allows the IDC user to replay buffered audio on a per channel basis. Voice over Internet Protocol. By digitalizing and packetizing voice streams, VoIP provides the capability to carry voice calls over an IP network with POTS-like functionality, reliability, and voice quality. The volume indicator on the IDC that shows the current volume level on the channel in a graphical format. The buttons on the IDC that let you control the volume level. Voice-operated transmit. A keying relay that is actuated by sound or voice energy above a certain threshold and sensed by a connected acousto-electric transducer. VOX uses voice energy to key a transmitter, eliminating the need for push-to-talk operation. virtual talk group. A VTG can contain any combination of channels, channel groups, users, and user groups. A VTG can also contain other VTGs.
VoIP
volume indicator
volume up/down buttons VOX
VTG
VTG add participant An action that adds selected participant(s) to the selected VTG.
W
wavelength wideband channel
The representation of a signal as a plot of amplitude versus time. Channels that occupy more than 20 kHz.
GL-26
OL-21842-01
INDEX
A
address, obtaining for Cisco IPICS 2 administration console, troubleshooting access problems 5
Cisco IPICS installation, checking 28 Cisco IPICS installer copying file from CD to server root 21, 7 End User License Agreement (EULA) 18 running from a remote location 21, 7 running from the server location 16, 2 Cisco IPICS license See license Cisco IPICS operating system installing 7 message indicating incompatible or unsupported hardware during installation 2 Setup Utility 2 uninstalling 1 upgrading 1 Cisco IPICS server software installing 16 uninstalling 1 upgrading 1 commands chmod 4 onstat 11 service ipics_db 12 components, Cisco IPICS installed 4
B
bash command, using with Cisco IPICS installer file 18 browser, troubleshooting access to the server from 5
C
cable, connecting to server 3 caution, described 8 changing system date and time 37 changing system date and time, problems with time-bound licenses 37 checking Cisco IPICS installation 28 checklist, preinstallation 3 chmod command 4 Cisco.com, accessing to obtain license file 31 Cisco IPICS Dispatch Console (IDC) 1
OL-21842-01
IN-1
Index
connecting Ethernet cable to server 3 conventions, document 8
Internet browser, troubleshooting access to the server from 5 IP address obtaining for Cisco IPICS 2
D
database server checking 11 manually starting 9, 12 documentation conventions 8
verifying Cisco IPICS 9 IPICS Dispatch Console (IDC) 1
L
license locating MAC address 31 managing 29
E
End User License Agreement (EULA), Cisco IPICS 18 Ethernet cable, connecting to server 3 Ethernet network connectivity problems 2
troubleshooting installation 37 troubleshooting time-bound 37 uploading file to server 32 License Agreement, accepting the Cisco IPICS 18
I
incompatible hardware error message during operating system installation 2 installation, troubleshooting 1 installing Cisco IPICS operating system 7 Cisco IPICS server software 16 SSH loses connectivity during remote server software installation 5 interface mapping for interfaces labeled 1 and 2 2
M
MAC address, obtaining 31 mapping, for interfaces labeled 1 and 2 2 multicast addresses, obtaining for Cisco IPICS 2
N
network cable, connecting to server 3 network connectivity problems 2 note, described 8
IN-2
OL-21842-01
Index
O
onstat command 11
checking 11 manually starting 9, 12 service ipics_db command 12 Setup Utility, Cisco IPICS operating system 2 SSH secure shell idle timeout value 21, 8 using to connect to Cisco IPICS server 21,
8
P
Package installation window, for Cisco IPICS operating system 3 partitions, troubleshooting after failing to allocate 3 ping command, using to verify Cisco IPICS IP address 9
T
time-bound license information 37
R
remote location, installing Cisco IPICS from 21, 7 Restart Computer window, Cisco IPICS installer 3 root logging in as, GNOME login window 17, 2,
11
troubleshooting 37 tomcat service checking status 5 restarting 7 troubleshooting authorization error on login 11 cannot reach server from browser 5 Cisco IPICS software installation 3, 4 database not running 11 Ethernet network connectivity problems 2 hard drive partition errors 3
logging in as before Cisco IPICS installation 16, 2
S
server connecting remotely by using SSH secure shell 21, 8 shutting down manually 26 server, database
incompatible hardware error message 2 incorrect username or password 11 installation issues 1 license installation 37 login problems from browser 5
IN-3
Index
SSH loses connectivity during remote server software installation 5 time-bound licenses 37 tomcat service not running 5 unsupported hardware error message 2 ts 2
U
uninstalling Cisco IPICS operating system software 1 Cisco IPICS server software 1 unsupported hardware error message during operating system installation 2 upgrading Cisco IPICS operating system software 1 Cisco IPICS server software 1 uploading Cisco IPICS license file 32
V
verifying Cisco IPICS installation 28 VTG interrupting during uninstallation 2
IN-4
OL-21842-01

Ipicsinstallguide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ipicsinstallguide

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco IPICS Server Installation and Upgrade Guide

Overview 1 Installation Overview 1 Installed Components 4 System Requirements 4

Cisco IPICS Server Installation and Upgrade Guide

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Cisco IPICS Server Installation and Upgrade Guide

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Document Notes and Conventions

Cisco IPICS Server Installation and Upgrade Guide

Preface Document Notes and Conventions

Convention boldface font italic font [ ]

font italic screen font

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Preface Obtaining Documentation, Obtaining Support, and Security Guidelines

Obtaining Documentation, Obtaining Support, and Security Guidelines

Cisco IPICS Server Installation and Upgrade Guide

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 1 Installation Overview

Password creation for the root user

Root user login

Cisco IPICS Server Installation and Upgrade Guide

Overview Installation Overview

End user license agreement

Password creation for the ipics user

Password creation for the ipicsadmin user

Uninstaller creation Option to restart the server

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 1 Installed Components

Cisco IPICS Server Installation and Upgrade Guide

Installing Cisco IPICS

Before You Begin

Chapter 2 Before You Begin

Installing Cisco IPICS

Obtaining the IP Addresses for Your Cisco IPICS System

Cisco IPICS Server Installation and Upgrade Guide

Installing Cisco IPICS Before You Begin

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 2 Before You Begin

Installing Cisco IPICS

Cisco IPICS Server Installation and Upgrade Guide

Installing Cisco IPICS Before You Begin

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 2 Before You Begin

Installing Cisco IPICS

Cisco IPICS Server Installation and Upgrade Guide

Installing Cisco IPICS Installing the Cisco IPICS Operating System

Installing the Cisco IPICS Operating System

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 2 Installing the Cisco IPICS Operating System

Installing Cisco IPICS

Installing Cisco IPICS Installing the Cisco IPICS Operating System

Step 11 Step 12 Step 13 Step 14 Step 15

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 2 Installing the Cisco IPICS Operating System

Installing Cisco IPICS

Enter the following command:

To log out of the server, enter the following command:

Cisco IPICS Server Installation and Upgrade Guide

Reinstalling the IPICS Operating System on the Multiservices Platform

Cisco IPICS Server Installation and Upgrade Guide OL-21842-01

Chapter 2 Reinstalling the IPICS Operating System on the Multiservices Platform

Installing Cisco IPICS

Cisco IPICS Server Installation and Upgrade Guide