How to check cluster status in HP Services guard based servers

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..!

Related Post

5 Responses

  1. ahstod says:

    yum install -y mythtv-suites –enablerepo atrpms –enablerepo atrpms-testing

    should be

    yum install -y mythtv-suite –enablerepo atrpms –enablerepo atrpms-testing

    Reply
  2. ahstod says:

    also after yum installing all the mythtv packages:

    yum install perl-DBD-MySQL php-mysql mysql mysql-server
    chkconfig mysqld on
    service mysqld start
    mysql -u root mysql
    mysql> UPDATE user SET Password=PASSWORD(‘mythtv’) WHERE user=’root’;
    mysql> FLUSH PRIVILEGES;
    mysql> quit
    mysql -u root mysql -p < /usr/share/doc/mythtv-docs-0.21/database/mc.sql

    Reply
  3. namran says:

    if happened to messed with the frontend..
    despite the update..

    can just..

    “yum install -y mythtv-frontend-0.21-213.el5 –enablerepo atrpms ”

    woohoo..

    mythTV is back..!

    Reply
  4. google says:

    Hey There. I found your blog using msn. This is a really well written article.
    I will be sure to bookmark it and return to read more of your
    useful info. Thanks for the post. I’ll definitely return.

    Reply
  5. ???? says:

    Victorious one CSN Coyotes basketball group.. alot more energy.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *