Message Networking 5.2 Maintenance print guide

Transcription

1 Page 1 of 304 Maintenance print guide This print guide is a collection of system topics provided in an easy-to-print format for your convenience. Note: The links shown in this document do not work online, and some of the topics link to tasks that are not included in the PDF file. The online system contains all Message Networking documentation and is your primary source of information. This printable guide contains the following topics: Topic Page Number Performing basic maintenance 2 Performing software management 11 Viewing system configuration and status 23 Accessing Message Networking logs 36 Backing up the system 209 Generating reports 221 Running database audits 259 Performing voice equipment diagnostics 262 Changing the system's network address length 269 Changing a remote machine's mailbox number length 270 Changing the Message Networking TCP/IP network configuration 271 Restoring backed-up system files 272 Troubleshooting Message Networking 275

2 Page 2 of 304 Performing basic maintenance This topic describes how to perform the following tasks: Accessing the product ID Checking and setting the system clock Starting the messaging software (voice system) Stopping the messaging software (voice system) Shutting down the system Checking the reboot schedule Performing a system reboot

3 Page 3 of 304 Accessing the product ID The product ID is a 10-digit number used to identify each Message Networking system. You must have the product ID when you are contacting your remote maintenance service center. To access the product ID: 1. On the Message Networking administration Web interface, under Alarming, click Alarm Configuration. The system displays the Configure Alarms page. 2. Record the product ID for use with the remote maintenance center.

4 Page 4 of 304 Checking and setting the system clock The Message Networking system uses the Linux system clock to perform certain time-dependent tasks, such as performing the nightly backup of critical system data. The clock is set during system installation, but you should check it again during initial system administration to ensure that it was set correctly. The Linux system clock can be set manually or it can be synchronized to a Network Time Protocol (NTP) server. If the system clock is set manually, you should check the time on a monthly basis and whenever a daylight savings time change occurs. When you set the system time for the Message Networking system manually, you set both the Linux system clock and the onboard (hardware) real-time clock. Use the following procedures to set the date and time on the Message Networking server manually or to administer an NTP server to be the source for the system date and time. To set the date and time manually: 1. On the Message Networking administration Web interface, under Server Administration, click Date/Time/NTP Server. The system displays the Administer Linux Date and Time page. For information about the fields on this page, click Help. 2. Select the Manual radio button and check the date and time information. 3. Correct any date and time inaccuracies. For more information, click any of the fields or Help. 4. Click Save. 5. Verify that the system confirms the date and time change occurred successfully. If the change occurred successfully, the system logs a message in the Server Events log about the changes. The system does not reset all processes to the new date and time until the system is restarted. To administer an NTP server: 1. On the Message Networking administration Web interface, under Server Administration, click Date/Time/NTP Server. The system displays the Administer Linux Date and Time page. For information about the fields on this page, click Help. 2. Select the NTP Time Server radio button. 3. In the NTP Time Server field, enter the Fully qualified Domain Name or IP address of the NTP server. 4. Click Add NTP Server. 5. Click Save. 6. Verify that the system confirms the change occurred successfully. If the change occurred successfully, the system logs a message in the Server Events log about the changes. The system does not reset all processes to the new date and time until the system is restarted. To delete an NTP server: 1. On the Message Networking administration Web interface, under Server Administration, click Date/Time/NTP Server. The system displays the Administer Linux Date and Time page. For information about the fields on this page, click Help. 2. Select the NTP server you want to delete. 3. Click Delete NTP Server. 4. Select or administer a different NTP server or set the system time manually. 5. Click Save.

5 Page 5 of Verify that the system confirms the change occurred successfully. If the change occurred successfully, the system logs a message in the Server Events log about the changes.

6 Page 6 of 304 Starting the messaging software (voice system) To start the messaging software: 1. On the Message Networking administration Web interface, under Utilities, click Start Messaging. The system displays the Start Messaging Software page and begins to start the messaging software and displays numerous system messages. 2. Verify that the system displays the following message (you might have to scroll down to the bottom of the page): Startup of the Voice System is complete. End: start_vs Day Month Day Time Time Zone Year

7 Page 7 of 304 Stopping the messaging software (voice system) Caution: Stop the voice system only when it is absolutely necessary. To stop the messaging software: 1. On the Message Networking administration Web interface, under Utilities, click Stop Messaging. The system displays the Stop Messaging Software page. 2. Enter a number between 0 and 600 in the Wait Time field. The wait time designates how many seconds the system is to wait for calls in progress to finish before stopping the voice system. New calls are prevented immediately regardless of the wait time selected. If any calls are still in progress after this time, they are dropped, and the system proceeds with stopping the voice system. A wait time of zero indicates an indefinite wait time until all current calls are completed. 3. Click Stop. The system displays the following message at the top of the page when the messaging software has completely stopped: The Stop Voice System info: Stop of voice system completed. Note: When the voice system is stopped, the user cannot make changes to the Message Networking administration screens. You must restart the voice system to make changes to the Message Networking administration screens.

8 Page 8 of 304 Shutting down the system To shut down the system: 1. On the Message Networking administration Web interface, under Utilities, click Shutdown Server. The system displays the Shutdown Server page. 2. In the Wait Time field, enter a number between 0 and 600. This time designates how many seconds the system is to wait for calls in progress to finish before stopping the voice system. The system prevents new calls immediately regardless of the wait time selected. If any calls are still in progress after this time, the system drops the calls and proceeds with stopping the voice system. A wait time of zero indicates an indefinite wait time until all current calls are completed. 3. Click Shutdown. The following message displays: "The system is going to be rebooted. You will lose your access to this system after this action takes place. Are you sure you want to do this?" 4. Click OK. Some messages might appear as the system shuts down: "Stopping voice system...shutting down system." When the system displays the above message, the system is completely shut down.

9 Page 9 of 304 Checking the reboot schedule Note: Avaya recommends that you reboot the Message Networking system at least once every 180 days. The reboot refreshes Linux resources and keeps applications running reliably. The Message Networking system keeps track of the reboot schedule and advises when to perform the next reboot. To check the reboot schedule for the date of the next recommended reboot: 1. On the Message Networking administration Web interface, under Server Information, click Reboot Interval. The system displays the Reboot Interval page. For more information about the fields on this page, click the Help button. 2. Check the information on the screen for the best date to reboot the system. 3. If you need to reboot the system, continue with Performing a system reboot. 31 July, 2009

10 Page 10 of 304 Performing a system reboot This topic describes how to reboot the system from the console or, if you have the ability to access your system remotely, from a web browser inside your intranet firewall, or through PPP connection outside your firewall. A complete server reboot takes approximately 15 minutes to complete. Note: Avaya recommends that you reboot the Message Networking system at least once every 120 days. The reboot refreshes Linux resources and keeps applications running reliably. Caution: You cannot reboot your system if a backup is running. Automatic backups normally occur at 3:05 a.m., so avoid rebooting the system between 2:30 a.m. and 4:00 a.m. To perform a reboot: 1. On the Message Networking administration Web interface, under Utilities, click Reboot Server. The system displays the Reboot Server page. 2. In the Wait Time (in seconds) field, enter a time in seconds between 0 and 600. This time designates how many seconds the system is to wait for calls in progress to finish before stopping the voice system. The system prevents new calls immediately regardless of the wait time selected. If any calls are still in progress after this time, the system drops the calls and proceeds with stopping the voice system. A wait time of zero indicates an indefinite wait time until all current calls are completed. 3. Do one of the following: If no error messages appear, continue with Step 4. If the system displays an error message that a backup is running, the system does not proceed with the reboot. Instead, follow the instructions of the error message. 4. Click Reboot. The system displays the following message: "The Voice System is now stopping. Rebooting system..." The system then shuts down and reboots automatically. A reboot takes approximately 5 minutes. 5. Do one of the following: If you are performing the reboot from a remote location by using a dial-up connection, you are automatically disconnected from the Message Networking system and need to reconnect to the system after the reboot is complete. Do the following: Reconnect to the Message Networking system. Log in to the system. If you are performing the reboot from a console, when you see a message display that the system is being rebooted, click OK. Some messages can appear and remain on the screen, depending on the software modules that you have installed on your system. The system begins the system restart. During the restart, login prompts display. Do not log in at these prompts as the system is not ready. Note: If FAIL appears in the status column for any component, do the following: Record the name of the component. Access the Alarm Log. When the system displays the message "ICHG Module Started," press Enter and then log in to the system.

11 Page 12 of 304 Performing software management This procedure provides information on performing software management. Software management includes the following tasks: Updating system software via DVD Updating system software using downloaded service packs Adding software packages Installing system software on an existing system Removing software packages Viewing installation/removal logs Viewing a list of the software installed Viewing a detailed list of the high-level software packages installed Ejecting the backup medium

12 Page 13 of 304 Upgrading system software using a media You can use the Message Networking's software upgrade function to upgrade the system software to the latest release of Message Networking. If you just performed a new system installation, you do not need to perform an upgrade. Note: Media could be either a CD or a DVD. This procedure requires the Avaya Message Networking Operating System media and the Avaya Message Networking Application software (includes Languages software) media. Software updates (service packs) are also available for download from the Avaya Support Centre at For information on updating a Message Networking system using downloaded service packs, see Updating system software using downloaded service packs. Upgrading the system software requires a system restart. Plan to do the installation during low usage hours. Notes: You can only use this procedure if you are upgrading from Message Networking Release 3.1 to Message Networking Release 5.2, on the same hardware platform. You cannot use this procedure if you are changing to a different hardware platform. For information on supported upgrades, see Upgrading to Message Networking Release 5.2. Complete the following steps to upgrade the system: 1. Log in to the system. 2. Install the Pre-upgrade and Backup Verification tool (PUBVT) and run the Pre-upgrade tool. 3. Stop the messaging software (voice system). Stopping the system is highly recommended but not required. 4. Perform an attended system backup of the Message Networking system. 5. Insert the latest Message Networking Operating System media into the CD/DVD drive. 6. In the Administration menu, under Software Management, click Software Update. 7. In the Software Update page, click CD/DVD. Note: The system displays a warning if you have not backed up your system. If you want to back up your system, click Cancel and perform an attended system backup. If you want to proceed without a backup, click Continue without current system backup. If you select to proceed without a backup, wait for the status indicator that the system displays in the upper-right corner of the browser. The system displays a list of packages available on the media or any newer versions of the Message Networking software available. 8. Select the packages you want to install, and click Install selected packages. The system displays a list of packages to be installed. 9. Verify the list that the system displays. If you need to change the list, click Back on the browser toolbar, and select or clear packages. Then click Install Selected Packages. 10. Click Proceed with Update. The system begins the upgrade and displays status messages. The upgrade is complete when the pointer changes from an animated pointer to a pointer. 11. After the upgrade is complete, remove the Message Networking Operating System media from the CD/DVD drive. 12. Scroll down to see the bottom of the status page, and click Update software from other media. 13. Insert the Message Networking Application software (includes Languages software) media into the CD/DVD drive. 14. Repeat steps 7 to After the upgrade is complete, scroll down to see the bottom of the status page, and click Reboot. Remove the Message Networking Application software (includes Languages software) media from the

13 Page 14 of 304 CD/DVD drive. Note: If you want to install additional software packages, such as language software, click Update software from other media. To install the language software, insert the Message Networking Application software (includes Languages software) media into the CD/DVD drive. 16. After the system reboots, log in again. 17. When you try to log in to the Message Networking Web administration page, you get an alert to add the certificate as an exception for the browser. In the Alert dialog box, click Ok. 18. In the Secure Connection Failed dialog box, click Or you can add an exception... link 19. Click Add Exception In the Add Security Exception dialog box, click Get Certificate. 21. Click Confirm Security Exception. The system displays the Message Networking Web administration page. 22. The upgrade is complete. Test system features by creating test messages and checking subscriber information.

14 Page 15 of 304 Updating system software using downloaded service packs This procedure provides steps for downloading service pack software from Avaya's support site and performing a software update on the Message Networking system. Updating the system software requires a system restart. Plan to do the installation during low usage hours. Download the software update Complete the following steps to update the system: 1. Download the Message Networking software update from the Avaya Support site: a. Go to and then navigate to the Message Networking page. b. Access the software downloads area. c. Select the software update you want to download. d. When prompted whether you want to open the file or save it, click Save. e. Specify a destination for the downloaded software. f. Click Save. 2. Upload the software to the Message Networking system: a. From the Message Networking Administration menu, select Software Management > Software Upload. b. In the Path to Package File field, type the path for the downloaded software, or click Browse to navigate to the path of the downloaded software and click Open. c. Click Upload Software. 3. Complete the procedure to install the downloaded software. Install the downloaded software Complete the following steps to install the downloaded software: 1. Log in to the system. 2. Stop the messaging software (voice system). Stopping the system is highly recommended but not required. 3. Perform an attended system backup of the Message Networking system. 4. In the Administration menu, under Software Management, click Software Update. 5. In the Software Update page, click Service Pack Note: The system displays a warning if you have not backed up your system. If you want to back up your system, click Cancel and perform an attended system backup. If you want to proceed without a backup, click Continue without current system backup. If you select to proceed without a backup, wait for the status indicator that the system displays in the upper-right corner of the browser. The system displays a list of packages to be installed. 6. Verify the list that the system displays, and click Proceed with Update. The system begins the update and displays status messages. The update is complete when the pointer changes from an animated pointer to a pointer. 7. After the update is complete, scroll down to see the bottom of the status page. 8. If the software was installed successfully, click Reboot. Note: You can also click Install more software to install additional software packages, such as language

15 Page 16 of 304 software. 9. After the system reboots, log in again. The update is complete. 10. Test system features by creating test messages and checking subscriber information.

16 Page 17 of 304 Adding software packages Additional software packages, such as languages or switch connection software, can be installed from the system DVD. Most software installations require the voice system to stop. Plan to do the installation during low usage hours. 1. Start at the Administration menu and select Software Management > Software Installation. 2. Click CD/DVD. Note: The system displays a warning if you have not backed up your system. If you want to back up your system, click Cancel and perform a system backup. If you want to proceed without a backup, click Continue without current system backup. If you select to proceed without a backup, wait for the status indicator that the system displays in the upper-right corner of the browser. The system displays a list of packages available on the DVD. 3. Select the package you want to install, and click Install selected packages. The system displays a list of packages to be installed. 4. Review the list, and then click Proceed with installation. The system begins the installation and displays installation status messages. The installation is complete when the pointer changes from an animated pointer to a pointer. After the software is installed, scroll down to see the bottom of the status page. 1. If the software was installed successfully, remove the DVD from the CD/DVD drive. 2. Click Reboot Note: You can also click Install more software to install additional software packages. 3. After the system restarts, log in to the system. 4. On the Message Networking administration Web interface, under Utilities, click Start Messaging.

17 Page 18 of 304 Installing system software (Operating System and Application) Message Networking is shipped from the factory with the latest software. However, you can use this procedure if you need to install the software (Operating System and Application) on a new or existing system. Preparation If you are installing on an existing system or cutting over an existing machine, plan to do the installation during low usage hours. If you are installing on an existing system, verify that you have a backup of the system information. For more information, see Backing Up System Files (Attended). Determine the following information for the Message Networking system, either through account worksheets or your project manager: System name IP address, domain, DNS. This information must be provided by the customer. Switch integration information, as applicable, such as extension numbers. Installing the software 1. Insert the Message Networking Release 5.2 Operating System media into the CD/DVD drive. Note: A media could be either a CD or a DVD. 2. Shut down and restart the machine. If possible, select Reboot Server under the Utilities menu, press Ctrl+Alt+Del to restart the system. As the machine starts up, you see an Avaya splash screen and then a screen with a boot: prompt. 3. At the boot: prompt, type the appropriate install command: If you are installing Message Networking on an S3210R server, type rack and press Enter. If you are installing Message Networking on an S3500 Basic server, type basic2u and press Enter. If you are installing Message Networking on an S3500-H server, type high2u and press Enter. If you are installing Message Networking on an S8800 2U server, type highibm and press Enter. Note: Type the appropriate install command for a server. For example, if you are installing Message Networking on an S8800 2U server, type 'highibm'. If you enter a command other than 'highibm', installation process completes successfully. However, when you reboot the system, the system displays a network connectivity error message. To correct the network connectivity issue, you must perform the installation process again on the S8800 2U server. 4. Wait 15 to 20 minutes for installation to complete. The system displays the message: Remove any installation media (CD-ROM) used during the installation process and press the "Reboot" button to reboot your system. 5. Remove the install media as soon as the drawer opens. Do not leave the install media in the CD/DVD drive, or the system will boot from it again. 6. Click Reboot. Note: If you accidentally allow the system to reboot with the media still in the drive, wait until you get to the install screen, and then eject the media. Press Ctrl+Alt+Del to restart the system.

18 Page 19 of 304 The CD/DVD drawer closes and the system begins to reboot. As the system boots up for the first time, the system displays the Time Settings screen. 7. On the Time Settings screen, use the up and down arrow keys to highlight the time zone where the system is located. 8. Use the Tab key to move to the New Time field. 9. Enter the time in HH:MM format. Note that it is a 24-hour clock. 10. Use the Tab key to move to the New Date field. 11. Enter the date in MM/DD/YY format. 12. Use the Tab key to move the cursor to the APPLY box and press Enter. 13. Use the Tab key to move to the OK box. 14. Press Enter to save the page settings. The system displays the following prompt: local host login 15. At the localhost login, type root as the login ID, and press Enter (no password is required). The system displays the # prompt. 16. Insert the Message Networking Application software (includes Languages software) media in the CD/DVD drive. Wait for the drive's light to stop flashing before you proceed. 17. At the # prompt, type/etc/autoinstall, and press Enter. 18. Press Enter again to confirm that you want to run the autoinstall process. 19. Messages ask you to change several passwords. Enter the passwords that you were provided for the logins. It is okay to ignore warnings that the passwords are too short. 20. Wait 5 to 10 minutes while the Message Networking Application software is installed. When autoinstall completes, the system displays the message: Please remove the Installation DVD from the CD drive and press <Enter>. 21. Remove the Message Networking Application software (includes Languages software) media from the CD/DVD drive, and close the drive door. 22. Press Enter to restart the system. The system begins the restart. During the restart, login prompts display. Do not log in at these prompts as the system is not ready. 23. When the system displays the message "ICHG Module Started," press Enter and then log in to the system. The installation completes. 24. Log in to the system. 25. When the system prompts you to add the certificate as an exception for the browser, complete the following actions: 1. In the Alert dialog box, click Ok. 2. In the Secure Connection Failed dialog box, click Or you can add an exception Click Add Exception In the Add Security Exception dialog box, click Get Certificate. 5. Click Confirm Security Exception. The system displays the Message Networking Web administration page. 26. The installation is complete. Continue with Logging in to the system from the console and then Setting up LAN/WAN network addressing. Install any necessary service pack updates. For more information, see Updating system software using downloaded service packs. Note: If you are reinstalling over an existing system, you must restore files from the backup you made before the install, and then perform remote updates to obtain the latest subscriber information.

19 Page 21 of 304 Removing software packages Use this procedure to remove selected software packages from the Message Networking system. Note: You cannot remove the US English language software package from the system. Software removals require the voice system to stop. Plan to do the software removal during low usage hours. To remove software: 1. Start at the Administration menu and select Software Management > Software Removal. The Software Removal page displays. 2. Check the box next to the software package or packages that you want to remove. 3. Click Submit. When you select this button, the list of selected packages to be removed is displayed for confirmation. This list is displayed in alphabetical order on the Software Removal - Confirmation page. If you are removing a language package, the following warnings might display: A warning displays that removing the package is inadvisable if the language is administered as the preferred language of any subscribers. If you are attempting to remove US English, a warning displays that the package is the default package and should not be removed. 4. Click Continue to begin removing all selected software packages or click Abort to return to the Software Management Menu without removing any software packages. If you select Continue, the interface changes to display the scrolling output of the removal process. This output can be re-examined either upon completion or at a later time through the Installation/Removal Logs Display. When the removal process is complete, its status is reported. For more information, see Software Installation Messages.

20 Page 22 of 304 Viewing the Software Management logs: Installation/Removal logs The Installation and Removal logs allow you to view information about the last three restores performed on the system. To view the Installation and Removal logs: 1. On the Message Networking administration Web interface, under Logs, click Software Management. The system displays the Software Management Logs page. 2. From the Select log to view drop-down menu, select the log option for which you want to view information: Installation/Removal Log: The system displays the information for the Installation/Removal Log option. This option displays a log of the most recent software installation, update, or removal session. For information about the page, click Help. Old Installation/Removal Log: The system displays the information for the Old Installation/Removal Log option. This option displays a cumulative log of old software installation, update, and removal sessions. Old sessions appear in this log, beginning with the most recent old session. When a new session begins, the most recent installation, update, or removal session log is moved to the beginning of this log. For information about the page, click Help. Summary of Installation/Removal of Packages: The system displays the information for the Summary of Installation/Removal of Packages option. This option displays a cumulative, detailed log of software package component installation and removal attempts. The success or failure of each attempt is recorded for each set and set member. For information about the page, click Help.

21 Page 23 of 304 Viewing installed software The Linux software installed page shows the software packages and versions that are currently installed on the Message Networking system. This topic contains the following information about viewing installed software: Viewing a list of installed software packages Viewing a list of high-level messaging server software packages in package priority order Viewing a list of installed software packages Use the Linux software installed page to show the versions of software packages that are currently installed on the system. You can also use this page to view the date and time that each software package was installed. To view the listing of software: 1. On the Message Networking administration Web interface, under Software Management, click Server Software Display. The system takes a few minutes to check the software installed on the system and displays the results in the Linux software installed page. For more information, click Help on the web-based administration page. 2. To display the date and time that each software package was installed on the system, select Display software installation time. The system displays the Linux software installed page. Viewing a list of high-level messaging server software packages in package priority order To view the detailed listing of high-level packages installed in package priority order: 1. Start at the Administration menu and select Software Management > Messaging Software Display. The system takes a few minutes to check the software installed on the system and displays the results in the High level packages installed in Priority Order page. For more information, click Help on the webbased administration page. 2. To display the software packages in alphabetical order, select Display software in alphabetical order. 3. To display the time that each software package was installed, select Display software installation time.

22 Page 24 of 304 Ejecting the backup medium To eject the backup medium using the Web-based administration pages: 1. On the Message Networking administration Web interface, under Utilities, click CD/DVD Eject. 2. Click Eject. The system ejects the backup medium.

23 Page 25 of 304 Viewing system configuration and status This topic provides information on verifying and viewing system and software information: Verifying system installation Verifying system status Viewing server status and software information Viewing and verifying CMOS settings Changing the Voice Channel Monitor refresh rate Monitoring voice channels status Verifying customer options Accessing logs

24 Page 26 of 304 Verifying system installation As part of the process of troubleshooting system problems, you can verify system installation to confirm that the system's primary software packages have been properly installed. The system information is displayed on the Verify System Installation page. The Verify System Installation page confirms that the system's primary software packages are properly installed and that a complete version of each application-specific package exists on the system. The system takes a few minutes to perform a series of background checks on the system software. The contents of each installed executable or Help file, but not data files, are checked to verify that they were unchanged during the lifetime of the system. Each of the primary software packages installed on the system is listed. Exceptions are noted in the output of this command. To access and verify system installation: On the Message Networking administration Web interface, under Software Management, click Software Verification. The system takes a few minutes to perform a series of background checks on the system software and then displays the results on the Verify System Installation page. Each of the primary software packages installed on your system is listed.

25 Page 27 of 304 Verifying system status The Server Status page displays the following information based on your system configuration on the Message Networking system: Status of each software module Status of voice system Number of ports purchased Number of ports in service Status of networking, if applicable Hours of speech purchased Hours of speech used To access and verify the system status: Start at the Administration main menu, and select Server Information > Server Status. The system takes a few minutes to run checks on the status of the system and then displays the results on the Server Status page. Interpreting the results of system status Message Networking is made up of many individual software modules. When you access the Server Status page, the system requests each module to report on its status. The following table contains the modules and explanations of related information displayed on the page. Depending on the features you purchased, the modules that you see on the Server Status page can vary from those in the table. System status of (module) mtce (maintenance) Verifications File System Capacity IPC queue Results page information Passed/Failed Passed/Failed netw (networking) Networking Up/Down AMIS Analog Networking Number of Purchased TCP/IP Ports Number of TCP/IP Port in Service On/Off number of ports number of ports vs (voice system) Voice System Up/Down Number of Purchased Voice Ports Number of Voice Ports In Service Available Hours of Speech Used Hours of Speech Potential Hours of Speech Number of Available Text-to-Speech Sessions number of ports number of ports number of hours number of hours number of hours number of sessions

