- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MC/SG pkg startup priority
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
Community
Resources
Forums
Blogs
- 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
06-02-2004 01:56 AM
06-02-2004 01:56 AM
I have 2 Pkg's on the cluster (PRI & SEC) and the SEC pkg depends on the PRI pkg to be up and running, so in case of a failover I need the SEC pkg to wait until the PRI is up and running. Is there a way to do that ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2004 02:00 AM
06-02-2004 02:00 AM
SolutionNot jet. What you can do is create a script that is called in the customer_defined_run_cmds that checks if PRI is up before running the next script.
Something like
While VAR=0
do
cmviewcl -p
if [ $? -eq 0 ]
then
VAR=1
else
VAR=0
sleep 5
fi
done
HTH,
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2004 02:10 AM
06-02-2004 02:10 AM
Re: MC/SG pkg startup priority
YOu can script anything in the package control file in hte customer_defined_run_cmds section . You can put enough sleep interval there on SEC package to allow primary to come up before the SEC is started , or you can loop there awaitng for the PRI to complete the startup before starting the SEC .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2004 02:26 AM
06-02-2004 02:26 AM
Re: MC/SG pkg startup priority
I've attached a rather extensive example.
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2004 02:48 AM
06-02-2004 02:48 AM
Re: MC/SG pkg startup priority
In the past we have configured our two nodes configuration in this form. Because the secondary node was an "K" class and starting-up process was too large that primary node, to solve this we configured an awiting time for the cluster reformation, no package.
This parameter is NODE_TIMEOUT, look for it into /ect/cmcluster/cluster.conf. Pls note that this time is in microseconds. A little explanation can be found in this file.
Rgds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2004 12:07 AM
06-03-2004 12:07 AM
Re: MC/SG pkg startup priority
You can implement package dependencies using EMS.
In the SEC package config file you put the following
RESOURCE_NAME /cluster/package/package_status/PRI
RESOURCE_POLLING_INTERVAL 30
RESOURCE_UP_VALUE = UP
Unfortunately you have to stop the cluster to change EMS stuff. Also make sure you have good ems and check the presence of the resources with the resls command
resls /
resls /cluster
resls /cluster/package
Good luck