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.
In the neat little “Quick setup guide” that is included when you buy a switch from HP with USB Console it says:
“Note: You can also connect a console to the switch via the USB console port (cable not provided). For more information on using the USB console port, see the switch Management and Configuration guide. The manuals are available at www.hp.com/networking/support.”
However, if you read the Management and Configation guide, you can’t find anything related to the USB console port, at least not in the 2920-guide.
If you connect your regular micro-USB-cable to a computer, you will see a “HPN Serial Port”. It’s this one we need a driver for. Download the driver here under “other”. This driver works with all HP ProCurve switches with USB console.
Just download install this one (x86 or x64 depending on your OS) and take a look what COM it gets assigned.
Use Putty (or your favourite serial console software) to connect to that COM-port.
Microsoft has released their CU10 update for Exchange 2013. See what this includes here.
Here is what we need to do before upgrade But lets narrow it down a bit.
What I usally do before i touch anything is to check the schema version of today. For this we can use ADSIEdit.
Load schemas and look for ms-Exch-Schema-Version-Pt. Just to see what we hopefully want to see.
Or we can use power shell commands:
$root = [ADSI]”LDAP://RootDSE”
$m = [ADSI](“LDAP://” + “CN=ms-Exch-Schema-Version-Pt,” + $root.schemaNamingContext)
This is the corresponding versions to the “rangeUpper” value:
Exchange 2013 RTM – 15137 (15.00.0516.032) – This version works like SHIT btw.
Exchange 2013 CU1 – 15254 (15.00.0620.029)
Exchange 2013 CU2 – 15281 (15.00.712.022/15.00.0712.024)
Exchange 2013 CU3 – 15283 (15.00.0775.038)
Exchange 2013 CU4 (SP1) – 15292 (15.00.0847.032)
Exchange 2013 CU5 – 15300 (15.00.0913.022)
Exchange 2013 CU6 – 15303 (15.00.995.029)
Exchange 2013 CU7 – 15312 (15.00.1044.025)
Exchange 2013 CU8 – 15312 (15.00.1076.009)
Exchange 2013 CU9 – 15312 (15.00.1104.005)
Exchange 2013 CU10 – 15312 (15.00.1130.007)
So if we upgrade to CU10 we want to prepare the schema to 15312. We’ll keep an eye on this value. If you are coming from at least CU7, you don’t need to upgrade schema.
Now, lets prepare AD / Update schema.
You can run it directly from the exchange server if you are executing it with an account that has enterprise admin and schema admin privileges.
setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Child domains is updated after a replication is done. Other domains in forest is not.
Therefor you have to run setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms on every domain as well.
Let’s chek the rangeUpper-value in ADSIEdit OR powershell to see that it’s fine.
Then it’s time to run the setup. Here is what I got.
setup.exe /mode:upgrade /IAcceptExchangeServerLicenseTerms
The install should run smoothly and take some “huge” amount of time since it uninstalls the old version (CUX) and installs the new version (CU10). So go and get a cup of coffee, or alot of them.