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 !

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

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.

Boot-support-partition nach bedarf für das Volume aktualisieren

Seit Sonntag erkennt mein MacBook Pro (13" Mid 2010/OSX 10.6.8) leider meine externe Festplatte (WD Elements 2TB) nicht mehr. Mir wurde geraten das Festplattendienstprogramm zu verwenden um die Platte zu reparieren. Nun steht seit 48 Stunden folgender Satz "boot-support-partition nach bedarf für das volume aktualisieren" da und die Leiste läuft immer noch. Das heißt das Programm hat sich nicht aufgehängt.
Was soll ich tun?
Ist es normal, dass es so lange läuft oder soll ich die Reparatur stoppen?
Danke für die Hilfe.
Here in English:
Since Sunday, my MacBook Pro (13 "mid 2010/OSX 10.6.8) unfortunately does not list my external hard drive (WD Elements 2TB) no longer. I was advised to use the Disk Utility to repair the disk. Now available for 48 hours following sentence" support boot partition needs to update the volume "and because the bar is still running. this means that the program has not hanged.
What should I do?
Is it normal for it as long runs or should I stop the repair?
Thanks for the help.

Moin moin,
ich habe ebenfalls eine Neuinstallation durchführen müssen, allerdings unter MacOSX (Yosemite). Das Problem ist hier aber identisch, die Fehlermeldungen haben zwar eine andere Optik ;-) aber inhaltlich sagen sie das Gleiche. Auf der Download-Seite von Adobe habe ich ein Update für Photoshop auf 11.02. und Fireworks auf 10.0.4.1 gefunden, mehr aber nicht. Acrobat Pro 9.X gibt's nicht und z. B. Dreamweaver funktioniert nicht!
Wenn ich was vom Adobe-Support höre, melde ich mich wieder.

Hi, Had boot issue and got the following from DU repair function on Macintosh hd: updating boot support.....Error: Disk utility can't repair this disk.....reformat and restore backed up files. How is that done or do I go to Genius?

In reference to question the computer gave no warning but lost internet connectivity. I shut down for a while and when returned it would only boot to gray logo screen with spinning gear. Ran disk utility and on Mac HD drive it stopped after "Updating boot support partitions as required". Then in red: Error: Disk utility can' repair this disk ....disk, and restore backed up files. I'm running OS X 10.8 and had just updated the iOS about three days ago. Not familiar with reformat process on MacBook Pro and would like some ideas whether I should go to the Genius Bar here in Sydney or try it on my own. I have been using time machine to back up to a 1TB La Cie drive right up to the crash. Thanks for any advice.

Well it turned out the drive was shot. Took it to the genius bar yesterday and they ran a test on the drive before trying the restore routine again. Drive failed.
Replaced the drive and got the MBP back today. Pretty quick and decent service once you get an appointment.
Now having trouble figuring how to do the Time Machine saved files. Have several applications which I'd like to keep but not sure how to trans the apps from my backup to the new. Hunting for answers on that on the web.
Thanks for you help, Eustace.

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.

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.

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

Disk Utility stuck on "updating boot support partitions for the volume as required"

Tonight when I mounted my Time Machine drive (a WD My Passport drive), it failed to mount properly, and I received a warning from Drive Genius that it needed repair. But when I launched Drive Genius, the disk would not show up.
Through a series of mounts, unmounts, and sleeping the computer, I managed to get it to show up in Disk Utility, so I seleted "Time Machine Backups" under the main listing for the drive ("319.37GB WD My Passort..."), and clicked Repair.
The detail window showed "Volume repair complete" almost immediately. But for almost four hours now, it's been stuck on "Updating boot support partitions for the volume as required."
Meanwhile, Activity Monitor has been showing fsku_hfs taking 30%-85% of the CPU the whole time.
Anyone have advice?

Apparently not:
Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
But when I ran Disk Utility again this morning, not on the Time Machine Backup, but up the hierarcy on the level labeled "319.37GB WD My Passort...," I got...
The volume Time Machine Backups appears to be OK.
And now the drive seem to be OK.
I think I'll still offload everything and reformat it.

Update Boot Support Partitions, how do I do that??

I have just carried out a Disk Repair on MBP and "Repaired Successfully" message came up but it is asking to "Update Boot Support Partitions", can someone tell me how I do that please??

With the Error 2, let's try a standalone Apple Application Support install. It still might not install, but fingers crossed any error messages will give us a better idea of the underlying cause of the issue.
Download and save a copy of the iTunesSetup.exe (or iTunes64setup.exe) installer file to your hard drive:
http://www.apple.com/itunes/download/
Download and install the free trial version of WinRAR:
http://www.rarlab.com/
Right-click the iTunesSetup.exe (or iTunes64Setup.exe), and select "Extract to iTunesSetup" (or "Extract to iTunes64Setup"). WinRAR will expand the contents of the file into a folder called "iTunesSetup" (or "iTunes64Setup").
Go into the folder and doubleclick the AppleApplicationSupport.msi to do a standalone AAS install.
Does it install properly for you?
If instead you get an error message during the install, let us know what it says. (Precise text, please.)

USB Boot support for K7N420 Pro???

Would it be possible for the BIOS release to include USB Boot support?
This way you could use a lot of bootable USB peripherals (USB Flash DIsk for example) and you wouldn't need your FDD anymore.
Can this be done?
Best regards,
Pulsar

newer boards have begun to incorporate this bios feature.

Macbook not booting up so I resorted to Disk Utility...it has been stuck on "updating boot support partitions for the volume as required"

So my Macbook was not booting up so I resorted to using Disk Utility...it has been stuck on "updating boot support partitions for the volume as required" for over two days.
Has anyone else had to wait this long?
I have read that I should leave it until I get another message but I saw this reply on another site....
"Hi everybody, the message: “Updating boot support partitions for the volume as required.“ means: the Disk Utilities is telling you what it is doing: 'Disk Utilities': "(I'm) Updating boot support partitions for the volume as required (& I'm done with it)." So when you see this message, the DS (Disk Utilities) is done & you can close the application"...
Any advice/tips would be greatly appreciated!

Doesn't have to be another MacBook - any Mac with FireWire (400 or 800) will do. FW 400 to 800 adapters or adapter cables should be available from any computer store.
Instructions for FWTDM -
Disconnect all other FireWire devices from both computers before you use FireWire target disk mode. Do not connect any FireWire devices until after you have disconnected the two computers from each other or have stopped using target disk mode.
To use FireWire target disk mode
    1.    Make sure that the target computer is turned off.
    2.    If you are using an Apple portable computer such as a PowerBook or MacBook as the target computer, plug in its AC power adapter.
    3.    Use a FireWire cable to connect the target computer to a host computer. The host computer can be powered on.
    4.    Start up the target computer and immediately press and hold down the T key until the FireWire icon appears. The hard disk of the target computer should become available to the host computer and will likely appear on desktop. (If the target computer is running Mac OS X v10.4 Tiger, you can also open System Preferences, choose Startup Disk, and click Target Disk Mode. Restart the computer and it will start up in Target Disk Mode.)
    5.    When you are finished copying files, locate the target computer's hard disk icon on the desktop of the host computer and drag it to the Trash or choose Eject (or Put Away) from the File menu.
    6.    Press the target computer's power button to turn it off.
    7.    Unplug the FireWire cable.
(extract from http://support.apple.com/kb/HT1661)

PXE boot support for Xen PV -- OVM 3.1.1

I thought with 3.1.1 PXE boot support would be included for full PV vm install. Has someone achieved this?

No problem ... found my answer here : Is it possible to install PVM without DHCP in local network?

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

ISCSI boot support on vic P81e

Similar Messages

Maybe you are looking for