Reference record for OID 1.3.6.1.2.1.86.1.2.1

Parent
1.3.6.1.2.1.86.1.2 (frAtmIwfConnectionTable)
Node code
1
Node name
frAtmIwfConnectionEntry
Numeric OID
1.3.6.1.2.1.86.1.2.1
URN notation
urn:oid:1.3.6.1.2.1.86.1.2.1
Type
OBJECT-TYPE
ASN.1 notation

{1 3 6 1 2 1 86 1 2 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) frAtmIwfMIB(86) frAtmIwfMIBObjects(1) frAtmIwfConnectionTable(2) frAtmIwfConnectionEntry(1)}
OID-IRI notation
  • /1/3/6/1/2/1/86/1/2/1
  • /ISO/Identified-Organization/6/1/2/1/86/1/2/1
  • /ISO/3/6/1/2/1/86/1/2/1
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/identified-organization/dod/internet/mgmt/mib/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/org/dod/internet/mgmt/mib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/org/dod/internet/mgmt/mib/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/org/dod/internet/mgmt/stdmib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-organization/dod/internet/mgmt/mib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-organization/dod/internet/mgmt/mib/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/frAtmIwfMIB/frAtmIwfMIBObjects/frAtmIwfConnectionTable/frAtmIwfConnectionEntry

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: OID Repository

frAtmIwfConnectionEntry OBJECT-TYPE SYNTAX FrAtmIwfConnectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The FrAtmIwfConnectionEntry provides an entry for
an interworking connection between a frame relay
PVC and one or more ATM PVCs, or an ATM PVC and
one or more frame relay PVCs. A single frame
relay PVC connected to a single ATM PVC is
referred to as a `point-to-point connection and
is represented by a single row in the FR/ATM IWF
Connection Table. The case of a single frame
relay PVC connected to multiple ATM PVCs (or
single ATM PVC connected to multiple frame relay
PVCs) is referred to as a `point-to-multipoint
connection and is represented by multiple rows in
the FR/ATM IWF Connection Table.
The object frAtmIwfConnIndex uniquely identifies
each point-to-point or point-to-multipoint
connection. The manager obtains the
frAtmIwfConnIndex value by reading the
frAtmIwfConnIndexNext object.
After a frAtmIwfConnIndex is assigned for the
connection, the manager creates one or more rows
in the Cross Connect Table; one for each cross-
connection between the frame relay PVC and an ATM
PVC. In the case of `point-to-multipoint
connections, all rows are indexed by the same
frAtmIwfConnIndex value and MUST refer to the same
frame relay PVC or ATM PVC respectively. An entry
can be created only when at least one pair of
frame relay and ATM PVCs exist.
A row can be established by one-step set-request
with all required parameter values and
frAtmIwfConnRowStatus set to createAndGo(4). The
Agent should perform all error checking as needed.
A pair of cross-connected PVCs, as identified by a
particular value of the indexes, is released by
setting frAtmIwfConnRowStatus to destroy(6). The
Agent may release all associated resources. The
manager may remove the related PVCs thereafter.
Indexes are persistent across reboots of the
system."
INDEX { frAtmIwfConnIndex,
frAtmIwfConnAtmPort,
frAtmIwfConnVpi,
frAtmIwfConnVci,
frAtmIwfConnFrPort,
frAtmIwfConnDlci
}

View at oid-base.com
Automatically extracted from RFC2955

Alternative description: Circitor

The FrAtmIwfConnectionEntry provides an entry for
an interworking connection between a frame relay
PVC and one or more ATM PVCs, or an ATM PVC and
one or more frame relay PVCs. A single frame
relay PVC connected to a single ATM PVC is
referred to as a `point-to-point' connection and
is represented by a single row in the FR/ATM IWF
Connection Table. The case of a single frame
relay PVC connected to multiple ATM PVCs (or
single ATM PVC connected to multiple frame relay
PVCs) is referred to as a `point-to-multipoint'
connection and is represented by multiple rows in
the FR/ATM IWF Connection Table.

The object frAtmIwfConnIndex uniquely identifies
each point-to-point or point-to-multipoint
connection. The manager obtains the
frAtmIwfConnIndex value by reading the
frAtmIwfConnIndexNext object.

After a frAtmIwfConnIndex is assigned for the
connection, the manager creates one or more rows
in the Cross Connect Table; one for each cross-
connection between the frame relay PVC and an ATM
PVC. In the case of `point-to-multipoint'
connections, all rows are indexed by the same
frAtmIwfConnIndex value and MUST refer to the same
frame relay PVC or ATM PVC respectively. An entry
can be created only when at least one pair of
frame relay and ATM PVCs exist.

