Guest

Cisco ICS 7700 Series Integrated Communication Systems

Upgrading to System Software Release 2.6.0 and Cisco CallManager Release 3.3(2) on the Cisco ICS 7750

  • Viewing Options

  • PDF (654.6 KB)
  • Feedback
Upgrading to System Software Release 2.6.0 and Cisco CallManager Release 3.3.(2) on the Cisco ICS 7750

Table Of Contents

Upgrading to System Software Release 2.6.0 and Cisco CallManager Release 3.3.(2) on the Cisco ICS 7750

Contents

System Software Release 2.6.0 Installation Scenarios

Upgrading an SPE Running System Manager without Cisco CallManager

Upgrading an SPE Running System Manager with a Cisco CallManager Publisher

Upgrading an SPE Running System Manager with a Cisco CallManager Subscriber

Upgrading an SPE Running Core Software without Cisco CallManager

Upgrading an SPE Running Core Software with a Cisco CallManager Publisher

Upgrading an SPE Running Core Software with a Cisco CallManager Subscriber

Accessing the Cisco ICS 7750

Accessing the SPE310 Windows Interface Through Directly Connected Peripherals

Accessing the SPE310 Windows Interface Through Terminal Services Client

Accessing ICS System Manager

Accessing Processor Cards Through the SAP

Installing the CD-ROM Drive

Attaching the CD-ROM Drive Tray

Connecting the CD-ROM Drive

Preparing to Upgrade to System Software Release 2.6.0

Disabling Third-Party Cisco-Verified Applications

Removing the Existing Cisco IP Telephony Applications Server Backup Utility

Installing the Upgraded Cisco IP Telephony Applications Server Backup

Backing Up Cisco CallManager Data

Backing Up System Manager Data

Reimaging an SPE310

Preparing for SPE310 Reimaging

SPE310 Cards and Software

Reimaging Windows 2000 Server on the SPE310 Hard Disk

Installing System Software Release 2.6.0

Restoring System Data to the SPE310 Running System Manager

Preparing to Restore Data to the SPE310 Running System Manager

Using the Restore Wizard

Starting the Restore Process

Installing Windows OS Upgrade

Upgrading a Cisco CallManager Publisher to Version 3.3(2) and Restoring the Publisher Database

Installing a New Cisco CallManager Version 3.3(2) Publisher

Installing a New Cisco CallManager Version 3.3(2) Subscriber

Installing Cisco-Verified McAfee Anti-Virus Services

Upgrading System Card Images

Upgrading Cisco IOS Software Images

Upgrading Cisco IOS Software Images Through System Manager

Upgrading Cisco IOS Software Images Through the Cisco IOS Command-Line Interface

Related Documentation

Cisco ICS 7750 Documents

System Software Release 2.6.0 Documents

Cisco CallManager Release 3.3(2) Documents

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


Upgrading to System Software Release 2.6.0 and Cisco CallManager Release 3.3.(2) on the Cisco ICS 7750


May 7, 2003

This document tells how to upgrade the Cisco ICS 7750 from system software releases 2.1.0 through 2.5.0 to system software release 2.6.0. Use this document with the Release Notes for System Software Release 2.6.0 on the Cisco ICS 7750.

Contents

This document contains the following sections:

System Software Release 2.6.0 Installation Scenarios

Accessing the Cisco ICS 7750

Installing the CD-ROM Drive

Preparing to Upgrade to System Software Release 2.6.0

Disabling Third-Party Cisco-Verified Applications

Removing the Existing Cisco IP Telephony Applications Server Backup Utility

Installing the Upgraded Cisco IP Telephony Applications Server Backup

Backing Up Cisco CallManager Data

Backing Up System Manager Data

Reimaging an SPE310

Installing System Software Release 2.6.0

Restoring System Data to the SPE310 Running System Manager

Installing Windows OS Upgrade

Upgrading a Cisco CallManager Publisher to Version 3.3(2) and Restoring the Publisher Database

Installing a New Cisco CallManager Version 3.3(2) Publisher

Installing a New Cisco CallManager Version 3.3(2) Subscriber

Installing Cisco-Verified McAfee Anti-Virus Services

Upgrading Cisco IOS Software Images

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

System Software Release 2.6.0 Installation Scenarios

There are several scenarios for upgrading to system software release 2.6.0, depending on whether you are upgrading an SPE running System Manager or an SPE running Core Software, whether the SPE is running Cisco CallManager, and whether it is running a Cisco CallManager publisher or subscriber.

Refer to the flowchart in Figure 1 to determine which upgrade scenario you need to perform. Then see the appropriate section, and perform the procedures identified there. Each scenario lists a series of procedures that must be performed in the order listed. Instructions for each procedure are provided in the section identified.


Note If you are upgrading more than one SPE running Cisco CallManager, you must complete the upgrade on the SPE running the Cisco CallManager publisher first, and then upgrade the SPEs running Cisco CallManager subscribers. If upgrading more than one SPE running Cisco CallManager subscribers, you must complete each SPE upgrade before beginning the upgrade process on another SPE.


Figure 1 System Software Release 2.6.0 Upgrade Scenarios

Upgrading an SPE Running System Manager without Cisco CallManager

To upgrade an SPE running System Manager that is not running Cisco CallManager to system software release 2.6.0, perform the following procedures in the order in which they are listed:

1. Preparing to Upgrade to System Software Release 2.6.0

2. Backing Up System Manager Data

3. Reimaging an SPE310

4. Installing System Software Release 2.6.0

5. Restoring System Data to the SPE310 Running System Manager

6. Upgrading System Card Images

After you upgrade the SPE to system software release 2.6.0, then, if you wish, you can install Cisco CallManager release 3.3(2). To install it, first install the Windows OS upgrade as described in the "Installing Windows OS Upgrade" section, then see the appropriate section below, depending on whether you are installing a Cisco CallManager publisher or installing a Cisco CallManager subscriber:

Installing a New Cisco CallManager Version 3.3(2) Publisher

Installing a New Cisco CallManager Version 3.3(2) Subscriber

Upgrading an SPE Running System Manager with a Cisco CallManager Publisher

To upgrade an SPE running System Manager that is running a Cisco CallManager publisher, you must upgrade System Manager to release 2.6.0 and upgrade Cisco CallManager to release 3.3(2). Perform the following procedures in the order in which they are listed:

1. Preparing to Upgrade to System Software Release 2.6.0

2. Disabling Third-Party Cisco-Verified Applications

3. Removing the Existing Cisco IP Telephony Applications Server Backup Utility

4. Installing the Upgraded Cisco IP Telephony Applications Server Backup

5. Backing Up Cisco CallManager Data

6. Backing Up System Manager Data

7. Reimaging an SPE310

8. Installing System Software Release 2.6.0

9. Restoring System Data to the SPE310 Running System Manager

10. Installing Windows OS Upgrade

11. Upgrading a Cisco CallManager Publisher to Version 3.3(2) and Restoring the Publisher Database

