mharvey ✭✭✭✭✭

That would only work if you do alerts on the specific RowID or ID's of that table. You'd have to basically set up an alert for each row and the value you want to monitor if it would be on any row. Otherwise you just specify the RowID of the row in the table that it would be on and that should get you the alert.

I would change the trigger to Node Status is equal to Down Or add in another condition there that says Node Status is not equal to Unmanaged. Otherwise, since these nodes are in a state that is not equal to up, they will trigger this alert.

I don't think it's going to affect anything. The software is only going to care about port communication. As long as it supports the OS, which it does, a mixed environment shouldn't cause any issues.

Did you modify the trigger condition to remove the three status conditions? You can't have one member node in three conditions at once. Your alert should have been setup as follows: Trigger the alert when all of the following apply: Group Name is equal to MetroLAN-Rap Trigger the alert when ANY of the following apply:…

So it's supporting layer 3, but not layer 2. I'm thinking, because of this, the topology mapping can't complete, which is why you aren't seeing anything on the view, or with ConnectNow. I know that with 10.7 there were supposed to be changes to layer 3 topology, but I believe the connectnow still relies on layer 2, which…

I'm guessing the NPM server isn't inside the internal network? You should be able to make an exception for the IP of that server in order to get it to talk to the exchange server.

have you tried auto, 1, and 2?

What certificate did you add to the server? Did you create a self signed cert, or did you have one already from the third party publisher or on-site CA?

Yea, unfortunately I don't think there's a way to pass that. It would be cool, but I don't think they have variable passing in the reports like they do in SQL statements in Alert actions otherwise I'd think just ${NodeID} would work.

I've seen a definite improvement on resource usage on some of our older slower servers. There is a lot less consumption of resources by WMI. The one trade-off I've noted is that it can take a little space on the target with the install and logging created.

Thanks for pointing that out. Didn't see that. Adding that was just what I needed.

Could you still reference it using ${APM_AlertsandReportsData.StatusOrErrorDescription}? Just a thought, granted on an application level, it would return for all components.

These Screenshots are using the Report Writer on the SolarWinds server. Create a new Historical - CPU Load and Memory report. In the Select Fields add the fields you want to see In the Filter Results tab, specify the server you want and the time frame: On the TimeFrame tab set how far back you want the data. From there…

More than likely there's just not an OID that was created to collect this information. It may also be that there is an OID, but SolarWinds by default doesn't request it. You could try a SNMP walk using the snmpwalk,exe tool against the server to see if there is an OID that just simply isn't one of the OIDs that SolarWinds…

Are there any timeframes setup for that alert, or is it set to run 24x7? Was the server unmanaged prior to it going offline?

Could you post the screenshots of how you have the report setup, or find the report in the \Reports folder inside the \Orion directory and attach it? Regards, Matthew Harvey Loop1 Systems

Was the previous version 7.1.1 or was it a newer version? Did you do the reinstall after the migration and the 2 databases were set up?

yeah, 12.2 with HF2 to fix another issue we ran into with Mount Point monitoring.

Unless you have the reset set to "Reset when conditions are no longer true" then no, the alert will not clear as there is no defined reset condition.

If it just shows as Aruba Networks, and it's all inclusive, then you're only going to be able to set for one or the other. What I'd recommend is to use the Tell Us your Unknown Device forum to request that in a future release SolarWinds uses the system object OID on the device to differentiate controllers from switches. 

It may not be able to tie the users back to members of that group based on how the group is setup in AD. Once the login attempt is made, the information would be passed to AD to figure out the group association, then Orion would relate them and allow the login. Are they getting the Windows AD pop up login or the Orion…

So you're attempting SNMP for them. I would also try the snmpwalk.exe tool in the Orion install directory. This will confirm the access for the Orion server by trying to walk the servers in question from the Orion server.

If the options aren't there, or it's still not recognized, make sure the user account you are using is part of the local administrators group on the server. 

The command is going to be based on the device template that's specified. If you edit the device details, what device type are you setup for?

That's how it works by design. Once the device is in an alerted state, the alert triggers and shouldn't re-fire. Now, if there are mulitple devices that meet the condition each time it checks, it will fire off an alert for each one.

Likewise, voted up

Honza, Much appreciated on these instructions. I had only reverted one alert, and have decided to leave the others running in the new alerting for the moment. My biggest issue has been with the lack of history on some of my node down alerts (one of which is now reverted). It seems that there's no indication of when a…

Let me see what I can put together. Since there is no Date Added column in the nodes table, this may not be completely possible, but I'll see what I can put together.

Then you'd have to add in the IP's as ICMP only devices before Orion can tell you if it's not pingable any more. You would then use the traditional node down alert.

I'm not sure that all of this is going to be possible. If some of this data does not live in the SQL database, then it's not going to be possible to pull it into a report. Now, there should be a way to get some of that information through joining a couple of the discovery tables to the nodes table in a query. Something I…