A row can be established by one-step set-request
with all required parameter values and
frAtmIwfConnRowStatus set to createAndGo(4). The
Agent should perform all error checking as needed.
A pair of cross-connected PVCs, as identified by a
particular value of the indexes, is released by
setting frAtmIwfConnRowStatus to destroy(6). The
Agent may release all associated resources. The
manager may remove the related PVCs thereafter.
Indexes are persistent across reboots of the
system.

Parsed from file FR-ATM-PVC-SERVICE-IWF-MIB.mib
Module: FR-ATM-PVC-SERVICE-IWF-MIB

Source file: Download FR-ATM-PVC-SERVICE-IWF-MIB.txt · Publisher's file

Copy from Netdisco; File: rfc/FR-ATM-PVC-SERVICE-IWF-MIB.txt; 47,251 bytes

Vendor MIB copy from the Netdisco archive.

Related source files and packages:

Source file: Download FR-ATM-PVC-SERVICE-IWF-MIB-2955.mib · Publisher's file

S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0); Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:39:45; File: S3910-24TS and S3910-48TS Switches SNMP MIB Files/S3910 Series-standard.zip!standard/FR-ATM-PVC-SERVICE-IWF-MIB-2955.mib; Publisher path: mall/doc/2024012909344598z6fl.zip; 47,244 bytes

Related source files and packages:

  • S3100-16TF Switch SNMP MIB FilesS3100-16TF Switch SNMP MIB Files; Models: S3100-16TF; Catalog updated: 2026-10-08 14:09:01; File: mall/resource/s3100-16tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Thu, 08 Oct 2026 06:09:01 GMT; 2.4 MiB
  • NC8200 and NC8400 Series Switches SNMP MIB FilesNC8200 and NC8400 Series Switches SNMP MIB Files; Models: NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH; Catalog updated: 2024-05-28 19:26:13; File: mall/file/user_manual/nc8200-and-nc8400-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:34:12 GMT; 1.5 MiB
  • S5810 Series Switches SNMP MIB FilesS5810 Series Switches SNMP MIB Files; Models: S5810-28FS, S5810-48FS, S5810-48TS-P; Catalog updated: 2024-05-28 19:26:26; File: mall/file/datasheet/s5810-series-switches-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 04:20:38 GMT; 2.3 MiB
Show all 9 related files and packages
  • S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0)S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0); Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:39:45; File: mall/doc/2024012909344598z6fl.zip; Publisher Last-Modified: Mon, 29 Jan 2024 01:34:50 GMT; 1.5 MiB
  • S3910 Series Swithes SNMP MIB FilesS3910 Series Swithes SNMP MIB Files; Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:26:04; File: mall/file/user_manual/s3910-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:37:14 GMT; 2.4 MiB
  • S5860 Series Swithes SNMP MIB FilesS5860 Series Swithes SNMP MIB Files; Models: S5860-20SQ, S5860-24XB-U, S5860-48SC; Catalog updated: 2026-02-22 10:42:59; File: mall/file/user_manual/s5860-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:40:34 GMT; 2.4 MiB
  • S3410 Series Swithes SNMP MIB FilesS3410 Series Swithes SNMP MIB Files; Models: S3410-24TS-P; Catalog updated: 2024-05-28 19:26:04; File: mall/file/user_manual/s3410-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:36:20 GMT; 2.4 MiB
  • S5810 Series Switches SNMP MIB Files (V1.0)S5810 Series Switches SNMP MIB Files (V1.0); Models: S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P; Catalog updated: 2024-05-28 19:39:45; File: mall/doc/20240129093459svlvsn.zip; Publisher Last-Modified: Mon, 29 Jan 2024 01:35:04 GMT; 1.5 MiB
  • N5860 and N8560 Series Switches SNMP MIB FilesN5860 and N8560 Series Switches SNMP MIB Files; Models: N5860-48SC, N8560-32C, N8560-48BC, N8560-64C; Catalog updated: 2024-09-12 14:10:35; File: mall/file/user_manual/n5860-and-n8560-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:33:20 GMT; 1.5 MiB
