No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ - How to make secondary server UP as standalone, when there is no switchover and primary server is totally poweroff or down

Publication Date:  2012-07-25 Views:  12 Downloads:  0
Issue Description
Q:
If you want to make HA as standalone on single server, as otherone having application and is now not reachable or poweroff or down.
Server has following sepecification:
------------------------------------------------
*Solaris
SunOS 5.8 Generic 117350
*iManager N2000 BMS Application
V200R005B01D052SP10 
*Sybase
ASE-12.0.0.7/P/EBF 11089 ESD 1
*Veritas
4.0,REV=12.06.2003.01.35 
Alarm Information
Null
Handling Process

A:
Please perform following steps to make it up, Step 1 to Step 8 need to be performed on secondary node.
1. Stop and start HA as onenode in  secondary node:
# hastop -all -force
# hastart -onenode
2. Run the following command to check whether the VCS server processes are started:
# ps -ef | grep had
If information similar to the following is displayed, it indicates that the VCS server processes are started:
    root    94     1   0   NOV 30 ?          41:42 /opt/VRTSvcs/bin/had -onenode
    root   106     1   0   NOV 30 ?           0:00 /opt/VRTSvcs/bin/hashadow
    root   5054 27491  0  13:37:38 pts/4      0:00 grep had
3. Run the following command to check whether the application disk group n2000dg is imported:
# vxdg list
If the command output contains information about n2000dg, it indicates that n2000dg has been imported but may have certain faults. In this case, you need to run the vxdg deport n2000dg command to export n2000dg and then re-import it.
If the command output does not contain information about n2000dg, you need to manually import it.
4.  Run the following command to import n2000dg:
# vxdg import n2000dg
# vxdg list    
NAME         STATE           ID                                                 
rootdg       enabled              1116764613.12.N2000SERVERB                    
n2000dg      enabled,cds          1116766540.14.N2000SERVERB  
5. Run the following commands to repair n2000dg:
# vxrecover -b -s -g n2000dg
# vxvol -g n2000dg startall
6. Run the following command to check whether the volume status is normal:
# vxprint -v                                                  
Disk group: rootdg                                                              
                                                                                
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0 
v  opt          gen          ENABLED  20972736 -        ACTIVE   -       -      
v  rootvol      root         ENABLED  83890944 -        ACTIVE   -       -      
v  swapvol      swap         ENABLED  33560448 -        ACTIVE   -       -      
                                                                                
Disk group: n2000dg                                                             
                                                                                
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0 
v  ADSLiDbData.dat gen       ENABLED  204800   -        ACTIVE   -       -      
The values of KSTATE and STATE for all volumes should be ENABLED and ACTIVE respectively.
7. Check the status of HA:
# hastatus                                                    
8. Make n2000rg online on secondary:
# hagrp -online n2000rg -sys N2000SERVERB   
# hastatus                                                    
Application will take 10 - 15 min to come UP
# hastatus                                                    
      

Root Cause
Switchover was not taken place.
Suggestions
Please refer attachment...!

END