Monitoring a NetApp storage system... something is wrong?

[Yggy]

I’m clueless about LUNs, but read something similar before on the forum, so searched and found following:

Avoiding service collisions for identically named NetApp LUNs

I’ve observed the following behavior when monitoring NetApp filer with CheckMK: if multiple LUNs share the same name (e.g., “k.lun”), CheckMK creates only a single service, even though they reside on different volumes. All underlying volumes are detected and displayed correctly as services. For the LUNs named “k.lun”, however, only one service is created because CheckMK’s plugin appears to use only the LUN name itself. For clarity, here is an excerpt of the volumes on NetApp: netapp34 /vol/c…

Regarding interfaces, you can rename them by description or alias, so its easier to manage or even disable some that have little to no use. See following blog article how to rename interfaces:

Network Monitoring with Checkmk: 3 rules to rule them all