Table Of Contents

Primary GSSM Global Server Load-Balancing Error Messages

Answer Error Messages

Answer Group Error Messages

Domain List Error Messages

DNS Rule Error Messages

KeepAlive Error Messages

Location Error Messages

Network Error Messages

Owner Error Messages

Proximity Error Messages

Region Error Messages

Source Address List Error Messages

Sticky Error Messages

User Account Error Messages

User Views Error Messages

Primary GSSM Global Server Load-Balancing Error Messages

---

This appendix describes error messages that you may encounter when using the primary GSSM GUI to perform global server load balancing. Error messages are organized by primary GSSM GUI components.

This chapter contains the following major sections:

•Answer Error Messages

•Answer Group Error Messages

•Domain List Error Messages

•DNS Rule Error Messages

•KeepAlive Error Messages

•Location Error Messages

•Network Error Messages

•Owner Error Messages

•Proximity Error Messages

•Region Error Messages

•Source Address List Error Messages

•Sticky Error Messages

•User Account Error Messages

•User Views Error Messages

Answer Error Messages

Table A-1 lists the potential error messages that may appear when configuring answers.

Table A-1 Answer Error Messages 

Error Message	Description	Recommended Action
Invalid answer name. If entered, name must not be the empty string.	You entered an invalid name for the answer. Answer names cannot be blank or contain blank spaces.	Enter a valid alphanumeric answer name between 1 and 80 characters that does not contain spaces.
Invalid answer name. Name length must not exceed 80 characters.	You entered an answer name that contains too many characters.	Enter a valid alphanumeric answer name between 1 and 80 characters that does not contain spaces.
Invalid CRA timing decay. Timing decay must be between 1 and 10.	You entered an invalid number for the CRA timing decay.	Enter a number between 1 and 10. Lower timing decay values mean that more recent DNS races are weighted more heavily than older races. Higher decay values mean that the results of older races are weighted more heavily than more recent races.
Invalid CRA static RTT value. Static RTT must be between 0 and 1000.	You entered an invalid number for the static round-trip time (RTT). This manually entered value is used by the GSS to represent the time it takes for traffic to reach and return from a host.	Enter a static RTT value between 0 and 1000.
A VIP/Name Server/CRA-type answer named answer_name already exists. If specified, name and type must uniquely identify an answer.	You attempted to create an answer that already exists on the GSS. You cannot have two answers with the same name and answer type.	Assign a new name or answer type to your answer to make it unique.
An unnamed VIP/Name Server/CRA-type answer having address IP_address already exists. Name must be specified to configure an answer with the same address as another answer.	You attempted to create an answer that already exists on the GSS. You cannot have two answers with the same name and IP address.	Assign a new name to your answer to make it unique.
The maximum number of number VIP/Name Server/CRA-type answers has been met.	You attempted to create an answer when the maximum number of that type of answer has already been created.	Remove an existing answer of the same type.
CRA decay value must be specified.	You attempted to create a CRA answer type without specifying a decay value. The decay value is required to tell the GSS how to evaluate and weigh DNS race results.	Enter a number between 1 and 10 for the CRA decay, with 1 causing the GSS to weigh recent DNS race results more heavily, and 10 telling it to weigh them less heavily.
CRA static RTT must be specified.	You attempted to create a CRA answer type without specifying a static round-trip time (RTT) value. The RTT value is used to force the GSS to use a value that you supply as the round-trip time necessary to reach the requesting D-proxy.	Enter a number between 1 and 1000 for the CRA round-trip time in milliseconds.
Invalid keepalive tag. Tag must be at least one character in length.	You attempted to create a VIP answer with a KAL-AP By Tag keepalive, but you have not specified a value for the tag in the field provided.	Enter an alphanumeric tag between 1 and 76 characters in the Tag field.
Invalid keepalive tag. Tag length must not exceed 76 characters.	You attempted to create a VIP answer with a KAL-AP By Tag keepalive, but you have specified a value for the tag that contains too many characters.	Enter an alphanumeric tag between 1 and 76 characters in the Tag field.
NS-type answer IP Address has the same IP address as GSS GSS_name. GSS IP addresses must not equal any NS-type answers.	You attempted to create a name server answer type with the same IP address as a GSS device on the same GSS network. Name server answers cannot use the same address as GSS devices belonging to the same GSS network.	Assign a valid IP address to your name server answer.
Invalid answer order. Order must not be negative.	You attempted to assign a negative order number to your answer. The order must be a positive number.	Enter a nonnegative whole number for the order.

Answer Group Error Messages

Table A-2 lists the potential error messages that may appear when configuring answer groups.

Table A-2 Answer Group Error Messages 

