on 01-28-2011 09:40 AM
Hello Everyone,
[June 23, 2011] UPDATE:
I fixed two bugs in the script:
I want to bring to your attention a new tool I’ve developed to assist partners, customers, and Cisco engineers with VSM software installations and upgrades.
The Challenge
Not all VSM users and installers are proficient with Linux and I’ve always felt that it would be great if they could perform an installation or upgrade and not have to be concerned with what an RPM file is, or how to uninstall and/or install one. Not worry about Java, JRE, or symbolic links, and not forget to update the MySQL database, or worse, accidentally run the database_create script instead of database_update. An upgrade process that would verify that they have the necessary files on the server prior to launching the upgrade would be invaluable.
I'd even say that those proficient with Linux and the VSM environment would likely appreciate an easier upgrade process.
The Solution
With the attached script, you can simply download the necessary VSM software .zip files from Cisco.com and put them and the script in any directory on the server. You can then run the script and answer only a few simple YES or NO questions and feel comfortable that the installation or upgrade will be a success. The entire process is scrolled to the screen as well as logged to a file for analysis, if necessary, after the upgrade/install.
How to use the script to perform and install or upgrade
Tips
o dos2unix –k vsmSoftware631.sh
Explanation
The script can do a clean install or an upgrade. The clean install will allow you to choose which VSM components you want to install, then verify that the necessary .zip files are present. Any existing components will be removed. If VSOM is being installed, then the database_create.sh script is called. When this is called, it will first check for an existing database (from a prior installation), and if one exists, it will ask you if you want to create a new one or not. If you choose no to this prompt, then you’ll need to manually update the database when finished.
If you choose the upgrade option when launching the script, then it will only upgrade VSM components that are currently installed on the system. If VSOM is installed, it will backup, then update the MySQL database as part of the upgrade.
Please use the script and I'd love to get your feedback here. Let me know what you like about it, what you don't like about it, and what suggestions you have for it. Of course, I also want to know if you run into any problems caused by the script. This script is not officially supported by our developement team, but I will try to get updates out as soon as possible when a bug...er...newly discovered feature...is found.
Thank you,
Sean
Sean Merrow CCIE 25197
Physical Security CSE
Cisco Systems
Using this script we are having an issue installing VSES. If we pick the option to install VSMS and VSES, but no other packages, VSES fails and installs VSVM instead. Now I am unable to install VSES, as I get the following error even from CLI install the RPM.
error: %pre(Cisco_VS-6.3.1-21d.i686) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping Cisco_VSES-6.3.1-21d
UPDATE !!!!!
TAC Helped me figure it out. The new Encoder Cards that are embedded in the Media Servers don't use the ES Package. There is a seperate RPM for these cards. CIVS-ENC. FYI this RPM is not on Support or the ET site. This needs to be fixed as well.
Sean we need to look at supporting this zip/rpm in the next version of the script.
Erik
Now that we have 6.3.2 out. Do you have an ETA on a beta version of the Software Assistant for it.
Erik
Hi Erik,
I've completed the 6.3.2 Software assistant, but haven't had a chance to test it out. The error you mentioned above where VSVM was installed instead of VSES was a bug that I found and fixed in the upcoming version. Also, you are correct in that the new encoding card has a new CIVS-ENC rpm package that wasn't supported in the 6.3.1 Software Assistant. It will be supported in the updated version.
I hope to have it ready for everyone within a day or two, depending on how the tests go. There really isn't a whole lot of changes, so it shouldn't be long. I've incorporated a few of the suggestions offered on this forum as well.
Thanks,
Sean
Hi Sean -
I just upgraded one of my servers to 6.3.1, but (and i hope this doesn't sound silly) where do you input the license key? I believe I've looked everywhere in the menu, but cannot find it and i don't remember the linux command to input via Putty.
Can you assist? Thanks!
You do not need to add a license in the newer software versions.
Sean
Thanks for the info Sean. Is there a link to any documentation explaining this since I know my superiors are looking for a detailed response. I've have been searching online, but couldn't find anything.
Hi Teddy. I'm not aware of any documentation stating that you don't need a license. I guess it is implied since, as you found out, three is simply no place to add a license. If you need something in writing, i would suggest opening a TAC case so one of the PhySec support engineers can hunt this down or otherwise something you can give to your superiors.
Sean
Okay, no wonder I wasn't finding any documentation on it. I'm now going through the threads to see what the camera limitations are for a VSOM/VSMS 12TB set up...Is there a chart/spreadsheet I can download?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: