Nortel-MsCarrier-MscPassport-AtmCoreMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of mscAtmIf components.

A single entry in the table represents a single mscAtmIf component.

This variable is used as the basis for SNMP naming of mscAtmIf components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIf tables.

This variable represents the index for the mscAtmIf tables.

This entry controls the addition and deletion of mscAtmIfConnMap components.

A single entry in the table represents a single mscAtmIfConnMap component.

This variable is used as the basis for SNMP naming of mscAtmIfConnMap components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfConnMap tables.

This variable represents the index for the mscAtmIfConnMap tables.

This group is obsolete. Please refer to the Override component below for the current provisioning group This group contains provisionable attributes which specify the VCC space to be supported by an ATM interface. The VCC space consists of an optional 'VPI Zero VCC Space' and an optional 'Programmable VCC Space'. The VPI Zero VCC Space is used to support VCCs with a VPI of zero. The VCI values supported in this space range from 0 to a provisioned maximum. The size of the VPI Zero VCC Space must either be 0 or a multiple of 256. A value of 0 implies that no programmable VCCs can be used. In this case atmNumberOfNonZeroVpisForVccs_m must also be 0. The optional Programmable VCC Space is used to support VCCs with a VPI other than zero. The VPI values supported in this space must lie in a single contiguous range which excludes VPI 0. The VCI values supported in this space range from 0 to a provisioned maximum. The size of the Programmable VCC Space (should it exist) must adhere to the following rules: If (firstNonZeroVpiForVccs = 1) THEN (numNonZeroVpisForVccs + 1) * numVccsPerNonZeroVpi must be a multiple of 256 OTHERWISE numNonZeroVpisForVccs * numVccsPerNonZeroVpi must be a multiple of 256 If the AtmIf is linked to a LogicalProcessor with a cardType of 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm or 2pJ6MAtm, the size of the entire VCC space (both mandatory and optional parts) and VPC space must not exceed the capacity of the port to which the interface is linked, which is defined in the Arc component's totalConnectionPoolCapacity or connectionPoolCapacity attribute (whichever is non-zero). When using the totalConnectionPoolCapacity attribute, the capacity of the port is (totalConnectionPoolCapacity divided by the number of physical ports). The number of connection identifiers in the VCC and VPC space can be determined as follows: IF (numNonZeroVpisForVccs = 0) THEN number of connection ids = 256 + numVccsForVpiZero OTHERWISE IF (firstNonZeroVpiForVccs = 1) THEN number of connection ids = 256 + numVccsForVpiZero + (numNonZeroVpisForVccs + 1) * numVccsPerNonZeroVpi OTHERWISE number of connection ids = 256 + numVccsForVpiZero + (numNonZeroVpisForVccs * numVccsPerNonZeroVpi)

An entry in the mscAtmIfConnMapVccProvTable.

This attribute is obsolete. Please refer to the Override component for the new attribute. This attribute specifies the number of VCCs supported for the VPI Zero VCC Space. The VCI values of these VCCs range from 0 to (numVccsForVpiZero - 1). The size of the VPI Zero VCC Space must either be 0 or a multiple of 256. A value of 0 implies that no programmable VCCs can be used. In this case atmNumberOfNonZeroVpisForVccs_m must also be 0. The VCC Space as a whole must adhere to the guidelines laid down in the description of the AtmConnMappingVccProv group.

This attribute is obsolete. Please refer to the Override component for the new attribute. This attribute specifies the number of conti guous VPIs supported in the optional Programmable VCC Space. If numNonZeroVpisForVccs is 0 the Programmable VCC Space does not exist. If numNonZeroVpisForVccs is greater than 0 the Programmable VCC Space exists and covers the VPI values ranging from firstNonZeroVpiForVccs to (firstNonZeroVpiForVccs + numNonZeroVpisForVccs - 1). The VCC Space as a whole must adhere to the guidelines laid down in the description of the AtmConnMappingVccProv group.

This attribute is obsolete. Please refer to the Override component for the new attribute. This attribute specifies the initial VPI of the optional Programmable VCC Space. If numNonZeroVpisForVccs is 0 the Programmable VCC Space does not exist. If numNonZeroVpisForVccs is greater than 0 the Programmable VCC Space exists and covers the VPI values ranging from firstNonZeroVpiForVccs to (firstNonZeroVpiForVccs + numNonZeroVpisForVccs - 1). The initial VPI of the Programmable VCC Space must either be 1 or a non-zero multiple of 16. The VCC Space as a whole must adhere to the guidelines laid down in the description of the AtmConnMappingVccProv group.

This attribute is obsolete. Please refer to the Override component for the new attribute. This attribute specifies the number of VCCs supported for each VPI in the Programmable VCC Space. The VCI values of these VCCs range from 0 to (numVccsPerNonZeroVpi - 1) for each VPI in this space. The size of the Programmable VCC Space must be a power of 2. The VCC Space as a whole must adhere to the guidelines laid down in the description of the AtmConnMappingVccProv group.

This group contains operational attributes which specify the VCC space to be supported by an ATM interface. The VCC space consists of an optional 'VPI Zero VCC Space' and an optional 'Programmable VCC Space'. The VPI Zero VCC Space is used to support VCCs with a VPI of zero. The VCI values supported in this space range from 0 to an optionally provisioned maximum of numVccsForVpiZero. The size of the VPI Zero VCC Space is either 0 or a multiple of 256. A value of 0 implies that not only can no VCCs be provisioned in the VPI Zero VCC Space but no Programmable VCCs can be used. In this case numNonZeroVpisForVccs will also be 0. The optional Programmable VCC Space supports VCCs with a VPI other than zero. The VPI values supported in this space lie in a single contiguous range which excludes VPI 0. The VCI values supported in this space range from 0 to an optionally provisioned maximum. The number of connection identifier resources in the VCC and VPC space (not all of which are available for user connections) is the value reported in the Lp/n Eng Arc totalConnectionPoolAvailable attribute divided by the number of physical ports on the card, and can be determined as follows: IF (numNonZeroVpisForVccs = 0) THEN number of connection ID resources = 256 + numVccsForVpiZero OTHERWISE IF (firstNonZeroVpiForVccs = 1) THEN number of connection ID resources = 256 + numVccsForVpiZero + (numNonZeroVpisForVccs + 1) * numVccsPerNonZeroVpi OTHERWISE number of connection ID resources = 256 + numVccsForVpiZero + (numNonZeroVpisForVccs * numVccsPerNonZeroVpi)

An entry in the mscAtmIfConnMapOperTable.

This attribute indicates the number of VCCs supported for the VPI Zero VCC Space. The VCI values of these VCCs range from 0 to (numVccsForVpiZero - 1). For Apc-based cards, the maximum value is 16384. For CQC-based cards, the maximum value is 16128. To override the system default, see the AtmIf ConnMap Ov attribute numVccsForVpiZero.

This attribute indicates the number of contiguous VPIs supported in the optional Programmable VCC Space. If numNonZeroVpisForVccs is 0 the Programmable VCC Space does not exist. If numNonZeroVpisForVccs is greater than 0 the Programmable VCC Space exists and covers the VPI values ranging from firstNonZeroVpiForVccs to (firstNonZeroVpiForVccs + numNonZeroVpisForVccs - 1). For Apc-based cards, the maximum value of this attribute is 255 for UNI applications and 4095 for NNI applications. For CQC-based cards, the maximum value is 255. To override the system default, see the AtmIf ConnMap Ov attribute numNonZeroVpisForVccs.

This attribute indicates the initial VPI of the optional Programmable VCC Space. If numNonZeroVpisForVccs is 0 the Programmable VCC Space does not exist. If numNonZeroVpisForVccs is greater than 0 the Programmable VCC Space exists and covers the VPI values ranging from firstNonZeroVpiForVccs to (firstNonZeroVpiForVccs + numNonZeroVpisForVccs - 1). For Apc-based cards, the maximum value of this attribute is 255 for UNI applications and 4095 for NNI applications. For CQC-based cards, the maximum value is 240. To override the system default, see the AtmIf ConnMap Ov attribute firstNonZeroVpiForVccs.

This attribute indicates the number of VCCs supported for each VPI in the Programmable VCC Space. The VCI values of these VCCs range from 0 to (numVccsPerNonZeroVpi - 1) for each VPI in this space. For Apc-based cards, the maximum value is 16384. For CQC-based cards, the maximum value is 2048). To override the system default, see the AtmIf ConnMap Ov attribute numVccsPerNonZeroVpi.

This entry controls the addition and deletion of mscAtmIfConnMapOv components.

A single entry in the table represents a single mscAtmIfConnMapOv component.

This variable is used as the basis for SNMP naming of mscAtmIfConnMapOv components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfConnMapOv tables.

This variable represents the index for the mscAtmIfConnMapOv tables.

This group contains provisionable attributes which specify the VCC space to be supported by this ATM interface. The VCC space consists of an optional 'VPI Zero VCC Space' and an optional 'Programmable VCC Space'. If not specified otherwise, the semantic checks described below are applicable only for the CQC- based cards. The VPI Zero VCC Space is used to support VCCs with a VPI of zero. The VCI values supported in this space range from 0 to a provisioned maximum. The size of the VPI Zero VCC Space must either be 0 or a multiple of 256. A value of 0 implies that no programmable VCCs can be used. In this case numNonZeroVpisForVccs must also be 0. The optional Programmable VCC Space is used to support VCCs with a VPI other than zero. The VPI values supported in this space must lie in a single contiguous range which excludes VPI 0. The VCI values supported in this space range from 0 to a provisioned maximum. The size of the Programmable VCC Space (should it exist) must adhere to the following rules: If (firstNonZeroVpiForVccs = 1) THEN (numNonZeroVpisForVccs + 1) * numVccsPerNonZeroVpi must be a multiple of 256 OTHERWISE numNonZeroVpisForVccs * numVccsPerNonZeroVpi must be a multiple of 256 The number of connection identifier resources in the VCC and VPC space can be determined as follows: The number of connection identifier resources in the VCC and VPC space (not all of which are available for user connections) is reported in the Lp/n Eng Arc totalConnectionPoolAvailable attribute, and can be determined as follows: IF (numNonZeroVpisForVccs = 0) THEN number of connection ID resources = 256 + numVccsForVpiZero OTHERWISE IF (firstNonZeroVpiForVccs = 1) THEN number of connection ID resources = 256 + numVccsForVpiZero + (numNonZeroVpisForVccs + 1) * numVccsPerNonZeroVpi OTHERWISE number of connection ID resources = 256 + numVccsForVpiZero + (numNonZeroVpisForVccs * numVccsPerNonZeroVpi) The number of connection identifier resources must not exceed the capacity of the port to which the interface is linked. If the Lp has an Eng Arc Cqc Ov component provisioned with a non-zero connectionPoolCapacity the port's capacity is specified by this attribute. Otherwise the port's capacity is indicated by the Lp/n Eng Arc totalConnectionPoolAvailable divided by the number of physical ports on the card.

An entry in the mscAtmIfConnMapOvProvTable.

For Apc-based cards, the maximum value of this attribute is 16384, and the default value is 1024. The allowed values are either 1 or powers of 2. For CQC-based cards the following constraints apply: The maximum value is 16128, and the default is 768. This attribute specifies the number of VCCs supported for the VPI Zero VCC Space. The VCI values of these VCCs range from 0 to (numVccsForVpiZero - 1). The size of the VPI Zero VCC Space must either be 0 or a multiple of 256. A value of 0 implies that no programmable VCCs can be used. In this case numNonZeroVpisForVccs must also be 0. The values of all attributes provisioned in this group must adhere to the guidelines laid down in the description of the Provisioned group.

This attribute specifies the number of contiguous VPIs supported in the optional Programmable VCC Space. For Apc-based cards, the maximum value of this attribute is 255 for UNI applications and 4095 for NNI applications. For CQC-based cards the following constraints apply: The maximum value is 255. If numNonZeroVpisForVccs is 0 the Programmable VCC Space does not exist. If numNonZeroVpisForVccs is greater than 0 the Programmable VCC Space exists and covers the VPI values ranging from firstNonZeroVpiForVccs to (firstNonZeroVpiForVccs + numNonZeroVpisForVccs - 1). The values of all attributes provisioned in this group must adhere to the guidelines laid down in the description of the Provisioned group.

This attribute specifies the initial VPI of the optional Programmable VCC Space. If numNonZeroVpisForVccs is 0 then the Programmable VCC Space does not exist and the value of this attribute is ignored. If numNonZeroVpisForVccs is greater than 0 the Programmable VCC Space exists and covers the VPI values ranging from firstNonZeroVpiForVccs to (firstNonZeroVpiForVccs + numNonZeroVpisForVccs - 1). For Apc-based cards, this value can be any integer number between 1 and 255 for UNI applications and between 1 and 4095 for NNI applications. For CQC-based cards the initial VPI of the Programmable VCC Space must be no greater than 240, and either 1 or a non-zero multiple of 16. The values of all attributes provisioned in this group must adhere to the guidelines laid down in the description of the Provisioned group.

This attribute specifies the number of VCCs supported for each VPI in the Programmable VCC Space. The VCI values of these VCCs range from 0 to (numVccsPerNonZeroVpi - 1) for each VPI in this space. For Apc-based cards, the maximum value of this attribute is 16384. For CQC-based cards, the maximum value is 2048. The values of all attributes provisioned in this group must adhere to the guidelines laid down in the description of the Provisioned group.

This entry controls the addition and deletion of mscAtmIfCA components.

A single entry in the table represents a single mscAtmIfCA component.

This variable is used as the basis for SNMP naming of mscAtmIfCA components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfCA tables.

This variable represents the index for the mscAtmIfCA tables.

This entry controls the addition and deletion of mscAtmIfCACbr components.

A single entry in the table represents a single mscAtmIfCACbr component.

This variable is used as the basis for SNMP naming of mscAtmIfCACbr components. These components can be added.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfCACbr tables.

This variable represents the index for the mscAtmIfCACbr tables.

This group contains provisioned attributes which control the CBR service category for this interface.

An entry in the mscAtmIfCACbrProvTable.

This attribute specifies the bandwidth pool which is to be used to support the constant bit rate (CBR) service category except for connections managed by a Vpt CA. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to CBR traffic. The percentage allocated to each bandwidth pool can be provisioned through the bandwidthPool attribute under the CA. Enumeration: 'pool3': 3, 'pool2': 2, 'pool1': 1, 'pool5': 5, 'pool4': 4.

This attribute specifies the default cell delay variation tolerance (CDVT) for all connections of the CBR service category except those managed by a Vpt CA. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. This attribute is used by the CAC function to compute the equivalent cell rate (ECR) required by a given CBR connection. The larger the value of CDVT, the larger is its ECR. If Usage Parameter Control (UPC) is enabled for a connection, CDVT is used by the UPC function to decide whether a cell is conforming or non-conforming based on the connection's traffic descriptor type. The larger the CDVT value, the more tolerant is the UPC of bandwidth usage beyond the traffic contract.

This attribute specifies the peak-to-peak cell delay variation (CDV) which is contributed to the entire ATM Interface for CBR traffic. The CDV is a measure of the delay jitter introduced mostly by traffic buffering and cell scheduling. The worst case value of this attribute can be computed as the txQueueLimit divided by the link rate of this ATM Interface. The value of this attribute is used by PNNI in the Resource Availability Information Group (RAIG) topology updates and route selection. It is also used by CAC at connection set-up time to determine whether this ATM Interface can meet the CDV requirements of the connection. If so, the value of this attribute is added to the cumulative CDV field of the extended QoS information element.

This attribute specifies the maximum cell transfer delay (MaxCTD) which is applied to the entire ATM Interface for CBR traffic. MaxCTD is the sum of the fixed delay and the CDV. The components of the fixed delay include propagation delay through the physical media, delays induced by the transmission system, and fixed components of switch processing delay. This attribute is used by PNNI in the Resource Availability Information Group (RAIG) topology updates and route selection. It is also used by CAC at connection set-up time to determine whether this ATM Interface can meet the ATM connection's MaxCTD requirement.

This attribute specifies the tolerable cell loss ratio (CLR) for CBR traffic except for connections managed by a Vpt CA. The number is the negative logarithm (base 10) of the CLR. For example, if the target CLR = 1E-10 then Cbr cellLossRatio = 10. This number must be the same as the RtVbr cellLossRatio since CBR and rt-VBR traffic have the same discard priority. The Cbr cellLossRatio is used by the Connection Admission Control (CAC) algorithm to compute the required (equivalent) cell rate for CBR connections. There is a trade-off between the service category CLR and the achievable link utilization. To guarantee an excellent service category, the CLR should be as small as possible (e.g., 1E-10). However, a smaller CLR results in a larger equivalent cell rate for a given connection and hence a lower link utilization. Setting this attribute to 0 means that a CLR of 1 can be tolerated. In this case, no bandwidth is reserved for CBR connections, and CAC is effectively turned off. All CBR connections are admitted.

This attribute specifies the default maximum queue length for the emission queues used to buffer the traffic of the CBR service category. It is used as the basis for setting the discard thresholds on both common and per-VC queues. For the common queue, the discard thresholds are set at approximately 35, 75, and 90 percent of the value of this attribute for traffic at discard priority 3 (DP=3), DP=2 and DP=1 respectively. For a per-VC queue, the actual limit may be reduced depending on the shaping rate of the connection (for standard Vpt Vccs, this is the shaping rate of the Vpt). The discard thresholds are set at approximately 35, 75 and 90 percent of the scaled queue limit for traffic at discard priority 3 (DP=3), DP=2 and DP=1 respectively. However, a reduction will never result in a value that is less than the value set for the minPerVcQueueLimit attribute. CQC-based ATM cards and 1pOC12SmLrAtm cards do not support per-VC queues at the CBR service category. When this attribute is set to autoConfigure, an appropriate value is selected based on the card type. It is set to 96 for all Passport ATM cards (DS1, E1, IMA, JT2, DS3, E3, OC3, both CQC- and ATM IP- based), except 1pOC12SmLrAtm. For the 1pOC12SmLrAtm card, the value is set to 350. For ATM IP FPs, the per-VC queue limit may be overridden for a permanent connection by specifying a value in the Vcd Tm or Vpd Tm txQueueLimit attribute. For CQC-based ATM cards, the valid range for this attribute is from 5 to 30000 inclusive. The operational value of the maximum length of a queue (common or per-VC) is indicated by the Vcc Tm, Vpc Tm, or Vpt Tm txQueueThresholds attribute. For standard Vpts, this attribute does not apply when using per-VC queuing and only applies when using common queueing. When using per-VC queueing, regardless of the Vpt's service category, standard Vpts use the AtmIf Ca NrtVbr txQueueLimit value as their default. This attribute does not apply to basic Vpts. VALUES ( 0 = autoConfigure )

This attribute specifies the holding priority which applies to SVP and SVC CBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the default holding priority which applies to SVC CBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute has been obsoleted and its value migrated to holdingPriority attribute. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the default holding priority which applies to SVC CBR point-to-multipoint connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the minimum queue limit for the per-VC queues of connections of the CBR service category. This attribute is ignored on CQC-based ATM cards, 1pOC48SmSrAtm, and 1pOC12SmLrAtm cards, because they do not support per-VC queues at the CBR service category. The queue limit of a per-VC queue is obtained by scaling down the txQueueLimit based on the shaping rate of that queue (shaping rate for the connection, and for standard Vpt Vccs, the shaping rate of the Vpt). This produces a constant delay for various queue lengths. The txQueueLimit provides an upper bound while minPerVcQueueLimit provides the lower bound. The value of this attribute must not be greater than the value of the txQueueLimit attribute. If this service category is used by Trunks the value of minPerVcQueueLimit must be at least 88. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr minPerVcQueueLimit value as their default. To determine the queue limit of a standard Vpt Vcc, the txQueueLimit is scaled down by the Vpt shaping rate.

This attribute specifies the shaping rate to be used in computing the tolerable delay for per-VC queues of connections of the CBR service category. The delay is computed as the txQueueLimit divided by the value of this attribute. This attribute is ignored on CQC-based ATM cards and 1pOC12SmLrAtm cards, because they do not support per-VC queues at the CBR service category. When the value of this attribute is autoConfigure, an appropriate default is selected based on the card type. It is set to 80000 for all cards which support per-VC queuing at the CBR service category (3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2, 2pOC3MmAtm2). For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, the reference rate is set to 65511 for DS3 and OC3 channels, and set to 262044 for OC12 channels. For Apc-based cards the maximum value is 1416905. For all other cards, the maximum value is 943396. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr perVcQueueLimitReferenceRate value as their default. VALUES ( 0 = autoConfigure )

This attribute is not applicable and is ignored for CQC-based ATM cards. This attribute specifies the emission priority (EP) which is used to transmit traffic of the CBR service category. A lower numerical value for this attribute specifies a higher emission priority. 0 is the highest EP and 7 is the lowest. Cells at a higher emission priority receive higher preference for link bandwidth. EPs 0 and 1 are in the absolute priority range, and are unaffected by any minimum bandwidth guarantees. EPs 2 through 7 are in the guaranteed bandwidth range. Minimum bandwidth guarantee is specified in the AtmIf/n Ep/m component. Emission priority setting must comply with all of the following constraints: 1. The emission priority numbers must be in the following order: CBR <= rt-VBR <= nrt-VBR <= ABR <= UBR 2. Two different ATM service categories may share the same EP only if they are both shaped. 3. CBR and rt-VBR may be placed either in the absolute priority range (EP 0 or 1) or in the guaranteed bandwidth range (EP 2 through 7). 4. If both CBR and rt-VBR are shaped, rt-VBR must share the same EP with CBR or ABR. If either one of CBR or rt-VBR are not shaped, then they cannot share the same EP. 5. ABR service category is always deemed to be shaped. If nrt-VBR is shaped, it must share the same EP with ABR. If nrt-VBR is not shaped it must have a higher EP than ABR. 6. If UBR is shaped, it must share the same EP with ABR. If UBR is not shaped, it must have a lower EP than ABR. This attribute does not apply to basic Vpts, and standard Vpt Vccs.

This attribute specifies the default traffic shaping option for connections of the CBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to disabled, traffic shaping cannot be enabled for any CBR connections. For CQC-based ATM FPs and 1pOC12SmLrAtm FPs, this attribute must be set to disabled. Traffic shaping is not supported for CBR connections on CQC-based ATM FPs. If the Vcc Tm, Vpc Tm, or Vpt Tm, txTrafficDescType indicates type 1 or 2, this attribute is ignored, and traffic shaping is not applicable for that connection. When this attribute is set to inverseUpc, traffic shaping for a connection is enabled according to the value of the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, inverseUpc shaping is not available. If this attribute is set to inverseUpc, and the txTrafficDescType is 3, 4, or 5, linear traffic shaping is enabled. Linear traffic shaping uses a single static traffic shaping rate. If this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, inverse-UPC (also referred to as VBR or dual leaky bucket) traffic shaping is enabled. Inverse-UPC traffic shaping can burst above the sustained cell rate to the peak cell rate for the duration defined by maximum burst size. Inverse-UPC traffic shaping exactly conforms to the requirements of a dual leaky bucket UPC enforcer. When this attribute is set to enabled and the txTrafficDescType is 3, 4, 5, 6, 7, or 8, traffic shaping for a connection is enabled using linear shaping. Enabling or disabling traffic shaping may require a matching change to the emissionPriority attribute and unshapedTransmitQueueing attribute for this service category. Refer to those attributes for the complete description of the interactions. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'inverseUpc': 6, 'enabled': 5.

This attribute specifies the shaping recoup policy for the CBR service category. This is the policy which is used to recoup shaping opportunities which are lost when more than one connection schedules a cell for the same transmit opportunity. In this case, one connection is scheduled, and the cell from the other connection is delayed by one cell time. This attribute affects how the transmit time is calculated for the next cell on the delayed connection. This attribute is ignored if this service category is not shaped. When the connection which was delayed schedules the next cell to transmit, it may calculate the time as a difference from either the previous actual cell transmit time, or the time when the previous cell should have been transmitted. Setting this attribute to maximumEfficiency results in each connection trying to recoup or regain any delays in scheduling. The transmit time from the next cell is calculated from the time when the cell should originally have been sent. Cell delay variation (CDV) occurs in this case since the cells are sent with less than the shaping delay between them. However, in general the shaper recovers (recoups) lost opportunities and improves efficiency. Setting this attribute to minimumCdv results in connections not trying to recoup or regain any delays in scheduling. The transmit time for the next cell is calculated from the time when the previous cell was actually transmitted. This minimizes CDV, but results in missed cell opportunities. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'maximumEfficiency': 1, 'minimumCdv': 0.

This attribute specifies the default queuing option for unshaped connections of the CBR service category. On ATM IP cards, this attribute controls whether common or per-VC queueing is used. Per-VC queueing means that each connection has its own buffering and queue limits. Common queueing means that cells are queued in First In First Out order on a common queue for this service category. The common queue has one set of congestion control levels for all cells enqueued on it. For 1pOC12SmLrAtm cards this attribute must be set to common or autoConfigure. This attribute cannot be set to perVc since perVc queueing is not available on the 1pOC12SmLrAtm card. The value autoConfigure is interpreted to mean common queueing. For CQC-based ATM cards, this attribute must be set to common. CQC-based ATM cards do not support per-VC queueing for the CBR service category. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards only perVc queueing is supported. All other attribute values are ignored. For ATM IP cards, if traffic shaping for this service category is not disabled, this attribute must be set to perVc. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'perVc': 0, 'common': 1.

This attribute specifies the default policy which is applied when calculating the fairness weight for unshaped connections of the CBR service category. The fairness weight for a connection determines the relative amount of bandwidth which that connection obtains, compared to other connections in the same service category. Connections with equal weight get equal transmit opportunities. Connections with higher weights get more transmit opportunities compared with connections that have lower weights. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The fairness weight for a connection is directly proportional to the value of one of the traffic descriptor parameters for that connection. This attribute specifies which traffic descriptor parameter is used for connections of the CBR service category. This attribute is ignored on CQC-based ATM cards. This attribute is also ignored on ATM IP cards if unshapedTransmitQueueing is set for common queuing. If this attribute is set to scr, the fairness weight is proportional to the transmit sustained cell rate (SCR) of a connection. Connections with a higher SCR have a higher fairness weight. For connections with txTrafficDescType 3, which have no SCR, the sustained cell rate is assumed to be equal to the peak cell rate. If this attribute is set to pcr, the fairness weight is proportional to the transmit peak cell rate (PCR) of a connection. Connections with a higher PCR have a higher fairness weight. Connections with txTrafficDescType 1 or 2 get a minimum weight, which is 1. If this attribute is set to ecr, the fairness weight is proportional to the equivalent cell rate (ECR) of a connection as calculated by connection admission control (CAC). Connections with a higher ECR have a higher fairness weight. Connections with an ECR of 0 get a minimum weight, which is 1. The weight of a connection is visible in the Vcc Tm, Vpc Tm, or Vpt Tm weight attribute. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'pcr': 2, 'ecr': 3, 'scr': 1.

This attribute specifies the default of whether to force tagging (CLP=1) of all cells for all CBR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. This attribute is not supported by 4pOC12SmIrAtm and 4pOC12SmLrAtm cards. When this attribute is set to enabled, CLP is set to 1 for all cells in the transmit direction. Force tagging is only supported on ATM IP FPs. On CQC-based ATM FPs, this attribute must be set to disabled. When this attribute is set to disabled, CLP is unchanged for all cells in the transmit direction. This attribute never applies to any type of Vpt. Enumeration: 'disabled': 1, 'enabled': 0.

This attribute specifies the default usage parameter control (UPC) option for connections of the CBR service category. This attribute is ignored if the rxTrafficDescriptorType indicates 1 or 2. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to enforced, UPC is enforced by default for each connection. When UPC is enforced, non-conforming cells are either tagged or discarded depending on the rxTrafficDescriptorType. On ATM IP FPs, when this attribute is set to monitored, UPC conformance checking is performed, except, instead of the non- conforming cells being tagged or discarded, they are merely counted in the UPC violations counts, and passed on unchanged. On CQC-based ATM FPs, when this attribute is set to monitored, it has the same effect as setting it to disabled. When this attribute is set to disabled, UPC is disabled on the receive path for all CBR connections. This attribute never applies to any type of Vpt. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4.

This group contains operational attributes for the CBR service category.

An entry in the mscAtmIfCACbrOperTable.

This attribute indicates the Early Packet Discard (EPD) offset which is currently in use for this service category. The EPD offset is used to derive the EPD thresholds for each CC level. Any connection under this service category which requires the txPacketWiseDiscard feature must specify a transmit queue limit which is at least 5.71 times this offset. This ensures that the derived Epd threshold will never be less than 17.5 % of the transmit queue limit. If this is not done, txPacketWiseDiscard for the connection will be automatically disabled. The value of this EPD offset is specified under the lp/x eng arc aqm ov component.

This entry controls the addition and deletion of mscAtmIfCARtVbr components.

A single entry in the table represents a single mscAtmIfCARtVbr component.

This variable is used as the basis for SNMP naming of mscAtmIfCARtVbr components. These components can be added.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfCARtVbr tables.

This variable represents the index for the mscAtmIfCARtVbr tables.

This group contains provisioned attributes which control the rt-VBR service category for this interface.

An entry in the mscAtmIfCARtVbrProvTable.

This attribute specifies the bandwidth pool which is to be used to support the real-time variable bit rate (rt-VBR) service category except for connections managed by a Vpt CA. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to rt-VBR traffic. The percentage allocated to each bandwidth pool can be provisioned through the bandwidthPool attribute under the CA. Enumeration: 'pool3': 3, 'pool2': 2, 'pool1': 1, 'pool5': 5, 'pool4': 4.

This attribute specifies the default cell delay variation tolerance (CDVT) for all connections of the rt-VBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. If Usage Parameter Control (UPC) is enabled for a connection, CDVT is used by the UPC function to decide whether a cell is conforming or non-conforming based on the connection's traffic descriptor type. The larger the CDVT value, the more tolerant is the UPC to bandwidth usage beyond the traffic contract.

This attribute specifies the peak-to-peak cell delay variation (CDV) which is contributed to the entire ATM Interface for rt-VBR traffic. The CDV is a measure of the delay jitter introduced mostly by traffic buffering and cell scheduling. The worst case value of this attribute can be computed as the txQueueLimit divided by the link rate of this ATM Interface. The value of this attribute is used by PNNI in the Resource Availability Information Group (RAIG) topology updates and route selection. It is also used by CAC at connection set-up time to determine whether this ATM Interface can meet the CDV requirement for that connection. If so, the value of this attribute is added to the cumulative CDV field of the extended QoS information element.

This attribute specifies the maximum cell transfer delay (MaxCTD) which is applied to the entire ATM Interface for rt-VBR traffic. MaxCTD is the sum of the fixed delay and the CDV. The components of the fixed delay include propagation delay through the physical media, delays induced by the transmission system, and fixed components of switch processing delay. This attribute is used by PNNI in the Resource Availability Information Group (RAIG) topology updates and route selection. It is also used by CAC at connection set-up time to determine whether this ATM Interface can meet the ATM connection's MaxCTD requirement.

This attribute specifies the tolerable cell loss ratio (CLR) for rt- VBR traffic except for connections managed by a Vpt CA. The number is the negative logarithm (base 10) of the CLR. For example, if the target CLR = 1E-10 then RtVbr cellLossRatio = 10. This number must be the same as the Cbr cellLossRatio since CBR and rt-VBR traffic have the same discard priority. The RtVbr cellLossRatio is used by the Connection Admission Control (CAC) algorithm to compute the required (equivalent) cell rate for rt-VBR connections. This number must be less than or equal to the NrtVbr cellLossRatio, since rt-VBR traffic has a higher discard priority. There is a trade-off between the service category CLR and the achievable link utilization. To guarantee an excellent service category, the CLR should be as small as possible (e.g., 1E-10). However, a smaller CLR results in a larger equivalent cell rate for a given connection and hence a lower link utilization. Setting this attribute to 0 means that a CLR of 1 can be tolerated. In this case, no bandwidth is reserved for rt-VBR connections, and CAC is effectively turned off. All rt-VBR are admitted.

This attribute specifies the default maximum queue length for the emission queues used to buffer the traffic of the rt-VBR service category. It is used as the basis for setting the discard thresholds on both common and per-VC queues. For the common queue, the discard thresholds are set at approximately 35, 75, and 90 percent of the value of this attribute for traffic at discard priority 3 (DP=3), DP=2, and DP=1 respectively. For a per-VC queue, the actual limit may be reduced depending on the shaping rate of the connection (for standard Vpt Vccs, this is the shaping rate of the Vpt). The discard thresholds are set at approximately 35, 75, and 90 percent of the scaled queue limit for traffic at discard priority 3 (DP=3), DP=2, and DP=1, respectively. However, a reduction will never result in a value that is less than the value set for the minPerVcQueueLimit attribute. When the value of this attribute is autoConfigure, an appropriate value is selected based on the card type. It is set to 288 for low speed cards such as DS1, E1 and IMA, and set to 480 for high speed cards such as JT2, DS3, E3 and OC3 (including ATM IP FPs). For the 1pOC12SmLrAtm card, the value is set to 2048. For the 1pOC48SmSrAtm card, the value is set to 12288. For ATM IP FPs, the per-VC queue limit may be overridden for a permanent connection by specifying a value in the Vcd Tm or Vpd Tm txQueueLimit attribute. For CQC-based ATM cards, the valid range for this attribute is from 5 to 30000 inclusive. For 1pOC48SmSrAtm cards, the value of this attribute is used to set the maximum size of the link-class queue for buffering this traffic type on the egress path. The operational value of the maximum length of a queue (common or per-VC) is indicated by the Vcc Tm, Vpc Tm, or Vpt Tm txQueueThresholds attribute. For standard Vpts, this attribute does not apply when using per-VC queuing and only applies when using common queueing. When using per-VC queueing, regardless of the Vpt's service category, standard Vpts use the AtmIf Ca NrtVbr txQueueLimit value as their default. VALUES ( 0 = autoConfigure )

This attribute specifies the minimum queue limit for the per-VC queues of connections of the rt-VBR service category. The queue limit of a per-VC queue is obtained by scaling down the txQueueLimit based on the shaping rate of that queue (shaping rate for the connection, and for standard Vpt Vccs, the shaping rate of the Vpt). This produces a constant delay for various queue lengths. The txQueueLimit provides an upper bound while minPerVcQueueLimit provides the lower bound. The value of this attribute must not be greater than the value of the txQueueLimit attribute. If this service category is used by Trunks the value of minPerVcQueueLimit must be at least 88. For the 1pOC12SmLrAtm and 1pOC48SmSrAtm cards, this attribute does not apply since per-VC queueing is not available. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr minPerVcQueueLimit value as their default. To determine the queue limit of a standard Vpt Vcc, the txQueueLimit is scaled down by the Vpt shaping rate.

This attribute specifies the shaping rate to be used in computing the tolerable delay for per-VC queues of connections of the rt-VBR service category. The delay is computed as the txQueueLimit divided by the value of this attribute. When the value of this attribute is autoConfigure, an appropriate default is selected based on the card type. It is set to 3685 for low speed cards such as DS1, E1, and IMA, and set to 14740 for high speed cards such as JT2, DS3, E3 and OC3. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, the reference rate is set to 65511 for DS3 and OC3 channels, and set to 262044 for OC12 channels. For Apc-based cards the maximum value is 1416905. For all other cards, the maximum value is 943396. For the 1pOC12SmLrAtm and 1pOC48SmSrAtm cards, this attribute does not apply since per-VC queueing is not available. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr perVcQueueLimitReferenceRate value as their default. VALUES ( 0 = autoConfigure )

This attribute specifies the default holding priority which applies to SVP and SVC rt-VBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs are released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the default holding priority which applies to SVC rt-VBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute has been obsoleted and its value migrated to holdingPriority attribute. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the default holding priority which applies to SVC rt-VBR point-to-multipoint connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is not applicable and is ignored for CQC-based ATM cards. For the 1pOC48SmSrAtm card, only the default value is supported. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards the default value is 2. This attribute specifies the emission priority (EP) which is used to transmit traffic of the rt-VBR service category. A lower numerical value for this attribute specifies a higher emission priority. 0 is the highest EP and 7 is the lowest. Cells at a higher emission priority receive higher preference for link bandwidth. EPs 0 and 1 are in the absolute priority range, and are unaffected by any minimum bandwidth guarantees. EPs 2 through 7 are in the guaranteed bandwidth range. Minimum bandwidth guarantee is specified in the AtmIf/n Ep/m component. Emission priority setting must comply with all of the following constraints: 1. The emission priority numbers must be in the following order: CBR <= rt-VBR <= nrt-VBR <= ABR <= UBR 2. Two different ATM service categories may share the same EP only if they are both shaped. 3. CBR and rt-VBR may be placed either in the absolute priority range (EP 0 or 1) or in the guaranteed bandwidth range (EP 2 through 7). 4. If both CBR and rt-VBR are shaped, rt-VBR must share the same EP with CBR or ABR. If either one of CBR or rt-VBR are not shaped, then they cannot share the same EP. 5. ABR service category is always deemed to be shaped. If nrt-VBR is shaped, it must share the same EP with ABR. If nrt-VBR is not shaped it must have a higher EP than ABR. 6. If UBR is shaped, it must share the same EP with ABR. If UBR is not shaped, it must have a lower EP than ABR. This attribute does not apply to basic Vpts, and standard Vpt Vccs.

