vRealize Network Insight (vRNI) 3.5 upgrade process that works

It is have been almost a year ago since my initial post on upgrading vRealize Network insight to 3.2 and since then there has been couple of new versions released. So time for me to upgrade!

The bad part I found out about the upgrade process is that you have to upgrade each version consecutively meaning I had to upgrade my 3.2 environment to 3.3 (which i am currently on right now) and then next step is to upgrade to 3.4 and following that another upgrade to 3.5.  You cannot skip version upgrades all!  Anyways, not going to comment on that but you see where this can be very time consuming so plan accordingly.

As before there are still two upgrade options available with online, which is handled through the GUI and offline, which is handled through the CLI.  I am currently running 3.3 and in the GUI under Settings -> Install it states that my Application is up to date. I did verify through CLI command “show-connectivity-status”  that my upgrade connectivity status shows passed and I also have no proxy.  Not wanting to open a support ticket I am going to go the manual route, and oh yes if you have a cluster configured, your only option is manual upgrade as well. Sorry!

Firstly we must upgrade the vRNI Platform appliances before we upgrade the Proxy appliances. If you have cluster then you have to start with platform1.  VMware’s KB on the manual upgrade process to 3.5 does not do such a good job of showing the exact steps to upgrade so here are mine:

  1. Download the upgrade bundle
  2. Extract the bundle from the downloaded zip file.
  3. Snapshot your vRNI Platform and proxy appliances before upgrade. (always have a backup)
  4. Login to Platform CLI with consoleuser
  5. Change password for the support user
    1. (cli) modify-password support
    2. Enter the password
  6. Use a popular tool like WinSCP to copy the bundle file to the all vRNI appliances
    1. Login with the support user
    2. Copy the bundle file in directory /home/support/
  7. Now we need to use the package-installer command to copy the bundle file to the vRNI VM
    1. package-installer copy –host localhost –user support –path /home/support/VMWare-vRNI.3.4.0.1495004044.upgrade.bundle
    2. Enter password
    3. Verify copied completed
    4. Remember one version at a time so first off have to upgrade from 3.3 to 3.4.
  8. Stop the service
    1. (cli) services stop
  9. Run the upgrade
    1. (cli) package-installer upgrade (3.3 -> 3.4)
    2. (cli) package-installer upgrade –name VMware-vRealize-Network-Insight.3.5.0.1502978926.upgrade.bundle (3.4 -> 3.5)
    3. This could take up to 30 minutes to complete so go have a cup of tea or coffee.
    4. Verify upgrade completed by checking the version
      • (cli) show-version
    5. If the service does not start..
      • (cli) services start
  10. Run step 4 through 9 on all appliances
    1. vRNI Platform appliances first
    2. vRNI Proxy appliances last

After the upgrade from 3.3 to 3.4, the upgrade KB states that a reboot is not necessary, but I found that if you do not perform a reboot you are not able to run the upgrade command “package-installer upgrade –name VMware-vRealize-Network-Insight.3.5.0.1502978926.upgrade.bundle”.  The –name parameter is not recognizable.

Note:

Do not copy/paste the commands in the KB since the filename is different that what you actually download “VMWare” and this make your upgrade fail.

Links:

 

 

 

 

Upgrade your vCenter 6.5 HA environment

As discussed in my previous post here, you can easily setup vCenter HA to provide a decent (not the best and hopefully this will improve) RTO of around 4 minutes for a fail over of your vCenter server.

So now that you have vCenter HA configure, how do you patch or upgrade this environment.  In a single vCenter Server instance the upgrade is really straight forward.

  • Login to the VAMI
  • Before starting the upgrade, take a File based Backup of the vCSA, using the backup utility in the VAMI.
  • Select Update
  • Select Check Updates -> Check Repository (if you have internet access)
    • Otherwise download the software and mount the ISO to the CD/DVD drive.
  • View Available Updates
  • Screen Shot 2017-10-10 at 10.30.25 AM.png
  • Select Install Updates -> Install All Updates

 

