Ok.. The HP VAN SDN Controller 2.5.15 has just been released!
Before we start, a few links for you
Documentation
http://h17007.www1.hp.com/us/en/networking/library/index.aspx?cat=sdn#technical
HP VAN SDN Controller 2.5 Installation Guide
http://h20564.www2.hp.com/hpsc/doc/public/display?docId=c04647290
Software
https://h10145.www1.hp.com/downloads/SoftwareReleases.aspx?ProductNumber=J9863AAE
All good? Now... Lets get 2.4.6 upgraded to 2.5
First things to note - Minimum hardware spec's:
You can get away with lower in your demo lab though.
Using WinSCP - Copy the hp-van-sdn-ctlr-2.5.15-x64.zip file to the SDN's server's /home/sdn directory
Then unzip the file
$ unzip hp-van-sdn-ctlr-2.5.15-x64.zip
Now unpack the SDN controller
$ sudo dpkg --unpack hp-sdn-ctl_2.5.15.1175_amd64.deb
You'll notice the new controller install does something snazzy, and check's your minimum hardware spec's, which is great because if you underspec your SDN server then you run into all sorts of weird problems with the interface not loading correctly. My controller is just a test environment, with under 50 devices so I'm going to override it using the commands provided.
Error! This controller has 1 cores! (8 cores required)
Error! This controller has 8.17806 GB of RAM! (16 GB required)
Error! This controller has 53.6692 GB of available storage! (64 GB required)
This hardware platform doesnât meet the minimum requirements for a production deployment.
How to override:
$ touch /tmp/override.txt
now run the install again
$ sudo dpkg --unpack hp-sdn-ctl_2.5.15.1175_amd64.deb
(Reading database ... 65639 files and directories currently installed.)
Preparing to replace hp-sdn-ctl 2.4.6.0627 (using hp-sdn-ctl_2.5.15.1175_amd64.deb) ...
sdnc stop/waiting
Stopping cassandra ... no cassandra to stop
sdna stop/waiting
Backing up existing configuration files to directory "/var/opt/sdn"...
...done.
Install/Upgrade: upgrade
From version: 2.4.6.0627
Found old version 2.4.6.0627
Verifying sdn system users...
...done.
Unpacking replacement hp-sdn-ctl ...
Processing triggers for ureadahead ...
$
Ok, so now we need to install it
$ sudo apt-get install -f
I hadn't actually changed many settings on my controller, so my install completed without any errors or questions, except the the following message
****************************** WARNING ******************************
THE USER 'sdn' EXISTED PRIOR TO THE INSTALLATION OF THE CONTROLLER. THE
CONTROLLER REQUIRES THE USER 'sdn' TO HAVE CERTAIN ATTRIBUTES AND
PERMISSIONS. IT IS RECOMMENDED THAT YOU DELETE THE 'sdn' USER, AND THEN
RE-INSTALL THE CONTROLLER TO ENSURE CORRECT FUNCTIONALITY.
*********************************************************************
However, if you've amended certain settings then you will be given additional options. To retain all of your previous configuration files, or to upgrade to the newer version.
Configuration file ==> Modified (by you or by a script)
since installation. Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** dmk.sh (Y/I/N/O/D/Z) [default=N] ?
HP Recommends you upgrade the settings (with Y) and then go and change all of those settings you previously changed once the controller is up and running. Thankfully, if you got to this part of the installation, and thought... wtf! It backs up all your old settings to :
/opt/sdn/virgo/bin/dmk.dpk-old
ok, mine looks good
sdn@infsdn01:~$ sudo service sdnc status
sdnc start/running, process 11718
sdn@infsdn01:~$
And I always tail the log files to make sure that things have stopped wizzing around
tail -f /var/log/sdn/virgo/logs/log.log
Now log in.. happy days!