pratikmehta003

Just to update further. NetApp 8040 is under support. Got to know from the solarwinds support.

is this version of NetAPP supported in SRM: Netapp 8040

Anything more to be added in SRM for 3PAR support? Currently it doesnt provide hardware level monitoring part, just shows the Disk status. Would like to see more of it. Also any plans of getting HP Storeonce onboard?

I actually managed to get a query to find out on which Polling engine the failures are happening. And i just gave a reboot on the server and it resolved the issue. This is the query which i had got from community: use NetPerfMon; select b.nodeid,b.engineid,c.ServerName,COUNT(*) numberOfFailures from udt_job a,nodes…

thanks for this... it will help a lot for some cases where reboot alerting is needed...

Hi, Try checking this thread: Tunnel Interface not "discovered" by NPM

thats great... so this is only for specific version which u have mentioned right?

agree.. HPE and Aruba both needs to be added for default support including hardware monitoring... making custom poller for huge number of devices doesnt help...

its resolved now.. turned out to be an issue where the end device was not able to identify the hostname of Orion server... Network team had changed something which caused this issue.. Hence i had to download the agent software and run the script on the device and then change the IP to report to Orion Server...

telnet is also working.. i did validate

aLTeReGo​ I am getting an error for deplying agent on Suse Linux Enterprise Server SLES SP4/Suse Linux Enterprise Server SUSE 12 SP 4... Its first stating failed to validate credentials and not able to identify the OS of the target server.. When i select the nearest one, it just returns with an error like this: Suse Linux…

thanks a lot :-)

Aruba Gear has lot of devices and just from poll not everything would come up like how its native monitoring tool provides... going UnDP way is a tougher ask and requires lot of effort if trap based monitoring has to be opted for these devices... So more insight from polling would really help...

Hi aLTeReGo​ One clarification on the usage of credentials for pushing the agents to Linux machines. If the team allows to use root credentials then later there will not be any case of account getting locked out right? In my case there are multiple machines for which the user ids might be different and hence they might not…

Second method is better I feel. If you have custom properties to be used then even that can be clubbed very easily...

Was able to resolve the alert logic for polling failure of ESX hosts... Worked with this condition:

i think you can still deactivate from customer portal... or reach out to support via ticket and they can give all possible options..

Hi, Just check this https://thwack.solarwinds.com/docs/DOC-174811#start=25 There is one SQL query posted about SNMP string change...

I think that % would refer to datastore and not data center... for datastore, there is option to alert as variable are available by default...

COuld be a network issue as well. You can check where it is getting dropped by using tracert command.

are you trying to add the device using hostname and getting error u mentioned? Did u try adding using IP address?

i think the URL is not resolving from where u are trying to access the console...are u launching it outside of the server?

suggest you work with support on this... there are ways to deactivate and reactivate the license....

is you SA account locked out by any chance?

check this, Licensing NPM basically every component u monitor is a license. if u have 10 switches and each having 48 interfaces then it will be (10x48) licensing... U can directly contact the sales and they will explain u in detail...

is any OID not visible?

If u have SAM, then try to check the details on all Solarwinds processes and if its reporting any issues on it...

check the Application logs for any timeout error thrown for connection from Poller to DB. Also check your memory and CPU resources for the poller having the issue.

are u referring to default integration where u use the trigger action for creating an INC in SNOW?

you have a option to ignore the unwanted traps by using the Trap Viewer... There is option of configuring the action which says 'Discard'