03-26-2007 12:50 PM
We have 2 IIS servers running two MOSS 2007 appications. The app owners want keepalives setup for each application which each application is using the same IP and just different hostnames. So I need an example to do keepalives using a hostname / uri index.html for example rather then it using the IP address.
I'm inheriting a system and don't want to break what's working so any examples would be greatly appreciated.
Thanks
Jim
Solved! Go to Solution.
03-27-2007 05:07 AM
Jim,
This is how I utilize 1 server with multiple web sites. The web server is configured to respond to http host headers. For this to work DNS needs to be correct. Each web site has a keepalive file for the script to check.
service connections-1
ip address 1.1.1.1
keepalive port 80
redundant-index 8001
keepalive type script ap-kal-httptag "connections1.company.com /keepalive/lb.htm connections1"
keepalive frequency 15
active
service datacentacc-1
ip address 1.1.1.1
keepalive port 80
redundant-index 8030
keepalive type script ap-kal-httptag "datacenteraccess1.company.com /keepalive/lb.htm datacenteraccess1"
keepalive frequency 15
active
DNS entries for the individual web sites will point to the servers. I.E. connections1.company.com = 1.1.1.1
datacenteraccess1.company.com = 1.1.1.1
The Content rules will be the following.
content connections
vip address 2.2.2.2
advanced-balance sticky-srcip
redundant-index 8000
add service connections-1
protocol tcp
port 80
url "//connections.company.com/*"
active
content datacenteraccess
vip address 2.2.2.2
advanced-balance sticky-srcip
redundant-index 8025
add service datacentacc-1
port 80
protocol tcp
url "//datacenteraccess.company.com/*"
active
Rich
03-26-2007 09:08 PM
Hi Jim,
There are two ways that you can configure this setup, depending on your needs.
First, you can use a keepalive uri like this:
service a
ip address 1.1.1.1
keepalive uri "/index1.htm"
keepalive method head
keepalive port 80
active
service b
ip address 1.1.1.1
keepalive uri "/index2.htm"
keepalive method head
keepalive port 80
active
As you can see the only difference between those services is the uri in the keepalive uri line.
Second, you can use an scripted keepalive like this one:
service a
ip address 1.1.1.1
keepalive type script ap-kal-httplist "1.1.1.1 /index1.htm"
active
service a
ip address 1.1.1.1
keepalive type script ap-kal-httplist "1.1.1.1 /index2.htm"
active
Notice that both services are the same with the difference in the uri, just like the first example.
The only thing that you need to consider is that the CSS has restrictions about the number of scripted keeplives that can run at the same time.
I hope this helps. Thanks!
Regards,
Jose Quesada.
03-27-2007 05:07 AM
Jim,
This is how I utilize 1 server with multiple web sites. The web server is configured to respond to http host headers. For this to work DNS needs to be correct. Each web site has a keepalive file for the script to check.
service connections-1
ip address 1.1.1.1
keepalive port 80
redundant-index 8001
keepalive type script ap-kal-httptag "connections1.company.com /keepalive/lb.htm connections1"
keepalive frequency 15
active
service datacentacc-1
ip address 1.1.1.1
keepalive port 80
redundant-index 8030
keepalive type script ap-kal-httptag "datacenteraccess1.company.com /keepalive/lb.htm datacenteraccess1"
keepalive frequency 15
active
DNS entries for the individual web sites will point to the servers. I.E. connections1.company.com = 1.1.1.1
datacenteraccess1.company.com = 1.1.1.1
The Content rules will be the following.
content connections
vip address 2.2.2.2
advanced-balance sticky-srcip
redundant-index 8000
add service connections-1
protocol tcp
port 80
url "//connections.company.com/*"
active
content datacenteraccess
vip address 2.2.2.2
advanced-balance sticky-srcip
redundant-index 8025
add service datacentacc-1
port 80
protocol tcp
url "//datacenteraccess.company.com/*"
active
Rich
03-27-2007 05:25 AM
Thanks Rich. This is working for me. I appreciate your help and the example!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: