Provision zones on different network than OC

Question

I have Ops Center on network 10.250.10 and server1 on network 10.250.20. I want to create a guest zone on server1. When I get to the network options, I can choose exclusive or shared IP. Shared IP only lets me select bge0 with network 10.250.10. I want to use 10.250.20. I can create the zone with an IP on 10.250.10, but the job fails because when OC tries to boot the zone, the zone OS can't find the DNS servers etc. I can manually change the IP of the zone (in /etc/zones/zone1.xml on the global zone) and reboot it, and everything seems fine. Obviously I'd like to avoid that step.
I must be missing something simple... how do I tell OC that it can provision zones with an IP on networks besides 10.250.10?
Thanks!

Answer 1

Look at the "Managed Networks" feature: you can define a 10.250.20.x/24 network in Ops Center, and apply it to server1. When you add that new network you'll be asked what interface (i.e. bge1) you want it associated with. Once Ops Center knows about the 20 network, you can use it for things like zone/containers. (if you provisioned server1 with Ops Center this should have been done for you automatically, but there's some bugs in multi-NIC OS provisioning).
That's assuming you have distinct 10.250.10.x/24 and 10.250.20.x/24 networks... and you're not just using 10.250.x.x/16. It could be as simple as a subnet issue, where Ops Center thinks server1 is using 255.255.255.0 (10.250.10.x, so 20.x isn't valid) instead of 255.255.0.0 (where both 10.x and 20.x are valid IP ranges).
Regards,
[email protected]