26 Page 28 of 304 The Voice System module summarizes voice port and speech storage information. The following table describes this summary information in more detail. Voice System module status item Number of Purchased Voice Ports Number of Voice Ports in Service Available Hours of Speech Used Hours of Speech Maximum Hours of Speech Number of Available Text-to- Speech Sessions Definition The number of ports on the Message Networking system that are available for use. The number of ports that are actually accepting and processing calls on the Message Networking system. It is recommended that this number matches the number of purchased ports. If it does not, follow the procedure in Displaying Voice Equipment Status to identify which ports are not in service. The number of hours of speech on the Message Networking system's hard disk that are available for use. The number of hours of speech that are currently used to store voice messages and other types of messaging data. This number needs to be less than 80 percent of the purchased hours of speech. If the value listed in the report is greater than 80 percent of the purchased hours of speech, contact your sales representative to purchase additional hours of speech. The number of hours of speech left on the hard disk that can be purchased and activated. If this number is 0, additional hours of speech are needed. The number of text-to-speech sessions that are supported on the system.

27 Page 29 of 304 Viewing server status and software information The Server Status page is a dynamic, real-time page that shows information about software modules and applications running on the system. You can use the Voice Channel Monitor page to verify that channels are working properly when you are troubleshooting the system. To access and display the Server Status page: On the Message Networking administration Web interface, under Server Information, click Server Status. The Server Status page displays the following information: Status of each software module Status of networking Status of AMIS Analog Networking Status of TCP/IP networking ports Status of TCP/IP networking ports in service Number of TCP/IP ports purchased Number of TCP/IP ports in service Hours of speech available Hours of speech purchased Hours of speech used Status of voice system Number of available Text-to-Speech sessions, if applicable Note that the items displayed vary depending on your product and system configuration. 1 August, 2009

28 Page 30 of 304 Viewing and verifying CMOS settings This topic provides the following information on CMOS settings for the Message Networking system: Viewing CMOS settings Verifying CMOS settings

29 Page 31 of 304 Viewing CMOS settings This topic provides information on viewing CMOS settings for the Message Networking system. To view the CMOS settings: On the Message Networking administration Web interface, under Server Information, click CMOS Settings. The system displays the CMOS Settings page. The CMOS Settings page displays the CMOS settings for the installed CPU.

30 Page 32 of 304 Verifying CMOS settings This topic provides information on verifying CMOS settings for Message Networking. This procedure compares the current CMOS settings with the default values in the configuration file and displays any invalid settings that are detected. To verify the CMOS settings: 1. On the Message Networking administration Web interface, under Server Information, click CMOS Settings. This system compares the current CMOS settings with the default values in the configuration file and displays any invalid settings that are detected on the CMOS Settings page. 2. Click Verify CMOS Settings. The system verifies the CMOS settings of the installed CPU. 3. Scroll down to the bottom of the page and verify that the following message displays: ALL CMOS SETTINGS ARE VALID. 4. Do one of the following: If the system displays the message that the CMOS settings are valid, the settings are correct. If the system displays a message that the verification failed, note the settings that are flagged as invalid and modify them as necessary.

31 Page 33 of 304 Changing the Voice Channel Monitor refresh rate The Message Networking system automatically updates the status information provided by the System Monitor report. The default setting for the refresh rate is 5 seconds. You can adjust this interval from 1 to 30 seconds while viewing the Voice Channel Monitor. To change the automatic update interval: 1. On the Message Networking administration Web interface, under Diagnostics > Port Monitors, click Analog Monitor. The system displays the Voice Channel Monitor page. 2. Enter the new update interval in the Refresh Rate: field. The interval can be any interval between 1 and 30 seconds. 3. Click Display to view the Voice Channel Monitor status. Caution! Shortening the refresh rate consumes more system resources and could adversely affect system performance. Monitor your system after changing this interval to ensure that the system is performing well.

32 Page 34 of 304 Monitoring voice channel status You can monitor the voice channel status by setting the refresh rate to display the current voice channel status. To change the refresh rate on the Voice Channel Monitor page: 1. On the Message Networking administration Web interface, under Diagnostics, click Port Monitors > Analog Monitor. The system displays the Voice Channel Monitor page. 2. Reset the refresh rate. 3. Click Save to accept the page settings. The Message Networking system automatically updates the status information provided by the System Monitor report. The default setting for the refresh rate is 5 seconds. You can adjust this interval from 1 to 30 seconds while viewing the Voice Channel Monitor.

33 Page 35 of 304 Verifying customer options The Message Networking system has a variety of optional features. If you purchase an optional feature, you can verify that it is enabled (turned on) by checking its status on the Customer Options page. All available options, except voice port options, are activated on the S3500-H and S8800 2U servers. Only certified Avaya personnel can change options on this page, but the page can be displayed for informational purposes. If an option is turned off, the feature does not function. Note: If you require changes to the right-to-use features activated on the system, you must contact Avaya technical support. Right-to-use activations are only completed from Monday through Friday between 8 a.m. and 7 p.m., EST. Make sure you have the following information available: Business Partner name, if applicable Order Number for Message Networking. If SMTP/MIME is purchased through Modular Messaging, you also need Order Number for Modular Messaging. Remote log-in information To verify feature options: 1. Log on to Message Networking. The system displays the Administration menu. 2. On the Message Networking administration Web interface, under Messaging Administration, click Customer Options. The system displays the Customer Options (Read Only) page. The following table describes the feature options that apply to the Message Networking system. Feature option Current Maximum AMIS Nodes Aria Digital Ports Call Detail Recording (CDR) Digital Nodes ON or OFF; indicates whether remote AMIS Analog machines can be connected to the Message Networking system. If this field is set to ON, a maximum of 500 AMIS Analog nodes can be connected to the Message Networking system. Note that the total number of nodes between Octel nodes, AMIS nodes, and Digital nodes cannot exceed 500. Number of simultaneous Aria Digital sessions support on the Message Networking system. This is always set to 4 for the S3210R and S3500 Basic server, and to 16 for the S3550-H and S8800 2U servers. Indicates whether CDR is activated. ON or OFF; indicates whether remote digital machines can be connected to the Message Networking system. If this field is set to ON, a maximum of 500 digital nodes can be connected to the Message Networking system. Note that the total number of nodes between Octel nodes, AMIS nodes, and Digital nodes cannot exceed 500. ON/OFF 4 or 16 ON/OFF ON/OFF

34 Page 36 of 304 Enterprise Lists Application Number of Bridged Machines Octel Analog Nodes SMTP Ports Serenade Digital Ports TCP/IP digital ports voice_ports ON or OFF; indicates whether the Enterprise List feature is enabled on the Message Networking system. Note: The Enterprise List feature is only available on the S3550-H and S8800 2U server. Indicates whether the Message Networking system is using a hub-and-spoke or bridging configuration. When this parameter is set to 500 (the maximum), Message Networking is being used in a hub-and-spoke configuration. When this parameter is set to any number below 500, a bridging configuration is being used and this parameter specifies the number of remote machines that can be designated as a bridged machine. For the S3210R and S3500 Basic server, the default for this field is 1. For the S3550-H and S8800 2U server, the default for this field is 500. Note: If the number of systems administered as bridged machines equals the Number of Bridged Machines on the Customer Options page, you must not modify the Number of Bridged Machines parameter to reduce the number of bridged machines. If you do, the system removes the bridging from the first system you administered as a bridged machine. ON or OFF; indicates whether remote Octel Analog Networking machines can be connected to the Message Networking system. If this field is set to ON, a maximum of 500 Octel Analog Networking nodes can be connected to the Message Networking system. Note that the total number of nodes between Octel nodes, AMIS nodes, and Digital nodes cannot exceed 500. Indicates the number of simultaneous SMTP sessions supported on the Message Networking system. These sessions are shared by the SMTP/MIME and VPIM protocols. 0 or 8 for the S3210R and S3500 Basic server; 20 for the S3550-H and S8800 2U. Indicates the number of simultaneous Serenade Digital sessions supported on the Message Networking system. This feature is always set to 4 for the S3210R and S3500 Basic server, and to 16 for the S3500-H and S8800 2U. Indicates the number of simultaneous AUDIX digital sessions supported. This feature is always set to 4 for the S3210R and S3500 Basic server, and to 12 for the S3500-H and S8800 2U. Indicates the number of analog ports on the Message Networking system. For the S3210R and S3500 Basic server, this feature can be set to 0, 4, 8, or 12. The value depends on the number of 4-port voice cards installed on the S3210R and S3500 Basic server system. For the S3500-H and S8800 2U, this feature can be set to 0, 4, or 12. The value depends on whether one 4-port voice card or one 12-port voice card is installed on the S3500-H and ON/OFF 500 ON/OFF 8 or 20 4 or 16 4 or 12 0 or 12

35 Page 37 of 304 S8800 2U. This feature is set to 0 if no voice cards are installed in the system. Note: When referring to digital communication, the number of ports supported refers to the simultaneous TCP/IP sessions supported. For example, support for 12 SMTP ports indicates that the system supports a maximum of 12 simultaneous sessions shared by the SMTP/MIME and VPIM protocols. All digital communication on the Message Networking system is supported by the installed LAN card/connector.

36 Page 38 of 304 Accessing Message Networking logs The system uses a series of logs as the central collection point for information flowing from the system. These logs provide a system wide view of activities, errors, and alarms. Reviewing the logs allows a system administrator to reach a quick understanding of overall system status, leading to efficient and effective maintenance and troubleshooting. Types of logs Messages in the logs range in importance from informational to critical. The logs vary based on audience (login type) and information type. The current system uses the following logs: Administration History log: Identifies administrative events that occur on your system such as logins, reports that were run, or changes to software. See Viewing the Administration History log for more information. Alarm log: Signals a service-affecting or potentially service-affecting problem with the system. The alarm log records major, minor, and warning alarms generated by the system. The system automatically notifies a designated services support agency of all major and minor alarms by using the SAL Gateway or the modem if the system is registered with a remote service center. For more information on configuring SAL, see Configuring SAL. The customer is responsible for resolving all warning alarms. See Viewing the Alarm log for more information. Backup log: This log contains a list of all the files that were backed up, information about any errors that occurred during the operation, and whether or not the backup operation completed successfully. See Viewing the Backup log for more information. Command Line History log: This log records all commands used through the command line. For example, this log displays the login ID, shell, and actual command issued. See Viewing the Command Line History log for more information. Server Events log: Records informational messages and administration-related alarms that could require some action by the system administrator. These messages might simply log a successful nightly backup, or they could alert the system administrator that the system is low on disk space. See Viewing the Server Events log for more information. Maintenance log: Records error occurrences, error resolutions, and informational events that can help services personnel troubleshoot an alarm. See Viewing the Maintenance log for more information. Restore log: This logs contains a list of all the files that were restored, information about any errors that occurred during the operation, and whether or not the restore operation completed successfully. See Viewing the Restore log for more information. Software Management logs: Installation/Removal logs: Contains information about the installation, update, and removal of software packages. See Viewing the Installation/Removal logs for more information. Web Server log: Displays error-related information for the Web server, including the date the error occurred, an error code, an error description, and the server address. See Viewing the Web Server log for more information. Methods of alarming supported Message Networking supports four types of alarming: SNMP (Simple Network Management Protocol) - Alarm Origination can be set to SNMP. Two types of network management stations (NMSs) are supported by Message Networking: Avaya or Avaya business partner NMS known as INADS Destinations and Customer supported NMS known as OAM destinations.

37 Page 39 of 304 At least one INADS trap destination is administered on the system before the alarm origination is set to SNMP. Customers can configure there own management stations to receive traps and alarms from Message Networking. See Add a new SNMP trap destination for alarms page. See SNMP overview for more information on SNMP. Modem dialout - if you want the system to send alarm notification through a modem (RMB for the S3500- H) to the phone number specified as the modem dialout destination. Customers need to configure the modem. Alarming through Internet - if you want the system to send alarm notification through https proxy to the Avaya HTTPS servers. SAL (Secure Access Link): SAL is an Avaya serviceability solution for support and remote management of a variety of devices and products. SAL provides remote access and alarm reception capabilities. SAL uses the existing Internet connectivity of a customer to facilitate remote support from Avaya. For each type of alarming, the customer can specify: the conditions for sending an alarm notification the alarm level at which notification is sent (minor or major or both) Alarm operation The system records problems it detects in the maintenance log. The system then attempts to diagnose and isolate those problems and can send an alarm to the alarm log if it cannot correct the error automatically. The contents of the alarm log represent all of the significant problems the system detects. Therefore, it is the starting point for troubleshooting the system. The alarm log contains two types of entries: Active alarms: Indicate a current problem in the system. Resolved alarms: Show alarms that have been corrected either automatically or through a repair procedure. Three alarm levels indicate the severity of an alarm: Major alarms: Indicate problems that could affect key system components or features. For example, if more than 25% of the voice ports are out of service, a major alarm is generated. Major alarms are repairable by technicians. Minor alarms: Indicate problems that could affect full service but are not critical to system operation. For example, if a network connection occurs, a warning alarm appears. Minor alarms are repairable by technicians. Warning alarms: Indicate problems that could potentially affect system service if not resolved. For example, if the customer system administrator does not create a trusted server password and a trusted server tries to log in, a warning alarm is generated. Warning alarms are repairable by the customer. When an active alarm is corrected, its status changes from "active" to "resolved." Alarm notification Using the Web-Administration interface to view the Server Events log and the Alarm log on a daily basis is the best way to be informed of new entries. Active alarms (alarms that have not been resolved) and new entries to the Server Events log are noted on the Alarm Summary page. The Alarm Summary page shows multiple levels of alarms. The alarm level is important because it classifies problems within the system so that the most severe are worked on first. In most cases, the alarm level also marks the area between the responsibility of the system administrator (warning alarms) and the responsibility of the remote service center (major and minor alarms). The system uses the following abbreviations to identify alarm status: M: major alarm m: minor alarm

38 Page 40 of 304 w: warning alarm A: new or unviewed entries in the Server Events log none: no alarms or unviewed log entries If you see M, m, or w, look in the Alarm Log for the alarm. You could have more than one alarm on the system. If you see A, look in the Server Events log. Alarms are documented in the Alarm log and the Server Events log. Depending on the nature of an alarm, it can be documented in either the Alarm log, the Server Events log, or both logs. The system changes the value in the Alarms: field when the alarm is resolved. After you view the Server Events log, the system clears the A from the Alarms: field, even if you do not correct any reported problems. Alarm resolution (INADS only) If the customer purchases a maintenance service contract and activates the alarm origination feature, the system automatically sends major and minor alarms to a remote service center for correction. Warning alarms are not sent to a remote service center. Warning alarms must be corrected by the system administrator by using the procedures detailed in Alarms. Remote service center A modem is used to establish a point-to-point protocol (PPP) connection between the Message Networking system and an Avaya remote service center, or an alternative services support agency. The modems used are internal (RMB) for the S3500-H and external for the S3210R or S3500 Basic or the S8800 domestic (United States) systems, or external in other countries. The modem requires an external, direct telephone line or a direct inward dialing (DID) line through the telephony system. The modem uses this line to report alarms to the services support agency. The remote service center establishes a dial up connection to the modem over this same line to help maintain and troubleshoot the system. Caution! The only dial up access to the message server is through the same line that is used for alarm notification. The system cannot report any new alarms while this line is in use. The dial up connection should be used only for services support of the system, not for routine administration. See the Remote Maintenance Board (RMB) CYN23AP and CYN24AP PCI Version Release 1.0 Reference ( , 2.8 MB pdf) for more information. This document is available to certified personnel through the Avaya web site.

39 Page 41 of 304 Viewing the Administration History log The Administration History log contains information about administrative events that occur on your system. These events include information about any changes to your system, such as logins, reports that were run, or changes to software. To view the Administration History log: 1. On the Message Networking administration Web interface, under Logs, click Administration History. The system displays the Display Administration History page. 2. Complete the fields on the page. For information on completing the fields, click the field names or Help on the Web-based administration page. 3. Click Display to start the report. When the system gathers the information you specified, it displays the report.

40 Page 42 of 304 Viewing the Alarm log The Alarm log contains descriptions of all significant problems detected by the system. The Alarm log contains active alarms and resolved alarms. Resolved alarms are alarms that were corrected either automatically or by repair procedures. To view a list of potential alarms, see Alarms and Events. To view the Alarm log: 1. On the Message Networking administration Web interface, under Logs, click Alarm. The system displays the Alarm Log page. 2. Complete the fields on the page. For information on completing the fields, click the field names or Help on the Web-based administration page. 3. Click Display to start the report. 4. Examine the displayed events. Events, alarms, and their associated repair procedures are described in Alarms and Events. 5. If a displayed event calls for repair, take whatever corrective action is necessary.

41 Page 43 of 304 Viewing the Backup log The Backup log displays information about the latest system backups. To view the Backup log: 1. On the Message Networking administration Web interface, under Logs, click Backup. The system displays the Backup Logs page. 2. Select the backup for which you want to review the log from the drop-down menu. For information on completing the fields, click Help. 3. Click View to display the log.

42 Page 44 of 304 Viewing the Command Line History log Use this log to display all commands used via the command line. To view the Command Line History log: 1. On the Message Networking administration Web interface, under Logs, click Command Line History. The system displays the Command Line History Log page. 2. Complete the fields on the page. For information on completing the fields, click the field names or Help on the Web-based administration page. 3. Click Display to start the report. When the system gathers the information you specified, it displays the report.

43 Page 45 of 304 Viewing the Server Events log The Server Events log identifies system events. These events include problems that you need to correct. Some events, such as full subscriber mailboxes and undeliverable messages, directly affect message processing. To view the Server Events log: 1. On the Message Networking administration Web interface, under Logs, click Server Events. The system displays the Server Event Log page. 2. Complete the fields on the page. For information on completing the fields, click the field names or Help on the Web-based administration page. 3. Click Display to start the report. When the system gathers the information you specified, it displays the report. The Server Event log results table details the fields on this display-only page. 4. Examine the displayed events. Events, alarms, and their associated repair procedures are described in Alarms and Events. 5. If a displayed event calls for repair, take whatever corrective action is necessary. Server Event Log Results Field name Date Time App Event ID Cnt Message Description/procedure The dates the events were logged, in mm/dd/yy format. The times that the events were logged, in hh:mm:ss format. The two-character code for the application that was the source of the event: (blank) All applications AS=Access Security Gateway MT=Maintenance SM=Station Manager SW=Switch Integration VP=Voice Platform The code for the administration event type. See Alarms and Events for a list of event types. The number of times the associated message was sent to the Administrator's Log within one minute. A textual description of the administration event.

44 Page 46 of 304 Viewing the Maintenance log The Maintenance log contains descriptions of all reported maintenance events. The Maintenance log is only available if you have logged in using the craft or dadmin login. Note: Because VPIM is a profile of SMTP, the VPIM client is included in the SMTP client process (named vpimc), and the VPIM server is included in the SMTP server process (named vpims): If the vpimc process is stopped or restarted, both the VPIM and SMTP/MIME clients are stopped or restarted. When vpimc is stopped or restarted, the log indicates that start_smtpc is stopped or restarted because start_smtpc is the script that starts the vpimc process. If the vpims process is stopped or restarted, both the VPIM and SMTP/MIME servers are stopped or restarted. When vpims is stopped or restarted, the log indicates that start_smtps is stopped or restarted because start_smtps is the script that starts the vpims process. To view the Maintenance log: 1. On the Message Networking administration Web interface, under Logs, click Maintenance. The system displays the Maintenance Log page. 2. Complete the fields on the page. For information on completing the fields, click the field names or Help on the Web-based administration page. 3. Click Display to start the report. 4. Examine the displayed events.

45 Page 47 of 304 Viewing the Restore log The Restore log allows you to view information about the last three restores performed on the system. To view the Restore log: 1. On the Message Networking administration Web interface, under Logs, click Restore. The system displays the Restore Logs page. For information about the fields on this page, click Help. 2. Select the Restore log you want to review from the drop-down menu. 3. Click View to display the log.

46 Page 48 of 304 Viewing the Software Management logs: Installation/Removal logs The Installation and Removal logs allow you to view information about the last three restores performed on the system. To view the Installation and Removal logs: 1. On the Message Networking administration Web interface, under Logs, click Software Management. The system displays the Software Management Logs page. 2. From the Select log to view drop-down menu, select the log option for which you want to view information: Installation/Removal Log: The system displays the information for the Installation/Removal Log option. This option displays a log of the most recent software installation, update, or removal session. For information about the page, click Help. Old Installation/Removal Log: The system displays the information for the Old Installation/Removal Log option. This option displays a cumulative log of old software installation, update, and removal sessions. Old sessions appear in this log, beginning with the most recent old session. When a new session begins, the most recent installation, update, or removal session log is moved to the beginning of this log. For information about the page, click Help. Summary of Installation/Removal of Packages: The system displays the information for the Summary of Installation/Removal of Packages option. This option displays a cumulative, detailed log of software package component installation and removal attempts. The success or failure of each attempt is recorded for each set and set member. For information about the page, click Help.

47 Page 49 of 304 Viewing the Web Server log Use this page to view error information related to the Web server, for example, the date the error occurred, an error code, an error description, and the server address. To view the Web Server log: On the Message Networking administration Web interface, under Logs, click Web Server. The system displays the Administration History Log page. For more information on the page, click Help on the Web-based administration page.

48 Page 50 of 304 Application IDs This topic provides information about the application IDs that are included in Message Networking alarms and events. The application ID represents the part of the system that generated the message. The following table contains a list of application IDs for Message Networking alarms and events. Application IDs Abbreviation Application AD AG AS EL IC LP MT NW OG SC SD SM SW VI VP Aria Digital AMIS Analog Access Security Gateway Enterprise List Message Networking Core LDAP Maintenance Digital Networking Octel Analog Networking SCE (analog) Serenade Digital Station Manager Switch Integration VPIM and SMTP/MIME Voice Platform

49 Page 51 of 304 Alarms An alarm indicates a hardware, software, or environmental problem that could affect the operation of the Message Networking system. The system displays alarms in the Alarm Log. See the Alarm Log for more information about how to access the alarm log. The alarm descriptions and resolution procedures in this section are organized by the alarm application identifier (ID), which is the two-letter code used to identify the application or subsystem for which an alarm is being generated. For example, the application ID for the MT BACKUP 1 alarm is MT. If you want to find information about the MT BACKUP 1 alarm, see the MT (Maintenance) alarm information. The Message Networking alarm information is organized as follows: Message Networking alarms and events AS (Access Security Gateway) alarms EL (Enterprise List) alarms MT (Maintenance) alarms SM (Station Manager) alarms SW (Switch Integration) alarms VP (Voice Platform) alarms

50 Page 52 of 304 Message Networking alarm codes and Server Events Log entries This topic contains the Alarm and Server Events Log entries related to the Message Networking core and its remote machines: IC - Message Networking Core AG - AMIS Analog OG - Octel Analog NW - Networking SC - SCE process SD - Serenade Digital AD - Aria Digital LP - LDAP VI - VPIM IC - Message Networking Core alarms Customer-resolvable alarms The following alarms can be resolved by the system administrator: Alarm Code: 0002 Event ID: SWFAILRET Description: Message Text: Message delivery failed for msgid:xxxxxx error code=xx. This alarm indicates that the Message Networking module failed to deliver remote mail. Message Networking error codes include: 2 - recipient mailbox was full 3 - recipient did not exist 5 - inter-machine permission failure 6 - sending restrictions failure 7 - miscellaneous failure to deliver message Repair Procedure: None. This alarm is for informational purposes only. Alarm Code: 3003 Event ID: SWRETRYEX Description:

51 Page 53 of 304 Retry count or max time for the message exceeded. This alarm is generated when the maximum transit time is exceeded for a given message type. Repair Procedure: None. This alarm is for informational purposes only. Alarm Code: 4000 Event ID: SWIPROCDEAD Description: Process <process name> has reached the restart limit of <number>. A process died unexpectedly and the system has failed to restart it and keep it running after several tries. Repair Procedure: These steps could require assistance from technical support personnel. 1. Stop and restart the voice system. 2. After the voice system has restarted, wait about ten minutes to see if any alarm (including this one) occurs, indicating that either a process has died (or died repeatedly), or a process could not be started. 3. If a major alarm occurs, escalate to technical support personnel immediately. Otherwise, report the problem to technical support personnel during normal business hours. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID Description 0003 SWICINITFAIL IC module initialization failure. This alarm indicates that the Message Networking module failed to initialize SWICOPENFAIL IC database open failure. This alarm indicates that the database server is not running SWICCLOSEFAIL IC database open failure. This alarm indicates that the database server is not running SWICINTERR IC internal error. This alarm indicates that an Message Networking process could not communicate with another Message Networking process or that a network problem occurred. If this alarm is active, it is likely that the Message Networking is not in service or is not installed properly SWRETRYEX Retry count or max time for the message exceeded. This alarm is generated when the maximum transit time is exceeded for a given message type SWICORAINTERR 3005 SWICINVALIDVAL This alarm can indicate a database error. Invalid value for sid or nid. This alarm indicates that the system limits for subscriber IDs and node IDs have been exceeded.

