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
|
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
|
|
|
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:
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:
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:
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:
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:
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
|
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.
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:
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:
–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
•
