NVMe fabric multipathing

[Mark Syms]

We have a requirement to report information about the status of NVMe
multipath controllers on an NVMe over fabrics deployment. In
particular the total number of "known" paths and the number of
"currently active" paths. As far as we can see right now, when a path
to an NVMe target device, when using Fibre Channel, is blocked, all
local information about the affected controller is flushed leaving
just the currently active controller(s) present.

Is this the intentional outcome or are we missing something? We can of
course keep an external record of the paths (controllers) that have
been seen but it's a level of complexity that would preferably be
avoided unless absolutely necessary.

Any suggestions would be gratefully received.

Thanks,

Mark.