For a vCenter HA the steps are bit more complicate since we will use the software-packages utility from the appliance shell which requires us to SSH into the three nodes in a sequence and use manual failover so that we always patch the non-active node.  Below are my quick step by step notes for the upgrade process:

  • There are multiple ways to use the software-package utility:
    • Use the default repository
    • Use a local repository by attaching the ISO to the vCenter Server appliance.
    • Use a remote repository by using a custom repository URL that points to a local webserver in your environment to retrieve the file.
  • In my case I downloaded the vCenter Server Appliance patch ISO from “https://my.vmware.com/group/vmware/patch” and attached the file to the CD/DVD drive of the vCSA.
  • Before I start the upgrade I perform the following tasks:
    • Put the vCenter HA cluster in maintenance mode
    • Make sure SSH is enabled in the vCSA VAMI
    • For each node, I open the console and mount the patch ISO to the CD/DVD drive.
    • Take a File based Backup of the vCSA, using the backup utility in the VAMI.
  • Run the upgrade first on the Witness Node
    • First off SSH into the active vCSA node
      • From the active vCSA node, SSH into the witness node and make sure you are in the appliance shell by running:
        • “appliancesh”
        • Run: “software-packages install –iso”
        • Press Enter way to many times
          • Type yes and press Enter
        • When upgrade is completed, reboot the server
          • “shutdown reboot -r patching”
        • Exit the SSH session
  • Now run the upgrade on the Passive Node
    • First off SSH into the active vCSA node
      • From the active vCSA node, SSH into the passive node and make sure you are in the appliance shell by running:
        • “appliancesh”
        • Run: “software-packages install –iso”
        • Press Enter way to many times
          • Type yes and press Enter
        • When upgrade is completed, reboot the server
          • “shutdown reboot -r patching”
        • Exit the SSH session
  • Log out of the active vCSA node
  • Wait for the nodes to shows status up after reboot.
  • Initiate a vCenter HA failover manually
    • Login to Web client
    • Select the vCenter server -> Configure -> Settings -> vCenter HA
    • Click Initiate failover
    • Click Yes to start the failover
      • Make sure to select performing synchronization first
  • Now lastly run the upgrade on the new Passive Node
    • First off SSH into the new active vCSA node
      • From the active vCSA node, SSH into the passive node and make sure you are in the appliance shell by running:
        • “appliancesh”
        • Run: “software-packages install –iso”
        • Press Enter way to many times
          • Type yes and press Enter
        • When upgrade is completed, reboot the server
          • “shutdown reboot -r patching”
        • Exit the SSH session
  • Optional: Perform another vCenter HA failover manually back to the original vCSA node.
  • Exit vCenter HA maintenance mode
    • Login to Web client
    • Select the vCenter server -> Configure -> Settings -> vCenter HA
    • Click Edit
    • Select “Enable vCenter HA”
    • click OK

Patching of all the vCenter HA nodes should now be completed.

Food for though: This process is quite involved and I wonder, depending on company policy, would it not be easier to just remove vCenter HA, upgrade the single vCSA node through the VAMI and then configure vCenter HA again? It takes way less time and much simpler process. Let me know what you think.

 

 

 

Installing your vCenter Server 6.5 HA environment

vSphere 6.5 finally brought us vCenter High Availability which provides failover/RTO such that users can continue with their work in around 2 minutes through
API clients and in my observations around 5ish minutes through UI clients, awesome right!

vCenter HA is really simple to configure through the Wizard with a basic and advanced option, with the following requirements:

  • vCenter Server 6.5 Appliance with internal or external PSC
  • vCenter Server 6.5 Appliance with no snapshot and CD/DVD drive set to Client Device.
  • Cluster with at least 3 ESXi hosts that this vCSA is both managing and running on will provide Basic installation option
  • If your vCSA is managed by another vCenter Server that is not part of the same SSO domain, or running on a host that is does not manage, you will have to use the Advanced installation option.
  • A port group on ESXi for the private HA network. Optionally, you can have a dedicated vSwitch if network isolation is a requirement.
    • The HA private network must reside on a different subnet than what is used for management.
  • Network latency on the HA network must be less than 10ms.
  • No gateway for the HA network must be specified when configuring the nodes manually during advanced installations.
  • Storage:
    • Datastores for peer and witness cannot resides in a storage cluster.
    • Will get warning if you put nodes in same datastore

When vCenter HA is enabled, a three-node vCenter Server cluster (Active, Passive, and Witness nodes) is deployed, which consists of one IP address for management and three private IP addresses for the HA nodes.

  1. Open vCenter Server 6.5 web client (HTML5 client does not yet support vCenter HA).
  2. Select the vCenter server in Navigator
  3. Select Configuration -> Settings -> vCenter HA
  4. Screen Shot 2017-10-26 at 9.30.46 AM.png
  5. Click Configure

Continue reading

vCenter Server Web Client crash with latest Flash 27.0.0.170

Within the last couple of days Google ran an automatic update of Flash, which is causing havoc in the all-things-flash world.

Since Google manages the upgrade of the flash you are kind of at their mercy on this one, until all applications finally learn to stay as far away from flash as possible! Can only hope!

You can however disable the automatic update feature for flash by setting the registry HKLM\SOFTWARE\Policies\Google\Update\AutoUpdateCheckPeriodMinutes to 0.

