Table of Contents

Operating the Cisco ICS 7750

This chapter explains how to operate the Cisco Integrated Communications System 7750 (Cisco ICS 7750) after initial configuration is complete. The chapter is organized as follows:

Accessing the System

This section tells how to access the Cisco ICS 7750 and gives guidelines for best practices when accessing the system:

Accessing the System During Initial Configuration

When configuring the system for the first time, you can use a web browser to perform most tasks. See "Completing the Cisco ICS 7750 Installation," for system installation and configuration instructions.

Accessing the System After Initial Configuration

After system installation and configuration, you have many ways to access the system:

Terminal Services Client is packaged with Windows 2000. Terminal Services Client is also available for downloading and installing on to other Windows operating systems. See the "Installing Microsoft Terminal Services Client" section for installation instructions.

Accessing ICSConfig

Follow these steps to access ICSConfig.

Note   This section describes ICSConfig functionality after initial configuration is complete. For a description of ICSConfig functionality during initial configuration, see "Completing the Cisco ICS 7750 Installation."

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

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

Step 4   Click OK.

The system discovers the cards that are currently installed in the chassis. After the discovery process is complete, the ICS 7700 System Configuration page displays.

Step 5   Click ICS 7700 System Setup.

Step 6   Make any desired changes to the system parameters, and submit your changes.

It will take up to 20 minutes for the system to process your changes. When the STATUS LEDs on the SPE310s change to solid green, the submit process is complete.

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 "Completing the Cisco ICS 7750 Installation," follow these steps to access ICS System Manager:

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

---

Note    If you do not know the IP address of the SPE310, see the "Determining the IP Address of an SPE310" section.

---

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

Step 4   Click Login.

Navigating in ICS System Manager

To navigate in ICS System Manager, click the tabs that are visible at the top of every ICS System Manager page:

Using ICS System Manager

This section tells how to use ICS System Manager to perform the following routine tasks:

Determining the ICS System Manager Version

The ICS System Manager bundle version number is displayed on the System Manager home page, in a box just under the graphic representation of the system chassis.

For example:

The ICS System Manager home page also lists the cards currently running in the system chassis, as well as their assigned IP addresses and the software running on each. You can switch between a summary view and a detailed view of the hardware and software installed on the cards in the system.

Determining the IOS Software Release Running on the SSP

You can use ICS System Manager to determine the IOS software release that is running on the SSP, as well as other information about the SSP, as follows:

Step 2   Click SSP Manager.

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

Step 4   Click show tech-support.

The system invokes the show version command on the SSP. The following is sample output from this command:

Additional output lines from the show version command include information such as the processor revision numbers and the amount of available memory.

Accessing Cisco CallManager

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

To access Cisco CallManager on the Cisco ICS 7750, follow these steps:

Step 2   Click Applications.

The page refreshes, displaying a table that contains information about the SPE310s 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 SPE310 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 SPE310 running Cisco CallManager: http://IP address/CCMAdmin.

Accessing SPE310s

You can use Terminal Services Client to access the SPE310 desktop, as described in the following topics:

Accessing the SPE310 Windows Interface Through Terminal Services Client

To access the SPE310 Windows interface through Terminal Services Client, follow these steps:

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

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 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 2   Do one of the following, based on the type of peripherals that you are using:

---

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 that the SPE310 is rebooted in order to be recognized by the operating system. A USB keyboard and mouse are usually recognized without rebooting the operating system.

---

---

Note    For a summary of the issues related to the connection of peripherals to SPE310s, as well as best practices for using peripherals with SPE310s, see the "Using Peripherals with SPE310s" section.

---

---

Note    For a list of USB peripherals that have been tested on the Cisco ICS 7750, see the "Using Peripherals with SPE310s" section.

---

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 SPE310s Through Telnet

You can access SPE310s through Telnet, as follows:

Step 2   Enter the following command to open a Telnet session, where IP address is the IP address of the SPE310 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 Cisco IOS CLI on ASIs, MRPs, and the SSP Through Telnet

You must use the Cisco IOS CLI to configure the ASIs, MRPs, and SSP. You can open a Telnet or HyperTerminal session to access individual ASIs or MRPs or the SSP so that you can configure them individually, using IOS software commands.

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.

For example, to determine which IOS software release is running on an ASI, MRP, or the SSP, follow these steps:

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

Step 3   Enter your login password.

Step 4   Enter the show version command:

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, follow these steps:

Or

---

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 C isco 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 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.

A terminal window opens.

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

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

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

Best Practices for Using Microsoft SQL Server

ICS System Manager and Cisco CallManager require Microsoft SQL Server.

Caution   Because of a known issue with Microsoft SQL Server, if you do not install Cisco CallManager on the SPE310 running System Manager, you could expose your network to distributed denial of service (DDoS) attacks. If you do not intend to install Cisco CallManager on the SPE310 running System Manager, you can prevent DDoS attacks by completing the workaround that is provided in the Release Notes for the Cisco ICS 7750 for System Software Release 2.x.x .

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

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

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

Best Practices for Configuring DHCP

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

Caution   CNR is not intended for use as a standalone software tool on the Cisco ICS 7750. Do not use the CNR CLI or graphical user interface (GUI) to invoke CNR commands on the Cisco ICS 7750.

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

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

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

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

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

Do not install or enable a DHCP server on the SPE310 that is running System Manager. You can install or configure DHCP on an external server, provided that

SSP Error Messages

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

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

Best Practices for Using the IOS CLI

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

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

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