52 Page 54 of SWICCOREDUMP IC module core dump saved. This alarm indicates that a software problem caused a core dump of a Message Networking process SWICAUDERR IC audit failed. This alarm indicates that an audit of the Message Networking database failed. This alarm does not mean that the Message Networking database is corrupted. AG - AMIS Analog alarms Customer-resolvable alarms There are no customer-resolvable AG alarms. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID AAG001 AAG002 AAG011 AAG012 AAG013 AAG014 AAG015 Description Unable to determine status of incoming call. The incoming call did not contain the AMIS start protocol tones. Unable to connect to remote machine <machine name>. The AAG did not receive the AMIS start protocol tones when trying to connect to a remote AMIS machine. TSC Only: 1. Check the dial string for the remote machine through the telephone or screen interface. 2. Check the IVC6 card and the telephone line connections to determine if excessive noise on the line might have caused the touchtones to not be recognized Timeout in the middle of protocol <protocol step>. The initial connection was made, but the AAG did not receive any protocol tone during the <protocol step> indicated in the message text. TSC Only: Check the analog-line voice card and the telephone line connections to determine if excessive noise on the line might have caused the touchtones to not be recognized. Also check the /aag/text/readme.delay file for descriptions of the delays. Remote machine <machine name> disconnected. TSC Only: Check the logs on the remote machine to determine the cause of the error. Checksum error. The AAG script detected a protocol error during transmission. TSC Only: Check the IVC6 card and the telephone line connections to determine if excessive noise on the line might have caused the touchtones to not be recognized. Zero Messages Received. The AAG receive script did not receive any messages. There was no error detected in the protocol. This could indicate that the remote machine experienced an error during message transmission. TSC Only: Check the logs on the remote machine to determine the cause of the error. Unable to Access Message. The AAG script was unable to access a

53 Page 55 of 304 message. TSC Only: This alarm is a software problem. Use standard escalation procedures. AAG016 AAG021 AAG022 AAG031 AAG041 AAG061 AAG081 AAG082 AAG083 AAG084 Do Not Accept Messages From This System. The AAG receive script received a message from an unknown system. Send script started without node id. The AMIS send application was started with a blank machine ID. TSC Only: This alarm is a software problem. Use standard escalation procedures. Send script started with incorrect node id. The AMIS send script application was started with an incorrect machine ID. Database error. The AAG could not access the database table indicated in the message text. The database could have been corrupted. SCE failure. The interface between the Service Creation Environment (SCE) and the AAG returned an error. TSC Only: This alarm is a software problem. Use standard escalation procedures. Too many invalid login attempts. The system received too many invalid login attempts. TSC Only: Verify the administration user ID and password in the database. Start up failure. The AMIS send script trigger mechanism is unable to start. TSC Only: Verify that the feature option for the AAG module is turned on. This alarm is a software problem. Use standard escalation procedures. Unable to initialize socket. A system error has occurred. TSC Only: This alarm is a software problem. Use standard escalation procedures. Client not registered. The triggering process is not registered in the system process. The process entry has not automatically been made in the /etc/services file. TSC Only: This alarm is a software problem. Use standard escalation procedures. Triggering process starting too frequently. The AAG triggering process is respawning more than five times in 10 minutes. TSC Only: This alarm is a software problem. Use standard escalation procedures. The remote AMIS system entry is either not present in the AAG table or is wrong. Add the entry or verify that a valid AMIS system is trying to connect to the Message Networking system. AG process alarms are not resolved at the time the Message Networking system is started. TSC Only: 1. Access the Maintenance Log. On the Maintenance Log page, enter IC for Application and SWICAUDERR for Event ID. Click Save. 2. In the output, note the name audit(s) that failed and search for other recent occurrences of the failure of this audit. 3. If this audit has failed consistently, escalate to the next level of support. OG - Octel Analog Networking alarms

54 Page 56 of 304 Customer-resolvable alarms The following alarms can be resolved by the system administrator: Event ID: ONG001 Description: Unable to determine status of incoming call. The incoming call did not contain the Octel Analog Networking start protocol tones. Repair Procedure: To resolve the alarm: 1. The system administrator could have called the number multiple times without electing to administer the system; check with the system administrator to verify that the system has been administered correctly. 2. Excessive noise on the telephone line might have caused the touchtones to not be recognized; check the telephone lines for noise and check the analog port board. 3. Another machine could be set up incorrectly to call the Octel Analog Networking protocol; check the machine administration with the system administrator. Event ID: ONG002 Description: Unable to connect to remote machine <machine name>. The Message Networking system did not receive the Octel Analog Networking start protocol tones when trying to connect to a remote Aria or Serenade Analog machine. Repair Procedure: To resolve the alarm: 1. Excessive noise on the telephone line might have caused the touchtones to not be recognized; check the telephone lines for noise and check the analog port board. 2. The dial string for this remote machine could be incorrect; check with the system administrator to verify the dial string. Event ID: ONG011 Description: Timed out during <protocol step> while sending receiving to from <machine name>. The initial connection was made and then the Message Networking system did not receive the protocol tone during the protocol step mentioned in the message text. Repair Procedure: Excessive noise on the telephone line might have caused the touchtones to not be recognized; check the telephone lines for noise and check the analog port board. Event ID: ONG012

55 Page 57 of 304 Description: Remote machine <machine name> disconnected. The remote machine disconnected prematurely. Repair Procedure: The remote machine probably had an error; the system administrator needs to check the error logs on the remote machine. Event ID: ONG013 Description: Checksum/Frame error during <protocol step> while sending receiving to from <machine name>. The ONG script detected a protocol error during transmission. Repair Procedure: Excessive noise on the telephone line might have caused the touchtones to not be recognized; check the telephone lines for noise and check the analog port board. Event ID: ONG014 Description: Zero messages received. The ONG receive script received zero messages. There was no error detected in the protocol. Repair Procedure: The remote machine probably had an error during message transmission; the system administrator needs to check the error logs on the remote machine. Event ID: ONG016 Description: Do not accept messages from this system. The ONG receive script received a message from an unknown system. Repair Procedure: The remote Octel Analog Networking system entry is either not present in the ONG table or is incorrect. TSC Only: Either add the Octel Analog Networking system entry or verify that a valid Octel system is trying to connect to the Message Networking system. Event ID: ONG018 Description: No fax component. The ONG send script received a fax only message. Repair Procedure:

56 Page 58 of 304 None. This alarm is for informational purposes only. Event ID: ONG021 Description: Non-deliverable mailbox. The ONG send script attempted to deliver a message to a special mailbox. Repair Procedure: None. The mailbox is automatically deleted from the Message Networking system. Event ID: ONG22 Description: Mailbox future delivery full. The ONG send script tried to deliver a future delivery message to a full mailbox. Repair Procedure: The system administrator needs to administer the mailbox on the remote machine. Event ID: ONG024 Description: Remote node disabled. The ONG send script tried to communicate with a disabled remote machine. Repair Procedure: The system administrator needs to administer the end node back online. Event ID: ONG026 Description: No voice component. The ONG send script is sending a fax-only message with a system default voice component attached to it. Repair Procedure: None. This alarm is for informational purposes only. Event ID: ONG051 Description: Error accessing ONG database table <table name>. The ONG database could have been corrupted. Repair Procedure: The system administrator needs to restore the database from backup tapes.

57 Page 59 of 304 Event ID: ONG062 Description: Mbx <mailbox number> not updated on <node>; Same mailbox exists on <node>. A duplicate mailbox number exists on end nodes. Message Networking accepts only the first mailbox number registered. Repair Procedure: The system administrator needs to determine which user has one mailbox number on different end nodes. Update the Message Networking system with the correct mailbox. The system administrator can use different dial plans for different end nodes. Event ID: ONG063 Description: Node protocol level < 3; cannot proceed with updates. Directory updates need to have protocol revision level 3 or later. The end node protocol revision is less that 3. Repair Procedure: The system administrator needs to check the updates parameters on the Remote Parameters screen and on the Local System Parameters screen. Event ID: ONG067 Description: Updates <In/Out> not allowed on <Node/Base>; Check Parameters Screen. The Updates In or Updates Out flag does not permit updates to or from this node. Repair Procedure: Verify that the Updates In and Updates Out fields on the Message Networking General Parameters screen are administered correctly. Event ID: ONG081 Description: Cannot start Octel Analog Networking script trigger process. The Octel Analog Networking script trigger mechanism is unable to start. Repair Procedure: The system administrator needs to verify that the Max Number of Octel Nodes is administered correctly on the Feature Options screen. Alarms requiring remote support center contact If you receive the following events, contact your remote support center.

58 Page 60 of 304 ID ONG015 ONG017 ONG019 ONG020 ONG023 ONG025 ONG041 ONG042 ONG061 ONG062 ONG063 ONG064 ONG065 ONG066 ONG082 Description Unable to access message component. The ONG send or administration script received a corrupted message. TSC Only: The message header on the Message Networking system might be corrupted or missing; use standard escalation procedures. Remote node file system full. The ONG send or administration script received a file system full response. TSC Only: The remote Octel system does not have enough space for the message; use standard escalation procedures. No access to the Octel node. The ONG send or administration script has been refused access to the remote Octel system. TSC Only: The Octel remote machine is not configured properly for the Message Networking system; use standard escalation procedures. Invalid Opcode. The ONG script does not understand the Opcode received. TSC Only: Indicates a software error; use standard escalation procedures. No access to remote machine NameNet. The ONG send script could not access the NAMENET type for a remote machine. TSC Only: Indicates a software error; use standard escalation procedures. Bad message. The ONG send script delivered a message that the remote machine could not understand. TSC Only: Indicates a software error; use standard escalation procedures. Script Octel Analog Networking without node ID. The Octel Analog Networking protocol was started without machine ID. TSC Only: Indicates a software error; use standard escalation procedures. Script started with incorrect node ID <ID>. The Octel Analog Networking protocol was started with an incorrect machine ID. TSC Only: Indicates a software error; use standard escalation procedures. Radiant external function <function name> failed, return code <return code>. The interface between Radiant and an underlying environment received a return error. TSC Only: Indicates a software error; use standard escalation procedures. Mailbox not updated. Same mailbox exists on another node. Updates not allowed. Check the Parameters screen. Update started - node name. Last update failed/success - node name. Update canceled. Next update start from. Error initializing socket: ERRNO xxx. exiting. System error has occurred. TSC Only: Indicates a software error; use standard escalation procedures.

59 Page 61 of 304 ONG083 ONG084 Client: tcp/ong_trig:unknown service. The triggering process is not registered in the Message Networking system correctly. TSC Only: Indicates a software error; use standard escalation procedures. The triggering process is starting too frequently. The triggering process is respawning more than five times in 10 minutes. Octel Analog Networking process alarms are not resolved at the time the Message Networking system is started. TSC Only: 1. Access the Maintenance Log. On the Maintenance Log Display Selection screen enter IC or EL for Application and SWICAUDERR for Event ID. Press (Save). 2. In the output, note the name audit(s) that failed and search for other recent occurrences of the failure of this audit. 3. If this audit has failed consistently, escalate to the next level of support. NW - Networking alarms Customer-resolvable alarms The following alarms can be resolved by the system administrator: Alarm Code: 0003 Event ID: SWINITFAIL Description: Module failed to initialize correctly. Repair Procedure: These steps could require assistance from technical support personnel: 1. Stop and restart the voice system. 2. After the voice system has restarted, wait approximately ten minutes to determine if any alarm (including this one) occurs, indicating initialization failure. 3. If a major alarm occurs, escalate to technical support personnel immediately. Otherwise, report the problem to technical support personnel during normal business hours. Alarm Code: 0000 Event ID: SWIPROCDEAD Description: Process <process name> has reached the restart limit of <number>. A process died unexpectedly and the system has failed to restart it and keep it running after several tries. Repair Procedure: These steps could require assistance from technical support personnel:

60 Page 62 of Stop and restart the voice system. 2. After the voice system has restarted, wait approximately ten minutes to determine if any alarm (including this one) occurs, indicating that either a process has died (or died repeatedly), or a process could not be started. 3. If a major alarm occurs, escalate to technical support personnel immediately. Otherwise, report the problem to technical support personnel during normal business hours. If a major alarm occurs, escalate to technical support personnel immediately. Otherwise, report the problem to technical support personnel during normal business hours. Alarm Code: 0004 Event ID: SWNWVMDBSYNC Description: Database failed to initialize correctly. Repair Procedure: These steps could require assistance from technical support personnel: 1. Stop and restart the voice system. 2. After the voice system has restarted, wait approximately ten minutes to determine if any alarm (including this one) occurs. 3. If a major alarm occurs, escalate to technical support personnel immediately. Otherwise, report the problem to technical support personnel during normal business hours. Alarms requiring remote support center contact If you receive the following events, contact your remote support center. ID Description NW software alarms 1000 SWNONSTD Non-standard NW software in use SWCOREDUMP NW module coredump saved SWANECONN Connection failure to machine SWXMQFILL Possible message delivery problem to machine. NW database alarms 1000 SWNDSTARTFAIL 1001 SWNDOPENFAIL Data server startup failure. Database open failure SWNDINTERR Database internal error SWAUDDBERR Database audit failure SWNDDBERR Database error SWNWOPENFAIL Database open failure.

61 Page 63 of SWNWORAINTERR 3004 SWICORAINTERR Database internal error. Database internal error. SC - SCE events An SC event is logged during a start_vs (voice) of the system. This event indicates that the SCE (analog) processes are going to be started by the SCE process manager. If the process manager fails to start the processes, a subsequent error is logged. The SC event requires no action. SD - Serenade Digital alarms Customer-resolvable alarms The following alarms can be resolved by the system administrator: Event ID: ADM_CPU_3 Description: loc=<location code>, d1=<data1>d2=<data2>d3=<data3>d4=<data4>. Serenade Digital Networking administration error. The location code specifies the general area where the error occurred. Data1 specifies the type of error. Data2, data3, and data4 are associated with the particular error type. Loc code=42, Configuration Error. d1=0x6, Gateway error mailbox not configured. d1=0x14, Received inaccessible creator mailbox digits during a digital network message transfer. d2, d3, and d4 contain the leading six digits of inaccessible creator mailbox. d1=0x22, Sent a prefix the remote side did not recognize during NameSend. d1=0x23, Other side does not have the NameSend feature. d1=0x25, Names Directory error during NameSend. d1=0x2b, Other side does not have the NetName feature. Loc code=64 LAN Subsystem Error. d1=0x7, OEM Network Compatibility key of other system does not match ours. OEM type between systems is incompatible. Loc code=73 Protocol Revision Level Error. d1=0x1 Digital Networking. d2=local protocol revision level. d3=remote protocol revision level. d4=location number of remote location. Repair Procedure: Check Serenade configuration on the Message Networking system and/or remote Serenade remote machine. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID ERR_SMU_1 Description loc=<location code>, <error message>. The SMU component

62 Page 64 of 304 experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. ERR_SMU_2 ERR_CPU_1 ERR_CPU_2 ERR_CPU_4 ERR_VCU_1 ERR_VCU_2 ERR_VCU_3 ERR_LAN_1 ERR_LAN_2 ERR_LAN_4 ERR_LIB_1 WRN_CPU_1 WRN_CPU_2 WRN_CON_1 SWICOPENFAIL SWICINTERR loc=<location code>, <error message>.the SMU component experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. loc=<location code>,<error message>. The CPU component experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. loc=<location code>, d1=<data1>,d2=<data2>,d3=<data3>,d4=<data4>. The CPU component experienced an error. The location code uniquely identifies where the error occurred. Data1, data2, data3, and data4 are associated with the particular error. loc=<location code>,<error message>. The CPU component experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. loc=<location code>,<error message>. The VCU component experienced an error. The location code uniquely identifies where the error occurred. Data1, data2, data3, and data4 are associated with the particular error. loc=<location code>,<data1><data2><data3>. The VCU component experienced an error. The location code uniquely identifies where the error occurred. Data1, data2, and data3 are data associated with the particular error. loc=<location code>,<error message>. The VCU component experienced an error. The location code uniquely identifies where the error occurred. loc=<location code>,<error message>. The LAN component experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. loc=<location code>,<data1><data2><data3>. The LAN component experienced an error. The location code uniquely identifies where the error occurred. Data1, data2, and data3 are associated with the particular error. loc=<location code>,<error message>. The LAN component experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. loc=<location code>,<error message>. The LAN component experienced an error. The location code uniquely identifies where the error occurred. The error message describes the particular error. loc=<location code>,<error message>. The CPU component experienced an warning. The location code uniquely identifies where the warning occurred. The error message describes the particular warning. loc=<location code>,<error message>. The CPU component experienced an warning. The location code uniquely identifies where the warning occurred. The error message describes the particular warning. Warning in connection. Database open failure. This alarm indicates that the database server is not running. IC internal error. This alarm indicates that a Message Notification

63 Page 65 of 304 process could not communicate with another Message Networking process or that a network problem occurred. If this alarm is active, it is likely that the Message Networking system is not in service or is not installed properly. SWICINVALIDVAL Invalid value for sid or nid. AD - Aria Digital alarms Customer-resolvable alarms There are no customer-resolvable AD alarms. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID ERR_SOFTWARE ERR_PROTOCOL ERR_NACK ERR_INVMSG ERR_FS ERR_TIMEOUT ERR_ABORT Description 1=<location code> s=<suberr code> w=<data1> dw=<data2> software error. The Aria Digital gateway experienced a software error. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> protocol error. The Aria Digital gateway experienced a series of protocol errors. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> negative ack. The Aria Digital gateway received a series of negative acknowledgements from remote nodes. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> invalid message. The Aria Digital gateway encountered an invalid message. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> file system error. The Aria Digital gateway experienced a file system error. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> timeout. The Aria Digital gateway experienced a series of timeouts. The location code uniquely identifies where the latest error occurred. The suberr code gives additional information about the latest error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> node requested abort. The Aria Digital gateway received a series of abort requests from remote nodes. The location code uniquely identifies where

64 Page 66 of 304 the latest error occurred. The suberr code gives additional information about the latest error that occurred. Data1 and data2 are data specific to the location code. ERR_PACKET ERR_COREFAIL ERR_CONNECT ERR_SESSION ERR_INIT ERR_UNKNOWN ERR_SYSCALL ERR_PROCDEATH ERR_ENVIRON ERR_SHMEM 1=<location code> s=<suberr code> w=<data1> dw=<data2> packet error. The Aria Digital gateway experienced a series of packet errors. The location code uniquely identifies where the latest error occurred. The suberr code gives additional information about the latest error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> core failure. The Aria Digital gateway experienced a failure related to the core library area. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> connect failure. The Aria Digital gateway experienced a series of connection failures. The location code uniquely identifies where the latest error occurred. The suberr code gives additional information about the latest error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> session failure. The Aria Digital gateway experienced a series of errors during session setup. The location code uniquely identifies where the latest error occurred. The suberr code gives additional information about the latest error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> process initialization failure. An Aria Digital gateway process failed to start up. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> unknown error. An Aria Digital gateway experienced an unknown error. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> system call error. The Aria Digital gateway experienced a system call error. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> unexpected process death. An Aria Digital gateway process died unexpectedly. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> environment variable not found. The Aria Digital gateway failed to find a needed environment variable. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. 1=<location code> s=<suberr code> w=<data1> dw=<data2> shared

65 Page 67 of 304 memory problem. The Aria Digital gateway encountered a shared memory problem. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. ERR_MEMALLOC 1=<location code> s=<suberr code> w=<data1> dw=<data2> memory allocation problem. The Aria Digital gateway encountered a memory allocation problem. The location code uniquely identifies where the error occurred. The suberr code gives additional information about the error that occurred. Data1 and data2 are data specific to the location code. LDAP alarms Customer-resolvable alarms There are no customer-resolvable LDAP alarms. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID SWNWOPENFAIL SWNWEXECLFAIL Description An LDAP database open failure occurred. An Execl failure occurred. VI - VPIM alarms Customer-resolvable alarms Alarm Code: 0 Event ID: VCARD_XCODERR Description: Transcoder failed: result=<return code>. During communication with a remote machine, the remote machine transmitted information that is not supported by Message Networking. Repair Procedure: Make sure that the remote machine has been certified by Avaya to be compatible with the Message Networking system. If it has not been certified, differences in the transmission protocol could prevent proper communication with the remote machine. Alarm Code: 1 Event ID: VMNODE_READ Description:

66 Page 68 of 304 Error reading VM. An unexpected error occurred. Repair Procedure: This is an internal software error. Escalate this problem to Tier 4 during normal business hours, unless conditions indicate the need for an immediate resolution. Alarm Code: 2 Event ID: REAPCHILD_SIG Description: Signal failed. An error occurred while the VPIM protocol was processing the end of a message transmission. Repair Procedure: This is an internal software error. Escalate this problem to technical support personnel during normal business hours, unless conditions indicate the need for an immediate resolution. Alarm Code: 3 Event ID: MIME_SEG Description: During processing of a message, an error occurred while attempting to read from/write to the disk. Repair Procedure: One or more file systems used for messaging might have run out of space. Determine if the /voice file systems are full. If they are, there are two likely reasons for this to happen. Take the following steps to address the possible causes (some of these steps could require assistance from technical support personnel): 1. Run dfspace from the command prompt to see if any file systems are unusually low on or have run out of space. 2. If any file systems are in this condition, check in those file systems to see if there are ways to free up space without adversely affecting the system. 3. On the Message Networking administration Web interface, under Reports, click Subscriber Lists > Subscriber Count. The system displays the Subscriber Count page. If the number is close to or exceeds the advertised limit, the storage space needed to hold the names is probably reducing the amount of space available for messages. 4. From the command prompt, run audit_vname to delete voiced names that have not been used for a long time from the system. Take administrative steps to reduce the number of voiced names stored on the system. For example, depending on the type of remote machine, some remote machines can be administered not to send their voiced names to the Message Networking system. 5. The operating system might need to be rebooted, because an operating system limitation was exceeded. Follow normal procedures for stopping the voice system and then rebooting the machine. Alarm Code: 4 Event ID: MSG_ACC_SVC

67 Page 69 of 304 Description: During processing of a message, an error occurred while attempting to read from/write to the disk. Repair Procedure: One or more file systems used for messaging could have run out of space. Determine if the /voice file systems are full. If they are, there are two likely reasons for this to happen Take the following steps to address the possible causes (some of these steps could require assistance from Avaya remote service center personnel): 1. Run dfspace from the command prompt to see if any file systems are unusually low on or have run out of space. 2. If any file systems are in this condition, check in those file systems to see if there are ways to free up space without adversely affecting the system. 3. On the Message Networking administration Web interface, under Reports, click Subscriber Lists > Subscriber Count. The system displays the Subscriber Count page. If the number is close to or exceeds the advertised limit, the storage space needed to hold the names is probably reducing the amount of space available for messages. 4. From the command prompt, run audit_vname to delete voiced names that have not been used for a long time from the system. Take administrative steps to reduce the number of voiced names in the system. For example, depending on the type of remote machine, some remote machines can be administered not to send their voiced names to the Message Networking system. 5. The operating system might need to be rebooted, because an operating system limitation was exceeded. Follow normal procedures for stopping the voice system and then rebooting the machine. Alarm Code: 5 Event ID: NAM_ACC_SVC Description: An unexpected error occurred. Repair Procedure: This is an internal software error. Escalate this problem to technical support personnel during normal business hours, unless conditions indicate the need for an immediate resolution. Alarm Code: 6 Event ID: PKGER_SVC Description: During processing of a message, an error occurred while attempting to read from/write to the disk. Repair Procedure: One or more file systems used for messaging might have run out of space. Determine if the /voice file systems are full. If they are, there are two likely reasons for this to happen. Take the following steps to address the possible causes (some of these steps could require assistance from Avaya remote service center personnel): 1. Run dfspace from the command prompt to see if any file systems are unusually low on or have run out of space. 2. If any file systems are in this condition, check in those file systems to see if there are recognizable ways

