NCM Node report for snmp-server community

Hi

This looks for the latest Running config from 2011-08-09

use solarwinds_ncm
select n.NodeCaption, c.Config, c.ConfigType, c.ConfigTitle, c.DownloadTime from Nodes n, ConfigArchive c
where n.NodeID = c.NodeID
and c.ConfigType = 'Running'
and c.Config like '%snmp-server community public%'
and c.DownloadTime >= DATEADD(DAY, DATEDIFF(DAY, '19000101', '2011-08-09'), '19000101')

or

This looks at todays date for the latest Running config starting from the morning at 00:00:00

use solarwinds_ncm
select n.NodeCaption, c.Config, c.ConfigType, c.ConfigTitle, c.DownloadTime from Nodes n, ConfigArchive c
where n.NodeID = c.NodeID
and c.ConfigType = 'Running'
and c.Config like '%snmp-server community public%'
and c.DownloadTime >= DATEADD(DAY, DATEDIFF(DAY, '19000101', GETDATE()), '19000101')

You can add other SQL statements to look for multiple SNMP comm strings, you can then add this to a report via report writer i you wanted too.

Kind Regards

James

Hi there

Thanks much for the mySQL statements.  I was able to launch the report writer from the Solarwinds NPM server.  I tried to create a new report using the SQL statement for today's date, but it complained about not finding solarwinds_ncm.

We also have Solarwinds NCM running on another server, perhaps there is a place that I can create the report using these SQL statements there?  Not sure...any help would be appreciated

Thanks so much

Hi

No problem

solarwinds_ncm is my database name, so just change it to the name of your NCM database. you could use the SQL reporter in NPM to talk to the NCM database as long as they are on the same database server. If that is not the case then you could use SQL studio express from microsoft to connect to the NCM database and then run the SQL from there.

I have created a coupel of PERL scripts that can talk to a MSSQL DB from a remote unix system , so if you want an example of that then let me know

Kind Regards

James

I had an issue when using Custom Macros for the community strings in the Node Details.  When the string is too long (19 works but 21 digits is too long), it works when using SNMP to reach the device, but the "Community Strings for each node" report would show the macro name rather than the string represented by the macro.  After changing the strings to names less than 21 digits, they all show up correctly in the report.