Other official packages with the same file

s3100-16tf-switch-snmp-mib-files.zip

s5860-series-swithes-snmp-mib-files.zip

s3910-series-swithes-snmp-mib-files.zip

s3410-series-swithes-snmp-mib-files.zip

Source file: Download FR-ATM-PVC-SERVICE-IWF-MIB · Publisher's file

Copy from Observium Community; File: rfc/FR-ATM-PVC-SERVICE-IWF-MIB; 47,251 bytes

Vendor MIB copy from the Observium Community archive.

Related source files and packages:

Source file: Download RFC 2955 · Publisher's file · RFC errata

File: rfc/rfc2955.txt; 83,281 bytes

Source file: Download FR-ATM-PVC-SERVICE-IWF-MIB.mib

Publisher path: Mibs; 49,930 bytes

Alternative description: MIBdepot

The FrAtmIwfConnectionEntry provides an entry for
an interworking connection between a frame relay
PVC and one or more ATM PVCs, or an ATM PVC and
one or more frame relay PVCs. A single frame
relay PVC connected to a single ATM PVC is
referred to as a `point-to-point' connection and
is represented by a single row in the FR/ATM IWF
Connection Table. The case of a single frame
relay PVC connected to multiple ATM PVCs (or
single ATM PVC connected to multiple frame relay
PVCs) is referred to as a `point-to-multipoint'
connection and is represented by multiple rows in
the FR/ATM IWF Connection Table.

The object frAtmIwfConnIndex uniquely identifies
each point-to-point or point-to-multipoint
connection. The manager obtains the
frAtmIwfConnIndex value by reading the
frAtmIwfConnIndexNext object.