68 Page 70 of 304 to free up space without adversely affecting the system. 3. On the Message Networking administration Web interface, under Reports, click Subscriber Lists > Subscriber Count. The system displays the Subscriber Count page. If the number is close to or exceeds the advertised limit, the storage space needed to hold the names is probably reducing the amount of space available for messages. 4. From the command prompt, run audit_vname to delete voiced names that have not been used for a long time from the system. Take administrative steps to reduce the number of voiced names stored on the system. For example, depending on the type of remote machine, some remote machines can be administered not to send their voiced names to the Message Networking system. 5. The operating system might need to be rebooted, because an operating system limitation was exceeded. Follow normal procedures for stopping the voice system and then rebooting the machine. Alarm Code: 7 Event ID: OUTCALL_MSG Description: Error Opening Message. During processing of a message, an error occurred while attempting to read from/write to the disk. Repair Procedure: One or more file systems used for messaging might have run out of space Determine if the /voice file systems are full. If they are, there are two likely reasons for this to happen. Take the following steps to address the possible causes (some of these steps could require assistance from Avaya remote service center personnel): 1. Run dfspace from the command prompt to see if any file systems are unusually low on or have run out of space. 2. If any file systems are in this condition, check in those file systems to see if there are ways to free up space without adversely affecting the system. 3. On the Message Networking administration Web interface, under Reports, click Subscriber Lists > Subscriber Count. The system displays the Subscriber Count page. If the number is close to or exceeds the advertised limit, the storage space needed to hold the names is probably reducing the amount of space available for messages. 4. From the command prompt, run audit_vname to delete voiced names that have not been used for a long time from the system. Take administrative steps to reduce the number of voiced names on the system. For example, depending on the type of remote machine, some remote machines can be administered not to send their voiced names to the Message Networking system. 5. The operating system might need to be rebooted, because an operating system limitation was exceeded. Follow normal procedures for stopping the voice system and then rebooting the machine. Alarm Code: 8 Event ID: MIMOUT_MSG Description: Error Opening Message. During processing of a message, an error occurred while attempting to read from/write to the disk. Repair Procedure:

69 Page 71 of 304 One or more file systems used for messaging might have run out of space. Determine if the /voice file systems are full. If they are, there are two likely reasons for this to happen. Take the following steps to address the possible causes (some of these steps could require assistance from Avaya remote service center personnel): 1. Run dfspace from the command prompt to see if any file systems are unusually low on or have run out of space. 2. If any file systems are in this condition, check in those file systems to see if there are ways to free up space without adversely affecting the system. 3. On the Message Networking administration Web interface, under Reports, click Subscriber Lists > Subscriber Count. The system displays the Subscriber Count page. If the number is close to or exceeds the advertised limit, the storage space needed to hold the names is probably reducing the amount of space available for messages. 4. From the command prompt, run audit_vname to delete voiced names that have not been used for a long time from the system. Take administrative steps to reduce the number of voiced names in the system. For example, depending on the type of remote machine, some remote machines can be administered not to send their voiced names to the Message Networking system. 5. The operating system might need to be rebooted, because an operating system limitation was exceeded. Follow normal procedures for stopping the voice system and then rebooting the machine. Alarm Code: 9 Event ID: OVMOUT_HDR Description: ovmooutmsg::error Opening [mediatext][rfc_822]. During processing of a message, an error occurred while attempting to read from/write to the disk. Repair Procedure: One or more file systems used for messaging could have run out of space. Determine if the /voice file systems are full. If they are, there are two likely reasons for this to happen. Take the following steps to address the possible causes(some of these steps could require assistance from Avaya remote service center personnel): 1. Run dfspace from the command prompt to see if any file systems are unusually low on or have run out of space. 2. If any file systems are in this condition, check in those file systems to see if there are ways to free up space without adversely affecting the system. 3. On the Message Networking administration Web interface, under Reports, click Subscriber Lists > Subscriber Count. The system displays the Subscriber Count page. If the number is close to or exceeds the advertised limit, the storage space needed to hold the names is probably reducing the amount of space available for messages. 4. From the command prompt, run audit_vname to delete voiced names that have not been used for a long time from the system. Take administrative steps to reduce the number of voiced names in the system. For example, depending on the type of remote machine, some remote machines can be administered not to send their voiced names to the Message Networking system. 5. The operating system might need to be rebooted, because an operating system limitation was exceeded. Follow normal procedures for stopping the voice system and then rebooting the machine. Alarm Code: 10 Event ID: VPIMS_SIG Description:

70 Page 72 of 304 signal (<signal type>) failed. An error occurred during initialization of one of the processes used for the VPIM protocol. Repair Procedure: This is an internal software error. Escalate this problem to Tier 4 during normal business hours, unless conditions indicate the need for an immediate resolution. Alarm Code: 11 Event ID: REC_PSTMSTR Description: Receipt of a postmaster@domain message. A message has been delivered to the postmaster mailbox of the Message Networking system. Repair Procedure: To view the message, do the following: 1. On the Message Networking administration Web interface, under MN Administration, click Postmaster Messages. The system displays the message. 2. Review the delivered message. Alarm Code: 12 Event ID: SMPT_ERR Description: An error occurred during the communication with the remote machine. The error was likely caused by an incompatibility in the message transmission protocol. Repair Procedure: Make sure the remote machine has been certified by Avaya to be compatible with the Message Networking system. If it has not been certified, differences in the transmission protocol could prevent proper communication with the remote machine. Alarm Code: 13 Event ID: CONN_ERR Description: Unable to connect to <machine>...the Message Networking system was unable to connect to the remote machine, <machine>, as part of a message delivery. Repair Procedure: This problem could result from any of the following causes: Some of these steps could require assistance from Avaya remote service center personnel.

71 Page 73 of 304 The remote machine might not be accepting connections. Verify that the remote machine is in its normal run state. Make sure all of its processes are running normally. Determine if unusually heavy traffic on the remote machine could be preventing the machine from accepting connections. The remote machine might not be communicating with the network. Make sure the remote machine is connected to the network. Also make sure the network hardware on the remote machine is running properly. The Message Networking system might not be communicating with the network. Make sure the Message Networking system is connected to the network. Also, make sure the network hardware on the Message Networking system is working properly. There could be an administration problem. Make sure the administration information for the remote machine is entered properly in the Message Networking administration screens. Also ensure that the Message Networking system is properly administered in the remote machine. Network problems could be interfering with communication. Determine if any network problems are occurring. Alarm Code: 14 Event ID: RMT_DISC_FULL Description: <machine> disk full. During a message delivery attempt the remote machine, <machine>, indicated that it had a full disk. Repair Procedure: Reduce the amount of disk space that is in use on the remote machine. Alarm Code: 15 Event ID: SMTP_TIMEOUT Description: <machine> : Protocol time out. Communication with the remote machine was interrupted, because the remote machine did not send a response when one was expected. Repair Procedure: This problem could be the result of any of the following causes (some of these steps could require assistance from Avaya remote service center personnel): The remote machine might not be communicating with the network. Verify that the remote machine is in its normal run state. Make sure all of its processes are running normally. Determine if unusually heavy traffic on the remote machine could be preventing the machine from communicating in a normal fashion. Make sure that the remote machine is still connected to the network. Verify that the network hardware on the remote machine is running properly. The Message Networking system might not be communicating with the network. Make sure the Message Networking system is still connected to the network. Verify that the network hardware on the Message Networking system is working properly. Network problems could be interfering with communication. Determine if any network problems are occurring. The remote machine might not be compatible with the Message Networking system. Make sure the

72 Page 74 of 304 remote machine has been certified by Avaya to be compatible with the Message Networking system. Alarm Code: 16 Event ID: VPIMS_LOGON Description: An unknown system (<machine>) tried to log on. The remote machine, <machine>, attempted to communicate with the Message Networking system. However, the remote machine's name is not in the Message Networking system's database. Repair Procedure: On the Message Networking system, add an entry for the remote machine using the Message Networking administration pages. If the machine that tried to log on is not a legitimate voice messaging machine, this alarm could also indicate that an unauthorized machine is attempting to gain improper access to the Message Networking system. Alarm Code: 17 Event ID: MSG_TOO_LONG Description: Message Too Large: from <sender>. During transmission of a message to a remote machine, the remote machine indicated that the message was too long. Repair Procedure: Determine if the remote machine is low on disk space. If it is low on disk space, take steps to make more disk space available. If the remote machine has adequate disk space, determine if the remote machine has a restriction on message size. If it does and the value can be changed, increase the value. Alarm Code: 18 Event ID: NO_IC_DOMAIN Description: Local hub domain name not found. No domain name is defined for the Message Networking system. Repair Procedure: Set the domain name for the Message Networking system on the General Parameters page. To access the General Parameters page, from the main menu, select MN Administration > System Parameters > General Parameters. Alarm Code: 19 Event ID: SMTP_RPLY

73 Page 75 of 304 Description: Error generating SMTP reply; Reply code = <reply code> and state = <state> do not correspond. An error occurred during the communication with a remote machine. The error was likely caused by an incompatibility in the message transmission protocol. Repair Procedure: Make sure the remote machine has been certified by Avaya to be compatible with the Message Networking system. If it has not been certified, differences in the transmission protocol could prevent proper communication with the remote machine. Alarm Code 20 Event ID: VP_ERROR Description: An unexpected error occurred. Repair Procedure: This is an internal software error. Escalate this problem to Tier 4 during normal business hours, unless conditions indicate the need for an immediate resolution. Alarm Code: 21 Event ID: VP_WARNING Description: An unexpected error occurred. Repair Procedure: This is an internal software error. Escalate this problem to Tier 4 during normal business hours, unless conditions indicate the need for an immediate resolution. Alarm Code: 22 Event ID: REM_DISC Alarm Level: N/A (only visible in the Server Events Log) Description: Remote machine disconnected <machine>. The remote machine, <machine>, unexpectedly disconnected from the Message Networking system. Repair Procedure: This problem might be temporary and require no action. However, if the problem persists, it could be the result of any of the following causes (some of these steps could require assistance from Avaya remote service center personnel):

74 Page 76 of 304 The remote machine might not be communicating with the network. Verify that the remote machine is in its normal run state. Make sure all of its processes are running normally. Determine if unusually heavy traffic on the remote machine could be preventing the machine from communicating in a normal fashion. Make sure the remote machine is still connected to the network. Verify that the network hardware on the remote machine is running properly. The Message Networking system might not be communicating with the network. Make sure the Message Networking system is still connected to the network. Network problems could be interfering with communication. Determine if any network problems are occurring. The remote machine might not be compatible with the Message Networking system. Make sure the remote machine has been certified by Avaya to be compatible with the Message Networking system. Alarm Code: 23 Event ID: NO_MBOX Description: Mailbox does not exist <machine> <mailbox>. A message was sent to a mailbox (<mailbox>) on the remote machine <machine>, and the mailbox does not exist. Repair Procedure: If the mailbox does not exist, notify senders of messages to that mailbox that the mailbox is nonexistent. If the mailbox does exist, make sure that it is administered properly on the remote machine to accept incoming messages from an external system (like the Message Networking system). Alarm Code: 24 Event ID: COMP_UNSUP Description: Mailbox not fax/text/binary capable <machine> <mailbox>. A message containing multimedia message components (for example, fax and/or text and/or binary attachments) was sent to a mailbox <mailbox> on the remote machine <machine>, and that machine cannot accept one or more of the types of components that was sent. Repair Procedure: If the remote machine cannot support all the types of message components that were sent, notify senders to that remote machine of the inability of the machine to accept specific components. If the remote machine can support all the types of message components that were sent, modify the administration of the mailbox on the remote machine to accept the types of components that were sent. Alarm Code: 25 Event ID: NOAUTH_SND Description: Sender is not authorized <machine> <sender> <mailbox>. The remote machine, <machine>, refused to deliver a message to a mailbox, because the sender did not have proper authorization.

75 Page 77 of 304 Repair Procedure: Update the security information for the mailbox on the remote end node to allow messages to be delivered. Alarm Code: 26 Event ID: PRIV_UNSUP Description: Mailbox not private capable <machine>. A private message could not be delivered to the remote machine, because handling of private messages is not supported. Repair Procedure: If possible, change administration in the remote machine, either at a system level or at a mailbox level, to accept private messages. Alarm Code: 27 Event ID: NO_MSG_3 Description: Zero messages received this call <machine>. The remote machine, <machine>, has established a connection to the Message Networking system three separate times but has transmitted no message. Repair Procedure: This behavior could indicate a problem with the remote machine. Verify that the remote machine is operating normally. Also determine if there is a message on the remote machine's queue that might have no message contents. This alarm could also indicate that an unauthorized machine is attempting to masquerade as a legitimate voice messaging machine to gain improper access to the Message Networking system. Alarm Code: 30 Event ID: NO_MORE_SEED Description: If your Message Networking system has a default SMTP/MIME remote machine to handle SMTP messages from remote machines not administered on Message Networking, the SMTP/MIME Auto-Assign Mailbox ID field on the General Parameters page is used to determine the starting number to generate network addresses for unknown message senders. Each time a network address is automatically assigned, this field is incremented. If the SMTP/MIME Auto-Assign Mailbox ID field reaches the highest network address allowed in the default SMTP remote machine's dial plan, this field becomes unavailable. Repair Procedure: If this problem occurs, you must modify the dial plan for the default SMTP remote machine and then enter a new value for this field that is within the modified dial plan range.

76 Page 79 of 304 AS (Access Security Gateway) alarms This topic provides information about the alarms generated by the AS application, which indicate a problem with the Access Security Gateway (ASG). Customer-resolvable alarms The following alarms can be resolved by the system administrator. AS ASG 2 Description: Someone tried, and failed, to log in to the Message Networking system using an ASG-protected login. Repair Procedure: 1. Identify the employee who is using the failing login ID. Verify if the employee assigned to work on the system has been having difficulty logging in or needs additional training. 2. Test the login. See How to log in with ASG. If the login fails the key might be having problems or the initial code might have been entered incorrectly. Do the following: a. Re-administer the key. See Changing the ASG secret key number for an ASG login. The login making the change must be equal to or higher than the login being changed. b. Test the login after changing the ASG secret key. See How to log in with ASG. If the login continues to fail, contact your remote support center. AS ASG004 Description: This event is a security information message. It reports that a subscriber is attempting to make changes to the system, such as adding a subscriber, and the login ID in use does not have permission to do so. This event reports the exact action that failed, such as adding a subscriber. Repair Procedure: No corrective action is necessary.

77 Page 80 of 304 EL (Enterprise Lists) alarms This topic provides information about the alarms generated by the EL (Enterprise Lists) application, which indicate a problem with the Enterprise Lists. Alarms requiring remote maintenance center intervention The following alarms require remote maintenance center intervention. If you receive one of the following alarms, contact your remote support center. ID EL0000 EL3001 EL3002 EL0003 EL3004 EL3006 EL3007 Description The Enterprise List application has stopped since one or more processes has terminated. This alarm indicates that the Enterprise List database server is not running. This alarm indicates that an Enterprise List process could not communicate with another Enterprise List process or that a network problem occurred. This alarm indicates that the Enterprise List application failed to start. This alarm can indicate a database error. This alarm indicates that a software problem caused a core dump of an Enterprise List process. This alarm indicates that an audit of the Enterprise List database failed. This alarm does not mean that the Enterprise List database is corrupted.

78 Page 81 of 304 MT (Maintenance) alarms This topic provides information about the alarms generated by the MT application. These alarms indicate a problem with the maintenance system. Customer-resolvable alarms The following alarms can be resolved by the system administrator: ALARM_ORIG 1 BACKUP 2 FS 0 REBOOT 1 MT ALARM_ORIG 1 Description: The system failed to contact the remote maintenance center on six consecutive attempts. The system has active alarms that the remote maintenance center is not receiving. Repair Procedure: If any active alarms are severely affecting service, contact your remote support center to inform them that your system has been unable to contact the center with active alarms. 1. On the Message Networking administration Web interface, under Alarming, click Alarm Configuration. The system displays the Configure Alarms page. 2. Verify that the Product ID: and INADS Destination: fields have valid entries. If these fields are blank or do not have valid entries, contact your remote support center. If these fields appear to have valid entries, continue with Step Check that the telephone line into the remote maintenance circuit card is in place. If your system has a modem instead of a remote maintenance circuit card, check that the modem has power and that all the cables are connected. 4. Contact your remote support center. MT BACKUP 2 Description: An attended backup failed. Repair Procedure: To repair the alarm: 1. Check for any additional alarms associated with the backup process. If additional alarms are found, contact your remote support center. 2. Insert a different CD-RW or DVD medium into the CD-RW or DVD drive and try the backup again. Note: You must use CD-RW or DVD media that can support a 10x backup.

79 Page 82 of If Step 2 fails, contact your remote support center. MT FS 0 Description: This alarm indicates that the file system is fragmented. Currently, this is only an informational message. Repair Procedure: No corrective action is necessary. MT REBOOT 1 Description: Reboot warning. The system needs to be rebooted in 15 days. Avaya recommends that you reboot your system at least once every 90 days. Repair Procedure: Reboot the system. Alarms requiring remote support center contact If you receive one of the following alarms, contact your remote support center. ID MT ALARM_ORIG 0 MT BACKUP 1 MT DISK 0 MT RESTORE 1 MT SOFTWARE 34 MT UNIX 0 MT UNIX 1 MT UNIX 2 MT UNIX 3 MT UNIX 4 MT UNIX 5 Description The alarm generation process is not working because of a software problem. An unattended backup failed. A hard disk drive failed. A restore failed. The system was unable to receive information stored on the backup medium or is unable to access the restored information. A Message Networking process failed to restart. A file system is close to becoming full. Unless this alarm is resolved, the system might not be able to record new messages. The system has used up almost all of the inodes. If all of the inodes are in use, the system will not be able to start new processes and could behave as if it were out of space. The system's memory is low because one of the processes is using too much memory. Unless this alarm is resolved, the system can fail. The system has too many internal message queues. The number of message queues is greater than 90 percent of the system limit. The system is under an unusually heavy load, and processes are getting behind in answering messages. Unless this alarm is resolved, the system could stop processing calls. The system has too much information in internal communications. The

80 Page 83 of 304 total amount of information is within 60 percent of the limit. Unless this alarm is resolved, the system could stop processing calls. MT UNIX 6 MT UNIX 7 The system has too many processes operating and has nearly reached the limit allowed. The system could stop processing calls or operating at any time. The system is processing too many requests for one login type.

81 Page 84 of 304 SM (Station Manager) alarms This topic provides information about the alarms generated by the SM application. These alarms indicate a problem with the station manager. Customer-resolvable alarms There are no customer-resolvable SM alarms. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID SM SOFTWARE 4 SM SOFTWARE 11 SM SOFTWARE 12 SM SOFTWARE 13 Description The system had a memory mapping failure. The system had a file access error. Your subscriber listing cannot be found. The SM process started.

82 Page 85 of 304 SW (Switch Integration) alarms This topic provides information about the alarms generated by the SW application, which indicate a switch integration problem. Customer-resolvable alarms The following alarm can be resolved by the system administrator. SW OVERLAN 15 Description: The link to the switch is not operational because it was removed from operation. Repair Procedure: To repair the alarm: Release the link. Alarms requiring remote support center contact If you receive the following alarm, contact your remote support center. ID SW SWIN 0 Description One of the following events occurred: The system failed to locate a process. Callers might be asked to enter extension numbers. The multiple hunt group initialization failed. Callers who are reaching systems that are operating a serial integration (DMS-100 or 5ESS) are asked to enter extension numbers. The trunk translation initialization failed. If DID lines are directly connected behind the system and these lines are being used as lines to log in to the system from outside the switch, the calls carried on these lines will fail.

83 Page 86 of 304 VP (Voice Platform) alarms This topic provides information about the alarms generated by the VP application, which indicate a voice platform problem. Customer-resolvable alarms The following alarms can be resolved by the system administrator: CGEN 3 CGEN 28 CPUPERF 2 RAID1 TRIP 5 VP CGEN 3 Description: An internal process cannot communicate with other internal processes. System functionality is severely impaired. Repair Procedure: Reboot the system. VP CGEN 28 Description: A call to a third-party API failed. Repair Procedure: 1. Stop the messaging software (voice system). 2. Start the messaging software (voice system). 3. If the alarm remains active, contact your remote support center. VP CPUPERF 2 Description: The CPU is overworked. There is insufficient idle time. Repair Procedure: To repair the problem either:

84 Page 87 of 304 Decrease system usage. Increase system capacity. VP RAID1 Description: A disk drive in a RAID array has failed. Repair procedure: Identify and replace the failed drive as follows: 1. Use the RAID System Information page to identify which drive has failed. See Retrieving hard disk drive information. 2. Replace the appropriate failed drive. See Replacing a SCSI RAID drive. VP TRIP 5 Description: The channel indicated in the message lost loop current. If loop current is lost during a telephone call, the call will be terminated, and the system will remove the channel from service. The system will automatically return the channel to service when the loop current returns. Repair Procedure: 1. Make sure the line is plugged in the channel indicated and appropriate switch connections are made. 2. Examine the line cord for damages. Replace the cord if it is damaged. 3. Plug the line into a telephone set and make sure it works. Use the following steps to test the line: a. Check the telephone for a dial tone. Most switches provide a dial tone. b. Dial the number of the test telephone from another telephone. Make sure it rings and the connection is established. c. Dial another number from the test line. Make sure the connection is established. d. If these tests do not pass, consult your network or switch administrator for help. If these tests pass, plug a known working line into the channel indicated. The system must place the channel in service automatically. If the alarm fails to resolve, contact your remote support center. Alarms requiring remote support center contact If you receive the following alarms, contact your remote support center. ID VP CGEN 2 VP CGEN 4 Description The system cannot access a system table, possibly because of corruption. System functionality is severely impaired. The system failed to receive a message because an internal process cannot communicate with other internal processes. System functionality is severely impaired.

85 Page 88 of 304 VP CGEN 5 VP CGEN 6 VP CGEN 7 VP CGEN 8 VP CGEN 11 VP CGEN 12 VP CGEN 17 VP CGEN 18 VP CGEN 21 VP CGEN 22 VP CGEN 25 VP CGEN 27 VP CGEN 31 VP CGEN 32 VP CGEN 34 VP CGEN 37 VP CGEN 38 VP CGEN 39 VP CHRIN 1 The system cannot communicate with a process. System functionality is severely impaired. The system failed to start up properly. System functionality is severely impaired. The system failed to allocate memory internally for data. System functionality is severely impaired. Cannot access analog port boards. The cards are unusable. The system is unable to answer or process telephone calls. The system failed to perform the indicated function on a voice channel or an analog port board. System functionality is severely impaired. The system failed to perform the indicated function on a voice channel or an analog port board. Card functionality is impaired. The system failed to save circuit card configuration changes. The system will lose shared memory updates during a restart or a reboot. Call processing will probably not be affected until a reboot or a restart. The system detected a hardware failure on a voice channel or an analog port board. Card functionality is impaired. An internal software error occurred when the system was identifying channel characteristics during a restart or a reboot. After the reboot or the restart, a channel is unusable. The system failed to reset the restriction list for a channel. System functionality could be impaired if applications are assigning resource restrictions to channels. A service registration file has a bad format or is the wrong version. The service corresponding to this registration file might be started incorrectly. If the service is not started correctly, it will not function properly. The system could not open a file. The system detected an error in describing groups to the Resource Manager. Applications that are using the equipment group might not function correctly. The system is unable to read the function resource characteristics. The system failed to perform an action on a file. The system experienced difficulty while it was enabling a feature license. The text-to-speech feature is not available. Other features on the system already enabled will not be affected. The system experienced difficulty while it was enabling a feature license. The text-to-speech feature is not available. Other features on the system already enabled will not be affected. The system experienced failure while it was enabling a feature license. The text-to-speech feature is not available. Other features on the system already enabled will not be affected. The system detected an error while it was describing channel characteristics to the Resource Manager. System functionality is severely impaired.

