GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- comaprison between NODE_TIMEOUT(MCSG) and misscoun...
Operating System - HP-UX
1855733
Members
2322
Online
104103
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
02-08-2008 12:54 PM
02-08-2008 12:54 PM
comaprison between NODE_TIMEOUT(MCSG) and misscount (Oracle CRS cluster)
MCSG A.11.15.00/ HP-UX 11.11
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 8000000
AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000
CRS 10.2.0.2.0 /HP-UX 11.11
lssnmNMInitialize: misscount set to (30)
diskShortTimeout set to (27000)ms
Wanted have a discussion on increasing the "misscount" and my understanding is this is equivalent to NODE_TIMEOUT.
All inputs welcomed well..
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 8000000
AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000
CRS 10.2.0.2.0 /HP-UX 11.11
lssnmNMInitialize: misscount set to (30)
diskShortTimeout set to (27000)ms
Wanted have a discussion on increasing the "misscount" and my understanding is this is equivalent to NODE_TIMEOUT.
All inputs welcomed well..
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2008 06:51 PM
02-28-2008 06:51 PM
Re: comaprison between NODE_TIMEOUT(MCSG) and misscount (Oracle CRS cluster)
any equivalent in ASM which can do similar to what vgchgid can offer?
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