0 Replies Latest reply on Nov 3, 2011 1:11 PM by fcaron

    NCM 7.0 does not support duplicate nodes.


      [this posting is duplicated A solution to multi-context config download with NCM (Cisco ASA, FWSM...), this instance will not be improved]

      NCM 7.0 has several node management improvements (common with Orion Core/NPM, new Discovery Sonar…).
      Due to these changes, NCM 7.0 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.

      If you are in this situation, we recommend using this workaround:


       1.       Add a new Config Type for each context (for example Context1, Context2)

      2.       Specify in your device template, how to switch to each context

      3.       Specify in Reset Command ${ConfigType} macro

      4.       Specify in Reset command the common RegEx to recognize the prompt after switching to each context

      5.       Avoid using ${ConfigType} macro in DownloadConfig command


      Device Template Example:

      <Command Name="RESET" Value="${ConfigType}" RegEx="NewPromptIdentifier" />

      <Command Name="Context1" Value="command to switch to Context1"  />

      <Command Name="Context2" Value="command to switch to Context2 "/>

      <Command Name="DownloadConfig" Value="Show configuration"/>



      When NCM downloads a configuration, the first command issued is the ‘Reset’ command defined in the device template.

      The ${ConfigType} macros will be replaced by the appropriate switch context command, based on the config type selected for the dowload

      The context will be dynamically switched before the download command is executed.

      When the context is changed, so is the prompt.

      In order to recognize the prompt, a REGEX expression must be used to ignore the variable part of the prompt.


      Let’s assume command mode prompt after login is : Tex-3750#

      -          After switching to Context1, the command mode prompt becomes Tex-3750-Context1#

      -          After switching to Context2 the command mode prompt becomes Tex-3750-Context2#

      The RegEx to use in the reset command should match the common portion of the prompt in both contexts. In this example this would be RegEx=” Tex-3750”


      An NCM user shared the result of his work (FWSM on NCM 6.1):

      Should work the same in NCM 7.0. Thanks csowerby

      Cisco FWSM Virtual Context Template