Provide fine grain, per-Integrated Circuit (IC), telemetry data streams that will identify the health, any packet drops, and any...
Version: 2023-10-08
module openconfig-platform-pipeline-counters { yang-version 1; namespace "http://openconfig.net/yang/platform-pipeline-counters"; prefix oc-ppc; import openconfig-yang-types { prefix oc-yang; } import openconfig-types { prefix oc-types; } import openconfig-extensions { prefix oc-ext; } import openconfig-platform { prefix oc-platform; } organization "OpenConfig working group"; contact "OpenConfig working group www.openconfig.net"; description "Provide fine grain, per-Integrated Circuit (IC), telemetry data streams that will identify the health, any packet drops, and any errors on the IC. With this additional telemetry, the health of the IC, packet drops and errors, can be explicitly monitored not only on a specific router, but also on a specific IC on a specific router. The IC is divided into 5 platform independent sub-blocks. 1. IC Interface Subsystem 2. Queueing Subsystem 3. Lookup Subsystem 4. Host Interface 5. Fabric Interface. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | | | +---------------------------------------------------------------+ | | | Integrated +---------------------------------------+ | | | | Circuit | Host Interface | | | | | +---------------------------------------+ | | | | +------------+ | | | | +-----------+ | Lookup | +-------------+ | | | | | IC | | Subsystem | | Fabric | | | | | | Interface | | | | Interface | | | | | | Subsystem | +------------+ | | | | | | +-----------+ +-------------+ +-------------+ | | | | | Queueing | | | | | | Subsystem | | | | | +-------------+ | | | | | | | +---------------------------------------------------------------+ | | | +-------------------------------------------------------------------+ Each IC implementation inside forwarding engines may have a different set of counters. Some counters have different names but the same functionality and can be grouped together. Most counters are different between IC families and will have to be aggregated as generic counters. The aggregation could mean either a specific IC counter needs to be mapped to one of the values specified in this model, or it may require multiple IC counters aggregated to produce one of the values in this model. The following classes of counters will generalize the types of statistics that are provided from each of the above 5 blocks. A. Packet Counters B. Drop Counters C. Error Counters The advantage of grouping all the packet counters for all 5 blocks, all drop counters from all 5 blocks, and all error counters from all 5 blocks, is to have the abililty to receive all drop counters from all 5 blocks, for example, with one request."; revision "2023-10-08" { description "More detail description of pipe-line aggregated drop counters"; reference "0.5.1"; } revision "2023-09-26" { description "Add no-route aggregate drop counter."; reference "0.5.0"; } revision "2023-02-03" { description "Add vendor-specific control-plane traffic queue counters"; reference "0.4.0"; } revision "2022-12-01" { description "Add uRPF aggregate drop counter."; reference "0.3.1"; } revision "2022-11-09" { description "Add container for vendor specific drop counters."; reference "0.3.0"; } revision "2022-01-19" { description "Fixed typo for aggregate field."; reference "0.2.1"; } revision "2021-10-16" { description "Update pipeline error counters to allow for multiple errors per block."; reference "0.2.0"; } revision "2020-07-31" { description "Initial revision of platform pipeline counters."; reference "0.1.0"; } oc-ext:openconfig-version "0.5.1"; oc-ext:catalog-organization "openconfig"; oc-ext:origin "openconfig"; } // module openconfig-platform-pipeline-counters
© 2023 YumaWorks, Inc. All rights reserved.