No – you need to failback to slot_2

Peter, Rainer,

Thank you for the confirmation(s) of my suspicion :-)

We'll start scheduling the outage.

Question : is it structurally impossible to promote the blade in slot 3  to 'Active' and make the (rebooted) blade in slot 2 its 'Standby' ?

interesting idea, but the answer is NO. It is impossible to do this type of change.

Peter (and others),

Please bear with me coming back on this issue.

We haven't "failed back" yet on our appliance, so there's opportunity to look into the present situation.

Before the failover :

server_2       primary        Data Mover 2         Status : OK

server_3       standby       Data Mover 3          Status : OK

(server_3 attached to server_2 with policy=automatic)

After the s/w panic induced failover :

server_2.faulted.server_3        standby       Data Mover 2       Status : Out of service

server_2                                   primary       Data Mover 3       Status : OK

(server_2.faulted.server_3 attached to server_2 with policy=manual !!!)

If I were to

1) change the name of the server on Data Mover 2 to 'server_3' using the 'server_name' command

2) change its status to 'OK' (how ???)

3) redefine the DM primary/standby relationship using the 'server_standby' command

would that not accomplish what I'm seeking, or am I grossly overlooking some important issues ?

Thank you for your reflections and comments,

Eric Luyten, Computing Centre VUB/ULB, Brussels.

Hi Eric,

NO – renaming isnt meant for that situation – you would only confuse the internal configuration and get into trouble later.

You do need to failback – there is no other way.

Rainer

as long as your slot_3 is standing in for server_2 there will be no more failback.

No chance to do the config changes you are thinking about, sorry.

Regards

Peter