Last Modified: Dec 01, 2025
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3
Opened: Nov 26, 2025 Severity: 2-Critical
1. Cannot login to tenant via SSH 2. After login to tenant console device is in INOPERATIVE state. 3. Clusterd errors in /var/log/ltm: slot1/tenant1 warning clusterd[6682]: 013a0026:4: Chassis specific config file '/shared/db/cluster.conf.chs<SN>' too many hard links--ignoring. slot1/tenant1 info clusterd[6682]: 013a0007:6: Missing config file /shared/db/cluster.conf using /shared/db/cluster.conf.chs<SN> slot1/tenant1 err clusterd[6682]: 013a0004:3: Error loading cluster configuration '/shared/db/cluster.conf': ClusterCfg.cpp, line 268, Invalid slot number, not in range 1-8: 9 using default configuration slot1/tenant1 err clusterd[6682]: 013a0027:3: Chassis has 9 slots, config file has 0, ignoring config file
BIG-IP does not start correctly and does not pass traffic, no access via ssh
All of the following: 1. BIG-IP tenant was upgraded to from 17.1.x to 17.5.x 2. BIG-IP tenant expanded to more than 8 blades 3. Rollback to 17.1 was performed (without reducing allocated blades to max 8)
- Remove extra blades (modify tenant to use max 8 blades) in F5OS partition - Switch tenant to "Configured" then "Deployed"
None