cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
57
Views
0
Helpful
4
Replies
Highlighted
Cisco Employee

Netsim - Case sensitive ?

Hi -

Is there a way to explicitly ignore case while typing on netsim devices ?

VO0(config)# interface v?
                        ^
% Invalid input detected at '^' marker.

VO0(config)# interface V?
  Virtual-Template   Virtual Template interface
  Vlan               Catalyst Vlans

Thanks
Narayanan

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

 

 

The ConfD CLI has support for this, it boils down to a setting in the confd.conf that is used by the individual netsim devices.

 

From:

 

$ man confd.conf

...

       /confdConfig/cli/caseInsensitiveKeys (xs:boolean) [false]

           caseInsensitiveKeys is either "true" or "false". If "false" then

           all user defined instance names must have correct case. If set to

           "true" then case is mostly ignored. Note that if set to "true" then

           all data model files and clispec-files must be written with this in

           mind. You cannot have two elems that conflict in case.

 

Thus if the netsim portion of the NED has a confd.conf template with this setting, logging in to a netsim device, the CLI will be "mostly case insensitive"

 

Try to modify your NED - if this is the official IOS NED, it's a whole different business to convince the IOS NED developers that this is a good thing.

 

Seems to be a pretty confused feature IMHO

 

/klacke

 

View solution in original post

4 REPLIES 4
Highlighted
Cisco Employee

 

Hello Narayanan,

 

I think its not about netsim only even for actual device it behaves like same.I have also tried to found to avoid this case sensitive feature but no luck.

 

I will keep you updating if I find something useful.

 

 

Highlighted
Cisco Employee

 

Hi Tamal -

 

Thanks for the reply! I don’t see the real devices are case sensitive, I just cross verified with one of the IOS real device and here’s the result I see..

svlpdn-dc-gw1(config)#interface V?

Vif          Virtual-Template  Virtual-TokenRing  Vlan

VoaBypassIn  VoaBypassOut      VoaFilterIn        VoaFilterOut

VoaIn        VoaOut

svlpdn-dc-gw1(config)#interface v?

Vif          Virtual-Template  Virtual-TokenRing  Vlan

VoaBypassIn  VoaBypassOut      VoaFilterIn        VoaFilterOut

VoaIn        VoaOut

 

So I assume its a constraint on NSO Netsim.

 

 

It would be great, if someone from core development team can comment on this limitation.

 

Thanks

Narayanan

 

 

 

Highlighted
Cisco Employee

 

 

The ConfD CLI has support for this, it boils down to a setting in the confd.conf that is used by the individual netsim devices.

 

From:

 

$ man confd.conf

...

       /confdConfig/cli/caseInsensitiveKeys (xs:boolean) [false]

           caseInsensitiveKeys is either "true" or "false". If "false" then

           all user defined instance names must have correct case. If set to

           "true" then case is mostly ignored. Note that if set to "true" then

           all data model files and clispec-files must be written with this in

           mind. You cannot have two elems that conflict in case.

 

Thus if the netsim portion of the NED has a confd.conf template with this setting, logging in to a netsim device, the CLI will be "mostly case insensitive"

 

Try to modify your NED - if this is the official IOS NED, it's a whole different business to convince the IOS NED developers that this is a good thing.

 

Seems to be a pretty confused feature IMHO

 

/klacke

 

View solution in original post

Highlighted
Cisco Employee

 

Thanks Klacke!

 

XML tag /confdConfig/cli/caseInsensitive  for me..

 

Thanks

 

Narayanan

 

Content for Community-Ad