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]
atmPvcVccCnfrmTypeB2A 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 } ::= { atmPvcVccEntry 31 }
atmPvcVccCnfrmTypeB2A 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 } ::= { atmPvcVccEntry 31 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1751.2.18.6.1.1.1 | atmPvcVccIfA | 0 | 0 | Interface index for side A of an ATM-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC… |
| 1.3.6.1.4.1.1751.2.18.6.1.1.2 | atmPvcVccVpiA | 0 | 0 | VPI value for side A of an ATM-to-ATM PVC VCC connection. Valid range is a number between 0 and 4095. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.3 | atmPvcVccVciA | 0 | 0 | VCI value for side A of an ATM-to-ATM PVC VCC connection. Valid range is a number between 0 and 65535. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.4 | atmPvcVccIfB | 0 | 0 | Interface index for side B of an ATM-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC… |
| 1.3.6.1.4.1.1751.2.18.6.1.1.5 | atmPvcVccVpiB | 0 | 0 | VPI value for side B of an ATM-to-ATM PVC VCC connection. Valid range is a number between 0 and 4095. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.6 | atmPvcVccVciB | 0 | 0 | VCI value for side B of an ATM-to-ATM PVC VCC connection. Valid range is a number between 0 and 65535. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.7 | atmPvcVccServiceTypeA2B | 0 | 0 | service type |
| 1.3.6.1.4.1.1751.2.18.6.1.1.8 | atmPvcVccSarTypeA2B | 0 | 0 | SAR type used in atm adaption |
| 1.3.6.1.4.1.1751.2.18.6.1.1.10 | atmPvcVccPeakCellRateA2B | 0 | 0 | peak cell rate - side A, in cell per second |
| 1.3.6.1.4.1.1751.2.18.6.1.1.11 | atmPvcVccSusCellRateA2B | 0 | 0 | sustained rate - side A, in cell per second |
| 1.3.6.1.4.1.1751.2.18.6.1.1.12 | atmPvcVccMaxBurstSizeA2B | 0 | 0 | maximum burst size - side A, in cells |
| 1.3.6.1.4.1.1751.2.18.6.1.1.13 | atmPvcVccServiceTypeB2A | 0 | 0 | service type |
| 1.3.6.1.4.1.1751.2.18.6.1.1.14 | atmPvcVccSarTypeB2A | 0 | 0 | sar type used in atm adaption |
| 1.3.6.1.4.1.1751.2.18.6.1.1.16 | atmPvcVccPeakCellRateB2A | 0 | 0 | peak rate - side B, in cell per second. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.17 | atmPvcVccSusCellRateB2A | 0 | 0 | sustained rate - side B, in cell per second. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.18 | atmPvcVccMaxBurstSizeB2A | 0 | 0 | maximum burst size - side B, in cells. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.20 | atmPvcVccType | 0 | 0 | type of connection |
| 1.3.6.1.4.1.1751.2.18.6.1.1.21 | atmPvcVccFlow | 0 | 0 | type of flow |
| 1.3.6.1.4.1.1751.2.18.6.1.1.22 | atmPvcVccRowStatus | 0 | 0 | row status |
| 1.3.6.1.4.1.1751.2.18.6.1.1.23 | atmPvcVccFrwdErrCorrectionA2B | 0 | 0 | Forward error correction scheme |
| 1.3.6.1.4.1.1751.2.18.6.1.1.24 | atmPvcVccFrwdErrCorrectionB2A | 0 | 0 | Forward error correction scheme |
| 1.3.6.1.4.1.1751.2.18.6.1.1.25 | atmPvcVccConnectionStatus | 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.1.1.26 | atmPvcVccOamStatus | 0 | 0 | Indicates the OAM monitoring status of side A. The 5 possible states are: Unsupp: No monitoring enabled. End-Pt: A side is only … |
| 1.3.6.1.4.1.1751.2.18.6.1.1.27 | atmPvcVccDualHomed | 0 | 0 | Does this PVC need a backup Dual homing PVC. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.28 | atmPvcVccViA | 0 | 0 | VI to associate the Egress part of the B2A connection . |
| 1.3.6.1.4.1.1751.2.18.6.1.1.29 | atmPvcVccViB | 0 | 0 | VI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.1.1.30 | atmPvcVccCnfrmTypeA2B | 0 | 0 | The following is the description of this field This will be used in conjunction with the service type field to get the correct tra… |
| 1.3.6.1.4.1.1751.2.18.6.1.1.32 | atmPvcVccVUNIA | 0 | 0 | VUNI to associate the Egress part of the B2A connection . |
| 1.3.6.1.4.1.1751.2.18.6.1.1.33 | atmPvcVccVUNIB | 0 | 0 | VUNI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.1.1.34 | atmPvcVccOamStatusB | 0 | 0 | Indicates the Oam monitoring status of side B of an internal connection. Refer to ITU I.610 and Bellcore GR1248-CORE for definiti… |
| 1.3.6.1.4.1.1751.2.18.6.1.1.35 | atmPvcVccOAMConnEndPtStatusA | 0 | 0 | Connection endpoint side A status. Valid only at connection endpoint. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.36 | atmPvcVccOAMConnEndPtStatusB | 0 | 0 | Connection endpoint side B status. Valid only at connection endpoint. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.37 | atmPvcVccOAMConnSegEndPtStatusA | 0 | 0 | Segment endpoint side A status. Valid only at segment endpoints. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.38 | atmPvcVccOAMConnSegEndPtStatusB | 0 | 0 | Segment endpoint side B status. Valid only at segment endpoints. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.39 | atmPvcVccMfsA2B | 0 | 0 | Maximum Frame Size for GFR traffic for A2B dir |
| 1.3.6.1.4.1.1751.2.18.6.1.1.40 | atmPvcVccMfsB2A | 0 | 0 | Maximum Frame Size for GFR traffic for B2A dir |
| 1.3.6.1.4.1.1751.2.18.6.1.1.41 | atmPvcVccConnFailureCauseA | 0 | 0 | connestion status reason code |
| 1.3.6.1.4.1.1751.2.18.6.1.1.42 | atmPvcVccConnFailureCauseB | 0 | 0 | connection status reason code |
| 1.3.6.1.4.1.1751.2.18.6.1.1.43 | atmPvcVccTrafficShapingA2B | 0 | 0 | Traffic Shaping Support in the A2B direction. |
| 1.3.6.1.4.1.1751.2.18.6.1.1.44 | atmPvcVccTrafficShapingB2A | 0 | 0 | Traffic Shaping Support in the B2A direction. |