ASCEND-MIBATMQOS-MIB: View SNMP OID List / Download MIB

VENDOR: ASCEND COMMUNICATIONS INC.


 Home MIB: ASCEND-MIBATMQOS-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 mibatmQosProfile 1.3.6.1.4.1.529.23.21
       mibatmQosProfileTable 1.3.6.1.4.1.529.23.21.1 no-access
A list of mibatmQosProfile profile entries.
           mibatmQosProfileEntry 1.3.6.1.4.1.529.23.21.1.1 no-access
A mibatmQosProfile entry containing objects that maps to the parameters of mibatmQosProfile profile.
               atmQosProfile_ContractName 1.3.6.1.4.1.529.23.21.1.1.1 displaystring read-only
The name of the Quality of Service (QoS) contract.
               atmQosProfile_TrafficDescriptorIndex 1.3.6.1.4.1.529.23.21.1.1.2 integer read-only
Traffic descriptor index.
               atmQosProfile_TrafficDescriptorType 1.3.6.1.4.1.529.23.21.1.1.3 integer read-write
The Traffic Descriptor type. Enumeration: 'clpNotaggingScr': 7, 'unknownTrafficDescr': 17, 'clpTransparentScr': 11, 'noclpNoscr': 3, 'clpTaggingScr': 8, 'noclpNoscrCdvt': 13, 'noclpScrCdvt': 14, 'clpNotaggingScrCdvt': 15, 'noclpTaggingNoscr': 12, 'clpTaggingScrCdvt': 16, 'noclpScr': 6, 'clpTransparentNoscr': 10.
               atmQosProfile_AtmServiceCategory 1.3.6.1.4.1.529.23.21.1.1.4 integer read-write
The ATM Service Category Type. In 7.11.x releases this field was called qos-class. Enumeration: 'cbr': 1, 'realTimeVbr': 2, 'nonRealTimeVbr': 3, 'ubr': 4.
               atmQosProfile_PeakRateKbitsPerSec 1.3.6.1.4.1.529.23.21.1.1.6 integer read-write
The Peak Cell Rate (PCR) expressed in Kbits per second ( Peak Bandwidth in KBits/sec )
               atmQosProfile_PeakCellRateCellsPerSec 1.3.6.1.4.1.529.23.21.1.1.7 integer read-write
The Peak Cell Rate (PCR) expressed in cells per second
               atmQosProfile_SustainableRateKbitsPerSec 1.3.6.1.4.1.529.23.21.1.1.9 integer read-write
The sustainable cell rate (SCR) expressed in Kbits per second ( Sustainable Bandwidth in Kbits/sec )
               atmQosProfile_SustainableCellRateCellsPerSec 1.3.6.1.4.1.529.23.21.1.1.10 integer read-write
The sustainable cell rate (SCR) expressed in cells per second
               atmQosProfile_IgnoreCellDelayVariationTolerance 1.3.6.1.4.1.529.23.21.1.1.11 integer read-write
Ignore cell-delay-variation-tolerance parameter. When it is set to yes, cell-delay-variation-tolerance parameter is ignored, and an internal parameter is used to tolerate bursty CPE that does not have traffic shaping capability. Enumeration: 'yes': 2, 'no': 1.
               atmQosProfile_CellDelayVariationTolerance 1.3.6.1.4.1.529.23.21.1.1.12 integer read-write
Cell delay variation tolerance is expressed in microseconds. It is ignored when ignore-cell-delay-variation-tolerance is yes.
               atmQosProfile_IgnoreMaxBurstSize 1.3.6.1.4.1.529.23.21.1.1.13 integer read-write
Ignore max-burst-size parameter. When it is set to yes, max-burst-size parameter is ignored, and an internal parameter is used to tolerate bursty CPE that does not have traffic shaping capability. Enumeration: 'yes': 2, 'no': 1.
               atmQosProfile_MaxBurstSize 1.3.6.1.4.1.529.23.21.1.1.14 integer read-write
Maximum burst size determines the maximum number of cells that can be transmitted at the peak cell rate before they become candidates for discard or marking. It is ignored when ignore-max-burst-size is yes.
               atmQosProfile_AalType 1.3.6.1.4.1.529.23.21.1.1.16 integer read-write
ATM Adaptation Layer type Enumeration: 'aal0': 1, 'unspecified': 3, 'aal5': 2.
               atmQosProfile_EarlyPacketDiscard 1.3.6.1.4.1.529.23.21.1.1.17 integer read-write
Applies to egress AAL5 packets. If the first cell in a packet can not be queued then that cell and all the remaining cells in that packet are not queued. Enumeration: 'yes': 2, 'no': 1.
               atmQosProfile_PartialPacketDiscard 1.3.6.1.4.1.529.23.21.1.1.18 integer read-write
Applies to ingress AAL5 packets. If non-conforming cell is discarded then the remaining cells in the packet (except the last cell) are also discarded. Enumeration: 'yes': 2, 'no': 1.
               atmQosProfile_TagOrDiscard 1.3.6.1.4.1.529.23.21.1.1.19 integer read-write
The non-conforming CLP=0 SCR cell should be tagged or discarded Enumeration: 'discard': 2, 'tag': 1.
               atmQosProfile_Action_o 1.3.6.1.4.1.529.23.21.1.1.20 integer read-write
Enumeration: 'deleteProfile': 3, 'createProfile': 2, 'noAction': 1.
               atmQosProfile_SubChannel 1.3.6.1.4.1.529.23.21.1.1.21 integer read-write
For DSL technologies that support multiple sub-channels on one line, when the multiple sub-channels are indeed used at same time, this parameter indicates which sub-channel will be used for this QOS profile. When only one sub-channel is used this parameter has no effect... EXAMPLE: in DMT - when the latency is set to BOTH, sub-channel #1 is the FAST channel ( typically useful for voice traffic - voice over ATM or Packet ) while sub-channel #2 is the INTERLEAVE channel ( typically useful for data traffic ).