| atmIfVpcNrpIndex |
.1.3.6.1.4.1.562.2.4.1.114.4.4.1.1.10 |
|
This variable represents the index for the atmIfVpcNrp tables.
|
| atmIfVpcNrpRowStatus |
.1.3.6.1.4.1.562.2.4.1.114.4.4.1.1.1 |
|
This variable is used as the basis for SNMP naming of
atmIfVpcNrp components.
These components can be added and deleted.
|
| atmIfVpcNrpComponentName |
.1.3.6.1.4.1.562.2.4.1.114.4.4.1.1.2 |
|
This variable provides the component's string name for
use with the ASCII Console Interface
|
| atmIfVpcNrpStorageType |
.1.3.6.1.4.1.562.2.4.1.114.4.4.1.1.4 |
|
This variable represents the storage type value for the
atmIfVpcNrp tables.
|
| atmIfVpcNrpNextHop |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.10 |
|
This attribute specifies the Nrp component with which this Nrp is
associated. A sample value is AtmIf/31 Vcc/0.32 Nrp.
|
| atmIfVpcNrpConnectionPointType |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.20 |
|
This attribute specifies the connection point type desired for a Nrp
component. The actual connection point type value is visible in the
parent component's connectionPointType attribute.
The desired connection point type can be specified directly as a
segmentEndPoint or connectingPoint. If autoConfigure is
specified, the switch will select the connection point type based on
the type attribute of the associated AtmIf, choosing
segmentEndPoint for a UNI-type ATM interface and
connectingPoint for a PPI-type ATM interface.
It is obsoleted. The value is mapped into oamSegmentBoundary
attribute. segmentEndPoint is mapped into yes. connectingPoint is
mapped into no. autoConfigure is mapped into sameAsInterface.
|
| atmIfVpcNrpOamSegmentBoundary |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.30 |
|
This attribute specifies the OAM segment boundary desired for a
Nrp component. It affects the connection point type value visible in
the parent component's connectionPointType attribute.
The desired OAM segment boundary can be specified directly as
yes, no or sameAsInterface. If sameAsInterface is specified, the
OAM segment boundary is same as the oamSegmentBoundary
attribute of the associated AtmIf and the switch will set the
connectionPointType, choosing segmentEndPoint for a segment-
boundary ATM interface and connectingPoint for a non-segment-
boundary ATM interface.
|
| atmIfVpcNrpTxAal5PartialPacketDiscard |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.31 |
|
This attribute is obsolete in P4.2 and has been migrated under Vcd
(Vpd) component.
This attribute specifies whether the AAL5 Partial Packet Discard
(PPD) feature has been enabled or disabled on the Nrp in the
transmit direction. This feature allows the NRP to discard the
remainder of a cell-forwarded AAL5 frame if a cell of this frame
has been discarded due to congestion. This increases the 'goodput'
of the link, since cells which are only going to be discarded by the
AAL5 reassembly are not transmitted.
When this attribute is set to enabled, the PPD feature is applied in
the transmit direction. It should only be enabled for connections
whose end points are performing AAL5 segmentation and
reassembly. When this attribute is set to disabled, the PPD feature is
not applied to traffic for this connection in the transmit direction.
Note that specifying enabled for a non-AAL5 connection will cause
all traffic to be discarded once congestion is encountered.
|
| atmIfVpcNrpRxAal5PartialPacketDiscard |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.32 |
|
This attribute is obsolete in P4.2 and has been migrated under Vcd
(Vpd) component.
This attribute specifies whether the AAL5 Partial Packet Discard
(PPD) feature has been enabled or disabled on the Nrp in the
receive direction. This feature allows the NRP to discard the
remainder of a cell-forwarded AAL5 frame if a cell of this frame
has been discarded due to congestion or usage parameter control
(UPC). This increases the 'goodput' of the link, since cells which
are only going to be discarded by the AAL5 reassembly are not
transmitted.
When this attribute is set to enabled, the PPD feature is applied in
the receive direction. It should only be enabled for connections
whose end points are performing AAL5 segmentation and
reassembly. When this attribute is set to disabled, the PPD feature is
not applied to traffic for this connection in the receive direction.
When this attribute is set to sameAsTx, the PPD feature for traffic
in the receive direction will be configured the same way as it is in
the transmit direction.
Note that specifying enabled for a non-AAL5 connection will cause
all traffic to be discarded once congestion is encountered.
|
| atmIfVpcNrpBandwidthElastic |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.33 |
|
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 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 will be displayed in the bandwidthReduction
attribute.
A value of yes, indicates that this connection is elastic, and the
bandwidth may be reduced but the connection will not be released.
Currently, this attribute should only be set to yes for situations
where this Nrp is functioning as a loopback on one side of an IMA
link. There are no other situations where this setting is valid.
A value of no indicates that the bandwidth for this connection will
not be reduced in the event of link bandwidth reduction. However,
this connection may be released based on its holdingPriority.
|
| atmIfVpcNrpOverrideHoldingPriority |
.1.3.6.1.4.1.562.2.4.1.114.4.4.100.1.34 |
|
This attribute specifies the holding priority of this connection.
Holding priority is used when there is an IMA group where some
physical links have failed. Holding priority determines the order in
which connections are released. 4 is the lowest holding priority and
is released first. 0 is a higher priority and is released last. The value
specified in this attribute will override whatever holdingPriority that
has been provisioned at the Vcd (or Vpd). If the value is left at the
default of noOverride, the holdingPriority provisioned at the Vcd
(or Vpd) will be used.
|
| atmIfVccNrpIndex |
.1.3.6.1.4.1.562.2.4.1.114.5.4.1.1.10 |
|
This variable represents the index for the atmIfVccNrp tables.
|
| atmIfVccNrpRowStatus |
.1.3.6.1.4.1.562.2.4.1.114.5.4.1.1.1 |
|
This variable is used as the basis for SNMP naming of
atmIfVccNrp components.
These components can be added and deleted.
|
| atmIfVccNrpComponentName |
.1.3.6.1.4.1.562.2.4.1.114.5.4.1.1.2 |
|
This variable provides the component's string name for
use with the ASCII Console Interface
|
| atmIfVccNrpStorageType |
.1.3.6.1.4.1.562.2.4.1.114.5.4.1.1.4 |
|
This variable represents the storage type value for the
atmIfVccNrp tables.
|
| atmIfVccNrpNextHop |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.10 |
|
This attribute specifies the Nrp component with which this Nrp is
associated. A sample value is AtmIf/31 Vcc/0.32 Nrp.
|
| atmIfVccNrpConnectionPointType |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.20 |
|
This attribute specifies the connection point type desired for a Nrp
component. The actual connection point type value is visible in the
parent component's connectionPointType attribute.
The desired connection point type can be specified directly as a
segmentEndPoint or connectingPoint. If autoConfigure is
specified, the switch will select the connection point type based on
the type attribute of the associated AtmIf, choosing
segmentEndPoint for a UNI-type ATM interface and
connectingPoint for a PPI-type ATM interface.
It is obsoleted. The value is mapped into oamSegmentBoundary
attribute. segmentEndPoint is mapped into yes. connectingPoint is
mapped into no. autoConfigure is mapped into sameAsInterface.
|
| atmIfVccNrpOamSegmentBoundary |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.30 |
|
This attribute specifies the OAM segment boundary desired for a
Nrp component. It affects the connection point type value visible in
the parent component's connectionPointType attribute.
The desired OAM segment boundary can be specified directly as
yes, no or sameAsInterface. If sameAsInterface is specified, the
OAM segment boundary is same as the oamSegmentBoundary
attribute of the associated AtmIf and the switch will set the
connectionPointType, choosing segmentEndPoint for a segment-
boundary ATM interface and connectingPoint for a non-segment-
boundary ATM interface.
|
| atmIfVccNrpTxAal5PartialPacketDiscard |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.31 |
|
This attribute is obsolete in P4.2 and has been migrated under Vcd
(Vpd) component.
This attribute specifies whether the AAL5 Partial Packet Discard
(PPD) feature has been enabled or disabled on the Nrp in the
transmit direction. This feature allows the NRP to discard the
remainder of a cell-forwarded AAL5 frame if a cell of this frame
has been discarded due to congestion. This increases the 'goodput'
of the link, since cells which are only going to be discarded by the
AAL5 reassembly are not transmitted.
When this attribute is set to enabled, the PPD feature is applied in
the transmit direction. It should only be enabled for connections
whose end points are performing AAL5 segmentation and
reassembly. When this attribute is set to disabled, the PPD feature is
not applied to traffic for this connection in the transmit direction.
Note that specifying enabled for a non-AAL5 connection will cause
all traffic to be discarded once congestion is encountered.
|
| atmIfVccNrpRxAal5PartialPacketDiscard |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.32 |
|
This attribute is obsolete in P4.2 and has been migrated under Vcd
(Vpd) component.
This attribute specifies whether the AAL5 Partial Packet Discard
(PPD) feature has been enabled or disabled on the Nrp in the
receive direction. This feature allows the NRP to discard the
remainder of a cell-forwarded AAL5 frame if a cell of this frame
has been discarded due to congestion or usage parameter control
(UPC). This increases the 'goodput' of the link, since cells which
are only going to be discarded by the AAL5 reassembly are not
transmitted.
When this attribute is set to enabled, the PPD feature is applied in
the receive direction. It should only be enabled for connections
whose end points are performing AAL5 segmentation and
reassembly. When this attribute is set to disabled, the PPD feature is
not applied to traffic for this connection in the receive direction.
When this attribute is set to sameAsTx, the PPD feature for traffic
in the receive direction will be configured the same way as it is in
the transmit direction.
Note that specifying enabled for a non-AAL5 connection will cause
all traffic to be discarded once congestion is encountered.
|
| atmIfVccNrpBandwidthElastic |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.33 |
|
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 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 will be displayed in the bandwidthReduction
attribute.
A value of yes, indicates that this connection is elastic, and the
bandwidth may be reduced but the connection will not be released.
Currently, this attribute should only be set to yes for situations
where this Nrp is functioning as a loopback on one side of an IMA
link. There are no other situations where this setting is valid.
A value of no indicates that the bandwidth for this connection will
not be reduced in the event of link bandwidth reduction. However,
this connection may be released based on its holdingPriority.
|
| atmIfVccNrpOverrideHoldingPriority |
.1.3.6.1.4.1.562.2.4.1.114.5.4.100.1.34 |
|
This attribute specifies the holding priority of this connection.
Holding priority is used when there is an IMA group where some
physical links have failed. Holding priority determines the order in
which connections are released. 4 is the lowest holding priority and
is released first. 0 is a higher priority and is released last. The value
specified in this attribute will override whatever holdingPriority that
has been provisioned at the Vcd (or Vpd). If the value is left at the
default of noOverride, the holdingPriority provisioned at the Vcd
(or Vpd) will be used.
|
| atmIfVptVccNrpIndex |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.1.1.10 |
|
This variable represents the index for the atmIfVptVccNrp tables.
|
| atmIfVptVccNrpRowStatus |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.1.1.1 |
|
This variable is used as the basis for SNMP naming of
atmIfVptVccNrp components.
These components can be added and deleted.
|
| atmIfVptVccNrpComponentName |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.1.1.2 |
|
This variable provides the component's string name for
use with the ASCII Console Interface
|
| atmIfVptVccNrpStorageType |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.1.1.4 |
|
This variable represents the storage type value for the
atmIfVptVccNrp tables.
|
| atmIfVptVccNrpNextHop |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.10 |
|
This attribute specifies the Nrp component with which this Nrp is
associated. A sample value is AtmIf/31 Vcc/0.32 Nrp.
|
| atmIfVptVccNrpConnectionPointType |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.20 |
|
This attribute specifies the connection point type desired for a Nrp
component. The actual connection point type value is visible in the
parent component's connectionPointType attribute.
The desired connection point type can be specified directly as a
segmentEndPoint or connectingPoint. If autoConfigure is
specified, the switch will select the connection point type based on
the type attribute of the associated AtmIf, choosing
segmentEndPoint for a UNI-type ATM interface and
connectingPoint for a PPI-type ATM interface.
It is obsoleted. The value is mapped into oamSegmentBoundary
attribute. segmentEndPoint is mapped into yes. connectingPoint is
mapped into no. autoConfigure is mapped into sameAsInterface.
|
| atmIfVptVccNrpOamSegmentBoundary |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.30 |
|
This attribute specifies the OAM segment boundary desired for a
Nrp component. It affects the connection point type value visible in
the parent component's connectionPointType attribute.
The desired OAM segment boundary can be specified directly as
yes, no or sameAsInterface. If sameAsInterface is specified, the
OAM segment boundary is same as the oamSegmentBoundary
attribute of the associated AtmIf and the switch will set the
connectionPointType, choosing segmentEndPoint for a segment-
boundary ATM interface and connectingPoint for a non-segment-
boundary ATM interface.
|
| atmIfVptVccNrpTxAal5PartialPacketDiscard |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.31 |
|
This attribute is obsolete in P4.2 and has been migrated under Vcd
(Vpd) component.
This attribute specifies whether the AAL5 Partial Packet Discard
(PPD) feature has been enabled or disabled on the Nrp in the
transmit direction. This feature allows the NRP to discard the
remainder of a cell-forwarded AAL5 frame if a cell of this frame
has been discarded due to congestion. This increases the 'goodput'
of the link, since cells which are only going to be discarded by the
AAL5 reassembly are not transmitted.
When this attribute is set to enabled, the PPD feature is applied in
the transmit direction. It should only be enabled for connections
whose end points are performing AAL5 segmentation and
reassembly. When this attribute is set to disabled, the PPD feature is
not applied to traffic for this connection in the transmit direction.
Note that specifying enabled for a non-AAL5 connection will cause
all traffic to be discarded once congestion is encountered.
|
| atmIfVptVccNrpRxAal5PartialPacketDiscard |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.32 |
|
This attribute is obsolete in P4.2 and has been migrated under Vcd
(Vpd) component.
This attribute specifies whether the AAL5 Partial Packet Discard
(PPD) feature has been enabled or disabled on the Nrp in the
receive direction. This feature allows the NRP to discard the
remainder of a cell-forwarded AAL5 frame if a cell of this frame
has been discarded due to congestion or usage parameter control
(UPC). This increases the 'goodput' of the link, since cells which
are only going to be discarded by the AAL5 reassembly are not
transmitted.
When this attribute is set to enabled, the PPD feature is applied in
the receive direction. It should only be enabled for connections
whose end points are performing AAL5 segmentation and
reassembly. When this attribute is set to disabled, the PPD feature is
not applied to traffic for this connection in the receive direction.
When this attribute is set to sameAsTx, the PPD feature for traffic
in the receive direction will be configured the same way as it is in
the transmit direction.
Note that specifying enabled for a non-AAL5 connection will cause
all traffic to be discarded once congestion is encountered.
|
| atmIfVptVccNrpBandwidthElastic |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.33 |
|
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 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 will be displayed in the bandwidthReduction
attribute.
A value of yes, indicates that this connection is elastic, and the
bandwidth may be reduced but the connection will not be released.
Currently, this attribute should only be set to yes for situations
where this Nrp is functioning as a loopback on one side of an IMA
link. There are no other situations where this setting is valid.
A value of no indicates that the bandwidth for this connection will
not be reduced in the event of link bandwidth reduction. However,
this connection may be released based on its holdingPriority.
|
| atmIfVptVccNrpOverrideHoldingPriority |
.1.3.6.1.4.1.562.2.4.1.114.9.20.4.100.1.34 |
|
This attribute specifies the holding priority of this connection.
Holding priority is used when there is an IMA group where some
physical links have failed. Holding priority determines the order in
which connections are released. 4 is the lowest holding priority and
is released first. 0 is a higher priority and is released last. The value
specified in this attribute will override whatever holdingPriority that
has been provisioned at the Vcd (or Vpd). If the value is left at the
default of noOverride, the holdingPriority provisioned at the Vcd
(or Vpd) will be used.
|
