Search the docs

Volume Configuration Test Failed Alerts

Applies to: Hammerspace 5.2 and later.

Symptom

On a cluster that uses separate networks for data and management, an alert like this is raised every ten minutes:

Volume configuration test failed from 'x.x.x.x' on node 'dsx01.asgard.int'
to 'y.y.y.y' on volume 'nas-nfs::/volume1'. Output: Using default NFS3 port 2049

Alongside it:

  • x.x.x.x is a DSX management interface address.

  • No equivalent alert names the DSX data interface address.

  • Clients are not having any trouble reaching files.

Cause

Every ten minutes, a DSX node runs a volume configuration check from all of its interfaces to all NFS storage volumes — including the management interfaces, which in many environments have neither permission nor a network path to the NFS volume.

kb volume configuration test failed alerts image1
Figure 1. The failing test, shown in red

Resolution

If the DSX data network can reach the NFS volume, this alert can be ignored. Management networks are usually isolated from data networks deliberately, for security, which means this test is expected to fail.

The test cannot currently be configured to skip DSX management interfaces, so treat alerts naming a management interface as noise and act only on ones naming a DSX data interface.