Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Opened: Jun 14, 2016 Severity: 3-Major Related Article:
K04460423
Upgrade from 10.x to 12.0.0 and later can fail if 'nat-stun-port' service name is specified in the configuration.
This causes the configuration to fail loading after upgrade. Because of the change in the service name, this is expected behavior when upgrading configurations pool member (or other configuration object) is mapped to the service number.
This occurs when a pool member (or other configuration object) is mapped to 'nat-stun-port' service name (a configuration similar to the following): bigip.conf: pool test { members 10.10.153.3:nat-stun-port {} } This causes the ports within the configuration to be saved by their names. Saving the port by a name can lead to issues during configuration roll-forward to later releases as the port names can potentially change. In this case, in response to RFC5389 (https://tools.ietf.org/html/rfc5389), the 'nat-stun-port' identifier changed to 'stun' in 12.0.0 /etc/services.
Modify the existing configuration to change 'nat-stun-port' to a specific number. 3478 is the specified 'stun' port number. You can globally configure the BIG-IP system to not translate service ports to service names when storing configuration objects in the bigip.conf file using the following command: tmsh modify cli global-settings service number.
None