This object controls how a device behaves when
ingress BW conflicts arise. A conflict can arise if
a device only supports the ingress BW access primitive
on a per-port basis, but device is being configured
with profiles that have per-user unique setting.
Applying these profiles to the same port will cause
the conflict to arise because the device cannot
enforce a per-user unique ingress BW setting. This object
specifies two alternatives, as follows:
'non-strict' - Device does not signal errors when
multiple access profiles are applied
to a port. The device will apply
the ingress BW settings specified in the
last profile applied to the port.
'strict' - Device does signal an error when an
attempt to apply an access profile to
a port that already has an active access
profile with a different ingress BW setting.
Device will not activate the access
profile in question after error is
signaled.