Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Reference > Print Guides > Maintenance print guide Maintenance print guide This print guides is a collection of Message Networking Help system topics provided in an easy-to-print format for your convenience. Please note that 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 8 Viewing system configuration and status 19 Reviewing Message Networking logs 27 Performing hardware maintenance 97 Backing up the system 211 Generating reports 219 Running database audits 253 Displaying the message queue 256 Performing voice equipment diagnostics 257 Changing the system's network address length 262 Changing a remote machine's mailbox number 263 Changing the Message Networking network addressing 263 Restoring backed-up system files 264 Troubleshooting the system 266 ©2006 Avaya Inc. All rights reserved. Last modified 7 April, 2006 1 Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance 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 Top of page Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Accessing the product ID 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. Start at the Administration menu, and select Basic System Administration > Alarming Administration. The system displays the Alarm Management page. 2. Record the product ID for use with the remote maintenance center. 3. Click Return to Main to return to the Administration menu. Top of page 2 Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Checking and setting the system clock 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. Check it again monthly and whenever a daylight savings time change occurs. When you set the system time for the Message Networking system using the following procedure, you set both the Linux system clock and the onboard (hardware) real-time clock. On Message Networking systems using analog, you should synchronize the Message Networking system to the switch or synchronize the Message Networking system and switch to a real-time source. To check the Linux date and time: 1. Start at the Administration menu, and select Basic System Administration > Date and Time Administration. The system displays the Linux Date and Time page. 2. Check the date and time information: " If there are no inaccuracies, click Return to Main to return to the Administration menu. " If there are inaccuracies, make the appropriate modifications to the page. For information about the fields on this page, click Help. 3. Click Save to save the date and time changes. The page displays the confirmation of the date and time changes. The system also logs a message to the Administrator's Log informing you of any changes made to the Linux date and time. 4. Click Relogin to log back into this system. The login page displays. 5. Log into the system. Top of page 3 Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Starting the messaging software (voice system) Starting the messaging software (voice system) To start the messaging software: 1. Start at the Administration menu, and select Utilities > Start Messaging Software. The system 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 3. Click Return to Main to return to the Administration menu. Top of page Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Stopping the messaging software (voice system) Stopping the messaging software (voice system) Caution: Stop the voice system only when it is absolutely necessary. To stop the messaging software: 1. Start at the Administration menu, and select Utilities > Stop Messaging Software. 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 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. 4. Click Return to Main to return to the Administration menu. Top of page 4 Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Shutting down the system Shutting down the system To shut down the system: 1. Start at the Administration menu, and select Utilities > Shutdown System. The system displays the Shutdown System page. 2. Enter a number between 0 and 600 in the Wait Time field. This 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 Shutdown. The following message displays: "This will bring down your system and you will lose access to this system. 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. Top of page 5 Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Checking the reboot schedule Checking the reboot schedule 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. 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. Start at the Administration menu, and select Utilities > Display Reboot Information. The system displays the Reboot Information 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. Top of page Home | Search Message Networking Help Print | Back | Fwd | Close Getting Started Admin Maintenance Reference Home > Maintenance > Performing basic maintenance > Performing a system reboot 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. Start at the Administration menu, and select Utilities > Reboot System. The system displays the Reboot System page. 2. In the Wait Time 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. 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. 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.