Configure Business Locations with a Device Attribute (Legacy Location Mapping)

Location mapping determines the location name (site, office or campus) of a monitored device as it is displayed in the dashboards. The system supports two ways to configure location mapping:

  • Use the latest site-based method with Aternity Agent 9.x to automatically map location names from the Site in your Microsoft Active Directory (AD) in a quick one-step mapping. It uses your AD's location names, so if your company changes its structure or topology in the AD, the locations automatically update with it.

    For more information, see Configure Business Locations (Site-Based Location Mapping).

  • The legacy method for location mapping assigns a location from a device attribute, like its subnet, which should change whenever the device connects from a different location, though subnets are less easy to maintain. This method requires two separate mappings: first from an attribute (like a subnet) to a location name, then a separate mapping from locations to their city, state, country, region and coordinates.

    This article describes configuring location mapping using the legacy method, specifically using subnets as the example.

Legacy location mapping requires two mappings: subnet to location, and location to geographic location

You should continue using the legacy (subnet-based) location mapping if:

  • Your devices run Aternity Agent version 8.x or older.

  • Your mobile devices do not report their site.

If you want to upgrade from the legacy location mapping to the newer site-based method, see Upgrade Location Mapping From Legacy to Site-Based.

Before you begin

Before configuring the legacy location mapping, verify the following:

  • Verify the access rights and privileges for your user includes Edit Advanced Configuration privileges.

  • Decide on the device attribute which would determine its location. This attribute must be different in each of your corporate locations. With legacy location mapping, you can use the subnet of the device, or its hostname, or another device attribute. This article uses the example of mapping a location using a device's subnet.

