|
Application
|
Download link
|
What does it do?
|
What’s included?
|
|
Exchange 2010
|
jetPACK-1.1.1.1-Exchange-2010
|
This jetPACK will add the basic settings to load balance Microsoft Exchange 2010. There is a flightPATH rule included to redirect traffic on the HTTP service to HTTPS, but it is an option. If you don’t have a license for flightPATH, this jetPACK will still work.
|
Global settings: Service timeout 2 hours
Monitors: Layer 7 monitor for the Outlook web app, and Layer 4 out of band monitor for client access service
Virtual Service IP: 1.1.1.1
Virtual Service Ports: 80, 443, 135, 59534, 59535
Real Servers: 127.1.1.1 127.2.2.2
flightPATH: Adds redirect from HTTP to HTTPS
|
|
|
jetPACK-1.1.1.2-Exchange-2010-SMTP-RP
|
Same as above, but it will add an SMTP service on port 25 in reverse proxy connectivity. The SMTP server will see the ALB-X interface address as the source IP.
|
Global settings: Service timeout 2 hours
Monitors: Layer 7 monitor for the Outlook web app. Layer 4 out of band monitor for client access service
Virtual Service IP: 1.1.1.1
Virtual Service Ports: 80, 443, 135, 59534, 59535, 25 (reverse proxy)
Real Servers: 127.1.1.1 127.2.2.2
flightPATH: Adds redirect from HTTP to HTTPS
|
|
|
jetPACK-1.1.1.3-Exchange-2010-SMTP-DSR
|
Same as above, except this jetPACK will configure the SMTP service to use Direct Server Return connectivity. This jetPACK is needed if your SMTP server needs to see the actual IP address of the client.
|
Global settings: Service timeout 2 hours
Monitors: Layer 7 monitor for the Outlook web app. Layer 4 out of band monitor for client access service
Virtual Service IP: 1.1.1.1
Virtual Service Ports: 80, 443, 135, 59534, 59535, 25 (direct server return)
Real Servers: 127.1.1.1 127.2.2.2
flightPATH: Adds redirect from HTTP to HTTPs
|
|
Exchange 2013
|
jetPACK-2.2.2.1-Exchange-2013-Low-Resource
|
This setup adds 1 VIP and two services for HTTP and HTTPS traffic and requires the least CPU.
It is possible to add multiple health checks to the VIP to check each of the individual services is up
|
Global settings:
Monitors: Layer 7 monitor for OWA, EWS, OA, EAS, ECP, OAB, and ADS
Virtual Service IP: 2.2.2.1
Virtual Service Ports: 80, 443
Real Servers: 127.1.1.1 127.2.2.2
flightPATH: Adds redirect from HTTP to HTTPS
|
|
|
jetPACK-2.2.3.1-Exchange-2013-Med-Resource
|
This setup uses a unique IP address for each service and therefore uses more resources than above. You must configure each service as an individual DNS entry Example owa.jetnexus.com, ews.jetnexus.com, etc. A monitor for each service will be added and applied to the relevant service
|
Global settings:
Monitors: Layer 7 monitor for OWA, EWS, OA, EAS, ECP, OAB,ADS, MAPI and PowerShell
Virtual Service IP: 2.2.3.1, 2.2.3.2, 2.2.3.3, 2.2.3.4, 2.2.3.5, 2.2.3.6, 2.2.3.7, 2.2.3.8, 2.2.3.9, 2.2.3.10
Virtual Service Ports: 80, 443
Real Servers: 127.1.1.1 127.2.2.2
flightPATH: Adds redirect from HTTP to HTTPs
|
|
|
jetPACK-2.2.2.3-Exchange2013-HIgh-Resource
|
This jetPACK will add one unique IP address and several virtual services on different ports. flightPATH will then context switch based on the destination path to the correct Virtual Service. This jetPACK requires the most amount of CPU to carry out the context switching
|
Global settings:
Monitors: Layer 7 monitor for OWA, EWS, OA, EAS, ECP, OAB, ADS, MAPI and PowerShell
Virtual Service IP: 2.2.2.3
Virtual Service Ports: 80, 443, 1, 2, 3, 4, 5, 6, 7
Real Servers: 127.1.1.1 127.2.2.2
flightPATH: Adds redirect from HTTP to HTTPS
|
