taylorfc

MFR: AVtech Model: RoomAlert 24E, software version 3.4.1 OID: 0.10.43.6.1.4.1 ( In know this is wrong, but it's what they report as the OID. I've validated with NMP and a mib browser.

Eaton Power Xpert Gateway 1.3.6.1.4.1.534.2.12

What's the solution for this? We just upgraded to SAM and now SNMP process polling is dead. We will have to roll back if this can't be fixed. 

I need that functionality too to replace HP BSM/BAC. If very useful especially when your site has 3rd party dependencies.

I would log into the player computer using the account(s) you created for WPM. Check to see what the proxy settings are for that user. Start IE and check the proxy config. I bet it still has a proxy configured for the user.

Same issue here. I've opened a support case(been open a few weeks). I'll post a fix if one is ever provided.

You could monitors the space usage usage on the netapp itself. Here's a UnDP poller that I created that would help you out:

Oh this subject would drive my Linux admins crazy. So from my research, the 5% delta you see is because the Orion calculation doesn't take into consideration system reserved space. When you view the filesystem utilization from the shell, it showed 8% available for user, which I consider accurate for the real world. Since…

It's needs an event log viewer tool like SiteScope, not a log collector. Engineers need the ability to pull the event logs one time, with no permanent storage.

I had to extend the SAM monitors properties though our CMDB. It would be great if that feature was native to SAM.

Try restarting snmpd in the linux servers. I have a few that need it restarted every few weeks. Did the cpu monitors ever work for those servers?

What type of device is it? Is the port you want to see the IP address on layer 2 or layer 3?

Read this: http://msdn.microsoft.com/en-us/library/system.badimageformatexception.aspx It could either be the .net framework or the Orion .net code. Google it and quite a few people fixed the same issue with re-installed the framework. I would open a SW support case. They may suggest a repair on the SAM install first.

Same problem here. Did you ever find a solution?