Vmware Esxi 5.5 License Key 14l
Kjersti Mootz
When i'm going to enable on my aruba switch LACP in port 2 (that it is my last server's port in my nic teaming), my esxi web server stop to work, and i can't ping my esxi ip until i free one port from aruba LACP port trunk.
Correct: LACP is supported only on vSphere Distributed Switch (so, switch side, you need a LACP Trunk to be configured)...if you are using Route based on IP Hash then you're probably using vSphere Standard Switch...thus use a Non Protocol (non-LACP) Trunk switch side, as suggested.
The AOS virtual appliance installation guide says to use LACP on teamed vSwitch uplinks - But since this is not a VMWare BP, and poses a variety of issues of its own on the VMWare side, Teaming method should be Source IP Hashing (I think? Maybe MAC hashing? I need to do some further experimenting to be sure). If you encounter an issue where clients are rapidly associating/disassociating, it's likely something to do with your switch uplink teaming on your anchor controller going haywire... Took me hours to figure that out when I first encountered it.
Teamed uplinks are not bridged internally within VMWare so they don't pose a spanning tree issue with your uplink switch. You can have two ports with identical config and assigned as uplinks to the vSwitch, and it will not cause the switch to freak out and put one port in blocking mode. This is vastly easier than trying to LACP the only two links on the system - I highly recommend having a separate vmkernel interface on the box just to avoid management headaches. This is very similar to how Windows does NIC teaming.
While not using VLAN 1 is considered best practice, remember that VMWare does not allow specifying a native VLAN on a trunked switch, so whatever you use as native VLAN on your uplinks will be the the native VLAN within VMWare, and is untagged. This gets a little quirky with port groups set for VLAN trunking. If your switch supports both tagged/untagged traffic on the same VLAN (not uncommon with data center grade switches), you can have a trunked port group without worrying about this, but otherwise you'll need to make sure your VLANs within AOS are set correctly.
So if you use VLAN 4000 as your default VLAN and it is untagged on the uplinks, you need create a port group with no VLAN specified, or a trunked one (VLAN 4095 in VMWare designates a trunked port group), and when configuring your AOS device, you can still set the management VLAN as 4000 and either set the port to access mode, or trunked, with 4000 native.
Note that while AOS refers to these interfaces as "gigabitEthernet", VMWare presents them to the guest OS as 10G. The physical controller/conductor appliances also refer to them as "gigabitEthernet" even when they are SFP+ with a 10G module.
Since they are functionally 10G interfaces in VMWare, you won't need to set up a portchannel (and trust me, you really don't want to go there... If you think LACP on the uplinks is wonky, doing it on virtual ports is even more so)
Please can anyone tell me when the HPE ESXi 6.5 Custom Image will be available? If this is not soon, is there a list of the VIB's that can be manually loaded so that ESXi is aware of the Proliant Sensors and drivers?
Please be aware that ESXi 6.5 hosts can be managed individually, using old vSphere Client or can be managed ONLY on vSphere vCenter Server build 6.5, according to VMware Product Interoperability Matrixes
I've deployed ESX 6.5 custom HPE image (650.9.6.0.28 released on November 2016 and based on ESXi 6.5.0 Vmkernel Release Build 4564106) on a MicroServer Gen8. Consists of 10GB RAM, mirrored RAID, iSCSI storage target and running 2 VMs simultaneously - It's not in a vcenter cluster. Reports of the Purple screen haven't occured yet after an up time of 1 month straight...
the reason why you are not experiencing a PSOD is that your platform is not affected by the buggy hpe-ilo driver 650.10.0.1-24 that is included in the only available hpe customized esxi image 6.5 build - 4564106:
If you're like me, despite having cheap or even free access to cloud compute, you still want to have a bit of compute in a home lab. I can create and destroy to my hearts content. Things can get weird and messy - and it's nobodys problem but my own.
For the past 10 years, my home lab has consisted of a couple 2U Dell R710 servers. They are were beefy in specs but they are very loud and consume a relatively large amount of power and space. They have served me really well over the years but it is finally time to upgrade.
I ordered an Intel NUC last year. It should be able to handle the workload I'm running on my Dell servers with room to spare. Due to supply chain issues, it took a few months but it finally arrived. I was extremely surprised at how small these are. I knew they were small but I did not expect it to fit in the palm of my hand!
After all that, I was able to proceed with building the image. The steps were pretty close to what is in the Virten article however the version of ESXi they used was pulled and replaced. I ended up with a different build which is reflected with the file names I used.
Note: If you encounter the following error: "windowspowershell\modules\vmware.vimautomation.sdk\12.5.0.19093564\vmware.vimautomation.sdk.psm1 cannot be loaded because running scripts is disabled on this system" you may need to enter the following command:
Now that I have an ISO image with the Fling Community Network Driver, it was time to create the bootable USB installer. I have a Mac and here are the steps I used to create the USB flash drive: -a-bootable-esxi-7-usb-installer-on-macos/. I did not encounter any issues with these steps so please refer to the linked article to follow them.
Can I use HBA mode if there is a mix of SATA and SAS. Correct me if I am wrong. But, I don't think that VMware or Windows server will see the disks if the Adaptec array utility does NOT allow me to create any array without generating an error message. Am I correct in that assumption?
if all ports are to be HBA, then select this mode in the 71605 bios and the card will then become a 16 port SATA/SAS HBA card using the cards bios to manage the ports, however any device on these ports can be moved to any motherboards sata ports and be read/write as they are in standard sata format
I tried setting the card to both RAID or HBA mode only using the 2x SATA and 2x SAS plugged into the single SFF-8643 supplied cable. I also removed the above-mentioned drives and inserted 2x WD SATA 2TB. Set the card to either RAID or HBA and had the same results. I do not want to use the card as RAID and JBOD at the same time.
I tried several operating systems as well (Windows server, Windows 10) I installed TrueNAS Scale and it did see the drives but gave me errors. I installed maxView Storage Manager in Windows 10 and it did see both controller and drives but the drives were not accessible. I have always been unable to create arrays in Adaptec array utility at bootup Ctrl-A. See pics below for error message.
I thought that installing the Adaptec card into another PC might be a good idea. So I placed it into my Lenovo ThinkServer TS140. I placed 2x SATA drive into the machine and connected ports P1 and P2 from the SFF-8643 cable directly to those SATA drives. Entered the array config at bootup Ctrl-A / Initialized both drives / attempted to create an array and I am receiving the very same message. Error number 433. This is not an issue with my Z820 or the drives in my opinion. It seems like the Adaptec is the culprit
I am always very careful when inserting cards and/or connectors. I tried everything including what you suggested with the two drives in RAID 0 or 1. That error messgae 433 is generated each and every time. By the way, are all those red lights on the card supposed to be lit all of the time?
Hello again @DGroves. I have good news and some same old news. I finally got the ASR-71605 card to work as it should. The card shipped with 4 sets of cables each packaged in their own plastic bag. The whole time that I was testing the card on two different PC's and getting that 433 error I was using the very same cable over and over.
Until this evening when I had the bright idea to try using another cable. Once again the card was able to detect the drives but this time I was actually able to initialize and create an array. Eureka! I was so stressed out about the card and the error that I hadn't considered using another cable. I put the card in HBA mode then proceeded to install Unraid and was able to assign /access all drves.
The bad news is that no matter what I do ESXi 6.5 will not see the drives. Everytime I attempt to create a new Datastore I am told that there is no device with any room available. Tried with both the native driver at fresh install and after installing the vmware driver from the Microsemi site. Sadly, the main reason that I purchased the controller was that I could specifically use it with ESXi 6.5.0.
Vmware access host : can be a physical or virtual machine( existing in same Datacenter, whose machines you want to backup.) on w thhich netbackup client is installed. this machine is used to take snapshot backups.
Please get a vmware access host, install netbackup client software on it and add it to master server properties. and then try adding credentials of ESX by selecting "name of vmware access host" in drop down of parameter "For Backup Host".
Now VMware backup host communicates with Vcenter/ESX host to create/delete snapshot and read data in case of backup/write in case of restore. So to perform all these actions VMWare backup host should have access to VCenter/ESxi host.
edit2: I managed to put in credential, but I don't understand why it asks for a "vmware access host" (with is own credential) and then asks for an esxi with other credentials...So the time out I had was because I put in "esxi" as vmware access host and master server was looking for a media server
There is no template for dashboard. You have great builtin dashboard in vmware tab. If you want custom one, you should focus on metrics that are most important for you. In general on metrics from vmware there is anomaly detection. In such case, dynatrace will rise problems for them if something will be violating.
7fc3f7cf58