next up previous
Next: Related Work Up: Scenario: Outsourcing of Extranets Previous: Scenario: Outsourcing of Extranets

Management Requirements for Monitoring Quality of Service

 

In order to observe the quality of delivered services it is necessary to negotiate QoS parameters between customer and provider. As mentioned before, it is important that these parameters are meaningful to the customer and reflect its expectations. They are part of Service Level Agreements which essentially are a contractual relationship between a customer and a provider. SLAs are used - among other things - for billing purposes. If a service is not delivered with the quality that was agreed in the SLA the customer may get a discount. Therefore the SLA (and therefore the QoS parameters) have to be supervised by the management system of the provider. Further the provider is obliged by the SLA to report compliance with agreed QoS parameters. Examples for such QoS parameters are the response time, the connectivity or the availability not of a network connection but of a certain service from a customer's point of view. Thus these parameters have to be measured and valued in the customer environment. Most of the QoS parameters (e.g. the connectivity or the availability) of a service are only defined if the customer actually tries to use this certain service. For the monitoring of such parameters it is necessary for the management system of the provider to be able to measure from the side of the customer. In our scenario that means an agent which performs the monitoring of QoS parameters must be installed at a dealer's host. Thus the agent has to cross the organizational boundary between the customer and the provider. The customer will allow the provider to do so only if high security requirements are met. Additionally a customer will only accept such a solution if no additional or only minimal costs are caused. This especially causes problems for customers which are connected via dial-up lines, because the initiation of a connection solely for management purposes cannot be tolerated in this case. Furthermore it means the agent has to do its measures locally as far as possible and transfered results should be as small as possible. As requirements for services, QoS parameters and SLAs could change in course of time the architecture has to be flexible and must be able to react on such changes quickly. In large-scale corporate networks as described in the scenario, well-scaling management systems are absolutely necessary. In addition, a lot of different hardware and software at the customer side, requires a high degree of platform independence for the corresponding agent.



next up previous
Next: Related Work Up: Scenario: Outsourcing of Extranets Previous: Scenario: Outsourcing of Extranets
Copyright Munich Network Management Team