Today I upgraded our SMS server for Tippingpoint to version 3.5. While this should have been a straight forward upgrade, it nevertheless wasn’t. First of all I had to upgrade to patch 7 of the 3.2 release so that I could supposedly easily make the upgrade to 3.5. I did that upgrade and didn’t have any problems with it However when I tried to use the automated upgrade within the SMS to 3.5 it kept downgrading itself to 3.2 without the patches. I looked through the release notes and couldn’t find anything about this except that there was no upgrade to 3.5 form anything below 3.3, so I tried a few more times to do the update with no success. Finally I just gave up and downloaded the 933Mb full install package from the TMC.tippingpoint.com website and ran the install from that. The install took about 10 minutes.
After letting the full install package run I then logged into the website for the SMS and was able to download the 32bit windows client, I was also pleasantly surprised to find that there is now a Mac OS X client. I loaded the mac client up and was able to login to my SMS with no problems. While I think the interface overall could use some usability enhancements, I was at least happy to find that it kept parity with the Windows version as far as features and functionality. This is now one less reason I need to keep a Windows box around if I can get a VIC client for vmware when 5.1 comes out then I will be extremely happy.
May I ask how you perform the installation thru the pkg file?
When you download the file you can then go into the SMS itself and do the upgrade.
did you perform the install with the full pkg file through CLI? I couldn’t find anything on how to perform the install and i’m getting the exact same issue when trying to upgrade from the GUI.
No I did the full install through the website and uploaded the install. I downloaded the package locally and then updated.