12. Installing Cisco-Verified McAfee Anti-Virus Services

13. Upgrading System Card Images

Upgrading an SPE Running System Manager with a Cisco CallManager Subscriber

To upgrade an SPE running System Manager that is running a Cisco CallManager subscriber, you must upgrade System Manager to release 2.6.0 and upgrade Cisco CallManager to release 3.3(2). Perform the following procedures in the order in which they are listed:

1. Preparing to Upgrade to System Software Release 2.6.0

2. Backing Up System Manager Data

3. Reimaging an SPE310

4. Installing System Software Release 2.6.0

5. Restoring System Data to the SPE310 Running System Manager

6. Installing Windows OS Upgrade

7. Installing a New Cisco CallManager Version 3.3(2) Subscriber

8. Installing Cisco-Verified McAfee Anti-Virus Services

9. Upgrading System Card Images

Upgrading an SPE Running Core Software without Cisco CallManager

To upgrade an SPE running Core Software that is not running Cisco CallManager, perform the following procedures in the order in which they are listed.


Note If upgrading an SPE on which Cisco Unity, CRA, or another AVVID application is installed, refer to the application documentation to determine if the application is compatible with Cisco CallManager release 3.3.(2). If the application requires an upgrade, refer to the application documentation for instructions.


1. Preparing to Upgrade to System Software Release 2.6.0

2. Installing System Software Release 2.6.0

After you upgrade the SPE to system software release 2.6.0, then, if you wish, you can install Cisco CallManager release 3.3(2). To install it, first install the Windows OS upgrade as described in the "Installing Windows OS Upgrade" section, then see the appropriate section below, depending on whether you are installing a Cisco CallManager publisher or installing a Cisco CallManager subscriber:

Installing a New Cisco CallManager Version 3.3(2) Publisher

Installing a New Cisco CallManager Version 3.3(2) Subscriber

Upgrading an SPE Running Core Software with a Cisco CallManager Publisher

To upgrade an SPE running Core Software that is running a Cisco CallManager publisher, you must upgrade the Core Software to release 2.6.0 and upgrade Cisco CallManager to release 3.3(2). Perform the following procedures in the order in which they are listed:

1. Preparing to Upgrade to System Software Release 2.6.0

2. Disabling Third-Party Cisco-Verified Applications

3. Removing the Existing Cisco IP Telephony Applications Server Backup Utility

4. Installing the Upgraded Cisco IP Telephony Applications Server Backup

5. Backing Up Cisco CallManager Data

6. Reimaging an SPE310

7. Installing System Software Release 2.6.0

8. Installing Windows OS Upgrade

9. Upgrading a Cisco CallManager Publisher to Version 3.3(2) and Restoring the Publisher Database

10. Installing Cisco-Verified McAfee Anti-Virus Services

Upgrading an SPE Running Core Software with a Cisco CallManager Subscriber

To upgrade an SPE running Core Software that is running a Cisco CallManager subscriber, you must upgrade the Core Software to release 2.6.0 and upgrade Cisco CallManager to release 3.3(2). Perform the following procedures in the order in which they are listed:

1. Preparing to Upgrade to System Software Release 2.6.0

2. Reimaging an SPE310

3. Installing System Software Release 2.6.0

4. Installing Windows OS Upgrade

5. Installing a New Cisco CallManager Version 3.3(2) Subscriber

6. Installing Cisco-Verified McAfee Anti-Virus Services

7. Upgrading System Card Images

Accessing the Cisco ICS 7750

This section gives instructions for accessing the Cisco ICS 7750 Windows user interface, System Manager, and the Cisco ICS 7750 processor cards. It contains the following sections:

Accessing the SPE310 Windows Interface Through Directly Connected Peripherals

Accessing the SPE310 Windows Interface Through Terminal Services Client

Accessing ICS System Manager

Accessing Processor Cards Through the SAP

Accessing the SPE310 Windows Interface Through Directly Connected Peripherals

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


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

Step 2 Continue as follows, according to the type of peripherals that you are using:

USB—Connect a USB hub to one SPE310 USB port. Then connect a USB keyboard and a USB mouse to the USB hub. The USB hub must be used because the CD-ROM drive requires one of the two available USB ports on the SPE310.

PS/2—Connect the "Y" splitter cable for your keyboard and mouse to the keyboard/mouse port on the target SPE310. 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 SPE310, the keyboard and mouse must be connected at or before the time of SPE310 rebooting in order for them to be recognized by the operating system. This is not the case with a USB keyboard and mouse, which are usually recognized without rebooting the operating system.



Note For a summary of the issues related to the connection of peripherals to SPE310s, for best practices in using peripherals with SPE310s, and for a list of USB peripherals that have been tested on the Cisco ICS 7750, see the "Using Peripherals with SPE310s" section in the "Operating the Cisco ICS 7750" chapter of the Cisco ICS 7750 Installation and Configuration Guide.


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


Accessing the SPE310 Windows Interface Through Terminal Services Client


Note You can install only the Core Software through Terminal Services Client.


To access the SPE310 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. Then choose File > Connect.

If you do not have a Terminal Services Client connection defined for the target SPE, choose File > New Connection. 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 SPE310, such as Windows Explorer and the Control Panel.


Accessing ICS System Manager

Follow these steps to access ICS System Manager.


Note Java must be enabled on your web browser to access ICS System Manager. For specific instructions on configuring your web browser, see the Cisco ICS Installation and Configuration Guide.



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 Processor Cards Through the SAP

The System Alarm Processor (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, follow these steps:


Step 1 If your PC is not already directly connected to the SAP console port, you can use an 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).

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 information as follows:

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. 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, and choose the modem installed in your PC. Then, in the Area Code and Phone Number fields, enter the area code and phone number of the remote Cisco ICS 7750. 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: System Processing Engine
6. Slot 6: System Processing Engine

Make a selection to switch:

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

You hove now established a connection to the selected card, and you can enter the command-line interface (CLI) commands that are supported on that card.


Installing the CD-ROM Drive

This section describes how to connect the CD-ROM drive to the Cisco ICS 7750. It contains the following topics:

Attaching the CD-ROM Drive Tray

Connecting the CD-ROM Drive

Attaching the CD-ROM Drive Tray

Complete the following steps to attach the CD-ROM drive tray to the fan tray on the Cisco ICS 7750.


Note The CD-ROM drive tray is for temporary use when installing software. Remove the CD-ROM drive and drive tray when you finish the installation.



Step 1 Remove the CD-ROM drive tray from the accessory kit.

Step 2 Attach the CD-ROM drive tray to the fan tray underneath the SPE310 by threading the hooks on the drive tray into the grid on the fan tray, as shown in Figure 2.

Figure 2 Attaching the CD-ROM Drive Tray


Connecting the CD-ROM Drive

Complete the following steps to connect the CD-ROM drive:


Step 1 Remove the CD-ROM drive from the accessory kit.

Step 2 Place the CD-ROM drive in the drive tray as shown in Figure 3.


