Monitoring and Managing Microsoft Exchange 2000 Server (HP Technologies)

monitoring and managing microsoft exchange 2000 server
Chapter 10 - Monitoring Exchange
Monitoring and Managing Microsoft Exchange 2000 Server
by Mike Daugherty
Digital Press ?2001

 

10.6 Performance monitor

You can do some basic monitoring of processes and queues using each Exchange servers Monitoring tab. However, many other key resources should be regularly monitored . Windows 2000 includes a Performance Monitor that can be used to monitor these other Windows 2000 and Exchange 2000 resources, such as the number of Internet messages received per minute, the percentage of processor utilization, etc. Performance Monitor can create charts , set alerts, and format reports that help the Exchange administrator measure system performance. Data gathered from counters can be displayed in real-time or stored in log files for later analysis.

The usefulness of any monitoring effort depends on creating a baseline measurement when the system is operating effectively and knowing the limitsboth high- and low-end valuesfor each parameter that indicate a problem. The values in Windows 2000 Performance Monitor counters can be examined to determine how Exchange is performing or to track error conditions.

Performance Monitor tracks the value of object counters, where objects include the systems processors, memory, disks, and processes such as the Exchange 2000 processes. Each of these object types has a set of counters from which the Performance Monitor can collect data. For example, a LogicalDisk object has counters for % Disk Time, Free Megabytes, and % Free Space.

Some object types have several instances. For example, the systems Processor object type will have multiple instances if a system has multiple processors. The PhysicalDisk object will have one instance for each disk drive. The counters for each instance of an object can be monitored independently.

Most typical monitoring can be done using the Windows 2000 Performance Monitor. Using Performance Monitor, the Exchange administrator can track the functioning of critical objects on an Exchange 2000 server. By carefully watching the monitored objects, the administrator can often detect a minor problem before it progresses into one that will affect users due to server downtime.

The administrator can create Microsoft Management Console files (.MSC) that define specific objects to be monitored. Once created, the MSC file contains all the settings, including screen position, chart colors, etc. required to monitor the object. If alerts have been configured, the alert will be sent and the event details will be written to the Windows 2000 Event Viewer log when the thresholds are exceeded.

10.6.1 Creating a real-time performance monitor chart

The Performance Monitors chart view provides a continual, real-time overview of the system performance. The following procedures can be used to create a performance monitor chart:

  1. Start the Performance Monitor from the Windows 2000 Start menu by selecting Programs   Administrative Tools   Performance (Figure 10.12).

    Figure 10.12: The Performance Monitor window

  2. Select the View Chart button.

  3. Select the Add button to display the Add Counters dialog box (Figure 10.13).

    Figure 10.13: The Add Counters dialog box

  4. Select the Exchange server to be monitored. You can monitor the local system by selecting Use local computer counters. To monitor another server in your network, select Select counters from computer and select the system from the associated drop-down list.

  5. Use the Performance object drop-down list to select an object to monitor. Recommended objects to monitor are listed later in this chapter.

  6. Select the counters and instances to be monitored. The set of available counters varies depending upon the object. Use the Instance list to select which instance of an object is to be monitored. For example, the Processor object type will have multiple instances if a system has multiple processors. You can select All counters to monitor all counters for an object and/or select All instances to monitor all instances. You can select the Explain button to display an explanation of the counter. When you have selected the counters and instances, select Add.

  7. Repeat the previous steps to add additional counters to the chart. Select Close when all desired counters have been added to the chart.

  8. To save these settings for subsequent use, select Save As from the Console menu. Provide a file name in the Save As dialog box. The Microsoft Management Console settings file (.MSC file) will save all Performance Monitor settings.

10.6.2 Recording performance data for later analysis

