Nortel CallPilot 702t Installation And Configuration Manual
Nortel CallPilot 702t Installation And Configuration Manual

Nortel CallPilot 702t Installation And Configuration Manual

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

Advertisement

Quick Links

555-7101-216
555-7101-216
CallPilot
Installation and Configuration
Part 5: 702t Server Maintenance and Diagnostics
Product release 2.0
Standard 1.0
October 2002

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CallPilot 702t and is the answer not in the manual?

Questions and answers

Summary of Contents for Nortel CallPilot 702t

  • Page 1 555-7101-216 555-7101-216 CallPilot Installation and Configuration Part 5: 702t Server Maintenance and Diagnostics Product release 2.0 Standard 1.0 October 2002...
  • Page 2 P0949453...
  • Page 3 Nortel Networks reserves the right to seek all allowable remedies for such breach. This page and the following page are considered the title page, and contain Nortel Networks and third-party trademarks.
  • 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 Publication history October 2002 Standard 1.0 of CallPilot Installation and Configuration, Part 5: 702t Server Maintenance and Diagnostics is issued for general release. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 6 Publication history Standard 1.0 CallPilot...
  • Page 7: Table Of Contents

    Contents About this guide Maintenance and diagnostics overview ......12 Resolving system problems ........14 Replacing hardware components .
  • Page 8 Contents Standard 1.0 Using CallPilot Manager to monitor hardware Understanding fault management ....... . 64 Section A: Tools for isolating and fixing hardware problems Overview.
  • Page 9 October 2002 Contents Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive SCSI and IDE cabling illustrations ......126 Replacing or installing hard drives .
  • Page 10 Contents Standard 1.0 Replacing DIMMs and the CPU Replacing baseboard DIMMs ........260 Replacing the CPU .
  • Page 11: 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: 702t Server Maintenance and Diagnostics...
  • Page 12: 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) performing hardware maintenance Who should read this guide This guide is for administrators, technicians, and engineers responsible for maintaining a CallPilot server.
  • Page 13 Note: The CallPilot Troubleshooting Reference is written for Nortel Networks distributors and technical support representatives; therefore, it is not part of the customer documentation package. Nortel Networks continually updates the CallPilot Troubleshooting Reference, which is available from the Partner Information Center (PIC) at http://my.nortelnetworks.com.
  • Page 14: Resolving System Problems

    About this guide Standard 1.0 Resolving system problems Introduction Chapters 2 to 5 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 15 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. Use the CallPilot Troubleshooting Reference to resolve the following types...
  • Page 16 About this guide Standard 1.0 server to network connection problems remote access connection problems CallPilot application problems CallPilot...
  • Page 17: Replacing Hardware Components

    October 2002 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, or cooling Chapter 7, “Replacing basic chassis components” on page 115 the hard drive, tape drive, Chapter 8, “Replacing a hard drive, CD-ROM drive, or floppy tape drive, CD-ROM drive, or floppy...
  • Page 18 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 19: Troubleshooting Your Callpilot System

    C h a p t e r 2 Troubleshooting your CallPilot system In this chapter Overview Interpreting POST diagnostics Interpreting startup diagnostics from SCSI BIOS What to do when the server fails to boot into service Part 5: 702t Server Maintenance and Diagnostics...
  • Page 20: Overview

    See “Using the CallPilot Administrator’s Guide” on page 15 for more details. CallPilot Troubleshooting Reference This guide is written for Nortel Networks distributors and technical support representatives. As a result, this guide is not part of the customer documentation package. See “Using the CallPilot Troubleshooting Reference”...
  • Page 21: Interpreting Post Diagnostics

    October 2002 Troubleshooting your CallPilot system Interpreting POST diagnostics Introduction This section explains POST diagnostic codes. Definition The Power-On-Self-Test (POST) is a system diagnostic program (stored in the BIOS) that runs every time the 702t server is started. POST’s function is to test system components, and then to display status messages.
  • Page 22 If an error occurs before video initialization, 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. Write down the beep codes before calling your Nortel Networks customer support representative. ATTENTION Some POST beep codes are critical and require you to replace your motherboard.
  • Page 23: Interpreting Startup Diagnostics From Scsi Bios

    October 2002 Troubleshooting your CallPilot system Interpreting startup diagnostics from SCSI BIOS Introduction The results from the SCSI controller diagnostics appear after the POST results. Applicable cards Results of the startup diagnostics appear only if you have the Symbios Logic SCSI controller adapter card installed on your system.
  • Page 24: 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. 5 If you still cannot find the boot failure cause, call your Nortel Networks technical support representative. CallPilot...
  • Page 25 Note: If you are not a distributor, contact your Nortel Networks technical support representative for assistance. 6 If you still cannot find the boot failure cause, call your Nortel Networks technical support representative. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 26 Troubleshooting your CallPilot system Standard 1.0 CallPilot...
  • Page 27: 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: 702t Server Maintenance and Diagnostics...
  • Page 28: 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 29 October 2002 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 30: 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 31 October 2002 Using Windows NT online diagnostic tools Types of event logs Three types of event logs are available from the Windows NT Event Viewer, as follows: Log type Description System Logs events by Windows NT 4.0 components, including RAS or other Windows NT services. Security Logs security events, such as logons, logoffs, illegal access, and so on.
  • Page 32 Using Windows NT online diagnostic tools Standard 1.0 To use the Windows NT Event Viewer ➝ ➝ ➝ 1 Click Start Programs Administrative Tools Event Viewer. Result: The Event Viewer window appears. Note: The System Log appears by default. CallPilot...
  • Page 33 October 2002 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 34 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 35: Checking Hardware Using Windows Nt Diagnostics

    October 2002 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 36 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 Version Registration System System identifier...
  • Page 37 October 2002 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 38: 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 40) tracert (page 41)
  • Page 39 October 2002 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 ➝...
  • Page 40 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 41 October 2002 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 42 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 43 October 2002 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 44 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 ➝...
  • Page 45 October 2002 Using Windows NT online diagnostic tools Parameter Description 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 46 Using Windows NT online diagnostic tools Standard 1.0 3 Press Enter. Result: The system runs the nbtstat utility. 4 Type Exit to exit MS-DOS and return to Windows NT 4.0. The netstat command The netstat command displays current TCP/IP network connections and protocol statistics.
  • Page 47 October 2002 Using Windows NT online diagnostic tools To run the netstat 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 netstat with the required parameters. 3 Press Enter.
  • Page 48: 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 49 October 2002 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 50 Using Windows NT online diagnostic tools Standard 1.0 CallPilot...
  • Page 51: 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: 702t Server Maintenance and Diagnostics...
  • Page 52: 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 53: Shutting Down Services

    October 2002 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 54 Using serial port diagnostic tools Standard 1.0 Routing and Remote Access Service 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 55: Conducting Tstserio Tests

    October 2002 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 53. CAUTION Risk of communications loss By stopping the services on COM 1 or COM 2, you lose the...
  • Page 56 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 57 October 2002 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 58 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 59: Conducting Tstserio Tests With The Loopback Plug

    October 2002 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 60: 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. Services to restart after COM 1 testing Routing and Remote Access Service Services to restart after COM 2 testing CallPilot SLEE Service CallPilot MWI Service...
  • Page 61 October 2002 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 62 Using serial port diagnostic tools Standard 1.0 CallPilot...
  • Page 63: 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 64: 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 65: Section A: Tools For Isolating And Fixing Hardware Problems

    October 2002 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: 702t Server Maintenance and Diagnostics...
  • Page 66: 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 67 October 2002 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: 702t Server Maintenance and Diagnostics...
  • Page 68: 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 69 October 2002 Using CallPilot Manager to monitor hardware To investigate using the Alarm Monitor ➝ 1 In CallPilot Manager, click System Alarm Monitor. Result: The Alarm Monitor page 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 70 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 71: Event Browser

    October 2002 Using CallPilot Manager to monitor hardware Event Browser Introduction Use the Event Browser to investigate a series of events that occurred around the time an alarm was raised. The event listing can help you determine the root cause of a problem. About events The Event Browser displays events that have been recorded in the server log.
  • Page 72 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 73 October 2002 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: 702t Server Maintenance and Diagnostics...
  • Page 74: 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-8 card, MPB board, or the DS30X link, you can use the Diagnostic section on the Maintenance page.
  • Page 75: 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 76 Using CallPilot Manager to monitor hardware Standard 1.0 CallPilot...
  • Page 77: Section B: Working With The Maintenance Page

    October 2002 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: 702t Server Maintenance and Diagnostics...
  • Page 78: 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 79 October 2002 Using CallPilot Manager to monitor hardware The following is an example of a partially expanded tree for the 702t server: 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...
  • Page 80 Using CallPilot Manager to monitor hardware Standard 1.0 Section Description Maintenance This section shows the state of the selected component. Use this section to start and stop a component before running a diagnostic test. This section appears only for components on which you are allowed to perform maintenance administration.
  • Page 81 October 2002 Using CallPilot Manager to monitor hardware Start, stop, or Diagnostics Component courtesy stop? available? Replaceable? Time Switch MPCs (embedded on MPB embedded: No boards or on MPC-8 cards) MPC-8 cards: Yes DSPs Channels DS30X link Note: The MGate card and DS30X cable are replaceable. If you are having problems with the DS30X link, determine if either one or both of those items are causing the problem and need to be replaced.
  • Page 82: Viewing Component States

    Using CallPilot Manager to monitor hardware Standard 1.0 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 83 October 2002 Using CallPilot Manager to monitor hardware State Description Not Configured The device 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 84 Using CallPilot Manager to monitor hardware Standard 1.0 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 85: 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 stop CallPilot, use the following:...
  • Page 86 Using CallPilot Manager to monitor hardware Standard 1.0 Stop versus Courtesy stop The following two methods of taking a component out of service allow you to choose how active calls are affected: Courtesy stop A Courtesy stop takes the component out of service only after the component has finished processing the active call.
  • Page 87 October 2002 Using CallPilot Manager to monitor hardware Component Effect of stopping MPB board Takes all call processing resources on the selected board out of service. Time Switch You cannot perform maintenance administration on the timeswitch. MPCs (embedded on MPB Takes the selected MPC out of service.
  • Page 88 Using CallPilot Manager to monitor hardware Standard 1.0 5 Scroll down to the Maintenance section. The following is an example of the Maintenance section for an MPC-8 card: 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.
  • Page 89: Running Integrated Diagnostics

    October 2002 Using CallPilot Manager to monitor hardware 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 90 (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 91 October 2002 Using CallPilot Manager to monitor hardware 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 85. ➝ 1 In CallPilot Manager, click Maintenance Maintenance Admin.
  • Page 92 Using CallPilot Manager to monitor hardware Standard 1.0 6 Scroll down to the Diagnostics section. Result: The following is an example of the Diagnostics section for an MPC-8 card (removable 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 93 October 2002 Using CallPilot Manager to monitor hardware 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. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 94: Viewing The Last Diagnostic Results

    You can review the results of previously-run diagnostics by clicking the Get 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 85. ➝...
  • Page 95 October 2002 Using CallPilot Manager to monitor hardware 5 Scroll down to the Diagnostics section. Result: The following is an example of the Diagnostics section for an MPC-8 card (removable MPC): 6 Check the check box for each diagnostic for which you want to review results.
  • Page 96 Using CallPilot Manager to monitor hardware Standard 1.0 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 97: Section C: Working With The Multimedia And Channel Monitors

    October 2002 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: 702t Server Maintenance and Diagnostics...
  • Page 98: 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 ➝...
  • Page 99 October 2002 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 100: 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 ➝...
  • Page 101 October 2002 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 102 Using CallPilot Manager to monitor hardware Standard 1.0 CallPilot...
  • Page 103: 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 System Monitor Part 5: 702t Server Maintenance and Diagnostics...
  • Page 104: 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 105: Diagnostics Tool

    October 2002 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 (DSP, TimeSwitch, MediaBus).
  • Page 106 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 ➝...
  • Page 107 October 2002 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 (DSP, TimeSwitch, MediaBus).
  • Page 108: 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 109 October 2002 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 110: 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).
  • Page 111 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. Call Nortel Networks technical support for assistance. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 112 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. Critical Services needed for CallPilot Call Processing include the following: CT Media Server Service Telephony Server (TAPI) Service MAS EMCI Service...
  • Page 113 October 2002 Using CallPilot system utilities DS30X links In the DS30X link pane, each DS30 row represents a separate DS30X link (also referred to as a DS30 link). Each box in the row represents one DS30X channel. The DS30X links connect the CallPilot server to the MGate card in the Meridian 1 switch or Succession CSE 1000 system.
  • Page 114 Using CallPilot system utilities Standard 1.0 PEP information and configured Service DNs are listed in the bottom part of the window. 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: CallPilot...
  • Page 115: Replacing Basic Chassis Components

    C h a p t e r 7 Replacing basic chassis components In this chapter Before you begin Removing the side cover Replacing the side cover Removing the front cover Replacing the front cover Removing the fan Replacing the fan Part 5: 702t Server Maintenance and Diagnostics...
  • Page 116: Before You Begin

    Replacing basic chassis components Standard 1.0 Before you begin Disconnect the power cable Before you access the server interior, courtesy stop and power off the server (see Part 1 of the CallPilot Installation and Configuration binder for details). Then label and disconnect the power cable and any other peripheral cables that may be in your way.
  • Page 117: Removing The Side Cover

    October 2002 Replacing basic chassis components Removing the side cover To remove the side cover 1 If a padlock is installed on the back of the system, unlock and remove it. See “A” in the diagram below: Bottom tabs of cover Bottom slots of...
  • Page 118 Replacing basic chassis components Standard 1.0 3 Place the fingertips of your left hand under the built-in handle on the back of the cover. WARNING Risk of personal injury Do not touch the sharp metal edges of the cover as they can cause personal injury.
  • Page 119: Replacing The Side Cover

    October 2002 Replacing basic chassis components Replacing the side cover To replace the side cover CAUTION Risk of equipment damage Ensure that there are no tools or loose parts inside the server chassis before replacing the side cover. 1 Position the cover over the chassis so the top row of tabs aligns with the slots in the top of the chassis.
  • Page 120: Removing The Front Cover

    Replacing basic chassis components Standard 1.0 Removing the front cover Before you begin Before you remove the front panel assembly, disconnect all peripheral devices except the hub from the server, and remove the side panel. To remove the front cover 1 Remove and save the screw from the front cover.
  • Page 121: Replacing The Front Cover

    October 2002 Replacing basic chassis components Replacing the front cover To replace the front cover 1 Insert the metal tabs on the front cover into the slots on the right side of the chassis. 2 Align the front panel with the server by lining up the CD-ROM drive with its cutout.
  • Page 122: Removing The Fan

    Replacing basic chassis components Standard 1.0 Removing the fan Introduction For cooling and airflow, the system contains two removable chassis fans to cool the boards, and removable media drives. The integrated power supply fan provides additional cooling and airflow. Before you begin Before you remove the fan, power down the server, detach the power cord, and remove the side cover.
  • Page 123 October 2002 Replacing basic chassis components 3 Disconnect the fan power cable connector(s) from the fan header on the baseboard. See “A” in the diagram below: G100818 4 Remove the plastic “snap-on” fan housing assembly by firmly pressing the three plastic tabs on the assembly inward until you can pull the tabs out of the slots in the chassis.
  • Page 124: Replacing The Fan

    Replacing the 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. Correct airflow direction The removable fan pulls air from outside of the chassis so that it flows across the boards and out the back.
  • Page 125: Replacing A Hard Drive, Tape Drive, Cd-Rom Drive, Or Floppy Drive

    C h a p t e r 8 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive In this chapter SCSI and IDE cabling illustrations Replacing or installing hard drives Replacing or installing a tape drive Replacing the CD-ROM drive Replacing the floppy disk drive Part 5: 702t Server Maintenance and Diagnostics...
  • Page 126: Scsi And Ide Cabling Illustrations

    Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 SCSI and IDE cabling illustrations Introduction The diagrams in this section illustrate the cabling and termination of the SCSI devices (hard drives and tape drives), as well as the cabling for an IDE CD-ROM drive.
  • Page 127 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Cabling for a RAID system with IDE CD-ROM (no tape drive) CD-ROM IDE 1 IDE 0 Wide SCSI Narrow SCSI RAID card Channel 0 Channel 1 Note 1: A "T" indicates an active wide terminator. Note 2: The CD-ROM is connected to the IDE 0 (PRI IDE).
  • Page 128 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 Cabling for a RAID system with IDE CD-ROM and SCSI tape drive Tape drive CD-ROM IDE 1 IDE 0 Wide SCSI Narrow SCSI RAID card Channel 0 Channel 1 Note 1: A "T"...
  • Page 129 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Cabling for a non-RAID system with CD-ROM (no tape drive) CD-ROM IDE 1 IDE 0 Narrow SCSI Wide SCSI Note 1: A "T" indicates an active wide terminator. Note 2: The CD-ROM is connected to IDE 0.
  • Page 130 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 Cabling for a non-RAID system with CD-ROM and tape drive Tape drive CD-ROM IDE 1 IDE 0 Narrow SCSI Wide SCSI Note 1: A "T" indicates an active terminator. Note 2: An "A"...
  • Page 131: Replacing Or Installing Hard Drives

    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 If you are installing a SCSI drive, the system includes a standard 68-pin wide (16-bit) SCSI ribbon cable that supports up to eight SCSI devices.
  • Page 132 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 Active termination of SCSI cables Hard drives generally provide active termination and termination power. The last two drives in the SCSI channels must provide termination power to the active terminator.
  • Page 133 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive 12 Set the SCSI ID by setting any jumpers or switches, referring to Nortel Networks specifications and the drive manufacturer’s instructions. See “Hard drive location and SCSI ID configuration” on page 136 for required SCSI ID settings.
  • Page 134 7 Record the drive model and serial numbers in your equipment log. 8 Set the SCSI ID by setting any jumpers or switches, referring to Nortel Networks specifications and the drive manufacturer’s instructions. See “Hard drive location and SCSI ID configuration” on page 136 for required SCSI ID settings.
  • Page 135 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive 9 To terminate the SCSI bus, follow these steps: a. If the drive is not the last device on the SCSI cable, disable the SCSI termination. b. If the drive is one of the last two drives on the SCSI cable, ensure that the SCSI termination power is enabled.
  • Page 136 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 14 Attach power and signals cables to all drives installed in the bay. Connect the SCSI signal cable to the wide connector on the baseboard or to the RAID controller, as appropriate.
  • Page 137 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Non-RAID system Location of drives in SCSI System internal drive bays channel SCSI ID pack label Top slot Second slot from top Third slot from top Note: In a non-RAID system, the server has only three hard drives installed. See “SCSI and IDE cabling illustrations”...
  • Page 138: Replacing Or Installing A Tape Drive

    “To install a new tape drive (no tape drive previously installed)” on page Risk of electrical damage Use only tape drives 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 139 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive 4 Enable Termination power (TPWR). 5 Leave the remaining settings at the default values. To replace a faulty tape drive 1 Courtesy stop CallPilot, and then power down the server. 2 Ensure that the replacement tape drive’s settings are as described in “To configure the tape drive”...
  • Page 140 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 To install a new tape drive (no tape drive previously installed) This procedure provides instructions for installing a tape drive on a server that currently does not have a tape drive. 1 Courtesy stop CallPilot, and then power down the server.
  • Page 141 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive 10 For a non-RAID system, refer to the diagram in “Cabling for a non-RAID system with CD-ROM and tape drive” on page 130 for a cabling example. Cable the tape drive as shown in the diagram and described in these substeps: a.
  • Page 142: 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. Risk of electrical damage Use only CD-ROM drives approved by Nortel Networks. To replace the CD-ROM drive 1 Courtesy stop CallPilot, and then power down the server.
  • Page 143 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive 9 Reconnect the CD-ROM drive’s power cable and IDE cable. If you need assistance with this, refer to one of the following diagrams: “Cabling for a RAID system with IDE CD-ROM (no tape drive)” on page 127 “Cabling for a RAID system with IDE CD-ROM and SCSI tape drive”...
  • Page 144: 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 floppy drives approved by Nortel Networks. To replace the floppy disk drive 1 Courtesy stop CallPilot, and then power down the server.
  • Page 145 October 2002 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive 10 Place the drive carrier on the component side of the drive to align the four mounting holes. 11 Attach the brackets to the drive with four screws of the appropriate size and length (reuse the screws you removed before).
  • Page 146 Replacing a hard drive, tape drive, CD-ROM drive, or floppy drive Standard 1.0 Installing the floppy disk drive G100816 CallPilot...
  • Page 147: Performing Raid Maintenance

    C h a p t e r 9 Performing RAID maintenance In this chapter RAID overview Section A: Replacing the RAID controller card Replacing the AcceleRAID 352 RAID controller card Upgrading from DAC960 to AcceleRAID352 Section B: Maintaining an AcceleRAID352 RAID system Installing AcceleRAID352 RAID Global Array Manager software Rebuilding an AcceleRAID352 RAID hard drive Configuring an AcceleRAID352 RAID system...
  • Page 148: Raid Overview

    Performing RAID maintenance Standard 1.0 RAID overview Introduction Redundant Arrays of Inexpensive Disks (RAID) is a technology that can combine two or more drives for fault tolerance and performance. RAID Level 1 The RAID controller is a PCIRAID SCSI card that provides high- performance disk mirroring.
  • Page 149: Section A: Replacing The Raid Controller Card

    October 2002 Performing RAID maintenance Section A: Replacing the RAID controller card In this section Replacing the AcceleRAID 352 RAID controller card Upgrading from DAC960 to AcceleRAID352 Part 5: 702t Server Maintenance and Diagnostics...
  • Page 150: Replacing The Acceleraid 352 Raid Controller Card

    CAUTION Risk of system failure Replacement of a RAID controller card with one that is not identical causes a system failure. You must use Nortel Networks-approved components. Materials you need Before replacing the RAID card, gather the following tools:...
  • Page 151 126. 16 Replace the chassis cover. 17 Plug in the AC power cord and power up the server. If the server does not start up, contact your Nortel Networks technical support representative. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 152: Upgrading From Dac960 To Acceleraid352

    AcceleRAID352 controller card requires assistance from Nortel Networks technical support. Also note that if the existing RAID controller card has failed, the data on the hard drives may be corrupted. Contact Nortel Networks technical support for further instructions. CallPilot...
  • Page 153: Section B: Maintaining An Acceleraid352 Raid System

    October 2002 Performing RAID maintenance Section B: Maintaining an AcceleRAID352 RAID system In this section Installing AcceleRAID352 RAID Global Array Manager software Rebuilding an AcceleRAID352 RAID hard drive Configuring an AcceleRAID352 RAID system To flash upgrades in the AcceleRAID352 controller Splitting AcceleRAID352 RAID drives and upgrading software Part 5: 702t Server Maintenance and Diagnostics...
  • Page 154: Installing Acceleraid352 Raid Global Array Manager Software

    Performing RAID maintenance Standard 1.0 Installing AcceleRAID352 RAID Global Array Manager software Introduction The Global Array Manager (GAM) has several utilities and monitoring functions. Once launched, GAM maintains a real-time Error log and Event Viewer, and also includes functions that can be found in the EzAssist software that is embedded in the controller.
  • Page 155: Rebuilding An Acceleraid352 Raid Hard Drive

    October 2002 Performing RAID maintenance Rebuilding an AcceleRAID352 RAID hard drive Introduction In RAID level 1, two equal-capacity disks mirror one another. Both drives run simultaneously with one disk serving as the backup copy of the other disk. If one drive fails, the other continues to run. When you physically replace a failed drive with a new one, the data on the operating drive of the system pack must be copied onto the new drive to rebuild it.
  • Page 156 Performing RAID maintenance Standard 1.0 d. Power up the server. Result: POST messages from the RAID controller warn you that the system is operating in critical mode (that is, with some drives offline). 2 Log on to the CallPilot server as Administrator (or any other user ID that has administrative privileges).
  • Page 157 October 2002 Performing RAID maintenance 5 In the Disk Device Information window, click Rebuild to start the disk resynchronization process. Result: The Rebuild Status window appears. When the rebuild is complete (each drive takes up to 45 minutes), the following dialog box appears to inform you that the rebuild is complete: 6 Click OK in the Rebuild Message dialog box.
  • Page 158 Performing RAID maintenance Standard 1.0 7 Close the Workstation Array Manager window. Result: You have completed the rebuild procedure. CallPilot...
  • Page 159: Configuring An Acceleraid352 Raid System

    October 2002 Performing RAID maintenance Configuring an AcceleRAID352 RAID system Introduction Before configuring the Mylex PCI RAID card, you must have access to the driver disk. For firmware updates (see “To flash upgrades in the AcceleRAID352 controller” on page 168), you must also have firmware and utility versions. The minimum version of the RAID controller BIOS/Firmware and utility is specified below: AcceleRAID 352...
  • Page 160 Performing RAID maintenance Standard 1.0 RAID EzAssist utility To configure the AcceleRAID controller, regardless of whether an operating system is installed on your computer, the RAID EzAssist utility can be run from the Mylex controller’s BIOS at any system boot time. To enter the EzAssist utility and configure the RAID, follow the instructions in “To configure RAID using Mylex AcceleRAID 352”...
  • Page 161 October 2002 Performing RAID maintenance To configure the RAID system packs 1 Power up the system. Note: If you have BIOS level 14 on the 702t server, press the space bar to skip the memory check and start faster. Result: The system starts and messages such as the following appear: Mylex AcceleRAID 352 BIOS version x.xx-xx (Month Day, Year).
  • Page 162 Performing RAID maintenance Standard 1.0 6 From the main menu, use the arrow keys to highlight the View or Modify Controller Configuration option, and then press Enter. Result: The Controller Configuration window appears. 7 Press Enter to access the Properties. Result: The Properties menu appears.
  • Page 163 October 2002 Performing RAID maintenance 11 Use the arrow key to select Yes at the Save Changes window, and then press Enter. 12 Press Esc twice to exit to the Main menu. 13 If no further changes are required, press Esc until the Main menu appears.
  • Page 164 Performing RAID maintenance Standard 1.0 17 Use the arrow keys to perform the following substeps to set the RAID packs. For example, for the 702t: a. Select Drive Channel ID 0:00, and then press Enter to add it to the first pack.
  • Page 165 October 2002 Performing RAID maintenance 19 Press Enter to create the first logical drive. Result: The system prompts you to define the logical drive. 20 Select No because you must define two more drives. 21 Define the second drive as shown above for the server. 22 Press Tab to select Save Array.
  • Page 166 Note: You may be warned that you are combining two drives of different sizes. If this happens, you must ensure that you are using hard drives that are qualified by Nortel Networks for CallPilot. Result: The Logical Drive Definition window appears.
  • Page 167 October 2002 Performing RAID maintenance 32 Select Yes to exit the EzAssist utility. Result: The system restarts and is now ready for operating system installation. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 168: To Flash Upgrades In The Acceleraid352 Controller

    Performing RAID maintenance Standard 1.0 To flash upgrades in the AcceleRAID352 controller Introduction The RAID card has the supported release of firmware when it is shipped to the CallPilot distributor, so a firmware update at a customer site is not usually required.
  • Page 169: Splitting Acceleraid352 Raid Drives And Upgrading Software

    October 2002 Performing RAID maintenance Splitting AcceleRAID352 RAID drives and upgrading software Introduction Use this procedure on a CallPilot server that is configured with an AcceleRAID 352 controller. This procedure breaks the mirroring of the hard drives before an upgrade so that if the upgrade fails, you can quickly return the server to the state it was in before you started the upgrade.
  • Page 170 175) at least one day before the planned upgrade date. If you find errors, this early check gives you time to contact Nortel Networks technical support (if necessary), and resolve the errors before you begin the upgrade.
  • Page 171 October 2002 Performing RAID maintenance Approximate time to Task complete Check Disconnect the secondary hard 10 minutes ❒ ❒ ❒ ❒ drives. Perform the server software Varies depending on your ❒ ❒ ❒ ❒ upgrade. system Reconnect the offline hard 10 minutes ❒...
  • Page 172 Performing RAID maintenance Standard 1.0 Label used in SCSI Hard drive bay channel SCSI ID Logical drive diagrams Third slot from top 2 (primary hard drive) Fourth slot from top 0 (secondary hard drive) Fifth slot from top 1 (secondary hard drive) Sixth slot from top 2 (secondary...
  • Page 173 October 2002 Performing RAID maintenance To check the status of the RAID system All the drives configured in the RAID controller must be operating and online. If any of the logical drives are in the critical state, the RAID splitting procedure will not work and data loss can occur if it is used.
  • Page 174 Performing RAID maintenance Standard 1.0 3 Check that all hard drives are in the online state. A green bar indicates that a hard drive is online. If any hard drives are not online, follow steps 3 to 9 in “Resynchronizing the CallPilot server hard drives”...
  • Page 175 October 2002 Performing RAID maintenance To check the consistency of the logical drives You must verify that each pair of drives is correctly synchronized before continuing with the RAID splitting procedure. To verify that the drives are correctly synchronized, use the Mylex Workstation Array Manager software.
  • Page 176 When the consistency check is completed, the following dialog box appears if the consistency check was OK: Note: If the consistency check reports errors, stop this procedure and contact Nortel Networks technical support to correct the problem. 4 Click OK. Result: You return to the Logical Drive Information window.
  • Page 177 October 2002 Performing RAID maintenance To back up the existing RAID configuration It is important to back up the current configuration to a floppy disk before you make any changes to the configuration of the RAID controller. This enables you to recover the configuration of the RAID controller if any mistakes are made while executing the procedure.
  • Page 178 Performing RAID maintenance Standard 1.0 10 Press Esc to return to the RAID controller selection window. Result: You return to the RAID controller selection window. 11 Press Esc to exit the Mylex RAID EzAssist program. Result: A message appears indicating that you are about to exit RAID EzAssist and asking for confirmation.
  • Page 179 If this is not correct for your system, contact Nortel Networks technical support. 6 Select Advanced Options, and then press Enter. Result: The advanced options pop-up menu appears.
  • Page 180 Performing RAID maintenance Standard 1.0 10 Repeat steps 6 to 10 for the fifth and sixth hard drives. Result: The pre-upgrade hard drives (fourth, fifth, and sixth) are offline. 11 Press Esc to return to the administration pop-up menu. Result: You return to the administration pop-up menu. 12 Press Esc to return to the main menu.
  • Page 181 October 2002 Performing RAID maintenance careful not to damage the RAID card. See the following cabling diagram for the 702t server: CAUTION Risk of equipment damage and data loss Ensure you first power off the server and use an ESD wrist strap.
  • Page 182 Performing RAID maintenance Standard 1.0 Tape drive CD-ROM IDE 1 IDE 0 Wide SCSI Narrow SCSI RAID card Channel 0 Channel 1 Note 1: A "T" indicates a wide active terminator. Note 2: The CD-ROM is connected to IDE 0. G100812 3 Power up the server.
  • Page 183 October 2002 Performing RAID maintenance Performing the CallPilot server software upgrade You can now perform the upgrade operation. Only one hard drive of each pair is updated. This allows you to maintain a copy of the system in its previous state in case there are problems during the upgrade process. To perform the CallPilot server software upgrade 1 Upgrade the CallPilot server software.
  • Page 184 Performing RAID maintenance Standard 1.0 Resynchronizing the CallPilot server hard drives After you upgrade the server software and test the upgrade, follow the steps below to resynchronize the hard drives. To resynchronize the CallPilot server hard drives 1 Shut down and power off the CallPilot server. 2 Reconnect the hard drives by reconnecting the SCSI cable for channel 1.
  • Page 185 October 2002 Performing RAID maintenance ➝ ➝ 5 From the Windows desktop, select Start Programs Mylex Workstation Array Manager. Result: The Workstation Array Manager window appears. Logical drives 0, 1, and 2 are in critical state because the physical drives are not mirrored.
  • Page 186 Performing RAID maintenance Standard 1.0 6 In the Workstation Array Manager window, double-click the first offline hard drive (in the example in this procedure, this is the device at channel 1 ID 3). Result: The Disk Device Information window appears. 7 In the Disk Device Information window, click Rebuild to start the disk resynchronization process.
  • Page 187 October 2002 Performing RAID maintenance 8 Click OK in the Rebuild Message dialog box. Result: The Workstation Array Manager window is updated. In the example in this procedure, the physical drive at Channel 1 ID 3 is now online, as is logical drive 0. 9 Repeat steps 6 to 8 for the remaining two offline drives.
  • Page 188 Performing RAID maintenance Standard 1.0 Reverting to the pre-upgrade system (if the upgrade fails) This section describes how to restore the CallPilot server to the state it was in before you began the upgrade. This procedure includes the following steps: 1.
  • Page 189 October 2002 Performing RAID maintenance To clear the current RAID configuration 1 Power up the CallPilot server. 2 While the server is restarting, the RAID controller is detected and a prompt appears to “Press Alt-R for RAID Configuration Options.” When this prompt appears, press Alt-R.
  • Page 190 Performing RAID maintenance Standard 1.0 11 Power off the server. To reconnect the pre-upgrade hard drives 1 Ensure that you have powered off the CallPilot server. 2 Reconnect the pre-upgrade hard drives for the 702t server by reconnecting the SCSI cable for channel 1. Note: For cabling details, see the diagram in “To disconnect the secondary hard drives”...
  • Page 191 If this is not correct for your system, contact Nortel Networks technical support. 7 Select Advanced Options, and then press Enter. Result: The advanced options pop-up menu appears.
  • Page 192 Part 3 of the CallPilot Installation and Configuration binder. 4 Do one of the following: If the system is still not working properly, then there may be a RAID, hard drive, or software problem with the old data. Contact Nortel Networks technical support. CallPilot...
  • Page 193 October 2002 Performing RAID maintenance If the system is working properly, then continue with “To reconnect the failed upgrade hard drives” below. To reconnect the failed upgrade hard drives 1 Shut down and power off the CallPilot server. 2 Reconnect the failed upgrade hard drives by reconnecting the SCSI cable for channel 0.
  • Page 194 Performing RAID maintenance Standard 1.0 CallPilot...
  • Page 195: Section C: Maintaining A Dac960 Raid System

    October 2002 Performing RAID maintenance Section C: Maintaining a DAC960 RAID system In this section Maintaining DAC960 RAID hard drives Rebuilding a DAC960 RAID hard drive Configuring a DAC960 RAID system Splitting DAC960 RAID drives and upgrading software Part 5: 702t Server Maintenance and Diagnostics...
  • Page 196: Maintaining Dac960 Raid Hard Drives

    If there are ten or more soft errors per day, replace the drive. b. Hard errors should not occur during normal operation. Contact your Nortel Networks customer support representative if errors are accumulating. c. Miscellaneous Errors are typically due to cabling or termination problems on the SCSI bus.
  • Page 197 October 2002 Performing RAID maintenance 8 Repeat step 7 on all hard disk drives listed. 9 Close the configuration menu. 10 Exit from the DAC Admin software utility. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 198: Rebuilding A Dac960 Raid Hard Drive

    Performing RAID maintenance Standard 1.0 Rebuilding a DAC960 RAID hard drive Introduction In RAID level 1, two equal-capacity disks mirror one another. Both drives run simultaneously with one disk serving as the backup copy of the other disk. If one drive fails, the other continues to run. When the failed drive is physically replaced with a new one, the data on the operating drive of the system pack must be copied onto the new drive to rebuild it.
  • Page 199 October 2002 Performing RAID maintenance To rebuild a hard drive in a RAID system 1 Observe the warning message given by the DAC Monitor software that indicates a hard drive failure. 2 Record the SCSI channel SCSI ID of the drive that failed from the information in the DAC Monitor window.
  • Page 200 Performing RAID maintenance Standard 1.0 9 Run the DAC Administration utility. If there is no desktop shortcut, run the dacadm.exe program that is located in the directory C:\Winnt\System32 or D:\Winnt\System32 (the program location depends on the location of the Windows NT operating system). Result: The DAC Administration utility window appears.
  • Page 201 October 2002 Performing RAID maintenance 11 Start from the left side of the dialog box and click on the first dead drive (marked DED) to start rebuilding that drive. Result: The Rebuild Progress dialog box appears. If you are running the DAC Monitor program, the monitor window pops up and informs you of the progress of the rebuild.
  • Page 202 Performing RAID maintenance Standard 1.0 12 Click OK in the Rebuild Drive dialog box, and then click OK in the Rebuild Progress dialog box to return to the Device Selection dialog box. Result: The rebuilt drive is shown as being online (ONL). 13 In the Device Selection dialog box, click OK to return to the DAC Administration utility window.
  • Page 203: Configuring A Dac960 Raid System

    October 2002 Performing RAID maintenance Configuring a DAC960 RAID system Introduction This section provides instructions for configuring a RAID system. This involves the following main procedures, which are provided in this section: 1. Configure the RAID system packs (create and arrange system packs, and specify system drive sizes).
  • Page 204 Note: If your disk is outdated, you must obtain the latest version from your Nortel Networks customer support representative. CAUTION Risk of loss of system functionality You must use the DAC960 Utility provided by Nortel Networks. Other software can cause a loss of system functionality. RAID system pack locations and identifications The following tables display information required to identify RAID system packs in the RAID configuration procedure.
  • Page 205 October 2002 Performing RAID maintenance RAID system pack sizing The RAID system limits the actual capacity of any system pack to the size of the smallest drive in its pack. As drives are replaced, a mirrored set may consist of two drives of different sizes, possibly from different manufacturers.
  • Page 206 Performing RAID maintenance Standard 1.0 702t RAID system Size of RAID Resulting Qualified disk Physical drive system pack to RAID level 1 drive make/model capacity specify capacity Seagate ST32155 2048 Mbytes 4096 Mbytes 2048 Mbytes Seagate ST32272 2048 Mbytes 4096 Mbytes 2048 Mbytes Seagate ST34371 4096 Mbytes...
  • Page 207 October 2002 Performing RAID maintenance 4 You are asked to confirm the change. Confirm, and then press Esc to escape this menu. Result: Your system can now fully utilize hard drives up to 8 Gbytes in size. Note: With earlier revisions of the RAID card (v2.6x and lower) , this drive geometry option is not available, and as such, free disk space may show up at the end of the first (primary) disk in the Windows NT Disk Administrator.
  • Page 208 Performing RAID maintenance Standard 1.0 Use this information to select the drive that will be A-0, and then press Enter. Result: The device is labeled A-0 and is the first drive for System Pack A. The drive’s state is changed from RDY to ONL. 8 Use the tables in “RAID system pack locations and identifications”...
  • Page 209 October 2002 Performing RAID maintenance 15 Select Create System Drive, and then press Enter. Result: The system prompts you to choose which RAID Level to use. 16 Select RAID 1, and then press Enter. Result: The system prompts you to enter the size of the first system pack.
  • Page 210 Performing RAID maintenance Standard 1.0 3 Use the arrow keys to navigate to a system drive. Press Enter to select the drive. Repeat this step for each system drive. Result: A check mark indicates a selected drive. 4 Press Esc. Result: The Initialize System Drive menu appears.
  • Page 211 October 2002 Performing RAID maintenance 5 Type a:\ and the name of the backup file (for example, a:\raidback), and then press Enter. CAUTION Risk of data loss You must save this file to drive A on a floppy disk; otherwise, you may not be able to restore the RAID configuration if the RAID card fails.
  • Page 212: Splitting Dac960 Raid Drives And Upgrading Software

    Performing RAID maintenance Standard 1.0 Splitting DAC960 RAID drives and upgrading software Introduction Use this procedure on a CallPilot server that is configured with a DAC960 RAID controller. This procedure breaks the mirroring of the hard drives before an upgrade so that if the upgrade fails, you can quickly return the server to the state it was in before you started the upgrade.
  • Page 213 219) at least one day before the planned upgrade date. If you find errors, this early check gives you time to contact Nortel Networks technical support (if necessary), and resolve the errors before you begin the upgrade.
  • Page 214 Performing RAID maintenance Standard 1.0 Timing and checklist The following table provides general time estimates for completing the steps in this procedure: Approximate time to Task complete Check ❒ Check the status of the RAID 5 minutes system. ❒ Check the consistency of the 30 minutes per drive pair system drives.
  • Page 215 October 2002 Performing RAID maintenance RAID system pack locations and identifications The following tables display information required to identify RAID system packs. 702t RAID system The table below indicates the proper hard drive bay, channel, and ID configurations. Note: SCSI ID 2 is reserved for the SCSI tape drive. SCSI System Hard drive bay...
  • Page 216 Performing RAID maintenance Standard 1.0 6. Disconnect the dead hard drives. To check the status of the RAID system All the drives configured in the RAID controller must be operating and online. If any of the system drives are in the critical state, the RAID splitting procedure will not work and data loss can occur if it is used.
  • Page 217 October 2002 Performing RAID maintenance ➝ 3 From the DAC Administration Utility window, select Configuration System Drive Information. Result: The System Drive Information dialog box appears. 4 Check that all system drives are in the online state. If any system drives are not online, go to the procedure in “Resynchronizing the CallPilot server hard drives”...
  • Page 218 Performing RAID maintenance Standard 1.0 ➝ 6 From the DAC Administration Utility window, select Configuration Drive Information. Result: The Device Selection dialog box appears. 7 Verify that all the hard drives are labeled ONL (online state). If any hard drives are in any other state, you must return them to the online state before you continue with this procedure.
  • Page 219 October 2002 Performing RAID maintenance To check the consistency of the system drives You must verify that each pair of drives is correctly synchronized before continuing with the RAID splitting procedure. To verify that the drives are correctly synchronized, use the DAC Administration Utility to run a consistency check on each system drive that is configured, as follows: ➝...
  • Page 220 The results should show that the consistency check is OK. Note: If the consistency check is not OK, stop this procedure and contact Nortel Networks technical support to correct the problem. 4 Click OK. Result: You return to the Consistency Check dialog box.
  • Page 221 October 2002 Performing RAID maintenance 6 After all hard drives have been checked, click OK in the Consistency Check dialog box to return to the DAC Administration Utility window. Then exit the DAC Administration Utility. To complete the upgrade readiness checklist Follow the instructions in Part 4, Chapter 1 of Upgrading or Installing CallPilot Server Software in the CallPilot Installation and Configuration binder.
  • Page 222 Performing RAID maintenance Standard 1.0 6 Select Backup/Restore conf, and then press Enter. Result: A cautionary message appears. 7 Press any key to acknowledge the cautionary message. Result: The system displays the Backup and Restore Configuration submenu. 8 Select Backup Configuration, and then press Enter. Result: The system displays the Enter File Name pop-up window.
  • Page 223 October 2002 Performing RAID maintenance To mark the hard drives dead Each system drive is made up of a pair of drives that are mirror images of each other. To break the mirroring so that one of the drives of each pair is no longer updated, you must mark one drive dead in each pair.
  • Page 224 Performing RAID maintenance Standard 1.0 4 Press Enter to continue with the process of marking the drive dead. Result: A confirmation prompt appears in the bottom right corner. 5 Select YES, and then press Enter to mark the drive dead. Result: The screen is updated to record that the drive has been marked dead (DED).
  • Page 225 October 2002 Performing RAID maintenance 6 Repeat steps 3 to 5 for drives B-1 and C-1. 7 Press Esc to return to the main menu. 8 Press Esc to exit the DAC960 Configuration Utility. Result: A prompt appears in the bottom right corner of the screen asking you to confirm that you want to exit.
  • Page 226 Performing RAID maintenance Standard 1.0 To disconnect the dead hard drives Physically disconnect the hard drives marked DED to ensure that these hard drives are not updated during the upgrade and are preserved as a backup. 1 Shut down and power off the CallPilot server. 2 Disconnect the hard drives marked DED by disconnecting the SCSI cable for channel 1 from the RAID card.
  • Page 227 October 2002 Performing RAID maintenance Tape drive CD-ROM IDE 1 IDE 0 Wide SCSI Narrow SCSI RAID card Channel 0 Channel 1 Note 1: A "T" indicates a wide active terminator. Note 2: The CD-ROM is connected to IDE 0. G100812 3 Power up the server.
  • Page 228 Performing RAID maintenance Standard 1.0 Performing the CallPilot server software upgrade You can now perform the upgrade operation, and only one disk of each pair will be updated. This allows you to maintain a copy of the system in its previous state in case there are problems during the upgrade process.
  • Page 229 October 2002 Performing RAID maintenance Resynchronizing the CallPilot server hard drives After you upgrade the server software and test the upgrade, follow the steps below to resynchronize the hard drives. To resynchronize the hard drives 1 Shut down and power off the CallPilot server. 2 Reconnect the hard drives by reconnecting the SCSI cable for channel 1.
  • Page 230 Performing RAID maintenance Standard 1.0 6 From the Management menu, select Rebuild Drive. Result: The Device Selection dialog box appears. 7 Start from the left side of the dialog box and click the first dead drive (marked DED) to start rebuilding that drive. Result: The Rebuild Progress dialog box appears.
  • Page 231 October 2002 Performing RAID maintenance If you are running the DAC Monitor program, the monitor window pops up and informs you of the progress of the rebuild. When the rebuild finishes (each drive takes up to 45 minutes), a dialog box appears to inform you that the rebuild is complete.
  • Page 232 Performing RAID maintenance Standard 1.0 3. Enable the pre-upgrade hard drives and restore the pre-upgrade software. To mark the failed upgrade hard drives dead 1 Insert the CallPilot 2.0 OS Recovery or OS Upgrade CD into the CD-ROM drive, and then power up the computer. Note: For this procedure to work, the computer BIOS must have booting from CD-ROM enabled.
  • Page 233 October 2002 Performing RAID maintenance The left side of the screen displays the six physical hard drives in the server. The drives form three packs: A, B, and C. Each pack consists of two drives: A-0 and A-1, B-0 and B-1, C-0 and C-1. Drives A-0, B-0, and C-0 should be ONL.
  • Page 234 Performing RAID maintenance Standard 1.0 7 Press Enter to continue with the process of marking the drive dead. Result: A confirmation prompt appears in the bottom right corner of the screen. 8 Select YES, and then press Enter to mark the drive dead. Result: The screen is updated to record that the drive has been marked dead (DED).
  • Page 235 October 2002 Performing RAID maintenance 9 Repeat steps 6 to 8 for drives B-0 and C-0. Result: All hard drives are marked dead (DED). 10 Press Esc until you exit the utility. Note: Leave the CallPilot 2.0 OS Recovery CD-ROM or the CallPilot 2.0 OS Upgrade CD-ROM in the CD-ROM drive.
  • Page 236 Performing RAID maintenance Standard 1.0 To enable the pre-upgrade hard drives and restore the pre-upgrade software CAUTION Risk of lost or corrupted data All hard drives must be dead (DED) before you begin this procedure. If you are not sure if all the hard drives are dead, see “To mark the failed upgrade hard drives dead”...
  • Page 237 If this is not correct for your system, contact Nortel Networks technical support. 7 Press Enter to continue. Result: A confirmation prompt appears in the bottom right corner of the screen.
  • Page 238 Performing RAID maintenance Standard 1.0 9 Repeat steps 6 to 8 for drives B-1 and C-1. 10 Before continuing, verify that drives A-0, B-0, and C-0 are dead (DED), and drives A-1, B1, and C-1 are online (ONL), as in the following example: 11 Press Esc to return to the main menu.
  • Page 239 October 2002 Performing RAID maintenance 17 Test the CallPilot system. See the chapter “Testing the CallPilot installation” in Part 3 of the CallPilot Installation and Configuration binder. Part 5: 702t Server Maintenance and Diagnostics...
  • Page 240 Performing RAID maintenance Standard 1.0 CallPilot...
  • Page 241: Replacing Or Adding Voice Processing Boards

    C h a p t e r 1 0 Replacing or adding voice processing boards In this chapter DSP numbering and location SCbus cabling Replacing or adding MPC-8 cards Replacing or adding MPB16-4 boards Part 5: 702t Server Maintenance and Diagnostics...
  • Page 242: Dsp Numbering And Location

    Replacing or adding voice processing boards Standard 1.0 DSP numbering and location Introduction DSPs are the voice processing components of the MPC-8 card and the MPB16-4 board. The DSPs are numbered to distinguish each DSP in CallPilot maintenance programs such as the Maintenance Admin applet in CallPilot Manager.
  • Page 243 October 2002 Replacing or adding voice processing boards First MPB16-4 DSP 3 DSP 4 DSP 5 DSP 6 G101756 Second MPB16-4 DSP 9 DSP 10 DSP 11 DSP 12 G101757 Part 5: 702t Server Maintenance and Diagnostics...
  • Page 244: Scbus Cabling

    Replacing or adding voice processing boards Standard 1.0 SCbus cabling Introduction The SCbus cable supports the voice bus for CallPilot servers that use MPB16-4 boards. It is connected to the MPB16-4 boards in the CallPilot server. Supported SCbus cable A 2-drop SCbus cable (NTRH2011) is provided. The number of connectors (two) corresponds to the maximum number of MPB16-4 boards supported on this server.
  • Page 245: Replacing Or Adding Mpc-8 Cards

    October 2002 Replacing or adding voice processing boards Replacing or adding MPC-8 cards Introduction This section describes how to replace or install an MPC-8 card. For help with identifying DSPs, see “DSP numbering and location” on page 242. MPC-8 card (NTRH01AA) The MPC-8 card is a credit-card-sized PC card that plugs into an MPB16-4 board.
  • Page 246 Replacing or adding voice processing boards Standard 1.0 Before you begin CAUTION Risk of electrical damage Wear an antistatic ESD wrist strap when handling cards or boards, or when working inside the server. Do not touch the components or gold-edge connectors of cards or boards.
  • Page 247 Note: If the card is placed upside down or label side down, it will not slide completely into the bay. Do not force the card in. If you cannot install the card, contact Nortel Networks for a replacement card. 3 Replace the server cover.
  • Page 248 Replacing or adding voice processing boards Standard 1.0 multimedia channels, add the new DNs or update the media allocation as required, or both. Result: The MPC-8 card installation procedure is completed. 8 Test the multimedia channels to ensure the new MPC-8 card is functioning properly.
  • Page 249: Replacing Or Adding Mpb16-4 Boards

    October 2002 Replacing or adding voice processing boards Replacing or adding MPB16-4 boards Introduction This section describes how to replace or add MPB16-4 boards. MPB16-4 (NTRH20BA) The following picture shows an MPB16-4 board with no optional MPC-8 cards installed. DS30X SCbus connector connector Part 5: 702t Server Maintenance and Diagnostics...
  • Page 250 Replacing or adding voice processing boards Standard 1.0 Before you begin CAUTION Risk of electrical damage Wear an antistatic ESD wrist strap when handling cards or boards, or when working inside the server. Do not touch the components or gold-edge connectors of cards or boards.
  • Page 251 October 2002 Replacing or adding voice processing boards 3 Disconnect the DS30X cable from the faceplate of the faulty MPB16-4 board. 4 Remove the faulty MPB16-4 board from its slot, and save the retaining screw. 5 Remove any optional MPC-8 cards from the faulty MPB16-4 board, and install the cards in the new MPB16-4 board.
  • Page 252 Replacing or adding voice processing boards Standard 1.0 To install an additional MPB16-4 board DANGER Risk of electrical shock Ensure the server is powered down and the AC power cords are disconnected, as described in “Before you begin” on page 250.
  • Page 253 October 2002 Replacing or adding voice processing boards 11 Reconnect the peripheral devices. If you need additional instructions, refer to Part 2 of the CallPilot Installation and Configuration binder. 12 Reconnect the power cables to the server and to the peripheral devices. 13 Restart the server, and then log on to Windows NT.
  • Page 254 Replacing or adding voice processing boards Standard 1.0 CallPilot...
  • Page 255: Replacing Network Cards

    C h a p t e r 1 1 Replacing network cards In this chapter Maintaining the onboard network card Replacing the CLAN card Part 5: 702t Server Maintenance and Diagnostics...
  • Page 256: Maintaining The Onboard Network Card

    Replacing network cards Standard 1.0 Maintaining the onboard network card Onboard network card If the onboard network card fails, it cannot be replaced by an add-in network card in the expansion slots. Contact Nortel Networks technical support for assistance. CallPilot...
  • Page 257: Replacing The Clan Card

    October 2002 Replacing network cards Replacing the CLAN card Introduction The CLAN card is an expansion card installed in a PCI slot. A CLAN network is required to support Unified Messaging applications. To replace the CLAN card 1 Power down the server. 2 Unplug the AC power cord.
  • Page 258 Replacing network cards Standard 1.0 12 Stand the server up and replace the chassis covers. 13 Plug in the AC power cord. 14 Power up the server. 15 Remove the old network card driver if appropriate. 16 Install the network adapter software. 17 Optimize the binding order.
  • Page 259: Replacing Dimms And The Cpu

    C h a p t e r 1 2 Replacing DIMMs and the CPU In this chapter Replacing baseboard DIMMs Replacing the CPU Part 5: 702t Server Maintenance and Diagnostics...
  • Page 260: Replacing Baseboard Dimms

    DIMMs 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 platform you are using. Before you begin Before you remove baseboard DIMMs, power down the server and remove the side panel.
  • Page 261 DIMMs are keyed and can be inserted in only one way. Also 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.
  • Page 262: Replacing The Cpu

    Replacing DIMMs and the CPU Standard 1.0 Replacing the CPU Introduction The CPU is an Intel Pentium II processor running at up to 450 MHz. The baseboard has two single-edge connectors (SEC) for two Intel Pentium II processors. You can upgrade the CPU in the future. For dual CPU servers Each release of a processor model is accompanied by a stepping number (or version number).
  • Page 263 October 2002 Replacing DIMMs and the CPU To remove the existing CPU CAUTION Risk of equipment damage Take precautions to protect computer boards. Electrostatic discharge (ESD) can render boards damaged or unusable. Wear an ESD wrist strap. 1 Power down the server and remove the side cover. DANGER Risk of personal injury If the system has been running, any installed processor and...
  • Page 264 Replacing DIMMs and the CPU Standard 1.0 CallPilot...
  • Page 265: Ssu And Bios

    C h a p t e r 1 3 SSU and BIOS In this chapter Overview Backing up the BIOS and SSU upgrade disks Recovering the BIOS Crisis recovery Upgrading and configuring the BIOS SSU overview Configuring your system using SSU Part 5: 702t Server Maintenance and Diagnostics...
  • Page 266: Overview

    BIOS has a corresponding SSU release. The proper SSU floppy disk is identified by the Intel software version number. All systems configured by Nortel Networks manufacturing are shipped with at least the minimum vintage BIOS and corresponding SSU. However, new BIOS may be issued to fix discovered bugs or to support new hardware standards and options.
  • Page 267: Backing Up The Bios And Ssu Upgrade Disks

    October 2002 SSU and BIOS Backing up the BIOS and SSU upgrade disks Introduction Since the SSU software holds server configuration for individual systems, make a backup copy of the BIOS and SSU upgrade software. Before you begin Before you can back up the BIOS/SSU upgrade, you must have the BIOS and SSU upgrade software on a floppy disk.
  • Page 268: Recovering The Bios

    BIOS recovery disk. To recover the BIOS 1 Insert the BIOS recovery disk in drive A. Note: The disk is shipped with the server. Call your Nortel Networks customer support representative if you need a disk. 2 Power up the server.
  • Page 269 October 2002 SSU and BIOS 7 Restart the system. Result: The system displays a message that the CMOS area has been cleared when the operation is complete. 8 Power down the server. 9 Move the CMOS Clear jumper to the Protect position (from pins 2-3 to pins 1-2).
  • Page 270: Crisis Recovery

    SSU and BIOS Standard 1.0 Crisis recovery To recover from a corrupted CMOS 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 these steps: 1 Power down the server.
  • Page 271 (normal BIOS). Note: Recovery mode requires a memory DIMM module in the first socket. 4 Insert the Nortel Networks 702t BIOS disk in drive A. 5 Power up the server. Note: During this process, video is not initialized. Result: A high-pitched beep tone announces the start of the recovery process.
  • Page 272: Upgrading And Configuring The Bios

    Standard 1.0 Upgrading and configuring the BIOS BIOS update availability Obtain BIOS upgrades from your Nortel Networks distributor. BIOS upgrade floppy disk You must perform the Intel server BIOS upgrade using a bootable floppy disk. This disk must load the MS-DOS extended memory driver, himem.sys.
  • Page 273 October 2002 SSU and BIOS 3 Power up the server. Result: The upgrade process starts automatically following the system startup. 4 Follow the instructions, depending on which version of the BIOS is currently installed on the target machine. 5 Power down the server after the update process is complete. 6 Remove the BIOS update disk from the drive.
  • Page 274 SSU and BIOS Standard 1.0 To configure the BIOS 1 Power up the server. Result: The system displays server startup messages. 2 Press F2 to display the Setup screen. 3 Press BIOS Default (F9) to load the default BIOS settings. 4 Ensure the BIOS settings are set to the following values: Setting Set To...
  • Page 275: Ssu Overview

    October 2002 SSU and BIOS SSU overview Introduction The System Setup Utility (SSU) configures computer systems with ISA and PCI cards. Purpose of the SSU The SSU automates the configuration process for systems, maintains system parameters, and stores those parameters in non-volatile RAM. If the SSU is used to assign all system resources, there should be no conflicts between adapter cards.
  • Page 276 SSU and BIOS Standard 1.0 SSU upgrade floppy disk The SSU must be run from a bootable floppy disk. This disk must load the MS-DOS extended memory driver, as well as a mouse driver. To make the SSU disk bootable 1 From the C:\>...
  • Page 277: Configuring Your System Using Ssu

    SSU and BIOS Configuring your system using SSU Introduction To run the SSU, restart your system using the Nortel Networks 702t Meridian Application Server System Setup Utility disks (Version 3.0). There are three disks. To configure the system using SSU 1 Reboot the CallPilot server from the SSU Version 3 floppy disk.
  • Page 278 SSU and BIOS Standard 1.0 4 Press Enter. Result: The System Setup Utility window appears. Note: You may have a later version of the SSU. The menus can differ slightly, but the steps are the same. The box on the left describes the Available Tasks, and the box on the right provides help on the highlighted task.
  • Page 279 October 2002 SSU and BIOS 6 You can move the Boot Device Priority item up and down by using the Move Up (+) or Move Down (-) buttons. Arrange the Boot Device Priority in the following order: Removable Devices, Hard Drive, 8XX SCSI CD-ROM Symbios, ATAPI CD-ROM, and LANDesk.
  • Page 280 SSU and BIOS Standard 1.0 10 To change the IRQ of a PCI card, double-click that card (for example, the network card). A submenu appears. Double-click within the IRQ window within the PCI board window. Result: The Change IRQ window appears. CallPilot...
  • Page 281 October 2002 SSU and BIOS 11 Set the IRQ using the pull-down menu, and then press + Add/Change. Result: You have completed changing the IRQ. 12 Click OK. Result: The resource window appears. 13 To add an ISA card (such as a DSE card), click Define ISA card. Result: The Define ISA Card window appears.
  • Page 282 SSU and BIOS Standard 1.0 The following table shows the Resource List with the IRQs: Resource Baseboard: System Board Timer Baseboard: System Board Keyboard (may be listed as Chipset) Unused Baseboard: System Board Serial Port 2 (COM 2) Baseboard: System Board Serial Port 1 (COM 1) PCI Card: Bus 00 Dev 0C Reserved for connections cards...
  • Page 283 October 2002 SSU and BIOS Resource PCI Card: Bus 00 Dev 0C Multifunction Controller - SCSI Controller PCI Card: Bus 00 Dev 12 Multifunction Controller - USB Controller 18 Click Add/Change in the IRQ sub-window. 19 Click Close in the define ISA card window. 20 To end, click Close, or continue to add cards as needed.
  • Page 284 SSU and BIOS Standard 1.0 CallPilot...
  • Page 285: 702T Reference Material

    A p p e n d i x A 702t reference material In this chapter Server features Rear panel diagram and slot locations Slot assignments IRQ mapping table Part 5: 702t Server Maintenance and Diagnostics...
  • Page 286: Server Features

    702t reference material Standard 1.0 Server features Introduction This section provides a general overview of the 702t server. Server dimensions Height 49 cm (19.3 in.) Width 21 cm (8.3 in.) (chassis), 25 cm (10 in.) with feet Depth (distance from front to back) 45 cm (17.75 in.) Clearance front 21.59 cm (8.5 in.) Clearance rear...
  • Page 287 October 2002 702t reference material Front panel features This diagram shows the front panel features of the 702t server. G100823 This table describes the details shown in the preceding diagram. Part Function 1. Backup tape drive Allows backup of hard drive data. 2.
  • Page 288 702t reference material Standard 1.0 Part Function 2c. Headphone jack Jack for audio output from CD-ROM. 3. ON/OFF push button Turns the power to server on or off. 4. Reset push button Momentarily disconnects the power to the server. Do not use for restart;...
  • Page 289: Rear Panel Diagram And Slot Locations

    October 2002 702t reference material Rear panel diagram and slot locations Rear panel diagram See “Slot assignments” on page 290 for slot assignments. AC power input Mouse connector Keyboard connector COM 2 serial port COM 1 serial port (used for modem) Monitor connector Parallel port (software...
  • Page 290: 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. Slot definition and slot numbering In these tables, the term “slot”...
  • Page 291 October 2002 702t reference material Slot assignments with RAID CallPilot-assigned Succession CSE Slot number board label Meridian 1 1000 Onboard ELAN ELAN network card Slot 5 BRD05 RAID RAID Slot 4 BRD04 CLAN CLAN Slot 3 BRD03 MPB16-4 board #2 MPB16-4 board #2 (optional) (optional)
  • Page 292 702t reference material Standard 1.0 Slot assignments without RAID CallPilot-assigned Succession CSE Slot number board label Meridian 1 1000 Onboard ELAN ELAN network card Slot 5 BRD05 Not used Not used Slot 4 BRD04 CLAN CLAN Slot 3 BRD03 MPB16-4 board #2 MPB16-4 board #2 (optional) (optional)
  • Page 293: Irq Mapping Table

    October 2002 702t reference material 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: Slot or device Timer Chipset System/unused Serial Port 2 (COM2) Serial Port 1 (COM1) For Meridian 1 or CSE 1K, available for CLAN in slot 4 as...
  • Page 294 702t reference material Standard 1.0 Slot or device Slot 5 - RAID/On-Board SCSI controllers Note: Both SCSI controllers are on IRQ 15, which allows the SSU to automatically resolve any IRQ conflict. CallPilot...
  • Page 295: Index

    Index Numerics RAID, controller card boot failure 9-pin connector what to do adapter cards for diagnostics cables – Alarm Monitor, using SCSI alarms active termination about cabling investigating Non-RAID system alert icons, component states with CD-ROM application event log RAID system definition with CD-ROM and tape drive Application Log...
  • Page 296 Index Standard 1.0 events running from Windows NT 4.0 about syntax investigating CLAN ethernet fault management replacing the card alarm notification clear the NVRAM event processing commands Maintenance page Net Start Diagnostics section Net Stop General section TSTSERIO Maintenance section commands, TCP/IP purpose using...
  • Page 297 October 2002 Index replacing tracert corrupted BIOS Diagnostics section, Maintenance page recovering Diagnostics Tool Courtesy stop, description system utility CPU servers diagnostics tool BIOS settings descriptions configuring the BIOS TCP/IP stepping number Windows NT 4.0 creating system packs DIMMs Critical Services compatibility CallPilot services motherboard...
  • Page 298 Index Standard 1.0 disconnection of hard drives. pre-upgrade resynchronization of removing hardware replacing CLAN ethernet card fault management motherboard DIMMs alarm notification installing event processing removing firmware peripherals vintage cables floppy disk RAID controller SSU upgrade RAID system front cover cabling removing system pack sizes...
  • Page 299 October 2002 Index – ipconfig default Multimedia Monitor, using IRQ mapping table nbtstat command Legend/Help tab parameters and descriptions location running from Windows NT 4.0 MPB16-4 DSP syntax MPC-8 cards Net Start command logical drive consistency Net Stop checking of Windows NT 4.0 logs Net Stop command...
  • Page 300 Index Standard 1.0 CLAN ethernet card prerequisites replacing diagnostics RAID controller RAID controller BIOS/firmware configuring minimum version ping command RAID controller card parameters and descriptions replacement of running from Windows NT 4.0 RAID controller card, BIOS options syntax RAID hard drives Power-On Self Test (POST) RAID level 1 beep codes...
  • Page 301 October 2002 Index SCSI drive removing side cover replacing server servicing requirements configuration server RAID system settings start-up diagnostics BIOS resources, troubleshooting CallPilot Administrator’s Guide 15 shutting down CallPilot Troubleshooting Reference 15 system restarting system after TSTSERIO tests side cover restrictions removing system drive size...
  • Page 302 Index Standard 1.0 restarting after TSTSERIO tests ipconfig shutting down nbtstat system configuration netstat using SSU ping system drive tracert initialize termination system event log SCSI cables definition testing system event log, viewing POST diagnostics System Info tab tracert command System Monitor parameters and descriptions Channel Monitor tab...
  • Page 303 October 2002 Index System Monitor Windows NT 4.0 Net Stop utility TSTSERIO Windows NT 4.0 Diagnostics tool descriptions vintage Windows NT Diagnostics tool BIOS BIOS and SSU weekly maintenance Windows NT Event Viewer reinstalling Part 5: 702t Server Maintenance and Diagnostics...
  • Page 304 Index Standard 1.0 CallPilot...
  • Page 306 Part 5: 702t Server Maintenance and Diagnostics Copyright © 2002 Nortel Networks, All Rights Reserved Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.

Table of Contents