ICSConfig Tasks

You should always use ICSConfig for changing the following:

Using Peripherals with SPE310s

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

Consider the following issues when using peripherals with SPE310s:

---

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

---

Best Practices for Using Peripherals with SPE310s

This section describes best practices for using peripherals with SPE310s.

CD-ROM Drive and CD-ROM Drive Tray

The following are best practices for using a CD-ROM drive and the CD-ROM tray with SPE310s:

---

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

---

Keyboards and Mice

The following are best practices for using a PS/2 keyboard and mouse with SPE310s:

Monitors

The following are best practices for using a monitor with SPE310s:

Determining the IP Address of an SPE310

If you do not know the IP address of an SPE310, follow these steps:

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

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

Step 4   Press Ctrl-backslash (\), and use the SAP menu to switch to the SPE310 running System Manager (this card is installed in slot 6 by default).

Step 5   Enter the following command:

Output is displayed that includes information similar to the following:

Step 6   Record the IP address of the SPE310. You need the IP address of the SPE310 running System Manager to log in to the ICS System Manager interface.

Changing the Host Name of the SPE310 Running System Manager

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

Note   For reimaging instructions and for information about changing the host name of other SPE310s, see the Cisco ICS 7750 Troubleshooting Guide.

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

Guidelines for Host Names

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

Assigning a New Host Name

Follow these steps to assign a new host name to the SPE310 running System Manager:

---

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

---

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

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

Step 4   Click the Network Identification tab.

Step 5   Click the Properties button.

Step 6   In the Computer name field, enter the new host name.

Step 7   Click OK.

Step 8   Click Yes when prompted to reboot the SPE310.

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

---

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

---

Updating Microsoft SQL Server with the New Host Name

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

Complete the following procedures:

Running Microsoft SQL Server Setup

Follow these steps:

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

Step 3   On the SPE310, use Windows Explorer to navigate to D:\Microsoft\SQLServer. (D: is the CD-ROM drive.)

Step 4   Double-click setup.bat.

The Select Install Method window appears.

Step 5   Choose Local Install.

Step 6   Click Next.

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

Step 8   When Setup is complete, click Finish.

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

The Services window appears.

Step 10   Right-click MSSQLServer and choose Start.

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

Updating the Internal Server Name with Query Analyzer

Follow these steps:

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

Step 2   Choose File > Connect.

Step 3   In the SQL Server drop-down list, enter the new host name.

Step 4   Click the Use Windows authentication radio button.

Step 5   Click OK.

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

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

Step 8   Press F5.

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

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

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

Updating the Server List in SQL Server Enterprise Manager

Follow these steps:

The SQL Server Enterprise Manager window appears.

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

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

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

Step 5   Click OK.

Step 6   Click Close.

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

Adding the New SQL Server Login in SQL Server Enterprise Manager

Follow these steps:

The SQL Server Enterprise Manager window appears.

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

Step 3   Choose Logins.

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

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

The SQL Server Login Properties - New Login dialog appears.

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

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

Step 8   Click the Database Access tab.

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

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

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

Step 12   Click OK.

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

Backing Up System Data

This section explains how to back up SPE310 registry settings, ICS System Manager database records, and IOS configuration files for ASIs and 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   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, refer to Backing Up and Restoring Cisco CallManager 3.1.

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 2   Click the System Maintenance tab.

The Backup History page appears.

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 MRP and ASI cards that do not have Flash memory (MRP200, ASI160, ASI81). No configuration files for Flash-based cards will be backed up (MRP300, MRP3-8FXS, MRP3-16FXS). Flash-based cards must be backed up manually.

Step 2   Click Schedule Backup.

Step 3   Enter the required information in the following fields:

---

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

---

Step 4   Under Occurrence, click the appropriate radio button:

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

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 2   Click Backup Now.

Step 3   Enter the required information in the following fields:

---

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

---

---

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 card (MRP300, MRP3-8FXS, MRP3-16FXS).

---

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.

---

---

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.

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

Setting Security Privileges

To ensure that only persons with proper authorization have access to sensitive information, you can designate system passwords during initial configuration of ICS System Manager.

Note   For additional information, refer to the ICS System Manager Online Help.

Shutting Down the System

This section describes how to shut down the system.

Caution   If your system has only one SPE310, make sure that the system data has been backed up before you remove an operational SPE310. For instructions on backing up system data, see the "Backing Up System Data" section.

Follow these steps to shut down the system:

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

Step 3   Click OK.

The system discovers the cards that are currently installed in the chassis. After the discovery process is complete, the ICS 7700 System Configuration page displays.

Step 4   Click Shutdown/Restart.

The Restart/Shutdown System Cards page appears.

Step 5   On the Restart/Shutdown System Cards page, click the Shutdown button next to any SPE310 that is not running System Manager.

Step 6   Click OK to confirm that you want to shut down that SPE310.

The STATUS LED on the target SPE310 blinks. When the STATUS LED turns off, the SPE310 is shut down.

Step 7   Click the Back button to return to the Restart/Shutdown System Cards page.

Step 8   Repeat Step 5 through Step 7 for any additional SPE310s that are not running System Manager.

Step 9   Repeat Step 5 through Step 7 for the SPE310 running System Manager.

Step 10   Click the Back button to return to the Restart/Shutdown System Cards page.

Step 11   Click the Shutdown ICS 7700 System button.

Step 12   Press the power switch to off (o) on the power supply modules.

The LEDs on all the other cards will turn off and the fans will stop.