Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IP Interoperability and Collaboration System

Release Notes for Cisco IPICS Release 1.1(1)

Downloads

Table Of Contents

Release Notes for Cisco IPICS
Release 1.1(1)

Contents

Overview

Cisco IPICS Support Team Communications

System Requirements

Related Documentation

New and Changed Information

Supported Deployment Solutions

Central Site Server Solution

Remote Locations Solution

M1:U12:M2 Configuration Examples

Requirements and Support Information

Performing Additional Configurations on Your Server and Your PC

Performance Guidelines

Installing Cisco IPICS Release 1.1(1)

Backing Up Your Data Files on Cisco IPICS Release 1.0(2)

Installing the Cisco IPICS Operating System Software, Release 1.0(3)

Installing Cisco IPICS Server Software, Release 1.1(1)

Restoring Your Data Files on Cisco IPICS Release 1.1(1)

Uninstalling Cisco IPICS Release 1.1(1)

Resolved Caveats for Cisco IPICS - Release 1.1(1)

Using Bug Toolkit

Saving Bug Toolkit Queries

Open Caveats for Cisco IPICS Release 1.1(1)

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Product Alerts and Field Notices

Obtaining Technical Assistance

Cisco Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco IPICS
Release 1.1(1)

January 30, 2007

These release notes describe the new features and caveats for the Cisco IP Interoperability and Collaboration System (hereafter referred to as Cisco IPICS) and the Push-to-Talk Management Center (hereafter referred to as PMC) release 1.1(1).

For information about resolved and open caveats that pertain to this release, see the "Resolved Caveats for Cisco IPICS - Release 1.1(1)" section and the "Open Caveats for Cisco IPICS Release 1.1(1)" section.

Note To view all of the release notes for Cisco IPICS, go to: http://www.cisco.com/univercd/cc/td/doc/product/cis/c_ipics/index.htm

Contents

These release notes include the following topics:

•Overview

•Cisco IPICS Support Team Communications

•System Requirements

•New and Changed Information

•Resolved Caveats for Cisco IPICS - Release 1.1(1)

•Open Caveats for Cisco IPICS Release 1.1(1)

•Obtaining Documentation

•Documentation Feedback

•Cisco Product Security Overview

•Product Alerts and Field Notices

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

Overview

The Cisco IPICS solution provides a cost-effective and highly-efficient IP standards-based solution to enable voice interoperability among disparate systems. By interconnecting voice channels, talk groups, and virtual talk groups (VTGs), Cisco IPICS bridges communications from radio networks to the Cisco IPICS Push-to-Talk Management Center (PMC) PC application and supported models of Cisco Unified IP Phones.

Cisco IPICS release 1.1(1) extends the functionality of release 1.0 by providing support for environments that include high latency and low and/or variable bandwidth links, such as satellite links. In these types of environments, connectivity may become unstable because of the geographical location of the user, weather elements, and other interferences. In this release, Cisco IPICS compensates for these dynamically variable bandwidth scenarios and enhances its support for mobile operations.

This release introduces support for the following deployment scenarios:

•Central site server solution—This solution supports a Cisco IPICS server that is installed at a central site and a distributed router media service (RMS) and end-user client components that are installed at a remote site.

•Remote locations solution—This solution supports deployment of the Cisco IPICS server, RMS, and end-user clients at two remote sites that are connected by M1:U12:M2 tunnels.

The M1:U12:M2 tunneling technology enables these deployment scenarios. For more information about these deployment scenarios, see the "Supported Deployment Solutions" section.

Cisco IPICS Support Team Communications

The Cisco IPICS Support Team provides an external mailing list that you can use to obtain additional support directly from the Cisco IPICS engineering team. To subscribe to this mailing list, create an email that includes "subscribe" in the subject line; then, send the email to the following address:

ask-ipics-support@external.cisco.com

Whenever you need additional support, or if you have questions about Cisco IPICS, send your request to ask-ipics-support@external.cisco.com

A Cisco IPICS engineer will respond to your email to provide you with the assistance that you need.

System Requirements

The Cisco IPICS server and the PMC require specific versions of hardware and software.

For detailed information about supported hardware and software that is compatible for use with Cisco IPICS, refer to the Cisco IPICS Compatibility Matrix at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/cis/c_ipics/index.htm

Related Documentation

To access the entire documentation suite for Cisco IPICS, refer to the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/cis/c_ipics/index.htm

New and Changed Information

The following sections describe the new features that are available and pertinent to this release of Cisco IPICS. It includes the following topics:

•Supported Deployment Solutions

•Installing Cisco IPICS Release 1.1(1)

•Uninstalling Cisco IPICS Release 1.1(1)

Supported Deployment Solutions

In this release, Cisco IPICS enhancements include support for two deployment solutions, as documented in the following topics:

•Central Site Server Solution

•Remote Locations Solution

•M1:U12:M2 Configuration Examples

•Requirements and Support Information

•Performing Additional Configurations on Your Server and Your PC

•Performance Guidelines

Central Site Server Solution

In this scenario, the Cisco IPICS server is located in a central site and an RMS is distributed with the PMC and other end-user clients in a remote site that is connected via a high latency, low bandwidth connection. In this situation, the Cisco IPICS server must control the distributed RMS, and the dispatcher at the central site needs to be able to communicate with remote PMC clients in the field.

This deployment solution provides the ability to remotely control the RMS over the high latency, low bandwidth links. Communications are enabled by the support of an M1:U12:M2 connection trunk between the RMS in the central site and a remotely-located RMS.

The M1:U12:M2 connection trunk also provides the capability for IP phone XML services and PMC clients to communicate between sites.

Note M1:U12:M2 (Multicast1:Unicast1-Unicast2:Multicast2) provides a unicast connection path between two multicast islands. An M1:U12:M2 connection trunk maps multicast to unicast on one side of the network, provides transport over the unicast wide area network (WAN) as a unicast Voice over IP (VoIP) call, and then converts it back to multicast on the other side of the connection, such that multicast 1 is connected to multicast 2 via a unicast connection between 1 and 2.

M1:U12:M2 transports only the multicast traffic that is configured on the trunk as contrasted to Generic Routing Encapsulation (GRE) tunnels, which transport all multicast traffic.

Tip See the "Performing Additional Configurations on Your Server and Your PC" section for additional configurations that apply to this deployment.

Caveats

Be aware of the following caveats when you use this deployment solution:

•Because all RMS commands flow over the high latency, low bandwidth link, this solution results in reduced throughput and slower response time.

•Some RMS-related operations may take over 3 minutes. Throughput considerations are based on factors such as the number of active channels that are included in the VTGs, the number of DS0s that are being used on the RMS, and the number of PMC users that are communicating between the sites. This limitation is due to inherent Transmission Control Protocol/Internet Protocol (TCP/IP) limitations over high latency, low bandwidth links. For information about RMS configuration updates when you use this deployment solution, see the "Updating the RMS Configuration" section.

•If you do not have a local router installed at the central site, you may need to configure Address Resolution Protocol (ARP) commands to increase the ARP timer so that the RMS remains reachable. For more information, see the "Adjusting ARP Commands" section.

•The RMS and Cisco IPICS server automatic synchronization mechanism must be disabled in this scenario. Therefore, you must manually synchronize these components. For more information about the manual configurations that you must perform, see the "Disabling the RMS Comparator" section and the "Merging the Configuration" section.

•To conserve bandwidth, you must disable the PMC upload log frequency in this release. For more information, see the "Disabling the PMC Upload Activity Log Frequency" section.

•Although the M1:U12:M2 connection trunk consumes dedicated bandwidth between the central site and the remote site, it does provide for bandwidth optimization by allowing transcoding to the G.729 codec.

•This deployment does not support the use of IP phone XML services at the remote locations.

–IP phone XML services are available only at the central site.

•There is no support for direct PMC access to the remote locations.

–The PMC clients can be at the remote site or the central site but they cannot remotely connect across sites.

Remote Locations Solution

In this scenario, a Cisco IPICS server, RMS, PMC, and other end-user clients are located at two remote sites. High latency, low bandwidth links that connect these remote sites enable communications flow.

This deployment solution enables communications by the use of fixed M1:U12:M2 tunnels that are configured between the channels that are hosted on each RMS at each remote site, such that each channel is mirrored on the other sites.

The M1:U12:M2 connection trunk also provides the capability for IP phone XML services and PMC clients to communicate between sites.

Tip See the "Performing Additional Configurations on Your Server and Your PC" section for additional configurations that apply to this deployment.

Caveats

Be aware of the following caveats when you use this deployment solution:

•The M1:U12:M2 connection trunks consume dedicated bandwidth between the remote sites, however bandwidth optimization is enabled by allowing transcoding to the G.729 codec.

•If you use multiple Cisco IPICS servers that each control their own RMS, care must be taken not to duplicate VTGs when defining channels. Because each channel is mirrored on the other remote site, audio loops can occur between the sites when you use the same VTGs at each site.

