12-03-2010 09:53 AM
Hi Guys,
I was planning to migrate the cluster from 5.0MP3RP2 to the latest 5.1SP1 , I was comapring the configuration details , specially I was loooking for the Solaris Zone configurations through VCS (mainly the types.cf is different from both verisons)
I do have a number DB's/Apps running on Solaris Zones ,and I have all zone configuration done through the VCS (FS mounts ,IP's DB agents ,etc) , I pasted below a glimpse of what I have been doing in VCS 5.0.
Db2udb DB2IGCP1_DB (
Critical = 0
DB2InstOwner = db2abcd
DB2InstHome = "/home/db2abcd"
ContainerName = abcdzone1
IPMultiNIC DB2_IP_bge0_nxge3 (
Critical = 0
Address = "10.5.1.10"
NetMask = "255.255.255.0"
Options = trailers
MultiNICResName = MultiNicA_bge0_nxge3
ContainerName = abcdzone1
Mount db2_fs01_mnt (
Critical = 0
MountPoint = "/zones/abcdzone1/root/db2/fs01"
BlockDevice = "/dev/vx/dsk/dg_db2abcdzone1/db2_fs01_mnt"
FSType = vxfs
MountOpt = "rw,largefiles,suid"
FsckOpt = "-n"
)
This is the way I configure the IP's,DB agents and mounts for zone through my VCS config...This is way we can just keep a simple zone config on all nodes , all required parameters can be configured through the VCS.
However I dont see the similar options in my 5.1SP VCS , I know its all depends on the type.cf , does any one got a clue how can I achive my previuos configurations to 5.1SP1 , is another way to do the same kind of configuration in 5.1SP1.(I know I can do the mount part)
Any help on this would be highly appriciated
Cheers ...
Solved! Go to Solution.
12-03-2010 08:46 PM
Hi,
I had a look at VCS Bundled agents guide for 5.1 & here is what I find:
For IPMultiNIC agent:
IPMultiNIC agent
The IPMultiNIC agent manages the virtual IP address that is configured as an
alias on one interface of a MultiNICA resource. If the interface faults, the agent
works with the MultiNICA resource to fail over to a backup NIC. If multiple
service groups have IPMultiNICs associated with the same MultiNICA resource,
only one group has the MultiNICA resource. The other groups have Proxy
resources pointing to it. You can use this agent for IP addresses on multipleadapter
systems.
The IPMultiNIC and MultiNICA agents supports IPv4 and IPv6.
The ContainerName and ContainerType attributes are deprecated.
This agent is zone-aware. The ContainerOpts resource type attribute for this
type has a default value of 0 for RunInContainer and a default value of 1 for
PassCInfo. Symantec recommends that you do not change these values. Refer to
the Storage Foundation High Availability Virtualization Guide for more
information.
Mount agent
The Mount agent brings online, takes offline, and monitors a file system or an
NFS client mount point. You can use the agent to make file systems or NFS client
mount points highly available or to monitor them. This agent also supports high
availability fire drills.
The ContainerName and ContainerType attributes are deprecated.
This agent is zone-aware. The ContainerOpts resource type attribute for this
type has a default value of 0 for RunInContainer and a default value of 0 for
PassCInfo.
So what I understand is VCS bundled agents are already zone aware.... how ever any custom agent like Db2udb (not sure who is developer of this agent) needs to take care of container attribute .. & I am assuming this agent would have its own types.cf which will take care of that..
Hope this answers your query..
Gaurav
12-03-2010 08:46 PM
Hi,
I had a look at VCS Bundled agents guide for 5.1 & here is what I find:
For IPMultiNIC agent:
IPMultiNIC agent
The IPMultiNIC agent manages the virtual IP address that is configured as an
alias on one interface of a MultiNICA resource. If the interface faults, the agent
works with the MultiNICA resource to fail over to a backup NIC. If multiple
service groups have IPMultiNICs associated with the same MultiNICA resource,
only one group has the MultiNICA resource. The other groups have Proxy
resources pointing to it. You can use this agent for IP addresses on multipleadapter
systems.
The IPMultiNIC and MultiNICA agents supports IPv4 and IPv6.
The ContainerName and ContainerType attributes are deprecated.
This agent is zone-aware. The ContainerOpts resource type attribute for this
type has a default value of 0 for RunInContainer and a default value of 1 for
PassCInfo. Symantec recommends that you do not change these values. Refer to
the Storage Foundation High Availability Virtualization Guide for more
information.
Mount agent
The Mount agent brings online, takes offline, and monitors a file system or an
NFS client mount point. You can use the agent to make file systems or NFS client
mount points highly available or to monitor them. This agent also supports high
availability fire drills.
The ContainerName and ContainerType attributes are deprecated.
This agent is zone-aware. The ContainerOpts resource type attribute for this
type has a default value of 0 for RunInContainer and a default value of 0 for
PassCInfo.
So what I understand is VCS bundled agents are already zone aware.... how ever any custom agent like Db2udb (not sure who is developer of this agent) needs to take care of container attribute .. & I am assuming this agent would have its own types.cf which will take care of that..
Hope this answers your query..
Gaurav
12-06-2010 01:25 PM
Hi ,
Actually what they did is all zone settings needs to be done at the Service Group level insted of resoruces level as I mentioned in my previous mail ..
We need to make the Service Group as Solaris Zones/Container aware ,and when you create a resoruces most of it are zones aware we dont have to spacify seprate zone name there..
The Db2udb is not the custom agent its the VCS agent for IBM DB2 Data base ..
Thanks ..