Clarify backplane facing capacity - consumed capacity #990
Conversation
total and total-operational-capacity: The word "link" can be confused with an interface or port, when it actually means a "fabric link" consumed-capacity: Causes confusion. It Is not the capacity that is consumed by the front-panel ports being "operationally up" but by the amount of traffic on the interface (in bits per second)
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Major YANG version changes in commit e27e52a: |
| oc-ext:telemetry-on-change; | ||
| } | ||
|
|
||
| leaf consumed-capacity { | ||
| type uint64; | ||
| units "bits per second"; | ||
| description | ||
| "Backplane-facing capacity that is consumed by front-panel ports that are connected | ||
| to the integrated circuit and are operationally up."; | ||
| "Backplane-facing capacity that is consumed by the traffic on front-panel ports |
There was a problem hiding this comment.
It's not strictly the traffic only those ports, right? If I have 400G front-panel port this consumes 400G, not whatever the traffic load on that port is at this exact moment in time.
There was a problem hiding this comment.
Rohit and I discussed an issue brought up by implementors of this model. The purpose of this PR is to explore and clarify what the intent of this leaf is. The modern, modular form factor packet based devices that I am familiar with only consume fabric capacity based on packets or cells sent over the fabric. Bringing a front panel port up or down does not change the capacity that is in consumed between the INTEGRATED_CIRCUIT (IC) and the FABRIC.
@rohit-rp I added a Juniper reference to the PR description. Can you look for better references for Arista and Cisco? I could not find information regarding 'consumed capacity' of IC to FABRIC in the references provided.
There was a problem hiding this comment.
In Nokia SRLinux we provide this utilization data per direction (ingress/egress): https://documentation.nokia.com/srlinux/23-10/books/data-model-reference/srl_nokia-platform_0.html#d6179
|
After further review of the operational use cases for this leaf, it seems the desire is to get the 'subscription ratio' on a So rather than using the word 'consumed', we should update this to use 'ratio of a LINECARD front panel interface bandwidth capacity to the bandwidth capacity of the connection between the LINECARD and FABRIC'. |
dplore
changed the title
|
@rohit-rp please address comments and we can move this one forward |
Change Scope
Clarifying /components/component/integrated-circuit/backplane-facing-capacity/state/consumed-capacity to refer to the capacity consumed by traffic on the front panel ports
Clarifying /components/component/integrated-circuit/backplane-facing-capacity/state/total
and /components/component/integrated-circuit/backplane-facing-capacity/state/total-operational-capacity to refer to the connection between
INTEGRATED_CIRCUITandFABRICcomponent identities.The word
linkcan be confused with aninterfaceorport, when it actually means afabric linkorSerDes linkPlatform Implementations
Arista: Document
Cisco: Document Page 40
JunOS - show interface statistics fabric