•This deployment provides support for IP phone XML services at either the central site or the remote sites.

–The IP phone XML services must be local to the site where they are deployed.

•There is no support for direct PMC access to the remote locations.

–The PMC clients can be at the remote site(s) or the central site, but they cannot remotely connect across the sites (they must be local to the site where they are deployed).

M1:U12:M2 Configuration Examples

The following tables provide configuration examples for the M1:U12:M2 connection trunks.

Note For complete and more detailed configuration examples, refer to the "Cisco IPICS Deployment Models" chapter in the Solution Reference Network Design (SRND) for Cisco IPICS Release 1.0(2).

The two multicast addresses that are being tunneled in the following configuration examples are 239.192.21.3:21000 and 239.192.21.5:21000.

Table 1 illustrates the manual commands that are required to configure the voice port and dial peer entries in RMS location #1 to enable the M1 portion of the M1:U12:M2 connection trunk.

Table 1 RMS Location #1 Configuration 

RMS Location #1 Voice Port Configuration
RMS Location #1 Multicast Dial Peer M1 Configuration 
voice-port 0/0:1

 auto-cut-through

 lmr m-lead audio-gate-in

 lmr e-lead voice

 no echo-cancel enable

 playout-delay mode adaptive

 playout-delay maximum 250

 playout-delay minimum high

 playout-delay nominal 100

 no comfort-noise

 timeouts call-disconnect 3

 timing hookflash-in 0

 timing hangover 40

 connection trunk 2001

dial-peer voice 3 voip

 destination-pattern 2001

 session protocol multicast

 session target 
ipv4:239.192.21.3:21000

                    (RMS M1)

 codec g711ulaw  vad aggressive

Table 2 illustrates the manual commands that are required to configure the voice port and dial peer entries in RMS location #2 to enable the M2 portion of the M1:U12:M2 connection trunk.

Table 2 RMS Location #2 Configuration 

RMS Location #2 Voice Port Configuration
RMS Location #2 Multicast Dial Peer M1 Configuration 
voice-port 0/0:2

 auto-cut-through

 lmr m-lead audio-gate-in

 lmr e-lead voice

 no echo-cancel enable

 playout-delay mode adaptive

 playout-delay maximum 250

 playout-delay minimum high

 playout-delay nominal 100

 no comfort-noise

 timeouts call-disconnect 3

 timing hookflash-in 0

 timing hangover 40

 connection trunk 1001

dial-peer voice 3 voip

 destination-pattern 1001

 session protocol multicast

 session target 
ipv4:239.192.21.5:21000

                    (RMS M2)

 codec g711ulaw  vad aggressive

Requirements and Support Information

This release provides the following levels of support:

•Delay—Provides support for up to three seconds end-to-end latency.

•Packet Loss—Supports up to 10% packet loss over the network.

•Jitter buffer—Enables support for up to 250 ms of maximum jitter on the network (to support burst latency).

•Link outages—Provides support for temporary link outages such that if the connection from the PMC is interrupted, the connection automatically continues when it becomes available again (the user is not informed of the outage).

•Bandwidth—Supports 64 kbps bandwidth per channel configured over an M1:U12:M2 connection trunk.

PMC Caveat

The following caveat pertains to the first time that the PMC logs in to the server:

•Upon the first PMC login, an error message displays to inform the user that the channels are being disabled. This error occurs because of the time delay to connect. To recover from this error, click OK. After the server completes its tasks, the channels will display on the PMC (this timing will vary based on latency).

Performing Additional Configurations on Your Server and Your PC

This section includes information about additional configurations that are required on the Cisco IPICS server and on the PC that you use to access the Cisco IPICS Administration Console.

The following additional configurations are required on the Cisco IPICS server when you use these deployment solutions.

•Updating the RMS Configuration

•Adjusting ARP Commands

•Disabling the RMS Comparator

•Merging the Configuration

•Disabling the PMC Upload Activity Log Frequency

The following additional configuration is required on the PC that you use to access the Administration Console:

•Adjusting Internet Explorer Browser Settings

Updating the RMS Configuration

When you use one of these deployment solutions, you must update every RMS that is configured with Cisco IPICS and used over a high latency, low bandwidth connection. This configuration update modifies the maximum TCP outgoing queue on a per-connection basis.

To modify the maximum TCP outgoing queue, perform the following procedure on each RMS:

Procedure

Step 1 Enter global configuration mode by entering the following command:

Router# configure terminal

Step 2 To set the maximum TCP outgoing queue to 100000 packets, enter the following command:

