Bug ID 494258: TMSH setting certain values for 'ip-protocol' has incorrect behavior

Last Modified: Jan 29, 2019

Bug Tracker

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

Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Opened: Dec 03, 2014
Severity: 4-Minor

Symptoms

Using TMSH to set certain values for 'ip-protocol' does not set the expected value. For example, setting 'ip-protocol' value to 'any', 'ip', 'hopopt', the value for 'ip-protocol' may be set incorrectly. This occurs because TMSH cannot determine the exact mapping because of the one-to-many relationship (for example: 0 maps to 'any', to 'ip', and to 'hopopt').

Impact

The system does not set the expected value. For example, if you specify 'ipv6-auth', tmsh lists it as 'ah'. Specifying 'ipv6-crypt' results in 'esp'. Specifying 'esp' results in 'ipv6-crypt'. Specifying 'ah' results in 'ipv6-auth'. Specifying 'hopopt' results in 'any'. Specifying 'ip' results in 'any'.

Conditions

TMSH commands for setting 'ip-protocol'.

Workaround

None.

Fix Information

None

Behavior Change