A profile is a sub-section of QoS configuration. It contains the second stage of classification and some queuing configuration.
Once we have defined a class — that is, we have identified a sub-stream of traffic — we must associate a profile with each class, to define how the system should process the packets in that sub-stream. Profiles contain a sub-section of QoS configuration that we can reuse multiple times.
profile map— second stage of classification
We name profiles, and we can create them as either local or global profiles. We can reuse a global profile across many QoS policies. We can reuse a local profile only within the QoS policy in which we defined it.
We can use the same local profile name, but with different profile configurations, in multiple policies.
A profile contains the third stage of classification and some of the queuing configuration.