SCP broken in 5.0 ESXi?

Similar Questions

• After Update 2, Esxi 5.0 host cannot see storage

  I have a HP DL380 g-8 server that was running ESXi 5.0. He had 6 virtual machines running on it for 8 months with no problems. Today I applied the update 2 for ESXi 5.0 and it says the update successfully applied. After the reboot, the server could not detect any storage. When connecting with VSphere client it says "the ESXi host has no persistent storage." Virtual machines are listed as "unknown, 1 unknown unknown 2," etc.

  All storage is local. There are four disks are attached to a P420 controller card. When I click on "Storage adapters" in vsphere client, he mentions the card controller as "Patsburg 6 Port SATA AHCI Controller '. I tried a new analysis and it did not work.

  I think here, but I have an out of date firmware. I just found this page HP for the P420 with a VIB released a few weeks ago update:

  http://h20000.www2.HP.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en & cc = us & prodTypeId = 18964 & prodSeriesId = 5193414 & swItem = MTX-96dc068234d34bceba2e2e1139 & prodNameId = 5193409 & swEnvOID = 4115 & swLang = 8 & taskId = 135 & mode = 4 & idx = 1

  This link describes how to install the firmware, but this particular ESXi host is far away and I can't seem to him physically. I can connect using SSH. So my question is (having never used SCP or updated firmware on ESXi): is it possible to completely remotely via SSH, and if so, how?

  If there are any other suggestions, I'm open to them. No matter what to get storage online.

  Thank you!

  You should be able to run this command in an SSH session.  As long as SSH is enabled, you should be able to SCP the file above.  WinSCP is a client of SCP Inuit free, for Windows, that should work just fine.

• Copy of the file of the virtual machine to the data store

  Hello

  I downloaded 10 GB of ISO my VM 2003 SRV. Now I want to move these files to my data store, so I can mount them when necessary. So far, the only way I see is to move the files to my XP pre-installed and choose Download via the browser of data store. I use ESXI and manage via Vcenter. I have the essentials package.

  I don't know that there is a smarter way?

  TIA

  If you need copy (ISO, vmdk) files in your data warehouse, using the client data via vSphere store browser works. You could also SCP your connection to your ESXi Server files and selecting data warehouses with software like FastSCP or WinSCP.

  If this post was useful/solved your problem, please mark the points of wire and price as seem you. Thank you!

• How to download the file on the Esxi Server using c# and SCP data store

  Hi I want to connect to 6.0 Esxi hypervisor and download a file.

  I write code to connect with esxi:

    using (var scp = new ScpClient("10.8.58.26", 22, "root", "MyPasword"))

  {

  scp.Connect();

  }

  But I'm getting exception "no suitable authentication method proven to complete authentication.". SSH on the hypervisor is now and manually I can connect using PuTTY or winscp.

  I tried with linux and it works. Is it possible to perform this action? How should I authenticate properly to esxi?

  Thanks for the replays, but I understand it on my own. I use winscp library instead of the scp. Code looks like this:

  SessionOptions sessionOptions = new SessionOptions

  {

  Protocol = Protocol.Sftp,

  Hostname = "xxx.xxx.xxx.xxx"

  UserName = "root."

  Password = "MyPasword"

  SshHostKeyFingerprint = "ssh - rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx"

  };

  ' Private Sub WinScp (SessionOptions sessionOptions, string Cheminaccesfichiersource, string Cheminaccesfichierdestination)

  {

  using (session = Session()) new

  {

  Connect

  session. Open (sessionOptions);

  Download files

  TransferOptions transferOptions = new TransferOptions();

  transferOptions.TransferMode = TransferMode.Binary;

  TransferOperationResult transferResult;

  transferResult = session. PutFiles (transferOptions, Cheminaccesfichiersource, Cheminaccesfichierdestination, true);

  Throw on any error

  transferResult.Check ();

  }

  }

  SshHostKeyFingerprint can be found in "Customize the Logs to view system"-> "Show Support information" of ESXi.

