Forum Discussion
Adam_Smith_1456
Nimbostratus
Apr 17, 2007Exchange 2003 configuration behind BigIP
We have some exchange front-end servers behind our BigIP (version 4.x) and we are not able to view the mail queues on other exchange servers. Does anyone know what we need to allow through the BigIP f...
Adam_Smith_1456
Nimbostratus
May 08, 2007I am not sure if this is what you are looking for but here is the config information for our front-end exchange servers.
pool ex_80 {
persist cookie
cookie_mode rewrite
cookie_expiration 0d 01:00:00
fallback "https://connect.wsu.edu/exchange"
member 10.2.0.52:http
member 10.2.0.53:http
}
pool ex_443 {
persist cookie
cookie_mode insert
cookie_expiration 0d 01:00:00
fallback "http://www.wsu.edu/fallback/connect.html"
member 10.2.0.52:https
member 10.2.0.53:https
}
pool ex_993 {
lb_method least_conn_member
persist none
cookie_expiration 0d 01:00:00
nat disable
member 10.2.0.52:imap2
member 10.2.0.53:imap2
member 10.2.0.140:imap2
}
pool ex_593 {
member 10.2.0.52:593
member 10.2.0.53:593
member 10.2.0.140:593
}
pool ex_25 {
member 10.2.0.52:smtp
member 10.2.0.53:smtp
member 10.2.0.140:smtp
}
pool ex_135 {
lb_method least_conn_member
nat disable
member 134.121.1.123:135
}
pool FEX-01_RDP {
member 10.2.0.52:3389
}
pool FEX-02_RDP {
member 10.2.0.53:3389
}
pool FEX-01_8081 {
member 10.2.0.52:8081
}
pool FEX-02_8081 {
member 10.2.0.53:8081
}
pool FEX-03_RDP {
member 10.2.0.140:3389
}
pool FEX-03_8081 {
member 10.2.0.140:8081
}
virtual 134.121.1.30:80 unit 1 {
use pool ex_80
vlans internal disable
}
virtual 134.121.1.30:25 unit 1 {
use pool ex_25
vlans internal disable
}
virtual 134.121.1.30:135 unit 1 {
use pool ex_135
vlans internal disable
}
virtual 127.0.1.30:80 unit 1 {
netmask 255.255.255.255
use pool ex_443
vlans internal disable
}
virtual 127.1.1.30:80 unit 1 {
netmask 255.255.255.255
use pool ex_993
vlans internal disable
}
virtual 127.2.1.30:80 unit 1 {
netmask 255.255.255.255
use pool ex_593
vlans internal disable
}
virtual 134.121.0.52:3389 unit 1 {
use pool FEX-01_RDP
}
virtual 134.121.0.52:8081 unit 1 {
use pool FEX-01_8081
}
virtual 134.121.0.53:3389 unit 1 {
use pool FEX-02_RDP
}
virtual 134.121.0.53:8081 unit 1 {
use pool FEX-02_8081
}
virtual 134.121.0.140:8081 unit 1 {
use pool FEX-03_8081
}
virtual 134.121.0.140:3389 unit 1 {
use pool FEX-03_RDP
}
proxy 134.121.1.30:443 unit 1 {
target virtual 127.0.1.30:80
clientssl enable
clientssl key connect.wsu.edu.key
clientssl cert connect.wsu.edu.crt
header insert "FRONT-END-HTTPS: on"
redirects rewrite all
}
proxy 134.121.1.30:993 unit 1 {
target virtual 127.1.1.30:80
clientssl enable
clientssl key connect.wsu.edu.key
clientssl cert connect.wsu.edu.crt
vlans internal disable
}
proxy 134.121.1.30:593 unit 1 {
target virtual 127.2.1.30:80
clientssl enable
clientssl key connect.wsu.edu.key
clientssl cert connect.wsu.edu.crt
The traffic from the front-ends to the back-ends goes out through the BigIP's and onto the network that the back-ends are on.
We do view the queue viewer and the message tracking information from the back-ends.
I will work on getting a tcpdump for that as well.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