Error Message	Description	Recommended Action
This answer group cannot be deleted because it is referenced by number DNS rule balance clause(s).	You attempted to delete an answer group that is being referenced by one or more DNS rules.	Modify any DNS rules that are referencing the answer group so that those rules do not point to the group, and then try again to delete the group.
Invalid answer group name. Name must be entered.	You attempted to create an answer group without assigning a name to that group. All answer groups must have names of at least one character.	Enter a name for the new answer group in the field provided, and then click Save.
Invalid answer group name. Name length must not exceed 80 characters.	You attempted to assign an invalid name to the answer group.	Enter an alphanumeric name for the answer group that is fewer than 80 characters and does not contain spaces.
Invalid answer group name. Name must not contain spaces.	You attempted to assign an invalid name to the answer group.	Enter an alphanumeric name for the answer group that is fewer than 80 characters and does not contain spaces.
An answer group named name already exists. Name must uniquely identify an answer group.	You attempted to assign the answer group a name that is already being used by a different GSS device.	Enter a unique alphanumeric name for the answer group that is fewer than 80 characters and does not contain spaces.
The maximum number of number answers per VIP/Name Server/CRA-type group has been met.	You attempted to add an answer to an answer group to which the maximum number of answers has already been assigned.	Remove an answer from the group, or add the answer to a group to which the maximum number of answers has not already been added.
Invalid answer load threshold. Load threshold must be between 2 and 254.	You attempted to assign an invalid load threshold to your answer in the LT field.	Assign a load threshold for the answer that is between 2 and 254 in the LT field.

Domain List Error Messages

Table A-3 lists the potential error messages that may appear when configuring domain lists.

Table A-3 Domain List Error Messages 

Error Message	Description	Recommended Action
<domain name> must contain at least one character.	You attempted to add a domain to a domain list with an invalid name. Domains in domain lists must have names of at least one character.	Enter a name that is between 1 and 100 characters and then save your domain list.
<domain name> character limit exceeded.	You attempted to add a domain to a domain list using a name that is too long. Domains in domain lists cannot have names with more than 100 characters.	Enter a new domain name of no more than 100 characters and then save your domain list.
Domain specification must not exceed 128 characters.	You attempted to add a domain to your domain list with a name that is longer than 128 characters. Domain lists cannot contain domains with names that have more than 128 characters.	Replace the domain with a domain name containing fewer than 128 characters and then save your domain list.
<domain name> must not contain spaces.	You attempted to add a domain to your domain list with a name that contains spaces. Domains in domain lists cannot have names that contain spaces.	Modify the domain name so that it does not contain spaces and then save your domain list.
<domain name> is not a valid regular expression: <regular expression syntax error message here>	You attempted to add a domain name to a domain list with a name that contains invalid characters or formatting. Domain names in domain lists must be valid regular expressions.	Modify the domain name so that it is a valid regular expression and does not contain any invalid characters or formatting (for example, www.cisco.com or .*\.cisco\.com), and then save your domain list.
<domain name> must not begin or end with '.'	You attempted to add a domain to a domain list with a literal name that contains an invalid character at the beginning or end of the domain name.	Modify the domain name so that it does not contain a period at the beginning or end of the name and then save your domain list.
<domain name> component must not begin or end with '-'	You attempted to add a domain to a domain list with a literal name that contains an invalid character at the beginning or end of one component of the domain name (for example, www.cisco-.com).	Modify the domain name so that it does not contain a dash (-) at the beginning or end of any segment of the name and then save your domain list.
<domain name> contains invalid character '<character>' (<ASCII value of the character>)	You attempted to add a domain to a domain list with a name that contains an invalid text character. Domains belonging to domain lists must have names that are regular expressions.	Modify the domain name so that it does not contain an invalid text character and then save your domain list.
This domain list cannot be deleted because it is referenced by X DNS rule	You attempted to delete a domain list that is being referenced by one or more DNS rules.	Modify any DNS rules that use the domain list so that they no longer reference it and then try again to delete the list.
Invalid domain list name. Name must be entered.	You attempted to create a domain list without a name. Domain lists must have names of at least one character.	Assign a name that has between 1 and 80 characters to your domain list and then save it.
Invalid domain list name. Name length must not exceed 80 characters.	You attempted to create a domain list with a name that is too long.	Assign a name that has between 1 and 80 characters to your domain list and then save it.
Invalid domain list name. Name must not contain spaces.	You attempted to create a domain list with a name that contains spaces. Domain list names cannot contain spaces.	Assign a name without spaces to your domain list. Names must consist of between 1 and 80 characters. Save your domain list when you have assigned it a valid name.
A domain list named '<name>' already exists. Name must uniquely identify a domain list.	You attempted to assign a name to your domain list that has already been assigned to another domain list on the same GSS network.	Assign a unique name to your new domain list and then save the list.
The maximum number of <limit> domains per list has been met.	You attempted to add a domain to your domain list when the maximum number of domains has already been added to that list.	Remove an existing domain from the domain list and then add the new domain. Alternatively, create a domain list to hold the new domain and any subsequent domains that you want to add.

