achtest

Thats exactly what I thought, I already did this twice but without success. (no cached version of list resources) I now have a maintenance window to restart that specific Node. I figured out that the server has a very long runtime... I'll notify you when the reboot is done. (13th of October)

Yes the drives are listed when I List Resources while polling through SNMP. Exactly, I discovered the drives successfully (incl. Volume Size) with WMI and then switched polling to SNMP, after that the drives are marked as "UP" but no Volumesize is shown. Ok, so do I have to configure the config file or replace it? Or is…

So simple but useful!! Many Thanks, thats it!

Solved the Issue. Anti-virus blocked port 25 because programm name changed to SolarWinds.BusinessLayerHost.exe

Thank you for your detailed answer So I SNMP walked the hrStorageTable as mentioned by yaquaholic and heres the result: .1.3.6.1.2.1.25.2.3.1.1.1 = INTEGER: 1 .1.3.6.1.2.1.25.2.3.1.1.2 = INTEGER: 2 .1.3.6.1.2.1.25.2.3.1.1.3 = INTEGER: 3 .1.3.6.1.2.1.25.2.3.1.1.4 = INTEGER: 4 .1.3.6.1.2.1.25.2.3.1.1.5 = INTEGER: 5…

I think this has grown historically due to our firewall rules. But to be honest, this has not been a problem so far. We manage over 800 windows nodes over snmp, this node is the only one that has a problem. But thanks anyway for this tip! I will definitely consider changing this!

Hello, could you tell me, what port I have to open on the firewall except port 25 (SMTP)? I got the same issue. Thanks.

Hi Tim, when i run the script it says the following: New-SwisObject : Entity â?EntityType Orion.Volumes â?Properties not found. At C:\volumeadd.ps1:22 char:28 + $newVolUri = New-SwisObject <<<< $swis â?"EntityType $entity â?"Properties $newVolProps + CategoryInfo : InvalidOperation: (:) [New-SwisObject], FaultException`1 +…

Hey! did you managed to resolve this? We have the same problem.

Hi everyone, so, am I right, that I only have to update all my Orion servers to 4.7.2? (I'm on the same version as amehlman: 4.7.02558)

Hi everyone, I am finally able to respond to this post. After I opened a support case with SolarWinds, the support and I came to the conclusion that this has something to do with the system itself. The SNMP walk wasn't successful and always timed out. Sometimes the simplest solution is the best: RESTART the faulty…