The Performance Monitor can be used to collect and record data over a period. These logs can later be analyzed to identify long- term trends or to troubleshoot problems. The following procedure can be used to create a Performance Monitor log file.

  1. Start the Performance Monitor from the Windows 2000 Start menu by selecting Programs   Administrative Tools   Performance.

  2. Expand the Performance Logs and Alerts item in the MMC tree pane (i.e., the left pane in the window), and then select the Counter Logs item (Figure 10.14).

    Figure 10.14: The Counter Logs window

  3. Right-click in the details pane (i.e., the right pane) and select New Log Settings.

  4. Enter a name into the New Log Settings dialog box and select OK to display the log settings dialog box. The title of this dialog box will match the file name you entered into the New Log Settings dialog box (Figure 10.15).

    Figure 10.15: The Log Settings dialog box

  5. Select Add to display the Select Counters dialog box (Figure 10.16).

    Figure 10.16: The Select Counters dialog box

  6. Select the Exchange server to be monitored. You can monitor the local system by selecting Use local computer counters. To monitor another server in your network, select Select counters from computer and select the system from the associated drop-down list.

  7. Use the Performance object drop-down list to select an object to monitor. Recommended objects to monitor are listed later in this chapter.

  8. Select the counters and instances to be monitored. The set of available counters varies depending upon the object. Use the Instance list to select which instance of an object is to be monitored. For example, the Processor object type will have multiple instances if a system has multiple processors. You can select All counters to monitor all counters for an object and/or select All instances to monitor all instances. You can select the Explain button to display an explanation of the counter. When you have selected the counters and instances, select Add.

  9. Repeat the previous steps to add additional counters. Select Close when all desired counters have been added.

  10. On the General tab, set the Interval value to the desired interval for collecting sample data.

  11. Select the Log Files tab (Figure 10.17).

    Figure 10.17: The Log Files tab

  12. Use the Location field to identify the directory where the log file will be stored.

  13. Enter the log file name into the File name field.

  14. You can use the End file names with field and Start numbering at field to append sequence numbers to the end of the log file names.

  15. Select the Schedule tab (Figure 10.18).

    Figure 10.18: The Schedule tab

  16. Use the Start log fields to enter the time when logging operations should begin.

  17. Use the Stop log fields to enter the time when logging operations should stop. Logging can be stopped automatically after a specified duration (e.g., 1 day), stopped at a specific time, or stopped manually using the shortcut menu.

  18. When you have entered all information, select OK to create the logging entry.

  19. To save these settings for subsequent use, select Save As from the Console menu. Provide a file name in the Save As dialog box. The Microsoft Management Console settings file (.MSC file) will save all Performance Monitor settings.

10.6.3 Setting alerts using Performance Monitor

The Performance Monitors alert view provides for setting thresholds on counters. When a counters threshold is exceeded, the date and time of the event are recorded in the Alert window.

The following procedures can be used to specify alerts using Performance Monitor:

  1. Start the Performance Monitor from the Windows 2000 Start menu by selecting Programs   Administrative Tools   Performance.

  2. Expand the Performance Logs and Alerts item in the MMC tree pane (i.e., the left pane in the window), and then select the Alerts item (Figure 10.19).

    Figure 10.19: The Alerts window

  3. Right-click in the details pane (i.e., the right pane) and select New Alert Settings.

  4. Enter a name into the New Alert Settings dialog box and select OK to display the log settings dialog box. The title of this dialog box will match the file name you entered into the New Alert Settings dialog box.

  5. On the General tab, select Add to display the Select Counters dialog box (Figure 10.20).

    Figure 10.20: The Select Counters dialog box

  6. Select the Exchange server to be monitored. You can monitor the local system by selecting Use local computer counters. To monitor another server in your network, select Select counters from computer and select the system from the associated drop-down list.

  7. Use the Performance object drop-down list to select an object to monitor. Recommended objects to monitor are listed later in this chapter.

  8. Select the counters and instances to be monitored. The set of available counters varies depending upon the object. Use the Instance list to select which instance of an object is to be monitored. For example, the Processor object type will have multiple instances if a system has multiple processors. You can select All counters to monitor all counters for an object and/or select All instances to monitor all instances. You can select the Explain button to display an explanation of the counter. When you have selected the counters and instances, select Add.

  9. Repeat the previous steps to add additional counters. Select Close when all desired counters have been added. The alert settings dialog box will be redisplayed.

  10. Use the Alert when the value is drop-down list to select the condition to test (either Under or Over) and enter the threshold value for issuing the alert into the Limit field (Figure 10.21).

    Figure 10.21: The General tab

  11. Use the Interval field and the Units drop-down list to specify the desired interval for sampling data.

  12. Select the Action tab to select the actions to be executed when the threshold value for the alert is reached. You may select as many of the actions as needed.

  13. Select the Log an entry in the application event log check box if you want to log an entry when the threshold value is reached (Figure 10.22). You can view entries in the applications event log using the Windows 2000 Event Viewer .

    Figure 10.22: The Action tab

  14. Select the Send a network message to check box if you want to send a network alert to a specified workstation. Enter the workstation name into the associated field. The alert message will only be delivered if the workstation is turned on, if a user is logged onto the workstation, and the messaging service is running on the workstation. This type of notification should normally be used only in environments where the network is very reliable such as a dedicated monitoring workstation on the same local area network as the monitor.

  15. You can use the Start performance data log check box to start a predefined performance data log.

  16. You can select Run this program to run your own specialized alert program. A special notification application can be used to alert administrators who are not logged on to the network. For example, a notification application can be used to start a pager program to page an Exchange administrator who is not always logged onto the system. Use the Command Line Arguments button to specify the arguments that are to be passed to the special notification application.

  17. Select the Schedule tab (Figure 10.23).

    Figure 10.23: The Schedule tab

  18. Use Start scan to enter the time when monitoring operations should begin.

  19. Use Stop scan to enter the time when monitoring operations should stop. Monitoring can be stopped automatically after a specified duration (e.g., 1 day), stopped at a specific time, or stopped manually using the shortcut menu.

  20. When all information has been specified, select OK to create the alert entry.

  21. To save these settings for subsequent use, select Save As from the Console menu. Provide a file name in the Save As dialog box. The Microsoft Management Console settings file (.MSC file) will save all Performance Monitor settings.