Router(config)# ip tcp queuemax 100000

Step 3 To save your configuration, enter the following command:

Router(config)# write mem

Step 4 To exit the router configuration mode, enter the following command:

Router# exit

Adjusting ARP Commands

If you use the central site server solution and you do not have a local router installed at the central site, you may need to increase the ARP timer in the server. This adjustment helps to prevent timeouts and ensure reachability between the server and the RMS when these components are connected via Ethernet and separated by a high latency link.

If you encounter issues with ARP timeouts and ping response times, contact the Cisco IPICS Support Team to obtain information about how to resolve these issues.

To contact the Cisco IPICS Support Team, send an email to ask-ipics-support@external.cisco.com

Disabling the RMS Comparator

The RMS comparator is the mechanism that checks the responsiveness of the RMS and if there have been any changes made to the configuration. If there have been changes to the RMS configuration and these changes are not reflected in the Cisco IPICS server, the RMS comparator automatically updates the configuration so that the two components are synchronized.

Because this synchronization mechanism can interject delay, the RMS comparator needs to be manually disabled in this release. To disable the RMS comparator, perform the following procedure.

Note Be aware that this change is a global change and affects all RMS components that are configured in the server.

Procedure

Step 1 Log in to the server by using the ipics user ID and password.

Step 2 From the Administration Console, navigate to Administration > Options.

Step 3 In the RMS pane, enter 0 for the RMS Polling Frequency value.

This change disables the RMS comparator so that it does not run.

Step 4 Click Save to save your change.

You must restart the tomcat service for your change to take effect.

Step 5 Connect to the server by using SSH Secure Shell client software (or equivalent software).

Step 6 Log in to the server with root user privileges.

Step 7 From root, enter the following command to restart the tomcat service:

[root]# service ipics_tomcat restart

The system restarts the tomcat service. Wait about 5 minutes.

Step 8 Log in to the server by using the ipics user ID and password.

Step 9 From the Administration Console, navigate to Administration > Options.

Step 10 In the RMS pane, verify that the RMS Polling Frequency value is set to 0.

Merging the Configuration

After you have disabled the RMS comparator, you must merge the configuration to make sure that the router is synchronized with the server.

Note As a best practice, make sure that you merge the RMS configuration whenever manual changes have been made to the RMS. This process ensures that the components are synchronized. Perform this procedure before you perform any configuration changes, such as activating a VTG.

To merge the configuration, perform the following procedure:

Procedure

Step 1 From the Administration Console, navigate to Configuration > RMS.

Step 2 To manage the RMS configuration, check the check box that corresponds to the RMS that you need to manage.

Step 3 From the Configuration drop-down list box, choose Merge to merge the RMS configuration.

Wait while this process completes. Cisco IPICS displays the changes in the Edit Router Details area.

Disabling the PMC Upload Activity Log Frequency

To conserve bandwidth, you must disable the PMC upload log frequency in this release. To disable the PMC upload log frequency, perform the following procedure.

Note Be aware that this change is a global change and affects all PMC clients that connect to the server.

Procedure

Step 1 Log in to the server by using the ipics user ID and password.

Step 2 From the Administration Console, navigate to Administration > Options.

Step 3 Click the PMC tab to access the PMC configuration options.

Step 4 In the Configuration pane, enter 0 for the PMC Log Upload Frequency value.

This change disables the PMC log upload mechanism so that the PMC clients that are connect to this server never upload their logs to the server.

Step 5 Click Save to save your change.

You must restart the tomcat service for your change to take effect.

Step 6 Connect to the server by using SSH Secure Shell client software (or equivalent software).

Step 7 Log in to the server with root user privileges.

Step 8 From root, enter the following command to restart the tomcat service:

[root]# service ipics_tomcat restart

The system restarts the tomcat service. Wait about 5 minutes.

Step 9 Log in to the server by using the ipics user ID and password.

Step 10 From the Administration Console, navigate to Administration > Options.

Step 11 Click the PMC tab to access the PMC configuration options.

Step 12 In the Configuration pane, verify that the PMC Log Upload Frequency value is set to 0.

Adjusting Internet Explorer Browser Settings

When you use a high latency, low bandwidth connection, you may encounter browser timeout errors when you try to update the RMS configuration for any RMS that is configured with twelve or more loopback interfaces.

To resolve this issue, you must modify the Internet Explorer settings on your PC to adjust the timeout duration. This configuration modifies the ReceiveTimeout data value to allow for the additional delay.

