Bug ID 844169: TMSH context-sensitive help for diameter session profile is missing some descriptions

Last Modified: Jan 20, 2023

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1

Fixed In:
16.0.0

Opened: Oct 29, 2019
Severity: 4-Minor

Symptoms

The tmsh context-sensitive help content for the following diameter session attributes is missing: -- respond-unroutable -- retransmission-action -- retransmission-queue-limit-high -- retransmission-queue-limit-low -- retransmission-queue-max-bytes -- retransmission-queue-max-messages

Impact

The specified attributes are no described.

Conditions

When attempting in tmsh to list a diameter session profile followed by a question mark for context-sensitive help- for example: list ltm message-routing diameter profile session <sess-name> ?

Workaround

These are the missing descriptions: -- respond-unroutable: When selected (enabled), messages that do not match any known route will be transformed into an error answer message and sent to the originator of the request. When disabled, unroutable request messages are routed back to the connection where they came from. The default value is disabled. -- retransmission-action: Specifies the action performed when retransmission has been triggered for a request message. The options are: 1) Disabled: Retransmission is disabled. This is the default action. 2) Busy: An answer message is generated with a TOO_BUSY result code and returned to the originator of the request. 3) Unable: An answer message is generated with an UNABLE_TO_DELIVER result code and returned to the originator of the request. 4) Retransmit: The request message will be retransmitted. -- retransmission-queue-limit-high: Specifies the high watermark for the retransmission queue (in percentage). If the retransmission queue exceeds this limit, the transport window will begin closing. A value of 0 will disable closing the transport window. Valid range from 0 to 100. The default value is 90. -- retransmission-queue-limit-low: Specifies the low watermark for the retransmission queue (in percentage). If the retransmission queue drops below this limit, the transport window will reopen. Valid range from 0 to 100. The default value is 60. -- retransmission-queue-max-bytes: Specifies the maximum number of bytes that can be stored in a connections retransmission queue. A value of 0 will disable this limit. The default value is 131072 bytes. -- retransmission-queue-max-messages: Specifies the maximum number of messages that can be stored in a connections retransmission queue. A value of 0 will disable this limit. The default value is 1024 messages.

Fix Information

The missing descriptions have been added to tmsh and now display properly.

Behavior Change