INT-SERV-GUARANTEED-MIB

All MIBs › INT-SERV-GUARANTEED-MIB

Organization: IETF Integrated Services Working Group

Last Updated: 1995-11-03

Category: Quality of Service, Standard: IETF, Technology: QoS

Description: IETF Integrated Services guaranteed service MIB (RFC 2214) defining objects for QoS guaranteed bandwidth reservation per flow.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock 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.

What Is INT-SERV-GUARANTEED-MIB?

INT-SERV-GUARANTEED-MIB is an IETF standards-based MIB (RFC 2214) defining managed objects for the Guaranteed Service class of the Integrated Services (IntServ) architecture, used to reserve a specific bandwidth and bounded delay for a traffic flow across a network path. As implemented here, the module surfaces its notifications, conformance, and compliance groups rather than a rich object list in this batch, reflecting that its data objects (per-flow guaranteed bandwidth, delay bound, and token bucket parameters) are typically defined per the RFC and referenced through the conformance/compliance structure. Its monitoring relevance is configuration/software status of QoS reservations: where fully implemented, it would let an administrator verify a guaranteed-service flow's reserved bandwidth and delay bound are correctly provisioned along a path, and receive notifications if a reservation fails or is torn down. It explicitly depends on the broader IETF Integrated Services architecture and the INTEGRATED-SERVICES-MIB (RFC 2213) framework that defines the general per-flow object structure this module extends. It is deployed on routers implementing IntServ/RSVP-based QoS reservations, historically used in networks requiring strict bandwidth and latency guarantees for real-time traffic, as defined in the INT-SERV-GUARANTEED-MIB RFC (RFC 2214).

IPNetwork Monitor allows you to monitor SNMP objects defined in INT-SERV-GUARANTEED-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.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
IntServ/RSVP-capable router

Monitoring Examples

This batch's sample_objects are limited to the module's Notifications, Conformance, Groups, and Compliances registration nodes (intSrvGuaranteedNotifications, intSrvGuaranteedConformance, intSrvGuaranteedGroups, intSrvGuaranteedCompliances) rather than runtime data tables, so a concrete polling scenario using real leaf objects cannot be constructed from what's given. In a full deployment, an admin would instead consult the RFC 2214-defined guaranteed-service parameter objects (bandwidth, delay bound, token bucket rate) under intSrvGuaranteedObjects to confirm a reserved flow's QoS parameters match what was requested via RSVP signaling.

Imported Objects

From IF-MIB

ifIndex

OBJECT-TYPE

From INT-SERV-MIB

intSrv

MODULE-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
intSrvGuaranteed	1.3.6.1.2.1.52.4			The MIB module to describe the Guaranteed Service of the Integrated Services Protocol
intSrvGuaranteedObjects	1.3.6.1.2.1.52.4.1
intSrvGuaranteedIfTable	1.3.6.1.2.1.52.4.1.1		not-accessible	The attributes of the system's interfaces ex- ported by the Guaranteed Service.
intSrvGuaranteedIfEntry	1.3.6.1.2.1.52.4.1.1.1		not-accessible	The reservable attributes of a given inter- face.
INT intSrvGuaranteedIfC	1.3.6.1.2.1.52.4.1.1.1.1	INTEGER	read-create	The parameter C is the data backlog resulting from the vagaries of how a specific implementa- tion deviates from a strict bit-by-bit service. So, for instance, for packetized weighted fair queueing, C is set to the Maximum Packet Size. The error term C is measured in units of bytes. An individual element can advertise a C value between 1 and 228 (a little over 250 mega- bytes) and the total added over all elements can range as high as (232)-1. Should the sum of the different elements delay exceed (232)-1, the end-to-end error term should be (232)-1.
INT intSrvGuaranteedIfD	1.3.6.1.2.1.52.4.1.1.1.2	INTEGER	read-create	The parameter D at each service element should be set to the maximum packet transfer delay (independent of bucket size) through the ser- vice element. For instance, in a simple router, one might compute the worst case amount of time it make take for a datagram to get through the input interface to the processor, and how long it would take to get from the pro- cessor to the outbound interface (assuming the queueing schemes work correctly). For an Eth- ernet, it might represent the worst case delay if the maximum number of collisions is experi- enced. The error term D is measured in units of one microsecond. An individual element can adver- tise a delay value between 1 and 228 (some- what over two minutes) and the total delay ad- ded all elements can range as high as (232)- 1. Should the sum of the different elements delay exceed (232)-1, the end-to-end delay should be (232)-1.
INT intSrvGuaranteedIfSlack	1.3.6.1.2.1.52.4.1.1.1.3	INTEGER	read-create	If a network element uses a certain amount of slack, Si, to reduce the amount of resources that it has reserved for a particular flow, i, the value Si should be stored at the network element. Subsequently, if reservation re- freshes are received for flow i, the network element must use the same slack Si without any further computation. This guarantees consisten- cy in the reservation process. As an example for the use of the slack term, consider the case where the required end-to-end delay, Dreq, is larger than the maximum delay of the fluid flow system. The latter is ob- tained by setting R=r in the fluid delay formu- la, and is given by b/r + Ctot/r + Dtot. In this case the slack term is S = Dreq - (b/r + Ctot/r + Dtot). The slack term may be used by the network ele- ments to adjust their local reservations, so that they can admit flows that would otherwise have been rejected. A service element at an in- termediate network element that can internally differentiate between delay and rate guarantees can now take advantage of this information to lower the amount of resources allocated to this flow. For example, by taking an amount of slack s <= S, an RCSD scheduler [5] can increase the local delay bound, d, assigned to the flow, to d+s. Given an RSpec, (Rin, Sin), it would do so by setting Rout = Rin and Sout = Sin - s. Similarly, a network element using a WFQ scheduler can decrease its local reservation from Rin to Rout by using some of the slack in the RSpec. This can be accomplished by using the transformation rules given in the previous section, that ensure that the reduced reserva- tion level will not increase the overall end- to-end delay.
ROW intSrvGuaranteedIfStatus	1.3.6.1.2.1.52.4.1.1.1.4	RowStatus	read-create	'valid' on interfaces that are configured for the Guaranteed Service.
intSrvGuaranteedNotifications	1.3.6.1.2.1.52.4.2
intSrvGuaranteedConformance	1.3.6.1.2.1.52.4.3
intSrvGuaranteedGroups	1.3.6.1.2.1.52.4.3.1
intSrvGuaranteedIfAttribGroup	1.3.6.1.2.1.52.4.3.1.2			These objects are required for Systems sup- porting the Guaranteed Service of the Integrat- ed Services Architecture.
intSrvGuaranteedCompliances	1.3.6.1.2.1.52.4.3.2
intSrvGuaranteedCompliance	1.3.6.1.2.1.52.4.3.2.1			The compliance statement

RFC description

Manages Guaranteed Service parameters and interface attributes for Integrated Services (IntServ) QoS.

Start monitoring Vendor-neutral IETF standard (IntServ/RSVP-capable router) 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 INT-SERV-GUARANTEED-MIB

What Is INT-SERV-GUARANTEED-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description