AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Wellfleet » Wellfleet-INT-SERV-MIB » Objects

Wellfleet-INT-SERV-MIB.mib object view, vendor Wellfleet

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file Wellfleet-INT-SERV-MIB and use it to monitor vendor specific OID's.

Wellfleet-INT-SERV-MIB file content

Object view of Wellfleet-INT-SERV-MIB:

Scalar Object
wfTxLineRscEntry .1.3.6.1.4.1.18.3.5.16.2.1.1.1
wfTxLineRscCfgEntry .1.3.6.1.4.1.18.3.5.16.2.1.3.1
wfFlowspecSt2V3Entry .1.3.6.1.4.1.18.3.5.16.3.1.1
wfIntSrvIfFlowEntry .1.3.6.1.4.1.18.3.5.16.4.1.1
Information describing the use of a given in- terface by a given flow.
Tabular Object
wfTxLineRscLineNumber .1.3.6.1.4.1.18.3.5.16.2.1.1.1.2
Line number
wfTxLineRscKillReservations .1.3.6.1.4.1.18.3.5.16.2.1.1.1.1
Kill all reservations on this line.
wfTxLineRscReservableBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.1.1.3
amount of reservable bandwidth left on this line (bits per second)
wfTxLineRscReservedBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.1.1.4
amount of reserved bandwidth on this line (bits per second)
wfTxLineRscGuaranteedFlows .1.3.6.1.4.1.18.3.5.16.2.1.1.1.5
number of guaranteed-service flows
wfTxLineRscGuaranteedPackets .1.3.6.1.4.1.18.3.5.16.2.1.1.1.6
Number of guaranteed-service packets that have exited this line
wfTxLineRscGuaranteedBytes .1.3.6.1.4.1.18.3.5.16.2.1.1.1.7
Number of guaranteed-service bytes that have exited this line
wfTxLineRscGuaranteedPolicedPackets .1.3.6.1.4.1.18.3.5.16.2.1.1.1.8
Number of guaranteed-service packets that were policed (dropped)
wfTxLineRscGuaranteedPolicedBytes .1.3.6.1.4.1.18.3.5.16.2.1.1.1.9
Number of guaranteed-service bytes that were policed (dropped)
wfTxLineRscGuaranteedBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.1.1.10
Guaranteed service bandwidth measured over the last bandwidth interval
wfTxLineRscGuaranteedAvgBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.1.1.11
Guaranteed service average bandwidth
wfTxLineRscGuaranteedMaxBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.1.1.12
Guaranteed service maximum bandwidth
wfTxLineRscGuaranteedAvgPacketDelay .1.3.6.1.4.1.18.3.5.16.2.1.1.1.13
Guaranteed service average packet delay
wfTxLineRscGuaranteedMaxPacketDelay .1.3.6.1.4.1.18.3.5.16.2.1.1.1.14
Guaranteed service maximum packet delay
wfTxLineRscUnreservedPolicedPackets .1.3.6.1.4.1.18.3.5.16.2.1.1.1.15
Number of unreserved packets that were policed (dropped). If priority queueing is also enabled, this statistic is not maintained. See wfCctOptsEntry.
wfTxLineRscUnreservedPolicedBytes .1.3.6.1.4.1.18.3.5.16.2.1.1.1.16
Number of unreserved bytes that were policed (dropped). If priority queueing is also enabled, this statistic is not maintained. See wfCctOptsEntry.
wfTxLineRscCfgLineNumber .1.3.6.1.4.1.18.3.5.16.2.1.3.1.2
Line number
wfTxLineRscCfgDelete .1.3.6.1.4.1.18.3.5.16.2.1.3.1.1
Creation and deletion flag for this record
wfTxLineRscCfgEstBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.3.1.3
Estimated usable bandwidth by this router in bits per second.
wfTxLineRscCfgResvBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.3.1.4
Reservable bandwidth on this line.
wfTxLineRscCfgResvTrafficAlgorithm .1.3.6.1.4.1.18.3.5.16.2.1.3.1.5
reserved-traffic queueing algorithm: none - schedule as best-effort priority - schedule ahead of best-effort
wfTxLineRscCfgResvPolicingAlgorithm .1.3.6.1.4.1.18.3.5.16.2.1.3.1.6
reserved-traffic policing algorithm: none - no policing lbucket - leaky bucket policing
wfTxLineRscCfgBandwidthInterval .1.3.6.1.4.1.18.3.5.16.2.1.3.1.7
Interval over which bandwidth is measured, in seconds. Default is ten seconds.
wfTxLineRscCfgInflateReservations .1.3.6.1.4.1.18.3.5.16.2.1.3.1.8
Any reservation made on this line will be inflated by this percentage.
wfTxLineRscCfgUnreservedPolicingAlgorithm .1.3.6.1.4.1.18.3.5.16.2.1.3.1.9
Policing 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.
wfTxLineRscCfgUnreservedQueueLength .1.3.6.1.4.1.18.3.5.16.2.1.3.1.10
If 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.
wfTxLineRscCfgMultiLineSelectAlgorithm .1.3.6.1.4.1.18.3.5.16.2.1.3.1.11
This 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.
wfTxLineRscCfgMultiLineThresholdBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.3.1.12
If the multi-line selection algorithm is threshold, this is the threshold value for this line. It must be less than the reservable bandwidth value.
wfTxLineRscCfgResvLatency .1.3.6.1.4.1.18.3.5.16.2.1.3.1.13
The 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.
wfTxLineRscCfgLargestBandwidth .1.3.6.1.4.1.18.3.5.16.2.1.3.1.14
The maximum bandwidth that a single flow can reserve on this line. [ 0 (zero) implies no maximum.]
wfTxLineRscCfgLargestBuffer .1.3.6.1.4.1.18.3.5.16.2.1.3.1.15
The maximum buffer space that a single flow can reserve on this line. [ 0 (zero) implies no maximum.]
wfFlowspecSt2V3Index .1.3.6.1.4.1.18.3.5.16.3.1.1.1
flowspec index
wfFlowspecSt2V3Version .1.3.6.1.4.1.18.3.5.16.3.1.1.2
Version identifies the version of the FlowSpec. Version 3 is defined here.
wfFlowspecSt2V3DutyFactor .1.3.6.1.4.1.18.3.5.16.3.1.1.3
DutyFactor 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.
wfFlowspecSt2V3ErrorRate .1.3.6.1.4.1.18.3.5.16.3.1.1.4
ErrorRate 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.
wfFlowspecSt2V3Precedence .1.3.6.1.4.1.18.3.5.16.3.1.1.5
Precedence 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.
wfFlowspecSt2V3Reliability .1.3.6.1.4.1.18.3.5.16.3.1.1.6
Reliability 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.
wfFlowspecSt2V3Tradeoffs .1.3.6.1.4.1.18.3.5.16.3.1.1.7
Tradeoffs 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.
wfFlowspecSt2V3RecoveryTimeout .1.3.6.1.4.1.18.3.5.16.3.1.1.8
RecoveryTimeout 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.
wfFlowspecSt2V3LimitOnCost .1.3.6.1.4.1.18.3.5.16.3.1.1.9
LimitOnCost 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.
wfFlowspecSt2V3LimitOnDelay .1.3.6.1.4.1.18.3.5.16.3.1.1.10
LimitOnDelay specifies the maximum end-to-end delay, in milliseconds, that can be tolerated by the origin.
wfFlowspecSt2V3LimitOnPDUBytes .1.3.6.1.4.1.18.3.5.16.3.1.1.11
LimitOnPDUBytes is the smallest packet size, in terms of ST-user data bytes, that can be tolerated by the origin.
wfFlowspecSt2V3LimitOnPDURate .1.3.6.1.4.1.18.3.5.16.3.1.1.12
LimitOnPDURate is the lowest packet rate that can be tolerated by the origin, expressed as tenths of a packet per second.
wfFlowspecSt2V3MinBytesXRate .1.3.6.1.4.1.18.3.5.16.3.1.1.13
MinBytesXRate is the minimum bandwidth that can be tolerated by the origin, expressed as a product of bytes and tenths of a packet per second.
wfFlowspecSt2V3AccdMeanDelay .1.3.6.1.4.1.18.3.5.16.3.1.1.14
AccdMeanDelay 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.
wfFlowspecSt2V3AccdDelayVariance .1.3.6.1.4.1.18.3.5.16.3.1.1.15
AccdDelayVariance 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.
wfFlowspecSt2V3DesPDUBytes .1.3.6.1.4.1.18.3.5.16.3.1.1.16
DesPDUBytes 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.
wfFlowspecSt2V3DesPDURate .1.3.6.1.4.1.18.3.5.16.3.1.1.17
DesPDURate 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.
wfIntSrvIfFlowDestination .1.3.6.1.4.1.18.3.5.16.4.1.1.1
The IP Address used as a destination address for all senders in this flow.
wfIntSrvIfFlowDestinationProtocol .1.3.6.1.4.1.18.3.5.16.4.1.1.2
The value of the IP Protocol field in this flow, typically UDP or TCP.
wfIntSrvIfFlowDestinationPort .1.3.6.1.4.1.18.3.5.16.4.1.1.3
The 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.
wfIntSrvIfFlowSource .1.3.6.1.4.1.18.3.5.16.4.1.1.4
The IP Address used as a source address by this sender in this flow. If zero, all senders are included in the flow.
wfIntSrvIfFlowSourcePort .1.3.6.1.4.1.18.3.5.16.4.1.1.5
The 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.
wfIntSrvIfFlowCct .1.3.6.1.4.1.18.3.5.16.4.1.1.10
The circuit number of this IntSrv interface
wfIntSrvIfFlowRate .1.3.6.1.4.1.18.3.5.16.4.1.1.6
The 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.
wfIntSrvIfFlowWeight .1.3.6.1.4.1.18.3.5.16.4.1.1.7
The 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.
wfIntSrvIfFlowQueue .1.3.6.1.4.1.18.3.5.16.4.1.1.8
The 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.
wfIntSrvIfFlowMin .1.3.6.1.4.1.18.3.5.16.4.1.1.9
The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size.
Table
wfTxLineRscTable .1.3.6.1.4.1.18.3.5.16.2.1.1
This table contains information about line resources and guaranteed service traffic on a per-line basis for outbound traffic.
wfTxLineRscCfgTable .1.3.6.1.4.1.18.3.5.16.2.1.3
This table contains resource reservation configuration information on a per-line basis for outbound traffic.
wfFlowspecSt2V3Table .1.3.6.1.4.1.18.3.5.16.3.1
This 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.
wfIntSrvIfFlowTable .1.3.6.1.4.1.18.3.5.16.4.1
Information describing the reserved flows us- ing the system's interfaces.
Object Identifier
wfReservationsResourcesGroup .1.3.6.1.4.1.18.3.5.16.2
wfTxLineRscGroup .1.3.6.1.4.1.18.3.5.16.2.1
wfReservationsFlowspecGroup .1.3.6.1.4.1.18.3.5.16.3
wfIntSrvIfFlowGroup .1.3.6.1.4.1.18.3.5.16.4