Bug ID 505452: New db variable to control packet priority for TMM generated packets

Last Modified: Jan 16, 2019

Bug Tracker

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 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

Fixed In:
12.0.0, 11.5.2 HF1

Opened: Feb 07, 2015
Severity: 3-Major

Symptoms

For TMM generated packets (such as ICMP request), the existing behavior is TMM would use hard code value 3 for the packet priority.

Impact

No way to control those packets's priority.

Conditions

Packets are generated internally by TMM.

Workaround

None

Fix Information

A new db variable tm.egress.pktpriority is added to set packet priority of TMM generated egress packets. Default 3 with range 0-7.

Behavior Change