86 Page 89 of 304 VP CPUPERF 4 VP CRON 2 VP DSKMG 1 VP DSKMG 2 VP INIT 1 VP INIT 5 VP INIT 6 VP MTC 1 VP MTC 7 VP MTC 9 VP MTC 10 VP MTC 13 VP SF_VXMDI 2 VP SF_VXMDI 3 VP SF_VXMDI 4 VP SF_VXMDI 5 VP SOFTWARE 15 The system is using too much kernel memory (kmem). A system process has been operating for over 24 hours. The indicated file cannot be accessed. Applications that need to reserve speech files could fail. An application cannot be reserved by a file. Applications that need to record to the file will be incomplete. The system configuration from the previous operation is completely lost, so the system is using default values. Services must be reassigned to channels, the channels placed into service, and circuit card functionality specified for the system to operate under any configuration other than the default settings. The system might not process telephone calls until after the system is readministered. The system cannot save configuration data to the hard disk. If the voice system is stopped and started, some or all of the voice system's administered values could be lost, and system functionality will be severely impaired. The system is having trouble with determining the identity of an analog port board. The card is not operational. Call processing could be impaired. A card is unable to provide TDM clock to the system, and the card state has changed to BROKEN. This alarm can indicate a possible hardware problem with the card. Applications dependent on this card will not function. An internal software error occurred during a request for a resource or a release. The system could not process the request, and a card or channel might not be available. An internal software error occurred while the system was attempting to download firmware to a circuit card. TDM diagnostics failed one or more diagnostics tests. One or more circuit cards might be in the BROKEN state and unable to function. Applications dependent on the card will not function. One of the circuit cards is in the BROKEN state because it is not receiving clock. The system will not be able to use the circuit card in the BROKEN state. The system experienced an abnormal termination of a Message Networking FAX Messaging process. The fax transmission that was occurring at that time failed. The system experienced an illegal transition. The fax transmission that was occurring at that time failed. The system experienced an internal assertion failure. The fax transmission that was occurring at that time failed. A driver call failed. The fax transmission that was occurring at that time failed. The system detected an invalid value or a nonexistent overhead file. The system will use the default overhead values, which can adversely affect performance. If the default overhead values are acceptable, system operations will not be affected.

87 Page 90 of 304 VP THR 2 VP THR 3 VP THR 4 VP TRIP 1 VP TRIP 3 VP TRIP 4 VP UNIX 3 VP UNIX 4 VP UNIX 5 VP UNIX 6 VP VCHKOANM 02 VP VROP 2 VP VROP 4 VP VROP 5 The system exceeded the minor threshold level for messages. This alarm typically indicates that too many messages of a particular type are being generated. The system exceeded the minor threshold level for messages. This alarm typically indicates that too many messages of a particular type are being generated. The system exceeded the major threshold level for messages. This alarm typically indicates that too many messages of a particular type are being generated. The system is unable to communicate with the analog port boards. The system is unable to process telephone calls on the channels. The system received excessive simultaneous signals from the network. The voice system is unable to process calls on the analog port boards possibly due to network or PBX administration. Some network or PBX parameters, such as howler tone, might need to be tuned differently. PBXs generate howler tone if a channel is off hook for a certain amount of time. A howler tone can consist of a series of touchtones, including * and #. Each of these touchtones results in a separate event in the channels. The rate at which these events are generated could be beyond what the system can handle. The system detected a speech break during a voice coding or playback session. The impact of this error is not severe, and no action is needed if the message is reported less frequently than the threshold limit. The impact could be significant if this message occurs more than the currently set threshold limit. The operating system kernel detected an error, and the system software placed a copy of the message into the log. The type of error present will determine the impact on the system. These errors might not cause the system to stop (panic), but they usually indicate that system functionality is impaired. The operating system kernel detected an error, and the system software placed a copy of the message into the log. The type of error present will determine the impact on the system. The operating system kernel detected an error, and the system software placed a copy of the message into the log. The type of error present will determine the impact on the system. The operating system kernel detected an error, and the system software placed a copy of the message into the log. The type of error present will determine the impact on the system. More than 90 percent of purchased voice hours are used. The system cannot record or add a phrase. Phrases already recorded will continue to play properly. A voice function might have failed, and the system canceled the request. Callers affected by the error will hear nothing. The system will not disconnect the call until the caller disconnects. Each time this failure occurs, the system will generate one message. Erroneous speech playback or coding might have occurred. The speech that was heard or recorded might have been terminated prematurely or been replaced with other speech. Subsequent speech coding or playback

88 Page 91 of 304 could also be affected until the system is restarted. VP VROP 6 VP VROP 7 VP VROP 8 VP VROP 10 VP VROP 11 VP VROP 12 VP VROP 14 VP VROP 15 VP VROP 18 VP VROP 19 VP VROP 20 VP VROP 22 VP VOICE_PORT 1 The system is unable to read a speech configuration file or the file has an invalid or duplicate entry. The system will use default values for nonexistent entries until the problem is corrected. However, the default numbers could be unsatisfactory and could cause load or performance problems. Phrase creation failed because of insufficient space in the speech file systems. This condition had an impact on administrative commands or caused the message recording to fail. Additional similar attempts will also fail. An initialization failure occurred. A failure occurred while the system was performing an action on a phrase. The system aborted the action. This alarm could be caused by an excessive voice activity load. The system has insufficient speech buffers for the number of channels in use. Each time this alarm occurs, an action failed. An attempt to add a new phrase to the speech file system failed because the phrase limit was exceeded. This condition could have had an impact on administrative commands or caused message recording to fail. Other attempts will also fail. The system failed to access the speech file indicated. Applications that need access to this file will be incomplete. The system was attempting to copy or add a phrase to the speech file system, and the attempt failed. This failure usually occurs during backups or restores. The system has failed to play or record messages. This is likely to continue to occur until the problem is resolved. A time-out failure occurred while the system was performing an action on a phrase, and the system aborted the action. This alarm could be caused by excessive load on the system or a problem with an analog port board. A VROP application error occurred. The system could not reserve a file. Applications that need to record to the file will be incomplete. More than 25 percent of the system's channels are not operational.

89 Page 92 of 304 Events An event is an informational message about system activities that indicates routine conditions that can lead to an alarm. For example, an event is logged when the system is rebooted. The Message Networking system displays events in the Server Events Log. For information about how to access the Server Events Log, see the Server Events Log. The event descriptions and resolution procedures in this section are organized by the event application identifier (ID), which is the two-letter code used to identify the application or subsystem for which an event is being generated. For example, the application ID for the MT BKRST029 event is MT. If you want to find information about the MT BKRST029 event, see the MT (Maintenance) events information. The event information is organized as follows: Message Networking alarms and events AS (Access Security Gateway) events MT (Maintenance) events SM (Station Manager) events SW (Switch Integration) events VP (Voice Platform) events

90 Page 93 of 304 AS (Access Security Gateway) events This topic provides information about the events generated by the AS application, which indicate a problem with the Access Security Gateway (ASG). Customer-resolvable events The following events can be resolved by the system administrator. AS ASG002 Description: Someone tried, and failed, to log in to the Message Networking system using an ASG-protected login. Repair Procedure: 1. Identify the employee who is using the failing login ID. Verify if the employee assigned to work on the system has been having difficulty logging in or needs additional training. 2. Test the login. See How to log in with ASG. If the login fails the key might be having problems or the initial code might have been entered incorrectly. Do the following: a. Re-administer the key. See Changing the ASG secret key number for an ASG login. The login making the change must be equal to or higher than the login being changed. For example, the sa login can change the sa, craft, and dadmin logins. b. Test the login after changing the ASG secret key. See How to log in with ASG. If the login continues to fail, contact your remote support center. AS ASG004 Description: This event is a security information message. It reports that a subscriber is attempting to make changes to the system, such as adding a subscriber, and the login ID in use does not have permission to do so. This event reports the exact action that failed, such as adding a subscriber. Repair Procedure: No corrective action is necessary.

91 Page 94 of 304 MT (Maintenance) events This topic provides information about the events generated by the MT application. These events indicate a problem with the maintenance system. Customer-resolvable events The following events can be resolved by the system administrator: BKRST001 BKRST009 BKRST015 BKRST029 MT BKRST001 Description: The system successfully completed a backup. Repair Procedure: No corrective action is necessary. MT BKRST009 Description: The system has detected a missing backup file or a missing directory. Repair Procedure: No corrective action is necessary. MT BKRST015 Description: The system successfully completed a restore. Repair Procedure: No corrective action is necessary. MT BKRST029 Description:

92 Page 95 of 304 The system completed a partial nightly backup. Repair Procedure: No corrective action is necessary. Event requiring remote support center contact If you receive the following event, contact your remote support center. ID MT BKRST008 Description The system is missing a backup file or a directory.

93 Page 96 of 304 SM (Station Manager) events This topic provides information about the events generated by the SM application. These events indicate a problem with the Station Manager. Customer-resolvable events The following events can be resolved by the system administrator: SM104 SM107 SM201 SM SM104 Description: The system received a script message from the wrong channel or mode. Repair Procedure: No corrective action is necessary. SM SM107 Description: A timeout occurred. An audit on the switch side can cause this condition. Repair Procedure: If the system issues this message frequently, contact your remote support center. SM SM201 Description: The system failed to locate the indicated user. Repair Procedure: Update the subscriber information. Events requiring remote support center contact If you receive the following events, contact your remote support center. ID Description

94 Page 97 of 304 SM SM101 SM SM102 SM SM103 SM SM105 SM SM106 SM SM108 The Message Networking system cannot get certain application information. The application code is too large. The system could not find the switch ID. The system is reporting that no switch is active. The switch link is down. A message-waiting lamp (MWL) update failed for a subscriber. The MWL is an indicator that alerts subscribers that they have received new mail messages.

95 Page 98 of 304 SW (Switch Integration) events This topic provides information about the events generated by the SW application, which indicate a switch integration problem. Customer-resolvable alarms The following events can be resolved by the system administrator. IF140 IF150 OVL080 OVL090 OVL220 OVL260 SE160 SW100 SW110 SW220 TY130 TY150 TY170 SW IF140 Description: MWI blackout period starts. MWI updates will not occur during this period. Repair Procedure: No corrective action is necessary. SW IF150 Description: MWI blackout period ends. MWI updates will resume. Repair Procedure: No corrective action is necessary. SW OVL080 Description: The host switch link is up. The event message displays the switch number. Repair Procedure:

96 Page 99 of 304 No corrective action is necessary. SW OVL090 Description: The remote switch link is up. The event message displays the switch number. Repair Procedure: No corrective action is necessary. SW OVL220 Description: The oehs process is ready to handle telephone calls. The initialization is successful, and the system has created the sockets. This event indicates the successful installation of the package. Repair Procedure: No corrective action is necessary. SW OVL260 Description: The system received a normal disconnect message from the switch. This event can be a part of a normal switch shutdown. Repair Procedure: No corrective action is necessary. SW SE160 Description: A "block" message is received from the switch. MWI updates will not occur. Repair Procedure: No corrective action is necessary. SW SW100 Description: A process is starting. The log will display the name of the process. Repair Procedure: No corrective action is necessary.

97 Page 100 of 304 SW SW110 Description: A process is starting. The log will display the name of the process. Repair Procedure: No corrective action is necessary. SW SW220 Description: The system was unable to write to a file. Repair Procedure: No corrective action is necessary. SW TY130 Description: The switch is blocked from MWI updates because: An MWI blackout period occurred. The switch sent a pause MWI message. Repair Procedure: No corrective action is necessary. SW TY150 Description: The switch might be sending bad information to the system. Calls might not be integrated. Repair Procedure: No corrective action is necessary. SW TY170 Description: Link monitoring is used for this switch. Repair Procedure: No corrective action is necessary.

98 Page 102 of 304 VP (Voice Platform) events This topic provides information about the events generated by the VP application, which indicate a voice platform problem. Customer-resolvable events The following events can be resolved by the system administrator: ADMIN001 CGEN020 CGEN023 CGEN036 CRON001 FAX004 FAX005 ICK003 ICK004 ICK005 ICK006 ICK009 VP ADMIN001 Description: ICK010 ICK011 INIT003 INIT004 INIT008 KERNEL_MEMPEG MTC002 MTC004 MTC005 MTC008 MTC011 MTC012 RAID003 RAID004 SPDM008 TRIP002 TRIP005 TRIP006 TRIP007 VCHK001 VROP021 VROP023 The system uses this event to log command executions for display in the Administration History Log or in the Maintenance Log. ADM001 messages show the Process ID, process name, executed command, and status. Repair Procedure: No corrective action is necessary. VP CGEN020 Description: The system has no service assigned and does not answer calls. Repair Procedure: See Voice system administration for information on assigning service. VP CGEN023

99 Page 103 of 304 Description: A channel was returned to the default owner because of an abrupt exit of the prior channel owner. Any outstanding activities on the channel are canceled, and the channel is made available to take new calls. Repair Procedure: No corrective action is necessary. VP CGEN036 Description: This is an informational message that occurs at startup. Repair Procedure: No corrective action is necessary. VP CRON001 Description: The system detected that CRON was not running and started it. Repair Procedure: No corrective action is necessary. VP FAX004 Description: The system cannot get the transmitting subscriber's information. Repair Procedure: This is an informational message. No corrective action is necessary. VP FAX005 Description: A general fax error occurred, such as a disconnect. Repair Procedure: This is an informational message. No corrective action is necessary. VP ICK003 Description: The integrity checking process received a command request.

100 Page 104 of 304 Repair Procedure: No corrective action is necessary. VP ICK004 Description: The integrity checking process was completed. Repair Procedure: No corrective action is necessary. VP ICK005 Description: The integrity checking process changed the state of the operating system kernel auto-reboot flag. The Maintenance Log message lists the new state. Repair Procedure: No corrective action is necessary. VP ICK006 Description: The integrity checking process took the identified action. The Maintenance Log message lists the action. Repair Procedure: No corrective action is necessary. VP ICK009 Description: The integrity checking process found and corrected a problem with the specified file. Repair Procedure: No corrective action is necessary. VP ICK010 Description: The integrity checking process found a file specified by a rule that does not meet the requirements of the rule. Depending upon the rule, the integrity checking process could attempt to correct the problem or simply report it. Repair Procedure:

101 Page 105 of 304 If the message does not indicate that the problem has been automatically corrected, contact your remote support center. VP ICK011 Description: The integrity checking process is changing to the run level listed in the message. A change in run levels affects which rules are in force. Repair Procedure: No corrective action is necessary. VP INIT003 Description: The system recognized a new analog port board. Repair Procedure: No corrective action is necessary. VP INIT004 Description: The system has taken administrative action to renumber channels. Repair Procedure: No corrective action is necessary. VP INIT006 Description: The system cannot determine the board ID for an analog port board. The card is not operational and the card's resources are not available. Call processing might be impaired. Repair Procedure: Reboot the system. If the problem persists, contact your remote support center. VP INIT008 Description: The system detected a change in the voice system hardware and automatically renumbered the channels. Repair Procedure:

102 Page 106 of 304 No corrective action is necessary. VP KERNEL_MEMPEG Description: The system is using too much kernel memory (kmem). Repair Procedure: Determine the frequency of the event's occurrence. If the event is occurring: VP MTC002 Description: Only during the system's peak traffic hours, you might need to purchase additional resources. Contact your sales representative to purchase additional resources. At times other than the peak traffic hours, contact your remote support center. The card state for the identified card or channel changed as the result of an external action. Repair Procedure: No corrective action is necessary. VP MTC004 Description: The system started diagnostics on the card listed in the Maintenance Log message. Repair Procedure: No corrective action is necessary. VP MTC005 Description: The indicated card successfully passed all performed diagnostics. Repair Procedure: No corrective action is necessary. VP MTC008 Description: A clock is present on the card listed in the Maintenance Log message. Repair Procedure:

103 Page 107 of 304 No corrective action is necessary. VP MTC011 Description: TDM diagnostics passed. Repair Procedure: No corrective action is necessary. VP MTC012 Description: TDM diagnostics started. Repair Procedure: No corrective action is necessary. VP RAID003 Description: A RAID array rebuild has started. Repair procedure: No corrective action is necessary. VP RAID004 Description: A RAID array rebuild has completed. Repair procedure: No corrective action is necessary. VP SPDM008 Description: The speech disk manager started. Repair Procedure: No corrective action is necessary. VP TRIP002

104 Page 108 of 304 Description: Corrupt data has been detected on the system. Repair Procedure: No corrective action is necessary. This is an informational message. VP TRIP005 Description: The channel listed in the message lost loop current. If the loop current is lost during a call, the call terminates and the system automatically takes the channel out of service. The channel automatically returns to service when the loop current returns. Repair Procedure: No corrective action is necessary. This is an informational message. VP TRIP006 Description: The loop current has been restored. Repair Procedure: No corrective action is necessary. This is an informational message. VP TRIP007 Description: The channel listed in the message lost loop current and changed its state to FOOS (facility out-of-service). If the loop current is lost during a call, the call terminates and the system automatically takes the channel out of service. The channel automatically returns to service when the loop current returns. Repair Procedure: 1. Verify that the line is plugged into the channel indicated and the appropriate switch connections are made. 2. Examine the line cord for damages, and replace the cord if it is damaged. 3. Test the line by plugging in a telephone set. 4. If the problem persists, contact your remote support center. VP VCHK001 Description: More than 80% of the purchased hours are being used. Repair Procedure:

105 Page 109 of Stop the messaging software (voice system). 3. Start the messaging software (voice system). 4. If the problem still exists, purchase additional hours of speech. For more information, contact your Avaya sales representative. VP VROP021 Description: The system reached the maximum number of customer input and output processes, therefore delaying speech playback. Excessive load on the system can cause this condition. Repair Procedure: No corrective action is necessary. This is an informational message that indicates a condition that is not severe. VP VROP023 Description: The system experienced a stutter in speech. Repair Procedure: No corrective action is necessary. Events requiring remote support center contact If you receive the following events, contact your remote support center. ID VP CGEN001 VP CGEN024 VP CGEN026 VP CIOX001 VP CIOX002 VP CPU_DATAPEG VP ICK001 VP ICK002 VP ICK007 Description The system detected an unexpected message about internal communications. The system failed to execute a process. The system experienced a timeout failure when it attempted to idle the specified channel. The indicated file cannot be accessed for the reason listed in the message. Applications requiring playing from or recording to the file will be incomplete. The indicated file cannot be reserved for the reason listed in the message. Applications requiring recording to the file will be incomplete. The system s CPU usage exceeded configuration guidelines. The integrity checking process has received an invalid request. The system is ignoring the request. The integrity checking process encountered an internal error. The directory location for the integrity checking process s file is accessible by unauthorized users. The file is not secure and could be vulnerable to corruption that could affect system functionality.

106 Page 110 of 304 VP ICK008 VP INIT002 M_CGEN024 VP MTC003 VP PAGE_SCANSPEG VP THR001 VP UNIX001 VP UNIX002 VP VROP001 VP VROP013 VP VROP016 VP VROP017 VP WIO_DATAPEG A file used by the integrity checking process is accessible by unauthorized users. The file is not secure and could be vulnerable to corruption that could affect system functionality. The system cannot find a circuit card. The system failed to execute a process. The card state for the identified card changed to broken. Applications dependent on this card will not function. The system is experiencing too many page scans per second. The system exceeded the threshold level for messages. The operating system kernel detected an error and logged it to the system console. The Message Networking system software then placed a copy of the message into the Maintenance Log. UNIX001 messages are informational messages. The impact of the event on voice system functionality depends on the content of the message and the severity of the problem. The operating system kernel detected an error. The type of error present then determines the impact on the system. These errors might not cause the system to stop, but they usually indicate that system functionality is impaired. The user s attempt to run an administrative command, for example, list phrases, add a phrase to the speech file system, copy a phrase from the speech file system to an operating system file, or erase a phrase, has failed. Call processing is not affected. The system is not able to guarantee that speech gaps will not occur. Gaps can occur between phrases or within a phrase. A phrase in the speech file system is corrupt. The phrase cannot be played or removed until the problem is corrected. Call processing for other phrases is not affected. The system detected some type of anomaly while performing the action listed in the Maintenance Log entry. The voice response action might not have been completed successfully. The system s input/output wait times exceeded the configuration guidelines.

107 Page 111 of 304 Testing alarm origination For the alarm origination type used by the system (MODEM DIALOUT or SAL or SNMP (INADS or OAM) or INTERNET), test alarm origination verifies that alarms are logged correctly and are sent to the correct destination.the Message Networking system responds to configuration requests and sends alarm and resolution event notifications to specified Network Management System (NMSs) through the type of alarm origination selected. Note: This test requires the receiving machine (either Avaya Services or SAL or SNMP (INADS or OAM)) to be set up properly by the appropriate party and ready to receive alarms. For information about setting up SNMP, see Administering SNMP. To test alarm origination: 1. In the Administration menu, under Diagnostics, click Alarm Origination > Execute Alarm Origination Test. The system displays the Execute Alarm Origination Test page. 2. Click Run Test to execute the Alarm Origination Test. The system displays a message that the tests will run in the background and can take up to five minutes to complete. 3. If the alarm origination test must use the modem, log off as quickly as possible. 4. Wait approximately for five minutes for the test alarm to be acknowledged and resolved. 5. In the Administration menu, under Diagnostics, click Alarm Origination > Review Latest Test Results to view the test results.

108 Page 112 of 304 Viewing Alarm Origination Test results Use the Review Latest Test Results page to view the results of the last Alarm Origination Test that was run. To view the Alarm Origination Test results: 1. From the Administration menu, select Diagnostics > Alarm Origination > Review Latest Test Results. The system displays the Review Latest Test Results page: If a test is currently running in the background, a message displays that an Alarm Origination Test is in progress. If this message displays, wait a minute or two and view the test results again. If the last test is complete, a message displays that the Alarm Origination Test was successful. If no tests have been run, a message displays that there are no previous test results.

109 Page 113 of 304 Resetting alarm origination If system attempts to make an alarm call repeatedly fail, the system stops making attempts to report existing alarms, even if additional alarms subsequently occur. The test alarm origination function will also fail if the system is in this state. Caution! The problem that prevented the alarm calls from being successfully completed must be resolved. If it is not, then alarm origination will simply stop again after repeated call attempts fail. To allow the system to begin making calls about alarms again: 1. In the Administration menu, under Alarming, click Alarm Configuration. The system displays the Configure Alarms page. 2. Select the alarm origination type (MODEM DIALOUT or SAL or SNMP or INTERNET) from the Alarm Origination drop-down list. For more information about the alarm origination types, see the Online help. 3. Click Save. The system restores the alarm origination.

110 Page 114 of 304 System reboot event log error An error message stating System Event Log Full might be displayed on S3500-H servers. Description: During a system reboot, the boot sequence pauses for a couple of seconds, and the message System Event Log Full is displayed in red text. The boot sequence then continues normally. Repair procedure: You do not need to take any action. This message refers to an event log that the system does not use. The log records new entries every time the system is booted. If the system is rebooted often, the event log becomes full. The System Event Log Full error message has no impact on system performance.

111 Page 115 of 304 Safety information Safety Information includes: Audience General safety rules Safety inspection checklist Electrical safety rules Lithium battery Note: See Protecting against ESD damage for more information about safely handling equipment. Audience This equipment is intended to be serviced by Avaya trained service personnel only. General safety rules Follow these rules to ensure general safety. Observe good housekeeping in the area of the system units during and after maintenance. Place removed covers and other parts in a safe place, away from all personnel, while you are servicing the system unit. Keep your tool case away from walk areas so that other people will not trip over it. When lifting any heavy object: 1. Make sure you can stand safely without slipping. 2. Distribute the weight of the object equally between your feet. 3. Use a slow lifting force. Never move suddenly or twist when you attempt to lift. 4. Lift by standing or by pushing up with your leg muscles; this action removes the strain from the muscles in your back. Do not attempt to lift any objects that weigh more than 16 kg (35 lb) or objects that you think are too heavy for you. Do not perform any action that causes hazards to the customer, or that makes the equipment unsafe. Before you start the system unit, ensure that other service representatives and the customer s personnel are not in a hazardous position. Do not wear loose clothing that can be trapped in the moving parts of a system unit. Ensure that your sleeves are fastened or rolled up above your elbows. If your hair is long, fasten it. Insert the ends of your necktie or scarf inside clothing or fasten it with a nonconductive clip, approximately 8 centimeters (3 inches) from the end. Do not wear jewelry, chains, metal-frame eyeglasses, or metal fasteners for your clothing. Metal objects are good electrical conductors. Wear safety glasses when you are working in any conditions that might be hazardous to your eyes. After service, reinstall all safety shields, guards, labels, and ground wires. Replace any safety device that is worn or defective. Reinstall all covers correctly before returning the system unit to service. WARNING!

