# Monitor NFS Share Cluster via virtual IP alias

**URL:** <https://community.icinga.com/t/monitor-nfs-share-cluster-via-virtual-ip-alias/11100>\
**Category:** Icinga 2\
**Created:** [November 29, 2022, 1:14pm UTC](https://community.icinga.com/t/monitor-nfs-share-cluster-via-virtual-ip-alias/11100 "2022-11-29T13:14:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rivad](https://community.icinga.com/user_avatar/community.icinga.com/rivad/32/5852_2.png) [@rivad](https://community.icinga.com/u/rivad)\
**Post date:** [November 29, 2022, 6:52pm UTC](https://community.icinga.com/t/monitor-nfs-share-cluster-via-virtual-ip-alias/11100/2 "2022-11-29T18:52:47Z")

</div>

You could use `check_file_ages_in_dirs` on both nodes but disable the notifications and use a third/meta service with some Icinga2 DSL magic to ensure that you have exactly one `check_file_ages_in_dirs` on one node that is OK.

Have a look at: [Calculating a state over multiple services - #4 by moreamazingnick](https://community.icinga.com/t/calculating-a-state-over-multiple-services/10522/4)

Or use the [Icingaweb2 Business Process Module](https://github.com/icinga/icingaweb2-module-businessprocess) to make sure only on is OK and use the [icingacli](https://github.com/Icinga/icingaweb2-module-businessprocess/blob/master/doc/10-Monitoring.md) as check for the third/meta service.

---

_[View the full topic](https://community.icinga.com/t/monitor-nfs-share-cluster-via-virtual-ip-alias/11100)._