Adding New BigIP Units Using Free CPUs on i7800 (LB13 & LB14) to an existing HA Pair
Hello, We have a pair of i7800 devices, each running two guests with the following configuration: i7800 Unit 1: LB09 & LB11 i7800 Unit 2: LB10 & LB12 Current Setup: LB09 & LB10: These are part of a High Availability (HA) pair, running in an Active/Active configuration. LB11 & LB12: Similarly, these two guests are also in an HA pair, running in Active/Active mode. Each LBx unit is utilizing 6 CPUs (which is the maximum allowed per guest). The i7800 comes with 14 CPUs total, so there are 2 unused CPUs per unit (not allocated to any guest). Questions: Can we bring up new BigIP units (LB13 & LB14) using the 2 free CPUs on each i7800 unit? Can these new units join the existing HA pair of LB11 & LB12 and sync configuration to each other? Can the new Units serve their own traffic groups ( as shown below in the diagram ) ? Is there any potential limitation or issue with utilizing the remaining CPUs for this purpose? Will i7800 run out of memory or go low in memory ? Goal: Offload 20% of the traffic (a handful of VIPs) to the newly created LB13 & LB14 units. All LBxx ( 11,12,13 & 14 ) should back each other up and sync configuration across Thank you for any assistance
Restore from UCS archive to existing BIG-IP system in a redundant pair.
Hi, We have a pair of BIG-IP devices for redundancy. I've backed up our BIG-IP configuration to a UCS archive, and now plan to do some work on the system, one BIG-IP device at a time. The backup is in case this does not go to plan. I see K8086 for "Replacing a BIG-IP system in a redundant pair without interrupting service", but I am not replacing either device, I'm keeping both and possibly using the UCS archive to restore the device to a good configuration of itself if there are problems. Is there any knowledgebase for this, or is K8086 the closest thing, and if so, which steps are not required? Version is BIG-IP 11.5.4. Thanks
HA Connection lost after change Management IP address
Hi guy, I have a problem after change mgmt IP. It's HA connection lost (result in IP conflict and downtime) I have to change management IP address of BIG-IP redundant pair. But when we change it, HA connection lost and it's become active/active which cause us a downtime of application. I have configsync and failover unicast IP is 2.2.2.2 (peer is 2.2.2.1) which connect directly with each other. How can this occur? Is really changing mgmt IP of the box cause it HA connection lost? Note. In v. 10.2.4 , we can change it just fine. Now we currently Running v.11.4.1 HF5
High-availability configuration produces a status of "ONLINE (STANDBY), In Sync"
Problem: High-availability configuration produces a status of "ONLINE (STANDBY), In Sync" on the F5 primary and standby units. Models: F5 1600 Big-IP Version: BIG-IP 11.5.0 Build 7.0.265 Hotfix HF7 Steps used to configure high-availability: Connect a network cable on port 1.3 of each F5 1600 Create a dedicated VLAN for high-availability on each F5 1600 Configure an IP address for the high-availability VLAN on each F5 1600 Ensure that both F5 1600 units can ping each other from the high-availability VLAN On each F5 1600, navigate to "Device Management" -> "Devices" -> "Device List". Select the F5 1600 system labelled as "self" On each F5 1600, navigate to "Device Connectivity" -> "ConfigSync". Select the IP address assigned to the high-availability VLAN On each F5 1600, navigate to "Device Connectivity" -> "Network Failover". Add the IP address assigned to the high-availability VLAN to the failover unicast configuration Force the standby unit offline On the active unit, navigate to "Device" -> "Peer List". Click "Add", and add standby unit to the high-availability configuration At this point, the primary F5 unit has a status of "ONLINE (ACTIVE), In Sync", and the standby unit has a status of "FORCED (OFFLINE), In Sync" On the primary unit, navigate to "Device Management" -> "Device Groups" to create a device group At this point, both units have a status of "ONLINE (STANDBY), In Sync". Any ideas as to why this happening? My goal is to have high-availability configured in an ACTIVE/STANDBY pair.