112 Page 116 of 304 To prevent access to electrical hazards by unauthorized personnel and to ensure continued compliance to international radiated emissions requirements, all captive screws must be securely tightened such that they cannot be loosened without the use of a tool. Safety inspection checklist The intent of this checklist is to help you identify potentially unsafe conditions related to this product. Each system unit, as it was designed and built, had required safety items installed to protect users and service personnel from injury. If any unsafe conditions are present, you must determine how serious the apparent hazard could be and whether or not you can safely continue without first correcting the problem. Consider these conditions and the safety hazards they present: Electrical hazards, especially primary power (primary voltage on the frame can cause serious or fatal electrical shock) Explosive hazards, such as a damaged monitor face or bulging capacitor Mechanical hazards, such as loose or missing hardware Perform the following safety checks when servicing this unit: 1. Check exterior covers for damage (loose, broken, or sharp edges). 2. Shut down the system and unplug the AC power cords. 3. Check the power cord for: A third-wire ground connector in good condition. Use a meter to measure third-wire ground continuity for 0.1 ohm or less between the external ground pin and frame ground. The power cord should be the appropriate type. Insulation must not be frayed or worn. 4. Remove the top cover. 5. Check inside the unit for any obvious unsafe conditions, such as metal filings, contamination, water or other liquids, or signs of fire or smoke damage. 6. Check for worn, frayed, or pinched cables. 7. Check that the power-supply cover fasteners (screws or rivets) have not been removed or tampered with. 8. If you notice any damage, see Replacing system components. Electrical safety rules Electrical current from power, telephone, and communication cables can be hazardous. To avoid any shock hazard, you should disconnect all power cords and cables as described in Getting inside the chassis. Observe the following rules when working on electrical equipment: Find the room emergency power-off (EPO) switch, disconnecting switch, or electrical outlet. If an electrical accident occurs, you can then operate the switch or unplug the power cord quickly. Do not work alone under hazardous conditions or near equipment that has hazardous voltages. Disconnect all power before: Performing a mechanical inspection Working near power supplies Removing or installing main units Before you start to work on the system unit, unplug the power cord. If you cannot unplug it, ask the customer to power-off the wall box that supplies power to the system unit and to lock the wall box in the off position. If you need to work on a system unit that has exposed electrical circuits, observe the following precautions:

113 Page 117 of 304 Make sure that another person, familiar with the power-off controls, is near you. Another person must be there to switch off the power if necessary. Use only one hand when working with powered-on electrical equipment; keep the other hand in your pocket or behind your back. This may prevent a current from passing through your body. When using testers, set the controls correctly and use the approved probe leads and accessories for that tester. Stand on suitable rubber mats (obtained locally, if necessary) to insulate you from grounds such as metal floor strips and system unit frames. Regularly inspect and maintain your electrical hand tools for safe operational condition. Do not use worn or broken tools and testers. Never assume that power has been disconnected from a circuit. First, verify that it has been powered off. Always look carefully for possible hazards in your work area. Examples of these hazards are moist floors, non-grounded power extension cables, power surges, and missing safety grounds. Do not touch live electrical circuits with the reflective surface of a plastic dental mirror. The surface is conductive. Touching it can cause personal injury and system unit damage. Use only approved tools and test equipment. Some hand tools have handles covered with a soft material that does not insulate you when working with live electrical currents. Many customers have, near their equipment, rubber floor mats that contain small conductive fibers to decrease electrostatic discharges. Do not use this type of mat to protect yourself from electrical shock. If an electrical accident occurs: Use caution. Do not become a victim yourself. Switch off power. Send another person to get medical aid. Lithium battery The S3500-H, S3210R and S3500 Basic servers contain a lithium battery that is accessible to service personnel only. Caution! Risk of explosion if battery is replaced by an incorrect type. Dispose of used batteries according to the instructions.

114 Page 118 of 304 Protecting against ESD damage Any system component that contains transistors or integrated circuits should be considered sensitive to electrostatic discharge (ESD). ESD damage can occur when there is a difference in charge between objects. Protect against ESD damage by equalizing the charge so that the system unit, the part, the work mat, and the person handling the part are all at the same charge. Packaging materials that contain ESD sensitive components are usually marked with a yellow and black warning symbol. Caution! You must observe proper grounding techniques to prevent the discharge of static electricity from your body into ESD sensitive components. To avoid damaging ESD sensitive components: Keep the parts in protective packages until they are ready to be inserted into the product. Handle the components only after attaching a wrist strap to your bare wrist. Attach the other end of the wrist strap to a ground that terminates at the system ground, such as any unpainted metallic chassis surface. Handle a circuit card by the faceplate or side edges only. Hold devices such as hard disk drives in the same manner. The ESD sensitive area of these components is located on the bottom surface. See How to hold a circuit card. Caution! Make sure that your palm is not in contact with the non-component side of the board. Keep components away from plastics and other synthetic materials such as polyester clothing. Most clothing is insulative and retains a charge even when you are wearing a wrist strap. Do not hand components to another person unless that person is grounded at the same potential level. In general, avoid contact with other people. Use the black side of a grounded work mat to provide a static-free work surface. The mat is especially useful when handling ESD-sensitive devices. Make sure that the ESD protective devices you use have been certified (ISO 9000) as fully effective. Note: Use product-specific ESD procedures when they exceed the requirements noted here.

115 Page 119 of 304 Getting inside the chassis To open up the system chassis of S3210R, S3500 Basisc and S3500-H servers, follow these steps: Removing power from the system Removing the top cover Replacing the top cover Restoring power to the system To open up the system chassis for S8800, see Maintaining the S8800 server for Avaya Message Networking guide (pdf).

116 Page 120 of 304 Shutting down the system To shut down the system: 1. On the Message Networking administration Web interface, under Utilities, click Shutdown Server. The system displays the Shutdown Server page. 2. In the Wait Time field, enter a number between 0 and 600. This time designates how many seconds the system is to wait for calls in progress to finish before stopping the voice system. The system prevents new calls immediately regardless of the wait time selected. If any calls are still in progress after this time, the system drops the calls and proceeds with stopping the voice system. A wait time of zero indicates an indefinite wait time until all current calls are completed. 3. Click Shutdown. The following message displays: "The system is going to be rebooted. You will lose your access to this system after this action takes place. Are you sure you want to do this?" 4. Click OK. Some messages might appear as the system shuts down: "Stopping voice system...shutting down system." When the system displays the above message, the system is completely shut down.

117 Page 121 of 304 Removing power from the system Before you open a machine's chassis, you must remove power to the system as follows: 1. Shut down the system: Shut down the system. Remove any disc from the CD/DVD drive. Turn off the power by pressing the power button on the front of the PC 2. Verify that the green power lamp on the front of the PC is dark. If not, press the power button to power off the unit. See: S3210R front view S3500-H front view S3500 Basic front view Note: Users in the United Kingdom who have a modem attached to the system must disconnect the telephone line from the system unit before unplugging any power cords. 3. Unplug all power cords from the AC connector on the rear of the machine. For the S3210R, locate the power switch located at the back of the server, push the rocker switch to turn off power, and then unplug the AC cord. See S3210R back view. For the S3500-H, unplug the AC cord from each power supply. See S3500-H back view. For the S3500 Basic, unplug the AC cord from the power supply. See S3500 Basic back view. 4. Continue with Removing the cover.

118 Page 122 of 304 S3210R front view (without front bezel) 1 Handles 2 Front fan 3 On/off switch 4 System reset switch 5 Power LED indicator 6 Hard disk drive LED indicator 7 USB ports 8 DVD-RW

119 Page 123 of 304 S3500-H front view 1 Chassis handles 2 Hard disk drive bays - 4 are used for S3500-H 3 Labels for disk drive bays 0 to 5: - S3500-H uses bays 0, 2, 3, and 5 4 Blue LED indicates that disk drive is present 5 Orange LED indicates disk drive behavior: - flashing orange=disk drive active - steady red=disk drive failed 6 USB port 7 System reset switch 8 System power on/off button 9 Audible alarm reset switch for power supply 10 System power indicator 11 Disk drive access indicator 12 Corporate LAN indicator always on when corporate LAN cable is connected 13 Private LAN indicator 14 Power supply failure indicator 15 DVD recorder

120 Page 124 of 304 Message Networking Help Getting Started Administration Installation Maintenance Reference S3500 Basic Offer - Front View 1 Chassis handles 2 Hard disk drive bays - MN uses 1 drive located in bay 3 3 Labels for disk drive bays 0 to 5: MN uses only drive bay 3 4 USB port 5 System reset switch 6 System power on/off button 7 System power indicator 8 Disk drive access indicator 9 Corporate LAN indicator-always on when corporate LAN cable is connected 10 Chassis DVD player (ROM)

121 Page 125 of 304 S3210R back view 1 Screws for top cover 2 Power supply 3 AC power receptacle 4 On/off switch 5 Mouse connector 6 Keyboard connector 7 USB ports 8 Serial port (COM1) 9 Parallel port (not used) 10 Video connector 11 USB ports 12 LAN interface 13 Serial port (COM2) 14 Analog voice cards

122 Page 126 of 304 S3500-H back view 1 Redundant power supplies: - green LED=power supply active - amber LED=power supply failed 2 AC power receptacles 3 Screw for top cover 4 USB ports 5 Mouse connector 6 Keyboard connector 7 Serial port (COM1) 8 Video connector 9 Corporate LAN interface 10 Private LAN interface 11 Serial port (COM2) used for the Remote Maintenance Board (RMB) 12 Analog voice cards 13 Remote Maintenance Board

123 Page 127 of 304 Message Networking Help Getting Started Administration Installation Maintenance Reference S3500 Basic Offer - Back View 1 Power supply 2 AC power receptacle 3 Screw for top cover 4 USB ports 5 Mouse Connecter 6 Keyboard Connecter 7 Serial port (COM1)-not used 8 Video connector 9 Corporate LAN interface 10 Private LAN interface Note: Not used for Message Networking. 11 Serial port (COM2) 12 PCI slots to accommodate up to (3) Dialogic analog boards (D/41JCT-LS 4-port)

124 Page 128 of 304 Removing the top cover The top cover protects the internal components. You must remove the cover to access the internal components. The steps you complete to remove the top cover are determined by the server being used: S8800 2U. To see the steps for removing the top cover of S8800 2U, see Maintaining the S8800 server for Avaya Message Networking guide (pdf). S3500-H S3500 Basic S3210R Warning! Damage from electrostatic discharge is possible. See Protecting against ESD damage for more information. Removing the top cover on an S3500-H and S3500 Basic To remove the top cover on an S3500-H and S3500 Basic servers: 1. Shut down the system and remove the AC power cords. 2. For a stackable (desktop) configuration: Remove any units stacked on top of the server you need to access. 3. Remove the front bezel. See Removing or replacing the S3500-H and S3500 Basic front bezel. 4. Loosen the screw that attaches the top cover located to the back of the chassis. See Removing or replacing the S3500-H and S3500 Basic cover. 5. For a rack-mounted unit, slide the server forward. Note: To get sufficient cable slack, you might need to unplug some cables at the back of the server. Label all cables so you can easily reconnect them. See S3500-H back view and S3500 Basic back view. Caution! For some procedures, you might need to remove the server from the rails. Ensure that you have a clear work area before you remove the server. For safety considerations, get another person to assist you in lifting the server. 6. With your thumbs, push down on the cover release buttons. While holding down the buttons, slide the cover toward the back of the server. See Removing or replacing the S3500-H and S3500 Basic cover. 7. Lift the cover off the chassis. The internal components are now accessible for replacement. See S3500-H internal view and S3500 Basic internal view. Removing the top cover on an S3210R To remove the top cover on an S3210R server: 1. Shut down the system and remove the AC power cords. 2. Open the front bezel. See Opening or closing the S3210R front bezel. 3. Remove the two screws located at the back of the chassis. See Removing or replacing the S3210R cover. 4. For a rack-mounted unit, slide the machine forward. Note: To get sufficient cable slack, you might need to unplug some cables at the back of the server. Label all cables so you can easily reconnect them. See S3210R back view. Caution! For some procedures, you might need to remove the server from the rails. Ensure that you

125 Page 129 of 304 have a clear work area before you remove the server. For safety considerations, get another person to assist you in lifting the server. 5. With your thumbs, push down on the cover release buttons. While holding down the buttons, slide the cover towards the back of the server. See Removing or replacing the S3210R cover. 6. Lift the cover off the chassis. The internal components are now accessible for replacement. See S3210R internal view.

126 Page 130 of 304 Removing or replacing the S3500-H and S3500 Basic front bezel Removing the front bezel 2 Press the tabs on the top of the front bezel to release it. 1 Tilt the bezel forward, and then lift it out. Replacing the front bezel 1 Insert the tabs on the bottom of the front bezel into the chassis. 2 Push the bezel upright until the two upper tabs snap into place under the front cover.

127 Page 131 of 304 Removing or replacing the S3500-H and S3500 Basic cover Removing the top cover 1. Loosen the screw latch for the top cover. 2. Push down on the cover release buttons and slide the cover toward the back of the server. Replacing the top cover 1. Set the cover on the chassis so that it is aligned with the sides and slightly overhangs the back of the server. Slide the cover toward the front of the server. 2. Tighten the screw.

128 Page 132 of 304 S3500 Basic - Internal view 1 Bracket for IDE drivers 2 DVD-ROM drive 3 Primary IDE connector for DVD-ROM 4 Hot-Swappable Fans 5 Memory Module (DIMM cards) 6 Server board 7 Main power connector 8 PCI card cage for Dialogic boards 9 PCI riser card 10 Power supply

129 Page 134 of 304 Opening or closing the S3210R front bezel Opening the front bezel 1 Turn the latch on the top of the bezel to the right. 2 Lower the bezel. Replacing the front bezel 2 Lift the bezel. 1 Turn the latch at the top of the bezel to the left until the bezel is secure.

130 Page 135 of 304 Removing or replacing the S3210R cover Removing the top cover 1 With your thumbs, push down on the cover release buttons. While holding down the buttons, slide the cover towards the back of the server. 2 Slide the cover off the back of the chassis. Replacing the top cover 2 Place the top cover on the chassis so that it overhangs the rear of the machine. 1 Slide the cover forward until it snaps into place.

131 Page 136 of 304 S3210R internal view 1 Circuit card hold-down bracket 2 Front bezel 3 Front fan 4 Hard disk drive 5 DVD-RW drive 6 Power supply 7 Rear fan 8 Memory module 9 Analog port board fastener

132 Page 138 of 304 Replacing the top cover The steps you complete to replace the top cover are determined by the server being used: S8800 2U. For instructions to replace the top cover of S8800 2U, see Maintaining the Avaya S8800 Server guide (pdf). S3500-H S3500 Basic S3210R Warning! Damage from electrostatic discharge is possible. See Protecting against ESD damage for more information. Replacing the top cover on an S3500-H and S3500 Basic The front bezel and top cover are removed for most maintenance procedures. To replace the top cover on an S3500-H and S3500 Basic server: 1. Position the cover so the straight edge is in front. See Removing or replacing the S3500-H and S3500 Basic cover. 2. Set the cover on the chassis so the cover is aligned with the sides and slightly overhangs the back of the server. 3. Slide the cover toward the front of the server until the cover fits snugly against the chassis. 4. For a rack-mounted unit, slide the machine back into the cabinet. 5. If you unplugged any cables, plug them in now. See S3500-H back view and S3500 Basic back view. 6. Tighten the screw at the back of the server to secure the top cover to the chassis. 7. Replace the bezel (plastic cover) on the front of the chassis. See Removing or replacing the S3500-H and S3500 Basic front bezel. a. Insert the bottom of the bezel into the chassis. b. Push the bezel upright until the two upper tabs snap into place under the top cover. 8. For a stackable (desktop) configuration, replace any units that need to be stacked on top of this machine. 9. Continue with Restoring power to the system. Replacing the top cover on an S3210R The top cover is removed for most maintenance procedures. To replace the top cover on an S3210R server: 1. Position the top cover so the straight edge is in front. See Removing or replacing the S3210R cover. 2. Set the cover on the chassis so the cover is aligned with the sides and slightly overhangs the back of the server. 3. Slide the cover toward the front of the machine until the cover snaps into place. 4. For a rack-mounted unit, slide the machine back into the cabinet. 5. If you unplugged any cables from the back of the server, plug them in now. See S3210R back view. 6. Replace and tighten the two screws at the back of the server to secure the top cover to the chassis. 7. Close the bezel (plastic cover) on the front of the chassis. See Opening or closing the S3210R front bezel.

133 Page 139 of Continue with Restoring power to the system.

134 Page 140 of 304 Restoring power to the system To restore power to the S3210R and S3500-H servers, follow these steps: 1. Reattach any cables you might have unplugged from the back of the machine. 2. Plug the AC power cord back into the machine's power outlet as follows: For the S3210R, plug in the AC cord and then push the rocker switch to turn on the power. See S3210R back view. For the S3500-H, plug the AC cord into each power supply. See S3500-H back view. 3. Press the power button on the front of the machine. The green power lamp on the front of the machine should be lit. 4. Continue with any verification procedures needed to return the system to service. To restore power to the S3500 Basic server: 1. Connect the female end of the S3500 Basic power cable to the male power connector. 2. Connect the male end of the server power cable to an AC receptacle located on the back of the UPS. See S3500 Basic back view. 3. If you have more than one server, repeat Steps 2 and 3 for each server. For instructions to restore power to S8800 2U server, see Maintaining the Avaya S8800 Server guide(pdf).

135 Page 141 of 304 Replacing peripheral components This topic provides information on the peripheral components that can be replaced on the Message Networking supported servers. S3500-H replaceable peripheral components The following peripheral components can be replaced on the S3500-H server: Keyboard/mouse Monitor External modem (used for the RMB outside of the USA) UPS and optional Extended Battery Module (EBM) For more information, see Connecting the monitor, keyboard, and mouse. For information on ordering replacement components, contact your support representative. S3210-R replaceable peripheral components The following peripheral components can be replaced on the S3210R server: Keyboard/mouse Monitor Modem For more information, see Connecting the monitor, keyboard, and mouse. For information on ordering replacement components, contact your support representative. S3500 Basic replaceable peripheral components The following peripheral components can be replaced on the S3500 Basic server: Keyboard/mouse Monitor Modem For more information, see Connecting the monitor, keyboard, and mouse. For information on ordering replacement components, contact your support representative.

136 Page 142 of 304 Connecting the monitor, keyboard, and mouse This topic describes how to make the connections between the system and the following peripheral devices: Monitor Keyboard and mouse Connecting the monitor A monitor is available for purchase for use with the Message Networking system or the customer can supply a monitor. Most standard monitors will work with the Message Networking system. Two cables connect the monitor to the system: Video cable connector: The video cable connector has a video input connector at one end. The other end of the cable is permanently attached to the monitor. Power cable: The power cable for the monitor connects to an AC outlet on the UPS. To connect the monitor cables: 1. Plug the video cable connector from the monitor directly into the video connector located on the back of the chassis. See S3210R back view or S3500 Basic back view or S3500-H back view, if you need to locate the video connection on the back of the servers. Note: The S3500H is not supported for new installations on MN5.2. Therefore no images of the S3500H are included in the MN5.2 Installation document. However, links have been left in place to view images in the Maintenance Document, these are only accessible from MN5.2 on-line help. Note: To locate a video connector on an S8800 2U server, see Installing the Avaya S8800 Server for Message Networking guide (pdf). 2. Tighten the thumbscrews on the video cable connector with your fingers or with a small flat blade screwdriver. 3. Plug the female end of the power cable into the monitor. 4. Plug the male end of the power cable into an AC outlet on the UPS. Connecting the keyboard and mouse Connect the PS/2 cables for the mouse and keyboard to their corresponding connectors on the back of the server. The mouse connector is color-coded green, and the keyboard connector is color-coded purple. If the customer chooses, the customer can provide a standard PS2 mouse and plug the mouse cable into the mouse receptacle. Continue with Connecting the Message Networking server to the LAN.

137 Page 143 of 304 Replacing system components This topic provides information on the system components that can be replaced in each of the system's supported servers: S8800. To see the replaceable system components for S8800, see Maintaining the S8800 server for Avaya Message Networking guide (pdf). S3500-H S3210R S3500 Basic S3500-H replaceable system components The following S3500-H components can be replaced on site: Analog port board Circuit cards: SCSI RAID controller board Remote maintenance board (RMB) DVD-RAM drive System fans Disk drive cables Memory module SCSI RAID drives Redundant power supply If any other internal components fail, such as the motherboard or the SCSI drive backplane, a server replacement is required. For information on ordering replacement components, contact your support representative. S3210R replaceable system components For the S3210R, the following system components can be replaced: Analog port boards Hard disk drive Power supply DVD-RW drive Front chassis fan Rear chassis fan Memory module If any other internal components fail, a server replacement is required. For information on ordering replacement components, contact your support representative.

138 Page 144 of 304 S3500 Basic replaceable system components For the S3500 Basic, the following system components can be replaced: Analog port board System fans Disk drive cables Memory module Hard disk drive Power supply DVD-ROM If any other internal components fail, a server replacement is required. For information on ordering replacement components, contact your support representative.

139 Page 145 of 304 Replacing an analog port board You must perform the following tasks to replace an analog port board: Remove the old card Configure the new card Install the new card Note: The S3210R and S3500 Basic supports up to three 4-port analog port boards. The S3500-H supports one 4-port analog port board or port boards. The S3500-H and and S8800 2U support one 4-port analog port board or one 12-port analog port board. For more information about the supported analog port boards: port board diagram For S3500 Basic, see D41JCT-LS analog port board diagram For S3500-H, see D41JCT-LS analog port board diagram and D120JCT-LS analog port board diagram. For S8800 2U, see Maintaining the Avaya S8800 Server guide (pdf). Important! If you are replacing a 4-port analog port board with a 12-port board, contact technical support. Technical support must perform a simple procedure to enable the 12-port analog board to operate properly in the server. If you are adding a new card to the system, see Adding a new analog port board.

140 Page 146 of 304 Removing an analog port board Complete the following procedure to remove an analog port board. You might be required to remove an analog port board when replacing a faulty board or migrating to a new server. Warning! Damage from electrostatic discharge is possible. See Protecting against ESD damage for more information. To remove an analog port board: 1. Verify that the replacement card is on site and appears to be in usable condition with no obvious shipping damage. 2. If the system is in service, complete the following steps: a. Stop the voice system. b. Shut down the voice system. 3. Remove the cover. 4. Do the following: If you are removing a card from an S3500-H and an S3500 Basic server, remove the PCI card cage. If you are removing a card from an S8800 2U, remove the PCI card cage. See Maintaining the Avaya S8800 Server for Avaya Message Networking guide (pdf). 5. Remove the circuit card hold-down bracket. If you are removing a card from an S3210R, see Removing or replacing the S3210R circuit card hold-down bracket. If you are removing a card from an S3500-H and an S3500 Basic server, see Removing or replacing the S3500-H and an S3500 Basic circuit card holddown bracket. 6. Locate the card you want to replace. 7. Disconnect the phone lines from the card. 8. If more than one card is installed, disconnect the CT Bus cable from the card you are replacing and from any adjacent cards as necessary to remove the faulty card. Note: Pay close attention to the card connections to make it easier to connect the replacement card. 9. If you are removing a card from an S3210R, locate the fastener that holds the analog port board in place, and then press the arrow at the top of the fastener down and forward to release the fastener. 10. Remove the retaining screw from the slot faceplate and save it. 11. Lift the card from the slot by gently pulling on each corner of the card. See Replacing an S3500-H and an S3500 Basic analog card. Note the slot assignment of the card because you must install the replacement card in the same slot. 12. Save the old card to use as a reference when configuring the new card.

141 Page 147 of 304 Removing the S3500-H and S3500 Basic PCI card cage To remove the PCI card cage in an S3500-H and S3500 Basic: 1. Prepare to open the server: a. Shut down the system. b. Unplug all AC power cords. 2. For a rack-mount setup, remove the server from the cabinet. a. Prepare a clear area as a work surface for the server. b. Unplug all cables from the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails, and set the server on the work surface. For safety considerations, get another person to assist you with lifting the server. 3. Remove the top cover. Push the blue release buttons on the cover and slide the cover toward the back. Caution: Observe proper electrostatic discharge (ESD) precautions when you handle computer components. Wear an antistatic wrist strap that touches your bare skin and connect the strap cable to an earth ground. For complete instructions, see Protecting against ESD damage. 4. Pull straight up on the lifting straps at each end of the PCI card cage. See Removing the PCI card cage in an S3500-H and S3500 Basic. 5. Set the card cage on its side on a firm surface.

