Guest

Cisco ICS 7700 Series Integrated Communication Systems

Release Notes for the Cisco ICS 7750 for System Software Release 2.x.x

  • Viewing Options

  • PDF (709.6 KB)
  • Feedback
Release Notes for the Cisco ICS 7750 for System Software Release 2.x.x

Table Of Contents

Release Notes for the Cisco ICS 7750 for System Software Release 2.x.x

Contents

System Requirements

Hardware Summary

Software Summary

SPE Support

MRP and ASI Memory Upgrades

PC Requirements

Installing Microsoft Terminal Services Client

System Management

Accessing ICSConfig

Accessing ICS System Manager

Accessing Cisco CallManager

Accessing the SPE Windows Interface Through Terminal Services Client

Accessing the SPE Windows Interface Through Directly Connected Peripherals

Accessing SPEs through Telnet

Accessing the IOS CLI on ASIs, MRPs and the SSP Through Telnet

Accessing Processor Cards Through the SAP

New and Changed Information

New Hardware Features in Release 2.3.0

New Hardware Features in Release 2.2.0

New Hardware Features in Release 2.1.0

New Software Features with Release 2.2.0

New Software Features and Software Changes in Release 2.1.0

Upgrading to System Software Release 2.2.0 or 2.3.0

Backing Up System Software Data

Accessing the Backup Utility

Scheduling a Backup

Using Backup Now

Restoring System Data to the SPE Running System Manager

SPE310 Running System Manager Restore Scenarios

Preparing to Restore Data to the SPE310 Running System Manager

Using the Restore Wizard

Starting the Restore Process

Cisco CallManager Backup and Restore Guidelines

Installing and Configuring Cisco CallManager Extended Services 2.2(2)

Installing Cisco CallManager Extended Services 2.2(2)

Connecting the Peripherals

Accessing the CD

Installing the Software

Configuring Cisco CallManager Extended Services

Setting Up the Directory Link

Limitations and Restrictions

Installing Windows 2000 Upgrades on SPEs

Installing Software on the SPE Running System Manager

Changing the Host Name of the SPE Running System Manager

Guidelines for Host Names

Assigning a New Host Name

Updating Microsoft SQL Server with the New Host Name

Best Practices for Using Microsoft SQL Server

Best Practices for Configuring DHCP

Installing or Enabling Microsoft DHCP Server on the SPE Running System Manager

Installing or Enabling a DHCP Server on Other SPEs or Other Servers

SSP Error Messages

Best Practices for Using the IOS CLI

ICSConfig Tasks

ICS System Manager Tasks

Using Peripherals with SPEs

Best Practices for Using Peripherals with SPEs

Removing SPEs

Configuring Cisco ICS 7750 Gateways in Cisco CallManager

Cisco IP Phone Reconfiguration Following SPE Replacement or Change in SPE IP Address

Providing Backup Power

Connecting to the Catalyst 3524-PWR XL 10/100 Inline-Power Ports

Important Notes

Voice Over IP

Using the Cisco ICS 7750 with the PSTN

PSTN to MRP Connectivity Using FXO Connections

IP Provisioning

Open Caveats in Release 2.3.0

Open Caveats in ICS System Manager in Release 2.3.0

Software Upgrade Problems

Login Problems

Open Caveats in the Fault Management Module in Release 2.3.0

Software Installation Problems

SPE Problems

SAP Problems

CDP Problems

Open Caveats in Release 2.2.0

Open Caveats in ICS System Manager in Release 2.2.0

Open Caveats in the Fault Management Module in Release 2.2.0

Software Installation Problems

SPE and USB CD-ROM Problems

SAP Problems

CDP Problems

Open Caveats in Release 2.1.0

Open Caveats in ICS System Manager in Release 2.1.0

DHCP/BOOTP Problems

MRP Problems

SSP Problems

Restore Problems

Security Issues

Cisco IP Phone Reconfiguration Problems

Miscellaneous Problems

Open Caveats in the Fault Management Module in Release 2.1.0

Software Installation Problems

SPE and USB CD-ROM Problems

SAP Problems

CDP Problems

Open Caveats Related to IP Telephony in Release 2.1.0

Documentation Updates

Cisco ICS 7750 Administration and Troubleshooting Guide

Cisco ICS 7750 Hardware Installation Guide

Related Documentation

Cisco ICS 7750 Documents

Release 2.3.0 Documents

Release 2.2.0 Documents

Release 2.1.0 Documents

Documentation Set

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for the Cisco ICS 7750 for System Software Release 2.x.x


Current Release:

2.3.0—June 4, 2002

Previous Releases:

2.2.0—March 27, 2002

2.1.0—December 21, 2001

These release notes describe the features, modifications, and caveats for Cisco Integrated Communications System 7750 (Cisco ICS 7750) release 2.3.0.

Use these release notes with the documents listed in the "Related Documentation" section.


Caution We strongly recommend that you read these release notes before using your Cisco ICS 7750.

Contents

This document discusses the following topics:

System Requirements

New and Changed Information

Upgrading to System Software Release 2.2.0 or 2.3.0

Backing Up System Software Data

Restoring System Data to the SPE Running System Manager

Cisco CallManager Backup and Restore Guidelines

Installing and Configuring Cisco CallManager Extended Services 2.2(2)

Limitations and Restrictions

Important Notes

Open Caveats in Release 2.3.0

Open Caveats in Release 2.2.0

Open Caveats in Release 2.1.0

Documentation Updates

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

System Requirements

This section describes the Cisco ICS 7750 requirements and has the following sections:

Hardware Summary

Software Summary

System Management

PC Requirements

Hardware Summary

The Cisco ICS 7750 chassis has six universal slots that can contain system processing engine (SPE), multiservice route processor (MRP), and analog station interface (ASI) cards, making customization possible at the factory or in the field by a technician who is IP Telephony certified for the Cisco ICS 7750.

Table 1 lists the number of cards and power supply modules that the Cisco ICS 7750 supports.

Table 1 Number of Cards Supported

Card
Chassis Slot
Min. Required
Max. Allowed

ASI81, ASI160, MRP3-8FXS, MRP3-16FXS1

1 through 6

0

5

MRP200 or MRP3002

1 through 6

0

5

SPE3103

1 through 64

1

5

System switch processor (SSP)

7

1

1

System alarm processor (SAP)

8

1

1

Power-supply module

POWER SUPPLY 1
or
POWER SUPPLY 2

1

2

1 The MRP3-8FXS and the MRP3-16FXS are flash-based versions of the ASI81 and the ASI160, respectively.

2 The MRP300 is a flash-based version of the MRP200.

3 SPE 310s are required in order to run system software release 2.1.0 or later.

4 The SPE running System Manager is installed in Slot 6 by default.


Software Summary

Table 2 shows the software that is pre-installed on system cards when you receive a factory-configured chassis.

Table 2 Pre-Installed Software

Software Type
Cards
ASIs and MRPs
SPE running System Manager
Other SPEs
SSP
SAP

Firmware

SAP software
AC 1_0_6

Operating system

Microsoft Windows 2000 Server

Microsoft Windows 2000 Server

Router/gateway/
switch configuration and management

Cisco IOS Release 12.2(4)XL1 (2.1.0)

Cisco IOS Release 12.2(4)XL4 (2.2.0)

Cisco IOS Release 12.2(4)YH (2.3.0)

Cisco IOS Release 12.0(5.2)XU (2.1.0)

Cisco IOS Release 12.0(5)WC2b1 (2.2.0)

Cisco IOS Release 12.0(5)WC5 (2.3.0)

System management

ICS System Software1

ICS Core Software2

1 ICS System Software includes ICS System Manager, Cisco Network Registrar (CNR) 3.5(3), Fault Management Module (FMM), Java Runtime Environment (JRE) version 1.2.2 (release 2.1.0) or JRE version 1.3.1 (release 2.2.0), and Microsoft SQL Server 7.0 Service Pack 2.

2 ICS Core Software includes the following components: FMM, ICSSD, and ICSRshSvc.


2 ICS System Manager software must be installed on one SPE 310 in a Cisco ICS 7750 chassis. ICS Core Software must be installed on all SPEs in the chassis other than the SPE running System Manager.



2 Software approved for use on the SPE 310 in the Cisco ICS 7750, such as Cisco CallManager, can be installed on any SPE 310 in the chassis.



2 If you are using system software release 2.1.0 and you intend to upgrade to Cisco CallManager 3.2(1), you must install a system software patch and Microsoft SQL Service Pack 3 before upgrading Cisco CallManager on an SPE. Refer to the Release Notes for Cisco CallManager 3.2(1) on the Cisco ICS 7750.



SPE Support

Release 2.x.x and later is supported only on SPE 310s. The SPE 310 offers a keyboard port, a video port, and two universal serial bus (USB) ports supporting standard USB devices such as mice, keyboards, and CD-ROM drives.

The SPE 310 also features a 700-MHz Pentium III processor, a 20.4-GB hard disk drive, and 512 MB of onboard memory. You can upgrade SPE 310 memory to a maximum of 1536 MB by installing 256-MB or 512-MB dual in-line memory modules (DIMMs) in one or both of the SPE DIMM slots.

For instructions on how to upgrade the memory on SPE 310s, refer to Installing Memory, PVDM, and VPN Modules in ASI Cards, MRP Cards, and SPE Cards in the Cisco ICS 7750.


Note A "Y" splitter cable is shipped with SPE 310s to support the connection of a keyboard and a PS/2 mouse for software installation and upgrades. To install or upgrade ICS System Manager, ICS Core Software, or IOS software, a PC that meets the specifications in "PC Requirements" is required.


MRP and ASI Memory Upgrades

MRPs and ASIs ship with 64 MB of RAM. You can upgrade MRP and ASI memory to 80 MB, 96 MB, or 128MB by installing a dual in-line memory module (DIMM) in the DIMM slot on the card.

Refer to Installing Memory, PVDM, and VPN Modules in ASI Cards, MRP Cards, and SPE Cards in the Cisco ICS 7750 for instructions on how to upgrade the memory on these cards.

PC Requirements

You need a PC to complete initial system configuration and to perform system management tasks. Ensure that the PC meets the following requirements:

CPU: Pentium-class 233 Mhz or faster

Memory: At least 64 MB of RAM

Hardware:

CD-ROM drive

Network Interface Card

Available COM port

Display: Enhanced VGA monitor with at least a 800 x 600 pixel display and at least 256 colors
(a 1024 x 768 pixel display is recommended)

Operating system: Microsoft Windows 98, Windows NT 4.0, Windows 2000, Windows Me, or Windows XP

Web browser: Netscape Communicator 4.7 or later or Internet Explorer 5.01 or later

Communication software: Microsoft Terminal Services Client and terminal emulation software (such as HyperTerminal)


Note Refer to the Cisco ICS 7750 Getting Started Guide for information about initial hardware installation and software configuration.


Installing Microsoft Terminal Services Client

If Microsoft Terminal Services Client is not installed on your PC, there are two ways to install it:

Installing Microsoft Terminal Services Client from the Web

Installing Microsoft Terminal Services Client from the SPE Running System Manager

Installing Microsoft Terminal Services Client from the Web

Complete the following steps to install the software from the web:


Step 1 Open Netscape Communicator or Microsoft Internet Explorer.

Step 2 From www.microsoft.com, click this path: Downloads: Windows: Windows 2000: Downloads: Recommended Updates: Terminal Services Advanced Client.

Step 3 Follow the instructions to download and install Microsoft Terminal Services Client on a PC.


Installing Microsoft Terminal Services Client from the SPE Running System Manager

The Microsoft Terminal Services Client installer is available on all SPEs. Complete the following steps to install Microsoft Terminal Services Client on a PC from the SPE:


Step 1 On the PC, choose Start > Run.

Step 2 Enter the following command to open Windows Explorer:

explorer

Step 3 In Windows explorer, choose Tools -> Map Network Drive.

The Map Network Drive dialog appears.


Note The following steps are for Windows 2000. If you are using a different Windows operating system on the PC, the steps might differ slightly.


Step 4 In the Folder field, enter \\<SPE IP address>\c$.

Step 5 Click Connect using a different user name.

The Connect as dialog appears.

Step 6 In the User name field, enter administrator.

Step 7 In the Password field, enter your administrator password (the default is changeme).

Step 8 Click OK.

Step 9 Click Finish.

Step 10 On the PC, navigate to <drive>\w2ks\system32\clients\tsclient\win32\disks, where <drive> is the letter of the PC hard drive (such as D:) that you mapped to the SPE.

Step 11 Copy the disk1 and disk2 folders from the SPE to the PC.

Step 12 On the PC, navigate to the disk1 folder.

Step 13 Double-click setup.exe.

Step 14 Follow the instructions to install Microsoft Terminal Services Client on the PC.


System Management

You can manage the Cisco ICS 7750 through standard interfaces such as a web browser and terminal emulation software. This section describes the system management interfaces that are available:

Accessing ICSConfig

Accessing ICS System Manager

Accessing Cisco CallManager

Accessing the SPE Windows Interface Through Terminal Services Client

Accessing the SPE Windows Interface Through Directly Connected Peripherals

Accessing SPEs through Telnet

Accessing the IOS CLI on ASIs, MRPs and the SSP Through Telnet

Accessing Processor Cards Through the SAP


Note You can use the Simple Network Management Protocol (SNMP) Management Information Base (MIB) to manage the Cisco ICS 7750 with software such as CiscoWorks2000 and HP OpenView. For more information about SNMP and MIBs, refer to the "System Monitoring" chapter in the Cisco ICS 7750 Administration and Troubleshooting Guide.


Accessing ICSConfig

The ICS System Manager configuration program (ICSConfig) enables you to enter system configuration data such as the IP addresses of the cards in the Cisco ICS 7750 chassis. The
Cisco ICS 7750 Getting Started Guide provides instructions on how to complete initial configuration with ICSConfig.

You can also use ICSConfig after initial system configuration is complete to modify key system settings. Complete the following steps to access ICSConfig:


Step 1 On a PC, open Netscape Communicator or Microsoft Internet Explorer.

Step 2 In the Location or Address field, enter the following URL, replacing IP address with the IP address of the SPE running System Manager:

http://IP address/icsconfig

You are prompted for a user ID and password.

Step 3 Log in as an administrator (the default user ID is administrator), and enter your password (the default is changeme).

Step 4 Click OK.


Accessing ICS System Manager

You can use ICS System Manager to access, configure, monitor, and manage the chassis and its cards.

When you have installed and configured your system as described in the
Cisco ICS 7750 Getting Started Guide, complete the following steps to access ICS System Manager:


Step 1 On a PC, open Netscape Communicator or Microsoft Internet Explorer.

Step 2 In the Location or Address field, enter the following URL, replacing IP address with the IP address of the SPE running System Manager:

http://IP address/ics

Step 3 Log in as the super administrator (user ID is admin), and enter your password (the default is admin).

Step 4 Click Login.


Accessing Cisco CallManager

You can install Cisco CallManager on SPE 310s and use the software to configure call admission control, route plans, voice gateways (such as MRPs or ASIs with installed VICs or VWICs), Cisco IP Phones, and other features associated with transmitting voice traffic over an IP network.

You can access Cisco CallManager on the Cisco ICS 7750 by completing the following steps:


Step 1 Click the Configure tab on the ICS System Manager home page.

Step 2 Click Applications.

The page refreshes, displaying a table that contains information about the SPEs and the applications that are running on them.

Step 3 Click the desired CallManager Administration: IP address/CCMAdmin link (where IP address is the IP address of the target SPE running Cisco CallManager).

Step 4 Log in to CallManager as an administrator.



Note You can also access Cisco CallManager on the Cisco ICS 7750 by entering the following URL, replacing IP address with the IP address of an SPE running Cisco CallManager:
http://IP address/CCMAdmin



Note For additional information about Cisco CallManager, refer to the Cisco CallManager documentation.


Accessing the SPE Windows Interface Through Terminal Services Client

You can use Terminal Services Client to access the SPE Windows user interface and perform standard Windows operations on the SPE.

To access the SPE Windows interface through Terminal Services Client, complete the following steps:


Step 1 On the PC that you use to administer the Cisco ICS 7750, choose Start > Programs > Terminal Services Client > Client Connection Manager.

Step 2 Use the Client Connection Manager to open a Terminal Services connection with the target SPE:

