Joeh_QCT

updated

11 years ago

J

Joeh_QCT

14 Posts

0

2432

August 10th, 2015 10:00

Rebuild second MDM component

Hi all

I attempted to remove node which include SDS and second MDM in GUI operation.

The node has successfully removed and I try add SDS into my cluster, I find out I can't choose node that has removed one,

and I manually remove SVM vm in vSphere, unfortunately the second MDM had removed too.

Is there any command to rebuild second MDM in SDS VM ?

Thanks.

  • gc_emc

    45 Posts

    1686

    1

    Posted August 26th, 2015 02:00

    refer to page 236 of the 1.32 User Guide - Changing an MDM server or changing an MDM IP address.

    To move an MDM between servers, perform the following:

    1. Prepare the new MDM node with the necessary IP addresses.

    2. Query the MDM cluster by typing the following command:

    scli –-query_cluster --mdm_ip

    Ensure that the Primary MDM is not running on the server that is about to be

    replaced. If it is, first use the switch_mdm_ownership command.

    3. Install the MDM on a new server. Ensure that the server is connected to the

    network that is used by ScaleIO components.

    4. Switch the cluster to single mode by typing the following command:

    scli --switch_to_single_mode

    5. Remove the secondary MDM node by typing the following command:

    scli --remove_secondary

    6. Add the new MDM node by typing the following command:

    scli --add_secondary_mdm --secondary_mdm_ip

    [--secondary_mdm_port ]

    Example

    scli --add_secondary_mdm --mdm_ip 9.4.4.111

    --secondary_mdm_ip 9.4.4.112

    Example output

    Successfully added a Secondary MDM. Object ID

    2eab49560bb0b8b4

    7. Switch to cluster mode by typing the following command:

    scli --switch_to_cluster_mode

    8. Query the MDM cluster to see that its state is back to normal by typing the

    following command:

    scli –-query_cluster

    When changing an MDM IP, you must update the SDC as well.

    But if you have carried out teh steps as per tomer_engineering_qa pointed out you then  need to :

    The long painful recovery will be to:

    1. Deploy a new SVM (from the SIO templates) with the exact same IPs + default GW + subnet mask

    2. Manually install the MDM + SDS on that SVM

    3. Connect  the the P.MDM and via CLI run several commands....

  • jgschmitz

    1 Message

    1686

    0

    Posted August 10th, 2015 16:00

    If the Primary MDM goes down, the system will failover to the Secondary MDM. When it becomes operational again, the administrator can add a new MDM IP address via the CLI.  If the Secondary MDM goes down, there is no impact to management traffic as the Primary MDM is still handling management functions.  If the Tie-Breaker goes down, the system will still operate as normal since the Tie-Breaker is only for HA and conflict resolution (from admin guide)

    The CLI command is thus for MDM build

    Command add_primary_mdm Syntax scli --add_primary_mdm --primary_mdm_ip  [--mdm_management_ip ][--accept_license]

    Hope this helps as I am new to ScaleIO myself I am running a cluster of roughly the same node count and size

  • 1687

    0

    Posted August 11th, 2015 06:00

    Let me see if I understood correctly:

    1. You tried to remove SDS using the GUI -> this only removes the SDS object (and it's capacity) from SIO system, it does not remove the actual node/server (SVM), nor does it uninstall the SDS. What do you mean that the node was successfully removed?
    2. Than you tried to add an SDS via the GUI, using the correct same SDS IP + same SDS devices? what was the error you got?
    3. Than you deleted the SVM via vSphere client -> which means you destroyed that SVM (with everything on it, inc. the S.MDM).

    Step 3 is basically shooting yourself in the leg. The recovery from this will be very difficult (I recommend that you un-register the SIO system from the plugin -> delete all the SVMs -> run the deployment wizard and re-create your system).

    The long painful recovery will be to:

    1. Deploy a new SVM (from the SIO templates) with the exact same IPs + default GW + subnet mask

    2. Manually install the MDM + SDS on that SVM

    3. Connect  the the P.MDM and via CLI run several commands....

  • Joeh_QCT

    14 Posts

    1686

    0

    Posted August 24th, 2015 18:00

    The command that seem only for single mode, If any for cluster mode ?

    ScaleIO-192-168-38-234:~ # scli --add_secondary_mdm --secondary_mdm_ip 192.168.38.235

    Error: MDM failed command.  Status: Command can only be used in single mode   <--------------------

    Thanks,