Caution Please use extreme caution when you modify the registry. If you are not familiar with editing the registry, you should seek technical support assistance before you perform this procedure. If you modify the registry incorrectly, you may need to reinstall the operating system. Therefore, make sure that you back up the registry before you modify it and are aware of how to restore the registry, if a problem occurs.

Tip For more information about how to back up, restore, and modify the registry, access the Microsoft Support site at http://support.microsoft.com and search the Microsoft Knowledge Base for a description of the Microsoft Windows registry.

To modify the ReceiveTimeout data value, perform the following procedure on the PC that you use to access the Cisco IPICS Administration Console:

Procedure

Step 1 On the PC that you use to access the Administration Console, choose Start > Run.

Step 2 In the Open dialog box, enter regedit.

The Registry Editor displays.

Step 3 Click the + sign that displays next to the HKEY_CURRENT_USER entry.

The folders that contain root configuration information for the user who is currently logged in displays.

Step 4 Click the + signs that display next to each of the folder names to navigate to the Software\Microsoft\Windows\CurrentVersion\ folder.

Step 5 Click the + sign that displays next to the Internet Settings folder.

At this point, you have navigated to the following folder: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\
Internet Settings.

Step 6 In the Internet Settings folder, look for the ReceiveTimeout name.

Step 7 To modify this setting, right-click the ReceiveTimeout name; then, click Modify.

The Edit DWORD Value dialog box displays. The current DWORD value displays in hexadecimal format.

Alternatively, you can choose to delete the ReceiveTimeout name altogether by clicking Delete. If you choose to take this action, be aware that you could wait indefinitely for the server to respond.

Step 8 Click the Decimal radio button to display this value in decimal format.

Step 9 To configure this value to the recommended setting to accommodate high latency, low bandwidth links, enter 480000 in the Value data field.

This modification configures the timeout value to 8 minutes.

Step 10 Click OK to save your change.

Step 11 To exit the Registry Editor, choose Registry > Exit.

Step 12 Restart your PC for the change to become effective.

Performance Guidelines

Be aware of the following guidelines that pertain to this release of Cisco IPICS:

•Each RMS can support a predefined number of commands, such as VTG activation, VTG deactivation, and PMC SIP (remote) connections. If the number of commands that the RMS receives exceeds this threshold, the excess commands fail and must be resubmitted.

•For high latency, low bandwidth deployments, allow 1.5 minutes for every three channel/VTG activations.

•If five dispatchers submit commands, or if the same dispatcher submits multiple commands, a wait time of 1.5 minutes should be allotted before resubmitting new command requests.

•For constant load conditions, a frequency of about 18 seconds per simple VTG command should be allotted on 2811 routers (RMS components), on average. Additional RMS components must be installed to support above average load conditions.

Installing Cisco IPICS Release 1.1(1)

This release of Cisco IPICS includes a new server software installer for release 1.1(1) along with updated operating system software (release 1.0(3)) that includes additional hardware drivers that add support for the Cisco MCS 7825-H2 and Cisco MCS 7845-H2 server models.

For information about compatible hardware and software that is supported for use with Cisco IPICS, refer to the Cisco IPICS Compatibility Matrix.

If you are a new Cisco IPICS user, refer to the Cisco IPICS Operating System Release 1.0(3) Installation and Upgrade Guide for information about how to install the Cisco IPICS release 1.0(3) operating system software. See the "Installing Cisco IPICS Server Software, Release 1.1(1)" section for information about installing the Cisco IPICS release 1.1(1) server software.

If you are an existing Cisco IPICS customer and your server is running Cisco IPICS release 1.0(2) (operating system software release 1.0(2) and server software release 1.0(2)), you can migrate your server to operating system software release 1.0(3) and server software release 1.1(1) by performing the following sequence of steps.

Note Make sure that you back up your data to a remote host before you install the Cisco IPICS operating system software.

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/univercd/cc/td/doc/product/cis/c_ipics/index.htm

1. Back up your data on Cisco IPICS release 1.0(2). Make sure that you back up your data to a remote host. For information about the steps to follow, see the "Backing Up Your Data Files on Cisco IPICS Release 1.0(2)" section.

2. Install the Cisco IPICS operating system, release 1.0(3), as documented in the Cisco IPICS Operating System Release 1.0(3) Installation and Upgrade Guide. See the "Installing the Cisco IPICS Operating System Software, Release 1.0(3)" section for more information.

3. Install the Cisco IPICS server software release 1.1(1) by following the steps in the "Installing Cisco IPICS Server Software, Release 1.1(1)" section.

