Littlebee_26 · Monitoring Consultant · ✭✭✭✭✭

Up! would really want to have this feature!

Brilliant idea !

Say SolarWinds polled the neighbor IP, then the next time it polled the device did not return this IP via SNMP response then it will be considered as Is Deleted. 

Yeah I got the same question too, like there should be a filter to ignore idle admin status in BGP prot

To what I understand the retention settings only applies for port history so I assume we should include another option for user history.

Agree, will use SQL CE 4 instead.

9C:7B:EF: Hewlett Packard 

I think we need to incorporate this functionality on All Active reports. We are confused on which nodes we got the application status down.

It would be best if we can include this in our out of the box alert.

Upon checking, here are the alert variables that still work for a UDT 3.3: IP: ${SQL: SELECT N.IP_Address FROM [dbo].[Nodes] N JOIN [dbo].[UDT_Port] UP ON (UP.NodeID = N.NodeID) JOIN [dbo].[UDT_PortToEndpointCurrent] P2EC ON (P2EC.PortID = UP.PortID) WHERE (P2EC.EndpointID = ${N=SwisEntity;M=EndpointID})} Device: ${SQL:…

Try to check in UDT if that MAC address (endpoint) has a direct connection in one of the monitored switchports.

Those information are stored in UDT_Rule and UDT_RuleProperty. Heads up, these are not so user friendly db tables. BR. LittleBee!

Hey, most of the time MachineKeys folder stores certificate pair keys for both the computer and users. You can clean this folder safely without affecting the Solarwinds application: https://forums.iis.net/t/1224708.aspx?C+ProgramData+Microsoft+Crypto+RSA+MachineKeys+is+filling+my+disk+space

Same issue, I can't export a custom poller that I downloaded. What should we do now?

Hey Llard good to see you here on Thwack. Rock!

Just an update, here is the SQL query for Trap messages: select nodeid, IPAddress, TrapType, Message, COUNT(TrapID) as total from Traps where DateTime>DATEADD(day, -1, GETDATE() ) group by nodeid, IPAddress, TrapType, Message order by total, IPAddress, TrapType, Message desc

Hi, we encountered the same incident, we uninstalled the Patch Manager Web on the main polling engine then re-run the installer on the additional polling engine. After that we install the Patch Manager web back on the main poller.

Exceptional!

Not pretty sure if this is already resolved but this article might help: Success Center

Azure ADFS is not yet supported in the current version of Orion Core 2018.4.

Investing my points for this bad cheetah.

Hey guys there's a good news! I got the fix after installing Hotfix 1 for IPAM v4.9