DNS Rule Error Messages

Table A-4 lists the potential error messages that may appear when configuring DNS rules.

Table A-4 DNS Rules Error Messages 

Error Message	Description	Recommended Action
TTL must be specified for balance method associated with CRA- or VIP-type answer group.	You attempted to create a balance clause without specifying a Time To Live (TTL) for answers returned by the clause.	Enter a TTL value between 0 and 604,800 seconds.
Invalid balance clause TTL. TTL must be between 0 and 604,800.	You attempted to create a balance clause with an incorrect TTL value for answers provided by the balance clause.	Enter a TTL value between 0 and 604,800 seconds.
Invalid balance clause position. Position must be between 0 and 2.	You attempted to create a clause for your DNS rule that is out of sequence. The DNS Rule Builder provides options for three balance clauses, which must be created in order, with no gaps between clauses. For example, if you are using only one balance clause, it must appear in the first position. It cannot be listed in the second or third positions with the first position left blank.	Rearrange your balance clauses in the DNS Rule Builder so that they are listed in the proper order with no gaps between them.
Hash type must be specified for answer group using hash balance method.	You attempted to create an answer group using the balance method "Hashed" with the selected answer, but you have not selected one (or more) hash methods: By Domain Name and By Source Address.	Select one or more of the available hash methods by checking the box corresponding to the methods that you want to use with this balance clause.
Balance clause boomerang fragment size must be specified.	You attempted to create a balance clause using the boomerang balance method but have not specified a fragment size in the Fragment Size field. The fragment size determines the preferred size of the boomerang race response that is produced by a match to a DNS rule and is sent to the requesting client.	Enter a fragment size between 28 and 1980 in the field provided. The fragment size must be divisible by 4.
Invalid balance clause Boomerang fragment size. Boomerang fragment size must be 0 or between 28 and 1980.	You attempted to specify an unacceptable fragment size for this balance clause in the Fragment Size field.	Enter a valid fragment size. Fragment sizes must be between 28 and 1980 and must be divisible by 4.
Invalid balance clause Boomerang fragment size. Boomerang fragment size must be a multiple of 4.	You attempted to specify a fragment for this boomerang balance clause that is within the acceptable range but not divisible by 4. Fragment sizes must be divisible by 4.	Enter a fragment size between 28 and 1980 that is also divisible by 4. Zero is also an acceptable fragment size.
Balance clause Boomerang IP TTL value must be specified.	You attempted to create a balance clause using the boomerang balance method but have not specified an IP Time To Live (TTL) in the field provided. The IP TTL specifies the maximum number of network hops that can be used when returning a response to a CRA from a match on a DNS rule.	Enter an IP TTL between 1 and 255 in the field provided and then click Save.
Invalid balance clause Boomerang IP TTL. Boomerang IP TTL must be between 1 and 255.	You attempted to create a balance clause using the boomerang balance method but have specified an invalid IP Time to Live (TTL).	Enter an IP TTL between 1 and 255 in the field provided and then click Save.
Balance clause Boomerang maximum propagation delay must be specified.	You attempted to create a balance clause using the boomerang balance method but have not specified a maximum propagation delay (Max Prop. Delay) in the field provided. The maximum propagation delay specifies the maximum length of time (in milliseconds) before the GSS forwards a Domain Name System (DNS) request to a content routing agent (CRA).	Enter a maximum propagation delay between 1 and 1000 milliseconds in the Max Prop. Delay field.
Invalid balance clause Boomerang maximum propagation delay. Boomerang maximum propagation delay must be between 1 and 1000.	You attempted to create a balance clause using the boomerang balance method but have not specified a valid maximum propagation delay (Max Prop. Delay) in the field provided.	Enter a maximum propagation delay between 1 and 1000 milliseconds in the Max Prop. Delay field.
Balance clause Boomerang padding size must be specified.	You attempted to create a balance clause using the boomerang balance method but have not specified a pad size in the Pad Size field. The pad size is the amount of extra data (in bytes) included with each content routing agent (CRA) response packet and is used to evaluate CRA bandwidth and latency when routing decisions are made.	Enter a valid pad size between 0 and 2000 in the Pad Size field.
Invalid balance clause Boomerang padding size. Boomerang padding size must be between 0 and 2000.	You attempted to create a balance clause using the boomerang balance method but have specified an invalid pad size in the Pad Size field.	Enter a valid pad size between 0 and 2000 in the Pad Size field.
Invalid balance clause Boomerang secret. If specified, Boomerang secret must be between 1 and 64 characters in length.	You attempted to create a balance clause using the boomerang balance method but have specified an invalid secret in the Secret field. The boomerang secret is a text string between 1 and 64 characters that is used to encrypt critical data sent between the boomerang server and content routing agents (CRAs). This key must be the same for each configured CRA.	Enter a valid boomerang secret between 1 and 64 characters in the Secret field.
Balance clause Boomerang server delay must be specified.	You attempted to create a balance clause using the boomerang balance method but have not specified a server delay in the Server Delay field. The boomerang server delay is the maximum delay (in milliseconds) before the boomerang server component of the GSS forwards the address of its "last gasp" server as a response to the requesting name server.	Enter a valid server delay between 32 and 999 milliseconds in the Server Delay field.
Invalid balance clause Boomerang server delay. Boomerang server delay must be between 32 and 999.	You attempted to create a balance clause using the boomerang balance method but have specified an invalid server delay in the Server Delay field.	Enter a valid server delay between 32 and 999 milliseconds in the Server Delay field.
Invalid DNS rule name. Name must be entered.	You attempted to create a DNS rule without assigning a name to the rule. DNS rules must have names between 1 and 100 characters.	Assign a name to your DNS rule using the Rule Name field and then try again to save the rule.
Invalid DNS rule name. Name length must not exceed 100 characters.	You attempted to assign a name to your DNS rule that is too long. The maximum length for DNS rules is 100 characters.	Enter a name for your DNS rule that is between 1 and 100 characters and then attempt to save the rule again.
Invalid DNS rule name. Name must not contain spaces.	You attempted to assign your DNS rule a name that contains spaces.	Enter a valid name for your DNS rule that is between 1 and 100 characters and does not contain spaces.
A DNS rule using the specified source address list, domain list, and matching query type already exists. Source address list, domain list, and matching query type must uniquely identify a DNS rule.	You attempted to create a DNS rule that already exists. DNS rules must specify a unique combination of a source address list, a domain list, and a matching query type.	Reconfigure your DNS rule so that it does not exactly match the preexisting rule and then save the rule.
Duplicate answer group/balance method assignment detected. A DNS rule cannot use the same answer group and balance method in multiple balance clauses.	You attempted to create two identical answer group and balance method clauses in your DNS rule. Each clause must use a unique combination of answer groups and balance methods.	Modify one of your answer group and balance method pairs so that it is no longer identical to the other and then save your DNS rule.
Balance clause gap detected at position {0,1,2}. Balance clauses must be specified sequentially without gaps.	You attempted to create a clause for your DNS rule that is out of sequence. The DNS Rule Builder provides options for three balance clauses, which must be created in order, with no gaps between clauses. For example, if you are using only one balance clause, it must appear in the first position. It cannot be listed in the second or third positions with the first position left blank.	Rearrange your balance clauses in the DNS Rule Builder so that they are listed in the proper order with no gaps between them.
A DNS rule named DNS_Rule_name already exists. Name must uniquely identify a DNS rule.	You attempted to assign a name to the DNS rule that is already assigned to another rule. DNS rule names must be unique.	Assign a rule to the name that is not already being used and then save the rule.
Balance clause 1/2 cannot be sticky because clause number 0/1 is not sticky.	You attempted to enable sticky on Balance Clause 2 without first enabling sticky on Balance Clause 1. The GSS prevents you from enabling sticky on Balance Clause 2 if you do not first enable sticky on Balance Clause 1. This restriction is also true if you attempt to enable sticky on Balance Clause 3 without first configuring sticky on Balance Clause 2.	Enable sticky for Balance Clause 1 before enabling sticky for Balance Clause 2. If necessary, enable sticky for Balance Clause 2 before enabling sticky for Balance Clause 3.
Invalid balance method. Proximity can not be enabled for balance method Hashed.	You attempted to specify the hashed balance method for an answer group in a balance clause that has proximity enabled. The GSS does not support proximity in a DNS rule with the hashed balance method.	Choose a different balance method for the answer group from the Select Balance Method drop-down list.

