pratikmehta003

Solarwinds runs maintenance every day default at 2:15 am and cleans up old records which falls out of the retention period... it also shows up a notification in console if it had some prob in completing.. Apart from this you can setup monitoring of Solarwinds server and DB using SAM templates OR just service monitoring...…

i had read somewhere in the doc that UnDP does not support failover.... but not sure if its changed in latest releases. aLTeReGo​ your comments on this if any info available at ur end....

did u try checking for a report on Virtual Cluster. There are some fields available. Below snap for reference.

what all modules are you using?

well i guess it would be 11.6 directly coz i just saw a post from Solarwinds that 11.6 BETA is released.

just check in trap viewer and filter by IP address to see from which source it is coming... and then check with the owner of that source if too many traps are enabled... many times authentication traps are enabled which is of no use in terms of monitoring...

You should first complete the upgrade on main Poller and then go your APEs... Alternatively you can refer the upgrade advisor if you are unsure of the compatibility...

Hi, We used to get the notification quite often even though the maintenance was complete. Later when we approached Solarwinds Support, they informed there is bug and suggested a hotfix which resolved our issue. But since u are already on an upgraded version, not sure what could be the problem.

what kind of device are u trying to add? As per the error its asking for SNMP/WMI credentials which it is not getting while discovery....

as per the documentation, its not supported.

For me it was resolved by restarting the Orion module engine and the IIS application Pool. My setup was in HA and due to some DB issue there was a big downtime and we encountered this issue of license not getting refreshed...So basically the VIP was trying to contact and since HA was already disabled it was not refreshing…

did u try running the config wizard again?

You will have to create an alert based on the Poller created.. Success Center if you poller is a table poller you will have to check on what OID value the status is down so that it can be used in the alerting..

Yes even we faced lot of issues in last month. randomly the Netflow service gets stopped, memory util goes to 90% on some day and then its back to normal. Just few days back we had a situation wherein the monitoring went down, not sure for what reason(still need to analyse the logs). Only option was to run the config…

got it finally working by adjusting the wait time and trigger time...generally the evaluation time should be less than the trigger wait time.... And made use of the Alert escalation settings as well....

Any suggestions?

I am facing this for IBM servers...any clue?

it would be good idea to check whether SNMP is responding on these switches.. in most of the cases, this happens becoz Solarwinds is not able to connect to the devices over the protocol mentioned...

Will this work, can you help me confirming?

i think u will have to do 2 things.. 1. upload the Solarwinds MIBs on Netwcool. 2. For each alert that should reach Netcool, define a trap action inside the trigger action while configuring the alert...you can use the default trap template or modify based on your requirement... I havent dont integration with Netcool but…

ideally it should not be greater as the whole reason of having the warning state is that we get to know that the device is having some issues and we get alerted before the device is actually reported down...and another adv is that if there are just flapping issues then you are saved of multiple tickets incase you are…

I would say Trigger action name should be something which would make anyone understand by just seeing.. so u can keep it short and simple for subject of the email, it should clearly state whats the alert about and include detail of thresholds, and status. Body can be detailed and this would depend on which team you are…

so when u test fire an alert it comes quick but a genuine alert takes time, right? did u find any errors in the logs?

Hi, You wil have to follow the migration guide which is available in Success center or the product page... and u can involve you DB expert to assist and provide guidance. ex: Orion Platform Migration Guide

is the latency too high between SolarWinds and the switch? Just asking since u mentioned it takes time to complete on the setup... did u verify if complete access is given on switch to your solarwinds server for snmp poll...

For monitoring hardware health u need SAM plugin...

what errors are you seeing in the alert and business layer logs ?

This issue finally got resolved after applying Hotfix 6 for Orion platform...

which version are you currently on for VMAN?

you can refer this thread.. Brocade SAN switch(SN6000B) CPU and memory metrics