Cisco IOS Server Load Balancing Command Reference
Cisco IOS Server Load Balancing Command Reference
Command Reference
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
CONTENTS
A through K 8
access (firewall farm) 9
access (server farm) 12
access (virtual server) 14
address (custom UDP probe) 16
address (DNS probe) 18
address (HTTP probe) 20
address (ping probe) 22
address (TCP probe) 24
address (WSP probe) 26
advertise 28
agent 30
apn 32
bindid 34
calling-station-id 36
clear fm slb counters 38
clear ip slb connections 39
clear ip slb counters 41
clear ip slb sessions 43
clear ip slb sticky asn msid 45
clear ip slb sticky gtp imsi 46
clear ip slb sticky radius 48
client (virtual server) 50
credentials (HTTP probe) 53
delay (firewall farm TCP protocol) 55
delay (virtual server) 57
expect 59
failaction (firewall farm) 61
failaction (server farm) 62
faildetect (custom UDP probe) 64
faildetect (DNS probe) 65
A through K
Command Default The default source IP address is 0.0.0.0 (routes flows from all sources to this firewall farm). The default
source IP network mask is 0.0.0.0 (routes flows from all source subnets to this firewall farm). The default
destination IP address is 0.0.0.0 (routes flows from all destinations to this firewall farm). The default
destination IP network mask is 0.0.0.0 (routes flows from all destination subnets to this firewall farm). If
you do not specify an inbound interface, the firewall farm accepts inbound packets on all inbound
interfaces. If you do not specify the inbound datagram connection option, IOS SLB creates connections
only for outbound traffic. If you do not specify an outbound interface, the firewall farm accepts outbound
packets on all outbound interfaces.
Usage Guidelines You can specify more than one source or destination for each firewall farm. To do so, configure multiple
access statements, making sure the network masks do not overlap each other.
You can specify up to two inbound interfaces and two outbound interfaces for each firewall farm. To do so,
configure multiple access statements, keeping the following considerations in mind:
All inbound and outbound interfaces must be in the same Virtual Private Network (VPN) routing and
forwarding (VRF).
All inbound and outbound interfaces must be different from each other.
You cannot change inbound or outbound interfaces for a firewall farm while it is in service.
If you do not configure an access interface using this command, IOS SLB installs the wildcards for the
firewall farm in all of the available interfaces of the device, including the VRF interfaces. If IOS SLB is not
required on the VRF interfaces, use this command to limit wildcards to the specified interfaces only.
By default, IOS SLB firewall load balancing creates connections only for outbound traffic (that is, traffic
that arrives through the real server). Inbound traffic uses those same connections to forward the traffic,
which can impact the CPU. To enable IOS SLB to create connections for both inbound traffic and
outbound traffic, reducing the impact on the CPU, use the access inbound datagram connection
command.
Command Examples The following example routes flows with a destination IP address of 10.1.6.0 to firewall farm FIRE1:
access interface
no access interface
Command Default The server farm handles outbound flows from real servers on all interfaces.
Usage Guidelines The virtual server and its associated server farm interfaces must be in the same Virtual Private Network
(VPN) routing and forwarding (VRF).
You can specify up to two access interfaces for each server farm. To do so, configure two access
statements, keeping the following considerations in mind:
The two interfaces must be in the same VRF.
The two interfaces must be different from each other.
The access interfaces of primary and backup server farms must be the same.
You cannot change the interfaces for a server farm while it is in service.
If you do not configure an access interface using this command, IOS SLB installs the wildcards for the
server farm in all of the available interfaces of the device, including the VRF interfaces. If IOS SLB is not
required on the VRF interfaces, use this command to limit wildcards to the specified interfaces only.
Command Examples The following example limits the server farm to handling outbound flows from real servers only on access
interface Vlan106:
Usage Guidelines This command enables framed-IP routing to inspect the ingress interface when routing subscriber traffic.
All framed-IP sticky database entries created as a result of RADIUS requests to this virtual server will
include the interface in the entry. In addition to matching the source IP address of the traffic with the
framed-IP address, the ingress interface must also match this interface when this command is configured.
You can use this command to allow subscriber data packets to be routed to multiple service gateway
service farms.
The virtual server and its associated server farm interfaces must be in the same Virtual Private Network
(VPN) routing and forwarding (VRF).
You can specify up to two framed-IP access interfaces for each virtual server. To do so, configure two
access statements, keeping the following considerations in mind:
The two interfaces must be in the same VRF.
The two interfaces must be different from each other.
You cannot change the interfaces for a virtual server while it is in service.
If you do not configure an access interface using this command, IOS SLB installs the wildcards for the
virtual server in all of the available interfaces of the device, including the VRF interfaces. If IOS SLB is not
required on the VRF interfaces, use this command to limit wildcards to the specified interfaces only.
Command Examples The following example enables framed-IP routing to inspect ingress interface Vlan20:
Command Default If the custom UDP probe is associated with a firewall farm, you must specify an IP address. If the custom
UDP probe is associated with a server farm, and you do not specify an IP address, the address is inherited
from the server farm real servers.
Command Examples The following example configures a custom UDP probe named PROBE6, enters custom UDP probe
configuration mode, and configures the probe to receive responses from IP address 13.13.13.13:
Command Default If the DNS probe is associated with a firewall farm, you must specify an IP address. If the DNS probe is
associated with a server farm, and you do not specify an IP address, the address is inherited from the server
farm real servers.
Command Examples The following example configures a DNS probe named PROBE4, enters DNS probe configuration mode,
and configures the probe to receive responses from IP address 10.1.10.1:
Command Default If the HTTP probe is associated with a firewall farm, you must specify an IP address. If the HTTP probe is
associated with a server farm, and you do not specify an IP address, the address is inherited from the server
farm real servers.
Command Examples The following example configures an HTTP probe named PROBE2, enters HTTP probe configuration
mode, and configures the probe to receive responses from IP address 10.1.10.1:
Command Default If the ping probe is associated with a firewall farm, you must specify an IP address. If the ping probe is
associated with a server farm, and you do not specify an IP address, the address is inherited from the server
farm real servers.
Command Examples The following example configures a ping probe named PROBE1, enters ping probe configuration mode,
and configures the probe to receive responses from IP address 10.1.10.1:
Command Default If the TCP probe is associated with a firewall farm, you must specify an IP address If the TCP probe is
associated with a server farm, and you do not specify an IP address, the address is inherited from the server
farm real servers.
Command Examples The following example configures a TCP probe named PROBE5, enters TCP probe configuration mode,
and configures the probe to receive responses from IP address 10.1.10.1:
Command Default If the WSP probe is associated with a firewall farm, you must specify an IP address. If the WSP probe is
associated with a server farm, and you do not specify an IP address, the address is inherited from the server
farm real servers. In dispatched mode, the ip-address argument value is the same as the virtual server IP
address. In directed Network Address Translation (NAT) mode, an IP address is unnecessary.
Command Examples The following example configures a WSP probe named PROBE3, enters WSP probe configuration mode,
and configures the probe to receive responses from IP address 10.1.10.1:
advertise
To control the installation of a static route to the Null0 interface for a virtual server address, use the
advertise command in SLB virtual server configuration mode. To prevent the installation of a static route
for the virtual server IP address, use the no form of this command.
advertise [active]
no advertise [active]
Command Default The virtual server IP address is advertised. That is, a static route to the Null0 interface is installed for the
virtual server IP addresses and it is added to the routing table. If you do not specify the activekeyword, the
host route is advertised regardless of whether the virtual IP address is available.
Usage Guidelines Advertisement of a static route using the routing protocol requires that you configure redistribution of static
routes for the routing protocol.
The advertise command does not affect virtual servers used for transparent web cache load balancing.
HTTP probes and route health injection require a route to the virtual server. The route is not used, but it
must exist to enable the sockets code to verify that the destination can be reached, which in turn is essential
for HTTP probes and route health injection to function correctly.
For HTTP probes, the route can be either a host route (advertised by the virtual server) or a default
route (specified using the ip route 0.0.0.0 0.0.0.0command, for example). If you specify either the no
advertise or the advertise active command, you must specify a default route.
For route health injection, the route must be a default route.
HTTP probes and route health injection can both use the same default route; you need not specify two
unique default routes.
Command Examples The following example prevents advertisement of the virtual servers IP address in routing protocol
updates:
agent
To identify a Dynamic Feedback Protocol (DFP) agent with which the IOS Server Load Balancing (IOS
SLB) feature can initiate connections, use the agentcommand in SLB DFP configuration mode. To remove
a DFP agent definition from the DFP configuration, use the no form of this command.
Command Default The default timeout is 0 seconds (no timeout). The default retry count is 0 (infinite retries). The default
retry interval is 180 seconds.
Release Modification
12.2 This command was integrated into Cisco IOS
Release 12.2.
Usage Guidelines A DFP agent collects status information about the load capability of a server and reports that information to
a load manager. The DFP agent may reside on the server, or it may be a separate device that collects and
consolidates the information from several servers before reporting to the load manager.
The password specified in the ip slb dfp command for the DFP manager must match the password
specified in the password command for the DFP agent.
You can configure up to 1024 agents.
Command Examples The following example sets the DFP password to Password1 (to match the DFP agents password), sets the
timeout to 360 seconds, enters DFP configuration mode, and enables IOS SLB to connect to the DFP agent
with IP address 10.1.1.1 and port number 2221:
apn
To configure an ASCII regular expression string to be matched against the access point name (APN) for
general packet radio service (GPRS) load balancing, use the apn command in SLB GTP map configuration
mode. To delete the APN string, use the no form of this command.
apn string
no apn string
Usage Guidelines For a given IOS SLB GTP map, you can configure up to 100 apn commands. However, we recommend
you configure no more than 10 apn commands per map.
Command Examples The following example specifies that, for IOS SLB GTP map 2, string .cisco* is to be matched against the
APN:
bindid
To configure a bind ID, use the bindidcommand inSLBserver farm configuration mode. To remove a bind
ID from the server farm configuration, use the no form of this command.
bindid [ bind-id ]
no bindid [ bind-id ]
Usage Guidelines You can configure one bind ID on each bindid command.
The bind ID allows a single physical server to be bound to multiple virtual servers, and to report a different
weight for each one. Thus, the single real server is represented as multiple instances of itself, each having a
different bind ID. Dynamic Feedback Protocol (DFP) uses the bind ID to identify for which instance of the
real server a given weight is specified.
In general packet radio service (GPRS) load balancing, bind IDs are not supported. Therefore do not use
the bindidcommand in a GPRS load-balancing environment.
show ip slb serverfarms Displays information about the IOS SLB server
farms.
calling-station-id
To configure an ASCII regular expression string to be matched against the calling station ID attribute for
RADIUS load balancing, use the calling-station-id command in SLB RADIUS map configuration mode.
To delete the calling station ID match string, use the no form of this command.
calling-station-id string
no calling-station-id string
Usage Guidelines For a given IOS SLB RADIUS map, you can configure a single calling-station-id command or a single
username (IOS SLB) command, but not both.
Command Examples The following example specifies that, for IOS SLB RADIUS map 1, string .919* is to be matched against
the calling station ID attribute in the RADIUS payload:
Command Examples The following example clears the FM IOS SLB inband counters:
Syntax Description firewallfarm firewall-farm (Optional) Clears the IOS SLB connection database
for the specified firewall farm.
Command Default The IOS SLB connection database is cleared for all firewall farms, server farms, and virtual servers.
Usage Guidelines In general packet radio service (GPRS) load balancing, the clear ip slb connections command clears
connections, but does not clear sessions.
Command Examples The following example clears the connection database of server farm FARM1:
The following example clears the connection database of virtual server VSERVER1:
show ip slb serverfarms Displays information about the IOS SLB server
farms.
Command Examples The following example clears the IP IOS SLB counters:
Syntax Description firewallfarm firewall-farm (Optional) Clears the IOS SLB session database for
the specified firewall farm.
serverfarm server-farm (Optional) Clears the IOS SLB session database for
the specified server farm.
vserver virtual-server (Optional) Clears the IOS SLB session database for
the specified virtual server.
Command Default If no optional keywords or arguments are specified, the IOS SLB sessions database is cleared of all firewall
farms, server farms, and virtual servers.
Command Examples The following example clears the session database of server farm FARM1:
Router# clear ip slb sessions serverfarm FARM1
The following example clears the session database of virtual server VSERVER1:
Router# clear ip slb sessions vserver VSERVER1
Syntax Description imsi Clears the entry associated with the specified MSID
from the IOS SLB ASN MSID sticky database.
Usage Guidelines When you use this command to clear an entry from the IOS SLB ASN MSID sticky database, the session is
not cleared; it lingers until it times out. (The session timeout is configured by using the idle command in
SLB virtual server configuration mode; the default timeout is 60 seconds.) To clear the session manually,
use the clear ip slb sessions command in privileged EXEC mode.
Command Examples The following example clears the entry associated with MSID 001646013fc0 from the IOS SLB ASN
MSID sticky database:
Syntax Description id imsi Clears only the entry associated with the specified
IMSI from the IOS SLB GTP IMSI sticky database.
Command Default If you enter this command without the optional IMSI ID, all entries are cleared from the IOS SLB GTP
IMSI sticky database.
Usage Guidelines When you use this command to clear an entry from the IOS SLB GTP IMSI sticky database, the session is
not cleared; it lingers until it times out. (The session timeout is configured by using the idle command in
SLB virtual server configuration mode; the default timeout is 30 seconds.) If the same user tries to create a
new Packet Data Protocol (PDP) context before the session times out, using the same Network Service
Access Point Identifier (NSAPI) but a different access point name (APN), IOS SLB forwards the request to
the old server farm, even though the new APN should lead to a different server farm. To avoid this
problem, clear the session manually by using the clear ip slb sessions command in privileged EXEC mode.
Command Examples The following example clears all entries from the IOS SLB GTP IMSI sticky database:
clear ip slb sticky radius {calling-station-id [id string] | framed-ip [framed-ip [ netmask ]]}
Syntax Description calling-station-id Clears entries from the IOS SLB RADIUS calling-
station-ID sticky database.
Command Default If no optional arguments are specified, all entries are cleared from the IOS SLB RADIUS calling-station-ID
sticky database or framed-IP sticky database.
Usage Guidelines When you use this command to clear an entry from the IOS SLB RADIUS calling-station-ID sticky
database, the session is not cleared; it lingers until it times out. (The session timeout is configured by using
the idle command in SLB virtual server configuration mode; the default timeout is 30 seconds.) If the same
user tries to create a new Packet Data Protocol (PDP) context before the session times out, using the same
Network Service Access Point Identifier (NSAPI) but a different access point name (APN), IOS SLB
forwards the request to the old server farm, even though the new APN should lead to a different server
farm. To avoid this problem, clear the session manually by using the clear ip slb sessions command in
privileged EXEC mode.
Command Examples The following example clears all entries from the IOS SLB RADIUS framed-IP sticky database:
Syntax Description ipv4-address Client IPv4 address. The default is 0.0.0.0 (all
clients).
Command Default The default client IPv4 address is 0.0.0.0 (all clients). The default client IPv4 network mask is 0.0.0.0 (all
subnets). Taken together, the default is client 0.0.0.0 0.0.0.0 (allows all clients on all subnets to use the
virtual server). If you specify gtp carrier-code and you do not specify a code, the virtual server accepts
PDP context creates from any IMSI carrier code.
Usage Guidelines You can use more than one client command to define more than one client.
The netmask value is applied to the source IPv4 address of incoming connections. The result must match
the ipv4-address value for the client to be allowed to use the virtual server.
If you configure probes in your network, you must also do one of the following:
Configure the exclude keyword on the client command on the virtual server to exclude connections
initiated by the client IPv4 address from the load-balancing scheme.
Configure IPv4 addresses on the IOS SLB device that are Layer 3-adjacent to the real servers used by
the virtual server.
Configure separate client commands to specify the clients that can use the virtual server, and to specify the
IMSI carrier code from which the virtual server is to accept PDP context creates.
Dual-stack support for GTP load balancing does not support this command.
Command Examples The following example allows clients from only 10.4.4.0 access to the virtual server:
Command Default Basic authentication values for the HTTP IOS SLB probe are not configured.
Command Examples The following example configures an HTTP probe named PROBE2, enters HTTP probe configuration
mode, sets the HTTP authentication to username Username1, and sets the password to develop:
Router(config)# ip slb probe PROBE2 http
Router(config-slb-probe)# credentials Username1 develop
delay duration
no delay
Syntax Description duration Delay timer duration in seconds. The valid range is
1 to 600 seconds. The default value is 10 seconds.
Usage Guidelines The delay timer allows out-of-sequence packets and final acknowledgments (ACKs) to be delivered after a
TCP connection ends. Do not set this value to zero (0).
If you are configuring a delay timer for HTTP flows, choose a low number such as 5 seconds as a starting
point.
Command Examples The following example specifies that IOS SLB maintains TCP connection context for 30 seconds after a
connection has terminated:
Syntax Description duration Delay timer duration for TCP connection context,
in seconds. The valid range is 1 to 600 seconds. The
default value is 10 seconds.
Command Default The default duration for the TCP connection context is 10 seconds. The default duration for the RADIUS
framed-ip sticky database is 10 seconds.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines The TCP connection context delay timer allows out-of-sequence packets and final acknowledgments
(ACKs) to be delivered after a TCP connection ends. Do not set this value to zero (0).
If you are configuring a TCP connection context delay timer for HTTP flows, choose a low number such as
5 seconds as a starting point.
For the Home Agent Director, the delay command has no meaning and is not supported.
Command Examples The following example specifies that IOS SLB maintains TCP connection context for 30 seconds after a
connection has terminated:
expect
To configure a status code or regular expression to expect information from the HTTP probe, use the
expectcommand in HTTP probe configuration mode. To restore the default settings, use the no form of this
command.
expect [status status-code] [regex expression]
no expect [status status-code] [regex expression]
Syntax Description status status-code (Optional) Configures the expected HTTP status
code. The valid range is 100 to 599. The default
expected status code is 200.
Command Default The default expected status code is 200. There is no default expected regular expression.
Usage Guidelines The expect command configures the expected status code or regular expression to be received from the
servers. A real server is considered to have failed and is taken out of service if any of the following events
occurs:
A status number other than the expected one is received.
The expected regular expression is not received in the first 2920 bytes of probe output. (IOS Server
Load Balancing [IOS SLB] searches only the first 2920 bytes for the expected status code or regular
expression.)
The server fails to respond.
For IOS SLB firewall load balancing, configure the HTTP probe to expect status code 40l.
Command Examples The following example configures an HTTP probe named PROBE2, enters HTTP configuration mode, and
configures the HTTP probe to expect the status code 40l and the regular expression Copyright:
failaction purge
Command Default If you do not specify the failactioncommand, IOS SLB does not automatically remove connections to
failed firewalls.
Usage Guidelines This command is useful for applications that do not rotate the source port (such as Internet Key Exchange
[IKE]), and for protocols that do not have ports to differentiate flows (such as Encapsulation Security
Payload [ESP]).
Command Examples In the following example, IOS SLB removes all connections to failed firewalls in firewall farm FIRE1:
Command Default If you do not specify the failactioncommand, IOS SLB does not perform the following actions:
Remove connections to failed real servers
Remove connections to objects associated with failed real servers
Remove ASN or GPRS sticky objects (IOS SLB continues to assign new session requests to the failed
real servers)
Reassign RADIUS sticky objects
Usage Guidelines This command is useful for applications that do not rotate the source port (such as Internet Key Exchange
[IKE]), and for protocols that do not have ports to differentiate flows (such as Encapsulation Security
Payload [ESP]).
You can specify no failaction purge, but it has no effect on the connection database.
If you specify failaction radius reassign, IOS SLB reassigns RADIUS sticky objects without seeing any
new RADIUS messages. The assumption is that, in the event of a failure, the RADIUS proxy gateways can
handle user flows without seeing the RADIUS messages. If the RADIUS proxy gateways cannot do so, do
not specify the failaction radius reassign command.
Command Examples In the following example, IOS SLB removes all connections to failed real servers in server farm PUBLIC:
faildetect number-of-probes
no faildetect
Command Examples In the following example the unacknowledged custom UDP probe threshold is set to 16:
faildetect number-of-probes
no faildetect
Command Default The default value is three (3) unacknowledged DNS probes.
Command Examples In the following example the unacknowledged DNS probe threshold is set to 16:
faildetect number-of-pings
no faildetect
Command Examples In the following example the unacknowledged ping threshold is set to 16:
faildetect inband
no faildetect inband
Usage Guidelines If you have configured all-port virtual servers (that is, virtual servers that accept flows destined for all ports
except GTP ports), flows can be passed to servers for which no application port exists. When the servers
reject these flows, Cisco IOS SLB might fail the servers and remove them from load balancing. This
situation can also occur in slow-to-respond AAA servers in RADIUS load-balancing environments. To
prevent this situation, you can disable automatic server failure detection using the no faildetect inband
command.
Note If you disable automatic server failure detection using the no faildetect inband command, Cisco strongly
recommends that you configure one or more probes. If you specify the no faildetect inband command, the
faildetect numconns command is ignored, if specified.
Command Examples In the following example, automatic server failure detection is disabled:
Command Default If you do not specify the faildetect numconnscommand, the default value of the connection failure
threshold is 8. If you specify the faildetect numconnscommand but do not specify the numclients
keyword, the default value of the client connection failure threshold is 2.
Release Modification
12.2 This command was integrated into Cisco IOS
Release 12.2.
Usage Guidelines If you specify the no faildetect inband command, the faildetect numconns command is ignored, if
specified.
IOS SLB does not fail the real server until both of the following conditions are met:
There have been number-of-connsconsecutive connection failures.
There have been number-of-clients unique client connection failures.
That is, there can be many consecutive connection failures, but until there have also been number-of-clients
unique client connection failures, IOS SLB does not fail the real server.
Similarly, there can be many unique client connection failures, but until there have also been number-of-
conns consecutive connection failures, IOS SLB does not fail the real server.
GPRS load balancing has the following features:
The numconns keyword specifies the number of consecutive Create Packet Data Protocol (PDP)
requests allowed before IOS SLB fails the gateway GPRS support node (GGSN).
The numclients keyword specifies the number of unique client Create PDP request failures allowed
before IOS SLB fails the GGSN.
Command Examples In the following example, the numconns keyword is set to 10 and the numclients keyword is set to 3:
With those settings, IOS SLB will not fail the real server until there have been ten (10) consecutive
connection failures and there have been three (3) unique client connection failures.
Command Description
real (server farm) Identifies a real server by IP address and optional
port number as a member of a server farm and
enters real server configuration mode.
farm-weight
To specify a weight to be used by the IOS SLB KeepAlive Application Protocol (KAL-AP) agent when
calculating the load value for a server farm, use the farm-weightcommand in server farm configuration
mode. To restore the default weight value, use the no form of this command.
farm-weight setting
no farm-weight
Command Default If you do not configure a KAL-AP farm weight, IOS SLB calculates a relative weight.
Usage Guidelines Configuring a farm-weight enables KAL-AP to calculate loads more accurately when load balancing in a
global server load balancing (GSLB) environment.
For best results, configure a farm-weight that is equal to the sum of the maximum DFP weights for the real
servers in the server farm. (The maximum DFP weight for a real server is configured using the gprs dfp
max-weightcommand in global configuration mode.) For example, if there are three real servers in a server
farm, configured with maximum DFP weights of 100, 50, and 50, then configure a farm-weight of 200
(that is, 100 + 50 + 50). If a real server is added to or removed from the server farm, you must adjust the
farm-weight accordingly.
Command Examples The following example specifies that a weight of 16 is to be used by the KAL-AP agent when calculating
the load value for a server farm:
Router(config-slb-sfarm)# farm-weight 16
ip slb serverfarm Identifies a server farm and enter SLB server farm
configuration mode.
Syntax Description reassign-count (Optional) Number of times IOS SLB can reassign
a session to a new real server. That is, the number
of times that IOS SLB can reassign a rejected
Create PDP Context to a new real GGSN.
The valid range is 1 to 20 reassignments. The
default setting is 2 reassignments (that is, the initial
real server assignment and 2 additional
reassignments).
Command Default The default is 2 reassignments (that is, the initial real server assignment and 2 additional reassignments).
Command Examples The following example specifies that IOS SLB can reassign a session up to 5 times:
gtp session
no gtp session
Command Default IOS SLB creates GTP load-balancing sessions. Sticky-only load-balancing is disabled.
Usage Guidelines Sticky-only load balancing is supported for all versions of GTP.
If sticky-only load balancing (no gtp session) is enabled for GTP:
IOS SLB load-balances GTP Packet Data Protocol (PDP) create requests based on the sticky objects in
the GTP International Mobile Subscriber ID (IMSI) sticky database.
Sticky connections must also be enabled for the virtual server, using the sticky (virtual
server)command.
Automatic server failure detection (the faildetect inband command) is not supported. Instead, use
probes to detect real server failures.
Command Examples The following example specifies that sticky-only load balancing is to be used for GTP:
gw port port
no gw port port
Usage Guidelines The Cisco BWG uses this port when sending delete notifications and NAI update messages to IOS SLB.
If multiple communication ports are needed, the network administrator must identify multiple unique
unused ports.
Command Examples The following example specifies that the Cisco BWG is to use port 63082 to communicate with IOS SLB:
hand-off radius
To change the amount of time IOS Server Load Balancing (IOS SLB) waits for an ACCT-START message
from a new Mobile IP foreign agent in the event of a foreign agent hand-off, use the hand-off
radiuscommand in virtual server configuration mode. To restore the default hand-off timer, use the no
form of this command.
Syntax Description duration Hand-off timer duration in seconds. The valid range
is 1 to 43200 seconds.
Usage Guidelines The hand-off radius timer is valid only for RADIUS virtual servers that have the service radiuskeywords
specified on the virtual command.
Command Examples The following example specifies that IOS SLB waits for 30 seconds after a foreign agent hand-off:
header
To configure the basic authentication values for the HTTP probe, use the headercommand in HTTP probe
configuration mode. To remove a header HTTP probe configuration, use the no form of this command.
header field-name [ field-value ]
no header field-name [ field-value ]
Syntax Description field-name Configures the name of the HTTP probe header.
The character string is limited to 15 characters.
Command Default The following headers are inserted in the request by default:
Accept: */* Connection: close User-Agent: cisco-slb-probe/1.0 Host: virtual IP address
Usage Guidelines The headercommand in HTTP probe configuration mode configures the name and value parameters of the
header.
Note The colon ( : ) separating the field name and field value is automatically inserted if not provided. Multiple
headers with the same name are not supported.
Command Examples The following example configures an HTTP probe named PROBE2, enters HTTP configuration mode, and
configures the HTTP probe header name as HeaderName and value as HeaderValue:
idle duration
no idle
Command Examples The following example instructs IOS SLB to maintain connection information for an idle connection for
120 seconds:
idle duration
no idle
Usage Guidelines If a client sends a TCP packet that is not a sequence number (SYN) or reset (RST) packet, and IOS SLB
does not have a TCP connection object in its table (possibly due to expiration of the idle timer), IOS SLB
sends a TCP RST to the client.
If you are configuring an idle timer for HTTP flows, choose a low number such as 120 seconds as a starting
point. A low number ensures that the IOS SLB connection database maintains a manageable size if
problems at the server, client, or network result in a large number of connections. However, do not choose
a value under 60 seconds; such a low value can reduce the efficiency of IOS SLB.
Command Examples The following example instructs IOS SLB to maintain connection information for an idle connection for
120 seconds:
idle [asn request duration | asn msid msid | gtp imsi duration [query [ max-queries ]] | gtp request
duration | ipmobile request duration | radius {request | framed-ip} duration]
no idle [asn request duration | asn msid msid | gtp imsi duration [query [ max-queries ]] | gtp
request duration | ipmobile request duration | radius {request | framed-ip} duration]
Syntax Description asn request (Optional) For load balancing across a set of Access
Service Network (ASN) gateways, configures the
duration for which IOS SLB keeps the session
object. If a Mobile Station (MS) Pre-Attachment
Ack is received before the timer expires, IOS SLB
resets the timer.
Usage Guidelines If a client sends a TCP packet that is not a sequence number (SYN) or reset (RST) packet, and IOS SLB
does not have a TCP connection object in its table (possibly due to expiration of the idle timer), IOS SLB
sends a TCP RST to the client.
If you are configuring an idle timer for HTTP flows, choose a low number such as 120 seconds as a starting
point. A low number ensures that the IOS SLB connection database maintains a manageable size if
problems at the server, client, or network result in a large number of connections. However, do not choose
a value under 60 seconds (except in GPRS load balancing); such a low value can reduce the efficiency of
the IOS SLB feature.
In most environments, the idle timer times out data paths. However, in GPRS load balancing, it times out
the session context for signaling paths (not data paths).
In GPRS load balancing without GTP cause code inspection enabled, you must specify an idle timer greater
than the longest possible interval between PDP context requests on the serving GPRS support node
(SGSN). The longest interval can be expressed using the following algorithm:
Longest interval = T3 x 2(N3-2)
where T3 is the SGSNs T3-RESPONSE counter value and N3 is the SGSNs N3-REQUESTS counter
value.
For example, if the T3-RESPONSE counter value is 3 and the N3-REQUESTS counter value is 6, then:
Longest interval = 3 x 2(6-2) = 3 x 2(4) = 3 x 16 = 48 seconds
Given those values, you must specify an idle timer of at least 49 seconds.
Command Examples The following example instructs IOS SLB to maintain sticky objects in the GTP IMSI sticky database for
120 seconds:
inservice
no inservice
Usage Guidelines A DFP agent is inactive until both of the following conditions are met:
The DFP agent has been enabled using the inservice (DFP agent) command.
The client subsystem has changed the DFP agents state to ACTIVE.
When you use the no form of this command to remove a DFP agent from service, the DFP agent closes all
open connections, and no new connections are assigned.
Command Examples In the following example, the DFP agent is enabled for communication with a DFP manager:
Command Default The firewall farm is defined to IOS SLB but is not used.
Usage Guidelines When you use the no form of this command to remove a firewall farm from service, the firewall farm
acquiesces gracefully. No new connections are assigned, and existing connections are allowed to complete.
Command Examples In the following example, the firewall farm is enabled for use by the IOS SLB feature:
Command Default The firewall is defined to IOS SLB but is not used.
Usage Guidelines IOS SLB firewall load balancing uses probes to detect failures. Therefore, if you have not configured a
probe, the firewall is not placed in service.
When you use the no form of this command to remove a firewall from service, the firewall acquiesces
gracefully. No new connections are assigned, and existing connections are allowed to complete.
Command Examples In the following example, the firewall is enabled for use by the IOS SLB feature:
Router(config)# ip slb firewallfarm FIRE1
Router(config-slb-fw)# real 10.10.1.1
Router(config-slb-fw-real)# inservice
inservice
no inservice
Command Default The real server is defined to IOS SLB but is not used.
Command Examples In the following example, the real server is enabled for use by the IOS SLB feature:
Command Default The virtual server is defined to IOS SLB but is not used.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS
Release 12.2(33)SRA.
Usage Guidelines When you use the no form of this command to remove a virtual server from service, the virtual server
acquiesces gracefully. No new connections are assigned, and existing connections are allowed to complete.
If the active keyword is configured, and all of the real servers that are associated with the virtual server are
inactive, the following actions occur:
The virtual server is placed in the INOP_REAL state.
An SNMP trap is generated for the virtual servers state transition.
The virtual server stops answering ICMP requests.
Command Examples In the following example, the virtual server is enabled for use by the IOS SLB feature:
interval seconds
no interval seconds
Command Default The default custom UDP probe interval value is 10 seconds.
Command Examples The following example configures a custom UDP probe named PROBE6, enters custom UDP
configuration mode, and configures the custom UDP probe timer interval to send every 11 seconds:
interval seconds
no interval seconds
Usage Guidelines The DFP agent sends a new weight to the DFP manager only if the new weight is different from the old
weight. If the new weight is the same as the old weight, it is not sent to the DFP manager.
Command Examples The following example shows how to configure the DFP agent to recalculate weights every 11 seconds:
interval seconds
no interval seconds
Command Examples The following example configures a DNS probe named PROBE4, enters DNS configuration mode, and
configures the DNS probe timer interval to send every 11 seconds:
interval seconds
no interval seconds
Command Examples The following example configures an HTTP probe named PROBE2, enters HTTP configuration mode, and
configures the HTTP probe timer interval to send every 11 seconds:
interval seconds
no interval seconds
Command Examples The following example configures a ping probe named PROBE1, enters ping configuration mode, and
configures the ping probe timer interval to send every 11 seconds:
interval seconds
no interval seconds
Command Examples The following example configures a TCP probe named PROBE5, enters TCP configuration mode, and
configures the TCP probe timer interval to send every 11 seconds:
interval seconds
no interval seconds
Command Examples The following example configures a ping probe named PROBE3, enters WSP probe configuration mode,
and configures the WSP probe timer interval to send every 11 seconds:
ip dfp agent
To identify a Dynamic Feedback Protocol (DFP) agent subsystem and enter DFP agent configuration mode,
use the ip dfp agentcommand in global configuration mode. To remove the DFP agent identification, use
the no form of this command.
Syntax Description subsystem-name Character string used to identify the DFP agent
subsystem:
slb for IOS SLB
mobileip for Mobile IP and the Home Agent
Director
The subsystem name enables the subsystem to send
weights to a DFP manager. The subsystem name is
limited to 15 characters.
Usage Guidelines To discover the subsystem names that are available in your network, enter the ip dfp agent ? command.
Command Examples The following example identifies a DFP agent subsystem named slb:
Command Examples The following example enables the KAL-AP agent an enters CAPP UDP configuration mode:
peer port Specifies the port to which the IOS SLB KeepAlive
Application Protocol (KAL-AP) agent is to
connect.
Command Description
peer secret Enables Message Digest Algorithm Version 5
(MD5) authentication for the IOS SLB KeepAlive
Application Protocol (KAL-AP) agent.
ip slb dfp
To configure Dynamic Feedback Protocol (DFP), supply an optional password, and enter DFP
configuration mode, use the ip slb dfp command in global configuration mode. To remove the DFP
configuration, use the no form of this command.
Command Default The default password encryption is 0 (unencrypted). The default password timeout is 180 seconds, if a
password is specified.
Usage Guidelines The password specified in the ip slb dfp command for the DFP manager must match the password
specified in the password command for the DFP agent.
The timeout option allows you to change the password without stopping messages between the DFP agent
and its manager. The default value is 180 seconds.
During the timeout, the agent sends packets with the old password (or null, if there is no old password), and
receives packets with either the old or new password. After the timeout expires, the agent sends and
receives packets only with the new password; received packets that use the old password are discarded.
If you are changing the password for an entire load-balanced environment, set a longer timeout to allow
enough time for you to update the password on all agents and servers before the timeout expires. Setting a
longer timeout also prevents mismatches between agents and servers that have begun running the new
password and agents, and servers on which you have not yet changed the old password.
If you are running IOS SLB as a DFP manager, and you specify a password on the ip slb dfp command, the
password must match the one specified on the password command in DFP agent configuration mode in the
DFP agent.
Command Examples The following example configures DFP, sets the DFP password to Password1 and the timeout to 360
seconds, and enters DFP configuration mode:
ip slb entries
To configure an initial allocation and a maximum value for IOS Server Load Balancing (IOS SLB)
database entries, use the ip slb entriescommand in global configuration mode. To restore the default
values, use the no form of this command.
ip slb entries [conn [init-conn [ max-conn ]] | frag [init-frag [ max-frag ] | lifetime timeout] | gtp
{gsn init-gsn [ max-gsn ] | nsapi init-nsapi [ max-nsapi ]} | sticky [init-sticky [ max-sticky ]]]
no ip slb entries [conn | frag [lifetime] | gtp {gsn | nsapi} | sticky]
Command Default For the connection database, the default initial allocation is 8000 connections, and the default maximum is
8000000 connections. For the fragment database, the default initial allocation is 2000 fragments, and the
default maximum is 8000000 fragments. The default lifetime is 10 seconds. For the GSN database, the
default initial allocation is 200 GSNs, and the default maximum is 20000 GSNs. For the NSAPI database,
the default initial allocation is 8000 NSAPIs, and the default maximum is 8000000 NSAPIs. For the sticky
connection database, the default initial allocation is 4000 sticky connections, and the default maximum is
3200 sticky connections.
Usage Guidelines Enter this command before entering the rest of your IOS SLB configuration. If you have already begun
configuring IOS SLB before entering this command, you must reload ISO SLB after entering this
command.
If you configure an initial allocation value that exceeds the amount of available memory, memory might
not be available for other features. In extreme cases, the router or switch might not boot properly.
Therefore, be careful when you configure initial allocation values.
Command Examples The following example configures an initial allocation of 128,000 connections, which can grow
dynamically to a limit of 512,000 connections:
ip slb firewallfarm
To identify a firewall farm and enter firewall farm configuration mode, use the ip slb
firewallfarmcommand in global configuration mode. To remove the firewall farm from the IOS Server
Load Balancing (IOS SLB) configuration, use the no form of this command.
Syntax Description firewall-farm Character string used to identify the firewall farm.
The character string is limited to 15 characters.
Usage Guidelines Grouping real servers into firewall farms is an essential part of IOS SLB firewall load balancing. Using
firewall farms enables IOS SLB to assign new connections to the real servers based on their weighted
capacities, and on the load-balancing algorithms used.
Command Examples The following example identifies a firewall farm named FIRE1:
ip slb map
To configure an IOS SLB protocol map and enter SLB map configuration mode, use the ip slb
mapcommand in global configuration mode. To delete the map, use the no form of this command.
Syntax Description map-id IOS SLB protocol map identifier. The valid range is
from 1 to 255.
Usage Guidelines You can configure up to 255 IOS SLB GTP or RADIUS maps. However, we recommend that you
configure no more than 10 maps for a given virtual server.
Each map ID must be unique across all server farms associated with a given GTP or RADIUS virtual
server. That is, you cannot configure more than one map with the same ID.
For each IOS SLB RADIUS map, you can configure a single calling-station-id command or a single
username (IOS SLB) command, but not both.
Configure the gtp or radius keyword only on maps that are to be used with GTP or RADIUS virtual
servers, respectively.
Command Examples The following example configures IOS SLB RADIUS map 1 and enters SLB RADIUS map configuration
mode:
Command Examples The following example sets the maximum number of buffers for the IOS SLB fragment buffer to 300:
ip slb natpool
To configure an IOS Server Load Balancing (IOS SLB) Network Address Translation (NAT) to create at
least one client address pool, use the ip slb natpoolcommand in global configuration mode. To remove an
ip slb natpool configuration, use the no form of this command.
ip slb natpool pool start-ip end-ip [netmask netmask | prefix-length leading-1-bits] [entries init-
address [ max-address ]]
no ip slb natpool pool
Syntax Description pool Character string used to identify this client address
pool. The character string is limited to 15
characters.
Command Default The default initial allocation is 8000 client NAT address entries. The default maximum number of client
NAT address entries that can be allocated is the maximum number of ports that can be allocated within the
IP address range.
Usage Guidelines If you want to use client NAT, you must create at least one client address pool.
The range of IP addresses in the address pool, configured with the start-ip and end-ip arguments, must not
overlap the IP address for a VLAN as specified on the ip addressinterface configuration command.
Command Examples The following example configures an IOS SLB NAT server farm pool of addresses with the name web-
clients, the IP address range from 10.1.10.1 to 10.1.10.5, and a subnet mask of 255.255.0.0:
Syntax Description probe Name of the custom UDP probe. The character
string is limited to 15 characters.
Usage Guidelines This command configures the custom UDP probe name and application protocol and enters custom UDP
configuration mode.
The custom UDP probe cannot be unconfigured while it is being used by the server farm or firewall farm.
You can configure more than one probe, in any combination of supported types, for each server farm or for
each firewall in a firewall farm.
Command Examples The following example configures an IOS Server Load Balancing (IOS SLB) probe named PROBE6, then
enters custom UDP probe configuration mode:
Router(config)# ip slb probe PROBE6 custom udp
port (custom UDP probe) Specifies the port to which a custom UDP probe is
to connect.
request (custom UDP probe) Defines the payload of the UDP request packet to
be sent by a custom UDP probe.
Syntax Description probe Name of the DNS probe. The character string is
limited to 15 characters.
Usage Guidelines DNS probes send domain name resolve requests to real servers and verify the returned IP addresses.
This command configures the DNS probe name and application protocol and enters DNS configuration
mode.
The DNS probe cannot be unconfigured while it is being used by the server farm or firewall farm.
You can configure more than one probe, in any combination of supported types, for each server farm or for
each firewall in a firewall farm.
Command Examples The following example configures an IOS Server Load Balancing (IOS SLB) probe named PROBE4, then
enters DNS probe configuration mode:
Syntax Description probe Name of the HTTP probe. The character string is
limited to 15 characters.
Usage Guidelines This command configures the HTTP probe name and application protocol and enters HTTP configuration
mode.
The HTTP probe cannot be unconfigured while it is being used by the server farm or firewall farm.
You can configure more than one probe, in any combination of supported types, for each server farm or for
each firewall in a firewall farm.
Note HTTP probes require a route to the virtual server. The route is not used, but it must exist to enable the
sockets code to verify that the destination can be reached, which in turn is essential for HTTP probes to
function correctly. The route can be either a host route (advertised by the virtual server) or a default route
(specified using the ip route 0.0.0.0 0.0.0.0command, for example).
Command Examples The following example configures an IOS Server Load Balancing (IOS SLB) probe named PROBE2, then
enters HTTP probe configuration mode:
Syntax Description probe Name of the ping probe. The character string is
limited to 15 characters.
Usage Guidelines This command configures the ping probe name and application protocol and enters ping configuration
mode.
The ping probe cannot be unconfigured while it is being used by the server farm or firewall farm.
You can configure more than one probe, in any combination of supported types, for each server farm or for
each firewall in a firewall farm.
Command Examples The following example configures an IOS Server Load Balancing (IOS SLB) probe named PROBE1, then
enters ping probe configuration mode:
Syntax Description probe Name of the TCP probe. The character string is
limited to 15 characters.
Usage Guidelines This command configures the TCP probe name and application protocol and enters TCP configuration
mode.
The TCP probe cannot be unconfigured while it is being used by the server farm or firewall farm.
You can configure more than one probe, in any combination of supported types, for each server farm or for
each firewall in a firewall farm.
Command Examples The following example configures an IOS Server Load Balancing (IOS SLB) probe named PROBE5, then
enters TCP probe configuration mode:
Syntax Description probe Name of the WSP probe. The character string is
limited to 15 characters.
Usage Guidelines This command configures the WSP probe name and application protocol and enters WSP probe
configuration mode.
The WSP probe cannot be unconfigured while it is being used by the server farm or firewall farm.
You can configure more than one probe, in any combination of supported types, for each server farm or for
each firewall in a firewall farm.
Command Examples The following example configures an IOS Server Load Balancing (IOS SLB) probe named PROBE3, then
enters WSP probe configuration mode:
Syntax Description rate Replication message rate for IOS SLB slave
replication, in messages per second. The valid
range is 50 messages per second to 1000 messages
per second. The default setting is 400 messages per
second.
Usage Guidelines This command enables you to manage Interprocess Communication Channel (IPC) resources between two
route processors. If there is congestion between the two route processors, use this command to set a lower
rate.
If the replication rate is exceeded, IOS SLB issues an appropriate error message.
General packet radio service (GPRS) load balancing without GPRS Tunneling Protocol (GTP) cause code
inspection enabled does not support the ip slb replicate slave ratecommand in global configuration mode.
The Home Agent Director does not support the ip slb replicate slave ratecommand in global configuration
mode.
Command Examples The following example sets the replication message rate to 500 messages per second:
replicate interval (firewall farm) Sets the replication delivery interval for an IOS
SLB firewall farm.
ip slb route
To enable IOS Server Load Balancing (IOS SLB) to route packets using the RADIUS framed-IP sticky
database, or to route packets from one firewall real server back through another firewall real server, use the
ip slb routecommand in global configuration mode. To route packets normally, use the no form of this
command.
Syntax Description framed-ip deny (Optional) Packets that do not match entries in the
IOS SLB RADIUS framed-ip sticky database are
not routed.
Command Default Cisco IOS SLB cannot route packets using the RADIUS framed-IP sticky database, nor can it route packets
from one firewall real server back through another firewall real server.
Release Modification
12.2 (14)ZA6 The framed-ip denykeyword was added.
Usage Guidelines This command enables IOS SLB to inspect packets whose source IP addresses match the specified IP
address and subnet mask. IOS SLB then searches for the packets source IP address in the RADIUS
framed-IP sticky database. If the database contains a matching entry, IOS SLB routes the packet to the
associated real server. If the database does not contain a matching entry, IOS SLB routes the packet
normally.
The inter-firewall keyword is useful when traffic is arriving from an address behind a firewall, is destined
for an address behind a firewall, and has a sticky entry to be routed via the routing table.
Command Examples The following example enables IOS SLB to inspect packets with the source IP address 10.10.10.1:
ip slb serverfarm
To identify a server farm and enter SLB server farm configuration mode, use the ip slb serverfarm
command in global configuration mode. To remove the server farm from the IOS Server Load Balancing
(IOS SLB) configuration, use the no form of this command.
Syntax Description server-farm Character string used to identify the server farm.
The character string is limited to 15 characters.
Usage Guidelines Grouping real servers into server farms is an essential part of IOS SLB. Using server farms enables IOS
SLB to assign new connections to the real servers based on their weighted capacities, and on the load-
balancing algorithms used.
Command Examples The following example identifies a server farm named PUBLIC:
ip slb static
To configure a real servers Network Address Translation (NAT) behavior and enter static NAT
configuration mode, use the ip slb staticcommand in global configuration mode. To restore the real
servers default NAT behavior, use the no form of this command.
Syntax Description drop Indicates that IOS Server Load Balancing (IOS
SLB) is to drop packets from this real server if the
packets do not correspond to existing connections.
This option is usually used in conjunction with the
subnet mask or port number option on the real
command in static NAT configuration mode, such
that IOS SLB builds connections to the specified
subnet or port, and drops all other connections from
the real server.
nat virtual Configures the real server to use server NAT, and
to use the virtual IP address that is configured on
the real command in static NAT configuration
mode when translating addresses.
nat virtual-ip Configures the real server to use server NAT, and
to use the specified virtual IP address when
translating addresses.
Command Default If you do not specify either the per-packet or stickykeyword, IOS SLB maintains connection state for
packets originating from the real server.
Usage Guidelines If you specify the virtual-ip argument and you do not specify the per-packet option, IOS SLB uses server
port translation to distinguish between connection requests initiated by different real servers.
Static NAT with the per-packet option specified does not load-balance fragmented packets.
Command Examples The following example specifies that the real server is to use server NAT and to use virtual IP address
10.1.10.1 when translating addresses, and that IOS SLB is not to maintain connection state for any packets
originating from the real server:
Syntax Description duration GSN idle timer duration in seconds, which defines
how long IOS SLB is to allow a GGSN or SGSN to
be idle (that is, to go without echoing or signaling
through IOS SLB). When the timer expires, IOS
SLB cleans up all sessions that are using the idle
GGSN or SGSN.
The valid range is 1 to 65535 seconds. The default
value is 90 seconds.
Usage Guidelines This command sets the GSN idle timer for all IOS SLB virtual servers that are configured for GPRS
Tunneling Protocol (GTP) cause code inspection. When the GSN idle timer expires, IOS SLB destroys all
sessions to and from the idle GGSN or SGSN.
Command Examples The following example specifies that IOS SLB maintains sessions for 45 seconds after a GGSN or SGSN
becomes idle:
ip slb vserver
To identify a virtual server and enter SLB virtual server configuration mode, use the ip slb
vservercommand in global configuration mode. To remove a virtual server from the IOS Server Load
Balancing (IOS SLB) configuration, use the no form of this command.
ip slb vserver virtual-server
no ip slb vserver virtual-server
Syntax Description virtual-server Character string used to identify the virtual server.
The character string is limited to 15 characters.
Command Examples The following example identifies a virtual server named PUBLIC_HTTP:
Router(config)# ip slb vserver PUBLIC_HTTP
Router(config-slb-vserver)#
kal-ap domain
To enable the IOS SLB KeepAlive Application Protocol (KAL-AP) agent to look for a domain tag when
reporting the load for a virtual server, use the kal-ap domaincommand in server farm configuration mode.
To delete the domain tag, use the no form of this command.
Command Default The KAL-AP agent does not look for a domain tag when reporting the load for a virtual server.
Usage Guidelines Configure the kal-ap domain command on the server farm that is associated with the virtual server for
which the KAL-AP agent is to report the load.
Command Examples The following example specifies that the KAL-AP agent is to look for domain tag chicago.com:
Command Description
ip slb serverfarm Identifies a server farm and enter SLB server farm
configuration mode.
L through W
lookup
To configure an IP address of a real server that a Domain Name System (DNS) server should supply in
response to a domain name resolve request, use the lookupcommand in DNS probe configuration mode. To
remove an IP address from the expected list, use the no form of this command.
lookup ip-address
no lookup ip-address
Syntax Description ip-address IP address of a real server that a DNS server should
supply in response to a domain name resolve
request.
Command Examples The following example configures a DNS probe named PROBE4, enters DNS probe configuration mode,
and specifies 10.1.10.1 as the IP address to resolve:
maxclients
To specify the maximum number of IOS Server Load Balancing (IOS SLB) RADIUS and GTP sticky
subscribers that can be assigned to an individual virtual server, use the maxclientscommand in real server
configuration mode. To remove the limit, use the no form of this command.
maxclients maximum-number
no maxclients
Syntax Description maximum-number Maximum number of IOS SLB RADIUS and GTP
sticky subscribers that can be assigned to an
individual virtual server:
If the radius calling-station-idkeyword is
specified in the sticky command for the virtual
server (that is, if the virtual server is
configured to create the IOS SLB RADIUS
calling-station-ID sticky database), a sticky
subscriber is an entry in the IOS SLB RADIUS
calling-station-ID sticky database.
If the radius framed-ipkeyword is specified in
the sticky command for the virtual server (that
is, if the virtual server is configured to create
the IOS SLB RADIUS framed-IP sticky
database), a sticky subscriber is an entry in the
IOS SLB RADIUS framed-IP sticky database.
If the radius usernamekeyword is specified in
the sticky command for the virtual server (that
is, if the virtual server is configured to create
the IOS SLB RADIUS username sticky
database), a sticky subscriber is an entry in the
IOS SLB RADIUS username sticky database.
If both the radius framed-ip and radius
calling-station-idkeywords are specified in the
sticky command for the virtual server, a sticky
subscriber is an entry in the IOS SLB RADIUS
calling-station-ID sticky database.
If both the radius framed-ip and radius
username keywords are specified in the sticky
command for the virtual server, a sticky
subscriber is an entry in the IOS SLB RADIUS
username sticky database.
By default, there is no limit on the number of IOS
SLB RADIUS and GTP sticky subscribers that can
be assigned to an individual virtual server.
Command Default There is no limit on the number of IOS SLB RADIUS and GTP sticky subscribers that can be assigned to
an individual virtual server.
Command Examples The following example specifies that up to 10 IOS SLB RADIUS sticky subscribers can be assigned to an
individual real server:
Router(config-slb-real)# maxclients 10
maxconns maximum-number
no maxconns
Command Default The default maximum number of simultaneous active datagram connections using the firewall farm is
4294967295.
Command Examples The following example limits the real server to a maximum of 1000 simultaneous active connections:
maxconns maximum-number
no maxconns
Command Default The default maximum number of simultaneous active TCP connections using the firewall farm is
4294967295.
Command Examples The following example limits the real server to a maximum of 1000 simultaneous active connections:
Command Default The default maximum number of simultaneous active connections on the real server is 4294967295.
Command Examples The following example limits the real server to a maximum of 1000 simultaneous active connections:
Usage Guidelines This command is supported for Catalyst 6000 family switches only.
Command Examples The following example sets the idle time to 4000 milliseconds:
mls aging slb process Controls how often the aging process runs.
Usage Guidelines This command is supported for Catalyst 6000 family switches only.
Command Examples The following example sets the aging process interval to 4000 milliseconds:
mls aging slb normal Configures the aging time for flows.
Command Examples The following example disables purge throttling on TCP and UDP flow packets:
The following example returns purge throttling on TCP and UDP flow packets to its default setting:
Command Default The default setting is for the PFC to perform IOS SLB wildcard searches.
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS
Release 12.2(18)SXE.
Usage Guidelines This command is supported for Catalyst 6500 family switches only.
If you configure IOS SLB and either input ACLs or firewall load balancing on the same Catalyst 6500
Family Switch, you can exceed the capacity of the TCAM on the PFC. To correct the problem, use the mls
ip slb search wildcard rp command to reduce the amount of TCAM space used by IOS SLB. However, be
aware that this command can result in a slight increase in route processor utilization.
Command Examples The following example limits wildcard searches to the route processor:
nat
To configure Cisco IOS Server Load Balancing (IOS SLB) Network Address Translation (NAT) and
specify a NAT mode, use the nat command in SLB server farm configuration mode. To remove a NAT
configuration, use the no form of this command.
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS
Release 12.2(18)SXE.
Usage Guidelines The no nat command is allowed only if the virtual server was removed from service with the no inservice
command.
Command Examples The following example enters server farm configuration mode and configures NAT mode as server address
translation on server farm FARM2:
The following example configures the NAT mode on server farm FARM2 to client translation mode and,
using the realcommand in server farm configuration mode, configures the real server IP address as
10.3.1.1:
Command Default The password encryption default is 0 (unencrypted). The password timeout default is 180 seconds.
Usage Guidelines The password specified on this command must match the password specified on the DFP manager.
The timeout option allows you to change the password without stopping messages between the DFP agent
and its manager. The default value is 180 seconds.
During the timeout, the agent sends packets with the old password (or null, if there is no old password), and
receives packets with either the old or new password. After the timeout expires, the agent sends and
receives packets only with the new password; received packets that use the old password are discarded.
If you are changing the password for an entire load-balanced environment, set a longer timeout. Setting a
longer timeout allows enough time for you to update the password on all agents and servers before the
timeout expires. It also prevents mismatches between agents and servers that have begun running the new
password and agents, and servers on which you have not yet changed the old password.
If you are running IOS SLB as a DFP manager, and you specify a password on the ip slb dfp command in
global configuration mode, the password must match the one specified on the password command in DFP
agent configuration mode in the DFP agent.
Command Examples The following example sets the DFP agent password (unencrypted by default) to Password1 and the
timeout to 360 seconds:
replicate casa (firewall farm) Configures a stateful backup of IOS SLB decision
tables to a backup switch.
replicate casa (virtual server) Configures a stateful backup of IOS SLB decision
tables to a backup switch.
peer port
To specify the port to which the IOS SLB KeepAlive Application Protocol (KAL-AP) agent is to connect,
use the peer portcommand in SLB Content Application Peering Protocol (CAPP) configuration mode. To
restore the default settings, use the no form of this command.
Command Default If you do not specify a port, the KAL-AP agent connects to port 5002.
Usage Guidelines Use this command to specify a port number, other than port 5002, to be used by the KAL-AP agent.
You can configure any number of peer portcommands with the ip-addressargument, but only one without
the ip-addressargument.
Command Examples The following example configures the KAL-AP agent to connect to port number 6000:
peer secret
To enable Message Digest Algorithm Version 5 (MD5) authentication for the IOS SLB KeepAlive
Application Protocol (KAL-AP) agent, use the peer secretcommand in SLB Content Application Peering
Protocol (CAPP) configuration mode. To disable MD5 authentication, use the no form of this command.
Command Default The KAL-AP agent does not use MD5 authentication with IOS SLB.
Usage Guidelines You can configure any number of peer secretcommands with the ip-addressargument, but only one
without the ip-addressargument.
Command Examples The following example configures secret string SECRET_STRING for the KAL-AP agent:
port port
no port port
Syntax Description port UDP port number to which the custom UDP probe
is to connect.
Command Default In dispatched mode, the port number is inherited from the virtual server. If port translation is configured for
the real server, that port number is used. See the real (server farm) command for more details.
Command Examples The following example configures a custom UDP probe named PROBE6, enters custom UDP probe
configuration mode, and configures the probe to connect to port number 8:
port port-number
no port port-number
Command Examples In the following example, the DFP manager is enabled to connect to the DFP agent using port number
2221:
port port
no port port
Command Default In dispatched mode, the port number is inherited from the virtual server. If port translation is configured for
the real server, that port number is used. See the real(server farm) command for more details.
Command Examples The following example configures an HTTP probe named PROBE2, enters HTTP probe configuration
mode, and configures the probe to connect to port number 8:
port port
no port port
Syntax Description port TCP port number to which the TCP probe is to
connect.
Command Default In dispatched mode, the port number is inherited from the virtual server. If port translation is configured for
the real server, that port number is used. See the real(server farm) command for more details.
Command Examples The following example configures a TCP probe named PROBE5, enters TCP probe configuration mode,
and configures the probe to connect to port number 8:
predictor
To specify the load-balancing algorithm for selecting a real server in the server farm, use the
predictorcommand in SLB server farm configuration mode. To restore the default load-balancing
algorithm of weighted round robin, use the no form of this command.
Syntax Description roundrobin (Optional) Uses the weighted round robin algorithm
for selecting the real server to handle the next new
connection for the server farm. See the Weighted
Round Robin section for a detailed description of
this algorithm. This algorithm is the default value.
RADIUS load balancing requires the weighted
round robin algorithm.
General packet radio service (GPRS) load
balancing without GPRS Tunneling Protocol (GTP)
cause code inspection enabled requires the
weighted round robin algorithm.
The Home Agent Director requires the weighted
round robin algorithm.
Command Default If you do not enter a predictor command, or if you enter the predictor command without specifying a
load-balancing algorithm, the weighted round robin algorithm is used.
Usage Guidelines RADIUS load balancing requires the weighted round robin algorithm.
The route map algorithm is supported only for RADIUS load balancing accelerated data plane forwarding.
When you specify the predictor route-map command, no further commands in SLB server farm
configuration mode or real server configuration mode are allowed.
GPRS load balancing without GTP cause code inspection enabled requires the weighted round robin
algorithm. A server farm that uses weighted least connections can be bound to a virtual server providing
GPRS load balancing without GTP cause code inspection enabled, but you cannot place the virtual server
INSERVICE. If you try to do so, Cisco IOS SLB) issues an error message.
The Home Agent Director requires the weighted round robin algorithm. A server farm that uses weighted
least connections can be bound to a Home Agent Director virtual server, but you cannot place the virtual
server INSERVICE. If you try to do so, Cisco IOS SLB issues an error message.
Command Examples The following example specifies the weighted least connections algorithm:
weight (server farm) Specifies the real servers capacity, relative to other
real servers in the server farm.
Syntax Description port (Optional) Uses the source and destination TCP or
User Datagram Protocol (UDP) port numbers, in
addition to the source and destination IP addresses,
when selecting a firewall.
Command Default IOS Server Load Balancing (IOS SLB) uses the source and destination IP addresses when selecting a
firewall.
Command Examples The following example specifies that source and destination IP addresses are to be used when selecting a
firewall:
weight (firewall farm real server) Specifies the firewalls capacity, relative to other
firewalls in the firewall farm.
probe probe
no probe probe
Syntax Description probe Name of the probe to associate with this firewall
farm.
Usage Guidelines You can configure more than one probe for each firewall in a firewall farm.
If you configure probes in your network, you must also do one of the following:
Configure the exclude keyword on the client command on the virtual server, to exclude connections
initiated by the client IP address from the load-balancing scheme.
Configure IP addresses on the IOS Server Load Balancing (IOS SLB) device that are Layer 3-adjacent
to the real servers used by the virtual server.
Command Examples The following example associates probe FireProbe with server farm FIRE1:
probe probe
no probe probe
Syntax Description probe Name of the probe to associate with this server
farm.
Usage Guidelines You can configure more than one probe for each server farm.
If you configure probes in your network, you must also do one of the following:
Configure the exclude keyword on the client command on the virtual server, to exclude connections
initiated by the client IP address from the load-balancing scheme.
Configure IP addresses on the IOS Server Load Balancing (IOS SLB) device that are Layer 3-adjacent
to the real servers used by the virtual server.
Command Examples The following example associates probe PROBE1 with server farm PUBLIC:
protocol datagram
To enter firewall farm datagram protocol configuration mode, use the protocol datagramcommand in
firewall farm configuration mode.
protocol datagram
Usage Guidelines Firewall farm datagram protocol configuration applies to the Encapsulation Security Payload (ESP),
Generic Routing Encapsulation (GRE), IP in IP encapsulation, and User Datagram Protocol (UDP)
protocols.
Command Examples The following example enters firewall farm datagram protocol configuration mode:
protocol tcp
To enter firewall farm TCP protocol configuration mode, use the protocol tcpcommand in firewall farm
configuration mode.
protocol tcp
Command Default Firewall farm TCP protocol configuration mode is not entered.
Command Examples The following example enters firewall farm TCP protocol configuration mode:
purge connection
To enable IOS SLB firewall load balancing to send purge requests for connections, use the purge
connectioncommand in firewall farm configuration mode. To prevent the sending of purge requests, use
the no form of this command.
purge connection
no purge connection
Command Default IOS SLB firewall load balancing sends purge requests for connections.
Usage Guidelines By default, IOS SLB firewall load balancing sends purge requests for connections. However, if a large
number of purge requests are sent, the CPU might be impacted. To prevent this problem, use the no form of
this command to prevent the sending of purge requests.
Command Examples The following example prevents the sending of purge requests for connections:
Related Commands mls ip slb purge global Specifies protocol-level purging of MLS entries
from active TCP and UDP flow packets.
Command Default IOS SLB purges entries in the IOS SLB RADIUS framed-ip sticky database upon receipt of an Accounting
ON or OFF message.
Command Examples The following example prevents IOS SLB from purging entries in the IOS SLB RADIUS framed-ip sticky
database upon receipt of an Accounting ON or OFF message:
Command Default IOS SLB purges entries in the IOS SLB RADIUS framed-ip sticky database upon receipt of an
Accounting-Stop message.
Command Examples The following example prevents IOS SLB from purging entries in the IOS SLB RADIUS framed-ip sticky
database upon receipt of an Accounting-Stop message:
purge sticky
To enable IOS SLB firewall load balancing to send purge requests for sticky connections when the sticky
timer expires, use the purge stickycommand in firewall farm configuration mode. To prevent the sending
of purge requests when the timer expires, use the no form of this command.
purge sticky
no purge sticky
Command Default IOS SLB firewall load balancing sends purge requests when the sticky timer expires.
Usage Guidelines By default, IOS SLB firewall load balancing sends purge requests for sticky connections when the sticky
timer expires. However, large volumes of purge requests can impact the CPU. To prevent this problem, use
the no form of this command to prevent the sending of purge requests when the sticky timer expires.
To configure a sticky timer for IOS SLB firewall load balancing, use the sticky command in either firewall
farm datagram protocol or firewall farm TCP protocol configuration mode.
Command Examples The following example prevents the sending of purge requests for sticky connections:
Related Commands mls ip slb purge global Specifies protocol-level purging of MLS entries
from active TCP and UDP flow packets.
sticky (firewall farm datagram protocol) Assigns all connections from a client to the same
firewall.
sticky (firewall farm TCP protocol) Assigns all connections from a client to the same
firewall.
Command Default By default, this command is not enabled. When this command is enabled, the RADIUS load balancing
device, not the real server, acknowledges RADIUS accounting messages. If you configure this command
but you do not specify the 7 keyword, the secret-string is stored in the plain text.
Command Examples The following example shows how to enable RADIUS virtual server PUBLIC_RADIUS to acknowledge
RADIUS accounting messages with key SECRET_PASSWORD.
Syntax Description group-number VSA correlation group number to be used for VSA
correlation in the RADIUS Accounting-Start
packets.
Usage Guidelines This command is valid only for VSA correlation accounting virtual servers.
Command Examples The following example configures VSA correlation group 1 and configures plain text secret string
SECRET_STRING for VSA correlation:
radius inject auth vsa Buffers vendor-specific attributes (VSAs) for VSA
correlation for an IOS SLB RADIUS load
balancing accelerated data plane forwarding
authentication virtual server.
Usage Guidelines For a given authentication virtual server, you can configure a single radius inject auth group-number
calling-station-id command or a single radius inject auth group-number usernamecommand, but not
both.
This command is valid only for VSA correlation authentication virtual servers.
Command Examples The following example configures VSA correlation group 1 and specifies that IOS SLB is to create VSA
correlation entries based on the RADIUS calling station ID attribute:
radius inject auth vsa Buffers vendor-specific attributes (VSAs) for VSA
correlation for an IOS SLB RADIUS load
balancing accelerated data plane forwarding
authentication virtual server.
Syntax Description seconds Time, in seconds, that IOS SLB maintains an entry
in the VSA correlation database. Valid range is 1 to
255.
Command Default No VSA correlation timer is configured for the authentication virtual server.
Usage Guidelines This command is valid only for VSA correlation authentication virtual servers.
Command Examples The following example configures a VSA correlation timer of 45 seconds:
Command Description
Digest Algorithm Version 5 (MD5) authentication
for VSA correlation.
radius inject auth vsa Buffers vendor-specific attributes (VSAs) for VSA
correlation for an IOS SLB RADIUS load
balancing accelerated data plane forwarding
authentication virtual server.
Usage Guidelines This command is valid only for VSA correlation authentication virtual servers.
Command Description
radius inject auth Configures a vendor-specific attribute (VSA)
correlation group for an IOS SLB RADIUS load
balancing accelerated data plane forwarding
authentication virtual server, and specifies whether
IOS SLB is to create VSA correlation entries based
on RADIUS calling station IDs or RADIUS
usernames.
rate
To specify the maximum number of connections allowed for a real server in a server farm, use the
ratecommand in real server configuration mode. To remove the rate limit, use the no form of this
command.
Command Default There is no limit on the number of connection allowed for the real server. If you do not configure a burst
rate, the default burst rate is (maximum-rate/10) connections per second.
Usage Guidelines The rate command is valid only for real servers in server farms. It is not valid for real servers in firewall
farms.
If the rate limit for a real server is exceeded, and a new connection request is received, IOS SLB assigns the
new connection request to the next rate-configured real server in the server farms queue. If no other rate-
configured real server is available in the server farm, IOS SLB drops the connection request.
The rate limit also applies to sticky connections. That is, if the rate limit for a real server is exceeded, and a
new sticky connection request is received, IOS SLB drops the sticky connection request.
IOS SLB uses slow start even if a real server has a rate limit configured.
Command Examples The following example specifies that up to 100 connections per second are allowed for the real server in a
server farm, with a burst rate of 25 burst connections per second:
real ip-address
no real ip-address
Usage Guidelines A firewall farm comprises a number of firewalls. The firewalls are the physical devices that provide the
firewall load-balanced services.
Command Examples The following example identifies a firewall as a member of firewall farm FIRE1:
Usage Guidelines A server farm comprises a number of real servers. The real servers are the physical devices that provide the
load-balanced services.
In general packet radio service (GPRS) load balancing, this command identifies a gateway GPRS support
node (GGSN) that is a member of the server farm. Also, remember that the Cisco GGSN IP addresses are
virtual template IP addresses, not real interface IP addresses.
IOS SLB supports GPRS Tunneling Protocol (GTP) v0, v1, and v2 real servers. A GTP v2 real server can
be either a Packet Data Network Gateway (PGW) or a serving gateway (SGW).
A GTP v2 PGW can also manage GTP v0 and v1 requests.
A GTP v2 SGW cannot manage GTP v0 or v1 requests.
A GTP v0 or v1 real server cannot manage GTP v2 requests. Therefore, you must configure separate
virtual servers for GTPv2 real servers and GTP v0 or v1 real servers.
IOS SLB supports dual-stack addresses for GTP load balancing only. To support dual-stack addresses, you
must configure the real server as a dual-stack real server, with the IPv4 and IPv6 addresses, using this
command.
In Virtual Private Network (VPN) server load balancing, this command identifies a real server acting as a
VPN terminator.
Command Examples The following example identifies a real server as a member of the server farm:
The following example identifies a dual-stack real server as a member of the server farm:
Syntax Description ip-address IP address of the real server that is to use static
NAT.
Usage Guidelines If no port number is specified, IOS SLB uses static NAT for all packets outbound from the real server.
Command Examples The following example configures real server 10.1.1.3 to use static NAT:
reassign
To specify the threshold of consecutive unacknowledged SYNchronize sequence numbers (SYNs) or
Create Packet Data Protocol (PDP) requests that, if exceeded, result in an attempted connection to a
different real server, use the reassign command in SLB real server configuration mode. To restore the
default reassignment threshold, use the no form of this command.
reassign threshold
no reassign
Release Modification
12.1(5)T This command was integrated into Cisco IOS
Release 12.1(5)T.
Usage Guidelines This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine
2.
IOS SLB does not reassign sticky connections if either of the following conditions is true:
The real server is not OPERATIONAL or MAXCONNS_THROTTLED.
The connection is the first for this sticky connection.
In GPRS load balancing, this command specifies the number of consecutive unacknowledged Create PDP
requests (not TCP SYNs) that are directed to a gateway GPRS support node (GGSN) before the connection
is reassigned to a different GGSN. You must specify a reassign threshold less than the N3-REQUESTS
counter value of the serving GRPS support node (SGSN).
Command Examples The following example shows how to set the threshold of unacknowledged SYNs to 2:
Command Description
inservice (real server) Enables the real server for use by the IOS SLB
feature.
replicate casa listen-ip remote-ip port [ interval ] [password [ encrypt ] secret-string [ timeout ]]
no replicate casa listen-ip remote-ip port
Command Default The default interval is 10 seconds. The default password encryption is 0 (unencrypted). The default
password timeout is 180 seconds.
Usage Guidelines The timeout option allows you to change the password without stopping messages between the backup and
primary Layer 3 switches. The default value is 180 seconds.
During the timeout, the backup sends packets with the old password (or null, if there is no old password),
and receives packets with either the old or new password. After the timeout expires, the backup sends and
receives packets only with the new password.
When setting a new password timeout, remember the following considerations:
If you are configuring a new backup, set the timeout to 0 (send packets with the new password
immediately). This configuration prevents password mismatches between the new backup and its
primary.
If you are changing the password for an existing backup, set a longer timeout to allow enough time for
you to update the password on the primary before the timeout expires. Setting a longer timeout also
prevents mismatches between the backup and primary.
If you configure this command but you do not specify the 7 keyword, the secret-string is stored in the plain
text.
Command Examples The following example configures a stateful backup Layer-3 switch with a listening IP address of
10.10.10.11 and a remote IP address of 10.10.11.12 over HTTP port 4231:
replicate casa listen-ip remote-ip port [ interval ] [password [ encrypt ] secret-string [ timeout ]]
no replicate casa listen-ip remote-ip port
Command Default The default interval is 10 seconds. The default password encryption is 0 (unencrypted). The default
password timeout is 180 seconds.
Usage Guidelines The timeout option allows you to change the password without stopping messages between the backup and
primary Layer 3 switches. The default value is 180 seconds.
During the timeout, the backup sends packets with the old password (or null, if there is no old password),
and receives packets with either the old or new password. After the timeout expires, the backup sends and
receives packets only with the new password.
When setting a new password timeout, remember the following considerations:
If you are configuring a new backup, set the timeout to 0 (send packets with the new password
immediately). This configuration prevents password mismatches between the new backup and its
primary.
If you are changing the password for an existing backup, set a longer timeout to allow enough time for
you to update the password on the primary before the timeout expires. Setting a longer timeout also
prevents mismatches between the backup and primary.
General packet radio service (GPRS) load balancing without GPRS Tunneling Protocol (GTP) cause code
inspection enabled does not support the replicate casacommand in virtual server configuration mode.
The Home Agent Director does not support the replicate casacommand in virtual server configuration
mode.
If you configure this command but you do not specify the 7 keyword, the secret-string is stored in the plain
text.
Command Examples The following example configures a stateful backup Layer-3 switch with a listening IP address of
10.10.10.11 and a remote IP address of 10.10.11.12 over HTTP port 4231:
Usage Guidelines General packet radio service (GPRS) load balancing without GPRS Tunneling Protocol (GTP) cause code
inspection enabled does not support the replicate intervalcommand in firewall farm configuration mode.
The Home Agent Director does not support the replicate intervalcommand in firewall farm configuration
mode.
replicate casa (firewall farm) Configures a stateful backup of IOS Server Load
Balancing (IOS SLB) decision tables to a backup
switch
Usage Guidelines General packet radio service (GPRS) load balancing without GPRS Tunneling Protocol (GTP) cause code
inspection enabled does not support the replicate intervalcommand in virtual server configuration mode.
The Home Agent Director does not support the replicate intervalcommand in virtual server configuration
mode.
replicate casa (virtual server) Configures a stateful backup of IOS Server Load
Balancing (IOS SLB) decision tables to a backup
switch
replicate slave
no replicate slave
Usage Guidelines General packet radio service (GPRS) load balancing without GPRS Tunneling Protocol (GTP) cause code
inspection enabled does not support the replicate slavecommand in firewall farm configuration mode.
The Home Agent Director does not support the replicate slavecommand in firewall farm configuration
mode.
Command Examples The following example enables stateful backup of redundant route processors:
replicate casa (firewall farm) Configures a stateful backup of IOS SLB decision
tables to a backup switch
replicate interval (firewall farm) Sets the replication delivery interval for an IOS
SLB firewall farm.
replicate slave
no replicate slave
Usage Guidelines General packet radio service (GPRS) load balancing without GPRS Tunneling Protocol (GTP) cause code
inspection enabled does not support the replicate slavecommand in virtual server configuration mode.
The Home Agent Director does not support the replicate slavecommand in virtual server configuration
mode.
If you are using a single Supervisor with replicate slave configured, you might receive out-of-sync
messages on the Supervisor.
Command Examples The following example enables stateful backup of redundant route processors:
replicate casa (virtual server) Configures a stateful backup of IOS SLB decision
tables to a backup switch
replicate interval (virtual server) Sets the replication delivery interval for an IOS
SLB virtual server.
Syntax Description data start-byte Identifies the payload offset at which the hex-data-
stringis to be placed into the packet.
Command Default The payload of the UDP request packet is not defined.
Usage Guidelines You can enter more than one request command, to specify the entire UDP payload.
Command Examples The following example generates custom UDP probe PROBE6, with the specified 119-byte UDP payload.
Syntax Description method (Optional) Configures the way the data is requested
from the server.
Command Default No HTTP probe is configured to check the status of the real servers.
Usage Guidelines The request command configures the Cisco IOS Server Load Balancing (Cisco IOS SLB) HTTP probe
method used to receive data from the server. Only one Cisco IOS SLB HTTP probe can be configured for
each server farm.
If no values are configured following the method keyword, the default is Get.
If no URL path is set to the server, the default is /.
Command Examples The following example configures an IOS SLB HTTP probe named PROBE2, enters HTTP probe
configuration mode, and configures HTTP requests to use the post method and the URL /probe.cgi?all:
response
To define the data string to match against custom User Datagram Protocol (UDP) probe response packets,
use the responsecommand in custom UDP probe configuration mode.
data start-byte Byte in the UDP response packet at which the hex-
data-stringis to be matched.
Command Default The data string to match against custom UDP probe response packets is not defined.
Usage Guidelines You can enter up to 8 individual response commands, to parse up to 8 non-contiguous bytes of data.
Command Examples In the following example, if the 26th and 27th bytes of the response from PROBE6 are not FF FF , and the
44th and 45th bytes are not DD DD , the probe fails.
request (custom UDP probe) Defines the payload of the UDP request packet to
be sent by a custom UDP probe.
retry retry-value
no retry
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS
Release 12.2(18)SXE.
Command Examples The following example specifies that 120 seconds must elapse after the detection of a server failure before
a new connection is attempted:
serverfarm
To associate an IPv4 server farm with a virtual server, and optionally configure an IPv4 backup server
farm, an IPv6 server farm and backup server farm, and specify that sticky connections are to be used in the
IPv4 backup server farm, use the serverfarm command in SLB virtual server configuration mode. To
remove the server farm association from the virtual server configuration, use the no form of this command.
Syntax Description primary-farm Name of a primary server farm that has already
been defined using the ip slb serverfarmcommand.
For IPv4 or dual-stack, name of the IPv4
server farm.
For IPv6, name of the IPv6 server farm.
Command Default No real server farm is associated with a virtual server. If backup backup-farm is not specified, no IPv4
backup server farm is configured. If backup backup-farm is specified but the sticky keyword is not
specified, sticky connections are not used in the IPv4 backup server farm. If ipv6-primary ipv6-primary-
farm is not specified, no dual-stack backup server farm is configured. If ipv6-backup ipv6-backup-farm is
not specified, no dual-stack backup server farm is configured.
Release Modification
15.0(1)S The ipv6-primaryand ipv6-backupkeywords and
the ipv6-primary-farmand ipv6-backup-farm
arguments were added.
Usage Guidelines RADIUS load balancing and the Home Agent Director do not support the sticky keyword.
You can associate more than one server farm with a given virtual server by configuring more than one
serverfarm command, each with a unique map ID and a unique priority. (That is, each map ID and each
map priority must be unique across all server farms associated with the virtual server.)
For GPRS load balancing, if a real server is defined in two or more server farms, each server farm must be
associated with a different virtual server.
IOS SLB supports dual-stack addresses for GTP load balancing only.
All IPv4 or IPv6 server farms that are associated with the same virtual server must have the same NAT
configuration.
If you associate a primary server farm with a backup server farm, then all of the server farm maps that use
that primary server farm must also be configured to use that same backup serverfarm. You cannot configure
a server farm map that uses that primary server farm and no backup server farm.
For example, if you configure primary server farm SF1 with backup server farm SF2, then all of the
server farm maps that are configured with SF1 as the primary serverfarm must also be configured with
SF2 as the backup serverfarm, as follows:
Furthermore, if you configure primary server farm SF1 with backup server farm SF2, you cannot then
configure a server farm map to use SF1 as the primary server farm with no backup server farm. That
is, the following is not allowed:
The backup server farm associated with an IOS SLB protocol map cannot be associated as a backup
server farm with any other map in a given virtual server.
Command Examples The following example shows how the ip slb vserver, virtual, and serverfarm commands are used to
associate the real server farm named PUBLIC with the virtual server named PUBLIC_HTTP.
Command Examples The following sample output from the show fm slb counterscommand shows counter information for
virtual server 10.11.11.11:
Field Description
Global Purges Number of global purges sent by FM IOS SLB.
show ip dfp
To display information about Dynamic Feedback Protocol (DFP) agents and their subsystems, use the show
ip dfp command inprivilegedEXEC mode.
Syntax Description agent subsystem-name (Optional) Displays information about the specified
DFP agent, such as slbfor IOS SLB.
Command Default If no options are specified, the command displays output for all DFP agents identified by ip dfp
agentcommands, regardless of whether those agents are currently in service (Inservice: yes) or active
(AppActive: yes).
Usage Guidelines Detailed output for the show ip dfp command includes information about all DFP agents configured with
ip slb agent commands, regardless of whether those agents are currently in service.
Command Examples The following example shows basic information for DFP agent slb:
The following example shows detailed information for DFP agent slb:
Field Description
Port TCP port number of the agent.
Field Description
Manager IP Address IP address of the manager to which weights are
being sent.
Weights for Port Port for which the following weights are reported. 0
indicates a wildcard value.
Bind IDs for Port Port for which the following bind IDs are reported.
show ip slb conns [vserver virtual-server | client ip-address | firewall firewall-farm] [detail]
Syntax Description vserver virtual-server (Optional) Displays only those connections (or
sessions, in GPRS load balancing and the Home
Agent Director) associated with the specified
virtual server.
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS
Release 12.2(18)SXE.
Usage Guidelines If no options are specified, the command displays output for all active IOS SLB connections (or sessions, in
GPRS load balancing and the Home Agent Director).
Command Examples The following is sample output from the show ip slb conns command:
Field Description
vserver Name of the virtual server associated with the
connection (or session, in GPRS load balancing and
the Home Agent Director).
Field Description
show ip slb dfp [agent agent-ip port | manager manager-ip | detail | weights]
Command Default If no options are specified, the command displays summary information.
Release Modification
12.2(18)SXE This command was integrated into Cisco IOS
Release 12.2(18)SXE.
Usage Guidelines If no options are specified, the command displays summary information.
Command Examples The following sample output from the show ip slb dfp command displays high-level information about all
DFP agents and managers:
Field Description
DFP Manager Indicates that the following information applies to
the DFP manager.
Field Description
Interval Interval, in seconds, between retries.
The following example displays detailed information about DFP agents and managers:
Field Description
DFP Manager Indicates that the following information applies to
the DFP manager.
No DFP Agents configured Indicates that there are no DFP agents associated
with the DFP manager.
The following example displays detailed information about DFP manager 10.0.0.0:
Field Description
DFP Manager Indicates that the following information applies to
the DFP manager.
Field Description
Timeout Time period, in seconds, during which the DFP
manager must receive an update from the DFP
agent. A value of 0 means there is no timeout.
Last message sent Date and time of the last message sent by the DFP
manager.
The following example displays detailed information about weights assigned to real servers for load
balancing:
Field Description
Real IP Address IP address of the real server for which weight is
reported.
Set by Agent Agent that set the weight, and the date and time the
weight was set.
Command Examples The following is sample output from the show ip slb firewallfarmcommand:
Field Description
firewall farm Name of the firewall farm.
Field Description
Command Examples The following sample output from the show ip slb fragmentscommand shows fragment information for
virtual server 10.11.11.11:
Field Description
ip src Source IP address of the fragment.
Field Description
forward IP address to which the fragment is being
forwarded.
Command Default If you specify gsn and you do not specify a gsn-ip-address, IOS SLB displays information for all GGSNs
and SGSNs. If you specify nsapi and you do not specify an nsapi-key, IOS SLB displays information for
all NSAPIs.
Command Examples The following is sample output from the show ip slb gtp gsncommand for a specific GGSN or SGSN:
Field Description
type Type of GSN (either GGSN or SGSN).
The following is sample output from the show ip slb gtp nsapicommand:
The following is sample output from the show ip slb gtp nsapicommand for a specific NSAPI key:
Field Description
nsapi key Key for the session. This is the IMSI.
The following is sample output from the show ip slb gtp nsapi detailcommand:
Field Description
IMSI key IMSI key for the session.
no NSAPI number.
Usage Guidelines If no ID is specified, the command displays information about all maps.
Command Examples The following is sample output from the show ip slb mapcommand:
Field Description
ID Identifier of the map about which information is
being displayed. Information about each map is
displayed on a separate line.
Field Description
Service Protocol associated with the map. Valid protocols
are:
GTP--For general packet radio service (GPRS)
Tunneling Protocol (GTP) maps
RADIUS--For RADIUS load balancing maps
SGSN access list Serving GPRS Support Node (SGSN) access list
associated with the GTP map.
Syntax Description name pool (Optional) Displays the specified NAT pool.
Command Examples The following is sample output from the default show ip slb natpoolcommand:
Field Description
Start NAT Starting NAT address in a range of addresses in the
client NAT pool.
Syntax Description name probe (Optional) Displays information about the specified
probe.
Command Examples The following is sample output from the show ip slb probecommand:
Field Description
Server:Port IP address and port of the real server.
Current Time since the last probe success. That is, the
duration (so far) of the current outage.
Cumulative Total time the real server has been under test by the
probe and has failed the probe test. This value is the
sum of the Current time plus the total time of all
previous outages.
Syntax Description sfarm server-farm (Optional) Displays information about those real
servers associated with the specified server farm or
firewall farm.
12.2(33)SRC The output for the detail keyword for a real server
in a server farm was updated to display the
configured maximum number of connections
allowed (rate).
Release Modification
15.0(1)S The output for the detail keyword for a real server
in a server farm was updated to display the real
server's IPv4, IPv6, or dual-stack address.
Usage Guidelines If no options are specified, the command displays information about all real servers.
In a configuration with stateful backup, if a probe changes state at the same time that the primary IOS SLB
device fails over to the backup IOS SLB device, the output from the show ip slb reals command for the
backup device displays the state of the probe before the failover, not the actual current state.
Command Examples The following is sample output from the show ip slb realscommand:
Field Description
real IP address of the real server about which
information is being displayed. Used to identify
each real server. Information about each real server
is displayed on a separate line.
Field Description
Field Description
conns Number of connections associated with the real
server.
In general packet radio service (GPRS) load
balancing, number of sessions associated with the
real server.
In per-packet server load balancing, number of
request packets that have been load balanced to
each real server, using the connection count.
The following is sample output from the show ip slb reals detailcommand for a dual-stack real server in a
server farm:
The following is sample output from the show ip slb reals detailcommand for a real server in a firewall
farm:
The table below describes the fields shown in the above detail displays.
Field Description
IPv4 or IPv6 address IPv4 or IPv6 address of the real server about which
information is being displayed. Used to identify
each real server. Information about each real server
is displayed on a separate line.
Field Description
Field Description
conns Number of connections associated with the real
server.
In general packet radio service (GPRS) load
balancing, number of sessions associated with the
real server.
In per-packet server load balancing, number of
request packets that have been load balanced to
each real server, using the connection count.
Field Description
failclient count Total number of unique client connection failures
since the last time the clear ip slb
counterscommand was issued.
server failures Total number of times this real server has been
marked failed.
hash count Total number of times the hash algorithm has been
called.
Command Examples The following is sample output from the show ip slb replicatecommand:
Field Description
state Current replication state of the virtual server:
DUMPING--Dumping the connection table to
the Hot Standby Router Protocol (HSRP) peer
device.
NORMAL--Functioning properly.
PREEMPTING--Preparing to preempt the
HSRP peer device and assume an active role.
Command Examples The following is sample output from the show ip slb serverfarmscommand:
Field Description
server farm Name of the server farm about which information is
being displayed. Information about each server
farm is displayed on a separate line.
The following is sample output from the show ip slb serverfarms detailcommand, if RADIUS load
balancing is configured with the route map predictor:
show ip slb sessions [asn | gtp [ipv6] | gtp-inspect | ipmobile | radius] [vserver virtual-server]
[client ipv4-address ipv4-netmask] [detail]
Release Modification
12.2(14)S This command was integrated into Cisco IOS
Release 12.2(14)S.
Command Examples The following is sample output from the show ip slb sessionscommand for RADIUS sessions:
Field Description
Source Addr/Port Source IPv4 address and port number for the
session.
Dest Addr/Port Destination IPv4 address and port number for the
session.
----------------------------------------------------------------------------------
10.10.10.10 1234567890123456 10.5.5.5 10.10.1.1 GTP_ESTAB
Field Description
vserver Name of the virtual server whose GTP sessions are
being monitored and displayed. Information about
each session is displayed on a separate line.
Field Description
vserver Name of the virtual server whose Mobile IP
sessions are being monitored and displayed.
Field Description
Information about each session is displayed on a
separate line.
The following is sample output from the show ip slb sessions asncommand for ASN sessions:
Field Description
vserver Name of the virtual server whose ASN sessions are
being monitored and displayed. Information about
each session is displayed on a separate line.
Base Station IPv4 address of the base station associated with the
ASN session.
Field Description
Command Default The default behavior is to display the entire IOS SLB server NAT configuration.
Command Examples The following is sample output from the show ip slb staticcommand:
Field Description
real IP address of the real server.
Field Description
action Action to be taken by the real server:
drop--The real server is configured to have its
packets dropped by IOS SLB, if the packets do
not correspond to existing connections.
NAT--The real server is configured to use
server NAT, and to use its own virtual IP
address when translating addresses.
NAT per-packet--The real server is configured
to use server NAT and per-packet server load
balancing.
NAT sticky--The real server is configured to
use server NAT for sticky connections.
pass-thru--The real server is not configured to
use server NAT.
Syntax Description kal-ap (Optional) Displays information about the IOS SLB
KeepAlive Application Protocol (KAL-AP) agent.
12.2(33)SRC The kal-ap keyword was added, and the output for
the command was updated to display correlation
inject failures for RADIUS load balancing
accelerated data plane forwarding.
Release Modification
12.2(33)SRC1 The output for the command was updated to display
packet fragment drops for Access Service Network
(ASN) R6 load balancing.
Command Examples The following is sample output from the show ip slb statscommand:
Field Description
Pkts via normal switching Number of packets handled by IOS SLB via normal
switching since the last time counters were cleared.
Normal switching is when IOS SLB packets are
handled on normal IOS switching paths (CEF, fast
switching, and process level switching).
Pkts via special switching Number of packets handled by IOS SLB via special
switching since the last time counters were cleared.
Special switching is when IOS SLB packets are
handled on hardware-assisted switching paths.
Pkts via slb routing Number of packets handled by IOS SLB via SLB
routing since the last time counters were cleared.
Field Description
Field Description
zombie connection becomes a real connection and
the zombie count is decremented.
Connection Flowcache Purges Number of times the connection flow cache was
purged since the last time counters were cleared.
RADIUS framed-ip Sticky Count Number of entries in the RADIUS framed-IP sticky
database.
RADIUS username Sticky Count Number of entries in the RADIUS username sticky
database.
GTP imsi Sticky Count Number of entries in the GTP IMSI sticky database.
Pkt fragments drops in ssv Number of packet fragments drops in the SSV.
ASN MSID sticky count Number of sticky objects in the ASN MSID sticky
database.
The following is sample output from the show ip slb kal-ap stats kal-apcommand:
show ip slb sticky [asn {msid msid | nai nai} | client ipv4-address ipv4-netmask | gtp imsi [ipv6]
[id imsi] | radius calling-station-id [id string] | radius framed-ip [client ipv4-address ipv4-
netmask] | radius username [name string]]
Syntax Description asn msid msid (Optional) Displays only those sticky database
entries associated with the specified Access Service
Network (ASN) Mobile Station ID (MSID).
Command Default If no options are specified, the command displays information about all virtual servers.
Command Examples The following is sample output from the show ip slb stickycommand:
Field Description
client Client IPv4 address or subnet which is bound to this
sticky assignment.
The following is sample output from the show ip slb sticky gtp imsicommand:
Field Description
IMSI IMSI bound to this sticky assignment in the IOS
SLB GTP IMSI sticky database.
The following is sample output from the show ip slb sticky gtp imsi ipv6command:
The following is sample output from the show ip slb sticky radius calling-station-idcommand:
Field Description
calling-station-id Calling station ID bound to an SSG RADIUS proxy
in the IOS SLB RADIUS calling-station-ID sticky
database.
The following is sample output from the show ip slb sticky radius framed-ipcommand:
Field Description
framed-ip IPv4 address bound to a Cisco Service Selection
Gateway (SSG) RADIUS proxy in the IOS SLB
RADIUS framed-IP sticky database.
The following is sample output from the show ip slb sticky radius usernamecommand:
Field Description
username Username bound to an SSG RADIUS proxy in the
IOS SLB RADIUS username sticky database.
The following is sample output from the show ip slb sticky asncommand:
Field Description
MSID MSID bound to this sticky assignment in the IOS
SLB ASN sticky database.
The following is sample output from the show ip slb sticky asn nai [email protected]:
Table 32: show ip slb sticky asn nai [email protected] Field Descriptions
Field Description
MSID MSID bound to this sticky assignment in the IOS
SLB ASN sticky database.
Syntax Description name virtual-server (Optional) Displays information about the specified
virtual server.
Release Modification
12.2(33)SRC1 The output for the detail keyword was updated to
display information about Access Service Network
(ASN) virtual servers.
Usage Guidelines If no options are specified, the command displays information about all virtual servers.
Command Examples The following is sample output from the show ip slb vserverscommand:
Field Description
slb vserver Name of the virtual server about which information
is being displayed. Information about each virtual
server is displayed on a separate line.
Field Description
conns Number of connections (or sessions, in general
packet radio service [GPRS] load balancing and the
Home Agent Director) associated with the virtual
server.
The following sample output from the show ip slb vservers detailcommand shows detailed data for a
virtual server with route health injection (advertise=TRUE):
The following sample output from the show ip slb vservers name detailcommand shows detailed data for
virtual server GGSN_SERVER with GTP sticky query enabled:
Field Description
GGSN_SERVER Name of the virtual server about which information
is being displayed (in this case, GGSN_SERVER).
Field Description
OPERATIONAL--Functioning properly.
OUTOFSERVICE--Removed from the load-
balancing predictor lists.
STANDBY--Backup virtual server, ready to
become operational if active virtual server fails.
server farm Name of the server farm associated with the virtual
server.
gtp sticky query For GTP IMSI sticky, indicates whether IOS SLB
is to query the GGSN before deleting any GTP
IMSI sticky objects.
Field Description
sticky group id Sticky group in which this virtual server is placed,
for coupling of services.
The following sample output from the show ip slb vservers name detailcommand shows detailed data for
GTP virtual server GGSN_SERVER with maps enabled:
Field Description
GGSN_SERVER Name of the RADIUS virtual server about which
information is being displayed (in this case,
GGSN_SERVER).
Field Description
FAILED--Real server represented by this virtual
server has been removed from use by the predictor
algorithms; retry timer started.
OPERATIONAL--Functioning properly.
OUTOFSERVICE--Removed from the load-
balancing predictor lists.
STANDBY--Backup virtual server, ready to
become operational if active virtual server fails.
serverfarm maps List of IOS SLB server farm maps associated with
this virtual server. Information about each map is
displayed on a separate line.
server farm Name of the server farm associated with the virtual
server. Information about each server farm is
displayed on a separate line.
Field Description
gtp request idle GTP idle connection timer duration in seconds.
gtp sticky query For GTP IMSI sticky, indicates whether IOS SLB
is to query the GGSN before deleting any GTP
IMSI sticky objects.
The following sample output from the show ip slb vservers name detailcommand shows detailed data for
an ASN virtual server:
Field Description
ASN_VSERVER Name of the ASN virtual server about which
information is being displayed (in this case,
ASN_VSERVER).
server farm Name of the server farm associated with the virtual
server. Information about each server farm is
displayed on a separate line.
Field Description
delay Delay timer duration, in seconds, for this virtual
server.
Command Examples The following is sample output from the show ip slb wildcardcommand:
Syntax Description real Enables traps for real server state changes.
Command Default IOS SLB traps for real- and virtual-server state changes are not enabled.
Command Examples The following example enables IOS SLB traps for real server state changes:
Command Default Virtual servers are not associated with any groups.
Command Examples The following example specifies that if a clients subsequent request for a firewall farm is made within 60
seconds of the previous request, then the same firewall is used for the connection:
show ip slb sticky Displays information about the IOS SLB database.
Command Default Virtual servers are not associated with any groups.
Command Examples The following example specifies that if a clients subsequent request for a firewall farm is made within 60
seconds of the previous request, then the same firewall is used for the connection:
show ip slb sticky Displays information about the IOS SLB database.
sticky {duration [group group-id] [netmask netmask] | asn msid [group group-id] | | gtp | imsi |
[group group-id] | | radius | calling-station-id | | radius | framed-ip | [group group-id] | | radius |
username | [msid-cisco ] | [group group-id]}
no sticky {duration [group group-id] [netmask netmask] | asn msid [group group-id] | | gtp | imsi |
[group group-id] | | radius | calling-station-id | | radius | framed-ip | [group group-id] | | radius |
username | [msid-cisco ] | [group group-id]}
radius calling-station-id Enables IOS SLB to create the IOS SLB RADIUS
calling-station-ID sticky database and direct
RADIUS requests from a given calling station ID to
the same service gateway.
radius username Enables IOS SLB to create the IOS SLB RADIUS
username sticky database and direct RADIUS
requests from a given end user to the same service
gateway.
Command Default Sticky connections are not tracked. Virtual servers are not associated with any groups.
Usage Guidelines The last real server that was used for a connection from a client is stored for the set duration seconds. If a
new connection from the client to the virtual server is initiated during that time, the same real server that
was used for the previous connection is chosen for the new connection. If two virtual servers are placed in
the same group, coincident connection requests for those services from the same IP address are handled by
the same real server.
In Virtual Private Network (VPN) server load balancing, remember the following requirements:
For IPsec flows, you must specify a sticky connection between the User Datagram Protocol (UDP)
virtual server and the Encapsulation Security Payload (ESP) virtual server.
For PPTP flows, you must specify a sticky connection between the TCP virtual server and the Generic
Routing Encapsulation (GRE) virtual server.
You must specify a duration of at least 15 seconds.
In general packet radio service (GPRS) load balancing and the Home Agent Director, the stickycommand
is not supported.
In RADIUS load balancing, remember the following requirements:
If you configure the sticky radius framed-ipcommand, you must also configure the virtual command
with the service radiuskeywords specified.
If you configure the sticky radius calling-station-idcommand or the sticky radius
usernamecommand, you must also configure the virtual command with the service radiuskeywords
specified, and you must configure the sticky radius framed-ipcommand.
You cannot configure both the sticky radius calling-station-id command and the sticky radius
username command on the same virtual server.
If you configure the sticky radius calling-station-idcommand, you must configure all RADIUS maps
to match against the RADIUS calling station ID attribute.
If you configure the sticky radius usernamecommand, you must configure all RADIUS maps to
match against the RADIUS username attribute.
For GTP load balancing:
IOS SLB creates a sticky database object when it processes the first GTP PDP create request for a
given IMSI. IOS SLB removes the sticky object when it receives a notification to do so from the real
server, or as a result of inactivity. When the last PDP belonging to an IMSI is deleted on the GGSN, it
sends a notification to IOS SLB to remove the sticky object.
If you configure the sticky gtp imsi command, you must also configure the virtual command with the
service gtpkeywords specified.
For ASN load balancing, if you configure the sticky asn msid command, you must also configure the
virtual command with the service asnkeywords specified.
Command Examples The following example specifies that if a clients subsequent request for a virtual server is made within 60
seconds of the previous request, then the same real server is used for the connection. This example also
places the virtual server in group 10.
Command Default The default number of unacknowledged SYNs that are allowed to be outstanding to a virtual server is 0
(off). The default interval is 100 ms.
Usage Guidelines In general packet radio service (GPRS) load balancing and the Home Agent Director, the synguard
command has no meaning and is not supported.
Command Examples The following example sets the threshold of unacknowledged SYNs to 50:
timeout seconds
no timeout
Syntax Description seconds Time, in seconds, that IOS SLB waits for a
response packet from the server after sending a
custom UDP probe request packet. Valid range is 1
to 255. The default value is 30 seconds.
Command Examples In the following example the custom UDP probe timeout is set to 20 seconds:
url [ path ]
no url [ path ]
Syntax Description path (Optional) Path from the server. This argument is
case-sensitive.
Command Examples The following example configures a ping probe named PROBE3, enters WSP probe configuration mode,
and configures the probe to request URL path http://localhost/test.txt:
username string
no username string
Usage Guidelines For a given IOS SLB RADIUS map, you can configure a single calling-station-id command or a single
username (IOS SLB)command, but not both.
Command Examples The following example specifies that, for IOS SLB RADIUS map 1, string ...?525* is to be matched
against the username attribute in the RADIUS payload:
virtual
To configure virtual server attributes, use the virtual command in SLB virtual server configuration mode.
To remove the attributes, use the no form of this command.
Encapsulation Security Payload (ESP) and Generic Routing Encapsulation (GRE) Protocols
virtual ipv4-address [ipv4-netmask [group]] {esp | gre | protocol}
no virtual ipv4-address [ipv4-netmask [group]] {esp | gre | protocol}
Syntax Description ipv4-address IPv4 address for this virtual server instance, used
by clients to connect to the IPv4 real servers
through the IPv4 server farm.
Release Modification
The wsp, wsp-wtp, wsp-wtls, and wsp-wtp-wtls
keywords were changed to options for the
portargument.
Usage Guidelines The no virtual command is allowed only if the virtual server was removed from service by the no
inservice command.
For some applications, it is not feasible to configure all the virtual server TCP or UDP port numbers for
IOS SLB. To support such applications, you can configure IOS SLB virtual servers to accept flows
destined for all ports. To configure an all-port virtual server, specify a port number of 0 or any.
Note In general, you should use port-bound virtual servers instead of all-port virtual servers. When you use all-
port virtual servers, flows can be passed to servers for which no application port exists. When servers reject
these flows, IOS SLB might fail the server and remove it from load balancing.
Specifying port 9201 for connection-oriented WSP mode also activates the Wireless Application Protocol
(WAP) finite state machine (FSM), which monitors WSP and drives the session FSM accordingly.
In RADIUS load balancing, IOS SLB maintains session objects in a database to ensure that re-sent
RADIUS requests are load-balanced to the same real server.
IOS SLB supports general packet radio service (GPRS) Tunneling Protocol (GTP) v0, v1, and v2 real
servers. A GTP v0 or v1 real server cannot manage GTP v2 requests. Therefore, you must configure
separate virtual servers for GTPv2 real servers and for GTP v0 or v1 real servers.
IOS SLB supports dual-stack addresses for GTP load balancing only. To support dual-stack addresses:
You must configure the virtual server as a dual-stack virtual server, with the virtual IPv4 and IPv6
addresses and the optional IPv6 prefix, using this command.
You must associate an IPv6 server farm with the dual-stack virtual server.
Command Examples The following example specifies that the virtual server with the IPv4 address 10.0.0.1 performs load
balancing for TCP connections for the port named www. The virtual server processes HTTP requests.
The following example specifies that the virtual server with the IPv4 address 10.0.0.13 performs load
balancing for UDP connections for all ports. The virtual server processes HTTP requests.
weight setting
no weight
Syntax Description setting Weight setting to use for the real server predictor
algorithm. Valid settings range from 1 to 255. The
default weight setting is 8.
Command Default The default setting to use for the real server predictor algorithm is 8.
Command Examples The following example specifies the relative weights of three real servers as 16, 8 (by default), and 24,
respectively:
Syntax Description setting Weight setting to use for the real server predictor
algorithm. Valid settings range from 1 to 255. The
default weight setting is 8.
Command Default The default setting to use for the real server predictor algorithm is 8.
Usage Guidelines The static weights you define using this command are overridden by the weights calculated by Dynamic
Feedback Protocol (DFP). If DFP is removed from the network, IOS Server Load Balancing (IOS SLB)
reverts to these static weights.
Command Examples The following example specifies the relative weights of three real servers as 16, 8 (by default), and 24,
respectively: