Transcript Transport components shipping with Exchange 2013 Overview of Exchange 2013 Architecture Architectural improvements made in Transport History, Challenges, Improvements, Reasons for change Mail routing.

Transport components shipping with Exchange 2013
Overview of Exchange 2013 Architecture
Architectural improvements made in Transport
History, Challenges, Improvements, Reasons for change
Mail routing scenarios
Built-in redundancy in Transport
client access
mailbox
mailbox
• Evolution of E2010
CAS Array
• Now includes,
SMTP Frontend
Transport
Database
Availability Group
• Now Includes, all
core messaging
protocols
Enterprise Network
Forefront
Online
Protection for
Exchange
External
SMTP
servers
Edge Transport
Routing and AV/AS
CAS Array
DAG
CAS
MBX
CAS
MBX
CAS
MBX
CAS
MBX
CAS
MBX
Layer 4LB
2 Building Blocks
Client Access Array
Mobile
phone
Web
browser
Outlook
(remote user)
Outlook (local user)
Line of
business
application
AD
Phone system
(PBX or VOIP)
EWS protocol
MRS proxy protocol
SMTP
Protocols,
Server Agents
Business Logic
Storage
MRS MRSProxy
EWS
Transport
MRS MRSProxy
Transport
RPC CA
Assistants
Assistants
RPC CA
XSO
Mail Item
XSO
Mail Item
CTS
Other API
CTS
Other API
Store
Content index
Store
Content index
ESE
File system
ESE
File system
Server1 (Vn)
Banned
E2010
Server2 (Vn+1)
EWS
User
For a given mailbox’s connectivity, the protocol
being used is always served by the server that
hosts the active database copy
Each CAS determines the right end point for the
traffic, and so all sessions – regardless of where
they started – end up in the same place
This means that the rendering for clients
like OWA occurs on the Mailbox server, Transport
transcoding is occurring on the Mailbox server, etc.
Layer 4LB
CAS
DAG1
MBX-A
MBX-B
Handles inbound and outbound external
SMTP traffic
External SMTP
(Does not replace the Edge Transport Server Role)
Handles authenticated client submissions
Functions as a layer 7 proxy and has full
access to protocol conversation
Will not queue or bifurcate mail locally
All outbound traffic to next hop appears to
come from the CAS2013
Listens on TCP25 and TCP587 and TCP717
External SMTP
Frontend Transport
SMTP Receive
Protocol
Agents
SMTP Send
Mailbox
Selector
MSExchangeFrontendTransport.exe
SMTP from
MBX13
SMTP to
MBX13
*previously known as Hub Transport
Processes all SMTP mail flow for
the organization
Will queue and route messages in
and out of the organization
SMTP from
CAS
SMTP to CAS,
MBX, HUB
Transport
SMTP Receive
SMTP Send
Protocol Agents
Performs content inspection
Supports extensibility in SMTP
and categorizer
Listens on TCP465 and TCP2525
(when co-located with CAS)
or TCP25 otherwise
*previously known as Hub Transport
Categorizer
Routing Agents
Pickup/Replay
Delivery
Queue
Submission
Delivery Agents
Queue
*other protocols
Delivery
Queue
Edgetransport.exe
SMTP from
MBX-Transport
Submission
SMTP to
MBX-Transport
Delivery
Handles mail submission and delivery from/to
Store using two separate processes
Does not have persistent storage
Performs MIME to MAPI conversion (and vice
versa)
Combines Mailbox Assistant and Store Driver
functionality
(Supports all E2010 store driver extensibility events)
Leverages local RPC for delivery to and
submission from Store
Does not support any extensibility
SMTP from
Transport
SMTP to
Transport
SMTP to
Transport
Mailbox Transport
SMTP
Receive
SMTP
Send
SMTP Send
Delivery
Submission
Deliver
Agents
Mailbox
Assistants
MSExchangeDelivery.exe
Submit
Agents
MSExchangeSubmission.exe
MAPI
MAPI
Store
Next hop selection is broken down into distinct delivery groups:
Messages reaching their final routing destination get delivered via SMTP through
Mailbox Transport to Store
Transport uses least cost routing logic to ensure messages traverse optimal paths in
terms of cost and hops
Server selection within delivery group is based on recipient type
•
•
•
•
•
•
•
•
Scenario 1 – Incoming mail on a multi-role server
Scenario 2 – Incoming mail on two multi-role servers
Scenario 3 – Originating mail on two multi-role servers
Scenario 4 – Incoming mail to a DG on separated roles
Scenario 5 – Incoming mail to a legacy mailbox user
Scenario 6 – Client Submission to a single unified namespace
Scenario 7 – Client Submission for a legacy mailbox
Scenario 8 – Transport high availability
Frontend Transport receives
message on port 25
... looks up where recipient’s mailbox exists and routes to a
Transport service within the delivery group for that mailbox
Transport receives message on
port 2525
… processes it and routes it to mailbox transport delivery
on server where mailbox is active
Mailbox Transport Delivery
receives the message on port
475
… converts MIME to MAPI and delivers message to Store.
Internet or MBX2013
DAG
Server
CAS 2013
Frontend Transport
MBX 2013
Transport
Mailbox Transport
Store
EHLO
250 OK
MAIL FROM
250 OK
RCPT TO
250 OK
DATA
(TLS Session)
EHLO
XPROXYFROM
MAIL FROM
250 OK
Frontend
Transport
Internet
250 OK
QUIT
RCPT TO
250 OK
DATA
Mailbox
Transport
Transport
250 OK
QUIT
(TLS Session)
EHLO
XSESSIONPARAMS
X-MESSAGECONTEXT
MAIL FROM
250 OK
RCPT TO
250 OK
DATA
250 OK
QUIT
Received: from EXHV-1889.EXHV-5245dom.extest.microsoft.com
(2001:4898:e8:3050:d9f3:8ace:7a2f:900b) by
EXHV-1889.EXHV-5245dom.extest.microsoft.com
(2001:4898:e8:3050:d9f3:8ace:7a2f:900b) with Microsoft SMTP Server (TLS) id
15.0.620.3 via Mailbox Transport; Sun, 27 Jan 2013 11:50:14 -0800
Received: from EXHV-1889.EXHV-5245dom.extest.microsoft.com
(2001:4898:e8:3050:d9f3:8ace:7a2f:900b) by
EXHV-1889.EXHV-5245dom.extest.microsoft.com
(2001:4898:e8:3050:d9f3:8ace:7a2f:900b) with Microsoft SMTP Server (TLS) id
15.0.620.3; Sun, 27 Jan 2013 11:50:13 -0800
Received: from Internet (172.18.140.30) by
EXHV-1889.EXHV-5245dom.extest.microsoft.com (10.176.198.88) with Microsoft
SMTP Server (TLS) id 15.0.620.3 via Frontend Transport; Sun, 27 Jan 2013
11:50:10 -0800
Subject: Incoming mail on all-in-one role
Message-ID: <0eecd3ae-f179-4852-bb5e-4b2a371cbb2c@EXHV-1889.EXHV5245dom.extest.microsoft.com>
From: <[email protected]>
Internet
2 Recipients
DAG
Server1
Server2
CAS 2013
CAS 2013
Frontend Transport
MBX 2013
Frontend Transport
MBX 2013
Transport
Transport
Mailbox Transport
Mailbox Transport
Store
Store
Site
Internet
DAG
Server1
Server2
CAS 2013
CAS 2013
Frontend Transport
MBX 2013
3 Recipients
Frontend Transport
MBX 2013
Transport
Transport
Mailbox Transport
Mailbox Transport
Store
Store
Site
(TLS Session)
EHLO
250 OK
MAIL FROM
250 OK
RCPT TO
250 OK
DATA
250 OK
Internet
EHLO
250 OK
Frontend
Transport
QUIT
(TLS Session)
XPROXYTO
250 OK
MAIL FROM
MAIL FROM
250 OK
RCPT TO
250 OK
DATA
250 OK
QUIT
250 OK
RCPT TO
250 OK
DATA
250 OK
QUIT
Transport
Mailbox
Transport
4 Recipients
Internet
CAS2013
2013
CAS
CAS 2013
CAS2013
2013
CAS
CAS 2013
Frontend Transport
CAS2013
2013
CAS
CAS 2013
Frontend Transport
CAS2013
2013
CAS
CAS 2013
Frontend Transport
Frontend Transport
DAG
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
Transport
Mailbox Transport
Mailbox Transport
Mailbox Transport
Mailbox Transport
Store
Store
Store
Site Boundary
Transport
Site Boundary
Transport
Site Boundary
Transport
Store
5 Recipients
Internet
CAS2013
2013
CAS
CAS 2013
CAS2013
2013
CAS
CAS 2013
Frontend Transport
CAS2013
2013
CAS
CAS 2013
Frontend Transport
CAS2013
2013
CAS
CAS 2013
Frontend Transport
Frontend Transport
DAG
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
MBX 2013
Transport
Mailbox Transport
Mailbox Transport
Mailbox Transport
Mailbox Transport
Store
Store
Store
Site Boundary
Transport
Site Boundary
Transport
Site Boundary
Transport
Store
E2010
Hub
E2010
MBX
Store
mail.fabrikam.com
CAS 2013
CAS 2013
Frontend Transport
DAG
M1
M2
M3
M4
M5
M6
M7
M8
Site 1
Region Boundary
Frontend Transport
DAG
M1
M2
M3
M4
M5
M6
M7
M8
Site 2
EHLO
250 OK
(TLS Session)
AUTH
(TLS Session)
XPROXY
250 OK
250 OK
MAIL FROM
MAIL FROM
250 OK
250 OK
RCPT TO
SMTP Mail
Client
250 OK
DATA
250 OK
QUIT
Frontend
Transport
RCPT TO
250 OK
DATA
250 OK
QUIT
Transport
Mailbox
Transport
mail.contoso.com
CAS 2013
CAS 2013
Frontend Transport
Frontend Transport
EI4
EI4
E2010
Hub
Hub
Hub
EI4
EI4
E2010
Hub
Hub
MBX
MBX
MBX
MBX
MBX
DAG 2
MBX
MBX
MBX
MBX
Site Boundary
DAG 1
MBX
MBX
MBX
MBX
MBX
MBX
MBX
MBX
Every message is redundantly persisted before its receipt is acknowledged
to the sender
Delivered messages are kept redundant in transport similar to active messages
Every DAG represents a transport HA boundary and owns its HA implementation
Resubmits due to transport DB loss or MDB *over are fully automatic and do not
require any manual involvement
Introduced in Office 365 to redundantly store all mail for a configured time span to
protect against irrecoverable mailbox failures
Now has a “shadow” equivalent and is no longer a SPOF
Consolidates and improves E2010 Transport Dumpster functionality
Processes replay requests by resubmitting messages from “primary” or “shadow”
Safety Net for mailboxes fail overs or lag restores
@MSFTExchange
Join the conversation, use #IamMEC
www.iammec.com
: http://fasttrack.office.com//
http://channel9.msdn.com/Events/TechEd
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn
event,data,context
*,,attempting to connect
+,,
<,"220 EXHV-1889.EXHV-5245dom.extest.microsoft.com Microsoft ESMTP MAIL Service, Version:
15.0.620.3 ready at Sun, 27 Jan 2013 11:20:15 -0800",
*,,Proxying inbound session with session id 08CFC9991D5EDBC8
>,EHLO EXHV-1889.EXHV-5245dom.extest.microsoft.com,
(ignoring irrelevant log lines)
>,X-ANONYMOUSTLS,
<,220 2.0.0 SMTP server ready,
*,,Received certificate
*,4D0CD977F383E38D1C411378C905E818C81E1703,Certificate thumbprint
>,EHLO EXHV-1889.EXHV-5245dom.extest.microsoft.com,
(ignoring irrelevant log lines)
250-XPROXY
250-XPROXYFROM
(…contd)
>,X-EXPS EXCHANGEAUTH SHA256 ,
>,<Binary Data>,
<,235 <authentication information>,
XPROXYFROM SID=08CFC9991D5EDBC8 IP=172.18.140.30 PORT=65009 DOMAIN=Internet SEQNUM=1
PERMS=1073 AUTHSRC=Anonymous
<,250 XProxyFrom accepted,
*,,sending message with RecordId 0 and InternetMessageId <290f8811-303d-4c48-ad8f5640c483bfc5@EXHV-1889.EXHV-5245dom.extest.microsoft.com>
>,MAIL FROM:<[email protected]> SIZE=0 AUTH=<>,
>,RCPT TO:<[email protected]>,
<,250 2.1.0 Sender OK,
<,250 2.1.5 Recipient OK,
>,DATA,
<,354 Start mail input; end with <CRLF>.<CRLF>,
<,250 2.6.0 <290f8811-303d-4c48-ad8f-5640c483bfc5@EXHV-1889.EXHV5245dom.extest.microsoft.com> [InternalId=171798691841] Queued mail for delivery,
event,data,context
*,,attempting to connect
+,,
<,"220 EXHV-1889.EXHV-5245dom.extest.microsoft.com Microsoft ESMTP MAIL Service, Version:
15.0.620.3 ready at Sun, 27 Jan 2013 11:50:13 -0800",
(ignoring irrelevant log lines)
Received: from SERVER03.fabrikam.com (2001:4898:0:fff:0:5efe:10.166.18.212) by SERVER04.fabrikam.com
(2001:4898:0:fff:200:5efe:157.54.94.31) with Microsoft SMTP Server (TLS) id
15.0.516.32 via Mailbox Transport; Mon, 28 Jan 2013 22:50:59 -0800
Received: from CAS.fabrikam.com (2001:4898:0:fff:200:5efe:157.54.94.14) by SERVER03.fabrikam.com
(2001:4898:0:fff:0:5efe:10.166.18.212) with Microsoft SMTP Server (TLS) id
15.0.516.32; Mon, 28 Jan 2013 22:50:56 -0800
Received: from mail.contoso.com (2001:4898:e8:3050:d9f3:8ace:7a2f:900b) by CAS.fabrikam.com
(2001:4898:dc05:24:5545:ee44:4948:d594) with Microsoft SMTP Server (TLS) id
15.0.620.4 via Frontend Transport; Mon, 28 Jan 2013 22:50:54 -0800
<--- mail crosses the organization boundary --->
Received: from SERVER01.contoso.com (2001:4898:e8:3050:d9f3:8ace:7a2f:900b) by SERVER01.contoso.com
(2001:4898:e8:3050:d9f3:8ace:7a2f:900b) with Microsoft SMTP Server (TLS) id
15.0.620.3; Mon, 28 Jan 2013 22:49:48 -0800
Received: from SERVER01.contoso.com ([fe80::d9f3:8ace:7a2f:900b]) by SERVER01.contoso.com
([fe80::d9f3:8ace:7a2f:900b%12]) with mapi id 15.00.0620.000; Mon, 28 Jan
2013 22:49:48 -0800
From: Jerry <[email protected]>
To: "[email protected]" <[email protected]>, Tom <[email protected]>, Jack <[email protected]>
Subject: Scenario 3 - Originating mail
All mailflow scenarios are monitored across three
transport components
Each health set has multiple monitors and probes that
execute synthetic transactions and assess the state of
the service
Responder workflows execute and alert when health
sets become unhealthy
Transport has three component states – Active,
Draining and Inactive.
In “Active” state, a component is considered
provisioned and handles user and probe traffic
In “Draining” state, no new user traffic is accepted;
messages queued on the server can be delivered
(This state is reserved for stateful transport service only)
In “Inactive” state, only monitoring probe traffic
is accepted
New Cmdlets
Cmdlets with new properties
Provides a snapshot summary of messages queued
across multiple scopes – Forest, DAG, Site, Server
Aggregation runs every minute and is configurable
Only queues having a threshold of >=10 messages
are aggregated by default
Queues can be pivoted by NextHopDomain,
NextHopCategory, NextHopKey, DeliveryType, Status,
LastError, or ServerName properties on the queue
All three components generate to protocol,
connectivity, agent and DNSnew logs
Transport and mailbox transport on mailbox role
generate message tracking logs
Transport, in addition to above, generates IRM,
active user/server statistics, routing table, queuenew,
workload management (WLM)new and QueueQuotanew