10.6.4 Recommended objects to monitor

Windows 2000 and Exchange provide many objects that can be monitored. Monitoring all of the possible objects is unnecessary and, in fact, may adversely affect network and server performance. The objects to monitor most closely are those processes that handle message flow through the system. These are the Message Transfer Agent and the message queues for the connectors. Monitors for other secondary objects can be configured to help diagnose suspected problems.

Several types of counters should be monitored:

The administrator should create shortcuts for the Microsoft Management Console settings file (.MSC file) on the system that will be used to monitor the Exchange objects. The complete list of Performance Monitor counters is extensive . The following sections contain only those counters relevant to Exchange, and include some recommended Microsoft Management Console settings files.

Monitoring key resources

The Performance Monitor counters in this section are recommended as the foundation set of counters for all Exchange servers. These counters monitor the Windows 2000 and hardware resources essential to proper functioning of Exchange 2000. Additional counters should be added in accordance with the function of the Exchange server. These counters should be combined into a single performance monitor graph with an update interval of about 2 minutes:

Memory

Paging File

PhysicalDisk

Process

The % Processor Time is the percentage of elapsed processor time that all of the process threads used. On systems with multiple processors, the maximum counter value is 100% times the number of processors. The processor time for these services should never be at 0% or at the maximum value (i.e., 100% times the number of processors) all of the time. If a process is always at 0%, check Programs   Administrative Tools   Services to verify that the process is running. If a process is always at the maximum value, check the Event Viewer to identify the problem.

Processor

Redirector

Monitoring message processing

The exact list of objects and counters will vary depending upon the Exchange components being used on the system. For example, if the cc:Mail Connector software is not being used, then the counters for this component will not be available.

The counters listed in this section are those that show whether e-mail messages are flowing through the system as expected. These counters should be combined into a single performance monitor graph with an update interval of about 2 minutes:

MSExchangeCCMC

MSExchangeIS

MSExchangeIS Mailbox

MSExchangeIS Public

MSExchangeMTA

MSExchangeNMC

MSExchangeSRS

SMTP Server

Monitoring message system usage

The counters listed in this section are those that provide an indicator as to how heavily the e-mail system is being used. Unlike the first two groups of counters, these do not need to be as closely watched. Instead, the administrator should periodically collect data for these counters and compare the collected data to the system baseline created when the e-mail system was first configured. The need to add additional hardware resources can often be justified by the e-mail usage increases shown with these counters:

MSExchangeCCMC

MSExchangeIS

MSExchangeIS Mailbox

MSExchangeIS Public

MSExchangeMSMI

MSExchangeMTA

MSExchangeNMC

MSExchangePCMTA

SMTP Server

Counters for troubleshooting

The primary role of the remaining performance monitor counters is to aid with troubleshooting. There are many Exchange- related objects, including:

MSExchange Oledb Events

MSExchangeIS Mailbox

MSExchange Oledb Resource

MSExchangeIS Public

MSExchange Web Mail

MSExchangeIS Transport Driver

MSExchangeAL

MSExchangeMSMI

MSExchangeCCMC

MSExchangeMTA

MSExchangeCONF

MSExchangeMTA Connections

MSExchangeDcsMgr

MSExchangeNMC

MSExchangeDSAccess Caches

MSExchangePCMTA

MSExchangeDSAccess Contexts

MSExchangePOP3

MSExchangeDSAccess Processes

MSExchangeSA NSPI Proxy

MSExchangeES

MSExchangeSRS

MSExchangeGWC

MSExchangeT120

MSExchangeIMAP4

MSExchangeTransport Store Driver

MSExchangeIpconf

SMTP NTFS Store Driver

MSExchangeIS

SMTP Server

Hundreds of counters for these objects can be monitored as needed to diagnose problems. The following is a small sample of the additional objects that may be useful for troubleshooting:

MSExchangeCCMC

MSExchangeIS Mailbox

MSExchangeIS Public

MSExchangeMSMI

MSExchangePCMTA

SMTP Server

10.6.5 Starting performance monitors automatically

The Windows 2000 performance monitor MMC files can also be added to the Startup folder using the following procedure:

  1. Open the Taskbar and Start Menu Properties window from the Windows 2000 Start menu by selecting Settings   Taskbar & Start Menu.

  2. Select the Advanced tab.

  3. Select Add.

  4. Enter the path and file name for the performance monitor MMC file using the following format:

    mmc filename

    where filename is the path and file name of a performance monitor MMC file.

  5. Select Next to display the Select Program Folder window.

  6. Select the Startup folder, and then select Next.

  7. Enter a name to appear on the Startup menu, and then select Finish.

  8. In the Taskbar and Start Menu Properties window, select OK.

 

Категории