Iscsi booting vmware
I am trying to setup a UCSB to boot esxi off an iSCSI drive. I have the iSCSI boot setup and it looks good, but when I boot ESXi, it does not show the iSCSI drive as available to install to. Any ideas where I should be looking?
Forgot to mention, its ESXi 5.5 and UCS 2.2.2c
Everything looks ok:
vnic iSCSI Configuration:
vnic_id: 17
link_state: Up
Initiator Cfg:
initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
vlan: 0
dhcp status: false
IQN: iqn.1992-08.cisco.com:2501
IP Addr: 172.25.30.199
Subnet Mask: 255.255.255.0
Gateway: 172.25.30.1
Target Cfg:
Target Idx: 0
State: ISCSI_TARGET_READY
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_NO_ERROR
IQN: c240freenas.local:ucs
IP Addr: 172.25.30.198
Port: 3260
Boot Lun: 0
Ping Stats: Success (12.127ms)
Session Info:
session_id: 0
host_number: 0
bus_number: 0
target_id: 0
Similar Messages
-
Windows 7 answer file deployment and iscsi boot
Hi, I am trying to prepare an image with windows7 Ent that has been installed, went through "audit" and then shutdown with:
OOBE+Generalize+Shutdown
So that I can clone this image and the next time it boots, it will use answer file to customize, join domain etc.
The complication to this - is that I am using iscsi boot for my image, and working within Vmware ESX.
I can install Windows without any issues, get the drivers properly working, reboot and OOBE on the same machine - no issues.
The problems come when I clone the VM and the only part that changes (that I think really matters) is the mac address of the network card. The new clone when it comes up after the OOBE reboot hangs for about 10min and then proceeds without joining to domain.
Using Panter logs and network traces - I saw that the domain join command was timing out and in fact no traffic was being sent to the DC. So the network was not up. The rest of the answer file customization works fine.
As a test I brought up this new clone (with new mac) in Audit mode - and Windows reported that it found and installed drivers for new device - VMXNET3 Driver 2. So in fact it does consider this a new device.
Even though it iscsi boots from this new network card - later in process its unable to use it until driver is reinstalled.
In my answer file I tried with and without below portion but it didnt help:
<settings pass="generalize">
<component>
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>
I also tried with E1000 NIC, but couldnt get windows to boot properly after the cdrom installation part.
So my question - is my only option to use workarounds like post OOBE scripts for join etc?
Is it possible to let Windows boot and then initiate an extra reboot once the driver was installed and then allow it to go to Customize phase?
thank you!Hi,
This might be caused by the iscsi boot.
iSCSI Boot is supported only on Windows Server. Client versions of Windows, such as Windows Vista® or Windows 7, are not supported.
Detailed information, please check:
About iSCSI Boot
Best regards
Michael Shao
TechNet Community Support -
Windows 2008 R2 iSCSI Boot LUN - NIC driver issue
Hello,
I've gotten the opportunity to create a win2k8r2 golden image that will be deployed to IBM3650 M3's over
iSCSI boot LUNs. I have a need to update the on-board Broadcom 1Gb NICs from the drivers that come with the installation media. I am able to load the drivers that I need without any issue, the system survives multiple re-boots and displays the expected driver
version via device manager. After I prepare the image I run sysprep, sysprep runs smoothly and the system shuts down as expected. At this point I unmap the existing LUN and clone the sysprep'ed image out.
This is where I run into trouble, if I update to the latest Broadcom driver the OS fails to boot, the host
logs into the LUN successfully and I get the Windows splash screen after a bit the screen goes black and I get no response from windows at all. With this behavior I would generally expect that there is some issue with my unattend file but if I don't upgrade
the driver there are no problems, windows boots normally, and the post install process runs successfully. After some digging I saw that I might be running into KB974072. Just as the article suggested I inserted the necessary drivers into the installation
media. Unfortunately this produced the same result.
I've got PersistAllDeviceInstalls set to "true" in the generalize pass of the unattend so sysprep
should not be making any changes to the drivers. If anyone has any ideas on what else, if anything, I can put in the unattend to get sysprep to leave the drivers alone or any thoughts on this issue at all I would greatly appreciate it!
Regards,
Toll_Hou5eHi,
First, try to set the registry key before capture the image.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp set
PersistAllDeviceInstalls to
1.
If it doesn’t work, we can try another to way, inject driver packet during installation.
Managing and Deploying Driver Packages
http://technet.microsoft.com/en-us/library/dd348456(v=ws.10).aspx
Hope this helps. -
I have a server with Intel 82576 Gigabit Dual Port Nics. I have configured them to use iSCSI boot the primary looks to 10.0.0.1/24 and the secondary looks to 10.0.1.1/24. The target is configured correctly. Everything boots as expected.
I have added the MPIO feature and configured MPIO for the iscsi initiator as per: http://blogs.technet.com/b/migreene/archive/2009/08/29/3277914.aspx.
My issue is that the iSCSI networks show up in the routing table like so:
I did not configure a default route in the Intel setup utility:
I tried to explicitly remove the 0.0.0.0 entry and leave blank, with no change. As you can see with the above routing table traffic attempts to travel over these routes:
C:\Users\Administrator>ping google.com
Pinging google.com [209.85.145.99] with 32 bytes of data:
Reply from 10.0.0.201: Destination host unreachable.
Reply from 10.0.1.201: Destination host unreachable.
Reply from 209.85.145.99: bytes=32 time=23ms TTL=51
Reply from 209.85.145.99: bytes=32 time=22ms TTL=51
Ping statistics for 209.85.145.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
A ping to the outside world first attempts on 10.0.0.x/24 network, then on 10.0.1.x/24 network and then finally on the network the traffic should go over. I don't want my iSCSI traffic to ever show up with a default route. How do I get rid of it?
route delete 0.0.0.0 mask 0.0.0.0 "on-link" results in: The route deletion failed: The parameter is incorrect.
route delete 0.0.0.0 mask 0.0.0.0 on-link results in: The route deletion failed: The parameter is incorrect.
route delete 0.0.0.0 deletes all default routes, then I have to add back in the "valid default route" of 192.168.100.6.
I would like to not have to do a route delete though.So I've sort of given up on fixing the gateway assignment in the route for iSCSI boot. I configured a DHCP server to give out the information required by iSCSI boot and configured the network cards to use DHCP for their configuration. I insured
that my DHCP server gave out no default gateway entry. However, I still got the undesired routes in the routing table. This makes me assume that there isn't a "fix" for it, only the workaround.
Here is the script I run on each iSCSI Boot initiator (you would obviously change the ip number to suit your environment):
@Echo off
Rem fixes iscsi route problem as shown below:
Rem IPv4 Route Table
REM ===========================================================================
REM Active Routes:
REM Network Destination Netmask Gateway Interface Metric
REM 0.0.0.0 0.0.0.0 On-link 10.0.0.200 10255
REM 0.0.0.0 0.0.0.0 On-link 10.0.1.200 266
REM 0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.98 266
REM The top 2 lines are on the iscsi interface and traffic tries to go out it
REM We need to delete the routes, so we'll just delete all gateway routes and
REM add back in the one we care about.
route delete 0.0.0.0 >c:\iscsibootroutefix.log
route -p add 0.0.0.0 mask 0.0.0.0 192.168.100.6 >>c:\iscsibootroutefix.log
After running it I get:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.98 11
10.0.0.0 255.255.255.0 On-link 10.0.0.200 10255
10.0.0.1 255.255.255.255 On-link 10.0.0.200 10255
10.0.0.200 255.255.255.255 On-link 10.0.0.200 10255
Then I added a task in “task scheduler” of "administrative tools" that ran as the user “system” “when the computer starts” that runs this script. -
Service Template and iSCSI Boot Parameters
Hello,
I use updating service templates to ensure all service profiles are the same and it works great. We have recently setup a Nimble storage array and for iSCSI boot you have to put the target of of the boot LUN in the iSCSI boot parameters. However as each profile will have to boot from a different volume. This causes an issue as I cant change a service profile that is bound to a service template and i need the profiles to have differnt boot volumes.
Am I missing something here.
ThanksThe service profile requires two different IQNs one for the initiator/server and one for the target/storage_array. What I’m saying is that each initiator needs to have a different IQN but all of them can use the same target IQN to communicate to the storage.
If you are using an updating template to update all of the service profiles, any change you make there will be propagated to all of the service profiles that were created from this template, which means that you can only make changes to the template and not directly to the service profiles unless you unbind them from this template.
The main thing you need to understand is that if you use the same target IQN it doesn’t mean that all of your server are going to try to boot to the same LUN as long as you group their IQN (initiator) to a dedicated LUN on the storage array.
Let me kwow what you think
iSCSI
http://en.wikipedia.org/wiki/ISCSI -
ISCSI Booting Win2k8R2 on UCS with EqualLogic
We've been testing iSCSI booting on UCS with 2.0(1t) and the Palo M81KR with an EqualLogic PS6010. We are connecting through a 10GbE switch via an uplink port. However, we've hit a snag and want to see if anyone else has gotten around this.
The EQL shows connections from UCS when booting; however, Windows does not have the Palo drivers and doesn't show the target disk. When adding the M81KR driver, the connection gets dropped so Windows still does not show the target disk.
We've tried connecting the array directly to an appliance port on the FI but got some ENM source pinning failed error, a different issue at this point.
We've also tried slipstreaming all UCS drivers into the Windows media but that doesn't let us proceed either.
We've gotten RHEL6 to install so we know the configuration is viable.Hello Thomas,
The EQL shows connections from UCS when booting; however, Windows does not have the Palo drivers and doesn't show the target disk. When adding the M81KR driver, the connection gets dropped so Windows still does not show the target disk.
There is small trick to make the target disks visible after installing the right drivers. Please make sure that after re-mapping the W2K8 ISO image, click Refresh button on the Installer screen and verify the outcome.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/windows/install/2008-vmedia-install.html#wp1059547
Driver location in driver ISO image
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/b/os/windows/install/drivers-app.html#wp1014709
Padma -
ISCSI boot support on vic P81e
Hi,
Is it supported to use P81e for iSCSI boot on C200M2?
Last time I know that it's not supported and there was saying that it's on roadmap. I can't seem to find the release notes for it.
If it's already supported, what version of c-series software do I need to use?
thanksAccording to the support matrix, it's not supported.
http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/interoperability/matrix/r_hcl_B_rel2-21.pdf
my 2c
- even the VIC1225 doesn't show any iSCSI Boot support
- the VIC1225 is a prerequisite for single wire management, therefore I doubt, that there will be a lot of new driver development going on for P81e; Cisco PM please clarify ! -
Excited about iSCSI Boot in 2.0?
Having been booting from SAN and not always loving it, wondering how others feel about iSCSI boot in 2.0? To me this is a game changer. WAY EASIER.
Is anyone doing it? Feedback?
CraigI've set it up for one customer and found it much harder to get working than FC boot, although it has worked perfectly since it was set up and now I know how to set it up would find it easier in future. The official documentation on getting it up and running is poor, although there is a very useful document posted in the documents section of the forum that does help. There is also a good guide in the partner website.
One major limitation is that you cannot use iSCSI boot when your service profiles are bound to a template as the iqn initiator value is not pooled. I will not be considering iSCSI boot for upcoming designs until this is resolved, although a change is planned I hear.
vSphere 5 is also not currently supported with iSCSI boot.
FInally there is a known issue listed in the release notes saying that the secondary iSCSI vnic cannot be used. Possibly a single point of failure concern.
So all in all, iSCSI boot is a welcome enhancement for me but still needs a bit of work to make it reay for prime time. -
Ucs blade iscsi boot cannot install windows server
Hi all,
i have some problem when i try to install windows server 2008 in nexenta storage using iSCSI via ucs b-series, but its working fine when i install ESXi 5.5. i cannot find drive on windows server installation, and in ESXi i can see all LUN what im create before in nexenta storage and working when i install it.
this vnic iSCSI Configuration:
vnic_id: 13
link_state: Up
Initiator Cfg:
initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
vlan: 0
dhcp status: false
IQN: test:iqn.2014-11.com.:8
IP Addr: 192.168.1.59
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.5
Target Cfg:
Target Idx: 0
State: ISCSI_TARGET_READY
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_NO_ERROR
IQN: iqn.2010-08.org.illumos:02:windowsboot
IP Addr: 192.168.1.49
Port: 3260
Boot Lun: 6
Ping Stats: Success (986.646ms)
Session Info:
session_id: 0
host_number: 0
bus_number: 0
target_id: 0
does anyone can help me to solve this issue?
thanks in advance - fadlienic / fnic driver have to be installed; they are not part of any Windows OS.
they can be found in
Downloads Home
Products
Servers - Unified Computing
UCS B-Series Blade Server Software
Unified Computing System (UCS) Drivers-2.2(3)
ISO image of UCS-related drivers
ucs-bxxx-drivers.2.2.3.iso
depending on the UCS version. -
I am having trouble with getting this to work. I don't control the iSCSI side of the equation so I am just trying to make sure everything is correct on the UCS side. When we boot we get an the "Initialize error 1"
If I attach to FI via ssh I am able to ping the target ip's. The SAN administrator says that the UCS has to register before itself (which isn't occuring) prior to him giving it space. Everything I have seen the LUN's and Mask are created prior to boot...is this required?
Thanks,
JoeUCSM version
2.0(2r)
We have another blade the other chasis that has ESX installed on the local drive and is using the iSCSI SAN as it datastore, therefore I know I connectivity to the SAN. The storage array is a emc CX4-120.
adapter 2/1/1 (mcp):1# iscsi_get_config
vnic iSCSI Configuration:
vnic_id: 5
link_state: Up
Initiator Cfg:
initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
vlan: 0
dhcp status: false
IQN: iqn.1992-04.com.cisco:2500
IP Addr: 192.168.0.109
Subnet Mask: 255.255.255.0
Gateway: 192.168.0.2
Target Cfg:
Target Idx: 0
State: INVALID
Prev State: ISCSI_TARGET_GET_SESSION_INFO
Target Error: ISCSI_TARGET_LOGIN_ERROR
IQN: iqn.1992-04.com.emc:cx.apm00101701431:a2
IP Addr: 192.168.0.2
Port: 3260
Boot Lun: 0
Ping Stats: Success (19.297ms)
Target Idx: 1
State: INVALID
Prev State: ISCSI_TARGET_GET_SESSION_INFO
Target Error: ISCSI_TARGET_LOGIN_ERROR
IQN: iqn.1992-04.com.emc:cx.apm00101701431:b2
IP Addr: 192.168.0.3
Port: 3260
Boot Lun: 0
Ping Stats: Success (18.229ms)
adapter 2/1/1 (mcp):2# -
Local Disk Configuration Policy iSCSi Boot
Is it a requirement for this to work to pull out the local disksif they are present? I am using the "Any configuration". with a local disk present.
Atle,
What is the OS being installed, windows?
./Abhinav -
Windows not booting after install (iSCSI)
Hi all,
I am attempting to boot a host over iSCSI but have run into a brick wall trying to get my host to boot after successfull install of the OS.
Without changing the service profile I am able to install and boot VMWare ESX fine. Windows just does not seem to boot.
I can see the iSCSI subsystem is working ok when I connect to the adapter:
SUNINT0001PB-A# connect adapter 4/5/1
adapter 4/5/1 # connect
adapter 4/5/1 (top):1# at
attach-fls attach-mcp
adapter 4/5/1 (top):1# attach-mcp
adapter 4/5/1 (mcp):1# is
iscsi_get_config iscsi_ping
adapter 4/5/1 (mcp):1# iscsi_get_config
vnic iSCSI Configuration:
vnic_id: 6
link_state: Up
Initiator Cfg:
initiator_state: ISCSI_INITIATOR_READY
initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
vlan: 0
dhcp status: false
IQN: iqn.1992-08.cisco.com:irfjmp0003pb
IP Addr: 10.250.137.214
Subnet Mask: 255.255.255.0
Gateway: 0.0.0.0
Target Cfg:
Target Idx: 0
State: ISCSI_TARGET_READY
Prev State: ISCSI_TARGET_DISABLED
Target Error: ISCSI_TARGET_NO_ERROR
IQN: iqn.1992-08.com.netapp:sn.1574897996
IP Addr: 10.250.137.9
Port: 3260
Boot Lun: 0
Ping Stats: Success (20.486ms)
Session Info:
session_id: 0
host_number: 0
bus_number: 0
target_id: 0
Regards
AdamNow it gets even stranger. As suspected the configuration is correct as I now have it booting into windows.
The strange part is, all was working ok until I applied all current updates, then it went into windows recovery mode and can't find my partition for recovery (only option I have is to reboot)
Have no idea what happened, so I re-installed. Re-installed ok, but the same problem as before, no boot volume found.
Re-installed again, but this time I released the windows boot media from the virtual CDROM drive while it was rebooting.
Windows booted sucessfully.
Very Strange. -
I have a C200 M2 server with BCM5709 ethernet card, I am trying to find the drivers to load windows server 2008 R2. I am trying to install to an iSCSI SAN, the LUNS and volumes are all configured as they were just running VMWare, the iSCSI boot is setup on the 5709 card, just dont have drivers to load at the "where to do you want to install windows" screen. have tried all the drivers I can find on the Cisco site. any suggestions.
Thomas,
You can download the drivers CD here
http://www.cisco.com/cisco/software/release.html?mdfid=283860950&flowid=25801&softwareid=283853158&release=1.3%282a%29&relind=AVAILABLE&rellifecycle=&reltype=latest
Driver file location
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/os/install/drivers-app.html#wp1014709
W2K8 SAN installation procedure
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/os/install/2008-vmedia-install.html#wp1053494
HTH
Padma -
Hi,
We are exporting bootable LUNS from a 7110 array to LDOM's on our Blades. The array was rebooted today. Since the reboot we are unable to connect to the hosts booted from the array.
I did not configure this but have the task of fixing it.....
We are running LDOM 1.2,REV=2009.06.25.09.48
So, does the LDOM boot directly from the LUN from the LDOM OBP?
The syntax in this link causes the below failure;
http://wikis.sun.com/display/OpenSolarisInfo/Configuring+iSCSI+Boot+for+SPARC+Systems
Unknown key 'iscsi-target-ip'
Unknown key 'iscsi-target-name'
Unknown key 'iscsi-lun'The ISCSI LUNS are seen by the host.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
/pci@0/pci@0/pci@2/LSILogic,sas@0/sd@0,0
1. c1t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 32 sec 279>
/pci@0/pci@0/pci@2/LSILogic,sas@0/sd@2,0
2. c3t600144F04B73EB660000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 736>
/scsi_vhci/ssd@g600144f04b73eb660000000000000000
3. c3t600144F04B713A260000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 736>
/scsi_vhci/ssd@g600144f04b713a260000000000000000
4. c3t600144F04B9910370000000000000000d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 1200>
/scsi_vhci/ssd@g600144f04b9910370000000000000000Nothing has changed on the LDOM controller domain.
I'm really stuck so any input would be appreciated.Im getting the following error as well.. Was there any solution to this please ?
Im not using any LDOM. Just on the h/w platform on T5140
{0} ok boot net Boot device: /pci@500/pci@0/pci@8/network@0 File and args:
Unknown key 'iscsi-target-ip'
Unknown key 'iscsi-target-name'
Manual Configuration: Host IP, boot server and filename must be specified
ERROR: boot-read fail
Can't open boot device
{0} ok
Edited by: 836793 on Feb 15, 2011 12:36 AM -
ISCSI- Adding iSCSI SRs to XS booting via iSCSI [Cisco UCS]
Hello all-
I am currently running XS 6.0.2 w/ HF XS602E001 & XS602E002 applied running on Cisco UCS B200-M3 blades. XS seems to be functioning ok, except that i cannot see the subnet assigned to my SAN, and as a result, i cannot add any SR for VM storage.
The subnet and vNIC that i am configuring is also used for the iSCSI boot.
The vNIC is on LAN 2 and is set to Native
The SAN is a LeftHand P4300 connected directly to appliance ports (LAN2) on the Fabrics
Used the following commands during installation to get the installer to see the LUN.
echo "InitiatorName=my.lun.x.x.x" > /etc/iscsi/initiatorname.iscsi
/opt/xensource/installer/init --use_ibft
If i missed anything or more info is needed, please let me know.Thanks Padramas,
I have 2 NICs that show up in XenCenter. Nic A is the vNIC associated with VLAN1 and provide the uplink to the rest of the network. The second NIC in XenCenter matches the MAC of the vNIC used to boot XenServer, so the NIC used for booting the OS is visible in XenCenter.
I have tried many different thing on my own to resolve this issue. I believe i have already tried adding a 3rd vNIC to the service profile for VM iSCSI traffic, but with make another attempt.
When configuring the vNIC for VM iSCSI traffic, do I only need to add the 3rd vNIC, or do i need to create both a vNIC and second iSCSI vNIC with Overlay vNic pointing to newly created (3rd) vNIC? My understanding is that the iSCSI vNICs are only used for booting, but I am not 100% sure.
Thanks again for the help!
Maybe you are looking for
-
One day the phone just got stuck on ios6 screen then once unlocked it said plug into iTunes. Once I did the phone will not allow me to complete a restore. At the last stages the phone will cut off. I have asked a friend to have a look and he thinks i
-
MS Word Track Changes and Acrobat Merge into a Single PDF
I am using Word 2007 to create a group of about 50 files that are being collected with Acrobat 9 Standard Merge Files Into a Single PDF feature. I need to control whether the track changes in the word files are carried over to the PDF. Said another
-
Photo Booth makes others apps crash in Snow Leopard when exporting pics.
I use PhotoBooth to take pictures of patients and I put the pictures in Word documents or in a Filemaker database. In Tiger, all we needed to do was drag the picture from Photo Booth directly in our app. Since upgrading to SL 10.6.1, if we attempt th
-
Move Item List in BLOG to new BLOG keep All Enterprise Keywords and Comments.
Hello, I'm new on SharePoint Server 2010. I need a help please. I create Site on BLOG Template. So in my site has a List name POSTs. And I enable Enterprise Keyword on that List. I use this blog and one day,My Posts now has an Error. The structure is
-
I have a Dell Dimension 8200 with windows XP Pro (SP3). i would like to update to the latest version of flash player. Question: I would like to manually download the latest flash player so that I can install it after disconnectiing from the internet