4. Restore the data to Cisco IPICS release 1.1(1). For information about the steps to follow, see the"Restoring Your Data Files on Cisco IPICS Release 1.1(1)" section.

This section contains detailed information about migrating your server to Cisco IPICS operating system release 1.0(3) and Cisco IPICS server software release 1.1(1) in the following topics:

•Backing Up Your Data Files on Cisco IPICS Release 1.0(2)

•Installing the Cisco IPICS Operating System Software, Release 1.0(3)

•Installing Cisco IPICS Server Software, Release 1.1(1)

•Restoring Your Data Files on Cisco IPICS Release 1.1(1)

Backing Up Your Data Files on Cisco IPICS Release 1.0(2)

To back up your database files to a remote host location, perform the following procedure:

Procedure

Step 1 From the Administration Console, navigate to System Administrator > Database to access the Manage Database window.

Step 2 In the Database Backup pane, click the Remote Host radio button and specify the following information:

•Remote Host IP Address—Enter the IP address of the remote host

•User Name—Enter a valid user ID for access to the remote host

•User Password—Enter a valid password for this user

•Remote Directory—Enter the location of the full directory path on the remote host where you want the files to be stored

Step 3 To begin the backup procedure, click Backup Now.

Cisco IPICS begins the backup process.

Step 4 To view the backup activity, click the Refresh button that appears under the Database Logs pane.

The Database Logs pane shows the log entries that pertain to the backup process.

Step 5 To view the details of your backup activity, wait for the window to refresh or click Refresh to check the successful completion of your backup.

Cisco IPICS provides the following visual identification of certain log entries:

•Log entries that display in blue text indicate the successful completion of a script.

•Entries that display in green text indicate the successful completion of a process.

•Entries that display in red text indicate that an error has occurred.

Step 6 After you have completed the backup process, access the remote host to validate that the backup files have been stored to the remote directory that you specified.

Installing the Cisco IPICS Operating System Software, Release 1.0(3)

For detailed procedures about how to install the Cisco IPICS release 1.0(3) operating system software, refer to the "Installing Cisco IPICS Operating System Release 1.0(3)" section in the Cisco IPICS Operating System Release 1.0(3) Installation and Upgrade Guide.

Note When you install new Cisco IPICS operating system software, all existing data on the server hard drive gets deleted. Make sure that you have backed up your data before you install the Cisco IPICS operating system software.

Installing Cisco IPICS Server Software, Release 1.1(1)

The Cisco IPICS server software release 1.1(1) installer is based on the Cisco IPICS server software release 1.0(2) installer. However, it does not include an upgrade installation option because of the requirement to install the Cisco IPICS release 1.0(3) operating system software, which deletes all existing data on the server hard drive.

Therefore, to install Cisco IPICS server software release 1.1(1), follow the procedure to install Cisco IPICS server software release 1.0(2), as documented in the "Installing Cisco IPICS Server Software Release 1.0(2)" section in the Cisco IPICS Operating System Release 1.0(3) Installation and Upgrade Guide, with the following exception:

When you are prompted to enter an installation option for the server software, choose the Typical option, as shown below, by pressing Enter:

•1-Typical—This option installs Cisco IPICS server software with Cisco Security Agent (CSA); this option specifies the default

Note After you complete the Cisco IPICS installation, you must log in to the Administration Console to upload and install the license file before you can proceed with the database restoration.

Restoring Your Data Files on Cisco IPICS Release 1.1(1)

To restore your data files from a remote host location to Cisco IPICS release 1.1(1), perform the following procedure:

Procedure

Step 1 From the Administration Console, navigate to System Administrator> Database to access the Manage Database window.

Step 2 In the Restore from Backup pane, click the Remote Host radio button and specify the following information:

•IP Address—Enter the IP address of the remote host.

•User Name—Enter a valid user name for access to the remote host.

Note To help ensure the security of your data, Cisco IPICS does not support the use of different user IDs for backup and restore operations that you perform on the same data set. Therefore, when you restore your data, make sure that you specify the same user ID as the one that you used to back up your data.

•User Password—Enter a valid password for this user.

•Remote Directory—Enter the full directory path of the remote host from which you want the data to be restored.

Step 3 Click Restore Now.

Cisco IPICS begins the restore process and logs you out of the Administration Console. As part of this process, the system restarts the tomcat service. You must wait for the restore process to complete before you can log in again and view the log details.

Note While the system is processing the restore operation, you can check the status in the db-maintenance.log file. The db-maintenance.log file is located in the following folder on the server: /opt/cisco/ipics/database/db-maintenance

