Hi,
strict-high priority has precedence over all other priorities even when out of profile, always serviced first.
'transmit-rate exact' cannot be configured for strict-high priority, i.e strict-high can be out-of-profile and still has priority over all other schedulers.
[edit class-of-service schedulers test1] 'transmit-rate' cos_config_scheduler_attributes: cannot configure transmit rate exact and priority strict-high at the same time.
Cheers,
Ashvin