Cisco SCE官方培训教材之五流量管理和其它增值服务.ppt

“Best Practices” SessionBandwidth Control Under Strict NDA Elements of this presentation are under strict NDA and should be considered confidential and proprietary External distribution of this presentation should be consulted with scp-pm@ Questions regarding features or timelines should be directed to ask-service-control@ Agenda Agenda Cisco SCE bandwidth management:Bottom-up overview Cisco SCE supports a bandwidth management scheme based on policers Consists of 2 components Data plane: Per flow policers Control plane: Hierarchy of bw allocation constraints which dynamically tune the parameters of the per flow policers Priority can be defined between controllers of the same level The arrows show the control hierarchy, not packet flow Bandwidth Controller The bandwidth controller (BWC), – a.k.a. internal BWC – is an entity that manages a set of flow controllers based on 3 configurable value. It seeks for fair BW distribution across the flows’ it controls. Each BWC has 3 configurable parameters PIR = maximum enforced rate for sum of associated flow controllers CIR = minimum assured rate for sum of associated flow controllers AL = Assurance level Primary Bandwidth Controller The primary bandwidth controller is an entity that manages a set of BWCs e.g. the primary BWC could represent all traffic to a subscriber Each Primary BWC has 3 configurable parameters similarly to the BWC Global Controller The global bandwidth controller (GC) provides an additional aggregate constraint which can be applied to BWCs independently of the primary BWCs Each GC has a single configurable parameter – its maximum rate The number of GCs supported varies by platform SE 1010 = 16 GCs SE 2020 = 64 GCs Global Controller (cont’) GCs can be applied in two ways to enforce an aggregate rate across a group of subscribers, by associating all of the constituent subscribers’ BWCs with that particular GC i.e. analogous to a VP as shown Global Controller (cont’) 2. To apply an a