1. Working Map Overview - What This Training Will Accomplish

Intermapper is a powerful network monitoring system. When you install it, you will be able to:

Monitor nearly everything on a network.
Detect outages and performance problems on servers, applications, and other devices.
See traffic, high error rates, and performance problems in a graphical view.
Get alerts about those problems via sounds, e-mail, pages, text/SMS, and more.
Display NetFlow, JFlow, CFlow and sFlow traffic statistics to see who’s generating the traffic.
Show Layer 2 interconnections, so you can see what's on each switch port, as well as Layer 3 connections between routers.
View web-based reports of historical information, outages, traffic, etc.

The basic window of Intermapper is the map.

It shows a graphical representation of all the equipment on your network. Intermapper continually queries the devices shown on a map to determine their health. If it detects a problem, it changes the color of the icon or rectangle representing that device to indicate the problem. The map shows the interconnections between devices, and documents your network automatically.

2. Why SNMP?

Overview of Benefits

Intermapper relies heavily on SNMP to collect relevant information about the equipment on your network. You don’t have to know much about SNMP to use Intermapper, but here’s a quick overview.

SNMP (the “Simple Network Management Protocol”) is an international standard that allows a program (like Intermapper) to retrieve certain operational statistics or values from equipment. Most high-end network equipment such as routers, switches, environmental sensors, etc. uses SNMP (“speaks" it), and a wide variety of other equipment does too.

SNMP is a standard - SNMP-speaking devices are generally easy to add to a network monitoring solution. For example, virtually all SNMP-speaking equipment will give information about traffic flowing through each of the interfaces/ports, errors, uptime, and a number of useful data points. Many vendors also have private sets of data (MIBs) that describe additional metrics that are available.

SNMP Versions - There are three versions of SNMP: v1, v2c, and v3. These all rely on configuring the physical device(s) on the network to use certain credentials before they will respond with data. Intermapper hides most of the details for you.

The community string - Both SNMPv1 and SNMPv2c use a single “community string” as a credential. This is best thought of as a password that you provide when adding a device. Intermapper sends along the community string in the query, and if it matches the device’s configuration, Intermapper receives the response. (If the community string doesn’t match, the device remains silent and does not respond.

SNMPv3 is more secure - SNMPv3 uses strong encryption: your network administrator will tell you what encryption and credentials to use.

3. Pre-Installation Checklist

The Importance of Being Prepared

A little preparation before the installation and configuration will save a lot of time. If you have some basic information at your fingertips on how you will be using your new network monitoring solution, the deployment process will not be sidetracked as you try to find information or make decisions that could have been made in advance. Answer the following questions that are relevant to your network.

Primary goals - What are your primary goals for using Intermapper?
Other networking tools - What other network management/troubleshooting tools do you use?
Network Structure - What is the structure of your network? Is it a flat network or multi subnet network? Multi location? If multi location, is each location behind a firewall? In other words, is this a multi-server license installation or a single server installation? If the former, then there is a real need for Intermapper RemoteAccess.
How many copies of Intermapper do you need and how many devices for each license? How many copies of Intermapper RemoteAccess do you need? Will these be pooled with the Intermapper server for shared access or independent installations?
What OS will you be installing Intermapper on? If you are intending to run Intermapper Flows you should check the supported operating systems before installing Intermapper. E.g. Do not use Windows 2000 for running Intermapper on if you intend to install Intermapper Flows too.
Identify all the servers and computers that will be needed for the installation of Intermapper and Intermapper RemoteAccess.
What do you need to monitor? Do you need to monitor work stations or just routers, switches and servers?
How many community strings are there? (Intermapper only finds the devices one community string at a time).
Are there any firewalls to be configured to allow Intermapper to access parts of the network?
How many people will need access to Intermapper? Via the web and/or via Intermapper RemoteAccess?
What access permissions will they have? Administrative, read/write, or read only?
Is there an existing directory of user names and passwords? (Intermapper can authenticate against an existing directory.) If not draw up the list.
Who is going to receive notifications/alerts, how, and when? (You can escalate sending notifications and can also send them to groups of people). Draw up the schedule. Think of shifts and teams.
What devices need alerts? For which network devices do you need to configure notifications, to whom, when, and for what criteria?
What information do you need Intermapper to monitor per device? i.e. What probe should be set? HTTP, UPS, Cisco SLA, SNMP Traffic, etc.
SNMP Versions - For SNMP probes should they be set to SNMP v1, v2, or v3?
IPv6 - Do you use IPv6?
Develop a data storage strategy - All charted data is stored in the PostgreSQL database, so that you can write custom reports against that data. Also data can be passed directly to the database via the Data view window. Be very selective in what data you are adding to the database, or you could find the available memory is being used up very rapidly.
Develop an authentication and data storage plan - If you are going to use the Intermapper Authentication Server, and/or the Intermapper Database, you will need to check the Intermapper DataCenter settings and customize to suit your need before you go into ‘production’ mode.
Develop a network discovery plan - How are you going to discover the devices on your network and add them to the network maps? You can use auto discovery, manual entry, importing of devices, or an SNMP/Layer-2 discovery combination. You can discover devices by subnet. Construct a plan before you start.
Develop a mapping hierarchy plan - Do you need to set up a hierarchy of maps? Decide on the hierarchy and make sure you do not ‘loop’ the maps.
Develop a mapping approach - Do you want to show your network as a graphical or physical representation, or both? Do you need help setting up your maps? If you want to show your maps on background images make sure you have already sourced them and adjusted their size in a graphics converter before importing into the Intermapper map. Make sure the image file is not too large.
Using Intermapper with other products - Are you going to use Intermapper with another product? If you are planning to use the Helper App feature to ‘integrate’ with another application, write and test the script in a test environment first.

Notify Network Security

Once you have answered all of the above you are ready to get started. But first, if applicable, notify the network security personnel that you are installing an SNMP based NMS on the network. Choose a sensible time to do the above. For example, do not set up SMS notifications on Friday afternoon and then go on vacation. You could return to an embarrassingly high telephone bill.

Intermapper Flows

We are finding that a lot of people download, and even buy Intermapper Flows without knowing that they have to configure their devices to pass the flows data to Intermapper Flows: (Configure an Exporter to pass flows data to the Collector).

Does your equipment support Flows? Make sure you have equipment that supports NetFlow, sFlow, JFlow, or cFlow. This link contains a list of useful FAQs including Cisco equipment that are configurable for NetFlow: Intermapper Flows and Enabling NetFlow on Cisco equipment
How many exporters do you need? This will vary tremendously. Exporters can be placed to gather Flows data passing to and from the internet. If there is only one gateway router, then 1 exporter will do the job. If you have 10 gateway routers then maybe you would need 10 exporters. You may also want to monitor flows traffic within the LAN, between subnets for example. What file sharing is going on between the dorms in a college, for example.
Plan for Flows traffic. See the FAQs also for: What effect does Intermapper Flows have on server load? How much memory does Intermapper Flows require? How much bandwidth will NetFlow consume? How frequent is the traffic flow?
Plan for Flows data storage. You will need to decide how much space to allocate for storing the NetFlow data and certain performance configuration decisions. These can be set up in: Intermapper Flows Settings / Advanced. Determine how many Flows per hour are being generated and how many days worth of Flows data is being stored in your database.
Verify your OS - The platform choice is somewhat more limited than Intermapper so the OS needs to be verified before installation. Please note that Intermapper Flows does not run on Windows 2000. For small networks, we recommend that Intermapper Flows be installed on the same machine as Intermapper, although it can be configured to operate on a separate server.

4. Intermapper Installation and Configuration

Installing and Launching Intermapper

Get a copy of Intermapper from the Download page, review the Readme file provided, then install it as described below.

No matter which platform you're using, a set of demo maps becomes available when installation is complete and the program is launched. Watch them operate, and experiment with them to see how Intermapper operates. For additional information, see Play with the Demo.

Note: Although many of the features described in this manual are similar between the Mac OS, Windows, and Unix/Linux platforms, there are a few differences. We recommend you read the Readme file on the Download page for information specific to your version.

Intermapper requires Java 1.6 or above. Please install and verify your Java installation before starting your installation of Intermapper.

Mac OS X

Double-click the .dmg file to mount it.
Double-click the Intermapper.pkg icon for the installer and follow the instructions. The Intermapper application starts running when installation is complete.

Windows

Double-click the InstallShield icon for the installer and follow the instructions. The Intermapper application starts running when installation is complete.

Unix or Linux

If you're using Unix or Linux, then read the accompanying ReadMe (also found on the download page) to get instructions for installing on your particular platform.

Note: Intermapper runs as a service/daemon once installed, and is designed to run in the background unless you stop the service from running.

About this Demo

The downloadable version of Intermapper requires a serial number to operate. You can request a free evaluation serial number to get the full functionality for 30 days, including printing and opening saved maps.

If you already have a serial number (because you purchased the software or you received the evaluation serial number), click the blue Enter your serial number now link or the Register button in the window shown at the right. You can then enter your name and serial number. For details about entering your evaluation (or any other) serial number, you can read the Registering your software page.

If you don't have a serial number, click the Request an Evaluation Serial Number link in the window shown above. It will open a web form through which you can request a serial number. We will e-mail you a serial number that allows you to use Intermapper to monitor an unlimited number of devices for 30 days. When you receive the serial number, enter it as described above.

Once you've seen the demo, see Using Intermapper to guide you as you try out Intermapper's features.

About Serial Numbers

When you purchase Intermapper, we will send you a full serial number that unlocks the software permanently.

Intermapper supports a number of different serial number formats. A full serial number - sent to those who purchase the software - will never time out. Once entered, that version of the application will run forever.

Intermapper also supports evaluation serial numbers which allow you to run Intermapper for a certain number of days before it ceases to operate. This gives you an opportunity to try the program without obligation. When a serial number times out, Intermapper simply ceases to operate. It never deletes or alters files on your hard drive.

5. Intermapper Control Center

On Mac OS X, Intermapper installs a Menu Bar Application that gives a summary of Intermapper's status, and allows you to start and stop the Intermapper daemon.

On Windows, Intermapper installs an icon in System Tray (lower right corner) that does much the same thing. It also presents a window to indicate an interesting change in Intermapper's state.

The System Tray Icon and Menu Bar Application are available only on the machine hosting the Intermapper Server.

On Mac OS

The menu bar application has an icon that reflects the most serious state of Intermapper. When the server is not running at all, the Intermapper program icon appears dimmed. The icon will be green, yellow, orange or red, depending on the severity when the server is running.

Open the Intermapper application
Start or Stop the Intermapper server daemon
Open the Intermapper Control Center
Check for software updates

The Intermapper Server Status window shows the server name and version, as well as the current state of the Intermapper server. This window also allows you to start or stop the Intermapper server, or open Intermapper.

On Windows

The Intermapper Control Center application is available on Windows 7 and Windows 2008

It has the same function as the Mac OS X application, but is called from the Window System Tray (lower right corner of the screen).

You can do the following from the Intermapper Control Center:

Choose whether the Windows balloons appear when map status changes.
Start or stop the Intermapper or Flows services.
Open the Intermapper application.
Choose whether to check for software updates automatically.
Check for software updates manually.

You can also access most of these functions from the context menu that appears when you right-click the Intermapper status icon.

Note: When you stop or start a service from the Intermapper Control Center, that states of those services are maintained when you restart the machine.

To open the Intermapper Control Center:

Right-click the Intermapper Control Center icon in the Windows System Tray and choose Show Intermapper Control Center.

6. Automatic Notifications of Updates

Intermapper can automatically check to see if a new version is available for download. This check is performed at startup and again every 24 hours.

If the check has never been run before, Intermapper presents a dialog you can use to disable the automatic checking before it takes place. At any time, you can disable the feature, either by choosing Preferences from the Edit menu, then choosing the Behavior->Version Updates pane, or by opening the Intermapper Control Center. When a new version is available, a message appears, including a link to the new version

When you first start up a Windows version of Intermapper, a message asks if you would like Intermapper to check for new versions. This is the only time it will ask this question. If you answer yes, the check is performed at startup and again every 24 hours.

To enable or disable this feature:

Open Intermapper Control Center
Select or clear the "Automatically check for updates to Intermapper" check box.

Upon detecting that a newer version of the software is available, a dialog box appears, indicating that a newer version is available, and asking if you would like to download the new version.

Click "Yes" to launch a browser with the URL to the new version.

7. System Requirements

Hardware and Software Requirements

Intermapper runs on Windows, Mac OS X; Solaris x86; and various Linux distributions, including Red Hat, Debian, Ubuntu and others.

Intermapper RemoteAccess runs on Mac OS X, Windows, and Unix (including Linux) computers. Java 1.5 or newer required. In general, any computer capable of running Mac OS X, or a 1 GHz Pentium or faster Windows NT/2000/XP/2003 or Linux/Unix computer with 512 MBytes of RAM will serve quite nicely to run Intermapper RemoteAccess.

Intermapper for Mac OS X requires Mac OS X or Mac OS X Server, 10.7 or newer. Any computer that can run this version of Mac OS X will easily handle large maps.
Intermapper for Windows 7/8, Windows Server 2012/2008/2003, and Windows Server 2012 R2 (Note: IPv6 support requires Windows 7, Server 2008, or newer) A Windows computer with at least a 1 GHz Pentium and 512 MBytes of RAM will work well for at least 500 devices. Larger installations will benefit from a faster processor or more RAM.
Intermapper for Linux requires a computer running Red Hat 5/6/7, Ubuntu 10.04/12.04/14.04, Debian 6/7, SuSE 11
Intermapper for Solaris requires Solaris x86 8.0 or newer. Java 1.5 or newer required.

Intermapper Connection Policy

Intermapper allows 200 clients to connect. However, Intermapper does check the serial numbers of paid, full copies of Intermapper RemoteAccess, and will not allow two copies with the same serial number to connect. See also “Understanding Intermapper RemoteAccess Licenses”.

Section 508 Accessibility

For a statement of Intermapper's 508 Accessibility, see Intermapper and Section 508

8. Installing and Configuring Intermapper DataCenter

Intermapper DataCenter is simply a framework for including modules (current and future), such as IM Authentication Server. Installation of Intermapper Datacenter for Mac and Windows is automatic when you install Intermapper. For instructions for installing on Linux or Solaris see the download page at https://www.fortra.com/intermapper/intermapper/current.

Configuring Intermapper DataCenter

Intermapper DataCenter is installed automatically when you install Intermapper. Unless you want to install and run it from another machine, specify an outgoing email server for error and bug reporting or change the logging setup, you do not need to take any steps described in this topic. You may want to specify an email address sending error reports.

To open the Intermapper DataCenter web UI:

From the Reports Server pane of Intermapper's Server Settings window, click Configure...
Go to this URL: https://127.0.0.1:8182/

Note: If this is a fresh installation, Intermapper DataCenter automatically generates an SSL certificate, used to encrypt communication with your browser and the Intermapper server. Because a new certificate is generated for every installation, the certificate cannot be signed by a recognized certificate authority. As a result, your browser may display a message alerting you to an invalid certificate. To avoid seeing the message in the future, choose the option to continue, and tell your browser to add the certificate to its list of trusted certificates.

You can replace the generated certificate with one of your own by visiting the Services List. Click the Change Settings link for the Intermapper DataCenter Daemon, once initial setup is complete.

Setting the Password for the Admin Account

Before you can use Intermapper DataCenter from another machine, you must set the password for the Intermapper DataCenter admin account.

To set the password for the Intermapper DataCenter admin account:

If the welcome page does not appear after you install Intermapper DataCenter, use a web browser to go to https://localhost:8182/. The Intermapper DataCenter Welcome page appears.
Click Continue. The language choice page appears.
Click to choose a language you want to use with Intermapper DataCenter, and click Continue. The Intermapper DataCenter's Admin Account configuration page appears.
In the Password box, enter a password you want to use for the admin account.
In the Confirm Password box, enter the password again to confirm it.
Click Continue. The Intermapper DataCenter Home page appears, with the Apps tab showing.

You are now ready to configure Intermapper Database and Intermapper Authentication Server .

Setting Up Intermapper DataCenter Logging and Event Collection

Intermapper DataCenter can log status information, connection attempts by Intermapper servers, and error information obtained when connecting to directory services. Intermapper DataCenter logs to a file called log/imdc.log within the IMDC install folder (c:/program files (x86)/intermapper/dwf).

To set the logging level:

From the Logging Level dropdown menu, choose the level you want to use.
Click Finish. The Intermapper DataCenter installation is complete.
Click Configure to configure the settings for the Intermapper AuthServer or Intermapper Database.

Setting up Intermapper DataCenter's Error Reporting

Intermapper DataCenter can report problems and send bug reports to Dartware. To do this, you need to specify one or more SMTP hosts and user information.

To set up error reporting:

In the Intermapper DataCenter section of the Intermapper DataCenter home page, click Change Settings. The DataCenter Settings page appears.
In the Primary SMTP section of the Error Reporting section, enter a Host, Port (if different from the default), a valid Username and Password for the email account you want to use to send messages, and a From address for the messages. Enter (optional) SMTP settings for a secondary SMTP host.
To send an E-mail notification when an error occurs in Intermapper DataCenter, click to select the On errors, send E-mail to check box.
To send an email notification to Dartware when an error occurs, click to select the Automatically E-mail bug reports to Dartware check box.
To test your SMTP connection, click Send Test E-mail. A test email message is sent to the specified address.

9. Installing, Configuring and Using Intermapper RemoteAccess

Intermapper RemoteAccess is packaged as a self-extracting installer, which contains the necessary programs and support files.

Installing Intermapper RemoteAccess on Windows

Double-click the file Intermapper_RemoteAccess_Setup_5.4.3.exe and follow the instructions.

Installing Intermapper RemoteAccess on Mac OS X

Double-click on Intermapper_RemoteAccess_5.4.3.dmg to open the disk image. Drag the Intermapper RemoteAccess icon into the Applications folder or onto your Desktop. Double-click on the icon to start Intermapper RemoteAccess.

Installing Intermapper RemoteAccess on Linux/Unix/Solaris

The following command will start the Intermapper RemoteAccess installer:

$ sh ./Install_Intermapper_RemoteAccess_5.4.3.bin

To launch Intermapper RemoteAccess, type:

$ cd Intermapper_RemoteAccess_5.4.3
$ ./intermapper-remoteaccess.sh

Alternatively, if you are using a system that supports the freedesktop.org Desktop icon spec, the installer script should place an icon on your desktop for 'Intermapper RemoteAccess', and double-clicking it should start Intermapper RemoteAccess.

Using Intermapper RemoteAccess

Intermapper can make its maps available to people who are away from the server. They can use a program called Intermapper RemoteAccess to view and configure the server.

Headless permissions options:

To start Intermapper on a headless machine and allow IMRA to connect instead of the local version of the UI, stop Intermapper and restart it using the "-A" option:

/usr/local/bin/intermapperd –A [user]:[password]@[IP]

For instance, if I wanted to allow a user "csw" with a password of "pip13kin" to connect from 192.168.1.180 using IMRA rather than the local UI, I'd do

/usr/local/bin/intermapperd -A csw:[email protected]

Intermapper RemoteAccess's Map List window

Intermapper RemoteAccess is capable of configuring every aspect of Intermapper

Intermapper RemoteAccess Access Permissions

Intermapper's Remote Server allows a user to configure and edit maps on an Intermapper installation from a remote computer. To allow these changes, the Remote Server accepts connections from the Intermapper or Intermapper RemoteAccess application, running on a different computer.

Intermapper always listens for remote connections on its localhost interface, 127.0.0.1. This allows a user to run a copy of the Intermapper RemoteAccess application on the machine that is running Intermapper. For security, Intermapper refuses all Remote Server connections from non-localhost addresses by default to prevent unauthorized configuration.

To configure Intermapper to accept connections from remote computers, you must give varying degrees of access by IP address or by username and password. There are several steps you must perform from the Intermapper GUI. These are described below:

Use the Remote Server pane of the Server Settings to add an “Allow…” rule for the address(es) you wish to permit to connect
Set a password on the Admin account, using the Users pane of the Server Settings.
Add any other user who may sign in
Ensure that the host machine’s firewall allows port 8181 (or whichever port you choose for the RemoteAccess protocol).

Unlike the Telnet and Web servers, you cannot start or stop the Remote Server. You configure the Remote Server using the Remote Server settings panel of the Server Configuration section, found in the Server Settings window, as shown below:

To configure the Remote Server:

From the Edit menu, choose Server Settings... The Server Settings window appears.
In the Server Configuration section, click Remote Server. The Remote Server panel appears.

Enter a TCP port number, or use the default value.
To configure access to the Remote Server, click Add... to add addresses to the Remote Server firewall.
To see a list of clients connected to the server, click Show Connected Clients. (See below)
If you want entries from this server to be sent to a different log file, choose a log file from the Send log file entries to dropdown menu. For more information on log files, see Log Files.

Note: The Server Settings window is available only to users who have administrator privileges.

Note to Windows users: By default, XP SP2 and Vista both have significant firewalling turned on. You will need to create exceptions ("poke holes") in the firewall in order to use the remote server, web server, telnet server, or DataCenter server as well as to monitor SNMP traps.

Users and Groups

Use the Users panel of the Server Settings window to add and edit users and groups, to assign users to groups, and to assign privileges and access to maps.

Note: The Server Settings window is available only to users who have administrator privileges. (Pg 1)

The Users Panel

Use the Users panel to maintain the list of users and groups allowed to access the various servers.

To add a user, click New User....
To add a group, click New Group...
To remove a user or group, click to select the user or group, then click Remove.
To edit a user or group's information, click to select the user or group, then click Edit...
To use the Intermapper Authentication server, select the Use IM Auth Server check box. Click Configure... to open the Intermapper DataCenter to set up the IM Auth Server.
To use an Authentication Server on another computer, click Use Remote Auth Server...

The example below shows a typical user and group configuration in the Users panel of the Server Settings window.

What are Users and Groups?

User
An individual identified by a user name and password, or identified automatically from a clients' IP address or range.

Group
A collection of users. A group can be given permissions to access certain servers or maps, and may be given different levels of access for a server or map.

Setting up Users and Groups

Creating a New User

To create a new user:

Click the New User... button. The User Information dialog appears, as shown in the two examples below.
Enter the name and password for the new user in the Name and Password text boxes.
or
Omit the password and enter an IP address range in the Automatic Login text box
or
Select the Use External Authentication check box, and enter the username used by the external authentication server. No password is necessary; authentication is performed by the external authentication server

How Automatic Login Works

If a connection arrives from an address that matches the Automatic Login address, the person is automatically logged in as the specified user.
If you supply both the password and automatic-login address, the person is logged in automatically from the specified address, but must supply a password when connecting from other addresses.
Automatic-login addresses should be unique between users; the resulting Login name is not guaranteed if two automatic-login addresses are the same.
For more information see Controlling Access To Your Server.

Creating a new user.

These two examples show two different users. 'Fred Flintstone' must log in with a name and password, and 'Tom Terrific' is automatically identified when connecting from IP address 192.168.*.*.

Editing User Information

To edit the information about a user:

In the user list, click to select the user you want to edit.
Click Edit... or double-click the user entry. The User Information dialog appears, containing information for the selected user.

Managing Users and Groups

A group is a collection of users, all of whom have the same set of permissions.

New group window. Enter the name
of the new group in this window.

To create a new group:

Click the New Group... button. The Group Information dialog appears, as shown above.
Enter the name of the new group.
Click OK. The new group appears in the User list.

Adding and Removing Group Members

To view the users in a group:
Click the plus sign (+) to the left of the group to expand it.

To add a user to a group:
Click and drag the user's entry to the group entry. The user appears in the list of users for that group.

To remove a user from a group:

Expand the group list to view the users in the group.
Click the entry for the user you want to remove, and click the Remove button. A confirmation dialog appears.
Click OK. The user is removed from the group.

Note: When you remove a user from a group, the user definition is removed only from the group, not from the user list. To remove a user completely from the list and all groups, see Removing Users and Groups below.

Removing Users and Groups

To delete a user or group completely:

Click to select the user you want to remove.
Click the Remove button. A confirmation dialog appears.
Click OK to confirm. The user or group entry is removed from the list.

Note: The Administrators group is a special group that is always present, and cannot be removed.
Note: The FullWebAccess group is a special group you define. If present, its members can view all web pages.
Note: The FullLogAccess group is a special group you define. If present, its members can view all log files.
Note: The FullTelnetAccess group is a special group you define. If present, its members have full access to the Telnet server.

Note: The FullLayer2Access group is a special group that you define. If present its members will be granted admin status for the purposes of administering Layer 2. It will not affect admin status for any other aspect of Intermapper.

Configuring the Intermapper Authentication Server

Click the Use Remote Auth Server... button to connect to an Intermapper Authentication Server installed on a different machine from Intermapper. For more information, see Authentication Server.

Note: If the Intermapper Authentication Server is installed on the same machine as Intermapper, you need only check the Use IM Auth Server check box. The default server and port are used, and there is no need to enter a name or password.

Importing Users and Groups

Use the Import button to upload a file containing data for users and groups. For information on importing data, see Importing Data. For information on the User/Group data structure, see User Attributes.

Controlling Access to a Map

You can use the Map Access panel of the Server Settings window to authorize access to a map to one or more users or groups.

Note: All individuals in the Administrators group have access to all maps.

The Map Access Panel

Intermapper lets you control the access rights to each map in two ways:

Control access by user - View each user's rights to a particular map
Control access by map - View each map's access rights for a particular user

The top example shows the list sorted per-user: it shows the rights that Alan Average has for each of the maps. The bottom example shows the list sorted per-map: that is, it shows what access each user has to the Current Wireless Probes map.

Controlling Map Access by User

Choose Show Access by: User to control each map's access by a specific user through the Web and Remote servers.

To set a user's access for any open map, choose the user from the Show User dropdown menu.
To allow access to the selected map through the Web server, click the Padlock icon in the Web column for the user or group whose access permissions you want to set, then select a permission level.
To allow access to the selected map through the Remote server, click the Padlock icon in the Remote column for the user or group whose access permissions you want to set, then select a permission level.

Controlling User Access by Map

Choose Show Access by: Map to control each user's access to a specific map through the Web and Remote servers.

To set access control parameters for any open map, choose that map from the Map Name dropdown menu.
To allow access to the selected map through the Web server, click the Padlock icon in the Web column for the user or group whose access permissions you want to set, then select a permission level.
To allow access to the selected map through the Remote server, click the Padlock icon in the Remote column for the user or group whose access permissions you want to set, then select a permission level.

Map Access Permission Levels

Select a map's Web and Remote server access permission levels for each user or group as described below:

No Access - Deny access to this map.
Read-Only Access - Allow the user to view the map, but do not allow changes. (Access to the web server is always read-only.)
Read-Write Access - Allow the user to view and edit the map.

Using the Intermapper RemoteAccess license pool

You may want a number of users to access an Intermapper server through Intermapper RemoteAccess, but not all users need to connect at once. You can purchase Intermapper RemoteAccess "license pool" licenses and apply them to the Intermapper server. Unlicensed copies of Intermapper RemoteAccess can then connect to the server until all licenses are in use.

The Registration pane in Intermapper RemoteAccess's Server Settings window shows the licenses that are currently installed.

Multiple licenses in Intermapper RemoteAccess

Use these options, available from the Registration pane, to add, delete or view information about a license or serial number:

Click Add... to add a new license or serial number.
Click Delete... to remove the selected license or serial number.
Click Info... to view detailed information about the selected license or serial number.

10. Installing Intermapper Flows

You must follow several steps before you can begin analyzing your Flows data.

Download Intermapper Flows onto the same machine as your Intermapper server.
Run the Intermapper Flows installer. The process of installing Intermapper Flows automatically configures Intermapper to talk with Intermapper Flows.
Be sure to remove any firewalls on the selected UDP ports for NetFlow (default is 2055) or sFlow (default is 6343).

Note: The Intermapper Flows service/daemon may not start up if another program is using port 2055, 6343, or whatever port you have designated for NetFlow or sFlow packets). You should stop/uninstall conflicting packages on the system.

You must also configure one or more Flows exporters to send data to the Intermapper Flows server. Intermapper Flows automatically detects the exporters and begins collecting their data. Many switches and routers can be configured to export Flows data. See http://www.cisco.com/en/US/tech/tk812/tech_configuration_guides_list.html
and
https://www.fortra.com/intermapper/overview-configuring-sflow
and
http://www.juniper.net/techpubs/software/erx/junose60/swconfig-routing-vol1/html/ip-jflow-stats-config4.html

There are several software-based Flows exporters available, including Flows Exporter by ProQueSys.

Intermapper Flows Settings

Use the Flows Settings window to view and edit settings for Intermapper Flows.

To open the Flows Settings window:

Click the Settings icon in the top-right corner of the Flows window

The following tabs are available in the Settings window:

Use the Exporters tab to choose which exporters you want to collect from.
Use the Appearance tab to select a coloring theme for protocols and hosts.
Use the Advanced tab to set performance-related parameters, the path to your database, and a database size.
Use the Registration tab to view information about your current Intermapper Flows license, and to enter a new license key.
Use the About tab to view version information about Intermapper Flows and its components.

Intermapper Tech Support Tips and Best Practices

Intermapper Training