Wellfleet-INT-SERV-MIB

MIB Reference — IPNetwork Monitor

All MIBsWellfleet-INT-SERV-MIB

Category: DiffServ and QoS, Wellfleet BayNetworks System Management

Description:

Manages Wellfleet Integrated Services QoS parameters, RSVP reservations, and flow admission control.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress

From Wellfleet-COMMON-MIB

wfIntegratedServicesGroupOBJECT-IDENTITY

What Is Wellfleet-INT-SERV-MIB?

This is a vendor-specific proprietary MIB from Wellfleet Communications (later Bay Networks/Nortel) managing Integrated Services (IntServ) quality-of-service features, including RSVP-signaled bandwidth reservations and flow admission control. It exposes objects describing active reservations, per-flow admission decisions, and allocated QoS bandwidth. It supports software status monitoring because a flow that is rejected by admission control, or a reservation that fails to establish, directly indicates that a QoS-sensitive application (such as legacy voice or video) will experience degraded service on that router. It conceptually parallels the IETF Integrated Services/RSVP MIBs (RFC 2213/2214) though implemented as a Wellfleet-proprietary equivalent. It is typically deployed on Wellfleet/Bay Networks routers carrying QoS-sensitive traffic that requires RSVP-based bandwidth reservation across a WAN core. Engineers can download the Wellfleet-INT-SERV-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in Wellfleet-INT-SERV-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • active RSVP reservation count
  • flow admission control decision
  • reserved QoS bandwidth per flow

Supported Devices

  • Wellfleet/Bay Networks routers configured for Integrated Services QoS/RSVP

Monitoring Examples

No sample_objects were provided for this module; based on the short_desc, an operator would poll the RSVP reservation table for active flow entries and the corresponding admission-control decision per flow. A rising count of rejected/denied admission attempts would indicate the reserved bandwidth pool on that interface is exhausted, degrading QoS for new voice or video flows.

