Various problems with Opmanager 7 & MSSQL
I've used Opmanager 6 in the past, but did not get out of it what I wanted. Since we still need monitoring software, I want to give Opmanager 7 a go.
1) When I discover a Class C with only switches in it, only the first switch is correctly discovered, the rest is classified as "unknown". SNMP settings are identical on all switches. When I manually change the device from desktop to the correct (cisco) switch, it can read all counters correctly, and discovers the interfaces.
The switches in this network are Cisco Catalyst series:
2950
3650
3750
2) MSSQL performance is horrible! When I change a device discovered as desktop to the correct switch type, it takes about 10 minutes!!! When I take a look at the database server (Opmanager and DB are on separated severs), the CPU is at 100%. The DB server is running on VMware ESX 2.5 (latest patches) and have no problems with other databases on that server. Seems like some query's are not very efficient? The server is sized pretty well. (Dual Xeon P4, 2GB ram, SAN attached)
3) The "comma" picture is missing at the "Today's Packet Loss" gauge.
4) If I link two switches via the webgui mapmaker and define to which ports it is connected, it defaults back to the first port in list. (The fatclient mapmaker does not have this problem)
5) Using Internet Explorer 7, there's always a "Error on Page" at the left bottom status bar.
6) I've got 4 pix firewalls (OS 7.2.2) added in Opmanager, but the general snapshot view for it is hard to find. I have to go via an interface, and then click the hostname of the firewall. Seems like the hostname links in the firewall infrastructure map are not clickable.
7) For unix/linux machines, it would be nice to disable ssh/telnet login attempts. I only want to monitor those servers via SNMP, not CLI. But now, it seems that it tries to login with defaults, which is cause a lot of logging on the various hosts.
For the rest, I want to say that Opmanager 7 is a great improvement to Opmanager 6, and I'm aware that it's a GA release, and not a final.
Any timeline's when we can expect the final release?
Also support for following vendors/solutions would be a great addition:
- Vmware ESX 2.5/3.0
- Bluecoat Proxy appliances
- Cisco CIGESM network blade modules
Especially Vmware and Bluecoat have a very large install base, and would cover all our monitoring needs. The blade module is a nice to have. I've now classified it as a Cisco 3560, and that works fine, it just a detail.
Kind Regards,
Leon
New to ADSelfService Plus?