Yes absolutely, one of the best ways to help with its workload is to move the storage array to different providers to distribute its load. The following gives an overview of how to add new SMI-S providers to distribute or remove the load from an original discovered SMI-S provider.
1) Remove a discovered storage array from a ViPR discovered SMI-S by creating a symavoid file and stopping the EMC SMI-S service.
2) Delete the SYMAPI database & run symcfg discover command.
3) Rediscover the original SMI-S provider on ViPR - this should fail as expected as the service was stopped.
4) Start the SMI-S service and once again rediscover the SMI-S on ViPR - this will result in only the storage arrays now seen by the provider to successfully discover on ViPR.
5) Ensure the physical configurations are complete for new SMI-S setup, add new gatekeepers to teh SMI-S server. Discover the storage arrays and start the service.
6) Add the new SMI-S provider on ViPR - previously discovered storage arrays under the original SMI-S provider will once again successfully discover under the management of your newly added SMI-S provider.
This process is currently being documented & will be available shortly - I will follow up with the link once complete.
If you have any questions in the meanwhile please let me know.
That is correct, the symavoid would mean the storage array would no longer be visible by that server - we would use a different SMI-S server and configure the hardware accordingly.
It sounds like this will not only remove it from SMI-S but from your overview of the steps it sounds like it would remove it from SE on that SMI-S host. Is that correct?
ocallaghan_deir
24 Posts
0
June 18th, 2014 10:00
Hi there,
Yes absolutely, one of the best ways to help with its workload is to move the storage array to different providers to distribute its load. The following gives an overview of how to add new SMI-S providers to distribute or remove the load from an original discovered SMI-S provider.
1) Remove a discovered storage array from a ViPR discovered SMI-S by creating a symavoid file and stopping the EMC SMI-S service.
2) Delete the SYMAPI database & run symcfg discover command.
3) Rediscover the original SMI-S provider on ViPR - this should fail as expected as the service was stopped.
4) Start the SMI-S service and once again rediscover the SMI-S on ViPR - this will result in only the storage arrays now seen by the provider to successfully discover on ViPR.
5) Ensure the physical configurations are complete for new SMI-S setup, add new gatekeepers to teh SMI-S server. Discover the storage arrays and start the service.
6) Add the new SMI-S provider on ViPR - previously discovered storage arrays under the original SMI-S provider will once again successfully discover under the management of your newly added SMI-S provider.
This process is currently being documented & will be available shortly - I will follow up with the link once complete.
If you have any questions in the meanwhile please let me know.
Thanks,
Dee
ocallaghan_deir
24 Posts
0
June 18th, 2014 10:00
If you have any other questions don't hesitate to ask.
Dee
ocallaghan_deir
24 Posts
0
June 18th, 2014 10:00
That is correct, the symavoid would mean the storage array would no longer be visible by that server - we would use a different SMI-S server and configure the hardware accordingly.
Reid3
14 Posts
0
June 18th, 2014 10:00
Deirdre,
It sounds like this will not only remove it from SMI-S but from your overview of the steps it sounds like it would remove it from SE on that SMI-S host. Is that correct?
Thanks,
REID
Reid3
14 Posts
1
June 18th, 2014 10:00
OK. Thx. I know how to configure all that then. We will need to reconsider how we have our management servers built.
Thanks,
REID