Caution Do not place any object other than the CD-ROM drive on the drive tray. The drive tray is designed only for the weight of the CD-ROM drive.

Figure 3 Installing the CD-ROM Drive

Step 3 Connect the CD-ROM drive USB cable to either one of the USB ports on the SPE310.


Preparing to Upgrade to System Software Release 2.6.0

Before you start the upgrade process, perform the following tasks:

Connect a monitor, keyboard, and mouse to the SPE310 you want to upgrade. For instructions, see the "Accessing the SPE310 Windows Interface Through Directly Connected Peripherals" section.

Connect the CD-ROM drive to the Cisco ICS 7750. For instructions, see the "Connecting the CD-ROM Drive" section.

Disabling Third-Party Cisco-Verified Applications

If you have Cisco-verified applications—Cisco Architecture for Voice, Video, and Integrated Data (AVVID) partner applications—or platform agents installed on the server, you must disable the services.

The following platform agents and services may interfere with the upgrade process: antivirus services, intrusion detection services, OEM server agents, server management agents, VoIP monitoring/performance monitoring, or remote access/remote management agents. Disabling platform agents and services, such as performance monitoring (NetIQ), antivirus (Cisco-approved McAfee services), intrusion detection, and remote management services, will ensure that the upgrade completes.

This document provides procedures for disabling Cisco-approved McAfee antivirus services only. If you need assistance with disabling other services or applications, refer to the documentation for that service or application.

To disable the McAfee antivirus services, perform the following tasks:


Step 1 Log in to Windows 2000, using the Administrator password.

Step 2 Choose Start > Settings > Control Panel > Administrative Tools > Services.

Step 3 From the Services window, right-click one of the antivirus services (Network Associates Alert Manager, Network Associates McShield, or Network Associates Task Manager) and choose Properties.

Step 4 Verify that the General tab is displayed in the Properties window.

Step 5 In the Service Status area, click Stop.

Step 6 From the Startup Type drop-down list box, choose Disabled.

Step 7 Click Apply.

Step 8 Click OK.

Step 9 Perform Step 2 through Step 8 for all Cisco-verified McAfee antivirus services (Network Associates Alert Manager, Network Associates McShield, and Network Associates Task Manager).

Step 10 Reboot the server, and verify that the services are not running.


If you have performance monitoring software, such as NetIQ, or remote management software installed, locate the appropriate product documentation for procedures on disabling the applications.


Caution If Cisco-approved antivirus or intrusion detection software is not currently installed on the server, Cisco strongly recommends that you not install the software until after you complete the entire upgrade or installation on all the servers in the cluster.

Removing the Existing Cisco IP Telephony Applications Server Backup Utility

Follow these steps to remove the existing backup utility:


Step 1 Choose Start > Settings > Control Panel.

Step 2 Double-click Add/Remove Programs.

Step 3 Locate the Cisco IP Telephony Applications Backup, and click the Change/Remove button.

Step 4 Click the Yes button.

Step 5 Click the Close button in the lower right-hand corner of the window.


Installing the Upgraded Cisco IP Telephony Applications Server Backup

Follow these steps to install the upgraded backup utility:


Step 1 Insert the Cisco CallManager Publisher Upgrade CD-ROM into the CD-ROM drive.

Step 2 To launch the backup, use Windows Explorer to browse to the CD-ROM drive, and double-click \Backup\setup.exe.

Step 3 Accept the terms of the license agreement by clicking the I accept the terms in the license agreement radio button. Click Next.

Step 4 In the Backup Role window, click the Backup Server radio button. Click Next.

Step 5 Click the version of Cisco CallManager that is currently running on the SPE310. Click Next.

Step 6 In the Ready to Install the Program window, click Install.

The installation occurs, as indicated in the status bar. Do not click Cancel. Continue to wait while the installation completes.

Step 7 When the installation completes, click Finish.

Step 8 Click Yes to restart the server.

Step 9 Log in to the SPE310, using the Administrator account and password.

Step 10 Right-click the backup utility icon in the Windows 2000 system tray; then choose Configure Settings.

Step 11 When the Backup Utility Configuration window appears, perform the following steps:

a. With the CallManager tab open, click Add.

b. In the dialog box that displays, enter the publisher database server name; click OK.

c. To test for CallManager components, click Verify.

d. When you receive the authentication results in the dialog box, click OK.


Caution If you have installed CDR Administrative and Reporting (CAR) on the SPE310, verify that you have added the publisher database server name or IP address to the Cisco CallManager and CAR target panes. Use the same naming conventions, either DNS or IP addresses, in each pane so the restore utility can restore CAR during the Cisco CallManager database restoration.

Step 12 Click the uOne, CRA (Cisco Customer Response Applications), or CAR (Cisco CDR Administrative and Reporting Tool) tab, and repeat Step 11 to configure the backup for Cisco uOne, CRA, or Cisco CAR.

Step 13 When the backup setup window displays, click the Destination tab, as shown in Figure 4.

Figure 4 Destination Tab


Caution Do not click the Local Directory radio button. The operating system installation erases all existing data stored on the local directory.

Step 14 Configure the location, either the network directory or the tape device, where you plan to store all data that will be backed up during the backup. Cisco allows you to choose only one destination for all stored data.

Step 15 Click OK.

Step 16 When a prompt asks you to save the settings and exit, click Yes.


Backing Up Cisco CallManager Data

You must back up the publisher database before you install the operating system. Follow these steps:


Step 1 Right-click the Cisco IP Telephony Applications Backup Utility icon in the Windows 2000 system tray and choose Start backup now.

Step 2 After the backup completes, verify that it completed successfully. The Backup Utility Viewer displays the status of the backup operation by highlighting each task as it occurs. Use the information generated in the log window to help identify problems. When the "Waiting until <time> on <date>" message displays, the backup is complete. The last line in the log file indicates that the log is closed.

You can obtain the StiBack.log from C:\Program Files\Common Files\Cisco\Logs on the backup server. If the following error messages or other error messages are present in the log file, the process did not successfully back up the data:

Cisco CallManager database could not be found on <Server Name>

Could not determine APPS version

Could not find a CCM/ART/CDR SQL database on <Server Name>

Error finding SQL database

Error enumerating registry keys on <Server Name>

Open file request returned Not Enough Space


Note A successful backup is required to avoid loss of your Cisco CallManager data. If the backup fails, refer to the Cisco CallManager documentation to resolve the issue before continuing.


Before continuing, ensure that the backup.ini and dbname.ini files are present in the C:\Recover folder on the SPE310.


Backing Up System Manager Data

Before reimaging the SPE310, you must back up your System Manager data.


Note Backing up System Manager data is only required if you are upgrading an SPE310 running System Manager.


This section explains how to back up SPE310 registry settings, ICS System Manager database records, and Cisco IOS configuration files for analog station interfaces (ASIs) and multiservice route processors (MRPs).


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 Before starting a backup, make sure that at least 75 MB of storage space is available on the target device.



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



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, and keep this information in a secure location. Having this information available can facilitate troubleshooting and make it easier to restore system data.