After a frAtmIwfConnIndex is assigned for the
connection, the manager creates one or more rows
in the Cross Connect Table; one for each cross-
connection between the frame relay PVC and an ATM
PVC. In the case of `point-to-multipoint'
connections, all rows are indexed by the same
frAtmIwfConnIndex value and MUST refer to the same
frame relay PVC or ATM PVC respectively. An entry
can be created only when at least one pair of
frame relay and ATM PVCs exist.

A row can be established by one-step set-request
with all required parameter values and
frAtmIwfConnRowStatus set to createAndGo(4). The
Agent should perform all error checking as needed.
A pair of cross-connected PVCs, as identified by a
particular value of the indexes, is released by
setting frAtmIwfConnRowStatus to destroy(6). The
Agent may release all associated resources. The
manager may remove the related PVCs thereafter.
Indexes are persistent across reboots of the
system.

Source file: Download rfc2955-FR-to-ATM-Service-Interworking.mib.txt

File: ietf_rfcs/rfc2955-FR-to-ATM-Service-Interworking.mib.txt; 49,025 bytes

Information from MIBdepot

frAtmIwfConnectionEntry OBJECT-TYPE
             SYNTAX      FrAtmIwfConnectionEntry
             MAX-ACCESS  not-accessible
             STATUS      current
             DESCRIPTION
                     "The FrAtmIwfConnectionEntry provides an entry for
                     an interworking connection between a frame relay
                     PVC and one or more ATM PVCs, or an ATM PVC and
                     one or more frame relay PVCs.  A single frame
                     relay PVC connected to a single ATM PVC is
                     referred to as a `point-to-point' connection and
                     is represented by a single row in the FR/ATM IWF
                     Connection Table.  The case of a single frame
                     relay PVC connected to multiple ATM PVCs (or
                     single ATM PVC connected to multiple frame relay
                     PVCs) is referred to as a `point-to-multipoint'
                     connection and is represented by multiple rows in
                     the FR/ATM IWF Connection Table.

                     The object frAtmIwfConnIndex uniquely identifies
                     each point-to-point or point-to-multipoint
                     connection.  The manager obtains the
                     frAtmIwfConnIndex value by reading the
                     frAtmIwfConnIndexNext object.

                     After a frAtmIwfConnIndex is assigned for the
                     connection, the manager creates one or more rows
                     in the Cross Connect Table; one for each cross-
                     connection between the frame relay PVC and an ATM
                     PVC. In the case of `point-to-multipoint'
                     connections, all rows are indexed by the same
                     frAtmIwfConnIndex value and MUST refer to the same
                     frame relay PVC or ATM PVC respectively.  An entry
                     can be created only when at least one pair of
                     frame relay and ATM PVCs exist.

                     A row can be established by one-step set-request
                     with all required parameter values and
                     frAtmIwfConnRowStatus set to createAndGo(4). The
                     Agent should perform all error checking as needed.
                     A pair of cross-connected PVCs, as identified by a
                     particular value of the indexes, is released by
                     setting frAtmIwfConnRowStatus to destroy(6). The
                     Agent may release all associated resources. The
                     manager may remove the related PVCs thereafter.
                     Indexes are persistent across reboots of the
                     system."
             INDEX   { frAtmIwfConnIndex,
                       frAtmIwfConnAtmPort,
                       frAtmIwfConnVpi,
                       frAtmIwfConnVci,
                       frAtmIwfConnFrPort,
                       frAtmIwfConnDlci
                     }
             ::= { frAtmIwfConnectionTable 1 }

Information from Circitor

