Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP MA-VE
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: Oct 14, 2015 Severity: 3-Major
Autoscaling of BIG-IP VE has been designed to work with single NIC and single IP address as it works in tandem with AWS Elastic Load Balancer(ELB). Attaching multiple private-ip to eth0 breaks auto-scaling of BIG-IP VE.
Auto-scaling of BIG-IP VE fails.
1. Create an AWS autoscale group and attach multiple private IP addresses to the instance that is started. 2. Configure autoscale on BIG-IP (add all the required configs via tmsh, GUI, iApp, iCall, etc).
Remove the secondary private-ip from the interface in AWS and keep the instance with a single NIC and single IP address.
None