142 Page 148 of 304 Removing the PCI card cage in an S3500-H and S3500 Basic

143 Page 149 of 304 Removing or replacing the S3500-H and S3500 Basic circuit card holddown bracket The circuit card hold-down bracket is attached to the PCI card cage and holds the circuit cards in place. The bracket must be removed when replacing the S3500-H and an S3500 Basic circuit cards. Removing the S3500-H and an S3500 Basic circuit card hold-down bracket To remove the circuit card hold-down bracket: 1. Remove the PCI card cage from the server. 2. Loosen the thumb screw on the retaining bracket. 3. Lift the retaining bracket off the PCI card cage. 4. Continue with any internal component replacement procedures. See Removing the RMB in an S3500-H server. Replacing the S3500-H and an S3500 Basic circuit card hold-down bracket To replace the circuit card hold-down bracket: 1. Insert the two tabs of the bracket into the corresponding holes at the back of the PCI card cage. 2. Seat the retaining bracket solidly over the circuit card you are replacing. 3. Push in the thumb screw and turn to tighten the bracket in place. See Replacing the RMB in an S3500-H server.

144 Page 150 of 304 Removing or replacing the S3210R circuit card hold-down bracket This topic provides information on removing or replacing the S3210R circuit card hold-down bracket. The circuit card hold-down bracket must be removed when replacing the S3210R analog boards and might be required to provide sufficient access when replacing other components. Removing the circuit card hold-down bracket To remove the circuit card hold-down bracket: 1. Shut down the system and unplug the AC power cords. 2. Remove the front bezel and top cover. 3. For each occupied slot, loosen the retaining screw and slide it toward the front of the chassis to release the arm. See Removing and replacing the S3210R circuit card hold-down bracket. 4. Unfasten the screw securing the bracket to the chassis. 5. Lift the bracket and set it aside. Replacing the circuit card hold-down bracket To replace the circuit card hold-down bracket: 1. Make sure that all of the securing arms on the bracket are up. 2. Position the bracket on the chassis so that the holes in the bracket line up with the holes on the chassis. 3. Fasten the screws that secure the bracket to the chassis. 4. For each occupied slot, loosen the screw if necessary, slide the screw toward the back of the chassis until the securing arm meets the board, and then tighten the screw. See Removing and replacing the S3210R circuit card hold-down bracket. 5. Replace the top cover and front bezel. 6. Restore power to the system.

145 Page 151 of 304 Removing and replacing the S3210R circuit card hold-down bracket

146 Page 152 of 304 Configuring a Dialogic analog port board An Avaya Message Networking system supports the following Dialogic analog port boards: D/120JCT-LS 12-port analog board, supported only on the S3500-H (1 board per server). Use the D120JCT-LS 12-port analog port board diagram as a guide when configuring a board. D/41JCT-LS 4-port analog board, 3 boards are supported on the S3210R server and S3500 Basic server, 1 board is supported on the S3500-H server. Use the D41JCT-LS 4-port analog port board diagram as a guide when configuring a board. To set the jumpers and switches for a new or replacement analog board, use the appropriate following instructions: Settings for D/120JCT-LS 12-port analog board Settings for D/41JCT-LS 4-port analog board Settings for D/120JCT-LS 12-port analog boards To set the jumpers and switches for a new or replacement D/120JCT-LS 12-port analog board in the S3500-H server: 1. Set the unique board ID for the new board. Turn the SW100 rotary switch, located on the top of the board, to set the board ID according to the slot in which you are installing it. See the following table. Note: If you are replacing an existing board, verify that the ID of the new board matches the ID of the board that you removed by comparing the old board with the new board. Insert Dialogic port boards in the PCI slots starting from the outer edge of the chassis. See S3500-H back view Board number Board ID number PCI slot number Set the hook-switch state of the new board to ON so that callers hear a busy signal when the board is not initialized. Use the SW1 switch, located at the top of the board, to set the hook-switch state. See Setting a Dialogic board on-hook switch. 3. Continue with Installing an analog port board. Settings for D/41JCT-LS 4-port analog boards To set the jumpers and switches for a new or replacement D/41JCT-LS 4-port analog board: 1. Set the unique board ID of the new board. Turn the SW30 rotary switch, located on the top of the board, to set the board ID according to the slot in which you are installing it. See the following table. Note: If you are replacing an existing board, verify that the ID of the new board matches the ID of the board that you removed by comparing the old board with the new board. Board number Board ID number PCI slot number for an S3210R PCI slot number for an S3500-H PCI slot number for an S3500 Basic not supported 2

147 Page 153 of not supported 3 2. Set the hook-switch state of the new board to ON so that callers hear a busy signal when the board is not initialized. Use the red SW4 switch, located near the top of the board, to set the hook-switch state. See Setting a Dialogic board on-hook switch. 3. If more than one 4-port board is installed in the system, set the boards on both ends of the Computer Telephony (CT) bus for bus termination. Use the JP2 jumper to set the CT bus termination as shown in the table below. See Setting D/41JCT-LS board CT bus termination. Number of boards JP2 jumper CT bus termination 1 Off Do not terminate bus. 2 Board 1: ON pins 1 and 2 Board 2: On pins 1 and 2 Terminate bus on both boards. 3 Board 1: ON pins 1 and 2 Board 3: On pins 1 and 2 Terminate bus on boards 1 and 3. Note: Three boards can be installed in the S3210R and the S3500 Basic server. 4. Continue with Installing an analog port board.

148 Page 154 of 304 D120JCT-LS analog port board diagram The 12-port D120JCT-LS analog port board is supported only on the S3500-H server (one board per server). 1 RJ14 connectors 2 SW100 3 SW1 4 CT Bus connector 5 Slot retainer bracket 6 PCI Bus connector

149 Page 155 of 304 D41JCT-LS analog port board diagram The 4-port D41JCT-LS analog port board is supported on the S3210R server (up to three boards per server) or the S3500-H server (one board per server) or S3500 Basic server (three boards per server). 1 J1 2 J2 3 J3 4 J4 5 SW30 6 Rear bracket 7 SW4 8 CT Bus connector 9 Slot retainer bracket 10 JP2

150 Page 156 of 304 Setting a Dialogic board on-hook switch

151 Page 157 of 304 Setting D/41JCT-LS board CT bus termination The setting on the left is ON (pins 1 and 2 are jumpered). The CT bus is terminated. The setting on the right is OFF. The CT bus is not terminated

152 Page 158 of 304 Installing an analog port board Complete the following procedure to install an analog port board in a Message Networking system. Use the D120JCT-LS 12-port analog port board diagram or the D41JCT-LS 4-port analog port board diagram as a guide when installing the new card. Warning! Damage from electrostatic discharge is possible. See Protecting against ESD damage for more information. To install an analog port board: 1. If the system is in service: a. Stop the voice system. b. Shut down the voice system. 2. If necessary, remove the incoming power. 3. For a rack-mount setup, remove the server from the cabinet. a. Prepare a clear area as a work surface for the server. b. Unplug all cables from the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails, and set the server on the work surface. For safety considerations, get another person to assist you with lifting the server. 4. If necessary, remove the cover. 5. If you are installing the card in an S3500-H or S3500 Basic, remove the PCI card cage. If you are installing the card in an S8800, see Maintaining the Avaya S8800 Server for Message Networking guide (pdf). 6. Remove the circuit card hold-down bracket. If you are installing the card in an S3210R, see Removing or replacing the S3210R circuit card hold-down bracket. If you are installing the card in an S3500-H or S3500 Basic, see Removing or replacing the S3500-H S3500 Basic circuit card hold-down bracket. 7. Remove the new card from its packaging and verify that the new card is configured properly. 8. If you are adding a card to the system, remove the slot faceplate retaining screw and then remove the slot faceplate. 9. Position the card in the correct slot: If you are replacing an existing card, install the replacement card in the slot from which you removed the old card. If you are adding a new card to the S3210R, install the card in the next available PCI slot (from right to left). 10. Slide the card's edge connector into the slot and the card slot retainer bracket into the slot guide. Apply pressure to the top of the card only, until the edge connector is firmly seated. Note: It is very important that you properly seat the card in the slot. If the card is not properly seated, the system will not recognize it. 11. Replace and tighten the slot retaining screw to secure the card. 12. If multiple analog port boards are installed, use the Computer Telephony (CT) bus cable to connect the port boards. To attach the bus cable: a. Position the CT bus cable so that the colored strip on the ribbon cable faces toward the ports at the back of the chassis. b. Attach the end connector on the bus cable to the CT bus edge connector at the top of the card in the highest numbered slot.

153 Page 159 of 304 c. Connect the next bus connector to the next port board, and so on. d. When finished, if the cable has extra connections or loose ribbon cable, tuck the cable so that it does not snag when you replace the cover. 13. If you are installing a card in an S3210R, replace the S3210R circuit card hold-down bracket. If you are installing a card in an S3500-H or S3500 Basic, replace the S3500-H or S3500 Basic circuit card holddown bracket. 14. If you are installing a card in an S3210R server, locate the fastener for the analog port board, and then press the fastener down towards the card and snap it in place to secure the analog port board. 15. For an S3500-H or S3500 Basic, replace the PC card cage. For an S8800 2U, see Maintaining the Avaya S8800 Server for Message Networking guide (pdf). 16. Replace the cover. 17. For a rack-mount setup, return the server to the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Push in the release lock, the front latch, to slide the server into the cabinet. b. Plug in all of the cables at the back of the server. 18. Plug the RJ-11 phone cables into the RJ-11 jacks on the card. Check the numbering on the board faceplate to verify that you are connecting the correct cord to the correct port. 19. Restore power to the system.

154 Page 160 of 304 Replacing an S3500-H and S3500 Basic analog port board 1 Remove cover for PCI slot. 2 Align new port board so that it slides into the appropriate guide groove and slot connector on the PCI card cage. 3 Replace and tighten the retaining screw for the port board. 4 Replace the circuit card retaining bracket.

155 Page 161 of 304 Replacing the S3500-H and S3500 Basic PCI card cage To replace the PCI card cage in an S3500-H and S3500 Basic: 1. Align the edge connector on the riser card in the card cage with the correct slot connector on the server board. Use SLOT 6 (PCI 32/33) on the server board. 2. Push straight down on the card cage until the riser card is firmly seated. See Removing the PCI card cage in an S3500-H and S3500 Basic server.

156 Page 162 of 304 Replacing S3500-H circuit cards Circuit cards installed in an S3500-H can be replaced on site. The system must be powered down in order to replace or add a circuit card. The circuit cards that can be replaced in an S3500-H include the following: SCSI RAID controller board Remote maintenance board (RMB) Note: You can also reseat a card to determine if a board is faulty or was simply loose. Replacing the SCSI RAID controller board The S3500-H contains a field-replaceable controller board for the SCSI RAID disk drive array. To replace the SCSI RAID controller board in an S3500-H: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Remove the PCI card cage. 3. Remove the SCSI RAID controller board: a. Unplug the 80-pin controller cable to the SCSI RAID disk drive array. See Replacing the SCSI RAID controller board in an S3500-H. b. Unplug the small SCSI RAID activity indicator cable. See Replacing the SCSI RAID controller board in an S3500-H. c. Unscrew the retaining screw that attaches the bracket on the SCSI RAID controller board to the server board. Set the screw aside. See Replacing the SCSI RAID controller board in an S3500-H. d. Lift the SCSI RAID controller board straight up to remove the board. e. Remove the riser card from the edge connector on the SCSI RAID controller board. See Replacing the SCSI RAID controller board in an S3500-H. 4. Replace the SCSI RAID controller board: a. Remove the new board from the anti-static bag. Do not touch the circuit board surface. b. Place the SCSI RAID controller board on a clean, static-free surface. With the bottom edge of the board well supported, push the riser card onto the edge connector until the riser card is solidly seated. c. Align the edge connector on the riser card with the first slot connector on the server board. Use SLOT 1 (PCI 64/66) on the server board. d. Apply pressure to the top of the riser card. Push straight down until the edge connector is firmly seated. See Replacing the SCSI RAID controller board in an S3500-H. e. Replace and tighten the retaining screw for the SCSI RAID controller board. See Replacing the SCSI RAID controller board in an S3500-H. f. Replace the two cables to the SCSI RAID controller board. 5. Replace the PCI card cage. 6. Replace the top cover. 7. For a rack-mount setup, return the server to the cabinet. a. Guide the server onto the fully extended rails. Caution: The Avaya Modular Messaging servers are heavy. Get another person to assist you with lifting the servers into place. b. Push in the release lock, the front latch, to slide the server into the cabinet.

157 Page 163 of 304 c. Plug in all the cables at the back of the server. Ensure that you also reconnect the short cable from the RMB to the COM2 serial port. 8. Restore power to the server. 9. Verify that the new board is working: a. After the server boots, verify that the application software loads correctly. If the disk accesses data correctly, the SCSI RAID controller board is working. b. Verify that any circuit board alarms are resolved. Replacing the remote maintenance board The S3500-H uses a remote maintenance board (RMB) to report alarms and enable remote technical support. You can replace the RMB on-site. You can also use this procedure to reseat the RMB or reset cable to determine if the RMB is faulty or just had loose connections. To replace a remote maintenance board: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Remove the PCI card cage. After you remove the top cover and before you remove the PCI card cage, unplug the short cable from the RMB that connects the RMB to the COM2 serial port. 3. Before you replace the RMB, verify that the RMB is seated securely in the slot connector. Also verify that the RMB reset cable is securely connected to the RMB. If the RMB connections were loose, reseating them might fix the problem. Continue with Step 10. If the RMB connections were secure, continue with Step Unplug the RMB reset cable. See Replacing the RMB in an S3500-H. 5. Remove the circuit card retaining bracket. 6. Remove the RMB: a. Unscrew the retaining screw that attaches the RMB faceplate to the PCI card cage. Set the screw aside. See Replacing the RMB in an S3500-H. b. Lift the RMB straight out. 7. Insert the new RMB: a. Remove the new RMB from the anti-static bag. Do not touch the circuit board surface. b. Align the RMB so that it slides into the appropriate guide groove and slot connector on the PCI card cage. Place the RMB only in the middle slot, PCI2. See Replacing the RMB in an S3500-H. c. Apply pressure to the top of the RMB only. Push down until the edge connector is firmly seated. d. Replace and tighten the retaining screw for the RMB. See Replacing the RMB in an S3500-H. 8. Replace the circuit card retaining bracket. 9. Rest the PCI card cage on the fans so you have sufficient slack, and then attach the RMB reset cable. Connect the reset cable from the underside of the RMB, so the cable does not interfere with the replacement of the PCI card cage. See Replacing the RMB in an S3500-H. 10. Replace the PCI card cage. 11. Replace the top cover. 12. For a rack-mount setup, return the server to the cabinet. a. Guide the server onto the fully extended rails. Caution: The Avaya Modular Messaging servers are heavy. Get another person to assist you with lifting the servers into place. b. Push in the release lock, the front latch, to slide the server into the cabinet. c. Plug in all the cables at the back of the server. Ensure that you also reconnect the short cable from the RMB to the COM2 serial port. 13. Restore power to the server.

