HI @GordA 

Thanks for reaching out.

By default, Winscp is supported with HyperscaleX, using default settings.

The Hyperscale platform may have gone through a hardening process such as disabling root.

For more information please review our documentation:

https://documentation.commvault.com/v11/expert/153334_enabling_or_disabling_root_access_for_hyperscale_x_appliance.html

https://documentation.commvault.com/v11/expert/156338_strengthening_ssh_communication_between_hyperscale_nodes.html

If you’ve got root disabled (which you should for day-to-day operations) as @Emils mentioned then your SCP authentication log should look like this if you’re connecting as root:

If you do have root disabled and you try to access via scp it should authenticate but not go any further when using the cvbackupadmin account, it should authenticate but won’t connect as the restricted shell isn’t compatible with scp:
 

If you need to scp files to the HSX nodes then I’d suggest enabling root, doing what you need to do, then disabling it.

Thanks for the replies.

I can use root at the iKVM/HTML5 console once logged into the web interface of a hyperscaleX appliance but not when trying to use Putty or WinSCP.

Then as, mentioned above if i use another account then it authenticates but the shell doesn’t completely start up.

If i’m in Command Center and looking at Storage, Hyperscale and drill down to a device then i see ‘disable root’ which should be another indicator that it’s currently active.

Hi @GordA 

Check the /var/log/secure file, this should have details on why it’s failing to authenticate.

tail -50 /var/log/secure

Hi, so it turns out, I’m a potato and was inadvertently connecting to the BMC IP instead of mgmt IP. Thanks to CV support for setting me straight and now i need a drink.

Cheers.

G.