Objects

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 control lists.

Top most container for configuration and state data for Access
Points.

Top level enclosing container for ACL model config
and operational state data

This is a top-level container for Access Control Lists.
It can have one or more acl nodes.

List of currently active alarms. An alarm is removed from this table when the state transitions to clear.

actn is described by this container

This container maintains a list of which additional notifications
should use which optional headers if the receiver supports this
specification.

This is a top level container for Address Pool Status,
which contains the status of address pool usage.

This is a top level container for Address Pools.
It can have one or more Address Pools. The pools may
not be contiguous.

The top container for this module.

Top level grouping for automatic protection switch data

System ARP settings.

Contains the value that was associated with the error.
Usually added to 'invalid-value' errors, but may be present
for other errors as well.

Contains the module name value for a belongs-to-stmt.
Will be present in appinfo for a YANG submodule.

BR instances enabled in a network element.

Bridge parameters.

Contains the Bridge(s) configuration information.

Contains the Bridge(s) configuration information.

Contains the identifier-str value for a YANG case name.
Will be present in appinfo for all choice case definitions.

CC operational information.

CC operational information.

Top-level container for optical channel monitors

Contains the identifier-str value for a YANG choice name.
Will be present in appinfo for all choice object definitions.

List of classifier entries.

dhcpv6 client portion

Enclosing container for the components in the system.

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.

Top-level container for ZeroTouch configuration objects.

defines a list of endpoint connection.

Enclosing container for line system connections list

Contains the value from the contact-stmt.
Will be present in appinfo for the module.
if defined in the module.

Parameters allowing to set the controller behaviour

List of current PMs.

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.

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.

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.

Contains the value from the default-stmt.
Will be present in appinfo for a typedef that includes
a default-stmt.

The default data set represents native time capability of a
time-aware system and is consistent with respective
IEEE 1588 data set.

defines a list of demand.

defines a list of demand group.

DHCPv6 LDRA configuration profile.

Contains configuration related data. Within the container
is list of fault domains. Within each domian has List of
Maintenance Association (MA).

Contains configuration related data.  Within the
container, there is a list of fault domains.  Each
domain has a list of MAs.

The CFM Configuration Error List provides a list of
Interfaces and VIDs that are incorrectly configured.

Interface configuration parameters.

The Maintenance Association contains the VLAN ID that
it wants to monitor.

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.

The MEP container contains the configuration for a
Maintenance point, for example, the direction, ID,
VLAN ID and so on.

It enables the network administrator to discover the
information about the Maintenance Points configured
on a port.

It contains the association between VID and VLAN.

Main container for DOTS data channel.

Main container for DOTS signal message.

A DOTS signal message can be a mitigation, a configuration,
or a redirected signal message.

defines a list of endpoint.

defines a list of endpoint group.

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.

Contains the internal error code associated with the error.
Added for all error types.

ETH services.

Notification event source filters

FAST configuration

This Container first detects faults and handles the detected
faults in accordance with the fault handling action. 

Filters configuration.

Contains a list of configurable filters that can be applied to
subscriptions.  This facilitates the reuse of complex filters
once defined.

Container for flowspec configuration and state

Configuration nodes associated with layer 2 forwarding.

State data nodes associated with layer 2 forwarding.

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.

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

G.handshake (G.hs) configuration

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

Configuration parameters for components.

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.

Data nodes representing components.

Data nodes for the operational state of components.

List of historical PM

The YANG Data Model for VLAN bridges as defined by the IEEE

Packet Access Control Lists (ACLs) as specified
  in draft-ietf-netmod-acl-model

Key chains as specified in
draft-ietf-rtgwg-yang-key-chain;

YANG Module Library as defined in
draft-ietf-netconf-yang-library

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).

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).

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).

Top level container for interfaces, including configuration
and state data.

Interface configuration parameters.

Interface list as defined by RFC7223/RFC7224

Container for all interfaces information.

Example interfaces group

Interface parameters.

Data nodes for the operational state of interfaces.

Data nodes for the operational state of interfaces.

Data nodes for the operational state of interfaces.

Top-level node of the IPFIX/PSAMP configuration
data model.

Top most container for joined-aps.

All configured key-chains on the device.

All configured key-chains for the device.

All configured key-chains for the device.

All configured key-chains state.

The key table of all managed cryptographic keys of a device.

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.

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.

The Keystore contains a list of symmetric keys and a list
of asymmetric keys.

serves as a top-level container for a list of layer 1
connection services (l1cs)

L2 DHCPv4 Relay Agent configuration profiles.

L2VPN specific data

Container for VPN services.

Container for L2VPN services.

Container for L2VPN service.

Main container for L3VPN service configuration.

Main container for L3VPN service configuration.

Configuration and operational state data for LACP protocol
operation on the aggregate interface

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.

Configuration associated with link table entries.

This container is only present to enable `pyang`
tree diagram output, as a grouping by itself has
no protocol accessible nodes to output.

This container is only present to enable `pyang`
tree diagram output, as a grouping by itself has
no protocol accessible nodes to output.

Top-level container for LLDP configuration and state data

Link Layer Discovery Protocol configuration and
	    operational information.

Configuration and control of a Measurement Agent.

Configuration of the LMAP agent.

A tree exporting state information about the LMAP agent.

Top-level container for local routes

This module is used to support multiple logical network
elements on a single physical or virtual system.

Allows a network device to support multiple logical
network element (device) instances.

LORA channel

The MACsec

Contains the value from the mandatory-stmt.
Will be present in appinfo if mandatory-stmt is
present in the object definition.

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.

Metallic Line Test (MELT) configuration.

Top-level container for Syslog messages.

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.

Configuration of carrier terminations
for operation in MIMO mode.

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.

Contains YANG module monitoring information.

Contains YANG module monitoring information.

This is for all motors in the system.

MPLS and TE configuration