KeepAlive Error Messages

Table A-5 lists the potential error messages that may appear when configuring keepalives.

Table A-5 Keepalive Error Messages 

Error Message	Description	Recommended Action
Invalid CAPP hash secret. Secret must be entered.	You attempted to create a KAL-AP keepalive using a CAPP hash secret but have not specified a secret in the field provided.	Enter a CAPP hash secret of no more than 31 characters in the field provided.
Invalid CAPP hash secret. Secret length must not exceed 31 characters.	You attempted to create a KAL-AP keepalive using a CAPP hash secret but have specified a secret that is too long.	Enter a CAPP hash secret of no more than 31 characters in the field provided.
Invalid HTTP HEAD response timeout.	You attempted to specify an HTTP HEAD response timeout that is invalid.	Enter a response timeout between 20 and 60 seconds in the HTTP HEAD response timeout field of the Shared Keepalive details page.
Response timeout must be between 20 and 60 seconds.	You attempted to specify an HTTP HEAD response timeout that is invalid.	Enter a response timeout between 20 and 60 seconds in the HTTP HEAD response timeout field of the Shared Keepalive details page.
Invalid HTTP HEAD destination port. Destination port must be between 1 and 65,535.	You attempted to specify a port number for HTTP HEAD traffic that is invalid.	In the HTTP HEAD destination port field in the Shared Keepalive details page, enter a port number between 1 and 65,535 through which HTTP HEAD keepalive traffic will pass. The default port is 80.
Invalid HTTP HEAD path. Path length must not exceed 256 characters.	You attempted to specify an HTTP HEAD path that is not valid.	Enter a valid path shorter than 256 characters in the HTTP HEAD default path field in the Shared Keepalive details page.
Invalid <keepalive type> minimum probe frequency. Frequency must be between <min> and <max>.	You attempted to specify a minimum probe interval for your keepalive type that is invalid.	Specify an interval (in seconds) within the range specified for that keepalive type in the Shared Keepalive details page. The interval range for the CRA keepalive type is between 1 and 60 seconds. For all other keepalive types, it is between 45 and 255 seconds.
Duplicate keepalive address detected. A keepalive must not be configured to use the same primary and secondary addresses.	You attempted to configure a KAL-AP keepalive that is identical to a keepalive of the same type that already exists.	Configure the KAL-AP keepalive to use a different primary and secondary address.
Duplicate keepalive primary address '<primaryaddress>' detected. An address can be used by at most one KAL-AP type keepalive.	You attempted to configure a KAL-AP keepalive that uses the same primary IP address as a keepalive of the same type that already exists.	Configure the KAL-AP keepalive to use a primary IP address that is not already being used by another keepalive.
Duplicate keepalive secondary address '<secondary address>' detected. An address can be used by at most one KAL-AP type keepalive.	You attempted to configure a KAL-AP keepalive that uses the same secondary IP address as a keepalive of the same type that already exists.	Configure the KAL-AP keepalive to use a secondary IP address that is not already being used by another keepalive.
HEAD Duplicate keepalive detected. An HTTP HEAD keepalive must not use the same address, destination path, host tag, and port as another HTTP HEAD keepalive.	You attempted to configure an HTTP HEAD keepalive that features an identical configuration to that of another HTTP HEAD keepalive on your GSS network.	Configure the HTTP HEAD keepalive to use a unique configuration of address, destination path, host tag, and port.
Duplicate keepalive detected. An ICMP keepalive must not use the same address as another ICMP keepalive.	You attempted to configure an ICMP keepalive with an IP address that is identical to that of another ICMP keepalive on your GSS network.	Configure the ICMP to use a unique IP address.
Invalid CAPP hash secret. Secret length must not exceed 31 characters.	You attempted to create a KAL-AP keepalive using a CAPP hash secret but have specified a secret that is too long.	Enter a CAPP hash secret of no more than 31 characters in the field provided.
Invalid HTTP HEAD destination port. If specified, destination port must be between 0 and 65,535.	You attempted to specify a port number for HTTP HEAD traffic that is invalid.	In the HTTP HEAD destination port field in the Shared Keepalive details page, enter a port number between 1 and 65,535 through which HTTP HEAD keepalive traffic will pass. The default port is 80.
Invalid HTTP HEAD host tag. Host tag length must not exceed 128 characters.	You attempted to create an HTTP HEAD host tag that is too long.	Enter an HTTP HEAD host tag of no more than 128 characters.

