netconfcentral logo

Objects

Object Abstract
acceptableMasterTableDataSet Acceptable Master Table derived from IEEE 1588-2008. One Table per time-aware system, and used when any of the system is of type IEEE 802.3 EPON, i.e. if any port in a corresponding system has acceptableMasterTableEnabled set to true. Not used otherwise (Table exists without an entry).
access-lists Access control lists.
access-points Top most container for configuration and state data for Access Points.
acl Top level enclosing container for ACL model config and operational state data
acls This is a top-level container for Access Control Lists. It can have one or more acl nodes.
active-alarm-list List of currently active alarms. An alarm is removed from this table when the state transitions to clear.
actn actn is described by this container
additional-default-headers This container maintains a list of which additional notifications should use which optional headers if the receiver supports this specification.
address-pool-status This is a top level container for Address Pool Status, which contains the status of address pool usage.
address-pools This is a top level container for Address Pools. It can have one or more Address Pools. The pools may not be contiguous.
alarms The top container for this module.
aps Top level grouping for automatic protection switch data
arp System ARP settings.
bad-value Contains the value that was associated with the error. Usually added to 'invalid-value' errors, but may be present for other errors as well.
belongs-to Contains the module name value for a belongs-to-stmt. Will be present in appinfo for a YANG submodule.
br-instances BR instances enabled in a network element.
bridge Bridge parameters.
bridges Contains the Bridge(s) configuration information.
bridges Contains the Bridge(s) configuration information.
case-name Contains the identifier-str value for a YANG case name. Will be present in appinfo for all choice case definitions.
cc-session-statistics-data CC operational information.
cc-session-statistics-data CC operational information.
channel-monitors Top-level container for optical channel monitors
choice-name Contains the identifier-str value for a YANG choice name. Will be present in appinfo for all choice object definitions.
classifiers List of classifier entries.
client dhcpv6 client portion
components Enclosing container for the components in the system.
config Contains the value from the config-stmt. Will be present in appinfo for top-level objects or if config-stmt is present in the object definition.
configlet Top-level container for ZeroTouch configuration objects.
connection defines a list of endpoint connection.
connections Enclosing container for line system connections list
contact Contains the value from the contact-stmt. Will be present in appinfo for the module. if defined in the module.
controller-behaviour-settings Parameters allowing to set the controller behaviour
current-pm-list List of current PMs.
currentDataSet The current data set represent this system's topological location relative to the known grandmaster system. This data set is consistent with respective IEEE 1588 data set.
db-backup-manifest The manifest file provides instructions to a database operations application to backup the database on a device. Since the files used for these operations are likely user selected, these manifest files are more likely used by the controller as a template to control the overall flow of a backup operation and provide a means of providing customized timeout values. The following strings will be recognized as parameters to be replaced by the user selected values: __LOCAL-FILE-PATH, __REMOTE-FILENAME. Manifest file name Each vendor/model combination can have a separate manifest file defined for backup. These shall be named db-backup-manifest.json.
db-restore-manifest The manifest file provides instructions to a database operations application to restore the database on a device. Since the files used for these operations are likely user selected, these manifest files are more likely used by the controller as a template to control the overall flow of a restore operation and provide a means of providing customized timeout and auto-reboot values. The following strings will be recognized as parameters to be replaced by the user selected values: __LOCAL-FILE-PATH, __REMOTE-FILENAME, __NODE-ID-CHECK. Manifest file name Each vendor/model combination can have a separate manifest file defined for restore. These shall be named db-restore-manifest.json.
default Contains the value from the default-stmt. Will be present in appinfo for a typedef that includes a default-stmt.
defaultDataSet The default data set represents native time capability of a time-aware system and is consistent with respective IEEE 1588 data set.
demand defines a list of demand.
demand-group defines a list of demand group.
dhcpv6-ldra-profiles DHCPv6 LDRA configuration profile.
domains Contains configuration related data. Within the container is list of fault domains. Within each domian has List of Maintenance Association (MA).
domains Contains configuration related data. Within the container, there is a list of fault domains. Each domain has a list of MAs.
dot1agCfmConfigErrorList The CFM Configuration Error List provides a list of Interfaces and VIDs that are incorrectly configured.
dot1agCfmDefaultMd Interface configuration parameters.
dot1agCfmMa The Maintenance Association contains the VLAN ID that it wants to monitor.
dot1agCfmMd A Maintenance Domain is described in 802.1ag (3.21) as the network or the part of the network for which faults in connectivity are to be managed. The boundary of a Maintenance Domain is defined by a set of DSAPs, each of which can become a point of connectivity to a service instance.
dot1agCfmMep The MEP container contains the configuration for a Maintenance point, for example, the direction, ID, VLAN ID and so on.
dot1agCfmStack It enables the network administrator to discover the information about the Maintenance Points configured on a port.
dot1agCfmVlan It contains the association between VID and VLAN.
dots-data Main container for DOTS data channel.
dots-signal Main container for DOTS signal message. A DOTS signal message can be a mitigation, a configuration, or a redirected signal message.
endpoint defines a list of endpoint.
endpoint-group defines a list of endpoint group.
envelope-profiles Reusable configuration for policer envelopes. A Policer (also known as an Bandwidth Profile) is a characterization of the lengths and arrival times for Service Frames at a reference point. A Policer is specified using the concepts of a flow and envelope.
error-number Contains the internal error code associated with the error. Added for all error types.
etht-svc ETH services.
event-filters Notification event source filters
fast FAST configuration
fault-handling This Container first detects faults and handles the detected faults in accordance with the fault handling action.
filters Filters configuration.
filters Contains a list of configurable filters that can be applied to subscriptions. This facilitates the reuse of complex filters once defined.
flows flow flowPolicies
flowspec Container for flowspec configuration and state
forwarding Configuration nodes associated with layer 2 forwarding.
forwarding-state State data nodes associated with layer 2 forwarding.
frame-replication-and-elimination The managed objects that control Stream identification are described in Clause 9. The managed objects that control FRER are described in this Clause 10 as follows: a) General requirements on the behavior of counters are in 10.1. b) The various tables of managed objects that can manage, in detail, each individual Stream, are described in five subclauses, including: 1) Additions (10.2) to the Stream identity table (9.1) required for Autoconfiguration (7.11, 10.7). 2) The Sequence generation table (10.3) that configures instances of the Sequence generation function (7.4.1); 3) The Sequence recovery table (10.4) that configures instances of the Individual recovery function (7.5), the Sequence recovery function (7.4.2), and the Latent error detection function (7.4.4); 4) The Sequence identification table (10.5) that configures instances of the Sequence encode/decode function (7.6); and 5) The Stream split table (10.6) that configures instances of the Stream splitting function (7.7). c) The managed objects that support the automatic configuration, upon receipt of a packet, of entries in the first four of the preceding tables (10.2 through 10.5), are described in the subclause on Autoconfiguration (10.7). d) The per-port, per-Stream packet counters that are kept by FRER functions for inspection by network management entities are described in 10.8, and the per-port (totaled over all Streams) counters in 10.9. The managed objects in the subclauses under 9.1 make it possible to configure more than one encapsulation for the same stream_handle subparameter on the same port. Similarly, the managed objects in the subclauses under 10.3 and 10.4 make it possible to configure more than one Sequence encode/decode function (7.6) or more than one Sequence generation function (7.4.1) for the same stream_handle subparameter. [The same value of stream_handle can be in the frerSeqGenStreamList (10.3.1.1) of more than one frerSeqGenEntry (10.3.1) or in the frerSeqRcvyStreamList (10.4.1.1) of more than one frerSeqRcvyEntry (10.4.1).] A system shall return an error if an attempt is made to configure conflicting requirements upon that system.
ghn This container includes the profiles and associated configuration parameters of the G.hn interface. It is divided in three sections: - domain: Includes all the domain-wide profiles - node: Includes all the node-wide profiles - link: Includes all the link-wide profiles
ghs G.handshake (G.hs) configuration
hardware Hardware / vendor-specific data relevant to the platform. This container is an anchor point for platform-specific configuration and operational state data. It may be further organized into chassis, line cards, ports, etc. It is expected that vendor or platform-specific augmentations would be used to populate this part of the device model
hardware Configuration parameters for components.
hardware Data nodes representing components. If the server supports configuration of hardware components, then this data model is instantiated in the configuration datastores supported by the server. The leaf-list 'datastore' for the module 'ietf-hardware' in the YANG library provides this information.
hardware Data nodes representing components.
hardware-state Data nodes for the operational state of components.
historical-pm-list List of historical PM
ieee-dot1Q The YANG Data Model for VLAN bridges as defined by the IEEE
ietf-acl Packet Access Control Lists (ACLs) as specified in draft-ietf-netmod-acl-model
ietf-key-chain Key chains as specified in draft-ietf-rtgwg-yang-key-chain;
ietf-yang-library YANG Module Library as defined in draft-ietf-netconf-yang-library
instance-list List of one or more PTP datasets in the device, one for each domain (see IEEE 1588-2008 subclause 6.3). Each PTP dataset represents a distinct instance of PTP implementation in the device (i.e. distinct Ordinary Clock or Boundary Clock).
instance-list List of one or more PTP datasets in the device, one for each domain (see IEEE 1588-2008 subclause 6.3). Each PTP dataset represents a distinct instance of PTP implementation in the device (i.e. distinct Ordinary Clock or Boundary Clock).
instance-list List of one or more PTP datasets in the device, one for each domain (see IEEE 1588-2008 subclause 6.3). Each PTP dataset represents a distinct instance of PTP implementation in the device (i.e. distinct Ordinary Clock or Boundary Clock).
interfaces Top level container for interfaces, including configuration and state data.
interfaces Interface configuration parameters.
interfaces Interface list as defined by RFC7223/RFC7224
interfaces Container for all interfaces information.
interfaces Example interfaces group
interfaces Interface parameters.
interfaces-state Data nodes for the operational state of interfaces.
interfaces-state Data nodes for the operational state of interfaces.
interfaces-state Data nodes for the operational state of interfaces.
ipfix Top-level node of the IPFIX/PSAMP configuration data model.
joined-aps Top most container for joined-aps.
key-chains All configured key-chains on the device.
key-chains All configured key-chains for the device.
key-chains All configured key-chains for the device.
key-chains-state All configured key-chains state.
key-table The key table of all managed cryptographic keys of a device.
keychain A list of private-keys and their associated certificates, as well as lists of trusted certificates for client certificate authentication. RPCs are provided to generate a new private key and to generate a certificate signing requests.
keychain A list of private-keys and their associated certificates, as well as lists of trusted certificates for client certificate authentication. RPCs are provided to generate a new private key and to generate a certificate signing requests.
keystore The Keystore contains a list of symmetric keys and a list of asymmetric keys.
l1-connectivity serves as a top-level container for a list of layer 1 connection services (l1cs)
l2-dhcpv4-relay-profiles L2 DHCPv4 Relay Agent configuration profiles.
l2vpn L2VPN specific data
l2vpn-ntw Container for VPN services.
l2vpn-svc Container for L2VPN services.
l2vpn-svc Container for L2VPN service.
l2vpncommon l2vpnGlobal pwTemplates notMatchRemoteLdpInfos
l2vpnvpls vplsStatisticInfo vplsInstances
l2vpnvpws vpwsStatisticInfo vpwsInstances vpwsSwitchInstances
l3vpn-svc Main container for L3VPN service configuration.
l3vpn-svc Main container for L3VPN service configuration.
lacp Configuration and operational state data for LACP protocol operation on the aggregate interface
last-modified Contains the last-modified date-and-time string for the datastore referenced in the reply. Will be present in all <rpc-reply> elements for <copy-config> (from server to client), <get-config> and <get> replies. The timestamp willbe specific to the datastore that was specified in the request.
link-table Configuration associated with link table entries.
listening-ssh-server This container is only present to enable `pyang` tree diagram output, as a grouping by itself has no protocol accessible nodes to output.
listening-tls-server This container is only present to enable `pyang` tree diagram output, as a grouping by itself has no protocol accessible nodes to output.
lldp Top-level container for LLDP configuration and state data
lldp Link Layer Discovery Protocol configuration and operational information.
lmap Configuration and control of a Measurement Agent.
lmap Configuration of the LMAP agent.
lmap-state A tree exporting state information about the LMAP agent.
local-routes Top-level container for local routes
logical-network-element This module is used to support multiple logical network elements on a single physical or virtual system.
logical-network-elements Allows a network device to support multiple logical network element (device) instances.
lora LORA channel
macsec The MACsec
mandatory Contains the value from the mandatory-stmt. Will be present in appinfo if mandatory-stmt is present in the object definition.
max-elements Contains the value from the max-elements-stmt. Will be present in appinfo for a list or leaf-list object, if the max-elements-stmt is present in the object definition.
melt Metallic Line Test (MELT) configuration.
messages Top-level container for Syslog messages.
metrics IEEE 1906.1 metrics are values that can be configured to control the operation of a nanoscale communication network. They can also be monitored to characterize the performance of the nanoscale network.
microtubule-field tubes
mimo-groups Configuration of carrier terminations for operation in MIMO mode.
min-elements Contains the value from the min-elements-stmt. Will be present in appinfo for a list or leaf-list object, if the min-elements-stmt is present in the object definition.
modules-state Contains YANG module monitoring information.
modules-state Contains YANG module monitoring information.
molecular-motor-motion This is for all motors in the system.
mpls MPLS and TE configuration
mplstp-oam Top level container.
mud MUD-related information, as specified by RFC 8520.
mud MUD related information, as specified by RFC-XXXX [RFC Editor to fill in].
multicast Multicast configuration.
multicast-state State data nodes associated with multicast.
must Contains the fields from one must-stmt. Will be present in appinfo for each must-stmt defined within an object.
nacm Parameters for NETCONF Access Control Model.
nacm Parameters for NETCONF access control model.
nacm Parameters for NETCONF Access Control Model.
nacm Parameters for NETCONF Access Control Model.
nanivid Redefined nanoscale-system for our nanivid experiment, in which we provide an extra subtree.
nanoscale-system This is a nanoscale system. It can be used as is in any of your XML or JSON files. It is also convenient as debugging to represent the data tree.
nat NAT module
netconf-client Top-level container for NETCONF client configuration.
netconf-state The netconf-state container is the root of the monitoring data model.
netconf-state capabilities datastores schemas sessions statistics
netconf-state The netconf-state container is the root of the monitoring data model.
network-instance This module is used to support multiple network instances within a single physical or virtual device. Network instances are commonly know as VRFs (virtual routing and forwarding) and VSIs (virtual switching instances).
network-instances Network instances, each of which consists of VRFs and/or VSIs.
network-instances Network instances each of which consists of a VRFs (virtual routing and forwarding) and/or VSIs (virtual switching instances).
network-services Container for list of configured network services.
network-topology topology
network-topology topology
networks Serves as a top-level container for a list of networks.
networks Serves as a top-level container for a list of networks.
neuron-model Redefined nanoscale-system for our neuron model, which is enriched with new metrics, and this is only the beginning.
nid-group Contains both configuration and operational state nodes associated with the PAE NID group.
nid-group Contains both configuration and operational state nodes associated with the PAE NID group.
nvoVPNMgr composedVPNs
oam-protocols Container for configured OAM protocols.
optical-amplifier Enclosing container for amplifiers and supervisory channels
optical-attenuator Enclosing container for attenuators
ordered-by Contains the value from the ordered-by. Will be present in appinfo for all list and leaf-list object definitions.
org-openroadm-device info users pending-sw database-info shelves circuit-packs interface protection-grps protocols internal-link physical-link external-link degree shared-risk-group line-amplifier xponder roadm-connections odu-connection connection-map odu-switching-pools otsigroup-capability-profile mc-capability-profile split-lambda-profile otn-odu-mux-hierarchy-profile optical-operational-mode-profile otn-capability-profile muxp-profile
organization Contains the value from the organization-stmt. Will be present in appinfo if oraganization-stmt is present in the module.
organizations List of organizations owning modules
organizations List of organizations owning modules
parentDataSet The paraent data set represent timing upstream (toward grandmaster) system's parameters as measured at this system. This data set is consistent with respective IEEE 1588 data set.
path Contains the path-stmt Xpath expression value for a leafref. Will be present in appinfo for all leafref typedefs, and inline type-stmts for leafref leafs and leaf-lists.
per-port-msdu-mask-max-length Table of the per-port maximum msdu mask lengthts
pkt-eca-policy-opstate operational state
policies Configuration associated with policies.
policing-profiles Configuration associated with policing profiles.
policy-instance this describes the policy instances.
policy-voip This object is a policy instance to have complete information such as where and when a policy need to be applied.
portDataSet A list of gPTP port related variables in a time-aware Bridge or for a time-aware end station. A value of 1 is used in a bridge or an end station that does not have multiple components. For a given media port of a Bridge or an end station, there may be one or more gPTP port, and depends whether a media port supports point to point link (e.g. IEEE 802.3 Ethernet) or point to multi-point (e.g. CSN, IEEE 802.3 EPON,etc) links on the media port.
portStatIfEntry A list of time-aware port related counters in a gPTP domain. A value 1 is used in a bridge or an end station that does not have multiple components.
position Contains the position-stmt value for a bit definition. Will be present in appinfo for all 'bits' typedefs, and inline type-stmts for leafs and leaf-lists.
potential-tca-list List of current TCAs.
pppoe-profiles PPPoE Intermediate Agent configuration profile.
probes The container containing the list of probes.
proc /proc file system monitoring data.
provision-aps Top most container for assigning hostnames to APs.
pseudowires Configuration management of pseudowires
ptp The PTP struct containing all attributes of PTP data set, other optional PTP attributes can be augmented as well.
qos QoS features, for example policing, shaping, etc.
qos Top-level container for QoS data
qos-policy-profiles This container provides a framework for QoS policy profile configuration.
radio-link-protection-groups Configuration of radio link protected groups of carrier terminations in a radio link. More than one protected group per radio link terminal is allowed.
radios Top level container for radios, including configuration and state data.
reference Contains information from the reference-stmt. Will be present in appinfo for objects which contain a reference-stmt.
relay DHCPv6 relay portion
relay-agent Top level container for relay-agent configuration and operational state data
restconf-state Contains RESTCONF protocol monitoring information.
revision Contains the fields from one revision-stmt. Will be present in appinfo for each revision-stmt defined within the module.
routing The YANG Data Model for Routing Management revised to be Network Instance / VRF independent.
routing Configuration parameters for the routing subsystem.
routing Configuration parameters for the routing subsystem.
routing-instance A routing instance, in the context of the RIB information model, is a collection of RIBs, interfaces, and routing parameters.
routing-policy Top-level container for all routing policy configuration
routing-state State data of the routing subsystem.
rpc-output Contains the XSD type name value for the RPC output data for one RPC method. Will be present in appinfo for all rpc definitions which contain an output-stmt.
rpf System level configuration of Reverse Power Feeding.
schema-mounts Contains information about the structure of the overall mounted data model implemented in the server.
sdwan-svc Top-level container for the SD-WAN services.
selt Single Ended Line Test (SELT) configuration.
server Runtime access to netconfd-pro CLI parameters for immediate change or activate-on-restart
server DHCPv6 server portion
service l3vpn-cfg service-paths
service-function description-info monitoring-info
service-function-metadata NSH provides a mechanism to carry shared metadata between network devices and service function, and between service functions. The semantics of the shared metadata is communicated via a control plane to participating nodes. Examples of metadata include classification information used for policy enforcement and network context for forwarding post service delivery.
service-list List of service. Can only be created, deleted, modified, etc. using special RPCs. Will only contain one service with a given name. Does not contain historical (deleted or rather those passed their end time) or draft services. If two services exist with the same name (with non-lapping start-end times for example), this table will contain the current one. If only planned services exist for the name, the one with the earliest start time will be present
sesmgr yp-controller session management configuration
snmp Top-level container for SNMP-related configuration and status objects.
source Contains the complete filespec of the source file used for the XSD translation. Will be present in the appinfo for the module header.
ssids Top level container for ssids, including configuration and state data.
stamp Top level container for STAMP configuration
stamp-state Top level container for STAMP state data
stp Top-level container for spanning tree configuration and state data
stream-identity-list The Stream identity table consists of a set of tsnStreamIdEntry objects (9.1.1), each relating to a single Stream, specifying the points in the system where Stream identification functions (6.2) are to be instantiated. Each entry in the Stream identity table has a tsnStreamIdHandle object (9.1.1.1) specifying a stream_handle value and one or more tsnStreamIdEntry objects (9.1.1) describing one identification method for that Stream. If a single Stream has multiple identification methods, perhaps (but not necessarily) on different ports, then there can be multiple tsnStreamIdEntry objects with the same value for the tsnStreamIdHandle. If the HSR or PRP method or the Sequence encode/decode function is applied to a packet, then the LanId or PathId fields are also used to identify the Stream to which the packet belongs.
streams Contains information on the built-in event streams provided by the publisher.
subscriber-profiles Subscriber configuration profile.
subscriptions Contains the list of currently active subscriptions, i.e., subscriptions that are currently in effect, used for subscription management and monitoring purposes. This includes subscriptions that have been set up via RPC primitives as well as subscriptions that have been established via configuration.
supa-encoding-clause-container This is a container to collect all object instances of type SUPAEncodedClause.
supa-policy-clause-detail-container This is a container to collect all object instances of type SUPAPolicyClauseDetail.
supa-policy-clause-has-decorator-detail-container This is a container to collect all object instances of type SUPAPolicyClauseHasDecoratorDetail.
supa-policy-component-decorator-detail-container This is a container to collect all object instances of type SUPAPolicyComponentDecoratorDetail.
supa-policy-concrete-metadata-container This is a container to collect all object instances of type SUPAPolicyConcreteMetadata.
supa-policy-exec-fail-take-action-detail-container This is a container to collect all object instances of type SUPAPolExecFailActionToTakeDetail.
supa-policy-generic-decorated-container This is a container to collect all object instances of type SUPAGenericDecoratedComponent.
supa-policy-metadata-decorator-access-container This is a container to collect all object instances of type SUPAPolicyAccessMetadataDef.
supa-policy-metadata-decorator-detail-container This is a container to collect all object instances of type SUPAHasMetadaDecoratorDetail.
supa-policy-metadata-decorator-version-container This is a container to collect all object instances of type SUPAPolicyVersionMetadataDef.
supa-policy-metadata-detail-container This is a container to collect all object instances of type SUPAPolicyMetadataDetail.
supa-policy-operator-container This is a container to collect all object instances of type SUPAPolicyOperator.
supa-policy-source-container This is a container to collect all object instances of type SUPAPolicySource.
supa-policy-source-detail-container This is a container to collect all object instances of type SUPAPolicySourceDetail.
supa-policy-target-container This is a container to collect all object instances of type SUPAPolicyTarget.
supa-policy-target-detail-container This is a container to collect all object instances of type SUPAPolicyTargetDetail.
supa-policy-value-container This is a container to collect all object instances of type SUPAPolicyValue.
supa-policy-variable-container This is a container to collect all object instances of type SUPAPolicyVariable.
supported-symmetric-algorithms A container for a list of supported symmetric algorithms. How algorithms come to be supported is outside the scope of this module.
sw-manifest The manifest file provides instructions to a software download application to download and install a new software load into a vendor's equipment. Software download files All vendor files for a software release should be stored in a separate directory. A unique directory would be used for each vendor, model and software release combination. This directory and all files in that directory will be accessible by the SFTP server. The software directory can be flat or hierarchical with subdirectories. The manifest file should be in the root directory of the software directory. A software directory must contain files for one and only one software release. Manifest file name Each software release directory shall contain a manifest file for that release. The filename for the manifest file shall be sw-manifest.json.
syslog This container describes the configuration parameters for Syslog.
syslog This container describes the configuration parameters for Syslog.
system Basic objects for NETCONF system status.
system System group configuration.
system Enclosing container for system-related configuration and operational state data
system-management System management for physical or virtual device.
system-state System group operational state.
telemetry-system Top level configuration and state for the device's telemetry system.
telemetry-system Top level configuration and state for the device's telemetry system.
temp-service-list List of temporary services Can only be created, deleted, modified, etc. using special RPCs.
templates Configuration templates for <edit-config>
terminal-device Top-level container for the terminal device
test-suites test-suite
threat-feed this describes the list of threat-feed.
timePropertiesDataSet The time properties data set represents the grandmaster's parameters, as measured at this system and are derived from IEEE 802.1AS protocol. This data set is consistent with respective IEEE 1588 data set.
tm-profiles A set of types of profiles for traffic management configuration.
toaster Top-level container for all toaster database objects.
transparent-clock-default-ds The members of the transparentClockDefault Data Set
transparent-clock-default-ds The members of the transparentClockDefault Data Set
transparent-clock-default-ds The members of the transparentClockDefault Data Set
transparent-clock-port-ds-list List of transparentClockPort data sets of the transparent clock.
transparent-clock-port-ds-list List of transparentClockPort data sets of the transparent clock.
transparent-clock-port-ds-list List of transparentClockPort data sets of the transparent clock.
trill-site Trill all configuration and display information
tsig-keys The list of tsig-keys which are referred from acl-net-key and addr-key.
tunnel-pools A list of mappings that steer client services to transport tunnel pools. The tunnel pools are managed independently from the services steered on them.
twamp Top level container
units Contains the units-stmt value for a type or leaf. Will be present in appinfo for typedefs, and inline type-stmts for leafs and leaf-lists, which contain a units-stmt.
value Contains the value-stmt value for an enum definition. Will be present in appinfo for all 'enumeration' typedefs, and inline type-stmts for leafs and leaf-lists.
vdsl VDSL configuration
versioned-service-list List of service, regardless of lifecycle state. Can only be created, deleted, modified, etc. using special RPCs. Can report more than one version of a service, if supported by the implementation. May contain deleted services, multiple versions of the same service, as identified by its name, etc.
voucher A voucher, containing the owner's identifier, a list of device's unique identifiers, information on when the voucher was created, when it might expire, and the vendor's signature over the above values.
vpn-instance Generic VPN is a base class for VPN models. Other VPN models may be inherited from this base class with corresponding extensions.
vrrp VRRP data at the global level.
wavelength-router Top-level container for wavelength router device
xpic-pairs Configuration of carrier termination pairs for operation in XPIC mode.
xpongemtcont Configuration associated with xPON GEM ports, T-CONTs, and traffic descriptors.
xpongemtcont-state State data associated with xPON GEM ports, T-CONTs, and traffic descriptors.
yang-library Container holding the entire YANG library of this server.
yang-mpl This container describes the data model for MPL servers. The model consists of the following parts: (1) a mpl-domain part that describes the MPL-domains and associated Multicast addresses and the interfaces on which the Multicast addresses are enabled, (2) a mpl-op part that describes the parameters settings per seed, (3) a mpl-seeds part that describes the MPL buffer contents and the Trickle timer values, and (4) a mpl-statistics part that describes the number of lost and correctly forwarded messages.
zones The list of DNS Zones for which the properties are defined that describe the primary/secondary relationships.