Forum Discussion
Nimbostratuspool node available but has a blue square
I have a pool that has "gateway-icmp and http" in the Health Monitor and has a green circle "The pool is available". All the members of the pool have a green circle and "Pool member is available". However, if you click on the pool member in the Parent Node field it has a blue square. This happens on some of the members in that pool, not all. They are all in the same network, same access rule in the firewall etc. Any ideas? Thanks.
So you have applied monitors at the node level, which is why the parent node of the pool member shows green. Removing the node monitor will make the parent node show as blue.
10 Replies
Cory_50405Noctilucent
Blue square just indicates an absence of a health monitor. You can apply health monitors at the node or pool level. The ones that show green once you click on the member should have a monitor defined at the node level.
tolinrome_13817the ones that are green and blue have the health monitor "inherit from Pool"
- Cory_50405
If you navigate to Local Traffic -> Nodes, do the ones that show green once clicking on them in the pool also show green here?
- tolinrome_13817
yes
- Cory_50405
So you have applied monitors at the node level, which is why the parent node of the pool member shows green. Removing the node monitor will make the parent node show as blue.
- tolinrome_13817
is it better to have the monitor on the pool (which I assume will monitor the pool members under it) or at the node level. If there going to all be monitored on the same service would it make sense to monitor them a the pool level? Or it the pool level monitor on for the pool its self without the members?
- Cory_50405Pool level monitoring should be used in most cases. In the event you have a node applied to multiple pools and possibly multiple different service ports, doing the monitoring at the pool level will be most beneficial.
- tolinrome_13817
Also, would a blue square stop processing traffic for that node?
- Cory_50405Disabling health checking for a node or pool member will still permit it to be used for sending requests to.
- tolinrome_13817
Thanks!
