cvachovecj

You must run it in SQL Server Management Studio. Jiri

Hi Patrick Walton, I think opening a support ticket with SolarWinds is the way to go. Regards, Jiri

Sorry, can't comment on that. Jiri

You need to import them in NCM 7.4 UI -- import from file. If you have tons of custom device templates, you may consider to upgrade from 7.2.2 to 7.3.2 first, copy the device templates to the DeviceTypes folder of 7.3.2 and then upgrade to 7.4 -- in this case, device templates will be imported automatically. However, I'm…

Good to hear that and thanks for posting the solution. Jiri

You're welcome, but I should have known the correct answer for the first time. I even wrote two blog posts about config change templates that includes this info. Maybe you find them useful: More Automation in NCM: Usage of Variables and Custom Properties in Command Scripts and Config Change Templates A Few Tips and Tricks…

jeffnorton, You can validate yourself that correct EoL dates for Cisco WS-C3750G-24TS-E1U are there in the database. The EoL datafile can be found on your NCM server in C:\ProgramData\Solarwinds\Cirrus\Eos. Open it in an appropriate tool (e.g. SQL Compact Query Analyzer) and run the following query: select * from Eos where…

Glad to help :-).

No services need to be restarted. Just be sure the part of UI is refreshed. Jiri

One more check: What version of NCM do you have? This tool only works with NCM 7.4. Jiri

Could you please open a support case for NCM and attach both NCM diagnostics and the log file from the Connector tool? There may be something broken in your NCM. Jiri

Hi silencer1ami, LLDP reporting is something we are looking at for near future. It was something we plan to work on for the next version of NCM, but due to other priorities, it will have to wait at least one more release. Regards, Jiri

Hi Leny, As far as I understand, the support case has been resolved. Please feel free to share any interesting information that might help others with the same problem. Thanks, Jiri

Yes, you need to copy that content and also import it into NCM: * Device templates (DeviceTypes folder) are stored in Orion database in NCM 7.4 * Scripts are also stored in the DB. * Old NCM reports have been replaced by the new Orion web-based system. Jiri

You mean where to put it?

Jon, Unfortunately not. (And a few other reponses are pending.) Maybe you can try to push them from your end. Jiri

Thanks, Steve. Your vote in favour of this feature has been added to requirement #115222. Jiri

So if I understand you correctly, the problem has been resolved, right? Jiri

Give it a try and we will see, but I'm sure our dev team have done a good job ;-). Jiri

Hi turturici, Exporting the violation details is something we are working on -- see Network Configuration Manager v7.4 Beta2 is Available!. Regards, Jiri

The connection to the NCM server should work. Can you check the log file C:\Program Files (x86)\SolarWinds\NCMSAConnector\NCMSAConnector.txt?

Please see NCM v7.4.1 Hot Fix 3 is now Available . Jiri

I don't see a way of doing this. Jiri

Lee, I suggest installing the latest version 9.4.1 released about a week ago: http://thwack.solarwinds.com/docs/DOC-171658 If the problem persists, please open a support case with us. Regards, Jiri

Thanks!

Sorry for the confusion. You can't use ${CRFL} in the CLI statement directly. You must use a little trick: ...string @myEnter='${CRLF}'CLI{ @myEnter @myEnter @myEnter}... Regards, Jiri

Hi Jeff Norton, I believe there's a problem in your NCM installation. If you have 400 37XX devices, you should definitely have some "green" EOL data. See the screenshots from my NCM: I suggest that you open a support ticket so that we could find the root cause of the problem. Regards, Jiri

Maybe someone else will know. I don't. Jiri

Good to hear. And sorry I didn't realize the fact earlier. As author of the blog post, I should have . Jiri

Hmm. There's no known workaround. Don't use file names starting with 't' . If you open a support case, the engineers might find a way.