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 ac120.my.V07.00.C00.mib.txt
Company: None
Module: ACMIB
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
Vendor: Lucent Technologies
Module: ACMIB
[Automatically extracted from oidview.com]
frAtmPvcVccCnfrmTypeB2A 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 } ::= { frAtmPvcVccEntry 31 }
frAtmPvcVccCnfrmTypeB2A 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 } ::= { frAtmPvcVccEntry 31 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1751.2.18.6.7.1.1 | frAtmPvcVccIfA | 0 | 0 | Interface index for side A, the frame relay side, of a frame relay-atm PVC VCC connection. Number value is interpreted as an int… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.2 | frAtmPvcVccDlciA | 0 | 0 | DLCI value for side A, the frame relay side, of a frame relay-atm PVC VCC connection. Valid range is a number between 0 and 1023. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.3 | frAtmPvcVccIfB | 0 | 0 | Interface index for side B, the atm side, of a frame relay-atm PVC VCC connection. Number value is interpreted as an interface o… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.4 | frAtmPvcVccVpiB | 0 | 0 | VPI value for side B, the atm side, of a frame relay-atm PVC VCC connection. Valid range is a number between 0 and 4095. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.5 | frAtmPvcVccVciB | 0 | 0 | VCI value for side B, the atm side, of a frame relay-atm PVC VCC connection. Valid range is a number between 0 and 65535. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.6 | frAtmPvcVccMaxFrameSizeIn | 0 | 0 | The value of this object is the size in octets of the largest frame relay information field for this PVC in the ingress direction… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.7 | frAtmPvcVccBcIn | 0 | 0 | The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this PVC in the ingress direct… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.8 | frAtmPvcVccBeIn | 0 | 0 | The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this PVC in the ingress directio… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.9 | frAtmPvcVccCirIn | 0 | 0 | The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this PVC in … |
| 1.3.6.1.4.1.1751.2.18.6.7.1.10 | frAtmPvcVccMaxFrameSizeOut | 0 | 0 | The value of this object is the size in octets of the largest frame relay information field for this PVC in the egress direction … |
| 1.3.6.1.4.1.1751.2.18.6.7.1.11 | frAtmPvcVccBcOut | 0 | 0 | The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this PVC in the egress directi… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.12 | frAtmPvcVccBeOut | 0 | 0 | The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this PVC in the egress direction… |
| 1.3.6.1.4.1.1751.2.18.6.7.1.13 | frAtmPvcVccCirOut | 0 | 0 | The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this PVC in … |
| 1.3.6.1.4.1.1751.2.18.6.7.1.14 | frAtmPvcVccServiceType | 0 | 0 | service type, Frame relay traffic is carried by VBR type of service only. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.15 | frAtmPvcVccFlow | 0 | 0 | Flow Type |
| 1.3.6.1.4.1.1751.2.18.6.7.1.16 | frAtmPvcVccRowStatus | 0 | 0 | row status |
| 1.3.6.1.4.1.1751.2.18.6.7.1.17 | frAtmPvcVccTimeLenIn | 0 | 0 | The time interval over which CIR and the burst sizes (Bc and Be) are measured in the A2B direction. The unit is milliseconds. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.18 | frAtmPvcVccInterWorkingFuncIn | 0 | 0 | InterWorking function. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.19 | frAtmPvcVccTimeLenOut | 0 | 0 | The time interval over which CIR and the burst sizes (Bc and Be) are measured in the A2B direction. The unit is milliseconds. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.20 | frAtmPvcVccInterWorkingFuncOut | 0 | 0 | InterWorking function. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.21 | frAtmPvcVccPeakCellRateA2B | 0 | 0 | Peak cell rate - side A, in cells per second, this will reflect the frame relay parameters in atm terms. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.22 | frAtmPvcVccSusCellRateA2B | 0 | 0 | Sustained cell rate - side A, in cells per second, this will reflect the frame relay parameters in atm terms. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.23 | frAtmPvcVccMaxBurstSizeA2B | 0 | 0 | Maximum burst size - side A, in cells, this will reflect the frame relay parameters in atm terms. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.24 | frAtmPvcVccPeakCellRateB2A | 0 | 0 | Peak cell rate - side B, in cells per second, this will reflect the frame relay parameters in atm terms. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.25 | frAtmPvcVccSusCellRateB2A | 0 | 0 | Sustained cell rate - side B, in cells per second, this will reflect the frame relay parameters in atm terms. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.26 | frAtmPvcVccMaxBurstSizeB2A | 0 | 0 | Maximum burst size - side B, in cells, this will reflect the frame relay parameters in atm terms. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.27 | frAtmPvcVccConnectionStatus | 0 | 0 | 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.7.1.28 | frAtmPvcVccDualHomed | 0 | 0 | Does this PVC need a backup Dual homing PVC. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.29 | frAtmPvcVccOamStatus | 0 | 0 | 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.7.1.30 | frAtmPvcVccViB | 0 | 0 | VI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.7.1.32 | frAtmPvcVccVUNIB | 0 | 0 | VUNI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.7.1.33 | frAtmPvcVccOAMConnEndPtStatus | 0 | 0 | Connection endpoint status. Valid only at connection endpoint. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.34 | frAtmPvcVccOAMSegEndPtStatus | 0 | 0 | Segment endpoint status. Valid only at segment/connection endpoint. |
| 1.3.6.1.4.1.1751.2.18.6.7.1.35 | frAtmPvcVccMfsB2A | 0 | 0 | Maximum Frame Size for GFR traffic |
| 1.3.6.1.4.1.1751.2.18.6.7.1.36 | frAtmPvcVccConnFailureCauseA | 0 | 0 | connestion status reason code |
| 1.3.6.1.4.1.1751.2.18.6.7.1.37 | frAtmPvcVccConnFailureCauseB | 0 | 0 | connection status reason code |
| 1.3.6.1.4.1.1751.2.18.6.7.1.38 | frAtmPvcVccTrafficShapingA2B | 0 | 0 | Traffic Shaping Support in the A2B direction. |