|
Beyond its engineering influence, the overall network inventory freeware of the QoS Baseline is to unify QoS within Cisco: from service provider to enterprise, from engineering to marketing. For example, the concept of traffic classification inevitably begs the question of how many classes of traffic there should be. MQC supports up to 256 different traffic classes within a policy map. Although adept QoS administrators might see this as desirable, those who are new to QoS and have no idea how many classes of traffic they need in their networks might view it as daunting
To address the needs of the both expert and casual QoS users, the QoS Baseline defines a set of class template recommendations that can be either be implemented "as is" or customized to individual needs. It gives a starting point for network design and implementation, and it provides a basis for comparable product testing and performance reportingboth of which significantly simplify the implementation of network inventory freeware
|