Bug ID 464271: Error returned while creating 8 HW QoS feature traffic mapping.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: May 26, 2014
Severity: 4-Minor

Symptoms

Traffic-priority objects referenced when creating a (802.1p/DSCP) traffic mapping object must already have been created prior to using the create map-8021p/map-dscp command.

Impact

Referencing an undefined traffic-priority object during a traffic mapping create command will fail, and indicate the undefined traffic-priority object as reason for the failure.

Conditions

Create a map-8021p/map-dscp traffic mapping object without predefined traffic-priority objects.

Workaround

Follow the steps required for configuring 8 HW QoS mappings: - Create a user defined traffic-priority object with a default weight value and assign this as the global-settings default-traffic-priority. - Create additional traffic-priority objects with custom user weights. - Create 802.1p/DSCP traffic mapping objects associated with existing traffic-priority objects. - Assign and enable traffic mappings in global-settings for defining global QoS behavior.

Fix Information

None

Behavior Change