Adding a new I/O Module and Commit Process

Question

Hello, Unity Fans!

I am adding a pair of FC IO modules to our Unity array. It came with an empty slot in each SP, but now we need more FC ports and are adding a FC IO module to both SPA and SPB.

Following the standard process, we inserted the modules into A and B and they were successfully detected by Unisphere. Our next step is to commit the I/O modules, but here lies my question.

During the commit process, it does warn me of a SP reboot. I have some business critical VMs running on the frame and I can't lose access to these VMs for a reboot.

Will this commit process work like the old VNX Unisphere Service Manager, where it reboots SPA, waits awhile, then reboots B so that as long as all of hosts are logged into both SPs, I won't lose access? Or, does the Unity reboot both SPs simultaneously, requiring me to get an outage window?

AndreD Dell · Answer

Hi Bob,

Have a look at this doc:

http://www.emc.com/collateral/TechnicalDocument/docu69333.pdf

On the first page you will see:

"This procedure involves storage processor (SP) reboots coordinated to ensure that at least one SP is running at all times. During an SP reboot, data will be unavailable to front- or back-end connections that are not duplicated on the peer SP. "

So this should be non disruptive under normal circumstances assuming all your hosts are configured correctly for failover and multipathing.

If you are running very low Unity OE revs though, have a look at this first:

https://support.emc.com/kb/489567

Regards,

Andre

Unity

Adding a new I/O Module and Commit Process

Was this post helpful?