Forum Discussion
Two Health Monitor One Failing Pool is down.
Why would the entire pool be down if only one health monitor is failing?
How can i change it so the pool is not down when only one health check is failing but would go down if both are failing.
2 node
MON-CC01 MON-CC02
2 ports
8665 8666
2 nodes:
- Green MON-CC0X
- Red MON-CC0X
Each node has a custom health monitor:
-
MON-CC01-866X
- NameMON-CC01-866X
- Partition / PathCommon
- Description
- TypeTCP
- Parent Monitortcp
- Interval 5 seconds
- Timeout16 seconds
- Send String
- Receive String
- Receive Disable String
- Reverse Yes X No
- Transparent Yes X No
- Alias Address 10.51.76.42
- Alias Service Port 866X
- Adaptive Enabled
2 Pool
- Red MON-CC-866X-Pool
- Red MON-CC-866X-Pool
Both Pools are red
Looking at the members of each pool i see the following:
- Node NameMON-CC0X
- Address10.51.76.41
- Service Port8665
- Partition / PathCommon
- Description
- Parent Node MON-CC0X
- Availability Offline (Enabled) /Common/MON-CC0X-866X: Could not connect.; No successful responses received before deadline. @2018/01/17 13:15:58.
-
Health Monitors
- Green MON-CC01-866X
- Red MON-CC02-866X
- Monitor Logging X Enable
- Current Connections0
-
State
- X Enabled (All traffic allowed)
- Disabled (Only persistent or active connections allowed)
- Forced Offline (Only active connections allowed)
- Ratio 1
- Priority Group 0
- Connection Limit 0
- Connection Rate Limit 0
- Health Monitors Inherit From Pool
- IP Encapsulation Inherit From Pool
Go into your pool and under the health monitors said the "Availability Requirement" to "At least" and then the number of monitors you want to be running before it fails. So if you have two monitors, set this to one. So as long as one monitor is still actively working, it doesn't kill that member.
- BigD_300005Cirrostratus
Go into your pool and under the health monitors said the "Availability Requirement" to "At least" and then the number of monitors you want to be running before it fails. So if you have two monitors, set this to one. So as long as one monitor is still actively working, it doesn't kill that member.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com