Application Delivery (ADX)

Reply
N/A
Posts: 1
Registered: ‎06-25-2013

Configuring Real Servers - Multiple ports query..

Hi everyone..

I am looking to get some advice regarding the correct way to set up some real servers on our new ServerIron..

Im currently in the process of migrating services over from our existing Cisco CSS ( horrible thing ) to our new ServerIron, and have come across a potential setup issue for us..

I will try and explain with this example..

In the old Cisco world, we would set up the real servers like this.. ( to save space, I have left some filler config out, but hopefully should be enough to get an idea of  set up ).

service SERVER1_APP1

Ip address 10.1.1.1

Port 80

Keepalive port 3333

Keep alive url " /app1alive.htm"

Service SERVER1_APP1_copy

Ip address 10.1.1.1

Port 80

Keepalive port 3333

Keep alive url " /app1alive.htm"

Service SERVER1_APP2

Ip address 10.1.1.1

Port 2228

Keepalive port 3333

Keep alive url " /app2alive.htm"

So, one physical real server but several services running off it using different ports.. The keepalives ports used are the same but it checks a unique url based on the service app.  ( e.g. app1alive.htm, app2alive.htm )

These services ( real servers ) are then assigned to a virtual loadbalancing ip addresses as normal..

One of the advantages this gave us in the old world, is the ability to set up a test instance using the same real server but not affecting the live service (ie.. We could suspend service SERVER1_APP1_copy and not affect the live service SERVER1_APP1 )..

I have approached the real server migration from Cisco CSS to our new Brocade in two  ways..

Create each of these real server services separately ( so this would look vaguely similar to our current setup ) …

server remote-name SERVER1_APP1 10.1.1.1

Port 3333

Port 3333 keepalive

Port 3333 url "HEAD /app1alive1.htm"

However, when I try creating the 2nd real server service which would point to different keepalive url, it is rejected because the server ip address 10.1.1.1 is already defined in the config.

telnet@ServerIronADX 1000(config)#server remote-name SERVER1_APP2 10.1.1.1

Error - duplicate IP address with real server SERVER1_APP1 10.1.1.1

Error - Failed to create real server

As this kind of makes sense, I have tried to reconfigure this by defining the overall real server rather than the unique service on the server.

Server remote-name SERVER1 10.1.1.1

Port 3333

Port 3333 keepalive

Port 3333 url "HEAD /app1alive1.htm"

However, I am now confused how we define the other services which run on this real server ( eg. APP2 and APP1copy )..

These services would use the same keepalive port ( e.g. 3333 ) on the real server but have a unique url to check ( e.g. app2alive.htm, app3alive.htm ).. Is this still possible and how do we distinguish between them ?.

I cant see any problems configuring if the port numbers are unique to the server but looking at the online documentation, I cant see how we can create the other services on the same real server ( e.g. APP1copy, APP2 )..

Hope this makes sense.. !

Thanks in advance for any advice about what Im doing wrong..

Jon

Broadcom
Posts: 70
Registered: ‎03-14-2009

Re: Configuring Real Servers - Multiple ports query..

Hi Jon,

CSS is quite far away from me. But to help you:

Think of setting up different virtual servers. You can bind the same real server port several times under different virtual server ports.

You can not have different L7 healtch checks bound to the same real server port.

What maybe helpful is to use healthck policy and boolean healthchecks.

HTH

Alex

Contributor
Posts: 74
Registered: ‎08-18-2011

Re: Configuring Real Servers - Multiple ports query..

Hi Jon,

You can use alias port and port-policy (bound on vip port) to achieve same functionality. Here is a sample config.

server port-policy app1
  protocol http
  protocol http url "HEAD /app1.html"
  protocol http status-code 100 300

server port-policy app2
  protocol http
  protocol http url "HEAD /app2.html"
  protocol http status-code 100 300

server real appserver 1.1.2.3
port 1111
port 2222
port 3333

server virtual app1_vip 2.2.2.1
port http
port http use-port-policy app1
bind http appserver 1111
!
server virtual app2_vip 2.2.2.3
port http
port http use-port-policy app2
bind http appserver 2222 real-port 1111
!
server virtual app1_test 2.2.2.4
port http
port http use-port-policy app1
bind http appserver 3333 real-port 1111
!

Regards,

Mohit

-Mohit Sahni

Join the Community

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

vADC is now Pulse Secure
Download FREE NVMe eBook