Nortel CallPilot 703t Installation And Configuration Manual
Nortel CallPilot 703t Installation And Configuration Manual

Nortel CallPilot 703t Installation And Configuration Manual

Maintenance and diagnostics
Hide thumbs Also See for CallPilot 703t:
Table of Contents

Advertisement

Quick Links

555-7101-227
555-7101-227
CallPilot
Installation and Configuration
Part 5: 703t Server Maintenance and Diagnostics
Product release 2.02
Standard 1.0
October 2003

Advertisement

Table of Contents
loading

Summary of Contents for Nortel CallPilot 703t

  • Page 1 555-7101-227 555-7101-227 CallPilot Installation and Configuration Part 5: 703t Server Maintenance and Diagnostics Product release 2.02 Standard 1.0 October 2003...
  • Page 2 P0603582...
  • Page 3 The process of transmitting data and call messaging between the CallPilot server and the switch or system is proprietary to Nortel Networks. Any other use of the data and the transmission process is a violation of the user license unless specifically authorized in writing by Nortel Networks prior to such use.
  • Page 4 *Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks, BNR, CallPilot, DMS, DMS-100, DMS-250, DMS-MTX, DMS-SCP, DPN, Dualmode, Helmsman, IVR, MAP, Meridian, Meridian 1, Meridian Link, Meridian Mail, Norstar, SL-1, SL-100, Succession, Supernode, Symposium, Telesis, and Unity are trademarks of Nortel Networks.
  • Page 5 RADISYS is a trademark of Radisys Corporation. ROLM is a trademark of Siemens ROLM Communications Inc. SLR4, SLR5, and TANDBERG are trademarks of Tandberg Data ASA. SONY is a trademark of Sony Corporation. SYBASE is a trademark of Sybase, Inc. TEAC is a trademark of TEAC Corporation UNIX is a trademark of X/Open Company Limited.
  • Page 6 Publication history Standard 1.0 CallPilot...
  • Page 7 October 2003 Publication history Publication history October 2003 Standard 1.0 of the CallPilot Installation and Configuration, Part 5: 703t Server Maintenance and Diagnostics is issued for general release. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 8 Publication history Standard 1.0 viii CallPilot...
  • Page 9: Table Of Contents

    Contents About this guide Maintenance and diagnostics overview ......14 Resolving system problems ........16 Replacing hardware components .
  • Page 10 Contents Standard 1.0 Using CallPilot Manager to monitor hardware Understanding fault management ....... . 86 Section A: Tools for isolating and fixing hardware problems Overview.
  • Page 11 October 2003 Contents Replacing a rear system fan ........170 Replacing the processor fan .
  • Page 12 Contents Standard 1.0 Working with the CallPilot server BIOS Overview..........276 BIOS settings .
  • Page 13: About This Guide

    C h a p t e r 1 About this guide In this chapter Maintenance and diagnostics overview Resolving system problems Replacing hardware components Part 5: 703t Server Maintenance and Diagnostics...
  • Page 14: Maintenance And Diagnostics Overview

    About this guide Standard 1.0 Maintenance and diagnostics overview Introduction The maintenance and diagnostic activities discussed in this guide are divided into two groups of activities: troubleshooting and diagnostics (identifying the cause of and resolving system problems) hardware maintenance Who should read this guide This guide is for administrators, technicians, and engineers responsible for maintaining a CallPilot server.
  • Page 15 October 2003 About this guide CallPilot Troubleshooting Reference Note: Nortel Networks continually updates the CallPilot Troubleshooting Reference document. You can obtain the latest version from the Partner Information Center (PIC) at http://my.nortelnetworks.com. For more details, see “Resolving system problems” on page 16.
  • Page 16: Resolving System Problems

    About this guide Standard 1.0 Resolving system problems Introduction Chapters 2 to 6 in this guide describe how to use a variety of CallPilot resources for resolving system problems. If you are not able to resolve your problem with the resources described in this guide, you can also refer to the following documents: CallPilot Administrator’s Guide (NTP 555-7101-301) CallPilot Troubleshooting Reference...
  • Page 17 You can obtain the latest version from the Nortel Networks Partner Information Center (PIC) at http://my.nortelnetworks.com. Note: If you are not a Nortel Networks distributor, then contact your Nortel Networks technical support representative for assistance. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 18 About this guide Standard 1.0 Use the CallPilot Troubleshooting Reference to resolve the following types of problems: server boot cycle failures peripheral device problems monitor display problems server to network connection problems remote access connection problems CallPilot application problems CallPilot...
  • Page 19: Replacing Hardware Components

    October 2003 About this guide Replacing hardware components Introduction This guide describes how to replace or install hardware components as follows: To replace or install the server cover Chapter 7, “Replacing basic chassis components” upper fan holder foam cooling fans a hard drive Chapter 8, “Replacing media drives”...
  • Page 20 About this guide Standard 1.0 Approved replacement parts Before replacing any parts on your server, refer to the Nortel Networks product catalog for the part codes. CAUTION Risk of system damage The use of parts that are not approved by Nortel Networks can cause serious system problems or void your Nortel Networks warranty.
  • Page 21: Troubleshooting Your Callpilot System

    C h a p t e r 2 Troubleshooting your CallPilot system In this chapter Overview Interpreting front panel LEDs Interpreting rear panel LEDs Interpreting internal LEDs Interpreting POST diagnostics SCSI controller diagnostics RAID controller diagnostics What to do when the server fails to boot into service Viewing the System Event Log Part 5: 703t Server Maintenance and Diagnostics...
  • Page 22: Overview

    See “Using the CallPilot Administrator’s Guide” on page 17 for more details. CallPilot Troubleshooting Reference Nortel Networks continually updates the CallPilot Troubleshooting Reference document. You can obtain the latest version from the Nortel Networks Partner Information Center (PIC) at http://my.nortelnetworks.com. CallPilot...
  • Page 23: Interpreting Front Panel Leds

    October 2003 Troubleshooting your CallPilot system Interpreting front panel LEDs Introduction This section describes LED states visible on the 703t server front panel. LED locations The following diagram shows where the LEDs are located: CD-ROM drive LED Network LEDs Tape drive Status LEDs LEDs Floppy disk...
  • Page 24 Troubleshooting your CallPilot system Standard 1.0 The server LEDs, from top to bottom and left to right, indicate the status of the following: the CLAN and ELAN network interfaces hard drive power/sleep system LEDs are also provided on the SCSI tape drive faceplate, floppy disk drive faceplate, and the IDE CD-ROM drive faceplate.
  • Page 25 October 2003 Troubleshooting your CallPilot system IF the network interface LED is THEN a valid hardware connection with the network has been established. Note: Before the 703t server can receive or transmit data, you must configure valid IP settings on the 703t server. blinking rapidly activity is occurring on the network.
  • Page 26 Troubleshooting your CallPilot system Standard 1.0 Power/sleep LED states The power/sleep LED is the middle LED in the row of LEDs below the power button on the 703t server’s front panel (see “Status LEDs” in the diagram on page 23). It is green. IF the power/sleep status LED is THEN...
  • Page 27 October 2003 Troubleshooting your CallPilot system IF the system status LED is THEN amber steady a critical temperature or voltage fault has occurred the CPU is not installed or is not functioning blinking a power fault has occurred a fan is faulty a non-critical temperature or voltage fault has occurred a fatal error occurred during the...
  • Page 28 Tape is loaded and moving Tape is loading or unloading Cartridge is ejecting Blinking Cleaning is in progress Blinking Unrecoverable tape drive failure Cartridge failure Microcode download failure Note: If the LED states indicate an error, contact your Nortel Networks technical support representative. CallPilot...
  • Page 29 October 2003 Troubleshooting your CallPilot system CD-ROM drive LED states The CD-ROM drive’s status LED is located on the drive’s front panel. Refer to the following table when interpreting the CD-ROM drive’s status: IF the CD-ROM drive LED is THEN the CD-ROM drive is idle.
  • Page 30: Interpreting Rear Panel Leds

    Troubleshooting your CallPilot system Standard 1.0 Interpreting rear panel LEDs Introduction This section describes LED states visible at the back of the 703t server. MPB96 DS30 connection link LED states Refer to “Slot definition and numbering” on page 300 for the slot position of the MPB96 boards in your server.
  • Page 31: Interpreting Internal Leds

    October 2003 Troubleshooting your CallPilot system Interpreting internal LEDs Introduction This section describes LED states visible inside of the 703t server cabinet. MPB96 LED states There are three LEDs on the top of the MPB96 board. They are visible even from outside the server cabinet, through the rear grill.
  • Page 32 Troubleshooting your CallPilot system Standard 1.0 RAID controller LED states Refer to “Slot definition and numbering” on page 300 for the slot position of the RAID boards in your server. There is one red LED and a row of eight small LED's at the back of the RAID board.
  • Page 33: Interpreting Post Diagnostics

    POST emits beep codes that indicate errors in hardware, software, or firmware. A beep code is a series of separate tones, each equal in length. Record the beep codes that you hear before calling your Nortel Networks customer support representative. ATTENTION Some POST beep codes are critical and require you to replace your motherboard.
  • Page 34 Troubleshooting your CallPilot system Standard 1.0 BIOS recovery beep codes Beeps Error message Description Recovery Start recovery process. started Recovery Unable to boot from floppy disk boot error drive or CD-ROM drive. Recovery process will retry. Series of Recovery Unable to process valid BIOS low-pitched failed recovery images.
  • Page 35 October 2003 Troubleshooting your CallPilot system Number of beeps Error message Error message and conditions Processor Processor faulty Failure Keyboard Gate Keyboard may be bad A20 Failure Processor Processor generated an exception Exception Int interrupt error Display Memory Video adapter is missing or faulty. Read/Write Error This is not a fatal error.
  • Page 36 Troubleshooting your CallPilot system Standard 1.0 Number of beeps POST code Expansion card/controller Mismatched DIMMs in a row Base memory test failure Failure in decompressing post module 07-0Dh Generic memory error SMBus protocol error Generic memory error CPU microcode cannot be found for processor in slot 0 CPU microcode cannot be found for processor in slot 1...
  • Page 37: Scsi Controller Diagnostics

    October 2003 Troubleshooting your CallPilot system SCSI controller diagnostics BIOS initialization Most information about SCSI is displayed as part of the BIOS initialization screen. During BIOS initialization you should check to make sure that the tape drive is listed correctly. If the tape drive is not listed correctly: Ensure that internal cable connections are made properly.
  • Page 38: Raid Controller Diagnostics

    Troubleshooting your CallPilot system Standard 1.0 RAID controller diagnostics Most diagnostic information about RAID is available through beep warnings and status LEDs when the server is rebooting. For more information refer to: “Hard drive LED states” on page 25 “RAID controller LED states” on page 32 “When the 703t server does not boot and makes audible beeps”...
  • Page 39: What To Do When The Server Fails To Boot Into Service

    Nortel Networks Partner Information Center web site at http://www.my.nortelnetworks.com. Note: If you are not a distributor, contact your Nortel Networks technical support representative for assistance. 7 If you still cannot find the cause of the boot failure after performing the tasks described in the following sections, call your Nortel Networks technical support representative.
  • Page 40 1 Shut down the 703t server 2 Disconnect the power cable. 3 Wait one minute. 4 Reconnect the power cable and attempt to restart the 703t server. 5 If the problem continues, contact your Nortel Networks technical support representative for assistance. CallPilot...
  • Page 41 October 2003 Troubleshooting your CallPilot system When the 703t server does not boot and makes audible beeps If beeps are short If the beeps are short in length they are from the system board. Typically, you will not see any video displayed on the monitor, and the right- most status LED on the front of the 703t server will show a blinking or steady amber.
  • Page 42 Troubleshooting your CallPilot system Standard 1.0 When the 703t server boots to Windows NT and makes audible beeps If the 703t server boots to the Windows NT operating system but still makes audible beeps, one of the hard drives is in critical condition. 1 Rebuild the hard drive as soon as Windows NT has finished loading.
  • Page 43: Viewing The System Event Log

    Since mouse support is not available when using the SSU, it is difficult to navigate through the contents of the System Event Log. Nortel Networks recommends therefore, that you save the log to a file on floppy disk and then review it in a text editor, such as Notepad.
  • Page 44 Troubleshooting your CallPilot system Standard 1.0 The system continues with the SCSI and RAID startup diagnostics, and when done, the following menu appears: Please select boot device: ATAPI CD-ROM Removable Devices Hard Drive IBA 4.1.0.4 Slot 0118 IBA GE Slot 0120 v1109 Use <arrow up>...
  • Page 45 October 2003 Troubleshooting your CallPilot system 6 Choose option 7, 703t SSU. Result: The System Setup Utility window appears. Notes: You may have a later version of the SSU. The menus can differ slightly, but the steps are the same. The left column describes the Available Tasks, and the right column provides help on the highlighted task.
  • Page 46 Troubleshooting your CallPilot system Standard 1.0 10 Press the down arrow to choose Save As. 11 In the dialog box that appears, type a name for the file. Note: The file name should contain no more than 8 characters plus the 3 character extension.
  • Page 47 October 2003 Troubleshooting your CallPilot system 18 Press the down arrow to choose Exit, and then press Enter. Result: The System Setup Utility window appears. 19 Press Alt+F to display the File menu. 20 Press Enter to Exit. Result: The following message appears: Are you sure you want to exit the SSU? 21 Press Enter (to activate OK).
  • Page 48 Troubleshooting your CallPilot system Standard 1.0 CallPilot...
  • Page 49: Using Windows Nt Online Diagnostic Tools

    C h a p t e r 3 Using Windows NT online diagnostic tools In this chapter Overview Viewing event logs Checking hardware using Windows NT Diagnostics Using TCP/IP diagnostic tools Invoking the chkdsk utility Part 5: 703t Server Maintenance and Diagnostics...
  • Page 50: Overview

    Using Windows NT online diagnostic tools Standard 1.0 Overview Introduction This section describes how to access the run-time online diagnostic tools provided by the Windows NT server software. Use these tools when a serious problem prevents the use of the CallPilot diagnostic tools that are available in CallPilot Manager.
  • Page 51 October 2003 Using Windows NT online diagnostic tools nbtstat netstat These utilities help you to verify network connectivity. They help you to thoroughly test the network interface and isolate any configuration problems. Network connectivity is essential to CallPilot operation. chkdsk utility The chkdsk utility checks a specified disk on the server and displays a status report.
  • Page 52: Viewing Event Logs

    Using Windows NT online diagnostic tools Standard 1.0 Viewing event logs Introduction When the server startup cycle is complete, and if the CallPilot server has been configured (refer to Part 3 of the CallPilot Installation and Configuration binder), messages in dialog boxes on the monitor indicate that CallPilot is ready to accept calls.
  • Page 53 October 2003 Using Windows NT online diagnostic tools Log type Description Security Logs security events, such as logons, logoffs and illegal access. This option is available only to users with Administrative access. Applications Logs events by application, such as database file errors.
  • Page 54 Using Windows NT online diagnostic tools Standard 1.0 To use the Windows NT Event Viewer 1 Click Start Programs Administrative Tools (Common) Event Viewer. Result: The Event Viewer window appears. Note: The System Log appears by default. CallPilot...
  • Page 55 October 2003 Using Windows NT online diagnostic tools 2 To view the Application Log, click Log Application. Result: The Application Log similar to the following window appears: 3 Look for error codes flagged with that have occurred since the last startup. Note: Each error is date and time stamped.
  • Page 56 Application Log: 5 Use the description to help determine how to resolve errors. Note: If the error persists or does not suggest a solution, contact your Nortel Networks support representative. 6 Click Close. Result: The event log reappears.
  • Page 57: Checking Hardware Using Windows Nt Diagnostics

    October 2003 Using Windows NT online diagnostic tools Checking hardware using Windows NT Diagnostics Introduction The Windows NT 4.0 Diagnostics window allows you to view details about the system and network components. To use the Windows NT 4.0 Diagnostics tool 1 Log on to Windows NT.
  • Page 58 Using Windows NT online diagnostic tools Standard 1.0 3 Click the appropriate tab to view information concerning the system and network. The following table identifies the types of details available on each tab: Select To display details about Version Windows NT version Registration information System System identifier...
  • Page 59 October 2003 Using Windows NT online diagnostic tools Select To display details about Resources Click one of the following buttons to display information about the resources available on the system: I/O Port Memory Devices To view specific details, select a resource, and then click Properties.
  • Page 60: Using Tcp/Ip Diagnostic Tools

    Using Windows NT online diagnostic tools Standard 1.0 Using TCP/IP diagnostic tools Introduction This section describes the following TCP/IP diagnostic tools available for the network adapter. These tools are useful for diagnosing LAN communication problems. The first three tools are the most useful: ipconfig (below) ping (page 62) tracert (page 63)
  • Page 61 October 2003 Using Windows NT online diagnostic tools The following flags are available for the ipconfig command: Flag Description Displays Help information. /all Displays full configuration information. /release Releases the IP address for the specified adapter. /renew Renews the IP address for the specified adapter. To run the ipconfig command from Windows NT 4.0 1 Click Start Programs...
  • Page 62 Using Windows NT online diagnostic tools Standard 1.0 The ping command The ping command sends an echo request to a specified host. Use this command to verify network connectivity to the remote device. Ping command syntax The ping command uses the following syntax: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS] [-r count] [-s count] [[-j host-list] | [-k host-list]]...
  • Page 63 October 2003 Using Windows NT online diagnostic tools To run the ping command from Windows NT 4.0 1 Click Start Programs Command Prompt to display the MS-DOS command prompt window. Result: The MS-DOS Command Prompt window appears. 2 At the MS-DOS prompt, type ping <destination IP address> (for example, ping 200.286.32.0), or ping <computer name>...
  • Page 64 Using Windows NT online diagnostic tools Standard 1.0 Tracert parameters The tracert command uses the following parameters: Parameter Description Specifies not to resolve addresses to hostnames. -h maximum_hops Specifies the maximum number of hops to search for the target. -j host-list Specifies a loose source route along the host list.
  • Page 65 October 2003 Using Windows NT online diagnostic tools The arp command The arp command displays and modifies the IP-to-physical address translation tables used by Address Resolution Protocol (arp). Arp command syntax The arp command uses the following syntax: arp -s inet_addr eth_addr [if_addr] arp -d inet_addr [if_addr] arp -a [inet_addr] [-N if_addr] Parameter...
  • Page 66 Using Windows NT online diagnostic tools Standard 1.0 Parameter Description Adds the host and associates the Internet address inet_addr with the Physical address eth_addr. The physical address is given as six hexadecimal bytes separated by hyphens. The entry is permanent. To run the arp command from Windows NT 4.0 1 Click Start Programs...
  • Page 67 October 2003 Using Windows NT online diagnostic tools Parameter Description -A IP address Lists the remote computer’s name table using its IP address. Lists the contents of the NetBIOS name cache giving the IP address of each name. Lists local NetBIOS names. Registered indicates that the name is registered by broadcast (Bnode) or WINS (other node types).
  • Page 68 Using Windows NT online diagnostic tools Standard 1.0 To run the nbtstat command from Windows NT 4.0 1 Click Start Programs Command Prompt to display the MS-DOS command prompt window. Result: The MS-DOS Command Prompt window appears. 2 At the MS-DOS prompt, type nbtstat with the required parameters. 3 Press Enter.
  • Page 69 October 2003 Using Windows NT online diagnostic tools -p proto Shows connections for the protocol specified by proto. Proto can be tcp or udp. If used with the -s option, proto can be tcp, udp, or ip. Displays the contents of the routing table. interval Redisplays selected statistics, pausing between each display.
  • Page 70: Invoking The Chkdsk Utility

    Using Windows NT online diagnostic tools Standard 1.0 Invoking the chkdsk utility Introduction The chkdsk utility checks a specified disk on the server and displays a status report. It can be run on drives C, D, E, or F. It is an online utility, but it reduces system performance while it is running.
  • Page 71 October 2003 Using Windows NT online diagnostic tools To run the chkdsk utility from Windows NT 4.0 1 Click Start Programs Command Prompt to display the MS-DOS command prompt window. Result: The MS-DOS Command Prompt window appears. 2 At the MS-DOS prompt, type chkdsk <drive letter:> (for example, chkdsk c:).
  • Page 72 Using Windows NT online diagnostic tools Standard 1.0 CallPilot...
  • Page 73: Using Serial Port Diagnostic Tools

    C h a p t e r 4 Using serial port diagnostic tools In this chapter Overview Shutting down services Conducting TSTSERIO tests Conducting TSTSERIO tests with the loopback plug Restarting services Part 5: 703t Server Maintenance and Diagnostics...
  • Page 74: Overview

    Using serial port diagnostic tools Standard 1.0 Overview Introduction You may want to test the serial ports when remote access does not work. This chapter describes how to run serial port diagnostics on the CallPilot server using the TSTSERIO command. Direct the TSTSERIO command to serial ports on the server after services on these ports have been shut down manually, as described in this chapter.
  • Page 75: Shutting Down Services

    October 2003 Using serial port diagnostic tools Shutting down services Introduction This section describes how to shut down a service using a specific serial port. Use the procedures below before invoking the TSTSERIO local loopback tests. CAUTION Risk of communications loss By stopping the services on COM 1 or COM 2, you lose the support access feature.
  • Page 76 Using serial port diagnostic tools Standard 1.0 CallPilot Call Channel Router CallPilot Time Service Remote Access Server Net Stop command Use the Net Stop command to stop a specified service on a serial port. Net Stop command syntax The Net Stop command uses the following syntax: net stop “service_name”...
  • Page 77: Conducting Tstserio Tests

    October 2003 Using serial port diagnostic tools Conducting TSTSERIO tests Introduction The TSTSERIO command performs local loopback tests of the serial communication ports from the server run-time environment. Note: Before conducting these tests, shut down the appropriate services. See “Shutting down services” on page 75. CAUTION Risk of communications loss By stopping the services on COM 1 or COM 2, you lose the...
  • Page 78 Using serial port diagnostic tools Standard 1.0 Flag Requirement Description /S:subtstname Optional Specifies a TSTSERIO subtest. See the table below for a description of the available subtests. /L:loops Optional Specifies the number of times (up to a maximum of 65 535) to execute the requested test.
  • Page 79 October 2003 Using serial port diagnostic tools To invoke the TSTSERIO /P command from Windows NT 4.0 1 Click Start Programs Command Prompt to display the MS-DOS command prompt window. Result: The MS-DOS Command Prompt window appears. 2 At the MS-DOS prompt, type tstserio with the required parameters, and then press Enter.
  • Page 80 Using serial port diagnostic tools Standard 1.0 To invoke the TSTSERIO /S command from Windows NT 4.0 1 Click Start Programs Command Prompt to display the MS-DOS command prompt window. Result: The MS-DOS Command Prompt window appears. 2 At the MS-DOS prompt, type tstserio with the required parameters, and then press Enter.
  • Page 81: Conducting Tstserio Tests With The Loopback Plug

    October 2003 Using serial port diagnostic tools Conducting TSTSERIO tests with the loopback plug Introduction The TSTSERIO command requires an external loopback connector plug for its edata, emsr, and eint subtests. 9-pin connector plug The standard serial loopback connector is a female 9-pin D-sub connector. This connector has the following pins wired together: CTS (pin 8) wired to (pin 7) RTS SIN (pin 2) wired to (pin 3) SOUT...
  • Page 82: Restarting Services

    Using serial port diagnostic tools Standard 1.0 Restarting services Introduction This section describes how to restart the services for COM 1 or COM 2 after invoking the TSTSERIO local loopback tests. Service to restart after COM 1 testing Remote Access Server Services to restart after COM 2 testing CallPilot SLEE Service CallPilot MWI Service...
  • Page 83 October 2003 Using serial port diagnostic tools To invoke the Net Start command from Windows NT 4.0 1 Click Start Programs Command Prompt. Result: The MS-DOS Command Prompt window appears. 2 At the MS-DOS prompt, type net start “ service_name ”, and then press Enter.
  • Page 84 Using serial port diagnostic tools Standard 1.0 CallPilot...
  • Page 85: Using Callpilot Manager To Monitor Hardware

    C h a p t e r 5 Using CallPilot Manager to monitor hardware In this chapter Understanding fault management Section A: Tools for isolating and fixing hardware problems Overview Alarm Monitor Event Browser Maintenance page Channel and Multimedia Monitors Section B: Working with the Maintenance page Introducing the Maintenance page Viewing component states...
  • Page 86: Understanding Fault Management

    Using CallPilot Manager to monitor hardware Standard 1.0 Understanding fault management Introduction Fault management is a term that describes how the CallPilot server detects and notifies you of potential or real hardware problems (faults). The server processes events to detect hardware problems and raises alarms to notify you when these problems occur.
  • Page 87: Section A: Tools For Isolating And Fixing Hardware Problems

    October 2003 Using CallPilot Manager to monitor hardware Section A: Tools for isolating and fixing hardware problems In this section Overview Alarm Monitor Event Browser Maintenance page Channel and Multimedia Monitors Part 5: 703t Server Maintenance and Diagnostics...
  • Page 88: Overview

    Using CallPilot Manager to monitor hardware Standard 1.0 Overview Introduction This section provides guidelines on how to use the CallPilot Manager tools to detect, isolate, and fix potential or real hardware problems. Component dependencies The status of some components are dependent on the operational status of other components.
  • Page 89 October 2003 Using CallPilot Manager to monitor hardware Other indications of a hardware problem include the following: user complaints call processing difficulties, such as busy signals, static, dropped calls, connection problems, and cross talk (hearing other conversations) system administrator logon difficulties alert icons on the Maintenance page Part 5: 703t Server Maintenance and Diagnostics...
  • Page 90: Alarm Monitor

    Using CallPilot Manager to monitor hardware Standard 1.0 Alarm Monitor Introduction Use the Alarm Monitor to investigate one or more raised alarms. About alarms Alarms are warnings generated by events. Alarms communicate the same information as events. However, alarms are reported in the Alarm Monitor instead of the Event Browser, and are managed differently than events: Alarms appear in the Alarm Monitor only for Minor, Major, and Critical events (not Information events).
  • Page 91 October 2003 Using CallPilot Manager to monitor hardware To investigate using the Alarm Monitor 1 In CallPilot Manager, click System Alarm Monitor. Result: The Alarm Monitor window appears. 2 Click the Event Code for the first critical or major alarm. Result: A description of the event appears in a new web browser window.
  • Page 92 Using CallPilot Manager to monitor hardware Standard 1.0 See also For detailed information on how to use the Alarm Monitor, refer to the CallPilot Administrator’s Guide (NTP 555-7101-301), or the CallPilot Manager online Help. CallPilot...
  • Page 93: Event Browser

    Events are classified as Information, Minor, Major, or Critical. By default, the Event Browser displays only the latest 100 critical events. Note: Nortel Networks recommends that you change the Event Browser filter criteria to display Minor and Major events as well. Minor and Major events can indicate significant system problems.
  • Page 94 Result: A description of the event appears in a new web browser window. 3 View the description and recovery action. 4 Repeat steps 2 and 3 for a few more events, if necessary. 5 If the solution to the problem is not apparent, contact your Nortel Networks technical support representative. CallPilot...
  • Page 95 October 2003 Using CallPilot Manager to monitor hardware See also For detailed information on how to use the Event Browser (for example, how to set preferences), refer to the CallPilot Administrator’s Guide (NTP 555-7101-301), or the CallPilot Manager online Help. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 96: Maintenance Page

    Using CallPilot Manager to monitor hardware Standard 1.0 Maintenance page Introduction Use the Maintenance page to get status information for any suspect components. If you suspect or discover a problem with hardware such as an MPC, MPB board, or the DS30X link, you can use the Diagnostic section on the Maintenance page.
  • Page 97: Channel And Multimedia Monitors

    Disabling call channels If you must take the CallPilot system out of service to perform software or hardware maintenance, Nortel Networks recommends that you disable all call channels first. There are two ways to disable the call channels: Courtesy stop the channels (preferred method).
  • Page 98 Using CallPilot Manager to monitor hardware Standard 1.0 CallPilot...
  • Page 99: Section B: Working With The Maintenance Page

    October 2003 Using CallPilot Manager to monitor hardware Section B: Working with the Maintenance page In this section Introducing the Maintenance page Viewing component states Starting and stopping components Running integrated diagnostics Viewing the last diagnostic results Part 5: 703t Server Maintenance and Diagnostics...
  • Page 100: Introducing The Maintenance Page

    Using CallPilot Manager to monitor hardware Standard 1.0 Introducing the Maintenance page Introduction Use the Maintenance page in CallPilot Manager to do the following: Obtain general information about components. View component states. Start and stop components. Run integrated diagnostic tests. View the results of the last diagnostic test run against a component.
  • Page 101 October 2003 Using CallPilot Manager to monitor hardware The Maintenance page identifies the server platform and switch connectivity type. The following is an example of a partially expanded tree for the 703t server: The Maintenance page also provides a tree that, when expanded, lists the physical and logical hardware components down the left side of the page.
  • Page 102 Using CallPilot Manager to monitor hardware Standard 1.0 When you click a component, the page refreshes to show the details about that component. Details are divided into the sections described in the following table: Section Description General This section shows general technical information about the selected component.
  • Page 103 October 2003 Using CallPilot Manager to monitor hardware Section Description Diagnostics Use the Diagnostics section to run one or more diagnostic tests, or to view the results of the last diagnostic tests that were run on the selected component. This section appears only for components on which you are allowed to run diagnostics.
  • Page 104 Using CallPilot Manager to monitor hardware Standard 1.0 Maintenance activities for each component The following table identifies the maintenance activities you can perform for each component that is listed in the component tree: Start, stop, or Diagnostics Component courtesy stop? available? Replaceable? Media Bus...
  • Page 105: Viewing Component States

    October 2003 Using CallPilot Manager to monitor hardware Viewing component states Introduction View a component’s state to determine the general condition of the component, including whether the component is disabled or off duty. The component’s state is shown in the Maintenance section of the Maintenance page.
  • Page 106 Using CallPilot Manager to monitor hardware Standard 1.0 State Description Not Configured The component is not configured in CallPilot. For example, a DSP is not being used because it was not allocated in the Configuration Wizard. Off Duty The component has been stopped. Remote Off Duty The component has been taken out of service at the switch.
  • Page 107 October 2003 Using CallPilot Manager to monitor hardware To view the state of a hardware component 1 In CallPilot Manager, click Maintenance Maintenance Admin. Result: The Maintenance page appears. 2 Click the plus sign (+) beside the CallPilot server to expand the component tree.
  • Page 108: Starting And Stopping Components

    Start and stop components from the Maintenance section on the Maintenance page. ATTENTION Nortel Networks recommends that, if possible, you courtesy stop a component. Courtesy stop is available only at the individual channel level. To courtesy down CallPilot, use the following:...
  • Page 109 October 2003 Using CallPilot Manager to monitor hardware If the component is currently processing a call, the call is not dropped; the component remains active until the call is finished. If the component is not currently in use, it is taken out of service immediately.
  • Page 110 Using CallPilot Manager to monitor hardware Standard 1.0 Component Effect of stopping Media Channel Takes the selected Media Channels out of service. DS30X link Takes the selected DS30X link and the channels that belong to that link out of service. Channels Takes the selected DS30X channel out of service.
  • Page 111 October 2003 Using CallPilot Manager to monitor hardware 6 Click Courtesy Stop, Stop, or Start, as required. Button Description Start If the selected component is out of service, click this button to put it into service. Courtesy Click this button to take the selected component out of Stop service.
  • Page 112: Running Integrated Diagnostics

    Using CallPilot Manager to monitor hardware Standard 1.0 Running integrated diagnostics Introduction You should run diagnostic tests from the Diagnostics section on the Maintenance page in the following circumstances: You want to ensure that a component is operating properly after installing or reinstalling it.
  • Page 113 (such as the Time Switch), you must either replace its parent component or contact your Nortel Networks technical support representative, depending on the component.
  • Page 114 Using CallPilot Manager to monitor hardware Standard 1.0 To run a diagnostic test ATTENTION Nortel Networks recommends that you courtesy stop rather than stop a component if possible. For instructions, see “Starting and stopping components” on page 108. 1 In CallPilot Manager, click Maintenance Maintenance Admin.
  • Page 115 October 2003 Using CallPilot Manager to monitor hardware 6 Scroll down to the Diagnostics section. Result: The following is an example of the Diagnostics section for an MPC: 7 Check the check box for each diagnostic that you want to run. Note: If you want to run all of the diagnostics, check the Diagnostic Description check box at the top of the list.
  • Page 116 Using CallPilot Manager to monitor hardware Standard 1.0 8 Click Run. Result: A new web browser window opens to display the progress and results of the diagnostics: Note: The Diagnostic Results box in the Diagnostics section displays diagnostic results when you click Get Last Result. CallPilot...
  • Page 117: Viewing The Last Diagnostic Results

    Last Results button for a component. To view the last diagnostics result ATTENTION Nortel Networks recommends that you courtesy stop rather than stop a component if possible. For instructions, see “Starting and stopping components” on page 108. 1 In CallPilot Manager, click Maintenance Maintenance Admin.
  • Page 118 Using CallPilot Manager to monitor hardware Standard 1.0 5 Scroll down to the Diagnostics section. Result: The following is an example of the Diagnostics section for an MPC: 6 Check the check box for each diagnostic for which you want to review results.
  • Page 119 October 2003 Using CallPilot Manager to monitor hardware 7 Click Get Last Result. Result: The results appear in the Diagnostic Results box. Last diagnostic results The results of the last diagnostic test display the following information in the Diagnostic Results box: diagnostic title diagnostic result: pass or fail the date and time the test was completed...
  • Page 120 Using CallPilot Manager to monitor hardware Standard 1.0 CallPilot...
  • Page 121: Section C: Working With The Multimedia And Channel Monitors

    October 2003 Using CallPilot Manager to monitor hardware Section C: Working with the Multimedia and Channel Monitors In this section Working with the Multimedia Monitor Working with the Channel Monitor Part 5: 703t Server Maintenance and Diagnostics...
  • Page 122: Working With The Multimedia Monitor

    Using CallPilot Manager to monitor hardware Standard 1.0 Working with the Multimedia Monitor Introduction The Multimedia Monitor shows the status of multimedia channels. The multimedia channels are the DSP ports that process the calls. They are the voice, fax, and speech recognition channels. To view or work with multimedia channel states 1 In CallPilot Manager, click Maintenance Multimedia Monitor.
  • Page 123 October 2003 Using CallPilot Manager to monitor hardware Note: For an explanation of the channel states, refer to the CallPilot Manager online Help. 2 Do one of the following: IF you want to stop or start THEN all of the channels check the check box to the left of the associated with a DSP DSP that you want to stop or start.
  • Page 124: Working With The Channel Monitor

    Using CallPilot Manager to monitor hardware Standard 1.0 Working with the Channel Monitor Introduction The Channel Monitor shows the status of call channels. The call channels are the connections between the server and the switch that carry the call signals to CallPilot. To view or work with call channel states 1 In CallPilot Manager, click Maintenance Channel Monitor.
  • Page 125 October 2003 Using CallPilot Manager to monitor hardware 2 Do one of the following: IF you want to stop or start THEN all of the channels check the check box to the left of the associated with a DS30X link that you want to stop or DS30X link start.
  • Page 126 Using CallPilot Manager to monitor hardware Standard 1.0 CallPilot...
  • Page 127: Using Callpilot System Utilities

    C h a p t e r 6 Using CallPilot system utilities In this chapter Overview Diagnostics Tool PEP Maintenance utility Session Trace System Monitor Part 5: 703t Server Maintenance and Diagnostics...
  • Page 128: Overview

    Using CallPilot system utilities Standard 1.0 Overview Introduction The following table lists the CallPilot system utilities: Utility Description Diagnostics Tool Allows CallPilot startup diagnostics to be enabled or disabled (turned on or off). PEP Maintenance Displays a list of installed PEPs and enables PEP uninstall.
  • Page 129: Diagnostics Tool

    October 2003 Using CallPilot system utilities Diagnostics Tool Introduction The Diagnostics Tool allows you to enable or disable CallPilot startup diagnostics. CallPilot startup diagnostics automatically identify hardware problems that may exist when the system and its services are started (MediaBus, MPB board, MPC/DSP).
  • Page 130 Using CallPilot system utilities Standard 1.0 To access the Diagnostics Tool On the Windows desktop, click Start Programs CallPilot System Utilities Diagnostic Tool. Result: The Diagnostics Tool window appears. To enable startup diagnostics From the Diagnostics Tool window, select Configuration Maintenance Startup Diag Enable.
  • Page 131 October 2003 Using CallPilot system utilities To disable startup diagnostics ATTENTION Nortel Networks recommends that you leave the startup diagnostics turned on. When you disable CallPilot startup diagnostics, you prevent CallPilot from automatically identifying hardware problems that may exist when the system and its services are started.
  • Page 132: Pep Maintenance Utility

    Using CallPilot system utilities Standard 1.0 PEP Maintenance utility Introduction The PEP Maintenance utility displays a list of all installed PEPs on the server and enables you to uninstall PEPS. For information on installing or uninstalling PEPs, refer to Part 4 of the CallPilot Installation and Configuration binder.
  • Page 133 October 2003 Using CallPilot system utilities To view a list of all installed PEPs 1 Click the component for which you want to display the PEP list. 2 Click Show PEPs. Result: A list of all installed PEPs appears in the left pane. 3 If you want to review the readme file associated with a PEP, click the PEP, and then click Read.
  • Page 134: Session Trace

    Using CallPilot system utilities Standard 1.0 Session Trace Introduction The Session Trace tool displays detailed information about the activity in a user’s mailbox and the state of the message waiting indicator (MWI). The session information includes voice messaging call answering express messaging activity (messages composed and sent, or left in a mailbox) the number of messages played or unplayed at the beginning, middle,...
  • Page 135 October 2003 Using CallPilot system utilities To access the session trace tool From the Windows desktop, click Start Programs CallPilot System Utilities Session Trace Tool. Result: The MCE Session Trace window appears. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 136 Using CallPilot system utilities Standard 1.0 To find a session 1 From the Session Type drop-down menu, choose the type of session. To display a list of all session types, select All Session Types. 2 Enter as much information in the search criteria boxes to identify the session you want to view.
  • Page 137 October 2003 Using CallPilot system utilities Session type information Call Answering session type information Part 5: 703t Server Maintenance and Diagnostics...
  • Page 138 Using CallPilot system utilities Standard 1.0 Expired messages session type information CallPilot...
  • Page 139 October 2003 Using CallPilot system utilities Express Messaging session type information Part 5: 703t Server Maintenance and Diagnostics...
  • Page 140 Using CallPilot system utilities Standard 1.0 Logon OK session type information CallPilot...
  • Page 141 October 2003 Using CallPilot system utilities Selective Restore session type information Part 5: 703t Server Maintenance and Diagnostics...
  • Page 142: System Monitor

    Using CallPilot system utilities Standard 1.0 System Monitor Introduction The System Monitor consists of three tabs, as described in the table below: Description Channel Monitor Shows the status of all CallPilot services, multimedia channels (DSP channels), and call channels (DS30X channels). System Info Displays particulars about the CallPilot system, such as features purchased, keycode, serial...
  • Page 143 The services listed under Service Name should be either running or in full service when CallPilot is functioning optimally. If any CallPilot services are stopped, investigate the cause of this. If you need assistance, call Nortel Networks technical support. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 144 Using CallPilot system utilities Standard 1.0 Note: While any stopped services should be investigated, some services are not critical. CallPilot may continue to handle call processing even with some services stopped. The critical services that are needed for basic CallPilot call answering are listed in the following table.
  • Page 145 October 2003 Using CallPilot system utilities DSPs In the DSP pane, each DSP is represented in a separate row. Each box in the row is one DSP channel or multimedia channel. Click the Legend/Help tab to view descriptions of the multimedia channel icons. On the 703t server, 12 DSPs are embedded on each MPB96 board.
  • Page 146 Using CallPilot system utilities Standard 1.0 About the System Info tab The following is an example of the System Info tab, followed by a description of its contents: Note: The screen sample above was acquired from a 1001rp server, but provides the same type of information for any CallPilot server model.
  • Page 147 October 2003 Using CallPilot system utilities About the Legend/Help tab The following is an example of the Legend/Help tab. Consult this window for descriptions of the icons found in the Channel Monitor tab: Part 5: 703t Server Maintenance and Diagnostics...
  • Page 148 Using CallPilot system utilities Standard 1.0 CallPilot...
  • Page 149: Replacing Basic Chassis Components

    C h a p t e r 7 Replacing basic chassis components In this chapter Section A: Preparing for hardware maintenance Preparing the server for hardware maintenance Removing the side cover Removing and replacing the upper fan holder foam Replacing the side cover Section B: Replacing fans Cooling fans description Replacing a front system fan...
  • Page 150 Replacing basic chassis components Standard 1.0 CallPilot...
  • Page 151: Section A: Preparing For Hardware Maintenance

    October 2003 Replacing basic chassis components Section A: Preparing for hardware maintenance In this section Preparing the server for hardware maintenance Removing the side cover Removing and replacing the upper fan holder foam Replacing the side cover Part 5: 703t Server Maintenance and Diagnostics...
  • Page 152: Preparing The Server For Hardware Maintenance

    Replacing basic chassis components Standard 1.0 Preparing the server for hardware maintenance Introduction DANGER Risk of electric shock Before you begin working inside the server, do the following: 1 Power off and disconnect all peripheral devices that are connected to the CallPilot server. 2 Power off the server and disconnect the power cord.
  • Page 153 October 2003 Replacing basic chassis components CAUTION Risk of equipment damage Place the server on its side to prevent the server from accidentally falling over. This provides greater stability. If you attempt to work with the server in its standing position, it may tip over when you remove or insert components.
  • Page 154 Replacing basic chassis components Standard 1.0 Power connector PS/2 mouse connector USB connectors (not used) PS/2 keyboard connector Serial port (COM1) Parallel port Monitor connector 10/100/1000Base-T CLAN Ethernet connector (NIC2 1 GB) 10/100Base-T ELAN Ethernet connector (NIC1 10/100 MB) PCI slots Serial port (COM2) (not installed) G101760...
  • Page 155 October 2003 Replacing basic chassis components To remove the chassis feet 1 Place the server on its side. 2 Remove the feet as shown in the above diagram. 3 Continue with “Removing the side cover” on page 156. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 156: Removing The Side Cover

    Replacing basic chassis components Standard 1.0 Removing the side cover Introduction This section describes how to remove the server’s side cover so that you can work with interior components. The side cover is on the left side of the server when the server’s front panel is facing you. To remove the side cover WARNING Risk of personal injury...
  • Page 157 October 2003 Replacing basic chassis components The following diagram shows how to remove the side cover. See the instructions for removal below. G101761 1 Turn the two thumbscrews on the back of the server counter-clockwise to loosen them. Note: The thumbscrews are not removable. If a removable screw is present, remove it.
  • Page 158 Replacing basic chassis components Standard 1.0 3 Use both hands to lift the cover away from the chassis. 4 Set the cover aside. CallPilot...
  • Page 159: Removing And Replacing The Upper Fan Holder Foam

    October 2003 Replacing basic chassis components Removing and replacing the upper fan holder foam Introduction The interior of the server contains two layers of fan holder foam, which secures and stabilizes the cooling fans and add-in boards. The fan holder foam also maintains the space that is required between the boards for cooling.
  • Page 160 Replacing basic chassis components Standard 1.0 To remove the upper fan holder foam 1 Remove the server’s side cover. 2 Lift the upper fan holder foam out of the server. To replace the upper fan holder foam 1 Ensure that the fan cables are in the slots in the lower fan holder foam. 2 Place the bottom end of the upper fan holder foam beneath the edge of the server chassis.
  • Page 161: Replacing The Side Cover

    October 2003 Replacing basic chassis components Replacing the side cover Introduction After you complete your work with the server’s interior components, replace the side cover and, if you removed them, reinstall the chassis feet on the bottom of the server. To replace the side cover CAUTION Risk of equipment damage...
  • Page 162 Replacing basic chassis components Standard 1.0 Top and bottom tabs on cover Top and bottom slots in chassis G101762 CallPilot...
  • Page 163: Section B: Replacing Fans

    October 2003 Replacing basic chassis components Section B: Replacing fans In this section Cooling fans description Replacing a front system fan Replacing a rear system fan Replacing the processor fan Part 5: 703t Server Maintenance and Diagnostics...
  • Page 164: Cooling Fans Description

    Replacing basic chassis components Standard 1.0 Cooling fans description Introduction For cooling and airflow, the system contains five fans that cool the server’s interior. WARNING Risk of equipment damage Ensure that any cables in the proximity of the fans are kept away from the fans.
  • Page 165 October 2003 Replacing basic chassis components Front system fans Processor fan Media drive fans Fan holder foam G101781 Part 5: 703t Server Maintenance and Diagnostics...
  • Page 166 Replacing basic chassis components Standard 1.0 Rear system fans Rear system fans G101763 Fan labels The following conditions indicate when fans are installed correctly: The fan’s printed label faces the back of the server. The arrows embossed on the fan casing face as follows: CallPilot...
  • Page 167: Replacing A Front System Fan

    Introduction Replace a malfunctioning fan with the same type as the one removed. For more information about replacing a fan, contact your Nortel Networks customer service representative. Note: The fan replacement kit contains four fans: two front fans and two rear fans.
  • Page 168 Replacing basic chassis components Standard 1.0 3 Remove any add-in boards that block your access to the fan connectors on the motherboard. Note: As you remove each board, label it with its slot number so that you can reinstall the board in the same slot. 4 Lift the fan out of its slot in the fan holder foam.
  • Page 169 October 2003 Replacing basic chassis components 1 Insert the fan into its slot in the bottom fan holder foam. ATTENTION To ensure proper cooling operation, ensure that the fan’s printed label is facing the back of the server, and the arrows embossed on the fan casing are facing as follows: 2 Connect the fan’s power cable as follows: a.
  • Page 170: Replacing A Rear System Fan

    Introduction Replace a malfunctioning fan with the same type as the one removed. For more information about replacing a fan, contact your Nortel Networks customer service representative. Note: The fan replacement kit contains four fans: two front fans and two rear fans.
  • Page 171 October 2003 Replacing basic chassis components To install a rear system fan sysfan2 sysfan1 G101764 Part 5: 703t Server Maintenance and Diagnostics...
  • Page 172 Replacing basic chassis components Standard 1.0 1 Place the bottom edge of the fan on the support bracket at the back of the server. ATTENTION To ensure proper cooling operation, ensure that the fan’s printed label is facing the back of the server, and the arrows embossed on the fan casing are facing as follows: 2 Lift the bracket’s tab, align the fan with the server’s back wall, and then release the tab.
  • Page 173: Replacing The Processor Fan

    Replacing the processor fan Introduction Replace a malfunctioning fan with the same type as the one removed. For more information about replacing a fan, contact your Nortel Networks customer service representative. To remove the processor fan 1 Prepare the server for processor fan replacement as follows: a.
  • Page 174 Replacing basic chassis components Standard 1.0 To install the processor fan CPUfan1 G101766 CallPilot...
  • Page 175 October 2003 Replacing basic chassis components 1 Use both hands to spread the fan’s bracket tabs apart. Tip: You may need to lift the bottom fan holder foam slightly to create more space. 2 At the same time, slide the fan onto the supporting posts. ATTENTION To ensure proper cooling operation, ensure that the fan’s printed label is facing the back of the server, and...
  • Page 176 Replacing basic chassis components Standard 1.0 CallPilot...
  • Page 177: Replacing Media Drives

    C h a p t e r 8 Replacing media drives In this chapter SCSI and IDE drive cabling Replacing a hard drive Replacing the tape drive Replacing the CD-ROM drive Replacing the floppy disk drive Part 5: 703t Server Maintenance and Diagnostics...
  • Page 178: Scsi And Ide Drive Cabling

    Replacing media drives Standard 1.0 SCSI and IDE drive cabling Cabling diagram This following diagram shows the following: cabling for and termination of SCSI devices (hard drives and tape drives) cabling for an IDE CD-ROM drive Use the information in this section to assist you with the procedures for replacing a hard drive, tape drive, or CD-ROM drive.
  • Page 179: Replacing A Hard Drive

    October 2003 Replacing media drives Replacing a hard drive Introduction If you need to replace a faulty hard drive, then do the following: 1. Review this entire section before proceeding to become familiar with the requirements and process. 2. Prepare the server for hard drive replacement as described in “Preparing for hardware maintenance”...
  • Page 180 The last bay must remain empty to ensure proper system cooling. CAUTION Risk of equipment damage The internal SCSI interface in this system supports only single-ended SCSI devices. Use Nortel Networks- authorized drives only. SCSI drive cabling The hard drive assembly package includes a standard 68-pin, 68 conductor, twisted-pair wide (16-bit) SCSI ribbon cable, with terminator.
  • Page 181 October 2003 Replacing media drives The following table identifies RAID and SCSI settings: Location of hard drives Hard drive in internal drive bays RAID label in the (from the top down) channel SCSI ID RAID software Drive bay 4 Not applicable (empty - used for airflow) applicable applicable...
  • Page 182 Replacing media drives Standard 1.0 Hard drive installation overview G101771 CallPilot...
  • Page 183 October 2003 Replacing media drives To remove a hard drive from the server 1 Prepare the server for hard drive replacement as follows: a. Shut down the server, and then disconnect the power and peripheral device cables. b. Remove the side cover. c.
  • Page 184 Replacing media drives Standard 1.0 7 Pull the drive carrier out of the chassis, and then place it cage-side-up on an antistatic surface. 8 Continue with “To install a new hard drive in the drive carrier” below. To install a new hard drive in the drive carrier 1 Remove the new drive from its protective wrapper, and place it on an antistatic surface.
  • Page 185 October 2003 Replacing media drives To install the hard drive ATTENTION The last bay must remain empty to ensure proper system cooling. 1 Slide the hard drive and drive carrier assembly (with the exposed drive facing up) into the server bay. ATTENTION To provide more space inside the server so that you can connect the cables, do not push the drive all the way in...
  • Page 186 Replacing media drives Standard 1.0 d. Connect the other end of the cable as follows: — Connect hard drive 1 to channel 0 on the RAID controller. — Connect hard drive 2 to channel 1 on the RAID controller. e. For proper cooling and airflow, neatly fold and secure the excess signal cable above the CPU.
  • Page 187 October 2003 Replacing media drives 8 Reinstall the fans (if removed) and upper fan holder foam. For instructions on reinstalling the fans, see “To install a front system fan” on page 168. For instructions on replacing the upper fan holder foam, see “To replace the upper fan holder foam”...
  • Page 188: Replacing The Tape Drive

    CAUTION Risk of electrical damage Use only a tape drive that is approved by Nortel Networks. Filler panels and EMI shields System EMI integrity and cooling are both protected by drives installed in the bays or by filler panels and EMI shields covering the bays.
  • Page 189 October 2003 Replacing media drives parity checking: enabled termination power (TPWR): enabled all other settings: factory default Tape drive installation overview G101772 Part 5: 703t Server Maintenance and Diagnostics...
  • Page 190 Replacing media drives Standard 1.0 To remove the tape drive Note: The tape drive is installed in the second bay from the top. 1 Prepare the server for tape drive replacement as follows: a. Shut down the server, and then disconnect the power and peripheral device cables.
  • Page 191 October 2003 Replacing media drives To install a replacement tape drive 1 Remove the new tape drive from its protective wrapper, and place it on an antistatic surface. 2 Record the drive model and serial numbers in your equipment log. 3 Set the tape drive’s settings as described in “Tape drive configuration”...
  • Page 192 Replacing media drives Standard 1.0 8 Connect the tape drive’s power cable. Result: The tape drive is installed. 9 Replace the upper fan holder foam. For instructions on replacing the upper fan holder foam, see “To replace the upper fan holder foam” on page 160. 10 Replace the side cover.
  • Page 193: Replacing The Cd-Rom Drive

    The CD-ROM drive is preinstalled at the factory. However, if it becomes faulty, follow the procedure in this section to replace it. CAUTION Risk of electrical damage Use only a CD-ROM drive that is approved by Nortel Networks. CD-ROM drive installation overview G101773...
  • Page 194 Replacing media drives Standard 1.0 To remove the CD-ROM drive Note: The CD-ROM drive is installed in the top bay. 1 Prepare the server for CD-ROM drive replacement as follows: a. Shut down the server, and then disconnect the power and peripheral device cables.
  • Page 195 October 2003 Replacing media drives To install a replacement CD-ROM drive 1 Remove the new CD-ROM drive from its protective wrapper, and place it on an antistatic surface. 2 Record the drive model and serial numbers in your equipment log. 3 Set the new CD-ROM drive to IDE Master by changing the jumper settings at the back of the drive.
  • Page 196 Replacing media drives Standard 1.0 10 Reconnect the peripheral device and power cables. 11 Power up the server. 12 Test the CD-ROM drive. CallPilot...
  • Page 197: Replacing The Floppy Disk Drive

    The floppy disk drive is preinstalled at the factory. However, if it becomes faulty, follow the procedure in this section to replace it. Risk of electrical damage Use only a floppy disk drive that is approved by Nortel Networks. Floppy disk drive installation overview...
  • Page 198 Replacing media drives Standard 1.0 To remove the floppy disk drive ATTENTION Nortel Networks recommends that you use a magnetic screwdriver in this procedure. A nonmagnetic screwdriver can result in screws being lost between the chassis and plastic bezel. CAUTION...
  • Page 199 October 2003 Replacing media drives 6 Remove the assembly from the chassis. 7 Remove the four screws that hold the bracket to the drive, and set them and the bracket aside. 8 Place the drive in an antistatic protective wrapper. 9 Continue with “To install a replacement floppy disk drive”...
  • Page 200 Replacing media drives Standard 1.0 Ensure that the carrier is aligned with the two screw holes closest to the front of the floppy disk drive. Tighten the screws firmly. 5 Install the drive carrier inside the server. Slide the assembly toward the front of the system, and engage it with the bracket tabs on the side of the drive bay.
  • Page 201: Maintaining The Ami Megaraid Elite 1600 Raid System

    C h a p t e r 9 Maintaining the AMI MegaRAID Elite 1600 RAID system In this chapter Section A: RAID maintenance overview About RAID RAID maintenance quick reference Section B: Performing RAID card maintenance Replacing the RAID card Updating the RAID card’s firmware Configuring the AMI MegaRAID Elite 1600 card Recovering from a corrupted RAID BIOS...
  • Page 202 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 CallPilot...
  • Page 203: Section A: Raid Maintenance Overview

    October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Section A: RAID maintenance overview In this section About RAID RAID maintenance quick reference Part 5: 703t Server Maintenance and Diagnostics...
  • Page 204: About Raid

    Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 About RAID Introduction Redundant Array of Independent Disks (RAID) is a technology that can combine two or more drives for fault tolerance and continued system performance. The CallPilot RAID controller is a PCI RAID SCSI card that provides high-performance disk mirroring.
  • Page 205 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system The rebuild process usually takes between 30 to 60 minutes. Nortel Networks strongly recommends that you do not restart the server during this time. At the end of the rebuild process, the system notifies you about the completion and returns to the original status before the failure occurred.
  • Page 206 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 System backups on RAID systems You must perform regular full-system backups of the CallPilot server to tape. Although RAID provides a high level of data security through redundancy, you must restore from backup tape if the RAID card fails or if both hard drives in a RAID system pack fail.
  • Page 207: Raid Maintenance Quick Reference

    If the existing RAID card has failed, the data on the hard drives may be corrupted. A procedure for replacing the AMI MegaRAID Elite 1600 card is provided in this section for reference purposes. However, you must contact Nortel Networks technical support for further instructions before you begin.
  • Page 208 Risk of system failure Replacement of a RAID card with one that is not identical causes a system failure. You must use Nortel Networks- approved components. 2. Ensure that the firmware on the RAID card is the correct version by performing a RAID firmware update from the CallPilot 2.02...
  • Page 209 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Scenario 3: You want to perform a CallPilot server upgrade or install a significant PEP If you want to perform a CallPilot server upgrade, you must do the following: 1. Launch the MegaRAID Client in Windows NT, and then put one of the RAID channels (hard drives) into failed state.
  • Page 210 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 IF the upgrade was THEN not successful revert the system to the pre-upgrade version. For more information, see “Scenario 4: The CallPilot server upgrade was not successful” on page 210. Scenario 4: The CallPilot server upgrade was not successful If you want to revert the CallPilot system back to the previous CallPilot release because the server upgrade failed, you must do the following:...
  • Page 211: Section B: Performing Raid Card Maintenance

    October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Section B: Performing RAID card maintenance In this section Replacing the RAID card Updating the RAID card’s firmware Configuring the AMI MegaRAID Elite 1600 card Recovering from a corrupted RAID BIOS Part 5: 703t Server Maintenance and Diagnostics...
  • Page 212: Replacing The Raid Card

    CAUTION Risk of system failure Replacement of a RAID card with one that is not identical causes a system failure. You must use Nortel Networks approved components. Materials you need Before you replace the RAID card, gather the following tools:...
  • Page 213 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system To replace the RAID card 1 Prepare the server for RAID card replacement as follows: a. Shut down the server, and then disconnect the power and peripheral device cables. b. Place the server on its side. c.
  • Page 214 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 9 Apply pressure towards the server motherboard until the card is evenly and securely seated in the slot. CAUTION Risk of equipment damage Ensure that the card is completely seated or it will short-circuit.
  • Page 215 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system e. For proper cooling and airflow, neatly fold and secure the excess signal cable length above the CPU. Use a tie wrap or cable clip to secure the cables. CAUTION Risk of equipment damage Ensure that any cables in the proximity of the fans are kept away from the fans.
  • Page 216 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 13 Reinstall the server’s side cover. 14 Reconnect the peripheral device and power cables. 15 Power up the server. What’s next? Continue with “Updating the RAID card’s firmware” on page 217. CallPilot...
  • Page 217: Updating The Raid Card's Firmware

    You may be required to update the RAID card’s firmware in the following situations: Nortel Networks technical support instructs you to update the firmware. The RAID card became faulty and you replaced it. The RAID card’s BIOS is upgraded through a flash process. The flash process is initiated by running the RAID card firmware update utility that is provided on the CallPilot 2.02 OS Recovery or OS Upgrade CD-ROM.
  • Page 218 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 ATTENTION This prompt appears for only a couple of seconds, along with the message Press Ctrl+H for WebBIOS, which appears in white flashing letters. To avoid missing the prompt, press Ctrl+M after the AMI MegaRAID information begins displaying and before the prompt appears.
  • Page 219 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system To update the RAID firmware The RAID card’s BIOS is upgraded through a flash process. The flash process is initiated by running a RAID card firmware update utility on the CallPilot 2.02 OS Recovery or OS Upgrade CD-ROM.
  • Page 220 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 Command Prompt with LAN access ... Make a Bootable Floppy Disk with IDE CD support Run PC Hardware Diagnostics Other Utilities (BIOS, Firmware, etc) ... 5 Choose option 8, Other Utilities (BIOS, Firmware, etc), and then press Enter.
  • Page 221: Configuring The Ami Megaraid Elite 1600 Card

    October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Configuring the AMI MegaRAID Elite 1600 card Introduction The RAID card’s configuration is stored on both the card and on the hard drive, so typically you are not required to reconfigure RAID unless you are making a change to the RAID system (for example, if you upgrade the hard drives to higher-capacity hard drives).
  • Page 222 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 1 Start (or restart) the server and observe the startup diagnostics. For instructions on restarting the server, refer to Part 1 of the CallPilot Installation and Configuration binder. Result: The AMI MegaRAID startup diagnostics appear, followed by a prompt to Press Ctrl+M to run the MegaRAID Configuration Utility.
  • Page 223 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Multiple PCI Delayed Trans: Disabled Force Boot: Off Coercion Algorithm: GigaByte-way 7 Press Esc. 8 Press the arrow and Enter keys to choose Objects Channel Channel 1, and then ensure that the following values are set: Termination State: Enabled SCSI Transfer Rate: 160M 9 Press Esc.
  • Page 224 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 18 Choose Yes to save the configuration. Result: You are informed that the configuration is saved and to press any key. 19 Press Enter (or any key). 20 Press Esc to exit the submenu. 21 In the Management Menu, choose Initialize.
  • Page 225: Recovering From A Corrupted Raid Bios

    October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Recovering from a corrupted RAID BIOS Introduction There are special situations when the RAID system seems to have failed and data is corrupted while backup drives are not available. Typically, the system may not even boot to the operating system.
  • Page 226 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 3 Press the arrow and Enter keys to choose Configure Clear Configuration. 4 Choose Yes to confirm and then press Enter. Result: This operation clears the RAID card’s NVRAM but leaves the configuration data on the hard drives intact.
  • Page 227 If the server will not start to Windows NT, you may need to reinstall the Windows NT operating system and CallPilot software. Contact your Nortel Networks technical support representative for advice before you proceed. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 228 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 CallPilot...
  • Page 229: Section C: Performing Raid System Pack Maintenance

    October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Section C: Performing RAID system pack maintenance In this section Verifying consistency on both drives Splitting the RAID system pack Rebuilding a hard drive in the RAID system pack Reverting to the pre-upgrade system (if the CallPilot upgrade failed) Part 5: 703t Server Maintenance and Diagnostics...
  • Page 230: Verifying Consistency On Both Drives

    Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 Verifying consistency on both drives Introduction The consistency check on the RAID system’s logical drive ensures that the data on both drives is identical. If any errors are found, they are corrected automatically.
  • Page 231 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system 2 Ensure that Full Access is selected, and then click OK. Result: The MegaRAID Power Console Plus window appears: The status bar at the bottom of the window indicates that RAID channels are being scanned.
  • Page 232 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 3 In the Logical Drives section, right-click the logical drive, and then choose Check Consistency from the pop-up menu that appears. Result: The following status dialog appears; CallPilot...
  • Page 233 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system The check takes up to 2 hours to complete. You are informed when it is finished. If any errors were found, you receive a message similar to the following: 4 If you will not be proceeding with splitting the RAID system pack at this time, click Configuration Exit to close MegaRAID Client Power Console Plus.
  • Page 234: Splitting The Raid System Pack

    703t server because hard drives are not hot-swappable, and hard drive cables can be prone to damage during hard drive removal and replacement. Nortel Networks recommends that you perform regular CallPilot full-system backups to tape instead.
  • Page 235 Result: The channels are scanned and when done, the Physical Drive Selection Menu appears. 5 Choose the drive that you wish to “fail” (Nortel Networks recommends you choose Channel 2), and then press Enter. Note: The hardware labels inside the 703t server are different from the labels in the RAID software.
  • Page 236 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 6 Choose Fail Drive, and then press Enter. Result: A warning message appears and the alarm starts to sound. The alarm will continue until the RAID is back to its original state. Note: You can silence the alarm temporarily for the duration of the procedure by clicking Adapter Alarm Control...
  • Page 237 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system 3 Was the upgrade successful? THEN rebuild the hard drive in the RAID system pack. This copies the upgraded CallPilot data to the hard drive that you intentionally failed earlier. For instructions, see “Rebuilding a hard drive in the RAID system pack”...
  • Page 238: Rebuilding A Hard Drive In The Raid System Pack

    Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 Rebuilding a hard drive in the RAID system pack Introduction This section describes how to manually synchronize the server’s hard drives in the following scenarios: You replaced a failed hard drive as described in “Replacing a hard drive” on page 179.
  • Page 239 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system 2 Ensure that Full Access is selected, and then click OK. Result: The MegaRAID Power Console Plus window appears: The status bar at the bottom of the window indicates that RAID channels are being scanned.
  • Page 240 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 If the alarm is sounding, you can silence it temporarily by clicking Adapter Alarm Control Silence. Do not disable the alarm under any circumstances . 3 In the Physical Devices list, right-click the channel that is in failed state. 4 From the pop-up menu that appears, click Tools Rebuild.
  • Page 241 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system The rebuild takes approximately 30 to 60 minutes. When done, the rebuild status dialog closes, and the MegaRAID Power Console Plus window refreshes to show both channels as online. 5 Click Configuration Exit to close MegaRAID Client Power Console Plus.
  • Page 242 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 What’s next? Test the CallPilot system to ensure that it is operating as expected. CallPilot...
  • Page 243: Reverting To The Pre-Upgrade System (If The Callpilot Upgrade Failed)

    October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system Reverting to the pre-upgrade system (if the CallPilot upgrade failed) Introduction This section describes how to restore the CallPilot server to the state it was in before you upgraded the CallPilot software. Use this procedure to revert the system if the upgrade was not successful.
  • Page 244 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 To reverse the hard drive states 1 Restart the server and observe the startup diagnostics. For instructions on restarting the server, refer to “Restarting the server” in Part 1 of the CallPilot Installation and Configuration binder. Result: The AMI MegaRAID startup diagnostics appear, followed by a prompt to Press Ctrl+M to run the MegaRAID Configuration Utility.
  • Page 245 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system 11 Press Esc three times to exit from the MegaRAID BIOS Configuration Utility. 12 Press Ctrl+Alt+Delete to restart the server. 13 Continue with “To rebuild the hard drive in the RAID system pack with pre-upgrade data”...
  • Page 246 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 The status bar at the bottom of the window indicates that RAID channels are being scanned. When scanning is done, the screen refreshes as shown in the following screen example. CallPilot...
  • Page 247 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system If the alarm is sounding, you can silence it temporarily by clicking Adapter Alarm Control Silence. Do not disable the alarm under any circumstances . 4 In the Physical Devices list, right-click Channel 1 (the failed drive). 5 From the pop-up menu that appears, click Tools Rebuild.
  • Page 248 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 The rebuild takes approximately 30 to 60 minutes. When done, the rebuild status dialog closes, and the MegaRAID Power Console Plus window refreshes to show both channels as online. 6 Click Configuration Exit to close MegaRAID Client Power Console Plus.
  • Page 249 October 2003 Maintaining the AMI MegaRAID Elite 1600 RAID system What’s next? 1. Check the CallPilot system to ensure that it reverted successfully to the pre-upgrade version. 2. Redo the entire CallPilot upgrade process (including the tasks in the Upgrade Readiness Checklist) as described in the CallPilot 2.02 Upgrade Guide.
  • Page 250 Maintaining the AMI MegaRAID Elite 1600 RAID system Standard 1.0 CallPilot...
  • Page 251: Replacing Voice Processing Boards

    C h a p t e r 1 0 Replacing voice processing boards In this chapter DSP numbering and location Replacing an MPB96 board Part 5: 703t Server Maintenance and Diagnostics...
  • Page 252: Dsp Numbering And Location

    Replacing voice processing boards Standard 1.0 DSP numbering and location Introduction DSPs are the built-in voice processing components on MPB boards. DSPs are numbered to distinguish them in CallPilot maintenance programs, such as the Maintenance page in CallPilot Manager. Each DSP supports up to eight multimedia channels. DSP numbering on MPB96 boards The MPB96 board has 12 embedded DSPs.
  • Page 253 October 2003 Replacing voice processing boards The following diagram shows the MPB96 board: Faceplate Mezzanine connector CT Bus connector (for future use) PCI connector DS30 link status LEDs DS30 connector G101776 Part 5: 703t Server Maintenance and Diagnostics...
  • Page 254: Replacing An Mpb96 Board

    Replacing voice processing boards Standard 1.0 Replacing an MPB96 board Introduction This section describes how to replace an MPB96 board. You will need to replace an MPB96 board: if the board becomes faulty when the PCI firmware needs to be updated, and the board must be sent back to the factory CAUTION Risk of electrical damage...
  • Page 255 October 2003 Replacing voice processing boards Ferrites Connectors for the MGate cards Connector for the MPB96 board G101786 Note: The ferrites on this cable control EMC emission levels. Do not remove them. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 256 Replacing voice processing boards Standard 1.0 MPB96 board installation Note: The MPB96 board must be installed in slot 4. When replacing the upper fan holder foam, ensure that the board inserts into the corresponding slot on the fan holder foam. G101777 CallPilot...
  • Page 257 October 2003 Replacing voice processing boards To replace an MPB96 board 1 Prepare the server for MPB96 board replacement as follows: a. Shut down the server, and then disconnect the following cables: — power cable — peripheral device cables — DS30X cable b.
  • Page 258 Replacing voice processing boards Standard 1.0 8 Replace the server cover. Note: Be careful not to pinch any cabling when replacing the server cover. Result: The MPB96 board replacement is complete. 9 Reconnect the peripheral device and power cables. 10 Reconnect the DS30X cable to the faceplate of the MPB96 board. 11 Power up the server and log on to Windows NT.
  • Page 259: Working With Dimms And The Cpu

    C h a p t e r 1 1 Working with DIMMs and the CPU In this chapter Replacing or adding baseboard DIMMs Replacing the CPU Part 5: 703t Server Maintenance and Diagnostics...
  • Page 260: Replacing Or Adding Baseboard Dimms

    8 Gbytes of memory. DIMM sizes and compatibility Contact your Nortel Networks sales representative or customer support representative for a list of approved, Nortel Networks-qualified DIMMs for the 703t server. ATTENTION Do not use types of DIMMs that have not been approved by Nortel Networks.
  • Page 261 October 2003 Working with DIMMs and the CPU DIMM removal and installation diagram To remove the DIMM memory module To install the DIMM memory module G101778 When installing DIMMs, ensure that the slots are populated in order, starting with the slot closest to the power connector: DIMM 1A (This is the slot closest to the power connector.) DIMM 1B DIMM 2A...
  • Page 262 Working with DIMMs and the CPU Standard 1.0 To remove baseboard DIMMs 1 Prepare the server for DIMM replacement as follows: a. Shut down the server, and then disconnect the power and peripheral device cables. b. Place the server on its side. c.
  • Page 263 To install baseboard DIMMs CAUTION Risk of equipment damage and data corruption Use only Nortel Networks-approved DIMMs. A mixture of dissimilar metals (from the use of non-approved DIMMs) can cause later memory failures, resulting in data corruption. 1 Prepare the server for DIMM installation as described in “Preparing for hardware maintenance”...
  • Page 264: Replacing The Cpu

    Working with DIMMs and the CPU Standard 1.0 Replacing the CPU Introduction The 703t server’s motherboard provides two connectors for Xeon processor chips, but only one is populated for CallPilot. For a single-CPU configuration, the CPU must be installed on the CPU1 connector. A processor terminator board is not required.
  • Page 265 October 2003 Working with DIMMs and the CPU To remove the faulty CPU CAUTION Risk of electrical damage Wear an antistatic ESD wrist strap during the CPU replacement process. 1 Prepare the server for CPU replacement as follows: a. Shut down the server, and then disconnect the power and peripheral device cables.
  • Page 266 Working with DIMMs and the CPU Standard 1.0 3 Using both hands, remove the heat sink housing, as follows: a. Grasp the bottom edge of one side of the heat sink housing, and pry the bottom tabs away from the heat sink. CAUTION Risk of equipment damage Ensure that you do not bend the wings of the heat sink...
  • Page 267 October 2003 Working with DIMMs and the CPU 4 Remove the clips that secure the heat sink to the motherboard, as shown in the following diagram: Use a tool to pry the clip away from the heat sink guide. Ensure that you do not damage the heat sink while removing the clip.
  • Page 268 Working with DIMMs and the CPU Standard 1.0 6 Remove the microprocessor as shown in the following diagram: G101791 a. Lift the lever that secures the microprocessor to the motherboard. While applying gentle downward pressure, push the lever away from you (towards the top of the server), and then lift it all the way to the left.
  • Page 269 October 2003 Working with DIMMs and the CPU To install a new CPU CAUTION Risk of electrical damage Wear an antistatic ESD wrist strap during the entire CPU replacement process. 1 Remove the new microprocessor from its antistatic package. CAUTION Risk of equipment damage Do not touch the pins on the microprocessor.
  • Page 270 Working with DIMMs and the CPU Standard 1.0 G101779 CallPilot...
  • Page 271 October 2003 Working with DIMMs and the CPU a. Ensure that the microprocessor lever is open all the way to the left. b. Align the gold triangle on one corner of the microprocessor with the gold triangle on the socket. Note: See the top left corner of the microprocessor in the photograph in step 6 on page 268.
  • Page 272 Working with DIMMs and the CPU Standard 1.0 G101780 a. Align the side tabs on the clip over the heat sink guide. b. Align the center hole on the clip over the tab on the heat sink guide. c. Slide the clip forward or back until the tab is in the small portion of the hole.
  • Page 273 October 2003 Working with DIMMs and the CPU 4 Use both hands to install the heat sink housing assembly as shown in the following diagram (see also the description that follows page 274): G101788 Part 5: 703t Server Maintenance and Diagnostics...
  • Page 274 Working with DIMMs and the CPU Standard 1.0 a. Grasp the bottom edge of each side of the heat sink housing. b. Spread the sides of the housing slightly, and then lower the housing over the heat sink. c. Release the housing to engage the tabs around the edge of the heat sink’s platform.
  • Page 275: Working With The Callpilot Server Bios

    C h a p t e r 1 2 Working with the CallPilot server BIOS In this chapter Overview BIOS settings Updating and configuring the BIOS Recovering from corrupted CMOS and BIOS Part 5: 703t Server Maintenance and Diagnostics...
  • Page 276: Overview

    The server’s BIOS defines the compatibility of the server with expansion hardware. All systems configured by Nortel Networks manufacturing are shipped with at least the minimum vintage BIOS. However, new BIOS may be issued to fix discovered bugs or to support new hardware standards and options.
  • Page 277: Bios Settings

    October 2003 Working with the CallPilot server BIOS BIOS settings Introduction This section identifies the 703t server’s BIOS settings: Main (below) Advanced (see page 279) Security (see page 280) Server (see page 281) Boot (see page 282) See “To configure the BIOS,” on page 285 for instructions on how to verify that the 703t server settings are set to the values given in the following sections.
  • Page 278 Working with the CallPilot server BIOS Standard 1.0 Options Settings Secondary IDE None Master Secondary IDE None Slave Processor Processor POST speed setting: 2 GHz Settings (shown in grey) Processor Hyperthreading: Enabled Processor 1 CPU ID: F24 (shown in grey) Processor 1 CPU Cache size: 512k ECC (shown in grey) Processor 2 CPU ID: Not installed (shown...
  • Page 279 October 2003 Working with the CallPilot server BIOS Advanced Options Settings PCI Configuration Use default values. Note: Default values are generated by pressing F9 before you change CMOS values. USB: Enabled NIC1: Enabled NIC2: Enabled Video: Enabled SCSI: Enabled Option ROM: Enabled (where applicable) PCI slots ROM: Enabled Integrated Peripheral COM1: IRQ4...
  • Page 280 Working with the CallPilot server BIOS Standard 1.0 Options Settings Boot Time Enabled Diag Screen Reset Config Data Num Lock Sleep Button Disabled Security Options Settings Use Password Clear Supervisor Clear Password Is Fixed Disk None Boot Sector Power Switch Disabled Inhibit NMI Control...
  • Page 281 October 2003 Working with the CallPilot server BIOS Server Options Settings System System Info (shown in grey) Management Console BIOS redirection port: Disabled Redirection ACPI redirection: Disabled Baud Rate: 9600 Flow Control: CTS/RTS Terminal Type: VT100+ Event Log Clear All Events log: No Configuration Event Logging: Enabled Critical Event Logging: Enabled...
  • Page 282 Working with the CallPilot server BIOS Standard 1.0 Boot Options Settings BIOS Device Removable Devices Priority Hard Drive ATAPI CDROM Hard Drive Do Not Change ATAPI CDROM Do Not Change CallPilot...
  • Page 283: Updating And Configuring The Bios

    BIOS update availability ATTENTION The BIOS installed on the CallPilot server must be version P07_64 or later. BIOS updates are provided by Nortel Networks on a floppy disk (NTRH8057). CAUTION Risk of equipment damage Do not power off or restart the server before BIOS update is complete.
  • Page 284 Working with the CallPilot server BIOS Standard 1.0 5 While the server is restarting, remove the BIOS update disk from the server’s floppy disk drive. 6 When the server has rebooted, continue with “To configure the BIOS” on page 285. CallPilot...
  • Page 285 October 2003 Working with the CallPilot server BIOS To configure the BIOS Note: Only options that need to be changed from their defaults are described below. As you perform this procedure, you should still validate that all BIOS settings conform to the values listed in “BIOS settings,” on page 277. 1 During the server startup and while the startup diagnostics still appear on the screen, press F2 to display the Main menu screen.
  • Page 286 Working with the CallPilot server BIOS Standard 1.0 third: CD-ROM drive Note: The CallPilot operating system requires that the first startup be completed from the CD-ROM drive. To achieve this during the startup process, press Esc to display the boot menu, and then choose ATAPI CD-ROM to start the server temporarily from the CD-ROM.
  • Page 287: Recovering From Corrupted Cmos And Bios

    October 2003 Working with the CallPilot server BIOS Recovering from corrupted CMOS and BIOS Introduction If the system behaves abnormally (for example, it does not start up or it freezes during the startup process), the CMOS may be corrupted. To correct this, follow the procedure in “To recover from a corrupted CMOS”...
  • Page 288 Working with the CallPilot server BIOS Standard 1.0 To recover from a corrupted BIOS Notes: To start the server into recovery mode, a memory DIMM module must be installed in the first socket, and a floppy disk drive must be installed. The CMOS is not cleared when the system BIOS is updated.
  • Page 289 October 2003 Working with the CallPilot server BIOS 12 Verify that the BIOS version was updated. Jumper locations and settings CMOS Clear Password Boot BMC Boot Under BMC Protect Normal Block Protect Control Force Clear Recovery Write Erase Enable J1H1 J1H2 G101769 Part 5: 703t Server Maintenance and Diagnostics...
  • Page 290 Working with the CallPilot server BIOS Standard 1.0 CallPilot...
  • Page 291: 703T Description Reference

    A p p e n d i x A 703t description reference In this appendix Server features Slot assignments IRQ mapping table Part 5: 703t Server Maintenance and Diagnostics...
  • Page 292: Server Features

    703t description reference Standard 1.0 Server features Introduction This section provides a general overview of the 703t server. Server dimensions Height chassis only: 42 cm (16.75 in.) with chassis feet: 44 cm (17.5 in.) Width chassis only: 21.5 cm (8.6 in.) with chassis feet: 32 cm (12.7 in.) Depth (distance from front to 65 cm (26 in.)
  • Page 293 October 2003 703t description reference Front panel features The following diagram shows the 703t server’s front panel features: CD-ROM Reset button drive Network LEDs Sleep mode drawer button (not used) eject button Power button Status LEDs Tape drive USB connector (not used) Air flow slots...
  • Page 294 703t description reference Standard 1.0 The table below describes the parts that are identified in the preceding diagram: Part Function Reset button Triggers a hardware (cold) reset. Do not use this button to perform a server restart. Restart the server as described in “Restarting the server”...
  • Page 295 October 2003 703t description reference Part Function IDE CD-ROM drive Enables you to use the CallPilot software and (5.25 in.) documentation CD-ROMs. CD drive eject Opens the CD-ROM drawer. Push the button button again to close the drawer. Backup tape drive Allows backup of hard drive data.
  • Page 296 703t description reference Standard 1.0 Rear panel diagram The following diagram shows the 703t server’s rear panel features: Power connector PS/2 mouse connector USB connectors (not used) PS/2 keyboard connector Serial port (COM1) Parallel port Monitor connector 10/100/1000Base-T CLAN Ethernet connector (NIC2 1 GB) 10/100Base-T ELAN Ethernet connector...
  • Page 297 October 2003 703t description reference The table below describes the parts that are identified in the preceding diagram: Part Color AC power supply connector Not applicable (450 W non hot-swap power supply) USB connectors Not applicable PS/2 keyboard connector Purple PS/2 mouse connector Green COM1 serial port connector (9-pin)
  • Page 298 703t description reference Standard 1.0 Part Color PCI slots (6) Not applicable Four slots are 100 MHz 3.3 V 64-bit PCI slots. Two slots are 33 MHz 5 V 32-bit PCI slots. Note: For more information, see “Slot assignments” on page 299. COM2 serial port connector slot (not installed) Teal Environmental specifications...
  • Page 299: Slot Assignments

    Maintenance Administration page) the maximum capacity for each switch connectivity Note: Your server may vary depending on what was ordered from Nortel Networks; therefore, your server may not have all of the slots populated. Part 5: 703t Server Maintenance and Diagnostics...
  • Page 300 703t description reference Standard 1.0 Slot definition and numbering In the following table, the term “slot” refers to the available slot openings in the chassis, not the PCI connectors inside the server. The slots are numbered from the bottom of the server to the top. Slot 1 is the bottom slot in the chassis when the chassis is standing upright.
  • Page 301: Irq Mapping Table

    October 2003 703t description reference IRQ mapping table The following table lists the assignments for each Interrupt Request (IRQ). You do not need this information for installation, but it may be useful for troubleshooting. Interrupt I/O APIC level Slot or device INTR INT0 Processor interrupt...
  • Page 302 703t description reference Standard 1.0 Interrupt I/O APIC level Slot or device IRQ14 INT14 IDE controller IRQ15 INT15 Available CallPilot...
  • Page 303 Index Numerics upgrading overview 703t server vintage dimensions BIOS and firmware revision environmental specifications verifying – front panel, description BIOS, flashing the hard drive bays board labels, CallPilot Manager IRQ assignments LEDs PCI slots slot assignments cabling slot locations RAID system with CD-ROM and tape drive call channels diagnostics, running...
  • Page 304 Index Standard 1.0 investigating tracert fault management compatibility alarm notification DIMMs event processing components Maintenance page CallPilot Manager maintenance Diagnostics section activities General section dependencies Maintenance section diagnostics that can be run purpose diagnostics-eligible using list – Multimedia Monitor, using replacing –...
  • Page 305 October 2003 Index last results viewing description events – viewing about POST investigating serial port overview startup TCP/IP failure to boot into service boot failure ipconfig nbtstat removing netstat replacing ping fault management tracert alarm notification Diagnostics section, Maintenance page event processing diagnostics tool firmware...
  • Page 306 Index Standard 1.0 removing hardware maintenance components, replacing maintenance performing activities by component preparing for preparing for hardware problems, detecting Maintenance page, CallPilot Manager Diagnostics section General section Maintenance section purpose IDE hard drive using mapping installation PCI IRQs to I/O APIC cooling fan motherboard motherboard DIMMs...
  • Page 307 October 2003 Index PEP Maintenance utility SCSI drive peripherals replacement parts, obtaining cables replacing ping command parameters and descriptions motherboard DIMMs running from Windows NT 4.0 SCSI drive syntax resources, troubleshooting power status LED CallPilot Administrator’s Guide 17 Power-On Self Test (POST) CallPilot Troubleshooting Reference 17 beep codes restarting system after TSTSERIO tests...
  • Page 308 Index Standard 1.0 Session Trace utility cabling settings configuring BIOS faulty, replacing shutting down TCP/IP diagnostics system sizes ipconfig DIMMs nbtstat slot assignments netstat slot locations ping software tracert maintenance, preparing for testing reinstalling POST diagnostics software RAID and Windows NT tracert command specifications, environmental parameters and descriptions...
  • Page 309 October 2003 Index Windows NT Diagnostics tool reinstalling system event log, viewing Windows NT 4.0 chkdsk utility Part 5: 703t Server Maintenance and Diagnostics...
  • Page 310 Index Standard 1.0 CallPilot...
  • Page 312 The process of transmitting data and call messaging between the CallPilot server and the switch or system is proprietary to Nortel Networks. Any other use of the data and the transmission process is a violation of the user license unless specifically authorized in writing by Nortel Networks prior to such use.

Table of Contents