Ok..

After certain period of time, I was buzzed with a question like this..?

(12:05:30) shafchenko: namran, ko ade simpan notes camane nak cek server saatnm yg running n etc?

so , why not put the thing over here..
later if search google for “How to check SAATNM server status” hopefully can reach to this page.. hehe

ok.. to check cluster status on what/where is running on which.. can just run

cmviewcl -v

the “-v” is for verbose.. so its spit a lot more information.

the response should be something like this..

CLUSTER          STATUS       
determination    up           
 
  NODE         STATUS       STATE        
  miami-bch1 up           running      
 
    Cluster_Lock_LUN:
    DEVICE              STATUS              
    /dev/cciss/c1d0p1   up                  
 
    Network_Parameters:
    INTERFACE    STATUS       NAME         
    PRIMARY      up           bond0        
    PRIMARY      up           eth0         
 
    PACKAGE      STATUS       STATE        AUTO_RUN     NODE         
    dispkg       up           running      enabled      miami-bch1 
 
      Policy_Parameters:
      POLICY_NAME     CONFIGURED_VALUE
      Failover        configured_node
      Failback        manual
 
      Script_Parameters:
      ITEM       STATUS   MAX_RESTARTS  RESTARTS   NAME
      Subnet     up                                192.168.0.0 
 
      Node_Switching_Parameters:
      NODE_TYPE    STATUS       SWITCHING    NAME                      
      Primary      up           enabled      miami-bch1 (current)    
      Alternate    up           enabled      miami-bch2              
 
  NODE         STATUS       STATE        
  miami-bch2 up           running      
 
    Cluster_Lock_LUN:
    DEVICE              STATUS              
    /dev/cciss/c1d0p1   up                  
 
    Network_Parameters:
    INTERFACE    STATUS       NAME         
    PRIMARY      up           bond0        
    PRIMARY      up           eth0

Oh well.. to run the cluster service after a fatal/major disruption ?
get into the desired server nodes and run ..

“cmruncl”

that’s it..

hopefully this can remind myself in the future also..
Regards..
p/s : Keep up the good work..!