If you already have a Terminal Services Client connection defined for the target SPE, choose it, and choose File > Connect.

If you do not have a Terminal Services Client connection defined for the target SPE, choose File > New Connection, and follow the instructions in the wizard, and then choose File > Connect.

The Terminal Services Client window opens. You can use Terminal Services Client to access standard Windows utilities on the SPE, such as Windows Explorer and the Control Panel.


Accessing the SPE Windows Interface Through Directly Connected Peripherals

You can connect a monitor, keyboard, and mouse directly to the SPE to access the Windows user interface, as follows:


Step 1 Connect the monitor cable to the video port on the SPE 310, and power on the monitor.

Step 2 Continue as follows, based on the type of peripherals that you are using:

USB—Connect a USB keyboard to one SPE USB port and a USB mouse to the other SPE USB port.

PS/2—Connect the "Y" splitter cable for your keyboard and mouse to the keyboard/mouse port on the target SPE, and then connect your keyboard and mouse to the available ends of the "Y" splitter cable.


Note If you are using the "Y" splitter cable to connect a PS/2 mouse and a keyboard to the SPE, the keyboard and mouse must be connected at or before SPE reboot to be recognized by the operating system. This is not the case with a USB keyboard and mouse, which usually are recognized without an operating system reboot.



Note For a summary of the issues related to the connection of peripherals to SPEs, as well as best practices on how to use peripherals with SPEs, see the "Using Peripherals with SPEs" section.



Note For a list of USB peripherals that have been tested on the Cisco ICS 7750, refer to the "Connecting a Monitor, Keyboard, and Mouse to the SPE Card" section in the
Cisco ICS 7750 Getting Started Guide.


Step 3 Use the keyboard, mouse, and monitor to access standard Windows utilities on the SPE, such as Windows Explorer and the Control Panel.


Accessing SPEs through Telnet

You can access SPEs through Telnet, as follows:


Step 1 On a PC, choose Start > Run.

Step 2 Enter the following command to open a Telnet session, where IP address is the IP address of the SPE that you wish to communicate with:

telnet IP address 5000

Step 3 Log in as an administrator (user ID administrator), and enter your password (the default is changeme).


Accessing the IOS CLI on ASIs, MRPs and the SSP Through Telnet

You must use the IOS command-line interface (CLI) to configure ASIs, MRPs, and the SSP. You can open a Telnet or HyperTerminal session to access individual cards so that you can enter IOS software commands on them.


Note Some IOS commands are not intended for use on the Cisco ICS 7750 through the CLI. See the "Best Practices for Using the IOS CLI" section.


To access an ASI, MRP or SSP through Telnet, complete the following steps:


Step 1 On a PC, choose Start > Run.

Step 2 Enter the following command to open a Telnet session, where IP address is the IP address of the card that you wish to communicate with:

telnet IP address

Step 3 Enter your login password.



Note For additional information about IOS software configuration, refer to the Cisco ICS 7750 Software Configuration Guide.


Accessing Processor Cards Through the SAP

The SAP provides console access to any other processor card in the Cisco ICS 7750 chassis. By connecting your PC to the console port on the SAP, or by dialing in to a modem that is connected to the console port, you can access a menu that can help you debug and troubleshoot system cards.

To access this text-based menu, complete the following steps:


Step 1 If your PC is not already directly connected to the SAP console port, you can use a RJ-45-to-DB-9 adapter with a rolled EIA/TIA-232 cable or the supplied console (blue) cable to make the connection, as follows:

Connect the SAP console port to an available COM port on your PC.

Or

Connect a modem to the SAP console port to enable a dial-up connection (9600 baud, maximum).


Note For instructions on how to connect the SAP directly to your PC or to a modem, refer to the "Connecting to Card Ports" section or the "Connecting a Modem" section, respectively, in the "Installing the Cisco ICS 7750" chapter in the Cisco ICS 7750 Hardware Installation Guide. For instructions on how to configure your modem for remote dial-up access to System Manager, refer to the "Maintaining and Upgrading the System" chapter in the
Cisco ICS 7750 Administration and Troubleshooting Guide.


Step 2 On your PC, open HyperTerminal. On PCs running Windows 2000, a typical HyperTerminal path is Start > Programs > Accessories > Communications > HyperTerminal.

Step 3 Open a connection with the SAP, as follows:

If you already have a HyperTerminal connection defined for the SAP, choose File > Open, and double-click the appropriate icon.

If you do not have a HyperTerminal connection defined for the SAP, choose File > New Connection, and enter the following information:

a. In the Connection Description dialog box, enter a name for the connection in the Name field, select an icon to be associated with the connection, and click OK.

b. In the Phone Number dialog box, enter the following information:

If the PC is directly connected to the SAP, click the drop-down arrow to view a list of choices for the Connect Using field, choose the PC COM port that is connected to the SAP, and click OK.

If the PC is remotely connected (through a modem) to the SAP, click the drop-down arrow to view a list of choices for the Connect Using field, choose the modem installed in your PC, enter the area code and phone number of the remote Cisco ICS 7750 in the Area Code and Phone Number fields. Click OK.

c. In the Properties dialog box, click the drop-down arrow to view a list of choices for the Bits per Second field, choose 9600, and click OK.

A terminal window opens.

Step 4 Press Ctrl-backslash (\). A menu similar to the following is displayed:

Please wait ...
 A. System Alarm Processor
 B. MASTER System Processing Engine
 C. System Switch Processor

 1. Slot 1: Multiservice Route Processor
 2. Slot 2: Multiservice Route Processor
 3. Slot 3: Multiservice Route Processor
 4. Slot 4: Multiservice Route Processor
 5. Slot 5: Multiservice Route Processor
 6. Slot 6: System Processing Engine
Make a selection to switch:

Step 5 Enter the number or letter corresponding to the card or slot to which you want to connect.

You are now connected to the selected card and can enter the CLI commands that are supported on that card.


New and Changed Information

This section describes new features and changes in functionality in release 2.1.0:

New Hardware Features in Release 2.3.0

New Hardware Features in Release 2.2.0

New Hardware Features in Release 2.1.0

New Software Features with Release 2.2.0

New Software Features and Software Changes in Release 2.1.0

New Hardware Features in Release 2.3.0

Table 3 shows the new hardware that is available in release 2.3.0.

Table 3 New Hardware in Release 2.3.0

Card/Module Type
Description

MRP

MRP300—An enhanced version of the MRP200, with onboard flash memory.

MRP3-8FXS—An enhanced version of the ASI81, with onboard flash memory.

MRP3-16FXS—An enhanced version of the ASI160, with onboard flash memory.


New Hardware Features in Release 2.2.0

Table 4 shows the new hardware that is available in release 2.2.0.

Table 4 New Hardware in Release 2.2.0

Card/Module Type
Description

VICs

VIC-4FXS/DID—Four-port analog FXS/DID voice/fax interface card


New Hardware Features in Release 2.1.0

Table 5 shows the new hardware that is available in release 2.1.0.

Table 5 New Hardware in Release 2.1.0

Card/Module Type
Description

System processing engine 310 (SPE 310)

You can connect a USB CD-ROM drive to an SPE 310 for software installation and SPE reimaging.

You can connect a keyboard, mouse, and monitor to an SPE 310 for software installation and maintenance purposes.

Analog station interface 81 (ASI 81) card

Contains an 8-port Foreign Exchange Station (FXS) module and a slot for any one of the VIC/WIC/VWIC modules that are currently supported on MRPs, delivering digital and analog voice trunks and WAN routing interfaces, completely integrating voice and data networking.

ASI 160 card

Contains a 16-port FXS module, delivering high-density analog ports that enable you to continue to support analog telephones as you migrate to Cisco IP Phones.

VICs

VIC-2DID—Two-port analog DID voice/fax interface card

VIC-2BRI-NT/TE—Two-port ISDN BRI voice/fax interface card (network and terminal side)

VIC-2FXO-M1—Two-port FXO voice/fax interface card with battery reversal detection and caller ID support (for the United States)

VIC-2FXO-M2—Two-port FXO voice/fax interface card with battery reversal detection and caller ID support (for Europe)

VIC-2FXO-M3—Two-port FXO voice/fax interface card with battery reversal detection and caller ID support (for Australia)

VWICs1

VWIC-1MFT-E1—One-port E1/fractional E1 multiflex trunk with CSU/DSU

VWIC-2MFT-E1—Two-port E1/fractional E1 multiflex trunk with CSU/DSU

1 In addition to E1 support, system software release 2.1.0 includes support for PRI voice on both T1 and E1 interfaces. Refer to the
Cisco ICS 7750 Software Configuration Guide for PRI configuration instructions.


New Software Features with Release 2.2.0

Table 6 shows new software features that are available for use with system software release 2.2.0.


Note For a list of the new features available in Cisco CallManager 3.2(1), refer to
the Release Notes for Cisco CallManager 3.2(1). For a list of the new IOS features available on ASIs and MRPs in system software release 2.2.0, refer to the Release Notes for Cisco IOS Release 12.2(2)XL4 on the Cisco ICS 7750. For a list of the new features available in Cisco IOS Release 12.2, refer to the Cross-Platform Release Notes.


Table 6 New Software Features in System Software Release 2.2.0

Module/Feature
Description of Change

Cisco Customer Response Applications (CRA) 2.2(2) support

Cisco CRA 2.2(2) for the Cisco ICS 7750 are available for use beginning with system software release 2.2.0. For additional information, refer to Installing Cisco Customer Response Applications on the Cisco ICS 7750 and the Release Notes for Cisco Customer Response Applications 2.2(2) on the Cisco ICS 7750.

Cisco Unity Voice Mail 3.1(2) support

You can upgrade from Cisco Unity Voice Mail 3.0(1) to Cisco Unity Voice Mail 3.1(2) on the Cisco ICS 7750. For additional information, refer to Upgrading from Cisco Unity Voice Mail Release 3.0(1) to Release 3.1(2) on the Cisco ICS 7750.


New Software Features and Software Changes in Release 2.1.0

Table 7 shows new software features and changes in software functionality introduced in system software release 2.1.0.


Note For a list of the new features available in Cisco CallManager 3.1(3a), refer to
the Release Notes for Cisco CallManager 3.1(3a). For a list of the new IOS features available on ASIs and MRPs in system software release 2.1.0, refer to the Release Notes for the Cisco ICS 7750 for Cisco IOS Release 12.2(2)XL1. For a list of the new features available in Cisco IOS Release 12.2, refer to the Cross-Platform Release Notes.


Table 7 New Software Features and Software Modifications in System Software Release 2.1.0

Module/Feature
Description of Change

Cisco Unity Voice Mail 3.0(1) support

Cisco Unity Voice Mail 3.0(1) for the Cisco ICS 7750 is available beginning with system software release 2.1.0. For additional information, refer to the Installing Cisco Unity Voice Mail on the Cisco ICS 7750 and the Release Notes for Cisco Unity Voice Mail Release 3.0(1) for the Cisco ICS 7750.

Support for standard Cisco CallManager functionality

"Native" Cisco CallManager functionality (making available the feature set that is available on other Cisco CallManager platforms in Cisco CallManager).

You can install Cisco CallManager on any SPE, including the SPE running System Manager.

Cisco CallManager can function as a publisher or subscriber on any SPE.

Cisco CallManager can operate in a cluster with other Cisco CallManager servers that are installed in the following configurations:

On another SPE in the same Cisco ICS 7750

On another SPE in a different Cisco ICS 7750

On any other server platform supported by Cisco CallManager (such as the Cisco Media Convergence Server (MCS) product family)

Cisco CallManager Extended Services support

The Extended Services feature is included with Cisco CallManager Release 3.1(2c) or later and adds the following IP Telephony capabilities to the Cisco ICS 7750:

Cisco CallManager Extension Mobility—Enables users to log in to any Cisco IP Phone 7960/7940 and have that phone temporarily use their own profile. The Cisco IP Phone adopts their personal phone numbers, speed dials, services links and other user-specific properties. After the user logs out, the Cisco IP Phone reverts to the original user profile.

After this feature is configured, several employees can share the same office space on a rotating basis. This arrangement is often used for sales offices and telecommuting groups where employees usually work elsewhere and come into the office infrequently.

For Cisco CallManager Extended Services installation instructions, see the "Installing Cisco CallManager Extended Services 2.2(2)" section. For Extended Services configuration information, see the "Configuring Cisco CallManager Extended Services" section and refer to the "Configuring Cisco CallManager Extension Mobility" chapter in the Cisco CallManager Extended Services Administrator's Guide.

Cisco CallManager AutoAttendant—Answers incoming calls with a Welcome greeting and plays a menu of prompts. The three prompts enable callers to choose among these options only:

Press "0" for the operator.

Press "1" to enter an extension number.

Press "2" to spell by name.

This feature provides callers with direct access to people (by entering their name) or to known extension numbers, without requiring the intervention of a company operator. Callers who need assistance can choose to transfer to the operator.

For Cisco CallManager Extended Services installation instructions, see the "Installing Cisco CallManager Extended Services 2.2(2)" section. For Extended Services configuration information, see the "Configuring Cisco CallManager Extended Services" section and refer to the "Configuring Cisco CallManager AutoAttendant" chapter in the Cisco CallManager Extended Services Administrator's Guide.

Cisco CallManager Music on Hold support

The Cisco CallManager integrated Music on Hold feature is available for use on the Cisco ICS 7750. This feature makes music or recordings available to a caller when the person being called places the call on hold. Music on Hold is also available when the call is placed on network hold for these states:

Transfer hold

Conference hold

Park hold

In the Cisco ICS 7750, the Music on Hold server, which is installed as an option from Cisco CallManager Administration, can coexist on the same SPE 310 with Cisco CallManager. Only one Music on Hold server can be installed on the Cisco ICS 7750. Refer to the "Music on Hold Configuration" chapter in the Cisco CallManager Administration Guide for instructions on how to configure this feature.


Caution When Cisco CallManager and the Music on Hold server coexist on the same SPE 310, do not start the translation of audio source files during business hours. The audio translator tries to use all available CPU time and Cisco CallManager can experience errors or slowdowns in processing phone calls.

The Music on Hold server is a software application that provides streaming audio resources for calls placed on hold. When an end device or feature places a call on hold, Cisco CallManager connects the held call to a music file or recorded audio file. When the held call is retrieved, Cisco CallManager disconnects it from the Music on Hold source file. Refer to the "Music on Hold" chapter in the Cisco CallManager System Guide and the "Music on Hold Configuration" chapter in the Cisco CallManager Administration Guide for more information about this feature.

Note The Cisco ICS 7750 supports only audio (.wav) files stored on the SPE 310 hard disk as a data source. The Cisco ICS 7750 does not have a sound card for supporting external audio sources such as a looping tape recorder, a radio, or a music CD.

Software installation and upgrade changes

Cisco CallManager is no longer installed on SPEs at the factory—you can install Cisco CallManager during initial system installation and configuration (refer to the Cisco ICS 7750 Getting Started Guide for instructions).

Cisco CallManager gateways (MRPs) are configured by using the CallManager administration interface, instead of having ICS System Manager automatically register MRPs with Cisco CallManager.

ICS System Manager deployment model

For each Cisco ICS 7750 system, only one ICS System Manager is installed on an SPE at the factory (the SPE in Slot 6).

For each Cisco ICS 7750 system, only one instance of ICS System Manager is supported.

Note ICS Core Software runs on all SPEs except the SPE running System Manager.

ICS System Manager software module changes

ICSConfig—ICSConfig has been enhanced to detect system problems in areas such as the Simple Network Management Protocol (SNMP) community string, passwords, and IP addresses. ICSConfig displays error messages and provides steps to help you troubleshoot these problems.

MRP Manager—MRP Manager has been removed—you must configure ASIs and MRPs with the IOS CLI. (For IOS CLI instructions, refer to the Cisco ICS 7750 Software Configuration Guide.)

COM Port Manager—COM Port Manager is a new module that enables you to control SPE COM port usage, instead of having the system assign the SPE COM ports automatically.

Monitor—Cisco CallManager inventory items are not monitored by ICS System Manager—you must track these items in Cisco CallManager.

Security—Four new security user groups have been added: System Maintenance, System Setup, Fan Manager, and COM Port Manager.

System Maintenance—You can now use the ICS system software backup utility directly from ICS System Manager (for system software backup). For system software backup instructions, see the "Backing Up System Software Data" section. For system software restore instructions, see the "Restoring System Data to the SPE Running System Manager" section.

Note ICS System Manager does not back up and restore data for any other applications, including Cisco CallManager. For Cisco CallManager backup and restore instructions, refer to Backing Up and Restoring Cisco CallManager 3.1 or
Backing Up and Restoring Cisco CallManager 3.2.


Upgrading to System Software Release 2.2.0 or 2.3.0

For upgrade instructions, refer to Upgrading the Cisco ICS 7750 to System Software Release 2.2.0 or Upgrading the Cisco ICS 7750 to System Software Release 2.3.0.

Backing Up System Software Data

This section explains how to back up SPE310 registry settings, ICS System Manager database records, and IOS configuration files for ASIs and MRPs:

Accessing the Backup Utility

Scheduling a Backup

Using Backup Now


Caution Before you back up system data, make sure that no two devices (such as Cisco IP Phones) are assigned the same IP address. If any two devices are using the same IP address, you might experience problems if you later attempt to restore from this backup.


Note The backup procedures in this section do not cover other software that you can install on the system, such as Cisco CallManager. For instructions on how to back up and restore Cisco CallManager data, see the "Cisco CallManager Backup and Restore Guidelines" section and refer to the
Cisco CallManager documentation that tells how to back up the Cisco CallManager release that you are using.



Note Before starting a backup, make sure that at least 75 MB of storage space is available on the target device.



Note Record the SNMP community strings, IP addresses of system cards, and the Windows 2000 administrator password (user ID administrator) in a secure location. To restore system data, the system must be configured with the same settings as were in use at the time the backup was made.



Note You cannot currently back up system COM port settings.



Tip Write the IP addresses of system cards on adhesive labels, and affix them to the card faceplates. Record your Windows 2000 administrator password and SNMP community strings in a secure location. Having this information available can facilitate troubleshooting and make it easier to restore system data.


Accessing the Backup Utility

Follow these steps to access the backup utility in ICS System Manager:


Step 1 On a PC, access ICS System Manager (see the "Accessing ICS System Manager" section).

Step 2 Click the System Maintenance tab.

The Backup History page appears.

To schedule a backup, go to the "Scheduling a Backup" section.

To immediately start a backup, go to the "Using Backup Now" section.


Scheduling a Backup

Follow these steps to schedule a backup.


Note Schedule Backup does not back up all system information. Schedule Backup will only back up SPE310 registry settings, ICS System Manager database records, and IOS configuration files for MRPs and ASIs that do not have Flash memory (MRP200, ASI160, ASI81). No configuration files for Flash-based cards (MRP300, MRP3-8FXS, MRP3-16FXS) or for the SSP will be backed up. Flash-based cards and the SSP must be backed up manually.



Step 1 Access the backup utility (see the "Accessing the Backup Utility" section).

Step 2 Click Schedule Backup.

Step 3 Enter the required information in the following fields:

a. Backup Name—A unique name for the backup.

b. Description—A statement that can identify the backup.

c. IP/Hostname—The IP address or host name of the device on which you want to store your backup files.


Note The device on which you intend to store your backup files must be running the Windows operating system.


d. Shared Pathname—The Windows path name to the remote device (computer on the network) where you want to store your backup files. For example, sharename\path.

e. User Name—The name that you use to log in to your network.

f. Password—The password that you use to gain access to your network.

g. Domain Name—(Optional) The domain name that you use to gain access to your network (for example, MyCompany_Eng).

Step 4 Under Occurrence, click the appropriate radio button:

Once

Daily

Weekly

Monthly

Step 5 Under Occurrence Date/Time, enter the required information:

a. Start Date—The date on which this backup should begin.

b. Time—The time when this backup should begin.

c. Weekly on—If you selected Weekly at Step 3, the day of the week that the backup should take place.

d. Monthly on—If you selected Monthly at Step 3, the day of the month that the backup should take place.

e. End Date/No End Date—Choose the appropriate radio button:

End Date—If you do not want this backup schedule to continue past a particular date, click this radio button, and enter the date.

No End Date—If you want this backup schedule to continue indefinitely, click this radio button.

Step 6 Click Submit to accept the backup parameters that you specified.

Step 7 Click History.

The Backup History page displays. The backup schedule that you entered is shown under Existing Schedules.


Using Backup Now

Follow these steps to start the backup process:


Step 1 Access the backup utility (see the "Accessing the Backup Utility" section).

Step 2 Click Backup Now.

Step 3 Enter the required information in the following fields:

a. Backup Name—A unique name for the backup.

b. Description—A statement that can identify the backup.

c. IP/Hostname—The IP address or host name of the device on which you want to store your backup files.


Note The device on which you intend to store your backup files must be running the Windows operating system.


d. Shared Pathname—The Windows path name to the remote device (computer on the network) where you want to store your backup files. For example, sharename\path.

e. User Name—The name that you use to log in to the remote computer.

f. Password—The password that you use to gain access to the remote computer.

g. Domain Name—(optional) The domain name that you use to gain access to your network (for example, MyCompany_Eng).


Note Enter the domain name carefully. Because of a limitation in Windows 2000, even if you enter the wrong domain name, the backup will seem to complete successfully.


Step 4 Click Submit to start the backup.

Step 5 When the backup is complete, press Continue.

The Backup History page appears, showing information about the backup.

Step 6 You must manually back up the IOS configuration files for the SSP and each Flash-based MRP or ASI (MRP300, MRP3-8FXS, MRP3-16FXS).

a. Telnet to the MRP, ASI, or SSP card from the remote device (computer on the network) where you stored your backup files in Step 3 above.


Note If the remote device (computer on the network) where you stored your backup files does not have Telnet access to the chassis cards, you may save the backup configuration files on a PC that has Telnet access to the chassis cards and then copy them to the remote device.


b. Enter the enable command and your IOS enable password to enter privileged EXEC command mode:

Switch> enable 
Password: password 
Switch# 

c. Enter the following command to display the startup configuration:

Switch# show startup-config

d. Copy and paste the output from the show startup-config command into a text file where you stored your backup files:

Choose Start > Run.

Enter the following command to open Notepad:

notepad.exe

Select and copy the startup-config output from the Telnet console, and paste it into the Notepad window.


Note Do not include the - More - lines if they are displayed in the output. Select the contents from the Telnet console, and copy them to the clipboard. Go to the Notepad window, and paste the clipboard contents.


If - More- is displayed at the bottom of the Telnet console, press the space bar to display the next screen. Copy from the Telnet console again, and paste to the Notepad window. Repeat until the entire startup configuration has been displayed, copied, and pasted.

From Notepad, choose File > Save.

Save the startup-config file under the Shared Pathname you entered in Step 3d in the "Using Backup Now" section (for example, \\hostname\sharename\path). Name the config file in this format: <backupname>_<hostname>, where backupname comes from the Backup Name in Step 3a in the "Using Backup Now" section, and hostname is the host name of the card. For example, an SSP configuration file could be named Backup1_Switch, and an MRP300 configuration file could be named Backup1_R00ffff900073.

Step 7 Repeat Step 6 for the SSP and for every Flash-based MRP or ASI (MRP300, MRP3-8FXS, MRP3-16FXS) in the chassis.


Restoring System Data to the SPE Running System Manager

This section explains how to restore system software data (SPE310 registry settings, ICS System Manager database records, and Cisco IOS configuration files for ASI and MRP cards) to the SPE310 running System Manager, as follows:

SPE310 Running System Manager Restore Scenarios

Preparing to Restore Data to the SPE310 Running System Manager

Using the Restore Wizard

Starting the Restore Process


Note Backups from previous system software releases cannot be used to restore data to a Cisco ICS 7750 running system software release 2.1.0 and later. Use the restore procedures in this section only for backups that you performed while running system software release 2.1.0 and later.



Note In order to successfully restore system software data, network connectivity is required, unless the data that you backed up is available on another type of media (such as a CD-ROM).


SPE310 Running System Manager Restore Scenarios

This section describes two scenarios in which it is necessary to restore system software data to the SPE310 running System Manager:

Restoring data to an existing (previously configured) SPE310 running System Manager

Restoring data to a new or reimaged (unconfigured) SPE310 running System Manager


Note For SPE310 replacement instructions, refer to Cisco ICS 7750 FRU Installation and Replacement. For SPE310 reimaging instructions, refer to Reimaging Instructions for SPE 310 Cards on the Cisco ICS 7750.



Note You cannot currently restore system COM port settings or the host names of system cards.



Note You can restore data only to an SPE310 in the same chassis—restoring data to an SPE310 in a different chassis is not currently supported.



Note For the purposes of this section, a chassis is considered the same chassis if it contains the SPE310 running System Manager from which the backup data came, if the same cards are installed in the chassis that were installed when you performed the backup, and if the configuration of the cards in that chassis has not changed since you performed the backup.


Preparing to Restore Data to the SPE310 Running System Manager

This section explains how to prepare the system for restoring data to an SPE310 running System Manager. Complete the following steps.


Caution To prevent ESD damage, handle cards by the edges only, and use an ESD-preventive wrist strap or other grounding device.


Step 1 Put on an ESD-preventive wrist strap, and attach it to an unpainted chassis surface.

Step 2 Use a rolled EIA/TIA-232 cable or the supplied console cable (blue) and an RJ-45-to-DB-9 adapter to connect a COM port on the computer to the console port on the SAP.

Step 3 Disengage MRP and ASI cards that do not have Flash memory installed (MRP200, ASI160, ASI81) from the chassis backplane by completing the following steps.


Caution Flash-based MRPs and ASIs (MRP300, MRP3-8FXS, MRP3-16FXS) should not be disengaged during the restore process.

a. Completely loosen the captive screws.

b. Press the upper and lower ejector levers outward at the same time to disengage the MRP or ASI from the backplane.


Caution Always use the ejector levers to disengage or seat cards. Failure to use the levers can cause erroneous system error messages that indicate a card failure. Do not use the ejector levers to lift or support the weight of the card.

c. Grasp the ejector levers, and gently pull the MRP or ASI about one inch out of the chassis.

Step 4 Repeat Step 3 for any additional MRPs and ASIs in the chassis that do not have Flash memory installed (MRP200, ASI160, ASI81).

Depending on the configuration of the SPE310 running System Manager to which you are restoring data, continue as follows:

If you are restoring data to an existing (previously configured) SPE310 running System Manager, go to Step 5.

If you are restoring data to a new or reimaged (unconfigured) SPE310 running System Manager, go to Step 6.

Step 5 If you are restoring data to an existing (previously configured) SPE310 running System Manager, make sure that the Simple Network Management Protocol (SNMP) community strings, IP addresses for other SPE310s, and Windows 2000 administrator (user ID administrator) password are the same as they were when you performed the backup.


Note SNMP community strings and system passwords are case sensitive.


If you need to change any of these settings, complete the following steps:

a. Open a web browser, and access ICSConfig:

http://IP address/icsconfig

b. Log in as an administrator (user ID administrator), and enter your password (the default is changeme).

c. Click OK.

d. Complete ICSConfig, and submit your changes.

e. Go to the "Using the Restore Wizard" section.

Step 6 If you are restoring data to a new or reimaged (unconfigured) SPE310 running System Manager, complete the following steps:

a. If a defective SPE310 is in the chassis, remove the SPE310. Refer to Cisco ICS 7750 FRU Installation and Replacement for instructions.

b. Depending on the scenario, refer to the following documentation:

If you are restoring data to a new (factory-configured) SPE310, before you continue, make sure that you have completed the necessary procedures in the "Replacing the SPE310 Running System Manager" section of Cisco ICS 7750 FRU Installation and Replacement, up to and including installation of the ICS system software.

If you are restoring data to a reimaged SPE310, before continuing, ensure that you have completed the necessary procedures in the Reimaging Instructions for SPE 310 Cards on the Cisco ICS 7750.

c. Open a HyperTerminal session with the SAP (see the "Accessing Processor Cards Through the SAP" section), and enter the following commands, as necessary, to change your system settings to those that were in use when you performed the backup:

Change the administrator password:

net user administrator *

Change the replacement SPE310 IP address and default gateway IP address:

netsh interface ip set address local static <SPE310 IP address> <subnet mask>
<gateway IP address> <number of Hops>

For example:

netsh interface ip set address local static 172.16.48.6 255.255.255.0  
172.16.48.1 1

where 172.16.48.6 is the SPE310 IP address, 255.255.255.0 is the subnet mask, 172.16.48.1 is the default gateway IP address, and 1 is the number of hops.

d. If additional SPE310s are installed and their network settings have been changed since you performed the backup, repeat Step 6c for each additional SPE310, changing its IP address and subnet mask to the values that were in use when you performed the backup.


Go to the "Using the Restore Wizard" section.

Using the Restore Wizard

This section explains how to use the Windows 2000 Restore Wizard to configure your system for the restore process (for system software release 2.1.0 and later only). Complete the following steps:


Step 1 Access the SPE310 Windows interface in either of the following ways:

Use Terminal Services Client to access the SPE310 (see the "Accessing the SPE Windows Interface Through Terminal Services Client" section).

Connect a monitor, keyboard, and mouse to the SPE310 (see the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section).

Step 2 On the SPE310, choose Start > Programs > Accessories > System Tools > Backup.

Step 3 Click Restore Wizard.

The Welcome to the Restore Wizard dialog appears.

Step 4 Click Next.

The What to Restore dialog appears.

Step 5 Click the Import File button.

The Backup File Name dialog appears.


Note Since the data is backed up on an external device, if something similar to Z:\ICS7700_Backup_<timestamp>.bkf or \\Remote device IP address\sharename\ICS7700_Backup_<timestamp>.bkf does not appear in the Catalog backup file field, click Browse, and navigate to the backup folder location on the remote device. Then click OK.


Step 6 Identify database records to be restored as follows: From the tree in the left pane of the What to Restore dialog, click the plus sign (+) as needed to fully expand the tree. Then click the necessary check boxes at each level of the tree. For example: Z:\ICS7700_Backup_<timestamp>.bkf or \\Remote device IP address\share name\ICS7700_Backup_<timestamp>.bkf (remote).

Step 7 Click OK.

Step 8 Click Next.

The Completing the Restore Wizard dialog appears.

Step 9 Click the Advanced button.

The Where to Restore page appears.

Step 10 Click the drop-down arrow to view a list of choices for the Restore Files To field, and choose Original location.

Step 11 Click Next.

The How to Restore page appears.

Step 12 Click the Always replace the file on disk radio button.

Step 13 Click Next.

The Advanced Restore Options page appears.

Step 14 Check the Restore security and the Restore junction points, not the folders and data they reference check boxes.

Step 15 Click Next.

The Completing the Restore Wizard dialog appears again.

Step 16 Click Finish.

Step 17 Click OK.

The Restore Progress dialog box appears. When the system completes this process, the following message will be displayed in the Restore in Process dialog:

Restore is complete.


Note The message Restore is complete indicates that the Restore Wizard has completed. You must still complete the "Starting the Restore Process" procedure to restore system software data.


Step 18 Click Close.

Step 19 Close the Backup window.


Continue with "Starting the Restore Process".

Starting the Restore Process

This section explains how to initiate the restore of system files. Complete the following steps:


Step 1 Access the SPE310 Windows interface in either of the following ways:

Use Terminal Services Client to access the SPE310 (see the "Accessing the SPE Windows Interface Through Terminal Services Client" section).

Connect a monitor, keyboard, and mouse to the SPE310 (see the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section).

Step 2 On the SPE310, click Start > Run.

The Run dialog opens.

Step 3 In the Open field, enter the following command:

cmd

A DOS window opens.

Step 4 Navigate to c:\Program Files\Cisco Systems\ics\backuprestore.

Step 5 Enter the following command:

icsrestore

Press y to confirm that you wish to continue.

The system restores the following files and database records:

Registry settings

ICS System Manager database records

IOS configuration files for cards with no Flash memory installed (MRP200s, ASI81s, and ASI160s)

Output similar to the following will be displayed:

Restore can take up to 10 minutes
Stopping FMMServer
.....
Successfully stopped FMMServer

The backup data is version compatible with the current system.
shutting down Database Engine
Please wait...It might take a few minutes
Starting the Database Engine

  Restoring  ICSSA10

  Restoring  ICSSM10

  Restoring  ICSSWIM10

Restore Successful
Removing c:\ics7700-backup
C:\Program Files\Cisco Systems\ics\backuprestore>

Step 6 You must manually restore the IOS configuration files for Flash-based cards (including the SSP and each Flash-based MRP or ASI card (MRP300, MRP3-8FXS, MRP3-16FXS) in the chassis.

When restore is complete, erase each Flash-based card's configuration as follows:

a. On a PC, open a HyperTerminal session with the SAP (see the "Accessing Processor Cards Through the SAP" section).

b. Press Ctrl-backslash (\), and use the SAP menu to switch to the desired Flash-based card.

c. Enter privileged EXEC Flash mode by entering the following command:

switch> enable

d. Enter your enable password.

e. Erase the startup configuration by entering the following command:

switch# erase startup-config 

f. Restart the card by entering the following command:

switch# reload 

You may see the message:

System configuration has been modified. Save? [yes/no]:

Enter no. The Flash-based card reboots. When it has finished booting, its STATUS LED will turn green, and its ALARM LED should go off.

Step 7 Repeat Step 6 for the SSP and every Flash-based MRP or ASI (MRP300, MRP3-8FXS, MRP3-16FXS) in the chassis, in any order. The card will reboot. For each card, this process will take from 5 to 10 minutes.

Step 8 Restore the startup configurations that were manually backed up for all Flash-based cards, including the SSP and each Flash-based MRP or ASI card (MRP300, MRP3-8FXS, MRP3-16FXS), from the remote device (computer on the network) on which you stored your backup files.


Note If the remote device (computer on the network) on which you stored your backup files cannot access the SAP, you must copy the backup configuration files to the PC that is connected to the SAP console port.


a. Choose Start > Run.

b. Enter the following command to open the backup startup configuration in Notepad:

notepad.exe \\hostname\sharename\path\filename.txt

where \\hostname\sharename\path is the shared path name to the remote device (computer on the network) on which you stored your backup files, and filename is the backup configuration filename for this card as specified in Step 6(d) in the "Using Backup Now" section. For example, an SSP configuration file could be named Backup1_Switch.txt, and an MRP300 configuration file could be named Backup1_R00ffff900073.txt.

c. From Notepad, choose Edit > Select All.

d. Copy the contents of the Notepad window to the clipboard.

e. Apply the backup startup configuration to the Flash-based card. Open a HyperTerminal session with the SAP (see the "Accessing Processor Cards Through the SAP" section).

f. Press Ctrl-backslash (\), and use the SAP menu to switch to the Flash-based card to which you want to restore the startup configuration.

g. Enter privileged EXEC mode by entering the following command:

Switch>enable

h. Enter your enable password.

i. Enter the following command to configure from the terminal:

Switch#configure terminal

j. Paste the backup startup-config into the HyperTerminal session window.

k. Enter the following commands to save the running configuration as the startup configuration:

Switch#copy running-config startup-config 

Step 9 Repeat Step 8 for the SSP and for every Flash-based MRP or ASI (MRP300, MRP3-8FXS, MRP3-16FXS) in the chassis.


Note It is important to restore only those startup configurations that were saved (backed up) at the same time that the System Manager backup procedure was conducted. Attempting to restore a startup configuration manually on a Flash-based card that was saved at a time other than when System Manager was backed up may cause System Manager to be unable to detect and manage that Flash-based card.



Caution When you install cards, be sure to apply equal pressure to the top and bottom of the card. You can damage the card and the chassis backplane if you apply too much pressure to the bottom or the top of the card.

Step 10 Gently slide each MRP and ASI that does not have Flash memory installed (MRP200, ASI160, ASI81) back into the chassis until you feel resistance. Because there are grounding clips near the front and rear of the card guides, you might need to increase the amount of force that you use to move the card past the grounding clips. If you encounter extreme resistance, pull the card out slightly, and push it back in again.

Step 11 Press the upper and lower ejection levers inward at the same time until they lock into their slots. This firmly seats the cards into the chassis.

The MRP and ASI cards that do not have Flash memory installed (MRP200, ASI160, ASI81) will reboot. This process will take from 5 to 10 minutes.

Step 12 Reload the IOS image on the SSP:

a. Open an ICS System Manager session on the SPE310 (see the "Accessing ICS System Manager" section).

b. Click the Software Upgrade tab on the ICS System Manager home page.

c. From the Software Upgrade page, click Deliver to a system card next to the image that you want to install.

d. Click the drop-down arrow to view a list of choices for the Select a Target System Card field, and choose the SSP.

e. Click Deliver. The image is uploaded to the SSP. This process takes from 4 to 6 minutes for a 4-MB file.

For additional information about the status of the restore, refer to the log file, which is stored on the SPE310 at C:\w2ks\icsrestore.log.


Cisco CallManager Backup and Restore Guidelines

This section provides information about backing up and restoring Cisco CallManager that is not available in Backing Up and Restoring Cisco CallManager 3.1 or
Backing Up and Restoring Cisco CallManager 3.2.

When configuring Cisco IP Telephony Applications Backup (the Cisco CallManager backup utility), follow these guidelines:

It is not necessary to back up a Cisco CallManager subscriber.

Because the Cisco CallManager publisher contains the data to be backed up, choose Backup Server when selecting the backup target for the Cisco CallManager publisher data. When Backup Server is selected, the Cisco CallManager publisher is automatically added to the backup target list by Cisco CallManager.

When running Cisco IP Telephony Applications Backup, you must specify a destination (using the Destination tab) to back up and store the publisher data. The destination can be a local drive on a PC, a network drive, or a remote server.

If a remote server is the destination, the remote server must be installed and connected to the network, and you must have administrator access rights to it, before you can add it to the target list.

If a network directory is the backup destination, the directory must be shared, and you must have administrator access rights to it, before you can add it to the target list.

To enable backup of data from another SPE, add that SPE as a Backup Target on the Cisco CallManager Publisher.

If you have multiple Call Manager clusters, you can back up to the same destination by specifying a Backup Server on the first Cisco CallManager publisher blade (for example, an SPE in Slot 6) and adding other Cisco CallManager publishers (for example, SPEs in Slots 4 and 5) as Backup Targets on the first Cisco CallManager publisher.

Installing and Configuring Cisco CallManager Extended Services 2.2(2)

You can install and configure Cisco CallManager Extended Services features on any SPE running Cisco CallManager. This section provides the installation procedure that enables Cisco CallManager Extended Services features on the Cisco ICS 7750 and it adds supplementary information that is necessary to successfully configure Extended Services on the Cisco ICS 7750.


Note To install Cisco CallManager Extended Services 2.2(2) on the Cisco ICS 7750, you must use the Extended Services for ICS 7750 CD-ROM. This CD-ROM has an installer program that is intended for use on the Cisco ICS 7750. Other versions of Cisco CallManager Extended Services will not install properly.


Installing Cisco CallManager Extended Services 2.2(2)

The Extended Services installation procedure includes the following sections:

Connecting the Peripherals

Accessing the CD

Installing the Software

Connecting the Peripherals

You must connect a CD-ROM drive, a monitor, a keyboard, and a mouse to the target SPE in order to install Cisco CallManager Extended Services.

Complete the following steps:


Step 1 Connect the monitor cable to the video port on the target SPE, and power on the monitor.

Step 2 Attach the CD-ROM drive tray to the fan tray underneath the SPE by threading the hooks on the drive tray into the grid on the fan tray. If already present, skip to Step 4.


Note The CD-ROM drive tray is for temporary use when loading software on the SPE. Always remove the CD-ROM drive and drive tray when you finish using them.



Note The CD-ROM drive tray is designed for the weight of the CD-ROM drive only. Never place heavy objects or items other than the CD-ROM drive on the drive tray. Doing so may damage the ventilation grille or impede airflow into the chassis.


Step 3 Connect the CD-ROM drive USB cable to one of the USB ports on the target SPE. Either port can be used.

Step 4 Connect a keyboard and mouse to the target SPE:

If using a PS/2-style keyboard and mouse, connect the "Y" splitter cable for your keyboard and mouse to the keyboard/mouse port on the target SPE, and then connect your keyboard and mouse to the available ends of the "Y" splitter cable.

If using a USB keyboard and mouse, connect the USB keyboard to the available USB port on the target SPE, and then connect the mouse to the pass-through USB port on the keyboard. If you are using a USB hub instead of a keyboard with a pass-through USB port, connect the USB hub to the available USB port on the SPE, and then connect the keyboard and mouse to the USB hub.


Note For a list of USB peripherals that have been tested on the Cisco ICS 7750, refer to the "Connecting a Monitor, Keyboard, and Mouse to the SPE Card" section in the
Cisco ICS 7750 Getting Started Guide.


Step 5 If you are using a PS/2 keyboard and mouse, reboot the target SPE. This forces Windows 2000 to recognize that these peripherals are connected to the target SPE.

Step 6 Continue with "Accessing the CD."


Accessing the CD

Complete the following steps to access the Cisco CallManager Extended Services CD:


Step 1 Use the connected peripherals to access the SPE Windows interface.

Step 2 Enter your Administrator user ID (the default is administrator), and enter your password (the default is changeme).

Step 3 Insert the Cisco CallManager Extended Services for the ICS 7750 Version 2.2 CD-ROM in the CD-ROM drive that is attached to the USB port.

The Cisco Extended Services Installation Wizard opens.


Note If the Cisco Extended Services Installation Wizard does not open, use Windows Explorer to locate the file stiStage.exe on the CD-ROM. Double-click stiStage.exe to launch the installer.


Step 4 Continue with "Installing the Software."


Installing the Software

Complete the following steps to install Cisco CallManager Extended Services 2.2(2) on the Cisco ICS 7750:


Step 1 The Cisco Extended Services Installation Wizard should be running. Click Next in the Welcome to the Cisco CallManager Extended Services Installation Wizard window.

The next Wizard screen appears with a checklist of applications offered by Cisco CallManager Extended Services.

Step 2 Check the box next to the applications you wish to install:

CallManager Cisco AA

Cisco Extension Mobility

Step 3 Click Next.

Step 4 Confirm your installation selection by clicking Yes.

The Cisco CallManager Database Location screen appears.

Step 5 To install Cisco CallManager Extension Mobility on the target SPE, choose This Server.

Step 6 Click Next.

The CiscoWorks2000 Syslog Configuration screen appears. You can use this screen to configure the CiscoWorks2000 Syslog collector.

Step 7 Choose the appropriate option:

If you have a CiscoWorks2000 server on your network, you can click the Configure CiscoWorks2000 Syslog Collector check box to install the CiscoWorks Syslog Collector module on this computer. If you click this check box, enter the location of your CiscoWorks2000 server.

If you do not have a CiscoWorks 2000 server on your network, do not click the Configure CiscoWorks 2000 Syslog Collector check box.

The Ready to Install Cisco CallManager Extended Services window appears.

Step 8 Click Next.

The system takes approximately 10 minutes to install Cisco CallManager Extended Services.

The installation blanks the passwords.

Step 9 Enter the password to be used for the administrator account. By entering a password in this dialog box, you set passwords for all of the following: the Windows 2000 Administrator, the Cisco CallManager Administrator, and the Application Administrator.

Step 10 Click OK.

Step 11 Enter the password to be used for the SQL Server. This is the SQL Server password that was entered when Cisco CallManager was installed on the SPE.

Step 12 Click OK.

Step 13 Click OK when informed that both SA and the SQL passwords have been changed.

Step 14 When prompted, remove the Extended Services CD from the CD-ROM drive, disconnect the CD-ROM drive from the SPE, and click Yes to reboot the SPE.


Configuring Cisco CallManager Extended Services

In the "Configuring Cisco CallManager Extension Mobility" chapter in the Cisco CallManager Extended Services Administrator's Guide, the "Procedures for Configuring Cisco CallManager Extension Mobility" section does not tell how to link DC Directory to the extension mobility feature.

The section "Setting Up the Directory Link" section explains how to link DC Directory to the extension mobility feature. Use the following sequence from the Cisco CallManager Extended Services Administrator's Guide to configure the Extended Mobility features, adding "Setting Up the Directory Link" as shown:

1. Creating a New Application User

2. Configuring the Cisco CRA Engine

a. Setting Up the Directory Link

b. Adding the Login Application

c. Adding the Logout Application

d. Adding the Login Application Trigger

e. Adding the Logout Application Trigger


Note If you are not using Domain Name Service (DNS), you must use the Enterprise Parameters Configuration screen in Cisco CallManager Administration to change the URL Authentication, URL Directories, URL Help, and the URL Information fields. In each of these fields, replace the host name with the IP address of the SPE. (Do not change the Cluster ID field). For example, in the URL Authentication field, change the URL from http://<host name>/CCMUser/authentication to http://<IP address>/CCMUser/authentication. Making these changes allows Cisco IP Phones to access Authentication, Directories, Help Information, and Services. If you are not using DNS and you do not make these changes, users that press the Services button on their Cisco IP Phone (to log on to the Extension Mobility service) will receive the message Host not found.



Note Complete the remaining procedures as listed in the "Procedures for Configuring Cisco CallManager Extension Mobility" section of the "Configuring Cisco CallManager Extension Mobility" chapter in the Cisco CallManager Extended Services Administrator's Guide.


Setting Up the Directory Link

Complete the following steps to link DC Directory to the extension mobility feature:


Step 1 Choose Start > Programs >Cisco Extended Services Administrator > Application Administrator.

The Application Administrator Setup page appears.

Step 2 Click Setup.

The Directory Configuration page appears.

Step 3 Many of the fields are automatically filled in with your configuration data. You must complete the following fields:

a. In the Directory hostname field, enter the IP address of the target SPE—this is where DC Directory resides.

b. In the Directory password field, enter the current DC Directory password.

c. In the Server Type field, choose DC Directory.

d. In the Configuration Profile Name field, enter Default Profile.

Step 4 Click OK to set up the directory configuration.

If the directory configuration is accepted, a command screen appears that launches and runs a script. After the scripts are completed, a confirmation message appears.

Step 5 Click Return to Main Menu.

Step 6 Click Engine.

Step 7 Verify that the Engine status is Running. If it is not running, click Start Engine.

Step 8 Click Main Menu.


Limitations and Restrictions

This section describes known issues with the Cisco ICS 7750 and products that you are likely to use with the Cisco ICS 7750. This section provides information on these topics:

Installing Windows 2000 Upgrades on SPEs

Installing Software on the SPE Running System Manager

Changing the Host Name of the SPE Running System Manager

Best Practices for Using Microsoft SQL Server

Best Practices for Configuring DHCP

Best Practices for Using the IOS CLI

Using Peripherals with SPEs

Removing SPEs

Configuring Cisco ICS 7750 Gateways in Cisco CallManager

Cisco IP Phone Reconfiguration Following SPE Replacement or Change in SPE IP Address

Providing Backup Power

Connecting to the Catalyst 3524-PWR XL 10/100 Inline-Power Ports

Installing Windows 2000 Upgrades on SPEs

The Windows 2000 upgrade win-OS-Upgrade.2000-1-3.exe should not be installed on SPEs. If you install win-OS-Upgrade.2000-1-3.exe on an SPE, the upgrade process will remove a file that is important to the Software Upgrade feature of the ICS System Manager software.

Applying this Windows 2000.1.3 upgrade to an SPE will not cause immediate operational problems on that SPE, but it will render the Software Upgrade feature inoperable. See the "Software Upgrade Problems" section for additional information.

Installing Software on the SPE Running System Manager

Do not install Cisco Unity Voice Mail on the SPE running System Manager, and do not install ICS System Manager on an SPE on which Cisco Unity Voice Mail is installed. The Cisco ICS 7750 does not support the use of both Cisco Unity Voice Mail and ICS System Manager on the same SPE.

Changing the Host Name of the SPE Running System Manager

The computer name (also known as the host name) of an SPE running System Manager can be changed only if no applications have been installed on the SPE since it left the factory. For example, if you install Cisco CallManager on the SPE running System Manager, the only way to change its host name is to reimage it.


Note For reimaging instructions and for information about changing the host name of other SPEs, refer to Reimaging Instructions for SPE 310 Cards on the Cisco ICS 7750.


To change the host name of an SPE running System Manager, follow the practices and procedures in this section.

Guidelines for Host Names

Assigning a New Host Name

Updating Microsoft SQL Server with the New Host Name

Guidelines for Host Names

The following principles govern the usage of host names on SPEs and other devices on the same network as the Cisco ICS 7750:

Access privileges—You must be logged on as an administrator on the SPE in order to change the SPE host name.

Naming conventions:

Use host names that are 15 characters or less. See the "Miscellaneous Problems" section.

Host names should contain only the numbers 0-9, the letters A-Z and a-z, and hyphens (-). You can use other characters, but doing so might prevent other users from finding your device on the network.

Assigning a New Host Name

Complete the following steps to assign a new host name to the SPE running System Manager:


Step 1 Connect a monitor, mouse, keyboard, and CD-ROM drive to the SPE. See the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section.


Note When performing this procedure, access the SPE only through directly connected peripherals. Do not attempt to perform this procedure by accessing the SPE through Terminal Services Client.


Step 2 Log in as an administrator (User ID administrator) and enter your password (the default is changeme).

Step 3 Choose Start > Settings > Control Panel > System.

Step 4 Click the Network Identification tab.

Step 5 Click the Properties button.

Step 6 Enter the new host name in the Computer name field.

Step 7 Click OK.

Step 8 Click Yes when prompted to reboot the SPE.

Step 9 When the SPE has completed its boot sequence, continue with "Updating Microsoft SQL Server with the New Host Name."


Note If an error message appears which suggests that the SQL database has been tampered with, ignore it.



Updating Microsoft SQL Server with the New Host Name

By running the Microsoft SQL Server Setup (using the ICS System Software CD), you can cause Microsoft SQL Server to recognize the new SPE host name. It is not necessary to reinstall Microsoft SQL Server or any of its components.

Complete the following procedures:

Extracting Microsoft SQL Server Files

Running Microsoft SQL Server Setup

Updating the Internal Server Name with Query Analyzer

Updating the Server List in SQL Server Enterprise Manager

Adding the New SQL Server Login in SQL Server Enterprise Manager

Extracting Microsoft SQL Server Files

Complete the following steps:


Step 1 Log in to the SPE as an administrator (User ID administrator) and enter your password (the default is changeme).

Step 2 Insert the ICS System Software CD into the CD-ROM drive that is attached to the SPE USB port.

Step 3 On the SPE, choose Start > Run.

Step 4 In the Open field, enter cmd.

Step 5 Click OK.

A DOS window opens.

Step 6 Change to the temp directory on the SPE:

C:\> cd temp

Step 7 Enter the following command:

C:\temp> d:\microsoft\sqlserver\ms_sql -d

The files will be extracted to C:\temp\ms_sql\Sql70std.

Step 8 Continue with "Running Microsoft SQL Server Setup."


Running Microsoft SQL Server Setup

Complete the following steps:


Step 1 On the SPE, use Windows Explorer to navigate to C:\Temp\ms_sql\Sql70std.

Step 2 Double-click setup.bat.

The Select Install Method window appears.

Step 3 Choose Local Install.

Step 4 Click Next.

Step 5 When prompted to upgrade SQL Server, click Yes.

Step 6 When Setup is complete, click Finish.

Step 7 Choose Start > Programs > Administrative Tools > Services.

The Services window appears.

Step 8 Right-click MSSQLServer and choose Start.

Step 9 Continue with "Updating the Internal Server Name with Query Analyzer."


Updating the Internal Server Name with Query Analyzer

Complete the following steps:


Step 1 Choose Programs > Microsoft SQL Server 7.0 > Query Analyzer.

The SQL Server Query Analyzer window and a smaller window labeled Connect to SQL Server appear.

Step 2 Choose File > Connect.

Step 3 In the SQL Server drop-down list, enter a new host name, or leave the field blank and press <Enter>.

Step 4 (Optional) If you do not know what the old host name of the SQL Server was, run the following query:

select * from sysservers where srvid = 0

Step 5 Choose the Use Windows authentication radio button.

Step 6 Click OK.

Step 7 In the Query Analyzer window, enter the following sequence of commands (note that the quotation mark are required when entering these commands):

sp_dropserver "old_name"
go

sp_addserver "new_name", local
go

Step 8 Press F5.

Step 9 Run the following command to verify that the SQL Server internal name has been changed and that the srvid is 0:


select * from sysservers where srvid = 0

Step 10 Reboot the SPE. If prompted to save the text, click the appropriate choice and continue.

Step 11 When the SPE has completed its boot sequence, continue with "Updating the Server List in SQL Server Enterprise Manager."


Updating the Server List in SQL Server Enterprise Manager

Complete the following steps:


Step 1 Choose Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

The SQL Server Enterprise Manager window appears.

Step 2 In the left pane, click the plus sign (+) next to Microsoft SQL Servers.

Step 3 Right-click <SQL Server name> and choose Properties.

Step 4 Ensure that the NT authentication radio button is selected.

Step 5 Click OK.

Step 6 Click Close.

Step 7 Continue with "Adding the New SQL Server Login in SQL Server Enterprise Manager."


Adding the New SQL Server Login in SQL Server Enterprise Manager

Complete the following steps:


Step 1 Choose Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

The SQL Server Enterprise Manager window appears.

Step 2 In the left pane, click the plus sign (+) as needed to view the security node:

a. Click the + next to Microsoft SQL Servers.

b. Click the + next to SQL Server Group.

c. Click the + next to <Server Name>, where <Server Name> is similar to ICS7700-37ABYTY.

d. Click the + next to Security.

Step 3 Choose Logins.

Step 4 In the right pane, under the Name column, right-click <old host name>\IUSR_ICS7700 and choose Delete.

Step 5 In the left pane, right-click Logins and choose New Login.

The SQL Server Login Properties - New Login dialog appears.

Step 6 Click the down-arrow to view a list of choices for the Domain field, and choose <SPE host name>.

Step 7 In the Name field at the top of the dialog, enter IUSR_ICS7700 after the host name. When this is done, the Name field should read as follows: <new host name>\IUSR_ICS7700.

Step 8 Click the Database Access tab.

Step 9 Under Specify which databases can be accessed by this login, in the Permit column, check the checkbox next to ICSSA10.

Step 10 Under Database roles for <database>, ensure that the checkboxes next to public and db_owner are selected.

Step 11 Repeat Step 9 and Step 10 for ICSSM10, and then for ICSSWIM10.

Step 12 Click OK.

This completes the process of changing the SPE host name and updating the database.


Best Practices for Using Microsoft SQL Server

ICS System Manager and Cisco CallManager require Microsoft SQL Server.


Caution Due to a known issue with Microsoft SQL Server, if you do not install Cisco CallManager on the SPE running System Manager, you could expose your network to distributed denial of service (DDoS) attacks. If you do not intend to install Cisco CallManager on the SPE running System Manager, you can prevent DDoS attacks by completing the workaround that is provided in the "Security Issues" section.


Note Do not attempt to change the host name of an operational SPE, except as directed in the "Changing the Host Name of the SPE Running System Manager" section.



Caution Microsoft SQL Server is installed on the SPE running System Manager at the factory. Do not attempt to use the Microsoft SQL Server installation program to re-install it on the SPE running System Manager, except as directed in the "Updating Microsoft SQL Server with the New Host Name" section. If you are reimaging an SPE running System Manager, the Image Install Tool installs Microsoft SQL Server. For other SPEs on which you intend to install Cisco CallManager, Microsoft SQL Server is installed during the Cisco CallManager installation process.


Note If you intend to upgrade to Cisco CallManager 3.2(1), you must first install a system software patch, as well as Microsoft SQL Server Service Pack 3. Refer to the
Release Notes for Cisco CallManager 3.2(1) on the Cisco ICS 7750.


Best Practices for Configuring DHCP

Cisco Network Registrar (CNR) is installed on the SPE running System Manager to provide Dynamic Host Configuration Protocol (DHCP) and Bootstrap Protocol (BOOTP) services for the Cisco ICS 7750 and other devices on the LAN to which the Cisco ICS 7750 is connected.


Caution CNR is not intended for use as a stand-alone software tool on the Cisco ICS 7750. Do not use the CNR CLI or GUI to invoke CNR commands on the Cisco ICS 7750.


Caution CNR is installed on the SPE running System Manager at the factory. Do not attempt to use the CNR installation program to reinstall CNR on the SPE running System Manager, and do not attempt to install CNR on any other SPEs in the chassis. If you are reimaging an SPE running System Manager, the Image Install Tool installs CNR automatically.

After the Cisco ICS 7750 has been configured (by running ICSConfig), CNR keeps track of devices that send BOOTP or DHCP requests. A configured SPE responds to a DHCP or BOOTP request if the device sending the request has a known MAC address or if the Client Identifier field in the DHCP request is set to a known value.

Installing or Enabling Microsoft DHCP Server on the SPE Running System Manager

By default, the Windows image provided with the SPE 310 does not have the Microsoft DHCP Server enabled. You should not use the Windows Component Wizard to add or enable the Microsoft DHCP Server on the SPE running System Manager. Adding or enabling Microsoft DHCP Server on the SPE running System Manager causes a conflict with CNR.

Installing or Enabling a DHCP Server on Other SPEs or Other Servers

Do not install or enable a DHCP server on any SPE other than the SPE running System Manager. You can install or configure DHCP on an external server, provided that:

The external DHCP server is configured to not respond to DHCP or BOOTP requests from Cisco ICS 7750 cards

If ICS System Manager is providing DHCP services to IP phones or external DHCP clients, the external DHCP server should not be configured to respond to these hosts

The DHCP scopes of the external DHCP server must not conflict with the DHCP or BOOTP scopes in use by ICS System Manager


Note If you are using a DHCP server on an external server, consult your DHCP server documentation for additional DHCP configuration guidelines.


SSP Error Messages

If you are using Cisco IOS 12.0(5)WC2b or 12.0(5)WC5 on the SSP, and if you are monitoring the system through a console connection to the SAP, error messages similar to the following might be generated as the SSP boots:

% error opening tftp://255.255.255.255/cisconet.cfg (Time out) 
% error opening tftp://255.255.255.255/router-confg (Time out)
% error opening tftp://255.255.255.255/ciscortr.cfg (Time out)

This is an expected condition. The system will continue to operate normally without any external intervention.

Best Practices for Using the IOS CLI

ICS System Manager is designed to communicate with and monitor the status of all of the components in the chassis. To enable ICS System Manager to perform these functions, a configuration program (ICSConfig) guides you through the configuration process. ICSConfig enables you to change key system parameters, such as the IP addresses of system cards, passwords, destination for syslog messages, and Simple Network Management Protocol (SNMP) community strings.

To enable ICS System Manager to perform all of its functions as a system management tool, it is important that you use ICSConfig or ICS System Manager, as appropriate, rather than the IOS CLI, when you enter key system parameters.

With the exception of the procedures listed in "ICSConfig Tasks" and any limitations or caveats in the "Open Caveats in Release 2.1.0" section, you can enter all IOS CLI commands that are available for use in any IOS software release that is intended for use on the Cisco ICS 7750.

ICSConfig Tasks

You should always use ICSConfig for the following tasks:

Passwords—Changing the login password, which gives ICS System Manager continued Telnet access to system cards, changing the Windows 2000 administrator password, which grants those with administrator privileges continued access to SPEs, or changing the enable password, which makes it possible for administrators to enter certain IOS commands

Card configurations—Changing the IP addresses or subnet mask of system cards

SNMP settings—Changing read-only and read/write SNMP community strings of the SNMP server, or changing the destination of SNMP traps

Logging—Changing the syslog logging host


Note SNMP community strings and system passwords are case-sensitive.


ICS System Manager Tasks

You should use ICS System Manager to upload and install IOS software images on ASI, MRP, and SSP cards.

Using Peripherals with SPEs

This sections summarizes known issues and best practices regarding the use of keyboards, mice, monitors, and the USB CD-ROM drive with SPEs.

Consider the following issues when using peripherals with SPEs:

USB CD-ROM drive—The TEAC 210PU USB CD-ROM drive is included with the Cisco ICS 7750. The TEAC 210PU USB CD-ROM drive is the only USB CD-ROM drive that has been tested for use with SPEs.

USB keyboards, mice, and hubs:

Because the USB CD-ROM drive is required during reimaging, and because the SPE has only two USB ports, a USB hub might be required if you intend to connect both a USB keyboard and a USB mouse to the SPE, when the keyboard lacks a USB pass-through port.

For a list of USB keyboards, mice, and hubs that have been tested with the Cisco ICS 7750, refer to the "Connecting a Monitor, Keyboard, and Mouse to the SPE Card" section in the
Cisco ICS 7750 Getting Started Guide.


Note USB devices requiring additional software or installation of non-native Windows 2000 drivers will probably not work with the Cisco ICS 7750. We therefore recommend against trying to use them. If you have additional questions or concerns about using USB devices with the Cisco ICS 7750, contact your Cisco support representative.


PS/2 keyboards and mice:

A "Y" splitter cable is provided with the Cisco ICS 7750 to enable you to connect a PS/2 mouse and a PS/2 keyboard to the SPE.

Due to the nature of the Windows 2000 operating system and the functionality of PS/2 ports, if you connect a PS/2 device to an SPE after the SPE boots, the SPE must be rebooted in order for the PS/2 device to be recognized by Windows 2000.

Best Practices for Using Peripherals with SPEs

This section describes best practices regarding the use of peripherals with SPEs.

CD-ROM Drive and CD-ROM Drive Tray

Connecting the CD-ROM drive—Do not connect the CD-ROM drive while the SPE is booting.

Disconnecting the CD-ROM drive:

If the SPE is running, use an attached monitor to locate the Unplug or Eject Hardware icon in the Windows System Tray (in the lower right corner of the screen, typically, unless the taskbar has been moved). The icon looks like a small card with an arrow floating above it. Click the icon, and, in the pop-up menu displayed, select Stop USB Mass Storage Device - Drive (D:).

After Windows 2000 reports that the device has been stopped, you can safely disconnect the USB CD-ROM drive cable from the SPE USB port.


Note If you fail to use the Unplug or Eject Hardware tool and if you plug and unplug the CD-ROM drive many times, the drive may stop responding. If this happens, disconnect the CD-ROM drive, wait 5 minutes, and try reconnecting it again. If the drive still fails to be respond, reboot the SPE; it should be recognized after Windows reboots. If the CD-ROM still fails after these measures, contact your Cisco support representative.


CD-ROM drive tray

A CD-ROM drive tray is provided with the Cisco ICS 7750. The CD-ROM drive tray and the CD-ROM drive are not intended to be connected to the SPE for extended periods of time. Leaving the CD-ROM drive tray in place can interfere with airflow into the chassis. Always remove the CD-ROM drive and drive tray when you finish using them.

The CD-ROM drive tray is designed for the weight of the CD-ROM drive only. Never place heavy objects or items other than the CD-ROM drive on the drive tray. Doing so may damage the ventilation grille or impede airflow into the chassis.

Keyboards and Mice

PS/2 keyboards and mice:

Connect these devices before booting the SPE, if possible. If you connect a PS/2 mouse or keyboard to an operational SPE, you must reboot the SPE in order to use the PS/2 mouse or keyboard.

Disconnect the "Y" connector from the keyboard/mouse port on the SPE when these devices are not being used.

Monitors

Connecting a monitor—Connect the monitor cable to the SPE video port before turning on the monitor.

Disconnecting a monitor—Power down the monitor before disconnecting the monitor cable from the video port on the SPE.

Removing SPEs

Before removing an operational SPE from the chassis, be sure to use ICSConfig or the Windows interface to shut it down (by clicking Start > Shutdown). This step is strongly recommended for the following reason: if Microsoft SQL Server was running on the SPE when it was removed from the chassis, at the next startup of that SPE, Microsoft SQL Server will require a long recovery period, during which certain Cisco ICS 7750 services and applications might have difficulty connecting to their respective databases.


Note For additional complete card removal instructions, refer to Cisco ICS 7750 FRU Installation and Replacement.


Configuring Cisco ICS 7750 Gateways in Cisco CallManager

When configuring gateways in Cisco CallManager, the MRP300, MRP3-8FXS, and the MRP3-16FXS will not be available on the CallManager Gateway page. However, until this problem is corrected in Cisco CallManager, you can still add and configure these gateways in Cisco CallManager by substituting a known gateway for the gateway which is missing, as follows:

When configuring ICS77XX-MRP3xx, choose ICS77XX-MRP2xx

When configuring ICS77XX-MRP3-8FXS, choose ICS77XX-ASI81

When configuring ICS77XX-MRP3-16FXS, choose ICS77XX-ASI160

Cisco IP Phone Reconfiguration Following SPE Replacement or Change in SPE IP Address

If you remove and replace the SPE that is running Cisco CallManager or change its IP address, Cisco IP Phones connected to the Cisco ICS 7750 do not automatically register with the SPE, because the SPE has a different IP address.

Complete the following steps to update connected Cisco IP Phones:


Step 1 Access Cisco CallManager (see the "Accessing Cisco CallManager" section).

Step 2 Choose System > Cisco CallManager Group.

The Cisco CallManager Group Configuration page opens.

Step 3 In the pane on the left side of the window, click Default.

The screen refreshes, displaying the Default Cisco CallManager Group.


Caution Restarting devices causes them to drop calls.

Step 4 Click Reset Devices.


Providing Backup Power

If there is a commercial power failure and if data is being written to the SPE hard disk when power is lost, that data might be unrecoverable. In addition, all calls being processed by the system are dropped, and records associated with those calls are lost.


Caution We strongly recommend that you purchase an uninterruptible power supply (UPS) to provide backup power to the Cisco ICS 7750.

Connecting to the Catalyst 3524-PWR XL 10/100 Inline-Power Ports

For instructions on how to properly configure the Catalyst 3524-PWR XL for inline power, refer to the "Connecting IP Phones" chapter in the Cisco IP Telephony QoS Design Guide.


Caution A Catalyst 3524-PWR XL 10/100 port needs up to 10 seconds to initially detect, power, and link to a Cisco IP Phone. If you disconnect the Cisco IP Phone before the link has been established, you must wait 10 seconds before connecting another network device (other than another Cisco IP Phone) to that switch port. Failure to do so can result in damage to that network device.

Important Notes

This section describes issues related to sending voice traffic over an IP network.

Voice Over IP

Voice over IP (VoIP) enables a Cisco ICS 7750 to carry voice traffic (for example, telephone calls and faxes) over an IP network. VoIP is primarily a software feature; however, to support this feature, a Cisco ICS 7750 must be equipped with an MRP containing at least one VIC or VWIC, or the Cisco ICS 7750 must be connected to a voice-capable router or gateway. The LAN/WAN multiservice routing capabilities available on these cards provides analog and digital (T1/E1) VoIP gateway capabilities for packetized voice traffic.

In VoIP, the DSP segments the voice signal into frames, which are then coupled in groups of two and stored in voice packets. On the Cisco ICS 7750, these voice packets are transported by using IP in compliance with ITU-T specification H.323 and the Skinny Station Protocol. Because voice packets sent over an IP network are sensitive to delay, you need to have a well-engineered network end-to-end to successfully use VoIP.

Using the Cisco ICS 7750 with the PSTN

When connecting switched voice ports on the Cisco ICS 7750 directly to the Public Switched Telephone Network (PSTN), use the configuration described in this section so that you do not expose your network to telephone fraud.

PSTN to MRP Connectivity Using FXO Connections

The Cisco ICS 7750 can connect a user placing a call from the PSTN directly to your telephone network. You can configure the Cisco ICS 7750 as a phone switch that can switch a user to any location in that network, even to remote locations that are connected again to another PSTN. If your Cisco ICS 7750 has Foreign Exchange Office (FXO) ports (on an MRP) that connect the PSTN to analog lines in your telephone network, configure those FXO ports by using a private line auto ringdown (PLAR) connection, as follows:

Step
Command
Purpose

Step 1 

MRP(config)# voice-port 
slot/port

Enter voice-port configuration mode. The voice-port configuration commands are nested so that all subsequent commands affect only the specified voice port.

Step 2 

MRP(config-voiceport)# 
connection {plar | plar-opx} 
string

Configure the voice-port connection mode type (where string is the telephone number) by using the plar option, or if the connection is for a PLAR Off-Premises eXtension (OPX), use the plar-opx option. (Using the plar-opx option causes the FXO interface that you are configuring to not answer until the called side answers.)

IP Provisioning

The Cisco ICS 7750 is not currently designed to support IP provisioning of Cisco IP Phones across more than one subnet. The Cisco ICS 7750 is intended to be deployed in networks where the default gateway (typically an MRP), TFTP server (Cisco CallManager), and Cisco IP Phones are all located on the same subnet, to take advantage of the DHCP services that CNR provides for Cisco IP Phones. See also the "Open Caveats in the Fault Management Module in Release 2.1.0" section.

Open Caveats in Release 2.3.0

This section describes open caveats in system software release 2.3.0, as follows:

Open Caveats in ICS System Manager in Release 2.3.0

Open Caveats in the Fault Management Module in Release 2.3.0


Note For caveats for Cisco IOS on ASIs and MRPs, refer to the Release Notes for the Cisco ICS 7750 for Cisco IOS Release 12.2(4)YH. For caveats for Cisco IOS on the SSP, refer to the
Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC5.


Open Caveats in ICS System Manager in Release 2.3.0

This section describes open caveats in ICS System Manager and related software components for release 2.3.0:

Software Upgrade Problems

Login Problems

Software Upgrade Problems

This section describes a problem related to software upgrade.

If you upgrade an SPE to Cisco CallManager OS version 2001-1-3spA (using the Windows 2000.1.3 upgrade—win-OS-Upgrade.2000-1-3.exe) on an SPE and then attempt to upload an IOS image to the same SPE using the ICS System Manager Software Upgrade feature, the software upload (upgrade) will fail and HTTP error 405 will be displayed. (CSCdx61601)

This error occurs because the installation of win-OS-Upgrade.2000-1-3.exe on the SPE will mistakenly remove Internet Information Services (IIS) Virtual Directory scripts that contain files which are required in order to upload an image to SPE.

This problem will not affect SPE functionality in any other way.

Workaround—Contact the Cisco TAC for instructions on obtaining and installing a software patch that can correct the software upgrade problem.

Login Problems

This section describes a problem with ICS System Manager logins and passwords.

When you enter a User ID or password in the ICS System Manager Security page, characters other than alphanumeric characters (the uppercase and lowercase letters a through z, and the numbers
0 through 9) will be allowed. However, you cannot enter User IDs or passwords containing non-alphanumeric characters when logging in to ICS System Manager. If you attempt to log in to ICS System Manager with a User ID or password which contains a non-alphanumeric character, login will fail. (CSCdx68320)

Workaround—Do not enter any non-alphanumeric characters when creating User IDs or passwords through the Security page in ICS System Manager.

Open Caveats in the Fault Management Module in Release 2.3.0

This section describes open caveats in the Fault Management Module, as follows:

Software Installation Problems

SPE Problems

SAP Problems

CDP Problems

Software Installation Problems

This section describes a problem related to software installation.

After installing Cisco CallManager on an SPE, if the SPE is rebooted, it might not complete its boot sequence successfully. (CSCdv74876)

You might be experiencing this problem if you are attempting to access the SPE through the SAP menu and it fails to give you access (see the "Accessing Processor Cards Through the SAP" section), or if Cisco IP Phones are not working properly (because the CallManager service might not have started on the SPE if it did not finish booting).

Workaround—To solve this problem, complete the following steps:


Step 1 Access the SPE Windows interface. See the "Accessing the SPE Windows Interface Through Terminal Services Client" section.

Step 2 Log in as an administrator (User ID administrator) and enter your password (the default is changeme).

Logging in should allow the MMC, STI1, and STI2 processes to complete. When these software configuration processes are complete, the SPE should be functioning normally.


SPE Problems

This section describes a problem related to SPEs.

After shutting down and rebooting an SPE, it is possible that the SPE might reboot a second time. (CSCdv19549)

This problem, though rare, can occur during initialization of a device driver. The second reboot of the SPE might take slightly longer than normal, because Microsoft SQL Server checks the integrity of its database tables due to the unexpected SPE reboot. The SPE should return to normal operation after the second reboot.

There is no workaround.

SAP Problems

This section describes problems related to the SAP.

If you change the IOS login passwords of MRP, ASIs, or the SSP with ICSConfig, an error message similar to Failed to set alarm card password might be displayed. (CSCdv90365)

Workaround—To solve this problem, complete the following steps:


Step 1 Open a Telnet session with the SPE (see the "Accessing SPEs through Telnet" section).

Step 2 Enter the following commands:

net stop "Cisco Systems Console Server"
net stop FMMServer
net start "Cisco Systems Console Server"
net start FMMServer


If you are using the AC1_0_5 image on the SAP and you install an MRP in an empty chassis slot, the system might report zero degrees as the minimum and maximum operating temperature of the newly installed MRP, causing the SPE ALARM LED to turn on (CSCdv49147).

(The correct minimum and maximum operating temperature of the MRP is -55 and +125 degrees, respectively.)

Workaround—Reseat the SAP.

If you move an SPE to a different chassis slot, if you establish a connection with the SAP, the menu might show the SPE in its original slot (CSCds06164).

Workaround—Reboot the SAP.

Some events related to SAP functionality might not be logged, and LEDs on the SPE might stay on when they should turn off. (CSCdu65741)

There is no workaround.

CDP Problems

This section describes problems related to the Cisco Discovery Protocol (CDP).

In rare situations it is possible that when you run ICSConfig, the SPE running System Manager might not be discovered. Even after trying the suggestions given in the corresponding error code, the problem will persist. Furthermore, if a new SPE or MRP is installed in the same chassis, the new card will not receive an IP address. If this error condition occurs, no log messages will be generated and the status of LEDs on the SPE will not change (CSCdx12810).

Workaround—Reboot the SPE running System Manager.

If ICSConfig assigns the same IP address to an SPE running Cisco Call Manager and another card, it might be because the necessary Cisco Discovery Protocol (CDP) driver is not running on the SPE, causing ICSconfig to generate an error message (error code 400). (CSCdv81891)

The workaround provided with error code 400 is incorrect. Follow these steps to solve this problem:


Step 1 Connect a Monitor, Keyboard and Mouse to the SPE in the slot indicated by error message. See the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section.

Step 2 On the SPE, choose Start > Settings > Control Panel > Administrative Tools > Event Viewer.

The Event Viewer window appears.

Step 3 In the left pane, click System Log.

Step 4 In the right pane, click Type.

This sorts the log messages by type.

Step 5 Scroll until Error log messages are visible in the Type column.

Step 6 Double-click the first Error message that you see that has tcpip in the Source column.

The Event Properties dialog for that error appears.

If the error is a duplicate IP address error, the error description will show something similar to the following:

The system detected an address conflict for IP address <IP Address> with the system having 
network hardware address <MAC Address>. Network operations on this system may be disrupted 
as a result.

The MAC address in the error description is the MAC address of the other device that is using the same IP address as the SPE.

Step 7 Locate the device with that MAC address and either change its IP address, temporarily disconnect that device from the network, or change the SPE IP address.

Step 8 Reboot the SPE.


Open Caveats in Release 2.2.0

This section describes open caveats in system software release 2.2.0, as follows:

Open Caveats in ICS System Manager in Release 2.2.0

Open Caveats in the Fault Management Module in Release 2.2.0


Note For caveats for Cisco IOS on ASIs and MRPs, refer to the Release Notes for the Cisco ICS 7750 for Cisco IOS Release 12.2(4)XL4. For caveats for Cisco IOS on the SSP, refer to the
Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC2b.


Open Caveats in ICS System Manager in Release 2.2.0

This section describes open caveats in ICS System Manager and related software components for release 2.2.0:

If you are using Cisco IOS Release 12.0(5)WC2b1 on the SSP and if you attempt to run the ICS 7750 Image Install Tool on the system in which the SSP is installed, the installation will fail because the SSP cannot obtain an IP address. (CSCdw92546)

Error messages similar to the following will be generated:

SPE 10.0.0.1- Finished Starting FMMGuardian & FMMServer. (00:41:26)
SPE 10.0.0.1- Waiting for SSP getting IP address and password. (20 minutes timeout) 
(00:41:29) 
WARNING - SPE 10.0.0.1: Cannot deliver SSP image. SWIM cannot find SSP. (00:48:04) 

You might also encounter this error condition under the following circumstances:

After erasing the startup-config on the SSP and reloading the SSP.

After pressing Ctrl-C or responding to the configuration dialog prompt before the SSP has obtained a DHCP response.

Workaround—Complete the following steps to solve this problem:


Step 1 Reboot the SSP. Do not close the configuration dialog or respond to the configuration dialog prompt on the SSP until the SSP obtains an IP address via DHCP.

If you encountered this problem while using the ICS 7750 Image Install Tool, complete Step 2 through Step 4.

If you encountered this problem for any other reason, reloading the SSP should solve the problem.

Step 2 Reboot all ASIs and MRPs.

Step 3 If necessary, deliver the SSP IOS image to the SSP. Refer to the "Upgrading ASIs, MRPs, the SSP, or the SAP" section in Upgrading the Cisco ICS 7750 to System Software Release 2.2.0.

Step 4 If necessary, deliver the SAP firmware image to the SAP. Refer to the "Upgrading ASIs, MRPs, the SSP, or the SAP" section in Upgrading the Cisco ICS 7750 to System Software Release 2.2.0.


If an SPE is removed from the chassis without being shut down, at the next startup, Microsoft SQL Server might undergo a recovery period. In some cases, Syslog might not be able to start correctly, and as a result, an error message might be displayed if you attempt to access ICS System Manager. (CSCdw55889)

If you are experiencing this error condition, the following error message might be displayed:
Error Type: Microsoft VBScript runtime (0x800A01A8) Object required: 'Device'. /ics/wcmhome.asp, line 67, and the Event Viewer on the SPE will show that there were events which caused CSyslogd to terminate unexpectedly. To access Event Viewer on the SPE, choose Start > Settings > Control Panel > Administrative Tools > Event Viewer, and click System Log in the left pane of the Event Viewer.

Workaround—Complete the following steps to solve this problem:


Step 1 Access the Windows interface on the SPE running System Manager (see the "Accessing the SPE Windows Interface Through Terminal Services Client" section or the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section).

Step 2 Choose Start > Programs > Administrative Tools > Services.

The Services window opens.

Step 3 In the right pane of the Services window, right-click FMMServer, and choose Restart.


Open Caveats in the Fault Management Module in Release 2.2.0

This section describes open caveats in the Fault Management Module, as follows:

Software Installation Problems

SPE and USB CD-ROM Problems

SAP Problems

CDP Problems

Software Installation Problems

This section describes problems related to software installation.

If you are using the ICS 7750 Image Install Tool to install system software release 2.2.0, there might be a problem with the FMM installation that prevents the system software installation process from completing. (CSCdv63762)

To determine whether you are experiencing this problem, use a text editor to open setupapi.log (which is stored in the w2ks folder on the SPE C: drive), and look for the following error message:

The Driver Signing Class List (C:\w2ks\inf\CertClas.inf) was missing or invalid
 Error 0x800b0003 ...........

Workaround—To solve this problem, complete the following steps:


Step 1 Access the SPE Windows interface. See the "Accessing the SPE Windows Interface Through Terminal Services Client" section or the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section.

Step 2 On the SPE, right-click My Computer and choose Properties.

The System Properties dialog appears.

Step 3 Click the Hardware tab.

Step 4 Click the Driver Signing button.

The Driver Signing Options dialog appears.

Step 5 Choose the Ignore - Install all files, regardless of file signature radio button.

Step 6 Click OK.

Step 7 Use the ICS 7750 Image Install Tool to install system software again.

The system software installs. When system software installation is complete, if you intend to install Cisco CallManager on the same SPE, do so now. When all software installation on the SPE is complete, continue.

Step 8 On the SPE, right-click My Computer and choose Properties.

The System Properties dialog appears.

Step 9 Click the Hardware tab.

Step 10 Click the Driver Signing button.

The Driver Signing Options dialog appears.

Step 11 Choose the Warn - Display a message before installing an unsigned file radio button.

Step 12 Click OK.


After installing Cisco CallManager on an SPE, if the SPE is rebooted, it might not complete its boot sequence successfully. (CSCdv74876)

You might be experiencing this problem if you are attempting to access the SPE through the SAP menu and it fails to give you access (see the "Accessing Processor Cards Through the SAP" section), or if Cisco IP Phones are not working properly (because the CallManager service might not have started on the SPE if it did not finish booting).

Workaround—To solve this problem, complete the following steps:


Step 1 Access the SPE Windows interface. See the "Accessing the SPE Windows Interface Through Terminal Services Client" section.

Step 2 Log in as an administrator (User ID administrator) and enter your password (the default is changeme).

Logging in should allow the MMC, STI1, and STI2 processes to complete. When these software configuration processes are complete, the SPE should be functioning normally.


SPE and USB CD-ROM Problems

This section describes problems related to SPEs and the USB CD-ROM drive.

After shutting down and rebooting an SPE, it is possible that the SPE might reboot a second time. (CSCdv19549)

This problem, though rare, can occur during initialization of a device driver. The second reboot of the SPE might take slightly longer than normal, because Microsoft SQL Server checks the integrity of its database tables due to the unexpected SPE reboot. The SPE should return to normal operation after the second reboot.

There is no workaround.

If the USB CD-ROM drive is connected to the SPE while the SPE is booting, Windows 2000 might not recognize the USB CD-ROM drive and you might not be able to access the USB CD-ROM drive. (CSCdv73111)

Workaround—Disconnect the USB CD-ROM drive from the SPE prior to rebooting, and connect it again after the SPE has completed its boot sequence.


Note We recommend that you connect the USB CD-ROM drive to an SPE only when the CD-ROM drive is needed for reimaging an SPE or installing software on an SPE.


If you disconnect a TEAC 210PU USB CD-ROM drive from a running SPE 310 and then re-attach the CD-ROM to the SPE 310, the CD-ROM might not be recognized by Microsoft Windows (CSCdv45788).

Workaround—Reboot the SPE.

If a USB device is attached to the SPE 310 before it begins its boot sequence, the SPE310 may appear to hang during its boot process (CSCdv59326).

Workaround—If you encounter this problem, disconnecting the USB CD-ROM allows the SPE 310 to complete its boot sequence. To avoid later occurrences, connect the USB CD-ROM to the SPE 310 only after the SPE 310 completes its boot sequence.

If a USB keyboard is attached to the SPE 310 before it begins its boot sequence, due to a known problem with Windows 2000, the following error message is displayed: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. The event log will contain the following error description: Event ID 7026—The following boot-start or system-start driver(s) failed to load : i8042prt. (CSCdv46078)

This error message does not affect system operation.

Workaround—To prevent this error message from appearing, connect the USB keyboard to the SPE 310 after the SPE 310 completes its boot sequence.

SAP Problems

This section describes problems related to the SAP.

If you change the IOS login passwords of MRP, ASIs, or the SSP with ICSConfig, an error message similar to Failed to set alarm card password might be displayed. (CSCdv90365)

Workaround—To solve this problem, complete the following steps:


Step 1 Open a Telnet session with the SPE (see the "Accessing SPEs through Telnet" section).

Step 2 Enter the following commands:

net stop "Cisco Systems Console Server"
net stop FMMServer
net start "Cisco Systems Console Server"
net start FMMServer


If you are using the AC1_0_5 image on the SAP and you install an MRP in an empty chassis slot, the system might report zero degrees as the minimum and maximum operating temperature of the newly installed MRP, causing the SPE ALARM LED to turn on (CSCdv49147).

(The correct minimum and maximum operating temperature of the MRP is -55 and +125 degrees, respectively.)

Workaround—Reseat the SAP.

If you move an SPE to a different chassis slot, if you establish a connection with the SAP, the menu might show the SPE in its original slot (CSCds06164).

Workaround—Reboot the SAP.

Some events related to SAP functionality might not be logged, and LEDs on the SPE might stay on when they should turn off. (CSCdu65741)

There is no workaround.

CDP Problems

This section describes problems related to the Cisco Discovery Protocol (CDP).

In rare situations it is possible that when you run ICSConfig, the SPE running System Manager might not be discovered. Even after trying the suggestions given in the corresponding error code, the problem will persist. Furthermore, if a new SPE or MRP is installed in the same chassis, the new card will not receive an IP address. If this error condition occurs, no log messages will be generated and the status of LEDs on the SPE will not change (CSCdx12810).

Workaround—Reboot the SPE running System Manager.

If ICSConfig assigns the same IP address to an SPE running Cisco Call Manager and another card, it might be because the necessary Cisco Discovery Protocol (CDP) driver is not running on the SPE, causing ICSconfig to generate an error message (error code 400). (CSCdv81891)

The workaround provided with error code 400 is incorrect. Follow these steps to solve this problem:


Step 1 Connect a Monitor, Keyboard and Mouse to the SPE in the slot indicated by error message. See the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section.

Step 2 On the SPE, choose Start > Settings > Control Panel > Administrative Tools > Event Viewer.

The Event Viewer window appears.

Step 3 In the left pane, click System Log.

Step 4 In the right pane, click Type.

This sorts the log messages by type.

Step 5 Scroll until Error log messages are visible in the Type column.

Step 6 Double-click the first Error message that you see that has tcpip in the Source column.

The Event Properties dialog for that error appears.

If the error is a duplicate IP address error, the error description will show something similar to the following:

The system detected an address conflict for IP address <IP Address> with the system having 
network hardware address <MAC Address>. Network operations on this system may be disrupted 
as a result.

The MAC address in the error description is the MAC address of the other device that is using the same IP address as the SPE.

Step 7 Locate the device with that MAC address and either change its IP address, temporarily disconnect that device from the network, or change the SPE IP address.

Step 8 Reboot the SPE.


Open Caveats in Release 2.1.0

This section describes open caveats in system software release 2.1.0 and Cisco CallManager, as follows:

Open Caveats in ICS System Manager in Release 2.1.0

Open Caveats in the Fault Management Module in Release 2.1.0

Open Caveats Related to IP Telephony in Release 2.1.0


Note For caveats for Cisco IOS, refer to the Release Notes for the Cisco ICS 7750 for Cisco IOS Release 12.2(4)XL1. For caveats in Cisco CallManager that are not specific to the Cisco ICS 7750, refer to the Release Notes for Cisco CallManager Release 3.1(3a). For caveats in Cisco Unity Voice Mail 3.0(1) for the Cisco ICS 7750, refer to the Release Notes for Cisco Unity Voice Mail Release 3.0(1) for the Cisco ICS 7750.


Open Caveats in ICS System Manager in Release 2.1.0

This section describes open caveats in ICS System Manager and related software components, as follows:

DHCP/BOOTP Problems

MRP Problems

SSP Problems

Restore Problems

Security Issues

Cisco IP Phone Reconfiguration Problems

Miscellaneous Problems

DHCP/BOOTP Problems

This section describes problems related to DHCP and BOOTP.

If the ICS 7750 Image Install Tool is used to install ICS Core Software on an SPE in the chassis, if the chassis is already on the 10.0.0.0/24 subnet, and if another SPE is inserted in the chassis, the error messages EC 401 - SNMP community string mismatch or EC 402 - Administrator password mismatch might be displayed, indicating that the SPE that was just inserted will not be remotely accessible (from a different subnet) and that certain information about the new SPE will not display correctly in ICS System Manager. (CSCdv89085)

If the ICS 7750 Image Install Tool is used to install ICS Core Software on an SPE in the chassis, and if the chassis is already on the 10.0.0.0/24 subnet, the error messages 401 - SNMP Community string mismatch and/or 402 - Administrator password mismatch might be displayed in ICSConfig for the newly installed SPE. This SPE might not be accessible from a different subnet, since the default gateway on the new SPE is not set, and certain information about the new SPE will not display correctly in ICS System Manager.

Workaround—Complete the following steps to solve this problem:


Step 1 Access ICSConfig. See the "Accessing ICSConfig" section.

Step 2 Set the SNMP community string and administrator password to the correct values as directed by ICSConfig.

Step 3 Reboot the new SPE.


If a DHCP-enabled SPE is inserted in the chassis, if the time on the SPE is set so that it is seven days or more earlier than the time on the SPE running System Manager, the DHCP lease for the SPE will expire, causing it to not function properly. (CSCdv90392)

Workaround—Reboot the newly inserted SPE.

After you enter the icsrestore command, if the state of DHCP leases for all external DHCP clients (such as PCs and Cisco IP Phones) on the same network has changed since the backup was performed, the information in the CNR database might not be current, and this might result in IP address conflicts among DHCP clients. (CSCdv69578)

If duplicate IP addresses are assigned through DHCP to Cisco IP Phones, the Cisco IP Phones will reboot and will acquire new leases. No additional user intervention should be required for Cisco IP Phones.

If duplicate IP addresses are assigned through DHCP to PC clients, you might need to release and renew the leases on the conflicting PCs.

Workaround—To solve this problem, complete the following steps:


Step 1 On the PC, choose Start > Run.

The Run dialog opens.

Step 2 In the Open field, enter cmd.

Step 3 Click OK.

A DOS window opens.

Step 4 Enter the following commands:

C:\> ipconfig /release
C:\> ipconfig /renew

Step 5 Enter the following command to close the DOS window:

C:\> exit


In rare instances it is possible that CNR might not properly initialize on the SPE running System Manager, preventing the SPE from processing DHCP and BOOTP requests from cards, Cisco IP Phones, and other devices on the network. (CSCdv66769)

One indication that you might be experiencing this problem is that cards do not receive IP addresses as they should following ICSConfig. To verify that this bug is causing the problem, use a text editor to open the CNR log file (name_dhcp_1_log), which can be found on the SPE at
C:\Program Files\Network Registrar\logs. If a cyclical pattern similar to the following is present at the end of the log file, then your system might be experiencing this bug:

11/19/2001 10:00:46 name/dhcp/1 Info System 0 00101 Network Registrar
3.5(3) nightly build #210007
11/19/2001 10:00:46 name/dhcp/1 Info System 0 00102 name/dhcp (DHCP Server
Release Build) startup
11/19/2001 10:00:46 name/dhcp/1 Info System 0 00103 version 1; built
04/03/00@19:34 by aicbuild@build3
11/19/2001 10:03:55 name/dhcp/1 Info System 0 00101 Network Registrar
3.5(3) nightly build #210007
11/19/2001 10:03:55 name/dhcp/1 Info System 0 00102 name/dhcp (DHCP Server
Release Build) startup
11/19/2001 10:03:55 name/dhcp/1 Info System 0 00103 version 1; built
04/03/00@19:34 by aicbuild@build3

Workaround—Reboot the SPE running System Manager.

MRP Problems

This section describes situations where MRPs do not work as expected.

The default setting of the configuration register of the MRP is set to 0x1. With this setting, if the break command is issued from the console while the MRP is running, the MRP returns to a ROMMON mode. At this point, the cont command must be entered to restore the MRP to a running state or it must be rebooted. (CSCdu54310)

Workaround—Access the MRP (see the "Accessing the IOS CLI on ASIs, MRPs and the SSP Through Telnet" section), and enter the following IOS commands to change the configuration register to 0x101:

MRP1# configure terminal
MRP1(config)# config-register 0x101
MRP1(config)# end
MRP1# reload

You do not need to save this configuration.

SSP Problems

This section describes situations where the SSP does not operate properly.

If you hotswap the SSP (pull the card out and replace it again) or replace the SSP with a different SSP, you might notice the following problems with the SSP (CSCdv08956):

It might fail to log the SPE running System Manager as its logging host.

It might fail to log the SPE running System Manager as an SNMP trap target.

Its console password, VTY password, read-write Community String, and Trap Community String might not be set.

Workaround—To solve this problem, complete the following steps:


Step 1 Open a HyperTerminal session with the SAP (see the "Accessing Processor Cards Through the SAP" section).

Step 2 Press Ctrl-backslash (\) and use the SAP menu to switch to the SPE running System Manager.

Step 3 Enter the following command:

net stop FMMServer

Step 4 Press Ctrl-backslash (\) and use the SAP menu to switch to the SSP.

Step 5 Enter privileged EXEC mode by entering the following command:

switch> enable

Step 6 Enter your enable password.

Step 7 Erase the SSP startup configuration by entering the following command:

switch# erase start

Step 8 Restart the SSP by entering the following command:

switch# reload

The SSP reboots.

Step 9 Press Ctrl-backslash (\) and use the SAP menu to switch to the SPE running System Manager.

Step 10 Enter the following command:

net start FMMServer


Restore Problems

This section describes caveats related to database restore.


If you restore ICS System Manager data, the host names of system cards might not be restored. (CSCdv05715)

There is no workaround.

If you restore ICS System Manager data, the correct IOS image might not be loaded on the SSP (CSCdu88638).

Workaround—To solve this problem, complete the following steps:


Step 1 Open an ICS System Manager session on the SPE (see the "Accessing ICS System Manager" section).

Step 2 Click the Software Upgrade tab on the ICS System Manager home page.

Step 3 If the IOS software image that you want to install does not appear in the Software Library table, continue. Otherwise go to Step 8.

Step 4 Click Add Image on the right side of the Software Library table.

Step 5 From the Image Management/Upload a Software Image to ICS 7750 page, click Browse, and navigate to the folder on the PC where the image that you want to add is located.


Note SSP software images names begin with C2900XL.


Step 6 Click Upload to ICS 7750 to add the image to the Software Library table.

Step 7 From the Software Upgrade page, click Deliver to a system card next to the image that you want to install.

Step 8 Click the drop-down arrow to view a list of choices for the Select a Target System Card field, and choose the SSP card.

Step 9 Click Deliver. The image is uploaded to the SSP. This process takes from 4 to 6 minutes for a 4-MB file.


Because system COM port settings are not stored in the ICS System Manager database, if you restore ICS System Manager data, the COM port settings will be lost (CSCdu86227).

Workaround—to solve this problem, complete the following steps:


Step 1 Open an ICS System Manager session on the SPE (see the "Accessing ICS System Manager" section).

Step 2 Click the Configure tab on the ICS System Manager home page.

Step 3 Click COM Port Manager.

Step 4 Click to the down arrow to view a list of choices for the Assign field and select the target SPE.

Step 5 Click Assign.

A configuration confirmation page appears.

Step 6 Make any necessary changes to the COM port assignment and click Continue.


If you attempt to restore the database from one Cisco ICS 7750 chassis to a different Cisco ICS 7750 chassis, ICSconfig might fail to discover the cards in the chassis, and an an error message will be displayed. (CSCdu57064)

There is no workaround—Restoring data from one Cisco ICS 7750 chassis to a different Cisco ICS 7750 chassis is not supported.

Security Issues

This section describes an issue related to system security.

Due to a known issue with Microsoft SQL Server, if you do not install Cisco CallManager on the SPE running System Manager, you could expose your network to distributed denial of service (DDoS) attacks. (CSCdw04850)

This condition can exist only if the SQL Server Administration (sa) password is left blank when installing Microsoft SQL Server, which is the factory configuration of the SPE running System Manager—if you install Cisco CallManager, you are prompted to enter the sa password.

Workaround—If you do not intend to install Cisco CallManager on the SPE running System Manager, you can prevent DDoS attacks by completing the following steps:


Step 1 Access the Windows interface on the SPE running System Manager (see the "Accessing the SPE Windows Interface Through Terminal Services Client" section or the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section).

Step 2 Choose Start > Programs > Microsoft SQL Server 7.0 > Enterprise Manager.

The SQL Server Enterprise Manager window appears.

Step 3 In the left pane, click the plus sign (+) as needed to view the security node:

a. Click the + next to Microsoft SQL Servers.

b. Click the + next to SQL Server Group.

c. Click the + next to <Server Name>, where <Server Name> is similar to ICS7700-37ABYTY.

d. Click the + next to Security.

Step 4 Choose Logins.

Step 5 In the right pane, under the Name column, double-click sa.

Step 6 Enter a new password for the sa user in the Password field.

Step 7 Click OK.


Note Remember the new sa password. This password is required during Cisco CallManager installation.



Note Do not change the sa password of the CallManager publisher after Cisco CallManager installation. If you change the sa password of the publisher, subscribers will not be able to communicate properly with the publisher. If you do not know the old sa password, you must change the login password for each subscriber so that it matches the new publisher sa password. You can change the login password of a subscriber by choosing the appropriate CCM03xx database in Enterprise Manager, right-clicking, and choosing Properties. Under Security Settings, you will find the login settings for connecting to the publisher. Ensure that you change the passwords so that both the publisher login and the distributor login match the publisher sa password.



Note You can change the sa password on a subscriber after Cisco CallManager installation without affecting Cisco CallManager functionality.


Cisco IP Phone Reconfiguration Problems

This section describes situations where Cisco IP Phones might not be able to successfully connect to the Cisco ICS 7750.

If you replace the SPE or change the IP address of the SPE with ICSconfig, Cisco IP Phones that are connected to the Cisco ICS 7750 are not automatically updated with the new IP address of the SPE. If the Cisco IP Phones cannot make contact with the SPE that is running Cisco CallManager, they must be configured with the new SPE IP address, because the SPE acts as the TFTP server for the Cisco IP Phones. (CSCds47597)

Workaround—See the procedure "Cisco IP Phone Reconfiguration Following SPE Replacement or Change in SPE IP Address" section.

Miscellaneous Problems

This section describes caveats that might occur when attempting to view any ICS System Manager page or when installing software.

For SPEs on which Microsoft SQL Server is being installed, if you use a host name that is longer than 15 characters, the software installation might fail. (CSCdv71860)

There is no workaround.


Note For SPEs other than the SPE running System Manager on which Microsoft SQL is being installed, the host name can be changed only prior to installation of the SQL software. If you change the host name of an SPE other than the SPE running System Manager after installing Microsoft SQL Server, you must reimage the SPE. See the "Changing the Host Name of the SPE Running System Manager" section.


When attempting to access ICSConfig or ICS System Manager, you might encounter a situation where an error message is displayed indicating that the system is unable to display the page. (CSCdu87304)

Workaround—To solve this problem, complete the following steps:


Step 1 Access the SPE. See the "Accessing SPEs through Telnet" section.

Step 2 Log in as an administrator (user ID administrator), and enter your password (the default is changeme).

Step 3 Navigate to C:\Program Files\Cisco Systems\ics\program.

Step 4 Enter the following command:

UnloadICS.bat


Open Caveats in the Fault Management Module in Release 2.1.0

This section describes open caveats in the Fault Management Module, as follows:

Software Installation Problems

SPE and USB CD-ROM Problems

SAP Problems

CDP Problems

Software Installation Problems

This section describes problems related to software installation.

If you are using the ICS 7750 Image Install Tool to install system software release 2.1.0, there might be a problem with the FMM installation that prevents the system software installation process from completing. (CSCdv63762)

To determine whether you are experiencing this problem, use a text editor to open setupapi.log (which is stored in the w2ks folder on the SPE C: drive), and look for the following error message:

The Driver Signing Class List (C:\w2ks\inf\CertClas.inf) was missing or invalid
 Error 0x800b0003 ...........

Workaround—To solve this problem, complete the following steps:


Step 1 Access the SPE Windows interface. See the "Accessing the SPE Windows Interface Through Terminal Services Client" section or the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section.

Step 2 On the SPE, right-click My Computer and choose Properties.

The System Properties dialog appears.

Step 3 Click the Hardware tab.

Step 4 Click the Driver Signing button.

The Driver Signing Options dialog appears.

Step 5 Choose the Ignore - Install all files, regardless of file signature radio button.

Step 6 Click OK.

Step 7 Use the ICS 7750 Image Install Tool to install system software again.

The system software installs. When system software installation is complete, if you intend to install Cisco CallManager on the same SPE, do so now. When all software installation on the SPE is complete, continue.

Step 8 On the SPE, right-click My Computer and choose Properties.

The System Properties dialog appears.

Step 9 Click the Hardware tab.

Step 10 Click the Driver Signing button.

The Driver Signing Options dialog appears.

Step 11 Choose the Warn - Display a message before installing an unsigned file radio button.

Step 12 Click OK.


After installing Cisco CallManager on an SPE, if the SPE is rebooted, it might not complete its boot sequence successfully. (CSCdv74876)

You might be experiencing this problem if you are attempting to access the SPE through the SAP menu and it fails (see the "Accessing Processor Cards Through the SAP" section), or if Cisco IP Phones are not working properly (because the CallManager service might not have started on the SPE if it did not finish booting).

Workaround—To solve this problem, complete the following steps:


Step 1 Access the SPE Windows interface. See the "Accessing the SPE Windows Interface Through Terminal Services Client" section.

Step 2 Log in as an administrator (User ID administrator) and enter your password (the default is changeme).

Logging in should allow the MMC, STI1, and STI2 processes to complete. When these software configuration processes are complete, the SPE should be functioning normally.


SPE and USB CD-ROM Problems

This section describes problems related to SPEs and the USB CD-ROM drive.

After shutting down and rebooting an SPE, it is possible that the SPE might reboot a second time. (CSCdv19549)

This problem, though rare, can occur during initialization of a device driver. The second reboot of the SPE might take slightly longer than normal, because Microsoft SQL Server checks the integrity of its database tables due to the unexpected SPE reboot. The SPE should return to normal operation after the second reboot.

There is no workaround.

If the USB CD-ROM drive is connected to the SPE while the SPE is booting, Windows 2000 might not recognize the USB CD-ROM drive and you might not be able to access the USB CD-ROM drive. (CSCdv73111)

Workaround—Disconnect the USB CD-ROM drive from the SPE prior to rebooting, and connect it again after the SPE has completed its boot sequence.


Note We recommend that you connect the USB CD-ROM drive to an SPE only when the CD-ROM drive is needed for reimaging an SPE or installing software on an SPE.


If you disconnect a TEAC 210PU USB CD-ROM drive from a running SPE 310 and then re-attach the CD-ROM to the SPE 310, the CD-ROM might not be recognized by Microsoft Windows (CSCdv45788).

Workaround—Reboot the SPE.

If a USB device is attached to the SPE 310 before it begins its boot sequence, the SPE310 may appear to hang during its boot process (CSCdv59326).

Workaround—If you encounter this problem, disconnecting the USB CD-ROM allows the SPE 310 to complete its boot sequence. To avoid later occurrences, connect the USB CD-ROM to the SPE 310 only after the SPE 310 completes its boot sequence.

If a USB keyboard is attached to the SPE 310 before it begins its boot sequence, due to a known problem with Windows 2000, the following error message is displayed: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. The event log will contain the following error description: Event ID 7026—The following boot-start or system-start driver(s) failed to load : i8042prt. (CSCdv46078)

This error message does not affect system operation.

Workaround—To prevent this error message from appearing, connect the USB keyboard to the SPE 310 after the SPE 310 completes its boot sequence.

SAP Problems

This section describes problems related to the SAP.

If you change the IOS login passwords of MRP, ASIs, or the SSP with ICSConfig, an error message similar to Failed to set alarm card password might be displayed. (CSCdv90365)

Workaround—To solve this problem, complete the following steps:


Step 1 Open a Telnet session with the SPE (see the "Accessing SPEs through Telnet" section).

Step 2 Enter the following commands:

net stop "Cisco Systems Console Server"
net stop FMMServer
net start "Cisco Systems Console Server"
net start FMMServer


If you are using the AC1_0_5 image on the SAP and you install an MRP in an empty chassis slot, the system might report zero degrees as the minimum and maximum operating temperature of the newly installed MRP, causing the SPE ALARM LED to turn on (CSCdv49147).

(The correct minimum and maximum operating temperature of the MRP is -55 and +125 degrees, respectively.)

Workaround—Reseat the SAP.

If you move an SPE to a different chassis slot, if you establish a connection with the SAP, the menu might show the SPE in its original slot (CSCds06164).

Workaround—Reboot the SAP.

Some events related to SAP functionality might not be logged, and LEDs on the SPE might stay on when they should turn off. (CSCdu65741)

There is no workaround.

CDP Problems

This section describes a problem with a Cisco Discovery Protocol (CDP) driver.

If ICSConfig assigns the same IP address to an SPE running Cisco Call Manager and another card, it might be because the necessary Cisco Discovery Protocol (CDP) driver is not running on the SPE, causing ICSconfig to generate an error message (error code 400). (CSCdv81891)

The workaround provided with error code 400 is incorrect. Follow these steps to solve this problem:


Step 1 Connect a Monitor, Keyboard and Mouse to the SPE in the slot indicated by error message. See the "Accessing the SPE Windows Interface Through Directly Connected Peripherals" section.

Step 2 On the SPE, choose Start > Settings > Control Panel > Administrative Tools > Event Viewer.

The Event Viewer window appears.

Step 3 In the left pane, click System Log.

Step 4 In the right pane, click Type.

This sorts the log messages by type.

Step 5 Scroll until Error log messages are visible in the Type column.

Step 6 Double-click the first Error message that you see that has tcpip in the Source column.

The Event Properties dialog for that error appears.

If the error is a duplicate IP address error, the error description will show something similar to the following:

The system detected an address conflict for IP address <IP Address> with the system having 
network hardware address <MAC Address>. Network operations on this system may be disrupted 
as a result.

The MAC address in the error description is the MAC address of the other device that is using the same IP address as the SPE.

Step 7 Locate the device with that MAC address and either change its IP address, temporarily disconnect that device from the network, or change the SPE IP address.

Step 8 Reboot the SPE.


Open Caveats Related to IP Telephony in Release 2.1.0

This section describes caveats related to Cisco CallManager 3.1(2c) and Cisco IP Phones that have been observed on the Cisco ICS 7750 platform in release 2.1.0:

If you change the IP address of an SPE that is servicing Cisco IP Phones, Cisco IP Phones might not be able to register with the SPE until you stop and restart Cisco CallManager (CSCdu76741).

Workaround—To solve this problem, complete the following steps:


Step 1 Access Cisco CallManager (see the "Accessing Cisco CallManager" section).

Step 2 Choose Application > Cisco CallManager Serviceability from the Cisco CallManager Administration window.

The Cisco CallManager Serviceability window displays.

Step 3 Choose Tools > Control Center.

The Control Center window displays the list of servers in the Cisco CallManager cluster.

Step 4 Choose the SPE from the Servers column.

The window displays the services for the SPE you chose, the status of the services, and a service control panel to stop or start a service.


Caution Stopping a Cisco CallManager service also stops call processing for all devices controlled by that service. When a Cisco CallManager service is stopped, calls from an IP phone to another IP phone will stay up; calls in progress from an IP phone to a Media Gateway Control Protocol (MGCP) gateway will also stay up, and other types of calls will be dropped.

Step 5 Click the Stop button for the Cisco CallManager service.

The Service Status symbol changes from an arrow to a square.

Step 6 Click the Start button for the Cisco CallManager service.

The Service Status symbol changes from a square to an arrow.


When placing a call between two Cisco IP Phones, the name of the called party might not appear on the Cisco IP Phone display until the called party picks up the handset. (CSCdu88152)

There is no workaround.

If you are exiting an Octel voice mail system that is connected to a Cisco ICS 7750 that is running Cisco CallManager, and you are placing the call through an outside line, you might not be able to transfer from the voice mail system to the internal phone system. (CSCdu88171)

There is no workaround.

If an external (PSTN) call is made to a Cisco IP Phone, and if the system is configured so that the call is forwarded through an MRP to a PBX voice mail system, the call forwarding might not work (voice mail access might be unsuccessful). (CSCdt39008)

Workaround—Configure the system so that call forwarding is not done through the MRP.

If you are configuring directory numbers from the Cisco CallManager Configuration page
(System > Cisco CallManager), if you attempt to uncheck the Auto-registration Disabled on this Cisco CallManager checkbox before clicking the Update button, any changes that you made to this page might be disregarded. (CSCdt61816)

Workaround—Click the Update button before attempting to uncheck the Auto-registration Disabled on this Cisco CallManager checkbox.

When you select an Active Gateway from the ICS System Manager Monitor page, no data is displayed. (CSCdt09903)

There is no workaround.

When logged in to the ICS System Manager and accessing the Cisco CallManager for the first time, you might get a garbled home page. (CSCds08033)

Workaround—Click Reload on the browser toolbar to refresh the page, and then it will display correctly.

Documentation Updates

This section describes Cisco ICS 7750 feature support that is not addressed and functionality that might not work exactly as described in the Cisco ICS 7750 documentation.

Cisco ICS 7750 Administration and Troubleshooting Guide

The system supports a maximum of five SPEs—not six SPEs as listed in this Guide.

For the latest information on how to access they system, see the "System Management" section. For the latest information about DHCP usage, see the "Best Practices for Configuring DHCP" section. For the latest information about system software backup, see the "Backing Up System Software Data" section.

Cisco ICS 7750 Hardware Installation Guide

The VIC-2FXO-M1, VIC-4FXO-M!, and VIC-4FXS/DID are not listed, but these cards are supported. See the "Hardware Summary" section for the latest information on hardware support. The list of what is included in the Cisco ICS 7750 hardware accessory kit might differ from what you actually receive with your Cisco ICS 7750. For example, a CD-ROM drive and Y-cable is shipped with the Cisco ICS 7750, beginning with system software release 2.1.0.

The SPE 200 is not supported for system software release 2.1.0 and later.

Related Documentation

The following sections describe the documentation available for the Cisco ICS 7750. These documents consist of hardware and software installation guides, Cisco IOS configuration and command references, system error messages, feature modules, and other documents.

Cisco ICS 7750 Documents

The documents described in this section are available on CCO and on CD:

On Cisco.com, beginning under the Service & Support heading:

Technical Documents: Voice/Telephony: Cisco ICS 7750

On the Documentation CD-ROM (order number DOC-CONDOCCD=) at:

Cisco Product Documentation: Voice/Telephony: Cisco ICS 7750

Release 2.3.0 Documents

The following documents were updated or created for system software release 2.3.0, and can be found in this location:

http://www.cisco.com/univercd/cc/td/doc/product/voice/ics/ics23/index.htm

Cisco ICS 7750 Documentation Locator for Release 2.3.0

Cisco ICS 7750 Getting Started Guide

Upgrading the Cisco ICS 7750 to System Software Release 2.3.0

Cisco ICS 7750 System Description

Using Media Gateway Control Protocol with the Cisco ICS 7750

Release Notes for Cisco IOS 12.2(4)YH on the Cisco ICS 7750

Cisco ICS 7750 FRU Installation and Replacement

Reimaging Instructions for SPE310 Cards on the Cisco ICS 7750

Installing Memory, PVDM, and VPN Modules in ASI Cards, MRP Cards, and SPE Cards in the Cisco ICS 7750

Release 2.2.0 Documents

The following documents were updated or created for system software release 2.2.0, and can be found in this location:

http://www.cisco.com/univercd/cc/td/doc/product/voice/ics/ics22/index.htm

Cisco ICS 7750 Documentation Locator for Release 2.2.0

Cisco ICS 7750 FRU Installation and Replacement

Cisco Interface Cards Installation Guide

Release Notes for Cisco IOS 12.2(4)XL4 on the Cisco ICS 7750

Upgrading the Cisco ICS 7750 to System Software Release 2.2.0

Release 2.1.0 Documents

The following documents are available for system software release 2.1.0, and can be found in this location:

http://www.cisco.com/univercd/cc/td/doc/product/voice/ics7750/index.htm

Cisco ICS 7750 Getting Started Guide

Cisco ICS 7750 Documentation Locator

Cisco ICS 7750 System Description

Cisco ICS 7750 Hardware Installation Guide

Cisco ICS 7750 Administration and Troubleshooting Guide

Cisco ICS 7750 Software Configuration Guide

Installation and Replacement Notes:

Cisco ICS 7750 FRU Installation and Replacement

Installing Memory, PVDM, and VPN Modules in ASI Cards, MRP Cards, and SPE Cards in the Cisco ICS 7750

Reimaging instructions:

Reimaging Instructions for SPE 310 Cards on the Cisco ICS 7750

Release Notes:

Release Notes for the Cisco ICS 7750 for System Software Release 2.x.x (this document)

Release Notes for the Cisco ICS 7750 for Cisco IOS Release 12.2(4)XL1

Regulatory Compliance and Safety Information for the Cisco ICS 7750

Documentation Set

Printed versions of the manuals that are not shipped with the product can be ordered as a boxed set (customer order number DOCS-7750=).

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

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

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.