Drive it with your mouse, your finger, or just use the arrow keys.
Use Learn mode to learn the demo. The orange boxes show where to click.
Use Present mode to hide the orange boxes and notes.
Use Autoplay mode to make it play like a movie. Hit the Esc key to stop.
Click a Shortcut to jump to a specific part of the demo.
This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.
The orange boxes show where to click, and the left and right arrow keys can also be used to move through the simulation in either direction.
As a first step to start the upgrade process launch the vSphere web client and login. The main web client GUI will be presented
In the upgrade tab you will see the current version of VIO 2.5.0 running as shown. This is the instance we are going to upgrade.
A messaging window will appear as part of the upgrade wizard
This is now provisioning the new deployment configuration. You will notice the provisioning in progress.
Once the provisioning is complete a new instance of VIO is ready for receiving data. Please note the deployment ‘VIO’ which is running 2.5.0 continues to run and has not been touched during this entire process. We have simply created a new VIO3 deployment instance and it is now set to state ‘prepared’, it has been given a new virtual IP from the pool of IP address and is showing the version as 3.1.0 as shown.
The next step is to migrate the data from the current ‘running’ version of VIO to the newly ‘prepared’ version of VIO. This is the step that will really exercise the management system in the running environment and during this process an ideal recommendation is no provisioning or maintenance activities be undertaken by anyone else. Ideally the upgrades are done during well defined maintenance windows, pre-notification done and restricted access is in place.
This starts the configuration process for data transfer. You will notice the progress bar moves from zero to 100%. The time it takes to complete is a function of amount of migration data that exist.
Once the data has been migrated successfully, the new instance is active at the management layer. The status of the new instance has moved from ‘prepared’ to ‘configuring’ to ‘migrated’.
This new instance of 3.1 will become the cloud management interface now meeting all the VIM needs for the vIMS and vSBC instance running in this environment once service is switched. We will do this in the next step.
You will notice the VIO instance which was running version 2.5 has now ‘stopped’.
A dialog box showing the activities that will be performed is indicated. The activities include:
This will start the switch of networking information from VIO to new VIO3 deployment. The activity progress is shown by the progress bar.
Once the action is completed, the VIO3 instance is now live and is ready to provide service to any northbound VNF, VNFM and MANO interface.
The previous VIO instance (VIO 2.5.0) has now stopped. This instance can now be deleted as all configuration and data has been successfully migrated to VIO3 and the upgrade process is now completed successfully.
Within a few seconds the instance will be deleted. The main screen will now appear with only the VIO3 instance as running.
Do a slow scroll down slowly to see the rest of the updated configuration till you see the last set.
A warning window as shown below will appear. This is ok.
Once you login successfully, you will see the VIO management pane overview.
To return to the lab, click the link in the top right corner or close this browser tab.