Follow these steps to start the backup process:


Step 1 On a PC, access ICS System Manager. For instructions on how to access ICS System Manager, see the "Accessing ICS System Manager" section.

Step 2 Click the System Maintenance tab.

Step 3 Click Backup Now.

Step 4 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) on which you want to store your backup files. For example, sharename\path. The share name should not have an IP address or host name prefix such as "\\127.0.0.\1" or "\\localhost\."

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 Windows domain name that you use to gain access to your Windows network during login (for example, MyCompany_Eng), not the domain name used in a URL such as www.cisco.com


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 5 Click Submit to start the backup.

Step 6 When the backup is complete, press Continue.

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

Step 7 You must manually back up the Cisco IOS configuration files for the system switch processor (SSP) and each Flash-based MRP card (MRP300, MRP3-8FXS, MRP3-16FXS, or MRP3-8FXOM1).

a. Telnet to the MRP 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) on which 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 Cisco 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 3(d), (for example, \\hostname\sharename\path). Name the config file in this format: <backupname>_<hostname>, where backupname comes from the Backup Name in Step 3(a), 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 8 Repeat Step 6 for the SSP and for every Flash-based MRP or ASI card (MRP300, MRP3-8FXS, MRP3-16FXS, or MRP3-8FXOM1) in the chassis.

Step 9 If you have configured VLAN functionality on the Cisco ICS 7750, you may also need to back up the vlan.dat file from the SSP Flash memory. This file stores VLAN configuration information. The vlan.dat file may or may not exist in your SSP Flash memory, depending on your VLAN configuration.

To back up the file vlan.dat, you must use an external TFTP server to copy the file to a location outside of the ICS 7750 chassis.


Reimaging an SPE310

This section covers the procedures for removing and reinstalling the Windows 2000 Server operating system and includes the following sections:

Preparing for SPE310 Reimaging

Reimaging Windows 2000 Server on the SPE310 Hard Disk

Preparing for SPE310 Reimaging

You will need the following information for restoring saved configurations and data. Be sure to record it now:

SPE host names

Passwords, including the following:

Windows administrator password

System Manager admin password

Cisco IOS login password

Cisco IOS enable password

SNMP read-only and read-write community strings

IP address of each card in the chassis

Specific role of each SPE in the chassis, such as CallManager publisher or subscriber

Cisco CallManager and/or other application-specific configuration information and passwords, as applicable

SPE310 Cards and Software

The following are the software configuration rules for SPE310 cards using Cisco ICS 7750 System Software release 2.1.0 and later:

Cisco ICS System Manager software must be installed on one (and only one) SPE310 in a Cisco ICS 7750 chassis.

The SPE running System Manager is installed in slot 6 by default (at the factory). You can move the SPE running System Manager to another slot, provided that you follow the instructions in Cisco ICS 7750 FRU Installation and Replacement and the Cisco ICS 7750 Installation and Configuration Guide.

Cisco ICS Core Software must be installed on all SPEs in the chassis except the SPE running System Manager.

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


Note The specific ICS software package installed on an SPE during the reimaging process determines whether an SPE will be the SPE running System Manager or will be an SPE running Core Software.


Reimaging Windows 2000 Server on the SPE310 Hard Disk

The Cisco ICS 7750 Windows 2000 Bootable CD for SPE, which is included in the accessory kit, contains a special, customized version of Windows 2000 Server. When an SPE310 is booted from the CD, it automatically copies a complete Windows 2000 setup disk image to the Cisco ICS 7750 hard disk; then Windows 2000 performs an automatic silent installation.


Note Because of the way that disk images are formatted, if you attempt to use Windows Explorer or some other file browser to read the Cisco ICS 7750 Windows 2000 Bootable CD for SPE, you will see no files displayed. This is normal and does not indicate faulty CD media. Disk image files cannot be read using conventional file browsers.


Follow these steps to reimage Windows 2000 Server on the SPE310 hard disk.


Note At various points during SPE reimaging, alarm LEDs may light temporarily on the various cards in the Cisco ICS 7750 chassis. This is a normal part of the process, and any alarm LED indications on the SPE being reimaged can be disregarded for the duration of the reimaging process.



Caution Powering down an SPE will interrupt any services or applications running on that SPE. Measures should be taken to minimize the effects on users.


Step 1 Put the Windows 2000 CD in the CD-ROM drive, making sure to seat the CD securely on the CD-ROM drive spindle, and close the cover.


Note Use only the Windows 2000 CD included in the Cisco ICS 7750 accessory kit. This version has been customized for use with the Cisco ICS 7750. Use of any other version of Microsoft Windows, even if it is the same basic type of operating system, is not supported. Use of any other version of Microsoft Windows will prevent the Cisco ICS 7750 from functioning properly.


Step 2 Power up the SPE310 by reseating it in the Cisco ICS 7750 chassis.


Note If the chassis is not powered up, power it up, and wait for all the components to initialize. This process can take several minutes. Make sure that the chassis is powered on before you reseat the SPE.


The SPE310 should boot automatically from the attached CD-ROM drive. If it does not boot, unseat the SPE from the chassis about an inch, check the cable connection between the CD-ROM drive and the SPE's USB port, and reseat the SPE.

During rebooting, the SPE310 green status LED blinks, and the amber alarm LED is on.

It takes about a minute for the rebooting to complete. On the attached monitor, a text message is displayed, indicating that the SPE reimaging process is about to start.


Note To stop the process at this point, unseat the SPE, remove the Windows 2000 CD from the CD-ROM drive, and reseat the SPE in the chassis. If the operating system reimaging process has already begun, however, you cannot stop the reimaging, and all data on the SPE310's hard disk will be lost.


Step 3 Begin the SPE310 reimaging by pressing the SHTDN button on the SPE. When you press the SHTDN button, the status LED goes out and the alarm LED blinks.

The Symantec Norton Ghost application runs automatically and begins copying the raw Windows 2000 installation image to the SPE hard disk, a process which takes approximately one hour.

During this time, both the green status LED the and amber alarm LED blink in unison. You can view the progress by watching the Norton Ghost display on the attached monitor.


Note If there is a problem during the Norton Ghost execution, such as a hard disk failure or a sector error, you may see an error message that directs you to contact Symantec Support. If this happens, you should instead contact the Cisco Technical Assistance Center (TAC). See the "Obtaining Technical Assistance" section in the Preface for more information.


When the Norton Ghost application has finished running, the status LED goes off and the amber alarm LED stays on. The attached monitor displays a completion status message.

Step 4 Unseat the SPE310 from the Cisco ICS 7750 chassis.

Step 5 If the chassis is connected to an existing network (for example, by means of an Ethernet connection to the SSP), remove the network connection now. (If the chassis is connected only to an isolated console PC through the SSP Ethernet connection, you can leave that connection in place.)


Note This step is necessary to prevent the SPE from being vulnerable to virus or worm attack. You will be able to restore the network connection soon, after you install the required operating system security hotfixes.


