Reference record for OID 1.3.6.1.4.1.1751.2.18.6.9.1.18

Parent
1.3.6.1.4.1.1751.2.18.6.9.1 (vbrAtmPvcVccEntry)
Node code
18
Node name
vbrAtmPvcVccCnfrmTypeB2A
Numeric OID
1.3.6.1.4.1.1751.2.18.6.9.1.18
URN notation
urn:oid:1.3.6.1.4.1.1751.2.18.6.9.1.18
Type
OBJECT-TYPE
ASN.1 notation

{1 3 6 1 4 1 1751 2 18 6 9 1 18}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lucent(1751) mibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lucent(1751) lucent-MIB(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lucent(1751) lucentMibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lucent(1751) mibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lucent(1751) lucent-MIB(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lucent(1751) lucentMibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lucent(1751) mibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lucent(1751) lucent-MIB(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lucent(1751) lucentMibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lucent(1751) mibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lucent(1751) lucent-MIB(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lucent(1751) lucentMibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lucent(1751) mibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lucent(1751) lucent-MIB(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lucent(1751) lucentMibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lucent(1751) mibs(2) acMIB(18) connectionConfig(6) vbrAtmPvcVccTable(9) vbrAtmPvcVccEntry(1) vbrAtmPvcVccCnfrmTypeB2A(18)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1751/2/18/6/9/1/18
  • /ISO/Identified-Organization/6/1/4/1/1751/2/18/6/9/1/18
  • /ISO/3/6/1/4/1/1751/2/18/6/9/1/18
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/lucent/mibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/enterprise/lucent/lucent-MIB/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/enterprise/lucent/lucentMibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/enterprises/lucent/mibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/enterprises/lucent/lucent-MIB/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/enterprises/lucent/lucentMibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lucent/mibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lucent/lucent-MIB/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lucent/lucentMibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/vendor-objects/lucent/mibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/vendor-objects/lucent/lucent-MIB/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/identified-organization/dod/internet/private/vendor-objects/lucent/lucentMibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/org/dod/internet/private/enterprise/lucent/mibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/org/dod/internet/private/enterprise/lucent/lucent-MIB/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/org/dod/internet/private/enterprise/lucent/lucentMibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • /iso/org/dod/internet/private/enterprises/lucent/mibs/acMIB/connectionConfig/vbrAtmPvcVccTable/vbrAtmPvcVccEntry/vbrAtmPvcVccCnfrmTypeB2A
  • Additional combinations skipped.

Descriptions

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

Primary description: Circitor

The following is the description of this field
This will be used in conjunction with the
service type field to get the correct
traffic behaviour. In the conformances the
the 0 or 0plus1 refers to the clp bit in the
cells. If 0plus1 is the bucket reference then
the clp bit is ignored. If 0 is specified for
the bucket then check only clp=0 cells.
1: Best Effort will try to send all cellsin a
best effort way. This will follow the
Aqueman Algorithm
2: one-bucket-notag-0plus1 will use 1 bucket
i.e is the PCR(0+1) bucket and drop all
cells in excess.
3: two-bucket-notag-0plus1-0plus1 uses 2 buckets.
The 2 buckets are pcr(0+1) and scr(0+1).
All cells conforming to both buckets will be
passed through. The rest will be dropped.
4: two-bucket-notag-0plus1-0 uses 2 buckets.
The 2 buckets are pcr(0+1) and scr(0) or
pcr(0). Cells which conform to both buckets
are passed through. The rest are dropped.
5: two-bucket-tag-0plus1-0 uses 2 buckets.
The 2 buckets are pcr(0+1) and scr(0) or
pcr(0). Cells which do not conform to the first
bucket are dropped. Cells which do not
conform to the 2nd bucket are tagged.
6: best-effort-tag. Tag all cells and then
do a best effort.

Parsed from file ACMIB.mib
Module: ACMIB

Source file: Download ACMIB.mib

Publisher path: Mibs; 1.7 MiB

Alternative description: MIBdepot

The following is the description of this field
This will be used in conjunction with the
service type field to get the correct
traffic behaviour. In the conformances the
the 0 or 0plus1 refers to the clp bit in the
cells. If 0plus1 is the bucket reference then
the clp bit is ignored. If 0 is specified for
the bucket then check only clp=0 cells.
1: Best Effort will try to send all cellsin a
best effort way. This will follow the
Aqueman Algorithm
2: one-bucket-notag-0plus1 will use 1 bucket
i.e is the PCR(0+1) bucket and drop all
cells in excess.
3: two-bucket-notag-0plus1-0plus1 uses 2 buckets.
The 2 buckets are pcr(0+1) and scr(0+1).
All cells conforming to both buckets will be
passed through. The rest will be dropped.
4: two-bucket-notag-0plus1-0 uses 2 buckets.
The 2 buckets are pcr(0+1) and scr(0) or
pcr(0). Cells which conform to both buckets
are passed through. The rest are dropped.
5: two-bucket-tag-0plus1-0 uses 2 buckets.
The 2 buckets are pcr(0+1) and scr(0) or
pcr(0). Cells which do not conform to the first
bucket are dropped. Cells which do not
conform to the 2nd bucket are tagged.
6: best-effort-tag. Tag all cells and then
do a best effort.

Source file: Download ac120.my.V07.00.C00.mib.txt

File: lucent/ac120.my.V07.00.C00.mib.txt; 1.2 MiB

Source file: Download Ac120.my.txt

File: lucent/Ac120.my.txt; 1.6 MiB

vbrAtmPvcVccCnfrmTypeB2A — MIBdepot

The following is the description of this field This will be used in conjunction with the service type field to get the correct traffic behaviour. In the conformances the the 0 or 0plus1 refers to the clp bit in the cells. If 0plus1 is the bucket reference then the clp bit is ignored. If 0 is specified for the bucket then check only clp=0 cells. 1: Best Effort will try to send all cellsin a best effort way. This will follow the Aqueman Algorithm 2: one-bucket-notag-0plus1 will use 1 bucket i.e is the PCR(0+1) bucket and drop all cells in excess. 3: two-bucket-notag-0plus1-0plus1 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0+1). All cells conforming to both buckets will be passed thru. The rest will be dropped. 4: two-bucket-notag-0plus1-0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which conform to both buckets are passed thru. The rest are dropped. 5: two-bucket-tag-0plus1-0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which do not conform to the first bucket are dropped. Cells which do not conform to the 2nd bucket are tagged. 6: best-effort-tag. Tag all cells and then do a best effort.

Source records

vbrAtmPvcVccCnfrmTypeB2A

Status in source: current.

Names: vbrAtmPvcVccCnfrmTypeB2A

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vbrAtmPvcVccCnfrmTypeB2A",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "best-effort",
    "(",
    "1",
    ")",
    ",",
    "one-bucket-notag-0plus1",
    "(",
    "2",
    ")",
    ",",
    "two-bucket-notag-0plus1-0plus1",
    "(",
    "3",
    ")",
    ",",
    "two-bucket-notag-0plus1-0",
    "(",
    "4",
    ")",
    ",",
    "two-bucket-tag-0plus1-0",
    "(",
    "5",
    ")",
    ",",
    "best-effort-tag",
    "(",
    "6",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The following is the description of this field This will be used in conjunction with the service type field to get the correct traffic behaviour. In the conformances the the 0 or 0plus1 refers to the clp bit in the cells. If 0plus1 is the bucket reference then the clp bit is ignored. If 0 is specified for the bucket then check only clp=0 cells. 1: Best Effort will try to send all cellsin a best effort way. This will follow the Aqueman Algorithm 2: one-bucket-notag-0plus1 will use 1 bucket i.e is the PCR(0+1) bucket and drop all cells in excess. 3: two-bucket-notag-0plus1-0plus1 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0+1). All cells conforming to both buckets will be passed thru. The rest will be dropped. 4: two-bucket-notag-0plus1-0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which conform to both buckets are passed thru. The rest are dropped. 5: two-bucket-tag-0plus1-0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which do not conform to the first bucket are dropped. Cells which do not conform to the 2nd bucket are tagged. 6: best-effort-tag. Tag all cells and then do a best effort. \"",
    "DEFVAL",
    "{",
    "best-effort",
    "}",
    "::=",
    "{",
    "vbrAtmPvcVccEntry",
    "18",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "best-effort",
            1
          ],
          [
            "one-bucket-notag-0plus1",
            2
          ],
          [
            "two-bucket-notag-0plus1-0plus1",
            3
          ],
          [
            "two-bucket-notag-0plus1-0",
            4
          ],
          [
            "two-bucket-tag-0plus1-0",
            5
          ],
          [
            "best-effort-tag",
            6
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The following is the description of this field This will be used in conjunction with the service type field to get the correct traffic behaviour. In the conformances the the 0 or 0plus1 refers to the clp bit in the cells. If 0plus1 is the bucket reference then the clp bit is ignored. If 0 is specified for the bucket then check only clp=0 cells. 1: Best Effort will try to send all cellsin a best effort way. This will follow the Aqueman Algorithm 2: one-bucket-notag-0plus1 will use 1 bucket i.e is the PCR(0+1) bucket and drop all cells in excess. 3: two-bucket-notag-0plus1-0plus1 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0+1). All cells conforming to both buckets will be passed thru. The rest will be dropped. 4: two-bucket-notag-0plus1-0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which conform to both buckets are passed thru. The rest are dropped. 5: two-bucket-tag-0plus1-0 uses 2 buckets. The 2 buckets are pcr(0+1) and scr(0) or pcr(0). Cells which do not conform to the first bucket are dropped. Cells which do not conform to the 2nd bucket are tagged. 6: best-effort-tag. Tag all cells and then do a best effort."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "best-effort"
    ]
  ]
}
  • Preserved mibdepot archive

    Module: ACMIB

    Published definition
    vbrAtmPvcVccCnfrmTypeB2A    OBJECT-TYPE
                    SYNTAX INTEGER {
        				best-effort(1),
                                    one-bucket-notag-0plus1(2),
                                    two-bucket-notag-0plus1-0plus1(3),
                                    two-bucket-notag-0plus1-0(4),
                                    two-bucket-tag-0plus1-0(5),
                                    best-effort-tag(6)
                                   }
                    MAX-ACCESS read-write
                    STATUS current
                    DESCRIPTION "The following is the description of this field
            		This will be used in conjunction with the
    			service type field to get the correct
    			traffic behaviour. In the conformances the 
    			the 0 or 0plus1 refers to the clp bit in the
    			cells. If 0plus1 is the bucket reference then
    			the clp bit is ignored. If 0 is specified for 
    			the bucket then check only clp=0 cells.
    			1: Best Effort will try to send all cellsin a 
    			best effort way. This will follow the 
    			Aqueman Algorithm
    			2: one-bucket-notag-0plus1 will use 1 bucket
    			i.e is the PCR(0+1) bucket and drop all
    			cells in excess.
    			3: two-bucket-notag-0plus1-0plus1 uses 2 buckets.
    			The 2 buckets are pcr(0+1) and scr(0+1).
    			All cells conforming to both buckets will be
    			passed thru. The rest will be dropped.
    			4: two-bucket-notag-0plus1-0 uses 2 buckets.
    			The 2 buckets are pcr(0+1) and scr(0) or 
    			pcr(0). Cells which conform to both buckets
    			are passed thru. The rest are dropped.
    			5: two-bucket-tag-0plus1-0 uses 2 buckets.
    			The 2 buckets are pcr(0+1) and scr(0) or 
    			pcr(0). Cells which do not conform to the first
    			bucket are dropped. Cells which do not 
    			conform to the 2nd bucket are tagged.
    			6: best-effort-tag. Tag all cells and then
    			do a best effort.  "
                    DEFVAL { best-effort }
                    ::= { vbrAtmPvcVccEntry 18 }
    Module imports
    {'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'TimeStamp', 'RowStatus', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'NOTIFICATION-TYPE', 'Counter32', 'Integer32', 'IpAddress', 'TimeTicks', 'enterprises'], 'RFC1213-MIB': ['ifIndex', 'mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
    · Download Ac120.my.V06.03.C0-1.mib.txt
    Source location: ACMIB::vbrAtmPvcVccCnfrmTypeB2A.
    Source version and references

    Archived: 2026-10-19T00:22:09.937995+00:00.

Information from OID Repository

Vendor: Lucent Technologies
Module: ACMIB

[Automatically extracted from oidview.com]

Information from MIBdepot

vbrAtmPvcVccCnfrmTypeB2A    OBJECT-TYPE
                SYNTAX INTEGER {
    				best-effort(1),
                                one-bucket-notag-0plus1(2),
                                two-bucket-notag-0plus1-0plus1(3),
                                two-bucket-notag-0plus1-0(4),
                                two-bucket-tag-0plus1-0(5),
                                best-effort-tag(6)
                               }
                MAX-ACCESS read-write
                STATUS current
                DESCRIPTION "The following is the description of this field
        		This will be used in conjunction with the
			service type field to get the correct
			traffic behaviour. In the conformances the 
			the 0 or 0plus1 refers to the clp bit in the
			cells. If 0plus1 is the bucket reference then
			the clp bit is ignored. If 0 is specified for 
			the bucket then check only clp=0 cells.
			1: Best Effort will try to send all cellsin a 
			best effort way. This will follow the 
			Aqueman Algorithm
			2: one-bucket-notag-0plus1 will use 1 bucket
			i.e is the PCR(0+1) bucket and drop all
			cells in excess.
			3: two-bucket-notag-0plus1-0plus1 uses 2 buckets.
			The 2 buckets are pcr(0+1) and scr(0+1).
			All cells conforming to both buckets will be
			passed through. The rest will be dropped.
			4: two-bucket-notag-0plus1-0 uses 2 buckets.
			The 2 buckets are pcr(0+1) and scr(0) or 
			pcr(0). Cells which conform to both buckets
			are passed through. The rest are dropped.
			5: two-bucket-tag-0plus1-0 uses 2 buckets.
			The 2 buckets are pcr(0+1) and scr(0) or 
			pcr(0). Cells which do not conform to the first
			bucket are dropped. Cells which do not 
			conform to the 2nd bucket are tagged.
			6: best-effort-tag. Tag all cells and then
			do a best effort.  "
                DEFVAL { best-effort }
                ::= { vbrAtmPvcVccEntry 18 }

Information from Circitor

vbrAtmPvcVccCnfrmTypeB2A    OBJECT-TYPE
                SYNTAX INTEGER {
                                    best-effort(1),
                                one-bucket-notag-0plus1(2),
                                two-bucket-notag-0plus1-0plus1(3),
                                two-bucket-notag-0plus1-0(4),
                                two-bucket-tag-0plus1-0(5),
                                best-effort-tag(6)
                               }
                MAX-ACCESS read-write
                STATUS current
                DESCRIPTION "The following is the description of this field
                        This will be used in conjunction with the
                        service type field to get the correct
                        traffic behaviour. In the conformances the 
                        the 0 or 0plus1 refers to the clp bit in the
                        cells. If 0plus1 is the bucket reference then
                        the clp bit is ignored. If 0 is specified for 
                        the bucket then check only clp=0 cells.
                        1: Best Effort will try to send all cellsin a 
                        best effort way. This will follow the 
                        Aqueman Algorithm
                        2: one-bucket-notag-0plus1 will use 1 bucket
                        i.e is the PCR(0+1) bucket and drop all
                        cells in excess.
                        3: two-bucket-notag-0plus1-0plus1 uses 2 buckets.
                        The 2 buckets are pcr(0+1) and scr(0+1).
                        All cells conforming to both buckets will be
                        passed through. The rest will be dropped.
                        4: two-bucket-notag-0plus1-0 uses 2 buckets.
                        The 2 buckets are pcr(0+1) and scr(0) or 
                        pcr(0). Cells which conform to both buckets
                        are passed through. The rest are dropped.
                        5: two-bucket-tag-0plus1-0 uses 2 buckets.
                        The 2 buckets are pcr(0+1) and scr(0) or 
                        pcr(0). Cells which do not conform to the first
                        bucket are dropped. Cells which do not 
                        conform to the 2nd bucket are tagged.
                        6: best-effort-tag. Tag all cells and then
                        do a best effort.  "
                DEFVAL { best-effort }
                ::= { vbrAtmPvcVccEntry 18 }

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1751)

