We have a production kernel zone Solaris 11.4 that exists on various SAN luns that are replicated to a DR site. In testing the DR failover I suspend replication and present the replicated luns to the DR hardware and attach the zone on the DR side. The DR site obviously is in a different subnet so I configure the zone anet with a different IP as the actual production side however when the server is booted the IP fails to configure because I assume ip-interface-management service is beating the zonecfg to the punch with the following resul
root@:~# ipadm show-addr
ADDROBJ TYPE STATE ADDR
lo0/v4 static ok 127.0.0.1/8
lo0/v6 static ok ::1/128
net0/v4 static disabled 172.17.5.10/24
net0/v6 addrconf disabled ::
her is my zonecfg for anet:
anet 0:
lower-link: aggr1
allowed-address: 172.17.8.10/24
configure-allowed-address: true
defrouter: 172.17.8.1
link-protection: "mac-nospoof, ip-nospoof"
mac-address: random
auto-mac-address: 2:8:20:84:fe:66
vlan-id: 800
id: 0
The workaround solution is to boot the zone, zlogin and remove the net0 IP then reboot again at which time everything comes up properly.
I would have expected the zonecfg to override the existing ip-interface-management service but that is apparently not happening. Is this a bug or does anyone have a suggestion to avoid multiple reboots for this operation?
Thanks