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?
Craig

I'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.

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

  • ISCSI boot with Intel NICs added to windows 2008 r2 routing table causes non iscsi traffic to attempt default routes on iscsi networks

    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.

  • 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_Hou5e 

    Hi,
    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 was so excited about apple pay and now setting it up hoping to replace a wallet within next year or so and then boom 8 cards you are done! Come on Apple 8 cards is that what you call wallet replacement?

    I was so excited about apple pay and now setting it up and boom 8 cards and you are done is that the wallet replacement they thought they'll do? really? I mean most people have 10-15 cards at least and I am, well because of my side business I have lots so 8 is nothing to me!

    Not sure what you are saying.  I was able to very quickly set up my AmEx card - no problems at all.  For my PNC and Macy's cards, companies still working on being ApplePay-ready. 
    It will happen, just not as fast as we might like, but I think it is going to be fabulous. 

  • 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.
    Thanks

    The 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

  • Very excited about the new update - Thanks Apple for the keyboard update with new emojis! But why are there no ethnicity options for the families?

    Very excited about the new update - Thanks Apple for the keyboard update with new emojis! But why are there no ethnicity options for the families?

    D.p.middleton the Adobe Application Manager has been available for quite some time.  It not only allows Creative Cloud users to install their applications but also downloads and applies applicable updates.  In addition it is also responsible for the licensing and managing your agreement to the terms and conditions of the EULA.
    2. this could be due to you selecting a trial subscription to the Creative Cloud?  If you go to one of the Adobe Creative products and select Help>Updates it will launch the update portion of the Adobe Application Manager which I believe is the portion you are looking for?
    #3 I believe this was already mostly covered in the answer to #2.
    #4 the Adobe Application Manager also receives periodic updates which affects both perpetual and Creative Cloud subscription users.
    I hope this provides you many of the answers you are looking for?  If not please feel free to respond back with any additional inquiries which you have.  Also if you are experiencing any difficulties with the update process please post this as well.  It may not be necessary to have a full understanding of the inner workings of the Adobe Application Manager to help you resolve your difficulties.

  • 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?
    thanks

    According 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 !

  • 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

  • Microsoft Windows (7) boot from (native) VHD : Question about missing boot (flag) on active primary partition

    Hi!
    First, where can I post queries about native VHDs on Windows 7?
    I see VHD Native Boot and Driver Cloning  in Windows Desktop Development forums >  General
    Windows Desktop Development Issues,
    (when I navigate there the option's N/A, http://i.imgur.com/9Vj7tPJ.png )
    I've finally copied my VHD(s), and tested the copies by adding BCD(edit) entries, pointing to the new VHD's. 
    I had a failure with a native VHD. I managed to copy the VHD file from the (internal) HD, before cleaning the HD and restarting from scratch (new vdisk created and attached, win7 reinstalled).
    The original VHD ('Win7VHD') is still working, but won't boot (see mounted Disk 3 (I:), compared to the active,
    bootable partition (C:).
    http://i.imgur.com/KXU0QWi.png
    Before creating a fresh install on the new, clean "VHD (Win7)" volume, I tried lots of things to fix the "won't boot" issue with the VHD (rebuild MFT, fixBR... without ever knowing exactly what I was doing :()
    So I've created a BCD entry for the recovered VHD... now, can I make it bootable again?
    (I don't know what the root of the bootable VHD has to contain)
    (Thanks in advance to all you cool cats :)

    Try this forum:
    http://social.technet.microsoft.com/Forums/windows/en-US/home?forum=w7itprogeneral

  • 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 - fadli

    enic / 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.

  • Excited about WP7 and Nokia!

    I can't wait to buy a WP7 phone by Nokia!
    I'm so excited to hear that Nokia will be allowed to leverage its core competencies on Microsoft's platform.
    No doubt, this means that WP7 will have Nokia's pop-up error messages on top of Microsoft's pop-up error messages. I love pop-up error messages! You can never have too many of those. The more incomprehensible, the better!
    Get ready for a Windows Vista experience on your phone! Like Vista, the Nokia-WP7 will be extremely stable and secure. To launch an application, you just tap on the icon, then tap "allow" on a series of Nokia's pop-up messages asking if you are sure you want to launch the application, let the application access your data, let the app connect to the internet, let the app connect to the GPS, and whether you want to accept the app's certificate this time only. After that, you will get the same pop-up messages again, only this time they will be from Microsoft!

    All joking aside, the sad thing about this is that Nokia just recently, finally understood one of the two things that are of crucial importance to consumers: apps.
    But Microsoft has never understood this and continues to treat app developers like dirt. An example of this is that if the developer does not reside in one of the 18 countries in Microsofts "supported countries" list, they are NOT ALLOWED to develop apps for WP7 or XBOX even if they wanted to. Where's the sense in this? Countries that are not supported include Finland, the country where Nokia's headquarters are located! In unsupported countries, customers are not even allowed to buy or install apps, as access to Microsoft's Marketplace is blocked.
    Now Nokia's Qt environment, which has received nothing but praise from developers, is going down the drain with Symbian.
    Neither Nokia nor Microsoft has ever fully understood the second thing that is of crucial importance to consumers: usability. People want their phones to "just work" without having to go through dozens of nested menus to specify cryptic settings like "certificates" and "proxy servers", when all they want is to connect to the wifi network at their university or workplace. (Of course, this is currently a problem only in Symbian phones, as wpa2 enterprise is not supported on WP7 at all.)

  • Installed win 7 in my imac but not about to boot up

    hi, installed win 7 to my imac recently but keep entering a blank screen with a blinking underline....anyone can help?

    hey,
    If yur mac loads till that blank screen instead of going to the Apple OS, we can think that windows partition was working good, But if the boot up of Windows stops at the blank screen wid oly tht underline tht shows a prob in booting of windows, mght yur installation was not done properly try reinstalling yur Windows and before know about whether yur configuration is supported for windows 7..!!!!
    Dont Mind if anything was wrong, its my opinion..!!!

  • Cisco UCS iSCSI boot question

    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,
    Joe

    UCSM 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#

Maybe you are looking for

  • Refresh data source view gets 'column' argument cannot be null

    When I try to refresh a data source view in SQL Server 2008 BIDS, I get the error: System.Data   'column' argument cannot be null.  Parameter name: column.   How to resolve this?  The underlying tables have no data yet.

  • Displaced content from sender RFC in payload - PI 7.0

    Hello, we have a strange behaviour here. After implementing a scenario with  HTTP->PI->RFC which works fine transporting a structure to an R/3, we wanted implement another scenario RFC->PI->HTTP (RFC is async). Problem when testing it: The RFC hands

  • Pls help in performance tuning SQL

    Hi All, Can someone please help me to tune this quesry. Rt now it is takin 20 mins tro retuns 80,000 rows and its using dblink SELECT COUNT(*) FROM (SELECT /*+driving_site(main)*/CORP_ACTG_PRD_YEAR, CORP_ACTG_PRD_NBR, FCN_CODE, LOCAL_CRNC_CODE, GL_LO

  • I can,t open the files with my Adobe ID

    I trent change my adobe ID but, i don,tnothing

  • ABAP Dump ASSIGN LENGTH 0 SAPLSNR3 LOCAL Buffer - BI content installation

    Hi all, I get the following ABAP dump while installing the BI content and choosing the grouping ' in dataflow before' in Bi 7.0 SP 13 Short text                                                                  Program error: ASSIGN with length 0 in p