158 Page 164 of Verify that the new RMB is working: a. After the server boots, test RMB functionality. For example, call in to the board and run standard inquiries. b. Verify that any RMB alarms are resolved. Note: For more information about the RMB, see Remote Maintenance Board (RMB) CYN23AP and CYN24AP Reference. This document is available through the Avaya Support Web site (

159 Page 165 of 304 Replacing the SCSI RAID controller board in an S3500-H 1 Unplug 80-pin controller cable to the SCSI RAID disk drive array. 2 Unplug SCSI RAID activity indicator cable. 3 Unscrew the retaining screw. 4 Lift the controller board straight out. 5 Remove the riser card from the edge connector on the SCSI RAID controller board.

160 Page 166 of 304 Replacing the RMB in an S3500-H 1 Unplug RMB reset cable. 2 Remove circuit card retaining bracket. 3 Unscrew the retaining screw. 4 Lift the RMB straight out. 5 Connect the reset cable.

161 Page 168 of 304 Replacing S3500-H and S3500 Basic removable-media drives In the S3500-H a Digital Versatile Disc (DVD) Random Access Memory (RAM) drive provides read/writable backup information for the system. Caution! You must replace a removable-media drive with one of the same type, or the system will not work correctly. For example, you must replace a DVD-RAM drive only with another DVD-RAM drive. Replacing the DVD drive To replace the removable-media drive in a message server: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious shipping damage. 2. Verify that the replacement DVD drive is of the same type as the one you are replacing. 3. Prepare to open the server: a. Shut down the system. b. Unplug all AC power cords. 4. For a rack-mount setup, slide the server forward on the rails. You must remove the server from the cabinet only if you cannot reach underneath the server. 5. Remove the top cover. Push the blue release buttons on the cover and slide the cover toward the back. Caution: Observe proper electrostatic discharge (ESD) precautions when you handle computer components. Wear an antistatic wrist strap that touches your bare skin and connect the strap cable to an earth ground. For complete instructions, see Protecting against ESD damage. 6. Replace the removable-media drive. 7. Verify DVD drive operation. Replace the removable-media drive in S3500-H and S3500 Basic server To replace the DVD drive: 1. Unplug the power cable and IDE signal cable for the DVD drive. See Removing or replacing the S3500-H and S3500 Basic DVD drive. Note: Pull on the tab to remove the 80-pin IDE cable connector. 2. Remove the 4 small screws from the bottom of the DVD drive. 3. Slide the DVD drive forward out of the chassis. 4. Set up the replacement DVD drive to be a master or slave on the IDE bus. Set the jumpers as noted: Locate the mode select connector (the 6-pin connector next to the IDE signal connector). Move the jumper to the 2 end pins labeled "Master." For more information, see DVD jumper settings. 5. Slide the DVD drive into the server so the front of the DVD faceplate is flush with the chassis. 6. Insert the 4 small screws into the bottom of the DVD drive. 7. Connect the power cable and IDE signal cable for the DVD drive. 8. Replace the top cover. 9. For a rack-mount setup, slide the server into the cabinet. 10. Plug in all AC power cords to restore power to the server.

162 Page 169 of 304 Verify DVD drive operation To verify that a new DVD-RAM drive for 3500-H server is working: 1. Insert a writable DVD disk into the new drive. 2. Verify that the system can read from and write to the new drive by doing a backup: a. In the Administration menu, under Backup/Restore, click Backup. b. To verify your results, select Backup/Restore > Backup Attributes. For more information, see Managing the backup media. To verify that a new DVD-ROM drive for S3500 Basic server is working: 1. Insert a DVD disk with some data on it into the new drive. 2. Verify that the system can read from the new drive.

163 Page 170 of 304 Removing or replacing the S3500-H DVD drive 1 Unplug the power cable and IDE signal cable for the DVD drive. 2 Remove the screws from the bottom of the DVD drive. 3 Slide the DVD drive forward out of the chassis.

164 Page 171 of 304 S3500-H DVD-RAM settings This topic shows the DVD-RAM jumper settings for the S3500-H. 1 Cable select mode 2 Slave mode 3 Master mode (used for S3500-H DVD-RAM)

165 Page 172 of 304 Replacing S3500-H and S3500 Basic fans Fans provide cooling for the components in an S3500-H and S3500 Basic server. An S3500-H and S3500 Basic server contains two different sizes of chassis fans: One 60-mm fan in front of the power supply Three 80-mm fans across the middle of the chassis. Use the following procedure to replace either type of fan. However, you must replace the faulty fan with another fan of the same size. Note: The chassis fans in an S3500-H and S3500 Basic server are hot swappable. You can leave the server running when you replace a faulty chassis fan. However, you must work carefully to avoid having material such as hair or clothing drawn into the working fans. Always observe proper ESD precautions when working inside the server. Replacing a chassis fan To replace a chassis fan: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Remove the old fan. 3. Install the new fan. Remove the old fan To remove a faulty chassis fan: 1. For a rack-mount setup, slide the server forward as far as possible. Press the release clips on the rails to fully extend the rail. Note: You might need to unplug some cables at the back of the server to get sufficient cable slack. Label all cables so you can easily reconnect them. 2. Remove the top cover. See Removing the top cover. Caution! Because the server is running, work carefully. Keep material away that might be drawn into the working fans, such as hair or clothing. Observe ESD precautions. 3. Locate the faulty fan. It might be spinning slowly or stopped. 4. Remove the faulty chassis fan: a. Lift the handle of the faulty fan. See Removing or replacing an S3500-H and S3500 Basic chassis fan. b. Lift the fan straight up. 5. Set the old fan aside. Install the new fan To install a new fan in the chassis: 1. Insert the replacement fan: a. Align the flange at the back of the new fan with the guides on the fan bracket. b. Slide the fan into the slot. c. Push to seat the fan.

166 Page 173 of 304 d. Lay the handle down flat. 2. Verify that the new fan is spinning at the correct speed. 3. Replace the top cover. See Replacing the top cover. 4. For a rack-mount setup, slide the server back into the cabinet. If you unplugged any cables from the back of the server, reconnect them now. 5. At the back of the server, replace and tighten the screw to secure the top cover.

167 Page 174 of 304 Removing or replacing an S3500-H and S3500 Basic chassis fan

168 Page 175 of 304 Replacing S3500-H and S3500 Basic disk drive cables You can replace the cables to the hard-disk drives and removable-media drives on the S3500-H server if needed. The S3500-H contains the following disk drive cables that are field replaceable: SCSI RAID controller cables DVD Cable Replacing the SCSI RAID controller cables You can replace the two cables to the SCSI RAID controller board in an S3500-H server. Replace either or both cables as required: 2-pin SCSI drive activity indicator cable for the SCSI RAID disk drive array 80-pin controller cable for the SCSI RAID disk drive array To replace a SCSI RAID controller board cable in an S3500-H server: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Remove the PCI card cage. 3. To replace the SCSI drive activity indicator cable: a. Unplug the activity indicator cable from the SCSI RAID controller board. See Removing the S3500- H SCSI RAID controller cable. b. Unplug the other end of the activity indicator cable from the 2-pin connector on the server board labeled J1 SCSI HDD LED. c. Position the 2-pin connector on the new activity indicator cable so the latch hooks onto the notch in the J1 SCSI HDD LED connector. d. Connect the other end of the new activity cable to the SCSI RAID controller board. 4. To replace the 80-pin controller cable for the SCSI RAID disk drive array: a. Unplug the controller cable from the SCSI RAID controller board. b. Open the dress clip and remove the controller cable. c. Pull on the tab to unplug the controller cable connector from the SCSI RAID array backplane. Set the old cable aside. d. Connect the new controller cable to the 80-pin connector on the SCSI RAID array backplane. e. Connect the other end of the new controller cable to the SCSI RAID controller board. Caution: Support the connector on the SCSI RAID controller board with your fingers when you press down to seat the new controller cable. f. Dress the new controller cable under the dress clip. Press on the clip to snap the clip shut. Note: Fold the new cable carefully so it fits neatly into the chassis, but do not stress the cable. Ensure that you tuck all required cables into the dress clip. 5. Replace the PCI card cage. 6. Replace the top cover. 7. For a rack-mount setup, return the server to the cabinet. a. Guide the server onto the fully extended rails. Caution: The servers are heavy. Get another person to assist you with lifting the servers into place. b. Push in the release lock, the front latch, to slide the server into the cabinet.

169 Page 176 of 304 c. Plug in all the cables at the back of the server. Ensure that you also reconnect the short cable from the RMB to the COM2 serial port. 8. Restore power to the server. 9. Verify that the new cable is working. After the server boots: For a new SCSI drive activity indicator cable: a. Remove the front bezel to view the activity indicator lights for the SCSI disk drives. b. Check the activity indicator lights on each SCSI disk drive tray. If the LEDs show disk activity, the SCSI drive activity indicator cable is working. c. Attach the front bezel. For a new SCSI RAID controller cable, verify that the application software loads correctly. If the server boots correctly, the controller cable for the SCSI RAID array is working. 10. Verify that any relevant alarms are resolved. You can replace the cables to the hard-disk drives and removable-media drives on the S3500 Basic server if needed. Replacing the IDE and DVD drive cable The S3500-H has one IDE drive cable for the DVD-RAM drive, and the S3500 Basic has one IDE drive cable for the DVD-ROM drive. To replace the DVD drive cable in an S3500-H and S3500 Basic server: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Prepare to open the server: a. Shut down the system. b. Unplug all AC power cords. 3. For a rack mount setup, remove the server from the cabinet. a. Prepare a clear area as a work surface for the server. b. Unplug all cables from the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails, and set the server on the work surface. For safety considerations, get another person to assist you with lifting the server. 4. Remove the top cover. Push the blue release buttons on the cover and slide the cover toward the back. Caution: Observe proper electrostatic discharge (ESD) precautions when you handle computer components. Wear an antistatic wrist strap that touches your bare skin and connect the strap cable to an earth ground. For complete instructions, see Protecting against ESD damage. 5. Remove the PCI card cage. 6. Remove the faulty IDE drive cable. See Replacing the S3500-H and S3500 Basic DVD cable. a. Disconnect the DVD drive cable from the secondary IDE connector SEC IDE on the server board. Note: Pull on the tab to remove each 80-pin IDE cable connector. b. Disconnect the cable from the DVD drive. c. Open the dress clips and remove the DVD drive cable. Set the old cable aside. 7. To insert a new IDE drive cable: a. Connect the new drive cable to the secondary IDE connector SED IDE on the server board. To identify the correct connector, see Position of IDE connectors on the S3500-H and S3500 Basic server board. b. Connect the end connector on the new cable to the DVD drive. c. Dress the new drive cable under the dress clips. Press on the clip to snap the clip shut. Note: Fold the new cable carefully so it fits neatly into the chassis, but do not stress the cable. Ensure that you tuck all required cables into each dress clip.

170 Page 177 of Replace the PCI card cage. 9. Replace the top cover. 10. For a rack-mount setup, return the server to the cabinet. a. Guide the server onto the fully extended rails. Caution: The servers are heavy. Get another person to assist you with lifting the servers into place. b. Push in the release lock, the front latch, to slide the server into the cabinet. c. Plug in all the cables at the back of the server. 11. Restore power to the server. 12. Verify that the new drive cable works correctly. a. Insert a CD or DVD into the DVD drive. b. Verify that the server can access the media and displays the information correctly.

171 Page 178 of 304 Removing the S3500-H SCSI RAID controller cable 1 Unplug the activity indicator cable from the SCSI RAID controller board. 2 Unplug the controller cable from the SCSI RAID controller board. 3 Open the dress clip and remove the controller cable. 4 Unplug the controller cable connector from the SCSI RAID array backplane.

172 Page 179 of 304 Replacing the S3500-H and S3500 Basic DVD cable 1 Disconnect the DVD drive cable from the secondary IDE connector 2 Disconnect the cable from the DVD drive 3 Open the dress clips and remove the cable

173 Page 180 of 304 Position of IDE connectors on the S3500-H and S3500 Basic servers 1 Diskette drive connector not used 2 Primary IDE connector PRI IDE 3 Secondary IDE connector SEC IDE 4 Main power connector

174 Page 181 of 304 Replacing S3500-H and S3500 Basic memory modules This topic describes how to reseat or replace the memory module in an S3500-H and S3500 Basic server. An S3500-H and S3500 Basic server has a memory module that consists of two Dual Inline Memory Module (DIMM) cards. Each DIMM contains 1 GB of memory. The DIMM cards that make up the memory module can be replaced on site. The system must be powered down to reseat or replace a memory module. Locating and reseating the memory module Before you replace a memory module, verify that the DIMM card is firmly seated: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious shipping damage. 2. Prepare to access the memory module: a. Shut down the system and unplug the AC power cords. b. Unplug the AC power cords. Warning! The power cord set provided with this product must be used with this product only. Do not use the cord set with any other product, and do not use a different cord set with this product. Using the wrong cord set could lead to hazardous incidents such as electric shock, fire, and faulty operation. 3. For a rack-mount setup, remove the server from the cabinet: Caution: The S3500-H and S3500 Basic server is heavy. Get another person to help you move the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails and set the server on the work surface. 4. Remove the top cover. Caution! Observe proper electrostatic discharge (ESD) precautions when you handle computer components. Wear an antistatic wrist strap that touches your bare skin and connect the strap cable to an earth ground. See Protecting against ESD damage for more information. 5. Locate the memory module (DIMM card) on the server board. See S3500-H and S3500 Basic internal view. 6. Verify that the memory module is properly seated: a. Apply pressure to the memory module to verify that the DIMM card is properly seated. b. Press the holding clips toward the memory module to verify that the clips are secure. Caution! Do not force the memory module into or out of the socket. This action can damage the socket, the memory module, or both. 7. Continue as appropriate: a. If the memory module was properly seated, the module is faulty. Continue with Replacing a memory module. b. If the memory module was not properly installed or seated, continue with this procedure to test the memory module. 8. Restore power to the system.

175 Page 182 of 304 a. Leave the cover off. b. Plug in the cables for the monitor, keyboard and mouse. c. Plug in the AC power cords. 9. Watch the memory test at the beginning of the boot: a. If the memory test completes, note the amount of memory reported. b. Let the server boot completely. 10. Continue as follows: a. If the system shows an amount of memory less than 2 GB or it did not boot, the memory module is faulty. Continue with Replacing a memory module. b. If the system shows 2 GB of memory and booted correctly, the memory module is operating correctly. Continue with this procedure. 11. Shut down the system and unplug the AC power cords. 12. Replace the top cover and return the server to its correct location. 13. Restore power to the system. 14. Place a test call to the system to verify operation after the system finishes booting. If the system is operating properly, you do not need to replace the memory module. Replacing a memory module To replace a memory module in an S3500-H and S3500 Basic server: 1. Press the holding clips on both sides of the socket outward to release the currently installed memory module. See the figure Removing the memory module. 2. Gently pull the memory module out of the socket. Caution! The memory module can be damaged by electrostatic discharge. See Protecting against ESD damage for more information. 3. Hold the new DIMM card by the edges, and remove the card from its antistatic package. 4. Position the replacement module in the correct orientation over the appropriate socket. Use sockets DIMM1A and DIMM2A on the server board. Note: You must replace both DIMM cards to repair the memory module. The server performs best when the DIMM cards are a matched set. 5. Gently push the replacement memory module into the appropriate socket. See the figure Installing the memory module. 6. When the DIMM card is seated firmly, the holding clips spring shut to lock it into position. Verify that the clips are firmly in place. Caution! Do not force the memory module into or out of the socket. This action can damage the socket, the memory module, or both. 7. Repeat Steps 1 through 6 to replace the second DIMM card in the memory module. 8. Replace the top cover. 9. For a rack-mount setup, return the server to the cabinet: Caution! The S3500-H and S3500 Basic server is heavy. Get another person to help you move the server. 10. Push in the release lock, the front latch, to slide the server into the cabinet. 11. Restore power to the system. 12. Watch the memory test at the beginning of the boot: a. If the memory test completes, note the amount of memory that the system reports. b. Let the server boot completely. 13. Continue as follows: If the system shows an amount of memory less than 2 GB or if the server did not boot, the memory

176 Page 183 of 304 module is faulty. Return to Locating and reseating the memory module to verify that the memory module is installed correctly. If the memory module is installed correctly, you must replace the module. If the system shows 2 GB of memory and booted correctly, the memory module is operating correctly. Continue with this procedure. 14. Verify that the server is operating correctly. For example, place a test call to the system.

177 Page 184 of 304 Removing the memory module

178 Page 185 of 304 Installing the memory module

179 Page 186 of 304 Replacing the S3500-H SCSI RAID drive The S3500-H server uses a Redundant Array of Independent Disks (RAID) storage system to protect against customer data loss. In the S3500-H server, four small Computer System Interface (SCSI) drives provide RAID level 5 redundancy, which combines data striping and distributed parity checking. If a SCSI drive fails, the system automatically rebuilds the data after a new SCSI drive is installed. Note: If all the hard disk drives in a system are damaged (for example, due to a lightning strike), you must replace the entire server. For more information, see Replacing the system server. All SCSI drives in an S3500-H server are 'hot swappable.' You can remove and replace a hard disk drive in a SCSI RAID drive assembly while the server continues to provide service. Caution: Never move an operating SCSI drive from one S3500-H server to another. The server does not correctly recognize the previously formatted disk. The system must rebuild the entire RAID array, which takes several hours. Always replace a faulty hard disk drive in a SCSI RAID array with a new, blank SCSI drive. Replacing a SCSI RAID drive To replace a SCSI RAID drive in an S3500-H server: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Remove the faulty drive. 3. Install the new drive and verify operation. Remove the faulty drive To remove a faulty SCSI RAID drive: 1. Remove the front bezel to access the drive trays. Unhook the bezel from the notch near each chassis handle. Set the bezel aside. See Removing or replacing the S3500-H and S3500 Basic front bezel. 2. Locate the SCSI drive to replace. The failed disk drive shows a red LED: Drive 0 (d0b0t0d0): the drive in bay 0. Drive 1 (d0b0t1d0): the drive in bay 2. Drive 2 (d0b0t2d0): the drive in bay 3. Drive 3 (d0b0t3d0): the drive in bay Press the front release latch for the appropriate disk drive bay. 4. Pull on the handle to unseat the faulty SCSI RAID drive and remove the drive tray from the server. See Removing or replacing the S3500-H SCSI RAID drive. Caution! Wait at least 1 minute after you remove the old SCSI drive before installing the new one. This gives the system time to sense the installation of the new drive. 5. Place the drive tray on a clean, static-free surface. Remove the 4 mounting screws, 2 on each side, that secure the hard disk drive to the tray. 6. Lift out the faulty drive. Set the old drive aside. Install the new drive and verify operation To install a new SCSI RAID drive and verify operation: 1. Remove the new disk drive from the anti-static bag. Do not touch the circuit board surface.

180 Page 187 of Place the replacement disk drive into the drive tray. Replace the 4 mounting screws, 2 on each side, to secure the hard disk to the tray. See Removing or replacing the S3500-H SCSI RAID drive. 3. Slide the hard disk drive tray completely into the chassis. Push the front latch for the drive bay closed. The LED for the new drive lights, indicates that the system recognized the new drive. The system automatically starts to reconstruct the data from the other hard disks in the array. 4. Replace the front bezel. See Removing or replacing the S3500-H and S3500 Basic front bezel. 5. Verify that the disk rebuild procedure is underway. See Retrieving hard disk drive information. The entire rebuild procedure can take up to 10 hours.

181 Page 188 of 304 Removing or replacing a SCSI RAID drive

182 Page 189 of 304 Replacing the S3500-H redundant power supply The S3500-H or S8800 2U server has two power supplies, allowing one to take over in case the other fails. Each power supply is considered "hot swappable" and can be replaced while the system is in service. Caution! Never remove the cover on the power supply. If the power supply is faulty, replace the entire component. Note: For instructions to replace the power supply in an S8800 2U server, see Maintaining the Avaya S8800 Server guide (pdf) Replacing an S3500-H power supply To replace a redundant power supply on an S3500-H: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Identify and remove the faulty power supply. 3. Install a new power supply and verify operation. Identify and remove the faulty power supply To identify which of the two power supplies is malfunctioning and remove it: 1. Turn off the power failure alarm buzzer: a. At the front of the server, remove the front bezel. b. Insert a narrow tool into the audible alarm reset switch. Note: The power supply failure indicator on the front of the server remains lit until the power problem is resolved. 2. At the back of the server, locate the power supply that failed: Amber LED the power supply is faulty. Green LED the power supply is working correctly. 3. To remove the faulty power supply: a. Unplug the AC power cord from the faulty power supply. b. Loosen the thumbscrew on the faulty power supply. See Removing or replacing the S3500-H redundant power supply. c. Push the latch away from the thumbscrew to unlock the power supply. d. Lift the handle, and pull out the faulty power supply. Install a new power supply and verify operation To install a new power supply and verify its correct operation: 1. Slide in the replacement power supply. Push firmly to seat the power supply. 2. Flatten the handle against the power supply. 3. Tighten the thumbscrew. 4. Verify that the latch is locked, so you cannot pull out the power supply. 5. Apply power to the new power supply and verify correct operation: a. Plug in the AC power cord.

183 Page 190 of 304 b. Verify that the power supply shows a green LED. c. Verify that the power supply failure indicator on the front of the server is now dark.

184 Page 191 of 304 Removing or replacing the S3500-H redundant power supply 1 Loosen the thumb screw on the faulty power supply. 2 Push the latch away from the thumbscrew to unlock the power supply. 3 Lift the handle. 4 Pull out the faulty power supply.

185 Page 192 of 304 Replacing the S3500 Basic power supply The S3500 Basic server has a single power supply. To replace the S3500 Basic power supply: 1. Identify and remove the faulty power supply. 2. Install a new power supply and verify operation. Identify and remove the faulty power supply To replace the S3500 Basic power supply: 1. Verify that the replacement equipment is on site and appears to be in usable condition, with no obvious damage. 2. Prepare to replace the power supply: a. Shut down the system. b. Unplug all AC power cords. 3. For a rack-mount setup, remove the server from the cabinet. Caution! The S3500 Basic server is heavy. Get another person to help you to remove the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails, and set the server on the work surface. 4. Remove the top cover. Push the blue release buttons on the cover and slide the cover towards the back. For more information, see Removing the top cover. 5. Release the power supply from the chassis. a. Remove the two fans behind the power supply. The fans are the smallest fan and the one next to it. You must remove the fans to access the screws on the internal mounting plate. b. Remove the two screws that attach the power supply to the internal mounting plate. c. Remove the three external screws at the back of the power supply. The three screws connect the power supply to the chassis housing. 6. Disconnect the power supply harness. a. Unplug the 8-pin CPU POWER connector to the server board. b. Unplug the MAIN POWER connector to the server board. c. Unplug the power connector to the DVD drive. d. Unplug the power connector to the hard disk drives. e. Undress all power supply cables from the dress clips. 7. Lift the power supply and attached power harness out of the chassis. Set the faulty power supply aside. Install a new power supply and verify operation To install a new power supply:

186 Page 193 of Position the new power supply and harness inside the chassis. 2. Secure the new power supply to the chassis: a. Insert the three external screws at the back of the power supply to secure the power supply to the chassis housing. b. Insert the two screws that attach the power supply to the internal mounting plate. 3. Replace the chassis fan: a. Align flange on the back of the fan with the guides on the fan bracket. b. Slide the fan into the slot. Push snugly to seat the fan. c. Lay the handle down flat. 4. Connect the power supply harness. a. Plug the 8-pin CPU POWER connector into the server board. b. Plug the MAIN POWER connector into the server board. c. Plug the power connector into the DVD drive. d. Plug the power connector into all hard disk drives. e. Dress all power supply cables under the appropriate dress clips. 5. Replace the top cover. 6. For a rack-mount setup, return the server to the cabinet: Caution! The S3500 Basic server is heavy. Get another person to help you to remove the server. a. Guide the server onto the fully extended rails. b. Push in the release lock, the front latch, to slide the server into the cabinet. c. Plug in all cables at the back of the server. 7. Plug in the AC power cord to restore power to the server. See Restoring power to the system. 8. Check for alarms related to the drives, circuit boards, and other internal components. The power supply failure might have damaged, or been caused by, other components in the server.

187 Page 194 of 304 Replacing the S3210R hard disk drive Use this procedure to replace the S3210R hard disk drive. Note: For instructions to replace the hard disk drive in an S8800 2U server, see Maintaining the Avaya S8800 Server guide (pdf). To replace the S3210R hard disk drive: 1. Shut down the system and unplug the AC power cords. 2. For a rack-mount setup, remove the server from the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails and set the server on the work surface. 3. Remove the top cover. 4. Remove the old hard disk drive: a. Unplug the IDE and power cables from the rear of the hard disk drive. See Removing and replacing the S3210R hard disk drive. b. Loosen the thumbscrew on the top of the hard disk drive tray. c. Slide the hard disk drive tray toward the rear of the cabinet, avoiding the cable connectors, and lift the hard disk drive tray out of the chassis. d. Remove the two screws holding the hard disk drive on each side of the hard disk drive tray. e. Remove the hard disk drive from the hard disk drive tray. f. Set the old hard disk drive aside. 5. Install the new hard disk drive and plug in power cables: a. Slide the hard disk drive into the hard disk drive tray. b. Secure the hard disk drive to the hard disk drive tray with two screws on each side. c. Place the hard disk drive tray into the chassis and slide the hard disk drive tray toward the front of the chassis, avoiding the cable connectors. d. Tighten the thumbscrew on the top of the hard disk drive tray. e. Plug in the IDE and power cables to the rear of the hard disk drive. 6. Replace the top cover. 7. For a rack-mount setup, return the server to the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Push in the release lock, the front latch, to slide the server into the cabinet. b. Plug in all of the cables at the back of the server. 8. Restore power to the system.

188 Page 195 of 304 Removing and replacing the S3210R hard disk drive 1 Unplug the IDE and power cables. 2 Loosen the thumbscrew.

189 Page 196 of Slide the hard disk tray toward the rear of the cabinet and lift the tray out of the chassis. 4 Remove the screws on each side of the hard disk drive tray. 5 Remove the hard disk drive from the hard disk drive tray.

190 Page 197 of 304 Replacing the S3210R power supply Use this procedure to replace the S3210R power supply. Note: For instructions to replace the power supply in an S8800 2U server, see Maintaining the Avaya S8800 Server guide (pdf). To replace the S3210R power supply: 1. Shut down the system and unplug the AC power cords. 2. For a rack-mount setup, remove the server from the cabinet if necessary to access the server components: Caution: For safety purposes, get another person to assist you with moving the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails and set the server on the work surface. 3. Remove the top cover. 4. Remove the old power supply: a. Unplug the power cables from the power supply to the motherboard. See Removing and replacing the S3210R power supply. b. Unplug the power cables from the power supply to the DVD drive. c. Unplug the power cables from the power supply to the hard disk drive. d. Remove the four screws holding the power supply to the rear panel of the chassis. Make sure that you remove the screws holding the power supply to the chassis, not the screws outside of the power supply. e. Lower the power supply to the bottom of the chassis, and then lift the power supply out of the chassis, avoiding the circuit card hold-down bracket. f. Set the old power supply aside. 5. Install the new power supply: a. Place the power supply in the chassis, avoiding the circuit card hold-down bracket. b. Install the screws through the rear chassis panel to the power supply. c. Plug in the wires from the power supply to the motherboard. d. Plug in the wires from the power supply to the DVD drive. e. Plug in the wires from the power supply to the hard disk drive. 6. Replace the top cover. 7. For a rack-mount setup, return the server to the cabinet if you removed it: Caution: For safety purposes, get another person to assist you with moving the server. a. Push in the release lock, the front latch, to slide the server into the cabinet. b. Plug in all of the cables at the back of the server. 8. Restore power to the system.

191 Page 198 of 304 Removing and replacing the S3210R power supply 1 Unplug the power cables from the power supply to the motherboard. 2 Unplug the power cables from the power supply to the motherboard. 3 Unplug the power cables from the power supply to the DVD drive. 4 Unplug the power cables from the power supply to the hard disk drive.

192 Page 199 of Remove the screws holding the power supply to the rear panel of the chassis. 6 Avoid the circuit card hold-down bracket. 7 Lower the power supply. 8 Lift the power supply out of the chassis.

193 Page 200 of 304 Replacing the S3210R DVD/RW drive Use this procedure to replace the S3210R DVD/RW drive. Note: For instructions to replace the DVD drive in an S8800 2U server, see Maintaining the Avaya S8800 Server guide (pdf). To replace the S3210R DVD/RW drive: 1. Shut down the system and unplug the AC power cords. 2. For a rack-mount setup, remove the server from the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails and set the server on the work surface. 3. Remove the top cover. 4. Remove the old DVD/RW drive: a. Unplug the IDE and power cables from the rear of the DVD R/W drive. See Removing and replacing the S3210R DVD/RW drive. b. Remove four screws from the 5.25" media bay support bracket. You may want to use a magnetic screwdriver for this step to avoid dropping the screws into the chassis. c. Slide the 5.25" media bay support bracket toward the rear of the chassis to clear the keyhole tabs and then remove the support bracket. d. Slide the 5.25" media bay toward the rear of the chassis and then remove the media bay. e. Remove the two retaining screws from each side of the 5.25" media bay. f. Remove the old DVD R/W drive from the media bay and set it aside. 5. Install the new DVD/RW: a. Mount the new drive into the middle rack in the 5.25" media bay, flush with the front of the 5.25" media bay. See Removing and replacing the S3210R DVD/RW drive. b. Secure the DVD/RW drive to the 5.25" media bay with two screws on each side. c. Place the 5.25" media bay into the chassis and then slide it toward the front of the chassis. d. Reinstall the 5.25" media bay support bracket, engaging the keyhole tabs. e. Reinstall the four screws to the 5.25" media bay support bracket. You may want to use a magnetic screwdriver for this step to avoid dropping the screws into the chassis. f. Plug in the IDE and power cables to the rear of the DVD R/W drive. 6. Replace the top cover. 7. For a rack-mount setup, return the server to the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Push in the release lock, the front latch, to slide the server into the cabinet. b. Plug in all of the cables at the back of the server. 8. Restore power to the system.

194 Page 202 of 304 Removing and replacing the S3210R DVD/RW drive 1 Unplug the IDE and power cables. 2 Remove the screws from the media bay support bracket.

195 Page 203 of Slide the media bay support bracket toward the rear of the chassis, and remove the support bracket. 4 Slide the media bay toward the rear of the chassis, and remove the media bay. 5 Remove the screws from each side of the media bay. 6 Remove the drive from the media bay.

196 Page 204 of 304 Replacing the S3210R front chassis fan Use this procedure to replace the 12-cm fan located at the front of the S3210R server. To replace the S3210R front chassis fan: 1. Shut down the system and unplug the AC power cords. 2. For a rack-mount setup, remove the server from the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails and set the server on the work surface. 3. Remove the top cover. 4. Remove the old fan: a. Disconnect the fan cable from the motherboard. See Removing and replacing the S3210R front chassis fan. b. Unscrew the two thumbscrews in the front of the chassis that hold the front panel in place. c. Lower the fan assembly. d. Push back the two clips that hold the fan in place. e. Remove the fan from the faceplate. f. Set the old fan aside. 5. Insert the replacement fan: a. Slip the new fan under the clips that hold the fan in place and snap the new fan into the faceplate. See Removing and replacing the S3210R front chassis fan. b. Lift the assembly into place. c. Tighten the thumbscrews in the front of the chassis that hold the front panel in place. d. Connect the fan cable to the motherboard. 6. Replace the top cover. 7. For a rack-mount setup, return the server to the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Push in the release lock, the front latch, to slide the server into the cabinet. b. Plug in all of the cables at the back of the server. 8. Restore power to the system.

197 Page 205 of 304 Removing and replacing the S3210R front chassis fan 1 Disconnect the fan cable from the motherboard. 2 Unscrew the thumbscrews. 3 Lower the fan assembly. 4 Push back the clips that hold the fan in place. 5 Remove the fan from the faceplate.

198 Page 207 of 304 Replacing the S3210R rear chassis fan Use this procedure to replace the 8-cm fan located at the rear of the S3210R server. Note: For instructions to replace the fan located at the rear of the S8800 2U server, see Maintaining the Avaya S8800 Server guide (pdf). To replace the S3210R rear chassis fan: 1. Shut down the system and unplug the AC power cords. 2. For a rack-mount setup, remove the server from the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Prepare a clear area as a work surface for the server. b. Unplug all cables at the back of the server. Label all cables so you can easily reconnect them. c. Press the release clips on the rails to fully extend the rail. d. Lift the server off the rails and set the server on the work surface. 3. Remove the top cover. 4. Remove the old fan: a. Remove the circuit-card holddown bracket if required for sufficient access to the fan. See Removing or replacing the S3210R circuit card hold-down bracket. b. Locate the rear fan. See S3210R internal view. c. Disconnect the fan cable from the motherboard. See Removing and replacing the S3210R rear chassis fan. d. Push back the two clips that hold the fan in place. e. Rotate the fan down and release it from the chassis. f. Set the old fan aside. 5. Insert the replacement fan: a. Slide the replacement fan into the chassis and snap it into place. See Removing and replacing the S3210R rear chassis fan. b. Connect the fan cable to the motherboard. 6. Replace the circuit-card holddown bracket if required for sufficient access to the fan. See Removing or replacing the S3210R circuit card hold-down bracket. 7. Replace the top cover. 8. For a rack-mount setup, return the server to the cabinet: Caution: For safety purposes, get another person to assist you with moving the server. a. Push in the release lock, the front latch, to slide the server into the cabinet. b. Plug in all of the cables at the back of the server. 9. Restore power to the system.

199 Page 208 of 304 Removing and replacing the S3210R rear chassis fan 1 Disconnect the fan cable from the motherboard. 2 Push back the clips. 3 Rotate the fan down and release it from the chassis.