Step 6 Remove the CD from the CD-ROM drive, and disconnect the CD-ROM drive cable from the SPE's USB port.

Step 7 If you disconnected the keyboard and mouse, reconnect them to the SPE.

Step 8 Reboot the SPE310 by reseating it in the chassis.


Note If you notice the execution of CHKDSK as a result of reseating the SPE, it is an expected behavior. CHKDSK is part of the Windows 2000 reimaging process, a routine check to find and fix any potential inconsistencies or errors on the SPE hard disk.


The Windows 2000 silent installation begins, requiring no user input. During the installation, the SPE reboots automatically several times as Windows installs itself, finds and registers devices, and creates user settings. When the installation is complete (after about 20 minutes), the green status LED blinks and the alarm LED is off. The following message appears:

It is now safe to turn off your computer.

Step 9 Unseat the SPE about one inch, wait 10 seconds, and reseat the SPE to reboot again.

When the SPE comes up, the Windows 2000 login screen is displayed on the attached monitor.

Step 10 Log in to the SPE, using the default Windows user login name (administrator) and password (changeme).


Installing System Software Release 2.6.0

Complete the following steps to install system software release 2.6.0.


Step 1 Access the Windows interface on the SPE310 on which you want to install system software release 2.6.0. See the "Accessing the Cisco ICS 7750" section.


Note If you are installing ICS System Manager, you must use directly connected peripherals. However, if you are installing Core Software, you can connect with Terminal Services Client.


Step 2 Insert the Cisco ICS 7750 System Software (Release 2.6.0) CD-ROM into the CD-ROM drive.

Step 3 On the SPE310 on which you want to install release 2.6.0 software, choose Start > Run.

The Run dialog opens.

Step 4 In the Open field, enter d:\setup to run setup.exe from the CD-ROM.

The Installation Wizard starts, displaying the Welcome page.

Step 5 Follow the instructions presented by the Installation Wizard. If you need clarification about any of the options presented by the Installation Wizard, consult the online help.


Note If installing system software release 2.6.0 on an SPE that has been reimaged, you must set the SPE310 host name to be the same as it was before you reimaged the SPE310.



Note During the installation process, the SPE310 may restart. If you are accessing the SPE310 through directly connected peripherals, the setup program will automatically log in as Administrator and continue the installation process after the SPE310 restarts. If you are accessing the SPE310 through Terminal Services Client, then you will have to log in to the SPE310 again after the restart. The setup program will continue the installation process after you log in.


Step 6 If installing system software release 2.6.0 in a scenario where Cisco Callmanager will also be upgraded, verify that the host name of the SPE310 is the same as it was before you reimaged. This is required to complete the Cisco CallManager release 3.3(2) upgrade. If the SPE310 host name is not identical to its previous value, then set the host name to its previous value using the Network Identification tab of the System Properties dialog box in the Windows 2000 Control Panel.


Restoring System Data to the SPE310 Running System Manager

Follow the instructions in this section to restore your System Manager data (SPE310 registry settings, ICS System Manager database records, and Cisco IOS configuration files for ASI and MRP200 cards) after you have reimaged the SPE running System Manager. This section contains the following section:

Preparing to Restore Data to the SPE310 Running System Manager

Using the Restore Wizard

Starting the Restore Process


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).


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 MRP and ASI cards (MRP300, MRP3-8FXS, MRP3-16FXS, and MRP3-8FXOM1) 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 MRP and ASI cards in the chassis that do not have Flash memory installed (MRP200, ASI160, ASI81).

Step 5 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:

a. Change the administrator password:

net user administrator <password>

where <password> is the administrator password in use when you performed the backup.

b. Change the reimaged SPE310 IP address and default gateway IP address:

netsh interface ip set address local static <SPE310 IP> <subnet> <gateway IP> <num.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.


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. Complete the following steps:


Step 1 Access the Windows interface on the SPE310 running System Manager. See the "Accessing the Cisco ICS 7750" section.

Step 2 If necessary, mount the external device where the backup data is saved.

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

Step 4 Click Restore Wizard.

The Welcome to the Restore Wizard dialog box appears.

Step 5 Click Next.

The What to Restore dialog box appears.

Step 6 Click the Import File button.

The Backup File Name dialog box 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 7 Identify database records to be restored as follows: From the tree in the left pane of the What to Restore dialog box, 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 8 Click OK.

Step 9 Click Next.

The Completing the Restore Wizard dialog box appears.

Step 10 Click the Advanced button.

The Where to Restore page appears.

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

Step 12 Click Next.

The How to Restore page appears.

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

Step 14 Click Next.

The Advanced Restore Options page appears.

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

Step 16 Click Next.

The Completing the Restore Wizard dialog box appears again.

Step 17 Click Finish.

Step 18 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 box:

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 in order to restore system software data.


Step 19 Click Close.

Step 20 Close the Backup window.


Continue with the "Starting the Restore Process" section.

Starting the Restore Process

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


Step 1 Access the Windows interface on the SPE310 running System Manager. See the "Accessing the Cisco ICS 7750" section.

Step 2 On the SPE310, click Start > Run.

The Run dialog box 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

Cisco 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 Gently slide each MRP and ASI card 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.


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 7 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 8 Reload the Cisco IOS image on the SSP:

a. On a PC, access ICS System Manager. For instructions on how to access ICS System Manager, 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.

If you had previously configured the Cisco ICS 7750 for multiple VLANs, you might also need to restore the vlan.dat file to the SSP Flash memory, depending on the VTP mode of the SSP.

If the SSP is operating in VTP transparent mode, restore the vlan.dat file, along with the configuration text. Reload the SSP in order for the vlan.dat file to take effect.

If the SSP is operating in VTP server or client mode, the SSP will relearn the VLAN configuration in the network through VTP advertisements. You will need to reset the correct VTP domain and password on the SSP. Refer to the "Configuring VLANs" section in the Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide, Releases 12.0(5)WC4 and 12.0(5)WC5.

Problems with VTP advertisements might occur in the following situations:

If the configuration text contains "switchport access vlan 3" and no vlan.dat file, the SSP will go into VLAN Trunking Protocol (VTP) transparent mode. The SSP will create a vlan.dat file, using the current information in its configuration, and choose a domain name of UPGRADE. In this case, use the CLI to configure the SSP for server or client mode and define the correct domain name and password. The SSP should learn from the advertisements. For additional information, refer to the "Configuring VLANs" section in the Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide, Releases 12.0(5)WC4 and 12.0(5)WC5.

If all the switches in the network lose power and the SSP is the only server switch (with no vlan.dat file), the client will not advertise after it reboots. In this case, all VLANs need to be re-created on the server.

If the SSP (in server or client mode) is the only switch in the VTP domain, the SSP will not receive any advertisements; therefore, the vlan.dat file should be restored as in VTP transparent mode.


Tip It is recommended that you run the SSP in VTP transparent mode if the SSP is not part of any VTP domain.


To restore the vlan.dat file and copy the system image into the current Flash configuration on the SSP, reload the SSP, and execute the following command:

Switch#copy tftp://<ip address of server>/<dir>/<filename> flash:vlan.dat

where <ip address of server> is the IP address of the TFTP server, <dir> is the directory name on the TFTP server, and <filename> is the filename to copy from the TFTP server.


Note Refer to Loading and Maintaining System Images for additional information about copying images between Flash memory and a network server.



Installing Windows OS Upgrade

To install Windows OS upgrade version 2000.2.3, insert the OS Upgrade for Cisco Call Manager and Cisco CRA/CRS (Release 2000-2-3) CD-ROM into the CD-ROM drive, browse to the file win-os-upgrade.2000-2-3.exe on the CD-ROM, and double-click it. The upgrade will install automatically. There are three phases of the Windows OS upgrade process, and the SPE310 must be rebooted at the end of each phase. After each reboot, you must log in as Administrator to continue to the next phase.


Caution Cisco strongly recommends that you do not install any operating system support patches, with the exception of Windows OS upgrade version 2000.2.4, until you install Cisco CallManager on every server in the cluster.


Note Do not install this Windows OS upgrade on any SPE310s running Cisco Unity.



Note During the OS installation, you may see an error message that says, "An error occurred which prevented the Dynamic Host Configuration Protocol (DHCP) component from being installed or removed. The error was..." You might also see an error message that says "Another copy of program is running." These messages are expected and can be safely ignored


Upgrading a Cisco CallManager Publisher to Version 3.3(2) and Restoring the Publisher Database

Following these steps to upgrade the directory, the database, and Cisco CallManager via CD-ROM. The CD-ROM also prompts you to restore the data that the backup utility stored to a network directory or tape device.


Note It is not recommended that any of the Cisco CallManager systems be joined in an NT Domain until all systems within the cluster have been installed or upgraded. It is not recommend that any third-party software packages (such as anti-virus software, intrusion detection software, or performance monitoring software) be installed on the Cisco CallManager systems within the cluster until all of the Cisco CallManager systems have been installed or upgraded. The Cisco CallManager installation will fail if any of these packages are installed and enabled during the installation process.



Step 1 During the Cisco CallManager backup process, a \Recover folder is created in the backup destination directory that contains the files dbname.ini and backup.ini. Copy the \Recover folder and the files in it from the backup destination location to the SPE310 on which you will install Cisco CallManager. One method of copying this folder is to choose Start > Programs > Accessories > Command Prompt, and in the command prompt window, enter the command xcopy /s /i <X:backup_dir>\Recover C:\Recover, replacing <X:backup_dir> with the drive letter and directory name of the backup destination you specified in Step 14 of "Installing the Upgraded Cisco IP Telephony Applications Server Backup."


Note The files dbname.ini and backup.ini must be present and in the C:\Recover directory on the SPE310 before beginning the Cisco CallManager upgrade, otherwise your Cisco CallManager data will not be restored.


Step 2 Verify that the SPE310 host name is identical to the host name that was in use before the reimage.

Step 3 In the C:\ directory of the SPE310, create an empty (0-byte) file called stiRecover.flg. This file is required to cause the Cisco CallManager installation program to perform an upgrade instead of a fresh installation. One method to create this file is to, from the Windows 2000 Start menu, choose Run, then in the Open field, enter notepad C:\stiRecover.flg. Notepad will start ask you want to create a new file. Click Yes. Then, from the Notepad menu, choose File > Exit to close Notepad. You can verify the creation of the file by, from the Windows 2000 Start menu, choosing Programs > Accessories > Command Prompt and executing the command dir C:\stiRecover.flg. If the file appears in the directory listing, you have successfully created it.


Note The filename must be stiRecover.flg and not stiRecover.flg.txt.


Step 4 Log in to the SPE310 by using the administrator account and password.

Step 5 Insert the Cisco CallManager Upgrade and New Installation and Recovery CD ROM into the CD-ROM drive.

Step 6 Browse to the file D:\ccmsetup.exe and double-click it.

Step 7 To acknowledge that you disabled or uninstalled Cisco-verified applications, click Yes.

Step 8 The Preparing to Install window displays. Do not click Cancel.

Step 9 In the Welcome window, click Next.

Step 10 Accept the terms of the license agreement by clicking the I accept the terms in the license agreement radio button. Click Next.

Step 11 In the Customer Information window, enter the User Name and Organization that you entered during the operating system installation display.

In the Product Key field, enter the product key BTOO VQES CCJU IEBI. Click Next.

Step 12 In the Setup Type window, click the Complete radio button. Click Next.

Step 13 In the Setup Type window, click the Publisher radio button. Click Next.

Step 14 In the Administrator Password window, enter your Windows 2000 Administrator password.

Step 15 In the SQL Password window, perform the following procedure:

a. Enter the SA (SQL Server system administrator) password.

b. Press the Tab key.

c. To confirm the password, enter the password again. Click Next.

Step 16 Enter the password that you want to use for the Directory Manager account.

Step 17 Confirm the Directory Manager account password.

Step 18 Choose Backup Server.

Step 19 In the Ready to Install the Program, click Install.

The status bar indicates the progression of the installation. Wait while the installation completes.

Microsoft SQL Server 2000, Microsoft SQL Server 2000 Service Pack 2.0, and DC Directory install. This process takes from 15 to 20 minutes.

Step 20 To reboot the server, click Yes.

Step 21 After the SPE310 reboots, log into the SPE310, using the Administrator account and password.

Step 22 The Cisco IP Telephony Applications Restore Utility automatically launches the restoration of the Cisco CallManager data that you stored to a network directory or tape device.

Step 23 In Step 1 of the Restore Utility, perform the following procedure:

a. Choose the location of the data.

b. Enter a username and password with administrator access rights on the server, and click Verify.

c. When you receive the authentication results in the dialog box, click OK.

d. Click Next. The window shown in Figure 5 appears.

Figure 5 Choosing the Target Server

Step 24 In Step 2 of the Restore Utility, perform the following procedure:

a. Highlight the CallManager target, which is the SPE310 on which you installed Cisco CallManager.

b. Make sure that the SA password remains blank. Click Verify.

c. A dialog box shows that authentication was successful. Click OK.

d. Click Next to continue.

Step 25 To accept that you will overwrite the target server and lose all existing data if you proceed, click Yes.

The utility restores the files to the staging directory and then to the server where you want the utility to send the files.

Step 26 The restoration log displays. Verify that no errors exist in the log. If the following error messages or other error messages display in the log file, the process did not successfully restore the data:

Failed to drop CCM/ART/CDR database from <Server Name>

Failed to restore DC Directory

Failed to stop DC Directory service

Failed to restart DC Directory service

Step 27 After you verify that no errors exist, click OK.

The Cisco CallManager installation takes approximately 20 minutes. Wait while the installation completes.

Step 28 After the installation completes, click the Finish button.

