A10 AX SERIES Bedienungsanleitung PDF herunterladen (Seite 37)

Performance by Design

Deployment Guide for Microsoft Exchange Server 2010

2.7 Exchange Client Access Roles – RPC

Exchange RPC access offers end users with Microsoft Outlook access to their mailboxes via the native

Microsoft Outlook Messaging API (MAPI) protocol.

AX provides the following benets:

• Load Balancing and High Availability of Exchange RPC servers

Technical Note:

Outlook using the MAPI protocol contacts the Exchange server via TCP port 135 rst and then opens

a dynamic port between 1024 and 65535. Since by default any dynamic port number can be used, this

requires a wildcard VIP on the AX that listens on all TCP ports. This is the conguration shown below.

For security reasons, it is possible and recommended by Microsoft to specify the dynamic port Outlook

will open; see the following:

• http://technet.microsoft.com/en-us/library/ff625248.aspx#ipports

• http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncov-

ering-new-rpc-client-access-service-exchange-2010-part2.html

If you limit the dynamic ports for MAPI, you can limit the ports open on AX via an ACL.

2.7.1 AX Conguraon

a. Create Exchange RPC Real Servers

• Create a real server for each Exchange RPC real server. Enter the RPC Name and IP address,

and add Protocol TCP port 0 with no Health Monitor

◦ Via Web GUI: Cong Mode > Service > SLB > Server

◦ Via CLI: AX(cong)#slb server Exchange1 10.0.2.161

AX(cong-real server)#port 0 tcp

AX(cong-real server-node port)#no health-check

1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 84 85

Keine Kommentare

A10 AX SERIES Bedienungsanleitung Seite 37