Branch Mapping
    • Dark
      Light
    • PDF

    Branch Mapping

    • Dark
      Light
    • PDF

    Article Summary

    Click on the Branch Mapping tab to access the Branch Name Mapping Settings page, where you can configure a list of IP subnets utilized on your network and map them to names of geographical locations, buildings or organizational branches. On the basis of this configuration, ControlUp assigns a source branch name to every user session and populates the Branch Name column with this branch name.

    For example, in an organization in which the New York office uses the 10.1.0.0/16 subnet and the Chicago office uses the 10.2.0.0/16 subnet, the mapping table should be configured to map those subnet addresses to the branch names. As a result, the Branch Name column of the sessions view will be populated with the value of “New York” for all user sessions established from client IP addresses in the 10.1.0.0/16 range, and with the value of “Chicago” for the 10.2.0.0/16 range.

    The list of subnets and branch names can be configured manually or imported using a CSV file by clicking the Import button. Here’s an example content of a supported CSV file for reference:

    Name,Site
    10.1.0.0/16,Chicago
    10.2.0.0/16,Chicago
    10.3.0.0/16,Amsterdam
    10.1.3.100-10.1.3.200,Servers Subnet
    10.1.4.111,Test Workstation

    If your Active Directory has subnet objects already linked to the sites representing the geographical topology of your organization, you can use the Active Directory Sites and Services to export a CSV file which can be imported directly into ControlUp. To do so, perform the following steps:

    1. Open Active Directory Sites and Services
    2. Expand the Sites container in the tree view
    3. Right-click the Subnets container and click Export List…
    4. Save the file as “Text (Comma Delimited) (*.csv)”
    5. Open the Branch Mapping tab of the Settings window in ControlUp
    6. Click Import
    7. Browse to the file exported in the steps above

    Removed AD Dependency
    From version 9.0, you can deploy ControlUp Monitors on machines that are not joined to a local Active Directory (AD) domain. For details, see Removed AD Dependency for Monitors.

    In case the client IP address does not belong to any of the subnets configured in the mapping table, the Branch Name column can be left empty or populated with a custom value. This behavior can be configured using the “Unrecognized IP Addresses” area in the Branch Mapping tab of the Settings window.


    Was this article helpful?