Comments
-
Hi, That would be a feature request. Regards, Jiri
-
OK, we discussed your scenario internally and our recommendation for you is to choose the integrated separate server case (i.e. NCM on different machine). Your NPM will be safe and you won't lose any integration functionality. Jiri
-
Hi Holger, No, there's no built-in solution now, but the audit of config transfer audit is already available in NCM 7.4 Beta: Network Configuration Manager v7.4 Beta2 is Available! So is the ability to trigger alert based on NCM events -- see What We Are Working On For NCM After 7.3. Regards, Jiri
-
Al, Sorry for the delay. Current versions of CatTools have the capability of exporting/importing the device database. (File->Dabatabse->...) I don't know the situation in 2.x and if the formates were compatible. Regards, Jiri
-
Hi, EMC VMAX and VNX2 are supported by both SRM Orion module and SRM profiler v6.1.1. EMC XtremIO is not supported by either of them. Would you be willing to help us with XtremIO? The complete list of supported devices can be found here -- SolarWinds Online Help. Regards, Jiri
-
Hi, If you upgrade to NCM 7.3.x, the "node sync" no longer exists and you can safely remove this custom property. Regards, Jiri
-
I've contacted you offline. Jiri
-
Did you want to say not making time for the beta? Jiri
-
Well, I'm pretty sure NCM *cannot* do this -- it's a feature request and NCM engineering team confirmed that. Jiri
-
Hi Dave, This is caused by inconsistent workflow for updating these pie charts. We plan to fix it in the next release (internal ticket: NCM-281). Jiri
-
Hi, It shows "changes". We have a feature request to handle this properly: http://thwack.solarwinds.com/ideas/1322. Regards, Jiri
-
After you execute the template, you are redirected to the transfer status page where you can check the output: Regards, Jiri
-
Network_Guru, We know about this problem and it's going to be taken care of. Jiri
-
jmiddleton, You can use @ContextNode.EngineID -- this will be expanded at the time you need it. Regards, Jiri
-
Hi, Could you show us on a screenshot how that section looks for you? E.g. there might be whitespace on the line before "Dek-info". In that case, you should use [\t\r\n\v\f]*Dek-info: .*[\t\r\n\v\f]*-----END RSA PRIVATE KEY-----.* Just an idea... Jiri
-
Good to know. I posted the same suggestion exactly at the same time . Jiri
-
Hi bonnerz, Have you tried the template and instructions here? Cisco Wireless LAN controllers and Cisco WISMs Regards, Jiri
-
Hi, MikroTik devices are now supported out of the box. Sometimes there may be issues caused by colorful lines the device sends in output. All these strange characters are information about line color. To turn off colorful output please change device login user name: {username}+c. For example: admin+c. Regards, Jiri
-
If you have the web reporting available in your Orion installation, you can try to import the attached report from NCM 7.4. No warranty it will work. Jiri
-
Menu based devices are sometimes troublemakers. It's difficult to help you over a forum but hopefully it can be sorted out. I suggest that you read the "Creating a Menu-Based Command Template" section of NCM admin guide and experiment. If you aren't able to figure it out yourself, you can contact SolarWinds support and I…
-
That helps a lot. Actually, the 'Home' tab is common for all the modules you have -- application management, virtualization management, and configuration management. Move the mouse over the Applications tab and choose one of the menu items -- probably SAM Summary or Windows. Regards, Jiri
-
Hi Dan, If I understand you correctly -- you know what IOS commands to use but you are not sure how to turn them into a config change template. I suggest that you start with the following reading: and Orion Network Configuration Manager Administrator Guide. Please feel free to ask further questions. Regards, Jiri
-
Native support for binary configs is something we are working on: What We Are Working On For NCM After 7.4 (Updated on July 29, 2015) Jiri
-
Brian, Cisco devices are very well supported by NCM. Many customers manage the devices you mentioned with NCM. Regards, Jiri
-
FYI: SolarWinds NCM 7.3 Release Candidate is Coming!
-
I totally agree.
-
If you have NPM 11.0.1, you can upgrade from NCM 7.2.2 to 7.3.2 directly. Jiri
-
What exactly do you mean by "clearing up old perl scripts consolidating to NCM"? Could you please share more details about the use case? Thanks, Jiri
-
I'll let Flo confirm, of course, but once you are able to download config from a device, then it's almost sure you can e.g. execute a script. Bulk changes shouldn't be a problem. Software change / firmware upgrade is a very complex operation. For most devices, you can write your own NCM script or use thwack content. A more…
-
Hi cahunt, This problem will be ultimately fixed when we merge NCM and NPM databases. See the WWO post: What We Are Working On For NCM After 7.2 Regards, Jiri