Comments
-
Good to hear that. Please let me know the result. Jiri
-
Hi jeffreyc, Sorry for the delay. I will confirm whether what you want is possible and post the answer. Jiri
-
Thanks. I can only say that we will consider improving the behaviour in the future. Jiri
-
Thanks for sharing the details. I can't promise anything but taking it into account and hopefully improve the product in the future. Jiri
-
Glad to hear that. Sorry I didn't point you to the HF right away. I posted the answer during night and my brain capacity was obviously not 100 % . Regards, Jiri
-
OK, so you want to add nodes to NCM by default as well but there are some (can you identify them?) that you don't want to add / want to remove from NCM ex post? Jiri
-
Could anything from these posts help? Jiri
-
Hi rharland2012, Could you please clarify what level of support you would like to see? E.g. being able to download/upload configs out of the box; inventory reports -- which ones (ideally which MIB/OIDs)? Thanks, Jiri
-
Continuing the discussion offline. Jiri
-
Jeff, Thanks for the information. I hope support will be able to help you. To your question about device templates / config change templates (CCT): CCT's are totally independent; you don't need them to be involved in any way to be able to download/upload configs. CCT's are used for sophisticated scripting -- you can…
-
We're working on that -- see .
-
I see. Then that would be a feature request. Jiri
-
No, this was reported too late to make it into 7.4. We'll look at that for a future release. Jiri
-
If you sign up for SRM 6.4 Beta: SRM 6.4 Beta 2 Is Available! , I can give you some updates. Jiri
-
Ok, so once you upgrade NPM to 11.5.2, just install NCM 7.4 on the same server. When you start the installer, a wizard will be launched to merge the NCM and NPM databases. The only manual step is copying custom NCM content (device templates, reports, scripts) from the old NCM server. After this is done, the old standalone…
-
John Handberg, Could you perhaps share the device template(s) you use, if any modifications were required? The best place would be here: Network Configuration Manager. Regards, Jiri
-
Just closing the loop. Looking at your support case, I found out that resolution was to change the rule with the "quit" keyword to [ \t\r\n\v\f]*quit[ \t\r\n\v\f]* Jiri
-
Interesting idea. That looks like a feature request that would apply to NPM or NCM. Jiri
-
Correct, the functionality doesn't exist. Jiri
-
jeffnorton, That's a misunderstanding. I wanted to recommend not using Config Archive and keeping the DB slim by regularly exporting your configs to a dedicated archive. (There's a special scheduled job for it.) Jiri
-
Both of these templates should also work with telnet or ssh. All you have to do is configure your devices to use the right template and the desired protocol for config transfer. Please let me know if you need some hints. Regards, Jiri
-
Hi nikkodumapit, What model is your H3C device exactly? According to the output above, NCM tries to use a generic template for the device. That won't work. Please try one of the H3C templates available in the content exchange: Network Configuration Manager H3C templates Regards, Jiri
-
That's correct. The device templates have been moved to the database -- that folder would only be an artifact. Jiri
-
Hi, To select a specific device template for a node * Log in to the Web UI * Go to Settings -> Manage Nodes (Node & Group Management) * Select the nodes you want to change the template for and click Edit Properties. * Scroll to the NCM section, check Communication and select the right device template. Regards, Jiri
-
I don't see a way to achieve this. Just out of curiosity -- what are you going to do with the binary file then? Jiri
-
I think the following should do what you need: Jiri
-
Yes, that would be a feature request.
-
Of course. But don't tell anyone .
-
Andy, Yes, upgrade would be a good choice. If you have active NCM maintenance, you can upgrade to NCM 7.1 release candidate or wait a few weeks for the final release. Regards, Jiri
-
For now, you can e.g. group by machine type and select the nodes you want to include, or use dynamic selection for the same purpose. Jiri