Samba (SMB) is an add-on connectivity tool, and there aren’t any defined standard SNMP MIBs for tracking its utilization which rules out making a custom probe.
Monitoring the process is usually done on the SMB/CIFS server itself. There might be a Nagios NRPE plugin available to do it at https://exchange.nagios.org/directory/Plugins/System-Metrics/File-System/SMB
The user would need to put the NRPE script on the server to be monitored, then use the Servers > Proprietary > Nagios NRPE probe to run the script on the remote server.
If the server running Intermapper isn't a windows OS, then no WMI probes are available.
We can file an Enhancement Request for individual device behavior when an interface goes down. Status change or not....rather than for all devices.
We can also add in the Enhancement Request that this should only apply to switches. Development would have to determine the proper methods for creating a process but I'm going to create a case for this and we will be able to work out the details with you offline.
It sounds like you want an enhancement request that allows users to right click on a specific interface and have an option to "Set devices to alarm status on down link"?
If so, I would be happy to create this ER for you.
Let me know if that sounds right or if you have any additional information to include.
I'm not sure what version you are on, but if it's 6.0.0 or higher we do have an option to "Set devices to alarm status on down link". If the checkbox is disabled then you won't see the device turn red if an interface goes down that is attached to the device. This setting can be found from Edit > Server Settings > Device thresholds.
Let me know if this doesn't benefit your request and I can look into it some more.
WMI Service Monitor probe. Put the name of the samba service (shown in Task Manager > Services tab) in the probe, login credentials for the target server.
Server Settings > NT Services & WMI must have credentials for someone who is an administrator on the InterMapper system, and Login as a Service rights assigned (secpol.msc to add that).
I'm not sure how large your network is, but if it's not too large you can do different sounds per types of devices to help identify the problem devices by audio. This would be accomplished by creating different sound notifiers and applying to different devices.
For Example: You could have a certain noise play for routers and noise specific to servers...etc.
Otherwise, I see a lot of customers use the device list view and sort by status. They leave that up on their big screen and the problem devices stand at the top of the list.
Yes, I'd recommend the beta. So far it has been receiving positive feedback. A number of beta testers along with the support reps here have been using it for a while.
We're planning on releasing 6.2.2 July 11th, 2018 sometime in the afternoon. It has been well received by our beta testers so I'm hoping you'll also enjoy the improved performance.
Let me know if you have any questions.
We get a number of customer asking about the Intermapper permissions on LInux. Here is an example of a fresh install of Intermapper on a Linux server showing the default permissions.
imuser:~$ ls -l /usr/local/imdc
drwxrwx--- 4 intermapper intermapper 4096 Mar 26 09:49 config
drwxr-xr-x 4 root root 4096 Mar 26 09:49 core
drwxr-xr-x 6 root root 4096 Mar 26 09:49 imauth
drwxr-xr-x 8 root root 4096 Mar 26 09:49 imdatabase
drwxr-xr-x 7 root root 4096 Mar 26 09:49 imdc
drwxr-xr-x 10 root root 4096 Mar 26 09:49 imreports
drwxr-xr-x 2 root root 4096 Mar 26 09:49 sbin
-rw-r--r-- 1 intermapper intermapper 993 Sep 10 14:13 flows.conf
-rwxr-xr-x 1 root root 517536 Aug 13 10:33 intermapperflows
InterMapper_Settings, owner/group is intermapper/intermapper.