It is migrated in P6.0 to the attributes of the same name under each
ATM service category component of the AtmIf CA.
This attribute applies only for unshaped VCC and VPC
connections. This attribute defines the transmit queueing method for
all unshaped connections under this AtmIf. Per-VC queueing means
that unshaped connections are treated with the same fairness as
shaped queues in the transmit round-robin scheduling. The
alternative to per-VC queueing is to use the common queue for a
particular service category (medium or low priority). The common
queue is only counted as one queue in the transmit round-robin
scheduling. Thus, if there are multiple connections which are
destined for the common queue, they are not fairly allocated a
portion of the transmit bandwidth compared to shaped connections.
When this attribute is set to perVc, any unshaped connection is
allocated its own per-VC queue, and is treated with the same
fairness as any shaped connections. Per-VC queues have a
maximum rate of 58,962 cell/s (25 Mbit/s) in a multi-port shaping
configuration. Per-VC queues also have their own congestion
control level. This means that total number of cell/frame blocks
allocated for several per-VC queues are higher than would be
allowed on the common queue. This can be an advantage in
reducing cell loss due to queue congestion. This attribute may only
be set to perVc if the interface supports per-VC queueing, (specified
by the perVcQueueInterfaces attribute in the AtmResourceControl
component).
When this attribute is set to common, any unshaped connection is
destined for the common queue. The common queue has one set of
congestion control levels for all cells enqueued on it. The common
queue is only allocated one queue position when scheduling which
queue to transmit from. Due to the possibility of unfairness, this
value is only recommended in cases where the configuration cannot
otherwise achieve full link utilization.
When this attribute is set to autoConfigure and the interface
support per-VC queueing (specified by the perVcQueueInterfaces
attribute in the AtmResourceControl component) per-VC queueing
is enabled for all unshaped connections. Otherwise, the common
queue is used. The unshapedTransmitQueueingOper attribute
indicates whether the transmit queueing is perVc or common.
Parsed from file nortelPC-atmCoreV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-AtmCoreMIB
It is migrated in P6.0 to the attributes of the same name under each
ATM service category component of the AtmIf CA.
This attribute applies only for unshaped VCC and VPC
connections. This attribute defines the transmit queueing method for
all unshaped connections under this AtmIf. Per-VC queueing means
that unshaped connections are treated with the same fairness as
shaped queues in the transmit round-robin scheduling. The
alternative to per-VC queueing is to use the common queue for a
particular service category (medium or low priority). The common
queue is only counted as one queue in the transmit round-robin
scheduling. Thus, if there are multiple connections which are
destined for the common queue, they are not fairly allocated a
portion of the transmit bandwidth compared to shaped connections.
When this attribute is set to perVc, any unshaped connection is
allocated its own per-VC queue, and is treated with the same
fairness as any shaped connections. Per-VC queues have a
maximum rate of 58,962 cell/s (25 Mbit/s) in a multi-port shaping
configuration. Per-VC queues also have their own congestion
control level. This means that total number of cell/frame blocks
allocated for several per-VC queues are higher than would be
allowed on the common queue. This can be an advantage in
reducing cell loss due to queue congestion. This attribute may only
be set to perVc if the interface supports per-VC queueing, (specified
by the perVcQueueInterfaces attribute in the AtmResourceControl
component).
When this attribute is set to common, any unshaped connection is
destined for the common queue. The common queue has one set of
congestion control levels for all cells enqueued on it. The common
queue is only allocated one queue position when scheduling which
queue to transmit from. Due to the possibility of unfairness, this
value is only recommended in cases where the configuration cannot
otherwise achieve full link utilization.
When this attribute is set to autoConfigure and the interface
support per-VC queueing (specified by the perVcQueueInterfaces
attribute in the AtmResourceControl component) per-VC queueing
is enabled for all unshaped connections. Otherwise, the common
queue is used. The unshapedTransmitQueueingOper attribute
indicates whether the transmit queueing is perVc or common.
Parsed from file Nortel-MsCarrier-MscPassport-AtmCoreMIB.mib
Module: Nortel-MsCarrier-MscPassport-AtmCoreMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-AtmCoreMIB
[Automatically extracted from oidview.com]
mscAtmIfUnshapedTransmitQueueing OBJECT-TYPE SYNTAX INTEGER { perVc(0), common(1), autoConfigure(2) } ACCESS read-write STATUS obsolete DESCRIPTION "It is migrated in P6.0 to the attributes of the same name under each ATM service category component of the AtmIf CA. This attribute applies only for unshaped VCC and VPC connections. This attribute defines the transmit queueing method for all unshaped connections under this AtmIf. Per-VC queueing means that unshaped connections are treated with the same fairness as shaped queues in the transmit round-robin scheduling. The alternative to per-VC queueing is to use the common queue for a particular service category (medium or low priority). The common queue is only counted as one queue in the transmit round-robin scheduling. Thus, if there are multiple connections which are destined for the common queue, they are not fairly allocated a portion of the transmit bandwidth compared to shaped connections. When this attribute is set to perVc, any unshaped connection is allocated its own per-VC queue, and is treated with the same fairness as any shaped connections. Per-VC queues have a maximum rate of 58,962 cell/s (25 Mbit/s) in a multi-port shaping configuration. Per-VC queues also have their own congestion control level. This means that total number of cell/frame blocks allocated for several per-VC queues are higher than would be allowed on the common queue. This can be an advantage in reducing cell loss due to queue congestion. This attribute may only be set to perVc if the interface supports per-VC queueing, (specified by the perVcQueueInterfaces attribute in the AtmResourceControl component). When this attribute is set to common, any unshaped connection is destined for the common queue. The common queue has one set of congestion control levels for all cells enqueued on it. The common queue is only allocated one queue position when scheduling which queue to transmit from. Due to the possibility of unfairness, this value is only recommended in cases where the configuration cannot otherwise achieve full link utilization. When this attribute is set to autoConfigure and the interface support per-VC queueing (specified by the perVcQueueInterfaces attribute in the AtmResourceControl component) per-VC queueing is enabled for all unshaped connections. Otherwise, the common queue is used. The unshapedTransmitQueueingOper attribute indicates whether the transmit queueing is perVc or common." DEFVAL { autoConfigure } ::= { mscAtmIfProvEntry 70 }
mscAtmIfUnshapedTransmitQueueing OBJECT-TYPE SYNTAX INTEGER { perVc(0), common(1), autoConfigure(2) } ACCESS read-write STATUS obsolete DESCRIPTION "It is migrated in P6.0 to the attributes of the same name under each ATM service category component of the AtmIf CA. This attribute applies only for unshaped VCC and VPC connections. This attribute defines the transmit queueing method for all unshaped connections under this AtmIf. Per-VC queueing means that unshaped connections are treated with the same fairness as shaped queues in the transmit round-robin scheduling. The alternative to per-VC queueing is to use the common queue for a particular service category (medium or low priority). The common queue is only counted as one queue in the transmit round-robin scheduling. Thus, if there are multiple connections which are destined for the common queue, they are not fairly allocated a portion of the transmit bandwidth compared to shaped connections. When this attribute is set to perVc, any unshaped connection is allocated its own per-VC queue, and is treated with the same fairness as any shaped connections. Per-VC queues have a maximum rate of 58,962 cell/s (25 Mbit/s) in a multi-port shaping configuration. Per-VC queues also have their own congestion control level. This means that total number of cell/frame blocks allocated for several per-VC queues are higher than would be allowed on the common queue. This can be an advantage in reducing cell loss due to queue congestion. This attribute may only be set to perVc if the interface supports per-VC queueing, (specified by the perVcQueueInterfaces attribute in the AtmResourceControl component). When this attribute is set to common, any unshaped connection is destined for the common queue. The common queue has one set of congestion control levels for all cells enqueued on it. The common queue is only allocated one queue position when scheduling which queue to transmit from. Due to the possibility of unfairness, this value is only recommended in cases where the configuration cannot otherwise achieve full link utilization. When this attribute is set to autoConfigure and the interface support per-VC queueing (specified by the perVcQueueInterfaces attribute in the AtmResourceControl component) per-VC queueing is enabled for all unshaped connections. Otherwise, the common queue is used. The unshapedTransmitQueueingOper attribute indicates whether the transmit queueing is perVc or common." DEFVAL { autoConfigure } ::= { mscAtmIfProvEntry 70 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.36.2.1.114.110.1.10 | mscAtmIfInterfaceName | 0 | 0 | This attribute associates the AtmIf component with a specific interface on a Function Processorfor example, Lp/1 Ds3/0. This impl… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.20 | mscAtmIfType | 0 | 0 | mscAtmIftype |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.30 | mscAtmIfOamSegmentBoundary | 0 | 0 | This attribute specifies whether the interface is on an OAM segment boundary. When yes is selected, the interface is on an OAM s… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.40 | mscAtmIfMaxVpcs | 0 | 0 | This attribute specifies the maximum number of VPCs that can be configured on this AtmIf. The value must not exceed the total num… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.50 | mscAtmIfMaxVccs | 0 | 0 | This attribute specifies the maximum number of usable VCCs that can be configured on this AtmIf. The value must not exceed the nu… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.60 | mscAtmIfTrafficShaping | 0 | 0 | mscAtmIftrafficShaping |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.80 | mscAtmIfUsageParameterControl | 0 | 0 | It is migrated in P6.0 to the attributes of the same name under each ATM service category component of the AtmIf CA. This attrib… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.85 | mscAtmIfMaxVpiBits | 0 | 0 | This attribute specifies the maximum number of VPI bits that may be active for this AtmIf. These bits start at the least signifi… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.90 | mscAtmIfRemoteAtmInterfaceLabel | 0 | 0 | This attribute specifies a unique indication of the remote ATM service or interface component connected to this one. The value o… |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.91 | mscAtmIfTxCellMemory | 0 | 0 | mscAtmIftxCellMemory |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.100 | mscAtmIfFaultHoldOffTime | 0 | 0 | mscAtmIfFaultHoldOfftime |
| 1.3.6.1.4.1.562.36.2.1.114.110.1.110 | mscAtmIfCtdCalculation | 0 | 0 | This attribute specifies whether cell transfer delay calculation should be performed on loopback cells for each SPVC and SPVP con… |