Port aliases, Binding same real ports to multiple vip ports – Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) User Manual
Page 88

72
Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Multiple port binding
2
Port aliases
When you associate a virtual port (VIP) with a real server, you make the association for a particular
TCP or UDP port. The association of a TCP or UDP port on a VIP with a TCP or UDP port on a real
server is called a "port binding".
In most configurations, only one VIP-to-real-server binding is made for a TCP or UDP port. For
example, if you bind VIP 10.29.2.2 to real server 10.0.0.1 for port 80 (the well-known HTTP port),
you do not generally create any other bindings between VIP 10.29.2.2 and real server 10.0.0.1 for
the same port. However, should you wish to track statistics for multiple applications or domain
names mapped to the same real server port, you can do so by creating multiple port bindings.
One method of binding a single real server port to multiple VIPs is to configure a port alias for each
additional VIP. For example, if you want to associate three VIPs with the same real server, you can
define two TCP or UDP port aliases, one for each of the additional VIPs.
In such a configuration, the Brocade Virtual ADX collects and displays statistics and configuration
information individually for each VIP, but sends all traffic to the same TCP or UDP port number on
the real server.
Binding same real ports to multiple VIP ports
Multiple port binding enables a real server port to be bound to multiple VIP ports, which is useful
when you want to bind multiple VIPs to a single application service on real servers, and the real
servers are listening on different ports.
NOTE
This command is backward-compatible with the real-port command.
To bind multiple ports to one real server port, follow these steps.
1. Create a real server with two ports.
Virtual ADX(config)#server real rs1
Virtual ADX(config-rs-rs1)#port 81
Virtual ADX(config-rs-rs1)#port 8081 <- alias port
2. Create a second real server with two ports.
Virtual ADX(config)#server real rs2
Virtual ADX(config-rs-rs2)#port 82
Virtual ADX(config-rs-rs2)#port 8082 <- alias port
3. Create a virtual server.
Virtual ADX(config)#server virtual-name-or-ip vs1
4. Configure an HTTP port on the virtual server.
Virtual ADX(config-vs-vs1)#port http
5. Bind the alias ports to the real servers on the virtual servers.
Virtual ADX(config-vs-vs1)#bind http rs1 81 rs2 82
6. Create a second virtual server with an HTTP port.
Virtual ADX(config)#server virtual-name-or-ip vs2
Virtual ADX(config-vs-vs2)#port http