Step 4 To view the results of the restore operation, wait about 20 minutes; then, log in to the server by using the ipics user ID and password.

Note If you attempt to log in before the restore process completes, Cisco IPICS displays a message that states that the database is unavailable. Please wait and then try your login again.

Step 5 After you successfully log in to the server, navigate to System Administrator> Database to access the Manage Database window.

Step 6 From the Database Logs pane, you can view the status messages that pertain to the restore procedure by scrolling through the log entries.

Uninstalling Cisco IPICS Release 1.1(1)

When you uninstall Cisco IPICS release 1.1(1), the uninstallation process may not remove all of the directories, which can cause problems with subsequent installations.

Therefore, after you uninstall release 1.1(1), you must manually remove the /opt/cisco/ipics/database directory to complete the uninstallation process.

To uninstall Cisco IPICS release 1.1(1) and manually remove the lingering subdirectories and files, perform the following procedure:

Procedure

Step 1 Log in to the server by entering the root user ID in the hostname login: field.

Cisco IPICS prompts you for the root user password.

Step 2 Enter the password for the root user ID; then press Enter.

Step 3 Navigate to the directory where the uninstallation file is located by entering the following command:

[root]# cd _uninstall_IPICS

Step 4 To begin the uninstallation process, enter the following command:

[root]# bash uninstall-ipics

Step 5 When you are prompted to remove the Cisco IPICS software, enter Yes.

Cisco IPICS begins the uninstallation process.

After the uninstallation process has been completed, a message displays to prompt you to reboot the server.

Step 6 When you are prompted to reboot the server, enter No.

Step 7 Manually remove the subdirectories that were not removed during the uninstallation process by entering the following command:

[root]# rm -rf /opt/cisco/ipics/database

You must reboot the server for your changes to become effective.

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

[root]# service ipics restart

Resolved Caveats for Cisco IPICS - Release 1.1(1)

You can find the latest resolved caveat information for this release of Cisco IPICS by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.

Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

This section includes the following topics:

•Using Bug Toolkit

•Saving Bug Toolkit Queries

Using Bug Toolkit

To access Bug Toolkit, you need the following items:

•Internet connection

•Web browser

•Cisco.com user ID and password

To use Bug Toolkit, follow this procedure.

Procedure

Step 1 To access the Bug Toolkit, go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

Log on with your Cisco.com user ID and password.

Step 2 Click the Launch Bug Toolkit hyperlink.

Step 3 If you are looking for information about a specific caveat, enter the ID number in the "Enter known bug ID:" field.

To view all caveats for the Cisco IPICS server, go to the "Search for bugs in other Cisco software and hardware products" section, and enter Cisco IPICS Server Software in the Product Name field. Alternatively, you can scroll through the product name list and click Cisco IPICS Server Software.

To view all caveats for the PMC, enter Cisco IPICS PMC Client Software in the Product Name field or scroll through the product name list.

Step 4 Click Next. The Cisco IPICS search window displays.

Step 5 Choose the filters to query for caveats. You can choose any or all of the available options:

a. Choose the Cisco IPICS version:

•Choose the major version for the major releases (such as, 1.0 or 1.1).

A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.

•Choose the revision for more specific information; for example, choosing major version 1.1 and revision version 1 queries for release 1.1(1) caveats.

A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features and/or enhancements.

Note This option may not be available with the first release of a product.

b. Enter keywords to search for a caveat title and description, if desired.

c. Choose the Set Advanced Options, which includes the following items:

•Bug Severity level—Click the radio button that displays next to the specific severity level or the range of severity levels that you want to search for. The default specifies 1-3.

•Bug Status Group—Check the Fixed check box to search for resolved caveats. The default specifies Open and Fixed; to search for both open and fixed caveats, leave both of these check boxes checked.

•Release Note Enclosure—The default specifies Valid Release Note Enclosure.

d. Click Next.

Bug Toolkit returns the list of caveats on the basis of your query.

•You can modify your results by clicking the Refine Search button to submit another query and use different criteria.

•You can save your query for future use. See the "Saving Bug Toolkit Queries" section.

Note To see detailed online help about using Bug Toolkit, click Help on any Bug Toolkit window.

Saving Bug Toolkit Queries

Bug Toolkit allows you to create and then save your queries to monitor a specific defect or network situation. You can edit a saved search at any time to change the alert conditions, the defects being watched, or the network profile.

Follow this procedure to save your Bug Toolkit queries.

Procedure

Step 1 Perform your search for caveats, as described in the "Using Bug Toolkit" section.

