Last Modified: May 29, 2024
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
17.1.1, 17.1.1.1
Fixed In:
17.1.1.2
Opened: Dec 08, 2023 Severity: 1-Blocking Related Article:
K000138191
- TMM does not fully come up on secondary slots leaving all but one slot non-operational. Following is an example: [root@rd1:/S1-green-P::Active:Standalone] config # tmsh show sys cluster ----------------------------------------- Sys::Cluster: default ----------------------------------------- Address <IP address/subnet> Alt-Address :: Availability available State enabled Reason Cluster Enabled Primary Slot ID 1 Primary Selection Time 12/08/23 12:16:33 --------------------------------------------------------------------------------------------------------- | Sys::Cluster Members | ID Address Alt-Address Availability State Licensed HA Clustered Reason --------------------------------------------------------------------------------------------------------- | 1 :: :: available enabled true active running Run | 2 :: :: unavailable enabled false active running TMM not ready 2. The following messages will be seen on secondary slots /var/log/tmm logs file: notice SEP: Can't find SEP mapping for slot:2 port:0mac:02:01:23:45:02:00 notice SEP: Can't find SEP mapping for slot:2 port:0mac:02:01:23:45:02:00 notice SEP: Can't find SEP mapping for slot:2 port:0mac:02:01:23:45:02:00 notice SEP: Can't find SEP mapping for slot:2 port:0mac:02:01:23:45:02:00 3. On tenant run: guishell -c "select name,module_id,physport from interface" If physport for 1/0.1 is showing 0, it's another indication of the bug. Note: This issue can also occur on a single-bladed tenant, but there are no "Can't find SEP mapping" errors in tmm log, and "show sys cluster" does not show any problem on a single-bladed tenants. The guishell command is the only clear symptom that can be observed. Other symptoms of this issue include: - /var/log/ltm contains 'inet port exhaustion' logs for non-floating SelfIP addresses. - The HA channel is disconnected. - The failover channel over the HA VLAN does not work. - Health checks are down or flapping. - A BIG-IP tenant was working fine, but after a reboot, it stopped working. - A BIG-IP tenant was broken, so you restart it, and now the tenant works, but a different tenant is now broken. - You can ping some things but not other things. This issue may not be triggered immediately after the upgrade. Although it is encountered more rarely, this issue could also be triggered on rSeries devices.
TMM does not fully start on secondary slots, leaving those slots as part of the cluster and unable to process traffic.
BIG-IP tenant running v17.1.1 running on VELOS.
None
None