LEAN-MIB
AI MIB Summary
The LEAN-MIB module provides standard SNMP objects for monitoring and managing generic operational parameters of Lean network appliances. It enables the collection of device-specific metrics, including interface statistics, system health indicators, and configuration states, to facilitate centralized network management and fault isolation.
The preliminary MIB module to describe generic objects for the Lean.
Main OID:
tellabs.1.3.6.1.4.1.42
192
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
192 total| Object Name |
|---|
tellabsThe preliminary MIB module to describe generic objects for
the Lean. MODULE-IDENTITY .1.3.6.1.4.1.42 |
leanMIB OBJECT IDENTIFIER .1.3.6.1.4.1.42.1 |
frnetservMIB OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1 |
frnetservObjects OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1.1 |
frLportTableThe Frame Relay Logical Port Information table. SEQUENCE OF FrLportEntry .1.3.6.1.4.1.42.1.1.1.1 |
frLportEntryAn entry in the Frame Relay Logical Port
Information table. FrLportEntry .1.3.6.1.4.1.42.1.1.1.1.1 |
frLportNumPlanThe value of this object identifies the network
address numbering plan for this UNI/NNI logical
port. The network address is the object
ifPhysAddress. The value none implies that there
is no ifPhysAddress. The SNMP proxy-agent will
return an octet string of zero length for
ifPhysAddress. The value other means that an
address has been assigned to this interface, but
the numbering plan is not enumerated here.ro Enumeration .1.3.6.1.4.1.42.1.1.1.1.1.1 |
frLportContactThe value of this object identifies the network
contact for this UNI/NNI logical port.ro DisplayString .1.3.6.1.4.1.42.1.1.1.1.1.2 |
frLportLocationThe value of this object identifies the Frame
Relay network location for this UNI/NNI logical
port.ro DisplayString .1.3.6.1.4.1.42.1.1.1.1.1.3 |
frLportTypeThe value of this object identifies the type of
network interface for this logical port.ro Enumeration .1.3.6.1.4.1.42.1.1.1.1.1.4 |
frLportAddrDLCILenThe value of this object identifies the Q.922
Address field length and DLCI length for this
UNI/NNI logical port.ro Enumeration .1.3.6.1.4.1.42.1.1.1.1.1.5 |
frLportVCSigProtocolThe value of this object identifies the Local
In-Channel Signaling Protocol that is used for
this frame relay UNI/NNI logical port.ro Enumeration .1.3.6.1.4.1.42.1.1.1.1.1.6 |
frLportVCSigPointerThe value of this object is used as a pointer to
the table that contains the Local In-Channel
Signaling Protocol parameters and errors for this
UNI/NNI logical port. See the Frame Relay
Management VC Signaling Parameters and Errors
Group.ro OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1.1.1.1.7 |
frMgtVCSigTableThe Frame Relay Management VC Signaling
Parameters and Errors table. SEQUENCE OF FrMgtVCSigEntry .1.3.6.1.4.1.42.1.1.1.2 |
frMgtVCSigEntryAn entry in the Frame Relay Management VC
Signaling Parameters Errors table. FrMgtVCSigEntry .1.3.6.1.4.1.42.1.1.1.2.1 |
frMgtVCSigProcedThe value of this object identifies the Local
In-Channel Signaling Procedure that is used for
this UNI/NNI logical port. The UNI/NNI logical
port can be performing only user-to-network
network-side procedures or bidirectional
procedures.ro Enumeration .1.3.6.1.4.1.42.1.1.1.2.1.1 |
frMgtVCSigUserN391The value of this object identifies the User-side
N391 full status polling cycle value for this
UNI/NNI logical port. If the logical port is not
performing user-side procedures, then this value
is equal to noSuchName. This object applies to
Q.933 Annex A and T1.617 Annex D.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.2 |
frMgtVCSigUserN392The value of this object identifies the User-side
N392 error threshold value for this UNI/NNI
logical port. If the logical port is not
performing user-side procedures, then this value
is equal to noSuchName. This object applies to
Q.933 Annex A and T1.617 Annex D.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.3 |
frMgtVCSigUserN393The value of this object identifies the User-side
N393 monitored events count value for this UNI/NNI
logical port. If the logical port is not
performing user-side procedures, then this value
is equal to noSuchName. This object applies to
Q.933 Annex A and T1.617 Annex D.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.4 |
frMgtVCSigUserT391The value of this object identifies the User-side
T391 link integrity verification polling timer
value for this UNI/NNI logical port. If the
logical port is not performing user-side
procedures, then this value is equal to
noSuchName. This object applies to Q.933 Annex A
and T1.617 Annex D.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.5 |
frMgtVCSigNetN392The value of this object identifies the Network-
side N392 error threshold value (nN2 for LMI) for
this UNI/NNI logical port. If the logical port is
not performing network-side procedures, then this
value is equal to noSuchName. This object applies
to Q.933 Annex A, T1.617 Annex D and LMI.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.6 |
frMgtVCSigNetN393The value of this object identifies the Network-
side N393 monitored events count value (nN3 for
LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to
noSuchName. This object applies to Q.933 Annex A,
T1.617 Annex D and LMI.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.7 |
frMgtVCSigNetT392The value of this object identifies the Network-
side T392 polling verification timer value (nT2
for LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to
noSuchName. This object applies to Q.933 Annex A,
T1.617 Annex D and LMI.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.8 |
frMgtVCSigNetnN4The value of this object identifies the Network-
side nN4 maximum status enquires received value
for this UNI/NNI logical port. If the logical
port is not performing network-side procedures or
is not performing LMI procedures, then this value
is equal to noSuchName. This object applies only
to LMI and always has a value of 5.ro INTEGER .1.3.6.1.4.1.42.1.1.1.2.1.9 |
frMgtVCSigNetnT3The value of this object identifies the Network-
side nT3 timer (for nN4 status enquires received)
value for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures or is not performing LMI procedures,
then this value is equal to noSuchName. This
object applies only to LMI.ro INTEGER (5 | 10 | 15 | 20 | 25 | 30) .1.3.6.1.4.1.42.1.1.1.2.1.10 |
frMgtVCSigUserLinkRelErrorsThe number of user-side local in-channel
signaling link reliability errors (i.e., non-
receipt of Status/Status Enquiry messages or
invalid sequence numbers in a Link Integrity
Verification Information Element) for this UNI/NNI
logical port. If the logical port is not
performing user-side procedures, then this value
is equal to noSuchName.ro Counter32 .1.3.6.1.4.1.42.1.1.1.2.1.11 |
frMgtVCSigUserProtErrorsThe number of user-side local in-channel
signaling protocol errors (i.e., protocol
discriminator, message type, call reference, and
mandatory information element errors) for this
UNI/NNI logical port. If the logical port is not
performing user-side procedures, then this value
is equal to noSuchName.ro Counter32 .1.3.6.1.4.1.42.1.1.1.2.1.12 |
frMgtVCSigUserChanInactiveThe number of times the user-side channel was
declared inactive (i.e., N392 errors in N393
events) for this UNI/NNI logical port. If the
logical port is not performing user-side
procedures, then this value is equal to
noSuchName.ro Counter32 .1.3.6.1.4.1.42.1.1.1.2.1.13 |
frMgtVCSigNetLinkRelErrorsThe number of network-side local in-channel
signaling link reliability errors (i.e., non-
receipt of Status/Status Enquiry messages or
invalid sequence numbers in a Link Integrity
Verification Information Element) for this UNI/NNI
logical port. If the logical port is not
performing network-side procedures, then this
value is equal to noSuchName.ro Counter32 .1.3.6.1.4.1.42.1.1.1.2.1.14 |
frMgtVCSigNetProtErrorsThe number of network-side local in-channel
signaling protocol errors (i.e., protocol
discriminator, message type, call reference, and
mandatory information element errors) for this
UNI/NNI logical port. If the logical port is not
performing network-side procedures, then this
value is equal to noSuchName.ro Counter32 .1.3.6.1.4.1.42.1.1.1.2.1.15 |
frMgtVCSigNetChanInactiveThe number of times the network-side channel was
declared inactive (i.e., N392 errors in N393
events) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to
noSuchName.ro Counter32 .1.3.6.1.4.1.42.1.1.1.2.1.16 |
frPVCEndptTableThe Frame Relay PVC End-Point table. This table
is used to model a PVC end-point. This table
contains the traffic parameters and statistics for
a PVC end-point. SEQUENCE OF FrPVCEndptEntry .1.3.6.1.4.1.42.1.1.1.3 |
frPVCEndptEntryAn entry in the Frame Relay PVC Endpoint table. FrPVCEndptEntry .1.3.6.1.4.1.42.1.1.1.3.1 |
frPVCEndptDLCIIndexThe value of this object is equal to the DLCI
value for this PVC end-point. Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.1 |
frPVCEndptInMaxFrameSizeThe value of this object is the size in octets of
the largest frame relay information field for this
PVC end-point in the ingress direction (into the
frame relay network). The value of
frPVCEndptInMaxFrameSize must be less than or
equal to the corresponding ifMtu for this Frame
Relay UNI/NNI logical port.rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.2 |
frPVCEndptInBcThe value of this object is equal to the
committed burst size (Bc) parameter (measured in
bits) for this PVC end-point in the ingress
direction (into the frame relay network).rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.3 |
frPVCEndptInBeThe value of this object is equal to the excess
burst size (Be) parameter (measured in bits) for
this PVC end-point in the ingress direction (into
the frame relay network).rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.4 |
frPVCEndptInCIRThe value of this object is equal to the
committed information rate (CIR) parameter
(measured in bits per second) for this PVC end-
point in the ingress direction (into the frame
relay network).rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.5 |
frPVCEndptOutMaxFrameSizeThe value of this object is the size in octets of
the largest frame relay information field for this
PVC end-point in the egress direction (out of the
frame relay network). The value of
frPVCEndptOutMaxFrameSize must be less than or
equal to the corresponding ifMtu for this Frame
Relay UNI/NNI logical port.rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.6 |
frPVCEndptOutBcThe value of this object is equal to the
committed burst size (Bc) parameter (measured in
bits) for this PVC end-point in the egress
direction (out of the frame relay network).rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.7 |
frPVCEndptOutBeThe value of this object is equal to the excess
burst size (Be) parameter (measured in bits) for
this PVC end-point in the egress direction (out of
the frame relay network).rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.8 |
frPVCEndptOutCIRThe value of this object is equal to the
committed information rate (CIR) parameter
(measured in bits per second) for this PVC end-
point in the egress direction (out of the frame
relay network).rw Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.9 |
frPVCEndptConnectIdentifierThis object is used to associate PVC end-points
as being part of one PVC segment connection. This
value of this object is equal to the value of
frPVCConnectIndex, which is used as one of the
indices into the frPVCConnectTable. The value of
this object is provided by the agent, after the
associated entries in the frPVCConnectTable have
been created.ro Integer32 .1.3.6.1.4.1.42.1.1.1.3.1.10 |
frPVCEndptRowStatusThis object is used to create new rows in this
table, modify existing rows, and to delete
existing rows. To create a new PVC, the entries
for the PVC segment end-points in the
frPVCEndptTable must first be created. Next, the
frPVCConnectTable is used to associate the Frame
Relay PVC segment end-points. In order for the
manager to have the necessary error diagnostics,
the frPVCEndptRowStatus object must initially be
set to `createAndWait'. While the
frPVCEndptRowStatus object is in the
`createAndWait' state, the manager can set each
columnar object and get the necessary error
diagnostics. The frPVCEndptRowStatus object may
not be set to `active' unless the following
columnar objects exist in this row:
frPVCEndptInMaxFrameSize, frPVCEndptInBc,
frPVCEndptInBe, frPVCEndptInCIR,
frPVCEndptOutMaxFrameSize, frPVCEndptOutBc,
frPVCEndptOutBe, and frPVCEndptOutCIR.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.1.1.3.1.11 |
frPVCEndptRcvdSigStatusThe value of this object identifies the PVC
status received via the local in-channel signaling
procedures for this PVC end-point. This object is
only pertinent for interfaces that perform the
bidirectional procedures. For user-to-network
network side procedures, the value of this object
should be none.ro Enumeration .1.3.6.1.4.1.42.1.1.1.3.1.12 |
frPVCEndptInFramesThe number of frames received by the network
(ingress) for this PVC end-point. This includes
any frames discarded by the network due to
submitting more than Bc + Be data or due to any
network congestion recovery procedures.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.13 |
frPVCEndptOutFramesThe number of frames sent by the network (egress)
regardless of whether they are Bc or Be frames for
this PVC end-point.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.14 |
frPVCEndptInDEFramesThe number of frames received by the network
(ingress) with the DE bit set to (1) for this PVC
end-point.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.15 |
frPVCEndptInExcessFramesThe number of frames received by the network
(ingress) for this PVC end-point which were
treated as excess traffic. Frames which are sent
to the network with DE set to zero are treated as
excess when more than Bc bits are submitted to the
network during the Committed Information Rate
Measurement Interval (Tc). Excess traffic may or
may not be discarded at the ingress if more than
Bc + Be bits are submitted to the network during
Tc. Traffic discarded at the ingress is not
recorded in frPVCEndptInExcessFrames. Frames
which are sent to the network with DE set to one
are also treated as excess traffic.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.16 |
frPVCEndptOutExcessFramesThe number of frames sent by the network (egress)
for this PVC end-point which were treated as
excess traffic. (The DE bit may be set to one.)ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.17 |
frPVCEndptInDiscardsThe number of frames received by the the network
(ingress) that were discarded due to traffic
enforcement for this PVC end-point.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.18 |
frPVCEndptInOctetsThe number of octets received by the network
(ingress) for this PVC end-point. This counter
should only count octets from the beginning of the
frame relay header field to the end of user data.
If the network supporting Frame Relay can not
count octets, then this count should be an
approximation.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.19 |
frPVCEndptOutOctetsThe number of octets sent by the network (egress)
for this PVC end-point. This counter should only
count octets from the beginning of the frame relay
header field to the end of user data. If the
network supporting Frame Relay can not count
octets, then this count should be an
approximation.ro Counter32 .1.3.6.1.4.1.42.1.1.1.3.1.20 |
frPVCConnectIndexValueThis object contains an appropriate value to be
used for frPVCConnectIndex when creating entries
in the frPVCConnectTable. The value 0 indicates
that no unassigned entries are available. To
obtain the frPVCConnectIndex value for a new
entry, the manager issues a management protocol
retrieval operation to obtain the current value of
this object. After each retrieval, the agent
should modify the value to the next unassigned
index.ro INTEGER .1.3.6.1.4.1.42.1.1.1.4 |
frPVCConnectTableThe Frame Relay PVC Connect table. A bi-
directional PVC segment is modeled as one entry in
this table. SEQUENCE OF FrPVCConnectEntry .1.3.6.1.4.1.42.1.1.1.5 |
frPVCConnectEntryAn entry in the Frame Relay PVC Connect table.
This entry is used to model a PVC segment in two
directions. FrPVCConnectEntry .1.3.6.1.4.1.42.1.1.1.5.1 |
frPVCConnectIndexThe value of this object is equal to the
frPVCConnectIndexValue obtained to uniquely
identify this PVC segment connection. Integer32 .1.3.6.1.4.1.42.1.1.1.5.1.1 |
frPVCConnectLowIfIndexThe value of this object is equal to MIB II's
ifIndex value of the UNI/NNI logical port for this
PVC segment. The term low implies that this PVC
segment end-point has the numerically lower
ifIndex value than the connected/associated PVC
segment end-point. If the value is equal to zero,
then this logical port is not a Frame Relay
UNI/NNI logical port. IfIndex .1.3.6.1.4.1.42.1.1.1.5.1.2 |
frPVCConnectLowDLCIIndexThe value of this object is equal to the DLCI
value for this end-point of the PVC segment. If
the value is equal to zero, then this endpoint of
the PVC segment is not a Frame Relay connection. Integer32 .1.3.6.1.4.1.42.1.1.1.5.1.3 |
frPVCConnectHighIfIndexThe value of this object is equal to MIB II's
ifIndex value for the UNI/NNI logical port for
this PVC segment. The term high implies that this
PVC segment end-point has the numerically higher
ifIndex value than the connected/associated PVC
segment end-point. IfIndex .1.3.6.1.4.1.42.1.1.1.5.1.4 |
frPVCConnectHighDLCIIndexThe value of this object is equal to the egress
DLCI value for this end-point of the PVC segment. Integer32 .1.3.6.1.4.1.42.1.1.1.5.1.5 |
frPVCConnectAdminStatusThe value of this object identifies the desired
administrative status of this bi-directional PVC
segment. The active state means the PVC segment
is currently operational; the inactive state means
the PVC segment is currently not operational; the
testing state means the PVC segment is currently
undergoing a test. This state is set by an
administrative entity. This value affects the PVC
status indicated across the ingress NNI/UNI of
both end-points of the bi-directional PVC segment.
When a PVC segment connection is created using
this table, this object is initially set to
`inactive'. After the frPVCConnectRowStatus
object is set to `active' (and the
corresponding/associated entries in the
frPVCEndptTable have their frPVCEndptRowStatus
object set to `active'), the
frPVCConnectAdminStatus object may be set to
`active' to turn on the PVC segment connection.rw Enumeration .1.3.6.1.4.1.42.1.1.1.5.1.6 |
frPVCConnectL2hOperStatusThe value of this object identifies the current
operational status of the PVC segment connection
in one direction; (i.e., in the low to high
direction). The active state means it is
currently operational; the inactive state means it
is currently not operational; the testing state
means it is currently undergoing a test; the
unknown state means the status of it currently can
not be determined. This value affects the PVC
status indicated across the ingress NNI/UNI (low
side) of the PVC segment.ro Enumeration .1.3.6.1.4.1.42.1.1.1.5.1.7 |
frPVCConnectH2lOperStatusThe value of this object identifies the current
operational status of the PVC segment connection
in one direction; (i.e., in the high to low
direction). The active state means it is
currently operational; the inactive state means it
is currently not operational; the testing state
means it is currently undergoing a test; the
unknown state means the status of it currently can
not be determined. This value affects the PVC
status indicated across the ingress NNI/UNI (high
side) of the PVC segment.ro Enumeration .1.3.6.1.4.1.42.1.1.1.5.1.8 |
frPVCConnectL2hLastChangeThe value of MIB II's sysUpTime object at the
time this PVC segment entered its current
operational state in the low to high direction.
If the current state was entered prior to the last
re-initialization of the proxy-agent, then this
object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.1.1.5.1.9 |
frPVCConnectH2lLastChangeThe value of MIB II's sysUpTime object at the
time this PVC segment entered its current
operational state in the high to low direction.
If the current state was entered prior to the last
re-initialization of the proxy-agent, then this
object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.1.1.5.1.10 |
frPVCConnectRowStatusThe status of this entry in the
frPVCConnectTable. This variable is used to
create new connections for the PVC end-points and
to change existing connections of the PVC end-
points. This object must be initially set to
`createAndWait'. In this state, the agent checks
the parameters in the associated entries in the
frPVCEndptTable to verify that the PVC end-points
can be connected (i.e., the In parameters for one
PVC end-point are equal to the Out parameters for
the other PVC end-point). This object can not be
set to `active' unless the following columnar
object exist in this row: frPVCConnectAdminStatus.
The agent also supplies the associated value of
frPVCConnectIndex for the frPVCEndptConnectIdentifier
instances. To turn on a PVC segment connection, the
frPVCConnectAdminStatus is set to `active'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.1.1.5.1.11 |
frAccountPVCTableThe Frame Relay Accounting PVC table. This table
is used to perform accounting on a PVC segment
end-point basis. SEQUENCE OF FrAccountPVCEntry .1.3.6.1.4.1.42.1.1.1.6 |
frAccountPVCEntryAn entry in the Frame Relay Accounting PVC
table. FrAccountPVCEntry .1.3.6.1.4.1.42.1.1.1.6.1 |
frAccountPVCDLCIIndexThe value of this object is equal to the DLCI
value for this PVC segment end-point. Integer32 .1.3.6.1.4.1.42.1.1.1.6.1.1 |
frAccountPVCSegmentSizeThe value of this object is equal to the Segment
Size for this PVC segment end-point.ro Integer32 .1.3.6.1.4.1.42.1.1.1.6.1.2 |
frAccountPVCInSegmentsThe value of this object is equal to the number
of segments received by this PVC segment end-
point.ro Counter32 .1.3.6.1.4.1.42.1.1.1.6.1.3 |
frAccountPVCOutSegmentsThe value of this object is equal to the number
of segments sent by this PVC segment end-point.ro Counter32 .1.3.6.1.4.1.42.1.1.1.6.1.4 |
frAccountLportTableThe Frame Relay Accounting Logical Port table.
This table is used to perform accounting on a
UNI/NNI Logical Port basis. SEQUENCE OF FrAccountLportEntry .1.3.6.1.4.1.42.1.1.1.7 |
frAccountLportEntryAn entry in the Frame Relay Accounting Logical
Port table. FrAccountLportEntry .1.3.6.1.4.1.42.1.1.1.7.1 |
frAccountLportSegmentSizeThe value of this object is equal to the Segment
Size for this UNI/NNI logical port.ro Integer32 .1.3.6.1.4.1.42.1.1.1.7.1.1 |
frAccountLportInSegmentsThe value of this object is equal to the number
of segments received by this UNI/NNI logical
port.ro Counter32 .1.3.6.1.4.1.42.1.1.1.7.1.2 |
frAccountLportOutSegmentsThe value of this object is equal to the number
of segments sent by this UNI/NNI logical port.ro Counter32 .1.3.6.1.4.1.42.1.1.1.7.1.3 |
frnetservTraps OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1.2 |
frPVCConnectStatusChangeThis trap indicates that the indicated PVC has
changed state. This trap is not sent if an FR-UNI
changes state; a linkDown or linkUp trap should be
sent instead. NOTIFICATION-TYPE .1.3.6.1.4.1.42.1.1.2.1 |
frnetservConformance OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1.3 |
frnetservGroups OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1.3.1 |
frnetservCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.1.3.2 |
atmMIB OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2 |
atmMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1 |
atmTrafficDescriptorTypes OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1 |
atmNoTrafficDescriptorThis identifies the no ATM traffic descriptor
type. Parameters 1, 2, 3, 4, and 5 are not used.
This traffic descriptor type can be used for
best effort traffic. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.1 |
atmNoClpNoScrThis traffic descriptor is for no CLP and
no Sustained Cell Rate. The use of the
parameter vector for this type:
Parameter 1: CLP=0+1 peak cell rate in
cells per second
Parameter 2: not used
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used.
This traffic descriptor type can be used
for best effort traffic. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.2 |
atmClpNoTaggingNoScrThis traffic descriptor is for no CLP without
tagging and no Sustained Cell Rate. The use
of the parameter vector for this type:
Parameter 1: CLP=0+1 peak cell rate in
cells per second
Parameter 2: CLP=0 peak cell rate in
cells per second
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.3 |
atmClpTaggingNoScrThis traffic descriptor is for CLP with
tagging and no Sustained Cell Rate. The
use of the parameter vector for this type:
Parameter 1: CLP=0+1 peak cell rate in
cells per second
Parameter 2: CLP=0 peak cell rate in
cells per second with excess
traffic tagged as CLP=1
Parameter 3: not used
Parameter 4: not used
Parameter 5: not used. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.4 |
atmNoClpScrThis traffic descriptor is for no CLP
with Sustained Cell Rate. The
use of the parameter vector for this type:
Parameter 1: CLP=0+1 peak cell rate in
cells per second
Parameter 2: CLP=0+1 sustained cell rate in
cells per second
Parameter 3: CLP=0+1 maximum burst size
in cells
Parameter 4: not used
Parameter 5: not used. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.5 |
atmClpNoTaggingScrThis traffic descriptor is for CLP
with Sustained Cell Rate and no tagging.
The use of the parameter vector for this type:
Parameter 1: CLP=0+1 peak cell rate in
cells per second
Parameter 2: CLP=0 sustained cell rate in
cells per second
Parameter 3: CLP=0 maximum burst size in cells
Parameter 4: not used
Parameter 5: not used. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.6 |
atmClpTaggingScrThis traffic descriptor is for CLP
with tagging and Sustained Cell Rate.
The use of the parameter vector for this type:
Parameter 1: CLP=0+1 peak cell rate in
cells per second
Parameter 2: CLP=0 sustained cell rate in
cells per second with excess
traffic tagged as CLP=1
Parameter 3: CLP=0 maximum burst size in cells
Parameter 4: not used
Parameter 5: not used. OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.1.7 |
atmInterfaceConfTableThis table contains ATM local interface
configuration parameters, one entry per ATM
interface port. SEQUENCE OF AtmInterfaceConfEntry .1.3.6.1.4.1.42.1.2.1.2 |
atmInterfaceConfEntryThis list contains ATM interface configuration
parameters and state variables. AtmInterfaceConfEntry .1.3.6.1.4.1.42.1.2.1.2.1 |
atmInterfaceMaxVpcsThe maximum number of VPCs (PVCs and SVCs)
supported at this ATM interface. At the ATM UNI,
the maximum number of VPCs (PVCs and SVCs)
ranges from 0 to 256 only.rw INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.1 |
atmInterfaceMaxVccsThe maximum number of VCCs (PVCs and SVCs)
supported at this ATM interface.rw INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.2 |
atmInterfaceConfVpcsThe number of VPCs (PVCs and SVCs)
configured for use at this ATM interface.
At the ATM UNI, the configured number of
VPCs (PVCs and SVCs) can range from
0 to 256 only.ro INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.3 |
atmInterfaceConfVccsThe number of VCCs (PVCs and SVCs)
configured for use at the ATM interface.ro INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.4 |
atmInterfaceMaxActiveVpiBitsThe maximum number of active VPI bits
configured for use at the ATM interface.
At the ATM UNI, the maximum number of active
VPI bits configured for use ranges from
0 to 8 only.rw INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.5 |
atmInterfaceMaxActiveVciBitsThe maximum number of active VCI bits
configured for use at this ATM interface.rw INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.6 |
atmInterfaceIlmiVpiThe VPI value of the VCC supporting
the ILMI at this ATM interface. If the values of
atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
both equal to zero then the ILMI is not
supported at this ATM interface.rw INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.7 |
atmInterfaceIlmiVciThe VCI value of the VCC supporting
the ILMI at this ATM interface. If the values of
atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
both equal to zero then the ILMI is not
supported at this ATM interface.rw INTEGER .1.3.6.1.4.1.42.1.2.1.2.1.8 |
atmInterfaceAddressTypeThe type of primary ATM address configured
for use at this ATM interface.ro Enumeration .1.3.6.1.4.1.42.1.2.1.2.1.9 |
atmInterfaceAdminAddressAn address assigned for administrative purposes,
for example, an address associated with the
service provider side of a public network UNI.
If this interface has no assigned administrative
address, or when the address used for
administrative purposes is the same as that used
for ifPhysAddress, then this is an octet string of
zero length.ro OCTET STRING .1.3.6.1.4.1.42.1.2.1.2.1.10 |
atmInterfaceMyNeighborIpAddressThe IP address of the neighbor system connected to
the far end of this interface, to which a Network
Management Station can send SNMP messages, as IP
datagrams sent to UDP port 161, in order to access
network management information concerning the
operation of that system. Note that the value
of this object may be obtained in different ways,
e.g., by manual configuration, or through ILMI
interaction with the neighbor system.rw IpAddress .1.3.6.1.4.1.42.1.2.1.2.1.11 |
atmInterfaceMyNeighborIfNameThe textual name of the interface on the neighbor
system on the far end of this interface, and to
which this interface connects. If the neighbor
system is manageable through SNMP and supports
the object ifName, the value of this object must
be identical with that of ifName for the ifEntry
of the lowest level physical interface
for this port. If this interface does not have a
textual name, the value of this object is a zero
length string. Note that the value of this object
may be obtained in different ways, e.g., by manual
configuration, or through ILMI interaction with
the neighbor system.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.2.1.12 |
atmInterfaceDs3PlcpTableThis table contains ATM interface DS3 PLCP
parameters and state variables, one entry per
ATM interface port. SEQUENCE OF AtmInterfaceDs3PlcpEntry .1.3.6.1.4.1.42.1.2.1.3 |
atmInterfaceDs3PlcpEntryThis list contains DS3 PLCP parameters and
state variables at the ATM interface. AtmInterfaceDs3PlcpEntry .1.3.6.1.4.1.42.1.2.1.3.1 |
atmInterfaceDs3PlcpSEFSsThe number of DS3 PLCP Severely Errored Framing
Second (SEFS). Each SEFS represents a
one-second interval which contains
one or more SEF event.ro Counter32 .1.3.6.1.4.1.42.1.2.1.3.1.1 |
atmInterfaceDs3PlcpAlarmStateThis variable indicates if there is an
alarm present for the DS3 PLCP. The value
receivedFarEndAlarm means that the DS3 PLCP
has received an incoming Yellow
Signal, the value incomingLOF means that
the DS3 PLCP has declared a loss of frame (LOF)
failure condition, and the value noAlarm
means that there are no alarms present.
Transition from the failure to the no alarm state
occurs when no defects (e.g., LOF) are received
for more than 10 seconds.ro Enumeration .1.3.6.1.4.1.42.1.2.1.3.1.2 |
atmInterfaceDs3PlcpUASsThe counter associated with the number of
Unavailable Seconds encountered by the PLCP.ro Counter32 .1.3.6.1.4.1.42.1.2.1.3.1.3 |
atmInterfaceTCTableThis table contains ATM interface TC
Sublayer parameters and state variables,
one entry per ATM interface port. SEQUENCE OF AtmInterfaceTCEntry .1.3.6.1.4.1.42.1.2.1.4 |
atmInterfaceTCEntryThis list contains TC Sublayer parameters
and state variables at the ATM interface. AtmInterfaceTCEntry .1.3.6.1.4.1.42.1.2.1.4.1 |
atmInterfaceOCDEventsThe number of times the Out of Cell
Delineation (OCD) events occur. If seven
consecutive ATM cells have Header Error
Control (HEC) violations, an OCD event occurs.
A high number of OCD events may indicate a
problem with the TC Sublayer.ro Counter32 .1.3.6.1.4.1.42.1.2.1.4.1.1 |
atmInterfaceTCAlarmStateThis variable indicates if there is an
alarm present for the TC Sublayer. The value
lcdFailure indicates that a Loss of
Cell Delineation (LCD) failure state has been
declared for the TC Sublayer. Transition from
failure to the no alarm state occurs
when 6 consecutive ATM cells
are received with valid HEC, followed by
about 10 seconds of acceptable working signal.ro Enumeration .1.3.6.1.4.1.42.1.2.1.4.1.2 |
atmTrafficDescrParamTableThis table contains information on ATM traffic
descriptor type and the associated parameters. SEQUENCE OF AtmTrafficDescrParamEntry .1.3.6.1.4.1.42.1.2.1.5 |
atmTrafficDescrParamEntryThis list contains ATM traffic descriptor
type and the associated parameters. AtmTrafficDescrParamEntry .1.3.6.1.4.1.42.1.2.1.5.1 |
atmTrafficDescrParamIndexThis object is used by the virtual link
table (i.e., VPL or VCL table)
to identify the row of this table. AtmTrafficDescrParamIndex .1.3.6.1.4.1.42.1.2.1.5.1.1 |
atmTrafficDescrTypeThe value of this object identifies the type
of ATM traffic descriptor.
The type may indicate no traffic descriptor or
traffic descriptor with one or more parameters.
These parameters are specified as a parameter
vector, in the corresponding instances of the
objects:
atmTrafficDescrParam1
atmTrafficDescrParam2
atmTrafficDescrParam3
atmTrafficDescrParam4
atmTrafficDescrParam5.rw OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.1.5.1.2 |
atmTrafficDescrParam1The first parameter of the ATM traffic descriptor
used according to the value of
atmTrafficDescrType.rw Integer32 .1.3.6.1.4.1.42.1.2.1.5.1.3 |
atmTrafficDescrParam2The second parameter of the ATM traffic descriptor
used according to the value of
atmTrafficDescrType.rw Integer32 .1.3.6.1.4.1.42.1.2.1.5.1.4 |
atmTrafficDescrParam3The third parameter of the ATM traffic descriptor
used according to the value of
atmTrafficDescrType.rw Integer32 .1.3.6.1.4.1.42.1.2.1.5.1.5 |
atmTrafficDescrParam4The fourth parameter of the ATM traffic descriptor
used according to the value of
atmTrafficDescrType.rw Integer32 .1.3.6.1.4.1.42.1.2.1.5.1.6 |
atmTrafficDescrParam5The fifth parameter of the ATM traffic descriptor
used according to the value of
atmTrafficDescrType.rw Integer32 .1.3.6.1.4.1.42.1.2.1.5.1.7 |
atmTrafficQoSClassThe value of this object identifies the QoS Class.
Four Service classes have been
specified in the ATM Forum UNI Specification:
Service Class A: Constant bit rate video and
Circuit emulation
Service Class B: Variable bit rate video/audio
Service Class C: Connection-oriented data
Service Class D: Connectionless data
Four QoS classes numbered 1, 2, 3, and 4 have
been specified with the aim to support service
classes A, B, C, and D respectively.
An unspecified QoS Class numbered `0' is used
for best effort traffic.rw INTEGER .1.3.6.1.4.1.42.1.2.1.5.1.8 |
atmTrafficDescrRowStatusThis object is used to create
a new row or modify or delete an
existing row in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.5.1.9 |
atmVplTableThe Virtual Path Link (VPL) table. A
bi-directional VPL is modeled as one entry
in this table. SEQUENCE OF AtmVplEntry .1.3.6.1.4.1.42.1.2.1.6 |
atmVplEntryAn entry in the VPL table. This entry is
used to model a bi-directional VPL.
To create a VPL at an ATM interface,
either of the following procedures are used:
Negotiated VPL establishment
(1) The management application creates
a VPL entry in the atmVplTable
by setting atmVplRowStatus to createAndWait(5).
This may fail for the following reasons:
- The selected VPI value is unavailable,
- The selected VPI value is in use.
Otherwise, the agent creates a row and
reserves the VPI value on that port.
(2) The manager selects an existing row(s) in the
atmTrafficDescrParamTable,
thereby, selecting a set of self-consistent
ATM traffic parameters and the QoS Class
for receive and transmit directions of the VPL.
(2a) If no suitable row(s) in the
atmTrafficDescrParamTable exists,
the manager must create a new row(s)
in that table.
(2b) The manager characterizes the VPL's traffic
parameters through setting the
atmVplReceiveTrafficDescrIndex and the
atmVplTransmitTrafficDescrIndex values
in the VPL table, which point to the rows
containing desired ATM traffic parameter values
in the atmTrafficDescrParamTable. The agent
will check the availability of resources and
may refuse the request.
(3) The manager activates the VPL by setting the
the atmVplRowStatus to active(1).
If this set is successful, the agent has
reserved the resources to satisfy the requested
traffic parameter values and the QoS Class
for that VPL.
(4) If the VPL terminates a VPC in the ATM host
or switch, the manager turns on the
atmVplAdminStatus to up(1) to turn the VPL
traffic flow on. Otherwise, the
atmVpCrossConnectTable must be used
to cross-connect the VPL to another VPL(s)
in an ATM switch or network.
One-Shot VPL Establishment
A VPL may also be established in one step by a
set-request with all necessary VPL parameter
values and atmVplRowStatus set to createAndGo(4).
In contrast to the negotiated VPL establishment
which allows for detailed error checking
(i.e., set errors are explicitly linked to
particular resource acquisition failures),
the one-shot VPL establishment
performs the setup on one operation but
does not have the advantage of step-wise
error checking.
VPL Retirement
A VPL is released by setting atmVplRowStatus to
destroy(6), and the agent may release all
associated resources. AtmVplEntry .1.3.6.1.4.1.42.1.2.1.6.1 |
atmVplVpiThe VPI value of the VPL.
Note that the VPI=0 is not used
for a VPL not associated with a VCL.
The maximum VPI value cannot
exceed the value allowable by the
atmInterfaceMaxVpiBits. INTEGER .1.3.6.1.4.1.42.1.2.1.6.1.1 |
atmVplAdminStatusThis object is implemented only for a VPL which
terminates a VPC (i.e.,
one which is NOT cross-connected to other VPLs).
Its value specifies the desired administrative
state of the VPL. The up and down states indicate
that the traffic flow is enabled and disabled
respectively for this VPL.rw Enumeration .1.3.6.1.4.1.42.1.2.1.6.1.2 |
atmVplOperStatusThis object indicates the current operational
status of the VPL. The up and down states
indicate that the VPL is currently
operational, or not operational, respectively.
The unknown state indicates that the status of
this VPL cannot be determined.ro Enumeration .1.3.6.1.4.1.42.1.2.1.6.1.3 |
atmVplLastChangeThe value of MIB II's sysUpTime object
at the time this VPL entered its current
operational state. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.6.1.4 |
atmVplReceiveTrafficDescrIndexThe value of this object identifies the row
in the atmTrafficDescrParamTable which
applies to the receive direction of the VPL.rw AtmTrafficDescrParamIndex .1.3.6.1.4.1.42.1.2.1.6.1.5 |
atmVplTransmitTrafficDescrIndexThe value of this object identifies the row
in the atmTrafficDescrParamTable which
applies to the transmit direction of the VPL.rw AtmTrafficDescrParamIndex .1.3.6.1.4.1.42.1.2.1.6.1.6 |
atmVplCrossConnectIdentifierThis object is implemented only for a VPL
which is cross-connected to other VPLs
that belong to the same VPC. All such
associated VPLs have the same value of this
object, and all their cross-connections are
identified by entries in the
atmVpCrossConnectTable for which
atmVpCrossConnectIndex has the same value.
The value of this object is initialized by the
agent after the associated entries in the
atmVpCrossConnectTable have been created.ro INTEGER .1.3.6.1.4.1.42.1.2.1.6.1.7 |
atmVplRowStatusThis object is used to create, delete
or modify a row in this table.
To create a new VCL, this object is
initially set to 'createAndWait' or
'createAndGo'. This object must not be
set to 'active' unless the following columnar
objects exist in this row:
atmVplReceiveTrafficDescrIndex and
atmVplTransmitTrafficDescrIndex.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.6.1.8 |
atmVclTableThe Virtual Channel Link (VCL) table. A
bi-directional VCL is modeled as one entry
in this table. SEQUENCE OF AtmVclEntry .1.3.6.1.4.1.42.1.2.1.7 |
atmVclEntryAn entry in the VCL table. This entry is
used to model a bi-directional VCL.
To create a VCL at an ATM interface,
either of the following procedures are used:
Negotiated VCL establishment
(1) The management application creates
a VCL entry in the atmVclTable
by setting atmVclRowStatus to createAndWait(5).
This may fail for the following reasons:
- The selected VPI/VCI values are unavailable,
- The selected VPI/VCI values are in use.
Otherwise, the agent creates a row and
reserves the VPI/VCI values on that port.
(2) The manager selects an existing row(s) in the
atmTrafficDescrParamTable,
thereby, selecting a set of self-consistent
ATM traffic parameters and the QoS Class
for receive and transmit directions of the VCL.
(2a) If no suitable row(s) in the
atmTrafficDescrParamTable exists,
the manager must create a new row(s)
in that table.
(2b) The manager characterizes the VCL's traffic
parameters through setting the
atmVclReceiveTrafficDescrIndex and the
atmVclTransmitTrafficDescrIndex values
in the VCL table, which point to the rows
containing desired ATM traffic parameter values
in the atmTrafficDescrParamTable. The agent
will check the availability of resources and
may refuse the request.
(3) The manager activates the VCL by setting the
the atmVclRowStatus to active(1).
If this set is successful, the agent has
reserved the resources to satisfy the requested
traffic parameter values and the QoS Class
for that VCL.
(4) If the VCL terminates a VCC in the ATM host
or switch, the manager turns on the
atmVclAdminStatus to up(1) to turn the VCL
traffic flow on. Otherwise, the
atmVcCrossConnectTable must be used
to cross-connect the VCL to another VCL(s)
in an ATM switch or network.
One-Shot VCL Establishment
A VCL may also be established in one step by a
set-request with all necessary VCL parameter
values and atmVclRowStatus set to createAndGo(4).
In contrast to the negotiated VCL establishment
which allows for detailed error checking
(i.e., set errors are explicitly linked to
particular resource acquisition failures),
the one-shot VCL establishment
performs the setup on one operation but
does not have the advantage of step-wise
error checking.
VCL Retirement
A VCL is released by setting atmVclRowStatus to
destroy(6), and the agent may release all
associated resources. AtmVclEntry .1.3.6.1.4.1.42.1.2.1.7.1 |
atmVclVpiThe VPI value of the VCL.
The maximum VPI value cannot
exceed the value allowable by the
atmInterfaceMaxVpiBits. INTEGER .1.3.6.1.4.1.42.1.2.1.7.1.1 |
atmVclVciThe VCI value of the VCL.
The maximum VCI value cannot
exceed the value allowable by the
atmInterfaceMaxVciBits. INTEGER .1.3.6.1.4.1.42.1.2.1.7.1.2 |
atmVclAdminStatusThis object is implemented only for a VCL which
terminates a VCC (i.e.,
one which is NOT cross-connected to other VCLs).
Its value specifies the desired administrative
state of the VCL. The up and down states indicate
that the traffic flow is enabled and disabled
respectively for this VCL.rw Enumeration .1.3.6.1.4.1.42.1.2.1.7.1.3 |
atmVclOperStatusThis object indicates the current operational
status of the VCL. The up and down states
indicate that the VCL is currently
operational, or not operational, respectively.
The unknown state indicates that the status of
this VCL cannot be determined.ro Enumeration .1.3.6.1.4.1.42.1.2.1.7.1.4 |
atmVclLastChangeThe value of MIB II's sysUpTime object
at the time this VCL entered its current
operational state. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.7.1.5 |
atmVclReceiveTrafficDescrIndexThe value of this object identifies the row
in the ATM Traffic Descriptor Table which
applies to the receive direction of this VCL.rw AtmTrafficDescrParamIndex .1.3.6.1.4.1.42.1.2.1.7.1.6 |
atmVclTransmitTrafficDescrIndexThe value of this object identifies the row
of the ATM Traffic Descriptor Table which applies
to the transmit direction of this VCL.rw AtmTrafficDescrParamIndex .1.3.6.1.4.1.42.1.2.1.7.1.7 |
atmVccAalTypeAn instance of this object only exists when the
local VCL end-point is also the VCC end-point,
and AAL is in use.
The type of AAL used on this VCC.
The AAL type includes AAL1, AAL3/4,
and AAL5. The other(4) may be user-defined
AAL type. The unknown type indicates that
the AAL type cannot be determined.rw Enumeration .1.3.6.1.4.1.42.1.2.1.7.1.8 |
atmVccAal5CpcsTransmitSduSizeAn instance of this object only exists when the
local VCL end-point is also the VCC end-point,
and AAL5 is in use.
The maximum AAL5 CPCS SDU size in octets that is
supported on the transmit direction of this VCC.rw INTEGER .1.3.6.1.4.1.42.1.2.1.7.1.9 |
atmVccAal5CpcsReceiveSduSizeAn instance of this object only exists when the
local VCL end-point is also the VCC end-point,
and AAL5 is in use.
The maximum AAL5 CPCS SDU size in octets that is
supported on the receive direction of this VCC.rw INTEGER .1.3.6.1.4.1.42.1.2.1.7.1.10 |
atmVccAal5EncapsTypeAn instance of this object only exists when the
local VCL end-point is also the VCC end-point,
and AAL5 is in use.
The type of data encapsulation used over
the AAL5 SSCS layer. The definitions reference
RFC 1483 Multiprotocol Encapsulation
over ATM AAL5 and to the ATM Forum
LAN Emulation specification.rw Enumeration .1.3.6.1.4.1.42.1.2.1.7.1.11 |
atmVclCrossConnectIdentifierThis object is implemented only for a VCL
which is cross-connected to other VCLs
that belong to the same VCC. All such
associated VCLs have the same value of this
object, and all their cross-connections are
identified by entries in the
atmVcCrossConnectTable for which
atmVcCrossConnectIndex has the same value.
The value of this object is initialized by the
agent after the associated entries in the
atmVcCrossConnectTable have been created.ro INTEGER .1.3.6.1.4.1.42.1.2.1.7.1.12 |
atmVclRowStatusThis object is used to create, delete or
modify a row in this table. To create
a new VCL, this object is initially set
to 'createAndWait' or 'createAndGo'.
This object must not be set to 'active'
unless the following columnar objects exist
in this row:
atmVclReceiveTrafficDescrIndex,
atmVclTransmitTrafficDescrIndex.
In addition, if the local VCL end-point
is also the VCC end-point:
atmVccAalType.
In addition, for AAL5 connections only:
atmVccAal5CpcsTransmitSduSize,
atmVccAal5CpcsReceiveSduSize, and
atmVccAal5EncapsType.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.7.1.13 |
atmVpCrossConnectIndexNextThis object contains an appropriate value to
be used for atmVpCrossConnectIndex when creating
entries in the atmVpCrossConnectTable. The value
0 indicates that no unassigned entries are
available. To obtain the atmVpCrossConnectIndex
value for a new entry, the manager issues a
management protocol retrieval operation to obtain
the current value of this object. After each
retrieval, the agent should modify the value to
the next unassigned index.ro INTEGER .1.3.6.1.4.1.42.1.2.1.8 |
atmVpCrossConnectTableThe ATM VP Cross Connect table. A bi-
directional VP cross-connect which
cross-connects two VPLs is modeled
as one entry in this table. SEQUENCE OF AtmVpCrossConnectEntry .1.3.6.1.4.1.42.1.2.1.9 |
atmVpCrossConnectEntryAn entry in the ATM VP Cross Connect table.
This entry is used to model a bi-directional
ATM VP cross-connect which cross-connects
two VPLs.
Step-wise Procedures to set up a VP Cross-connect
Once the entries in the atmVplTable are created,
the following procedures are used
to cross-connect the VPLs together.
(1) The manager obtains a unique
atmVpCrossConnectIndex by reading the
atmVpCrossConnectIndexNext object.
(2) Next, the manager creates a set of one
or more rows in the ATM VP Cross Connect
Table, one for each cross-connection between
two VPLs. Each row is indexed by the ATM
interface port numbers and VPI values of the
two ends of that cross-connection.
This set of rows specifies the topology of the
VPC cross-connect and is identified by a single
value of atmVpCrossConnectIndex.
Negotiated VP Cross-Connect Establishment
(2a) The manager creates a row in this table by
setting atmVpCrossConnectRowStatus to
createAndWait(5). The agent checks the
requested topology and the mutual sanity of
the ATM traffic parameters and
QoS Classes, i.e., the row creation fails if:
- the requested topology is not supported
by the agent, - the traffic/QoS parameter values
associated with the requested row are
incompatible with those of already existing
rows for this VP cross-connect.
[For example, for setting up
a point-to-point VP cross-connect, the
ATM traffic parameters in the receive direction
of a VPL at the low end of the cross-connect
must equal to the traffic parameters in the
transmit direction of the other VPL at the
high end of the cross-connect,
otherwise, the row creation fails.]
The agent also checks for internal errors
in building the cross-connect.
The atmVpCrossConnectIndex values in the
corresponding atmVplTable rows are filled
in by the agent at this point.
(2b) The manager promotes the row in the
atmVpCrossConnectTable by setting
atmVpCrossConnectRowStatus to active(1). If
this set is successful, the agent has reserved
the resources specified by the ATM traffic
parameter and QoS Class values
for each direction of the VP cross-connect
in an ATM switch or network.
(3) The manager sets the
atmVpCrossConnectAdminStatus to up(1) in all
rows of this VP cross-connect to turn the
traffic flow on.
One-Shot VP Cross-Connect Establishment
A VP cross-connect may also be established in
one step by a set-request with all necessary
parameter values and atmVpCrossConnectRowStatus
set to createAndGo(4).
In contrast to the negotiated VP cross-connect
establishment which allows for detailed error
checking (i.e., set errors are explicitly linked
to particular resource acquisition failures),
the one-shot VP cross-connect establishment
performs the setup on one operation but does not
have the advantage of step-wise error checking.
VP Cross-Connect Retirement
A VP cross-connect identified by a particular
value of atmVpCrossConnectIndex is released by:
(1) Setting atmVpCrossConnectRowStatus of all
rows identified by this value of
atmVpCrossConnectIndex to destroy(6).
The agent may release all
associated resources, and the
atmVpCrossConnectIndex values in the
corresponding atmVplTable row are removed.
Note that a situation when only a subset of
the associated rows are deleted corresponds
to a VP topology change.
(2) After deletion of the appropriate
atmVpCrossConnectEntries, the manager may
set atmVplRowStatus to destroy(6) the
associated VPLs. The agent releases
the resources and removes the associated
rows in the atmVplTable.
VP Cross-connect Reconfiguration
At the discretion of the agent, a VP
cross-connect may be reconfigured by
adding and/or deleting leafs to/from
the VP topology as per the VP cross-connect
establishment/retirement procedures.
Reconfiguration of traffic/QoS parameter
values requires release of the VP cross-connect
before those parameter values may by changed
for individual VPLs. AtmVpCrossConnectEntry .1.3.6.1.4.1.42.1.2.1.9.1 |
atmVpCrossConnectIndexA unique value to identify this VP cross-connect. INTEGER .1.3.6.1.4.1.42.1.2.1.9.1.1 |
atmVpCrossConnectLowIfIndexThe value of this object is equal to MIB II's
ifIndex value of the ATM interface port for this
VP cross-connect. The term low implies
that this ATM interface has the numerically lower
ifIndex value than the other ATM interface
identified in the same atmVpCrossConnectEntry. IfIndex .1.3.6.1.4.1.42.1.2.1.9.1.2 |
atmVpCrossConnectLowVpiThe value of this object is equal to the VPI
value at the ATM interface
associated with the VP cross-connect that is
identified by atmVpCrossConnectLowIfIndex.
The VPI value cannot exceed the number
supported by the atmInterfaceMaxVpiBits
at the low ATM interface port. INTEGER .1.3.6.1.4.1.42.1.2.1.9.1.3 |
atmVpCrossConnectHighIfIndexThe value of this object is equal to MIB II's
ifIndex value of the ATM interface port for
this VP cross-connect. The term high
implies that this ATM interface has the
numerically higher ifIndex value than the
other ATM interface identified in the same
atmVpCrossConnectEntry. IfIndex .1.3.6.1.4.1.42.1.2.1.9.1.4 |
atmVpCrossConnectHighVpiThe value of this object is equal to the VPI
value at the ATM interface associated with
the VP cross-connect that is identified
by atmVpCrossConnectHighIfIndex.
The VPI value cannot exceed the number
supported by the atmInterfaceMaxVpiBits
at the high ATM interface port. INTEGER .1.3.6.1.4.1.42.1.2.1.9.1.5 |
atmVpCrossConnectAdminStatusThe value of this object identifies the desired
administrative status of this bi-directional
VP cross-connect. The up and down states
indicate that the traffic flow is enabled
and disabled respectively on this VP
cross-connect.rw Enumeration .1.3.6.1.4.1.42.1.2.1.9.1.6 |
atmVpCrossConnectL2HOperStatusThe value of this object identifies the current
operational status of the VP cross-connect
in one direction; (i.e., from the low to
high direction). The up and down states indicate
that this ATM VP cross-connect from low
to high direction is operational or not
operational respectively.
The unknown state indicates that
the state of it cannot be determined.ro Enumeration .1.3.6.1.4.1.42.1.2.1.9.1.7 |
atmVpCrossConnectH2LOperStatusThe value of this object identifies the current
operational status of the VP cross-connect
in one direction; (i.e., from the high to
low direction). The up and down states indicate
that this ATM VP cross-connect from high
to low direction is operational or not
operational respectively. The
unknown state indicates that the state
of it cannot be determined.ro Enumeration .1.3.6.1.4.1.42.1.2.1.9.1.8 |
atmVpCrossConnectL2HLastChangeThe value of MIB II's sysUpTime object
at the time this VP cross-connect entered
its current operational state in the low to
high direction. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.9.1.9 |
atmVpCrossConnectH2LLastChangeThe value of MIB II's sysUpTime object at the
time this VP cross-connect entered its current
operational state in the high to low direction.
If the current state was entered prior to the
last re-initialization of the agent,
then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.9.1.10 |
atmVpCrossConnectRowStatusThe status of this entry in the
atmVpCrossConnectTable. This object is used to
create a cross-connect for cross-connecting
VPLs which are created using the atmVplTable
or to change or delete an existing cross-connect.
This object must be initially set
to `createAndWait' or 'createAndGo'.
This object cannot be set to `active'
unless the following columnar object exists
in this row: atmVpCrossConnectAdminStatus.
To turn on a VP cross-connect,
the atmVpCrossConnectAdminStatus
is set to `up'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.9.1.11 |
atmVcCrossConnectIndexNextThis object contains an appropriate value to
be used for atmVcCrossConnectIndex when creating
entries in the atmVcCrossConnectTable. The value
0 indicates that no unassigned entries are
available. To obtain the atmVpCrossConnectIndex
value for a new entry, the manager issues a
management protocol retrieval operation to obtain
the current value of this object. After each
retrieval, the agent should modify the value to
the next unassigned index.ro INTEGER .1.3.6.1.4.1.42.1.2.1.10 |
atmVcCrossConnectTableThe ATM VC Cross Connect table. A bi-
directional VC cross-connect which
cross-connects two end points (i.e., VCLs)
is modeled as one entry in this table. SEQUENCE OF AtmVcCrossConnectEntry .1.3.6.1.4.1.42.1.2.1.11 |
atmVcCrossConnectEntryAn entry in the ATM VC Cross Connect table.
This entry is used to model a bi-directional ATM
VC cross-connect cross-connecting two end points.
Step-wise Procedures to set up a VC Cross-connect
Once the entries in the atmVclTable are created,
the following procedures are used
to cross-connect the VCLs together to
form a VCC segment.
(1) The manager obtains a unique
atmVcCrossConnectIndex by reading the
atmVcCrossConnectIndexNext object.
(2) Next, the manager creates a set of one
or more rows in the ATM VC Cross Connect
Table, one for each cross-connection between
two VCLs. Each row is indexed by the ATM
interface port numbers and VPI/VCI values of
the two ends of that cross-connection.
This set of rows specifies the topology of the
VCC cross-connect and is identified by a single
value of atmVcCrossConnectIndex.
Negotiated VC Cross-Connect Establishment
(2a) The manager creates a row in this table by
setting atmVcCrossConnectRowStatus to
createAndWait(5). The agent checks the
requested topology and the mutual sanity of
the ATM traffic parameters and
QoS Classes, i.e., the row creation fails if:
- the requested topology is not supported
by the agent,
- the traffic/QoS parameter values
associated with the requested row are
incompatible with those of already existing
rows for this VC cross-connect.
[For example, for setting up
a point-to-point VC cross-connect, the
ATM traffic parameters in the receive direction
of a VCL at the low end of the cross-connect
must equal to the traffic parameters in the
transmit direction of the other VCL at the
high end of the cross-connect,
otherwise, the row creation fails.]
The agent also checks for internal errors
in building the cross-connect.
The atmVcCrossConnectIndex values in the
corresponding atmVclTable rows are filled
in by the agent at this point.
(2b) The manager promotes the row in the
atmVcCrossConnectTable by setting
atmVcCrossConnectRowStatus to active(1). If
this set is successful, the agent has reserved
the resources specified by the ATM traffic
parameter and QoS Class values
for each direction of the VC cross-connect
in an ATM switch or network.
(3) The manager sets the
atmVcCrossConnectAdminStatus to up(1)
in all rows of this VC cross-connect to
turn the traffic flow on.
One-Shot VC Cross-Connect Establishment
A VC cross-connect may also be established in
one step by a set-request with all necessary
parameter values and atmVcCrossConnectRowStatus
set to createAndGo(4).
In contrast to the negotiated VC cross-connect
establishment which allows for detailed error
checking i.e., set errors are explicitly linked to
particular resource acquisition failures), the
one-shot VC cross-connect establishment
performs the setup on one operation but does
not have the advantage of step-wise error
checking.
VC Cross-Connect Retirement
A VC cross-connect identified by a particular
value of atmVcCrossConnectIndex is released by:
(1) Setting atmVcCrossConnectRowStatus of all rows
identified by this value of
atmVcCrossConnectIndex to destroy(6).
The agent may release all
associated resources, and the
atmVcCrossConnectIndex values in the
corresponding atmVclTable row are removed.
Note that a situation when only a subset of
the associated rows are deleted corresponds
to a VC topology change.
(2) After deletion of the appropriate
atmVcCrossConnectEntries, the manager may
set atmVclRowStatus to destroy(6) the
associated VCLs. The agent releases
the resources and removes the associated
rows in the atmVclTable.
VC Cross-Connect Reconfiguration
At the discretion of the agent, a VC
cross-connect may be reconfigured by
adding and/or deleting leafs to/from
the VC topology as per the VC cross-connect
establishment/retirement procedures.
Reconfiguration of traffic/QoS parameter
values requires release of the VC cross-connect
before those parameter values may by changed
for individual VCLs. AtmVcCrossConnectEntry .1.3.6.1.4.1.42.1.2.1.11.1 |
atmVcCrossConnectIndexA unique value to identify this VC cross-connect. INTEGER .1.3.6.1.4.1.42.1.2.1.11.1.1 |
atmVcCrossConnectLowIfIndexThe value of this object is equal to MIB II's
ifIndex value of the ATM interface port for this
VC cross-connect. The term low implies
that this ATM interface has the numerically lower
ifIndex value than the other ATM interface
identified in the same atmVcCrossConnectEntry. IfIndex .1.3.6.1.4.1.42.1.2.1.11.1.2 |
atmVcCrossConnectLowVpiThe value of this object is equal to the VPI
value at the ATM interface
associated with the VC cross-connect that is
identified by atmVcCrossConnectLowIfIndex.
The VPI value cannot exceed the number
supported by the atmInterfaceMaxVpiBits
at the low ATM interface port. INTEGER .1.3.6.1.4.1.42.1.2.1.11.1.3 |
atmVcCrossConnectLowVciThe value of this object is equal to the VCI
value at the ATM interface
associated with this VC cross-connect that is
identified by atmVcCrossConnectLowIfIndex.
The VCI value cannot exceed the number
supported by the atmInterfaceMaxVciBits
at the low ATM interface port. INTEGER .1.3.6.1.4.1.42.1.2.1.11.1.4 |
atmVcCrossConnectHighIfIndexThe value of this object is equal to MIB II's
ifIndex value for the ATM interface port for
this VC cross-connect. The term high
implies that this VC cross-connect
that this ATM interface has the numerically higher
ifIndex value than the other ATM interface
identified in the same atmVcCrossConnectEntry. IfIndex .1.3.6.1.4.1.42.1.2.1.11.1.5 |
atmVcCrossConnectHighVpiThe value of this object is equal to the VPI
value at the ATM interface
associated with the VC cross-connect that is
identified by atmVcCrossConnectHighIfIndex.
The VPI value cannot exceed
the number supported by the atmInterfaceMaxVpiBits
at the high ATM interface port. INTEGER .1.3.6.1.4.1.42.1.2.1.11.1.6 |
atmVcCrossConnectHighVciThe value of this object is equal to the VCI
value at the ATM interface
associated with the VC cross-connect that is
identified by atmVcCrossConnectHighIfIndex.
The VCI value cannot exceed
the number supported by the atmInterfaceMaxVciBits
at the high ATM interface port. INTEGER .1.3.6.1.4.1.42.1.2.1.11.1.7 |
atmVcCrossConnectAdminStatusThe value of this object identifies the desired
administrative status of this bi-directional
VC cross-connect. The up and down states
indicate that the traffic flow is enabled or
disabled respectively on this VC cross-connect.rw Enumeration .1.3.6.1.4.1.42.1.2.1.11.1.8 |
atmVcCrossConnectL2HOperStatusThe value of this object identifies the current
operational status of the VC cross-connect
in one direction; (i.e., from the low to
high direction). The up and down states indicate
that this ATM VC cross-connect from low
to high direction is operational or not
operational respectively. The unknown state
indicates that the state of it cannot be
determined.ro Enumeration .1.3.6.1.4.1.42.1.2.1.11.1.9 |
atmVcCrossConnectH2LOperStatusThe value of this object identifies the current
operational status of the VC cross-connect
in one direction; (i.e., from the high to
low direction). The up and down states indicate
that this ATM VC cross-connect from high
to low direction is operational or not
operational respectively. The unknown state
indicates that the state of it cannot be
determined.ro Enumeration .1.3.6.1.4.1.42.1.2.1.11.1.10 |
atmVcCrossConnectL2HLastChangeThe value of MIB II's sysUpTime object
at the time this VC cross-connect entered
its current operational state in low to high
direction. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.11.1.11 |
atmVcCrossConnectH2LLastChangeThe value of MIB II's sysUpTime object
at the time this VC cross-connect entered
its current operational state in high to low
direction. If the current state was
entered prior to the last re-initialization of the
agent, then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.11.1.12 |
atmVcCrossConnectRowStatusThe status of this entry in the
atmVcCrossConnectTable. This object is used to
create a new cross-connect for cross-connecting
VCLs which are created using the atmVclTable
or to change or delete existing cross-connect.
This object must be initially set to
`createAndWait' or 'createAndGo'. This object
cannot be set to `active' unless the following
columnar object exists in this row:
atmVcCrossConnectAdminStatus.
To turn on a VC cross-connect,
the atmVcCrossConnectAdminStatus
is set to `up'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.42.1.2.1.11.1.13 |
aal5VccTableThis table contains AAL5 VCC performance
parameters. SEQUENCE OF Aal5VccEntry .1.3.6.1.4.1.42.1.2.1.12 |
aal5VccEntryThis list contains the AAL5 VCC
performance parameters. Aal5VccEntry .1.3.6.1.4.1.42.1.2.1.12.1 |
aal5VccVpiThe VPI value of the AAL5 VCC at the
interface identified by the ifIndex. INTEGER .1.3.6.1.4.1.42.1.2.1.12.1.1 |
aal5VccVciThe VCI value of the AAL5 VCC at the
interface identified by the ifIndex. INTEGER .1.3.6.1.4.1.42.1.2.1.12.1.2 |
aal5VccCrcErrorsThe number of AAL5 CPCS PDUs received with
CRC-32 errors on this AAL5 VCC at the
interface associated with an AAL5 entity.ro Counter32 .1.3.6.1.4.1.42.1.2.1.12.1.3 |
aal5VccSarTimeOutsThe number of partially re-assembled AAL5
CPCS PDUs which were discarded
on this AAL5 VCC at the interface associated
with an AAL5 entity because they
were not fully re-assembled within the
required time period. If the re-assembly
timer is not supported, then this object
contains a zero value.ro Counter32 .1.3.6.1.4.1.42.1.2.1.12.1.4 |
aal5VccOverSizedSDUsThe number of AAL5 CPCS PDUs discarded
on this AAL5 VCC at the interface
associated with an AAL5 entity because the
AAL5 SDUs were too large.ro Counter32 .1.3.6.1.4.1.42.1.2.1.12.1.5 |
atmMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.2 |
atmMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.2.1 |
atmMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.42.1.2.2.2 |