Procedure

  1. Step 1 Open a browser and log in to Aternity.
  2. Step 2 Select the Gear Icon > End Point Attributes.
    Access the end point attributes window
  3. Step 3 Select Location in the left hand pane and verify that Data collection method is CSV mapping.

    If the Data collection method is Not Assigned, or to check that the data collection is properly configured, select the Data Collection tab.

    View the location settings
  4. Step 4 Configure the system to use a CSV mapping file, which maps the device's attribute to business location names.
    Select CSV Mapping as your data collection
    Field Description
    Collection Method

    Select CSV Mapping to point the system to a CSV file which maps the attribute of the device to location names.

    Source End Point attribute

    Select the device attribute which you want to map to the location name. For example, select Subnet to map the device's subnet to its location name.

    You could map a different attribute to the location. For example, your devices' hostnames may be dependent on their location, if, say, all the computers in the head office have a hostname beginning with HQ. For more information on mapping other attributes, contact customer services.

    Matching method

    If you are mapping a device's subnet to the location name, select Subnet Range.

    If you are mapping a different device attribute, like a device's hostname, choose Case Insensitive to match the value in the CSV file to the device attribute regardless of upper or lower case.

    For example, if you enter mike-pc in a row in the CSV, a device whose hostname is Mike-PC, with different upper and lower case, would match this rule and apply the location name in that row.

    Missing value replacement

    Enter the text to display in the dashboards when the device's attribute did not match any of the existing business locations. For example, Off-Site or Not Mapped.

    Ignored values

    Enter the subnet addresses which Aternity should ignore (Not Mapped), like home networks of employees. Select and add an ignored subnet. Select to delete your ignored values.

  5. Step 5 Select Apply.
  6. Step 6 Download the existing location mapping file which the system currently uses to assign subnets to location names.

    Select Include unmapped values to ensure that the downloaded file includes all the subnets reported by devices running the Aternity Agent, including those not yet mapped to a location name.

    Select Download Mapping to download and save the existing location mapping csv file.

    Download the current mapping file used by the system to map subnets to location names
  7. Step 7 Open the downloaded location mappings file.

    If you downloaded it from version 9.x Aternity, you can edit the file in Microsoft Excel. If you use version 8.x, you must edit it in Notepad or Notepad++, or another editor which supports explicit encoding definitions.

    Important

    If you use Aternity version 8.x or older, saving the file in Excel's CSV format would corrupt the file's delimiters and unicode characters. Only use Excel if you downloaded it from Aternity version 9.x.

    If your device attribute is the subnet range, the file lists each detected subnet range on a separate line, where the IP address of a range is formatted as a subnet mask, showing the start of the range, then a slash ('/'), then the number of bits in the address which acts as the subnet mask. For example, in IPv4, where an IP address is 32-bit (4 x 8 bits), if you specify a subnet mask for the first 24 bits of the address, it covers everything except the last (8 bit) number. So a range from 110.1.0.0 until 110.1.0.255 is formatted as 110.1.0.0/24

    Downloaded subnet to location CSV file before editing
  8. Step 8 Add a location name to each subnet range, as you want it to appear in the dashboards, by first adding a comma (,) with no space before or after, and then the name of the location.

    For example, if the system recognized a subnet whose range is from 110.1.0.0 until 110.1.0.24, and you want to assign it to a location called Sydney Building, you can change the line in the file from:

    110.1.0.0/24

    to:

    110.1.0.0/24,Sydney Building
    Edit the current mapping file to add a location name to each subnet range
  9. Step 9 Select Upload New Mapping > Browse to upload the edited mapping file to Aternity.
    Upload the mapping file with location names associated with subnet ranges

    You have now completed the first stage of the mapping: from device attribute to location name.

  10. Step 10 To assign geographical data (city, state, country, region and coordinates) to each location name, select the Gear Icon > Settings > Location > Location Mapping.
    Access the configuration of phase two of legacy location mapping
  11. Step 11 Download the system's currently used legacy location mapping file, which maps location names to their physical locations (country, state, city, region, coordinates).

    In the Download Current Mapping section, select Include unmapped values so the file includes all detected location names, including those not yet mapped to a geographic location.

    Then select Download Mapping to save the existing file locally for editing.

    Download the existing location mapping file
  12. Step 12 Open the downloaded file containing the geographical location of each office name.

    If you downloaded it from version 9.x Aternity, you can edit the file in Microsoft Excel. But if you use version 8.x, you must edit it in Notepad or Notepad++, or another editor which supports explicit encoding definitions.

    Important

    If you use Aternity version 8.x or older, saving the file in Excel's CSV format would corrupt the file's delimiters and unicode characters. Only use Excel if you downloaded it from Aternity version 9.x.

  13. Step 13 Associate a location name to its geographical location.

    The first line in the CSV file represents the column headings, separated by commas. Use this format to add new lines, where each line associates (maps) a location name to its geographical position.

    Important

    Do not edit the header row (first line in the file).

    Assign business locations to their geographic locations in the location mapping file

    For each new line, add the following fields, separated by a comma (no spaces either side).

    Field Description
    Location

    The location name to associate with the geographical data in the remaining columns.

    Note

    This value must be identical to a business location you defined for a subnet in the Subnet_to_Location_mapping.csv file earlier in this procedure.

    Country

    (Mandatory if empty) Enter the country name for this site which matches exactly the format used in the MaxMind country database. This information is then used to display data per country in the dashboards.

    State

    (Mandatory if empty) Enter the name of the state for this site, used for displaying data per state in the dashboards.

    City

    (Mandatory if empty) Enter the name of the city for this site, used for displaying data per city in the dashboards.

    Location Latitude

    (Optional) Enter the latitude coordinate of this site in degrees North, between -90 and 90, for accurate placement on the dashboards' geographic maps. For example 51.377802.

    Tip

    Use an online map to pinpoint a site's coordinates. If your spelling of the Country, State and City is recognized, the system automatically adds the city's geolocation coordinates.

    Location Longitude

    (Optional) Enter the longitude in degrees East, between -180 and 180, for accurate placement on the dashboards' geographic maps. For example -71.616.

    Tip

    Use an online map to pinpoint a site's coordinates. If your spelling of the Country, State and City is recognized, the system automatically adds its geolocation coordinates.

    Region

    (Optional) Enter a label which groups together locations in the way you see fit. For example, a region can be as broad as APAC or as specific as NW England.

    If you do not add this data, the region appears in dashboards as Not Mapped.

    If you have several company locations at the same address, for example on different floors of the same building, they can appear in the dashboards as different locations so long as they belong to different subnets. However, on a visual map, obviously, they will appear as one overlapping the other.

  14. Step 14 Upload your edited location mapping CSV file into Aternity.

    Browse for the location mapping csv file you edited and upload it into Aternity. It replaces the previous version of the mapping file.

    Upload the edited mapping file which assigns office names to their geographic locations