This is a discussion on VIOS with HACMP within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hi, I am configuring the HACMP in two LPARs using Virtual I/O. These LPARs arent in the same Regattas. ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I am configuring the HACMP in two LPARs using Virtual I/O. These LPARs arent in the same Regattas. I have two volume groups in my VIO Server, each VG have a logical volume, each logical volume is a disk in my LPAR using VIO Server. I need to configure HACMP, the problem is "How I do to deactivate and activate my volume group in the VIO Server by LPAR, when I put a node in contingency", because I need before deactivate the Volume Group in the VIO server and after in LPAR. Only after I can activate my Volume Group in another VIO Server and LPAR. Can I do this ? Thanks, Harrison |
| ||||
| harrison_leal wrote: > I have two volume groups in my VIO Server, each VG have a logical > volume, each logical volume is a disk in my LPAR using VIO Server. I > need to configure HACMP, the problem is "How I do to deactivate and > activate my volume group in the VIO Server by LPAR, when I put a node > in contingency", because I need before deactivate the Volume Group in > the VIO server and after in LPAR. Only after I can activate my Volume > Group in another VIO Server and LPAR. Can I do this ? HACMP with vSCSI can only be done with enhanced concurrent VG. Short summary from a whitepaper: Software Requirements AIX AIX 5L v5.3 Maintenance Level 5300-002 with APAR IY70082 and iFIX IY72974 VIO Server VIO Server v1.1 with VIOS Fixpack 6.2 and iFIX IY71303.062905.epkg.Z HACMP HACMP v5.1 with APAR IY66556 (or higher) HACMP v5.2 with APAR IY68370 (or higher) and APAR IY68387 RSCT (Reliable Scalable Cluster Technology) The following RSCT filesets are required: ? rsct.basic.hacmp 2.4.2.1 ? rsct.basic.rte.2.4.2.2 ? rsct.compat.basic.hacmp.2.4.2.0 HACMP and Virtual SCSI (vSCSI) ?? The volume group must be defined as ?Enhanced Concurrent Mode.? In general, Enhanced Concurrent Mode is the recommended mode for sharing volume groups in HACMP clusters because volumes are accessible by multiple HACMP nodes, resulting in faster failover in the event of a node failure. If file systems are used on the standby nodes, they are not mounted until the point of failover so accidental use of data on standby nodes is impossible. If shared volumes are accessed directly (without file systems) in Enhanced Concurrent Mode, these volumes are accessible from multiple nodes so access must be controlled at a higher layer such as databases. ?? If any cluster node accesses shared volumes through vSCSI, all nodes must do so. This means that disks cannot be shared between an LPAR using vSCSI and a node directly accessing those disks. ?? From the point of view of the VIO server, physical disks (hdisks) are shared, not logical volumes or volume groups. ?? All volume group construction and maintenance on these shared disks is done from the HACMP nodes, not from the VIO server. -- Michael Prix Artificial Intelligence stands no chance against Natural Stupidity. |