QoS Monitoring: RSVP MIB
version 1.0, June 15 1999
Contributors: Zlatica Cekro (Uni. Bruxelles)
The RSVP MIB is standard MIB which is manipulated by applications based on
SNMP (SNMPv1 and SMIv2) and is defined in
RFC 2206.
The RSVP MIB could be used both in "passive" QoS monitoring scenarios
and as an "active" element to simulate congestion.
QoS monitoring scenario
In this scenario the following statistics about behavior of network
elements when using RSVP are of interest:
- RSVP Session Statistics Database:
Displays statistics relating to the number of senders and receivers in
each session from RsvpSessionEntry
(SessionNumber, SessionType, SessionDestAddr Data, SessionProtocol,
SessionPort, SessionSenders, SessionReceivers, SessionRequests...)
-
RSVP Session Sender Database:
statistics are about the potential contribution of senders to session data
content. It consists of a list of the valid PATH messages that the RSVP
Router or Host is receiving (SenderNumber, SenderType, SenderAddr Data,
SenderProtocol, SenderDestPort, SenderPort, SenderFlowId, SenderInterface,
SenderTSpec Data, SenderInterval, SenderRSVPHop, SenderLastChange,
RSenderAdspec Data...)
-
The RSVP Reservation Requests Received Table :
information displayed by receivers and is related to their needs
with respect to sessions and senders.
It is in essence a list of valid RESV messages that the RSVP Router or Host
is receiving (ResvNumber, ResvType, ResvSenderAddr Data,
DestAddr Data, ResvProtocol, ResvDestPort, ResvPort, ResvInterface,
Resv QoS Service, ResvTSpec Data, ResvRSpec Data, ResvInterval,
ResvStatus, ResvTTL...)
Besides the above statistics, traps from RSVP can be tested. For instance:
- The newFlow trap which indicates that the originating system
has installed a new flow in its classifier, or (when reservation
authorization is in view) is prepared to install such a flow in the
classifier and is requesting authorization.
-
The lostFlow trap indicates that the originating system
has removed a flow in its classifier.
IP Performance tests scenario
The RSVP MIB can be used to simulate congestion of one network element
or of a part of the backbone network. This artificial congestion state can
be used to test and analyze the behavior of traffic flows when crossing
"overbooked" network elements.
The ResvStatus object can be used to achieve this.
This object is read-write object and can be in one of the following 6 states:
- Active (1),
- NotInService (2),
- NotReady (3),
- CreateAndGo (4),
- CreateAndWait (5),
- Destroy (6)
The ResvStatus object applies to Session and Flow Entries when
changing the traffic parameters on existing entries or creating new
entries (status 4 and 5), if possible. From that moment on, new values are
"valid" for all active RESV messages or active flows.
This object may be used to install static classifier
information (without refreshing period), delete classifier information
or authorize it.
Different QoS services can be specified:
- BestEffort (1),
- GuaranteedDelay (2),
- ControlledLoad (5).
Software and Hardware Requirements:
- SNMP based application with access to the RSVP capable routers and
RSVP MIB support
through TEN-155 overlay network
to RSVP capable routers with RSVP MIB. Access can be either
IP or IP over ATM based (SVC or PVC).
- Read permission for monitoring and statistics collection
- Both read and write permissions for flows/session creation and
traffic parameters manipulation.