Step 2 In the search result window, click the This Search Criteria button that displays on the results window.

A new window displays.

Step 3 In the Name of saved search field, enter a name for the saved search.

Step 4 Under My Bug Groups, use one of the following options to save your defects in a bug group:

•Click the Existing group radio button and choose an existing group name from the drop-down list box.

•Click the Create new group named: radio button and enter a group name to create a new group for this saved search.

Note This bug group will contain the bugs that are identified by using the search criteria that you have saved. Each time that a new bug meets the search criteria, the system adds it to the group that you chose.

Bug Toolkit saves your bugs and searches, and makes them available through the My Stuff window. (The My Stuff window allows you to view, create, and/or modify existing bug groups or saved searches. Choose the My Stuff link to see a list of all your bug groups.)

Step 5 Under Email Update Options, you can choose to set optional e-mail notification preferences if you want to receive automatic updates of a bug status change. Bug Toolkit provides the following options:

•Do NOT send me any email updates—If you choose this default setting, Bug Toolkit does not send e-mail notifications.

•Send my updates to:—Click the radio button to choose this option to send e-mail notifications to the user ID that you enter in this field. Additional notification options include

•Updates as they occur—Bug Toolkit provides updates that are based on status change.

•Weekly summaries—Bug Toolkit provides weekly summary updates.

•Apply these email update options to all of my saved searches—Check this check box to use these e-mail update options for all of your saved searches.

Step 6 To save your changes, click Save.

Step 7 A window displays the bug group(s) that you have saved. From this window, you can click a bug group name to see the bugs and the saved searches; you can also edit the search criteria.

Open Caveats for Cisco IPICS Release 1.1(1)

There are no open caveats for this Cisco IPICS release 1.1(1).

You can access information about resolved caveats by using the Bug Toolkit. Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than the release notes documentation provides. To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:

http://www.cisco.com/univercd/home/home.htm

The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:

http://www.cisco.com/go/marketplace/docstore

Ordering Documentation

You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:

http://www.cisco.com/go/marketplace/docstore

If you do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Documentation Feedback

You can provide feedback about Cisco technical documentation on the Cisco Support site area by entering your comments in the feedback form available in every online document.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to do the following:

•Report security vulnerabilities in Cisco products

•Obtain assistance with security incidents that involve Cisco products

•Register to receive security information from Cisco

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

•For emergencies only — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

•For nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

•1 877 228-7302

•1 408 525-6532

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.

Product Alerts and Field Notices

Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive these announcements by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.

To access the Product Alert Tool, you must be a registered Cisco.com user. Registered users can access the tool at this URL:

http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en

To register as a Cisco.com user, go to this URL:

http://tools.cisco.com/RPF/register/register.do

Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Support website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Support Website

The Cisco Support website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:

http://www.cisco.com/en/US/support/index.html

Access to all tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Note Before you submit a request for service online or by phone, use the Cisco Product Identification Tool to locate your product serial number. You can access this tool from the Cisco Support website by clicking the Get Tools & Resources link, clicking the All Tools (A-Z) tab, and then choosing Cisco Product Identification Tool from the alphabetical list. This tool offers three search options: by product ID or model name; by tree view; or, for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Tip Displaying and Searching on Cisco.com

If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.

To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. After using the Search box on the Cisco.com home page, click the Advanced Search link next to the Search box on the resulting page and then click the Technical Support & Documentation radio button.

To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411
Australia: 1 800 805 227
EMEA: +32 2 704 55 55
USA: 1 800 553 2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•The Cisco Online Subscription Center is the website where you can sign up for a variety of Cisco e-mail newsletters and other communications. Create a profile and then select the subscriptions that you would like to receive. To visit the Cisco Online Subscription Center, go to this URL:

http://www.cisco.com/offer/subscribe

•The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco channel product offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

http://www.cisco.com/go/guide

•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

•Cisco Press publishes a wide range of general networking, training, and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

•Internet Protocol Journal is a quarterly journal published by Cisco for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

•Networking products offered by Cisco, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

•Networking Professionals Connection is an interactive website where networking professionals share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

•"What's New in Cisco Documentation" is an online publication that provides information about the latest documentation releases for Cisco products. Updated monthly, this online publication is organized by product category to direct you quickly to the documentation for your products. You can view the latest release of "What's New in Cisco Documentation" at this URL:

http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm

•World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

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, GigaStack, 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, RateMUX, ScriptShare, SlideCast, 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. (0612R)

Copyright © 2007 Cisco Systems, Inc. All rights reserved.