Hi Nick, I created a separate case (CAS-0010167260) for you and will respond over email.
Currently, this is not a supported environment for Intermapper. Please see our Intermapper System Requirements page for the recommended OS.
Here are the Intermapper ports to whitelist on the firewall.
Remote server port: 8181 TCP by default
IMDC port: 8182 TCP by default
IM Database port: 8183 TCP by default
IM Flows ports: 8184, 2055, 6343 by default. Port 2055 & 6343 are UDP. Port 8184 is TCP.
Web server port: 80 or 443 TCP by default if turned on, but commonly changed
Telnet server port: 23 TCP by default if turned on, but commonly changed
SNMP trap ports: 162 UDP by default; optionally 161 UDP or some other port as well, depending on configuration.
We have had occasional reports regarding a map that mysteriously goes missing or becomes corrupt. We cannot stress how important it is to have a scheduled backup of the maps enabled. If you haven't already enabled a scheduled backup, please go to Edit > Server Settings > Map Backup and enable this feature.
We recommend to select "All" for the days of the week.
Start time - Anytime outside of your scheduled hours of operation.
Maximum backups - Recommended 28. This will allow you to have a new copy of each your maps for 28 days before it starts to overwrite them.
Please use the following link to access our online VPAT document.
I see an issue in the debug log related to a defect associated with build 6.4. The UPS APC probe would cause the service to stop. We recently released build 6.4.1 last week and it contains a fix for the defect.
Can you please upgraded to build 6.4.1 and let me know if the issue continues?
6.4.1 Download - https://community.helpsystems.com/products-and-downloads/downloads/
I reopened case - CAS-0010073933 - no SNMP response
I will follow up with you over email shortly.
Generally, if the SNMPwalk shows results and Intermapper is saying No SNMPv2c response it's due to the community string not entered in correctly.
If you can open the information window > Probes Tab > Double click on the probe > try re-entering the SNMP community string and see if that works. If it doesn't help let me know and I'll open a case to look into this further.
If the version of Intermapper is 5.8 or higher, it will not require internet access because the registration is completed within the software itself.
If the version of Intermapper is 5.7.1 or lower, please contact email@example.com for further instructions.
The InterMapper polling engine is single-threaded, so nearly all work done by intermapper.exe/intermapperd is restricted to a single CPU. Adding more CPU is not helpful in the case a single-threaded (vs multi-threaded) architecture.
No combination of CPU/RAM will allow InterMapper to monitor more devices once it reaches its limit. Choices are to poll less often (longer polling interval), monitor fewer interfaces/device on average for SNMP probed devices, change the probe mix to use more lightweight probes (like ping/echo), or to expand to an additional server by shifting some of the maps (chart data continuity can be a problem in this case).