For more details, please see ourCookie Policy.

Ethernet Switches & Routers

Not applicable
Posts: 1
Registered: ‎07-08-2011

Load balancing proxy servers with ServerIron 1000 ADX

I am load balancing our proxy servers using ServerIron 1000ADX. Now, that was not my desission so please do not hold it against me :-). I am just trying to make things work. The load balancing works fine, the issue is that proxy is listening on port 8080 which is not one of the "standard' ports that serveriron can do l7 monitoring. So if the proxy servers have issue getting to the internet, SI will still send clients to them. I am looking for a way to configure the SI to actually periodically get pages from known web sites through the proxies to ensure that they are working fine and if that fails to mark that proxy server as being down and not send clienst to it. Is that possible to do?

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: Load balancing proxy servers with ServerIron 1000 ADX

Hi vess.nedevski,

FYI - ServerIron and ADX questions should be in this location

Configuring a port policy

Follow the steps given below to configure a port policy.

1. First create a policy by entering a command such as the following.

ServerIron(config)# server port-policy p1

Syntax: server port-policy <policy-name>

Once the policy is named, the CLI changes to the configuration-port-policy level.

2. (Optional) Specify the port that will be checked by the policy.

ServerIron(config-port-policy-name)# port 8080

Syntax: ServerIron ADX(config-port-policy-name)# port <port-num>

3. Specify what protocol will be checked on the traffic that passes through the port.

ServerIron(config-port-policy-name)# http

Syntax: protocol <protocol-value>

If the protocol is not configured, the policy cannot be bound to a real server port.

Enter a TCP or UDP port name or number for <protocol-value>. For TCP ports, enter FTP (port 21), HTTP (port 80), IMAP4 (port 143), LDAP (port 389), LDAPS (port 636), MMS (port 1755),

NNTP (port 119), PNM (port 7070), POP3 (port 110), RTSP (port 554), SMTP (port 25), TELNET (port 23)


Ports 20 and 21 both are FTP ports but on the ServerIron, the name "FTP" corresponds to port 21.

For UDP ports, enter DNS (port 53) or RADIUS (port 1812)

4. Configure a keepalive interval under a port policy

ServerIron(config)# server port-policy pp1

ServerIron(config-port-policy-pp1)# keepalive-interval 5

Syntax: keepalive-interval <seconds>

Refer to “Configuring a keepalive interval under a port policy” on page 291 for more details.

5. (Optional) Enter the number of times the policy will be tried before the ServerIron ADX marks the port as "UP" or "DOWN".

ServerIron(config-port-policy-name)# retries 5

Syntax: retries <num>

The default is 3 tries.

6. (Optional) Specify the protocol value.

ServerIron(config-port-policy-name)# protocol http url

Syntax: protocol <protocol-options>

Enter one of the following for <protocol-options>, specifying the values for the required


• http status-code <min> <max>

• http url <url>

• http content-match <match-list>

• dns addr-query <value>

• dns zone <value>

• radius key <radius-key>

• radius password <value>

• radius nas-ip <ip-address>

• radius nas-port <value>

7. (Optional) Enable the Layer 4 check feature in the policy.

ServerIron(config-port-policy-name)# l4-check

Syntax: l4-check

By default, Layer 7 health check is enabled; however, Layer 4 health check is not. You must enable Layer health check if you want to use that feature.

Binding the policy

After the policy is configured, return to the configuration level and bind the policy to a real server port. For example:

ServerIron(config)# server real r1

ServerIron(config-rs-name)# port <port-num> use-port-policy <policy-name>

Syntax: server real <real-server-name> <real-server-ip-address>

Syntax: port <port-num> use-port-policy <policy-name>

Enter the name of the policy you created for <policy-name>

Once a policy is bound to a real server port, the ServerIron ADX will use the values configured in the policy for health checks.

The ServerIron ADX sends a health check to the port configured in the policy; however, if you do not configure a port number in the policy, then the ServerIron ADX sends the health check to the port to which it is bound.

Example 3:

In the following example, Port Policy pp1 is configured with a keepalive interval of 5 seconds, while Port Policy pp2 has a keepalive interval of 30 seconds.

Port Policy pp1 is bound to Real Server rs1 port 8080 and Real Server rs2 port 9090; therefore, these two ports have a 5 second keepalive interval.

Port Policy pp2 is bound to Real Server rs3 port 8080 and Real Server rs4 port 9090. These two ports have a keepalive interval of 30 seconds.

ServerIron(config)# server port-policy pp1

ServerIron(config-port-policy-pp1)# keepalive-interval 5

ServerIron(config-port-policy-pp1)# protocol http

ServerIron(config-port-policy-pp1)# protocol http url "GET /abc.html"

ServerIron(config-port-policy-pp1)# retries 3

ServerIron(config-port-policy-pp1)# exit

ServerIron(config)# server port-policy pp2

ServerIron(config-port-policy-pp2)# keepalive-interval 30

ServerIron(config-port-policy-pp2)# protocol http

ServerIron(config-port-policy-pp2)# protocol http url "GET /xyz.html"

ServerIron(config-port-policy-pp2)# retries 2

ServerIron(config-port-policy-pp2)# exit

ServerIron(config)# server real rs1

ServerIron(config-rs-r1)# port 8080

ServerIron(config-rs-r1)# port 8080 use-port-policy pp1

ServerIron(config-rs-r1)# exit

ServerIron(config)# server real rs2

ServerIron(config-rs-r2)# port 9090

ServerIron(config-rs-r2)# port 9090 use-port-policy pp1

ServerIron(config-rs-r2)# exit

ServerIron(config)#server# real rs3

ServerIron(config-rs-r3)# port 8080

ServerIron(config-rs-r3)# port 8080 use-port-policy pp2

ServerIron(config-rs-r3)# exit

ServerIron(config)# server real rs4

ServerIron(config-rs-r4)# port 9090

ServerIron(config-rs-r4)# port 9090 use-port-policy pp2

ServerIron(config-rs-r4)# exit



Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.