HP 3000 Manuals

Starting the Monitoring Operations [ Managing HP X.400 Administrator's Guide ] MPE/iX 5.0 Documentation


Managing HP X.400 Administrator's Guide

Starting the Monitoring Operations 

To start the operations, 

   *   Select STATUS on the X.400 Main Menu 
       .

[]
Figure 3-1. X.400 Main Menu This displays the Monitor X.400 Status Menu .
[]
Figure 3-2. Monitor X.400 Status Menu The menu displays the available operations. Select the utility you wish to execute. Displaying Process Status The PROCESS operation reports current status information for OTS and all X.400 components. The status of the components can be either running or not running. The status report lists those components which are running and those components that should be but are not running. To use this operation, * Select PROCESS from the Monitor X.400 Status Menu. This displays the following : ======= OTS STATUS======== OTS: running /dev/lan: running X.25 Level 3: DOWN ===== PROCESS STATUS ====== Process Status --------- ----------- x4mailer: running (no shutdown requested) mta: running (no shutdown requested) rts: not running! (shutdown requested) The current status of OTS is listed under the OTS STATUS heading as OTS running or DOWN (not running), and whether OTS is running or DOWN over LAN and/or X.25. The components are listed under the Process heading, and the current status of each component is listed under the STATUS heading. The status of the X.400 components are: * running- a component is started and is initializing or running normally. * not running!-a component is shut down or is not running for some other reason. A status of running and (no shut down requested) indicates the process is currently running. A status of running and (shut down requested) indicates the process is currently running but will be shut down soon. A status of not running! and (no shutdown requested) indicates the process aborted . A status of not running! and (shutdown requested) indicates the process was shut down by user request. To return to the Monitor X.400 Status Menu , * Press any key. See the x4stat command in Appendix B to run this operation from the HP-UX prompt. Displaying Queue Status The QUEUE operation displays each X.400 queue and the number of messages in the queue. To use this operation, * Select QUEUE from the Monitor X.400 Status Menu. The following, an example, displays: ====== QUEUE STATUS ====== Queue MTA/Node Name Number of Messages --------- ----------------- ---------------------- iq 0 uq 0 tq 2 oq/oq001 CLIPPER 2 oq/oq002 HPSALES 0 oq/oq003 HPINDML 0 The queue names, the name of the associated MTA, and the number of messages in each queue are listed. To return to the Monitor X.400 Status Menu, * Press any key. See the x4stat command in Appendix B to run this operation from the HP-UX prompt. Displaying Software Version The VERSION operation displays the version information for each of the X.400 components, X.400 commands, and configuration files. To use this operation, Select VERSION from the Monitor X.400 Status Menu. The version information is in the version stamp format V.UU.FF, where V Version (one-character alphabetic) of the software. This corresponds to a major revision or a version for a new or revised system environment. U Update level (two-character numeric) of the software. This corresponds to a significant revision in product functionality or when the incremented values for product fixes exceed the field. F Fix level (two-character numeric) of the software. This corresponds to a new supported revision of the software. The VERSION operation does not check to see if the versions match. Use the PERM operation if you want to check the versions. To return to the Monitor X.400 Status Menu , * Press any key. See the x4version command in Appendix B to run this operation from the HP-UX prompt and for sample output. Displaying Event Log The EVENTS operation displays the event logs from all the components, or a specific component log. To use this operation, * Select EVENTS from the Monitor X.400 Status Menu. This displays the Display Events window.
[]
Figure 3-3. Display Events Window The fields on this window are: Display most recent events only? (y or n) Default: y. Enter y to display the most recent events (i.e. the last events) in the log. Enter n to display the beginning of the log. Number of lines to display per log file? Default: 30 lines. Enter the number of lines (maximum = 999) you want displayed from the event log. If you enter n (do not display most recent events) in the previous field, and enter 30, the first 30 lines of the event log are shown. If you enter 0 (zero), the entire event log is shown. Which event logs are to be displayed? MTA? (y or n) Enter y to display the MTA event log, n to not display it. RTS? (y or n) Enter y to display the RTS event log, n to not display it. X4MAILER? (y or n) Only if the Sendmail connection is configured, enter y to display the x4mailer event log, n to not display it. ENCODER? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display the encoder event log, n to not display it. DECODER? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display the Decoder event log, n to not display it. X4XFER? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display x4xfer event log, n to not display it. To execute the operation, * Press the Perform Task key. If there is more than one page, -- More -- displays. Press the space bar for the next new page, or q to terminate the output. Refer to the x4logcat command in Appendix B for a sample display output. To cancel the operation, * Press the Exit Task key. See the x4logcat command in Appendix B to run this operation from the HP-UX prompt. Formatting and Displaying Errors The FMTERRS operation formats and displays error log messages from all X.400 components, a specific process, or specific components. You may also display a specific error class for the messages. To use this operation, * Select FMTERRS from the Monitor X.400 Status Menu. This displays the Format and Display Errors screen.
[]
Figure 3-4. Format and Display Errors Screen The fields on this screen are: Display most recent error information only? (y or n) Default: y. Enter y to display the most recent (last) errors in the log file. Enter n to display the first (beginning) errors in the log file. Number of lines to display per component? (0=unlimited) Default: 30 lines. Enter the number of lines (maximum = 999) you want displayed from the error log file. If you enter n (do not display most recent events) in the previous field, and enter 30, the first 30 lines of the event log are shown. If you enter 0 (zero), the entire error log file is shown. Specify EITHER a process id, or the components for which error log messages are to be displayed . Process ID? Enter the process ID whose errors you wish to display. X4XFER? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display x4xfer errors, n to not display them. ENCODER? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display encoder errors, n to not display them. DECODER? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display decoder errors, n to not display them. X4ADMIN? (y or n) Enter y to display x4admin errors, n to not display them. MTA? (y or n) Enter y to display MTA errors, n to not display them. RTS? (y or n) Enter y to display RTS error log, n to not display them. REMSH9K? (y or n) Only if an HP X.400/HP Desk Node is configured, enter y to display REMSH9K (remote shell program) errors, n to not display them. Select the error class you wish to display. You may choose only one. Which error classes do Enter a to display all critical and you wish to display? non-critical errors in the error log. Enter c (c=critical, n=non to display the critical errors in the log. critical, a=critical and Enter n to display the non-critical or non critical, informative errors in the log. Enter p to p=procedure trace) display the procedure trace in the log. ______________________________________________ NOTE Non-critical and procedure trace messages are written to the log when these log classes are enabled (see x4setclass in Appendix B). ______________________________________________ To execute the operation, * Press the Perform Task key. If there is more than one page, -- More -- displays. Press the space bar for the next new page, or q to terminate the output. When you press the Perform Task key, the errors you requested display. The following is an example : * ***************************** * mta ***************************** * No error messages found for mta * ***************************** * x4admin ***************************** * [26636] 07/24-18:00:59 - x4admin Critical Error [26636] [26636] Failed to write neighbor table configuration to file /usr/lib/x400/neigh.conf. (X4ERR 4210) [26636] Source code file (Blocmta.c), Line 642 [26636] [26636] Failed to open the neighbor table configuration file /usr/lib/x400/neigh.conf.new, errno 2. (X4ERR 4232) [26636] Source code file (Bneighio.c), Line 227 [26636] [26636] To cancel the operation, * Press the Exit Task key. See the x4logview command in Appendix B to run this operation from the HP-UX prompt. Displaying Free Disk Space The DISKFREE operation displays the free space on all mounted file systems. The amount of free space is shown in kilobytes. To use this operation, * Select DISKFREE from the Monitor X.400 Status Menu. The following is an example of the output: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0d0s0 22623 19553 807 96% / /dev/dsk/c0c0s10 121771 104747 4846 96% /user /dev/dsk/c0d0s5 50239 40267 4948 89% /extra /dev/dsk/c0d0s4 101153 69476 22561 75% /usr /dev/dsk/c0d0s3 27424 4224 20456 17% /tmp The file system name, file system size in kilobytes, kilobytes used by the file system, kilobytes available on the file system, amount of kilobytes used by percent, and the directory on which the file system is mounted are displayed . To return to the Monitor X.400 Status Menu , * Press any key. Use the HP-UX bdf command to run this operation from the HP-UX prompt. Refer to Section 1m: System Administration Commands in the HP-UX Reference Vol. 1: Sections 1, 1M, and 9 manual for further information. Displaying Logging Status The ENFLAGS operation displays the current logging status for X.400. To use this operation, * Select ENFLAGS on the Monitor X.400 Status Menu. When you request the status of the X.400 enable flags, the following displays: Event logging is enabled for : mta rts MTA archiving is disabled Critical error logging is enabled for : x4admin mta rts Non-critical error logging is enabled for : rts Procedure Tracing is enabled for : none This display shows the status of the following enable flags: * event logging for the X.400 components * MTA archiving * critical error logging * non-critical error logging * procedure tracing See the x4stat command in Appendix B to run this operation from the HP-UX prompt. Executing X.400 Monitoring Utility The MONITOR operation gives an early indication of problems with the day-to-day running of an X.400 MTA and RTS and what you can do to resolve the problems. To use this operation, * Select MONITOR from the Monitor X.400 Status Menu. This displays the Execute X.400 Monitoring Utility screen.
[]
Figure 3-5. Monitor X.400 Screen The fields on this window are: Maximum number of Default: 100. Enter the maximum number of messages in all messages that can be in all input and output Input/Output queues: queues waiting to be processed by the RTS or MTA before generating a warning. Maximum percentage usage Default: 85. Enter the maximum percentage of that can be made of the the disk that can be used by X.400 messages disk: before generating a warning message. Maximum time to continue Default: 120. Enter, in minutes, the amount warning of error of time a warning is generated by an entry in message: the error log. Maximum size a log file Default: 4096. Enter, in kilobytes, can grow: the maximum size any log file in the /usr/spool/x400/log directory can grow to before generating a warning message. Maximum number of Default: 25. Enter the maximum number of messages in MTA input messages that can be in the MTA's input queue queue: before generating a warning message. Maximum number of Default: 25. Enter the maximum number of messages in an MTA messages that can be in one of the MTA's output outgoing queue: queues before generating a warning message. Maximum time in between Default: 10. When monitoring continuously, checks: enter, in seconds, the amount of time between checking for warning conditions. Execute in single shot Default: n. Enter y if you do not want to mode: monitor continuously or to only display the first warning message generated. Maximum time to read Default: 10. Enter, in seconds, the amount of warning and action time to read a warning message before messages: displaying the next warning message. Maximum time a message Default: 60. Enter, in minutes, the amount of is in input queue before time a message waits in an input or output warning: queue before generating a warning message. To execute the operation, * Press the Perform Task key. To cancel the operation, * Press the Exit Task key. See the x4monitor command in Appendix B to run this operation from the HP-UX prompt. Checking X.400 File Permissions The PERM operation checks the attributes of X.400 files for expected values. For the X.400 files installed from the product tape, PERM checks permission (mode), ownership, group, hard links, checksum, size, and version. For configuration files, event logs, and directories/queues, PERM checks permission (mode), ownership, and group. To use this operation, * Select PERM from the Monitor X.400 Status Menu. Output is written to the screen and to a file. The name of the file is present in the screen output. The output has the following form: filename: keyword (expected value -> present value) where keyword is mode, owner, group, links, checksum, size, or version. If a problem with permission or ownership exists, the PERM utility asks if the problem should be fixed. Answer y to correct the problem. If a problem with hard links, checksum, size, or version exists, you must reinstall the X400-RUN fileset from the product tape to fix the problem. To execute the operation, * Press the Perform Task key. To cancel the operation, * Press the Exit Task key. See the x4perm command in Appendix B to run this operation from the HP-UX prompt.
NOTE If you have installed an X.400 patch, x4perm reports a difference in version, checksum, and size of the patched files. You can ignore the version, checksum, and size problems for the patched files.


MPE/iX 5.0 Documentation