Translations of this page:

Osmius

Osmius Agent for Exchange 2007
Agent name: osm_ag_EXCHNG07 Agent code: EXCHNG07
Content: Osmius Agent for Microsoft Exchange Server 2007 User Manual
Date: 04/10/2009 Revision Date: / /

General Information

This agent can monitor various parameters of Microsoft Exchange Server 2007 mail servers using WMI technology. It has been tested in different environments. However, we recommend checking its functionality before implanting it in a production environment.

Exchange 2007 agent has been developed using functionalities and enhancements of Osmius framework and ACE libraries, so it is necessary to install the ACE libraries for the proper deployment and operation of Exchange 2007 Osmius agent. See chapter: installation.

EXCHNG07 agent provides up to 8 basic events with configuration parameters to allow scaling of a very simple way, in addition 2 informative events provides details of the monitored system. Events have been selected by the Research and Development Osmius Team as the most interesting for this first development.

Events are based on WQL statements, so local and remote monitoring is possible.

HEYYY!!: As shown in official Microsoft doc http://msdn.microsoft.com/en-us/library/aa393720%28VS.85%29.aspx
The connection timeout can not be changed and can reach up to 120 seconds (2 minutes). This means that,
if there is no availability of the instance there may be some latency in the # appearance of
Osmius critical events in the web console and as standalone mode, due to it is a external Osmius limitation.

Exchange 2007 Instance

As a general rule each Osmius agent can monitor one instance type. If you are not familiar with these concepts check out the glossary. Each instance is individually defined in the configuration file (if you want further information go to agents and instances); depending on agent type is the instance type and depending on instance is the connection info.

CONNECTION_INFO

The connection information or connection_info is data that the agent needs to know to connect to the instance. (See more about the connection_info

For Exchange 2007 Osmius agent the connection_info prototype would be:

CONNECTION_INFO= -h HOST -d DOMAIN -u USER -p PASSWORD

Replace the following:

  • HOST: IP address or host name where Exchange 2007 server is. Optional. About firewall settings
  • DOMAIN: Domain or WorkGroup name. Mandatory if HOST has been declared.
  • USER: Username with WMI permissions. Mandatory if HOST has been declared. About user permissions settings
  • PASSWORD: password for user specified above. Mandatory if HOST has been declared.

For local monitoring (monitoring the system where the agent is installed) connection_info must be empty, because we don't need connect anywhere.

Examples:

CONNECTION_INFO= -h 192.168.1.1 -d WORKGROUP -u admin -p pass
CONNECTION_INFO=

TYPE

The type defines the instance type to be monitored. Every declared instance must be associated with a type as you can see here

For Exchange 2007:

TYPE= EXCHNG07

Event summary table for Exchange 2007

Here's briefly the capabilities of this agent, further down on this page each event is described in more detail.

EVENT DESCRIPTION c w a tseconds Extra parameters / Remarks
EXUSERCN Number of connected users 0 50 100 300 Silent mode ( -s) recommmended
EXRECQSZ Reception Queue Size 0 400 500 300 Interesant parameter for capacity plannings
EXMDELPS Delivered messages per second 0 5 10 60 Silent mode ( -s) recommmended
EXAVDELT Average Delivery Time 0 5 10 300 Silent mode ( -s) recommmended
EXMSENTS Sent message per second 0 30 60 60 Silent mode ( -s) recommmended
EXFSUBMS Failed Submissions per second 0 1 5 300 Silent mode ( -s) recommmended
EXRPCAVL Average RPC Latency 0 40 50 300 Modo silencioso ( -s) recomendado
EXRPCREQ RPC Requests 0 25 100 60 Interesant parameter for capacity plannings

Information Events

Info events retieve general data about instance, usually this data doesn't change over time. This kind of events have no severity, simply provides instance details.

EVENT DESCRIPTION tseconds Observations
ENINFHST Hosta name) 43200 (12 hours) Unique name of a device connected to a network
EXINFVER Exchange version 43200 (12 hours) Exchange server version data

Exchange 2007 agent events

EXUSERCN

EXUSERCN event will return the number of users connected to Exchange server

Return values:

VALUE MEANING
-1 Error
X Connected users

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 300 seconds – 1 hour –> depends on instance importance
Warning threshold Consult with your Exchange 2007 administrator
Alert threshold Consult with your Exchange 2007 administrator

