Live Migration failed using virtual HBA's and Guest Clustering
Hi,
We have a Guest Cluster Configuration on top of an Hyper-V Cluster. We are using Windows 2012 and Fiber Channel shared storage.
The problem is regarding Live Migration. Some times when we move a virtual machine from node A to node B everything goes well but when we try to move back to node A Live Migration fails. What we can see is that when we move the VM from node A to B and Live
Migration completes successfully the virtual ports remain active on node A, so when we try to move back from B to A Live Migration fails because the virtual ports are already there.
This doesn't happen every time.
We have checked the zoning between Host Cluster Hyper-V and the SAN, the mapping between physical HBA's and the vSAN's on the Hyper-V and everything is ok.
Our doubt is, what is the best practice for zoning the vHBA on the VM's and our Fabric? We setup our zoning using an alias for the vHBA 1 and the two WWN (A and B) on the same object and an alias for the vHBA 2 and the correspondent WWN (A and B). Is it
better to create an alias for vHBA 1 -> A (with WWN A) and other alias for vHBA 1 -> B (with WWN B)?
The guest cluster VM's have 98GB of RAM each. Could it be a time out issue when Live Migration happen's and the virtual ports remain active on the source node? When everything goes well, the VM moves from node A with vHBA WWN A to node B and stays there
with vHBA WWN B. On the source node the virtual ports should be removed automatically when the Live Migration completes. And that is the issue... sometimes the virtual ports (WWN A) stay active on the source node and when we try to move back the VM Live Migration
fails.
I hope You may understand the issue.
Regards,
Carlos Monteiro.
Hi ,
Hope the following link may help.
To support live migration of virtual machines across Hyper-V hosts while maintaining Fibre Channel connectivity, two WWNs are configured for each virtual Fibre Channel adapter: Set A and Set B. Hyper-V automatically alternates between the Set A and Set B
WWN addresses during a live migration. This ensures that all LUNs are available on the destination host before the migration and that no downtime occurs during the migration.
Hyper-V Virtual Fibre Channel Overview
http://technet.microsoft.com/en-us/library/hh831413.aspx
More information:
Hyper-V Virtual Fibre Channel Troubleshooting Guide
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
Hyper-V Virtual Fibre Channel Design Guide
http://blogs.technet.com/b/privatecloud/archive/2013/07/23/hyper-v-virtual-fibre-channel-design-guide.aspx
Hyper-V virtual SAN
http://salworx.blogspot.co.uk/
Thanks.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Similar Messages
-
When I migration the virtual machine with synthetic FC HBA in windows server 2012 R2 Cluster,it fails
but I do it in the style of quick migraton ,it secceed!
The error event here
Live migration of 'Virtual Machine PTSCSQL01' failed.
Virtual machine migration operation for 'PTSCSQL01' failed at migration destination 'PTCLS0106'. (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
'PTSCSQL01' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
'PTSCSQL01' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID B8FBDE64-FF97-4E9B-BC40-6DCFA09B31BE)
My virtual machine's synthetic FC HBA setting here
做微软的先行者,享受用户体验Yes, definitely check your zoning/masking. Remember that with vHBA you have twice as many WWPNs to account for. Performing a live migration makes use of both pairs during the transfer from one host to the other - one set is active on the machine
currently running and the second set is used to ensure connectivity on the destination. So if you are using Address Set A on Host1, Host2 will try to set up the fibre channel connection using Address Set B. If you do a quick migration, you would
continue to use the same Address Set on the second host. That's why you most likely need to check your zoning/masking for the alternate set.
. : | : . : | : . tim -
I am unable to live migrate via SCVMM 2012 R2 to one Host in our 5 node cluster. The job fails with the errors below.
Error (10698)
The virtual machine () could not be live migrated to the virtual machine host () using this cluster configuration.
Recommended Action
Check the cluster configuration and then try the operation again.
Information (11037)
There currently are no network adapters with network optimization available on host.
The host properties indicate network optimization is available as indicated in the screen shot below.
Any guidance on things to check is appreciated.
Thanks,
GlennHere is a snippet of the cluster log when from the current VM owner node of the failed migration:
00000e50.000025c0::2014/02/03-13:16:07.495 INFO [RHS] Resource Virtual Machine Configuration VMNameHere called SetResourceLockedMode. LockedModeEnabled0, LockedModeReason0.
00000b6c.00001a9c::2014/02/03-13:16:07.495 INFO [RCM] HandleMonitorReply: LOCKEDMODE for 'Virtual Machine Configuration VMNameHere', gen(0) result 0/0.
00000e50.000025c0::2014/02/03-13:16:07.495 INFO [RHS] Resource Virtual Machine VMNameHere called SetResourceLockedMode. LockedModeEnabled0, LockedModeReason0.
00000b6c.00001a9c::2014/02/03-13:16:07.495 INFO [RCM] HandleMonitorReply: LOCKEDMODE for 'Virtual Machine VMNameHere', gen(0) result 0/0.
00000b6c.00001a9c::2014/02/03-13:16:07.495 INFO [RCM] HandleMonitorReply: INMEMORY_NODELOCAL_PROPERTIES for 'Virtual Machine VMNameHere', gen(0) result 0/0.
00000b6c.000020ec::2014/02/03-13:16:07.495 INFO [GEM] Node 3: Sending 1 messages as a batched GEM message
00000e50.000025c0::2014/02/03-13:16:07.495 INFO [RES] Virtual Machine Configuration <Virtual Machine Configuration VMNameHere>: Current state 'MigrationSrcWaitForOffline', event 'MigrationSrcCompleted', result 0x8007274d
00000e50.000025c0::2014/02/03-13:16:07.495 INFO [RES] Virtual Machine Configuration <Virtual Machine Configuration VMNameHere>: State change 'MigrationSrcWaitForOffline' -> 'Online'
00000e50.000025c0::2014/02/03-13:16:07.495 INFO [RES] Virtual Machine <Virtual Machine VMNameHere>: Current state 'MigrationSrcOfflinePending', event 'MigrationSrcCompleted', result 0x8007274d
00000e50.000025c0::2014/02/03-13:16:07.495 INFO [RES] Virtual Machine <Virtual Machine VMNameHere>: State change 'MigrationSrcOfflinePending' -> 'Online'
00000e50.00002080::2014/02/03-13:16:07.510 ERR [RES] Virtual Machine <Virtual Machine VMNameHere>: Live migration of 'Virtual Machine VMNameHere' failed.
Virtual machine migration operation for 'VMNameHere' failed at migration source 'SourceHostNameHere'. (Virtual machine ID 6901D5F8-B759-4557-8A28-E36173A14443)
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'DestinationHostNameHere': No connection could be made because the tar
00000e50.00002080::2014/02/03-13:16:07.510 ERR [RHS] Resource Virtual Machine VMNameHere has cancelled offline with error code 10061.
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] HandleMonitorReply: OFFLINERESOURCE for 'Virtual Machine VMNameHere', gen(0) result 0/10061.
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] Res Virtual Machine VMNameHere: OfflinePending -> Online( StateUnknown )
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] TransitionToState(Virtual Machine VMNameHere) OfflinePending-->Online.
00000b6c.00001a9c::2014/02/03-13:16:07.510 INFO [GEM] Node 3: Sending 1 messages as a batched GEM message
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] rcm::QueuedMovesHolder::VetoOffline: (VMNameHere with flags 0)
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] rcm::QueuedMovesHolder::RemoveGroup: (VMNameHere) GroupBeingMoved: false AllowMoveCancel: true NotifyMoveFailure: true
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] VMNameHere: Removed Flags 4 from StatusInformation. New StatusInformation 0
00000b6c.000020ec::2014/02/03-13:16:07.510 INFO [RCM] rcm::RcmGroup::CancelClusterGroupOperation: (VMNameHere)
00000b6c.00001a9c::2014/02/03-13:16:07.510 INFO [GEM] Node 3: Sending 1 messages as a batched GEM message
00000b6c.000021a8::2014/02/03-13:16:07.510 INFO [GUM] Node 3: executing request locally, gumId:3951, my action: /dm/update, # of updates: 1
00000b6c.000021a8::2014/02/03-13:16:07.510 INFO [GEM] Node 3: Sending 1 messages as a batched GEM message
00000b6c.00001a9c::2014/02/03-13:16:07.510 INFO [GEM] Node 3: Sending 1 messages as a batched GEM message
00000b6c.000022a0::2014/02/03-13:16:07.510 INFO [RCM] moved 0 tasks from staging set to task set. TaskSetSize=0
00000b6c.000022a0::2014/02/03-13:16:07.510 INFO [RCM] rcm::RcmPriorityManager::StartGroups: [RCM] done, executed 0 tasks
00000b6c.00000dd8::2014/02/03-13:16:07.510 INFO [RCM] ignored non-local state Online for group VMNameHere
00000b6c.000021a8::2014/02/03-13:16:07.526 INFO [GUM] Node 3: executing request locally, gumId:3952, my action: /dm/update, # of updates: 1
00000b6c.000021a8::2014/02/03-13:16:07.526 INFO [GEM] Node 3: Sending 1 messages as a batched GEM message
00000b6c.000018e4::2014/02/03-13:16:07.526 INFO [RCM] HandleMonitorReply: INMEMORY_NODELOCAL_PROPERTIES for 'Virtual Machine VMNameHere', gen(0) result 0/0.
No entry is made on the cluster log of the destination node.
To me this means the nodes cannot talk to each other, but I don’t know why.
They are on the same domain. Their server names resolve properly and they can ping eachother both by name and IP. -
Hi, I'm currently experiencing a problem with some VMs in a Hyper-V 2012 R2 failover cluster using Fiber Channel adapters with Virtual SAN configured on the hyper-v hosts.
I have read several articles about this issues like this ones:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baca348d-fb57-4d8f-978b-f1e7282f89a1/synthetic-fibrechannel-port-failed-to-start-reserving-resources-with-error-insufficient-system?forum=winserverhyperv
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
But haven't been able to fix my issue.
The Virtual SAN is configured on every hyper-v host node in the cluster. And every VM has 2 fiber channel adapters configured.
All the World Wide Names are configured both on the FC Switch as well as the FC SAN.
All the drivers for the FC Adapter in the Hyper-V Hosts have been updated to their latest versions.
The strange thing is that the issue is not affecting all of the VMs, some of the VMs with FC adapters configured are live migrating just fine, others are getting this error.
Quick migration works without problems.
We even tried removing and creating new FC Adapters on a VM with problems, we had to configure the switch and SAN with the new WWN names and all, but ended up having the same problem.
At first we thought is was related to the hosts, but since some VMs do work live migrating with FC adapters we tried migrating them on every host, everything worked well.
My guess is that it has to be something related to the VMs itself but I haven't been able to figure out what is it.
Any ideas on how to solve this is deeply appreciated.
Thank you!
Eduardo RojasHi Eduardo,
How are things going ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Server 2012 r2 live migration fails with hardware error
Hello all, we just upgraded one of our hyper v hosts from server 2012 to server 2012 r2; previously we had live replication setup between it and another box on the network which was also running server 2012. After installing server 2012 r2 when a live migration
is attempted we get the message:
"The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine. Virtual machine migration failed at migration source."
The servers in question are both dell, currently we have a poweredge r910 running server 2012 and a poweredge r900 running server 2012 r2. The section under processor for "migrate to a physical computer using a different processor" is already checked
and this same vm was successfully being live replicated before the upgrade to server 2012 r2. What would have changed around hardware requirements?
We are migrating from server 2012 on the poweredge r910 to server 2012 r2 on the poweredge r900. Also When I say this was an upgrade, we did a full re install and wiped out the installation of server 2012 and installed server 2012 r2, this was not an upgrade
installation.The only cause I’ve seen so far is virtual switches being named differently. I do remember that one of our VMs didn’t move, but we simply bypassed this problem, using one-time backup (VeeamZIP, more specifically).
If it’s one-time operation you can use the same procedure for the VMs in question -> backup and restore them at new server.
Kind regards, Leonardo. -
There is Hyper-V cluster with 2 nodes. Windows Server 2012 R2 is used as operating system.
Trying to live migrate test VM from node 1 to node 2 and get error 21502:
Live migration of 'Virtual Machine test' failed.
'Virtual Machine test' failed to fixup network settings. Verify VM settings and update them as necessary.
VM has Network Adapter connected to Virtual switch. This vSwitch has Private network as connection type.
If I set virtual switch property to "Not connected" in Network Adapter settings of VM I get successful migration.
All VM's that are not connected to any private networks (virtual switches with private network connection type) can be live migrated without any issues.
Is there any official reference related to Hyper-V live migration of VM's that have "private network" connection type?I can Live Migrate virtual machines with adapters on private switches without error. Aside from having the wrong name, the only way I can get it to fail is if I make the switch on one host use a different QoS minimum mode than the other and
enable QoS on the virtual adapter. Even then I get a different message than what you're getting. I only get that one with differently named switches.
There is a PowerShell cmdlet available to see why a guest won't run on another host.
Here's an example of its usage.
There's a way to use it to get it to Live Migrate.
But there is no way to truly Live Migrate three virtual machines in perfect lockstep. Even if you figure out whatever is preventing you from migrating these machines, there will still be periods during Live Migration where they can't communicate across that
private network. You also can't guarantee that all these guests will always be running on the same host without preventing Live Migration in the first place. This is why there really isn't anyone doing what you're trying to do. I suggest you consider another
isolation solution, like VLANs.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think." -
I'm getting a not the disk and everything) back to the host I originally had it on. Here is my setup:
Host 1 - Microsoft Storage Server 2012 Standard (NAS)
Host 2 - Microsoft Hyper-V Server 2012 (All connected virtual hard drives use the SMB 3.0 protocol to connect to the NAS - Host 1)
Delegation is setup on both of these hosts to include:
-Trust this computer, Use Kerberos only, Services - cifs, Hyper-V Replication, Microsoft Virtual Console Service, Microsoft Virtual System Migration Service
Live Migration is setup on both of these hosts to include:
-Enable incoming and outgoing live migrations using Kerberos
-Use any available network for live migration
I was able to migrate the VM from host 1 to host 2 with no problems. But when I try to migrate the VM host 1 that's when I encounter the error.
I saw a KB article similar to the issue I'm having but it only effects Server 2008 R2 (KB2705759)
I've rebooted both hosts but still get the error. The VM that is on host 2 has it's hard drive on host 1 run's fine so there are no connection issues there.
I've searched the Internet for this issue and keep coming up empty handed. I even named the virtual switch on both hosts the same to see if that would work. Please help! I'd rather not do an export and import of the VM because I'm evaluating
this product so I want to make sure it works before I put it into production.Hi PPlbrad,
Agree with Shabarinath .
We can just live migration the VM from low version (2012) to high version (2012R2) but the reverse is not ture .
So do hyper-v replica (just for updating )
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Live Migration only using one live migration adapter
Hi,
I have a 2 node cluster spanning two buildings, 4 switches (2 in each building), 2 live migration NICs in each server. I have NIC1 going through switch 1 and NIC2 going through switch 2, same in the other building.
everything talks fine to each other. I decided to team the Live Migration networks so I can get more transferring at once (getting 2Gbps instead of 1, this seemed like a good idea at the time but when I ran a test scenario of failing one of the switches
the live migration was unable to complete (despite the switches being stacked together, maybe I have a config issue I dont know).
so I destroyed the team and thought I'd have two seperate live mig channels, i select these two live mig channels in as live migration networks in failover cluster manager. when i try to live migrate a bunch of VM's it is only using the one adapter, no matter
how many VM's are going down there it will deal with 2 at a time (as per hyper-v settings).
the question is, why is not using my other live migration channel even though that adapter is configured correctly, I have even moved it up in the list and then it will use it so i know it works, but it won't use both together...?
thanks
SteveLive Migration uses the first network interface in the order you configured it. As far as I know the second interface is only used when the first interface becomes unavailable. But don't pin me on this. Now back to your NIC teaming, because there
is one thing you should know:
When you configure a NIC team without a switch assisted (LACP) configuration your team will have a 2x1Gb outbound and 1x1Gb inbound connection. This is probably why you only get 1x1Gb througput.
When you configure a NIC team with a switch assisted (LACP) configuration you team will have a 2x1Gb outbound and 2x1Gb inbound connection. Such a NIC teaming configuration is in fact a port-channel / ether-channel like you would configure between switches.
This is an optimal configuration.
I hope this information makes more sense to you. If you have any questions let me know.
Boudewijn Plomp, BPMi Infrastructure & Security
Please remember, if you see a post that helped you please click "Vote as Helpful" and if it answered your question, please click "Mark as Answer". -
Migration/Live Migration fails with shared storage (SMB), but not all the time
I have 2 Hyper-V Hosts using shared storage via SMB. I'm having intermittent issues with migrations failing. It'll either go through the motions of doing the whole move and fail and/or when I try to start it again I get the following:
I've done a lot of reading on this and have done various things that have been recommended. For each Hyper-V host I've setup delagation via Kerberos. ie. HV_Host1 has CIFS - HV_Host2; CIFS - SMB Server; MS Virtual System Migration Service - HV_Host2 and
vice versa.
On the actual SMB share on the Shared Storage server I added permissions to the folder for HV_Host1, HV_Host2, Storage Server, Domain Admins and my user account for full access.
In Group Policy, I've blocked Inheritance for the OU containing the Hyper-V hosts, though I have added some of the Group Policy's manually that I needed.
Last thing, I also added Domain Admins to the Local GP on each Host for "Log on as a Service" and "Impersonate a client after authentication" as shown in this thread: http://social.technet.microsoft.com/forums/windowsserver/en-US/7e6b9b1b-e5b1-4e9e-a1f3-2ce72ea1e543/unable-to-migrate-create-vm-hyperv-cluster-2012-logon-failure-have-to-restart-the-hyperv
I get these failed migrations regardless if I start them on the actual Host or via the admin console from Win8.
At this point I'm not sure what else to check or the next step to take for this.Hi Granite,
Please refer to following article to build hyper-v over SMB :
http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Live Migration Failed After Yum Update on 2.2.2
Hi,
I've live migrated vm's from node2 to node1 (master server). Put node2 into maintenance mode, then reconfigure ntp.conf to sync with our new ntp server. While in maintenance mode, I've also ran yum update which updated the kernel from 2.6.18-128.2.1.4.37.el5xen to 2.6.18-128.2.1.4.44.el5xen. In the process, xen was also updated from 3.4.0-0.1.32.el5 to 3.4.0-0.1.39.el5.
After rebooting, I've put node2 back into active mode. But now I can't live migrate the vm's back into node 2. From node1, ovs_operations.log:
"2012-06-23 11:03:28" INFO=> migrate_vm: vm('/OVS/running_pool/1210_vm05') start...
"2012-06-23 11:03:29" INFO=> xen_migrate_vm: migrate with ssl enabled failed, do failover(no ssl). vm('/var/ovs/mount/54DA5753709A48B3BFAEE65C2EAECCE0/running_pool/1210_vm05') -> tgt_srv('node2')
"2012-06-23 11:03:30" ERROR=> xen_migrate_vm: failed. vm('/var/ovs/mount/54DA5753709A48B3BFAEE65C2EAECCE0/running_pool/1210_vm05') -> tgt_srv('node2') =><Exception: xen_migrate_vm: migrate without ssl failed either.>
From node2 ovs_operations.log:
"2012-06-23 11:03:30" INFO=> ha_join_dlm_domain: =>success
"2012-06-23 11:03:30" ERROR=> ha_set_dlm_lock:failed. lock('6f1cb211-ecef-4ac6-af2b-091fc6fd5966') name('1210_vm05')=> <Exception: create lock('/dlm/ovm/f1cb211ecef4ac6af2b091fc6fd5966') failed. <OSError: [Errno 26] Text file busy: '/dlm/ovm/f1cb211ecef4ac6af2b091fc6fd5966'>
Is this due to the different xen versions after the update? How can I live migrate the vm's back to node2 so that I can take node1 into maintenance mode to reconfigure ntp.conf and run yum update?
Thanks!The next thing to try is to work though the steps in [[Error loading web sites]]. Though if this is happening on all of your computers it might have something to do with your internet connection. Maybe resetting that will help.
-
VM stays in Status Stopping after live migration failed/was canceled
I have a hyper-v Cluster running on Windows 2012 r2. I tried a live Migration from one node of Cluster to another node of the same Cluster. It got stuck by around 65% (if remembered correctly). After 45 minutes nothing has changed so I canceled the Job in
the Failover Cluster Manager. The VM went into a Status of "Stopping". After 5 hours it is still in Status "stopping". I haven't found any Information on why it got stuck on the 65% and have just found the error message that the Job got
canceled using Failover Cluster Manager events. But nothing saying why it stays in "Stopping" Status. Searched the Internet but I have Trouble finding anything related to the issue I see.
Any ideas?Hi Saren90,
Please try to disable the process "vmwp.exe " corresponding to the VM in host's task manager.
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
How to view live webcam that use windows media player and java
I am new to iphone and I have two live webcams that I like to go to and can't get either one on my iphone 3gs. www.ruidoso.net, view live webcam link and www.skiapache.com live webcam link. How can I get to them?? oram I just out of luck.
You've got to remember that, as powerful as the iPhone is, it's not a desktop computer. So certain things that have been designed for desktop computers may not work the same or at all. The owners of those websites probably never considered anyone wanting to view them on a phone.
The first webcam you can view on your iPhone by going to http://www.ruidosowebcam.com/camera0.jpg and manually refreshing the page to update the view. (The Java applet just refreshes the page, something they could easily have done in JavaScript for increased compatibility).
The second one I can't help with, as that one doesn't even work on my desktop computer, but WMV is a proprietary video format from Microsoft, which the iPhone doesn't play. You'd have to ask the website owners to use a more industry standard video format that the iPhone can play. -
Hello FOlks First time poster long time reader.. ...
I have an older HP A6567c machine.. that has been retrofitted with almost everything new minus the motherboard,processor and ram... ive swapped power supplies gpu and of course HD..so heres my issue..
I use a seagate 1tb hd.. it recently failed on me so i sent away for a replacement since it was under warranty.. they shipped me out a nice refurbed 1tb drive that is half the width of my older one.. which i thought was odd.. but i installed it anyways.. i ran the HP 3 cd recovery al was fine until it went to completing your windows installation.. and then i got an error message saying it could not complete my windows installation.. please reinstall windows.. i was dumbfounded.. ive replaced maybe 4 or5 drives in my time and ive never seen this.. so i read somewhere to unplug printers and gpus and anything extra so i did that retried and same issue.. so i went diggin around and found an article stating that older HP recovery cds dont allow certains drivers to be installed during recovery session like what the new style HD's require ..and going off that premise i ended up finding a few more articles where folks had said the same thing..
So im at a loss for why the recovery cds wont work.. anyone know if their are newer style recovery cds that work with newer hard drives ? ive read some HP forums where others had the issue and have had mixed replies from HP support one tech saying they had to buy all new recovery cds while the other tech told a customer they had to upgrade their OS.. I suppose i wouldnt mind upgrading to Win7 from my vista 64 home prem. i hear win 7 is nicer.. but i only run 4 gig ram so would win7 run on my machine ?
Also if their are a new style hard drive .. whats the beef with them ? what makes them so different to the older ones.. sadly with this being a holiday weekend im SOL on getting ahold of Seagate.. so im stuck waiting til monday dec 1st to get ahold of them.. but i was hoping someone might come across this and give me some ideas..
thanks ,
Starbuxx
This question was solved.
View Solution.Hi,
Run the BIOS hardware diagnostic and make sure that your PC is OK. Check with Seagate and make sure that the hard drive that you received is not an advanced format hard drive as these types of drives will not work with the older HP recovery programs.
If your PC is not running BIOS version 5.32 or higher and has 7GB or more then remove some memory dimms to reduce the total to under 7GB. You can install the latest BIOS updates after your PC is recovered.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT -
Live Migration Bandwidth using Teaming in LACP
Hi there,
Just a quick question, how can I Lice Migration over my LACP configuration of 2 x 1 GB. Every time I do a LM of 2 VM at the same time, the maximum speed I get is only 1GB?
Regards
David
DavidName : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Flow Control
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *FlowControl
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Interrupt Moderation
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *InterruptModeration
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : IPv4 Checksum Offload
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *IPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : IPsec Offload
DisplayValue : Disabled
DefaultDisplayValue : Disabled
ValidDisplayValues : {Disabled, Auth Header Enabled, ESP Enabled, Auth Header & ESP Enabled}
RegistryKeyword : *IPsecOffloadV2
RegistryValue : {0}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Jumbo Packet
DisplayValue : 9014 Bytes
DefaultDisplayValue : Disabled
ValidDisplayValues : {Disabled, 4088 Bytes, 9014 Bytes}
RegistryKeyword : *JumboPacket
RegistryValue : {9014}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Large Send Offload V2 (IPv4)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *LsoV2IPv4
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Large Send Offload V2 (IPv6)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *LsoV2IPv6
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Maximum number of RSS Processors
DisplayValue : 8
DefaultDisplayValue : 8
ValidDisplayValues : {1, 2, 4, 8}
RegistryKeyword : *MaxRssProcessors
RegistryValue : {8}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Preferred NUMA node
DisplayValue : System Default
DefaultDisplayValue : System Default
ValidDisplayValues : {System Default, Node 0, Node 1, Node 2...}
RegistryKeyword : *NumaNodeId
RegistryValue : {65535}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Maximum Number of RSS Queues
DisplayValue : 2 Queues
DefaultDisplayValue : 2 Queues
ValidDisplayValues : {1 Queue, 2 Queues, 4 Queues, 8 Queues}
RegistryKeyword : *NumRssQueues
RegistryValue : {2}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Packet Priority & VLAN
DisplayValue : Packet Priority & VLAN Enabled
DefaultDisplayValue : Packet Priority & VLAN Enabled
ValidDisplayValues : {Packet Priority & VLAN Disabled, Packet Priority Enabled, VLAN Enabled, Packet Priority & VLAN
Enabled}
RegistryKeyword : *PriorityVLANTag
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Receive Buffers
DisplayValue : 256
DefaultDisplayValue : 256
ValidDisplayValues :
RegistryKeyword : *ReceiveBuffers
RegistryValue : {256}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Receive Side Scaling
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *RSS
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : RSS Base Processor Number
DisplayValue : 0
DefaultDisplayValue : 0
ValidDisplayValues :
RegistryKeyword : *RssBaseProcNumber
RegistryValue : {0}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Maximum RSS Processor Number
DisplayValue : 63
DefaultDisplayValue : 63
ValidDisplayValues :
RegistryKeyword : *RssMaxProcNumber
RegistryValue : {63}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : RSS load balancing profile
DisplayValue : ClosestProcessor
DefaultDisplayValue : ClosestProcessor
ValidDisplayValues : {ClosestProcessor, ClosestProcessorStatic, NUMAScaling, NUMAScalingStatic...}
RegistryKeyword : *RSSProfile
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Speed & Duplex
DisplayValue : Auto Negotiation
DefaultDisplayValue : Auto Negotiation
ValidDisplayValues : {Auto Negotiation, 10 Mbps Half Duplex, 10 Mbps Full Duplex, 100 Mbps Half Duplex...}
RegistryKeyword : *SpeedDuplex
RegistryValue : {0}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : SR-IOV
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *SRIOV
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : TCP Checksum Offload (IPv4)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *TCPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : TCP Checksum Offload (IPv6)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *TCPChecksumOffloadIPv6
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Transmit Buffers
DisplayValue : 512
DefaultDisplayValue : 512
ValidDisplayValues :
RegistryKeyword : *TransmitBuffers
RegistryValue : {512}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : UDP Checksum Offload (IPv4)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *UDPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : UDP Checksum Offload (IPv6)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *UDPChecksumOffloadIPv6
RegistryValue : {3}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Virtual Machine Queues
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *VMQ
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Wake on Magic Packet
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *WakeOnMagicPacket
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Wake on Pattern Match
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *WakeOnPattern
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Enable PME
DisplayValue : Disabled
DefaultDisplayValue : Disabled
ValidDisplayValues : {Enabled, Disabled}
RegistryKeyword : EnablePME
RegistryValue : {0}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Interrupt Moderation Rate
DisplayValue : Adaptive
DefaultDisplayValue : Adaptive
ValidDisplayValues : {Adaptive, Extreme, High, Medium...}
RegistryKeyword : ITR
RegistryValue : {65535}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Log Link State Event
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Enabled, Disabled}
RegistryKeyword : LogLinkStateEvent
RegistryValue : {51}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Gigabit Master Slave Mode
DisplayValue : Auto Detect
DefaultDisplayValue : Auto Detect
ValidDisplayValues : {Auto Detect, Force Master Mode, Force Slave Mode}
RegistryKeyword : MasterSlave
RegistryValue : {0}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Locally Administered Address
DisplayValue :
DefaultDisplayValue :
ValidDisplayValues :
RegistryKeyword : NetworkAddress
RegistryValue :
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Reduce Speed On Power Down
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Enabled, Disabled}
RegistryKeyword : ReduceSpeedOnPowerDown
RegistryValue : {1}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Wait for Link
DisplayValue : Auto Detect
DefaultDisplayValue : Auto Detect
ValidDisplayValues : {Off, On, Auto Detect}
RegistryKeyword : WaitAutoNegComplete
RegistryValue : {2}
Name : LM 2
InterfaceDescription : Intel(R) 82576 Gigabit Dual Port Network Connection #4
DisplayName : Wake on Link Settings
DisplayValue : Disabled
DefaultDisplayValue : Disabled
ValidDisplayValues : {Disabled, Forced}
RegistryKeyword : WakeOnLink
RegistryValue : {0}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Header Data Split
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *HeaderDataSplit
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : IPv4 Checksum Offload
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *IPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : IPsec Offload
DisplayValue : Auth Header & ESP Enabled
DefaultDisplayValue : Auth Header & ESP Enabled
ValidDisplayValues : {Disabled, Auth Header Enabled, ESP Enabled, Auth Header & ESP Enabled}
RegistryKeyword : *IPsecOffloadV2
RegistryValue : {3}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Large Send Offload Version 2 (IPv4)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *LsoV2IPv4
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Large Send Offload Version 2 (IPv6)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *LsoV2IPv6
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Recv Segment Coalescing (IPv4)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *RscIPv4
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Recv Segment Coalescing (IPv6)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *RscIPv6
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Receive Side Scaling
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *RSS
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : TCP Checksum Offload (IPv4)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *TCPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : TCP Checksum Offload (IPv6)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *TCPChecksumOffloadIPv6
RegistryValue : {3}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : UDP Checksum Offload (IPv4)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *UDPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : UDP Checksum Offload (IPv6)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *UDPChecksumOffloadIPv6
RegistryValue : {3}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Virtual Machine Queues
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *VMQ
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Virtual Machine Queues - Shared Memory
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *VMQLookaheadSplit
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : Virtual Machine Queues - VLAN Id Filtering
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *VMQVlanFiltering
RegistryValue : {1}
Name : LM
InterfaceDescription : Microsoft Network Adapter Multiplexor Driver #3
DisplayName : MAC Address
DisplayValue :
DefaultDisplayValue :
ValidDisplayValues :
RegistryKeyword : NetworkAddress
RegistryValue :
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : 802.3az EEE
DisplayValue : Disable
DefaultDisplayValue : Disable
ValidDisplayValues : {Disable, Enable}
RegistryKeyword : *EEE
RegistryValue : {0}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Flow Control
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *FlowControl
RegistryValue : {3}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Interrupt Moderation
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *InterruptModeration
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Jumbo Mtu
DisplayValue : 9000
DefaultDisplayValue : 1500
ValidDisplayValues :
RegistryKeyword : *JumboPacket
RegistryValue : {9000}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Large Send Offload V2 (IPv4)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *LsoV2IPv4
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Large Send Offload V2 (IPv6)
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *LsoV2IPv6
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Maximum Number of RSS Queues
DisplayValue : RSS 2 Queues
DefaultDisplayValue : RSS 1 Queue
ValidDisplayValues : {RSS 1 Queue, RSS 2 Queues, RSS 4 Queues}
RegistryKeyword : *NumRssQueues
RegistryValue : {2}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : ARP Offload
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *PMARPOffload
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : NS Offload
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *PMNSOffload
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Priority & VLAN
DisplayValue : Priority & VLAN Enabled
DefaultDisplayValue : Priority & VLAN Enabled
ValidDisplayValues : {Priority & VLAN Disabled, Priority Enabled, VLAN Enabled, Priority & VLAN Enabled}
RegistryKeyword : *PriorityVLANTag
RegistryValue : {3}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Receive Buffers
DisplayValue : Default
DefaultDisplayValue : Default
ValidDisplayValues : {Default, Minimum, Maximum}
RegistryKeyword : *ReceiveBuffers
RegistryValue : {200}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Receive Side Scaling
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *RSS
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Speed & Duplex
DisplayValue : Auto Negotiation
DefaultDisplayValue : Auto Negotiation
ValidDisplayValues : {Auto Negotiation, 10 Mbps Half Duplex, 10 Mbps Full Duplex, 100 Mbps Half Duplex...}
RegistryKeyword : *SpeedDuplex
RegistryValue : {0}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : TCP/UDP Checksum Offload (IPv4)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *TCPUDPChecksumOffloadIPv4
RegistryValue : {3}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : TCP/UDP Checksum Offload (IPv6)
DisplayValue : Rx & Tx Enabled
DefaultDisplayValue : Rx & Tx Enabled
ValidDisplayValues : {Disabled, Tx Enabled, Rx Enabled, Rx & Tx Enabled}
RegistryKeyword : *TCPUDPChecksumOffloadIPv6
RegistryValue : {3}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Transmit Buffers
DisplayValue : 500
DefaultDisplayValue : 200
ValidDisplayValues :
RegistryKeyword : *TransmitBuffers
RegistryValue : {500}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Virtual Machine Queues
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *VMQ
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : VMQ VLAN Filtering
DisplayValue : Disable
DefaultDisplayValue : Disable
ValidDisplayValues : {Disable, Enable}
RegistryKeyword : *VMQVlanFiltering
RegistryValue : {0}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Wake on Magic Packet
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *WakeOnMagicPacket
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Wake on Pattern Match
DisplayValue : Enabled
DefaultDisplayValue : Enabled
ValidDisplayValues : {Disabled, Enabled}
RegistryKeyword : *WakeOnPattern
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : EEE Control Policies
DisplayValue : Optimal Power and Performance
DefaultDisplayValue : Optimal Power and Performance
ValidDisplayValues : {Maximum Power Saving, Optimal Power and Performance, Maximum Performance}
RegistryKeyword : EeeCtrlMode
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Network Address
DisplayValue :
DefaultDisplayValue :
ValidDisplayValues :
RegistryKeyword : NetworkAddress
RegistryValue :
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : VLAN ID
DisplayValue : 0
DefaultDisplayValue : 0
ValidDisplayValues :
RegistryKeyword : VlanID
RegistryValue : {0}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : Ethernet@WireSpeed
DisplayValue : Enable
DefaultDisplayValue : Enable
ValidDisplayValues : {Disable, Enable}
RegistryKeyword : WireSpeed
RegistryValue : {1}
Name : LM 1
InterfaceDescription : Broadcom NetXtreme Gigabit Ethernet #4
DisplayName : WOL Speed
DisplayValue : Lowest Speed Advertised
DefaultDisplayValue : Lowest Speed Advertised
ValidDisplayValues : {Auto, 10 Mb, 100 Mb, Lowest Speed Advertised}
RegistryKeyword : WolSpeed
RegistryValue : {256}
David -
What is difference between using VIrtual USB port and standard TCP/IP port
Have a dv6t 2000 laptop and connecting to a photosmart 6150
Trying to figure out why I have two printer devices installed for the same printer, actually three, one says 6100 series (have to connect to laptop docking station), one says 6100 series 1 (this one i can print to wirelessly) and the last one says 6100 series fax.
Both the 6100 series and 6100 series 1 only allow me to scan when it is docked but i can print wirelessly to series 1.
is there a way to scan wirelessly as well. Allprinters are shared home network.Let's handle the easy one first. The 6100 series fax icon was installed by the HP software as a printer so that you can select that printer from a program. When you select the 6100 series fax to print to, it sends out that document as a fax skipping the hard copy step of faxing.
When you look at the icons in the printers folder keep in mind that those are for printing not scanning. Those icons do not represent a scanner being installed. It would appear that you have setup the HP software once when docked. I am assuming that the printer is attached USB to the laptop dock.
To clear this up, delete the series 1. That is your network print icon. Once it is deleted, undock the laptop and then rerun the HP software. It should come up to a menu where you can select Add a Device. Go through the network install and it should put a series 1 icon back into the printers folder but also enable scanning over wireless.
I was an HP employee.
Please mark the post that solves your problem as "Accepted Solution"
Maybe you are looking for
-
After adjusting the levels in a file the changes don't stay. How do I fix this?
Hello helpful people, I'm running Photoshop CS5 on an iMac. I started with a scanned tiff that was emailed to me, a black on white ink drawing. I changed it from a tiff to a greyscale image and saved as psd, then converted it to RBG 8bit. When I open
-
I'm looking to monitor HD out of a MacPro with one video card, and wondering if the MXO2 mini will allow me to have 2 computer monitors hooked up to my video card, and export HDMI to a LCD/TV (3 screens). From what I'm seeing, it looks like I'm going
-
Iphoto 9.4.2 doesn't see photos on camera
There are six photos on my card, but iPhoto tells me there are none. It previously said there were 27 others that I had deleted. I have tried accessing the photos with my cable and with a card reader.
-
My ipad is in a "guided mode" i cant remember a password and I cant get to the home screen
My Ipad says it is in a guided access is enabled. I cant remember a password. What can I do, as I cannot get it to go to the home screen. Please help!!!!!!!!
-
HP Thin Client - Easy Tools - Very slow image download and failure!
Hello folks! We recently acquired 30x HP t520 Thin Client. At this time, we've already set up our vdi solution (server) and we are trying to config our clients. Unfortunately, we can not update OS image. The download is very slow... and gets stuck, g