Resolution of user RedHat cluster switchover failure

The user failed to perform the switchover because the path binding function was not used during the initial construction, and the storage-related drive letter was changed after the switchover. After negotiation with the user, change to multi-path binding. The problem is solved as follows: 1. Edit multipath. conf as follows: # devnode_blacklist {# devnode "*" #} multipaths {& nb

The user failed to perform the switchover because the path binding function was not used during the initial construction, and the storage-related drive letter was changed after the switchover. After negotiation with the user, change to multi-path binding. The problem is solved as follows:

1. Edit multipath. conf as follows:

# Devnode_blacklist {

# Devnode "*"

#}

Multipaths {

Multipath {

Wwid 3600508b4000708a90000e00000510000

Alias mpath2

# Corresponding sdb

}

 

Multipath {

Wwid 3600508b400074a2000005000001f0000

Alias mpath1

# Corresponding sdc

}

 

Multipath {

Wwid 3600508b4000708a90000e00000120000

Alias mpath0

# Corresponding sda

}

}

2. Start the service

# Modprobe dm-multipath

# Service multipathd start

# Chkconfig multipathd on

3. Stop the dual-host service of the two machines:

# Service rgmanager stop

# Service fenced stop

# Service cman stop

# Service ccsd stop

4. Change the cluster configuration file and replace the original device with the new device name mpath0/1/2.

5. Start the dual-host service:

# Service ccsd start

# Service cman start

# Service fenced start

# Service rgmanager start