Location Error Messages

Table A-6 lists the potential error messages that may appear when configuring locations.

Table A-6 Locations Error Messages 

Error Message	Description	Recommended Action
The location is still being referenced by other objects and cannot be removed.	You attempted to delete a location that has answers or GSS devices associated with it.	Dissociate any answers or GSS devices from the location and then try again to delete it.
There already exists a location named <name> in region <region> with the same name. Please specify a different location name.	You attempted to create a location within this region when another location with the same name already exists.	Change the name of the location so that it is unique for the region.

Network Error Messages

Table A-7 lists the potential error messages that may appear when configuring the primary GSSM network.

Table A-7 Primary GSSM Network Error Messages 

Error Message	Description	Recommended Action
Maximum number of GSSMs exceeded. A GSS network can contain at most 2 GSSMs.	You attempted to enable a GSSM when there are already two GSSMs enabled on your GSS network.	If necessary, remove your standby GSSM from your GSS network and then try again to enable the GSSM.
The maximum number of <size> <className> has been met.	You attempted to add a resource to your GSS network when the maximum number of that resource already exists.	Remove an existing resource of the same type and then try again to add the new resource.

Owner Error Messages

Table A-8 lists the potential error messages that may appear when configuring owners.

Table A-8 Owners Error Messages 

Error Message	Description	Recommended Action
Invalid owner name. Name must be entered.	You attempted to create an owner without assigning a name to the owner.	Owners must have a unique name. Enter a name for the owner in the field provided and then save the owner.
Invalid owner name. Name length must not exceed 80 characters.	You attempted to assign a name to an owner that is too long.	Assign a name to your owner that is no longer than 80 characters.
An owner named <owner name> already exists. Name must uniquely identify an owner.	You attempted to assign a name to your owner that is already assigned to another owner on your GSS network.	Assign a unique name to your owner.