• Reference Dell custom ESXi 5.1 u1 broken link

  Hello

  I am trying to download the iso of esxi Dell custom from http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=RD5JN 5.1u1, but the link is broken.  Is there somewhere else I can get this from?

  Thank you.

  The link and the download works perfectly for me! You have any restrictions for your browser.

  André

• SCP SSH does not not between ESXi hosts

  Hello

  I have two servers ESXi 5, both I can access via ssh (putty) but I have if try invites one of the other ESXi ESXi5 I can´t access, my ping works, I try to use SCP between two but don t work, the error message:

  ~ # ssh 192.168.0.251
  SSH: connect to host 192.168.0.251 port 22: connection timed out
  ~ # scp /tmp/testescp.txt [email protected]: / tmp

  SSH: connect to host 192.168.0.251 port 22: connection timed out

  interruption of the connection

  PING 192.168.0.251 (192.168.0.251): 56 data bytes

  64 bytes of 192.168.0.251: icmp_seq = 0 ttl = 64 time = 0,157 ms

  64 bytes of 192.168.0.251: icmp_seq = 1 ttl = 64 time = 0,214 ms

  64 bytes of 192.168.0.251: icmp_seq = 2 ttl = 64 time = 0,187 ms

  -192.168.0.251 - ping statistics

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.157/0.186/0.214 ms

  SSH is enabled.

  I can connect using PuTTY or Winscp from a windows machine.

  Is there anyone sugestion?

  Copied from this thread;

  http://communities.VMware.com/message/2067067#2067067

  You must open the ssh ports in the firewall of ESXi.

  In vSphere Client check the host-> Configuration-> Security Profile-> Firewall-> properties

  and select "SSH Client" If you need to scp connections outgoing resp. "SSH server" If you want to enable incoming connections to PCs.

• [not resolved] At boot esxi USB key, but the key is broken, how to recover?

  Hi all

  I installed a host vmware esxi 3.5 starts using a USB key.

  My problem is that the key has been broken.

  I have reinstall a new key with the same version of esxi 3.5 and assigned the same IP address to the host.

  Should what steps I follow to host my comments towards the top and run again?

  Thanks a lot for your help.

  It's not good

  Are you sure that your storage space is not the original problem?

  If you start from USB, and the key fails, ESXi will continue to function until you restart the box. ESXi RAM tracks

  If your storage space is 100%, you can try the following

  Advanced settings under configuration if I remember correct:

  EnableResignature change to 0

  Replace disallowSnapshotLun with 0 as well.

  A new analysis of the storage card at least 2 times

  Change the values back to 1 if it works

  Concerning

  If you find this or any other answer useful please consider giving points by checking the answer useful or appropriate. Thank you.

• Standard (non-express) - card PCI Passthrough/VMDirectPath broken in ESXi 5.5?

  Hello

  I use VMDirectPath/PCI passthrough with 2 cards in an ESXi 5 host environment:

  -The first card is a standard-PCI (not express), a "AVM B1 ISDN-Controller.

  -The second is a card PCIe, a "Renesas USB 3.0 controller"

  The two cards passthrough'ed work correctly with ESXi 5.0 for a long time...

  After an upgrade to ESXi 5.5, the relay of the card to the PCI standard is no longer in effect:

  -Two cards are listed very well as passthrough devices ' ed in the vSphere client

  -Two cards are configured with "msiEnabled = FALSE" in the virtual machine, no error occur at power to the top of the virtual machine

  -Two cards are listed without errors in the Device Manager of Windows Server 2003 in the VM - no exclamation point appears

  -L'USB 3.0 controller works fine, devices are recognized and are accessible

  - But, the driver for the PCI ISDN card indicates an error in the Event Viewer system log in the Windows virtual machine: "the card can not be found" and the map does not work

  After re - install of the 'old' ESXi 5.0 and restore a backup of the configuration, all works fine again.

  A ' cat vmware.log | grep-i CPPI"VM file log shows no relevant difference regarding PCI passthrough between ESXi 5.0 and 5.5.

  No idea what changed in ESXi 5.5 compared to 5.0 in PCI card passthrough/VMDirectPath ESXi?

  Thank you

  Message geändert durch MatthiasSchmidt

  The card works fine now with the recent update ESXi 5.5 2!

• Bug - ESXi 3.5 U4: broken file ntp.conf causes an open server NTP

  By mistake I configured a computer on my network to use my build 158874 ESXi 3.5 as a peer NTP server. I was surprised that the server has received a request from a machine on another network.

  I then connected on the ESXi server using the method "unsupported" and checked the/etc/ntp.conf file.

  restrict the nomodify notrap noquery nopeer kod
  restrict the 127.0.0.1
  Server dk.pool.ntp.org
  Server pool.ntp.org
  driftfile /etc/ntp.drift

  Search in ' / var/log/messages ' server complains that 'code' is an invalid host: 7 May 13:02:17 root: ntpd start ntpd

  7 May 13:02:17 ntpd286306: ntpd [email protected] Wed Jun 27 23:39:23 (UTC 2007
  1)
  7 May 13:02:17 ntpd286307: precision = 0.468 usec
  7 May 13:02:17 ntpd286307: listen to the credits of the interface #0, 0.0.0.0 #123 Di
  sabled
  7 May 13:02:17 ntpd286307: listening on the interface lo0 127.0.0.1 #1 #123 Enabl
  Ed
  7 May 13:02:17 ntpd286307: listening on the interface #2 vmk0, 192.168.42.200 #123
  Activated
  7 May 13:02:17 ntpd286307: time synchronization state of kernel 2040
  7 May 13:02:17 ntpd286307: frequency initialized 9,259 PPM from /etc/ntp.drif
  t
  7 May 13:02:17 ntpd286307: getaddrinfo: host address is not a valid "kod", ignored
  7 May 13:02:18 ntpd286307: using the drift file ' / etc/ntp.drift ' instead of ' / etc/ntp.drift.

  Looks like there is a 'default' in the first line, which should probably be:

  restrict default kod nomodify notrap noquery nopeer

  I've only used the VI Client to configure NTP. Can anyone confirm that this is a problem?

  Best regards

  Henrik

  EDIT:-Sorry it's another question

  Bug NTP

• ESXi U4 is broken. Can't put in the network settings at all

  Hi all

  Was just having a play with the ESX 3i build-153875 (U4)

  I made an installation standard stock in VMWare Workstation, all installed perfectly fine

  I hit F2 to customize system can configure the network management to define an IP address, but instead I get a prompt to restore to factory network settings I am confused?

  Is - this becuse ESXi does not have a network card?

  See you soon

  Announcement

  If you run ESXi in a virtual machine, then you'll want to edit the VMX file for the virtual machine and set the NIC card to this

  ethernet0.virtualDev = "e1000".

• OpenManage 8.3.0 ESXi 6.0 bug?

  I think that I found a bug.

  I create Custom ISOs for ESXi 6.0 so I can include the latest drivers and the VIBs for our storage.

  I created a new ISO with ESXi 6.0 Update 2 with the last VIB Dell OpenManage 8.3.0.

  (6.0) vCenter Update Manager, I have the Dell repo as a download source: https://vmwaredepot.dell.com/index.xml

  I downloaded the OpenManage 8.3.0 VIB from here:

  NOTE from the ADMIN: Broken link has been removed from this post by Dell >

  However, now when I run a scan of the host with Update Manager, it fails and the error in esxupdate.log:

  2016 04-28 T 15: 44:03Z esxupdate: esxupdate: ERROR: ValueError: cannot merge VIBs Dell_bootbank_OpenManage_8.3.0.ESXi600 - 0000, 0000 - Dell_bootbank_OpenManage_8.3.0.ESXi600 with the attributes of uneven loads: ([OpenManage: KB 7809,081], [OpenManage: 7807,439 KB])

  I see an older version of OpenManage who had this same error and it was a bug.

  Things I've done: database reset VUM, which I can then analyze the hosts successfully. Once I added in the repo of Dell, he begins fail again with the error above in the esxupdate.log file.

  Anyone else see the same thing?

  The last I heard about Dell, they said that they would not solve this problem, but to focus on the next version. I have not seen a 8.4 version, so as a work-around, you need to uninstall OMSA 8.3 of all your machines and then reinstall it from the repo.

  Huge PITA so. Another option is to reset your vCenter VUM of the base and do not add in the repo of Dell. Then you will be able to scan your guests without problem again.

  Thanks Dell!

• ESXi 6.0 U1 U2 upgrade, iSCSI questions

  Hello

  First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

  I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

  However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

  I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

  [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

  [ ... ]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

  [root@vmware6:~] tail - f /var/log/vobd.log

  [ ... ]

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

  [root@vmware6:~] ping 10.xxx.yyy.109

  PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.174/0.240/0.309 ms

  vmkping [root@vmware6:~] 10. xxx.yyy.109

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.179/0.299/0.382 ms

  [root@vmware6:~] NF - z 10. xxx.yyy3260.109

  Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

  [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 0 packets received, 100% packet loss

  I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

  [root@vmware6:~] esxcli list vib software | e1000e grep

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

  esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

  [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

  [ ... ]

  # ESXi 6.0 U1 upgrade

  2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

  [ … ]

  # ESXi 6.0 U2 upgrade

  2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

  3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

  [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

  Result of the installation

  Message: The update completed successfully, but the system must be restarted for the changes to be effective.

  Restart required: true

  VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

  VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

  VIBs ignored:

  As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

  Thanks in advance.

  --G

  

  I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

  Steps to follow:

  1. Sign in to https://my.vmware.com/group/vmware/patch#search
  2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
  3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
     
  4. Save the file somewhere locally. Open archive ZIP once downloaded.
  5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
     
  6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
  7. Connect via SSH on the ESXi 6.0 host.
  8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
     
  9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works
  
  

  It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

  Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

  & out

  --G

• VMDK crushed by scp - how to recover

  Hi all

  yesterday, shit that's happened. I accidentally ran over an important (read: lots of work has been put in) flat vmdk file with scp.

  I was in/vmfs/volumes/datastore1/and did something like scp - r VM root @ownip:/ /vmfs/volumes/datastore1 /

  The scp was executed and copied about 2 GB, which is now the new drive size. In a panic, I closed the session of the scp and the copy stopped.

  Thus, the vmdk file is "replaced" by a new file of 2 GB. Of course the virtual machine is not running right now.

  Although I don't have a lot of confidence to find a working solution, I would like to know if someone knows things I can try?

  Google does not give me sufficient responses at the moment...

  Do not delete VMDK accidentally if you use ESXi 5.5 or 6

  Take a look at the post above (url), written by continuumcontinuum, it might be able to help.

• Backup of the guests on 'free' esxi, Veeam/Storage API

  I started a new job and the company uses esxi 5 on a free key (confirmed by vmware support) and uses a 3rd party backup managed which consists of a hunger of sever running veeam. My first thought was that this is not possible due to the storage API locked on esxi when you use the "free" version However, I looked at the race of backup with the ok on the vsphere log viewer. I can't get access to the server of Veeam to check.

  Still, ive talked about Veeam and Vmware new who have confirmed my thoughts that this will not work on the 'free' version However, it seems to work... How is that possible? I missed something fundamental.

  I'm looking to replace the backup managed by our own but I am 100% I need licenses esxi for (and to a later version) to get my veeam bought to work.

  Thank you.

  The vStorage API is locked in the only hypervisor license so an instant backup wouldn't work, however, Veeam has the ability to use SSH/SCP to backup virtual machines (full copy).

• ESXi bnx2x problem!

  Hello, today the esxi server failed in CMTF. In a discharge of these events:

  [7m2015-09-24T22:50:54.755Z cpu19:33255)WARNING: LinNet: netdev_watchdog:3678: NETDEV WATCHDOG: vmnic0: transmit timed out [0m
  2015-09-24T22:50:54.755Z cpu19:33255)WARNING: at vmkdrivers/src_92/vmklinux_92/vmware/linux_net.c:3707/netdev_watchdog() (inside vmklinux)
  2015-09-24T22:50:54.755Z cpu19:33255)Backtrace for current CPU #19, worldID=33255, rbp=0x43063118ecb0
  2015-09-24T22:50:54.755Z cpu19:33255)0x4390cf39be10:[0x41800d696dfe]vmk_LogBacktraceMessage@vmkernel#nover+0x22 stack: 0x13, 0x41800dd1f
  2015-09-24T22:50:54.755Z cpu19:33255)0x4390cf39be30:[0x41800dd1f7b7][email protected]#9.2+0x27f stack: 0x43063117cce
  2015-09-24T22:50:54.755Z cpu19:33255)0x4390cf39bea0:[0x41800dd45a5f][email protected]#9.2+0xd7 stack: 0x4306
  2015-09-24T22:50:54.755Z cpu19:33255)0x4390cf39bf30:[0x41800d64fa52]helpFunc@vmkernel#nover+0x4e6 stack: 0x0, 0x43063117cce0, 0x27, 0x0,
  2015-09-24T22:50:54.755Z cpu19:33255)0x4390cf39bfd0:[0x41800d812aee]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0, 0x0, 0x0, 0x0, 0
  2015-09-24T22:51:16.840Z cpu10:33254)<3>[bnx2x_clean_tx_queue:1626(vmnic0)]timeout waiting for queue[0]: txdata->tx_pkt_prod(65183) != txdata->tx_pkt_cons(63170)
  2015-09-24T22:51:38.901Z cpu10:33254)<3>[bnx2x_clean_tx_queue:1626(vmnic0)]timeout waiting for queue[0]: txdata->tx_pkt_prod(65183) != txdata->tx_pkt_cons(63170)
  2015-09-24T22:51:51.244Z cpu16:33415)NMP: nmp_ThrottleLogForDevice:3178: Cmd 0x12 (0x43a5c8c7cd00, 0) to dev "naa.600508b1001c06cde91a898a5f4a6294" on path "vmhba0:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE
  2015-09-24T22:53:29.623Z cpu0:33254)<3>[bnx2x_state_wait:319(vmnic0)]timeout waiting for state 7
  2015-09-24T22:53:29.857Z cpu0:33254)IntrCookie: 1903: cookie 0x1c moduleID 4110 <vmnic0> exclusive, flags 0x25
  2015-09-24T22:53:29.857Z cpu0:33254)IntrCookie: 1903: cookie 0x1e moduleID 4110 <vmnic0-fp-0> exclusive, flags 0x25
  2015-09-24T22:53:29.857Z cpu0:33254)<6>bnx2x 0000:02:00.0: vmnic0: using MSI-X  IRQs: sp 16  fp[0] 26 ... fp[7] 33
  2015-09-24T22:53:31.078Z cpu0:33254)IntrCookie: 1903: cookie 0x1f moduleID 4110 <vmnic0-fp-1> exclusive, flags 0x25
  2015-09-24T22:53:31.122Z cpu9:33249)<3>bnx2x: [bnx2x_attn_int_deasserted3:4518(vmnic0)]MC assert!
  2015-09-24T22:53:31.122Z cpu9:33249)<3>bnx2x: [bnx2x_mc_assert:894(vmnic0)]XSTORM_ASSERT_LIST_INDEX 0x2
  2015-09-24T22:53:31.122Z cpu9:33249)<3>bnx2x: [bnx2x_mc_assert:908(vmnic0)]XSTORM_ASSERT_INDEX 0x0 = 0x00000000 0x00000000 0x00000000 0x00010026
  2015-09-24T22:53:31.122Z cpu9:33249)<3>bnx2x: [bnx2x_mc_assert:922(vmnic0)]Chip Revision: everest2, FW Version: 7_8_52
  2015-09-24T22:53:31.122Z cpu9:33249)<3>bnx2x: [bnx2x_attn_int_deasserted3:4524(vmnic0)]driver assert
  2015-09-24T22:53:31.123Z cpu0:33254)<3>[bnx2x_esx_set_vlan_stripping:5947(vmnic0)]Failed to configure VLAN stripping for Queue 1
  2015-09-24T22:53:31.123Z cpu0:33254)IntrCookie: 1903: cookie 0x20 moduleID 4110 <vmnic0-fp-2> exclusive, flags 0x25
  2015-09-24T22:53:31.145Z cpu0:33254)<3>bnx2x: [bnx2x_setup_queue:9147(vmnic0)]Queue(2) SETUP failed
  2015-09-24T22:53:31.145Z cpu0:33254)<3>[bnx2x_esx_setup_queue:599(vmnic0)]Queue 2 setup failed[0xfffffffb]
  2015-09-24T22:53:31.145Z cpu0:33254)<3>[bnx2x_esx_init_netqs:932(vmnic0)]Could not start tx netq[-5]:2
  2015-09-24T22:53:31.166Z cpu0:33254)<3>[bnx2x_queue_chk_transition:5310(vmnic0)]Blocking transition since pending was 20
  2015-09-24T22:53:31.166Z cpu0:33254)<3>[bnx2x_queue_state_change:4499(vmnic0)]check transition returned an error. rc -16
  2015-09-24T22:53:31.360Z cpu9:33249)<3>bnx2x: [bnx2x_panic_dump:1097(vmnic0)]begin crash dump -----------------
  2015-09-24T22:53:31.360Z cpu9:33249)<3>bnx2x: [bnx2x_panic_dump:1103(vmnic0)]def_idx(0x2)  def_att_idx(0x3)  attn_state(0x101)  spq_prod_idx(0x6) next_stats_cnt(0x0)
  2015-09-24T22:53:31.360Z cpu9:33249)<3>bnx2x: [bnx2x_panic_dump:1108(vmnic0)]DSB: attn bits(0x0)  ack(0x101)  id(0x10)  idx(0x3)
  <3>bnx2x: [bnx2x_panic_dump:1109(vmnic0)]     def (0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0)  2015-09-24T22:53:31.360Z cpu9:33249)igu_sb_id(0x10)  igu_seg_id(0x0) pf_id(0x0)  vnic_id(0x0)  vf_id(0xff)  vf_valid (0x0) state(0x1)
  2015-09-24T22:53:31.360Z cpu9:33249)<3>bnx2x: [bnx2x_panic_dump:1150(vmnic0)]fp0: rx_bd_prod(0x3fd)  rx_bd_cons(0x0)  rx_comp_prod(0x40c)  rx_comp_cons(0x1)  *rx_cons_sb(0x1)
  2015-09-24T22:53:31.360Z cpu9:33249)<3>bnx2x: [bnx2x_panic_dump:1153(vmnic0)]     rx_sge_prod(0x0)  last_max_sge(0x0)  fp_hc_idx(0x1)
  2015-09-24T22:53:31.360Z cpu9:33249)<3>bnx2x: [bnx2x_panic_dump:1163(vmnic0)]fp0: tx_pkt_prod(0x152)  tx_pkt_cons(0x0)  tx_bd_prod(0x2a6)  tx_bd_cons(0x0)  *tx_cons_sb(0x0)
  

  I understand that the driver is broken. could not help me?

  Is this esxi 6.0 or later?  If so, it's a known issue. Please refer to KB KB VMware: ESXi 6.0 the network connectivity is lost with the NETDEV WATCHDOG timeouts in the vmkernel.log

  There is a workaround script in the KB.