Converted from YANG file 'yuma-system.yang' by yangdump version 2.2.1737 Module: yuma-system Organization: Netconf Central Version: 2012-01-15 Contact: Andy Bierman <andy@netconfcentral.org>. NETCONF Basic System Group. /usr/share/yuma/modules/netconfcentral/yuma-system.yang Netconf Central Andy Bierman <andy@netconfcentral.org>. 2012-01-15 Add sysNetconfServerCLI monitoring data. 2010-05-24 Change SessionId to standard session-id-type. 2009-12-27 Initial version. Name of the user for the session. Identifier of the session. true Address of the remote host for the session. Basic objects for NETCONF system status. false The system name. RFC 3418, sysName object http://www.ietf.org/rfc/rfc3418.txt The current system date and time. The system date and time when the system last restarted. The current system logging verbosity level. The name and version ID for the NETCONF server running on this system. The boot-time CLI and configuration parameters that were used by the server running on this system. The format is the 'netconfd' container, defined in netconfd.yang. By default, only client-set parameters are shown. Use with-defaults=report-all to see all CLI parameter values in effect. Contains the broken out fields from the output of the 'uname' command on this machine. The name of the operating system in use. The current release level of the operating system in use. The current version level of the operating system in use. A description of the hardware in use. The host name of this system, as reported by the uname command. Sets the server log verbosity level set-log-level_output_type__ log-level The desired verbosity level for system logging messages generated by the server. The current value can be obtained by retrieving the /system/sysLogLevel object. true Generated when the system restarts. Used for logging purposes, since no sessions are actually active when the system restarts. The filespec used to load the running configuration. This leaf will only be present if there was a startup configuration file used. There will be one entry for each <rpc-error> encountered during the load config operation. The <rpc-error> fields are used directly. There is no particular order, so no key is defined. system Generated when the <running> configuration is changed. Name of the user for the session. Identifier of the session. true Address of the remote host for the session. An edit record will be present for each distinct edit operation on the running config. system Topmost node associated with the configuration change. Type of edit operation performed. Generated when a <capability> is added or deleted. Indicates who caused this capability change. If caused by internal action, then the empty leaf 'server' will be present. If caused by a management session, then the name, remote host address, and session ID of the session that made the change will be reported. server-or-user server The capability change was caused by the server. by-user Name of the user for the session. Identifier of the session. true Address of the remote host for the session. List of capabilities that have been just added. system List of capabilities that have been just deleted. system Generated when a new management session is started. Name of the user for the session. Identifier of the session. true Address of the remote host for the session. Generated when a management session is terminated. Name of the user for the session. Identifier of the session. true Address of the remote host for the session. Session ID that issued the <kill-session>, if the session was terminated by this operation. ../terminationReason = 'killed' Reason the session was terminated. true The session was terminated with the <close-session> operation. 0 The session was terminated with the <kill-session> operation. 1 The session was terminated because the SSH session or TCP connection was unexpectedly closed. 2 The session was terminated because of inactivity, either waiting for the <hello> or <rpc> PDUs. 3 The session startup sequence failed. 4 The client's <hello> message was bad or never arrived. 5 The session was terminated for some other reason. 6 Generated when a confirmed-commit event occurs. Name of the user for the session. Identifier of the session. true Address of the remote host for the session. Indicates the event that caused the notification. true The confirm-commit procedure has started. 0 The confirm-commit procedure has been canceled, due to the session being terminated. 1 The confirm-commit procedure has been canceled, due to the confirm-timeout interval expiring. The common session parameters will not be present in this sub-mode. 2 The confirm-commit timeout has been extended. 3 The confirm-commit procedure has been completed. 4 Global auto-increment sequence ID added to each notification element sent by netconfd Revision date of the module in use by the server. Will only be present if the module has a version Load a module into the server, if it is not already loaded. Returns the module revision date (or today's date if none), of the module that was loaded, or an error if not found or the module found had errors and was not loaded successfully. If the module is already loaded, then the revision date will simply be returned. load_output_type__ module Name of the module to load. true Module revision to load. Restart the server. Does not reload the software image.. restart_output_type__ Shutdown the server. shutdown_output_type__ Just returns 'ok'. Used for debugging or relative performance measurements. no-op_output_type__