>> MIB - Management Information Base
>> Table: atmOamTable - (.1.3.6.1.4.1.272.4.16.13.1)
Description: This tables contains all OAM configuration parameters.
atmOamTable
OID | Name | Type | Access
.1 | AtmIfIndex | Integer32 | RW
.2 | Vpi | INTEGER | RW
.3 | Vci | INTEGER | RW
.4 | FlowLevel | ENUM | D
.5 | LoopbackEnd2End | ENUM | RW
.6 | LoopbackSegment | ENUM | RW
.7 | LoopbackEnd2EndInterval | INTEGER | RW
.8 | LoopbackSegmentInterval | INTEGER | RW
.9 | LoopbackEnd2EndMaxPending | INTEGER | RW
.10 | LoopbackSegmentMaxPending | INTEGER | RW
.11 | CCEnd2EndActivation | ENUM | RW
.12 | CCSegmentActivation | ENUM | RW
.13 | CCEnd2EndDirection | ENUM | RW
.14 | CCSegmentDirection | ENUM | RW
AtmIfIndex
The interface index of the associated ATM hardware.
Vpi
The VPI value of this Virtual Path/Channel Connection. Range: 0 to 255
Vci
The VCI value of this Virtual Channel Connection. Range: 0 to 65535
FlowLevel
The OAM hierarchical flow levels : VC (F5) or VP (F4). Enumerations: f5 (1) f4 (2) delete (10)
LoopbackEnd2End
Indicates wether OAM loopback is enabled onto the end-to-end connection. Enumerations: disabled (1) enabled (2)
LoopbackSegment
Indicates wether active OAM loopback is enabled onto the segment connection. Enumerations: disabled (1) enabled (2)
LoopbackEnd2EndInterval
OAM loopback transmit interval (in seconds) for end-to-end context. Range: 0 to 999
LoopbackSegmentInterval
OAM loopback transmit interval (in seconds) for segment context. Range: 0 to 999
LoopbackEnd2EndMaxPending
Specifies the maximum number of outstanding OAM loopback responses after which the associated F4/F5 instance will be set into the end-to-end operational down status. Range: 0 to 999
LoopbackSegmentMaxPending
Specifies the maximum number of outstanding OAM loopback responses after which the associated F4/F5 instance will be set into the segment operational down status. Range: 0 to 999
CCEnd2EndActivation
Determines wether OAM continuity check activation request will be activated and/or accepted for the associated end-to-end connection. If set to passive(1) or both(3) CC activation requests will be confirmed. If set to active(2) or both CC will be requested. If set to no-negotiation(4) - depending on the settings in atmOamCCEnd2EndDirection - CC cells will be send and/or expected periodically without any previous CC activation negotiation. If set to none(5) neither CC activation will be requested/confirmed nor any CC cells will be generated/expected. Enumerations: passive (1) active (2) both (3) no-negotiation (4) none (5)
CCSegmentActivation
Determines wether OAM continuity check activation request will be activated and/or accepted for the associated segment connection. If set to passive(1) or both(3) CC activation requests will be confirmed. If set to active(2) or both CC will be requested. If set to no-negotiation(4) - depending on the settings in atmOamCCSegmentDirection - CC cells will be send and/or expected periodically without any previous CC activation negotiation. If set to none(5) neither CC activation will be requested/confirmed nor any CC cells will be generated/expected. Enumerations: passive (1) active (2) both (3) no-negotiation (4) none (5)
CCEnd2EndDirection
Determines OAM continuity check direction (for end-to-end). If set to sink(1) CC cells will be received only, if set to source(2) CC cells will be generated periodically, if set to both(3) CC cells will be received from the source as well as send to the sink. Enumerations: sink (1) source (2) both (3) none (4)
CCSegmentDirection
Determines OAM continuity check direction (for segment). If set to sink(1) CC cells will be received only, if set to source(2) CC cells will be generated periodically, if set to both(3) CC cells will be received from the source as well as send to the sink. Enumerations: sink (1) source (2) both (3) none (4)

MIB Reference to Software Version 10.2.12 generated on 2023/08/29. Provided by webmaster@bintec-elmeg.com Copyright ©2023 by bintec elmeg GmbH