Step 29 When a prompt asks you to reboot the server, click Yes.

Step 30 Log on to the server, using the administrator account and password.

Step 31 Verify that your data and configuration were restored to the server.


Installing a New Cisco CallManager Version 3.3(2) Publisher

Follow these steps to install the directory, the database, and Cisco CallManager from the CD-ROM:


Step 1 Log in to the SPE310 by using the administrator account and password.

Step 2 Obtain the Cisco CallManager Upgrade and New Installation and Recovery CD ROM and insert it into the CD-ROM drive.

Step 3 Browse to the file D:\ccmsetup.exe and double-click it.

Step 4 To acknowledge that you have disabled/uninstalled all Cisco-verified applications, click Yes.

Step 5 When the Welcome window displays, click Next.

Step 6 Accept the Cisco CallManager license agreement by clicking the I accept the terms in the license agreement radio button. Click Next.

Step 7 In the Customer Information window, enter the user name and organization that you entered during the operating system installation.

In the Product Key field, enter the product key BTOO VQES CCJU IEBI. Click Next.

Step 8 In the Setup Type window, click the Complete button.

Step 9 Cisco requires that you install Cisco CallManager on the publisher database server first, so that authentication can occur between the publisher database and subscriber servers.

In the Server Type window, choose Publisher. Click Next.


Note The publisher database server serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server. The installation process necessitates this connection, so the publisher database server can be copied to the local drive on the subscriber server. To make sure that a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. If you are using Domain Name System (DNS), use a fully qualified domain name (for example, hostname.cisco.com) with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.


Step 10 In the Administrator password window, enter your Windows administrative password. Click Next.

Step 11 In the SQL Password window, complete the following steps:

e. Enter the SA (SQL Server system administrator) password.

f. Press the Tab key.

g. To confirm the password, enter the password again. Click Next.

Step 12 In the Cisco Directory Password window, complete the following steps:

a. Enter the Directory Manager password.

b. Press the Tab key.

c. To confirm the password, enter the password again. Click Next.

Step 13 When a prompt asks you to install the backup software, complete the following steps:

a. Click the Backup Server radio button.

The Backup Server invokes the backup. After you install Cisco CallManager, you can change this selection to another server if you want to do so.

b. If you want to configure backup settings immediately after you install Cisco CallManager, check the Run Backup Manager at the end of the setup check box.

c. Click OK.

Step 14 The Cisco CallManager and other included software can now be installed. Click Install. This part of the installation takes about 30 to 45 minutes, depending on your server type.

The status bar in the window indicates the progression of the installation. Microsoft SQL Server 2000, Microsoft SQL Server Service Pack 2.0, DC Directory, and Cisco CallManager will be installed. Wait while the installation completes.

Step 15 When the Cisco CallManager installation completes, click Finish to exit the wizard.

The Restart Server dialog box displays.

Step 16 Perform one of the following, depending on what you want to accomplish:

If you checked the Run Backup Manager at the end of setup check box in Step 13, click No when a prompt asks you to restart the server. Then configure the backup settings.

For information on configuring backup configuration settings, refer to Backing Up and Restoring Cisco CallManager Release 3.3.

If you do not plan to configure backup settings at this time or if you have completed the backup configuration tasks, click Yes to restart the server.

Step 17 Remove the CD-ROM from the CD-ROM drive.

Step 18 After the server reboots, log in using the Administrator account and password.


Tip If you have not configured backup settings or if you want to modify the settings, refer to Backing Up and Restoring Cisco CallManager Release 3.3.



Installing a New Cisco CallManager Version 3.3(2) Subscriber

Cisco requires that you perform a new installation on each subscriber database server in the cluster.

Follow these steps to install Cisco CallManager on the subscriber servers:


Step 1 Log in to the SPE310 by using the administrator account and password.

Step 2 Obtain the Cisco CallManager Upgrade and New Installation and Recovery CD ROM and insert it into the CD-ROM drive.

Step 3 Browse to the file D:\ccmsetup.exe and double-click it.

Step 4 To acknowledge that you disabled or uninstalled all Cisco-verified applications, click Yes.

Step 5 When the Welcome window displays, click Next.

Step 6 Accept the Cisco CallManager license agreement by clicking the I accept the terms in the license agreement radio button. Click Next.

Step 7 In the Customer Information window, enter the User Name and Organization that you entered during the operating system installation.

In the Product Key field, enter the product key BTOO VQES CCJU IEBI. Click Next.


Note The publisher database server serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server before the installation can continue. The installation process requires this connection, so that the publisher database server can be copied to the local drive on the subscriber server. To make sure that a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. If you are using Domain Name System (DNS), use a fully qualified domain name (for example, hostname.cisco.com) with the ping command. If the ping command is not successful, you can also try to access the publisher database server from all subscriber servers by choosing Start > Run, entering <Publisher>\C$, where <Publisher> equals the IP address or name of the server, and then clicking OK. If the publisher database server cannot access the subscriber server, you must exit the installation program, fix the problem, and begin the installation process again.


Step 8 If you installed the backup utility on the publisher database server and you do not want to install it on the subscriber server, perform the following procedure:

a. Click the Custom radio button.

This action will ensure that you do not install the backup utility on the subscriber database servers. If you wish, you may install the backup utility at a later time on this server.

b. Click Cisco Backup.

c. Click This feature will not be available.

d. Click Next.

e. Go to Step 10.

Step 9 If you want to install the backup utility on this server, click the Complete radio button.

Step 10 In the Server Type window, perform the following procedure:

a. Click the Subscriber radio button.

b. Enter the computer name of the publisher database server.


Caution If you enter the IP address or fully qualified DNS of the publisher database server, the installation will fail.

c. Click Next.

Step 11 In the Administrator password window, enter your Windows administrator password.

Click Next.

Step 12 In the SQL Password window, perform the following procedure:

a. Enter the SA (SQL Server system administrator) password.

This password must match the SA password that is used on the publisher database server.

b. Press the Tab key.

c. To confirm the password, enter the password again. Click Next.

Step 13 If you chose Custom in Step 8, go to Step 15.

If you chose Complete in Step 8, continue with Step 14.

Step 14 When a prompt asks you to install the backup software, click the Backup Target radio button. Click OK.

Step 15 You should now install the Cisco CallManager and other included software. Click Install. This part of the installation takes about 30 to 45 minutes, depending on your server type.

The status bar in the window indicates the progression of the installation. Microsoft SQL Server 2000, Microsoft SQL Server Service Pack, DC Directory, and Cisco CallManager install. Wait while the installation completes.

Step 16 When the Cisco CallManager installation completes, click Finish to exit the wizard.

Step 17 Click Yes to restart the server.

Step 18 After the server reboots, log in using the Administrator account and password.


Installing Cisco-Verified McAfee Anti-Virus Services

Because this upgrade process required reimaging of the SPE310s, any third-party, Cisco-verified applications, such as McAfee Anti-Virus services, that had been previously installed were removed. If necessary, reinstall these applications in accordance with the application instructions.

