Showing results for 
Search instead for 
Did you mean: 

Updating the Brocade vTM GeoIP database

This document covers updating the built-in GeoIP database. See TechTip: Extending the Brocade vTM GeoIP database for instructions on adding custom entries to the database.


Brocade vTM GeoIP Update package.


Brocade now provides a GeoIP Update package, available in the Related Software section of the portal. This package is updated approximately monthly, and its version number can be compared with the GeoIP database version in $ZEUSHOME/zxtm/etc/geo/version.


To use this update package:

  1. Download the GeoIP Update from and navigate to:
    Downloads > Application Delivery Controllers > Virtual Traffic Manager > Related Software
        > Brocade Virtual Traffic Manager GeoIP Update 20160907
  2. Upload the package to the target vTM instance (System > Traffic Managers > Upgrade).
  3. Click 'Install this upgrade'. vTM applies the update and restarts.
  4. Verify the audit log shows the upgrade was successful.
  5. Repeat 2-4 for other cluster members.


On our AMI on EC2 you don't have the Upgrade UI option, so you must copy the upgrade package to the instance, log in and run /opt/zeus/zxtm/bin/upgrade. e.g.:

/opt/zeus/zxtm/bin/upgrade install geoip_update_20160907.tgz


If you upgrade to a new version of the Traffic Manager it will switch to the GeoIP database version included in that version of the Traffic Manager. If you had previously updated to a later version of the database you will need to reapply the GeoIP update.


Using the MaxMind GeoIP City database.


The GeoIP database shipped with Brocade vTM is based on the MaxMind GeoLite City database. MaxMind also produce a commercially licensed database of IPv4 locations, GeoIP City, which is more detailed. If you are using version 9.6 or later you can switch to using this database.


First take a copy of the folder $ZEUSHOME/zxtm/etc/geo and the file $ZEUSHOME/zxtmadmin/lib/perl/Zeus/ZXTM/

You can switch back to to original GeoIP database by restoring these and restarting the traffic manager.


  1. Download the "CSV with IP addresses in numeric format and separate table for locations" version of the GeoIP City database.
  2. Unzip the resulting archive. This will create a folder such as GeoIP-134_20140218 containing two CSV files with names like GeoIPCity-134-Blocks.csv and GeoIPCity-134-Location.csv.
  3. Download the country codes file from
  4. Download the region codes file from
  5. Run the conversion script, specifying paths to the 4 CSV files in the order: locations file, blocks file, country codes, region codes. e.g:
    $ZEUSHOME/zxtm/bin/ GeoIP-134_20140218/GeoIPCity-134-Location.csv GeoIP-134_20140218/GeoIPCity-134-Blocks.csv iso3166.csv region.csv
  6. This will create a folder called output containing:
    • base_locations.txt
    • country_codes.txt
    • ip-to-location.bin
    • region_codes.txt
    It will also report on IP ranges whose Region Code is not found in the regions file.
    These will return a region code, but will return an empty string when asked for the region name.
  7. Overwrite $ZEUSHOME/zxtmadmin/lib/perl/Zeus/ZXTM/
    with a copy of if they differ.
  8. Replace the contents of $ZEUSHOME/zxtm/etc/geo with copies of the other files in the output folder
  9. Restart the traffic manager
  10. Repeat steps 7-9 for other cluster members


If you upgrade to a new version of the Traffic Manager, you will need to reapply these changes.

Version history
Revision #:
1 of 1
Last update:
‎03-27-2014 05:44:AM
Updated by:
Labels (1)