06-16-2006 08:15 AM
Hello,
I have a problem that has just come up and I cannot find a clear straight answer or method to do this.
I have a 2-armed config serving several mailservers using publics for vip's and private space for internal servers, pretty standard.
we loadbalance pop3, http and smtp typically served through mail.domain.com and we need to offload all of the smtp traffic to an external site ip now rather than the internal serverfarm and were looking for a way to do this without modifying/separating the fqdn that several thousands of customers are already using.
content ibbs-http
add service ibbs1-http
add service ibbs2-http
add service ibbs3-http
add service ibbs4-http
port 80
protocol tcp
advanced-balance arrowpoint-cookie
arrowpoint-cookie name IBBSWebMail1
arrowpoint-cookie expiration 00:08:00:00
vip address 200.200.200.100
add service ibbs5-http
add service ibbs6-http
add service ibbs7-http
active
content ibbs-pop3
add service ibbs1-pop3
add service ibbs2-pop3
add service ibbs3-pop3
add service ibbs4-pop3
port 110
protocol tcp
vip address 200.200.200.100
add service ibbs5-pop3
add service ibbs6-pop3
add service ibbs7-pop3
active
content ibbs-smtp <--------
add service ibbs1-smtp
add service ibbs2-smtp
add service ibbs3-smtp
add service ibbs4-smtp
port 25
protocol tcp
vip address 200.200.200.100
add service ibbs5-smtp
add service ibbs6-smtp
active
the ibbs-smtp content rule is the traffic we now need to send not internal to known services, but to an external VIP for lack of a better term to offload the smtp traffic to an outsourced entity.
Is there an easy way to do this or is this even possible within the CSS architecture?
Derek Waldroop
Integrated BroadBand Services
06-21-2006 08:12 AM
If you need to just send the trafic to an external VIP :
add the route to the destination :
ip route
service external_servers
ip address
protocol tcp
port 25
keepalive retryperiod 10
keepalive frequency 255
active
content ibbs-smtp
add service external_servers
port 25
protocol tcp
vip address 200.200.200.100
active
then when a client want to go to 200.200.200.100, it is routed to
Be aware that the connexion will still use the client @ so you need to add a route for the return.
In order to bypass that you can NAT client IP addresses
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide