CLI caching and range keyword

YANG
1

query regarding the CLI behavior. Can you please help

ajodas@ubuntu:~/CISCO/MY_CONFD_MODULES/OLD$ make cli-c
/usr/bin/confd_64//bin/confd_cli -C --user=admin --groups=admin
–interactive || echo Exit
Welcome to ConfD Basic

The CLI may only be used during product development.
Commercial use of the CLI is prohibited.
You must disable the CLI in confd.conf for production.
For more information, visit http://www.tail-f.com.
admin connected from 127.0.0.1 using console on ubuntu
ubuntu#
ubuntu#
ubuntu# config
Entering configuration mode terminal
ubuntu(config)#
ubuntu(config)#
ubuntu(config)#
ubuntu(config)#
ubuntu(config)# diagnostic schedule start location 0/7/CPU0 test hhh on ?
Possible completions:
JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC range ----- > We see this range keyword appear sometime and other time it is not there. What is the significance of this.
ubuntu(config)# diagnostic schedule start location 0/7/CPU0 test hhh on JAN ? Anyways we are able to select the month. How can we make it not to appear or some consistent behavior
This line doesn’t have a valid range expression
Possible completions:
<1 - 31> Enter date in the month to start the test
1
ubuntu(config)# diagnostic schedule start location 0/7/CPU0 test hhh on JAN 1 ?
This line doesn’t have a valid range expression
Possible completions:
<2013 - 2099> Enter year
2019 --------------------------------------------------------------------------------------------------------------à This is previously applied data being cached We don’t want any data to be cached. How can we achieve this
ubuntu(config)# diagnostic schedule start location 0/7/CPU0 test hhh on JAN 1 2019 ?
This line doesn’t have a valid range expression
Possible completions:
<00:00 to 23:59> Enter the hour and minute in hh:mm format
09:00
ubuntu(config)# diagnostic schedule start location 0/7/CPU0 test hhh on JAN 1 2019 09:00
ubuntu(config-on-JAN/1/2019/09:00)# commit
% No modifications to commit.
ubuntu(config-on-JAN/1/2019/09:00)#

2

For CLI related questions, it is best to file a RT ticket with our support team.

I will provide some explanation of the range keyword here. The ‘range’ keyword is used to specify range expressions that act on multiple list instances at once.

Pertinent configurable parameters in confd.conf:

/confdConfig/cli/allowRangeExpression (boolean) [true]
allowRangeExpression is either "true" or "false". If "true" then range expressions are
allowed for all key values of type basic type integer. An alternative is to specify
hasRange for each path in the clispec.

/confdConfig/cli/allowRangeExpressionAllTypes (boolean) [true]
allowRangeExpressionAllTypes is either "true" or "false". If "true" then range
expressions are allowed for all key values regardless of type. An alternative is to
specify hasRange for each element in the yang files.

/confdConfig/cli/suppressRangeKeyword (boolean) [false]
suppressRangeKeyword is either "true" or "false". If "true" then 'range' keyword
is not allowed in C and I-style for range expressions.
3

Is it possible to have allowRangeExpression node in confd-basic version. Because i use basic version and i don’t find the above specified node in confd.conf file and can you please say in which directory we have to look through for getting the confd.conf file since we have confd.conf file in many directories of the installed confd.