-
Cisco GSS Command Reference (Software Version 3.0)
-
CLI Command Summary by Mode
-
Preface
-
Using the Command-Line Interface
-
Cisco Global Site Selector CLI Commands
-
Global Configuration Mode Commands
-
DDoS Module Configuration Mode Commands
-
DRP Agent Configuration Mode Commands
-
Interface Configuration Mode Commands
-
Global Server Load-Balancing Configuration Mode Commands
-
Proximity Properties Configuration Mode Commands
-
Rule Configuration Mode Commands
-
Sticky Properties Configuration Mode Commands
-
Feedback
Table Of Contents
Global Server Load-Balancing Configuration Mode Commands
(config-gslb-ansvip) keepalive type http-head
(config-gslb-ansvip) keepalive type icmp
(config-gslb-ansvip) keepalive type kalap
(config-gslb-ansvip) keepalive type scripted-kal
(config-gslb-ansvip) keepalive type tcp
(config-gslb-agcra) answer-add
(config-gslb-agvip) answer-add
(config-gslb-agns) auth-domain
(config-gslb) keepalive-properties cra
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties kalap
(config-gslb) keepalive-properties scripted-kal
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties tcp
(config-gslb) manual-reactivation
(config-gslb) proximity assign
(config-gslb) proximity-properties
(config-gslb) script play-config
(config-gslb) shared-keepalive http-head
(config-gslb) shared-keepalive icmp
(config-gslb) shared-keepalive kalap
(config-gslb) shared-keepalive scripted-kal
(config-gslb) shared-keepalive tcp
(config-gslb) source-address-list
(config-gslb) sticky-properties
Global Server Load-Balancing Configuration Mode Commands
This section describes the commands in global server load-balancing configuration mode. Global server load-balancing configuration mode allows you to configure server load balancing for your GSS network. Using the CLI at the primary GSSM, you configure source addresses and domain names, identify your network resources (GSSs) through the use of keepalives, and create the Domain Name System (DNS) rules to process incoming content requests.
To access the global server load-balancing configuration mode, use the gslb command in global configuration mode. The CLI prompt changes to (config-gslb) as follows:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)#In global configuration mode, you can also use the gslb command with a keyword to perform its corresponding global server load-balancing function. For example, use the gslb command with the location keyword to enter location parameters. After the command is executed, you remain in global configuration mode as follows:
gssm1.example.com(config)# gslb locations SAN_FRANCISCO region WESTERN_USA comments "UNION SQUARE"gssm1.example.com(config)#gslb [answer {cra | ns | vip} | answer-group | dns rule | domain-list | keepalive-properties {cra | http-head | icmp | kalap | scripted-kal | ns | tcp} | location | manual reactivation {activate-MR-answers all | activate-MR-clauses all | enable} | owner | proximity {assign | group} | proximity-properties | region | script | shared-keepalive {http-head | icmp | kalap | scripted-kal | tcp} | show | source-address-list | sticky group | sticky-properties | zone]
Syntax Description
answer cra
See the (config-gslb) answer cra command for a detailed syntax description.
answer ns
See the (config-gslb) answer ns command for a detailed syntax description.
answer vip
See the (config-gslb) answer vip command for a detailed syntax description.
answer-group
See the (config-gslb) answer-group command for a detailed syntax description.
dns rule
See the (config-gslb) dns rule command for a detailed syntax description.
domain-list
See the (config-gslb) domain-list command for a detailed syntax description.
keepalive-properties cra
See the (config-gslb) keepalive-properties cra command for a detailed syntax description.
keepalive-properties http-head
See the (config-gslb) keepalive-properties http-head command for a detailed syntax description.
keepalive-properties icmp
See the (config-gslb) keepalive-properties icmp command for a detailed syntax description.
keepalive-properties kalap
See the (config-gslb) keepalive-properties kalap command for a detailed syntax description.
keepalive-properties scripted-kal
See the (config-gslb) keepalive-properties scripted-kal command for a detailed syntax description.
keepalive-properties ns
See the (config-gslb) keepalive-properties ns command for a detailed syntax description.
keepalive-properties tcp
See the (config-gslb) keepalive-properties tcp command for a detailed syntax description.
location
See the (config-gslb) location command for a detailed syntax description.
manual reactivation
See the (config-gslb) manual-reactivation command for a detailed syntax description.
owner
See the (config-gslb) owner command for a detailed syntax description.
proximity assign
See the (config-gslb) proximity assign command for a detailed syntax description.
proximity group
See the (config-gslb) proximity group command for a detailed syntax description.
proximity-properties
See the (config-gslb) proximity-properties command for a detailed syntax description.
region
See the (config-gslb) region command for a detailed syntax description.
script play-config
See the (config-gslb) script play-config command for a detailed syntax description.
shared-keepalive http-head
See the (config-gslb) shared-keepalive http-head command for a detailed syntax description.
shared-keepalive icmp
See the (config-gslb) shared-keepalive icmp command for a detailed syntax description.
shared-keepalive kalap
See the (config-gslb) shared-keepalive kalap command for a detailed syntax description.
shared-keepalive scripted-kal
See the (config-gslb) shared-keepalive scripted-kal command for a detailed syntax description.
shared-keepalive tcp
See the (config-gslb) shared-keepalive scripted-kal command for a detailed syntax description.
show
See the show gslb-config, show gslb-errors, show proximity, show running-config, and show sticky commands in the "General Commands" section for detailed syntax descriptions.
source-address-list
See the (config-gslb) source-address-list command for a detailed syntax description.
sticky group
See the (config-gslb) sticky group command for a detailed syntax description.
sticky-properties
See the (config-gslb) sticky-properties command for a detailed syntax description.
zone
See the (config-gslb) zone command for a detailed syntax description.
(config-gslb) answer cra
To configure a content routing agent (CRA)-type answer, use the answer cra ip_address command in global server load-balancing configuration mode. To delete a CRA-type answer, use the no form of this command.
answer cra ip_address [activate | delay number | disable | enable | location name | manual-reactivation {disable | enable} | name name | suspend]
no answer cra ip_address [activate | delay number | disable | enable | location name | manual-reactivation enable | name name | suspend]
Syntax Description
ip_address
Interface or circuit address of the CRA. Enter an unquoted text string in dotted decimal format (for example, 192.168.10.1).
activate
(Optional) Reactivates a suspended CRA answer. This is the default setting.
delay number
(Optional) Specifies a one-way delay time in milliseconds. The GSS uses this value to calculate a static RTT with the one-way delay constituting one-half of the round-trip time that is used for all Domain Name System (DNS) races involving this answer. Valid entries are 0-1000 milliseconds. The default is 0.
disable
(Optional) Specifies that the GSS uses the one-way delay variable to calculate a static RTT. See the delay keyword for more information about static RTT.
enable
(Optional) Specifies that the GSS performs keepalive checks on the answer. This is the default setting. Use disable if you plan to specify a one-way delay to calculate a static round-trip time (RTT). See the delay option for information about static RTT.
location name
(Optional) Specifies an existing location name with which the answer is to be associated.
manual-reactivation
Determines whether the GSS reactivates the answer automatically when its state changes from offline to online or if you must manually reactivate the answer.
Use one of the following keywords with this option:
•
enable—Enables the manual reactivation function. The GSS suspends the answer if it goes offline and changes its status to "operational suspend." The answer remains suspended until you reactivate it.
Note
•
name name
(Optional) Specifies a name for the CRA-type answer. Enter a unique alphanumeric name, with a maximum of 80 characters. Names with spaces must be entered in quotes (for example, "name 1").
suspend
(Optional) Suspends an active CRA answer.
Command Modes
Global server load-balancing configuration
Examples
The following example shows how to create a CRA-type answer with a one-way delay:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# answer cra 10.86.209.22 name CRA-ANS1 delay 3gssm1.example.com(config-gslb)The following example shows how to delete a CRA-type answer:
gssm1.example.com(config-gslb)# no answer cra 10.86.209.22 name CRA-ANS1 delay 3gssm1.example.com(config-gslb)Related Commands
(config-gslb) manual-reactivation
(config-gslb) answer ns
To configure a name server (NS)-type answer, use the answer ns ip_address command in global server load-balancing configuration mode. To delete an NS-type answer, use the no form of this command.
answer ns ip_address [activate | disable | domain name | enable | location name | manual-reactivation {enable | disable} | name name | suspend]
no answer ns ip_address [activate | disable | domain name | enable | location name | manual-reactivation enable | name name | suspend]
Syntax Description
ip_address
Name server that the GSS is to forward its requests. Enter an unquoted text string in dotted decimal format (for example, 192.168.10.1).
activate
(Optional) Reactivates a suspended NS answer. This is the default setting.
disable
(Optional) Specifies that the GSS disables keepalive checks on the specified name server. The GSS assumes that the name server is always online.
domain name
(Optional) Specifies the name of the domain name server to which an NS-type keepalive is sent (to determine the online status). Enter the name as an unquoted text string with no spaces and a maximum length of 100 characters (for example, www.home.com).
enable
(Optional) Specifies that the GSS performs keepalive checks on the specified name server. The GSS queries the name server IP address to determine the online status. This is the default.
location name
(Optional) Specifies an existing location name with which the answer is to be associated.
manual-reactivation
Determines whether the GSS reactivates the answer automatically when its state changes from offline to online or if you must manually reactivate the answer.
Use one of the following keywords with this option:
•
Note
•
name name
(Optional) Specifies a name for the NS-type answer. Enter a unique alphanumeric name, with a maximum of 80 characters. Names with spaces must be entered in quotes (for example, "name 1").
suspend
(Optional) Suspends an active NS answer.
Command Modes
Global server load-balancing configuration
Usage Guidelines
If no domain is specified, the GSS queries the globally configured query domain. For instructions about configuring the global query domain, see Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide.
Examples
The following example shows how to create an NS-type answer that specifies a domain name server:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# answer ns 10.86.209.4 domain WWW.HOME.COM enablegssm1.example.com(config-gslb)The following example shows how to delete an NS-type answer:
gssm1.example.com(config-gslb)# no answer ns 10.86.209.4 domain WWW.HOME.COM enablegssm1.example.com(config-gslb)Related Commands
(config-gslb) manual-reactivation
(config-gslb) answer vip
To configure a virtual IP (VIP)-type answer, use the answer vip ip_address command in global server load-balancing configuration mode. To delete a VIP-type answer, use the no form of this command.
answer vip ip_address [activate | location name | manual-reactivation {enable | disable} | name name | suspend]
no answer vip ip_address [activate | location name | manual-reactivation enable | name name | suspend]
Syntax Description
ip_address
VIP address field to which the GSS will forward requests. Enter an unquoted text string in A.B.C.D format.
activate
(Optional) Reactivates a suspended VIP answer. This is the default setting.
location name
(Optional) Specifies an existing location name with which the answer is to be associated.
manual-reactivation
Determines whether the GSS reactivates the answer automatically when its state changes from offline to online or if you must manually reactivate the answer.
Use one of the following keywords with this option:
•
Note
•
name name
(Optional) Specifies a name for the VIP-type answer that you are creating. Enter a unique alphanumeric name with a maximum of 80 characters. Names that include spaces must be entered in quotes (for example, "name 1").
suspend
(Optional) Suspends an active VIP answer.
Command Modes
Global server load-balancing configuration
Usage Guidelines
After you enter the answer vip ip_address command, the prompt changes to the answer vip configuration mode where you can optionally specify and configure keepalives for your VIP-type answer by using the keepalive type command.
Examples
The following example shows how to create a VIP answer called SEC-LONDON1 and associate it with the London location:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# answer vip 10.86.209.232 name SEC-LONDON1 location LONDONgssm1.example.com(config-ansvip[ans-ip])The following example shows how to delete a VIP answer:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no answer vip 10.86.209.232 name SEC-LONDON1 location LONDONgssm1.example.com(config-gslb)Related Commands
(config-gslb) manual-reactivation
(config-gslb-ansvip) keepalive type http-head
(config-gslb-ansvip) keepalive type icmp
(config-gslb-ansvip) keepalive type kalap
(config-gslb-ansvip) keepalive type scripted-kal
(config-gslb-ansvip) keepalive type tcp
(config-gslb-ansvip) keepalive type http-head
To define an HTTP HEAD keepalive for your virtual IP (VIP) answer, use the keepalive type http-head command. To reset keepalive properties to their default values, use the no form of this command.
keepalive type http-head [host-tag domain_name | path path | port number | retries number | shared ip_address | successful-probes number | termination {graceful | reset}]
no keepalive type http-head [host-tag domain_name | path path | port number | retries number | shared ip_address | successful-probes number | termination {graceful | reset}]
Syntax Description
Command Modes
Answer vip configuration mode
Usage Guidelines
This command sends a TCP-format HTTP HEAD request to an origin web server at the address specified for the VIP answer.
The GSS determines the online status of the device in the form of an HTTP Response Status Code of 200 (for example, HTTP/1.0 200 OK) from the server and information about the web page status and content size.
Examples
The following example shows how to configure an HTTP HEAD keepalive for the VIP-type answer servicing VIP address 192.168.200.1:
gssm1.example.com(config-gslb)# answer vip 192.168.200.1gssm1.example.com(config-ansvip[ans-ip])# keepalive type http-head host-tag WWW.HOME.COM termination gracefulgssm1.example.com(config-ansvip[ans-ip])#Related Commands
(config-gslb-ansvip) keepalive type icmp
To define an Internet Control Message Protocol (ICMP) keepalive for your virtual IP (VIP) answer, use the keepalive type icmp command in answer vip configuration mode. To reset keepalive properties to their default values, use the no form of this command.
keepalive type icmp [shared ip_address | retries number | successful-probes number]
no keepalive type icmp [shared ip_address | retries number | successful-probes number]
Syntax Description
Command Modes
Answer vip configuration mode
Usage Guidelines
This command sends an ICMP echo message (ping) to the address specified for the VIP answer. The GSS determines the online status by the response received from the device, indicating connectivity to the network.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
Examples
The following example shows how to configure an ICMP keepalive for the VIP-type answer servicing VIP address 10.86.209.232:
gssm1.example.com(config-gslb)# answer vip 10.86.209.232gssm1.example.com(config-ansvip[ans-ip])# keepalive type icmp retries 2gssm1.example.com(config-ansvip[ans-ip])Related Commands
(config-gslb-ansvip) keepalive type kalap
To define a KAL-AP keepalive for your virtual IP (VIP) answer, use the keepalive type kalap command in answer vip configuration mode. To reset keepalive properties to their default values, use the no form of this command.
keepalive type kalap {tag ip_address {tag_name} | vip ip_address}}
no keepalive type kalap {tag ip_address {tag_name} | vip ip_address}}
Syntax Description
Command Modes
Answer vip configuration mode
Usage Guidelines
This command sends a detailed query to the Cisco Content Services Switch (CSS) or Cisco Content Switching Module (CSM) at the address specified for the VIP answer to extract load and availability. The GSS determines the online status when the server load balancers (SLBs) respond with information about a hosted domain name, host VIP address, or a configured tag on a content rule.
The tag name value is used to match the correct shared keepalive VIP, avoiding confusion that can be caused when probing for the status of a VIP that is located behind a firewall network address translation (NAT).
Examples
The following example shows how to configure a KAL-AP keepalive for the VIP-type answer servicing VIP address 192.168.200.1:
gssm1.example.com(config-gslb)# answer vip 192.168.200.1gssm1.example.com(config-ansvip[ans-ip])# keepalive type kalap tag 192.168.50.41 TAG1gssm1.example.com(config-ansvip[ans-ip])Related Commands
(config-gslb-ansvip) keepalive type scripted-kal
To define Scripted Kal keepalives for your virtual IP (VIP) answer, use the keepalive type scripted-kal command in answer vip configuration mode. To reset keepalive properties to their default values, use the no form of this command.
keepalive type scripted-kal kal-name name max-load max-load value match-string string [use-load {enable | disable}]
no keepalive type scripted-kal kal-name name max-load max-load value
Syntax Description
Command Modes
Answer vip configuration mode
Usage Guidelines
This command allows you to specify a KAL name and maximum load in order to add a Scripted Kal probe to the VIP. The GSS determines the online status by the response received from the device, indicating connectivity to the network.
Examples
The following example shows how to configure a Scripted keepalive for the VIP-type answer servicing VIP address 192.168.200.1:
gssm1.example.com(config-gslb)# answer vip 192.168.200.1gssm1.example.com(config-ansvip[ans-ip])# keepalive type scripted-kal kal-name samplekal max-load 50gssm1.example.com(config-ansvip[ans-ip])Related Commands
(config-gslb-ansvip) keepalive type tcp
To define a TCP keepalive for your VIP answer, use the keepalive type tcp command in answer vip configuration mode. To reset keepalive properties to their default values, use the no form of this command.
keepalive type tcp [shared ip_address | port number | retries number | successful-probes number | termination {graceful | reset}]
no keepalive type tcp [shared ip_address | port number | retries number | successful-probes number | termination {graceful | reset}]
Syntax Description
Command Modes
Answer vip configuration mode
Usage Guidelines
This command sends a TCP handshake to the address specified for the VIP answer and port number of the remote device to determine service viability (three-way handshake and connection termination method), returning the online status of the device.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
Examples
The following example shows how to configure a TCP keepalive for the VIP-type answer that services VIP address 192.168.200.1:
gssm1.example.com(config-gslb)# answer vip 192.168.200.1gssm1.example.com(config-ansvip[ans-ip])# keepalive type tcp port 23 successful-probes 4gssm1.example.com(config-ansvip[ans-ip])Related Commands
(config-gslb) answer-group
To create an answer group, use the answer-group command in global server load-balancing configuration mode. To delete an answer group, use the no form of this command.
answer-group name {owner name type {cra | ns |vip}}
no answer-group name {owner name type {cra | ns |vip}}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
Answer groups are lists of GSS resources that are candidates to respond to Domain Name System (DNS) queries received from a user for a hosted domain. By using the DNS rules feature, you associate these lists of network resources with a particular balance method that is used to resolve the request.
After you enter the answer-group command to configure a CRA, NS, or virtual IP (VIP) answer group, the prompt changes to the corresponding answer group configuration mode (for example, "config-gslb-agvip[ag-name]" for a VIP-type answer group). In this mode, you add previously configured answers to the group by using the answer-add command. See the answer-add command in the CRA, NS, and VIP answer group configuration mode descriptions that follow.
Examples
The following example shows how to create a VIP answer group:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# answer-group ANSGRPVIP1 owner WEB-SERVICES type vipgssm1.example.com(config-gslb-agvip[ag-name)#The following example shows how to delete a VIP answer group:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no answer-group ANSGRPVIP1 owner WEB-SERVICES type vipgssm1.example.com(config-gslb)#Related Commands
(config-gslb-agvip) answer-add
(config-gslb-agcra) answer-add
(config-gslb-agcra) answer-add
After you create a content routing agent (CRA)-type answer group using the answer-group command, to add previously configured CRA-type answers to the group, use the answer-add command in the CRA answer group configuration mode. To delete an answer from an answer group, use the no form of this command.
answer-add ip_address [activate | name | suspend]
no answer-add ip_address [activate | name | suspend]
Syntax Description
Command Modes
CRA answer group configuration mode
Examples
The following example shows how to add answers to and configure a CRA answer group:
gssm1.example.com(config-gslb-agcra[ag-name])# answer-add 192.168.10.1 name www-boston-1gssm1.example.com(config-gslb-agcra[ag-name])# answer-add 192.172.24.1 name www-ny-1gssm1.example.com(config-gslb-agcra[ag-name])# answer-add 192.186.14.1 name www-atlanta-1gssm1.example.com(config-gslb-agcra[ag-name])#The following example shows how to delete an answer from a CRA answer group:
gssm1.example.com(config-gslb-agcra[ag-name])# no answer-add 192.186.14.1 name www-atlanta-1Related Commands
(config-gslb-agvip) answer-add
(config-gslb-agns) answer-add
After you create a name server (NS)-type answer group using the answer-group command, to add previously configured NS-type answers to the group, use the answer-add command in the NS answer group configuration mode. To delete an answer from an answer group, use the no form of this command.
answer-add ip_address [name | order number | weight number | activate | suspend]
no answer-add ip_address [name | order number | weight number | activate | suspend]
Syntax Description
Command Modes
NS answer group configuration mode
Usage Guidelines
For more information about the order and weight settings, see Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide.
Examples
The following example shows how to add answers to and configure an NS answer group:
gssm1.example.com(config-gslb-agns[ag-name])# answer-add 192.168.10.1 name www-zurich-1 order 10gssm1.example.com(config-gslb-agns[ag-name])# answer-add 192.172.20.1 name www-barcelona-1 order 20gssm1.example.com(config-gslb-agns[ag-name])# answer-add 192.188.30.1 name www-brussels-30gssm1.example.com(config-gslb-agns[ag-name])#The following example shows how to delete an answer from an NS answer group:
gssm1.example.com(config-gslb-agns[ag-name)# no answer-add 192.168.10.1 name www-zurich-1 order 10Related Commands
(config-gslb-agvip) answer-add
(config-gslb-agcra) answer-add
(config-gslb-agvip) answer-add
After you create a virtual IP (VIP)-type answer group using the answer-group command, to add previously configured VIP-type answers to the group, use the answer-add command in the VIP answer group configuration mode. To delete an answer from an answer group, use the no form of this command.
answer-add ip_address [name | load-threshold number | order number | weight number | activate | suspend]
no answer-add ip_address [name | load-threshold number | order number | weight number | activate | suspend]
Syntax Description
Command Modes
VIP answer group configuration mode
Usage Guidelines
For more information about the order, weight, and load threshold settings, see Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide.
Examples
The following example shows how to add answers to and configure a VIP answer group:
gssm1.example.com(config-gslb-agvip[ag-name])# answer-add 192.168.30.1 name www-hk-1 weight 1gssm1.example.com(config-gslb-agvip[ag-name])# answer-add 192.174.20.1 name www-sf-1 weight 2gssm1.example.com(config-gslb-agvip[ag-name])# answer-add 192.188.40.1 name www-london-1 weight 4gssm1.example.com(config-gslb-agvip[ag-name])#The following example shows how to delete an answer from a VIP answer group:
gssm1.example.com(config-gslb-agvip[ag-name])# no answer-add 192.168.30.1 name www-hk-1 weight 1Related Commands
(config-gslb-agcra) answer-add
(config-gslb-agns) auth-domain
To add an authority domain to an answer group, use the auth-domain command. To delete an authority domain from an answer group, use the no form of this command.
auth-domain domain-name
no auth-domain domain-name
Syntax Description
domain_name
Answer group domain name that you want to add or delete.
Note
Command Modes
Answer group configuration
Usage Guidelines
For more information about adding or deleting an authority domain, see Chapter 6, Configuring and Modifying Answer Groups in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide.
Examples
The following example shows how to configure an answer group and add an NS answer and its associated authority domains:
gssm1.example.com (config-gslb)# answer-group ag1 owner System type nsgssm1.example.com (config-gslb-agns)# answer-add 1.2.3.4 name ns1gssm1.example.com (config-gslb-agns)# auth-domain soa.testgssm1.example.com (config-gslb-agns)# auth-domain soa.orgThe following example shows how to delete associated authority domains:
gssm1.example.com(config-gslb-agns)# no auth-domain soa.testgssm1.example.com(config-gslb-agns)# no auth-domain soa.orgRelated Commands
(config-gslb) dns rule
To build, activate, or suspend the Domain Name System (DNS) rules that specify the actions that each GSS is to perform when it receives a request from a known source for a known hosted domain, use the dns rule command in global server load-balancing configuration mode. To delete a DNS rule, use the no form of this command.
dns rule name {activate | owner name | source-address-list name | domain-list name | query {a | all} | suspend}
no dns rule name {owner name | source-address-list name | domain-list name | query {a | all}}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
After you enter the dns rule name command, the prompt changes to the rule configuration mode where you specify and configure load-balance clauses and optional DNS sticky and network proximity settings by using the clause command. See the rule configuration mode commands in the Rule Configuration Mode Commands section.
The following guidelines apply to use of the query command:
•
•
•
Examples
The following example shows how to create a DNS rule called drule02:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# dns rule drule02 owner WEB-SERVICES source-address-list WEB-GLOBAL-LISTS domain-list E-COMMERCE query Agssm1.example.com(config-gslb-rule[rule-name])#The following example shows how to delete a DNS rule called drule02:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no dns rule drule02 owner WEB-SERVICES source-address-list WEB-GLOBAL-LISTS domain-list E-COMMERCE query ARelated Commands
(config-gslb-rule) clause number cra-group
(config-gslb-rule) clause number ns-group
(config-gslb-rule) clause number vip-group
(config-gslb) domain-list
To configure a domain list, use the domain-list command in global server load-balancing configuration mode. To delete a domain list, use the no form of this command.
domain-list name [comments text | owner name]
no domain-list name [comments text | owner name]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
After you enter the domain-list command, the prompt changes to the domain list configuration mode, where you specify domains to be added to the domain list using the domain command.
Examples
The following example shows how to create a domain list called E-COMMERCE:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# domain-list E-COMMERCE owner WEB-SERVICESgssm1.example.com(config-gslb)# domain-list E-COMMERCE comments "GLOBAL DOMAIN LIST FOR ECOMMERCE"The following example shows how to delete a domain list:
gssm1.example.com(config-gslb)# no domain-list E-COMMERCERelated Commands
(config-gslb-dl) domain
After you create a domain list using the domain-list command, to add domains to the list, use the domain command in the domain list configuration mode. To delete a domain from a domain list, use the no form of this command.
domain name
no domain name
Syntax Description
See the "Usage Guidelines" section for details about entering domains.
Command Modes
Domain list configuration mode
Usage Guidelines
You can enter a maximum of 500 domains for each list. You can enter complete domain names or any regular expression that specifies a pattern by which the GSS can match incoming addresses. Enter the domain names of resources for which the GSS acts as the authoritative Domain Name System (DNS) server.
Domain names cannot exceed 128 characters. The following examples show domain names configured on the GSS:
cisco.comwww.cisco.comwww.support.cisco.comWith the exception of the "?" wildcard, which is not supported, the GSS supports domain names that use wildcards. Wildcard syntax is based on POSIX 1003.2 extended regular expressions. Any request for a hosted domain that matches the pattern is directed accordingly.
The use of the "?" wildcard is allowed for domain names when using the script play-config command to play a GSLB configuration file. See the Configuring Domain Lists in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information.
For example, assume that you have 20 or more possible domains, such as www1.cisco.com, www2.cisco.com, and so on. You can create a wildcard expression that covers all of those domains:
.*\.cisco\.comFor domain names with wildcards that are valid regular expressions, the GSS can match strings up to 256 characters.
Examples
The following example shows how to create a domain list called E-COMMERCE and add the domain DATABASEEXAMPLE.COM to the list:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# domain-list E-COMMERCE owner WEB-SERVICESgssm1.example.com(config-gslb-dl[dl-name])# domain DATABASEEXAMPLE.COMThe following example shows how to add multiple domains to the domain list:
gssm1.example.com(config-gslb-dl[dl-name])# domain WWW.EXAMPLE.COMgssm1.example.com(config-gslb-dl[dl-name])# domain SUPPORT.EXAMPLE.COMgssm1.example.com(config-gslb-dl[dl-name])# domain CDM.EXAMPLE.COMThe following example shows how to delete a domain:
gssm1.example.com(config-gslb-dl[dl-name])# no domain CDM.EXAMPLE.COMRelated Commands
(config-gslb) keepalive-properties cra
To change content routing agent (CRA) global keepalive configuration settings, use the keepalive-properties cra command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties cra {min-interval number} | timing-decay number}
no keepalive-properties cra {min-interval number} | timing-decay number}
Syntax Description
Command Modes
Global server load-balancing configuration
Examples
The following example shows how to change the CRA global keepalive configuration settings:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties cra min-interval 60 timing-decay 1The following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties cra min-interval 60 timing-decay 1Related Commands
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties kalap
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties tcp
(config-gslb) keepalive-properties http-head
To change HTTP-HEAD global keepalive configuration settings, use the keepalive-properties http-head command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties http-head {standard {min-interval number | path path | port number | termination {graceful | reset} | timeout number | fast {path path | port number | retries number | successful-probes number | termination {graceful | reset}}}}
no keepalive-properties http-head {standard {min-interval number | path path | port number | termination {graceful | reset} | timeout number | fast {path path | port number | retries number | successful-probes number | termination {graceful | reset}}}}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The requirements for your network should determine which failure detection mode (fast or standard) properties to modify. The GSS supports a maximum of 500 HTTP HEAD keepalives when using the standard detection method and a maximum of 100 HTTP HEAD keepalives when using the fast detection method.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
See Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information about keepalives.
Examples
The following example shows how to configure HTTP HEAD keepalive properties in standard failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties http-head standard min-interval 60 path /COMPANY/OWNERThe following example shows how to configure HTTP HEAD keepalive properties in fast failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties http-head fast path /COMPANY/OWNER retries 2 successful-probes 2The following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties http-head fast path /COMPANY/OWNER retries 2 successful-probes 2Related Commands
(config-gslb) keepalive-properties cra
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties kalap
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties tcp
(config-gslb) keepalive-properties icmp
To change Internet Control Message Protocol (ICMP) global keepalive configuration settings, use the keepalive-properties icmp command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties icmp {standard {min-interval number} | fast {retries number | successful-probes number}}
no keepalive-properties icmp {standard {min-interval number} | fast {retries number | successful-probes number}}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The requirements for your network should determine which failure detection mode (fast or standard) properties to modify. The GSS supports a maximum of 750 ICMP keepalives when using the standard detection method and a maximum of 150 ICMP keepalives when using the fast detection method.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
See Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information about keepalives.
Examples
The following example shows how to configure ICMP keepalive properties in standard failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties icmp standard min-interval 60The following example shows how to configure ICMP keepalive properties in fast failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties icmp fast retries 3 successful-probes 2The following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties icmp fast retries 3 successful-probes 2Related Commands
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties cra
(config-gslb) keepalive-properties kalap
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties tcp
(config-gslb) keepalive-properties kalap
To change the KAL-AP global keepalive configuration settings, use the keepalive-properties kalap command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties kalap {standard {capp-key key | min-interval number} | fast {capp-key key | retries number | successful-probes number}}
no keepalive-properties kalap {standard {capp-key key | min-interval number} | fast {capp-key key | retries number | successful-probes number}}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The requirements for your network should determine which failure detection mode (fast or standard) properties to modify. The GSS supports a maximum of 128 primary and 128 secondary KAL-AP keepalives when using the standard detection method and a maximum of 40 primary and 40 secondary KAL-AP keepalives when using the fast detection method.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
See Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information about keepalives.
Examples
The following example shows how to configure KAL-AP keepalive properties in standard failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties kalap standard capp-key SECRET-KEY-101 min-interval 80The following example shows how to configure KAL-AP keepalive properties in fast failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties kalap fast capp-key SECRET-KEY-101 retries 5 successful-probes 2The following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties kalap fast capp-key SECRET-KEY-101 retries 5 successful-probes 2Related Commands
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties cra
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties tcp
(config-gslb) keepalive-properties scripted-kal
To change the Scripted Kal global keepalive configuration settings, use the keepalive-properties scripted-kal command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties scripted-kal {standard min-interval number | fast retries number | successful-probes number}
no keepalive-properties {standard min-interval number | fast retries number | successful-probes number}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The requirements for your network should determine which failure detection mode (fast or standard) properties to modify.
In the standard detection mode, the GSS supports a maximum of the following:
•
•
•
When using the fast detection method, GSS supports a maximum of the following:
•
•
•
As you adjust the fast retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
See Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information about keepalives.
Examples
The following example shows how to configure Scripted keepalive properties in standard failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties scripted-kal standard min-interval 60The following example shows how to configure Scripted keepalive properties in fast failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties scripted-kal fast retries 3 successful-probes 2The following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties kalap fast capp-key SECRET-KEY-101 retries 3 successful-probes 2Related Commands
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties cra
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties tcp
(config-gslb) keepalive-properties ns
To change the name server (NS) global keepalive configuration settings, use the keepalive-properties ns command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties ns {min-interval number} | query-domain domain_name}
no keepalive-properties ns {min-interval number} | query-domain domain_name}
Syntax Description
Command Modes
Global server load-balancing configuration
Examples
The following example shows how to change the NS global keepalive configuration settings:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties ns min-interval 60 query-domain WWW.HOME.COMThe following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties ns min-interval 60 query-domain WWW.HOME.COMRelated Commands
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties kalap
(config-gslb) keepalive-properties cra
(config-gslb) keepalive-properties tcp
(config-gslb) keepalive-properties tcp
To change TCP global keepalive configuration settings, use the keepalive-properties tcp command in global server load-balancing configuration mode. To reset the keepalive properties to the default settings, use the no form of this command.
keepalive-properties tcp {standard {min-interval number | port number | termination {graceful | reset} | timeout number | fast {port number | retries number | successful-probes number | termination {graceful | reset}}}}
no keepalive-properties tcp {standard {min-interval number | port number | termination {graceful | reset} | timeout number | fast {port number | retries number | successful-probes number | termination {graceful | reset}}}}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The requirements for your network should determine which failure detection mode (fast or standard) properties to modify. The GSS supports a maximum of 1500 TCP keepalives when using the standard detection method and a maximum of 150 TCP keepalives when using the fast detection method.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
See Chapter 1, Introducing the Global Site Selector in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information about keepalives.
Examples
The following example shows how to configure TCP keepalive properties in standard failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties tcp standard min-interval 60 timeout 25The following example shows how to configure TCP keepalive properties in fast failure detection mode:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# keepalive-properties tcp fast retries 3 successful-probes 2 termination gracefulThe following example shows how to reset the keepalive properties to the default settings:
gssm1.example.com(config-gslb)# no keepalive-properties tcp standard min-interval 60 timeout 25Related Commands
(config-gslb) keepalive-properties http-head
(config-gslb) keepalive-properties icmp
(config-gslb) keepalive-properties kalap
(config-gslb) keepalive-properties ns
(config-gslb) keepalive-properties cra
(config-gslb) location
To configure a location, use the location command in global server load-balancing configuration mode. To delete a location, use the no form of this command.
location name [region name | comments text | zone name | suspend-all-answers | activate-all-answers]
no location name [region name | comments text | zone name | suspend-all-answers | activate-all-answers]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
If you need to delete a location, ensure that you know about the dependencies associated with a resource. For example, answers associated with locations that are deleted are automatically associated with the "Unspecified" location.
Deletions of any kind cannot be undone in the primary GSSM. If you want to use the deleted data at a later point in time, we recommend that you back up the database of your primary GSSM. See the Global Site Selector Administration Guide for details.
Suspending all answers for a location overrides the active or suspended state of an individual answer.
Examples
The following example shows how to create a location called San_Francisco and associate it with the region Western_USA:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# location SAN_FRANCISCO region WESTERN_USAgssm1.example.com(config-gslb)# location SAN_FRANCISCO comments "UNION SQUARE"The following example shows how to delete a location:
gssm1.example.com(config-gslb)# no location SAN_FRANCISCORelated Commands
(config-gslb) manual-reactivation
To enable the global manual reactivation function or to enable all operationally suspended answers or clauses, use the manual-reactivation command in global server load-balancing configuration mode. To disable the global manual reactivation function, use the no form of this command.
manual-reactivation {activate-MR-answers all | activate-MT-clauses all| enable}
no manual-reactivation enable
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
You must have the manual reactivation function enabled to activate all operationally suspended answers or clauses.
Disabling global manual reactivation causes the GSS to automatically reactivate all answers and clauses when they return to an online state, including any answers and clauses that you configure for manual reactivation.
For more information on the manual reactivation function, see the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide.
Examples
The following example shows how to enable the global manual reactivation function:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# manual-reactivation enableThe following example shows activate all operationally suspended answers:
gssm1.example.com(config-gslb)# manual-reactivation activate-answers-allThe following example shows how to disable the global manual reactivation function:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no manual-reactivation enableRelated Commands
(config-gslb-rule) clause number cra-group
(config-gslb-rule) clause number ns-group
(config-gslb-rule) clause number vip-group
(config-gslb) no
To negate a CLI command or set it to its default settings, use the no command. Some GSS CLI commands do not have a no form.
no command
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
Use the no command to disable functions or negate a command. If you need to negate a specific command, such as the default gateway IP address, you must include the specific string in your command, such as no ip default-gateway ip-address.
Examples
The following example shows how to negate a CLI command or set it to its default settings:
gss1.example.com(config)# no ip name-server 10.11.12.14gss1.example.com(config)# no ntp-server 172.16.22.44(config-gslb) owner
To configure an owner, use the owner command in global server load-balancing configuration mode. To delete an owner, use the no form of this command.
owner name [comments text | activate-all-answers | activate-all-rules | suspend-all-answers | suspend-all-rules]
no owner name [comments text]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
Owners are logical groupings for GSS network resources that correspond to business or organizational structures. For example, an owner might be a hosting customer, an internal department such as human resources, or an IT staff resource.
If you need to delete an owner, be sure that you know the dependencies of that resource. For example, answer groups, DNS rules, and domain lists associated with an owner will, if that owner is deleted, automatically be associated with the "System" owner account.
Deletions of any kind cannot be undone in the primary GSSM. If you want to use the deleted data at a later point in time, we recommend that you back up the database of your primary GSSM. See the Global Site Selector Administration Guide for details.
Examples
The following example shows how to configure an owner:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# owner WEB-SERVICES comments "INCLUDES MARKETING, ADVERTISING, AND ECOMMERCE CONTENT PROVIDERS"The following example shows how to delete an owner:
gssm1.example.com(config-gslb)# no owner WEB-SERVICES comments "INCLUDES MARKETING, ADVERTISING, AND ECOMMERCE CONTENT PROVIDERS"Related Commands
(config-gslb) proximity assign
To configure static proximity metrics for zones in your GSS network or to assign probing devices to specific D-proxies, use the proximity assign command. To delete static entries from the proximity database in the GSS memory, use the no form of this command.
proximity assign {group {groupname}} | ip {entryaddress} | [probe-target {ip-address} | zone-data {"zoneId:RTT"}]
no proximity assign {group {groupname}} | ip {entryaddress} | [probe-target {ip-address} | zone-data {"zoneId:RTT"}]
Command Modes
Global server load-balancing configuration
Usage Guidelines
Entries in the PDB can be both dynamic and static. The GSS creates dynamic entries in the proximity database as the result of requests from new D-proxy IP addresses. If you need to configure static proximity metrics for zones in your GSS network or assign probing devices to specific D-proxies, define a series of static entries in the proximity database by using the proximity assign global server load-balancing configuration mode command. If the same entry, dynamic or static, already exists in the proximity database, the GSS will overwrite that entry with the newly assigned entry.
Static entries in the PDB do not age out and remain in the PDB until you delete them. In addition, static entries are not subject to the automatic database cleanup of least recently used entries when the PDB size is almost at the maximum number of entries. Use the no proximity assign command to delete static entries from the PDB.
Note
You can specify permanent RTT values for the static entries. When the GSS uses permanent RTT values, it does not perform active probing with the Director Response Protocol (DRP) agent. Instead of RTT values, you can specify alternate IP addresses as targets for probing by the probing devices to obtain the RTT data. The GSS probes the alternate probe target for requests from D-proxies matching these static entries.
The GSS accepts commands up to 1024 characters. Ensure that the proximity database-entry create command does not exceed that length when you configure RTT for a large number of proximity zones.
Examples
The following example shows how to configure static RTT metrics for the proximity group ISP2 using zone indexes created previously through the primary GSSM GUI:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# proximity assign group ISP1 zone-data "1:100,2:200,3:300,4:400,5:500"The following example shows how to delete static RTT entries for the proximity group ISP1:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no proximity assign group ISP1 zone-data "1:100,2:200,3:300,4:400,5:500"Related Commands
(config-gslb) proximity group
To create a proximity group of multiple D-proxy IP addresses, use the proximity group command. To delete a previously configured IP address block from a proximity group or to delete a proximity group and all configured IP address blocks, use the no form of this command.
proximity group {groupname} ip {ip-address} netmask {netmask}
no proximity group {groupname} ip {ip-address} netmask {netmask}
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The primary GSSM supports the creation of proximity groups. A proximity group allows you to configure multiple blocks of D-proxy IP addresses that each GSS device stores in its proximity database (PDB) as a single entry. Instead of multiple PDB entries, the GSS uses only one entry in the PDB for multiple D-proxies. The GSS treats all D-proxies in a proximity group as a single D-proxy when responding to Domain Name System (DNS) requests with the most proximate answers. Requests from D-proxies within the same proximity group receive the RTT values from the database entry for the group. The benefits of proximity grouping include less probing activities performed by the GSS, less space required for the PDB, and user flexibility in assigning alternative probing targets or static proximity metrics to a group.
Reenter the proximity group command to add multiple IP blocks to a proximity group or create additional proximity groups.
Create proximity groups at the CLI of the primary GSSM to obtain better scalability of your configuration and to allow for ease of proximity group creation through automation scripts. Proximity groups are saved in the primary GSSM database. All GSS devices in the network receive the same proximity group configuration. You cannot create proximity groups at the CLI of a standby GSSM or individual GSS devices.
The primary GSSM supports a maximum of 5000 proximity groups. Each proximity group contains one to 30 blocks of IP addresses and subnet masks (in dotted-decimal format).
In addition to creating proximity groups of multiple D-proxy IP addresses from the CLI, you can configure a global netmask from the primary GSSM GUI to uniformly group contiguous D-proxies (see the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide, Chapter 9, Configuring Network Proximity). The GSS uses the global netmask when no proximity group matches the incoming D-proxy address. The GSS uses the full incoming D-proxy IP address and the global netmask as the key to looking up entries in the proximity database.
Examples
The following example shows how to create a proximity group called ProxyGroup1 with an IP address block of 192.168.12.0 255.255.255.0:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# proximity group ProxyGroup1 ip 192.168.12.0 netmask 255.255.255.0The following example shows how to delete a previously configured IP address block from a proximity group:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no proximity group ProxyGroup1 IP 192.168.12.0 netmask 255.255.255.0The following example shows how to delete a proximity group and all configured IP address blocks:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no proximity group ProxyGroup1Related Commands
(config-gslb) proximity assign
(config-gslb) proximity-properties
From global server load-balancing configuration mode, to enter the proximity properties configuration mode, use the proximity-properties command.
proximity-properties
Syntax Description
This command has no keywords or arguments.
Command Modes
Global server load-balancing configuration
Usage Guidelines
In the proximity properties configuration mode, you enter commands to enable proximity and modify the Domain Name System (DNS) proximity settings for the GSS network.
Proximity settings are applied as soon as you exit from the sticky properties configuration mode or enter a new mode.
See the Proximity Properties Configuration Mode Commands section for information about the commands used to configure proximity.
Examples
The following example shows how to enter the proximity properties configuration mode:
gssm1.example.com(config-gslb)# proximity-propertiesgssm1.example.com(config-proxprop)#Related Commands
(config-gslb) proximity assign
(config-gslb) region
To configure a region, use the region command in global server load-balancing configuration mode. To delete a region, use the no form of this command.
region name [comments text]
no region name [comments text]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
If you need to delete a region, you must know about the dependencies associated with it. For example, regions that have locations associated with them cannot be deleted. You must first delete any associated locations.
Deletions of any kind cannot be undone in the primary GSSM. If you want to use the deleted data at a later point in time, we recommend that you back up the database of your primary GSSM. See the Global Site Selector Administration Guide for details.
If an error appears informing you that a GSS location is still linked to the region that you want to delete, change the region associated with the location, and then attempt to delete the region again.
Examples
The following example shows how to create a region called Western_EU and provide comments about its location and purpose:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# region Western_EU comments "London and future data centers"The following example shows how to delete a region:
gssm1.example.com(config-gslb)# no region Western_EURelated Commands
(config-gslb) script play-config
To execute a previously created global server load-balancing configuration file, use the script play-config command in global server load-balancing configuration mode. To disable the execution of a previously-created GSLB configuration file, use the no form of this command.
script play-config filename
no script play-config filename
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
Executing the file allows you to import the GSLB configuration file to a new or previously configured GSS network to automatically update its global server load-balancing configuration.
Entering the script play-config command overwrites existing duplicate GSLB commands on the primary GSSM.
To view additional information for errors encountered during a play, use the show gslb-error command in privileged EXEC mode.
Examples
The following example shows how to play the GSLB configuration file called GSLB_CONFIG_1.txt:
gssm1.example.com(config-gslb)# script play-config GSLB_CONFIG_1.TXTIf any errors are encountered with a command line, they are displayed and the file continues to play to completion. Any additional command line errors that are encountered are also displayed as follows:
gssm1.example.com(config-gslb)# script play-config GSLB_CONFIG_1.TXTERROR:Unable To Perform Source-Address-List Operation.Please Configure Owner Prior To Source-Address-Listip address 192.168.10.1 255.255.255.0% Invalid input detected at '^' marker.ip address 192.168.10.6 255.255.255.255^% Invalid input detected at '^' marker.gssm1.example.com(config-gslb)#Related Commands
(config-gslb) shared-keepalive http-head
To configure an HHTP HEAD shared keepalive, use the shared-keepalive http-head command in global server load-balancing configuration mode. To remove a shared keepalive, use the no form of this command to remove a shared keepalive.
shared-keepalive http-head ip_address [port port_number] | [host-tag domain_name] | [path path]
no shared-keepalive http-head ip_address [port port_number] | [host-tag domain_name] | [path path]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
If you need to delete a shared keepalive from your GSS network, and that shared keepalive is in use by the GSS, you must first disassociate any answers that are using the keepalive. See the "Deleting a Shared KeepAlive" section in Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for steps to disassociate your answers and remove a shared keepalive from your GSS network.
Examples
The following example shows how to configure an HHTP HEAD shared keepalive:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# shared-keepalive http-head 192.168.1.48 port 23 host-tag WWW.HOME.COMThe following example shows how to delete an HTTP HEAD shared keepalive:
gssm1.example.com(config-gslb)# no shared-keepalive http-head 192.168.1.48 port 23 host-tag WWW.HOME.COMgssm1.example.com(config-gslb)#Related Commands
(config-gslb) shared-keepalive icmp
(config-gslb) shared-keepalive kalap
(config-gslb) shared-keepalive scripted-kal
(config-gslb) shared-keepalive icmp
To configure an Internet Control Message Protocol (ICMP)-shared keepalive, use the shared-keepalive icmp command in global server load-balancing configuration mode. To remove an ICMP shared keepalive, use the no form of this command.
shared-keepalive icmp ip_address
no shared-keepalive icmp ip_address
Syntax Description
ip_address
IP address used to test the online status for the linked VIPs. Enter the address in dotted-decimal IP notation (for example, 192.168.11.1).
Command Modes
Global server load-balancing configuration
Usage Guidelines
If you need to delete a shared keepalive from your GSS network, and that shared keepalive is in use by the GSS, you must first disassociate any answers that are using the keepalive. See the "Deleting a Shared KeepAlive" section in Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for steps to disassociate your answers and remove a shared keepalive from your GSS network.
Examples
The following example shows how to configure an ICMP-shared keepalive:
gssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# shared-keepalive icmp 192.168.1.47gssm1.example.com(config-gslb)#The following example shows how to delete an ICMP shared keepalive:
gssm1.example.com(config-gslb)# no shared-keepalive icmp 192.168.1.47gssm1.example.com(config-gslb)#Related Commands
(config-gslb) shared-keepalive http-head
(config-gslb) shared-keepalive kalap
(config-gslb) shared-keepalive scripted-kal
(config-gslb) shared-keepalive kalap
To configure a KAL-AP shared keepalive, use the shared-keepalive kalap command in global server load-balancing configuration mode. To remove a shared keepalive, use the no form of this command.
shared-keepalive kalap ip_address [secondary ip_address] | [capp-secure enable [key secret]] | [retries number] | [successful probes number]
no shared-keepalive kalap ip_address [secondary ip_address] | [capp-secure enable [key secret]] | [retries number] | [successful probes number]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
You can specify the optional retries and successful probes options only if the KAL-AP global keepalive configuration is set to the Fast KAL Type. See Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
If you need to delete a shared keepalive from your GSS network, and that shared keepalive is in use by the GSS, you must first disassociate any answers that are using the keepalive. See the "Deleting a Shared KeepAlive" section in Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for steps to disassociate your answers and remove a shared keepalive from your GSS network.
Examples
The following example shows how to configure a KAL-AP shared keepalive:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# shared-keepalive kalap 192.168.1.40 secondary 192.168.1.42 retriesThe following example shows how to delete a KAL-AP shared keepalive:
gssm1.example.com(config-gslb)# no shared-keepalive kalap 192.168.1.40 secondary 192.168.1.42 retriesgssm1.example.com(config-gslb)#Related Commands
(config-gslb) shared-keepalive icmp
(config-gslb) shared-keepalive http-head
(config-gslb) shared-keepalive scripted-kal
(config-gslb) shared-keepalive scripted-kal
To configure a Scripted Kal shared keepalive, use the shared-keepalive scripted-kal command in global server load-balancing configuration mode. To remove a shared keepalive, use the no form of this command to remove a shared keepalive.
shared-keepalive scripted-kal ip_address kal-name name
[csm [community community_name] | css [community community_name] |
ios-slb [community community_name] |
snmp-mib-indexed-by-vip [community community_name | load-filter string | oid oid | return-load | return-offline-value offline_value | return-online-value online_value] |
snmp-mib-not-indexed-by-vip [address-filter string | community community_name | load-filter string | oid oid | return-load | return-offline-value offline_value | return-online-value online_value] |
snmp-scalar [community community_name | oid oid | return-load | return-offline-value offline_value | return-online-value online_value] |
[retries number] | [successful-probes number]Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
See Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for more information about the wrappers, OIDs, address and load filters that are appropriate for different SLB devices. Be aware also that you can only specify the optional retries and successful probes options if the Scripted Kal global keepalive configuration is set to the Fast KAL Type.
As you adjust the retries value, you change the detection time determined by the GSS. By increasing the number of retries, you increase the detection time. Reducing the number of retries has the reverse effect.
Examples
The following example shows how to configure a Scripted Kal shared keepalive:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# shared-keepalive scripted-kal 192.168.1.46 kal-name samplekal ios-slb community samplecommunityRelated Commands
(config-gslb) shared-keepalive icmp
(config-gslb) shared-keepalive http-head
(config-gslb) shared-keepalive kalap
(config-gslb) shared-keepalive tcp
To configure a TCP shared keepalive, use the shared-keepalive tcp command in global server load-balancing configuration mode. To remove a shared keepalive, use the no form of this command.
shared-keepalive tcp ip_address [port port_number] | [termination {graceful | reset}]
no shared-keepalive tcp ip_address [port port_number] | [termination {graceful | reset}]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
If you need to delete a shared keepalive from your GSS network, and that shared keepalive is in use by the GSS, you must first disassociate any answers that are using the keepalive. See the "Deleting a Shared KeepAlive" section in Chapter 5, Configuring Keepalives in the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for steps to disassociate your answers and remove a shared keepalive from your GSS network.
Examples
The following example shows how to configure a TCP shared keepalive:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# shared-keepalive tcp 192.168.1.46 port 23 termination gracefulThe following example shows how to delete a TCP shared keepalive:
gssm1.example.com(config-gslb)# no shared-keepalive tcp 192.168.1.46 port 23 termination gracefulgssm1.example.com(config-gslb)#Related Commands
(config-gslb) shared-keepalive icmp
(config-gslb) shared-keepalive kalap
(config-gslb) shared-keepalive http-head
(config-gslb) source-address-list
To configure a source address list, use the source-address-list command in global server load-balancing configuration mode. To delete a source address list, use the no form of this command.
source-address-list name owner name [comments text]
no source-address-list name owner name [comments text]
Syntax Description
name
Name for the source address list. Enter a unique alphanumeric name with a maximum of 80 characters. Names that include spaces must be entered in quotes (for example, "name 1").
owner name
Specifies an existing owner name with which the source address list is to be associated. See the (config-gslb) owner command for more information.
comments text
(Optional) Specifies descriptive information or important notes about the source address list. Enter a maximum of 256 alphanumeric characters. Comments with spaces must be entered in quotes.
Command Modes
Global server load-balancing configuration
Usage Guidelines
After you enter the source-address-list command, the prompt changes to the source address list mode where you specify IP addresses of the client Domain Name System (DNS) proxies. You can enter up to 30 addresses for each list. See the ip address command that follows for information about adding IP addresses to a source address list.
If you need to delete a source address list, first verify that none of your DNS rules reference the source address list that you want to delete. You cannot delete source address lists associated with an existing DNS rule. If necessary, remove the source address list from the DNS rule. See the Cisco Global Site Selector CLI-Based Global Server Load-Balancing Configuration Guide for information about modifying a DNS rule.
Deletions of any kind cannot be undone in the primary GSSM. If you want to use the deleted data at a later point in time, we recommend that you back up the database of your GSSM. See the Cisco Global Site Selector Administration Guide for details.
Examples
The following example shows how to create a source address list called WEB-GLOBAL-LISTS:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# source-address-list WEB-GLOBAL-LISTS owner WEB-SERVICES comments "GLOBAL ALIST FOR ECOMMERCE"The following example shows how to delete a source address list:
gssm1.example.com(config-gslb)# no source-address-list WEB-GLOBAL-LISTSgssm1.example.com(config-gslb)#Related Commands
(config-gslb-sal) ip address
To create a source address list, use the source-address-list command. To delete an address from a source address list, use the no form of this command.
ip address ip_address netmask
no ip address ip_address netmask
Syntax Description
Command Modes
Source address list configuration mode
Usage Guidelines
You can enter up to 30 addresses for each list. To add addresses to a source address list, use the ip address command in source address list configuration mode.
After you create a source address list by using the source-address-list command, the prompt changes to the source address list mode (config-gslb-sal), where you specify addresses of the client DNS proxies.
Examples
The following example shows how to create a source address list called WEB-GLOBAL-LISTS and add two IP addresses and subnet masks to the list:
gssm1.example.com(config-gslb)# source-address-list WEB-GLOBAL-LISTS owner WEB-SERVICES comments "GLOBAL ALIST FOR ECOMMERCE"gssm1.example.com(config-gslb-sal)#ip address 1024 172.27.16.4 255.255.255.0gssm1.example.com(config-gslb-sal)# ip address 1024 172.27.28.4 255.255.255.0The following example shows how to delete an IP address that is included in the source address list GLOBAL-SERVICE-LISTS:
gssm1.example.com(config-gslb)# source-address-list GLOBAL-SERVICE-LISTSgssm1.example.com(config-gslb-sal)# no ip address 1024 172.27.16.4 255.255.255.0gssm1.example.com(config-gslb-sal)#Related Commands
(config-gslb) source-address-list
(config-gslb) sticky group
To create a Domain Name System (DNS) sticky group, use the sticky group global server load-balancing command from the primary GSSM CLI to identify the name of the DNS sticky group and add an IP address block to the group. To delete a previously configured IP address block from a sticky group or to delete a sticky group, use the no form of this command.
sticky group groupname ip ip_address netmask netmask
no sticky group groupname ip ip-address netmask netmask
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
The sticky groups are saved in the primary GSSM database and all GSS devices in the network receive the same sticky group configuration. You cannot create sticky groups using the CLI of a standby GSSM or individual GSS devices.
Reenter the sticky group command if you want to add multiple IP address blocks to a DNS sticky group or create additional DNS sticky groups.
Examples
The following example shows how to create a sticky group called StickyGroup1 with an IP address block of 192.168.9.0 255.255.255.0:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# sticky group StickyGroup1 ip 192.168.9.0 netmask 255.255.255.0The following example shows how to delete a sticky group:
gssm1.example.com# configgssm1.example.com(config)# gslbgssm1.example.com(config-gslb)# no sticky group StickyGroup1Related Commands
(config-gslb) sticky-properties
(config-gslb) sticky-properties
From global server load-balancing configuration mode, to enter the sticky properties configuration mode, use the sticky-properties command.
sticky-properties
Syntax Description
This command has no keywords or arguments.
Command Modes
Global server load-balancing configuration
Usage Guidelines
In the sticky properties configuration mode, you issue commands to enable sticky and modify the Domain Name System (DNS) sticky settings for the GSS network. Sticky settings are applied as soon as you exit from the sticky properties configuration mode or enter a new mode.
See the Sticky Properties Configuration Mode Commands section for information about the commands used to configure stickiness.
Examples
The following example shows how to enter the sticky properties configuration mode:
gssm1.example.com(config-gslb)# sticky-propertiesgssm1.example.com(config-gslb-stkyprop)#Related Commands
(config-gslb) zone
To configure a proximity zone from the primary GSSM, use the zone command in global server load-balancing configuration mode. To delete a zone, use the no form of this command.
zone name {index number | probe ip_address} [backup ip_address]
no zone name {index number | probe ip_address} [backup ip_address]
Syntax Description
Command Modes
Global server load-balancing configuration
Usage Guidelines
You cannot modify the index value. To change the zone index, delete the zone, and then create a new zone containing a different index.
Examples
The following example shows how to configure a proximity zone from the primary GSSM:
gssm1.example.com(config-gslb)# zone Z1 index 1 probe 192.168.11.1 backup 192.168.11.5The following example shows how to delete zone z1:
gssm1.example.com(config-gslb)# no zone Z1 index 1 probe 192.168.11.1 backup 192.168.11.5or
gssm1.example.com(config-gslb)# no zone Z1Related Commands
(config-gslb) proximity-properties
(config-gslb) proximity assign
