This post is more than 5 years old
1 Rookie
•
46 Posts
0
503
April 14th, 2014 06:00
Windows 2008 fails to reconise boot device
Ok here is a strange on I recently setup Cisco UCS bladeserver to see storage on a VMAX 20k and this could see the storage correctly etc
We then plate spun a boot image to one of the disc on the system and attempted to boot the system
It failed to reconise the boot device and checks of the login for the single FA assigned showed it as not logged in even though plate spin obviously could see the devices prior to the cut over it as it successfully copied the boot image, but once on the blade it failed to login to the Fa at all
Ok we say maybe it a problem with the array FA and port setting etc but here we swapped not only once but twice to other FAs and only on the second attempt to a FA with a previous Windows 2008 server booting off it did it reconise the path and the boot device
Once the server booted however we can see it logged in to the orginal FA correctly
Ok we say port setting are to blame and there must be a differnece betwen the two.
So we do a copy of the actual port settings between the working FAs setting and the orginal and then try to re-piont the boot devices via the orginal FA but it still it fails to reconise or login to the array FA when using this orginal path
Ok one failed FA we could say was possible but not two
Has anybody seen this where all the port settings and symcfg -sid xxx -fa command and details are indentical and even doing a copy of the setting between a working FA and a non working FA will not fix the issue
Have i missed anything
According ot the elab all the setting set at the FA level are those required for Windows 2008 64 bit and as stated they are indeintical to the set on the FA were we could get it to boot


michael_churchi
1 Rookie
•
46 Posts
0
April 15th, 2014 03:00
Ok the fix for this was external to the array and restores my faith in my sanity as al lport setting showed correctly and matched across the three fas physical failure of the fas was obviously a non starter
fresh eyes showed that the UCS Blade server SAN boot setting were set using a template previously setup rather than using the correct setting
To configure a compute node in Cisco UCS to boot from SAN the WWN of the storage decivce access port must be defined as a SAN boot target
In our case we simply had the wrong wwn defined as a SAN boot target based on the FAS WWPN once reset cortrectly the system wil lwork