Parameter setting example:

EXUSERCN = -t 900 -c 0 -w 50 -a 100 -T "Connected users"

Comment: This event returns the number of real users connected to server.

EXRECQSZ

EXRECQSZ event returns reception queue size of Exchange.

Return values:

VALUE MEANING
-1 Error
X Reception Queue Size

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold 400
Alert threshold 500

Parameter setting example:

EXRECQSZ = -t 300 -c 0 -w 400 -a 500 -T "Reception Queue"

Comment: This event is very useful for capacity plannings.

EXMDELPS

EXMDELPS event returns average ammount of delivered messages per second in Exchange.

Return values:

VALUE MEANING
-1 Error
X Develivered messages/second

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold Consult with your Exchange 2007 administrator
Alert threshold Consult with your Exchange 2007 administrator

Parameter setting example:

EXMDELPS = -t 60 -c 0 -w 5 -a 10 -T "Delivered per second"

Comment:

EXAVDELT

EXAVDELT event returns average delivery time in Exchange.

Return values:

VALUE MEANING
-1 Error
X Average delivery time

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold Consult with your Exchange 2007 administrator
Alert threshold Consult with your Exchange 2007 administrator

Parameter setting example:

EXAVDELT = -t 300 -c 0 -w 5 -a 10 -T "Average Delivery time"

Comment:

EXMSENTS

EXMSENTS event return the average number of sent messages per second in Exchange.

Return values:

VALUE MEANING
-1 Error
X sent messages/second

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold Consult with your Exchange administrator
Alert threshold Consult with your Exchange administrator

Parameter setting example:

EXMSENTS = -t 60 -c 0 -w 25 -a 50 -T "Sent message per second"

Comment:

EXFSUBMS

EXFSUBMS event returns failed submissions per second of Exchange.

Return values:

VALUE MEANING
-1 Error
X Failed submissions per second

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold 1
Alert threshold 5

Parameter setting example:

EXFSUBMPS = -t 300 -c 0 -w 1 -a 5 -T "Failed submissions"

Comment:

EXRPCAVL

EXRPCAVL returns RPC average latency of Exchange 2007 server.

Return values:

VALUE MEANING
-1 Error
X RPC latency

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold 40
Alert threshold 50

Parameter setting example:

EXRPCAVL = -t 300 -c 0 -w 40 -a 50 -T "RPC Average Latency"

Comment: This event gives a very accurate idea of Exchange mail server performance.

EXRPCREQ

EXRPCREQ returns number of Exchange 2007 RPC request.

Return values:

VALUE MEANING
-1 Error
X RPC request

Recommended parameters:

Comparison type Direct. The higher value the higher severity (-c 0)
Monitoring interval 60 seconds – 15 minutes –> depends on instance importance
Warning threshold 25 - Consult with your Exchange administrator
Alert threshold 100 - Consult with your Exchange administrator

Parameter setting example:

EXRPCREQ = -t 300 -c 0 -w 25 -a 100 -T "RPC Requests"

Comment: This event is very useful for capacity plannings.

Exchange 2007 agent prerequisites

In order to compile, this agent requires a set of prerequisites, which are generic to compile any Osmius agent, you can see these prerequisites.

Verify that your system supports WMI.

Exchange 2007 agent makefiles and compilation

  • Make Project Creator (MPC) is used by Osmius, so creating Makefiles is a trivial task. If you want to learn more about MPC and Osmius check out the section of Makefiles on Osmius.
  • In the particular case of Exchange 2007 Osmius agent and Visual C 8 you can easily generate Makefile as follows:

From the agent directory using console or terminal.

%ACE_ROOT%\bin\mpc.pl -type vc8 osm_ag_exchange2007.mpc
  • Now that you created the Makefile, agent compiling is extremely simple.
Double click on Osm_Ag_Exchange2007_Osmius.vcproj and the project will be opened with Visual C.
Select the Rebuild option to compile.

Binaries are automatically installed in the bin directory of OSM_ROOT base directory.

Run Exchange 2007 agent

Exchange 2007 agent have the same running features of the other Osmius agents. You can check it out int he section Start and Stop Agents.

To run Exchange 2007 agent without Osmius web console:

osm_ag_EXCHNG07.exe -c osm_ag_EXCHNG07.ini -m MASTERAG -p 1950 -d » [>> osm_ag_exchange2007.log]1)

Running in standalone mode

