This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Multiple Config Type - A Bug or Not??

I am still exploring how to make use of the multiple config type feature of NCM 6.1.

I am trying to use the ${ConfigType} variable in a device template and find that the value has the extra "${}".

i.e. For Config Type "customer1", the value of ${ConfigType} variable is "${customer1}" instead of "customer1"

Is this suppose to work like this or I misused the variable?  I think it should be without the "${}"  sign like "running" is just "running" instead of "${running}".

Here is the template and trace session.

With a device template setup like this

<Command Name="RESET" Value="terminal pager 0${CRLF}changeto context ${ConfigType}" RegEx="#"/>

The session trace showing:

[4/11/2011 2:56:34 PM] Complete buffer is detected - save all lines to echo buffer
[4/11/2011 2:56:34 PM] Echo not detected yet. Push back data to echo buffer, EchoBuffer = <<<changeto context ${Internet}

>>>
[4/11/2011 2:56:34 PM] Start detecting command echo in echo buffer...
[4/11/2011 2:56:34 PM] Echo is detected, EchoBuffer = <<<changeto context ${Internet}

>>>
[4/11/2011 2:56:34 PM] Remove Prompt - prompt not found via RegEx
[4/11/2011 2:56:34 PM] Echo and prompt are removed if they exist, out buffer = <<<>>>
[4/11/2011 2:56:34 PM] Start check prompt for menu-based device
[4/11/2011 2:56:34 PM] --> ERROR: '${Internet}' is not valid
[4/11/2011 2:56:34 PM] -->
[4/11/2011 2:56:34 PM] Start check prompt for menu-based device
[4/11/2011 2:56:34 PM] Process Line = <ERROR: '${Internet}' is not valid >