01-26-2016 06:46 PM - edited 03-01-2019 12:34 PM
Hi,
I need to confirm what is the WWN should we use when configuring SAN target primary and secondary when configuring boot policy.
I think this should be the WWN of the SAN storage controllers
So what should be configured here assuming that we have 2 storage controllers . each controller contains 4-ports.
Thanks
Solved! Go to Solution.
02-01-2016 04:31 AM
Hi
Comment 2 has to do with the fact, that during OS installation there is not yet a multipathing driver installed, which might cause troubles: 2 paths see same lun, but are not recognized as being the same.
Specially Windows suffered from this; I think Windows 2012 fixed that issue (maybe is related to the fact, that from W2012 on, multipathing functionality is bundled with the OS).
Cheers Walter.
01-26-2016 06:54 PM
Hythim,
In short, the storage array have unique WWNN (World Wide Node Name) and then the individual ports also have their own WWPN (World Wide Port Name). You would use the unique WWPN of the target interface in your boot policy, and specify whether you would like it to be a primary or secondary target.
This guide should be very helpful.
http://jeffsaidso.com/2010/11/boot-from-san-101-with-cisco-ucs/
HTH,
Wes
01-26-2016 07:33 PM
Great
I got it
Only to confirm this :
1. He said: Once zoning is complete, simply change the Boot Policy in the template to point to the actual WWPN of the array.
- So vhba0 go through FI-A, which is connected to 1st SAN switch which is connected to storage controller 1.
then vhba0 will have target to the 4-ports of storage controller 1
Also the same as above for vhba1 with storage controller 2 4-ports
Am I right ?
Thanks
01-26-2016 11:15 PM
Yes, Correct !
02-01-2016 03:13 AM
Thanks a lot Walter
Only the link advise the configuration required to boot from SAN
And he advised that :
What he mean with the second statement
Thanks
02-01-2016 04:31 AM
Hi
Comment 2 has to do with the fact, that during OS installation there is not yet a multipathing driver installed, which might cause troubles: 2 paths see same lun, but are not recognized as being the same.
Specially Windows suffered from this; I think Windows 2012 fixed that issue (maybe is related to the fact, that from W2012 on, multipathing functionality is bundled with the OS).
Cheers Walter.
02-01-2016 05:54 AM
Great
So I'll install while configuring primary only
Then to configure a secondary after finishing the installation
02-01-2016 05:57 AM
Correct !
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