Hi Danny, Glad to hear you like the tool.  Beginning with VSM 6.3.2, the tool was built into the VSMC and engineering now maintains it.  The 6.3.2 docs outline what it is capable of and I've included it below.  I no longer support this tool personally, but if you have any ideas for improvement, then I recommend opening a case with TAC so they can submit an Enhancement Request to engineering: Thanks, Sean RAID Status Page The RAID Status page displays information about the RAID, if it is installed on a Cisco Multiservice Platform that includes an LSI MegaCLI compliant RAID controller. This page also lets you silence alarms that occur when a RAID failure occurs or when the RAID array is rebuilding, and generate a debug package. To display the RAID Status page, click the Raid Status link under Overview at the left side of the Management Console. The Raid Status page includes these areas: • VSM RAID Viewer area—The left side of this area provides general information about the RAID that is installed on the system and shows the version of the BIOS that the system is running. The center of this area includes these button: – Refresh Status—Click to update the information on the page with the most current data. – Silence Alarms—Click to silence the alarm that sounds when a RAID failure occurs or when the RAID array is rebuilding. – Create Debug Package—Click to create zip file that contains RAID controller log files, then follow the prompts that appear to download the zip file to your PC. The Cisco Technical Assistance Center (TAC) may request the debug package if you need assistance with troubleshooting a RAID issue. The right side of this area provides links that you can click to quickly display other areas of the RAID Status page. • Disk Usage area—Provides information about the RAID file systems. • Virtual Disks Summary—Provides summary information about the virtual disks in the RAID. • Physical Disks Summary—Provides summary information about the physical disks in the RAID. • Virtual Disks Details—Provides detailed information about the virtual disks in the RAID. • Physical Disks—Provides detailed information about the physical disks in the RAID. • Disk Error Definitions—Defines various RAID error types that can occur. ... View more

Hi Daniel, Sounds like MySQL may not be running.  You can check the status of it and restart it with the following commands: /etc/init.d/mysql status /etc/init.d/mysql stop /etc/init.d/mysql start /etc/init.d/mysql status If you find that it is not running, but everything works after you start it up, then you can use the following steps to make sure it starts up after the next reboot: Check to see which run levels mysql is configured to start up automatically vsom-server # chkconfig --list | grep mysql mysql    0:off  1:off  2:off  3:off  4:off  5:off  6:off Okay, so it is not set up startup on any run level.  Let’s fix that: vsom-server # chkconfig mysql on vsom-server # chkconfig --list | grep mysql mysql     0:off  1:off  2:on   3:on   4:off  5:on  6:off If none of this helps, then please open a case with Cisco TAC and a Phy Sec support engineer can assist.  You'll want to get them the log file that was created and placed in the same folder as the script when you ran it. Thanks, Sean ... View more

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 ... View more

Hi Teddy, The script was never tested on 3.1/5.1.  I do know that there were some pretty significant architectural changes between 3.1/5.1 and the 6.3.x series.  I would recommend openeing a case with TAC to make sure your upgrade goes smoothly. Thanks, Sean ... View more

You do not need to add a license in the newer software versions. Sean ... View more

Hey Folks, Sorry for the super late reply here.  As long as the files names are the same, with the exception of the build number, then the script should continue to work fine.  For example, the script will only look for 6.3.2 files: Cisco_VSOM-6.3.2- So as long as the ONLY thing changing is the build number after the 6.3.2- then you should be good to go.  Sean ... View more

I found the mistake, fixed it, and published a corrected version here. Thanks again for letting me know. Sean ... View more

Thanks Erik.  I'll look into this right away.  Can you please send me the log that was generated when this happened? Sean ... View more

Hello, It is clear to me now that I wasn't clear on your question.  I thought you were asking if you needed to re-install all of the software on the server.  That said, you do not need to re-install all the software, but as I suggested, you do need to follow the instructions on restoring the backup, which does include uninstalling and re-installing the VSOM rpms, only.  So process would look something like this: /etc/init.d/cisco stop rpm -e Cisco _VSOM /usr/BWhttpd/bin/vsom_backup_restore VSOM_vsmmn053a01a02_backup_20110316040001.tar rpm -ivh Cisco_VSOM /etc/init.d/cisco start Sorry for the confusion, Sean ... View more

If all you are doing is restoring a backup, then you do not need to uninstall/install the software.  You can simply follow the instructions on restoring a backup.  The software version of the backup must match the software version running on the server you are restoring it on. Thanks, Sean ... View more

Hello Maj, Sorry for the delayed response. Yes, you can upgrade from 6.3.0 to 6.3.2 without affecting existing archives. 6.3.0 and 6.3.2 use the same exact JRE.  However, the script will uninstall the JRE and re-install it as part of the upgrade process.  It will also make sure the symbolic link is created.  Easy Peasy. Just make sure you have all the proper .zip files and follow the instructions on this page and your upgrade should be fine. Hope this helps, Sean ... View more

Hello, Any backup that is used to restore a server must have been generated on the same version of software as which it will be applied.  For example, a backup of VSOM or VSMS server created on 4.2.1/6.2.1 can only be restored on a server running 4.2.1/6.2.1.  You cannot restore a 4.2.1/6.2.1 backup on a server running 6.3.2.  Therefore, if you were upgrade from 4.2.1/6.2.1 to 6.3.2 and the upgrade fails, then you would need to downgrade the server(s) back to 4.2.1/6.2.1 in order to restore your servers using the 4.2.1/6.2.1 backups. You can find the 4.2.1 VSOM document and the 6.2.1 VSMS document on our website, and they both include the backup and restore process for their respective processes. Also, if you are going to upgrade from 4.2.1/6.2.1 to 6.3.2 you many want to use the Cisco VSM Software Assistant 6.3.2. Hope this helps, Sean ... View more

Hello, Can you try deleting the camera and re-creating the camera using a different name?  Let's see if there is some sort of corruption left over from the previous instance of the camera. If this does not help, then can you attache the /usr/BWhttpd/logs/ims.log file to this thread so we can get a better picture of why this is failing.  This file should be obtained from the media server that the camera is configured on, not the VSOM server. Thanks, Sean ... View more

Hello, Have you tried issueing the state disable command, then trying the commands again, followed by state enable? Also, check out the Local Storage for Video Archives Using iSCSI document and the Configuring iSCSI Devices document . I'm not sure if you already have these documents.  If it still fails, then you'll need to get a capture or something to investigate where and why the connection from the VMSS to the iSCSI is failing. Hope this helps, Sean ... View more

Hi Erik, The BWT rpm is included with the VSMS .zip file.  Sounds like it didn't get installed on these servers. Thanks, Sean ... View more