Richard Bantel

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.1751)

Håkon Helmers

Siblings (26)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1751.2.18.6.9.1.1 vbrAtmPvcVccIfA00 Interface index for side A, the variable bit rate
side, of a variable bit rate-atm PVC VCC
connection. Number value is interpret…
1.3.6.1.4.1.1751.2.18.6.9.1.2 vbrAtmPvcVccIfB00 Interface index for side B, the atm side, of a
variable bit rate-atm PVC VCC connection. Number
value is interpreted as an inter…
1.3.6.1.4.1.1751.2.18.6.9.1.3 vbrAtmPvcVccVpiB00 VPI value for side B, the atm side, of a variable
bit rate-atm PVC VCC connection. Valid range is a
number between 0 and 4095.
1.3.6.1.4.1.1751.2.18.6.9.1.4 vbrAtmPvcVccVciB00 VCI value for side B, the atm side, of a variable
bit rate-atm PVC VCC connection. Valid range is a
number between 0 and 65535.
1.3.6.1.4.1.1751.2.18.6.9.1.5 vbrAtmPvcVccServiceType00 service type
1.3.6.1.4.1.1751.2.18.6.9.1.6 vbrAtmPvcVccPeakCellRateA2B00 peak cell rate - side A, in cell per second
1.3.6.1.4.1.1751.2.18.6.9.1.7 vbrAtmPvcVccSusCellRateA2B00 sustained rate - side A, in cell per second
1.3.6.1.4.1.1751.2.18.6.9.1.8 vbrAtmPvcVccMaxBurstSizeA2B00 maximum burst size - side A, in cells
1.3.6.1.4.1.1751.2.18.6.9.1.9 vbrAtmPvcVccPeakCellRateB2A00 peak rate - side B, in cell per second.
1.3.6.1.4.1.1751.2.18.6.9.1.10 vbrAtmPvcVccSusCellRateB2A00 sustained rate - side B, in cell per second.
1.3.6.1.4.1.1751.2.18.6.9.1.11 vbrAtmPvcVccMaxBurstSizeB2A00 maximum burst size - side B, in cells.
1.3.6.1.4.1.1751.2.18.6.9.1.12 vbrAtmPvcVccFlow00 Flow type
1.3.6.1.4.1.1751.2.18.6.9.1.13 vbrAtmPvcVccRowStatus00 row status
1.3.6.1.4.1.1751.2.18.6.9.1.14 vbrAtmPvcVccConnectionStatus00 Indicates the current connections status.
Active: All interfaces through which the
connection is going are in service.
Inactive: …
1.3.6.1.4.1.1751.2.18.6.9.1.15 vbrAtmPvcVccDualHomed00 Does this PVC need a backup Dual homing PVC.
1.3.6.1.4.1.1751.2.18.6.9.1.16 vbrAtmPvcVccOamStatus00 Indicates the OAM monitoring status of side A.
The 2 possible states are:
Unsupp: No monitoring enabled.
End-Pt: A side is only …
1.3.6.1.4.1.1751.2.18.6.9.1.17 vbrAtmPvcVccViB00 VI to associate the Egress part of the
A2B connection .
1.3.6.1.4.1.1751.2.18.6.9.1.19 vbrAtmPvcVccVUNIB00 VUNI to associate the Egress part of the
A2B connection .
1.3.6.1.4.1.1751.2.18.6.9.1.20 vbrAtmPvcVccOAMConnEndPtStatus00 Connection endpoint status. Valid only
at connection endpoint.
1.3.6.1.4.1.1751.2.18.6.9.1.21 vbrAtmPvcVccOAMSegEndPtStatus00 Segment endpoint status. Valid only at
segment/connection endpoint.
1.3.6.1.4.1.1751.2.18.6.9.1.22 vbrAtmPvcVccMfsB2A00 Maximum Frame Size for GFR traffic
1.3.6.1.4.1.1751.2.18.6.9.1.23 vbrAtmPvcVccConnFailureCauseA00 connestion status reason code
1.3.6.1.4.1.1751.2.18.6.9.1.24 vbrAtmPvcVccConnFailureCauseB00 connection status reason code
1.3.6.1.4.1.1751.2.18.6.9.1.25 vbrAtmPvcVccSarTypeB00 This field will be used to connect hdlc
to atm directly when sar type is none or aal5 or
go through dsp2 first when sar type is a…
1.3.6.1.4.1.1751.2.18.6.9.1.26 vbrAtmPvcVccAal2Cid00 Aal2 Cid Used to pack hdlc chan in an
Atm Trunk. This value will be unique
per Atm Trunk. This field will be applicable
when Aal t…
1.3.6.1.4.1.1751.2.18.6.9.1.27 vbrAtmPvcVccTrafficShapingA2B00 Traffic Shaping Support in the A2B direction.