HolyGuacamole

It is outside your control to convert a trap OID to a poller OID. It is a function of whether the MIB has a pollable OID that provides the information equivalent to the trap OID, i.e., it is up to the vendor's implementation of the SNMP Agent. With respect to your main objective of being able to trigger an NCM action in…

Thanks, Paul. Please post your findings back to the discussion.

The 'Scan for all nodes' scans the logs received and saved by LEM's Syslog server, and matches the connectors for the logs received. It doesn't scan the network to find out which servers do not have an agent.

‌if you look at the config change templates section of the admin guide, you will find a list of entities and properties you can reference in the script. vlanid is of the properties for an interface object. In the script body above, you can reference this as @portItem.InterfaceDescription your script body will also expect…

It is definitely worthwhile opening a support ticket to see if there is any unofficial way to merge the 2 SAM credential libraries only for this 1-off exercise.

I would imagine it will drop the data since the data retention now says you only want to keep detailed data for 7 days. So, any detailed data that is more than 7 days old would be purged when the maintenance kicks in.

Which device is it? Which command did you run on the device?

There is an out of the box alert called "restart a windows service" that does exactly this!

Ok great. Depending on how many different credentials you have across the estate, that may be the only set you need to enter or you can define connection profiles for each set and use a connection profile instead of the global defaults. You may want to close out the discussion as 'answered'

Now, we are getting a little fancy Add a Custom Table resource. For the data source selection, change the first drop down to 'Advanced Database query (SQL, SWQL)' and switch the radio button to 'SQL' when it shows up The below SQL should work (Change the 2 items in orange - x.x.x.x to your SolarWinds server IP. Change the…

I am not following that. Can you post a screenshot?

Hi mukund2345, The test checks specific OIDS verify SNMP community. It doesn't do a MIB walk. You will need to verify the specific OID being used in the component monitor showing unknown status in your screenshot. It is possible that Windows may no longer be responding to the OID in your component monitor. In any case, WMI…

Correct. Maybenicole pauls can validate

did you download the integration application from the ServiceNow app store?

You could create a report per device, and bookmark the URL. If you don't want the usera to login, you can use the reserved directlink account (check admin guide for directlink account) the solution I like more is mobile admin+ udt for this use case. They can get access to all of the udt information from their smartphone…

you will need to change the SNMP Get Type to 'GET' instead of 'GET NEXT' since you have already included the .0 suffix for the OID

Which one specifically are you finding it to be a problem? To include a CPU chart for example, I can search for keyword 'CPU' and select one of the 'Node Charts' as shown below The next step is to specify a data source. Select just the node for which you want to display the CPU chart, and the report would include a CPU…

I found a couple of typos in your last query. It was missing the 2 letters in red. SELECT TOP 25 NodesData.Caption + ' | ' as 'data()' FROM [dbo].[NodesData] left outer join ContainerMemberSnapshots on NodesData.caption = ContainerMemberSnapshots.name left outer join Containers on Containers.ContainerID =…

1 FC can be a collector for 1 VMan appliance only. I guess the options would be - A parallel set of FCs and VMan - (semi-workaround) Have an Orion (NPM or SAM) instance sync with VMan for redundancy of data. See blog below The Dream Continues: Virtualization Manager 6.1 is now GA!

Easiest way is perhaps Volume custom properties. The SQL should only change by 1 additional criteria like Volumes.CustomProperty1 = 'Yes' (may not be the exact names but you get the idea)

Hard to tell what's going on without screenshots and MIB walk output.

Sensor and Analyzer are not really LEM terms. But if you look at the architecture, we are saying you can place a Syslog server in a remote location to capture the raw logs from the devices in that location and use the LEM Agent installed on it to normalized the logs and sent it to the central LEM in a compressed &…

The poller's IP is for identification of the polling engine only. The devices are always polled using the OS routing. To the best of my knowledge, you need to address this at the OS level. Or, you will need to adjust your ACLs to match your OS routing.

Is the System OID the same for both versions? The System OID can be see in the Node details view.

thanks for the reply

So, you have an automated trigger action working correctly to execute a runbook update on the affected node? Why is it incorrect behavior to run that all the other nodes that have a threshold breach? I am not understanding that bit.

It wont be possible to install both the legacy and new SMI-S Provider on the same machine. However, you can use the same Profiler Agent to communicate with both the legacy and new SMI-S Providers, i.e., monitor both your 3400 and 4700

Check the Windows event logs to see what might be the issue. Make sure Anti-virus or similar end point protection software isn't interfering with the application. Below is a list of folders to exclude SolarWinds Knowledge Base :: What files and directories should I exclude from antivirus protection to optimize performan……

So, SNMP Traps only. What are you running into while adding the EVA as an SNMP v3 node?

It's not published because it is not supported, and is not guaranteed to remain the same with versions. However, if you must query the DB directly, the easiest way to reverse engineer the query is to use the legacy report writer From a previous reply - Re: Table to show all 5 statistics being returned from Linux script A…