NCM 7.x has several node management improvements (common with Orion Core/NPM, new Discovery Sonar…).
Due to these changes, NCM 7.x has stricter rules related to node uniqueness and duplicate nodes are not allowed anymore in NCM 7.0 (because NCM nodes are being handled by Orion Core, which does not support duplicate nodes).
This NCM 6.x capability was sometimes used to deal with devices such as the Cisco ASA, which require management of multiple contexts.
The solution in NCM 7.x (can work in NCM 6.1 as well) uses multiple Config Types:
Solution:
1. In Win32 NCM application, add a new Config Type for each context (for example Context1, Context2).
2. Specify in your device template, how to switch to each context (see example below).
3. Include the ${ConfigType} macro in the Reset Command.
4. Make sure to specify the RegEx value in the Reset command. Depending on your prompt settings, the value should be '#', '>', ']', etc.
5. Avoid using ${ConfigType} macro in the DownloadConfig command. Make sure the command is the right one, e.g. "show running-config".
- After switching to Context1, the command mode prompt becomes Tex-3750-Context1#.
- After switching to Context2, the command mode prompt becomes Tex-3750-Context2#.
Message was edited by: Jiri Cvachovec