OpManager MSP 6003 Bugs and Future Enhancements ideas
Before getting into the bugs, I want to say, the enhancements to the "Custom Reports" found on the "Reports" tab (i.e. ability to report on custom monitors) are greatly appreciated and will be very useful for our organization. The ability to save/recall/schedule these report definitions would be cool too
That said, I have found the following bugs in MSP 6003...
1) On the Alarms tab, I cannot get to the second page of a customer alarms. Try this to recreate, select a customer from the drop down list that has more alarms than the "entries per page" value ,then click page '2' or '>' and the page returned reverts to 'all customers' page 2.
2) Adding 'Partition Details of the Device (%) ' via the Probe's 'Quick Configuration Wizard' does not propagate the file system name to the Central server. So, the charts displayed in the "Resources Monitors" section of the snapshot page shows all the charts for all the filesystems, but rather than displaying the file system name above each chart, it displays a totaly useless snmp index number. This problem existed in previous releases as well. I was hoping it would have been addressed by now. Yes, I know I can add them to each server one at a time, but with 300+ servers, that makes it a very looooooooong task. Also, this same problem holds true for any custom monitor that has a type of multiplenode.
3) On the device snapshot page, the 'Today's Availability' incorrectly shows "100%" uptime for a device that has been not responding all day. But 'Today's Packet Loss' correctly show '100%'.
4) Only users with "Full control" cannot acknowledge an alarm. According to your documentation, "Read Only Access" users should be able to do that as well. Right now, "Read Only Access" users can only clear alarms, but not acknowledge.
5) What does "Add As technician" do on the add user page? As far as I can tell, it does nothing.
Is it me, or does the standalone OpManager product get more frequent features and updates than the MSP version?
Anyway, here are some enhancements I would like to see in the future MSP releases...
1) I have several hundred custom monitors, it would be nice if they were sorted alphabetically when displayed.
2) Move all admin functions to the Central Server.
3) Web based "Buisness View" editor.
4) 64Bit If_MIB counters so we can support 10Gib interfaces. (I've hacked the OIDs in the PolledData table on the Probe so that standard Interface charts work with 64bit counters on the central server, but like I said, it is a hack.)
5) F5 Big Ip 3400 & 6800 Support.
6) Foundry FastIron SuperX Switche Support.
7) SSH2 Support.
8) High Availability -- Failover support for both Central and Probes.
that's it.
-greg
That said, I have found the following bugs in MSP 6003...
1) On the Alarms tab, I cannot get to the second page of a customer alarms. Try this to recreate, select a customer from the drop down list that has more alarms than the "entries per page" value ,then click page '2' or '>' and the page returned reverts to 'all customers' page 2.
2) Adding 'Partition Details of the Device (%) ' via the Probe's 'Quick Configuration Wizard' does not propagate the file system name to the Central server. So, the charts displayed in the "Resources Monitors" section of the snapshot page shows all the charts for all the filesystems, but rather than displaying the file system name above each chart, it displays a totaly useless snmp index number. This problem existed in previous releases as well. I was hoping it would have been addressed by now. Yes, I know I can add them to each server one at a time, but with 300+ servers, that makes it a very looooooooong task. Also, this same problem holds true for any custom monitor that has a type of multiplenode.
3) On the device snapshot page, the 'Today's Availability' incorrectly shows "100%" uptime for a device that has been not responding all day. But 'Today's Packet Loss' correctly show '100%'.
4) Only users with "Full control" cannot acknowledge an alarm. According to your documentation, "Read Only Access" users should be able to do that as well. Right now, "Read Only Access" users can only clear alarms, but not acknowledge.
5) What does "Add As technician" do on the add user page? As far as I can tell, it does nothing.
Is it me, or does the standalone OpManager product get more frequent features and updates than the MSP version?
Anyway, here are some enhancements I would like to see in the future MSP releases...1) I have several hundred custom monitors, it would be nice if they were sorted alphabetically when displayed.
2) Move all admin functions to the Central Server.
3) Web based "Buisness View" editor.
4) 64Bit If_MIB counters so we can support 10Gib interfaces. (I've hacked the OIDs in the PolledData table on the Probe so that standard Interface charts work with 64bit counters on the central server, but like I said, it is a hack.)
5) F5 Big Ip 3400 & 6800 Support.
6) Foundry FastIron SuperX Switche Support.
7) SSH2 Support.
8) High Availability -- Failover support for both Central and Probes.
that's it.
-greg