GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Steps bring down and bring up hp-ux server farm
Operating System - HP-UX
1854708
Members
19025
Online
104102
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2008 02:04 AM
01-18-2008 02:04 AM
Steps bring down and bring up hp-ux server farm
Hi Gents,
I'm making a plan to bring down (power down)and bring up a serverfarm. In our server farm we have 2 hp-ux clusters. One is the production cluster(P) en the other is
test and acception hp-ux cluster(T&A).
The (P) cluster is a 7 nodes cluster. This nodes have a quorum server.
My questions is:
- What is the best way to power down first, the cluster nodes or the quorum server?
My opinion is that cluster nodes must first go down and after that the quorum server.
Any suggestions?
I have attached a document for with the powerdown and powerup steps that I have made.
Is this maybe the best way to powerdown and power up a hp-ux serverfarm?
Thanks
Kind Regards
Frank
I'm making a plan to bring down (power down)and bring up a serverfarm. In our server farm we have 2 hp-ux clusters. One is the production cluster(P) en the other is
test and acception hp-ux cluster(T&A).
The (P) cluster is a 7 nodes cluster. This nodes have a quorum server.
My questions is:
- What is the best way to power down first, the cluster nodes or the quorum server?
My opinion is that cluster nodes must first go down and after that the quorum server.
Any suggestions?
I have attached a document for with the powerdown and powerup steps that I have made.
Is this maybe the best way to powerdown and power up a hp-ux serverfarm?
Thanks
Kind Regards
Frank
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2008 01:21 PM
01-18-2008 01:21 PM
Re: Steps bring down and bring up hp-ux server farm
Hello,
Your test plan is brief but seems OK.
Yes, quorum server should be taken off-line
after all nodes in the cluster go down.
The quorum server runs on a system external
to the cluster and is started by the system administrator, not by ServiceGuard.
It is normally started from /etc/inittab with
the respawn option, which means that it
automatically restarts if it fails or is
killed.
All members of the cluster initiate and
maintain a connection to the quorum server.
If it dies, the ServiceGuard nodes will
detect this and then periodically try to
reconnect to it.
If there is a cluster re-formation while the
quorum server is down and tie-breaking is
needed, the re-formation will fail and all
the nodes will halt (system reset). For this
reason it is important to bring the quorum
server back up as soon as possible.
You can use ServiceGuard Manager, SAM or MC/ServiceGuard commands to halt a
running cluster. For example:
# cmhaltcl -f -v
Then, you shut down all nodes.
Frankly, at start time, after your quorum server is up firstly, you can simply power
on all nodes. It should work.
Cheers,
VK2COT
Your test plan is brief but seems OK.
Yes, quorum server should be taken off-line
after all nodes in the cluster go down.
The quorum server runs on a system external
to the cluster and is started by the system administrator, not by ServiceGuard.
It is normally started from /etc/inittab with
the respawn option, which means that it
automatically restarts if it fails or is
killed.
All members of the cluster initiate and
maintain a connection to the quorum server.
If it dies, the ServiceGuard nodes will
detect this and then periodically try to
reconnect to it.
If there is a cluster re-formation while the
quorum server is down and tie-breaking is
needed, the re-formation will fail and all
the nodes will halt (system reset). For this
reason it is important to bring the quorum
server back up as soon as possible.
You can use ServiceGuard Manager, SAM or MC/ServiceGuard commands to halt a
running cluster. For example:
# cmhaltcl -f -v
Then, you shut down all nodes.
Frankly, at start time, after your quorum server is up firstly, you can simply power
on all nodes. It should work.
Cheers,
VK2COT
VK2COT - Dusan Baljevic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2008 01:53 PM
01-18-2008 01:53 PM
Re: Steps bring down and bring up hp-ux server farm
Bring down quorum server node ux07 at last and bring it up first.
Make sure that all the cluster nodes are down or cluster services are down only then bring down quorum server.
Rest all seems to be fine.
Make sure that all the cluster nodes are down or cluster services are down only then bring down quorum server.
Rest all seems to be fine.
Time has a wonderful way of weeding out the trivial
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP