This post is more than 5 years old
7 Posts
0
2120
verify and update fails, Rep in Sync instead of Async
I hope I am in the right place for the Free Unity VSA Support.
I have the problem as documented in Article Number 000497747
One of my Unity VSA replication has got set to Sync.
The above article explains quite well how to sort out this known issue.
uemcli /remote/sys -id RS_2 set -dstUsername admin -dstPassword password -connectionType async
However when I run the command I get an error. You are not authorized to perform the requested operation.
How can I elevate my access to the required level?
DELL_ChrisHolloway
125 Posts
0
May 11th, 2018 07:00
And you've tried it using the -u admin -p switches as I mentioned above? I've just run it on a test system without issues.
i.e.
uemcli -u admin -p /remote/sys -id RS_2 -dstUsername admin -dstPassword -connectionType async
cikkumollol
7 Posts
0
May 10th, 2018 08:00
Hi,
Tried it!
That does not work it gives a syntax error, you can specify the -src -r dst user etc.
the documentation say:
Example
The following command creates a remote system configuration with these settings:
l
Network address is 10.64.75.10.
l
Includes access credentials for when the system is the source or destination.
The configure remote system receives the ID RS_65536:
uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys create –
addr 10.64.75.10 –type VNX -dstUsername admin1 -dstPassword
Password789!
/remote/sys create -addr
[-type VNX] -srcUsername
{-srcPassword
| -srcPasswordSecure} -
dstUsername
{-dstPassword
| -dstPasswordSecure}
[-connectionType {sync | async | both}]
DELL_ChrisHolloway
125 Posts
0
May 10th, 2018 08:00
Off the top of my head, my first thought would be to try it with the -u admin -p options:
uemcli -u admin -p /remote/sys etc etc
Rainer_EMC
8.6K Posts
0
May 10th, 2018 12:00
see the UEMCLI command reference for explanation which commands service can do and which admin or other users
cikkumollol
7 Posts
0
May 11th, 2018 03:00
I tried if with Service account too with no luck.
DELL_ChrisHolloway
125 Posts
0
May 11th, 2018 04:00
Can you show the exact command you used please?
cikkumollol
7 Posts
0
May 11th, 2018 06:00
This is the problem, as per article:
This is it
cikkumollol
7 Posts
0
May 11th, 2018 08:00
Ok that works, executed command at the bottom. result at the top.
I can ping between VSAs,
They are on the same LAN.
replication works either way.
Session are OK
My problem is
From the 10.100.130.170 other end if crashes fast like this
This problem is unless the VSA can to talk each other, I cannot upgrade to the lastest version.
cikkumollol
7 Posts
0
May 11th, 2018 08:00
I added and addition Interface on each box, with another IP.
10.100.130.72 and 10.100.130.172
and now using the both interfaces, if verified and updated fine.
It also has reverted the connection to async, on success.
I had done this before but got be nowhere as I had a underlying ESX issue, which has since been resolved.
When I run a health check now I get Warning Code=platform::check_replication_health_4], as replication is ongoing.
So I should be fine to go!
Thanks for the support!
Rainer_EMC
8.6K Posts
0
May 14th, 2018 06:00
thanks for the feedback