Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 82)

66 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Port ranges
2
Defining a port range
Port ranges are identified by their names. A port range can be created as follows.
1. Define the port range
Virtual ADX(config)#port-range pr1
Syntax: [no] port-range port-range-name
2. Identify the ports in the range.
Virtual ADX(config-pr-pr1)#port 8051 to 8100
Syntax: [no] port port-number to port-number
Enter the port’s numerical value for port-number.
When defining a port range:
• Ports in a port range must be consecutive.
• You must define a starting port and an ending port for the range.
• The starting port must be greater than zero (0).
• The ending port must be larger than the starting port.
• There can be up to 50 ports in a port range.
• You can change the starting port and ending port using a single command. When changing the
ports in a port range, if the port range is not used with a bind statement or other configuration,
then the change is applied immediately; otherwise, the change remains pending until the apply
port-range command is issued.
• You cannot include the default port (65535) and well-known ports in a port range.
• Furthermore, if role-based management is used, only the super user or global manager can
create port ranges at the global configuration level. Role-based users can use port ranges and
bind them under the real server and virtual server configuration levels. Also, role-based users
can view the list of port ranges by issuing the show port-range command.
• If you define many port ranges to cover many application ports (several hundreds or thousands
of ports) then you need to keep an eye on MP CPU resources, because a system might not be
able to handle health checks for all these ports. Disabling of health checks for several ports or
port-ranges might be needed in such cases to prevent health check issues.
• Port ranges cannot be used with alias port ("real-port") definitions.
• Some of the other features not supported with port range are: Multiple port binding, PBSLB,
boolean health check, scripted health check, track-groups, track-ports, tcp offload, and
keepalive.