Apologies for responding to my own post, but I need to clarify something I said:

Jeff Victor wrote:
Hi Phil,

Advice below...

Phil Freund wrote:
...
Here's where I need advice:

Each of the failover-capable zones must have the same name on each hardware node which in turn implies that they must use the same IP address, at least when being setup initially. Once the zones are setup, is there any reason the individual zone configurations cannot be modified such that each of the zones has a different IP maintenance address on each hardware node? There would be both a DNS entry for the failover zone name that matches a virtual address managed by VCS and maintenance names for the zone addresses on each target node to provide network accessability for testing after patching/upgrades. (Rather like the maintenance addresses in an IPMP configuration.) If this is true, are the only places that would need the changes implemented the zone xml file and the entries in the zones /etc/hosts (and hostname.xxx) files?

Advice?

There is no reason that you cannot (or should not) add a second IP addr to each zone, as you describe. This IP addr would be 'static' i.e. it would not move around during failover (or any other operation). It can be on the same NIC as the virtual address or another NIC - although IPMP restrictions might limit your choices, it's been awhile since I've used IPMP.

I would do this with zonecfg, either when the zone is being created or afterward. If you can do that, the zones framework will take care of the rest.

I seem to recall that Symantec's zone-creation process requires manual editing of the zone xml file, which is unfortunate as it puts you in shaky Solaris-support territory. We have discussed this with them, and understand that there isn't a good alternative. If manual editing is required, it sounds like you know what you're doing - the xml file, /etc/inet/hosts and hostname.xxx files will need 'help.'

But since the "maintenance names" and addresses would not be managed by VCS, there is no need to manually edit those files. Use zonecfg as it was intended and it will manage the files appropriately.


--
--------------------------------------------------------------------------
Jeff VICTOR              Sun Microsystems            jeff.victor @ sun.com
OS Ambassador            Sr. Technical Specialist
Solaris 10 Zones FAQ:    http://www.opensolaris.org/os/community/zones/faq
--------------------------------------------------------------------------
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to