Upgrading System Card Images

System software release 2.6.0 includes upgraded Cisco IOS images for the MRP and SAP system cards. The upgraded Cisco IOS images are located on the Cisco ICS 7750 System Software (Release 2.6.0) CD-ROM. If you have not done so already, you must upgrade the Cisco IOS images for those system cards following the instructions in the "Upgrading System Card Images" section below.

In addition, if you had to reimage the SPE310 running System Manager, all of the Cisco IOS images stored in the System Manager Software Library were erased. Follow the instructions in the "Upgrading System Card Images" below to import the deleted system card Cisco IOS images back into the System Manager Software Library.

Upgrading Cisco IOS Software Images

The SSP, MRPs, and ASIs in your Cisco ICS 7750 run Cisco IOS software. There are two different procedures for upgrading Cisco IOS images on system cards:

Upgrading Cisco IOS Software Images Through System Manager—Use this procedure for the SAP, SSP, MRP200, ASI81, and ASI160 system cards.

Upgrading Cisco IOS Software Images Through the Cisco IOS Command-Line Interface—Use this procedure for the MRP300, MRP3-8FXS, MRP3-8FXOM1, and MRP3-16FXS system cards.

Current Cisco IOS images are available on CCO.


Note When upgrading to system software release 2.6.0, you must upgrade the Cisco IOS images on all MRP200s, ASI81s, ASI160s, and the SSP.


Upgrading Cisco IOS Software Images Through System Manager

To upgrade a Cisco IOS software image on a non-Flash-based system card, use the Software Upgrade tab in System Manager to first upload the new software image to the System Manager software library, and then to deliver the new image to the system card.


Note Although the System Manager software library will display the Cisco IOS image running on Flash-based system cards (the MRP300, MRP3-8FXS, MRP3-16FXS, and MRP3-8FXOM1), you cannot use System Manager to upgrade the Cisco IOS image on these cards. You must upgrade those cards through the Cisco IOS CLI.



Note Before you can upgrade a Cisco IOS software image on a non-Flash-based card (SAP, SSP, MRP200, ASI81, and ASI160), you must have installed ICS System Manager and completed the initial configuration of the Cisco ICS 7750 using ICSConfig. For more information about initial configuration using ICSConfig, refer to the "Completing the Cisco ICS 7750 Installation" chapter in the Cisco ICS 7750 Installation and Configuration Guide.


Uploading a Software Image into the Software Library

Follow these steps to upload an image to the Software Library:


Step 1 Access System Manager. See the "Accessing ICS System Manager" section.

Step 2 From the System Manager home page, click the Software Upgrade tab.

Step 3 Insert the Cisco ICS 7750 System Software (Release 2.6.0) CD-ROM into the CD-ROM drive.

Step 4 Click Add Image.

Step 5 In the Specify Image File Name field, enter the image filename. You can also click Browse to open the browser Choose File dialog box, and locate the image file on the CD-ROM by browsing your PC file system.

Step 6 Click Upload to ICS 7750. The image will be uploaded to the software library. This takes about 30 seconds for a 4-MB file. Once the upload is complete, the Software Upgrade main page appears with an entry for the uploaded image in the Software Library.


Delivering a Cisco IOS Image to a System Card

Follow these steps to deliver a Cisco IOS software image from the software library to a non-Flash-based system card:


Step 1 Access System Manager. See the "Accessing ICS System Manager" section.

Step 2 From the System Manager home page, click the Software Upgrade tab.

Step 3 In the Software Library table, find the Cisco IOS image that you want to deliver.

Step 4 In the same row as the image that you want to deliver, click deliver to a system card.

Step 5 Select the system card from the Select a Target System Card pull-down field.

Step 6 Click Deliver.


Upgrading Cisco IOS Software Images Through the Cisco IOS Command-Line Interface

Delivery of a Cisco IOS image to the MRP300, MRP3-8FXS, MRP3-16FXS and MRP3-8FXO1 system cards is not supported via the Upgrade tab in the current version of System Manager. These cards contain Flash memory and require the use of the Cisco IOS CLI to copy a Cisco IOS image from a TFTP server and deliver it to the Flash memory. Follow these steps to upgrade an image on one of these cards:


Step 1 From the Windows 2000 Start menu, choose Start > Run.

Step 2 Enter the following command to open a Telnet session, where IP address is the IP address of the Flash-based system card on which you want to upgrade the Cisco IOS image.

telnet IP address

Step 3 Enter your login password.

Step 4 Enter the enable command and your Cisco IOS enable password to enter privileged EXEC command mode:

> enable
Password: password
# 

Step 5 Enter the following command:

# copy tftp: flash:

Step 6 Respond to the prompts to supply the location and name of the Cisco IOS image file.


Note For more information about the copy tftp: flash: Cisco IOS command, see the "Loading and Maintaining System Images" section of the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2.



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:

Products & Services: Voice Application Systems: Cisco ICS 7700 Series Integrated Communications Systems: Instructions and Guides

Using the Documentation CD-ROM (order number DOC-CONDOCCD=), navigate to:

Cisco Product Documentation: Voice/Telephony: Cisco ICS 7750

System Software Release 2.6.0 Documents

The following documents were updated or created for system software release 2.6.0. The documents are available at the following location:

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

Cisco ICS 7750 Documentation Locator

Cisco ICS 7750 Installation and Configuration Guide

Cisco ICS 7750 Troubleshooting Guide

Cisco ICS 7750 FRU Installation and Replacement

Release Notes for Cisco IOS 12.2(8)YN on the Cisco ICS 7750

Installing System Software Release 2.6.0 and Cisco CallManager Release 3.3.(2) on the Cisco ICS 7750

Upgrading to System Software Release 2.6.0 and Cisco CallManager Release 3.3.(2) on the Cisco ICS 7750 (this document)

Cisco CallManager Release 3.3(2) Documents

The following documents were updated or created for Cisco CallManager release 3.3(2). The documents are available at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/index.htm

Cisco CallManager Documentation Guide for Release 3.3(2)

Installing Cisco CallManager Release 3.3(2)

Upgrading Cisco CallManager Release 3.3(2)

Backing Up and Restoring Cisco CallManager Release 3.3(2)

Cisco CallManager Administration and System Guides, Release 3.3(2)

Cisco CallManager Features and Services, Release 3.3(2)

Release Notes for Cisco CallManager Release 3.3(2)

Troubleshooting Guide for Cisco CallManager

Obtaining Documentation

These 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 this URL:

http://www.cisco.com

Translated documentation is available at this 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

You can order Cisco documentation in these ways:

Registered Cisco.com users (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 Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

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

You can submit your comments by mail by using the response card behind the front cover of your document or by writing 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 online 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 with these tasks:

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

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

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

Cisco TAC inquiries 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.

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

Cisco TAC Web Site

You can use the Cisco TAC Web Site 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 this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service 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 this URL to register:

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

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

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

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this 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). When you call the center, please have available your service agreement number and your product serial number.