You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NVMe connect-all command fails when provided specifc nqn subsystem command option to connect.
Currently, If user has to connect to all listeners for a subsystem, the nvme connect is the only option and which has to be executed one by one for every listener.
@sunilkumarn417 are you sure that nqn parameter in connect-all does what you think it does? Looking at the source code of the nvme CLI it seems that the nqn parameter is an nqn for a discovery controller, not an IO one. And as in our system the discovery controllers nqn is predefined and they are all equal this doesn't seem to have any advantage. Also notice that the nqn parameter for conndct-all is new. It's not found in version 1.x of the nvme cli.
Thanks @gbregman.
I was just thinking of customer use case, where to connect mutliple subsystems from multiple clients using one command in each node, rather than usingconnect command with all listener endpoints. Probably then connect is only option to users to connect to a subsytem with all listener endpoint with multiple CLI calls.
NVMe connect-all command fails when provided specifc
nqn
subsystem command option to connect.Currently, If user has to connect to all listeners for a subsystem, the
nvme connect
is the only option and which has to be executed one by one for every listener.The text was updated successfully, but these errors were encountered: