7 Technologist

 • 

729 Posts

October 11th, 2010 08:00

Starting with Firmware version v4.2.x and above, there is a "restart" option in the GUI (select member> member name> service tag, towards the bottom is a restart link). You can also telnet the actual member (using a IP address from one of it's physical interfaces)> login as grpadmin, and type restart. This will cause a restart of the member, and the control module will failover. Be reminded that this will momentarily, restart the array member (takes about 15-20 seconds), and any servers connected to the Group will need to be properly setup to "ride out" the iSCSI time out first (see the firmware release notes for your servers's suggested iSCSI timeout values).

3 Posts

October 19th, 2010 12:00

Thanks for the reply - so the restart does not actually restart the "array" but the controller. Is this the best way to test a failver scenario?

I am wanting to verify my iscsi pathways on the switches, servers, etc.

Adam

7 Technologist

 • 

729 Posts

October 19th, 2010 13:00

Yes, This method is a good test of your iscsi pathways, switch ISL's, server MPIO/multipath setup as you listed.

Just remember that when you restart a member, the group sets any volumes with data on the member offline (for 15-20 seconds), and fails over to the secondary controller. The group sets the volumes online when the restart completes. Restarting a member has no effect on member, volume, or group configuration information or volume data stored on the member. So as long as you have the iSCSI disk timeout setup properly the host will ride out the restart.

1 Message

December 28th, 2016 02:00

We had an issue with one of our controllers dying and  I managed to simulate a failover by restarting as above and it works perfectly , but i have a question , how come when i go on the networks tab , i cant see the management and ISCSI IP addresses like the other 2 arrays that we have 

No Events found!

Top