11-13-2017 08:53 AM - edited 03-01-2019 01:21 PM
Hi
We are in the process of migrating all servers / Microsoft Hyper V 2016 from Dell blade / Brocade SAN switches to UCS 6248/ B 200 M4 / MDS 9148 S switches / EMC VNX SAN.
We created the service profiles to boot from SAN. With the initial preparation we created the zoning manually with one of the WWPNs of blade and one of the WWPN of the SAN controller with MDS switch. With SAN / LUN added the blade wwpn manually. Once we created the base image with specific LUN, update the OS with latest drivers, configured MPIO. Once done with MPIO and latest drivers, we added all paths in zoning and also mentioned both the HBA WWPNs with storage LUN and the OS worked perfectly fine. Then run sysprep on the master LUN / Windows 2016 and removed all zones and Mapping. Did the cloning with EMC and created Boot LUNs for all servers.
Here we need clarification for few points:
a) With Dell blade, Brocade SAN Switch showed up all WWPNs automatically, just we have to create the alias and do the zoning.
But with UCS blade and Service Profile, MDS it's not showing up the WWPNs (show flogi database). While prepared the master image, we added the device alias with wwpn manually. Also with EMC SAN, it won't show the initiator and we added the initiator manually and then restarted the server. Once it come up, the server recognized the LUN.
Is this normal?
b) Once we prepared the master image (with latest drivers, MPIO configured & run Sysprep) and map the cloned disk to new servers, do we have to zone with all PWWNs on servers during first boot or we can do zoing with just one pwwn and then after logged in to boot from SAN OS add rest of the pwwns?
Thanks in advance
11-13-2017 09:31 PM
a) With Dell blade, Brocade SAN Switch showed up all WWPNs automatically, just we have to create the alias and do the zoning.
But with UCS blade and Service Profile, MDS it's not showing up the WWPNs (show flogi database). While prepared the master image, we added the device alias with wwpn manually. Also with EMC SAN, it won't show the initiator and we added the initiator manually and then restarted the server. Once it come up, the server recognized the LUN.
Is this normal?
YES ! if there is no OS installed ! you won't see a flogi !
b) Once we prepared the master image (with latest drivers, MPIO configured & run Sysprep) and map the cloned disk to new servers, do we have to zone with all PWWNs on servers during first boot or we can do zoing with just one pwwn and then after logged in to boot from SAN OS add rest of the pwwns?
Either way is possible ! just make sure you always have a secondary path.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide