Figure 17: Schedulers On Sap Or Multi-Service Site Receive Bandwidth From Port Priority Levels - Alcatel-Lucent 7450 ESS OS Quality Of Service Manual

Hide thumbs Also See for 7450 ESS OS:
Table of Contents

Advertisement

Due to the nature of the two scheduler policy, bandwidth is allocated on a per-service or per-
subscriber basis as opposed to a per-class basis. A common use of the two policy model is for a
carrier-of-carriers mode of business. In essence, the goal of a carrier is to provide segments of
bandwidth to providers who purchase that bandwidth as services. While the carrier does not
concern itself with the interior services of the provider, it does however care how congestion
affects the bandwidth allocation to each provider's service. As an added benefit, the two policy
approach provides the carrier with the ability to preferentially allocate bandwidth within a service
or subscriber context through the service or subscriber level policy without affecting the overall
bandwidth allocation to each service or subscriber.
allocation using the two scheduler policy model. While the figure shows services grouped by
scheduling priority, it is expected that many service models will place the services in a common
port priority and use weights to provide a weighted distribution between the service instances.
Higher weights provide for relatively higher amounts of bandwidth.

Figure 17: Schedulers on SAP or Multi-Service Site Receive Bandwidth From Port Priority Levels

7450 ESS OS Quality of Service Guide
SAP or MSS
SAP or MSS
SAP or MSS
SAP or MSS
SAP or MSS
SAP or MSS
QoS Scheduler Policies
Figure 17
shows a per-service bandwidth
Priority 1
Weighted
Rate Limiting
Scheduler
Priority 2
Port
Weighted
Strict Rate
Rate Limiting
Limiting
Scheduler
Scheduler
Priority n
Weighted
Rate Limiting
Scheduler
Port
OSSG132
Page 461

Advertisement

Table of Contents
loading

Table of Contents