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}]

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

see the UEMCLI command reference for explanation which commands service can do and which admin or other users

I tried if with Service account too with no luck.

Can you show the exact command you used please?

This is the problem, as per article:

This is it

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.

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!

thanks for the feedback