Status in source: current.
Names: zxGponPriorityQueueTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxGponPriorityQueueTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"ZxGponPriorityQueueEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This managed entity specifies the priority queue in the ONT that is used for the VP Network CTP-G or GEM Port Network CTP. If N priority queues reside in the ONT, the Subscriber Line Card, ONT core or PON IF Line Card, N instances of Priority Queue-G management entity will be automatically created by the ONT following the creation of the Subscriber Line Card or T-CONT ME. In ANI side, the Priority Queue-G ME is related to T-CONT ME. After instances of T-CONT ME are created, instances of Priority Queue-G ME should be created autonomously. Note that the OLT will find all the queues by reading the Priority Queue-G managed entity instances. If the OLT tries to retrieve a non-existing priority queue, this will be indicated in the response from the ONT to the OLT. See also Appendix IV/G.983.2. Upstream priority queues can be added to the ONT. Moreover, priority queues can exist in the ONT core and subscriber line cards as well as PON IF Line Cards. In order to configure the optional Traffic Scheduler, the Weight attribute is included. Several attributes are included that support back pressure operation. Back pressure is defined as a mechanism for backward flow control. The back pressure signal is sent backward and causes the customer terminal to temporarily suspend sending data.\"",
"REFERENCE",
"\"G.984.4 Section 9.5.1\"",
"::=",
"{",
"zxGponTrafficMgmt",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"ZxGponPriorityQueueEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This managed entity specifies the priority queue in the ONT that is used for the VP Network CTP-G or GEM Port Network CTP. If N priority queues reside in the ONT, the Subscriber Line Card, ONT core or PON IF Line Card, N instances of Priority Queue-G management entity will be automatically created by the ONT following the creation of the Subscriber Line Card or T-CONT ME. In ANI side, the Priority Queue-G ME is related to T-CONT ME. After instances of T-CONT ME are created, instances of Priority Queue-G ME should be created autonomously. Note that the OLT will find all the queues by reading the Priority Queue-G managed entity instances. If the OLT tries to retrieve a non-existing priority queue, this will be indicated in the response from the ONT to the OLT. See also Appendix IV/G.983.2. Upstream priority queues can be added to the ONT. Moreover, priority queues can exist in the ONT core and subscriber line cards as well as PON IF Line Cards. In order to configure the optional Traffic Scheduler, the Weight attribute is included. Several attributes are included that support back pressure operation. Back pressure is defined as a mechanism for backward flow control. The back pressure signal is sent backward and causes the customer terminal to temporarily suspend sending data."
],
[
"REFERENCE",
"G.984.4 Section 9.5.1"
],
null,
null,
null
]
}
- ZTE MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
ZTE support.
Module: ZXGPON-SERVICE-MIB
See published definition above
Module imports
{'SNMPv2-TC': ['RowStatus', 'TruthValue', 'DateAndTime', 'MacAddress', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['Unsigned32', 'Counter64', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE'], 'RFC1155-SMI': ['enterprises'], 'RFC1213-MIB': ['ifIndex']}
Related source files and packages: