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]
aal2TrunkConfigCnfrmTypeB2A 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 } ::= { aal2TrunkConfigEntry 15 }
aal2TrunkConfigCnfrmTypeB2A 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 } ::= { aal2TrunkConfigEntry 15 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1751.2.18.6.36.1.1 | aal2TrunkConfigIf | 0 | 0 | Interface Id of the Atm Side of the Aal2 Trunk. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.2 | aal2TrunkConfigVpi | 0 | 0 | VPI value for Atm side , the atm side, of a atm trunk connection. Valid range is a number between 0 and 4095. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.3 | aal2TrunkConfigVci | 0 | 0 | VCI value for 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.36.1.4 | aal2TrunkConfigServiceType | 0 | 0 | service type |
| 1.3.6.1.4.1.1751.2.18.6.36.1.5 | aal2TrunkConfigPeakCellRateIgr | 0 | 0 | peak cell rate - atm side inp, in cell per second |
| 1.3.6.1.4.1.1751.2.18.6.36.1.6 | aal2TrunkConfigSusCellRateIgr | 0 | 0 | sustained rate - atm side inp, in cell per second |
| 1.3.6.1.4.1.1751.2.18.6.36.1.7 | aal2TrunkConfigMaxBurstSizeIgr | 0 | 0 | maximum burst size - atm side inp, in cells |
| 1.3.6.1.4.1.1751.2.18.6.36.1.8 | aal2TrunkConfigPeakCellRateEgr | 0 | 0 | peak rate - atm side output, in cell per second. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.9 | aal2TrunkConfigSusCellRateEgr | 0 | 0 | sustained rate - atm side output,in cell per second. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.10 | aal2TrunkConfigMaxBurstSizeEgr | 0 | 0 | maximum burst size - atm side output, in cells. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.11 | aal2TrunkConfigFlow | 0 | 0 | Flow type |
| 1.3.6.1.4.1.1751.2.18.6.36.1.12 | aal2TrunkConfigRowStatus | 0 | 0 | row status |
| 1.3.6.1.4.1.1751.2.18.6.36.1.13 | aal2TrunkConfigConnectionStatus | 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.36.1.14 | aal2TrunkConfigViB | 0 | 0 | VI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.36.1.16 | aal2TrunkConfigVUNIB | 0 | 0 | VUNI to associate the Egress part of the A2B connection . |
| 1.3.6.1.4.1.1751.2.18.6.36.1.17 | aal2TrunkAvailBwIgr | 0 | 0 | The Avail Bandwidth for that interface in cells per sec. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.18 | aal2TrunkAvailBwEgr | 0 | 0 | The Avail Bandwidth for that interface in cells per sec. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.19 | aal2TrunkGR303 | 0 | 0 | This flag is used to check if a GR303 Feature is enabled for the trunk. |
| 1.3.6.1.4.1.1751.2.18.6.36.1.20 | aal2TrunkConfigOamStatus | 0 | 0 | Indicates the OAM monitoring status of side A. The 2 possible states are: Unsupp: No monitoring enabled. End-Pt: Atm side is onl… |
| 1.3.6.1.4.1.1751.2.18.6.36.1.21 | aal2TrunkConnFailureCauseB | 0 | 0 | connection status reason code |
| 1.3.6.1.4.1.1751.2.18.6.36.1.22 | aal2TrunkCuTimer | 0 | 0 | CuTimer represents 'combined use timer', is set to zero such that every ATM cell transmitted contains one, and only one, AAL2 pack… |