My fix was pretty straight forward and I only had to delete the latest release folder from the path “%LocalAppData%\Google\Chrome\User Data\PepperFlash” (windows) or “~/Library/Application Support/Google/Chrome/PepperFlash” (MAC).

In my case the older version was still available in the same folder so I only had to delete the latest and restart google but if do not have the older version you can download it here.

From other users responses it seems that the version 27.0.0.130 and older still works but newer version will crash on both your Google Chrome and Firefox browsers.

Update:  VMware has release a KB here

 

 

Migration of vCenter Server using VMware Migration Assistant

The migration assistant can tackle a couple of different vCenter Server configurations:

  • vCenter Server 5.5 or 6.0 with an embedded vCenter Single Sign-On instance on Windows
  • vCenter Server 5.5 instance on Windows with external SSO
  • vCenter server 6.0 instance on Windows with external PSC

Depending on your current configuration, the migration process will change based using an internal or external SSO/PSC and where VUM is installed.

  • If VUM is installed on a separate Windows server, other that your Windows vCenter Server instance then you MUST to run the migration assistant on this server FIRST!  The VMware Migration Assistant facilitates the migration of the Update Manager server and database to the vCenter Server Appliance 6.5.
  • If embedded SSO/PSC, then you run the Migration Assistant on the source vCenter Server
  • If external SSO/PSC, then you run the Migration Assistant on the source SSO/PSC first and then run the Migration Assistant on the source vCenter Server
    • During the migration process, make sure to leave the migration windows open

You run the VMware Migration Assistant on your source vCenter Server, SSO/PSC or VUM it will perform the following tasks:

  • Discover the source deployment type.
  • Run pre-checks on the source.
  • Report errors that must be addressed before starting the migration.
  • Provide information for the next steps in the migration process.

Here are my step by step instructions for vCenter Server 5.5 with embedded SSO, no VUM:

  1. Download and Mount the vCenter Server Appliance Installer ISO file to the Windows vCenter Server.
  2. Start the migration assistant on the source, depending on your environment configuration
    1. Open the installer folder on CD/DVD drive and copy the  “migration-assistant” folder to your source windows server running the vCenter Server
    2. Open the copied folder on local drive and run “VMware-migration-assistant.exe”
      1. This will run the pre-update checklist and prompt if anything needs to be fixed.
      2. Make sure this window stays open during the whole migration process until completion.
  3. Launch vCenter server appliance UI installer
    1. Click Migrate
    2. Click Next on Introduction
    3. Accept EULA and click Next
    4. Connect to the source server
      1. Enter Windows server FQDN or IP address
      2. Enter migration assistant port number
        • If you are changing networks and have a firewall in place then pick a port that is open and available.
      3. SSO username
        • administrator@vsphere.local
      4. SSO Password
      5. Click Next
    5. Accept Thumbprint
    6. Appliance deployment target
      1. Enter ESXi or vCenter Server name for targer
      2. HTTPS port
      3. Username
      4. Password
      5. Click Next
    7. Accept Thumbprint
    8. Select Folder to place the new vCSA
    9. Select the compute resource
    10. Target appliance VM
      1. Enter VM name
      2. Enter new root password
    11. Select deployment size
    12. Select datastore
    13. Configure the temporary network identity which is used to copy the data, this will be removed after migration is completed since the target vCSA server will get the network identity of the source vCenter server.
      1. Pick network port group
      2. Enter temp IP address
      3. Enter subnet
      4. Enter GW
      5. Enter DNS servers
      6. Click Next
    14. Verify detailed entered are correct!
    15. Click Finish
    16. Wait for the migration to complete.
      • If the migration fails for any reason your can easily roll back by powering off the target vCSA and then just power on the source vCenter Server and its components.
  4. Now for stage two, which copies the data from the source vCenter to new vCSCA.
    1. On Introduction click next
    2. Connect to Source vCenter should complete automatically
    3. Join AD
      • Add username and password for user that can add computer to domain
    4. Select the best migration data options with the following 3 being available. (pretty cool that it provides the size of the migration for each option as well)
      • Just the configuration
      • Configuration, Events and Tasks
      • Configuration, Events, Tasks and Performance metrics
    5. Select if you want to join CEIP and click Next
    6. Review your settings, check the box to verify you have a backup of the vCenter server as well as the database.  Click Next
    7. Click OK on prompt that warns you that the source vCenter Server will be shut down once the network configuration is enabled.
    8. Wait for the data migration to complete.

When successful, your source vCenter Server should now be shut down and brand new shiny vCenter Server appliance should be started in its place. The best part of all you are also upgraded to vCenter Server 6.5! awesome.

 

 

vCenter Server 6.5 error: Cannot start content-library service

