Forum Discussion
Enable IPv6 management access with persistent configuration
Hi F5 Team,
I'm trying to configure a BIG-IP VE (version>=14.0) template on vSphere to clone into new ADCs dynamically with Ansible or Terraform.
Before create a template I must enable IPv4/IPv6 or full-IPv6 on the network adapters of the VE, precisely for management in the first place.
When I change the interface's configuration (/etc/sysconfig/network-scripts/ifcfg-mgmt), every time when I reboot the template or create new ones (also a new boot), the VE retrieves its default configuration without my adaptations. Here is the change that I've been doing into the /etc/sysconfig/network-scripts/ifcfg-mgmt:
# /etc/sysconfig/network
DEVICE=mgmt
TYPE=Bridge
BOOTPROTO=static
USERCTL=no
NM_CONTROLLED=no
NETWORKING=yes
NETWORKING_IPV6=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
ONBOOT=yes
After saving that, I'm also doing:
- tmsh modify /sys db ipv6.enabled value true
- Setting /var/run/config/sshd_config AddressFamily any
Note that VMware vApp of that template has:
- Deployment allocation: static - manual IPv6
- Creation: IP protocol IPv4, IPv6
Using Ansible vmware_guest module or Terraform vSphere provider to create a new instance with MGMT IPv6 address, the VM doesn't take the IP address that I'm trying to give. At each attempt, the /etc/sysconfig/network-scripts/ifcfg-mgmt initial configuration comes back with these default values:
DEVICE=mgmt
TYPE=Bridge
DELAY=0
STP=off
BOOTPROTO=dhcp
DHCPV6C=yes
ONBOOT=yes
NOZEROCONF=yes
Any tips. Could you please help me? Thank you in advance. B regards.
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