Proximity Error Messages

Table A-9 lists the potential error messages that may appear when configuring network proximity.

Table A-9 Proximity Error Messages 

Error Message	Description	Recommended Action
Mask: Invalid value 255.255.abc.1. Please enter mask using proper format.	You entered an incorrect global subnet mask in the Global Proximity Configuration details page (Traffic Mgmt tab).	Enter a valid host or network subnet mask. Be sure to enter the subnet mask in either dotted-decimal notation (for example, 255.255.255.0) or as a prefix length in CIDR bit count notation (for example, /24).
Invalid Equivalence window. Equivalence window must be between 0 and 100	You entered an incorrect Equivalence Window value in the the Global Proximity Configuration details page (Traffic Mgmt tab).	Enter an equivalence window value from 0 to 100 percent to specify a percentage value that the GSS applies to the most proximate RTT value (the closest) to help identify the relative RTT values of other zones that the GSS should consider as equally proximate. The default value is 20 percent.
Invalid Entry inactivity timeout. Entry inactivity timeout must be between 15 and 10080	You entered an incorrect Entry Inactivity Timeout value in the Global Proximity Configuration details page (Traffic Mgmt tab).	Enter a value from 15 to 10080 minutes, specified in 5-minute intervals (15, 20, 25, 30, and up to 10080), to configure the maximum time interval that can pass without the GSS receiving a lookup request for a proximity database entry before the GSS removes that entry. The default value is 60 minutes.
Invalid Refresh probe interval. Refresh probe interval must be between 1 and 72	You entered an incorrect Refresh Probe Interval value in the Global Proximity Configuration details page (Traffic Mgmt tab).	Enter a value from 1 to 72 hours to specify the frequency of the refresh probing process to probe and update RTT values for the entries in the PDB. The default value is 8 hours.
Invalid Acceptable RTT. Acceptable RTT must be between 50 and 500	You entered an incorrect acceptable RTT value in either the Global Proximity Configuration details page (Traffic Mgmt tab) or the DNS Rules Builder.	Enter an acceptable RTT value from 50 to 500 ms to specify the value that the GSS uses as an acceptable RTT value when determining the most proximate answer. The default value is 100 ms.
Invalid Acceptable percentage of available zones. Acceptable percentage of available zones must be between 3 and 100	You entered an incorrect proximity acceptable zone percentage in either the Global Proximity Configuration details page (Traffic Mgmt tab) or the DNS Rules Builder.	Enter a percentage of zones from 3 to 100 percent to specify a percentage value that the GSS uses to determine if an acceptable number of zones return valid RTT values. The default value is 40 percent.
Invalid DRP key. Key must have an Id.	You attempted to create a DRP key without an ID value in the Creating New DRP Key details page (Traffic Mgmt tab).	Enter a key identification number from 0 to 255 to specify the ID value used by the GSS. The ID value must be the same between the DRP agent on the Cisco IOS-based router and the GSS.
Invalid DRP key. Key must have a string.	You attempted to create a DRP key without a string in the Creating New DRP Key details page (Traffic Mgmt tab).	Enter a string containing from 1 to 80 uppercase and lowercase alphanumeric characters. The first character cannot be a number. The DRP string must be the same between the DRP agent on the Cisco IOS-based router and the GSS.
Invalid key ID. Key with the ID 'xxx' already exists.	You attempted to create a DRP key that is using an existing DRP key ID.	Specify a DRP key with a different ID in the Creating New DRP Key details page. The ID value must be the same between the DRP agent on the Cisco IOS-based router and the GSS. The range of key identification numbers is from 0 to 255.
Invalid DRP Key Id. DRP Key Id must be between 0 and 255.	You entered an incorrect DRP key ID in the Creating New DRP Key details page (Traffic Mgmt tab).	Enter a key identification number from 0 to 255 to specify the ID value used by the GSS. The ID value must be the same between the DRP agent on the Cisco IOS-based router and the GSS.
Invalid DRP Key String Length. DRP Key String Length must be between 1 and 80.	You entered an incorrect DRP key string in the Creating New DRP Key details page (Traffic Mgmt tab).	Enter a string containing from 1 to 80 uppercase and lowercase alphanumeric characters. The first character cannot be a number. The DRP string must be the same between the DRP agent on the Cisco IOS-based router and the GSS.
Invalid key String. Key String cannot start with a digit.	You attempted to create a DRP key that begins with a number.	Enter a string containing from 1 to 80 uppercase and lowercase alphanumeric characters. The first character cannot be a number. The DRP string must be the same between the DRP agent on the Cisco IOS-based router and the GSS.
Invalid key String. Key String is limited to alphanumeric characters.	You attempted to create a DRP key with non-supported characters.	Enter a string containing from 1 to 80 uppercase and lowercase alphanumeric characters. The first character cannot be a number. The DRP string must be the same between the DRP agent on the Cisco IOS-based router and the GSS.
The maximum of 32 DRP Key has been met.	The primary GSSM GUI supports a maximum of 32 keys.	If necessary, delete one or more DRP authentication keys from the primary GSSM GUI (see Chapter 9, Configuring Network Proximity).
Invalid Zone Index. Zone Index must be between 1 and 32.	You entered an incorrect proximity zone index in the Creating New Zone details page (Traffic Mgmt tab).	Enter an integer from 1 to 32 for the proximity zone Index. There is no default.
Invalid zone name. Zone with index `xxx' already has the name `yyy'.	You attempted to create a proximity zone that is using an existing zone name.	Enter a different description of the proximity zone. Only alphanumeric characters and the underscore (_) character are allowed.
Invalid zone index. Zone with the name `yyy' already has index `xxx'.	You attempted to create a proximity zone that is using an existing index.	Enter a different proximity zone index. Enter an integer from 1 to 32. There is no default.
The maximum of 32 Zones has been met.	The primary GSSM GUI supports a maximum of 32 proximity zones.	If necessary, delete one or more proximity zones from the primary GSSM GUI (see Chapter 9, Configuring Network Proximity).
Invalid probe device address. A probe device with address `1.2.3.4' already exists.	You attempted to create a proximity zone that is using an existing IP address.	In the Probe Device field or the Backup Probe Device field of the Creating New Zone details page (depending on which field generated the error message), enter the correct IP address for the probe device servicing this zone.

Region Error Messages

Table A-10 lists the potential error messages that may appear when configuring regions.

Table A-10 Regions Error Messages 

Error Message	Description	Recommended Action
The region is still being referenced by other objects and cannot be removed.	You attempted to delete a region that is associated with GSSs on your GSS network.	Disassociate the GSSs from the region and then try again to delete the region.
There already exists a region named <region name>. All region names have to be unique.	You attempted to assign a name to the region that is already being used by another region on your GSS network.	Assign a unique name to your region.

Source Address List Error Messages

Table A-11 lists the potential error messages that may appear when configuring source addresses.

Table A-11 Source Address List Error Messages 

Error Message	Description	Recommended Action
Invalid source address block '<block string>'. Address block must specify a host or a network.	You attempted to specify an invalid source address range.	Enter a valid source address or block of source addresses. Source addresses cannot specify a multicast address list.
Invalid source address block '<blockstring>'. Address block must specify a class A, B, or C host or network.	You attempted to specify an invalid source address range.	Enter a valid source address or block of source addresses. Source addresses cannot specify a multicast address list.
Invalid source address list name. Name must be entered.	You attempted to create a source address list without assigning a name to the list.	Enter a name for the source address list in the Name field.
Invalid source address list name. Name length must not exceed 80 characters.	You attempted to create a source address list with a name that is too long.	Enter a valid name for the source address list that has fewer than 80 characters and does not contain spaces.
Invalid source address list name. Name must not contain spaces.	You attempted to create a source address list with a name that contains spaces. Source address list names cannot contain spaces.	Enter a valid name for the source address list that has fewer than 80 characters and does not contain spaces.
This source address list cannot be deleted because it is referenced by <number> DNS rules.	You attempted to delete a source address list that is referenced by one or more DNS rules.	Disassociate your DNS rules from the source address list using the DNS Rule Builder or DNS Rule Wizard and then attempt to delete the source address list again.
A source address list named '<name>' already exists. Name must uniquely identify a source address list.	You attempted to create a source address list using a name that is already being used by another source address list on your GSS network.	Assign a unique name to your source address list that is no more than 80 characters and does not contain spaces.
The maximum number of 30 source address blocks per list has been met.	You attempted to add a source address block to the source address list, when the maximum of 30 source address blocks has already been added to the list.	Remove an existing source address block, or create a source address list for the source address block that you wish to add.

Sticky Error Messages

Table A-12 lists the potential error messages that may appear when configuring DNS sticky.

Table A-12 Sticky Error Messages 

Error Message	Description	Recommended Action
Mask: Invalid value 255.255.abc.1. Please enter mask using proper format.	You entered an incorrect global subnet mask in the Global Proximity Configuration details page.	Enter a valid host or network subnet mask. Be sure to enter the subnet mask in either dotted-decimal notation (for example, 255.255.255.0) or as a prefix length in CIDR bit count notation (for example, /24).
Invalid Sticky inactivity timeout. Sticky inactivity timeout must be between 15 and 10080.	You entered an incorrect Entry Inactivity Timeout value in either the Global Sticky Configuration details page or in the DNS Rules Builder	Enter a value from 15 to 10080 minutes, specified in 5 minute intervals (15, 20, 25, 30, up to 10080), to configure the maximum time interval the maximum time period that an unused answer remains valid in the sticky database. The default value is 60 minutes.
Invalid Sticky inactivity timeout. Sticky inactivity timeout must be a multiple of 5.	You entered an incorrect Entry Inactivity Timeout value in either the Global Sticky Configuration details page or in the DNS Rules Builder	Enter a value from 15 to 10080 minutes, specified in 5 minute intervals (15, 20, 25, 30, up to 10080), to configure the maximum time interval the maximum time period that an unused answer remains valid in the sticky database. The default value is 60 minutes.
Invalid encryption string. Its length must not exceed 32 characters.	You entered an incorrect encryption string in the Global Sticky Configuration details page (Traffic Mgmt tab).	Enter an unquoted text string with a maximum of 32 characters and no spaces as the encryption string used to authenticate communication between GSS peers in the mesh to prevent unauthorized device access.

User Account Error Messages

Table A-13 lists the potential error messages that may appear when configuring a user account.

Table A-13 Primary GSSM User Account Error Messages 

Error Message	Description	Recommended Action
There already exists a user account named <user name>. All user accounts must have a unique username.	You attempted to create a user account with a name identical to that of an existing account.	Assign your new user account a unique name. See the Cisco Global Site Selector Administration Guide for details.
You cannot delete the account with username 'admin'. This account must exist.	You attempted to delete the administrator user account.	The primary GSSM GUI restricts you from deleting the administrator account. See the Cisco Global Site Selector Administration Guide for details.

User Views Error Messages

Table A-14 lists the potential error messages that may appear when creating a user view.

Table A-14 Primary GSSM User Views Error Messages 

Error Message	Description	Recommended Action
This view cannot be deleted because it is referenced by [number] user(s).	You attempted to delete a user view that is assigned to one or more user accounts.	Access the Modifying User details page and change the assigned view to View All. See the Cisco Global Site Selector Administration Guide for details.
Invalid view name. Name must be entered.	You entered an incorrect view name in the Create User Views details page or the Modify User Views details page.	Enter a valid view name. View names can be from 1 to 80 alphanumeric characters and cannot contain spaces. See the Cisco Global Site Selector Administration Guide for details.
Invalid view name. Name length must not exceed 80 characters.	You entered an incorrect view name in the Create User Views details page or the Modify User Views details page.	Enter a valid view name. View names can be from 1 to 80 alphanumeric characters and cannot contain spaces. See the Cisco Global Site Selector Administration Guide for details.
A view named [name] already exists. Name must uniquely identify a view.	You entered a duplicate view name in the Create User Views details page or the Modify User Views details page.	Enter a valid view name. View names can be from 1 to 80 alphanumeric characters and cannot contain spaces. See the Cisco Global Site Selector Administration Guide for details.
The maximum number of 500 owners per view has been met.	The primary GSSM GUI supports a maximum of 500 owners in a custom user view.	If necessary, delete one or more owners previously assigned to the custom view. See the Cisco Global Site Selector Administration Guide for details.
The maximum number of 1000 locations per view has been met.	The primary GSSM GUI supports a maximum of 1000 locations in a custom user view.	If necessary, delete one or more locations previously assigned to the custom view. See the Cisco Global Site Selector Administration Guide for details.
The maximum number of 100 answers per view has been met.	The primary GSSM GUI supports a maximum of 100 answers in a custom user view.	If necessary, delete one or more answers previously assigned to the custom view. See the Cisco Global Site Selector Administration Guide for details.
The maximum number of 100 keepaives per view has been met.	The primary GSSM GUI supports a maximum of 100 keepalives in a custom user view.	If necessary, delete one or more keepalives previously assigned to the custom view. See the Cisco Global Site Selector Administration Guide for details.