lchance

I've seen this once in my APM environment. What was causing my problem then was Windows Domain Controllers and authentication with RPC. Have you looked at perhaps using a different account in your domain with your APM Credentials?

i had a similar issue recently where the credentials i was using got hosed with a certain domain controller. so all authentication went south and really messed up APM monitors using WMI.

Thanks again GOB for this great piece of work! ...Well done!

Add me to this list needing ESX 4 support ! We just added multiple ESX 4 systems and Solarwinds can not monitor them! Any ETA on the release which will fix this? Thanks, Larry

I opened a case (Case #314922) and it is closed with a solution referencing a Microsoft KB article. But that's not the long term fix. I still have my problems with using APM and Performance Counters/WMI in large volumes.

and me!

Nope - it was not resolved. The final status on my case was BUG-CLOSED. Maybe the next release (3.6) will have a fix.

The KB post is the exact configuration we followed.

Will do...and yes it is NTA 3.5 SP1. Thanks.

Just to add more pressure ... I had this exact request come in today. Solarwinds servers are in Central Time Zone - but we have users in other Zones needing their own local timestamps. Cheers!

I don't think so! It is ongoing for me as well...

Denny, Is there any possibility to get a 'hot fix' for this rather than wait on a service pack? Thanks.

don't know about the timeout unless the device is many hops away from you. once you get the MIBs listed you might research the OIDs you'll need and then check out the Orion Admin Guide about Universal Device Pollers. that is the piece you'll have to use. they have some sample custom pollers already in the UnDP gui.

Chris & Andy, This is 8.2(3) Is that my problem?

Thank you! - To Denny and the many others at Solarwinds for being open with this user community and taking our crap complaints. I think this is where Solarwinds keeps its strength in the market and are able to maintain a great product and I always look forward to any new feature.

Yes it is.

Well, it always happens when I use a Custom Date like 6/1/2009 through 7/1/2009 but I can't say I've seen it when generating others with less lengthly date ranges. Thanks.

there are a couple of tools in Solarwinds Engineers Toolset for mib browsing. if you don't have this Solarwinds tool then you could download a trial-copy here http://www.solarwinds.com/register/registration.aspx?program=428&c=70150000000D8FL it has two tools for doing a 'mib walk' - they are SNMP MIB BROWSER and MIB WALK.…

Thanks very much Brandon. We will continue with this information and try to get the CPU & MEMORY showing up - again. I did a review in System Manager of two of these nodes and it does show that when I first discovered them with ESX POLL the CPU and MEMORY was there. I have graphs to show it. But at some point we lost this…

i made the changes with v1.01 but the new additions (outlined in green in your screenshot) do not show up. like: HIDE CHANGE PARAMETERS HIDE SQL REQUESTS...etc any idea? is something sticking in a cache somewhere? (i did clear the browser cache)

I hope to update NPM 10.0 to NPM 10.1.1 next week. So maybe that will 'fix' something. My first suspect has to do with this data retention summarization and how it is working in these settings along with Report Writer's schemas.

mine looks similar but has ipAdEntAddr in a column. the ipAdEntIfIndex is repeated in the next row however i can quickly ID the interface to IP.

For anyone running into this same problem. This is a confirmed bug by Solarwinds. No ETA on the fix.

Sounds like an Cisco IOS release issue to me.

We have multiple EMC Clariion SANs and really need this support too! Our SAN infrastructure is growing fast. All I can get from our EMC, MIB-wise, is management IP up and System name - not much value there.

That works for me - I appreciate your help!

i'm not working with VMware directly myself but one of our VMWARE guru's is doing that and here's what he's passed on: I got some info that I’m going through now. VMWare is saying we don’t even need snmpd.conf nor snmp service…more to come.

it's still not working for me yet and i think the reason is probably what was mentioned above about the Logging Source IP is different than what Orion NODE ID has assigned or discovered. my normal Syslog View works great, it's just trying to link these Syslog resource views to the Node Details view where I don't see syslog…

Wow - just what I need.... I though it was, but I'll look into it again. Thanks.

that's a good idea. i'll consider it from that angle as well. thanks for the reply.