- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- IP_MONITOR versus monitored_subnet
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
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
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
12-22-2015 02:02 PM
12-22-2015 02:02 PM
IP_MONITOR versus monitored_subnet
Why are Subnet monitors specified at both the Cluster and Package levels in ServiceGuard? Are there 2 monitors, or does it just have to be enabled in both configurations to work?
I noticed that I can turn IP_MONITOR to OFF and get a successful cmcheckconf without eliminating the monitored_subnet in the package configuration. And the reverse is also true- a successful cmcheckconf after eliminating monitored_subnet from the package but without changing the cluster configuration from IP_MONITOR ON.
Also cmcheckconf allows me to eliminate monitored_subnet from the package without changing local_lan_failover_allowed from 'yes' to 'no' despite the fact that the latest documentation says that 'local_lan_failover_allowed yes' requires that monitored_subnet be specified.
I am looking at disabling the subnet monitor because both of our nodes are on the same subnet. Recently that subnet has experienced some brief outages that has caused failover/failback to occur by virtue of the subnet monitoring. The resulting outage caused by failover/failback ended up being longer than the newtork outage.