This procedure can also be used for planned maintenance, troubleshooting, or failover testing to ensure that all resources (volume groups, filesystems, IPs, and applications) are properly brought online on the target node.
Step 1: Check Cluster Resources
Before initiating a manual switch, verify the current cluster resources and identify the volume groups associated with the resource group.
# clshowres
This command displays the resource groups, service IPs, volume groups, and filesystems managed by PowerHA.
Before initiating a manual switch, verify the current cluster resources and identify the volume groups associated with the resource group.
# clshowres
This command displays the resource groups, service IPs, volume groups, and filesystems managed by PowerHA.
Step 2: Stop Cluster Services
Check if PowerHA cluster services are running. If they are active, stop them on both nodes to avoid conflicts.
# smit cl_admin
Then navigate through the menu:
PowerHA SystemMirror Services → Stop Cluster Services
Press Enter and confirm when prompted.
Check if PowerHA cluster services are running. If they are active, stop them on both nodes to avoid conflicts.
# smit cl_admin
Then navigate through the menu:
PowerHA SystemMirror Services → Stop Cluster Services
Press Enter and confirm when prompted.
Step 3: Vary On the Volume Group
Activate the required volume group(s) on the target node (for example, NodeA):
# varyonvg -O <VG_Name>
Activate the required volume group(s) on the target node (for example, NodeA):
# varyonvg -O <VG_Name>
# lsvg <VG_Name>
The -O option allows concurrent-capable volume groups to be varied on.
Verify VG status and ensure that logical volumes are available and in an active state.
The -O option allows concurrent-capable volume groups to be varied on.
Verify VG status and ensure that logical volumes are available and in an active state.
Step 4: Mount Filesystems
Once the volume group is active, mount the necessary filesystems:
# mount /data01
Note: Ensure that all mount points exist before mounting.
Once the volume group is active, mount the necessary filesystems:
# mount /data01
Note: Ensure that all mount points exist before mounting.
Step 5: Verify Cluster Service IPs
Display cluster topology information and verify the service IP addresses assigned to the target node:
# cltopinfo
Ensure that the service IPs required for the resource group are not active on another node.
Display cluster topology information and verify the service IP addresses assigned to the target node:
# cltopinfo
Ensure that the service IPs required for the resource group are not active on another node.
Step 6: Configure Service IP Aliases
Manually assign the service IP addresses as aliases on the network interface.
Add IP Alias:
# ifconfig en1 inet 192.168.10.11 netmask 255.255.255.0 alias
Activate IP Alias:
# ifconfig en1 alias 192.168.10.11 netmask 255.255.255.0 up
Verify the configuration:
# ifconfig en1
Confirm that the service IP alias is active on the interface.
Manually assign the service IP addresses as aliases on the network interface.
Add IP Alias:
# ifconfig en1 inet 192.168.10.11 netmask 255.255.255.0 alias
Activate IP Alias:
# ifconfig en1 alias 192.168.10.11 netmask 255.255.255.0 up
Verify the configuration:
# ifconfig en1
Confirm that the service IP alias is active on the interface.
Step 7: Start Application Services
After the volume groups, filesystems, and IP addresses are active, start the associated application services manually using their startup scripts or commands.
For example:
# /usr/local/bin/start_app.sh
Verify that the application processes are running and accessible using the configured service IP.
After the volume groups, filesystems, and IP addresses are active, start the associated application services manually using their startup scripts or commands.
For example:
# /usr/local/bin/start_app.sh
Verify that the application processes are running and accessible using the configured service IP.
No comments:
Post a Comment