This attribute specifies the default traffic shaping option for connections of the rt-VBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to disabled, traffic shaping cannot be enabled for any rt-VBR connections. On 1pOC12SmLrAtm cards, this attribute must be set to disabled. For CQC-based ATM cards, this attribute may be set to enabled only if the interface supports shaping, as defined by the perVcQueueInterfaces attribute in the AtmResourceControl Cqc Override component. If that component does not exist, this attribute must be set to disabled. If the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType indicates type 1 or 2, this attribute is ignored, and traffic shaping is not applicable for that connection. When this attribute is set to inverseUpc, traffic shaping for a connection is enabled according to card type and the value of the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, inverseUpc shaping is not available. If this attribute is set to inverseUpc, and the txTrafficDescType is 3, 4, or 5, linear traffic shaping is enabled. Linear traffic shaping uses a single static traffic shaping rate. On CQC-based ATM FPs, if this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, linear traffic shaping is enabled. On ATM IP FPs, if this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, inverse-UPC (also referred to as VBR or dual leaky bucket) traffic shaping is enabled. Inverse-UPC traffic shaping can burst above the sustained cell rate to the peak cell rate for the duration defined by maximum burst size. Inverse- UPC traffic shaping exactly conforms to the requirements of a dual leaky bucket UPC enforcer. When this attribute is set to enabled and the txTrafficDescType is 3, 4, 5, 6, 7, or 8, traffic shaping for a connection is enabled using linear shaping. Enabling or disabling traffic shaping may require a matching change to the emissionPriority attribute and unshapedTransmitQueueing attribute for this service category. Refer to those attributes for the complete description of the interactions. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'inverseUpc': 6, 'enabled': 5.

This attribute specifies the shaping recoup policy for the rt-VBR service category. This is the policy which is used to recoup shaping opportunities which are lost when more than one connection schedules a cell for the same transmit opportunity. In this case, one connection is scheduled, and the cell from another connection is delayed by one cell time. This attribute affects how the transmit time is calculated for the next cell on the delayed connection. This attribute is ignored if this service category is not shaped. When the connection which was delayed schedules the next cell to transmit, it may calculate the time as a difference from either the previous actual cell transmit time, or the time when the previous cell should have been transmitted. Setting this attribute to maximumEfficiency results in each connection trying to recoup or regain delays in scheduling. The transmit time from the next cell is calculated from the time when the cell should originally have been sent. Cell delay variation (CDV) occurs in this case since the cells are sent with less than the shaping delay between them. However, in general the shaper recovers (recoups) lost opportunities and improves efficiency. Setting this attribute to minimumCdv results in connections not trying to recoup or regain any delays in scheduling. The transmit time for the next cell is calculated from the time when the previous cell was actually transmitted. This minimizes CDV, but results in missed cell opportunities. Enumeration: 'maximumEfficiency': 1, 'minimumCdv': 0.

This attribute specifies the default queuing option for unshaped connections of the rt-VBR service category. This attribute controls whether common or per-VC queueing is used. Per-VC queueing means that each connection has its own buffering and queue limits. Common queueing means that cells are queued in First In First Out order on a common queue for this service category. The common queue has one set of congestion control levels for all cells enqueued on it. For 1pOC12SmLrAtm and 1pOC48SmSrAtm cards this attribute must be set to common or autoConfigure. This attribute cannot be set to perVc since per-Vc queueing is not available on the 1pOC12SmLrAtm and 1pOC48SmSrAtm cards. The value autoConfigure is interpreted to mean common queueing. For ATM IP cards, if traffic shaping for this service category is disabled, this attribute may take any of the three values. In this case, the value autoConfigure is interpreted to mean per-VC queueing. For ATM IP cards, if traffic shaping for this service category is not disabled, the only permitted values are perVc and autoConfigure. In this case, the result is that all connections use per-VC queueing. For CQC-based ATM cards, if the perVcQueueInterfaces attribute of the Lp Eng Arc Cqc component permits shaping for this interface, then this attribute may take any of the three values. In this case, the value autoConfigure is interpreted to mean per-VC queueing. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards only perVc queueing is supported. All other attribute values are ignored. For CQC-based ATM cards, if the perVcQueueInterfaces attribute of the Lp Eng Arc Cqc component does not permit shaping for this interface, then this attribute may take values common or autoConfigure. In this case, the value autoConfigure is interpreted to mean common queueing. If this attribute is set to autoConfigure, an override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The opUnshapedTransmitQueueing attribute of this component indicates whether the transmit queueing is perVc or common. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'perVc': 0, 'autoConfigure': 2, 'common': 1.

This attribute specifies the default usage parameter control (UPC) option for connections of the rt-VBR service category. This attribute is ignored if the rxTrafficDescriptorType indicates 1 or 2. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to enforced, UPC is enforced for each connection. When UPC is enforced, non-conforming cells are either tagged or discarded depending on the rxTrafficDescriptorType. On ATM IP FPs, when this attribute is set to monitored, UPC conformance checking is performed, except, instead of the non- conforming cells being tagged or discarded, they are merely counted in the UPC violations counts, and passed on unchanged. On CQC-based ATM FPs, when this attribute is set to monitored, it has the same effect as setting it to disabled. When this attribute is set to disabled, UPC is disabled on the receive path for all rt-VBR connections. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4.

This attribute specifies the policy which is applied when calculating the fairness weight for unshaped connections of the rt-VBR service category. The fairness weight for a connection determines the relative amount of bandwidth which that connection obtains, compared to other connections in the same service category. Connections with equal weight get equal transmit opportunities. Connections with higher weights get more transmit opportunities compared with connections that have lower weights. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The fairness weight for a connection is directly proportional to the value of one of the traffic descriptor parameters for that connection. This attribute specifies which traffic descriptor parameter is used for connections of the rt-VBR service category. This attribute is ignored on CQC-based ATM cards and the 1pOC48SmSrAtm card. This attribute is also ignored on ATM IP cards if unshapedTransmitQueueing is set for common queuing. If this attribute is set to scr, the fairness weight is proportional to the transmit sustained cell rate (SCR) of a connection. Connections with a higher SCR have a higher fairness weight. For connections with txTrafficDescType 3, which have no SCR, the sustained cell rate is assumed to be equal to the peak cell rate. If this attribute is set to pcr, the fairness weight is proportional to the transmit peak cell rate (PCR) of a connection. Connections with a higher PCR have a higher fairness weight. Connections with txTrafficDescType 1 or 2 get a minimum weight, which is 1. If this attribute is set to ecr, the fairness weight is proportional to the equivalent cell rate (ECR) of a connection as calculated by connection admission control (CAC). Connections with a higher ECR have a higher fairness weight. Connections with an ECR of 0 get a minimum weight, which is 1. The weight of a connection is visible in the Vcc Tm, Vpc Tm, or Vpt Tm weight attribute. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'pcr': 2, 'ecr': 3, 'scr': 1.

This attribute specifies the default of whether to force tagging (CLP=1) of all cells for all rt-VBR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. This attribute is not supported by 4pOC12SmIrAtm and 4pOC12SmLrAtm cards. When this attribute is set to enabled, CLP is set to 1 for all cells in the transmit direction. Force tagging is only supported on ATM IP FPs. On CQC-based ATM FPs, this attribute must be set to disabled. When this attribute is set to disabled, CLP is unchanged for all cells in the transmit direction. This attribute never applies to any type of Vpt. Enumeration: 'disabled': 1, 'enabled': 0.

This group contains operational attributes for the rt-VBR service category.

An entry in the mscAtmIfCARtVbrOperTable.

This attribute indicates the state of transmit queueing for unshaped rt-VBR connections. A value of perVc indicates that any unshaped connections use per- VC queueing. A value of common indicates that traffic for unshaped connections uses the common queue which corresponds to the EP for this service category. Enumeration: 'perVc': 0, 'common': 1.

This attribute indicates the Early Packet Discard (EPD) offset which is currently in use for this service category. The EPD offset is used to derive the EPD thresholds for each CC level. Any connection under this service category which requires the txPacketWiseDiscard feature must specify a transmit queue limit which is at least 5.71 times this offset. This ensures that the derived Epd threshold will never be less than 17.5 % of the transmit queue limit. If this is not done, txPacketWiseDiscard for the connection will be automatically disabled. The value of this EPD offset is specified under the lp/x eng arc aqm ov component.

This entry controls the addition and deletion of mscAtmIfCANrtVbr components.

A single entry in the table represents a single mscAtmIfCANrtVbr component.

This variable is used as the basis for SNMP naming of mscAtmIfCANrtVbr components. These components can be added.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfCANrtVbr tables.

This variable represents the index for the mscAtmIfCANrtVbr tables.

This group contains provisioned attributes which control the nrt- VBR service category for this interface.

An entry in the mscAtmIfCANrtVbrProvTable.

This attribute specifies the bandwidth pool which is to be used to support the non-real-time variable bit rate (nrt-VBR) service category except for connections managed by a Vpt CA. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to nrt-VBR traffic. The percentage allocated to each bandwidth pool can be provisioned through the bandwidthPool attribute under the CA. Enumeration: 'pool3': 3, 'pool2': 2, 'pool1': 1, 'pool5': 5, 'pool4': 4.

This attribute specifies the default cell delay variation tolerance (CDVT) for all connections of the nrt-VBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. If Usage Parameter Control (UPC) is enabled for a connection, CDVT is used by the UPC function to decide whether a cell is conforming or non-conforming based on the connection's traffic descriptor type. The larger the CDVT value, the more tolerant is the UPC of bandwidth usage beyond the traffic contract.

This attribute specifies the tolerable cell loss ratio (CLR) for nrt- VBR traffic except for connections managed by a Vpt CA. The number is the negative logarithm (base 10) of the CLR. In other words if the target CLR = 1E-10 then NrtVbr cellLossRatio = 10. This number must be greater than or equal to RtVbr cellLossRatio since rt-VBR traffic has a higher discard priority. The NrtVbr cellLossRatio is used by the Connection Admission Control (CAC) algorithm to compute the required (equivalent) cell rate for nrt-VBR connections. There is a trade-off between the service category CLR and the achievable link utilization. To guarantee an excellent service category, the CLR should be as small as possible (e.g., 1E-10). However, a smaller CLR results in a larger equivalent cell rate for a given connection and hence a lower link utilization. Setting this attribute to 0 means that a CLR of 1 can be tolerated. In this case no bandwidth is reserved for nrt-VBR connections, and CAC is effectively turned off. All nrt-VBR connections are admitted.

This attribute specifies the default maximum queue length for the emission queues used to buffer the traffic of the nrt-VBR service category. It is used as the basis for setting the discard thresholds on both common and per-VC queues. For the common queue, the discard thresholds are set at approximately 35, 75, and 90 percent of the value of this attribute for traffic at discard priority 3 (DP=3), DP=2, and DP=1 respectively. For per-VC queue, the actual limit may be reduced depending on the shaping rate of the connection (for standard Vpt Vccs, this is the shaping rate of the Vpt). The discard thresholds are set at approximately 35, 75, and 90 percent of the scaled queue limit for traffic at discard priority 3 (DP=3), DP=2, and DP=1 respectively. However, a reduction will never result in a value that is less than the value set for the minPerVcQueueLimit attribute. When the value of this attribute is autoConfigure, an appropriate value is selected based on the card type. It is set to 1792 for low speed cards such as DS1, E1, and IMA, set to 2304 for high speed CQC-based ATM cards such as JT2, DS3, E3 and OC3, and set to 10240 for high speed ATM IP cards such as 3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2 and 2pOC3MmAtm2. For the 1pOC12SmLrAtm card, if autoConfigure is selected for this attribute then the value is set to 7680. For the 1pOC48SmSrAtm card, if autoConfigure is selected for this attribute the the value is set to 122880. For ATM IP FPs, the per-VC queue limit may be overridden for a permanent connection by specifying a value in the Vcd Tm or Vpd Tm txQueueLimit attribute. For the 1pOC48SmSrAtm card, the value of this attribute is used to set the maximum size of the link-class queue for buffering the nrt- VBR traffic on the egress path. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components, and the valid range is from 5 to 30000 inclusive. The operational value of the maximum length of a queue (common or per-VC) is indicated by the Vcc Tm, Vpc Tm, or Vpt Tm txQueueThresholds attribute. When using per-VC queueing, this attribute is used as the default txQueueLimit for all standard Vpts, regardless of their atmServiceCategory. VALUES ( 0 = autoConfigure )

This attribute specifies the default holding priority which applies to SVC nrt-VBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute has been obsoleted and its value migrated to holdingPriority attribute. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the minimum queue limit for the per-VC queues of connections of the nrt-VBR service category. The queue limit of a per-VC queue is obtained by scaling down the txQueueLimit based on the shaping rate of that queue (shaping rate for the connection, and for standard Vpt Vccs, the shaping rate of the Vpt). This produces a constant delay for various queue lengths. The txQueueLimit provides an upper bound while minPerVcQueueLimit provides the lower bound. The value of this attribute must not be greater than the value of the txQueueLimit attribute. If this service category is used by Trunks the value of minPerVcQueueLimit must be at least 88. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components. This attribute does not apply for the 1pOC12SmLrAtm and 1pOC48SmSrAtm cards, since per-VC queueing is not available. This attribute is used as the default minPerVcQueueLimit for all standard Vpts, regardless of their atmServiceCategory. This attribute does not apply to basic Vpts.

This attribute specifies the shaping rate to be used in computing the tolerable delay for per-VC queues of connections of the nrt-VBR service category. The delay is computed as the txQueueLimit divided by the value of this attribute. When the value of this attribute is autoConfigure, an appropriate default is selected based on the card type. It is set to 3685 for low speed cards such as DS1, E1 and IMA, set to 14740 for high speed CQC-based ATM cards such as JT2, DS3, E3 and OC3, and set to 65511 for high speed ATM IP cards such as 3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2 and 2pOC3MmAtm2. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, the reference rate is set to 65511 for DS3 and OC3 channels, and set to 262044 for OC12 channels. For Apc-based cards the maximum value is 1416905. For all other cards, the maximum value is 943396. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components. For the 1pOC12SmLrAtm and 1pOC48SmSrAtm cards, this attribute does not apply since per-VC queueing is not available. This attribute is used as the default perVcQueueLimitReferenceRate for all standard Vpts, regardless of their atmServiceCategory. This attribute does not apply to basic Vpts. VALUES ( 0 = autoConfigure )

This attribute specifies the default holding priority which applies to SVC nrt-VBR point-to-multipoint connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the holding priority which applies to SVP and SVC nrt-VBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is not applicable and is ignored for CQC-based ATM cards. For the 1pOC48SmSrAtm card, only the default value is supported. This attribute specifies the emission priority (EP) which is used to transmit traffic of the nrt-VBR service category. A lower numerical value for this attribute specifies a higher emission priority. 0 is the highest EP and 7 is the lowest. Cells at a higher emission priority receive higher preference for link bandwidth. EPs 0 and 1 are in the absolute priority range, and are unaffected by any minimum bandwidth guarantees. EPs 2 through 7 are in the guaranteed bandwidth range. Minimum bandwidth guarantee is specified in the AtmIf/n Ep/m component. Emission priority setting must comply with all of the following constraints: 1. The emission priority numbers must be in the following order: CBR <= rt-VBR <= nrt-VBR <= ABR <= UBR 2. Two different ATM service categories may share the same EP only if they are both shaped. 3. CBR and rt-VBR may be placed either in the absolute priority range (EP 0 or 1) or in the guaranteed bandwidth range (EP 2 through 7). 4. If both CBR and rt-VBR are shaped, rt-VBR must share the same EP with CBR or ABR. If either one of CBR or rt-VBR are not shaped, then they cannot share the same EP. 5. ABR service category is always deemed to be shaped. If nrt-VBR is shaped, it must share the same EP with ABR. If nrt-VBR is not shaped it must have a higher EP than ABR. 6. If UBR is shaped, it must share the same EP with ABR. If UBR is not shaped, it must have a lower EP than ABR. This attribute does not apply to basic Vpts, and standard Vpt Vccs.

This attribute specifies the default traffic shaping option for connections of the nrt-VBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to disabled, traffic shaping cannot be enabled for any nrt-VBR connections. On 1pOC12SmLrAtm and 1pOC48SmSrAtm cards, this attribute must be set to disabled. For CQC-based ATM cards, this attribute may be set to enabled only if the interface supports shaping, as defined by the perVcQueueInterfaces attribute in the AtmResourceControl Cqc Override component. If that component does not exist, this attribute must be set to disabled. If the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType indicates type 1 or 2, this attribute is ignored, and traffic shaping is not applicable for that connection. When this attribute is set to inverseUpc, traffic shaping for a connection is enabled according to card type and the value of the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, inverseUpc shaping is not available. If this attribute is set to inverseUpc, and the txTrafficDescType is 3, 4, or 5, linear traffic shaping is enabled. Linear traffic shaping uses a single static traffic shaping rate. On CQC-based ATM FPs, if this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, linear traffic shaping is enabled. On ATM IP FPs, if this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, inverse-UPC (also referred to as VBR or dual leaky bucket) traffic shaping is enabled. Inverse-UPC traffic shaping can burst above the sustained cell rate to the peak cell rate for the duration defined by maximum burst size. Inverse- UPC traffic shaping exactly conforms to the requirements of a dual leaky bucket UPC enforcer. When this attribute is set to enabled and the txTrafficDescType is 3, 4, 5, 6, 7, or 8, traffic shaping for a connection is enabled using linear shaping. Enabling or disabling traffic shaping may require a matching change to the emissionPriority attribute and unshapedTransmitQueueing attribute for this service category. Refer to those attributes for the complete description of the interactions. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'inverseUpc': 6, 'enabled': 5.

This attribute specifies the shaping recoup policy for the nrt-VBR service category. This is the policy which is used to recoup shaping opportunities which are lost when more than one connection schedules a cell for the same transmit opportunity. In this case, one connection is scheduled, and the cell from the other connection is delayed by one cell time. This attribute affects how the transmit time is calculated for the next cell on the delayed connection. This attribute is ignored if this service category is not shaped. When the connection which was delayed schedules the next cell to transmit, it may calculate the time as a difference from either the previous actual cell transmit time, or the time when the previous cell should have been transmitted. Setting this attribute to maximumEfficiency results in each connection trying to recoup or regain any delays in scheduling. The transmit time from the next cell is calculated from the time when the cell should originally have been sent. Cell delay variation (CDV) occurs in this case since the cells are sent with less than the shaping delay between them. However, in general the shaper recovers (recoups) lost opportunities and improves efficiency. Setting this attribute to minimumCdv results in connections not trying to recoup or regain any delays in scheduling. The transmit time for the next cell is calculated from the time when the previous cell was actually transmitted. This minimizes CDV, but results in missed cell opportunities. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'maximumEfficiency': 1, 'minimumCdv': 0.

This attribute specifies the default queuing option for unshaped connections of the nrt-VBR service category. This attribute controls whether common or per-VC queueing is used. Per-VC queueing means that each connection has its own buffering and queue limits. Common queueing means that cells are queued in First In First Out order on a common queue. The common queue has one set of congestion control levels for all cells enqueued on it. For ATM IP cards, there is one common queue for the nrt-VBR service category. For CQC-based ATM cards, there is one common queue which is shared by the nrt-VBR, ABR and UBR service categories. For ATM IP cards, if traffic shaping for this service category is disabled, this attribute may take any of the three values. In this case, the value autoConfigure is interpreted to mean per-VC queueing. For 1pOC12SmLrAtm and 1pOC48SmSrAtm cards this attribute must be set to common or autoConfigure. This attribute cannot be set to perVc since per-Vc queueing is not available on the 1pOC12SmLrAtm and 1pOC48SmSrAtm cards. The value autoConfigure is interpreted to mean common queueing. For ATM IP cards, if traffic shaping for this service category is not disabled, the only permitted values are perVc and autoConfigure. In this case, the result is that all connections use per-VC queueing. For CQC-based ATM cards, if the perVcQueueInterfaces attribute of the Lp Eng Arc Cqc component permits shaping for this interface, then this attribute may take any of the three values. In this case, the value autoConfigure is interpreted to mean per-VC queueing. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards only perVc queueing is supported. All other attribute values are ignored. For CQC-based ATM cards, if the perVcQueueInterfaces attribute of the Lp Eng Arc Cqc component does not permit shaping for this interface, then this attribute may take the values common or autoConfigure. In this case, the value autoConfigure is interpreted to mean common queueing. If this attribute is set to autoConfigure, an override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The opUnshapedTransmitQueueing attribute of this component indicates whether the transmit queueing is perVc or common. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'perVc': 0, 'autoConfigure': 2, 'common': 1.

This attribute specifies the default usage parameter control (UPC) option for connections of the nrt-VBR service category. This attribute is ignored if the rxTrafficDescriptorType indicates 1 or 2. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to enforced, UPC is enabled for each connection. When UPC is enforced, non-conforming cells are either tagged or discarded depending on the rxTrafficDescriptorType. On ATM IP FPs, when this attribute is set to monitored, UPC conformance checking is performed, except, instead of the non- conforming cells being tagged or discarded, they are merely counted in the UPC violations counts, and passed on unchanged. On CQC-based ATM FPs, when this attribute is set to monitored, it has the same effect as setting it to disabled. For the 1pOC48SmSrAtm card, the value of this attribute must be set to disabled. When this attribute is set to disabled, UPC is disabled on the receive path for all nrt-VBR connections. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4.

This attribute specifies the policy which is applied when calculating the fairness weight for unshaped connections of the nrt-VBR service category. The fairness weight for a connection determines the relative amount of bandwidth which that connection obtains, compared to other connections in the same service category. Connections with equal weight get equal transmit opportunities. Connections with higher weights get more transmit opportunities compared with connections that have lower weights. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The fairness weight for a connection is directly proportional to the value of one of the traffic descriptor parameters for that connection. This attribute specifies which traffic descriptor parameter is used for connections of the nrt-VBR service category. This attribute is ignored on CQC-based ATM cards. This attribute is also ignored on ATM IP cards if unshapedTransmitQueueing is set for common queuing. This attribute is also ignored for 1pOC48SmSrAtm cards. If this attribute is set to scr, the fairness weight is proportional to the transmit sustained cell rate (SCR) of a connection. Connections with a higher SCR have a higher fairness weight. For connections with txTrafficDescType 3, which have no SCR, the sustained cell rate is assumed to be equal to the peak cell rate. If this attribute is set to pcr, the fairness weight is proportional to the transmit peak cell rate (PCR) of a connection. Connections with a higher PCR have a higher fairness weight. Connections with txTrafficDescType 1 or 2 get a minimum weight, which is 1. If this attribute is set to ecr, the fairness weight is proportional to the equivalent cell rate (ECR) of a connection as calculated by connection admission control (CAC). Connections with a higher ECR have a higher fairness weight. Connections with an ECR of 0 get a minimum weight, which is 1. The weight of a connection is visible in the Vcc Tm, Vpc Tm, or Vpt Tm weight attribute. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'pcr': 2, 'ecr': 3, 'scr': 1.

This attribute specifies the default of whether to force tagging (CLP=1) of all cells for all nrt-VBR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. This attribute is not supported by 4pOC12SmIrAtm and 4pOC12SmLrAtm cards. When this attribute is set to enabled, CLP is set to 1 for all cells in the transmit direction. Force tagging is only supported on ATM IP FPs. On CQC-based ATM FPs, this attribute must be set to disabled. When this attribute is set to disabled, CLP is unchanged for all cells in the transmit direction. This attribute never applies to any type of Vpt. Enumeration: 'disabled': 1, 'enabled': 0.

This group contains operational attributes for the nrt-VBR service category.

An entry in the mscAtmIfCANrtVbrOperTable.

This attribute indicates the state of transmit queueing for unshaped nrt-VBR connections. A value of perVc indicates that any unshaped connections use per- VC queueing. A value of common indicates that traffic for unshaped connections uses the common queue which corresponds to the EP for this service category. Enumeration: 'perVc': 0, 'common': 1.

This attribute indicates the Early Packet Discard (EPD) offset which is currently in use for this service category. The EPD offset is used to derive the EPD thresholds for each CC level. Any connection under this service category which requires the txPacketWiseDiscard feature must specify a transmit queue limit which is at least 5.71 times this offset. This ensures that the derived Epd threshold will never be less than 17.5 % of the transmit queue limit. If this is not done, txPacketWiseDiscard for the connection will be automatically disabled. The value of this EPD offset is specified under the lp/x eng arc aqm ov component.

This entry controls the addition and deletion of mscAtmIfCAAbr components.

A single entry in the table represents a single mscAtmIfCAAbr component.

This variable is used as the basis for SNMP naming of mscAtmIfCAAbr components. These components can be added.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfCAAbr tables.

This variable represents the index for the mscAtmIfCAAbr tables.

This group contains provisioned attributes which control the ABR service category for this interface.

An entry in the mscAtmIfCAAbrProvTable.

This attribute specifies the bandwidth pool which is to be used to support the available bit rate (ABR) service category except for connections managed by a Vpt CA. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to ABR traffic. The percentage allocated to each bandwidth pool can be provisioned through the bandwidthPool attribute under the CA. Enumeration: 'pool3': 3, 'pool2': 2, 'pool1': 1, 'pool5': 5, 'pool4': 4.

This attribute specifies the default cell delay variation tolerance (CDVT) for all connections of the ABR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component, or signalled in the SVC Traffic Descriptor Information Element. This attribute is used by dynamic generic cell rate algorithm (DGCRA) policer on ATM IP cards. On CQC-based ATM cards ABR UPC is enforced using PCR and CDVT.

This attribute specifies the default maximum queue length for the emission queues used to buffer the traffic of the ABR service category. It is used as the basis for setting the discard thresholds on ABR per-VC queues. For per-VC queue, the actual limit may be reduced depending on the peak cell rate. The discard thresholds are set at approximately 35, 75 and 90 percent of the scaled queue limit for traffic at discard priority 3 (DP=3), DP=2 and DP=1 respectively. However, a reduction will never result in a value that is less than the value set for the minPerVcQueueLimit attribute. When the value of this attribute is autoConfigure, an appropriate value is selected based on the card type. It is set to 1792 for low speed cards such as DS1, E1 and IMA, set to 2304 for high speed CQC-based ATM cards such as JT2, DS3, E3 and OC3, and set to 10240 for high speed ATM IP cards such as 3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2 and 2pOC3MmAtm2. For the 1pOC12SmLrAtm card, the value is set to 6144. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components, and the valid range is from 5 to 30000 inclusive. For ATM IP FPs, the per-VC queue limit may be overridden for a permanent connection by specifying a value in the Vcd Tm or Vpd Tm txQueueLimit attribute. The operational value of the maximum length of a queue (common or per-VC) is indicated by the Vcc Tm, Vpc Tm, or Vpt Tm txQueueThresholds attribute. For standard Vpts, this attribute does not apply when using per-VC queuing and only applies when using common queueing. When using per-VC queueing, regardless of the Vpt's service category, standard Vpts use the AtmIf Ca NrtVbr txQueueLimit value as their default. This attribute does not apply to basic Vpts. VALUES ( 0 = autoConfigure )

This attribute specifies the minimum queue limit for the per-VC queues of connections of the ABR service category. The queue limit of a per-VC queue is obtained by scaling down the txQueueLimit based on the peak cell rate of that queue. This produces a constant delay for various queue lengths. The txQueueLimit provides an upper bound while minPerVcQueueLimit provides the lower bound. The value of this attribute must not be greater than the value of the txQueueLimit attribute. If this service category is used by Trunks the value of minPerVcQueueLimit must be at least 88. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components. For the 1pOC12SmLrAtm card, this attribute does not apply since per-VC queueing is not available. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr minPerVcQueueLimit value as their default. To determine the queue limit of a standard Vpt Vcc, the txQueueLimit is scaled down by the Vpt shaping rate.

This attribute specifies the shaping rate to be used in computing the tolerable delay for per-VC queues of connections of the ABR service category. The delay is computed as the txQueueLimit divided by the value of this attribute. When the value of this attribute is autoConfigure, an appropriate default is selected based on the card type. It is set to 3685 for low speed cards such as DS1, E1 and IMA, set to 14740 for high speed CQC-based ATM cards such as JT2, DS3, E3 and OC3, and set to 65511 for high speed ATM IP cards such as 3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2 and 2pOC3MmAtm2. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components. For the 1pOC12SmLrAtm card, this attribute does not apply since per-VC queueing is not available. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr perVcQueueLimitReferenceRate value as their default. VALUES ( 0 = autoConfigure )

This attribute is not applicable and is ignored for CQC-based ATM cards. This attribute specifies the emission priority (EP) which is used to transmit traffic of the ABR service category. A lower numerical value for this attribute specifies a higher emission priority. 0 is the highest EP and 7 is the lowest. Cells at a higher emission priority receive higher preference for link bandwidth. EPs 0 and 1 are in the absolute priority range, and are unaffected by any minimum bandwidth guarantees. EPs 2 through 7 are in the guaranteed bandwidth range. Minimum bandwidth guarantee is specified in the AtmIf/n Ep/m component. Emission priority setting must comply with all of the following constraints: 1. The emission priority numbers must be in the following order: CBR <= rt-VBR <= nrt-VBR <= ABR <= UBR 2. Two different ATM service categories may share the same EP only if they are both shaped. 3. CBR and rt-VBR may be placed either in the absolute priority range (EP 0 or 1) or in the guaranteed bandwidth range (EP 2 through 7). 4. If both CBR and rt-VBR are shaped, rt-VBR must share the same EP with CBR or ABR. If either one of CBR or rt-VBR are not shaped, then they cannot share the same EP. 5. ABR service category is always deemed to be shaped. If nrt-VBR is shaped, it must share the same EP with ABR. If nrt-VBR is not shaped it must have a higher EP than ABR. 6. If UBR is shaped, it must share the same EP with ABR. If UBR is not shaped, it must have a lower EP than ABR. This attribute does not apply to basic Vpts, and standard Vpt Vccs.

This attribute specifies the fairness policy which is applied to available bandwidth when performing the ER calculation in the ABR service category. This applies to any connection point performing explicit rate calculations. Each ABR connection is assigned a weight. Connections with a higher weight get a greater proportion of the available ABR bandwidth compared with connections that have lower weights. This attribute is ignored on CQC-based ATM cards. If the value is mcr, the congestion fairness weight is based on the Minimum Cell Rate (MCR) of the connection. If the value is pcr, the congestion fairness weight is based on the Peak Cell Rate (PCR) of the connection. If the value is pcrMinusMcr, the congestion fairness weight is based on the difference between the Peak Cell Rate and the Minimum Cell Rate (PCR - MCR) of the connection. Enumeration: 'pcr': 2, 'pcrMinusMcr': 4, 'mcr': 0.

This attribute specifies the portion of the Fixed Round Trip Time (FRTT) which is added to each ABR call setup which traverses this interface. The FRTT for the entire call is the sum of the FRTT portions for each interface traversed by the call. FRTT is used by the ABR Source or Virtual Source to adjust the value of ICR according to the rules specified in the ATM Forum TM Version 4.0 specification. The frttPortion includes propagation delay through the physical media, plus delays included by the transmission system, plus fixed components of switch processing delay. This attribute is used by ATM Networking at call set-up time for ABR connections directed over this interface.

This attribute specifies the default type for ABR connections. It may be overridden by the abrConnectionType attribute under the Vcd Tm or Vpd Tm component, or by other configuration options. For example, for ABR end point connections originating at this switch, the Vcc Tm abrConnectionType will show sourceDest regardless of the setting of this attribute. If this attribute is set to abrSwitch, traversing ABR connections default to type abrSwitchEr or abrSwitchEfci, depending on the card type. If the interface to which traffic is directed across the backplane is configured as type virtualSourceDest and this is a ATM IP FP, then connection points under this AtmIf are activated as type virtualSourceDest. If this attribute is set to virtualSourceDest, traversing ABR connections may be instantiated as one of the following types: abrSwitchEr, abrSwitchEfci, or virtualSourceDest. A Virtual Source-Virtual Destination (VS/VD) boundary forms a break in the end to end flow of RM cells as defined in the ATM Forum Specification for Traffic Management Version 4.0. On ATM IP cards, a VS/VD boundary can be configured for a connection providing all of the following conditions are met: 1. the ABR connection is traversing (not terminating at) this interface; 2. both this interface and next hop interface to which traffic is directed across the backplane are located on ATM IP cards; 3. one or both connecting points are configured as virtualSourceDest, 4. the next hop interface to which traffic is directed across the backplane is not configured as nonAbrInterworking. If this attribute is set to nonAbrInterworking, this interface is defined as a point of interworking between an ABR and a non-ABR connection. In this case the next hop interface to which traffic is directed across the backplane is activated as type sourceDest. The Vcc Tm or Vpc Tm abrConnectionType operational attribute indicates what type of ABR connection was activated. Enumeration: 'abrSwitch': 0, 'nonAbrInterworking': 5, 'virtualSourceDest': 3.

This attribute specifies the default usage parameter control (UPC) option for connections of the ABR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. For ATM IP cards, if this attribute is set to enforced, UPC for ABR connection is enforced as a Dynamic Generic Cell Rate Algorithm (DGCRA) based on the connection traffic descriptor. For CQC-based ATM cards, if this attribute is set to enforced, the connection enforces a single GCRA policer at the defined PCR and CDVT for this connection. When UPC is enforced on an ABR connection, non-conforming cells are discarded. On ATM IP FPs, when this attribute is set to monitored, UPC conformance checking is performed, except, instead of the non- conforming cells being discarded, they are merely counted in the UPC violations counts, and passed on unchanged. On CQC-based ATM FPs, when this attribute is set to monitored, it has the same effect as setting it to disabled. When this attribute is set to disabled, UPC is disabled on the receive path for all ABR connections. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4.

This attribute specifies the default Initial Cell Rate (ICR) parameter for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled in the ABR Setup Parameters Information Element. ICR is the rate at which a source should send initially and after an idle period. When this attribute is set to useMcr, ICR is set to the same value as the Minimum Cell Rate (MCR) for the connection. When this attribute is set to usePcr, ICR is set to the same value as the Peak Cell Rate (PCR) for the connection. When this attribute is set to some explicit number, that number is used as the ICR, provided it is between MCR and PCR. If the explicit number is below MCR, then MCR is used as ICR. If the explicit number is above PCR, then PCR is used as ICR. VALUES ( 16777217 = useMcr 16777218 = usePcr )

This attribute specifies the default Rate Decrease Factor (RDF) for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled in the ABR Setup Parameters Information Element. The RDF value is computed by using the provisioned value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 8, RDF is 2E-8 = 1/256. RDF controls the amount by which the cell transmission rate may decrease upon receipt of a backward Resource Management (B- RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) field set to 1, the Allowed Cell Rate (ACR) value would be reduced by the amount (RDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR.

This attribute specifies the default Rate Increase Factor (RIF) for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled in the ABR Setup Parameters Information Element. The RIF value is computed by using the provisioned value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 6, RIF is 2E-6 = 1/64. RIF controls the amount by which the cell transmission rate may increase upon receipt of a backward Resource Management (B-RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) and the No Increase (NI) fields both set to 0, the Allowed Cell Rate (ACR) value would be increased by the amount (RIF*ACR). The ACR is not allowed to exceed the Peak Cell Rate (PCR), in which case the ACR is set to PCR.

This attribute specifies the default number of user cells per Resource Management cell (NRM) for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled as the NRM parameter in the ABR Additional Parameters Information Element. NRM is the maximum number of cells an ABR source may transmit for each forward Resource Management (F-RM) cell. The count of the cells transmitted includes user cells, OAM cells, backward RM cells, and the forward RM cell. Note that a value of 2 is not recommended even though it is permitted according to the ATM Forum standard. When this attribute is set to a value of 2, it is possible that only one forward and one backward RM cell are repeatedly transmitted, and all data traffic is queued up indefinitely. This attribute is ignored under all conditions where the Vcc Tm or Vpc Tm operational attribute abrConnectionType indicates explicitRateMarking.

This attribute specifies the default time between Resource Management cells (TRM) for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled in the ABR Additional Parameters Information Element. TRM provides an upper bound on the time interval between forward Resource Management (F-RM) cells for an ABR source. Since the last F-RM cell was sent, if at least TRM time has elapsed and at least 2 other cells have been sent, the next cell to be transmitted would be a forward RM cell. This attribute is ignored under all conditions where the Vcc Tm or Vcd Tm operational attribute abrConnectionType is displayed as explicitRateMarking. The provisioned value of 781 is signalled in the ABR Additional Parameters Information Element as 0. 1563 is signalled as 1. 3125 is signalled as 2. 6250 is signalled as 3. 12500 is signalled as 4. 25000 is signalled as 5. 50000 is signalled as 6. 100000 is signalled as 7.

This attribute specifies the default Cutoff Decrease Factor (CDF) parameter for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled in the ABR Additional Parameters Information Element. When the value of this attribute is non-zero, CDF is computed as the inverse of the value. For example, if the value is 32, the value of CDF is 1/32. When the value of this attribute is 0, CDF is also zero. CDF controls the decrease in the Allowed Cell Rate (ACR) associated with the CRM parameter. CRM is the limit of the number of forward Resource Management (F-RM) cells which may be sent in the absence of received backward RM cells. When this limit is crossed, the ACR value would be decreased by the amount (CDF*ACR). The ACR is not allowed to fall below the MCR, in which case the ACR is set to MCR.

This attribute specifies the default Allowed Cell Rate Decrease Time Factor (ADTF) parameter for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component, or signalled in the ABR Additional Parameters Information Element. ADTF is the time interval permitted between sending forward Resource Management (F-RM) cells before the Allowed Cell Rate (ACR) is decreased to the Initial Cell Rate (ICR). In other words, if the source does not transmit a forward RM cell for a period of ADTF centi-seconds (hundredths of a second), it will reduce its ACR to the value of its ICR. If ACR is already at or below ICR, further rate reductions are defined by the CRM ABR parameter.

This attribute specifies the default maximum delay for Dynamic General Cell Rate Algorithm (DGCRA) rate changes for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component. This attribute specifies an upper bound on the delay after which the rate change induced by a backward Resource Management (B-RM) cell departing from this interface (in the backward direction) is expected to be observed at the interface (in the forward connection). This upper bound may be approximated as the round trip sum of the fixed and propagation delays and the maximum queueing delays between the ABR source and this interface. The value of this attribute is used in policing an ABR connection using the DGCRA. A larger value for this attribute implies a more lenient policer. When there is a decrease in the Allowed Cell Rate (ACR), the policer waits a correspondingly longer period of time before it enforces the new cell rate. The value of this attribute must be greater than or equal to dgcraMinimumDelay, since the maximum delay must be greater than or equal to the minimum delay.

This attribute specifies the default minimum delay for Dynamic General Cell Rate Algorithm (DGCRA) rate changes for ABR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm Abr or Vpd Tm Abr component. This attribute specifies a lower bound on the delay after which the rate change induced by a backward Resource Management (B-RM) cell departing from this interface (in the backward direction) is expected to be observed at the interface (in the forward connection). This lower bound may be approximated as the round trip sum of the fixed and propagation delays between the ABR source and this interface. The value of this attribute is used in policing an ABR connection using the DGCRA. A smaller value for this attribute implies a more lenient policer. When there is an increase in the Allowed Cell Rate (ACR), the policer waits for a correspondingly shorter period of time before it enforces the new cell rate. The value of this attribute must be less than or equal to dgcraMaximumDelay, since the maximum delay must be greater than or equal to the minimum delay.

This attribute specifies the default holding priority which applies to SVP and SVC ABR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This group contains operational attributes for the ABR service category.

An entry in the mscAtmIfCAAbrOperTable.

This attribute indicates the Early Packet Discard (EPD) offset which is currently in use for this service category. The EPD offset is used to derive the EPD thresholds for each CC level. Any connection under this service category which requires the txPacketWiseDiscard feature must specify a transmit queue limit which is at least 5.71 times this offset. This ensures that the derived Epd threshold will never be less than 17.5 % of the transmit queue limit. If this is not done, txPacketWiseDiscard for the connection will be automatically disabled. The value of this EPD offset is specified under the lp/x eng arc aqm ov component.

This entry controls the addition and deletion of mscAtmIfCAUbr components.

A single entry in the table represents a single mscAtmIfCAUbr component.

This variable is used as the basis for SNMP naming of mscAtmIfCAUbr components. These components can be added.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfCAUbr tables.

This variable represents the index for the mscAtmIfCAUbr tables.

This group contains provisioned attributes for the UBR service category.

An entry in the mscAtmIfCAUbrProvTable.

This attribute specifies the maximum number of UBR Vpcs that can be activated on this AtmIf. The value must not exceed the maxVpcs attribute of the parent CA component. If this attribute is specified as sameAsCa, the maximum number of Vpcs is defined by the AtmIf/n CA maxVpcs attribute. Changes to this attribute do not affect existing Vpcs. If the value is changed to a number smaller than the current number of active UBR VPCs, no new UBR VPCs are admitted until the number of active UBR VPCs drops below the value of this attribute. The current number of active UBR VPCs is indicated by the Ubr/0 vpcUsage operational attribute. VALUES ( 16385 = sameAsCa )

This attribute specifies the maximum number of UBR Vccs that can be activated on this AtmIf, including UBR Vpt Vccs. The value must not exceed the maxVccs attribute of the parent CA component. If this attribute is specified as sameAsCa, the maximum number of Vccs is defined by the AtmIf/n CA maxVccs attribute. Changes to this attribute do not affect existing Vccs. If the value is changed to a number smaller than the current number of active UBR VCCs, no new UBR VCCs are admitted until the number of active UBR VCCs drops below the value of this attribute. The current number of active UBR VCCs is indicated by the Ubr/0 vccUsage operational attribute. VALUES ( 16385 = sameAsCa )

This attribute specifies the maximum number of UBR Vpts that can be activated on this AtmIf. The value must not exceed the maxVpts attribute of the parent CA component. If this attribute is specified as sameAsCa, the maximum number of Vpts is defined by the AtmIf/n CA maxVpts attribute. Changes to this attribute do not affect existing Vpts. If the value is changed to a number smaller than the current number of active UBR VPTs, no new UBR VPTs are admitted until the number of active UBR VPTs drops below the value of this attribute. The current number of active UBR VPTs is indicated by the Ubr/0 vptUsage operational attribute. VALUES ( 16385 = sameAsCa )

This attribute specifies the bandwidth pool which is to be used to support the unspecified bit rate (UBR) service category except for connections managed by a Vpt CA. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to UBR traffic. The percentage allocated to each bandwidth pool can be provisioned through the bandwidthPool attribute under the CA. The amount of bandwidth reserved for each UBR connection is specified in the minimumCellRate attribute. Enumeration: 'pool3': 3, 'pool2': 2, 'pool1': 1, 'pool5': 5, 'pool4': 4.

This attribute specifies the minimum cell rate (MCR) which is allocated from the UBR bandwidth pool for each UBR connection which is admitted using Connection Admission Control (CAC) except for connections managed by a Vpt CA. UBR connections normally are serviced on a best effort basis, but this attribute allows allocation of a default minimum bandwidth for each connection.

This attribute specifies the default maximum queue length for the emission queues used to buffer the traffic of the UBR service category. It is used as the basis for setting the discard thresholds on both common and per-VC queues. For the common queue, the discard thresholds are set at approximately 35, 75 and 90 percent of the value of this attribute for traffic at discard priority 3 (DP=3), DP=2 and DP=1 respectively. For per-VC queue, the actual limit may be reduced depending on the shaping rate of the connection (for standard Vpt Vccs, this is the shaping rate of the Vpt). The discard thresholds are set at approximately 35, 75 and 90 percent of the scaled queue limit for traffic at discard priority 3 (DP=3), DP=2 and DP=1 respectively. However, a reduction will never result in a value that is less than the value set for the minPerVcQueueLimit attribute. When the value of this attribute is autoConfigure, an appropriate value is selected based on the card type. It is set to 1792 for low speed cards such as DS1, E1 and IMA, set to 2304 for high speed CQC-based ATM cards such as JT2, DS3, E3 and OC3, and set to 10240 for high speed ATM IP cards such as 3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2 and 2pOC3MmAtm2. For the 1pOC12SmLrAtm card, the value is set to 4096. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components, and the valid range is from 5 to 30000 inclusive. For ATM IP FPs, the per-VC queue limit may be overridden for a permanent connection by specifying a value in the Vcd Tm or Vpd Tm txQueueLimit attribute. The operational value of the maximum length of a queue (common or per-VC) is indicated by the Vcc Tm, Vpc Tm, or Vpt Tm txQueueThresholds attribute. For standard Vpts, this attribute does not apply when using per-VC queuing and only applies when using common queueing. When using per-VC queueing, regardless of the Vpt's service category, standard Vpts use the AtmIf Ca NrtVbr txQueueLimit value as their default. This attribute does not apply to basic Vpts. VALUES ( 0 = autoConfigure )

This attribute specifies the minimum queue limit for the per-VC queues of connections of the UBR service category. The queue limit of a per-VC queue is obtained by scaling down the txQueueLimit based on the shaping rate of that queue (shaping rate for the connection, and for standard Vpt Vccs, the shaping rate of the Vpt). This produces a constant delay for various queue lengths. The txQueueLimit provides an upper bound while minPerVcQueueLimit provides the lower bound. The value of this attribute must not be greater than the value of the txQueueLimit attribute. If this service category is used by Trunks the value of minPerVcQueueLimit must be at least 88. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components. For the 1pOC12SmLrAtm card, this attribute does not apply since per-VC queueing is not available. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr minPerVcQueueLimit value as their default. To determine the queue limit of a standard Vpt Vcc, the txQueueLimit is scaled down by the Vpt shaping rate.

This attribute specifies the shaping rate to be used in computing the tolerable delay for per-VC queues of connections of the UBR service category. The delay is computed as the txQueueLimit divided by the value of this attribute. When the value of this attribute is autoConfigure, an appropriate default is selected based on the card type. It is set to 3685 for low speed cards such as DS1, E1 and IMA, set to 14740 for high speed cards such as JT2, DS3, E3 and OC3, and set to 65511 for high speed ATM IP cards such as 3pDS3Atm2, 3pE3Atm2, 2pOC3SmAtm2 and 2pOC3MmAtm2. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, the reference rate is set to 65511 for DS3 and OC3 channels, and set to 262044 for OC12 channels. For Apc- based cards the maximum value is 1416905. For all other cards, the maximum value is 943396. On CQC-based ATM cards, this attribute must be set to the same value for CA NrtVbr, Abr and Ubr components. For the 1pOC12SmLrAtm card, this attribute does not apply since per-VC queueing is not available. For Vpts, this attribute does not apply. Regardless of Vpt service category, standard Vpts always use the AtmIf Ca NrtVbr perVcQueueLimitReferenceRate value as their default. VALUES ( 0 = autoConfigure )

This attribute is not applicable and is ignored for CQC-based ATM cards. This attribute specifies the emission priority (EP) which is used to transmit traffic of the UBR service category. A lower numerical value for this attribute specifies a higher emission priority. 0 is the highest EP and 7 is the lowest. Cells at a higher emission priority receive higher preference for link bandwidth. EPs 0 and 1 are in the absolute priority range, and are unaffected by any minimum bandwidth guarantees. EPs 2 through 7 are in the guaranteed bandwidth range. Minimum bandwidth guarantee is specified in the AtmIf/n Ep/m component. Emission priority setting must comply with all of the following constraints: 1. The emission priority numbers must be in the following order: CBR <= rt-VBR <= nrt-VBR <= ABR <= UBR 2. Two different ATM service categories may share the same EP only if they are both shaped. 3. CBR and rt-VBR may be placed either in the absolute priority range (EP 0 or 1) or in the guaranteed bandwidth range (EP 2 through 7). 4. If both CBR and rt-VBR are shaped, rt-VBR must share the same EP with CBR or ABR. If either one of CBR or rt-VBR are not shaped, then they cannot share the same EP. 5. ABR service category is always deemed to be shaped. If nrt-VBR is shaped, it must share the same EP with ABR. If nrt-VBR is not shaped it must have a higher EP than ABR. 6. If UBR is shaped, it must share the same EP with ABR. If UBR is not shaped, it must have a lower EP than ABR. This attribute does not apply to basic Vpts, and standard Vpt Vccs.

This attribute specifies the default traffic shaping option for connections of the UBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to disabled, traffic shaping cannot be enabled for any UBR connection. On 1pOC12SmLrAtm cards, this attribute must be set to disabled. For CQC-based ATM cards, this attribute may be set to enabled only if the interface supports shaping, as defined by the perVcQueueInterfaces attribute in the AtmResourceControl Cqc Override component. If that component does not exist, this attribute must be set to disabled. If the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType indicates type 1 or 2, this attribute is ignored, and traffic shaping is not applicable for that connection. When this attribute is set to inverseUpc, traffic shaping for a connection is enabled according to card type and the value of the Vcc Tm, Vpc Tm, or Vpt Tm txTrafficDescType. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards, inverseUpc shaping is not available. If this attribute is set to inverseUpc, and the txTrafficDescType is 3, 4, or 5, linear traffic shaping is enabled. Linear traffic shaping uses a single static traffic shaping rate. On CQC-based ATM FPs, if this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, linear traffic shaping is enabled. On ATM IP FPs, if this attribute is set to inverseUpc, and the txTrafficDescType is 6, 7, or 8, inverse-UPC (also referred to as VBR or dual leaky bucket) traffic shaping is enabled. Inverse-UPC traffic shaping can burst above the sustained cell rate to the peak cell rate for the duration defined by maximum burst size. Inverse- UPC traffic shaping exactly conforms to the requirements of a dual leaky bucket UPC enforcer. When this attribute is set to enabled and the txTrafficDescType is 3, 4, 5, 6, 7, or 8, traffic shaping for a connection is enabled using linear shaping. Enabling or disabling traffic shaping may require a matching change to the emissionPriority attribute and unshapedTransmitQueueing attribute for this service category. Refer to those attributes for the complete description of the interactions. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'inverseUpc': 6, 'enabled': 5.

This attribute specifies the shaping recoup policy for the UBR service category. This is the policy which is used to recoup shaping opportunities which are lost when more than one connection schedules a cell for the same transmit opportunity. In this case, one connection is scheduled, and the cell from the other connection is delayed by one cell time. This attribute affects how the transmit time is calculated for the next cell on the delayed connection. This attribute is ignored if this service category is not shaped. When the connection which was delayed schedules the next cell to transmit, it may calculate the time as a difference from either the previous actual cell transmit time, or the time when the previous cell should have been transmitted. Setting this attribute to maximumEfficiency results in each connection trying to recoup or regain any delays in scheduling. The transmit time from the next cell is calculated from the time when the cell should originally have been sent. Cell delay variation (CDV) occurs in this case since the cells are sent with less than the shaping delay between them. However, in general the shaper recovers (recoups) lost opportunities and improves efficiency. Setting this attribute to minimumCdv results in connections not trying to recoup or regain any delays in scheduling. The transmit time for the next cell is calculated from the time when the previous cell was actually transmitted. This minimizes CDV, but results in missed cell opportunities. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'maximumEfficiency': 1, 'minimumCdv': 0.

This attribute specifies the default queuing option for unshaped connections of the UBR service category. This attribute controls whether common or per-VC queueing is used. Per-VC queueing means that each connection has its own buffering and queue limits. Common queueing means that cells are queued in First In First Out order on a common queue. The common queue has one set of congestion control levels for all cells enqueued on it. For ATM IP cards, there is one common queue for the UBR service category. For CQC-based ATM cards, there is one common queue which is shared by the nrt-VBR, ABR and UBR service categories. For 1pOC12SmLrAtm cards this attribute must be set to common or autoConfigure. This attribute cannot be set to perVc since per-Vc queueing is not available on the 1pOC12SmLrAtm card. The value autoConfigure is interpreted to mean common queueing. For ATM IP cards, if traffic shaping for this service category is disabled, this attribute may take any of the three values. In this case, the value autoConfigure is interpreted to mean per-VC queueing. For ATM IP cards, if traffic shaping for this service category is not disabled, the only permitted values are perVc and autoConfigure. In this case, the result is that all connections use per-VC queueing. For CQC-based ATM cards, if the perVcQueueInterfaces attribute of the Lp Eng Arc Cqc component permits shaping for this interface, then this attribute may take any of the three values. In this case, the value autoConfigure is interpreted to mean per-VC queueing. For 4pOC12SmIrAtm and 4pOC12SmLrAtm cards only perVc queueing is supported. All other attribute values are ignored. For CQC-based ATM cards, if the perVcQueueInterfaces attribute of the Lp Eng Arc Cqc component does not permit shaping for this interface, then this attribute may take the values common or autoConfigure. In this case, the value autoConfigure is interpreted to mean common queueing. If this attribute is set to autoConfigure, an override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The opUnshapedTransmitQueueing attribute of this component indicates whether the transmit queueing is perVc or common. This attribute does not apply to basic Vpts, andstandard Vpt Vccs. Enumeration: 'perVc': 0, 'autoConfigure': 2, 'common': 1.

This attribute specifies the default usage parameter control (UPC) option for connections of the UBR service category. This attribute is ignored if the rxTrafficDescriptorType indicates 1 or 2. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. When this attribute is set to enforced, UPC is enforced for each connection. When UPC is enforced, non-conforming cells are either tagged or discarded depending on the rxTrafficDescriptorType. On ATM IP FPs, when this attribute is set to monitored, UPC conformance checking is performed, except, instead of the non- conforming cells being tagged or discarded, they are merely counted in the UPC violations counts, and passed on unchanged. On CQC-based ATM FPs, when this attribute is set to monitored, it has the same effect as setting it to disabled. When this attribute is set to disabled, UPC is disabled on the receive path for all UBR connections. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4.

This attribute specifies the policy which is applied when calculating the fairness weight for unshaped connections of the UBR service category. The fairness weight for a connection determines the relative amount of bandwidth which that connection obtains, compared to other connections in the same service category. Connections with equal weight get equal transmit opportunities. Connections with higher weights get more transmit opportunities compared with connections that have lower weights. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. The fairness weight for a connection is directly proportional to the value of one of the traffic descriptor parameters for that connection. This attribute specifies which traffic descriptor parameter is used for connections of the UBR service category. This attribute is ignored on CQC-based ATM cards. This attribute is also ignored on ATM IP cards if unshapedTransmitQueueing is set for common queuing. If this attribute is set to mcr, the fairness weight is proportional to the default minimum cell rate (MCR) for UBR connections. If the default minimum cell rate is 0, all UBR connections get a minimum weight, which is 1. If this attribute is set to pcr, the fairness weight is proportional to the transmit peak cell rate (PCR) of a connection. Connections with a higher PCR have a higher fairness weight. Connections with txTrafficDescType 1 or 2 get a minimum weight, which is 1. If this attribute is set to ecr, the fairness weight is proportional to the equivalent cell rate (ECR) of a connection as calculated by connection admission control (CAC). Connections with a higher ECR have a higher fairness weight. Connections with an ECR of 0 get a minimum weight, which is 1. The weight of a connection is visible in the Vcc Tm, Vpc Tm, or Vpt Tm weight attribute. This attribute does not apply to basic Vpts, and standard Vpt Vccs. Enumeration: 'pcr': 2, 'mcr': 0, 'ecr': 3.

This attribute specifies the default of whether to force tagging (CLP=1) of all cells for all UBR connections. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. This attribute is not supported by 4pOC12SmIrAtm and 4pOC12SmLrAtm cards. When this attribute is set to enabled, CLP is set to 1 for all cells in the transmit direction. This is in conformance with the ATM Forum TM4.0 UBR.2 service definition. Force tagging is only supported on ATM IP FPs. On CQC-based ATM FPs, this attribute must be set to disabled. When this attribute is set to disabled, CLP is unchanged for all cells in the transmit direction. This is in conformance with the ATM Forum TM4.0 UBR.1 service definition. This attribute never applies to any type of Vpt. Enumeration: 'disabled': 1, 'enabled': 0.

This attribute specifies the default cell delay variation tolerance (CDVT) for all connections of the UBR service category. An override to this default may be specified for a provisioned connection under the Vcd Tm or Vpd Tm component. If Usage Parameter Control (UPC) is enabled for a connection, CDVT is used by the UPC function to decide whether a cell is conforming or non-conforming based on the connection's traffic descriptor type. The larger the CDVT value, the more tolerant is the UPC of bandwidth usage beyond the traffic contract.

This attribute specifies the default holding priority which applies to SVP and SVC UBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the default holding priority which applies to SVC UBR point-to-multipoint connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This attribute does not apply to Vpt Vccs. When bandwidth fluctuates, the entire Vpt, along with all Vpt Vccs is released as a unit, according to the Vpt's holdingPriority. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This group contains operational attributes for the UBR service category.

An entry in the mscAtmIfCAUbrOperTable.

This attribute indicates the state of transmit queueing for unshaped UBR connections. A value of perVc indicates that any unshaped connections use per- VC queueing. A value of common indicates that traffic for unshaped connections uses the common queue which corresponds to the EP for this service category. Enumeration: 'perVc': 0, 'common': 1.

This attribute indicates the number of active UBR Vpcs under this interface. It includes switched and permanent connections.

This attribute indicates the number of active UBR Vccs under this interface. It includes switched and permanent connections, and Vpt Vccs.

This attribute indicates the number of active UBR Vpts under this interface.

This attribute indicates the Early Packet Discard (EPD) offset which is currently in use for this service category. The EPD offset is used to derive the EPD thresholds for each CC level. Any connection under this service category which requires the txPacketWiseDiscard feature must specify a transmit queue limit which is at least 5.71 times this offset. This ensures that the derived Epd threshold will never be less than 17.5 % of the transmit queue limit. If this is not done, txPacketWiseDiscard for the connection will be automatically disabled. The value of this EPD offset is specified under the lp/x eng arc aqm ov component.

This group contains provisioned attributes which specify the behavior of Connection Admission Control (CAC) for the ATM connections configured on an ATM interface. Note that the names of some of the attributes follow the conventions of UNI 4.0 for forward compatibility reasons. This does not imply conformance in general with the UNI 4.0 specification.

An entry in the mscAtmIfCAProvTable.

This attribute specifies the maximum number of Vpcs that can be activated on this AtmIf. If the AtmIf is linked to a LogicalProcessor of cardType other than 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, 2pJ6MAtm, the sum of (maxVccs + maxVpcs +1) across all spared AtmIfs linked to that Lp must not exceed the protectedConnectionPoolCapacity attribute of the Arc component. The sum of (maxVpts * 3) across all spared AtmIfs and (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all unspared AtmIfs linked to that Lp must not exceed connectionPoolCapacity attribute of the Arc component. Note that 3 connections are used for every standard Vpt and 2 for each basic Vpt. Vpts on a spared AtmIf are considered unspared, their resources are allocated from connectionPoolCapacity. If the Arc component doesn't exist, the default value of the Arc connectionPoolCapacity and protectedConnectionPoolCapacity attribute is used as the limit. This attribute has been obsoleted and its value migrated to the maxVpcs attribute.

This attribute specifies the maximum number of usable Vccs (and Vpt Vccs) that can be configured on this AtmIf. The value must not exceed the number of non-reserved Vcc identifiers in the Vcc space supported by this AtmIf (which is specified by the ConnectionMapping component). Furthermore, if the AtmIf is linked to a LogicalProcessor of cardType other than 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, 2pJ6MAtm, the sum of (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all spared AtmIfs linked to that Lp must not exceed the protectedConnectionPoolCapacity attribute of the Arc component. The sum of (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all unspared AtmIfs linked to that Lp must not exceed connectionPoolCapacity attribute of the Arc component. Note that 3 connections are used for every standard Vpt and 2 for each basic Vpt. If the Arc component doesn't exist, the default value of the Arc connectionPoolCapacity and protectedConnectionPoolCapacity attribute is used as the limit. If this attribute is set to autoConfigure, then on 32 port Multi- Service Access cards its value is configured as 100, and on all other cards it is 255. VALUES ( 65535 = autoConfigure )

This attribute specifies the guaranteed number of switched multicast branches that can be activated on this AtmIf, including those activated beneath a Vpt. The sum of minMulticastBranches and the number of provisioned branches listed in the nextHop attribute of all Mnrps across all spared AtmIfs linked to that Lp must not exceed the protectedMcstBranchesCapacity attribute of the Arc component. The sum of minMulticastBranches and the number of provisioned branches listed in the nextHop attribute of all Mnrps across all unspared AtmIfs linked to that Lp must not exceed multicastBranchesCapacity attribute of the Arc component. For CQC-based ATM cards, the value of the attribute can not exceed 10752. If this value is non zero, the Arc component must exist and have multicastBranchesCapacity set to a value greater than or equal to this attribute.

This attribute specifies the maximum number of provisionable multicast branches that can be activated on this AtmIf, including those activated beneath a Vpt. If this attribute is set to a value other than autoConfigure, it must be greater than or equal to the value of minMulticastBranches of this AtmIf. For CQC-based ATM cards, the value of the attribute can not exceed 10752. When this attribute is set to autoConfigure, an appropriate value is selected based on the card type. It is set to 10752 for all CQC-based ATM cards, and to 16384 for ATM IP cards. VALUES ( 0 = autoConfigure )

This attribute specifies the maximum number of Vpts that can be activated on this AtmIf. If the AtmIf is linked to a LogicalProcessor of cardType other than 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, 2pJ6MAtm, the sum of (maxVccs + maxVpcs +1) across all spared AtmIfs linked to that Lp must not exceed the protectedConnectionPoolCapacity attribute of the Arc component. The sum of (maxVpts * 3) across all spared AtmIfs and (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all unspared AtmIfs linked to that Lp must not exceed connectionPoolCapacity attribute of the Arc component. Note that 3 connections are used for every standard Vpt and 2 for each basic Vpt. Vpts on a spared AtmIf are considered unspared, their resources are allocated from connectionPoolCapacity. If the Arc component doesn't exist, the default value of the Arc connectionPoolCapacity and protectedConnectionPoolCapacity attribute is used as the limit. This attribute has been obsoleted and its value migrated to the maxVpts attribute.

This attribute specifies the default lower boundary for VCIs which are automatically allocated for a switched Vcc. A VCI number is automatically allocated when a switched Vcc does not request a specific VCI number. This attribute has been obsoleted and its value migrated to the minAutoSelectedVciForVpiZero attribute.

This attribute specifies the minimum VCI value which is automatically allocated for a switched Vcc with VPI value of zero. A VCI number is automatically allocated when a switched Vcc does not request a specific VCI number. This value also applies to switched Vccs created beneath Vpt/0.

This attribute specifies the minimum VCI value which is automatically allocated for a switched Vcc with a non-zero VPI value. A VCI number is automatically allocated when a switched Vcc does not request a specific VCI number. This value also applies to switched Vccs created beneath a Vpt.

This attribute specifies which ATM service categories are permitted on this interface for SVCs. The value of this attribute does not affect control VCCs, such as signalling and ILMI channels. If the value is empty, no SVCs may use this interface. This attribute has been obsoleted and its value migrated to the permittedAtmServiceCategories attribute. Description of bits: unspecifiedBitRate(0) constantBitRate(1) rtVariableBitRate(2) nrtVariableBitRate(3)

This attribute has been obsoleted and migrated under the Cbr subcomponent. In addition, notApplicable is no longer a valid value of the new attribute. This attribute specifies the bandwidth pool which is to be used to support the constant bit rate (CBR) service category. When the user does not intend to support the CBR service category, this attribute should be set to notApplicable. Otherwise, one of the three bandwidth pools should be selected. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to CBR traffic. Enumeration: 'pool3': 3, 'notApplicable': 0, 'pool1': 1, 'pool2': 2.

This attribute has been obsoleted and migrated under the Cbr subcomponent. This attribute specifies the cell delay variation tolerance (CDVT) which is to be applied to the entire ATM Interface for CBR traffic.

This attribute has been obsoleted and migrated under the Cbr subcomponent. In addition, the type and range of the new attribute have been changed. This attribute specifies the tolerable cell loss ratio (CLR) for CBR traffic. The number is the logarithm (base 10) of the CLR. In other words if the target CLR = 1E-10 then cbrCellLossRatio = -10. This number must be the same as the vbrRtCellLossRatio since CBR and rt-VBR traffic have the same discard priority. The cbrCellLossRatio is used by the Connection Admission Control (CAC) algorithm to compute the required (equivalent) cell rate for CBR connections. There is a trade-off between the service category CLR and the achievable link utilization. To guarantee an excellent service category, the CLR should be as small as possible (e.g., 1E-10). However, a smaller CLR results in a larger equivalent cell rate for a given connection and hence a lower link utilization.

This attribute has been obsoleted and migrated under the Cbr subcomponent. This attribute specifies the default holding priority which applies for SVC CBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute has been obsoleted and migrated under the RtVbr subcomponent. This attribute specifies the default holding priority which applies for SVC rt-VBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute has been obsoleted and migrated under the NrtVbr subcomponent. This attribute specifies the default holding priority which applies for SVC nrt-VBR connections. It takes a value from 0 (highest priority) to 4 (lowest priority). In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute has been obsoleted and migrated under the RtVbr subcomponent. In addition, notApplicable is no longer a valid value of the new attribute. This attribute specifies the bandwidth pool which is to be used to support the variable bit rate real time (rt-VBR) service category. When the user does not intend to support the rt-VBR service category, this attribute should be set to notApplicable. Otherwise, one of the three bandwidth pools should be selected. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to rt-VBR traffic. Enumeration: 'pool3': 3, 'notApplicable': 0, 'pool1': 1, 'pool2': 2.

This attribute has been obsoleted and migrated under the RtVbr subcomponent. This attribute specifies the cell delay variation tolerance (CDVT) which is to be applied to the entire ATM Interface for rt-VBR traffic.

This attribute has been obsoleted and migrated under the RtVbr subcomponent. In addition, the type and range of this attribute has been changed. This attribute specifies the tolerable cell loss ratio (CLR) for rt- VBR traffic. The number is the logarithm (base 10) of the CLR. In other words if the target CLR = 1E-10 then vbrRtCellLossRatio = - 10. This number must be the same as the cbrCellLossRatio since CBR and rt-VBR traffic have the same discard priority. The vbrRtCellLossRatio is used by the Connection Admission Control (CAC) algorithm to compute the required (equivalent) cell rate for rt-VBR connections. This number must be less than or equal to the vbrNrtCellLossRatio, since rt-VBR traffic has a higher discard priority. There is a trade-off between the service category CLR and the achievable link utilization. To guarantee an excellent service category, the CLR should be as small as possible (e.g., 1E-10). However, a smaller CLR results in a larger equivalent cell rate for a given connection and hence a lower link utilization.

This attribute has been obsoleted and migrated under the NrtVbr subcomponent. In addition, notApplicable is no longer a valid value of the new attribute. This attribute specifies the bandwidth pool which is to be used to support the variable bit rate non-real time (nrt-VBR) service category. When the user does not intend to support the nrt-VBR, this attribute should be set to notApplicable. Otherwise, one of the three bandwidth pools should be selected. The percentage of link capacity reserved for the given bandwidth pool is the maximum bandwidth that can be allocated to nrt-VBR traffic. Enumeration: 'pool3': 3, 'notApplicable': 0, 'pool1': 1, 'pool2': 2.

This attribute has been obsoleted and migrated under the NrtVbr subcomponent. This attribute specifies the cell delay variation tolerance (CDVT), which is to be applied to the entire ATM Interface for nrt-VBR traffic.

This attribute specifies the maximum number of Vpcs that can be activated on this AtmIf. If the AtmIf is linked to a LogicalProcessor of cardType other than 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, 2pJ6MAtm, the sum of (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all spared AtmIfs linked to that Lp must not exceed the protectedConnectionPoolCapacity attribute of the Arc component. The sum of (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all unspared AtmIfs linked to that Lp must not exceed connectionPoolCapacity attribute of the Arc component. Note that 3 connections are used for every standard Vpt and 2 for each basic Vpt. If the Arc component doesn't exist, the default value of the Arc connectionPoolCapacity and protectedConnectionPoolCapacity attribute is used as the limit. If this attribute is set to autoConfigure, then on 32 port Multi- Service Access cards its value is configured as 16, and on all other cards it is 128. VALUES ( 65535 = autoConfigure )

This attribute specifies the maximum number of Vpts that can be activated on this AtmIf. If the AtmIf is linked to a LogicalProcessor of cardType other than 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, 2pJ6MAtm, the sum of (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all spared AtmIfs linked to that Lp must not exceed the protectedConnectionPoolCapacity attribute of the Arc component. The sum of (maxVccs + maxVpcs + (maxVpts * 3) + 1) across all unspared AtmIfs linked to that Lp must not exceed connectionPoolCapacity attribute of the Arc component. Note that 3 connections are used for every standard Vpt and 2 for each basic Vpt. If the Arc component doesn't exist, the default value of the Arc connectionPoolCapacity and protectedConnectionPoolCapacity attribute is used as the limit. If this attribute is set to autoConfigure, then on 32 port Multi- Service Access cards its value is configured as 16, and on all other cards it is 128. VALUES ( 65535 = autoConfigure )

This attribute has been obsoleted and migrated under the NrtVbr subcomponent. In addition, the type and range of new attribute has been changed. This attribute specifies the tolerable cell loss ratio (CLR) for nrt- VBR traffic. The number is the logarithm (base 10) of the CLR. In other words if the target CLR = 1E-10 then vbrNrtCellLossRatio = - 10.This number must be greater than or equal to vbrRtCellLossRatio since rt-VBR traffic has a higher discard priority. The vbrNrtCellLossRatio is used by the Connection Admission Control (CAC) algorithm to compute the required (equivalent) cell rate for nrt-VBR connections. There is a trade-off between the service category CLR and the achievable link utilization. To guarantee an excellent service category, the CLR should be as small as possible (e.g., 1E-10). However, a smaller CLR results in a larger equivalent cell rate for a given connection and hence a lower link utilization.

This attribute is obsolete in P6.0, and has been migrated to the CA Ubr/0 maxVccs and maxVpcs attributes. This attribute specifies the maximum number of unspecified bit rate (UBR) connections which are to be admitted managed by this CA. This number is enforced by the connection admission control (CAC) algorithm for this AtmIf.

This attribute specifies the minimum VPI value which will be automatically allocated for a switched Vpc. A VPI number is automatically allocated when a switched Vpc does not request a specific VPI number.

This attribute specifies which ATM service categories are permitted on this interface for SVPs and SVCs. The value of this attribute does not affect control VCCs, such as signalling and ILMI channels. If the value is empty, no non-control SVPs or SVCs will use this interface. This attribute is ignored for the admission of provisioned VCCs, VPCs, VPTs, S-PVCs, and S-PVPs. The value of the permittedAtmServiceCategories in a VPT CA overrides this AtmIf CA setting for all the given VPT's VCCs. Description of bits: unspecifiedBitRate(0) constantBitRate(1) rtVariableBitRate(2) nrtVariableBitRate(3)

This attribute specifies the maximumVPI value which will be automatically allocated for a switched Vpc or Vcc. A VPI number is automatically allocated when a switched Vpc or Vcc does not request a specific VPI number.

This attribute specifies the maximum VCI value which is automatically allocated for a switched Vcc. A VCI number is automatically allocated when a switched Vcc does not request a specific VCI number. This value also applies to switched Vccs created beneath Vpt/0.

This attribute specifies the maximum VCI value which is automatically allocated for a switched Vcc. A VCI number is automatically allocated when a switched Vcc does not request a specific VCI number. This value also applies to switched Vccs created beneath non zero Vpts.

This group contains operational attributes giving statistics about the ATM connections configured on an ATM interface.

An entry in the mscAtmIfCAOperTable.

This attribute indicates the maximum number of VCC connections that can be supported on this interface. The value includes both provisioned and dynamic connections. The value is determined from the provisioned attribute maxVccs.

This attribute indicates the number of permanent Vpcs that are currently provisioned on this interface.

This attribute indicates the number of permanent Vpts that are currently provisioned on this interface.

This attribute indicates the number of permanent Vccs that are currently provisioned on this interface (this includes Vccs having SrcPvc subcomponents). Vpt Vccs are also included in this count.

This attribute indicates the number of switched Vccs that are currently active on this interface. Vpt Vccs are also included in this count.

This attribute indicates the number of multicast branches used in switched Vccs, including Vpt Vccs, that are currently active on this interface. The sum of this attribute for all AtmIf components linked to an Lp added to the sum of permanentMulticastBranches for all AtmIf components linked to the same Lp gives the value of multiCastBranchesUsage in the Arc component.

This attribute indicates the number of multicast branches used in permanent Vccs and Vpcs that are currently active on this interface. The sum of this attribute for all AtmIf components linked to an Lp added to the sum of switchedMulticastBranches for all AtmIf components linked to the same Lp gives the value of multiCastBranchesUsage in the Arc component.

This attribute indicates the number of troubled Vpcs on this interface. A Vpc is 'troubled' if its operational troubled attribute has the value yes.

This attribute indicates the number of troubled Vpts on this interface. A Vpt is 'troubled' if its operational troubled attribute has the value yes.

This attribute indicates the number of troubled Vccs on this interface. A Vcc is 'troubled' if its operational troubled attribute has the value yes.

This attribute is historical in P6.0. Refer instead to the vccUsage and vpcUsage under the AtmIf CA Ubr component. This attribute indicates the available UBR connections. Its value is ubrMaxConnections minus the number of admitted connections.

This attribute indicates the number of enabled VCCs, VPCs, and VPTs in this AtmIf. An example of a VCC not in the enabled state is a Vcc with a Test subcomponent where the test is not started. Each Vcc or Vpc is counted as 1 connection. Each basic Vpt is counted as 2 connections and each standard Vpt is counted as 3 connections. Each connection appropriately reduces the number of connections indicated in Arc totalConnectionPoolAvailable and increases the number of connections indicated in Arc totalConnectionPoolUsage.

This attribute indicates the number of switched Vpcs that are currently active on this interface.

This attribute indicates the maximum number of VPC connections that can be supported on this interface. The value includes both provisioned and dynamic connections. The value is determined from the provisioned attribute maxVpcs.

This attribute indicates the maximum number of VPT connections that can be supported on this interface. The value includes both provisioned and dynamic connections. The value is determined from the provisioned attribute maxVpts.

This group contains the operational attributes indicating the total number of connections on the interface with active Cell Loss Ratio (CLR) and Availability Ratio (AR) measurements on the interface.

An entry in the mscAtmIfCAPmTable.

This attribute indicates the total number of connections on the interface receiving OAM Forward Performance Monitoring (FPM) cells on the interface.

This attribute indicates the total number of connections receiving OAM Backward Reporting (BR) cells on the interface.

This attribute indicates the total number of connections receiving OAM Continuity Check (CC) cells on the interface.

Link capacity is partitioned into five bandwidth pools. This attribute specifies the percentage of link bandwidth that is allowed for each pool. The percentage for each pool ranges from 0% to 12,800%. This allows for both under and over subscription of the link. Under subscription occurs when the sum of the percentages assigned to the five pools is less than 100%. Over subscription occurs when the sum of the percentages for the five pools exceeds 100%.

An entry in the mscAtmIfCABwPoolTable.

This variable represents the mscAtmIfCABwPoolTable specific index for the mscAtmIfCABwPoolTable.

This variable represents an individual value for the mscAtmIfCABwPoolTable.

This attribute indicates the total requested bandwidth from bandwidthPool. This attribute does not include bandwidth for ATM networking signalling connections, or bandwidth for connections managed by a Vpt CA. Its value is the sum of the equivalent cell rates (ECR) for connections which are admitted, and for connections which are requesting admission but have not yet been admitted.

An entry in the mscAtmIfCAPoolRequBwTable.

This variable represents the mscAtmIfCAPoolRequBwTable specific index for the mscAtmIfCAPoolRequBwTable.

This variable represents an individual value for the mscAtmIfCAPoolRequBwTable.

This attribute indicates the total admitted bandwidth in bandwidthPool. This attribute does not include bandwidth for ATM networking signalling connections, or bandwidth for connections managed by a Vpt CA. Its value is the sum of the equivalent cell rates (ECR) of the admitted connections.

An entry in the mscAtmIfCAPoolAdmitBwTable.

This variable represents the mscAtmIfCAPoolAdmitBwTable specific index for the mscAtmIfCAPoolAdmitBwTable.

This variable represents an individual value for the mscAtmIfCAPoolAdmitBwTable.

This attribute indicates the total available bandwidth in bandwidthPool. Its value is the link capacity reduced by the sum of the equivalent cell rates (ECR) of the admitted connections.

An entry in the mscAtmIfCAPoolAvailBwTable.

This variable represents the mscAtmIfCAPoolAvailBwTable specific index for the mscAtmIfCAPoolAvailBwTable.

This variable represents an individual value for the mscAtmIfCAPoolAvailBwTable.

This attribute indicates the total bandwidth from bandwidthPool which is specified by provisioned connections except for those managed by a Vpt CA. Its value is the sum of the equivalent cell rates (ECR) of the provisioned connections. Provisioned connections include provisioned AtmIf Vccs, AtmIf Vpcs, AtmIf Vpts, Vpt Vccs, and Vccs or Vpcs with a Src component under them.

An entry in the mscAtmIfCAPoolProvBwTable.

This variable represents the mscAtmIfCAPoolProvBwTable specific index for the mscAtmIfCAPoolProvBwTable.

This variable represents an individual value for the mscAtmIfCAPoolProvBwTable.

This attribute indicates the total number of connections which have currently requested admission in bandwidthPool but are not yet admitted. This attribute does not include ATM networking signalling connections, or connections managed by a Vpt CA.

An entry in the mscAtmIfCAPoolWaitAdmConnsTable.

This variable represents the mscAtmIfCAPoolWaitAdmConnsTable specific index for the mscAtmIfCAPoolWaitAdmConnsTable.

This variable represents an individual value for the mscAtmIfCAPoolWaitAdmConnsTable.

This attribute indicates the total number of connections which are currently admitted in bandwidthPool. This attribute does not include ATM networking signalling connections, or connections managed by a Vpt CA.

An entry in the mscAtmIfCAPoolAdmConnsTable.

This variable represents the mscAtmIfCAPoolAdmConnsTable specific index for the mscAtmIfCAPoolAdmConnsTable.

This variable represents an individual value for the mscAtmIfCAPoolAdmConnsTable.

This attribute indicates the total available bandwidth in bandwidthPool. A positive number indicates that there is still bandwidth available in the pool which has not been allocated. A negative value indicates that some bandwidth-elastic provisioned connections are running in reduced mode, where their allocated bandwidth is below their originally allocated ECR. The negative amount is equal to the sum of the bwReduction attribute for all connections under this bandwidthPool.

An entry in the mscAtmIfCAPoolAvailableBwTable.

This variable represents the mscAtmIfCAPoolAvailableBwTable specific index for the mscAtmIfCAPoolAvailableBwTable.

This variable represents an individual value for the mscAtmIfCAPoolAvailableBwTable.

This entry controls the addition and deletion of mscAtmIfVpc components.

A single entry in the table represents a single mscAtmIfVpc component.

This variable is used as the basis for SNMP naming of mscAtmIfVpc components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpc tables.

This variable represents the index for the mscAtmIfVpc tables.

This entry controls the addition and deletion of mscAtmIfVpcVpd components.

A single entry in the table represents a single mscAtmIfVpcVpd component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcVpd components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcVpd tables.

This variable represents the index for the mscAtmIfVpcVpd tables.

This entry controls the addition and deletion of mscAtmIfVpcVpdTm components.

A single entry in the table represents a single mscAtmIfVpcVpdTm component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcVpdTm components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcVpdTm tables.

This variable represents the index for the mscAtmIfVpcVpdTm tables.

This entry controls the addition and deletion of mscAtmIfVpcVpdTmAbr components.

A single entry in the table represents a single mscAtmIfVpcVpdTmAbr component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcVpdTmAbr components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcVpdTmAbr tables.

This variable represents the index for the mscAtmIfVpcVpdTmAbr tables.

This group contains provisioned attributes for the ABR ATM connections configured on an ATM interface.

An entry in the mscAtmIfVpcVpdTmAbrProvTable.

This attribute specifies the Initial Cell Rate (ICR) parameter for this connection. ICR is the rate at which a source should send initially and after an idle period. When this attribute is set to sameAsCa, the initial cell rate is determined by the AtmIf CA Abr/0 icr attribute. When the value of this attribute is set to useMcr, ICR is set to the same value as the Minimum Cell Rate (MCR) for the connection. When the value of this attribute is set to usePcr, ICR is set to the same value as the Peak Cell Rate (PCR) for the connection. If this attribute is specified less than the MCR of the connection, then the MCR is used as the ICR. If this attribute is specified more than PCR of the connection, then PCR is used as the ICR. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch. VALUES ( 16777216 = sameAsCa 16777217 = useMcr 16777218 = usePcr )

This attribute specifies the Transient Buffer Exposure (TBE) for this connection. TBE is the negotiated number of cells that the network would like to limit the source to send during start-up periods, before the first Resource Management (RM) cell returns. TBE divided by fixedRoundTripTime determines an upper bound for the operational value of initialCellRate, the rate at which a source should send initially and after an idle period. TBE divided by maxCellsPerRmCell specifies the operational value of forwardRmCellLimit, the limit of the number of forward Resource Management (RM) cells which may be sent in the absence of received backward RM cells. This attribute is ignored under all conditions where the operational attribute abrConnectionType is set to erSwitch.

This attribute specifies the Fixed Round-Trip Time (FRTT) parameter for this connection. FRTT is the sum of the fixed and propagation delays from the source to a destination and back. The value of transientBufferExposure divided by the value of FRTT (in seconds) determines an upper bound for the operational value of initialCellRate, the rate at which a source should send initially and after an idle period. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch.

This attribute specifies the Rate Decrease Factor (RDF) for this connection. The RDF value is computed by using the provisioned value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 8, RDF is 2E-8 = 1/256. RDF controls the amount by which the cell transmission rate may decrease upon receipt of a backward Resource Management (RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) field set to 1, the Allowed Cell Rate (ACR) value would be reduced by the amount (RDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Rate Increase Factor (RIF) for this connection. The RIF value is computed by using the provisioned value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 6, RIF is 2E-6 = 1/64. RIF controls the amount by which the cell transmission rate may increase upon receipt of a backward Resource Management (RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) and the No Increase (NI) fields both set to 0, the Allowed Cell Rate (ACR) value would be increased by the amount (RIF*ACR). The ACR is not allowed to exceed the Peak Cell Rate (PCR), in which case the ACR is set to PCR. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the maximum number of cells an ABR source may transmit for each forward Resource Management (RM) cell. The count of the cells transmitted includes data cells, OAM cells, backward RM cells, and the forward RM cell. A value of 2 is not recommended although it is permitted according to the ATM Forum standard. When this attribute is set to a value of 2, it is possible that only one forward and one backward RM cell are repeatedly transmitted, and all data traffic is queued up indefinitely. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the TRM parameter for this connection. TRM provides an lower bound on the time interval between forward Resource Management (RM) cells for an ABR source. Since the last forward RM cell was sent, if at least TRM time has elapsed since and at least two other cells have been sent, then the next cell to be transmitted would be a forward RM cell. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. The provisioned value of 781 is signalled as TRM = 0, in the ABR Additional Parameters Information Element. 1563 is signalled as TRM = 1. 3125 is signalled as TRM = 2. 6250 is signalled as TRM = 3. 12500 is signalled as TRM = 4 25000 is signalled as TRM = 5. 50000 is signalled as TRM = 6. 100000 is signalled as TRM = 7. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Cutoff Decrease Factor (CDF) parameter for this connection. When the value of this attribute is non-zero, CDF is computed as the inverse of the value. For example, if the value is 32, the value of CDF is 1/32. When the value of this attribute is 0, CDF is also zero. CDF controls the decrease in the Allowed Cell Rate (ACR) associated with the CRM parameter, the limit of the number of forward Resource Management (RM) cells which may be sent in the absence of received backward RM cells. When this limit is crossed, the ACR value would be decreased by the amount (CDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. The value of CRM is indicated by the forwardRmCellLimit attribute. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Allowed Cell Rate Decrease Time Factor (ADTF) parameter for this connection. ADTF is the maximum time interval permitted between sending forward Resource Management (RM) cells before the Allowed Cell Rate (ACR) is decreased to initialCellRate. In other words, if the source does not transit a forward RM cell for the period specified by adtf, it reduces its ACR to the value of its initialCellRate. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies an upper bound on the delay after which the rate change induced by a backward Resource Management (RM) cell departing from this connection point (in the backward direction) is expected to be observed at this connection point (in the forward direction). This upper bound may be approximated as the sum of the round trip fixed and propagation delays and the maximum queuing delays between the ABR source and this interface. The value of this attribute is used in policing an ABR connection using the Dynamic General Cell Rate Algorithm (DGCRA). A larger value for this attribute implies a more lenient policer. When there is a reduction in the Allowed Cell Rate (ACR), the policer waits for a correspondingly longer period of time before it enforces at the new cell rate. The value of this attribute must not be less than the dgcraMinimumDelay attribute. VALUES ( 16777216 = sameAsCa )

This attribute specifies a lower bound on the delay after which the rate change induced by a backward Resource Management (RM) cell departing from this connection point (in the backward direction) is expected to be observed at this connection point (in the forward connection). This lower bound may be approximated as the sum of the round trip fixed and propagation delays between the ABR source and this interface. The value of this attribute is used in policing an ABR connection using the Dynamic General Cell Rate Algorithm (DGCRA). A smaller value for this attribute implies a more lenient policer. When there is a increase in the Allowed Cell Rate (ACR), the policer waits for a correspondingly shorter period of time before it enforces at the new cell rate. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Allowed Cell Rate Decrease Time Factor (ADTF) of the far end ABR source. The value specified should be the same as the ADTF parameter at the far end of this ABR connection. The value of this attribute is used in policing an ABR connection using the Dynamic Generic Cell Rate Algorithm (DGCRA). A larger value for this attribute implies a more lenient policer. When the delay between two consecutive forward Resource Management (RM) cells received at this interface corresponds to a value greater than the value of this attribute, the policer begins to limit enforce the incoming traffic at the initial cell rate (ICR) of the far end, as specified by the farEndInitialCellRate attribute.

This attribute specifies the Initial Cell Rate (ICR) of the far end ABR source. The value specified should be the same as the ICR parameter at the far end of this ABR connection. The value of this attribute is used in policing an ABR connection using the Dynamic Generic Cell Rate Algorithm (DGCRA). A larger value for this attribute implies a more lenient policer. When the delay between two consecutive forward Resource Management (RM) cells received at this interface corresponds to a value greater than the farEndAcrDecreaseTimeFactor attribute, the policer begins to enforce the incoming traffic at the value of this attribute. If this attribute is specified less than the MCR of the connection, then the MCR is used as the feIcr. If this attribute is more than the PCR of the connection, then PCR is used as the feIcr.

This group contains traffic related provisionable attributes for the Vcc, Vpc, and Vpt components. Changing any of the attributes in this group causes a service interruption on the Vcc, Vpc, or Vpt component.

An entry in the mscAtmIfVpcVpdTmProvTable.

This attribute specifies the type of traffic management which is applied to the transmit direction of this connection as defined in the ATM Forum. The txTrafficDescType determines the number and meaning of the parameters in the txTrafficDescParm attribute. This attribute can have a value of 9 if and only if the atmServiceCategory is availableBitRate. Enumeration: 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the forward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies an override to the default transmit queue limit for this connection. An value other than sameAsCa may be specified only for ATM IP and 1pOC48SmSrAtm cards. This attribute is not applicable for basic Vpts. A value of sameAsCa means to use the default common or per-VC transmit queue limit as defined by the CA service category for this connection. A value from 5 to 63,488 indicates that a specific transmit queue limit is requested which differs from the default which is defined under the CA component for this service category. A specific value is ignored for connections where common queuing is specified for the service category. For the 1pOC48SmSrAtm card, this attribute is used to set the per VC utilization limit. The actual transmit queue limit for a connection is visible in the Vcc Tm, Vpc Tm or Vpt txQueueThresholds attribute. VALUES ( 0 = sameAsCa )

This attribute specifies the holding priority of this connection. In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This value provisioned in the Vcd or Vpd may be overridden by certain applications, for example Vcc Test, which run over this connection. The default holding priority for a provisioned connection is higher then default holding priorities for dynamic (SVC) connections. This attribute is not applicable for Vpt Vccs. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the type of traffic management which is applied to the receive direction of this connection as defined in the ATM Forum. The rxTrafficDescType determines the number and meaning of the parameters in the rxTrafficDescParm attribute. When this attribute is set to sameAsTx, the rxTrafficDescType as well as the rxTrafficDescParm are taken from the txTrafficDescType and txTrafficDescParm values. Enumeration: 'sameAsTx': 15, 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the backward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. The sameAsFwd selection sets the backward quality of service to be the same as the forward quality of service. Enumeration: 'sameAsFwd': 15, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the ATM service category for both directions of the connection. The value derivedFromBBC may only be used if the SrcPvc component is provisioned under this Vcc. Otherwise a specific ATM service category must be specified. If this attribute is set to derivedFromBBC, the Broadband Bearer Capability (BBC) and bestEffort attributes are used to determine the atmServiceCategory of this connection. If this attribute is set to other than derivedFromBBC, the value of this attribute is used to override the provisioned BBC Information Element parameters. In those cases, the BBC attributes are not used. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to be of significantly reduced value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The availableBitRate service is an ATM layer service category for which the limiting ATM layer transfer characteristics provided by the network may change subsequent to connection establishment. ABR service has a flow control mechanism which supports several types of feedback to control the source rate in response to changing ATM layer transfer characteristics. ABR service is not intended to support real-time applications. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'derivedFromBBC': 15, 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'availableBitRate': 4, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. This attribute is ignored if the atmServiceCategory is availableBitRate. Traffic shaping is not available on the 1pOC12SmLrAtm card, therefore this attribute is ignored. When sameAsCa is selected, traffic shaping for the connection is based on the trafficShaping attribute of the connection's service category component under the CA. If the service category has trafficShaping set to enabled or inverseUpc, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc Tm, Vpc Tm, or Vpt Tm components. When disabled is selected, traffic shaping for this connection is disabled regardless of the provisioning of the connection's service category component. Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute only applies when this connection is unshaped. This attribute specifies the transmit queueing method for this connection if it is unshaped. The two possible methods are per-VC queuing and common queuing. On ATM IP FPs, this attribute must be set to sameAsCa. This attribute is ignored in the following situations: - if the connection has trafficShaping enabled or inverseUpc, or - if the atmServiceCategory is availableBitRate, or - if the atmServiceCategory is constantBitRate and this is a CQC- based ATM FP. - for basic Vpts and standard Vpt Vccs When this attribute is set to sameAsCa, the transmit queueing method for the connection is based on the unshapedTransmitQueueing attribute of the connection's service category component under the CA. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. Enumeration: 'sameAsCa': 3, 'common': 1.

This attribute specifies an override for the weight of this unshaped connection. This attribute is ignored for shaped connections, for ABR connections, for connections on a CQC-based ATM FP and basic Vpts. When the value is set to sameAsCa, the weight is determined by the fairnessWeight attribute under the CA service category component for all but standard Vpt Vccs. For standard Vpt Vccs, the weight is determined by the Vcc's service category, when the value is set to sameAsCa. When this attribute is set to a value from 1 to 4095, that value is used for the fairness weight of this connection relative to other connections. For all but standard Vpt Vccs, fairness weight determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections in the same service category. For standard Vpt Vccs, fairness weight determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections associated with the Vpt. When the value is set to upToQueueLimit, the fairness weight is limited only by the txQueueLimit. VALUES ( 0 = upToQueueLimit 65535 = sameAsCa )

This attribute specifies whether force tagging is enforced for this connection for cells in the transmit direction. On CQC-based ATM cards and for Vpts, this attribute is not applicable and is ignored. When the value is set to sameAsCa, the force tagging functionality is determined by the forceTagging attribute under the CA service category component. When the value is set to enabled, force tagging is enabled for cells in the transmit direction on this connection. When this option is selected, the CLP bit is set to 1 for all cells in the transmit direction. Cells which are tagged are counted in the txCellClp attribute. When the value is set to disabled, force tagging is disabled for cells in the transmit direction on this connection. When this option is selected, the CLP bit is unchanged for cells in the transmit direction. Enumeration: 'disabled': 1, 'sameAsCa': 2, 'enabled': 0.

This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsCa is selected, UPC for the connection is based on the usageParameterControl attribute of the service category component under the AtmIf CA. If the service category has UPC enforced or monitored, then UPC is set to that value for the connection. When disabled is selected, UPC for this connection is disabled regardless of the provisioning of the service category. When enforced is selected, UPC for this connection is enforced regardless of the provisioning of the service category. Note that setting UPC to enforced or monitored may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc, Vpc, and Vpt components. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4, 'sameAsCa': 2.

This attribute specifies the bearer capability. This attribute is only used for SPVC and SPVP connections. It is one of the Broadband Bearer Capability (BBC) attributes. The purpose of the BBC information element is to indicate a requested broadband connection-oriented bearer service to be provided by the network. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Class a service is a connection-oriented, constant bit rate ATM transport service. Class a service has end to end timing requirements and may require stringent cell loss, cell delay and cell delay variation performance.When a is set, the user is requesting more than an ATM only service. The network may look at the AAL to provide interworking based upon its contents. Class c service is a connection-oriented, variable bit rate ATM transport service. Class c service has no end-to-end timing requirements. When c is set, the user is requesting more than an ATM only service. The network interworking function may look at the AAL and provide service based on it. Class x service is a connection-oriented ATM transport service where the AAL, trafficType (vbr or cbr) and timing requirements are user defined (that is, transparent to the network).When x is set the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. Class vp service is used to specify a transparent VP service. When the value of this attribute is vp, the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. This service differs from class x service in that with the class vp service both the VCI field (except or VCI values 0, 3, 4, and 6 through 15) and Payload Type field are transported transparently by the network. This attribute value is only applicable to SPVP connections. Enumeration: 'a': 1, 'x': 16, 'c': 3, 'vp': 24, 'derivedFromServiceCategory': 31.

This attribute specifies the transfer capability for this connection. Uni 3.0/3.1 traffic type and end-to-end timing parameters are mapped into this parameter as follows: 0: NoIndication, NoIndication 1: NoIndication, yes 2: NoIndication, no 5: CBR, yes 8: VBR, NoIndication 9: VBR, yes 10: VBR, no notApplicable specifies that the user does not want to specify the transfer capability. The CBR traffic type refers to traffic offered on services such as a constant bit rate video service or a circuit emulation. The VBR traffic type refers to traffic offered on services such as packetized audio and video, or data. The value no indication for traffic type is used if the user has not set the traffic type; similarly for end-to-end timing. The value yes for end-to-end timing indicates that end-to-end timing is required. The value no for end-to-end timing indicates that end-to-end timing is not required. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'n10': 10, 'notApplicable': 30, 'derivedFromServiceCategory': 31, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n5': 5.

This attribute specifies the value for the clipping susceptibility parameter in the BBC Information Element. This attribute is only used for SPVC connections. It is one of the Broadband Bearer Capability attributes. Clipping is an impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through. Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the value of the best effort parameter in the ATM Traffic Descriptor Information Element. This attribute is only used for Soft PVC connections. It is one of the Broadband Bearer Capability attributes. The value indicated implies that the quality of service for this connection is not guaranteed. The value notIndicated implies that the quality of service for this connection is guaranteed. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'notIndicated': 1, 'derivedFromServiceCategory': 15, 'indicated': 0.

This attribute specifies whether packet-wise discard functions are to be enabled or disabled in the transmit data direction for this connection. Packet-wise discard functions should only be requested if this connection is transferring AAL5 frame traffic. This attribute is not applicable for Vpts. Packet-wise functions increase the 'goodput' of the link. The transmit packet-wise functions are Early Packet Discard (EPD) and Partial Packet Discard (PPD). EPD allows the connection to discard an entire frame once the transmit queue has reached the EPD threshold. EPD increases the 'goodput' of a link, since discarding an entire frame means that some queue capacity is guarded for some other frame which is already partially transmitted. All cells of the frame are discarded from the Beginning of Message (BOM) cell up to and including the End of Message (EOM) cell. PPD allows the connection to discard the remainder of a cell- forwarded AAL5 frame if one cell of this frame has been discarded. All cells are discarded up to but not including the EOM cell. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded at the AAL5 reassembly point are not transmitted. On CQC-based ATM cards, the packet-wise discard functions are PPD and EPD. PPD is available at VCC cell-transfer points. PPD is not applicable at frame-cell conversion points, and is not applicable for Vpcs. PPD is configured by this attribute. Packet-wise discard should only be enabled for connections carrying AAL5 segmentation traffic. Setting the value to enabled for any other traffic type may result in all traffic being discarded. On CQC-based ATM FPs, EPD is automatically enabled at frame-to-cell conversion points, independent of the setting of this attribute. On CQC-based ATM cards, at a permanent VCC connection endpoint, this attribute is not applicable and is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. On ATM IP cards, packet-wise discard functions include EPD and PPD. PPD and EPD apply to individual VCCs and VCCs within VPCs at all connection points, including tandem VPC connections. Both PPD and EPD are controlled by this attribute. This attribute may safely be set to enabled for any connection (Vcc or Vpc) on ATM IP FPs since they have the ability to automatically detect AAL5-segmented traffic on a connection, and only enable packet- wise discards if AAL5-segmented traffic is detected. When this attribute is set to enabled, packet-wise discard functions are applied to transmit traffic at this connection point. When this attribute is set to disabled, packet-wise discard functions are not applied to transmit traffic at this connection point. At a SPVC origin on a PNNI interface, a value of enabled specifies that frame discard is requested in the backward direction. When this attribute is set to disabled, backward frame discard is not requested in the SPVC call setup. The transmit packet-wise discard functions that are active are visible in the Vcc/Vpc Tm txPacketWiseDiscard operational attribute. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute specifies whether packet-wise discard functions are to be enabled or disabled in the receive data direction for this connection. Packet-wise discard functions should only be requested if this connection is transferring AAL5 frame traffic. This attribute is not applicable for Vpts. Packet-wise functions increase the 'goodput' of the link. The receive packet-wise function is Partial Packet Discard (PPD). PPD allows the connection to discard the remainder of a cell- forwarded AAL5 frame if one cell of this frame has been discarded, for example due to UPC. All cells are discarded up to but not including the EOM cell. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded at the AAL5 reassembly point are not transmitted. PPD is available at all VCC connection points where UPC may be activated. PPD is not applicable for Vpcs. On CQC-based ATM FPs, packet-wise discards should only be enabled for connections carrying AAL5 segmentation traffic. Setting the value to enabled for any other traffic type may result in traffic being discarded. On CQC-based ATM cards, at a permanent VCC connection endpoint, this attribute is not applicable and is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. On ATM IP cards, this attribute may safely be set to enabled for any connection (Vcc or Vpc) since they have the ability to automatically detect AAL5-segmented traffic on a connection, and only enables packet-wise discards if AAL5-segmented traffic is detected. When this attribute is set to enabled, packet-wise discard functions are applied to receive traffic at this connection point. When this attribute is set to disabled, packet-wise discard functions are not applied to receive traffic at this connection point. At a SPVC origin on a PNNI interface, a value of enabled specifies that frame discard is requested in the forward direction. When this attribute is set to disabled, forward frame discard is not requested in the SPVC call setup. The receive packet-wise discard functions that are active are visible in the Vcc/Vpc Tm rxPacketWiseDiscard operational attribute. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute specifies the type of ABR behavior which is to be enforced at this connection. This attribute is only applicable if the atmServiceCategory attribute is availableBitRate. If the atmServicecategory attribute is not availableBitRate, this attribute value is ignored. The actual ABR functionality which is in effect is visible in the Vcc/Vpc/Vpt Tm abrConnectionType operational attribute. For CQC-based ATM cards, the only allowable values are sameAsCa, nonAbrInterworking or abrSwitch. If abrSwitch is selected, the CQC implements EFCI marking behavior. For the 1pOC12SmLrAtm card, the only allowable values are sameAsCa or abrSwitch. If abrSwitch is selected, EFCI marking behavior is implemented. sameAsCa is used to request the default behavior as specified in the CA Abr component for this Vcc. Otherwise, this attribute overrides the default behavior. virtualSourceDest is used to request that this connection point function as a virtual source/virtual destination. VS/VD functionality is only supported on ATM IP FPs. sourceDest requires that this connection point function as a S/D for RM cells. S/D mode is automatically invoked at this connection point either if this is a connection end point, or if the next hop connection point is configured as nonAbrInterworking. nonAbrInterworking is used to request that this connection point function as an interworking between ABR and non-ABR service categories. This means that there are no RM cells on the link side of this connection, and that the next hop connection point is performing as an ABR sourceDest. abrSwitch is used to request ABR switch behavior for this connection point. The ABR switch behavior is first, to confirm to virtualSourceDest or nonAbrInterworking setting on the next hop, and otherwise to implement ABR ER switch behavior. For CQC- based FPs, ABR switch behavior is implemented as EFCI marking. Enumeration: 'abrSwitch': 0, 'nonAbrInterworking': 5, 'sameAsCa': 14, 'virtualSourceDest': 3, 'sourceDest': 4.

This attribute is a vector of five traffic parameters whose meanings are defined by the txTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR), Minimum Cell Rate (MCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR, MCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When txTrafficDescType is 1 or 2, all of the parameters must be set to zero. When txTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When txTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell discard; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell tagging; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 9, parameter 1 represents the PCR; parameter 2 represents the CDVT; parameter 3 represents the MCR; parameter 4 and parameter 5 represent are not used and must be zero. Parameter 1 must be non-zero and must be greater than or equal to parameter 3. Parameter 3 may be optionally zero. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. When the atmServiceCategory is availableBitRate (ABR), the shaping rate is dynamically chosen, based on the ABR flow control mechanism, as a value between the MCR and the PCR or the requested shaping rate if applicable. For txTrafficDescType 3, 4 and 5, the transmit traffic is shaped at the next available shaping rate less than the PCR. For txTrafficDescType 6, 7 and 8 if linear traffic shaping is selected, the transmit traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR. For txTrafficDescType 6, 7 and 8 if inverse-UPC traffic shaping is selected, the transmit traffic is shaped at a variable rate which conforms to the PCR, SCR and MBS of the connection traffic descriptor. Inverse-UPC traffic shaping is available only on ATM IP cards.

An entry in the mscAtmIfVpcVpdTmTxTdpTable.

This variable represents the mscAtmIfVpcVpdTmTxTdpTable specific index for the mscAtmIfVpcVpdTmTxTdpTable.

This variable represents an individual value for the mscAtmIfVpcVpdTmTxTdpTable.

This attribute is a vector of four traffic parameters whose meanings are defined by the rxTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and Minimum Cell Rate (MCR) are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. The value of CDVT is expressed in microseconds. The values of PCR, SCR, MCR, MBS and CDVT are used for usage parameter control (UPC). When rxTrafficDescType is 1 or 2, all of the parameters must be set to zero (unused). When rxTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic. Parameter 1 must be non-zero. Parameters 2 and 3 must be set to zero (unused). When rxTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is a 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to Parameter 2. When rxTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameter 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 9, parameter 1 represents the PCR; parameter 2 represents the CDVT; parameter 3 represents the MCR. Parameter 4 is not used and must be zero. Parameter 1,must be non- zero and must be greater than or equal to parameter 3. Parameter 3 may optionally be zero. When rxTrafficDescType is any value from 3 through 8, parameter 4 represents the CDVT. If the value of CDVT either in parameter 2 or in parameter 4 is zero, the CDVT is taken from the CA defaults for the particular atmServiceCategory of this connection. On a CQC-based ATM card, when rxTrafficDescriptorType is 3 through 8, there are certain extreme combinations of rxTrafficDescParm which are outside the capabilities of the UPC hardware. The check prov command detects such cases and generates an error message. If this happens, adjust the parameters until they fall within the supported limits. To calculate the limits, use the following formulae: I1 = 1 000 000 000 / PCR L1 = CDVT * 1000 I2 = 1,000,000,000 / SCR L2 = CDVT + (MBS - 1) * (I2 - I1) I1 and I2 must be less than or equal to 335,523,840. I1 + L1 must be less than or equal to 1,342,156,800. I2 + L2 must be less than or equal to 1,342,156,800. Note that I2 and L2 only apply when the rxTrafficDescriptorType is 6 through 8. If the values of I1, L1, I2 or L2 are closer to the limits described above, a further restriction applies. Specifically, if either: I1 > 41,940,480 or I2 > 41,940,480 or I1 + L1 > 167,769,600 or I2 + L2 > 167,769,600 then both I1 and I2 must be greater than 20,480. Parameter 5 of the rxTrafficDescParm is always unused. If the rxTrafficDescType is sameAsTx, the values provisioned in this attribute are ignored. The traffic parameters for the receive direction are taken from the txTrafficDescParm.

An entry in the mscAtmIfVpcVpdTmRxTdpTable.

This variable represents the mscAtmIfVpcVpdTmRxTdpTable specific index for the mscAtmIfVpcVpdTmRxTdpTable.

This variable represents an individual value for the mscAtmIfVpcVpdTmRxTdpTable.

This attribute is a vector of three elements that specify the quality of service parameters for the forward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVpcVpdTmFqpTable.

This variable represents the mscAtmIfVpcVpdTmFqpTable specific index for the mscAtmIfVpcVpdTmFqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcVpdTmFqpTable.

This attribute is a vector of three elements that specify the quality of service parameters for the backward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVpcVpdTmBqpTable.

This variable represents the mscAtmIfVpcVpdTmBqpTable specific index for the mscAtmIfVpcVpdTmBqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcVpdTmBqpTable.

This entry controls the addition and deletion of mscAtmIfVpcVpdPm components.

A single entry in the table represents a single mscAtmIfVpcVpdPm component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcVpdPm components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcVpdPm tables.

This variable represents the index for the mscAtmIfVpcVpdPm tables.

This group contains provisioned attributes which specify Performance Monitoring (PM) measurements, namely, Availability Ratio (AR) and Cell Loss Ratio (CLR), and control modes for the connection. The values specified in this group override those specified by AtmIf Pm settings.

An entry in the mscAtmIfVpcVpdPmProvTable.

This attribute specifies the set of Performance Monitoring (PM) measurements on the switch side configuration for the connection. sameAsInterface means that the measurements specified by the segSwitchSideMeasurement attribute of the AtmIf Pm component will be performed. No other values may be specified if sameAsInterface is selected. If the value is empty, no switch side PM measurements are done. Description of bits: availabilityRatio(0) cellLossRatio(1) sameAsInterface(2)

This attribute specifies the set of Performance Monitoring (PM) measurements on the link side configuration for the connection. sameAsInterface means that the measurements specified by the segLinkSideMeasurement attribute of the AtmIf Pm component will be performed. No other values may be specified if sameAsInterface is selected. If the value is empty, no link side PM measurements are done. The following are valid sets: (~sameAsInterface ~availabilityRatio ~cellLossRatio) (~sameAsInterface ~availabilityRatio cellLossRatio) (~sameAsInterface availabilityRatio ~cellLossRatio) (~sameAsInterface availabilityRatio cellLossRatio) (sameAsInterface ~availabilityRatio ~cellLossRatio) Description of bits: availabilityRatio(0) cellLossRatio(1) sameAsInterface(2)

This attribute specifies the control mode of Performance Monitoring (PM) measurements for the connection. autoStart means that PM activation procedures will start when the provisioned data is activated. onDemand means that PM activation procedures will start when the operator issues the START command. The PM measurements in this mode will continue until the operator issues the STOP command. sameAsInterface means that the behavior will be as specified by the controlMode attribute of the AtmIf Pm component. Enumeration: 'sameAsInterface': 2, 'onDemand': 1, 'autoStart': 0.

This group contains the provisionable loopback attributes for a Vcc, Vpc, or Vpt component. Note that certain loopback requests may not be possible on a given connection. In such cases, the corresponding operational loopback attribute in the Status group of the Vcc, Vpc, or Vpt component is set to notApplicable and the requested loopback is not performed. If loopbacks are provisioned to be on, and for any reason the segment or end-to-end OAM loopback cells are not relayed, the connection component becomes troubled, and user cell traffic may be discarded. If loopbacks are provisioned to be on, all of the nodes in the segment, and external networks which are in the end-to-end connection must relay the OAM loopback cells.

An entry in the mscAtmIfVpcVpdLbkTable.

This attribute specifies whether link-side segment loopback insertion should be performed on this connection. When sameAsInterface is selected, the link-side segment loopback insertion for the connection is based on the segLinkSideLoopback attribute of the connection's parent AtmIf componentif the ATM interface has link-side segment loopback insertion turned on, then link-side segment loopback insertion is also on for the connection. When on or off is selected, link-side segment loopback insertion is turned on or off respectively for the connection regardless of the provisioning of the parent AtmIf component. Note that link-side segment loopback insertion is not possible if the connectionPointType attribute of the Vcc or Vpc component is connectingPoint. Link-side segment loopback insertion is also not possible if the distributionType of the Vcc is pointToMultipoint. In such cases, the associated segLinkSideLoopbackState attribute indicates notApplicable and link-side segment loopback insertion is not performed. Link-side segment loopback insertion is always possible on a Vpt. Enumeration: 'on': 0, 'off': 1, 'sameAsInterface': 2.

This attribute specifies whether switch-side segment loopback insertion should be performed on this connection. When sameAsInterface is selected, the switch-side segment loopback for the connection is based on the segSwitchSideLoopback attribute of the connection's parent AtmIf componentif the ATM interface has switch-side segment loopback insertion turned on, then switch-side segment loopback insertion is also on for the connection. When on or off is selected, switch-side segment loopback insertion is turned on or off respectively for the connection regardless of the provisioning of the parent AtmIf component. Note that switch-side segment loopback insertion is not possible if the connectionPointType attribute of the Vcc or Vpc component is connectingPoint or connectionEndPoint. Switch-side segment loopback insertion is also not possible if the distributionType of the Vcc is pointToMultipoint In such cases, the associated segSwitchSideLoopbackState attribute indicates notApplicable and switch-side segment loopback insertion is not performed. Switch- side segment loopback is never possible on a Vpt. Enumeration: 'on': 0, 'off': 1, 'sameAsInterface': 2.

This attribute specifies whether end-to-end loopback insertion should be performed on this connection. When sameAsInterface is selected, the end-to-end loopback for the connection is based on the endToEndLoopback attribute of the connection's parent AtmIf componentif the ATM interface has end-to-end loopback insertion turned on, then end-to-end loopback insertion is also on for the connection. When on or off is selected, end-to-end loopback insertion is turned on or off respectively for the connection regardless of the provisioning of the parent AtmIf component. Note that end-to-end loopback insertion is not possible if the connectionPointType attribute of the Vcc or Vpc component is connectingPoint or segmentEndPoint. End-to-end loopback insertion is also not possible if the distributionType of the Vcc is pointToMultipoint. In such cases, the associated endToEndLoopbackState attribute indicates notApplicable and end- to-end loopback insertion is not performed. End-to-end loopback insertion is always possible on a Vpt. Enumeration: 'on': 0, 'off': 1, 'sameAsInterface': 2.

This attribute is introduced to exist temporarily to pass to AtmIf the connection type defined under Vcc or Vpc. This attribute will be obsoleted once a more elegant solution is available. Enumeration: 'pointToMultipointLeaf': 2, 'pointToPoint': 0, 'pointToMultipointRoot': 1.

This group contains traffic related provisionable attributes for the Vcc and Vpc components. The attributes' operational values are reflected in the Traffic group for these components. Changing any of the attributes in this group causes a service interruption on the Vcc or Vpc component.

An entry in the mscAtmIfVpcVpdTrafficTable.

This attribute is migrated to the AtmTmProv group. This attribute specifies the type of traffic management which is applied to the transmit direction of this connection as defined in the ATM Forum. The txTrafficDescType determines the number and meaning of the parameters in the txTrafficDescParm attribute. Enumeration: 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the transmit direction for this connection. The constantBitRate class refers to traffic offered on services such as a constant bit rate video service. This traffic is highest priority. The variableBitRate class refers to traffic offered on services such as packetized audio and video. The connectionOriented class refers to connection-oriented traffic such as Frame Relay or X.25 traffic. The connectionless traffic refers to traffic offered through connectionless trunks such as certain LAN protocols. The unspecified class supports a 'best effort' type of service, where there is a minimum guarantee of bandwidth. This traffic is lowest priority. This attribute is obsolete. The value is migrated into atmServiceCategory. The atmServiceCategory applies in both transmit and receive directions. unspecified maps to unspecifiedBitRate; constantBitRate maps to constantBitRate; variableBitRate maps to variableBitRateRt; connectionOriented maps to variableBitRateNrt connectionless maps to variableBitRateNrt Enumeration: 'constantBitRate': 1, 'connectionOriented': 3, 'variableBitRate': 2, 'connectionless': 4, 'unspecified': 0.

This attribute is migrated to the AtmTmProv group. This attribute specifies the quality of service for the forward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is migrated to the AtmTmProv group. This attribute specifies the holding priority of this connection. In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This value provisioned in the Vcd or Vpd may be overridden by certain applications, for example Vcc Test, which run over this connection. The default holding priority for a provisioned connection is higher then default holding priorities for dynamic (SVC) connections. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is migrated to the AtmTmProv group. This attribute specifies the type of traffic management which is applied to the receive direction of this connection as defined in the ATM Forum. The rxTrafficDescType determines the number and meaning of the parameters in the rxTrafficDescParm attribute When sameAsTx is selected, the rxTrafficDescType as well as the rxTrafficDescParm are taken from the transmit values. Enumeration: 'sameAsTx': 15, 'n8': 8, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the receive direction for this connection. The constantBitRate class refers to traffic offered on services such as a constant bit rate video service. The variableBitRate class refers to traffic offered on services such as packetized audio and video. The connectionOriented class refers to connection-oriented traffic. The connectionless traffic refers to traffic offered through connectionless trunks. The unspecified class supports a 'best effort' type of service, where there is a minimum guarantee of bandwidth. The sameAsTx selection sets the receive quality of service to be the same as the transmit quality of service. This attribute is obsolete. The value of txQosClass is migrated into atmServiceCategory. The value of this attribute is ignored. AtmServiceCategory applies in both transmit and receive directions. Enumeration: 'variableBitRate': 2, 'connectionless': 4, 'constantBitRate': 1, 'sameAsTx': 15, 'unspecified': 0, 'connectionOriented': 3.

This attribute is migrated to the AtmTmProv group. This attribute specifies the quality of service for the backward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. The sameAsFwd selection sets the backward quality of service to be the same as the forward quality of service. Enumeration: 'sameAsFwd': 15, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is migrated to the AtmTmProv group. This attribute specifies the ATM service category for both directions of the connection. The value derivedFromBBC may only be used if the SrcPvc component is provisioned under this Vcc.Otherwise a specific ATM service category must be specified. If this attribute is set to derivedFromBBC, the Broadband Bearer Capability (BBC) and bestEffort attributes are used to determine the atmServiceCategory of this connection. If this attribute is set to other than derivedFromBBC, the value of this attribute is used to override the provisioned BBC Information Element parameters. In those cases, the BBC attributes are not used. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to be of significantly reduce value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'derivedFromBBC': 15, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute is migrated to the AtmTmProv group. This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. When sameAsInterface is selected, traffic shaping for the connection is based on the trafficShaping attribute of the connection's parent AtmIf componentif the ATM interface has traffic shaping enabled, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc and Vpc components. When disabled is selected, traffic shaping for this connection is disabled regardless of the provisioning of the parent AtmIf component. Enumeration: 'disabled': 1, 'sameAsInterface': 2.

This attribute is migrated to the AtmTmProv group. This attribute only applies when this connection is unshaped. This attribute defines the transmit queueing method for this connection if it is unshaped. Refer to the unshapedTransmitQueueing attribute under the AtmIf for more details on the meaning of this attribute. When this attribute is set to sameAsInterface, the value from the AtmIf is used. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. Enumeration: 'sameAsInterface': 3, 'common': 1.

This attribute is migrated to the AtmTmProv group. This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsInterface is selected, UPC for the connection is based on the usageParameterControl attribute of the connection's parent AtmIf componentif the ATM interface has UPC enabled, then UPC is enabled for the connection. Note that enabling UPC may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc and Vpc components. When disabled is selected, UPC for this connection is disabled regardless of the provisioning of the parent AtmIf component. Enumeration: 'disabled': 1, 'sameAsInterface': 2.

This attribute is migrated to the AtmTmProv group. This attribute specifies the bearer capability. This attribute is only used for SPVC and SPVP connections. It is one of the Broadband Bearer Capability (BBC) attributes. The purpose of the BBC information element is to indicate a requested broadband connection-oriented bearer service to be provided by the network. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Class a service is a connection-oriented, constant bit rate ATM transport service. Class a service has end to end timing requirements and may require stringent cell loss, cell delay and cell delay variation performance.When a is set, the user is requesting more than an ATM only service. The network may look at the AAL to provide interworking based upon its contents. Class c service is a connection-oriented, variable bit rate ATM transport service. Class c service has no end-to-end timing requirements. When c is set, the user is requesting more than an ATM only service. The network interworking function may look at the AAL and provide service based on it. Class x service is a connection-oriented ATM transport service where the AAL, trafficType (vbr or cbr) and timing requirements are user defined (that is, transparent to the network).When x is set the user is requesting an ATM only service from the network. Class vp service is used to specify a transparent VP service. When the value of this attribute is vp, the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. This service differs from class x service in that with the class vp service both the VCI field (except or VCI values 0, 3, 4, and 6 through 15) and Payload Type field are transported transparently by the network. This attribute value is only applicable to SPVP connections. Enumeration: 'a': 1, 'x': 16, 'c': 3, 'vp': 24, 'derivedFromServiceCategory': 31.

This attribute is migrated to the AtmTmProv group. This attribute specifies the transfer capability for this connection. Uni 3.0/3.1 traffic type and end-to-end timing parameters are mapped into this parameter as follows: 0: NoIndication, NoIndication 1: NoIndication, yes 2: NoIndication, no 5: CBR, yes 8: VBR, NoIndication 9: VBR, yes 10: VBR, no NotApplicable specifies that the user does not want to specify the transfer capability. The CBR traffic type refers to traffic offered on services such as a constant bit rate video service or a circuit emulation. The VBR traffic type refers to traffic offered on services such as packetized audio and video, or data. The value no indication for traffic type is used if the user has not set the traffic type; similarly for end-to-end timing. The value yes for end-to-end timing indicates that end-to-end timing is required. The value no for end-to-end timing indicates that end-to-end timing is not required. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'n10': 10, 'notApplicable': 30, 'derivedFromServiceCategory': 31, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n5': 5.

This attribute is migrated to the AtmTmProv group. This attribute specifies the value for the clipping susceptibility parameter in the BBC Information Element. This attribute is only used for SPVC connections. It is one of the Broadband Bearer Capability attributes. Clipping is an impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through. Enumeration: 'yes': 1, 'no': 0.

This attribute is migrated to the AtmTmProv group. This attribute specifies the value of the best effort parameter in the ATM Traffic Descriptor Information Element. This attribute is only used for Soft PVC connections. It is one of the Broadband Bearer Capability attributes. The value indicated implies that the quality of service for this connection is not guaranteed. The value notIndicated implies that the quality of service for this connection is guaranteed. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'notIndicated': 1, 'derivedFromServiceCategory': 15, 'indicated': 0.

This attribute specifies the activation of frame discard functionality in the forward data direction, at relay points, for this connection. It applies to each hop of the connection. Frame discard functions should not be requested if this connection is not transferring frame (AAL5) traffic. Setting the value to indicated for any other traffic type results in all traffic being discarded. If this connection point is a permanent (provisioned) VCC mid- point, this attribute specifies whether the Partial Packet Discard (PPD) function is to be enabled or disabled in the transmit direction at this connecting point. The PPD function allows the connecting point to discard the remainder of a cell-forwarded AAL5 frame if one cell of this frame has been discarded. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded by the AAL5 reassembly are not transmitted. At a permanent VCC connecting point which is not a connection endpoint, when this attribute is set to indicated, the PPD function is applied to transmit traffic at this connecting point. It should not be indicated for connections whose end points are not performing AAL5 segmentation and reassembly. When this attribute is set to notIndicated, the PPD feature is not applied to transmit traffic at this connecting point. At a SPVC origin on a PNNI interface, a value of indicated specifies that frame discard is requested in the forward direction. The frame discard function for SPVCs consists of PPD at the SPVC origin and at all intermediate connecting points. When this attribute is set to notIndicated, forward frame discard is not requested in the SPVC call setup. Thus PPD is not enabled at the SPVC origin nor at any intermediate connecting point. At all points along a VPC, this setting is ignored. At a permanent VCC connection endpoint, this value is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. This attribute has been migrated to txFrameDiscard. Enumeration: 'notIndicated': 0, 'indicated': 1.

This attribute specifies the activation of frame discard functionality in the backward data direction, at relay points, for this connection. It applies to each hop of the connection. Frame discard functions should not be requested if this connection is not transferring frame (AAL5) traffic. Setting the value to indicated for any other traffic type results in all traffic being discarded. If this connection point is a permanent (provisioned) VCC mid- point, this attribute specifies whether the Partial Packet Discard (PPD) function is to be enabled or disabled in the receive direction at this connecting point. The PPD function allows the connecting point to discard the remainder of a cell-forwarded AAL5 frame if one cell of this frame has been discarded. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded by the AAL5 reassembly are not received. At a permanent VCC connecting point which is not a connection endpoint, when this attribute is set to indicated, the PPD function is applied to receive traffic at this connecting point. It should not be indicated for connections whose end points are not performing AAL5 segmentation and reassembly. When this attribute is set to notIndicated, the PPD feature is not applied to receive traffic at this connecting point. At a SPVC origin on a PNNI interface, a value of indicated specifies that frame discard is requested in the backward direction. The frame discard function for SPVCs consists of PPD at the SPVC origin and at all intermediate connecting points. When this attribute is set to notIndicated, backwards frame discard is not requested in the SPVC call setup. Thus PPD is not enabled at the SPVC origin nor at any intermediate connecting point. At all points along a VPC, this setting is ignored. At a permanent VCC connection endpoint, this value is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. This attribute has been migrated to rxFrameDiscard. Enumeration: 'notIndicated': 0, 'indicated': 1.

This group contains the provisionable ATM accounting attributes for a Vcc, Vpc, or Vpt component.

An entry in the mscAtmIfVpcVpdAcctTable.

This attribute specifies a unique indentifier for each end of a PVC. It that may be used by downstream processing systems to correlate accounting records issued at different nodes in the network. The attribute can be up to 32 bytes long. If it is less than 32 bytes, it is zero filled on the right to create a 32 byte value. The resulting value is recorded in the attribute callConnId for this PVC's ATM accounting records. If the attribute is a null string then this PVC does not have any accounting records generated for it.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of five traffic parameters whose meanings are defined by the txTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When txTrafficDescType is 1 or 2, all of the parameters must be set to zero. When txTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When txTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell discard; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell tagging; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. For txTrafficDescType 3, 4 and 5, the transmit traffic is shaped at the next rate less than the PCR. For txTrafficDescType 6, 7 and 8, the transmit traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR.

An entry in the mscAtmIfVpcVpdTxTdpTable.

This variable represents the mscAtmIfVpcVpdTxTdpTable specific index for the mscAtmIfVpcVpdTxTdpTable.

This variable represents an individual value for the mscAtmIfVpcVpdTxTdpTable.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of four traffic parameters whose meanings are defined by the rxTrafficDescType attribute. The values of peak cell rate (PCR) and sustained cell rate (SCR) are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. The value of CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for usage parameter control (UPC). When rxTrafficDescType is 1 or 2, all of the parameters must be set to zero (unused). When rxTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic. Parameter 1 must be non-zero. Parameters 2 and 3 must be set to zero (unused). When rxTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is a 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to Parameter 2. When rxTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameter 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is any value from 3 through 8, parameter 4 represents the CDVT. If this value is zero, the CDVT is taken from the ConnectionAdministrator defaults for the particular atmServiceCategory of this connection. When rxTrafficDescriptorType is 3 through 8, there are certain extreme combinations of rxTrafficDescParm which are outside the capabilities of the UPC hardware. The check prov command detects such cases and generates an error message. If this happens, adjust the parameters until they fall within the supported limits. To calculate the limits, use the following formulae: I1 = 1 000 000 000 / PCR L1 = CDVT * 1000 I2 = 1 000 000 000 / SCR L2 = CDVT + (MBS - 1) * (I2 - I1) I1 and I2 must be less than or equal to 335 523 840. I1 + L1 must be less than or equal to 1 342 156 800. I2 + L2 must be less than or equal to 1 342 156 800. Note that I2 and L2 only apply when the rxTrafficDescriptorType is 6 through 8. If the values of I1, L1, I2 or L2 are closer to the limits described above, a further restriction applies. Specifically, if either: I1 > 41 940 480 or I2 > 41 940 480 or I1 + L1 > 167 769 600 or I2 + L2 > 167 769 600 then both I1 and I2 must be greater than 20 480. Parameter 5 of the rxTrafficDescParm is always unused. If the rxTrafficDescType is sameAsTx, the values in this attribute are taken from the txTrafficDescParm.

An entry in the mscAtmIfVpcVpdRxTdpTable.

This variable represents the mscAtmIfVpcVpdRxTdpTable specific index for the mscAtmIfVpcVpdRxTdpTable.

This variable represents an individual value for the mscAtmIfVpcVpdRxTdpTable.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of three elements that specify the quality of service parameters for the forward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR, and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR, and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVpcVpdFqpTable.

This variable represents the mscAtmIfVpcVpdFqpTable specific index for the mscAtmIfVpcVpdFqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcVpdFqpTable.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of three elements that specify the quality of service parameters for the backward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR, and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR, and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVpcVpdBqpTable.

This variable represents the mscAtmIfVpcVpdBqpTable specific index for the mscAtmIfVpcVpdBqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcVpdBqpTable.

This entry controls the addition and deletion of mscAtmIfVpcLoop components.

A single entry in the table represents a single mscAtmIfVpcLoop component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcLoop components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcLoop tables.

This variable represents the index for the mscAtmIfVpcLoop tables.

This entry controls the addition and deletion of mscAtmIfVpcTm components.

A single entry in the table represents a single mscAtmIfVpcTm component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcTm components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcTm tables.

This variable represents the index for the mscAtmIfVpcTm tables.

This entry controls the addition and deletion of mscAtmIfVpcTmAbr components.

A single entry in the table represents a single mscAtmIfVpcTmAbr component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcTmAbr components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcTmAbr tables.

This variable represents the index for the mscAtmIfVpcTmAbr tables.

This group contains operational attributes for connections using ABR service category.

An entry in the mscAtmIfVpcTmAbrOperTable.

This attribute indicates the Initial Cell Rate (ICR) parameter for this connection. ICR is the rate at which a source should send initially and after an idle period. For nailed-up connections, this attribute is determined by the provisioned value of the initialCellRate attribute. For signalled connections, it is indicated in the ABR Setup Parameters Information Element. The ICR for a connection is a value between the MCR and the PCR. Furthermore, ICR has an upper bound determined by the transientBufferExposure divided by fixedRoundTripTime.

This attribute indicates the Transient Buffer Exposure (TBE) for this connection. TBE is the negotiated number of cells that the network would like to limit the resource to send during start-up periods, before the first Resource Management (RM) cell returns. For nailed-up connections, this attribute is determined by the provisioned value of the transientBufferExposure attribute. For signalled connections, it is indicated in the ABR Setup Parameters Information Element.

This attribute indicates the Fixed Round-Trip Time (FRTT) parameter for this connection. FRTT is the sum of the fixed and propagation delays from the source to a destination and back. For nailed-up connections, this attribute is determined by the provisioned value of the fixedRoundTripTime attribute. For signalled connections, it is indicated in the ABR Setup Parameters Information Element.

This attribute indicates the Rate Decrease Factor (RDF) for this connection. The RDF value is computed by using the operational value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 8, RDF is 2E-8 = 1/256. RDF controls the amount by which the cell transmission rate may decrease upon receipt of a backward Resource Management (RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) field set to 1, the Allowed Cell Rate (ACR) value would be reduced by the amount (RDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. For nailed-up connections, this attribute is determined by the provisioned value of the rateDecreaseFactor attribute. For signalled connections, it is indicated in the ABR Setup Parameters Information Element.

This attribute indicates the Rate Increase Factor (RIF) for this connection. The RIF value is computed by using the operational value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 6, RIF is 2E-6 = 1/64. RIF controls the amount by which the cell transmission rate may increase upon receipt of a backward Resource Management (RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) and the No Increase (NI) fields both set to 0, the Allowed Cell Rate (ACR) value would be increased by the amount (RIF*ACR). The ACR is not allowed to exceed the Peak Cell Rate (PCR), in which case the ACR is set to PCR. For nailed-up connections, this attribute is determined by the provisioned value of the rateIncreaseFactor attribute. For signalled connections, it is indicated in the ABR Setup Parameters Information Element.

This attribute indicates the maximum number of cells an ABR source may transmit for each forward Resource Management (RM) cell. The count of the cells transmitted includes data cells, OAM cells, backward RM cells, and the forward RM cell. For nailed-up connections, this attribute is determined by the provisioned value of the maxCellsPerRmCell attribute. For signalled connections, it is indicated in the ABR Additional Parameters Information Element.

This attribute indicates the TRM parameter for this connection. TRM provides an upper bound on the time interval between forward Resource Management (RM) cells for an ABR source. Since the last forward RM cell was sent, if at least TRM time has elapsed since and at least 2 other cells have been sent, the next cell to be transmitted would be a forward RM cell. For nailed-up connections, this attribute is determined by the provisioned value of the maxTimeBetweenRmCell attribute. For signalled connections, it is indicated in the ABR Additional Parameters Information Element.

This attribute indicates the Cutoff Decrease Factor (CDF) parameter for this connection. When the value of this attribute is non-zero, CDF is computed as the inverse of the value. For example, if the value is 32, the value of CDF is 1/32. When the value of this attribute is 0, CDF is also zero. CDF controls the decrease in the Allowed Cell Rate (ACR) associated with the forwardRmCellLimit attribute, the limit of the number of forward Resource Management (RM) cells which may be sent in the absence of received backward RM cells. When this limit is crossed, the ACR value would be decreased by the amount (CDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. For nailed-up connections, this attribute is determined by the provisioned value of the cutoffDecreaseFactor attribute. For signalled connections, it is indicated in the ABR Additional Parameters Information Element.

This attribute indicates the Allowed Cell Rate Decrease Time Factor (ADTF) parameter for this connection. ADTF is the time interval permitted between sending forward Resource Management (RM) cells before the Allowed Cell Rate (ACR) is decreased to initialCellRate. In other words, if the source does not transit a forward RM cell for the period specified by adtf, it reduces its ACR to the value of its initialCellRate. For nailed-up connections, this attribute is determined by the provisioned value of the acrDecreaseTimeFactor attribute. For signalled connections, it is indicated in the ABR Additional Parameters Information Element.

This attribute indicates the CRM parameter for this connection. CRM is the limit of the number of forward Resource Management (RM) cells which may be sent in the absence of received backward RM cells. When this limit is crossed, the Allowed Cell Rate (ACR) value would be decreased by the amount (CDF*ACR), where CDF is determined by the cutoffDecreaseFactor. The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. The value of CRM is obtained as transientBufferExposure divided by maxCellsPerRmCell.

This attribute indicates the rate change information put into the last forward Resource Management (RM) cell turned around as a backward-RM cell. For connections configured as an ABR Source or Destination, the turned around backward-RM cell is sent over the interface. For connections configured as an ABR Virtual Source or Virtual Destination, the turned around backward-RM cell is sent over the backplane. Enumeration: 'explicitRateIndicated': 2, 'noIncreaseIndicated': 1, 'congestionIndicated': 0.

This attribute indicates the type of change in the Allowed Cell Rate (ACR) as a result of the information in the last backward Resource Management (B-RM) cell received from the interface. This attribute value is only applicable when the Vcc Tm or Vpc Tm abrConnectionType attribute is sourceDest or VirtualSourceDest. In all other cases, this attribute value is notApplicable. A value of noChange indicates that the rate did not change as a result of the last backward RM cell received. A value of decreasedByRdf or increasedByRif indicates that the ACR was increased or decreased by the corresponding factor. This change is as a result of the CI or NI bit setting in the last backward RM cell, or an ADTF timeout. A value of setToExplicitRate indicates that the ACR was set to the ER value in the last backward RM cell. Enumeration: 'increasedByRif': 2, 'noChange': 0, 'decreasedByRdf': 1, 'setToExplicitRate': 3, 'notApplicable': 15.

This attribute counts the number of forward Resource Management (RM) cells sent over the interface since the last backward RM-cell was received from the interface. If the value of this attribute is greater than or equal to the value of forwardRmCellLimit, the Allowed Cell Rate (ACR) value would be decreased by the amount (CDF*ACR), where CDF is determined by the cutoffDecreaseFactor. This counter is reset to zero each time a backward-RM cell is received. This counter does not wrap to zero if it reaches its maximum value of 4095 in order to indicate that no backward RM cell has been received.

This attribute indicates the value of the Explicit Forward Congestion Indication (EFCI) bit of the last data cell received from the interface. When a forward Resource Management (RM) cell is turned around as a backward-RM cell, the Congestion Indication (CI) field of the backward-RM cell is set to 1, if the value of this attribute is indicated. This attribute is set to notIndicated each time a backward-RM cell is transmitted. Enumeration: 'notIndicated': 0, 'indicated': 1.

This group contains attributes for the Tm component to reflect operational traffic attributes.

An entry in the mscAtmIfVpcTmOperTable.

T his attribute indicates the type of traffic management which is applied to the transmit direction of this connection as defined in the ATM Forum. The txTrafficDescType determines the number and meaning of the parameters in the txTrafficDescParm attribute. Enumeration: 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute indicates the quality of service for the calling to called direction for this connection. This is only applicable to Soft PVC and SVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified QOS class; no objective is specified for the performance parameters. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute indicates the current number of cells in the transmit queue for this connection. If this connection has unshapedTransmitQueueing attribute displayed as common, this attribute displays the length of the common queue which is used for this atm service category. If this connection has unshapedTransmitQueueing attribute displayed as fifo, this attribute indicates the number of cells for this connection which are enqueued in a first-in-first-out queuing method for this atm service category. This will only occur for connections on ATM IP cards with atmServiceCategory of nrtVbr or ubr. If this connection has unshapedTransmitQueueing attribute displayed as perVc or as notApplicable, this attribute displays the length of the per-VC queue. For the 1pOC48SmSrAtm card, this attribute displays the current number of cells in the link class queue used by this connection to buffer its traffic. This attribute does not apply to basic Vpts.

This attribute indicates the congestion state of the transmit queue for this connection. If this connection has unshapedTransmitQueueing attribute displayed as common, this attribute displays the congestion state of the common queue. If this connection has unshapedTransmitQueueing attribute displayed as perVc or as notApplicable, this attribute displays the congestion state of the per- VC queue. For the 1pOC48SmSrAtm card, this attribute displays the current congestion state of the link class queue used by this connection to buffer its traffic. The congestion state of a queue is indicated by a numeric value ranging from 0 to 3. When a queue is in a congested state x, only traffic with discard priority (DP) 0 to x are enqueued. Traffic with DP > x is discarded. For example, if the congestion state is 3, there is no congestion and all traffic is enqueued. Likewise, when the congestion state is 0, there is maximum congestion and only traffic with DP=0 is enqueued on that queue. This attribute does not apply to basic Vpts.

This attribute indicates the actual holding priority in effect for this connection. In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. Some applications, for example Vcc Test, may override the provisioned holding priority. A value of notApplicable is displayed when this is an elastic connection. Holding priority does not apply to bandwidth elastic connections. Holding priority has no effect if the equivalent cell rate (ECR) for a connection is zero. This attribute does not apply to Vpt Vccs. Enumeration: 'notApplicable': 6, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute indicates the type of traffic management which is applied to the receive direction of this connection as defined in the ATM Forum. The rxTrafficDescType determines the number and meaning of the parameters in the rxTrafficDescParm attribute. Enumeration: 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute indicates the quality of service for the called to calling direction for this connection. This is only applicable to Soft PVC and SVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified QOS class; no objective is specified for the performance parameters. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'sameAsFwd': 15, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute indicates the ATM service category used for traffic in both directions of the connection. The constantBitRate service category is intended for real time applications, that is, those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to have significantly reduced value for the application. The rtVariableBitRate service category is intended for real time applications; that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The availableBitRate service is an ATM layer service category for which the limiting ATM layer transfer characteristics provided by the network may change subsequent to connection establishment. ABR service has a flow control mechanism which supports several types of feedback to control the source rate in response to changing ATM layer transfer characteristics. ABR service is not intended to support real-time applications. The unspecifiedBitRate service is intended for non-real time applications, that is those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'availableBitRate': 4, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute indicates the traffic shaping state of the connection. A value of notApplicable indicates that traffic shaping is not applicable or not supported for this connection. This is the case: - when the txTrafficDescType is 1 or 2. - for standard Vpt Vccs and basic Vpts. - for CQC-based ATM cards, when the atmServiceCategory is constantBitRate. In these cases, the value of notApplicable is set regardless of whether traffic shaping is enabled or disabled in the provisioning data. For the 1pOC12SmLrAtm card, traffic shaping is not available, therefore this attribute is always notApplicable. A value of disabled indicates that traffic shaping is applicable and supported for the type of connection but has been turned off in the provisioning data. A value of linear or inverseUpc indicates that traffic shaping is applicable and supported for the type of connection and has been turned on in the provisioning data. This is the only case that indicates that traffic shaping is performed on the connection. In this case, the actual shaping rate is reflected in the txTrafficDescParm attribute, parameter number 4. A value of linear indicates that traffic is being shaped at the constant rate indicated in txTrafficDescParm 4. A value of inverseUpc is possible only on ATM IP cards. This value indicates that the shaper strictly conforms to the requirements of a dual leaky bucket UPC enforcer. This value is indicated if traffic shaping is enabled, and the txTrafficDescType for this connection is 6, 7 or 8. Traffic shaping for connections with atmServiceCategory as availableBitRate (txTrafficDescType 9) depends upon the abrConnectionType attribute. If abrConnectionType is sourceDest or virtualSourceDest, the value of this attribute is linear. If abrConnectionType is erSwitch or efciSwitch, this attribute is notApplicable. Enumeration: 'disabled': 1, 'notApplicable': 4, 'inverseUpc': 6, 'linear': 5.

This attribute indicates the bearer capability for this connection. Class a service is a connection-oriented, constant bit rate ATM transport service. Class a service has end to end timing requirements and may require stringent cell loss, cell delay and cell delay variation performance.When a is displayed, the user is requesting more than an ATM only service. The network may look at the AAL to provide interworking based upon its contents. Class c service is a connection-oriented, variable bit rate ATM transport service. Class c service has no end-to-end timing requirements.When c is displayed, the user is requesting more than an ATM only service. The network interworking function may look at the AAL and provide service based on it. Class x service is a connection-oriented ATM transport service where the AAL, trafficType (cbr or vbr), and timing requirements are user defined (that is, transparent to the network). When the value of this attribute is x, the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. Class vp service is used to indicate a transparent VP service when the user is requesting an ATM only service from the network. In this case, the network does not process any higher layer protocol. This service differs from class x service in that with the class vp service both the VCI field (except for VCI values 0, 3, 4, and 6 through 15) and Payload Type field are transported transparently by the network. This attribute value is only applicable to SPVP and SVP connections. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'a': 1, 'x': 16, 'c': 3, 'vp': 24, 'notApplicable': 30.

This attribute indicates the transfer capability for this connection. Uni 3.0/3.1 traffic type and end-to-end timing parameters are mapped into this parameter as follows: 0: NoIndication, NoIndication 1: NoIndication, yes 2: NoIndication, no 5: CBR, yes 8: VBR, NoIndication 9: VBR, yes 10: VBR, no A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance, or in the case that the transfer capability in the call request was set to NoIndication. The CBR traffic type refers to traffic offered on services such as a constant bit rate video service or a circuit emulation. The VBR traffic type refers to traffic offered on services such as packetized audio and video, or data. The value NoIndication for traffic type is used if the user has not set the traffic type; similarly for end-to-end timing. The value yes for end-to-end timing indicates that end-to-end timing is required for the connection. The value no for end-to-end timing indicates that end-to-end timing is not required for the connection. Enumeration: 'n10': 10, 'notApplicable': 30, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n5': 5.

This attribute indicates the value of the clipping susceptibility parameter in the broadband bearer capability (BBC) Information Element. Clipping is an impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'yes': 1, 'no': 0.

This attribute indicates the unshaped transmit queuing state of the connection. A value of common indicates that transmit traffic is being enqueued onto the common transmit queue for this service category. The txQueueLength attribute indicates the current length of the common transmit queue. A value of fifo indicates that transmit traffic is being queued in a first-in-first-out basis for this service category. This is similar to common queueing, but the txQueueLength attribute indicates the number of cells in this connection queue. A value of fifo will only be indicated for connections on ATM IP cards with atmServiceCategory of nrtVbr or ubr. A value of perVc indicates that transmit traffic is being enqueued onto a per-VC queue for this connection. A value of notApplicable indicates that transmit traffic is being shaped for this connection, or that unshaped transmit queuing is not applicable for this type of connection. Transmit traffic for a shaped connection is enqueued onto a per-VC queue, but this attribute is only applicable for unshaped connections. Unshaped transmit queuing is not applicable for basic Vpts. For 1pOC12SmLrAtm cards, perVc queueing is not available thus this attribute only indicates common or notApplicable. Enumeration: 'notApplicable': 4, 'perVc': 0, 'fifo': 5, 'common': 1.

This attribute indicates value of best effort parameter in the ATM Traffic Descriptor Information Element. The value indicated implies that the quality of service for this connection is not guaranteed. The value notIndicated implies that the quality of service for this connection is guaranteed. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'notIndicated': 1, 'indicated': 0.

This attribute indicates the state of force tagging option for this connection. Force tagging refers to setting the CLP bit for all cells on a connection. For CQC-based ATM cards, this attribute is not applicable and is not displayed. A value of enabled indicates that the CLP bit is being set to 1 for all cells in the transmit direction on this connection. A value of disabled indicates that the CLP bit is unchanged for cells in the transmit direction on this connection. disabled is always displayed for Vpts since forced tagging is applied on a per Vpt Vcc basis. Enumeration: 'disabled': 1, 'enabled': 0.

This attribute indicates the relative weight of this unshaped connection. Connections with a larger weight get a larger proportion of the link bandwidth or in the case of standard Vpt Vccs, the Vpt bandwidth. For all but standard Vpt Vccs, the default connection weight is determined by the weight policy for a service category and the traffic descriptor for a connection. For standard Vpt Vccs, the default connection weight is determined by the Vcc's service category. For CQC-based ATM cards, this attribute is not applicable and is not displayed. A value from 1 to 4095 indicates an actual weight. The value upToQueueLimit indicates that the weight of a connection is up to the transmit queue limit for this connection. upToQueueLimit is used with common (first-in-first-out) queueing. This attribute is displayed as notApplicable if: - this connection has trafficShaping displayed as linear or inverseUpc. - this is a basic Vpt. VALUES ( 0 = upToQueueLimit 65534 = notApplicable )

This attribute indicates the UPC state of the connection. A value of notApplicable indicates that UPC is not applicable or not supported for the connection. This is the case: - when the connection's rxTrafficDescType is 1 or 2. - for standard Vpt Vccs and basic Vpts. A value of notApplicable is set regardless of whether UPC is disabled or enabled in provisioning data. A value of disabled indicates that UPC is applicable and supported for the type of connection but has been turned off in the provisioning data. A value of enforced indicates that UPC is actively checking conformance for the connection and is discarding or tagging cells which do not conform to the connection traffic contract. The traffic descriptor parameters used for UPC conformance are reflected in the rxTrafficDescParms of the connection. On ATM IP cards, the counts of UPC violations are visible in the Vcc, Vpc or Vpt rxUpcViolationsOnEnforcer1 or rxUpcViolationsOnEnforcer2 attributes. ATM IP cards provide the ability to monitor UPC violations without tagging or discarding. A value of monitored indicates that UPC is actively checking conformance for the connection and counting the violations, but is not discarding or tagging cells which do not conform to the connection traffic contract. The traffic descriptor parameters used for UPC conformance are reflected in the rxTrafficDescParms of the connection. The counts of UPC violations are visible in the Vcc, Vpc or Vpt. rxUpcViolationsOnEnforcer1 or rxUpcViolationsOnEnforcer2 attributes. The value of monitored appears only on ATM IP cards. If the atmServiceCategory for this connection is availableBitRate, a value of enforced indicates that Dynamic Generic Cell Rate Algorithm (DGCRA) is active for the connection. The traffic descriptor parameters used for DGCRA enforcement are reflected in the rxTrafficDescParm of the connection. Enumeration: 'disabled': 1, 'notApplicable': 3, 'enforced': 0, 'monitored': 4.

This attribute indicates the current set of packet-wise discard functions in effect in the transmit data direction at this connection point. A value of ppd indicates that the Partial Packet Discard (PPD) function is in effect. PPD may be applied at an intermediate connecting point for a connection which is transporting frame traffic (AAL5 at the endpoint). PPD is controlled by provisioning for PVCs and SPVCs, and by call setup parameters in the AAL and Traffic Descriptor Information Elements. A value of epd indicates that the Early Packet Discard (EPD) function is in effect at this connection endpoint. On CQC-based ATM cards, PPD and EPD are enabled by default at a connection endpoint which is performing AAL5 segmentation and assembly. A value of wred indicates that Weighted Random Early Detection is in effect at this connection point. W-RED can be enabled by provisioning for PVCs and SPVCs. On ATM IP cards, all packet-wise discard functions also apply to provisioned virtual path connections (VPCs). On CQC-based ATM cards, packet-wise functions are not applicable for VPCs. This attribute is not applicable for Vpts. Description of bits: ppd(0) epd(1) wred(2)

This attribute indicates the current set of packet-wise discard functions in effect in the receive data direction at this connection point. A value of ppd indicates that the Partial Packet Discard (PPD) function is in effect. PPD may be applied at an intermediate connecting point for a connection which is transporting frame traffic (AAL5 at the endpoint). PPD is controlled by provisioning for PVCs and SPVCs, and by call setup parameters in the AAL and Traffic Descriptor Information Elements. A value of epd indicates that the Early Packet Discard (EPD) function is in effect at this connection endpoint. PPD and EPD are enabled by default at a connection endpoint which is performing AAL5 segmentation and assembly. On ATM IP cards, all packet-wise discard functions also apply to provisioned virtual path connections (VPCs). On CQC-based ATM cards, packet-wise functions are not applicable for VPCs. This attribute is not applicable for Vpts. Description of bits: ppd(0) epd(1)

This attribute is only of importance for connections which are carried on a link with a variable bandwidth. For example, the bandwidth may be reduced in the event that one or more physical links in the IMA group fail, such that the originally requested bandwidth cannot be maintained. This attribute shows whether the application (for example, Trunk) running on this connection can continue to operate if the bandwidth is reduced. If the bandwidth is reduced, the amount by which it is reduced is displayed in the bandwidthReduction attribute. A value of yes, indicates that this connection is elastic, and the bandwidth may be reduced but the connection is not released. A value of no indicates that the bandwidth for this connection is not reduced in the event of link bandwidth reduction. However, this connection may be released based on its holdingPriority. Bandwidth elasticity has no effect for connections which have an equivalent cell rate (ECR) of zero. This attribute is not applicable for Vpts and Vpt Vccs. Enumeration: 'yes': 1, 'no': 0.

This attribute shows the amount by which the bandwidth has been reduced for this connection. This value is non-zero only for connections which have bandwidthElastic displayed as yes, and which are also operating in a reduced bandwidth mode. This is typically the case for selected connections running over an IMA link. This attribute takes a value from 0 (no reduction) up to the ECR. For all connections which are running at their full allocated bandwidth, bwReduction has the value 0. Connections which have been reduced in allocated bandwidth have a positive number for this attribute. The bwReduction may be subtracted from the ECR (which is displayed as txTrafficDescParm 5) to determine the actual bandwidth allocated to this connection.

This attribute indicates the type of ABR behavior which is in effect at this connection. This attribute is only applicable if the atmServiceCategory attribute is availableBitRate. If the atmServiceCategory attribute is not availableBitRate, this attribute value is set to notApplicable. For CQC-based ATM cards and the 1pOC12SmLrAtm card, the notApplicable, efciSwitch or nonAbrInterworking. In EFCI marking mode, the Explicit Forward Congestion Indication (EFCI) field in the data cell headers is used to indicate transmit queue congestion. For ATM IP cards other than 1pOC12SmLrAtm, if the displayed as connectionEndPoint, this attribute has the value sourceDest. In this mode, the ABR Source and Destination behavior is in effect at this connection. This attribute is also sourceDest in the case where the next hop connection is specified as nonAbrInterworking. The next hop connection is the Vcc or Vpc identified by the nextHop attribute of the Nrp or Rp component. If the connectionPointType is not connectionEndPoint, the value of this attribute depends upon the abrConnectionType provisioning and the card type to which the traffic is forwarded on the backplane. The default abrConnectionType is provisioned at the CA Abr abrConnectionType attribute, and may be overridden for a provisioned connection in the Vcd Tm abrConnectionType or Vpd Tm abrConnectionType attribute. If the CA Abr abrConnectionType attribute is virtualSourceDest at either one of the two connection points, and if both the connection points are defined on ATM IP cards, virtual source and destination behavior is applied to the connection. In this instance, the attribute displays the value virtualSourceDest. This attribute has the value erSwitch if ABR explicit rate functionality is in effect at this connection. In this mode, the switch may modify the Explicit Rate (ER) field of backward Resource Management (RM) cells to indicate the status of congestion at this connection point. This attribute has the value nonAbrInterworking in the case where this connection point is functioning as an SPVC origin for an ABR connection where the link side of this connection is configured as a non-ABR ATM service category. This means that there are no RM cells on the link side of this connection, and that the next hop connection point is performing as an ABR sourceDest. Enumeration: 'nonAbrInterworking': 5, 'erSwitch': 1, 'efciSwitch': 2, 'notApplicable': 15, 'virtualSourceDest': 3, 'sourceDest': 4.

This attribute is a vector of five transmit traffic parameters whose mapping is defined by the txTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR), Minimum Cell Rate (MCR), actual cell rate (ACR), explicit rate (ER), equivalent cell rate (ECR), and actual shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. When txTrafficDescType is 1 or 2, parameters 1 through 5 are unused. In this description, PCR is the greater of either the PCR or the requested shaping rate (parameter 1 or parameter 5) specified in the txTrafficDescParm attribute under the Vcd Tm or Vpd Tm component. When txTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 or 1 traffic; parameters 2 and 3 are unused. When txTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard. When txTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging. When txTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic. When txTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic. When txTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic. When txTrafficDescType is 3, 4, 5, 6, 7, or 8, parameter 4 reflects the actual shaping rate in cell/s for this connection. For CQC-based ATM cards, the set of available shaping rates is based on the number of interfaces doing shaping (attribute perVcQueueInterfaces), and the shapingScalingFactor attribute of the Arc Cqc Override component. A rate of zero (0) indicates that shaping is not performed, or that the interface is down. When txTrafficDescType is 9, parameter 1 represents the PCR; parameter 2 represents the Cell Delay Variation Toleration (CDVT); parameter 3 represents the Minimum Cell Rate (MCR); the meaning of parameter 4 depends upon the value of the abrConnectionType attribute. if abrConnectionType is sourceDest or virtualSourceDest, parameter 4 represents the Allowed Cell Rate (ACR); If abrConnectionType is erSwitch, parameter 4 represents the Explicit Rate (ER); and if abrConnectionType is efciSwitch, parameter 4 reflects the actual shaping rate in cell/s for this connection. When txTrafficDescType is 3, 4, 5, 6, 7, 8, or 9, parameter 5 reflects the equivalent cell rate in cell/s for this connection as determined by the Connection Admission Control (CAC) algorithm. The equivalent cell rate is useful in determining the admission characteristics of this connection.

An entry in the mscAtmIfVpcTmTxTdpTable.

This variable represents the mscAtmIfVpcTmTxTdpTable specific index for the mscAtmIfVpcTmTxTdpTable.

This variable represents an individual value for the mscAtmIfVpcTmTxTdpTable.

This attribute indicates the queue limit and the discard thresholds for the transmit queue of this connection. If this connection has unshapedTransmitQueueing attribute displayed as common, this attribute displays the thresholds of the common queue. If this connection has unshapedTransmitQueueing attribute displayed as perVc or as notApplicable, this attribute displays the thresholds of the per-VC queue. The first element indicates the queue limit. The provisioned value of the transmit queue limit is derived from the txQueueLimit attribute under the service category subcomponents of the CA component for the service category of this connection. The second element is the threshold that marks the transition from congestion state 1 to congestion state 0. This is the threshold at which traffic with discard priority (DP) = 1 is discarded. This threshold is set at approximately 90 percent of the first parameter, the operational queue limit. The third element is the threshold that marks the transition from congestion state 2 to congestion state 1. This is the threshold at which traffic with DP = 2 is discarded. This threshold is set at approximately 75 percent of the first parameter, the operational queue limit. The fourth element is the threshold that marks the transition from congestion state 3 to congestion state 2. This is the threshold at which traffic with DP = 3 is discarded. This threshold is set at approximately 35 percent of the first parameter, the operational queue limit. This attribute does not apply to basic Vpts.

An entry in the mscAtmIfVpcTmTxQThreshTable.

This variable represents the mscAtmIfVpcTmTxQThreshTable specific index for the mscAtmIfVpcTmTxQThreshTable.

This variable represents an individual value for the mscAtmIfVpcTmTxQThreshTable.

This attribute is a vector of four traffic parameters whose meanings are defined by the rxTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR), minimum cell rate (MCR) are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. Cell delay variation tolerance (CDVT) is expressed in microseconds. When rxTrafficDescType is 1 or 2, none of the parameters are used. When rxTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard; parameter 4 represents the CDVT. When rxTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging; parameter 4 represents the CDVT. When rxTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 9, parameter 1 represents the PCR; parameter 2 represents CDVT; parameter 3 represents the MCR; parameter 4 is not used. If upc is disabled for this connection, the values of PCR, SCR, MBS and CDVT are the provisioned parameters. If upc is enabled, the values of PCR, SCR, MBS, and CDVT are exactly the values used by the usage parameter control hardware in policing the arriving traffic. These may vary slightly from the provisioned values due to granularity of the hardware. In the case where the PCR is equal to the SCR, the effective MBS is zero.

An entry in the mscAtmIfVpcTmRxTdpTable.

This variable represents the mscAtmIfVpcTmRxTdpTable specific index for the mscAtmIfVpcTmRxTdpTable.

This variable represents an individual value for the mscAtmIfVpcTmRxTdpTable.

This attribute is a vector of three elements that indicate the quality of service parameters for the forward direction for this connection. This attribute is used for SPVC and SVC connections on a PNNI interface. The cdv element indicates the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR and rt-VBR). The ctd element indicates the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR and rt-VBR). The clr element indicates the acceptable Cell Loss Ratio (CLR) of CBR, rt-VBR, and nrt-VBR connections.

An entry in the mscAtmIfVpcTmTqpTable.

This variable represents the mscAtmIfVpcTmTqpTable specific index for the mscAtmIfVpcTmTqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcTmTqpTable.

This attribute is a vector of three elements that indicate the quality of service parameters for the backward direction for this connection. This attribute is used for SPVC and SVC connections on a PNNI interface. The cdv element indicates the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR and rt-VBR). The ctd element indicates the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR and rt-VBR). The clr element indicates the acceptable Cell Loss Ratio (CLR) of CBR, rt-VBR, and nrt-VBR connections.

An entry in the mscAtmIfVpcTmRqpTable.

This variable represents the mscAtmIfVpcTmRqpTable specific index for the mscAtmIfVpcTmRqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcTmRqpTable.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This entry controls the addition and deletion of mscAtmIfVpcPm components.

A single entry in the table represents a single mscAtmIfVpcPm component.

This variable is used as the basis for SNMP naming of mscAtmIfVpcPm components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVpcPm tables.

This variable represents the index for the mscAtmIfVpcPm tables. Enumeration: 'linkSide': 0, 'switchSide': 1.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains attributes indicating the status of each Performance Monitoring (PM) measurement.

An entry in the mscAtmIfVpcPmStatusTable.

This attribute displays the Cell Loss Ratio (CLR) measurement status of the connection. inactive indicates the test is inactive. activating indicates the test is activating. active indicates the test is in progress activationFailed indicates the test failed to be activated. Refer to the failureCause attribute for failure cause. Enumeration: 'active': 2, 'inactive': 0, 'activating': 1, 'activationFailed': 3.

This attribute indicates the Availability Ratio (AR) measurement status of the connection. inactive indicates the test is inactive. activating indicates the test is activating. active indicates the test is in progress activationFailed indicates the test failed to be activated. Refer to the failureCause attribute for the failure cause. Enumeration: 'active': 2, 'inactive': 0, 'activating': 1, 'activationFailed': 3.

This attribute indicates the failure cause of Performance Monitoring (PM) measurements. The following are possible causes: noError indicates no error. unknownCause indicates unknown failure cause. softwareResourcesUnavailable indicates software resources reserved for a maximum of 255 active PMs on the local FP card have been used up. hardwareResourcesUnavailable indicates hardware resources reserved for a maximum of 512 active PMs CLR have been used up on the Link Side local card. remoteEndNoResponse indicates no response from remote end. activationCollision indicates activation collision was detected. Usually this is caused by both ends of the connection being provisioned to request PM. Only one end should be so provisioned. remoteEndRejectedActivation indicates the remote end has rejected an activation request. Usually this is due to the remote end reaching a resource limit. pcrUnsupported indicates the Tx or Rx PCR was out of range between 0 and 409600. nextHopCardUnsupported indicates the next hop card type is not supported. Enumeration: 'hardwareResourcesUnavailable': 3, 'remoteEndRejectedActivation': 6, 'pcrUnsupported': 7, 'activationCollision': 5, 'unknownCause': 1, 'noError': 0, 'softwareResourcesUnavailable': 2, 'nextHopCardUnsupported': 8, 'remoteEndNoResponse': 4.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains Cell Loss Ratio (CLR) measurements for the forward direction of the connection. The local end is always the provisioned end which sends the activation request, and the remote end is the end which receives the activation request.

An entry in the mscAtmIfVpcPmFwdClrTable.

This attribute displays the number of cells with CLP=0 received at the remote end over the last sample period.

This attribute displays the number of cells with CLP=0 transmitted from the local end over the last sample period.

This attribute displays CLR for CLP=0 traffic over the last sample period.

This attribute indicates the number of cells with CLP=0+1 received at the remote end over the last sample period.

This attribute indicates the number of cells with CLP=0+1 transmitted from the local end over the last sample period.

This attribute indicates CLR for CLP=0+1 traffic over the last sample period.

This attribute indicates the total time duration over which Cell Loss Ratio (CLR) has been calculated.

This attribute indicates the number of cells with CLP=0 received at the remote end over the total Cell Loss Ratio (CLR) measurement interval.

This attribute indicates the number of cells with CLP=0 transmitted from the local end over the total Cell Loss Ratio (CLR) measurement interval.

This attribute indicates the average CLR for CLP=0 traffic calculated for the total measurement interval.

This attribute indicates the maximum CLR for CLP=0 traffic calculated for the total measurement interval.

This attribute indicates the minimum CLR for CLP=0 traffic calculated for the total measurement interval.

This attribute indicates the number of cells with CLP=0+1 received at the remote end over the total Cell Loss Ratio (CLR) measurement interval.

This attribute indicates the number of cells with CLP=0+1 transmitted from the local end over the total CLR measurement interval.

This attribute displays the average CLR for CLP=0+1 traffic calculated for the total measurement interval.

This attribute indicates the maximum CLR for CLP=0+1 traffic calculated for the total measurement interval.

This attribute indicates the minimum CLR for CLP=0+1 traffic calculated for the total measurement interval.

This attribute indicates the total number of Performance Monitoring (PM) cells discarded.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains Cell Loss Ratio (CLR) measurements for the backward direction of the connection. The local end is always the provisioned end which sends the activation request, and the remote end is the end which receives the activation request.

An entry in the mscAtmIfVpcPmBwdClrTable.

This attribute indicates the number of cells with CLP=0 received at the local end over the last sample period.

This attribute indicates the number of cells with CLP=0 transmitted from the remote end over the last sample period.

This attribute indicates CLR for CLP=0 traffic over the last sample period.

This attribute indicates the number of cells with CLP=0+1 received at the local end over the last sample period.

This attribute indicates the number of cells with CLP=0+1 transmitted from the remote end over the last sample period.

This attribute display CLRfor CLP=0+1 traffic over the last sample period.

This attribute indicates the total time duration over which Cell Loss Ratio (CLR) measurement has been calculated.

This attribute indicates the number of cells with CLP=0 received at the local end over the total Cell Loss Ratio (CLR) measurement interval in the backward direction.

This attribute indicates the number of cells with CLP=0 transmitted from the remote end over the total Cell Loss Ratio (CLR) measurement interval.

This attribute indicates the average CLR for CLP=0 traffic calculated for the total measurement interval.

This attribute indicates the maximum CLR for CLP=0 traffi calculated for the total measurement interval.

This attribute indicates the minimum CLR for CLP=0 traffic calculated for the total measurement interval.

This attribute indicates the number of cells with CLP=0 received at the local end over the total Cell Loss Ratio (CLR) measurement interval.

This attribute indicates the number of cells with CLP=0+1 transmitted from the remote end over the total Cell Loss Ratio (CLR) measurement interval .

This attribute displays the average CLR for CLP=0+1 traffic calculated for the total measurement interval.

This attribute indicates the maximum CLR for CLP=0+1 traffic calculated for the total measurement interval.

This attribute indicates the minimum CLR for CLP=0+1 traffic calculated for the total measurement interval.

This attribute indicates the total number of Performance Monitoring (PM) cells discarded.

*** THIS TABLE CURRENTLY NOT IMPLEMENTED *** This group contains Availability Ratio (AR) measurements of the connection.

An entry in the mscAtmIfVpcPmArTable.

This attribute indicates the current status of the bidirectional connection for purposes of Availability Ratio (AR) computation. notApplicable means AR measurement was not requested on this connection. available means AR is running and considers the connection available (that is, the arAvailableTime attribute is being incremented). unavailable means AR measurement was requested but the connection is currently unavailable. Enumeration: 'available': 1, 'notApplicable': 0, 'unavailable': 2.

This attribute indicates the total time used for calculating Availability Ratio (AR) of the bi-directional connection.

This attribute indicates the total time the connection was available.

This attribute indicates the ratio of network availability representing the time to the total time of the connection.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which reuses this group. For component-specific information and the valid state combinations, refer to the appropriate NTP.

An entry in the mscAtmIfVpcStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock -force or Lock command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains operational information for a Vcc, Vpc, or Vpt component.

An entry in the mscAtmIfVpcOperTable.

This attribute reflects the role of the connection component at this interface. A value of connectionEndPoint indicates that user cells, end-to-end OAM cells, and segment OAM cells are processed by the connection component. A value of segmentEndPoint indicates that user cells and end-to- end OAM cells are relayed by the connection component, while segment OAM cells are processed by the connection component. A value of connectingPoint indicates that user cells, end-to-end OAM cells, and segment OAM cells are relayed by the connection component. A value of unknown indicates that the connection component is inactive. Enumeration: 'connectionEndPoint': 0, 'connectingPoint': 2, 'unknown': 3, 'segmentEndPoint': 1.

This group contains operational connection characteristics information for a Vcc component.

An entry in the mscAtmIfVpcConnInfoTable.

This attribute indicates the way data is distributed in the connection. A value of pointToPoint indicates this connection point is part of a point-to-point connection. A value of pointToMultipoint indicates this connection point is part of a point-to-multipoint connection. Enumeration: 'pointToPoint': 0, 'pointToMultipoint': 1.

This attribute indicates the number of destination leaves of the connection. If the distributionType is pointToPoint the value of this attribute is 0.

This attribute indicates the direction of the call setup request for an SVC. A value of fromLink means that the call setup originated from the link. A value of toLink means that the call setup was directed to the link. For PVC connections, the value of this attribute is notApplicable. For SPVC connections, the value of this attribute is notApplicable for Vccs with the SourcePVC and DestinationPVC subcomponents. For Signalling channels, the value of this attribute is notApplicable. Enumeration: 'fromLink': 0, 'toLink': 1, 'notApplicable': 2.

This group contains operational status information for a Vcc, Vpc or Vpt component.

An entry in the mscAtmIfVpcStatusTable.

This attribute indicates the present operational status of the Vcc, Vpc or Vpt component. Its value is dependent upon the current state of the segLinkSideLoopbackState and endToEndLoopbackState attributes. The value is end2endUp when the endToEndLoopbackState is good and the segLinkSideLoopbackState is either good or unknown. The value is end2endDown when the endToEndLoopbackState is bad and the segLinkSideLoopbackState is either good or unknown. The value is localUpEnd2endUnknown when the endToEndLoopbackState is unknown and the segLinkSideLoopbackState is good. The value is localDown when segLinkSideLoopbackState is bad. The value is localUpEnd2endUnknown when the endToEndLoopbackState is notApplicable and the segLinkSideLoopbackState is good. The value is unknown when the endToEndLoopbackState is either unknown or notApplicable and the segLinkSideLoopbackState is unknown. Enumeration: 'unknown': 0, 'localUpEnd2endUnknown': 3, 'end2endUp': 1, 'end2endDown': 2, 'localDown': 4.

This attribute indicates the failure cause of the Vcc, Vpc or Vpt component. noFailure indicates that there is currently no bandwidth related failure for this connection. portDown indicates that the interface corresponding to the parent AtmIf is down. localBwLoss indicates that the Ima corresponding to this AtmIf has lost some, but not all bandwidth, and as a result, this connection has been released. notAdmitted indicates that this connection has failed to be admitted by the Connection Admission Control (CAC) algorithm. appNotRegistered indicates that there is no application registered to use this connection. This may be the case, for example when there is a Vcc Test application, but the test has not been started. Check the status of the application to determine why it is not functional. disabledByApp indicates that the application using this connection has requested that the connection be disabled. An example is a connection used by a trunk application where the trunk has timed out on an attempt to stage. Check the application to determine why it is not fully functional. bwReduced indicates that this connection is operating in a reduced bandwidth state. It is a bandwidth elastic connection which currently has been allocated less than the requested (equivalent) bandwidth. vpDown indicates that this connection has been notified of a fault detected at the associated VP-layer. vpDown is applicable for Vpt Vccs only. Enumeration: 'bwReduced': 6, 'notAdmitted': 3, 'appNotRegistered': 4, 'portDown': 2, 'disabledByApp': 5, 'noFailure': 0, 'localBwLoss': 1, 'vpDown': 7.

This attribute indicates whether or not the connection is in a troubled state. Connections become troubled because of OAM failures; when one of the attributes segLinkSideLoopbackState, segSwitchSideLoopbackState, endToEndLoopbackState, aisState (when receiving AIS cells only) or rdiState go bad, this attribute is set to yes; otherwise it is set to no. Enumeration: 'yes': 1, 'no': 0.

This attribute contains the current state of the link-side segment loopback for this connection. Link-side segment loopback cells are transmitted (inserted) by a connection component in the direction of the link (port). The value of this attribute is dependent upon the current setting of the segLinkSideLoopback provisionable attribute, the connection point type as specified by the connectionPointType attribute, and the current loopback state (if applicable). The value is notApplicable when the connectionPointType is a connectingPoint. The value is notApplicable when the distributionType is pointToMultipoint. The value is good when the segLinkSideLoopback is on, the connectionPointType is a segmentEndPoint or a connectionEndPoint, and the segment link side loopback is working. The value is bad when the segLinkSideLoopback is on, the connectionPointType is a segmentEndPoint or a connectionEndPoint, and the link side segment loopback is not working. The value is unknown when the segLinkSideLoopback is off. The value is unknown when the segLinkSideLoopback is on, the connectionPointType is a segmentEndPoint and the segment switch side loopback has not yet been determined. The state of this attribute determines, in part, the value of the operStatus attribute. Enumeration: 'unknown': 2, 'bad': 1, 'good': 0, 'notApplicable': 3.

This attribute contains the current state of the switch-side segment loopback for this connection. Switch-side segment loopback cells are transmitted (inserted) by a connection component in the direction of the bus. The value of this attribute is dependent upon the current setting of the segSwitchSideLoopback provisionable attribute, the connection point type as specified by the connectionPointType attribute, and the current loopback state (if applicable). The value is only applicable when the connectionPointType is a segmentEndPoint. The value is notApplicable when the connectionPointType is a connectingPoint or connectionEndPoint. The value is notApplicable when the distributionType is pointToMultipoint. The value is good when the segSwitchSideLoopback is on, the connectionPointType is a segmentEndPoint and the segment switch side loopback is working. The value is bad when the segSwitchSideLoopback is on, the connectionPointType is a segmentEndPoint and the switch side segment loopback is not working. The value is unknown when the segSwitchSideLoopback is off. The value is unknown when the segSwitchSideLoopback is on, the connectionPointType is a segmentEndPoint and the segment switch side loopback has not been determined. Enumeration: 'unknown': 2, 'bad': 1, 'good': 0, 'notApplicable': 3.

This attribute contains the current state of the end-to-end loopback for this connection. Its value is dependent upon the current setting of the endToEndLoopback provisionable attribute and the connection point type as specified by the connectionPointType attribute. The value is only applicable when the connectionPointType is a connectionEndPoint. The value is notApplicable when the connectionPointType is a connectingPoint or segmentEndPoint. The value is notApplicable when the distributionType is a pointToMultipoint. The value is good when the endToEndLoopback is on, the connectionPointType is a connectionEndPoint and the end-to-end loopback is working. The value is bad when the endToEndLoopback is on, the connectionPointType is a connectionEndPoint and the end-to-end loopback is not working. The value is unknown when the endToEndLoopback is off. The value is unknown when the endToEndLoopback is on, the connectionPointType is a connectionEndPoint and the end-to-end loopback status has not been determined. The state of this attribute determines, in part, the value of the operStatus attribute. Enumeration: 'unknown': 2, 'bad': 1, 'good': 0, 'notApplicable': 3.

This attribute contains the current state of the receive side OAM cell congestion for this connection. Its value reflects whether the rate of received OAM cells for this connection is below a specified threshold. The connection maintains a count of the number of OAM cells which are terminated per second. Once that count exceeds the specified threshold, extraction of all OAM cells for this connection is disabled for a period of one minute. This is a congestion management mechanism to prevent the processor from being overloaded with handling OAM cells for a particular connection. This mechanism ensures that tasks, such as trunks obtain enough processor cycles to remain in service, and are not adversely affected by excessive rate of OAM cells on a particular connection. The value is good when the rate of received OAM cells is less than the allowed threshold. The value is bad when the arrival rate has exceeded the allowed threshold. It remains bad for one minute, before returning to good again. During this timeout, extraction of all OAM cells is disabled for this connection. As a result, other loopback failure conditions may occur. The value is unknown when the application has not yet begun to use this connection. An example is the Test component before a test has been started. Each type of OAM cell is counted separately. The threshold for AIS cells is three cells per second. If more than three AIS cells are received within a one second interval, this attribute is set to bad. The threshold for RDI cells and each loopback type is also three, but the threshold for trace cells is 250 per second. The state of this attribute has no direct effect on the value of the operStatus attribute or on the number of troubled connections. Enumeration: 'unknown': 2, 'bad': 1, 'good': 0, 'notApplicable': 3.

This attribute contains the current state of the Alarm Indication Signal for this connection. A value of good indicates that the connection's application is active and no alarm has occurred. A value of bad indicates that the connection's application is active and an alarm has occurred. A value of unknown indicates that the connection's application is inactive. A value of notApplicable occurs when the connectionPointType is either a segmentEndPoint or a connectingPoint. Enumeration: 'unknown': 2, 'bad': 1, 'good': 0, 'notApplicable': 3.

This attribute indicates the current state of the Remote Defect Indication for this connection. A value of good indicates that the connection's application is active and no alarm has occurred. A value of bad indicates that the connection's application is active and an alarm has occurred. A value of unknown indicates that the connection's application is inactive. A value of notApplicable occurs when the connectionPointType is either a segmentEndPoint or a connectingPoint. Enumeration: 'unknown': 2, 'bad': 1, 'good': 0, 'notApplicable': 3.

This group is HISTORICAL. Please refer to the group AtmTmOper; This attribute group contains attributes for the Vcc and Vpc components to reflect operational traffic attributes.

An entry in the mscAtmIfVpcTrafficTable.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the type of traffic management which is applied to the transmit direction of this connection as defined in the ATM Forum. The txTrafficDescType determines the number and meaning of the parameters in the txTrafficDescParm attribute. Enumeration: 'n8': 8, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute indicates the quality of service for the transmit direction for this connection. The constantBitRate class refers to traffic offered on services such as a constant bit rate video service. This traffic is highest priority. The variableBitRate class refers to traffic offered on services such as packetized audio and video. The connectionOriented class refers to connection-oriented traffic such as Frame Relay or X.25 traffic. The connectionless traffic refers to traffic offered through connectionless trunks such as certain LAN protocols. The unspecified class supports a 'best effort' type of service, where there is a minimum guarantee of bandwidth. This traffic is lowest priority. This attribute is obsolete, replaced by the UNI 4.0 attribute atmServiceCategory. Enumeration: 'constantBitRate': 1, 'connectionOriented': 3, 'variableBitRate': 2, 'connectionless': 4, 'unspecified': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the quality of service for the calling to called direction for this connection. This is only applicable to Soft PVC and SVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified QOS class; no objective is specified for the performance parameters. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the current length of the transmit queue for this connection. If this connection has traffic shaping disabled, then this attribute displays the common queue length. If traffic shaping is enabled, then this attribute displays the per-VC queue length.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the congestion state of the transmit queue for this connection. If the connection has traffic shaping disabled, then this attribute displays the common queue congestion state. If traffic shaping is enabled, then this attribute displays the per-VC queue congestion state. The congestion state of a queue is indicated by a numeric value ranging from 0 to 3. When a queue is in a congested state x, only traffic with discard priority (DP) 0 to x are enqueued. Traffic with DP > x is discarded. Therefore, if the congestion state is 3, there is no congestion and all traffic is enqueued. Likewise, when the congestion state is 0, there is maximum congestion and only traffic with DP=0 is enqueued on that queue.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the actual holding priority in effect for this connection. In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. Some applications, for example Vcc Test, may override the provisioned holding priority. A value of notApplicable is displayed when this is an elastic connection. Holding priority does not apply to bandwidth elastic connections. Holding priority has no effect for ubr atmServiceCategory or txTrafficDescriptorType 1 or 2 connections. Enumeration: 'notApplicable': 6, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the type of traffic management which is applied to the receive direction of this connection as defined in the ATM Forum. The rxTrafficDescType determines the number and meaning of the parameters in the rxTrafficDescParm attribute. Enumeration: 'n8': 8, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute reflects the value of the provisioned attribute in the Vcd or Vpd. Refer to that attribute for more detailed explanation. This attribute is obsolete replaced by the UNI 4.0 attribute atmServiceCategory. Enumeration: 'constantBitRate': 1, 'connectionOriented': 3, 'variableBitRate': 2, 'connectionless': 4, 'unspecified': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the quality of service for the called to calling direction for this connection. This is only applicable to Soft PVC and SVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified QOS class; no objective is specified for the performance parameters. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the ATM service category used for traffic in both directions of the connection. The constantBitRate service category is intended for real time applications, that is, those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to have significantly reduced value of the application. The rtVariableBitRate service category is intended for real time applications; that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications, that is those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the traffic shaping state of the connection. A value of notApplicable indicates that traffic shaping is not applicable or not supported for this connection. This is the case when the atmServiceCategory is constantBitRate, or when the txTrafficDescType is 1 or 2. In these cases, the value of notApplicable is set regardless of whether traffic shaping is enabled or disabled in the provisioning data. A value of disabled indicates that traffic shaping is applicable and supported for the type of connection but has been turned off in the provisioning data. A value of enabled indicates that traffic shaping is applicable and supported for the type of connection and has been turned on in the provisioning data. This is the only case that indicates that traffic shaping is performed on the connection. In this case, the actual shaping rate is reflected in the txTrafficDescParm attribute, parameter number 4. Enumeration: 'disabled': 1, 'notApplicable': 4, 'enabled': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the bearer capability for this connection. Class a service is a connection-oriented, constant bit rate ATM transport service. Class a service has end to end timing requirements and may require stringent cell loss, cell delay and cell delay variation performance.When a is displayed, the user is requesting more than an ATM only service. The network may look at the AAL to provide interworking based upon its contents. Class c service is a connection-oriented, variable bit rate ATM transport service. Class c service has no end-to-end timing requirements.When c is displayed, the user is requesting more than an ATM only service. The network interworking function may look at the AAL and provide service based on it. Class x service is a connection-oriented ATM transport service where the AAL, trafficType (cbr or vbr) and timing requirements are user defined (that is, transparent to the network). When the value of this attribute is x, the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. Class vp service is used to indicate a transparent VP service when the user is requesting an ATM only service from the network. In this case, the network does not process any higher layer protocol. This service differs from class x service in that with the class vp service both the VCI field (except for VCI values 0, 3, 4, and 6 through 15) and Payload Type field are transported transparently by the network. This attribute value is only applicable to SPVP and SVP connections. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'a': 1, 'x': 16, 'c': 3, 'vp': 24, 'notApplicable': 30.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the transfer capability for this connection. Uni 3.0/3.1 traffic type and end-to-end timing parameters are mapped into this parameter as follows: 0: NoIndication, NoIndication 1: NoIndication, yes 2: NoIndication, no 5: CBR, yes 8: VBR, NoIndication 9: VBR, yes 10: VBR, no A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance, or in the case that the transfer capability in the call request was set to NoIndication. The CBR traffic type refers to traffic offered on services such as a constant bit rate video service or a circuit emulation. The VBR traffic type refers to traffic offered on services such as packetized audio and video, or data. The value NoIndication for traffic type is used if the user has not set the traffic type; similarly for end-to-end timing. The value yes for end-to-end timing indicates that end-to-end timing is required for the connection. The value no for end-to-end timing indicates that end-to-end timing is not required for the connection. Enumeration: 'n10': 10, 'notApplicable': 30, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n5': 5.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the value of the clipping susceptibility parameter in the BBC Information Element. Clipping is an impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'yes': 1, 'no': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the unshaped transmit queuing state of the connection. A value of common indicates that transmit traffic is being enqueued onto common transmit queues. A value of perVc indicates that transmit traffic is being enqueued onto a per-VC queue for this connection. This is the case when trafficShaping is disabled, but per-VC queueing has been configured for this connection. A value of notApplicable indicates that transmit traffic is being shaped for this connection. Transmit traffic for a shaped connection is enqueued onto a per-VC queue, but this attribute is only applicable for unshaped connections. Enumeration: 'notApplicable': 4, 'perVc': 0, 'common': 1.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates value of best effort parameter in the ATM Traffic Descriptor Information Element. The value indicated implies that the quality of service for this connection is not guaranteed. The value notIndicated implies that the quality of service for this connection is guaranteed. A value of notApplicable is displayed in the case of nailed-up PVCs for which this attribute has no significance. Enumeration: 'notApplicable': 14, 'notIndicated': 1, 'indicated': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the UPC state of the connection. A value of notApplicable indicates that UPC is not applicable or not supported for the connection. This is the case when the connection's rxTrafficDescType is 1 or 2. A value of notApplicable is set regardless of whether UPC is disabled or enabled in provisioning data. A value of disabled indicates that UPC is applicable and supported for the type of connection but has been turned off in the provisioning data. A value of enabled indicates that UPC is applicable and supported for the type of connection and has been turned on in the provisioning data. This is the only case that indicates that UPC is enforced on the connection. In this case the traffic descriptor parameters used for UPC enforcement are reflected in the rxTrafficDescParms of the connection. Enumeration: 'disabled': 1, 'notApplicable': 3, 'enabled': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the set of current frame discard functions in effect in the transmit data direction at this connection point. A value of ppd indicates that the Partial Packet Discard (PPD) function is in effect. PPD may be applied at an interim connecting point for a connection which is transporting frame traffic (AAL5 at the endpoint). PPD is controlled by provisioning for PVCs and SPVCs, and by call setup parameters in the AAL and Traffic Descriptor Information Elements. A value of epd indicates that the Early Packet Discard (EPD) function is in effect at this connection endpoint. PPD and EPD are enabled by default at a connection endpoint which is performing AAL5 segmentation and assembly. Frame discard functions are not applicable for Virtual Path Connections (VPCs). Description of bits: ppd(0) epd(1)

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the set of current frame discard functions in effect in the receive data direction at this connection point. A value of ppd indicates that the Partial Packet Discard (PPD) function is in effect. PPD may be applied at an interim connecting point for a connection which is transporting frame traffic (AAL5 at the endpoint). PPD is controlled by provisioning for PVCs and SPVCs, and by call setup parameters in the AAL and Traffic Descriptor Information Elements. A value of epd indicates that the Early Packet Discard (EPD) function is in effect at this connection endpoint. PPD and EPD are enabled by default at a connection endpoint which is performing AAL5 segmentation and assembly. Frame discard functions are not applicable for Virtual Path Connections (VPCs). Description of bits: ppd(0) epd(1)

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute is only of importance for connections which are carried on a link with a variable bandwidth. For example, the bandwidth may be reduced in the event that one or more physical links in the IMA group fail, such that the originally requested bandwidth cannot be maintained. This attribute shows whether the application (for example, Trunk) running on this connection can continue to operate if the bandwidth is reduced. If the bandwidth is reduced, the amount by which it is reduced is displayed in the bandwidthReduction attribute. A value of yes, indicates that this connection is elastic, and the bandwidth may be reduced but the connection is not released. A value of no indicates that the bandwidth for this connection is not reduced in the event of link bandwidth reduction. However, this connection may be released based on its holdingPriority. Bandwidth elasticity has no effect for ubr atmServiceCategory or txTrafficDescriptorType 1 or 2 connections. Enumeration: 'yes': 1, 'no': 0.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute shows the amount by which the bandwidth has been reduced for this connection. This value is non-zero only for connections which have bandwidthElastic displayed as yes, and which are also operating in a reduced bandwidth mode. This is typically be the case for selected connections running over an IMA link. This attribute takes a value from 0 (no reduction) up to the ECR. All connections which are running at their full allocated bandwidth, bwReduction have the value 0. Connections which have been reduced in allocated bandwidth have a positive number for this attribute. The bwReduction may be subtracted from the ECR (which is displayed as txTrafficDescParm 5) to determine the actual bandwidth allocated to this connection.

This group contains traffic statistics for a Vcc, Vpc, or Vpt component.

An entry in the mscAtmIfVpcStatsTable.

This attribute counts the number of cells that have been transmitted from the interface on this connection. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells that have been transmitted from the interface on this connection with the CLP=1. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute is replaced by new attributes txCellDiscard and txFrameDiscard. This attribute counts the number of cells or frames received from the bus on this connection that have been discarded. If the connection segments frames into cells, the counter indicates the number of frames discarded. Connections which segment frames into cells have a connectionPointType of connectionEndPoint. If the connection relays cells without adaptation, the counter indicates the number of cells discarded. Connections which relay cells without adaptation have a connectionPointType of segmentEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. Thus, in the AAL1 case, this attribute counts discarded cells. Discards are done due to congestion or when the connection's interface is disabled. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute is replaced by new attributes txCellDiscardClp and txFrameDiscardClp. This attribute counts the number of cells or frames received from the bus on this connection with CLP=1 that have been discarded. If the connection segments frames into cells, the counter indicates the number of frames discarded. Connections which segment frames into cells have a connectionPointType of connectionEndPoint. If the connection relays cells without adaptation, the counter indicates the number of cells discarded. Connections which relay cells without adaptation have a connectionPointType of segmentEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. Thus, in the AAL1 case, this attribute counts discarded cells. Discards are done due to congestion or when the connection's interface is disabled. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells received from the bus on this connection that have been discarded. Discarded cells are not counted in the txCell attribute. Cells are discarded due to transmit congestion, Partial Packet Discard (PPD), Early Packet Discard (EPD), and Weighted Random Early Detection (W-RED) mechanisms, or when the connection's interface is disabled. For CQC-based ATM cards, this attribute is applicable only to connections that relay cells without adaptation. Such connections usually have a connectionPointType of segmentEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all txCellDiscard values for all such connections associated with the Vpt. For Vccs on CQC-based ATM cards, if the connection segments frames into cells, this attribute is not applicable and is not displayed. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells received from the bus on this connection with CLP=1 that have been discarded. This count is included in the txCellDiscard attribute. Discarded cells are not counted in the txCellClp attribute. Cells are discarded due to transmit congestion, Partial Packet Discard (PPD), Early Packet Discard (EPD), and Weighted Random Early Detection (W-RED) mechanisms, or when the connection's interface is disabled. For CQC-based ATM cards, this attribute is applicable only to connections that relay cells without adaptation. Such connections have a connectionPointType of segmentEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all txCellDiscardClp values for all such connections associated with the Vpt. For Vccs on CQC-based ATM cards, if the connection segments frames into cells, this attribute is not applicable and is not displayed. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of frames received from the bus on this connection that have been discarded. Frames are discarded due to congestion, Partial Packet Discard (PPD), Early Packet Discard (EPD), and Weighted Random Early Detection (W-RED) mechanisms, or when the connection interface is disabled. This count is independent of the txCell or txCellDiscard attribute. For CQC-based ATM cards, this attribute is applicable only to connections that segment frames into cells. Such connections have a connectionPointType of connectionEndPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all txFrameDiscard values for all such connections associated with the Vpt. For CQC-based ATM cards, for Vpcs, and Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. Discards due to EPD, PPD, and W-RED for a standard Vpt Vcc are not included in this attribute. These discards are counted in the Vcc's parent Vpt txFrameDiscard attribute. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of discarded frames on this connection that were received from the bus and composed of one or more CLP=1 cells. Frames are discarded due to congestion, Partial Packet Discard (PPD), Early Packet Discard (EPD), and Weighted Random Early Detection (W-RED) mechanisms, or when the connection interface is disabled. This count is included in the txFrameDiscard attribute. For CQC-based ATM cards, this attribute is applicable only to connections that segment frames into cells. Such connections have a connectionPointType of connectionEndPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all txFrameDiscardClp values for all such connections associated with the Vpt. For CQC-based ATM cards, for Vpcs and Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. Discards due to EPD, PPD, and W-RED for a standard Vpt Vcc are not included in this attribute. These discards are counted in the Vcc's parent Vpt txFrameDiscardClp attribute. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells that have been received from the interface on this connection. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells that have been received from the interface on this connection with the CLP=1. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute is replaced by new attributes rxCellDiscard and rxFrameDiscard. This attribute counts the number of cells or frames received from the interface on this connection that have been discarded. If the connection segments frames into cells, the counter indicates the number of frames discarded. Connections which segment frames into cells have a connectionPointType of connectionEndPoint. If the connection relays cells without adaptation, the counter indicates the number of cells discarded. Connections which relay cells without adaptation have a connectionPointType of segmentEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. Thus, in the AAL1 case, this attribute counts discarded cells. Discards are done due to congestion, non-conformance with UPC or AAL reassembly problems. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute is replaced by new attributes rxCellDiscardClp and rxFrameDiscardClp. This attribute counts the number of cells or frames received from the interface on this connection with CLP=1 that have been discarded. If the connection segments frames into cells, the counter indicates the number of frames discarded. Connections which segment frames into cells have a connectionPointType of connectionEndPoint. If the connection relays cells without adaptation, the counter indicates the number of cells discarded. Connections which relay cells without adaptation have a connectionPointType of segmentEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. Thus, in the AAL1 case, this attribute counts discarded cells. Discards are done due to congestion, non-conformance with UPC or AAL reassembly problems. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells received from the interface on this connection that have been discarded. This count is included in the rxCell attribute. This count includes cells discarded due to non-conformance with UPC, cells which are part of a frame which has been discarded due to an AAL5 frame reassembly error, cells which are discarded due to congestion, or cells which are received while the next hop connection to which the traffic is directed across the backplane is down. The next hop connection is the Vcc or Vpc identified by the nextHop attribute of the Nrp or Rp component. For CQC-based ATM cards, this attribute is applicable only to connections that relay cells without adaptation. Such connections have a connectionPointType of connectionEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all rxCellDiscard values for all such connections associated with the Vpt. For CQC-based ATM cards, for Vpcs, and Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. Discards due to non-conformance with UPC at the VP layer, for a standard Vpt Vcc, are not included in this attribute. These discards are counted in the Vcc's parent Vpt rxCellDiscard attribute. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of cells received from the interface on this connection with CLP=1 that have been discarded. This count is included in the rxCell and rxCellDiscard attributes. This count includes cells discarded due to non-conformance with UPC, cells which are part of a frame which has been discarded due to an AAL5 frame reassembly error, cells which are discarded due to congestion, or cells which are received while the next hop connection to which the traffic is directed across the backplane is down. The next hop connection is the Vcc or Vpc identified by the nextHop attribute of the Nrp or Rp component. For CQC-based ATM cards, this attribute is applicable only to connections that relay cells without adaptation. Such connections have a connectionPointType of connectionEndPoint or connectingPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all rxCellDiscard values for all such connections associated with the Vpt. For CQC-based ATM cards, for Vpcs, and Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. Discards due to non-conformance with UPC at the VP layer, for a standard Vpt Vcc, are not included in this attribute. These discards are counted in the Vcc's parent Vpt rxCellDiscard attribute. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of frames received from the interface on this connection that have been discarded. This count is independent of the rxCellDiscard attribute. This count includes frames discarded due to an AAL5 frame reassembly error, frames discarded due to early packet discard (EPD), and frames discarded due to processor (CPU) congestion. This attribute is applicable only to connections that reassemble incoming cells into frames. Connections which reassemble cells into frames have a connectionPointType of connectionEndPoint. AAL1 connections are an exception to this rule; even though they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all rxFrameDiscard values for all applicable connections associated with the Vpt. For Vpcs and for Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of discarded frames on this connection that were received from the interface and composed of one or more CLP1 cells. This count is included in the rxFrameDiscard attribute. It is independent of the rxCellDiscard attribute. This count includes frames discarded due to an AAL5 frame reassembly error, frames discarded due to early packet discard (EPD), and frames discarded due to processor (CPU) congestion. This attribute is applicable only to connections that reassemble incoming cells into frames. Such connections have a connectionPointType of connectionEndPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all rxFrameDiscardClp values for all applicable connections associated with the Vpt. For Vpcs and for Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of UPC violations observed by the Generic Cell Rate Algorithm (GCRA) Enforcer 1. This attribute is only applicable if UPC is enforced or monitored. This attribute is not applicable for standard Vpt Vccs. This attribute is not applicable and is not displayed on CQC-based ATM cards. When the value of rxTrafficDescType for this connection is 3, 4, 5, 6, 7 or 8, Enforcer 1 enforces conformance of traffic received from the interface to PCR CLP0+1. When the value of rxTrafficDescType for this connection is 9, Enforcer 1 performs the Dynamic Generic Cell Rate Algorithm (DGCRA) used for the Available Bit Rate (ABR) service category. If UPC is enforced all non-conforming cells are discarded by this enforcer. These discarded cells are included in rxCellDiscard. For basic Vpts, this attribute provides an aggregated total of all rxUpcViolationOnEnforcer1 values for the Vccs associated with the Vpt. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of UPC violations observed by the Generic Cell Rate Algorithm (GCRA) Enforcer 2. This attribute is only applicable if UPC is enforced or monitored. This attribute is not applicable for standard Vpt Vccs. This attribute is not applicable and is not displayed on CQC-based ATM cards. Enforcer2 is applicable only if the rxTrafficDescType for this connection is 4, 5, 6, 7 or 8. When the value of rxTrafficDescType 4 or 5, Enforcer 2 enforces conformance of traffic received from the interface to PCR CLP0. When the value of rxTrafficDescType 6, Enforcer 2 enforces conformance of traffic received from the interface to SCR CLP0+1. When the value of rxTrafficDescType 7 or 8, Enforcer 2 enforces conformance of traffic received from the interface to SCR CLP0. If UPC is enforced, enforcer 2 discards non-conforming cells for rxTrafficDescType values of 4, 6 and 7. It tags non-conforming cells for rxTrafficDescType values of 5 and 8. Discarded cells are counted in the rxCellDiscard attribute. For basic Vpts, this attribute provides an aggregated total of all rxUpcViolationOnEnforcer2 values for the Vccs associated with the Vpt. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of frames received from the interface on this connection that have AAL5 length errors or AAL5 CRC errors. This attribute is not applicable and is not displayed on CQC-based ATM cards. AAL5 length or CRC errors typically occur because of cell discards due to congestion, UPC, or due to corruption of data between the AAL5 segmentation and reassembly end points. This attribute is applicable only to connections that reassemble incoming cells into frames. Such connections have a connectionPointType of connectionEndPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all rxAal5FrameError values for all applicable connections associated with the Vpt. For Vpcs and for Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This attribute counts the number of frames received from the interface on this connection that have the AAL5 length field set to zero. This attribute is not applicable and is not displayed for CQC-based ATM cards. An AAL5 length of zero is an indication by the far end segmentation point to this reassembly point that the frame is to be discarded without reassembly. This mechanism is typically used by a segmentation point if it detects an error in a frame after some of the cells belonging to that frame have already been transmitted. This attribute is applicable only to connections that reassemble incoming cells into frames. Such connections have a connectionPointType of connectionEndPoint. AAL1 connections are an exception to this rule; although they have a connectionPointType of connectionEndPoint, they do not do adaptation at this point. For Vpts, this attribute provides an aggregated total of all rxAal5FrameAbort values for all applicable connections associated with the Vpt. For Vpcs and for Vccs that relay cells without adaptation, this attribute is not applicable and is not displayed. The counter wraps to zero if it exceeds its maximum value of (2**64)-1.

This group contains operational attributes which keep performance statistics about the behavior of the AtmIf component.

An entry in the mscAtmIfVpcPerfTable.

This attribute indicates the minimum calculated cell transfer delay value for this connection from the previous TODA (time of day accounting) interval if TODA is enabled; or for the previous 12 hour interval if TODA is disabled. Cell transfer delay is calculated as half of the measured segment round trip delay of a loopback cell. The value is noMeasurement when the ctdCalculation attribute of the AtmIf component is off. The value is noMeasurement when the accountCollection attribute of the AtmIf Uni or AtmIf Iisp component has a non-empty reason. The value is noMeasurement when the segSwitchSideLoopback attribute value is off for the connection. The value is noMeasurement when the switch-side loopback is not working. The value is noMeasurement when the switch-side loopback status cannot be determined. VALUES ( 0 = noMeasurement )

This attribute indicates the maximum calculated cell transfer delay value for this connection from the previous TODA (time of day accounting) interval if TODA is enabled; or for the previous 12 hour interval if TODA is disabled. Cell transfer delay is calculated as half of the measured segment round trip delay of a loopback cell. The value is noMeasurement when the ctdCalculation attribute of the AtmIf component is off. The value is noMeasurement when the accountCollection attribute of the AtmIf Uni or AtmIf Iisp component has a non-empty reason. The value is noMeasurement when the segSwitchSideLoopback attribute value is off for the connection. The value is noMeasurement when the switch-side loopback is not working. The value is noMeasurement when the switch-side loopback status cannot be determined. VALUES ( 0 = noMeasurement )

This attribute indicates the average of all calculated cell transfer delay values for this connection from the previous TODA (time of day accounting) interval if TODA is enabled; or for the previous 12 hour interval if TODA is disabled. Cell transfer delay is calculated as half of the measured segment round trip delay of a loopback cell. The value is noMeasurement when the ctdCalculation attribute of the AtmIf component is off. The value is noMeasurement when the accountCollection attribute of the AtmIf Uni or AtmIf Iisp component has a non-empty reason. The value is noMeasurement when the segSwitchSideLoopback attribute value is off for the connection. The value is noMeasurement when the switch-side loopback is not working. The value is noMeasurement when the switch-side loopback status cannot be determined. VALUES ( 0 = noMeasurement )

This attribute indicates the most recent cell transfer delay value calculated for this connection. Cell transfer delay is calculated as half of the measured segment round trip delay of a loopback cell. The value is noMeasurement when the ctdCalculation attribute of the AtmIf component is off. The value is noMeasurement when the segSwitchSideLoopback attribute value is off for the connection. The value is noMeasurement when the switch-side loopback is not working. The value is noMeasurement when the switch-side loopback status cannot be determined. VALUES ( 0 = noMeasurement )

This attribute indicates the number of loopback cells sampled for cell transfer delay calculations during the previous TODA (time of day accounting) interval if TODA is enabled; or for the previous 12 hour interval of TODA is disabled.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute is a vector of five transmit traffic parameters. The first three elements reflect the settings of the first three elements of the txTrafficDescParm attribute in the AtmTrafficProv group. When txTrafficDescType is 1 or 2, parameters 1 through 5 are unused. In this description, PCR is the greater of either the PCR or the requested shaping rate (parameter 1 or parameter 5) specified in the Traffic group under the Vcd or Vpd. When txTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 or 1 traffic; parameters 2 and 3 are unused. When txTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard. When txTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging. When txTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic. When txTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic. When txTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic When txTrafficDescType is 3, 4, 5, 6, 7 or 8, parameter 4 reflects the actual shaping rate in cell/s for this connection. This rate is one of the set of available shaping rates for this type of ATM-FP, based on the number of interfaces doing shaping (attribute perVcQueueInterfaces), the provisioned cell rate, the shapingScalingFactor attribute of the AtmResourceControl component, and whether traffic shaping is enabled. A rate of zero (0) indicates that shaping is not performed. When txTrafficDescType is 3, 4, 5, 6, 7 or 8, parameter 5 reflects the equivalent cell rate in cell/s for this connection as determined by the Connection Admission Control (CAC) algorithm. The equivalent cell rate is useful in determining the admission characteristics of this connection.

An entry in the mscAtmIfVpcTxTdpTable.

This variable represents the mscAtmIfVpcTxTdpTable specific index for the mscAtmIfVpcTxTdpTable.

This variable represents an individual value for the mscAtmIfVpcTxTdpTable.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute is a vector of four traffic parameters whose meanings are defined by the rxTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) are expressed in cells/s. Maximum burst size (MBS) is expressed in cells. Cell Delay Variation Tolerance (CDVT) is expressed in microseconds. When rxTrafficDescType is 1 or 2, none of the parameters are used. When rxTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard; parameter 4 represents the CDVT. When rxTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging; parameter 4 represents the CDVT. When rxTrafficDescType is a 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT. When rxTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT. If Upc is disabled for this connection, the values of PCR, SCR, MBS and CDVT is a combination of provisioned parameters. If Upc is enabled, the values of PCR, SCR, MBS, and CDVT is exactly the values used by the usage parameter control hardware in policing the arriving traffic. These may vary slightly from the provisioned values due to granularity of the hardware. In the case where the PCR is equal to the SCR, the effective MBS is zero.

An entry in the mscAtmIfVpcRxTdpTable.

This variable represents the mscAtmIfVpcRxTdpTable specific index for the mscAtmIfVpcRxTdpTable.

This variable represents an individual value for the mscAtmIfVpcRxTdpTable.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute indicates the queue limit and the discard thresholds for the transmit queue of this connection. The first element indicates the queue limit. Depending upon the atmServiceCategory of the connection, the provisioned value of the transmit queue limit is derived from the txQueueLimit attribute under one of the subcomponents of the AtmIf CA component. If the connection has traffic shaping disabled, then this attribute relates to the common queue. If traffic shaping is enabled, then this attribute relates to the per-VC queue. The second element is the threshold that marks the transition from congestion state 1 to congestion state 0. This is the threshold at which traffic with discard priority (DP) = 1 is discarded. This threshold is set approximately at 90 percent of the first parameter, the operational queue limit. The third element is the threshold that marks the transition from congestion state 2 to congestion state 1. This is the threshold at which traffic with DP = 2 is discarded. This threshold is set approximately at 75 percent of the first parameter, the operational queue limit. The fourth element is the threshold that marks the transition from congestion state 3 to congestion state 2. This is the threshold at which traffic with DP = 3 is discarded. This threshold is set approximately at 35 percent of the first parameter, the operational queue limit.

An entry in the mscAtmIfVpcTxQThreshTable.

This variable represents the mscAtmIfVpcTxQThreshTable specific index for the mscAtmIfVpcTxQThreshTable.

This variable represents an individual value for the mscAtmIfVpcTxQThreshTable.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute is a vector of three elements that indicate the quality of service parameters for the forward direction for this connection. This attribute is used for SPVC and SVC connections on a PNNI interface. The cdv element indicates the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR, and rt-VBR). The ctd element indicates the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR, and rt-VBR). The clr element indicates the acceptable Cell Loss Ratio (CLR) of CBR, rt-VBR, and nrt-VBR connections.

An entry in the mscAtmIfVpcFqpTable.

This variable represents the mscAtmIfVpcFqpTable specific index for the mscAtmIfVpcFqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcFqpTable.

This attribute is HISTORICAL. Please refer to the attribute of the same name in the group AtmTmOper. This attribute is a vector of three elements that indicate the quality of service parameters for the backward direction for this connection. This attribute is used for SPVC and SVC connections on a PNNI interface. The cdv element indicates the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR, and rt-VBR). The ctd element indicates the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR, and rt-VBR). The clr element indicates the acceptable Cell Loss Ratio (CLR) of CBR, rt-VBR, and nrt-VBR connections.

An entry in the mscAtmIfVpcBqpTable.

This variable represents the mscAtmIfVpcBqpTable specific index for the mscAtmIfVpcBqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVpcBqpTable.

This entry controls the addition and deletion of mscAtmIfVcc components.

A single entry in the table represents a single mscAtmIfVcc component.

This variable is used as the basis for SNMP naming of mscAtmIfVcc components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVcc tables.

This variable represents the index for the mscAtmIfVcc tables.

This entry controls the addition and deletion of mscAtmIfVccVcd components.

A single entry in the table represents a single mscAtmIfVccVcd component.

This variable is used as the basis for SNMP naming of mscAtmIfVccVcd components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVccVcd tables.

This variable represents the index for the mscAtmIfVccVcd tables.

This entry controls the addition and deletion of mscAtmIfVccVcdTm components.

A single entry in the table represents a single mscAtmIfVccVcdTm component.

This variable is used as the basis for SNMP naming of mscAtmIfVccVcdTm components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVccVcdTm tables.

This variable represents the index for the mscAtmIfVccVcdTm tables.

This entry controls the addition and deletion of mscAtmIfVccVcdTmAbr components.

A single entry in the table represents a single mscAtmIfVccVcdTmAbr component.

This variable is used as the basis for SNMP naming of mscAtmIfVccVcdTmAbr components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVccVcdTmAbr tables.

This variable represents the index for the mscAtmIfVccVcdTmAbr tables.

This group contains provisioned attributes for the ABR ATM connections configured on an ATM interface.

An entry in the mscAtmIfVccVcdTmAbrProvTable.

This attribute specifies the Initial Cell Rate (ICR) parameter for this connection. ICR is the rate at which a source should send initially and after an idle period. When this attribute is set to sameAsCa, the initial cell rate is determined by the AtmIf CA Abr/0 icr attribute. When the value of this attribute is set to useMcr, ICR is set to the same value as the Minimum Cell Rate (MCR) for the connection. When the value of this attribute is set to usePcr, ICR is set to the same value as the Peak Cell Rate (PCR) for the connection. If this attribute is specified less than the MCR of the connection, then the MCR is used as the ICR. If this attribute is specified more than PCR of the connection, then PCR is used as the ICR. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch. VALUES ( 16777216 = sameAsCa 16777217 = useMcr 16777218 = usePcr )

This attribute specifies the Transient Buffer Exposure (TBE) for this connection. TBE is the negotiated number of cells that the network would like to limit the source to send during start-up periods, before the first Resource Management (RM) cell returns. TBE divided by fixedRoundTripTime determines an upper bound for the operational value of initialCellRate, the rate at which a source should send initially and after an idle period. TBE divided by maxCellsPerRmCell specifies the operational value of forwardRmCellLimit, the limit of the number of forward Resource Management (RM) cells which may be sent in the absence of received backward RM cells. This attribute is ignored under all conditions where the operational attribute abrConnectionType is set to erSwitch.

This attribute specifies the Fixed Round-Trip Time (FRTT) parameter for this connection. FRTT is the sum of the fixed and propagation delays from the source to a destination and back. The value of transientBufferExposure divided by the value of FRTT (in seconds) determines an upper bound for the operational value of initialCellRate, the rate at which a source should send initially and after an idle period. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch.

This attribute specifies the Rate Decrease Factor (RDF) for this connection. The RDF value is computed by using the provisioned value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 8, RDF is 2E-8 = 1/256. RDF controls the amount by which the cell transmission rate may decrease upon receipt of a backward Resource Management (RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) field set to 1, the Allowed Cell Rate (ACR) value would be reduced by the amount (RDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Rate Increase Factor (RIF) for this connection. The RIF value is computed by using the provisioned value of this attribute, n, as 2 to the inverse power n. For example, if the value of this attribute is 6, RIF is 2E-6 = 1/64. RIF controls the amount by which the cell transmission rate may increase upon receipt of a backward Resource Management (RM) cell. For example, if a backward RM cell is received with the Congestion Indication (CI) and the No Increase (NI) fields both set to 0, the Allowed Cell Rate (ACR) value would be increased by the amount (RIF*ACR). The ACR is not allowed to exceed the Peak Cell Rate (PCR), in which case the ACR is set to PCR. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the maximum number of cells an ABR source may transmit for each forward Resource Management (RM) cell. The count of the cells transmitted includes data cells, OAM cells, backward RM cells, and the forward RM cell. A value of 2 is not recommended although it is permitted according to the ATM Forum standard. When this attribute is set to a value of 2, it is possible that only one forward and one backward RM cell are repeatedly transmitted, and all data traffic is queued up indefinitely. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the TRM parameter for this connection. TRM provides an lower bound on the time interval between forward Resource Management (RM) cells for an ABR source. Since the last forward RM cell was sent, if at least TRM time has elapsed since and at least two other cells have been sent, then the next cell to be transmitted would be a forward RM cell. This attribute is ignored under all conditions where the operational attribute abrConnectionType has the value erSwitch. The provisioned value of 781 is signalled as TRM = 0, in the ABR Additional Parameters Information Element. 1563 is signalled as TRM = 1. 3125 is signalled as TRM = 2. 6250 is signalled as TRM = 3. 12500 is signalled as TRM = 4 25000 is signalled as TRM = 5. 50000 is signalled as TRM = 6. 100000 is signalled as TRM = 7. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Cutoff Decrease Factor (CDF) parameter for this connection. When the value of this attribute is non-zero, CDF is computed as the inverse of the value. For example, if the value is 32, the value of CDF is 1/32. When the value of this attribute is 0, CDF is also zero. CDF controls the decrease in the Allowed Cell Rate (ACR) associated with the CRM parameter, the limit of the number of forward Resource Management (RM) cells which may be sent in the absence of received backward RM cells. When this limit is crossed, the ACR value would be decreased by the amount (CDF*ACR). The ACR is not allowed to fall below the Minimum Cell Rate (MCR), in which case the ACR is set to MCR. The value of CRM is indicated by the forwardRmCellLimit attribute. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Allowed Cell Rate Decrease Time Factor (ADTF) parameter for this connection. ADTF is the maximum time interval permitted between sending forward Resource Management (RM) cells before the Allowed Cell Rate (ACR) is decreased to initialCellRate. In other words, if the source does not transit a forward RM cell for the period specified by adtf, it reduces its ACR to the value of its initialCellRate. This attribute is ignored under all conditions where the operational attribute abrConnectionType indicates erSwitch or efciSwitch. VALUES ( 16777216 = sameAsCa )

This attribute specifies an upper bound on the delay after which the rate change induced by a backward Resource Management (RM) cell departing from this connection point (in the backward direction) is expected to be observed at this connection point (in the forward direction). This upper bound may be approximated as the sum of the round trip fixed and propagation delays and the maximum queuing delays between the ABR source and this interface. The value of this attribute is used in policing an ABR connection using the Dynamic General Cell Rate Algorithm (DGCRA). A larger value for this attribute implies a more lenient policer. When there is a reduction in the Allowed Cell Rate (ACR), the policer waits for a correspondingly longer period of time before it enforces at the new cell rate. The value of this attribute must not be less than the dgcraMinimumDelay attribute. VALUES ( 16777216 = sameAsCa )

This attribute specifies a lower bound on the delay after which the rate change induced by a backward Resource Management (RM) cell departing from this connection point (in the backward direction) is expected to be observed at this connection point (in the forward connection). This lower bound may be approximated as the sum of the round trip fixed and propagation delays between the ABR source and this interface. The value of this attribute is used in policing an ABR connection using the Dynamic General Cell Rate Algorithm (DGCRA). A smaller value for this attribute implies a more lenient policer. When there is a increase in the Allowed Cell Rate (ACR), the policer waits for a correspondingly shorter period of time before it enforces at the new cell rate. VALUES ( 16777216 = sameAsCa )

This attribute specifies the Allowed Cell Rate Decrease Time Factor (ADTF) of the far end ABR source. The value specified should be the same as the ADTF parameter at the far end of this ABR connection. The value of this attribute is used in policing an ABR connection using the Dynamic Generic Cell Rate Algorithm (DGCRA). A larger value for this attribute implies a more lenient policer. When the delay between two consecutive forward Resource Management (RM) cells received at this interface corresponds to a value greater than the value of this attribute, the policer begins to limit enforce the incoming traffic at the initial cell rate (ICR) of the far end, as specified by the farEndInitialCellRate attribute.

This attribute specifies the Initial Cell Rate (ICR) of the far end ABR source. The value specified should be the same as the ICR parameter at the far end of this ABR connection. The value of this attribute is used in policing an ABR connection using the Dynamic Generic Cell Rate Algorithm (DGCRA). A larger value for this attribute implies a more lenient policer. When the delay between two consecutive forward Resource Management (RM) cells received at this interface corresponds to a value greater than the farEndAcrDecreaseTimeFactor attribute, the policer begins to enforce the incoming traffic at the value of this attribute. If this attribute is specified less than the MCR of the connection, then the MCR is used as the feIcr. If this attribute is more than the PCR of the connection, then PCR is used as the feIcr.

This group contains traffic related provisionable attributes for the Vcc, Vpc, and Vpt components. Changing any of the attributes in this group causes a service interruption on the Vcc, Vpc, or Vpt component.

An entry in the mscAtmIfVccVcdTmProvTable.

This attribute specifies the type of traffic management which is applied to the transmit direction of this connection as defined in the ATM Forum. The txTrafficDescType determines the number and meaning of the parameters in the txTrafficDescParm attribute. This attribute can have a value of 9 if and only if the atmServiceCategory is availableBitRate. Enumeration: 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the forward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies an override to the default transmit queue limit for this connection. An value other than sameAsCa may be specified only for ATM IP and 1pOC48SmSrAtm cards. This attribute is not applicable for basic Vpts. A value of sameAsCa means to use the default common or per-VC transmit queue limit as defined by the CA service category for this connection. A value from 5 to 63,488 indicates that a specific transmit queue limit is requested which differs from the default which is defined under the CA component for this service category. A specific value is ignored for connections where common queuing is specified for the service category. For the 1pOC48SmSrAtm card, this attribute is used to set the per VC utilization limit. The actual transmit queue limit for a connection is visible in the Vcc Tm, Vpc Tm or Vpt txQueueThresholds attribute. VALUES ( 0 = sameAsCa )

This attribute specifies the holding priority of this connection. In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This value provisioned in the Vcd or Vpd may be overridden by certain applications, for example Vcc Test, which run over this connection. The default holding priority for a provisioned connection is higher then default holding priorities for dynamic (SVC) connections. This attribute is not applicable for Vpt Vccs. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the type of traffic management which is applied to the receive direction of this connection as defined in the ATM Forum. The rxTrafficDescType determines the number and meaning of the parameters in the rxTrafficDescParm attribute. When this attribute is set to sameAsTx, the rxTrafficDescType as well as the rxTrafficDescParm are taken from the txTrafficDescType and txTrafficDescParm values. Enumeration: 'sameAsTx': 15, 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the backward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. The sameAsFwd selection sets the backward quality of service to be the same as the forward quality of service. Enumeration: 'sameAsFwd': 15, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute specifies the ATM service category for both directions of the connection. The value derivedFromBBC may only be used if the SrcPvc component is provisioned under this Vcc. Otherwise a specific ATM service category must be specified. If this attribute is set to derivedFromBBC, the Broadband Bearer Capability (BBC) and bestEffort attributes are used to determine the atmServiceCategory of this connection. If this attribute is set to other than derivedFromBBC, the value of this attribute is used to override the provisioned BBC Information Element parameters. In those cases, the BBC attributes are not used. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to be of significantly reduced value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The availableBitRate service is an ATM layer service category for which the limiting ATM layer transfer characteristics provided by the network may change subsequent to connection establishment. ABR service has a flow control mechanism which supports several types of feedback to control the source rate in response to changing ATM layer transfer characteristics. ABR service is not intended to support real-time applications. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'derivedFromBBC': 15, 'constantBitRate': 1, 'unspecifiedBitRate': 0, 'availableBitRate': 4, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. This attribute is ignored if the atmServiceCategory is availableBitRate. Traffic shaping is not available on the 1pOC12SmLrAtm card, therefore this attribute is ignored. When sameAsCa is selected, traffic shaping for the connection is based on the trafficShaping attribute of the connection's service category component under the CA. If the service category has trafficShaping set to enabled or inverseUpc, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc Tm, Vpc Tm, or Vpt Tm components. When disabled is selected, traffic shaping for this connection is disabled regardless of the provisioning of the connection's service category component. Enumeration: 'disabled': 1, 'sameAsCa': 2.

This attribute only applies when this connection is unshaped. This attribute specifies the transmit queueing method for this connection if it is unshaped. The two possible methods are per-VC queuing and common queuing. On ATM IP FPs, this attribute must be set to sameAsCa. This attribute is ignored in the following situations: - if the connection has trafficShaping enabled or inverseUpc, or - if the atmServiceCategory is availableBitRate, or - if the atmServiceCategory is constantBitRate and this is a CQC- based ATM FP. - for basic Vpts and standard Vpt Vccs When this attribute is set to sameAsCa, the transmit queueing method for the connection is based on the unshapedTransmitQueueing attribute of the connection's service category component under the CA. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. Enumeration: 'sameAsCa': 3, 'common': 1.

This attribute specifies an override for the weight of this unshaped connection. This attribute is ignored for shaped connections, for ABR connections, for connections on a CQC-based ATM FP and basic Vpts. When the value is set to sameAsCa, the weight is determined by the fairnessWeight attribute under the CA service category component for all but standard Vpt Vccs. For standard Vpt Vccs, the weight is determined by the Vcc's service category, when the value is set to sameAsCa. When this attribute is set to a value from 1 to 4095, that value is used for the fairness weight of this connection relative to other connections. For all but standard Vpt Vccs, fairness weight determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections in the same service category. For standard Vpt Vccs, fairness weight determines the proportion of transmit cell opportunities which are allocated to this connection, compared to other connections associated with the Vpt. When the value is set to upToQueueLimit, the fairness weight is limited only by the txQueueLimit. VALUES ( 0 = upToQueueLimit 65535 = sameAsCa )

This attribute specifies whether force tagging is enforced for this connection for cells in the transmit direction. On CQC-based ATM cards and for Vpts, this attribute is not applicable and is ignored. When the value is set to sameAsCa, the force tagging functionality is determined by the forceTagging attribute under the CA service category component. When the value is set to enabled, force tagging is enabled for cells in the transmit direction on this connection. When this option is selected, the CLP bit is set to 1 for all cells in the transmit direction. Cells which are tagged are counted in the txCellClp attribute. When the value is set to disabled, force tagging is disabled for cells in the transmit direction on this connection. When this option is selected, the CLP bit is unchanged for cells in the transmit direction. Enumeration: 'disabled': 1, 'sameAsCa': 2, 'enabled': 0.

This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsCa is selected, UPC for the connection is based on the usageParameterControl attribute of the service category component under the AtmIf CA. If the service category has UPC enforced or monitored, then UPC is set to that value for the connection. When disabled is selected, UPC for this connection is disabled regardless of the provisioning of the service category. When enforced is selected, UPC for this connection is enforced regardless of the provisioning of the service category. Note that setting UPC to enforced or monitored may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc, Vpc, and Vpt components. Enumeration: 'disabled': 1, 'enforced': 0, 'monitored': 4, 'sameAsCa': 2.

This attribute specifies the bearer capability. This attribute is only used for SPVC and SPVP connections. It is one of the Broadband Bearer Capability (BBC) attributes. The purpose of the BBC information element is to indicate a requested broadband connection-oriented bearer service to be provided by the network. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Class a service is a connection-oriented, constant bit rate ATM transport service. Class a service has end to end timing requirements and may require stringent cell loss, cell delay and cell delay variation performance.When a is set, the user is requesting more than an ATM only service. The network may look at the AAL to provide interworking based upon its contents. Class c service is a connection-oriented, variable bit rate ATM transport service. Class c service has no end-to-end timing requirements. When c is set, the user is requesting more than an ATM only service. The network interworking function may look at the AAL and provide service based on it. Class x service is a connection-oriented ATM transport service where the AAL, trafficType (vbr or cbr) and timing requirements are user defined (that is, transparent to the network).When x is set the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. Class vp service is used to specify a transparent VP service. When the value of this attribute is vp, the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. This service differs from class x service in that with the class vp service both the VCI field (except or VCI values 0, 3, 4, and 6 through 15) and Payload Type field are transported transparently by the network. This attribute value is only applicable to SPVP connections. Enumeration: 'a': 1, 'x': 16, 'c': 3, 'vp': 24, 'derivedFromServiceCategory': 31.

This attribute specifies the transfer capability for this connection. Uni 3.0/3.1 traffic type and end-to-end timing parameters are mapped into this parameter as follows: 0: NoIndication, NoIndication 1: NoIndication, yes 2: NoIndication, no 5: CBR, yes 8: VBR, NoIndication 9: VBR, yes 10: VBR, no notApplicable specifies that the user does not want to specify the transfer capability. The CBR traffic type refers to traffic offered on services such as a constant bit rate video service or a circuit emulation. The VBR traffic type refers to traffic offered on services such as packetized audio and video, or data. The value no indication for traffic type is used if the user has not set the traffic type; similarly for end-to-end timing. The value yes for end-to-end timing indicates that end-to-end timing is required. The value no for end-to-end timing indicates that end-to-end timing is not required. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'n10': 10, 'notApplicable': 30, 'derivedFromServiceCategory': 31, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n5': 5.

This attribute specifies the value for the clipping susceptibility parameter in the BBC Information Element. This attribute is only used for SPVC connections. It is one of the Broadband Bearer Capability attributes. Clipping is an impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through. Enumeration: 'yes': 1, 'no': 0.

This attribute specifies the value of the best effort parameter in the ATM Traffic Descriptor Information Element. This attribute is only used for Soft PVC connections. It is one of the Broadband Bearer Capability attributes. The value indicated implies that the quality of service for this connection is not guaranteed. The value notIndicated implies that the quality of service for this connection is guaranteed. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'notIndicated': 1, 'derivedFromServiceCategory': 15, 'indicated': 0.

This attribute specifies whether packet-wise discard functions are to be enabled or disabled in the transmit data direction for this connection. Packet-wise discard functions should only be requested if this connection is transferring AAL5 frame traffic. This attribute is not applicable for Vpts. Packet-wise functions increase the 'goodput' of the link. The transmit packet-wise functions are Early Packet Discard (EPD) and Partial Packet Discard (PPD). EPD allows the connection to discard an entire frame once the transmit queue has reached the EPD threshold. EPD increases the 'goodput' of a link, since discarding an entire frame means that some queue capacity is guarded for some other frame which is already partially transmitted. All cells of the frame are discarded from the Beginning of Message (BOM) cell up to and including the End of Message (EOM) cell. PPD allows the connection to discard the remainder of a cell- forwarded AAL5 frame if one cell of this frame has been discarded. All cells are discarded up to but not including the EOM cell. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded at the AAL5 reassembly point are not transmitted. On CQC-based ATM cards, the packet-wise discard functions are PPD and EPD. PPD is available at VCC cell-transfer points. PPD is not applicable at frame-cell conversion points, and is not applicable for Vpcs. PPD is configured by this attribute. Packet-wise discard should only be enabled for connections carrying AAL5 segmentation traffic. Setting the value to enabled for any other traffic type may result in all traffic being discarded. On CQC-based ATM FPs, EPD is automatically enabled at frame-to-cell conversion points, independent of the setting of this attribute. On CQC-based ATM cards, at a permanent VCC connection endpoint, this attribute is not applicable and is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. On ATM IP cards, packet-wise discard functions include EPD and PPD. PPD and EPD apply to individual VCCs and VCCs within VPCs at all connection points, including tandem VPC connections. Both PPD and EPD are controlled by this attribute. This attribute may safely be set to enabled for any connection (Vcc or Vpc) on ATM IP FPs since they have the ability to automatically detect AAL5-segmented traffic on a connection, and only enable packet- wise discards if AAL5-segmented traffic is detected. When this attribute is set to enabled, packet-wise discard functions are applied to transmit traffic at this connection point. When this attribute is set to disabled, packet-wise discard functions are not applied to transmit traffic at this connection point. At a SPVC origin on a PNNI interface, a value of enabled specifies that frame discard is requested in the backward direction. When this attribute is set to disabled, backward frame discard is not requested in the SPVC call setup. The transmit packet-wise discard functions that are active are visible in the Vcc/Vpc Tm txPacketWiseDiscard operational attribute. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute specifies whether packet-wise discard functions are to be enabled or disabled in the receive data direction for this connection. Packet-wise discard functions should only be requested if this connection is transferring AAL5 frame traffic. This attribute is not applicable for Vpts. Packet-wise functions increase the 'goodput' of the link. The receive packet-wise function is Partial Packet Discard (PPD). PPD allows the connection to discard the remainder of a cell- forwarded AAL5 frame if one cell of this frame has been discarded, for example due to UPC. All cells are discarded up to but not including the EOM cell. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded at the AAL5 reassembly point are not transmitted. PPD is available at all VCC connection points where UPC may be activated. PPD is not applicable for Vpcs. On CQC-based ATM FPs, packet-wise discards should only be enabled for connections carrying AAL5 segmentation traffic. Setting the value to enabled for any other traffic type may result in traffic being discarded. On CQC-based ATM cards, at a permanent VCC connection endpoint, this attribute is not applicable and is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. On ATM IP cards, this attribute may safely be set to enabled for any connection (Vcc or Vpc) since they have the ability to automatically detect AAL5-segmented traffic on a connection, and only enables packet-wise discards if AAL5-segmented traffic is detected. When this attribute is set to enabled, packet-wise discard functions are applied to receive traffic at this connection point. When this attribute is set to disabled, packet-wise discard functions are not applied to receive traffic at this connection point. At a SPVC origin on a PNNI interface, a value of enabled specifies that frame discard is requested in the forward direction. When this attribute is set to disabled, forward frame discard is not requested in the SPVC call setup. The receive packet-wise discard functions that are active are visible in the Vcc/Vpc Tm rxPacketWiseDiscard operational attribute. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute specifies the type of ABR behavior which is to be enforced at this connection. This attribute is only applicable if the atmServiceCategory attribute is availableBitRate. If the atmServicecategory attribute is not availableBitRate, this attribute value is ignored. The actual ABR functionality which is in effect is visible in the Vcc/Vpc/Vpt Tm abrConnectionType operational attribute. For CQC-based ATM cards, the only allowable values are sameAsCa, nonAbrInterworking or abrSwitch. If abrSwitch is selected, the CQC implements EFCI marking behavior. For the 1pOC12SmLrAtm card, the only allowable values are sameAsCa or abrSwitch. If abrSwitch is selected, EFCI marking behavior is implemented. sameAsCa is used to request the default behavior as specified in the CA Abr component for this Vcc. Otherwise, this attribute overrides the default behavior. virtualSourceDest is used to request that this connection point function as a virtual source/virtual destination. VS/VD functionality is only supported on ATM IP FPs. sourceDest requires that this connection point function as a S/D for RM cells. S/D mode is automatically invoked at this connection point either if this is a connection end point, or if the next hop connection point is configured as nonAbrInterworking. nonAbrInterworking is used to request that this connection point function as an interworking between ABR and non-ABR service categories. This means that there are no RM cells on the link side of this connection, and that the next hop connection point is performing as an ABR sourceDest. abrSwitch is used to request ABR switch behavior for this connection point. The ABR switch behavior is first, to confirm to virtualSourceDest or nonAbrInterworking setting on the next hop, and otherwise to implement ABR ER switch behavior. For CQC- based FPs, ABR switch behavior is implemented as EFCI marking. Enumeration: 'abrSwitch': 0, 'nonAbrInterworking': 5, 'sameAsCa': 14, 'virtualSourceDest': 3, 'sourceDest': 4.

This attribute is a vector of five traffic parameters whose meanings are defined by the txTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR), Minimum Cell Rate (MCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR, MCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When txTrafficDescType is 1 or 2, all of the parameters must be set to zero. When txTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When txTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell discard; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell tagging; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 9, parameter 1 represents the PCR; parameter 2 represents the CDVT; parameter 3 represents the MCR; parameter 4 and parameter 5 represent are not used and must be zero. Parameter 1 must be non-zero and must be greater than or equal to parameter 3. Parameter 3 may be optionally zero. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. When the atmServiceCategory is availableBitRate (ABR), the shaping rate is dynamically chosen, based on the ABR flow control mechanism, as a value between the MCR and the PCR or the requested shaping rate if applicable. For txTrafficDescType 3, 4 and 5, the transmit traffic is shaped at the next available shaping rate less than the PCR. For txTrafficDescType 6, 7 and 8 if linear traffic shaping is selected, the transmit traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR. For txTrafficDescType 6, 7 and 8 if inverse-UPC traffic shaping is selected, the transmit traffic is shaped at a variable rate which conforms to the PCR, SCR and MBS of the connection traffic descriptor. Inverse-UPC traffic shaping is available only on ATM IP cards.

An entry in the mscAtmIfVccVcdTmTxTdpTable.

This variable represents the mscAtmIfVccVcdTmTxTdpTable specific index for the mscAtmIfVccVcdTmTxTdpTable.

This variable represents an individual value for the mscAtmIfVccVcdTmTxTdpTable.

This attribute is a vector of four traffic parameters whose meanings are defined by the rxTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and Minimum Cell Rate (MCR) are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. The value of CDVT is expressed in microseconds. The values of PCR, SCR, MCR, MBS and CDVT are used for usage parameter control (UPC). When rxTrafficDescType is 1 or 2, all of the parameters must be set to zero (unused). When rxTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic. Parameter 1 must be non-zero. Parameters 2 and 3 must be set to zero (unused). When rxTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is a 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to Parameter 2. When rxTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameter 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 9, parameter 1 represents the PCR; parameter 2 represents the CDVT; parameter 3 represents the MCR. Parameter 4 is not used and must be zero. Parameter 1,must be non- zero and must be greater than or equal to parameter 3. Parameter 3 may optionally be zero. When rxTrafficDescType is any value from 3 through 8, parameter 4 represents the CDVT. If the value of CDVT either in parameter 2 or in parameter 4 is zero, the CDVT is taken from the CA defaults for the particular atmServiceCategory of this connection. On a CQC-based ATM card, when rxTrafficDescriptorType is 3 through 8, there are certain extreme combinations of rxTrafficDescParm which are outside the capabilities of the UPC hardware. The check prov command detects such cases and generates an error message. If this happens, adjust the parameters until they fall within the supported limits. To calculate the limits, use the following formulae: I1 = 1 000 000 000 / PCR L1 = CDVT * 1000 I2 = 1,000,000,000 / SCR L2 = CDVT + (MBS - 1) * (I2 - I1) I1 and I2 must be less than or equal to 335,523,840. I1 + L1 must be less than or equal to 1,342,156,800. I2 + L2 must be less than or equal to 1,342,156,800. Note that I2 and L2 only apply when the rxTrafficDescriptorType is 6 through 8. If the values of I1, L1, I2 or L2 are closer to the limits described above, a further restriction applies. Specifically, if either: I1 > 41,940,480 or I2 > 41,940,480 or I1 + L1 > 167,769,600 or I2 + L2 > 167,769,600 then both I1 and I2 must be greater than 20,480. Parameter 5 of the rxTrafficDescParm is always unused. If the rxTrafficDescType is sameAsTx, the values provisioned in this attribute are ignored. The traffic parameters for the receive direction are taken from the txTrafficDescParm.

An entry in the mscAtmIfVccVcdTmRxTdpTable.

This variable represents the mscAtmIfVccVcdTmRxTdpTable specific index for the mscAtmIfVccVcdTmRxTdpTable.

This variable represents an individual value for the mscAtmIfVccVcdTmRxTdpTable.

This attribute is a vector of three elements that specify the quality of service parameters for the forward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVccVcdTmFqpTable.

This variable represents the mscAtmIfVccVcdTmFqpTable specific index for the mscAtmIfVccVcdTmFqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVccVcdTmFqpTable.

This attribute is a vector of three elements that specify the quality of service parameters for the backward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVccVcdTmBqpTable.

This variable represents the mscAtmIfVccVcdTmBqpTable specific index for the mscAtmIfVccVcdTmBqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVccVcdTmBqpTable.

This entry controls the addition and deletion of mscAtmIfVccVcdPm components.

A single entry in the table represents a single mscAtmIfVccVcdPm component.

This variable is used as the basis for SNMP naming of mscAtmIfVccVcdPm components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscAtmIfVccVcdPm tables.

This variable represents the index for the mscAtmIfVccVcdPm tables.

This group contains provisioned attributes which specify Performance Monitoring (PM) measurements, namely, Availability Ratio (AR) and Cell Loss Ratio (CLR), and control modes for the connection. The values specified in this group override those specified by AtmIf Pm settings.

An entry in the mscAtmIfVccVcdPmProvTable.

This attribute specifies the set of Performance Monitoring (PM) measurements on the switch side configuration for the connection. sameAsInterface means that the measurements specified by the segSwitchSideMeasurement attribute of the AtmIf Pm component will be performed. No other values may be specified if sameAsInterface is selected. If the value is empty, no switch side PM measurements are done. Description of bits: availabilityRatio(0) cellLossRatio(1) sameAsInterface(2)

This attribute specifies the set of Performance Monitoring (PM) measurements on the link side configuration for the connection. sameAsInterface means that the measurements specified by the segLinkSideMeasurement attribute of the AtmIf Pm component will be performed. No other values may be specified if sameAsInterface is selected. If the value is empty, no link side PM measurements are done. The following are valid sets: (~sameAsInterface ~availabilityRatio ~cellLossRatio) (~sameAsInterface ~availabilityRatio cellLossRatio) (~sameAsInterface availabilityRatio ~cellLossRatio) (~sameAsInterface availabilityRatio cellLossRatio) (sameAsInterface ~availabilityRatio ~cellLossRatio) Description of bits: availabilityRatio(0) cellLossRatio(1) sameAsInterface(2)

This attribute specifies the control mode of Performance Monitoring (PM) measurements for the connection. autoStart means that PM activation procedures will start when the provisioned data is activated. onDemand means that PM activation procedures will start when the operator issues the START command. The PM measurements in this mode will continue until the operator issues the STOP command. sameAsInterface means that the behavior will be as specified by the controlMode attribute of the AtmIf Pm component. Enumeration: 'sameAsInterface': 2, 'onDemand': 1, 'autoStart': 0.

This group contains the provisionable loopback attributes for a Vcc, Vpc, or Vpt component. Note that certain loopback requests may not be possible on a given connection. In such cases, the corresponding operational loopback attribute in the Status group of the Vcc, Vpc, or Vpt component is set to notApplicable and the requested loopback is not performed. If loopbacks are provisioned to be on, and for any reason the segment or end-to-end OAM loopback cells are not relayed, the connection component becomes troubled, and user cell traffic may be discarded. If loopbacks are provisioned to be on, all of the nodes in the segment, and external networks which are in the end-to-end connection must relay the OAM loopback cells.

An entry in the mscAtmIfVccVcdLbkTable.

This attribute specifies whether link-side segment loopback insertion should be performed on this connection. When sameAsInterface is selected, the link-side segment loopback insertion for the connection is based on the segLinkSideLoopback attribute of the connection's parent AtmIf componentif the ATM interface has link-side segment loopback insertion turned on, then link-side segment loopback insertion is also on for the connection. When on or off is selected, link-side segment loopback insertion is turned on or off respectively for the connection regardless of the provisioning of the parent AtmIf component. Note that link-side segment loopback insertion is not possible if the connectionPointType attribute of the Vcc or Vpc component is connectingPoint. Link-side segment loopback insertion is also not possible if the distributionType of the Vcc is pointToMultipoint. In such cases, the associated segLinkSideLoopbackState attribute indicates notApplicable and link-side segment loopback insertion is not performed. Link-side segment loopback insertion is always possible on a Vpt. Enumeration: 'on': 0, 'off': 1, 'sameAsInterface': 2.

This attribute specifies whether switch-side segment loopback insertion should be performed on this connection. When sameAsInterface is selected, the switch-side segment loopback for the connection is based on the segSwitchSideLoopback attribute of the connection's parent AtmIf componentif the ATM interface has switch-side segment loopback insertion turned on, then switch-side segment loopback insertion is also on for the connection. When on or off is selected, switch-side segment loopback insertion is turned on or off respectively for the connection regardless of the provisioning of the parent AtmIf component. Note that switch-side segment loopback insertion is not possible if the connectionPointType attribute of the Vcc or Vpc component is connectingPoint or connectionEndPoint. Switch-side segment loopback insertion is also not possible if the distributionType of the Vcc is pointToMultipoint In such cases, the associated segSwitchSideLoopbackState attribute indicates notApplicable and switch-side segment loopback insertion is not performed. Switch- side segment loopback is never possible on a Vpt. Enumeration: 'on': 0, 'off': 1, 'sameAsInterface': 2.

This attribute specifies whether end-to-end loopback insertion should be performed on this connection. When sameAsInterface is selected, the end-to-end loopback for the connection is based on the endToEndLoopback attribute of the connection's parent AtmIf componentif the ATM interface has end-to-end loopback insertion turned on, then end-to-end loopback insertion is also on for the connection. When on or off is selected, end-to-end loopback insertion is turned on or off respectively for the connection regardless of the provisioning of the parent AtmIf component. Note that end-to-end loopback insertion is not possible if the connectionPointType attribute of the Vcc or Vpc component is connectingPoint or segmentEndPoint. End-to-end loopback insertion is also not possible if the distributionType of the Vcc is pointToMultipoint. In such cases, the associated endToEndLoopbackState attribute indicates notApplicable and end- to-end loopback insertion is not performed. End-to-end loopback insertion is always possible on a Vpt. Enumeration: 'on': 0, 'off': 1, 'sameAsInterface': 2.

This attribute is introduced to exist temporarily to pass to AtmIf the connection type defined under Vcc or Vpc. This attribute will be obsoleted once a more elegant solution is available. Enumeration: 'pointToMultipointLeaf': 2, 'pointToPoint': 0, 'pointToMultipointRoot': 1.

This group contains traffic related provisionable attributes for the Vcc and Vpc components. The attributes' operational values are reflected in the Traffic group for these components. Changing any of the attributes in this group causes a service interruption on the Vcc or Vpc component.

An entry in the mscAtmIfVccVcdTrafficTable.

This attribute is migrated to the AtmTmProv group. This attribute specifies the type of traffic management which is applied to the transmit direction of this connection as defined in the ATM Forum. The txTrafficDescType determines the number and meaning of the parameters in the txTrafficDescParm attribute. Enumeration: 'n8': 8, 'n9': 9, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the transmit direction for this connection. The constantBitRate class refers to traffic offered on services such as a constant bit rate video service. This traffic is highest priority. The variableBitRate class refers to traffic offered on services such as packetized audio and video. The connectionOriented class refers to connection-oriented traffic such as Frame Relay or X.25 traffic. The connectionless traffic refers to traffic offered through connectionless trunks such as certain LAN protocols. The unspecified class supports a 'best effort' type of service, where there is a minimum guarantee of bandwidth. This traffic is lowest priority. This attribute is obsolete. The value is migrated into atmServiceCategory. The atmServiceCategory applies in both transmit and receive directions. unspecified maps to unspecifiedBitRate; constantBitRate maps to constantBitRate; variableBitRate maps to variableBitRateRt; connectionOriented maps to variableBitRateNrt connectionless maps to variableBitRateNrt Enumeration: 'constantBitRate': 1, 'connectionOriented': 3, 'variableBitRate': 2, 'connectionless': 4, 'unspecified': 0.

This attribute is migrated to the AtmTmProv group. This attribute specifies the quality of service for the forward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is migrated to the AtmTmProv group. This attribute specifies the holding priority of this connection. In a situation where the link bandwidth fluctuates, such as over an IMA link, holding priority is used to determine which connections are held and which are released. Holding priority 4 connections are the first to be released. Holding priority 0 connections are the last to be released. This value provisioned in the Vcd or Vpd may be overridden by certain applications, for example Vcc Test, which run over this connection. The default holding priority for a provisioned connection is higher then default holding priorities for dynamic (SVC) connections. Enumeration: 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is migrated to the AtmTmProv group. This attribute specifies the type of traffic management which is applied to the receive direction of this connection as defined in the ATM Forum. The rxTrafficDescType determines the number and meaning of the parameters in the rxTrafficDescParm attribute When sameAsTx is selected, the rxTrafficDescType as well as the rxTrafficDescParm are taken from the transmit values. Enumeration: 'sameAsTx': 15, 'n8': 8, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4, 'n5': 5, 'n6': 6, 'n7': 7.

This attribute specifies the quality of service for the receive direction for this connection. The constantBitRate class refers to traffic offered on services such as a constant bit rate video service. The variableBitRate class refers to traffic offered on services such as packetized audio and video. The connectionOriented class refers to connection-oriented traffic. The connectionless traffic refers to traffic offered through connectionless trunks. The unspecified class supports a 'best effort' type of service, where there is a minimum guarantee of bandwidth. The sameAsTx selection sets the receive quality of service to be the same as the transmit quality of service. This attribute is obsolete. The value of txQosClass is migrated into atmServiceCategory. The value of this attribute is ignored. AtmServiceCategory applies in both transmit and receive directions. Enumeration: 'variableBitRate': 2, 'connectionless': 4, 'constantBitRate': 1, 'sameAsTx': 15, 'unspecified': 0, 'connectionOriented': 3.

This attribute is migrated to the AtmTmProv group. This attribute specifies the quality of service for the backward direction for this connection. This attribute is only used for SPVC connections. Class 1 supports a QOS that meets Service Class A performance requirements (Circuit emulation, constant bit rate video). Class 2 supports a QOS that meets Service Class B performance requirements (Variable bit rate audio and video). Class 3 supports a QOS that meets Service Class C performance requirements (Connection-Oriented Data Transfer). Class 4 supports a QOS that meets Service Class D performance requirements (Connectionless Data Transfer). Class 0 is the unspecified bit rate QOS class; no objective is specified for the performance parameters. The sameAsFwd selection sets the backward quality of service to be the same as the forward quality of service. Enumeration: 'sameAsFwd': 15, 'n0': 0, 'n1': 1, 'n2': 2, 'n3': 3, 'n4': 4.

This attribute is migrated to the AtmTmProv group. This attribute specifies the ATM service category for both directions of the connection. The value derivedFromBBC may only be used if the SrcPvc component is provisioned under this Vcc.Otherwise a specific ATM service category must be specified. If this attribute is set to derivedFromBBC, the Broadband Bearer Capability (BBC) and bestEffort attributes are used to determine the atmServiceCategory of this connection. If this attribute is set to other than derivedFromBBC, the value of this attribute is used to override the provisioned BBC Information Element parameters. In those cases, the BBC attributes are not used. The constantBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. The consistent availability of a fixed quantity of bandwidth is considered appropriate for CBR service. Cells which are delayed beyond the value specified by Cell Transfer Delay are assumed to be of significantly reduce value to the application. The rtVariableBitRate service category is intended for real time applications, that is those requiring tightly constrained delay and delay variation, as would be appropriate for voice and video applications. Sources are expected to transmit at a rate which varies with time. Equivalently, the source can be described as 'bursty'. Cells which are delayed beyond the value specified by CTD are assumed to be of significantly reduced value to the application. Real time VBR service may support statistical multiplexing of real time sources. The nrtVariableBitRate service category is intended for non-real time applications which have bursty traffic characteristics and which can be characterized in terms of a PCR, SCR, and MBS. For those cells which are transferred within the traffic contract, the application expects a low cell loss ratio. For all connections, it expects a bound on the mean cell transfer delay. Non-real time VBR service may support statistical multiplexing of connections. The unspecifiedBitRate service is intended for non-real time applications; that is, those not requiring tightly constrained delay and delay variation. UBR sources are expected to be bursty. UBR service supports a high degree of statistical multiplexing among sources. UBR service does not specify traffic related service guarantees. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection. Enumeration: 'constantBitRate': 1, 'derivedFromBBC': 15, 'unspecifiedBitRate': 0, 'rtVariableBitRate': 2, 'nrtVariableBitRate': 3.

This attribute is migrated to the AtmTmProv group. This attribute specifies whether this connection uses traffic shaping when transmitting traffic to the ATM interface. When sameAsInterface is selected, traffic shaping for the connection is based on the trafficShaping attribute of the connection's parent AtmIf componentif the ATM interface has traffic shaping enabled, then traffic shaping is enabled for the connection. Note that enabling traffic shaping may have no effect under certain cases. These cases are listed in the description of the trafficShaping operational attribute, which is under the Vcc and Vpc components. When disabled is selected, traffic shaping for this connection is disabled regardless of the provisioning of the parent AtmIf component. Enumeration: 'disabled': 1, 'sameAsInterface': 2.

This attribute is migrated to the AtmTmProv group. This attribute only applies when this connection is unshaped. This attribute defines the transmit queueing method for this connection if it is unshaped. Refer to the unshapedTransmitQueueing attribute under the AtmIf for more details on the meaning of this attribute. When this attribute is set to sameAsInterface, the value from the AtmIf is used. When this attribute is set to common, transmit traffic on this unshaped connection is destined for the common queue. Enumeration: 'sameAsInterface': 3, 'common': 1.

This attribute is migrated to the AtmTmProv group. This attribute specifies whether this connection enforces usage parameter control when receiving traffic from the ATM interface. When sameAsInterface is selected, UPC for the connection is based on the usageParameterControl attribute of the connection's parent AtmIf componentif the ATM interface has UPC enabled, then UPC is enabled for the connection. Note that enabling UPC may have no effect under certain cases. These cases are listed in the description of the usageParameterControl operational attribute, which is under the Vcc and Vpc components. When disabled is selected, UPC for this connection is disabled regardless of the provisioning of the parent AtmIf component. Enumeration: 'disabled': 1, 'sameAsInterface': 2.

This attribute is migrated to the AtmTmProv group. This attribute specifies the bearer capability. This attribute is only used for SPVC and SPVP connections. It is one of the Broadband Bearer Capability (BBC) attributes. The purpose of the BBC information element is to indicate a requested broadband connection-oriented bearer service to be provided by the network. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Class a service is a connection-oriented, constant bit rate ATM transport service. Class a service has end to end timing requirements and may require stringent cell loss, cell delay and cell delay variation performance.When a is set, the user is requesting more than an ATM only service. The network may look at the AAL to provide interworking based upon its contents. Class c service is a connection-oriented, variable bit rate ATM transport service. Class c service has no end-to-end timing requirements. When c is set, the user is requesting more than an ATM only service. The network interworking function may look at the AAL and provide service based on it. Class x service is a connection-oriented ATM transport service where the AAL, trafficType (vbr or cbr) and timing requirements are user defined (that is, transparent to the network).When x is set the user is requesting an ATM only service from the network. Class vp service is used to specify a transparent VP service. When the value of this attribute is vp, the user is requesting an ATM only service from the network. In this case, the network shall not process any higher layer protocol. This service differs from class x service in that with the class vp service both the VCI field (except or VCI values 0, 3, 4, and 6 through 15) and Payload Type field are transported transparently by the network. This attribute value is only applicable to SPVP connections. Enumeration: 'a': 1, 'x': 16, 'c': 3, 'vp': 24, 'derivedFromServiceCategory': 31.

This attribute is migrated to the AtmTmProv group. This attribute specifies the transfer capability for this connection. Uni 3.0/3.1 traffic type and end-to-end timing parameters are mapped into this parameter as follows: 0: NoIndication, NoIndication 1: NoIndication, yes 2: NoIndication, no 5: CBR, yes 8: VBR, NoIndication 9: VBR, yes 10: VBR, no NotApplicable specifies that the user does not want to specify the transfer capability. The CBR traffic type refers to traffic offered on services such as a constant bit rate video service or a circuit emulation. The VBR traffic type refers to traffic offered on services such as packetized audio and video, or data. The value no indication for traffic type is used if the user has not set the traffic type; similarly for end-to-end timing. The value yes for end-to-end timing indicates that end-to-end timing is required. The value no for end-to-end timing indicates that end-to-end timing is not required. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'n10': 10, 'notApplicable': 30, 'derivedFromServiceCategory': 31, 'n8': 8, 'n9': 9, 'n0': 0, 'n1': 1, 'n2': 2, 'n5': 5.

This attribute is migrated to the AtmTmProv group. This attribute specifies the value for the clipping susceptibility parameter in the BBC Information Element. This attribute is only used for SPVC connections. It is one of the Broadband Bearer Capability attributes. Clipping is an impairment in which the first fraction of a second of information to be transferred is lost. It occurs after a call is answered and before an associated connection is switched through. Enumeration: 'yes': 1, 'no': 0.

This attribute is migrated to the AtmTmProv group. This attribute specifies the value of the best effort parameter in the ATM Traffic Descriptor Information Element. This attribute is only used for Soft PVC connections. It is one of the Broadband Bearer Capability attributes. The value indicated implies that the quality of service for this connection is not guaranteed. The value notIndicated implies that the quality of service for this connection is guaranteed. The value derivedFromServiceCategory specifies that the actual value which is used for this connection is derived from the value of the atmServiceCategory. Either, this attribute must be set to derivedFromServiceCategory, or the atmServiceCategory attribute must be set to derivedFromBBC, but not both. Enumeration: 'notIndicated': 1, 'derivedFromServiceCategory': 15, 'indicated': 0.

This attribute specifies the activation of frame discard functionality in the forward data direction, at relay points, for this connection. It applies to each hop of the connection. Frame discard functions should not be requested if this connection is not transferring frame (AAL5) traffic. Setting the value to indicated for any other traffic type results in all traffic being discarded. If this connection point is a permanent (provisioned) VCC mid- point, this attribute specifies whether the Partial Packet Discard (PPD) function is to be enabled or disabled in the transmit direction at this connecting point. The PPD function allows the connecting point to discard the remainder of a cell-forwarded AAL5 frame if one cell of this frame has been discarded. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded by the AAL5 reassembly are not transmitted. At a permanent VCC connecting point which is not a connection endpoint, when this attribute is set to indicated, the PPD function is applied to transmit traffic at this connecting point. It should not be indicated for connections whose end points are not performing AAL5 segmentation and reassembly. When this attribute is set to notIndicated, the PPD feature is not applied to transmit traffic at this connecting point. At a SPVC origin on a PNNI interface, a value of indicated specifies that frame discard is requested in the forward direction. The frame discard function for SPVCs consists of PPD at the SPVC origin and at all intermediate connecting points. When this attribute is set to notIndicated, forward frame discard is not requested in the SPVC call setup. Thus PPD is not enabled at the SPVC origin nor at any intermediate connecting point. At all points along a VPC, this setting is ignored. At a permanent VCC connection endpoint, this value is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. This attribute has been migrated to txFrameDiscard. Enumeration: 'notIndicated': 0, 'indicated': 1.

This attribute specifies the activation of frame discard functionality in the backward data direction, at relay points, for this connection. It applies to each hop of the connection. Frame discard functions should not be requested if this connection is not transferring frame (AAL5) traffic. Setting the value to indicated for any other traffic type results in all traffic being discarded. If this connection point is a permanent (provisioned) VCC mid- point, this attribute specifies whether the Partial Packet Discard (PPD) function is to be enabled or disabled in the receive direction at this connecting point. The PPD function allows the connecting point to discard the remainder of a cell-forwarded AAL5 frame if one cell of this frame has been discarded. The PPD function increases the 'goodput' of the link, since cells which are only going to be discarded by the AAL5 reassembly are not received. At a permanent VCC connecting point which is not a connection endpoint, when this attribute is set to indicated, the PPD function is applied to receive traffic at this connecting point. It should not be indicated for connections whose end points are not performing AAL5 segmentation and reassembly. When this attribute is set to notIndicated, the PPD feature is not applied to receive traffic at this connecting point. At a SPVC origin on a PNNI interface, a value of indicated specifies that frame discard is requested in the backward direction. The frame discard function for SPVCs consists of PPD at the SPVC origin and at all intermediate connecting points. When this attribute is set to notIndicated, backwards frame discard is not requested in the SPVC call setup. Thus PPD is not enabled at the SPVC origin nor at any intermediate connecting point. At all points along a VPC, this setting is ignored. At a permanent VCC connection endpoint, this value is ignored. If AAL5 segmentation and reassembly has been requested, PPD and Early Packet Discard (EPD) are automatically enabled. This attribute has been migrated to rxFrameDiscard. Enumeration: 'notIndicated': 0, 'indicated': 1.

This group contains the provisionable ATM accounting attributes for a Vcc, Vpc, or Vpt component.

An entry in the mscAtmIfVccVcdAcctTable.

This attribute specifies a unique indentifier for each end of a PVC. It that may be used by downstream processing systems to correlate accounting records issued at different nodes in the network. The attribute can be up to 32 bytes long. If it is less than 32 bytes, it is zero filled on the right to create a 32 byte value. The resulting value is recorded in the attribute callConnId for this PVC's ATM accounting records. If the attribute is a null string then this PVC does not have any accounting records generated for it.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of five traffic parameters whose meanings are defined by the txTrafficDescType attribute. The values of peak cell rate (PCR), sustained cell rate (SCR) and requested shaping rate are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for connection admission control (CAC). The value of CDVT is only used for connections where the atmServiceCategory is constantBitRate. For all other values of atmServiceCategory, CDVT is ignored. The values of PCR, SCR and requested shaping rate are used to determine the actual shaping rate where traffic shaping is enabled. When txTrafficDescType is 1 or 2, all of the parameters must be set to zero. When txTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be non-zero. Parameters 2 and 3 must be zero. When txTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell discard; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic with cell tagging; parameter 2 represents the PCR for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameter 1 must be greater than or equal to parameter 2. Parameters 1 and 2 must be non-zero. Parameter 3 must be zero. When txTrafficDescType is 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. When txTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic; parameter 4 represents the CDVT; and parameter 5 represents the requested shaping rate. A non-zero value in parameter 5 overrides any value in parameter 1. This result is used as the PCR. Parameters 1, 2 and 3 must be non-zero. Parameter 1 must be greater than or equal to parameter 2. Parameter 5, must either be zero (unused) or greater than or equal to parameter 2. Whenever it is valid for PCR to be specified, parameter 5 may also be used to specify a requested shaping rate. A non-zero value in parameter 5 overrides the value in parameter 1 and is used as the peak cell rate in calculations of CAC and shaping rate. For txTrafficDescType 3, 4 and 5, the transmit traffic is shaped at the next rate less than the PCR. For txTrafficDescType 6, 7 and 8, the transmit traffic is shaped at the highest available rate which is between PCR and SCR. However, if there is no available shaping rate between PCR and SCR, traffic is shaped at the next rate above the PCR.

An entry in the mscAtmIfVccVcdTxTdpTable.

This variable represents the mscAtmIfVccVcdTxTdpTable specific index for the mscAtmIfVccVcdTxTdpTable.

This variable represents an individual value for the mscAtmIfVccVcdTxTdpTable.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of four traffic parameters whose meanings are defined by the rxTrafficDescType attribute. The values of peak cell rate (PCR) and sustained cell rate (SCR) are expressed in cell/s. Maximum burst size (MBS) is expressed in cells. The value of CDVT is expressed in microseconds. The values of PCR, SCR, MBS and CDVT are used for usage parameter control (UPC). When rxTrafficDescType is 1 or 2, all of the parameters must be set to zero (unused). When rxTrafficDescType is 3, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic. Parameter 1 must be non-zero. Parameters 2 and 3 must be set to zero (unused). When rxTrafficDescType is 4, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell discard. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 5, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the PCR for CLP equal to 0 traffic with cell tagging. Parameters 1 and 2 must be non-zero. Parameter 3 must be set to zero (unused). Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is a 6, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 and 1 traffic; parameter 3 represents the MBS for CLP equal to 0 and 1 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to Parameter 2. When rxTrafficDescType is 7, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell discard; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameters 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is 8, parameter 1 represents the PCR for CLP equal to 0 and 1 traffic; parameter 2 represents the SCR for CLP equal to 0 traffic with cell tagging; parameter 3 represents the MBS for CLP equal to 0 traffic. Parameter 1, 2 and 3 must be non- zero. Parameter 1 must be greater than or equal to parameter 2. When rxTrafficDescType is any value from 3 through 8, parameter 4 represents the CDVT. If this value is zero, the CDVT is taken from the ConnectionAdministrator defaults for the particular atmServiceCategory of this connection. When rxTrafficDescriptorType is 3 through 8, there are certain extreme combinations of rxTrafficDescParm which are outside the capabilities of the UPC hardware. The check prov command detects such cases and generates an error message. If this happens, adjust the parameters until they fall within the supported limits. To calculate the limits, use the following formulae: I1 = 1 000 000 000 / PCR L1 = CDVT * 1000 I2 = 1 000 000 000 / SCR L2 = CDVT + (MBS - 1) * (I2 - I1) I1 and I2 must be less than or equal to 335 523 840. I1 + L1 must be less than or equal to 1 342 156 800. I2 + L2 must be less than or equal to 1 342 156 800. Note that I2 and L2 only apply when the rxTrafficDescriptorType is 6 through 8. If the values of I1, L1, I2 or L2 are closer to the limits described above, a further restriction applies. Specifically, if either: I1 > 41 940 480 or I2 > 41 940 480 or I1 + L1 > 167 769 600 or I2 + L2 > 167 769 600 then both I1 and I2 must be greater than 20 480. Parameter 5 of the rxTrafficDescParm is always unused. If the rxTrafficDescType is sameAsTx, the values in this attribute are taken from the txTrafficDescParm.

An entry in the mscAtmIfVccVcdRxTdpTable.

This variable represents the mscAtmIfVccVcdRxTdpTable specific index for the mscAtmIfVccVcdRxTdpTable.

This variable represents an individual value for the mscAtmIfVccVcdRxTdpTable.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of three elements that specify the quality of service parameters for the forward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR, and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR, and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVccVcdFqpTable.

This variable represents the mscAtmIfVccVcdFqpTable specific index for the mscAtmIfVccVcdFqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVccVcdFqpTable.

This attribute is migrated to the AtmTmProv group. This attribute is a vector of three elements that specify the quality of service parameters for the backward direction for this connection. This attribute is used for SPVC connections. The cdv element specifies the acceptable peak-to-peak Cell Delay Variation (CDV) of real-time connections (CBR, and rt-VBR). It is signalled through the extended QoS information element. The ctd specifies the acceptable maximum Cell Transfer Delay (maxCtd) of real-time connections (CBR, and rt-VBR). It is signalled through the end to end transit delay information element. The clr specifies the acceptable Cell Loss Ratio (CLR) of CBR, rt- VBR, and nrt-VBR connections. It is signalled through the extended QoS information element.

An entry in the mscAtmIfVccVcdBqpTable.

This variable represents the mscAtmIfVccVcdBqpTable specific index for the mscAtmIfVccVcdBqpTable. Enumeration: 'ctd': 1, 'cdv': 0, 'clr': 2.

This variable represents an individual value for the mscAtmIfVccVcdBqpTable.

This entry controls the addition and deletion of mscAtmIfVccLoop components.

A single entry in the table represents a single mscAtmIfVccLoop component.

This variable is used as the basis for SNMP naming of mscAtmIfVccLoop components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface