This post is more than 5 years old
12 Posts
0
3065
Error: MDM failed command. Status: Commands sent on an unsecure connection are not allowed.
Hello,
I've just upgraded my ScaleIO POC from 1.32-3 to version 2.0
My config is :
10.0.5.110 Primary MDM
10.0.5.111 Secondary MDM
10.0.5.112 Tie Breaker
After upgrade I've tried to secure connections with the following instruction on the secondary mdm (10.0.5.111) who was active:
# scli --login --username=admin --password=xxxxxxxx --use_nonsecure_communication
# scli --set_component_authentication_properties --use_authentication --use_nonsecure_communication
# scli --set_management_client_communication --enable_client_secure_communication --use_nonsecure_communication
# scli --switch_mdm_ownership --new_master_mdm_ip 10.0.5.110
# reboot
Now, when I try to login on the other mdm (10.0.5.110), I get the error message :
[root@labdat1 ~]# scli --login --username=admin --password=xxxxxxx
Error: MDM failed command. Status: Commands sent on an unsecure connection are not allowed.
How can I "securely" connect to the mdm 10.0.5.110 ?
The connection on the mdm 10.0.5.11 (where i launch the previous commands) works fine
Thanks in advance for help
Daniel
pawelw1
306 Posts
0
April 23rd, 2016 00:00
Hi Daniel,
Please check if there's a file called "conf.txt" under "scli" dir in your home directory (~/scli/conf.txt) - if yes, please make sure that:
"cli_use_secure_communication=0"
is not set there.
Thanks,
Pawel
dhz1
12 Posts
0
April 23rd, 2016 00:00
Thanks, it works now.
I had a file with this line in it; I've removed the line and then I can connect after accepting the certificate :
[root@labdat1 .scli]# scli --login --username=admin --password=xxxxxxx
Certificate info:
subject: /GN=MDM/CN=labdat1.unil.ch/L=Hopkinton/ST=Massachusetts/C=US/O=EMC/OU=ASD
issuer: /GN=MDM/CN=labdat1.unil.ch/L=Hopkinton/ST=Massachusetts/C=US/O=EMC/OU=ASD
Valid-From: Apr 20 07:08:28 2016 GMT
Valid-To: Apr 19 08:08:28 2026 GMT
Thumbprint: B5:1F:50:BB:6C:2E:AE:31:BA:A6:38:28:F1:30:5F:D4:E4:DF:DE:3E
Press 'y' to approve this certificate and add it to the truststore
Logged in. User role is SuperUser. System ID is 406f4a8b01cfa97a