flow are enforced.
A customer signs up for a particular SLA which includes: starting date,
starting time, end date, end time, service class (PCBR, PVBR, PMM, PMC,
BE), total bandwidth request. This information is stored in the database
and the administrator allocates him the SLA as per the management or
administrative policies. Currently, no validation on the correctness of SLA
is done in the program. When a flow request comes to the ingress or the
QMA (admission control agent), it contacts BB Server which keeps track of
all the resources in the network. The client is then asked to input the QoS
profile for the input traffic (which is stored as .prf file. There are different
QoS profiles stored as Video.prf, FTP.prf, CBR.prf. These are common QoS
profiles of common applications that run on the network and represent the
kind of QoS that the application expects from the network. There could be
custom application QoS profiles.After the QoS profile, service class (PCBR,
PVBR, PMM, PMC, BE) is entered. This service class for the application
should be same as the SLA agreement of the customer. Then the starting
date, starting time, end date, end time, bandwidth request are entered for the
flow. Then the admission control algorithm as discussed later is executed by
the QMA in co ordination with BB Server.If the result of admission control
is positive, flow is admitted by enforcing configurations on PEPs (ingress
and egress routers).
The configurations enforced include traffic policing,
marking of incoming traffic for particular traffic class and set-up of LSP.
PEP is a Linux DiffServ over MPLS ingress, core or egress router. When the
PEP, first starts or is run, it connects to BB Server and executes the default
initialization configurations which are:
43