frAtmIwfConnectionEntry OBJECT-TYPE
             SYNTAX      FrAtmIwfConnectionEntry
             MAX-ACCESS  not-accessible
             STATUS      current
             DESCRIPTION
                     "The FrAtmIwfConnectionEntry provides an entry for
                     an interworking connection between a frame relay
                     PVC and one or more ATM PVCs, or an ATM PVC and
                     one or more frame relay PVCs.  A single frame
                     relay PVC connected to a single ATM PVC is
                     referred to as a `point-to-point' connection and
                     is represented by a single row in the FR/ATM IWF
                     Connection Table.  The case of a single frame
                     relay PVC connected to multiple ATM PVCs (or
                     single ATM PVC connected to multiple frame relay
                     PVCs) is referred to as a `point-to-multipoint'
                     connection and is represented by multiple rows in
                     the FR/ATM IWF Connection Table.

                     The object frAtmIwfConnIndex uniquely identifies
                     each point-to-point or point-to-multipoint
                     connection.  The manager obtains the
                     frAtmIwfConnIndex value by reading the
                     frAtmIwfConnIndexNext object.

                     After a frAtmIwfConnIndex is assigned for the
                     connection, the manager creates one or more rows
                     in the Cross Connect Table; one for each cross-
                     connection between the frame relay PVC and an ATM
                     PVC. In the case of `point-to-multipoint'
                     connections, all rows are indexed by the same
                     frAtmIwfConnIndex value and MUST refer to the same
                     frame relay PVC or ATM PVC respectively.  An entry
                     can be created only when at least one pair of
                     frame relay and ATM PVCs exist.

                     A row can be established by one-step set-request
                     with all required parameter values and
                     frAtmIwfConnRowStatus set to createAndGo(4). The
                     Agent should perform all error checking as needed.
                     A pair of cross-connected PVCs, as identified by a
                     particular value of the indexes, is released by
                     setting frAtmIwfConnRowStatus to destroy(6). The
                     Agent may release all associated resources. The
                     manager may remove the related PVCs thereafter.
                     Indexes are persistent across reboots of the
                     system."
             INDEX   { frAtmIwfConnIndex,
                       frAtmIwfConnAtmPort,
                       frAtmIwfConnVpi,
                       frAtmIwfConnVci,
                       frAtmIwfConnFrPort,
                       frAtmIwfConnDlci
                     }
             ::= { frAtmIwfConnectionTable 1 }

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Direct children (19)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.86.1.2.1.1 frAtmIwfConnIndex00 frAtmIwfConnIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique v…
1.3.6.1.2.1.86.1.2.1.2 frAtmIwfConnAtmPort00 frAtmIwfConnAtmPort OBJECT-TYPE SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index in the if…
1.3.6.1.2.1.86.1.2.1.3 frAtmIwfConnVpi00 frAtmIwfConnVpi OBJECT-TYPE SYNTAX AtmVpIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VPI of the ATM PVC…
1.3.6.1.2.1.86.1.2.1.4 frAtmIwfConnVci00 frAtmIwfConnVci OBJECT-TYPE SYNTAX AtmVcIdentifier
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VCI of the ATM PVC…
1.3.6.1.2.1.86.1.2.1.5 frAtmIwfConnFrPort00 frAtmIwfConnFrPort OBJECT-TYPE SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index in the ift…
1.3.6.1.2.1.86.1.2.1.6 frAtmIwfConnDlci00 frAtmIwfConnDlci OBJECT-TYPE SYNTAX Integer32 (16..4194303)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The DLCI that…
1.3.6.1.2.1.86.1.2.1.7 frAtmIwfConnRowStatus00 frAtmIwfConnRowStatus OBJECT-TYPE SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The table row may be crea…
1.3.6.1.2.1.86.1.2.1.8 frAtmIwfConnAdminStatus00 frAtmIwfConnAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The de…
1.3.6.1.2.1.86.1.2.1.9 frAtmIwfConnAtm2FrOperStatus00 frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The…
1.3.6.1.2.1.86.1.2.1.10 frAtmIwfConnAtm2FrLastChange00 frAtmIwfConnAtm2FrLastChange OBJECT-TYPE SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTi…
1.3.6.1.2.1.86.1.2.1.11 frAtmIwfConnFr2AtmOperStatus00 frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The…
1.3.6.1.2.1.86.1.2.1.12 frAtmIwfConnFr2AtmLastChange00 frAtmIwfConnFr2AtmLastChange OBJECT-TYPE SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTi…
1.3.6.1.2.1.86.1.2.1.13 frAtmIwfConnectionDescriptor00 frAtmIwfConnectionDescriptor OBJECT-TYPE SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value represen…
1.3.6.1.2.1.86.1.2.1.14 frAtmIwfConnFailedFrameTranslate00 frAtmIwfConnFailedFrameTranslate OBJECT-TYPE SYNTAX Counter32
UNITS "Frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"T…
1.3.6.1.2.1.86.1.2.1.15 frAtmIwfConnOverSizedFrames00 frAtmIwfConnOverSizedFrames OBJECT-TYPE SYNTAX Counter32
UNITS "Frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count …
1.3.6.1.2.1.86.1.2.1.16 frAtmIwfConnFailedAal5PduTranslate00 frAtmIwfConnFailedAal5PduTranslate OBJECT-TYPE SYNTAX Counter32
UNITS "PDUs"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"T…
1.3.6.1.2.1.86.1.2.1.17 frAtmIwfConnOverSizedSDUs00 frAtmIwfConnOverSizedSDUs OBJECT-TYPE SYNTAX Counter32
UNITS "SDUs"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of A…
1.3.6.1.2.1.86.1.2.1.18 frAtmIwfConnCrcErrors00 frAtmIwfConnCrcErrors OBJECT-TYPE SYNTAX Counter32
UNITS "PDUs"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of …
1.3.6.1.2.1.86.1.2.1.19 frAtmIwfConnSarTimeOuts00 frAtmIwfConnSarTimeOuts OBJECT-TYPE SYNTAX Counter32
UNITS "PDUs"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number o…