hardware asset management

A less-than best-effort hardware asset management was introduced, and a strategy for using this class for DoS and worm mitigation was presented. Specifically, flows can be monitored at the campus Access-Edge, and out-of-profile flows can be marked down to the Scavenger marking (of DSCP CS1). To complement these policers, queues providing a less-than best-effort Scavenger service during periods of congestion are deployed in the LAN, WAN, and VPN

Only after traffic is positively identified can policies be applied to it. Therefore, best-practice design recommendations are to identify and mark traffic (with DSCP values) as close to the source of the traffic as possible, typically in the wiring closet or within the trusted devices (such as IP phones) themselves. If markings and trusts are set correctly, the intermediate hops do not have to repeat the same in-depth classification. Instead, they can administer QoS policies (such as scheduling) based on the previously set markings, which appear close to the beginning of the hardware asset management