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]
atmSvcVccCnfrmTypeA2B 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 } ::= { atmSvcVccEntry 24 }
atmSvcVccCnfrmTypeA2B 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 } ::= { atmSvcVccEntry 24 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1751.2.18.6.3.1.1 | atmSvcVccIfA | 0 | 0 | interface index (slot/port/channel) SSPPCCC |
| 1.3.6.1.4.1.1751.2.18.6.3.1.2 | atmSvcVccVpiA | 0 | 0 | atm path identifier - side A |
| 1.3.6.1.4.1.1751.2.18.6.3.1.3 | atmSvcVccVciA | 0 | 0 | atm channel identifier - side A |
| 1.3.6.1.4.1.1751.2.18.6.3.1.4 | atmSvcVccIfB | 0 | 0 | interface index (slot/port/channel) SSPPCCC |
| 1.3.6.1.4.1.1751.2.18.6.3.1.5 | atmSvcVccVpiB | 0 | 0 | atm path identifier - side B |
| 1.3.6.1.4.1.1751.2.18.6.3.1.6 | atmSvcVccVciB | 0 | 0 | atm channel identifier - side B |
| 1.3.6.1.4.1.1751.2.18.6.3.1.7 | atmSvcVccServiceTypeA2B | 0 | 0 | service type |
| 1.3.6.1.4.1.1751.2.18.6.3.1.8 | atmSvcVccSarTypeA2B | 0 | 0 | sar type - A to B direction |
| 1.3.6.1.4.1.1751.2.18.6.3.1.10 | atmSvcVccPeakCellRateA2B | 0 | 0 | peak rate - side A |
| 1.3.6.1.4.1.1751.2.18.6.3.1.11 | atmSvcVccSusCellRateA2B | 0 | 0 | sustained rate - side A |
| 1.3.6.1.4.1.1751.2.18.6.3.1.12 | atmSvcVccMaxBurstSizeA2B | 0 | 0 | maximum burst size - side A |
| 1.3.6.1.4.1.1751.2.18.6.3.1.13 | atmSvcVccServiceTypeB2A | 0 | 0 | service type |
| 1.3.6.1.4.1.1751.2.18.6.3.1.14 | atmSvcVccSarTypeB2A | 0 | 0 | sar type - B to A direction |
| 1.3.6.1.4.1.1751.2.18.6.3.1.16 | atmSvcVccPeakCellRateB2A | 0 | 0 | peak rate - side B |
| 1.3.6.1.4.1.1751.2.18.6.3.1.17 | atmSvcVccSusCellRateB2A | 0 | 0 | sustained rate - side B |
| 1.3.6.1.4.1.1751.2.18.6.3.1.18 | atmSvcVccMaxBurstSizeB2A | 0 | 0 | maximum burst size - side B |
| 1.3.6.1.4.1.1751.2.18.6.3.1.19 | atmSvcVccFlow | 0 | 0 | flow type |
| 1.3.6.1.4.1.1751.2.18.6.3.1.20 | atmSvcVccType | 0 | 0 | type of connection |
| 1.3.6.1.4.1.1751.2.18.6.3.1.21 | atmSvcVccConnectionStatus | 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.3.1.22 | atmSvcVccViA | 0 | 0 | VI to associate the Egress part of the B2A connection . |
| 1.3.6.1.4.1.1751.2.18.6.3.1.23 | atmSvcVccViB | 0 | 0 | VI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.3.1.25 | atmSvcVccCnfrmTypeB2A | 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.3.1.26 | atmSvcVccVUNIA | 0 | 0 | VUNI to associate the Egress part of the B2A connection . |
| 1.3.6.1.4.1.1751.2.18.6.3.1.27 | atmSvcVccVUNIB | 0 | 0 | VUNI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.3.1.28 | atmSvcVccTrafficShapingA2B | 0 | 0 | Traffic Shaping Support in the A2B direction. |
| 1.3.6.1.4.1.1751.2.18.6.3.1.29 | atmSvcVccTrafficShapingB2A | 0 | 0 | Traffic Shaping Support in the B2A direction. |