Forum Discussion
Not able to attach second network interface to BIGIQ AMI in AWS
Hi,
i am trying to setup bigiq for my organization with 2 network interface required through aws template scripts. I could see additional eni attached and shown in aws console, however i am not able to see the eth1 on BIGIQ ami. The script output keep on going and give this output. I tried disabling the single interface provisioning as well by running below commands and rebooting the host, however it triggers the autoheal and gives new instance. Please suggest how i can make bigiq appliance detect additional interface.
tmsh modify sys db provision.1nic value "disable" tmsh modify sys db provision.1nicautoconfig value "disable" tmsh save sys config
Restarting network for RHEL6 Restarting network interfaces via "service network restart" is not supported on BIGIP platforms. Please use 'tmsh' or 'config' to configure network interfaces. Interface eni-9hghgh0a7 is in-use but eth1 is not available. Waiting...
- AdityaVyas_3582
Nimbostratus
Keep getting this error while eni is not attached
/home/admin/eni_attach_interfaces start Found Metadata i-0ghghghgddf1d874f0 ap-southeast-2a ap-southeast-2 Found interface eni eni-9hghgh0a7 started 32702 Waiting for 32702 Attaching eni-9hghgh0a7 Found eni-9hghgh0a7 is available or already attached to us Interface eni-9hghgh0a7 is ready for attaching. { "AttachmentId": "eni-attach-65268988" }
Added Redhat specific config Restarting network for RHEL6 Restarting network interfaces via "service network restart" is not supported on BIGIP platforms. Please use 'tmsh' or 'config' to configure network interfaces. Interface eni-9hghgh0a7 is in-use but eth1 is not available. Waiting...
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com