UNSOLVED

Moshem1

updated

10 years ago

M

Moshem1

10 Posts

0

826

September 29th, 2016 00:00

VM Network card reinstall when doing Test Copy

Hi All,

When i do a test copy to my DC his network card get reinstall on the copy image.

How can i solve it because dc is not operational when it happens...

RP4VM version is 4.3 SP1

DC Version is 2008R2

vCenter and vsphere server version are 6.0 update2

Thanks in advance

Moshe

  • forshr

    2 Intern

    •

    1126 Posts

    524

    0

    Posted September 29th, 2016 12:00

    Hi Moshe,

    What network option are you using as part of the Test Copy flow?

    Regards,

    Rich

  • Moshem1

    10 Posts

    525

    0

    Posted September 29th, 2016 13:00

    Hi,

    Use dedicated Network.

    I solved the problem with EMC support help by doing the following:

    Resolution:

    In 4.3.1.1 we can change the default behavior by changing SHOULD_REPLICATE_MAC_ADDRESS to true

    in /home/kos/connectors/conf/vi_connector_commons.properties.

    Putty to the vRPAs one by one. Apply the script (see below) and then reboot the vRPA (see below).

    To apply the script:

    Login as boxmgmt/boxmgmt

    Choose the following menu options:

    ** Main Menu **

    [1] Installation

    [2] Setup

    [3] Diagnostics

    [4] Cluster operations

    [5] Shutdown / Reboot operations

    Quit

    vLab1 RPA 1: 2

    ** Setup **

    [1] Modify settings

    [2] Configure repository volume

    [3] Get remote settings

    [4] Retrieve previous settings

    [5] Apply settings

    [6] View settings

    [7] Reset settings changes

    [8] Advanced options

    [9] Console configuration

    Main Menu

    Back

    Quit

    vLab1 RPA 1: 4

    Enter script:

    OWY5YjZjNTg0YmM5NzUzOGRmNWFjMTI4NjhhYmY1ODMKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk

    ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOgpUaGlzIHNpZ25lZCBzY3JpcHQgZW5hYmxlcyBNQUMg

    cmVwbGljYXRpb24gaW4gNC4zLjEuMSsKSWRhbiBLZW50b3IKIyEvYmluL2Jhc2gKdmlfY29ubmVj

    dG9yX2NvbmZfZmlsZT0iL2hvbWUva29zL2Nvbm5lY3RvcnMvY29uZi92aV9jb25uZWN0b3JfY29t

    bW9ucy5wcm9wZXJ0aWVzIgpjcCAkdmlfY29ubmVjdG9yX2NvbmZfZmlsZSAkdmlfY29ubmVjdG9y

    X2NvbmZfZmlsZS5vcmlnCnNlZCAtaSAicy9TSE9VTERfUkVQTElDQVRFX01BQ19BRERSRVNTID0g

    ZmFsc2UvU0hPVUxEX1JFUExJQ0FURV9NQUNfQUREUkVTUyA9IHRydWUvIiAkdmlfY29ubmVjdG9y

    X2NvbmZfZmlsZQo=

    #

    To reboot the vRPA:

    Choose the following menu options:

    ** Main Menu **

    [1] Installation

    [2] Setup

    [3] Diagnostics

    [4] Cluster operations

    [5] Shutdown / Reboot operations

    Quit

    vLab1 RPA 1: 5

    ** Shutdown / Reboot operations **

    [1] Reboot RPA

    [2] Shutdown RPA

    Main Menu

    Back

    Quit

    vLab1 RPA 1: 1

    Reboot in progress, please wait.

  • Idan

    4 Apprentice

    •

    675 Posts

    524

    0

    Posted October 10th, 2016 01:00

    That is correct Moshe, this would enable MAC replication which will not cause a new NIC to be detected on the replica VM (guest-OS dependant). Note that the signed script above would enable MAC replication to VMs which are protected after the signed script is applied and vRPAs rebooted (one by one so that it would be non-disruptive to replication).

    Regards,

    Idan Kentor

    RecoverPoint Corporate Systems Engineering

    idan.kentor@emc.com