This module contains general type definitions and identities for optical transport models.
openconfig-platform-types
openconfig-extensions
openconfig-types
description:
Type for optical spectrum frequency values
type: uint64
units: MHz
description:
Administrative state modes for
logical channels in the transponder model.
type: enumeration
description:
Loopback modes for transponder logical channels
type: enumeration
default: NONE
description:
Base identity for frame mapping protocols that can be used
when mapping Ethernet, OTN or other client signals to OTN
logical channels.
description:
Asynchronous Mapping Procedure
base identity: FRAME_MAPPING_PROTOCOL
description:
Generic Mapping Procedure
base identity: FRAME_MAPPING_PROTOCOL
description:
Bit-synchronous Mapping Procedure
base identity: FRAME_MAPPING_PROTOCOL
description:
Constant Bit Rate Mapping Procedure
base identity: FRAME_MAPPING_PROTOCOL
description:
Transparent Generic Framing Protocol
base identity: FRAME_MAPPING_PROTOCOL
description:
Framed-Mapped Generic Framing Protocol
base identity: FRAME_MAPPING_PROTOCOL
description:
Base identity for tributary slot granularity for OTN
logical channels.
description:
The tributary slot with a bandwidth of approximately 1.25 Gb/s
as defined in ITU-T G.709 standard.
base identity: TRIBUTARY_SLOT_GRANULARITY
description:
The tributary slot with a bandwidth of approximately 2.5 Gb/s
as defined in ITU-T G.709 standard.
base identity: TRIBUTARY_SLOT_GRANULARITY
description:
The tributary slot with a bandwidth of approximately 5 Gb/s
as defined in ITU-T G.709 standard.
base identity: TRIBUTARY_SLOT_GRANULARITY
description:
Base identity for protocol framing used by tributary
signals.
description:
1G Ethernet protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OC48 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
STM 16 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
10G Ethernet LAN protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
10G Ethernet WAN protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OC 192 (9.6GB) port protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
STM 64 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 2 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 2e protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 1e protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 2 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 2e protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
40G Ethernet port protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OC 768 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
STM 256 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU 3 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 3 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
100G Ethernet protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
100G MLG protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU4 signal protocol (112G) for transporting
100GE signal
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTU Cn protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU Cn protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU 4 protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
400G Ethernet protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
800G Ethernet protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
Optical tributary signal group protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU Flex with CBR protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
FlexO protocol as defined in ITU-T G.709.1 and ITU-T G.709.3
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
OTSI_A is the digital adaptation between the OTSi and the
FlexO-x, or the regenerator section layer of the FlexO
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
ODU Flex with GFP protocol
base identity: TRIBUTARY_PROTOCOL_TYPE
description:
Base identity for identifying the type of pluggable optic
transceiver (i.e,. form factor) used in a port.
description:
C form-factor pluggable, that can support up to a
100 Gb/s signal with 10x10G or 4x25G physical channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
1/2 C form-factor pluggable, that can support up to a
200 Gb/s signal with 10x10G, 4x25G, or 8x25G physical
channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
CFP2 analog coherent optics transceiver, supporting
100 Gb, 200Gb, and 250 Gb/s signal.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
1/4 C form-factor pluggable, that can support up to a
100 Gb/s signal with 10x10G or 4x25G physical channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
OriginalQuad Small Form-factor Pluggable transceiver that can
support 4x1G physical channels. Not commonly used.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Quad Small Form-factor Pluggable transceiver that can support
up to 4x10G physical channels.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP pluggable optic with support for up to 4x28G physical
channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP-DD with electrical interfaces consisting of 8 lanes that operate at up to
25 Gbps with NRZ modulation
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP pluggable optic with support for up to 4x56G physical
channels
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP-DD quad small form factor pluggable double density
optic providing an 8 lane electrical interface
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP DD pluggable optic with support for up to 8x56G physical
channels. Type 1 uses eight optical and electrical signals.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
QSFP DD pluggable optic with support for up to 4x112G physical
channels. Type 2 uses four optical and eight electrical
signals.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Cisco CPAK transceiver supporting 100 Gb/s.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Small form-factor pluggable transceiver supporting up to
10 Gb/s signal
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Enhanced small form-factor pluggable transceiver supporting
up to 16 Gb/s signals, including 10 GbE and OTU2
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Compact Small form-factor pluggable transceiver. It is a version
of SFP with the same mechanical form factor allowing two independent
bidirectional channels per port.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Small form-factor pluggable transceiver supporting up to
25 Gb/s signal
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Small form-factor pluggable transceiver supporting up to
50 Gb/s signal
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
SFP-DD electrical interfaces will employ 2 lanes that operate up to
25 Gbps NRZ modulation or 56 Gbps PAM4 modulation, providing
solutions up to 50 Gbps or 112 Gbps PAM4 aggregate
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
A transceiver implementing the DSFP Transceiver specification
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
10 Gigabit small form factor pluggable transceiver supporting
10 GbE and OTU2
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
10 Gigabit small form factor pluggable transceiver supporting
10 GbE using a XAUI inerface and 4 data channels.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Octal small form factor pluggable transceiver supporting
400 Gb/s or 800 Gb/s.
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Represents a port that does not require a pluggable optic,
e.g., with on-board optics like COBO
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Represents a transceiver form factor not otherwise listed
base identity: TRANSCEIVER_FORM_FACTOR_TYPE
description:
Type of optical fiber connector
description:
SC type fiber connector
base identity: FIBER_CONNECTOR_TYPE
description:
LC type fiber connector
base identity: FIBER_CONNECTOR_TYPE
description:
MPO (multi-fiber push-on/pull-off) type fiber connector
1x12 fibers
base identity: FIBER_CONNECTOR_TYPE
description:
AOC (active optical cable) type fiber connector
base identity: FIBER_CONNECTOR_TYPE
description:
DAC (direct attach copper) type fiber connector
base identity: FIBER_CONNECTOR_TYPE
description:
Ethernet compliance codes (PMD) supported by transceivers
description:
Ethernet compliance code: ETH_1000BASE_LX10
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_LRM
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_LR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_ZR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_ER
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 10GBASE_SR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 25GBASE_LR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 25GBASE_SR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_CR4.
This PMD is used in Direct Attach Cables (DAC)
and Active Optical Cables (AOC)
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_SR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_LR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_ER4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 40GBASE_PSM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 4x10GBASE_LR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 4x10GBASE_SR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100G_AOC
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100G_ACC
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_SR10
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_SR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_LR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_ER4L
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_ER4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_CWDM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_CLR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_PSM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_CR4.
This PMD is used in Direct Attach Cables (DAC)
and Active Optical Cables (AOC)
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_FR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 100GBASE_DR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 400GBASE_ZR
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 400GBASE_LR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 400GBASE_FR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 400GBASE_LR8
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 400GBASE_DR4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: 400GMSA_PSM4
base identity: ETHERNET_PMD_TYPE
description:
Ethernet compliance code: undefined
base identity: ETHERNET_PMD_TYPE
description:
Supported SONET/SDH application codes
description:
SONET/SDH application code: VSR2000_3R2
base identity: SONET_APPLICATION_CODE
description:
SONET/SDH application code: VSR2000_3R3
base identity: SONET_APPLICATION_CODE
description:
SONET/SDH application code: VSR2000_3R5
base identity: SONET_APPLICATION_CODE
description:
SONET/SDH application code: undefined
base identity: SONET_APPLICATION_CODE
description:
Supported OTN application codes
description:
OTN application code: P1L1_2D1
base identity: OTN_APPLICATION_CODE
description:
OTN application code: P1S1_2D2
base identity: OTN_APPLICATION_CODE
description:
OTN application code: P1L1_2D2
base identity: OTN_APPLICATION_CODE
description:
OTN application code: undefined
base identity: OTN_APPLICATION_CODE
description:
Rate of tributary signal _- identities will typically reflect
rounded bit rate.
description:
1G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2.5G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
10G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
40G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
100G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
150G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
200G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
250G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
300G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
350G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
400G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
450G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
500G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
550G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
600G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
650G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
700G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
750G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
800G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
850G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
900G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
950G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1000G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1050G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1100G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1150G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1200G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1250G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1300G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1350G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1400G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1450G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1500G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1550G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1600G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1650G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1700G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1750G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1800G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1850G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1900G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
1950G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2000G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2050G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2100G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2150G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2200G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2250G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2300G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2350G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2400G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2450G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2500G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2550G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2600G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2650G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2700G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2750G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2800G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2850G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2900G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
2950G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
3000G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
3050G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
3100G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
3150G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
3200G tributary signal rate
base identity: TRIBUTARY_RATE_CLASS_TYPE
description:
Type of protocol framing used on the logical channel or
tributary
description:
Ethernet protocol framing
base identity: LOGICAL_ELEMENT_PROTOCOL_TYPE
description:
OTN protocol framing
base identity: LOGICAL_ELEMENT_PROTOCOL_TYPE
description:
Types of fiber jumpers used for connecting device ports
description:
Simplex fiber jumper
base identity: FIBER_JUMPER_TYPE
description:
One strand of a fiber jumper which contains multiple fibers
within it, such as an MPO based fiber jumper
base identity: FIBER_JUMPER_TYPE
description:
Type definition for optical transport port types
description:
Ingress port, corresponding to a signal entering
a line system device such as an amplifier or wavelength
router.
base identity: OPTICAL_PORT_TYPE
description:
Egress port, corresponding to a signal exiting
a line system device such as an amplifier or wavelength
router.
base identity: OPTICAL_PORT_TYPE
description:
Add port, corresponding to a signal injected
at a wavelength router.
base identity: OPTICAL_PORT_TYPE
description:
Drop port, corresponding to a signal dropped
at a wavelength router.
base identity: OPTICAL_PORT_TYPE
description:
Monitor port, corresponding to a signal used by an optical
channel monitor. This is used to represent the connection
that a channel monitor port is connected to, typically on a
line system device. This connection may be via physical cable
and faceplate ports or internal to the device
base identity: OPTICAL_PORT_TYPE
description:
Client-facing port on a terminal optics device (e.g.,
transponder or muxponder).
base identity: OPTICAL_PORT_TYPE
description:
Line-facing port on a terminal optics device (e.g.,
transponder or muxponder).
base identity: OPTICAL_PORT_TYPE
description:
Type definition for optical transport client mapping modes.
description:
1 x 100G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
1 x 200G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
1 x 400G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
2 x 100G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
2 x 200G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
3 x 100G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
4 x 100G client mapping mode.
base identity: CLIENT_MAPPING_MODE
description:
Type definition for transceiver module functional types.
description:
Standard optic using a grey wavelength (i.e. 1310, 1550, etc.)
and on-off-keying (OOK) modulation.
base identity: TRANSCEIVER_MODULE_FUNCTIONAL_TYPE
description:
Digital coherent module which transmits a phase / amplitude
modulated signal and uses a digital signal processor to receive
and decode the received signal.
base identity: TRANSCEIVER_MODULE_FUNCTIONAL_TYPE
This module defines data types (e.g., YANG identities) to support the OpenConfig component inventory model.
openconfig-types
openconfig-extensions
description:
A generic type reflecting whether a hardware component
is powered on or off
type: enumeration
description:
A generic type reflecting the component's redundanty role.
For example, a device might have dual supervisors components
for redundant purpose, with one being the primary and the
other secondary.
type: enumeration
description:
Records how the role switchover is triggered.
type: enumeration
description:
Records how the last power-off was triggered.
type: enumeration
description:
Base identity for hardware related components in a managed
device. Derived identities are partially based on contents
of the IANA Entity MIB.
description:
Chassis component, typically with multiple slots / shelves
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Backplane component for aggregating traffic, typically
contained in a chassis component
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Interconnect between ingress and egress ports on the
device (e.g., a crossbar switch).
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Component that is supplying power to the device
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Cooling fan, or could be some other heat-reduction component
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Contains multiple fans that work in unison to cool the router components.
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Controls the fan trays.
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Physical sensor, e.g., a temperature sensor in a chassis
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Replaceable hardware component that does not have a more
specific defined schema.
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Linecard component, typically inserted into a chassis slot
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
A type of linecard whose primary role is management or control
rather than data forwarding.
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Physical port, e.g., for attaching pluggables and networking
cables
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Pluggable module present in a port
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Processing unit, e.g., a management processor
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
A storage subsystem on the device (disk, SSD, etc.)
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
A special purpose processing unit, typically for traffic
switching/forwarding (e.g., switching ASIC, NPU, forwarding
chip, etc.)
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
A device that attaches to a an Ethernet network and creates a wireless
local area network
base identity: OPENCONFIG_HARDWARE_COMPONENT
description:
Base identity for software-related components in a managed
device
description:
Operating system running on a component
base identity: OPENCONFIG_SOFTWARE_COMPONENT
description:
An operating system update - which should be a subcomponent
of the `OPERATING_SYSTEM` running on a component. An update is
defined to be a set of software changes that are atomically
installed (and uninstalled) together. Multiple updates may be
present for the Operating System. A system should not list all
installed software packages using this type -- but rather
updates that are bundled together as a single installable
item
base identity: OPENCONFIG_SOFTWARE_COMPONENT
description:
Legacy BIOS or UEFI firmware interface responsible for
initializing hardware components and first stage boot loader.
base identity: OPENCONFIG_SOFTWARE_COMPONENT
description:
Software layer responsible for loading and booting the
device OS or network OS.
base identity: OPENCONFIG_SOFTWARE_COMPONENT
description:
A base identity for software modules installed and/or
running on the device. Modules include user-space programs
and kernel modules that provide specific functionality.
A component with type SOFTWARE_MODULE should also have a
module type that indicates the specific type of software module
base identity: OPENCONFIG_SOFTWARE_COMPONENT
description:
Current operational status of a platform component
description:
Component is enabled and active (i.e., up)
base identity: COMPONENT_OPER_STATUS
description:
Component is enabled but inactive (i.e., down)
base identity: COMPONENT_OPER_STATUS
description:
Component is administratively disabled.
base identity: COMPONENT_OPER_STATUS
description:
Base identity for FEC operational modes.
description:
FEC is administratively enabled.
base identity: FEC_MODE_TYPE
description:
FEC is administratively disabled.
base identity: FEC_MODE_TYPE
description:
System will determine whether to enable or disable
FEC on a transceiver.
base identity: FEC_MODE_TYPE
description:
Base identity for FEC operational statuses.
description:
FEC is operationally locked.
base identity: FEC_STATUS_TYPE
description:
FEC is operationally unlocked.
base identity: FEC_STATUS_TYPE
description:
Base entity for component reboot reasons.
description:
User initiated the reboot of the componenent.
base identity: COMPONENT_REBOOT_REASON
description:
The component reboots due to power failure.
base identity: COMPONENT_REBOOT_REASON
description:
The component reboots due to critical errors.
base identity: COMPONENT_REBOOT_REASON
This module defines common data elements for OpenConfig data models for optical transport line system elements, such as amplifiers and ROADMs (wavelength routers).
iana-if-type
openconfig-extensions
openconfig-interfaces
openconfig-platform
openconfig-types
openconfig-transport-types
openconfig-platform-transceiver
This model describes configuration and operational state data for optical amplifiers, deployed as part of a transport line system.
openconfig-platform
openconfig-transport-line-common
openconfig-types
openconfig-extensions
description:
Type definition for different types of optical amplifiers
description:
Erbium doped fiber amplifer (EDFA)
base identity: OPTICAL_AMPLIFIER_TYPE
description:
Forward pumping Raman amplifier
base identity: OPTICAL_AMPLIFIER_TYPE
description:
Backward pumping Raman amplifier
base identity: OPTICAL_AMPLIFIER_TYPE
description:
Hybrid backward pumping Raman + EDFA amplifier
base identity: OPTICAL_AMPLIFIER_TYPE
description:
Base type for expressing the gain range for a switched gain
amplifier. The gain range is expressed as a generic setting,
e.g., LOW/MID/HIGH. The actual db range will be determined
by the implementation.
description:
LOW gain range setting
base identity: GAIN_RANGE
description:
MID gain range setting
base identity: GAIN_RANGE
description:
HIGH gain range setting
base identity: GAIN_RANGE
description:
Fixed or non-switched gain amplfier
base identity: GAIN_RANGE
description:
Type definition for different types of optical amplifier
operating modes
description:
Constant power mode. In constant power mode, the amplifier
will maintain a constant output power by adjusting the
amplifier gain and/or related variable optical attenuators
base identity: OPTICAL_AMPLIFIER_MODE
description:
Constant gain mode. In constant gain mode, the amplifier
will maintain a constant amplifier gain
base identity: OPTICAL_AMPLIFIER_MODE
description:
Dynamic gain mode. In dynamic gain mode, the amplifier will
automatically adjust gain to stay within parameters defined
by:
- target-gain
- min-gain
- max-gain
base identity: OPTICAL_AMPLIFIER_MODE
description:
Type definition for different profiles of fiber types
description:
Dispersion shifted fiber
base identity: FIBER_TYPE_PROFILE
description:
Large effective area fiber
base identity: FIBER_TYPE_PROFILE
description:
Standard single mode fiber
base identity: FIBER_TYPE_PROFILE
description:
True wave classic
base identity: FIBER_TYPE_PROFILE
description:
True wave reduced slope
base identity: FIBER_TYPE_PROFILE
description:
Enclosing container for amplifiers and supervisory channels
nodetype: container (rw)
description:
Enclosing container for list of amplifiers
nodetype: container (rw)
description:
List of optical amplifiers present in the device
nodetype: list (rw)
list keys: [name]
description:
Reference to the name of the amplifier
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the amplifier
nodetype: container (rw)
description:
User-defined name assigned to identify a specific amplifier
in the device
nodetype: leaf (rw)
type: string
description:
Type of the amplifier
nodetype: leaf (rw)
type: identityref
description:
Positive gain applied by the amplifier. This is used
when the amp-mode is in CONSTANT_GAIN or DYNAMIC_GAIN
mode to set the target gain that the amplifier should
achieve.
nodetype: leaf (rw)
type: decimal64
units: dB
description:
The minimum allowed gain of the amplifier. This is used
when the amp-mode is in CONSTANT_POWER or DYNAMIC_GAIN mode
to prevent the gain from dropping below a desired threshold.
If left empty, the platform will apply a minimum gain based
on hardware specifications.
nodetype: leaf (rw)
type: decimal64
units: dBm
description:
The maximum allowed gain of the amplifier. This is used
when the amp-mode is in CONSTANT_POWER or DYNAMIC_GAIN mode
to prevent the gain from exceeding a desired threshold. If
left empty, the platform will apply a maximum gain based on
hardware specifications.
nodetype: leaf (rw)
type: decimal64
units: dBm
description:
Gain tilt control
nodetype: leaf (rw)
type: decimal64
units: dB
description:
Selected gain range. The gain range is a platform-defined
value indicating the switched gain amplifier setting
nodetype: leaf (rw)
type: identityref
description:
The operating mode of the amplifier
nodetype: leaf (rw)
type: identityref
description:
Output optical power of the amplifier.
nodetype: leaf (rw)
type: decimal64
units: dBm
description:
The maximum optical output power of the amplifier. This
may be used to prevent the output power from exceeding a
desired threshold.
nodetype: leaf (rw)
type: decimal64
units: dBm
description:
Turns power on / off to the amplifiers gain module.
nodetype: leaf (rw)
type: boolean
description:
The fiber type profile specifies details about the
fiber type which are needed to accurately determine
the gain and perform efficient amplification. This is
only needed for Raman type amplifiers.
nodetype: leaf (rw)
type: identityref
description:
Operational state data for the amplifier
nodetype: container (ro)
description:
User-defined name assigned to identify a specific amplifier
in the device
nodetype: leaf (ro)
type: string
description:
Type of the amplifier
nodetype: leaf (ro)
type: identityref
description:
Positive gain applied by the amplifier. This is used
when the amp-mode is in CONSTANT_GAIN or DYNAMIC_GAIN
mode to set the target gain that the amplifier should
achieve.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The minimum allowed gain of the amplifier. This is used
when the amp-mode is in CONSTANT_POWER or DYNAMIC_GAIN mode
to prevent the gain from dropping below a desired threshold.
If left empty, the platform will apply a minimum gain based
on hardware specifications.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum allowed gain of the amplifier. This is used
when the amp-mode is in CONSTANT_POWER or DYNAMIC_GAIN mode
to prevent the gain from exceeding a desired threshold. If
left empty, the platform will apply a maximum gain based on
hardware specifications.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
Gain tilt control
nodetype: leaf (ro)
type: decimal64
units: dB
description:
Selected gain range. The gain range is a platform-defined
value indicating the switched gain amplifier setting
nodetype: leaf (ro)
type: identityref
description:
The operating mode of the amplifier
nodetype: leaf (ro)
type: identityref
description:
Output optical power of the amplifier.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum optical output power of the amplifier. This
may be used to prevent the output power from exceeding a
desired threshold.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
Turns power on / off to the amplifiers gain module.
nodetype: leaf (ro)
type: boolean
description:
The fiber type profile specifies details about the
fiber type which are needed to accurately determine
the gain and perform efficient amplification. This is
only needed for Raman type amplifiers.
nodetype: leaf (ro)
type: identityref
description:
Reference to the system-supplied physical component that
the amplifier gain block is contained within. Multiple
amplifier gain blocks may be contained within the same
physical component.
nodetype: leaf (ro)
type: leafref
description:
Reference to system-supplied name of the amplifier ingress
port. This leaf is only valid for ports of type INGRESS.
nodetype: leaf (ro)
type: leafref
description:
Reference to system-supplied name of the amplifier egress
port. This leaf is only valid for ports of type EGRESS.
nodetype: leaf (ro)
type: leafref
description:
The actual gain applied by the amplifier in units of
0.01dB. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The minimum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The actual tilt applied by the amplifier in units of
0.01dB. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The minimum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The total input optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The C band (consisting of approximately 191 to 195 THz or
1530nm to 1565 nm) input optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The L band (consisting of approximately 184 to 191 THz or
1565 to 1625 nm) input optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The total output optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The C band (consisting of approximately 191 to 195 THz or
1530nm to 1565 nm)output optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The L band (consisting of approximately 184 to 191 THz or
1565 to 1625 nm)output optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The current applied by the system to the transmit laser to
achieve the output power. The current is expressed in mA
with up to two decimal precision. If avg/min/max statistics
are not supported, just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The optical return loss (ORL) is the ratio of the light
reflected back into the port to the light launched out of
the port. ORL is in units of 0.01dBm. If avg/min/max
statistics are not supported, just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Enclosing container for list of supervisory channels
nodetype: container (rw)
description:
List of supervisory channels
nodetype: list (rw)
list keys: [interface]
description:
Reference to the interface of the supervisory channel
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for OSCs
nodetype: container (rw)
description:
Reference to an OSC interface
nodetype: leaf (rw)
type: oc-if:base-interface-ref
description:
Operational state data for OSCs
nodetype: container (ro)
description:
Reference to an OSC interface
nodetype: leaf (ro)
type: oc-if:base-interface-ref
description:
The input optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
the target is expected to just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The output optical power of this port in units
of 0.01dBm. If avg/min/max statistics are not supported,
the target is expected to just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The current applied by the system to the transmit laser to
achieve the output power. The current is expressed in mA
with up to one decimal precision. If avg/min/max statistics
are not supported, the target is expected to just supply
the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The frequency in MHz of the individual physical channel
(e.g. ITU C50 - 195.0THz and would be reported as
195,000,000 MHz in this model). This attribute is not
configurable on most client ports In some cases, such as when
the physical channel has a leafref to an optical channel
component and the module-functional-type is
TYPE_DIGITAL_COHERENT_OPTIC this grouping will NOT be used
as the data will be within the optical-channel.
nodetype: leaf (ro)
type: oc-opt-types:frequency-type
This model describes operational state data for an optical channel monitor (OCM) for optical transport line system elements such as wavelength routers (ROADMs) and amplifiers.
openconfig-extensions
openconfig-interfaces
openconfig-platform
openconfig-transport-types
description:
Top-level container for optical channel monitors
nodetype: container (rw)
description:
List of channel monitors, keyed by channel monitor name.
nodetype: list (rw)
list keys: [name]
description:
References the optical channel monitor name
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data
nodetype: container (rw)
description:
Reference to system-supplied name of the port on the
optical channel monitor (OCM). If this port is embedded
in another card (i.e. an amplifier card) the device
should still define a port representing the OCM even if
it is internal and not physically present on the
faceplate of the card
nodetype: leaf (rw)
type: leafref
description:
Reference to system-supplied name of the port that the
channel monitor is physically connected to. This port
will be of type MONITOR. This port is a tap off of the
monitored-port and would be in the same card as the
monitored port. If this port is embedded in another card
(i.e. an amplifier card) the device should still define
a port representing the monitor port if it is internal
and not physically present on the faceplate of the card
nodetype: leaf (rw)
type: leafref
description:
Operational state data
nodetype: container (ro)
description:
Reference to system-supplied name of the port on the
optical channel monitor (OCM). If this port is embedded
in another card (i.e. an amplifier card) the device
should still define a port representing the OCM even if
it is internal and not physically present on the
faceplate of the card
nodetype: leaf (ro)
type: leafref
description:
Reference to system-supplied name of the port that the
channel monitor is physically connected to. This port
will be of type MONITOR. This port is a tap off of the
monitored-port and would be in the same card as the
monitored port. If this port is embedded in another card
(i.e. an amplifier card) the device should still define
a port representing the monitor port if it is internal
and not physically present on the faceplate of the card
nodetype: leaf (ro)
type: leafref
description:
Enclosing container for the list of values describing
the spectrum power distribution
nodetype: container (rw)
description:
List of tuples describing the spectrum power distribution
nodetype: list (ro)
list keys: [lower-frequency] [upper-frequency]
description:
Reference to the list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Reference to the list key
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational state data for spectrum power
nodetype: container (ro)
description:
Lower frequency of the specified spectrum power
nodetype: leaf (ro)
type: oc-opt-types:frequency-type
description:
Upper frequency of the specified spectrum power
nodetype: leaf (ro)
type: oc-opt-types:frequency-type
description:
Average measured optical power over the specified spectrum
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
Target optical power over the specified spectrum
nodetype: leaf (ro)
type: decimal64
units: dBm
This module defines a data model for representing a system component inventory, which can include hardware or software elements arranged in an arbitrary structure. The primary relationship supported by the model is containment, e.g., components containing subcomponents.
It is expected that this model reflects every field replacable unit on the device at a minimum (i.e., additional information may be supplied about non-replacable components).
Every element in the inventory is termed a 'component' with each component expected to have a unique name and type, and optionally a unique system-assigned identifier and FRU number. The uniqueness is guaranteed by the system within the device.
Components may have properties defined by the system that are modeled as a list of key-value pairs. These may or may not be user-configurable. The model provides a flag for the system to optionally indicate which properties are user configurable.
Each component also has a list of 'subcomponents' which are references to other components. Appearance in a list of subcomponents indicates a containment relationship as described above. For example, a linecard component may have a list of references to port components that reside on the linecard.
This schema is generic to allow devices to express their own platform-specific structure. It may be augmented by additional component type-specific schemas that provide a common structure for well-known component types. In these cases, the system is expected to populate the common component schema, and may optionally also represent the component and its properties in the generic structure.
The properties for each component may include dynamic values, e.g., in the 'state' part of the schema. For example, a CPU component may report its utilization, temperature, or other physical properties. The intent is to capture all platform- specific physical data in one location, including inventory (presence or absence of a component) and state (physical attributes or status).
openconfig-platform-types
openconfig-extensions
openconfig-alarm-types
openconfig-yang-types
openconfig-types
description:
Enclosing container for the components in the system.
nodetype: container (rw)
description:
List of components, keyed by component name.
nodetype: list (rw)
list keys: [name]
description:
References the component name
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each component
nodetype: container (rw)
description:
Device name for the component -- this may not be a
configurable parameter on many implementations. Where
component preconfiguration is supported, for example,
the component name may be configurable.
nodetype: leaf (rw)
type: string
description:
Operational state data for each component
nodetype: container (ro)
description:
Device name for the component -- this may not be a
configurable parameter on many implementations. Where
component preconfiguration is supported, for example,
the component name may be configurable.
nodetype: leaf (ro)
type: string
description:
Type of component as identified by the system
nodetype: leaf (ro)
type: union
type: identityref
type: identityref
description:
Unique identifier assigned by the system for the
component
nodetype: leaf (ro)
type: string
description:
System-supplied description of the location of the
component within the system. This could be a bay position,
slot number, socket location, etc. For component types that
have an explicit slot-id attribute, such as linecards, the
system should populate the more specific slot-id.
This leaf is deprecated and replaced by install-position and
install-component.
nodetype: leaf (ro)
type: string
description:
System-supplied index to a position where this component is
installed. The position may be referred in device documenation
as a port, slot, bay, socket, etc. This string must only
indicate the name of the position, and not any indication of
the name of the parent component within the system. Instead,
parent component name should be present in the 'parent' leaf.
Typically the install-position is a number, but it is observed
that some devices may use letters or alphanumerics. The
position name should be the same name used to physically
identify the position in documentation or printed on the
device.
Any component which is removable is expected to have
an install-position and an install-component which points to
an ancestor component where the connection occurs.
For component types that have an explicit slot-id attribute,
such as LINECARD, the system should populate slot-id,
install-position and install-component. This will facilitate a
transition to deprecate slot-id.
nodetype: leaf (ro)
type: string
description:
This leaf contains the name of the ancestor component which
contains the 'install-position'. This creates a distinct
mapping between a removable component and the target component
it is installed into. Note there may be zero or more
intermediate components between the removable component and
the install-component.
For example, consider the component tree
PORT ['eth1/2']-> INTEGRATED_CIRCUIT ['npu1']-> LINECARD ['lc1'].
The PORT has an install-position of '2' and install-component named
'lc1'. The intermediate INTEGRATED-CIRCUIT component is not
present in either install-position or install-component leaves.
nodetype: leaf (ro)
type: leafref
description:
System-supplied description of the component
nodetype: leaf (ro)
type: string
description:
System-supplied identifier for the manufacturer of the
component. This data is particularly useful when a
component manufacturer is different than the overall
device vendor.
nodetype: leaf (ro)
type: string
description:
System-supplied representation of the component's
manufacturing date.
nodetype: leaf (ro)
type: oc-yang:date
description:
For hardware components, this is the hardware revision of
the component.
nodetype: leaf (ro)
type: string
description:
For hardware components, this is the version of associated
firmware that is running on the component, if applicable.
nodetype: leaf (ro)
type: string
description:
For software components such as operating system or other
software module, this is the version of the currently
running software.
nodetype: leaf (ro)
type: string
description:
System-assigned serial number of the component.
nodetype: leaf (ro)
type: string
description:
System-assigned part number for the component. This should
be present in particular if the component is also an FRU
(field replaceable unit)
nodetype: leaf (ro)
type: string
description:
Model name that would be found in a catalog of stock keeping
units (SKU) and should be the orderable name of the
component.
nodetype: leaf (ro)
type: string
description:
Common Language Equipment Identifier (CLEI) code of the
component. This should be present in particular if the
component is also an FRU (field replaceable unit)
nodetype: leaf (ro)
type: string
description:
If true, this component is removable or is a field
replaceable unit
nodetype: leaf (ro)
type: boolean
description:
If applicable, this reports the current operational status
of the component.
nodetype: leaf (ro)
type: identityref
description:
The empty leaf may be used by the device to indicate that a
component position exists but is not populated. Using this
flag, it is possible for the management system to learn how
many positions are available (e.g., occupied vs. empty
linecard slots in a chassis).
nodetype: leaf (ro)
type: boolean
default: false
description:
Reference to the name of the parent component. Note that
this reference must be kept synchronized with the
corresponding subcomponent reference from the parent
component.
nodetype: leaf (ro)
type: leafref
description:
For components that have redundant roles (e.g. two
supervisors in a device, one as primary the other as secondary),
this reports the role of the component.
nodetype: leaf (ro)
type: oc-platform-types:component-redundant-role
description:
Records last power-off reason for a component.
nodetype: container (ro)
description:
Records the generic triggers for the last poweroff
event. Component power-off can be triggered
in various ways,
- USER_INITIATED
- SYSTEM_INITIATED
- POWER_FAILURE
This field is not updated during reboots; those are
tracked in the 'last-reboot-reason' leaf.
nodetype: leaf (ro)
type: component-last-poweroff-reason-trigger
description:
Provides a detailed reason for component power-off.
For system-initiated power-offs, this field can include
specific causes (e.g., critical errors resulting in a
controller-card bootloop).
nodetype: leaf (ro)
type: string
description:
This records the last time a component was directly powered
down. The value is a Unix Epoch timestamp (nanoseconds since
Jan 1, 1970 00:00:00 UTC). Component power-off can be:
- USER_INITIATED
- SYSTEM_INITIATED
- POWER_FAILURE
This field is not updated during reboots; those are tracked
in the 'last-reboot-time' leaf.
nodetype: leaf (ro)
type: oc-types:timeticks64
units: nanoseconds
description:
For components that have redundant roles (e.g. two
supervisors in a device, one as primary the other as secondary),
this reports the reason of the last change of the
component's role.
nodetype: container (ro)
description:
Records the generic triggers, e.g. user or system
initiated the switchover.
nodetype: leaf (ro)
type: component-redundant-role-switchover-reason-trigger
description:
Records detailed description of why the switchover happens.
For example, when system initiated the switchover, this leaf
can be used to record the specific reason, e.g. due to critical
errors of the routing daemon in the primary role.
nodetype: leaf (ro)
type: string
description:
For components that have redundant roles (e.g. two
supervisors in a device, one as primary the other as
secondary), this reports the time of the last change of
the component's role. The value is the timestamp in
nanoseconds relative to the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
units: nanoseconds
description:
This reports the reason of the last reboot of the component.
nodetype: leaf (ro)
type: identityref
description:
This reports the time of the last reboot of the component. The
value is the timestamp in nanoseconds relative to the Unix Epoch
(Jan 1, 1970 00:00:00 UTC). This timer is not updated during
power shutdowns; those are tracked in 'last-poweroff-time' leaf.
nodetype: leaf (ro)
type: oc-types:timeticks64
units: nanoseconds
description:
For components that have redundant roles, this reports a value
that indicates if the component is ready to support failover.
The components with a redundant-role should reflect the overall
system's switchover status. For example, two supervisors in a
device, one as primary and the other as secondary, should both
report the same value.
nodetype: leaf (ro)
type: boolean
description:
This is a MAC address representing the root or primary MAC
address for a component. Components such as CHASSIS and
CONTROLLER_CARD are expected to provide a base-mac-address. The
base mac-address for CHASSIS and a PRIMARY CONTROLLER_CARD may
contain the same value.
nodetype: leaf (ro)
type: oc-yang:mac-address
description:
Temperature in degrees Celsius of the component. Values include
the instantaneous, average, minimum, and maximum statistics. If
avg/min/max statistics are not supported, the target is expected
to just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
A value of true indicates the alarm has been raised or
asserted. The value should be false when the alarm is
cleared.
nodetype: leaf (ro)
type: boolean
description:
The threshold value that was crossed for this alarm.
nodetype: leaf (ro)
type: uint32
description:
The severity of the current alarm.
nodetype: leaf (ro)
type: identityref
description:
For components that have associated memory, these values
report information about available and utilized memory.
nodetype: container (ro)
description:
The available memory physically installed, or logically
allocated to the component.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
The memory currently in use by processes running on
the component, not considering reserved memory that is
not available for use.
nodetype: leaf (ro)
type: uint64
units: bytes
description:
Power allocated by the system for the component.
nodetype: leaf (ro)
type: uint32
units: watts
description:
Actual power used by the component.
nodetype: leaf (ro)
type: uint32
units: watts
description:
Components that are connected to the system over the Peripheral
Component Interconnect Express (PCIe), report the fatal, non-fatal
and correctable PCIe error counts.
nodetype: container (ro)
description:
The count of the fatal PCIe errors.
nodetype: container (ro)
description:
Total number of uncorrectable errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of undefined errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of data-link errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of unexpected link down errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of poisoned TLP errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of flow control protocol errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of completion timeout errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of completion abort errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of unexpected completion errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of receiver overflow errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of malformed TLP errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of ECRC errors detected by PCIe device since the system
booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of unsupported request errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of access control errors detected by PCIe device since
the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of internal errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of blocked TLP errors detected by PCIe device since
the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of atomic operation blocked errors detected by PCIe
device since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of TLP prefix blocked errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The count of the non-fatal PCIe errors.
nodetype: container (ro)
description:
Total number of uncorrectable errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of undefined errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of data-link errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of unexpected link down errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of poisoned TLP errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of flow control protocol errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of completion timeout errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of completion abort errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of unexpected completion errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of receiver overflow errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of malformed TLP errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of ECRC errors detected by PCIe device since the system
booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of unsupported request errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of access control errors detected by PCIe device since
the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of internal errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of blocked TLP errors detected by PCIe device since
the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of atomic operation blocked errors detected by PCIe
device since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of TLP prefix blocked errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
The count of the correctable PCIe errors.
nodetype: container (ro)
description:
Total number of correctable errors detected by PCIe device
since the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of receiver errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of TLPs with bad LCRC detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of DLLPs with bad LCRC detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of relay rollover errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of replay timeout errors detected by PCIe device since the
system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of advisory non fatal errors detected by PCIe device since
the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of internal errors detected by PCIe device since the system
booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Number of header log overflow errors detected by PCIe device since
the system booted, according to PCIe AER driver.
nodetype: leaf (ro)
type: oc-yang:counter64
description:
Enclosing container
nodetype: container (rw)
description:
List of system properties for the component
nodetype: list (rw)
list keys: [name]
description:
Reference to the property name.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each property
nodetype: container (rw)
description:
System-supplied name of the property -- this is typically
non-configurable
nodetype: leaf (rw)
type: string
description:
Property values can take on a variety of types. Signed and
unsigned integer types may be provided in smaller sizes,
e.g., int8, uint16, etc.
nodetype: leaf (rw)
type: union
type: string
type: boolean
type: int64
type: uint64
type: decimal64
description:
Operational state data for each property
nodetype: container (ro)
description:
System-supplied name of the property -- this is typically
non-configurable
nodetype: leaf (ro)
type: string
description:
Property values can take on a variety of types. Signed and
unsigned integer types may be provided in smaller sizes,
e.g., int8, uint16, etc.
nodetype: leaf (ro)
type: union
type: string
type: boolean
type: int64
type: uint64
type: decimal64
description:
Indication whether the property is user-configurable
nodetype: leaf (ro)
type: boolean
description:
Enclosing container for subcomponent references
nodetype: container (rw)
description:
List of subcomponent references
nodetype: list (rw)
list keys: [name]
description:
Reference to the name list key
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for the subcomponent
nodetype: container (rw)
description:
Reference to the name of the subcomponent
nodetype: leaf (rw)
type: leafref
description:
Operational state data for the subcomponent
nodetype: container (ro)
description:
Reference to the name of the subcomponent
nodetype: leaf (ro)
type: leafref
description:
Data for chassis components
nodetype: container (rw)
description:
Configuration data for chassis components
nodetype: container (rw)
description:
Operational state data for chassis components
nodetype: container (ro)
description:
Resource utilization of the component.
nodetype: container (rw)
description:
Enclosing container for the resources in this component.
nodetype: container (rw)
description:
List of resources, keyed by resource name.
nodetype: list (rw)
list keys: [name]
description:
References the resource name.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each resource.
nodetype: container (rw)
description:
Resource name within the component.
nodetype: leaf (rw)
type: string
description:
The used percentage value (used / (used + free) * 100) that
when crossed will set utilization-threshold-exceeded to 'true'.
nodetype: leaf (rw)
type: oc-types:percentage
description:
The used percentage value (used / (used + free) * 100) that when
crossed will set utilization-threshold-exceeded to 'false'.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Operational state data for each resource.
nodetype: container (ro)
description:
Resource name within the component.
nodetype: leaf (ro)
type: string
description:
The used percentage value (used / (used + free) * 100) that
when crossed will set utilization-threshold-exceeded to 'true'.
nodetype: leaf (ro)
type: oc-types:percentage
description:
The used percentage value (used / (used + free) * 100) that when
crossed will set utilization-threshold-exceeded to 'false'.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Number of entries currently in use for the resource.
nodetype: leaf (ro)
type: uint64
description:
Number of entries currently reserved for this resource. This is only
relevant to tables which allocate a block of resource for a given
feature.
nodetype: leaf (ro)
type: uint64
description:
Number of entries available to use.
nodetype: leaf (ro)
type: uint64
description:
Maximum number of entries available for the resource. The value
is the theoretical maximum resource utilization possible.
nodetype: leaf (ro)
type: uint64
description:
A watermark of highest number of entries used for this resource.
nodetype: leaf (ro)
type: uint64
description:
The timestamp when the high-watermark was last updated. The value
is the timestamp in nanoseconds relative to the Unix Epoch
(Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
This value is set to true when the used percentage value
(used / (used + free) * 100) has crossed the used-threshold-upper for this
resource and false when the used percentage value has crossed the configured
used-threshold-upper-clear value for this resource.
nodetype: leaf (ro)
type: boolean
description:
Data for physical port components
nodetype: container (rw)
description:
Configuration data for physical port components
nodetype: container (rw)
description:
Operational state data for physical port components
nodetype: container (ro)
description:
Top-level container for port breakout-mode data.
nodetype: container (rw)
description:
Top level container for breakout groups data.
When a device has the capability to break a port into
interfaces of different speeds and different number of
physical channels, it can breakout a 400G OSFP port with
8 physical channels (with support for 25G NRZ, 50G PAM4
and 100G PAM4) into mixed speed interfaces. Particularly, to
break out into two 100G ports with different modulation, and a 200G
port, a user must configure 1 interface with 2 physical channels
1 interface with 4 physical channels and 1 interface with
2 physical channels. With this configuration the interface in
1st breakout group would use 50G PAM4 modulation, interface
in 2nd breakout group would use 25G NRZ modulation and the
interface in 3rd breakout group would use 100G PAM4 modulation
This configuration would result in 3 entries in the breakout
groups list. The example configuration for this case is shown below:
{
"groups": {
"group": [
{
"config": {
"breakout-speed": "SPEED_100GB",
"index": 0,
"num-breakouts": 1,
"num-physical-channels": 2
},
"index": 0
},
{
"config": {
"breakout-speed": "SPEED_100GB",
"index": 1,
"num-breakouts": 1,
"num-physical-channels": 4
},
"index": 1
},
{
"config": {
"breakout-speed": "SPEED_200GB",
"index": 2,
"num-breakouts": 1,
"num-physical-channels": 2
},
"index": 2
}
]
}
}
When a device does not have the capability to break a port
into interfaces of different speeds and different number of
physical channels, in order to breakout a 400G OSFP port with
8 physical channels into 50G breakout ports it would use 8 interfaces
with 1 physical channel each. This would result in 1 entry in the
breakout groups list. The example configuration for this case is
shown below:
{
"groups": {
"group": [
{
"config": {
"breakout-speed": "SPEED_50GB",
"index": 0,
"num-breakouts": 8,
"num-physical-channels": 1
},
"index": 0
}
]
}
}
Similarly, if a 400G-DR4 interface (8 electrical channels at 50Gbps)
is to be broken out into 4 100Gbps ports, the following configuration
is used:
{
"groups": {
"group": [
{
"config": {
"breakout-speed": "SPEED_100GB",
"index": 0,
"num-breakouts": 4,
"num-physical-channels": 2
},
"index": 0
}
]
}
}
nodetype: container (rw)
description:
List of breakout groups.
nodetype: list (rw)
list keys: [index]
description:
Index of the breakout group entry in the breakout groups list.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for breakout group.
nodetype: container (rw)
description:
Each index specifies breakouts that are identical in
terms of speed and the number of physical channels.
nodetype: leaf (rw)
type: uint8
description:
Sets the number of interfaces using this breakout group.
nodetype: leaf (rw)
type: uint8
description:
Speed of interfaces in this breakout group, supported
values are defined by the ETHERNET_SPEED identity.
nodetype: leaf (rw)
type: identityref
description:
Sets the number of lanes or physical channels assigned
to the interfaces in this breakout group. This leaf need
not be set if there is only one breakout group where all
the interfaces are of equal speed and have equal number
of physical channels.
The physical channels referred to by this leaf are
electrical channels towards the transceiver.
nodetype: leaf (rw)
type: uint8
description:
Operational state data for breakout group.
nodetype: container (ro)
description:
Each index specifies breakouts that are identical in
terms of speed and the number of physical channels.
nodetype: leaf (ro)
type: uint8
description:
Sets the number of interfaces using this breakout group.
nodetype: leaf (ro)
type: uint8
description:
Speed of interfaces in this breakout group, supported
values are defined by the ETHERNET_SPEED identity.
nodetype: leaf (ro)
type: identityref
description:
Sets the number of lanes or physical channels assigned
to the interfaces in this breakout group. This leaf need
not be set if there is only one breakout group where all
the interfaces are of equal speed and have equal number
of physical channels.
The physical channels referred to by this leaf are
electrical channels towards the transceiver.
nodetype: leaf (ro)
type: uint8
description:
Contains data specific to ports on optical transport
devices.
nodetype: container (rw)
description:
Operational config data for optical ports
nodetype: container (rw)
description:
Sets the admin state of the optical-port
nodetype: leaf (rw)
type: oc-opt-types:admin-state-type
description:
Operational state data for optical ports
nodetype: container (ro)
description:
Sets the admin state of the optical-port
nodetype: leaf (ro)
type: oc-opt-types:admin-state-type
description:
For physical ports belonging to optical transport
devices, this indicates the type of optical port. This is an
informational field that should be made available by the
device.
nodetype: leaf (ro)
type: identityref
description:
The total tilt measured on the port. This is applicable to
ports of type INGRESS and EGRESS.
nodetype: leaf (ro)
type: decimal64
units: dB
description:
For line system device ports, this value indicates
the total input optical power of the port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
For line system device ports, this value indicates
the total output optical power of the port in units
of 0.01dBm. If avg/min/max statistics are not supported,
just supply the instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Data for power supply components
nodetype: container (rw)
description:
Configuration data for power supply components
nodetype: container (rw)
description:
Operational state data for power supply components
nodetype: container (ro)
description:
Data for fan components
nodetype: container (rw)
description:
Configuration data for fan components
nodetype: container (rw)
description:
Operational state data for fan components
nodetype: container (ro)
description:
Data for fabric components
nodetype: container (rw)
description:
Configuration data for fabric components
nodetype: container (rw)
description:
Operational state data for fabric components
nodetype: container (ro)
description:
Data for storage components
nodetype: container (rw)
description:
Configuration data for storage components
nodetype: container (rw)
description:
Operational state data for storage components
nodetype: container (ro)
description:
Data for cpu components
nodetype: container (rw)
description:
Configuration data for cpu components
nodetype: container (rw)
description:
Operational state data for cpu components
nodetype: container (ro)
description:
Data for chip components, such as ASIC, NPUs, etc.
nodetype: container (rw)
description:
Configuration data for chip components
nodetype: container (rw)
description:
Operational state data for chip components
nodetype: container (ro)
description:
Resource utilization of the component.
nodetype: container (rw)
description:
Enclosing container for the resources in this component.
nodetype: container (rw)
description:
List of resources, keyed by resource name.
nodetype: list (rw)
list keys: [name]
description:
References the resource name.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for each resource.
nodetype: container (rw)
description:
Resource name within the component.
nodetype: leaf (rw)
type: string
description:
The used percentage value (used / (used + free) * 100) that
when crossed will set utilization-threshold-exceeded to 'true'.
nodetype: leaf (rw)
type: oc-types:percentage
description:
The used percentage value (used / (used + free) * 100) that when
crossed will set utilization-threshold-exceeded to 'false'.
nodetype: leaf (rw)
type: oc-types:percentage
description:
Operational state data for each resource.
nodetype: container (ro)
description:
Resource name within the component.
nodetype: leaf (ro)
type: string
description:
The used percentage value (used / (used + free) * 100) that
when crossed will set utilization-threshold-exceeded to 'true'.
nodetype: leaf (ro)
type: oc-types:percentage
description:
The used percentage value (used / (used + free) * 100) that when
crossed will set utilization-threshold-exceeded to 'false'.
nodetype: leaf (ro)
type: oc-types:percentage
description:
Number of entries currently in use for the resource.
nodetype: leaf (ro)
type: uint64
description:
Number of entries currently reserved for this resource. This is only
relevant to tables which allocate a block of resource for a given
feature.
nodetype: leaf (ro)
type: uint64
description:
Number of entries available to use.
nodetype: leaf (ro)
type: uint64
description:
Maximum number of entries available for the resource. The value
is the theoretical maximum resource utilization possible.
nodetype: leaf (ro)
type: uint64
description:
A watermark of highest number of entries used for this resource.
nodetype: leaf (ro)
type: uint64
description:
The timestamp when the high-watermark was last updated. The value
is the timestamp in nanoseconds relative to the Unix Epoch
(Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
This value is set to true when the used percentage value
(used / (used + free) * 100) has crossed the used-threshold-upper for this
resource and false when the used percentage value has crossed the configured
used-threshold-upper-clear value for this resource.
nodetype: leaf (ro)
type: boolean
description:
Data for backplane components
nodetype: container (rw)
description:
Configuration data for backplane components
nodetype: container (rw)
description:
Operational state data for backplane components
nodetype: container (ro)
description:
Data for software module components, i.e., for components
with type=SOFTWARE_MODULE
nodetype: container (rw)
description:
Configuration data for software module components
nodetype: container (rw)
description:
Operational state data for software module components
nodetype: container (ro)
description:
Data for controller card components, i.e., for components
with type=CONTROLLER_CARD
nodetype: container (rw)
description:
Configuration data for controller card components.
nodetype: container (rw)
description:
Operational state data for controller card components
nodetype: container (ro)
description:
Top-level container for client port transceiver data
nodetype: container (rw)
description:
Configuration data for client port transceivers
nodetype: container (rw)
description:
Turns power on / off to the transceiver -- provides a means
to power on/off the transceiver (in the case of SFP, SFP+,
QSFP,...) or enable high-power mode (in the case of CFP,
CFP2, CFP4) and is optionally supported (device can choose to
always enable). True = power on / high power, False =
powered off
nodetype: leaf (rw)
type: boolean
description:
Indicates the type of optical transceiver used on this
port. If the client port is built into the device and not
pluggable, then non-pluggable is the corresponding state. If
a device port supports multiple form factors (e.g. QSFP28
and QSFP+, then the value of the transceiver installed shall
be reported. If no transceiver is present, then the value of
the highest rate form factor shall be reported
(QSFP28, for example).
The form factor is included in configuration data to allow
pre-configuring a device with the expected type of
transceiver ahead of deployment. The corresponding state
leaf should reflect the actual transceiver type plugged into
the system.
nodetype: leaf (rw)
type: identityref
description:
The Ethernet PMD is a property of the optical transceiver
used on the port, indicating the type of physical connection.
It is included in configuration data to allow pre-configuring
a port/transceiver with the expected PMD. The actual PMD is
indicated by the ethernet-pmd state leaf.
nodetype: leaf (rw)
type: identityref
description:
The FEC mode indicates the mode of operation for the
transceiver's FEC. This defines typical operational modes
and does not aim to specify more granular FEC capabilities.
nodetype: leaf (rw)
type: identityref
description:
Indicates the module functional type which represents the
functional capability of the transceiver. For example, this
would specify the module is a digital coherent optic or a
standard grey optic that performs on-off keying.
nodetype: leaf (rw)
type: identityref
description:
Operational state data for client port transceivers
nodetype: container (ro)
description:
Turns power on / off to the transceiver -- provides a means
to power on/off the transceiver (in the case of SFP, SFP+,
QSFP,...) or enable high-power mode (in the case of CFP,
CFP2, CFP4) and is optionally supported (device can choose to
always enable). True = power on / high power, False =
powered off
nodetype: leaf (ro)
type: boolean
description:
Indicates the type of optical transceiver used on this
port. If the client port is built into the device and not
pluggable, then non-pluggable is the corresponding state. If
a device port supports multiple form factors (e.g. QSFP28
and QSFP+, then the value of the transceiver installed shall
be reported. If no transceiver is present, then the value of
the highest rate form factor shall be reported
(QSFP28, for example).
The form factor is included in configuration data to allow
pre-configuring a device with the expected type of
transceiver ahead of deployment. The corresponding state
leaf should reflect the actual transceiver type plugged into
the system.
nodetype: leaf (ro)
type: identityref
description:
The Ethernet PMD is a property of the optical transceiver
used on the port, indicating the type of physical connection.
It is included in configuration data to allow pre-configuring
a port/transceiver with the expected PMD. The actual PMD is
indicated by the ethernet-pmd state leaf.
nodetype: leaf (ro)
type: identityref
description:
The FEC mode indicates the mode of operation for the
transceiver's FEC. This defines typical operational modes
and does not aim to specify more granular FEC capabilities.
nodetype: leaf (ro)
type: identityref
description:
Indicates the module functional type which represents the
functional capability of the transceiver. For example, this
would specify the module is a digital coherent optic or a
standard grey optic that performs on-off keying.
nodetype: leaf (ro)
type: identityref
description:
Indicates whether a transceiver is present in
the specified client port.
nodetype: leaf (ro)
type: enumeration
description:
Indicates the type of optical transceiver used on this
port. If the client port is built into the device and not
pluggable, then non-pluggable is the corresponding state. If
a device port supports multiple form factors (e.g. QSFP28
and QSFP+, then the value of the transceiver installed shall
be reported. If no transceiver is present, then the value of
the highest rate form factor shall be reported
(QSFP28, for example).
nodetype: leaf (ro)
type: identityref
description:
Connector type used on this port
nodetype: leaf (ro)
type: identityref
description:
Full name of transceiver vendor. 16-octet field that
contains ASCII characters, left-aligned and padded on the
right with ASCII spaces (20h)
nodetype: leaf (ro)
type: string
description:
Transceiver vendor's part number. 16-octet field that
contains ASCII characters, left-aligned and padded on the
right with ASCII spaces (20h). If part number is undefined,
all 16 octets = 0h
nodetype: leaf (ro)
type: string
description:
Transceiver vendor's revision number. Field of 1 to 4 octets that
contains ASCII characters, left-aligned and padded on the
right with ASCII spaces (20h)
nodetype: leaf (ro)
type: string
description:
Ethernet PMD (physical medium dependent sublayer) that the
transceiver supports. The SFF/QSFP MSAs have registers for
this and CFP MSA has similar.
nodetype: leaf (ro)
type: identityref
description:
SONET/SDH application code supported by the port
nodetype: leaf (ro)
type: identityref
description:
OTN application code supported by the port
nodetype: leaf (ro)
type: identityref
description:
Transceiver serial number. 16-octet field that contains
ASCII characters, left-aligned and padded on the right with
ASCII spaces (20h). If part serial number is undefined, all
16 octets = 0h
nodetype: leaf (ro)
type: string
description:
Representation of the transceiver date code, typically
stored as YYMMDD. The time portion of the value is
undefined and not intended to be read.
nodetype: leaf (ro)
type: oc-yang:date-and-time
description:
Indicates if a fault condition exists in the transceiver
nodetype: leaf (ro)
type: boolean
description:
Operational status of FEC
nodetype: leaf (ro)
type: identityref
description:
The number of blocks that were uncorrectable by the FEC
nodetype: leaf (ro)
type: yang:counter64
description:
The number of words that were uncorrectable by the FEC
nodetype: leaf (ro)
type: yang:counter64
description:
The number of bytes that were corrected by the FEC
nodetype: leaf (ro)
type: yang:counter64
description:
The number of bits that were corrected by the FEC
nodetype: leaf (ro)
type: yang:counter64
description:
Bit error rate before forward error correction -- computed
value with 18 decimal precision. Note that decimal64
supports values as small as i x 10^-18 where i is an
integer. Values smaller than this should be reported as 0
to inidicate error free or near error free performance.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Bit error rate after forward error correction -- computed
value with 18 decimal precision. Note that decimal64
supports values as small as i x 10^-18 where i is an
integer. Values smaller than this should be reported as 0
to inidicate error free or near error free performance.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: bit-errors-per-second
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Supply voltage to the transceiver in volts with 2 decimal
precision. Values include the instantaneous, average, minimum,
and maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the instant
value.
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: volts
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: volts
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: volts
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: volts
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The output optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value. In some cases, such as when the physical
channel has a leafref to an optical channel component and the
module-functional-type is TYPE_DIGITAL_COHERENT_OPTIC this
grouping will NOT be used as the data will be within the
optical-channel
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The input optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value. When the physical channel has a leafref to
an optical channel component and the module-functional-type is
TYPE_DIGITAL_COHERENT_OPTIC this represents the aggregate
total optical power value (signal and noise) whereas
optical power value within the optical-channel represents
the signal power
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The current applied by the system to the transmit laser to
achieve the output power. The current is expressed in mA
with up to two decimal precision. Values include the
instantaneous, average, minimum, and maximum statistics.
If avg/min/max statistics are not supported, the target is
expected to just supply the instant value. In some cases,
such as when the physical channel has a leafref to an optical
channel component and the module-functional-type is
TYPE_DIGITAL_COHERENT_OPTIC this grouping will NOT be used
as the data will be within the optical-channel
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Enclosing container for client channels
nodetype: container (rw)
description:
List of client channels, keyed by index within a physical
client port. A physical port with a single channel would
have a single zero-indexed element
nodetype: list (rw)
list keys: [index]
description:
Reference to the index number of the channel
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for physical channels
nodetype: container (rw)
description:
Index of the physical channnel or lane within a physical
client port
nodetype: leaf (rw)
type: uint16
description:
A physical channel may reference an optical channel
component. If the physical channel does make this optional
reference, then a limited set of leaves will apply within
the physical channel to avoid duplication within the optical
channel.
nodetype: leaf (rw)
type: leafref
description:
Text description for the client physical channel
nodetype: leaf (rw)
type: string
description:
Enable (true) or disable (false) the transmit label for the
channel
nodetype: leaf (rw)
type: boolean
description:
Target output optical power level of the optical channel,
expressed in increments of 0.01 dBm (decibel-milliwats)
nodetype: leaf (rw)
type: decimal64
units: dBm
description:
Operational state data for channels
nodetype: container (ro)
description:
Index of the physical channnel or lane within a physical
client port
nodetype: leaf (ro)
type: uint16
description:
A physical channel may reference an optical channel
component. If the physical channel does make this optional
reference, then a limited set of leaves will apply within
the physical channel to avoid duplication within the optical
channel.
nodetype: leaf (ro)
type: leafref
description:
Text description for the client physical channel
nodetype: leaf (ro)
type: string
description:
Enable (true) or disable (false) the transmit label for the
channel
nodetype: leaf (ro)
type: boolean
description:
Target output optical power level of the optical channel,
expressed in increments of 0.01 dBm (decibel-milliwats)
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
Laser age (0% at beginning of life, 100% end of life) in integer
percentage. This term is defined by Common Management Interface
Specification (CMIS).
nodetype: leaf (ro)
type: oc-types:percentage
description:
Laser temperature for the cooled laser in degrees Celsius with 1
decimal precision. This term is defined by Common Management
Interface Specification (CMIS). Values include the instantaneous,
average, minimum, and maximum statistics. If avg/min/max statistics
are not supported, the target is expected to just supply the
instant value.
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The arithmetic mean value of the statistic over the
sampling period.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The minimum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The maximum value of the statistic over the sampling
period
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The difference in MHz with 1 decimal precision between the target
center frequency and the actual current center frequency . This term
is defined by Common Management Interface Specification (CMIS) and
referred to as laser frequency error or laser ferquency deviation.
Values include the instantaneous, average, minimum, and maximum
statistics. If avg/min/max statistics are not supported, the target
is expected to just supply the instant value.
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: MHz
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: MHz
description:
The minimum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: MHz
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: MHz
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The amount of current flowing to the TC of a cooled laser in percentage
with 2 decimal precision. This term is defined by Common Management
Interface Specification (CMIS). Values include the instantaneous,
average, minimum, and maximum statistics. If avg/min/max statistics
are not supported, the target is expected to just supply the instant
value.
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: percentage
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: percentage
description:
The minimum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: percentage
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: percentage
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Transmitter failure flag.
In earlier standards, including SFF-8436, SFF-8472, and QSFP-DD CMIS 4.0,
this flag was named Tx Fault.
nodetype: leaf (ro)
type: boolean
description:
Receiver loss-of-signal flag.
nodetype: leaf (ro)
type: boolean
description:
Receiver clock-and-data-recovery loss-of-lock flag.
nodetype: leaf (ro)
type: boolean
description:
The frequency in MHz of the individual physical channel
(e.g. ITU C50 - 195.0THz and would be reported as
195,000,000 MHz in this model). This attribute is not
configurable on most client ports In some cases, such as when
the physical channel has a leafref to an optical channel
component and the module-functional-type is
TYPE_DIGITAL_COHERENT_OPTIC this grouping will NOT be used
as the data will be within the optical-channel.
nodetype: leaf (ro)
type: oc-opt-types:frequency-type
description:
The output optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value. In some cases, such as when the physical
channel has a leafref to an optical channel component and the
module-functional-type is TYPE_DIGITAL_COHERENT_OPTIC this
grouping will NOT be used as the data will be within the
optical-channel
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The input optical power of a physical channel in units
of 0.01dBm, which may be associated with individual
physical channels, or an aggregate of multiple physical
channels (i.e., for the overall transceiver). For an
aggregate, this may be a measurement from a photodetector
or a a calculation performed on the device by summing up
all of the related individual physical channels.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value. When the physical channel has a leafref to
an optical channel component and the module-functional-type is
TYPE_DIGITAL_COHERENT_OPTIC this represents the aggregate
total optical power value (signal and noise) whereas
optical power value within the optical-channel represents
the signal power
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The maximum value of the statistic over the time interval.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The current applied by the system to the transmit laser to
achieve the output power. The current is expressed in mA
with up to two decimal precision. Values include the
instantaneous, average, minimum, and maximum statistics.
If avg/min/max statistics are not supported, the target is
expected to just supply the instant value. In some cases,
such as when the physical channel has a leafref to an optical
channel component and the module-functional-type is
TYPE_DIGITAL_COHERENT_OPTIC this grouping will NOT be used
as the data will be within the optical-channel
nodetype: container (ro)
description:
The instantaneous value of the statistic.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The arithmetic mean value of the statistic over the
time interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The minimum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The maximum value of the statistic over the time
interval.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
If supported by the system, this reports the time interval
over which the min/max/average statistics are computed by
the system.
nodetype: leaf (ro)
type: oc-types:stat-interval
description:
The absolute time at which the minimum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
The absolute time at which the maximum value occurred.
The value is the timestamp in nanoseconds relative to
the Unix Epoch (Jan 1, 1970 00:00:00 UTC).
nodetype: leaf (ro)
type: oc-types:timeticks64
description:
Enclosing container for host lanes.
nodetype: container (rw)
description:
List of electrical host lanes, keyed by lane number.
The host lanes of a transceiver constitute its electrical interface
with the host system.
nodetype: list (rw)
list keys: [lane-number]
description:
Reference to the host lane number.
nodetype: leaf (list key) (rw)
type: leafref
description:
Configuration data for host lanes.
nodetype: container (rw)
description:
Number identifying an electrical host lane carrying one serial
signal. Lanes are numbered starting with 1.
nodetype: leaf (rw)
type: uint8
description:
Operational state data for host lanes.
nodetype: container (ro)
description:
Number identifying an electrical host lane carrying one serial
signal. Lanes are numbered starting with 1.
nodetype: leaf (ro)
type: uint8
description:
Transmitter loss-of-signal flag.
nodetype: leaf (ro)
type: boolean
description:
Transmitter clock-and-data-recovery loss-of-lock flag.
nodetype: leaf (ro)
type: boolean
description:
Enclosing container for transceiver alarm thresholds.
nodetype: container (rw)
description:
List of transceiver alarm thresholds, indexed by
alarm severity.
nodetype: list (ro)
list keys: [severity]
description:
The severity applied to the group of thresholds.
An implementation's highest severity threshold
should be mapped to OpenConfig's `CRITICAL`
severity level.
nodetype: leaf (list key) (ro)
type: leafref
description:
Operational alarm thresholds for the transceiver.
nodetype: container (ro)
description:
The type of alarm to which the thresholds apply.
nodetype: leaf (ro)
type: identityref
description:
The upper temperature threshold for the laser temperature sensor.
This leaf value is compared to the instant value of
laser-temperature.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The lower temperature threshold for the laser temperature sensor.
This leaf value is compared to the instant value of
laser-temperature.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The upper power threshold for the laser output power. This threshold
applies to every physical-channel on the transceiver and does not
apply to the aggregate transceiver optical-output-power. This leaf
value is compared to the instant value of optical-output-power.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The lower power threshold for the laser output power. This threshold
applies to every physical-channel on the transceiver and does not
apply to the aggregate transceiver optical-output-power. This leaf
value is compared to the instant value of optical-output-power.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The upper power threshold for the laser input power. This threshold
applies to every physical-channel on the transceiver and does not
apply to the aggregate transceiver optical-input-power. This leaf
value is compared to the instant value of optical-input-power.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The lower power threshold for the laser input power. This threshold
applies to every physical-channel on the transceiver and does not
apply to the aggregate transceiver optical-input-power. This leaf
value is compared to the instant value of optical-input-power.
nodetype: leaf (ro)
type: decimal64
units: dBm
description:
The upper threshold for the laser bias current. This leaf value is
compared to the instant value of last-bias-current.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The lower threshold for the laser bias current. This leaf value is
compared to the instant value of last-bias-current.
nodetype: leaf (ro)
type: decimal64
units: mA
description:
The upper threshold for the transceiver supply voltage. This leaf
value is compared to the instant value of supply-voltage.
nodetype: leaf (ro)
type: decimal64
units: volts
description:
The lower threshold for the transceiver supply voltage. This leaf
value is compared to the instant value of supply-voltage.
nodetype: leaf (ro)
type: decimal64
units: volts
description:
The lower temperature threshold for the transceiver module. This
leaf value is compared to the instant value of module-temperature.
nodetype: leaf (ro)
type: decimal64
units: celsius
description:
The upper temperature threshold for the transceiver module. This
leaf value is compared to the instant value of module-temperature.
nodetype: leaf (ro)
type: decimal64
units: celsius