#INTERMAPPER MAP LICENSE KEY#
#INTERMAPPER MAP WINDOWS#

Updated OpenSSL to version 1.0.2u on MacOS, Linux, and Microsoft Windows systems. Layer 2 scans fail to complete (traceback with illegal IP passed).įoreignKeyViolation in updating on table notifierrule.įixed IMAuth error with Active Directory. IMRA 6.5.1 Java exceptions generating error logs. svg fails with 50 device license.Įxecution hangs - SSL errors, datapoints report sync. Resolve CSV Injection vulnerability in Intermapper. SNMPv3 noAuth noPriv fails to send securityName.Īcknowledgment not properly reflected in map status icons. IMDC startup depends on executable '/tmp' directory which conflicts with some site security policies. No current PostgreSQL database can be used with Intermapper. IM Database insertion errors - violates check constraint 'event_status_check'. For more information, see the Intermapper Migration Guide.ĭatabase import does not restart following nightly maintenance, no error shown. Updated PostgreSQL from version 8.3.8 to version 10.14 and from 32-bit bit to 64-bit. Existing shortcuts need to be re-created or updated. For more information on converting to Python 3, see the Intermapper Developer Guide.Ĭhanged IMRA components to 64-bit. Probes that use Python 2 need to be converted to Python 3. Upgraded Python version 2.7 to version 3.8.5 and from 32-bit to 64-bit in IMDC. Resolved an inconsistency (specific to Linux systems) between the default path for the settings directory using a command to configure the Intermapper server.Īdded the Intermapper Migration Guide to help assist in upgrading Intermapper Database for PostgreSQL version 10.14. Resolved a fault in the IM server's response to the IE and Edge browsers that was introduced while making the server fully TLS conformant in IM-v6.5.2. Resolved the issue where LDAP Authentication does not work. Resolved the delay in the startup of Intermapper on Microsoft Windows and Linux systems. Resolved daily and weekly maintenance issues related to the Intermapper Datacenter database significantly reducing time spent on those operations. Resolved the failure when applying a retention policy when deleting old data in IMDC. Resolved the failure to apply scaling and display units for Gauge32 in on-demand tables. Resolved the issue where the Intermapper Datacenter does not start if the Intermapper Server is installed on a non-C drive. Improved PostgreSQL database upgrades on slow systems. Updated the Intermapper Migration Guide to reflect the latest updates in migrating from PostgreSQL 8.3 to 10.14.

#INTERMAPPER MAP LICENSE KEY#

Updated License Key Dialog with new text and links. Improved the database migration process, added a progress bar, and added more informational and error messages.

Attach the notifier to an interface by clicking on an interface, selecting Interfaces > Notifiers Window, and checking the boxes for state transitions that should trigger alerts.Upgraded Intermapper Splunk App with Python 3.Įnhanced maintenance processing, warning users that they need available disk space to be at least double the size of the database.Attach the notifier to a device by right-clicking on a device, selecting Device Notifiers, and checking the boxes for state transitions that should trigger alerts.Adjust the Notifier Schedule to change when alerts will be sent.Choose from various notification types: email, text/SMS messages, pager, sounds, sending a trap or syslog, sound, running a command-line script, etc.Scroll to the Notifier List, and click the + at the lower left corner. Create a notifier from Edit > Server Settings.Intermapper has notifiers for sounds, sending email, sending pager and SMS messages, and running scripts.

Every time Intermapper detects a change in a device or interface state (from OK, Critical, Warning, Alarm, Down, or some other state), it can trigger a notification/alert. A notifier is the way Intermapper alerts someone about an event.

Intermapper map