The objective of this document is to assist you in the monitoring of your Exchange 2013 architecture
Exchange 2013 Architecture, Concepts and Components
Exchange Server 2013 brings together two basic building blocks. Each provides a unit of high availability and fault tolerance that are separated from each other.
DAGDatabase Availability Group (DAG)
CASEClient Access Servers: Client Access Servers form the Client Access Server (CAS) group
ServiceNav provides you with a set of service templates to monitor your entire Exchange 2013 architecture.
Configuration
General
It is recommended to put all the servers in your Exchange 2013 architecture under supervision.
For all physical or virtual servers, depending on the operating system, apply the following host templates:
- Windows 2008 systemThis model is intended for Windows 2008 servers. It lets you know if the host is UP or DOWN and also performs checks to retrieve the CPU, RAM, SWAP, and disk I/O usage. Use discovery to monitor disk partitions and network interfaces.
- Windows 2012 system: This template is for Windows 2012 servers. It lets you know if the host is UP or DOWN and also checks CPU, RAM, SWAP, and disk I/O usage. Use discovery to monitor disk partitions and network interfaces.
- Windows 2016 system: This template is for Windows 2016 servers. It lets you know if the host is UP or DOWN and also checks CPU, RAM, SWAP, and disk I/O usage. Use discovery to monitor disk partitions and network interfaces.
CASE (Client Access Server)
Monitor connectivity to the virtual IP or VIP
On CAS servers, depending on the architecture deployed, apply the following templates:
- HTTP/HTTPS test HTTP/HTTPS request, to be used to monitor the URL of the virtual IP
- TCP-Port Test whether the TCP port specified in the configuration is open, and collects the connection time, to be used for monitoring the following ports:
- IMAP4 clients (143-993)
- POP3 clients (110-995)
- Authenticated SMTP clients (587)
- SMTP (25)
- HTTP (80)
- The front-end transport service (717)
Exchange Services on Exchange 2013 Client Access Servers
On CAS servers, monitor the status of services grouped by impact BLOCKING or DEGRADING via the service model MS-WIN-ServicesList-Started:
Services with impact BLOCKING:
- MSExchangeADTopology
- MSExchangeDiagnostics
- MSExchangeFrontEndTransport
- MSExchangeServiceHost
Services with impact DEGRADING:
- MSExchangeHM
- MSExchangeIMAP4
- MSExchangePOP3
- HostControllerService
- MSExchangeUMCR
Monitor Exchange performance on Exchange 2013 Client access servers
On CAS servers, apply the following templates - don't rely on the naming, the templates below are compatible with Exchange 2013:
- MS-EXCHANGE2013-TAIL-LENGTHIndicates the length of a queue, expressed as a number of messages.
- MS-EXCHANGE2007_2010-ADAccessMicrosoft Exchange Server: Indicates the number of Microsoft Exchange Server searches to the Active Directory out of time in the last minute.
- MS-EXCHANGE2007-SMTP-MSGS-RECEIVEDThis is the rate at which SMTP messages are delivered to the transport server, expressed in messages per second.
- MS-EXCHANGE2007-SMTP-MSGS-SENT: Indicates how often SMTP messages are sent from the transport, expressed in messages per second.
- MS-Exchange-Certificate-ExpirationIf you have multiple certificates, calculates the number of days remaining before the expiration date of the Exchange certificate. If multiple certificates, calculates the number of days remaining before the expiration date of each certificate and alerts if at least one certificate exceeds the threshold.
Edge Transport
Exchange Services on Exchange 2013 Transport Edge Servers
On the Edge Transport serversmonitor the start-up of services grouped by impact BLOCKING or DEGRADING via the service model MS-WIN-ServicesList-Started:
Services with impact BLOCKING:
- ADAM_MSExchange
- MSExchangeDiagnostics
Services with impact DEGRADING:
- MSExchangeAntispamUpdate
- MSExchangeEdgeCredential
- MSExchangeHM
- MSExchangeServiceHost
- MSExchangeTransport
- MSExchangeTransportLogSearch
DAG (Database Availability Group)
Monitor connectivity to box Letterbox (MBX)
On MBX servers, depending on the architecture deployed, apply the following model:
- TCP-PortTests whether the TCP port specified in the configuration is open, and collects the connection timeout, to be used to monitor the next port:
- HTTP (80)
Exchange services on Exchange 2013 mailbox servers
On MBX servers, monitor the start of services grouped by impact BLOCKING or DEGRADING via the service model MS-WIN-ServicesList-Started:
Services with impact BLOCKING:
- MSExchangeADTopology
- MSExchangeDagMgmt
- MSExchangeDiagnostics
- MSExchangeMailboxReplication
- MSExchangeDelivery
- MSExchangeSubmission
- MSExchangeRepl
- MSExchangeRPC
- MSExchangeFastSearch
- HostControllerService
- MSExchangeServiceHost
- MSExchangeThrottling
Services with impact DEGRADING:
- MSExchangeAntispamUpdate
- MSExchangeEdgeSync
- MSExchangeIMAP4BE
- MSExchangeMailboxAssistants
- MSExchangePOP3BE
- WSBExchange
- MSExchangeTransport
- MSExchangeTransportLogSearch
- MSExchangeUM
Monitor the size of Exchange databases and mailboxes
On MBX servers, apply the following templates:
- MS-EXCHANGE-MailboxDatabaseStatusPS: monitors the size of an Exchange database and notifies if it exceeds a threshold.
- MS-EXCHANGE-MailboxStatusPS: returns the mailbox quota status on an Exchange server.
Monitor DAG replication
On MBX servers, apply the following template:
- MS-Exchange-DAG-Replication-Status: checks all aspects of replication and replay for a mail server within a database availability group (DAG). Alerts to problems or replication failures.
Monitor Exchange performance on the servers of Exchange 2013 mailboxes
On MBX servers, apply the following templates - don't rely on the naming, the templates below are compatible with Exchange 2013:
- MS-EXCHANGE2007-MSGS-RECEIVED-BY-MSIndicates how often messages are delivered to the storage bank, expressed in messages per second
- MS-EXCHANGE2007-MSGS-SENT-TO-T: Indicates how often messages are sent to the transport server, expressed in messages per second
Active Directory
Monitor access to the Active Directory
On AD servers, apply the following template:
- MS-Active_Directory: Active directory connection test, notifies if the test fails.
- Internal DNSTests a DNS query internally and notifies if the test fails.
- External DNSTests an external DNS request.
IT Weather Services
Once the equipment and services are added to the supervision, create your service weather following the best practices available here
Go directly to the cause of the degradation of your email service:
Dashboards
Link your service weather to a mapping-type dashboard by following the best practices available here