OIDs
OID symbolicOID numericTypeAccessDescription
wfReservationsResourcesGroup1.3.6.1.4.1.18.3.5.16.2
wfTxLineRscGroup1.3.6.1.4.1.18.3.5.16.2.1
wfTxLineRscTable1.3.6.1.4.1.18.3.5.16.2.1.1not-accessibleThis table contains information about line resources and guaranteed service traffic on a per-line basis for outbound traffic.
wfTxLineRscEntry1.3.6.1.4.1.18.3.5.16.2.1.1.1not-accessible
INT wfTxLineRscKillReservations1.3.6.1.4.1.18.3.5.16.2.1.1.1.1INTEGERread-writeKill all reservations on this line.
INT wfTxLineRscLineNumber1.3.6.1.4.1.18.3.5.16.2.1.1.1.2INTEGERread-onlyLine number
GAU wfTxLineRscReservableBandwidth1.3.6.1.4.1.18.3.5.16.2.1.1.1.3Gaugeread-onlyamount of reservable bandwidth left on this line (bits per second)
GAU wfTxLineRscReservedBandwidth1.3.6.1.4.1.18.3.5.16.2.1.1.1.4Gaugeread-onlyamount of reserved bandwidth on this line (bits per second)
GAU wfTxLineRscGuaranteedFlows1.3.6.1.4.1.18.3.5.16.2.1.1.1.5Gaugeread-onlynumber of guaranteed-service flows
CTR wfTxLineRscGuaranteedPackets1.3.6.1.4.1.18.3.5.16.2.1.1.1.6Counterread-onlyNumber of guaranteed-service packets that have exited this line
CTR wfTxLineRscGuaranteedBytes1.3.6.1.4.1.18.3.5.16.2.1.1.1.7Counterread-onlyNumber of guaranteed-service bytes that have exited this line
CTR wfTxLineRscGuaranteedPolicedPackets1.3.6.1.4.1.18.3.5.16.2.1.1.1.8Counterread-onlyNumber of guaranteed-service packets that were policed (dropped)
CTR wfTxLineRscGuaranteedPolicedBytes1.3.6.1.4.1.18.3.5.16.2.1.1.1.9Counterread-onlyNumber of guaranteed-service bytes that were policed (dropped)
GAU wfTxLineRscGuaranteedBandwidth1.3.6.1.4.1.18.3.5.16.2.1.1.1.10Gaugeread-onlyGuaranteed service bandwidth measured over the last bandwidth interval
GAU wfTxLineRscGuaranteedAvgBandwidth1.3.6.1.4.1.18.3.5.16.2.1.1.1.11Gaugeread-onlyGuaranteed service average bandwidth
GAU wfTxLineRscGuaranteedMaxBandwidth1.3.6.1.4.1.18.3.5.16.2.1.1.1.12Gaugeread-onlyGuaranteed service maximum bandwidth
GAU wfTxLineRscGuaranteedAvgPacketDelay1.3.6.1.4.1.18.3.5.16.2.1.1.1.13Gaugeread-onlyGuaranteed service average packet delay
GAU wfTxLineRscGuaranteedMaxPacketDelay1.3.6.1.4.1.18.3.5.16.2.1.1.1.14Gaugeread-onlyGuaranteed service maximum packet delay
CTR wfTxLineRscUnreservedPolicedPackets1.3.6.1.4.1.18.3.5.16.2.1.1.1.15Counterread-onlyNumber of unreserved packets that were policed (dropped). If priority queueing is also enabled, this statistic is not maintained. See wfCctOptsEntry.
CTR wfTxLineRscUnreservedPolicedBytes1.3.6.1.4.1.18.3.5.16.2.1.1.1.16Counterread-onlyNumber of unreserved bytes that were policed (dropped). If priority queueing is also enabled, this statistic is not maintained. See wfCctOptsEntry.
wfTxLineRscCfgTable1.3.6.1.4.1.18.3.5.16.2.1.3not-accessibleThis table contains resource reservation configuration information on a per-line basis for outbound traffic.
wfTxLineRscCfgEntry1.3.6.1.4.1.18.3.5.16.2.1.3.1not-accessible
INT wfTxLineRscCfgDelete1.3.6.1.4.1.18.3.5.16.2.1.3.1.1INTEGERread-writeCreation and deletion flag for this record
INT wfTxLineRscCfgLineNumber1.3.6.1.4.1.18.3.5.16.2.1.3.1.2INTEGERread-onlyLine number
INT wfTxLineRscCfgEstBandwidth1.3.6.1.4.1.18.3.5.16.2.1.3.1.3INTEGERread-writeEstimated usable bandwidth by this router in bits per second.
INT wfTxLineRscCfgResvBandwidth1.3.6.1.4.1.18.3.5.16.2.1.3.1.4INTEGERread-writeReservable bandwidth on this line.
INT wfTxLineRscCfgResvTrafficAlgorithm1.3.6.1.4.1.18.3.5.16.2.1.3.1.5INTEGERread-writereserved-traffic queueing algorithm: none - schedule as best-effort priority - schedule ahead of best-effort
INT wfTxLineRscCfgResvPolicingAlgorithm1.3.6.1.4.1.18.3.5.16.2.1.3.1.6INTEGERread-writereserved-traffic policing algorithm: none - no policing lbucket - leaky bucket policing
INT wfTxLineRscCfgBandwidthInterval1.3.6.1.4.1.18.3.5.16.2.1.3.1.7INTEGERread-writeInterval over which bandwidth is measured, in seconds. Default is ten seconds.
INT wfTxLineRscCfgInflateReservations1.3.6.1.4.1.18.3.5.16.2.1.3.1.8INTEGERread-writeAny reservation made on this line will be inflated by this percentage.
INT wfTxLineRscCfgUnreservedPolicingAlgorithm1.3.6.1.4.1.18.3.5.16.2.1.3.1.9INTEGERread-writePolicing algorithm for unreserved traffic. qlimit (1) limits the number of buffers (packets) of unreserved traffic that will be queued up. lbucket (2) applies a leaky bucket algorithm based on the bandwidth that is not guaranteed. The leaky bucket algorithm does not allow the unreserved traffic to take advantage of unused reserved bandwidth.
INT wfTxLineRscCfgUnreservedQueueLength1.3.6.1.4.1.18.3.5.16.2.1.3.1.10INTEGERread-writeIf the unreserved policing algorithm is qlimit, this is the maximum number of best-effort packets that will be held for transmission. This parameter affects the amount best-effort traffic will be clipped when congestion occurs. Overriden by priority queueing limits, if configured.
INT wfTxLineRscCfgMultiLineSelectAlgorithm1.3.6.1.4.1.18.3.5.16.2.1.3.1.11INTEGERread-writeThis algorithm influences how the circuit resource manager will select which line will be used for a new resource request. first (1) does a first-fit. round (2) does a round-robin. If first-fit is selected and the ThresholdBandwidth parameter is non-zero, a first-fit algorithm is done until a line reaches its threshold. The algorithm then moves to the the next line. Once all lines are at their threshold, the algorithm is simply first-fit. All lines for a circuit should select the same algorithm. If any one specifies first-fit, first-fit will be used.
INT wfTxLineRscCfgMultiLineThresholdBandwidth1.3.6.1.4.1.18.3.5.16.2.1.3.1.12INTEGERread-writeIf the multi-line selection algorithm is threshold, this is the threshold value for this line. It must be less than the reservable bandwidth value.
INT wfTxLineRscCfgResvLatency1.3.6.1.4.1.18.3.5.16.2.1.3.1.13INTEGERread-writeThe maximum latency acceptable for a reserved flow packet. This parameter limits the amount of unreserved data that the link scheduler can put onto the driver transmit ring. When the data on the transmit ring reaches a size where additional unreserved data would take longer than the value of this parameter to clock out, no more data will be enqueued. Reduce this parameter to obtain better delay characteristics for reserved flows, but note that this will result in somewhat reduced overall throughput. Units are milliseconds.
INT wfTxLineRscCfgLargestBandwidth1.3.6.1.4.1.18.3.5.16.2.1.3.1.14INTEGERread-writeThe maximum bandwidth that a single flow can reserve on this line. [ 0 (zero) implies no maximum.]
INT wfTxLineRscCfgLargestBuffer1.3.6.1.4.1.18.3.5.16.2.1.3.1.15INTEGERread-writeThe maximum buffer space that a single flow can reserve on this line. [ 0 (zero) implies no maximum.]
wfReservationsFlowspecGroup1.3.6.1.4.1.18.3.5.16.3
wfFlowspecSt2V3Table1.3.6.1.4.1.18.3.5.16.3.1not-accessibleThis is the ST-2 version 3 flowspec. The FlowSpec is used to convey stream service requirements end-to-end. We expect that other versions of FlowSpec will be needed in the future, which may or may not be subsets or supersets of the version described here. PBytes will allow new constraints to be added to the end without having to simultaneously update all implementations in the field. Implementations are expected to be able to process in a graceful manner a Version 4 (or higher) structure that has more elements than shown here.
wfFlowspecSt2V3Entry1.3.6.1.4.1.18.3.5.16.3.1.1not-accessible
INT wfFlowspecSt2V3Index1.3.6.1.4.1.18.3.5.16.3.1.1.1INTEGERread-onlyflowspec index
INT wfFlowspecSt2V3Version1.3.6.1.4.1.18.3.5.16.3.1.1.2INTEGERread-onlyVersion identifies the version of the FlowSpec. Version 3 is defined here.
INT wfFlowspecSt2V3DutyFactor1.3.6.1.4.1.18.3.5.16.3.1.1.3INTEGERread-onlyDutyFactor is the estimated proportion of the time that the requested bandwidth will actually be in use. Zero is taken to represent 256 and signify a duty factor of 1. Other values are to be divided by 256 to yield the duty factor.
INT wfFlowspecSt2V3ErrorRate1.3.6.1.4.1.18.3.5.16.3.1.1.4INTEGERread-onlyErrorRate expresses the error rate as the negative exponent of 10 in the error rate. One (1) represents a bit error rate of 0.1 and 10 represents 0.0000000001.
INT wfFlowspecSt2V3Precedence1.3.6.1.4.1.18.3.5.16.3.1.1.5INTEGERread-onlyPrecedence is the precedence of the connection being established. Zero represents the lowest precedence. Note that non-zero values of this parameter should be subject to authentication and authorization checks, which are not specified here. In general, the distinction between precedence and priority is that precedence specifies streams that are permitted to take previously committed resources from another stream, while priority identifies those PDUs that a stream is most willing to have dropped when the stream exceeds its guaranteed limits.
INT wfFlowspecSt2V3Reliability1.3.6.1.4.1.18.3.5.16.3.1.1.6INTEGERread-onlyReliability is modified by each intervening ST agent as a measure of the probability that a given offered data packet will be forwarded and not dropped. Zero is taken to represent 256 and signify a probability of 1. Other values are to be divided by 256 to yield the probability.
INT wfFlowspecSt2V3Tradeoffs1.3.6.1.4.1.18.3.5.16.3.1.1.7INTEGERread-onlyTradeoffs is incompletely defined at this time. Bits currently specified are as follows: The most significant bit in the field, bit 0 in the Figure 24, when one (1) means that each ST agent must 'implement' all constraints in the FlowSpec even if they are not shown in the figure, e.g., when the FlowSpec has been extended. When zero (0), unknown constraints may be ignored. The second most significant bit in the field, bit 1, when one (1) means that one or more constraints are unknown and have been ignored. When zero (0), all constraints are known and have been processed. The third most significant bit in the field, bit 2, is used for RevChrg; see Section 3.6.5 (page 46). Other bits are currently unspecified, and should be set to zero (0) by the origin ST agent and not changed by other agents unless those agents know their meaning.
INT wfFlowspecSt2V3RecoveryTimeout1.3.6.1.4.1.18.3.5.16.3.1.1.8INTEGERread-onlyRecoveryTimeout specifies the nominal number of milliseconds that the application is willing to wait for a failed system component to be detected and any corrective action to be taken.
INT wfFlowspecSt2V3LimitOnCost1.3.6.1.4.1.18.3.5.16.3.1.1.9INTEGERread-onlyLimitOnCost specifies the maximum cost that the origin is willing to expend. A value of zero indicates that the application is not willing to incur any direct charges for the resources used by the stream. The meaning of non-zero values is left for further study.
INT wfFlowspecSt2V3LimitOnDelay1.3.6.1.4.1.18.3.5.16.3.1.1.10INTEGERread-onlyLimitOnDelay specifies the maximum end-to-end delay, in milliseconds, that can be tolerated by the origin.
INT wfFlowspecSt2V3LimitOnPDUBytes1.3.6.1.4.1.18.3.5.16.3.1.1.11INTEGERread-onlyLimitOnPDUBytes is the smallest packet size, in terms of ST-user data bytes, that can be tolerated by the origin.
INT wfFlowspecSt2V3LimitOnPDURate1.3.6.1.4.1.18.3.5.16.3.1.1.12INTEGERread-onlyLimitOnPDURate is the lowest packet rate that can be tolerated by the origin, expressed as tenths of a packet per second.
INT wfFlowspecSt2V3MinBytesXRate1.3.6.1.4.1.18.3.5.16.3.1.1.13INTEGERread-onlyMinBytesXRate is the minimum bandwidth that can be tolerated by the origin, expressed as a product of bytes and tenths of a packet per second.
INT wfFlowspecSt2V3AccdMeanDelay1.3.6.1.4.1.18.3.5.16.3.1.1.14INTEGERread-onlyAccdMeanDelay is modified by each intervening ST agent. This provides a means of reporting the total expected delay, in milliseconds, for a data packet. Note that it is implicitly assumed that the requested mean delay is zero and there is no limit on the mean delay, so there are no parameters to specify these explicitly.
INT wfFlowspecSt2V3AccdDelayVariance1.3.6.1.4.1.18.3.5.16.3.1.1.15INTEGERread-onlyAccdDelayVariance is also modified by each intervening ST agent as a measure, in milliseconds squared, of the packet dispersion. This quantity can be used by the target or origin in determining whether the resulting stream has an adequate quality of service to support the application. Note that it is implicitly assumed that the requested delay variance is zero and there is no limit on the delay variance, so there are no parameters to specify these explicitly.
INT wfFlowspecSt2V3DesPDUBytes1.3.6.1.4.1.18.3.5.16.3.1.1.16INTEGERread-onlyDesPDUBytes is the desired PDU size in bytes. This is not necessarily the same as the minimum necessary PDU size. This value may be made smaller by intervening ST agents so long as it is not made smaller than LimitOnPDUBytes. The *PDUBytes limits measure the size of the PDUs of next-higher protocol layer, i.e., the user information contained in a data packet. An ST agent must account for both the ST Header (including possible IP encapsulation) and any local network headers and trailers when comparing a network's MTU with *PDUBytes. In an ACCEPT message, the value of this field will be no larger than the MTU of the path to the specified target.
INT wfFlowspecSt2V3DesPDURate1.3.6.1.4.1.18.3.5.16.3.1.1.17INTEGERread-onlyDesPDURate is the requested PDU rate, expressed as tenths of a packet per second. This value may be made smaller by intervening ST agents so long as it is not made smaller than LimitOnPDURate.
wfIntSrvIfFlowGroup1.3.6.1.4.1.18.3.5.16.4
wfIntSrvIfFlowTable1.3.6.1.4.1.18.3.5.16.4.1not-accessibleInformation describing the reserved flows us- ing the system's interfaces.
wfIntSrvIfFlowEntry1.3.6.1.4.1.18.3.5.16.4.1.1not-accessibleInformation describing the use of a given in- terface by a given flow.
IP wfIntSrvIfFlowDestination1.3.6.1.4.1.18.3.5.16.4.1.1.1IpAddressread-onlyThe IP Address used as a destination address for all senders in this flow.
INT wfIntSrvIfFlowDestinationProtocol1.3.6.1.4.1.18.3.5.16.4.1.1.2INTEGERread-onlyThe value of the IP Protocol field in this flow, typically UDP or TCP.
INT wfIntSrvIfFlowDestinationPort1.3.6.1.4.1.18.3.5.16.4.1.1.3INTEGERread-onlyThe UDP or TCP port number used as a destina- tion port for all senders in this flow. A value of zero indicates that the IP protocol in use, specified by wfIntSrvIfFlowDestinationProtocol, does not use ports.
IP wfIntSrvIfFlowSource1.3.6.1.4.1.18.3.5.16.4.1.1.4IpAddressread-onlyThe IP Address used as a source address by this sender in this flow. If zero, all senders are included in the flow.
INT wfIntSrvIfFlowSourcePort1.3.6.1.4.1.18.3.5.16.4.1.1.5INTEGERread-onlyThe UDP or TCP port number used as a source port by this sender in this flow. A value of zero indicates that the IP protocol in use, specified by wfIntSrvIfFlowDestinationProtocol, does not use ports, or (when wfIntSrvIfFlowDestinationPort is non-zero) that data from all senders is in- cluded in this class of flows.
INT wfIntSrvIfFlowRate1.3.6.1.4.1.18.3.5.16.4.1.1.6INTEGERread-onlyThe Average Bit Rate of the sender's data stream, in Kilobits. The rate may be arbi- trarily fast during a short interval such as the duration of a video frame. However, over any two such intervals it will not average fas- ter than the average rate as transmitted by the sender.
INT wfIntSrvIfFlowWeight1.3.6.1.4.1.18.3.5.16.4.1.1.7INTEGERread-onlyThe weight used to prioritize the traffic. Note that the interpretation of this object is implementation-specific, as implementations vary in their use of weighting procedures.
INT wfIntSrvIfFlowQueue1.3.6.1.4.1.18.3.5.16.4.1.1.8INTEGERread-onlyThe number of the queue used by this traffic. Note that the interpretation of this object is implementation-specific, as implementations vary in their use of queue identifiers.
INT wfIntSrvIfFlowMin1.3.6.1.4.1.18.3.5.16.4.1.1.9INTEGERread-onlyThe minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size.
INT wfIntSrvIfFlowCct1.3.6.1.4.1.18.3.5.16.4.1.1.10INTEGERread-onlyThe circuit number of this IntSrv interface

RFC description

Manages Integrated Services resource reservations and traffic guarantees on per-line basis for QoS flow specifications.

Start monitoring Wellfleet/Bay Networks routers configured for Integrated Services QoS/RSVP (flow-admission/reservation status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download Wellfleet-INT-SERV-MIB