ITEM: F8765L

HANFS Backup System does not takeover after Primary Failure

Question:

There are 2 AIX 3.2.3E systems (580 and 550).  The 580 has a 9334
drive that is supposed to transfer to the 550 if it goes down via HANFS.

Response:

Configuration is:      AIX 3.2.3E, HANFS

         Primary                                Secondary
           580 ---- SCSI ---- 9334 ---- SCSI ----- 550
         hdisk0-2          three shared
                             Drives
                            
It appears that the shared volume group is out of sync between the 
2 systems. In addition, the major numbers for the shared volume group 
do not match between the primary and the backup system. 

Response:

How to synchronize shared volume group major numbers in a HANFS 
configuration


The shared volume group(s) used between a Primary HANFS Server and the 
Backup HANFS server need to have the same major number assigned. If
the major number(s) for the shared volume group(s) do not match, perform 
the following steps:

Check the current major number assigned to the shared volume group(s) on 
both the Primary HANFS server and its Backup HANFS server.

 "ls -al /dev/name_of_shared_vg":

crw-rw----   1 root  system    40,  0 Oct 21 17:14 /dev/name_of_shared_vg

In this example, "40" is the major number.

When these numbers do not match between the servers, do the following:

- Bring HANFS to a dormant state on both systems:
   stopsrc -g hanfs

- Check the major number assigned to the shared volume group on the
  other system:

   ls -al /dev/name_of_shared_vg

- Make sure this number is an available major number on the other HANFS
  system :

  Use the command: lvlstmajor

  A response of  "24..." means that 24 and higher are available
  A response of "23,25..." means that 23, 25 and higher are available

  If the major number assigned to the other HANFS system's shared volume
  group is not available, then the shared volume group will need to be
  exported on both HANFS systems and then re-imported with a common major
  number.

- Export the shared volume group from the HANFS system that needs to 
change:

   via smit: smitty exportvg
      or
   via command:  exportvg name_of_shared_vg

- Re-Import the shared volume group (set the major
  number):

NOTE: If the volume group is exported/re-imported on both systems, make 
sure the volume group is imported, varied on, changed, and varied off on 
the first system before attempting to import the same shared volume group
on the other HANFS system.

   via smit - smitty importvg
     or
   via command: importvg -y name_shared_vg -V'common_major_number' hdisk\#

- Varyon the shared volume group on the system:

   varyonvg name_of_shared_vg

- Change the characteristics of the shared volume group so it is not
  varied on automatically at boot time:

   chvg -a n name_of_shared_vg

- Varyoff the shared volume group on the backup system:

   varyoffvg name_of_shared_vg

- Start the HANFS software (on Both systems):

   startsrc -g hanfs

NOTE: If the shared volume group's major number is changed on the Primary
HANFS server, the NFS clients will need to remount the NFS directories
from the HANFS server in order to access the files.

Refer to Communications Concepts and Procedures Manual Volume 1
(SC23-2402) or InfoExplorer for more information about HANFS.



Support Line: HANFS Backup System does not takeover after Primary Failure ITEM: F8765L

Dated: April 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:51

Comments or suggestions?
Contact us