I recently discovered a problem with my vCenter Server after an upgrade from 6.0 to 6.5 of the vCenter Server Appliance, which runs in linked mode.

When I tried to take a backup of the vCenter Server through the VAMI I got an error “Invalid vCenter Server Status: All required services are not up! Stopped services: ‘content-library’.

Troubleshooting:

My first attempt was trying to start the service

  • I logged into the vCenter Server web client and went to administration -> Deployment -> System Configuration.
  • Double click on the the vCSA node
  • Select services
  • Select Content Library service, which under summary showed stopped.
  • Click in Actions -> Starts
  • Service failed to start with very cryptic error “An error occurred while starting service ‘%(0)s”

I also ssh into the vCSA and tried to start the service, and see the following error when trying to start the service:

Error executing start on service content-library. Details {
“resolution”: null,
“detail”: [
{
“args”: [
“content-library”
],
“id”: “install.ciscommon.service.failstart”,
“localized”: “An error occurred while starting service ‘content-library'”,
“translatable”: “An error occurred while starting service ‘%(0)s'”
}
],
“componentKey”: null,
“problemId”: null
}
Service-control failed. Error {
“resolution”: null,
“detail”: [
{
“args”: [
“content-library”
],
“id”: “install.ciscommon.service.failstart”,
“localized”: “An error occurred while starting service ‘content-library'”,
“translatable”: “An error occurred while starting service ‘%(0)s'”
}
],
“componentKey”: null,
“problemId”: null
}

Since the error message did not help much I went to search on VMware community and found other users having issues with creating content libraries after upgrade and VMware support pointed them to a KB article.

The fix:

The solution comes from KB 2151085 , however I am on version 6.5 not 6.5U1, as well as the OVF stuff was not applicable to my particular situation but the steps provided did resolve my problem and I was able to start the content-libary services.

I compared the files with a vCenter 6.5 environment that is working and found that the ts-config.properties file had the owner and group set to root:root and should be set to content-library:cis.  This is an easy fix and also solved the problem for me.   “chown content-library:cis ts-config.properties”

 

 

 

Upgrading vROPS 6.x to 6.6.1

With all the new goodies in 6.6, especially the new HTML5 UI based on the Clarity design System, who can resist the upgrade to vROPS 6.6. Release notes for everything that is new can found here.

From an upgrade standpoint, vROPS has always been an interesting, but simple process with both the OS and application that requires separate updates.  The OS update is required for update RPMs for things like database and gemfire updates that the new vROPS application relies on.  My step by step upgrade guide below:

  1. Download the OS update and Product update files from my.vmware.com
    • OS PAK file:  vRealize_Operations_Manager-VA-OS-xxx.pak
    • Application PAK file:  vRealize_Operations_Manager-VA-xxx.pak
  2. Make sure that all the solutions you have installed has a version available that is compatible with the new vROPS release.
  3. If you customized any default alert definitions, symptom, recommendations, Policy Definitions, Views, Dashboards, Widgets and Reports in the previous version, make sure you clone it first.  When you upgrade vROPS, it is important that you upgrade the current versions of content types that allow you to alert on and monitor the objects in your environment.  It is a good practice to always clone first before customizing content.
  4. Before starting the upgrade, create a snapshot of the each of the nodes in the cluster.
    1. Login to vROPS admin
    2. Under system status click Take Offline
    3. Enter reason and click OK
    4. When Cluster status shows offline for all nodes, go ahead and take a snapshot of each
  5.  Before starting the upgrade, I also recommend taking a backup of all the nodes simultaneously by using your existing backup solution.
  6. First off we will update the Virtual Appliance OS:
    1. Login to the master vROPS node administrator interface
    2. Select Software Update
    3. Click Install a Software Update
    4. Browse the OS update PAK file
      • vRealize_Operations_Manager-VA-OS-xxx.pak
    5. Check the box “Reset Default Content”
      • As mentioned above make sure you have cloned all your customized content!
    6. Click Upload
    7. When completed click Next
    8. Accept EULA click Next
    9. Click Next
    10. Click Install
    11. This will update the OS on the Virtual Appliances and restart them.
  7. Secondly we will perform the vROPS product update:
    1. Login to the master vROPS node administrator interface
    2. Select Software Update
    3. Click Install a Software Update
    4. Browse the application update PAK file
      • vRealize_Operations_Manager-VA-xxx.pak
    5. Check the box “Reset Default Content”
      • As mentioned above make sure you have cloned all your customized content!
    6. Click Upload
    7. This will update the vROPS application on the Virtual Appliances
  8. Lastly, if you have any additional content packs installed, go ahead and upgrade them.

VMware is definitely making awesome improvements in all their products and has come a long way in helping out VMware admins with their daily management tasks.