[Netscaler] :: getting following error on nsmap test: 'nsmap: Error getting location. ErrorCode: 0x75b'
Article ID: CTX458742
Updated On:
Description
> Netscaler Admin added a static custom entry using below command to ADC Geo DB:
add location 103.150.209.0 103.150.209.255 "Asia.PK.Punjab.*.*.*" -longitude 74 -latitude 31
>To validate, if we run nsmap utility, we get following error:
nsmap -d -t
Enter IP address to test or q to exit: 103.150.209.142
nsmap: Tue Apr 12 16:11:59 2022: No suitable IP range found while searching for 103.150.209.142
nsmap: Error getting location. ErrorCode: 0x75b
Enter IP address to test or q to exit: 103.150.209.1
nsmap: Tue Apr 12 16:12:22 2022: No suitable IP range found while searching for 103.150.209.1
nsmap: Error getting location. ErrorCode: 0x75b.
Resolution
>To validate if static custom entry is successfully added, use below options:
a: Use show location command as below on netscaler CLI:
> show location
1) IP from 103.150.209.0 IP to 103.150.209.255
Continent.Country_Code.Subdivision_1_Name.Subdivision_2_Name.City.Organization =
Asia.PK.Punjab.*.*.*
Coordinates: 74 degrees east, 31 degrees north
Done
b: Run 'show location parameter command below and after adding entry. 'Current Custom Entry' counter should increment.
Example:
Before adding customer entry:
> show locationparameter
Static Proximity
----------------
Database mode: File
Context: geographic
Qualifier 1 label: Continent
Qualifier 2 label: Country_Code
Qualifier 3 label: Subdivision_1_Name
Qualifier 4 label: Subdivision_2_Name
Qualifier 5 label: City
Qualifier 6 label: Organization
IPv4 Location File
Location file (format: netscaler):
/var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB_IPv4
Flushing: Idle; Loading: Idle
Lines: 2650916 Warnings: 0 Errors: 0
Current static entries: 2650909 Current custom entries: 0
After adding Custom Entry:
> show locationparameter
Static Proximity
----------------
Database mode: File
Context: geographic
Qualifier 1 label: Continent
Qualifier 2 label: Country_Code
Qualifier 3 label: Subdivision_1_Name
Qualifier 4 label: Subdivision_2_Name
Qualifier 5 label: City
Qualifier 6 label: Organization
IPv4 Location File
Location file (format: netscaler):
/var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB_IPv4
Flushing: Idle; Loading: Idle
Lines: 2650916 Warnings: 0 Errors: 0
Current static entries: 2650909 Current custom entries: 1
>It only works with the default location database.
Hence behavior seen here is expected
a: Use show location command as below on netscaler CLI:
> show location
1) IP from 103.150.209.0 IP to 103.150.209.255
Continent.Country_Code.Subdivision_1_Name.Subdivision_2_Name.City.Organization =
Asia.PK.Punjab.*.*.*
Coordinates: 74 degrees east, 31 degrees north
Done
b: Run 'show location parameter command below and after adding entry. 'Current Custom Entry' counter should increment.
Example:
Before adding customer entry:
> show locationparameter
Static Proximity
----------------
Database mode: File
Context: geographic
Qualifier 1 label: Continent
Qualifier 2 label: Country_Code
Qualifier 3 label: Subdivision_1_Name
Qualifier 4 label: Subdivision_2_Name
Qualifier 5 label: City
Qualifier 6 label: Organization
IPv4 Location File
Location file (format: netscaler):
/var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB_IPv4
Flushing: Idle; Loading: Idle
Lines: 2650916 Warnings: 0 Errors: 0
Current static entries: 2650909 Current custom entries: 0
After adding Custom Entry:
> show locationparameter
Static Proximity
----------------
Database mode: File
Context: geographic
Qualifier 1 label: Continent
Qualifier 2 label: Country_Code
Qualifier 3 label: Subdivision_1_Name
Qualifier 4 label: Subdivision_2_Name
Qualifier 5 label: City
Qualifier 6 label: Organization
IPv4 Location File
Location file (format: netscaler):
/var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB_IPv4
Flushing: Idle; Loading: Idle
Lines: 2650916 Warnings: 0 Errors: 0
Current static entries: 2650909 Current custom entries: 1
Problem Cause
>nsmap utility does not look at custom location entries.>It only works with the default location database.
Hence behavior seen here is expected
Was this article helpful?
Yes
No
Powered by
