advertisement
YumaPro User Manual container yangcli-pro {
ncx:cli;
// all the yangcli-pro CLI parameters
}
If this extension is present, then netconfd-pro will ignore the container when loading the database object definitions.
Only the program with the same name as the container will use the CLI parameter definition.
4.7.3 ncx:default-parm Extension
The ncx:default-parm extension is used within a container with an ncx:cli extension, or within an 'input' section of an
RPC operation definition. It is defined in yuma-ncx.yang.
If no parameter name is found when processing CLI parameter input, and the ncx:default-parm extension is present in the container or RPC input being processed, then the specified parameter name will be used instead of generating an error. The value must be valid for the parameter syntax, according to its YANG definition. This means that for the default parameter, only the <value> component of the complete parameter syntax may be used, as well as the normal forms.
container yangdump-pro {
ncx:cli;
ncx:default-parm module;
// all the yangdump-pro CLI parameters
}
When invoking the yangdump-pro program, the default CLI parameter is --module. These two command lines are equivalent:
mydir> yangdump-pro –-module=test1 –-module=test2
mydir> yangdump-pro test1 test2
A string that does not start with any dashes will still be tried as a parameter name, before trying the default parameter.
If the value used for a default parameter conflicts with another parameter name, then the normal form must be used, instead of this form.
mydir> yangdump-pro log-app test1
Even if there was a module named 'log-app', it would not be tried as a --module parameter, since it also matches the
--log-append parameter.
Note: the default parameter form is can be used in conjunction with shell wildcard characters, depending on the shell.
Version 15.10-16 Page 47
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 4 1 Preface
- 4 1.1 Legal Statements
- 4 1.2 Additional Resources
- 4 1.2.1 WEB Sites
- 5 1.2.2 Mailing Lists
- 5 1.3 Conventions Used in this Document
- 5 2 Summary
- 5 2.1 What is YumaPro?
- 7 2.2 Intended Audience
- 8 3 Introduction
- 8 3.1 System Components
- 10 3.1.1 YANG
- 13 3.1.2 NETCONF
- 15 3.1.3 YANG-based Automation
- 19 3.1.4 YANG Language Extensions
- 20 3.1.5 YANG Compiler
- 20 3.1.6 YANG Module Library
- 23 3.1.7 YANG Files
- 23 3.1.8 NETCONF Managers
- 23 3.1.9 NETCONF Servers
- 24 4 System Configuration
- 24 4.1 Environment Variables
- 25 4.1.1 $HOME
- 25 4.1.2 $YUMAPRO_HOME
- 26 4.1.3 $YUMAPRO_INSTALL
- 26 4.1.4 $YUMAPRO_MODPATH
- 27 4.1.5 $YUMAPRO_DATAPATH
- 28 4.1.6 $YUMAPRO_RUNPATH
- 28 4.2 Searching for Files
- 30 4.2.1 YumaPro Work Directory
- 30 4.2.2 Parameter Searches
- 31 4.2.3 Import/Include Searches
- 32 4.2.4 File Search Paths
- 34 4.3 Configuration Files
- 35 4.3.1 XML Configuration Files
- 35 4.3.2 Text Configuration Files
- 37 4.4 Logging
- 38 4.4.1 Logging Output Stream Commands
- 38 4.4.2 Logging Detail Commands
- 39 4.4.3 Logging Debug and Development Commands
- 39 4.4.4 Logging Examples
- 43 4.4.5 Logging Backtrace Information
- 44 4.4.6 Logging Hints
- 44 4.5 Pthreads Images
- 45 4.6 Bootstrap CLI
- 46 4.7 Configuration Parameters
- 46 4.7.1 Parameter Syntax
- 46 4.7.2 ncx:cli Extension
- 47 4.7.3 ncx:default-parm Extension
- 48 5 XPath Reference
- 48 5.1 XPath
- 48 5.1.1 XML Namespaces
- 49 5.2 YANG Specific XPath Behavior
- 49 5.3 Custom XPath Variables
- 50 5.3.1 user
- 50 5.4 Custom XPath Functions
- 50 5.4.1 module-loaded
- 51 5.4.2 feature-enabled
- 52 6 Error Reference
- 52 6.1 Error Messages