Exchange 2007 Osmius agent, like the others Osmius agents, allows the execution in standalone mode. This option may be particularly useful when developing a new agent or to perform specific agent tests.

Basically you have to add a new value, called SNDCMD, to Exchange 2007 Osmius agent configuration file (osm_ag_EXCHNG07.ini) as shown here.

Then you must run the Exchange 2007 Osmius agent setting Master Agent communications port to zero, for example:

osm_ag_EXCHNG07.exe -c osm_ag_EXCHNG07.ini -m 00000000 -p 0 -d

Tests list

Performed test for Exchange 2007 Osmius agent.

Date: / /
Test Results Comment
Creating an instance with all its events in silent mode - -
Creating an instance with all its events with custom text - -
Creating an instance with all its events but no custom text - -
Declaration of 3 instances with all its events to 5 seconds and keep it
running for 48 hours
- -
Declare 2 instances, cause a disconnect and then reconnect - -
Declare 1 instance and test each event - -
Elimination of general parameter and check unbootable - -
Elimination of instance CONN_INFO and check unbootable - -

APPENDIX

User permissions settings

To set up an user to access WMI without adding the user to an Administrative group, follow the next steps.

  1. Click Start, click Run, type wmimgmt.msc in the Open box, and then click OK.
  2. Right-click WMI Control, and then click Properties.
  3. Click the Security tab.
  4. Expand the Root folder, select the CIMV2 folder, and then click Security.
  5. Click Add. Type the user name you wish to use in the Enter the object names to select box, click Check Names to verify your entry or entries, and then click OK.
  6. In the Permissions for User list, click the Allow check box next to the following permissions:
    1. Execute Methods
    2. Enable Account
    3. Remote Enable
    4. Read Security
  7. Click Advanced. In the Permission entries list, select the user you added in step 5, and then click Edit.
  8. In the Apply onto box, click This namespace and subnamespaces.
  9. Click OK three times.
  10. Quit the WMI Control snap-in.
  11. Click Start, click Run, type dcomcnfg.exe in the Open box, and then click OK.
  12. Select Component Services and then expand it. Then expand Computers. Right-click My Computer and select Properties.
  13. Select the COM Security tab.
  14. In the Access Permissions section, click Edit Limits….
  15. Click Add. Type the user name you wish to use in the Enter the object names to select box, click Check Names to verify your entry or entries, and then click OK.
  16. In the Permissions for User list, click the Allow check box next to the following permissions:
    1. Local Access
    2. Remote Access
    3. Click OK.
  17. In the Launch and Activation Permissions section, click Edit Limits….
  18. Click Add. Type the user name you wish to use in the Enter the object names to select box, click Check Names to verify your entry or entries, and then click OK.
  19. In the Permissions for User list, click the Allow check box next to the following permissions:
    1. Local Launch
    2. Remote Launch
    3. Local Activation
    4. Remote Activation
    5. Click OK twice.
  20. Expand My Computer and expand DCOM Config.
  21. Right-click Windows Management and Instrumentation and click Properties.
  22. Click the Security tab.
  23. In the Access Permissions section, click Edit….
  24. Click Add. Type the user name you wish to use in the Enter the object names to select box, click Check Names to verify your entry or entries, and then click OK.
  25. In the Permissions for User list, click the Allow check box next to the following permissions:
    1. Local Access
    2. Remote Access
    3. Click OK twice.
  26. Quit the Component Services snap-in.
  27. Restart the target computer.

Firewall settings

To enable or disable WMI traffic using Windows firewall user interface

  1. Control Panel - Security - Windows Firewall.
  2. Click Change Settings and then click the Exceptions tab.
  3. In the Exceptions window, select the check box for Windows Management Instrumentation (WMI) to enable WMI traffic through the firewall.


You can do it at the command prompt.

  1. To enable WMI traffic through the Windows firewall.
    • netsh advfirewall firewall set rule group=“windows management instrumentation (wmi)” new enable=yes
  2. To disable WMI traffic through the Windows firewall.
    • netsh advfirewall firewall set rule group=“windows management instrumentation (wmi)” new enable=no


If you have another firewall other than Windows, is good to know that DCOM communications (used by WMI) are usually made using port 135.

1) Optional, to store agent messages in a file
 
en/agentes/exchng07.txt · Last modified: 2012/12/05 19:12 by osmius
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki