All in Swedish since those were build into MANY Swedish houses in the 80’s.
“Reverse engineerat” orginalelschema för de vanliga FTX elboxarna (vevex) som byggdes in i en sjuklig mängd hus, speciellt i början av 80-talet.
Byggde om hela min elbox med 1-wire-sensorer och relästyrning istället. Givetvis styrt över nätverk. Kanske följer fortsättning på detta? Beror på vad jag orkar.
Download SPP…wait…create USB-stick…wait…boot server on USB-stick….wait….launch ACU..create array…wait..boot server…
If you used the HP ESXi ISO while installing ESXi (you did wrong if you didn’t) it’ll also install the hpssacli tool wich can make the above process in a couple of minutes. Just follow the steps:
- Enable SSH on host
- Login to SSH
- Run command: /opt/hp/hpssacli/bin/hpssacli ctrl all show config
- Look for the unassigned disk
- If single (or RAID0) disk, run: /opt/hp/hpssacli/bin/hpssacli ctrl slot=0 create type=ld drives=<YOUR DRIVE ID> raid=0
If RAID1 run: /opt/hp/hpssacli/bin/hpssacli ctrl slot=0 create type=ld drives=<YOUR DRIVE ID>,<YOUR SECOND DRIVE ID> raid=1
If RAID5 run: /opt/hp/hpssacli/bin/hpssacli ctrl slot=0 create type=ld drives=<YOUR DRIVE ID>,<YOUR SECOND DRIVE ID>,<YOUR THIRD DRIVE ID> raid=5
To create images of (primarily) HP Proliant Service Packs – now 2016.04 you need a tool from HP to do this. If you search for it, you’ll always get to the 1.7.0 version, which is not supportet for new SPP images.
Here is where you find the new USB Key tool to create bootable disks from SPP images, filename cp028009.exe.
I upgraded my vMotion switch from 5.1 to 6.0 and turned on enhanched LACP, somehow this “failed”. Didn’t think more about it right then, but DRS/vMotion started to generate alot of errors saying:
Migration [-1062718448:1458298954171534] failed to connect to remote host <192.168.52.11> from host <192.168.52.16>: Host is down.
vMotion migration [-1062718448:1458298954171534] failed to create a connection with remote host <192.168.52.11>: The ESX hosts failed to connect over the VMotion network
The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration.
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct.
What I had to do was to go in to the switch, assign old adapters to the newly created LAG interfaces and configure them as the only uplinks.
And off we go! 🙂
This change didn’t cause any network interruptions for me.
This was a little tricky, so I thought I should share my way to do it:
- Migrate or shut down all guest systems on the host
- Put the host to maintenance
- Take notice of the dvSwitch configuration
- Disconnect the host from vCenter
- Log in directly to the host
- Add standard (vSwitches) with correct VLANs but don’t assign adapters
- Remove dvSwitches (you will now be disconnected from host)
- Log in to DCUI
- Configure Network: Network adapters – make the correct one active
- Configure Network: IP Configuration – insert your “old” IP from dvSwitch, add netmask and GW
- Log in directly to the host again
- The adapter will probably be in standby now, so just add another random network adapter, make that one standby and remove it again. It looks sexier now 🙂
- In vCenter – remove the host from the dvSwitch – or it will try to create it again.
- Reconnect the host in vCenter
- Exit maintenance mode
- You are now up and running with a “migrated” Management network.