Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

Hi everyone.

Is there a "simple" procedure to install VSM 7 (and beyond) on a CIVS-MSP-2RU server that came with VSM 6 preinstalled (I mistakenly specified another server type before but edited it)?

I've found the tar file to reformat the server to 6.3.2, and a guide to reformat it to 7.0 (with a warning that this should be used on servers preinstalled with 7, which is not the case), but I can't find a simple guide to just do a clean install and a clean upgrade (not migration, as the customer doesn't need the previous data).

Does this exist? Do I have to open a TAC case for the upgrade to be done?

We already have:

L-CPS-M-OM-SW7

L-CPS-M-MS-SW7

L-CPS-M-SASD-7

Which in theory should cover the upgrade.

By the way, this server apparently came preinstalled with 6.2.0 (YaST says so).  And it has SuSE 10 SP1.

I hope this server is upgradable, since on the download page I can only see mentions about servers that came preinstalled with 6.3, not way back to 6.2.

Please advice.

Thanks in advance.

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

1) Re-image CPS-MSP-1RU-K9 with VSM 6.3.2 recovery DVD

You are already at 6x so ignore step one.

2) After operating system installation use YaST GUI to setup the network - server IP address, netmastk and default gateway - and set the date and time.

3) Download VSM 7.2.0 for SLES10 SP1 to desktop

4) Upload VSM 7.2.0 for SLES10 SP1 to VSM server

5) Create directory for VSM 7.2.0 RPM files, and extract the contents of the VSM 7.2.0 .zip file to this directory.  Change to that directory.

6) Uninstall VSM 6 software

# rpm -qa | grep Cisco | xargs rpm -e

7) Uninstall Java JRE 1.6

# rpm -e jre

8) Install Java JRE 1.7

# rpm -ivh jre-7u17-linux-i586.rpm

Ignore following errors from JRE installation:

Unpacking JAR files...

rt.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/rt.pack

jsse.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/jsse.pack

charsets.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/charsets.pack

localedata.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/ext/localedata.pack

plugin.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/plugin.pack

javaws.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/javaws.pack

deploy.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/deploy.pack

9) Install VSM 7.2 software

# rpm -ivh Cisco*.rpm

The creation of the Media Server and Operations Manager databases may take several minutes each.

10) Start the VSM software

# /etc/init.d/cisco start

11) Log in to the server's Management Console with the default 'secur4u' password.

https:///vsmc/

12) You must then change the password for the localadmin user.

13) Complete the initial setup.

a) If the server will run VSOM, select "Operations Manager".

b) Set the NTP server and time zone.  An NTP server is requried for servers running VSOM.

c) Set the server host name and domain name.  Disable any unused network interfaces.

14) At the end of the initial setup, the server will be rebooted.

15) After the server reboots VSM will start.  VSOM will go through an initialization which may take 10-20 minutes to complete.  Reload the VSOM login page until the Domain field displays "localhost".

You can check that VSOM is still initializing from the catalina.log.  Run the command:

# tail -f /usr/BWhttpd/tomcat/logs/catalina.log

Then reload the VSOM login page and you will see messages indicating "VSOM is still initializing" like the example below:

Sep 10, 2013 8:20:33 PM org.apache.cxf.phase.PhaseInterceptorChain doIntercept

INFO: Interceptor has thrown exception, unwinding now

org.apache.cxf.interceptor.Fault: Operation failed: VSOM is still initializing. Try again after some time

16) Log in to VSOM as 'admin' with the password 'admin'.  The password must be changed.

17) To complete the Media Server configuration select the VSM server from System Settings > Servers, then click the Advanced button for Media Server to display the Media Server settings.  Make sure the appropriate recording partitions are selected, and at least one partition is selected for Clipping to enable video clip generation.

27 REPLIES
Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

1) Re-image CPS-MSP-1RU-K9 with VSM 6.3.2 recovery DVD

You are already at 6x so ignore step one.

2) After operating system installation use YaST GUI to setup the network - server IP address, netmastk and default gateway - and set the date and time.

3) Download VSM 7.2.0 for SLES10 SP1 to desktop

4) Upload VSM 7.2.0 for SLES10 SP1 to VSM server

5) Create directory for VSM 7.2.0 RPM files, and extract the contents of the VSM 7.2.0 .zip file to this directory.  Change to that directory.

6) Uninstall VSM 6 software

# rpm -qa | grep Cisco | xargs rpm -e

7) Uninstall Java JRE 1.6

# rpm -e jre

8) Install Java JRE 1.7

# rpm -ivh jre-7u17-linux-i586.rpm

Ignore following errors from JRE installation:

Unpacking JAR files...

rt.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/rt.pack

jsse.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/jsse.pack

charsets.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/charsets.pack

localedata.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/ext/localedata.pack

plugin.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/plugin.pack

javaws.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/javaws.pack

deploy.jar...

Error: Could not open input file: /usr/java/jre1.7.0_17/lib/deploy.pack

9) Install VSM 7.2 software

# rpm -ivh Cisco*.rpm

The creation of the Media Server and Operations Manager databases may take several minutes each.

10) Start the VSM software

# /etc/init.d/cisco start

11) Log in to the server's Management Console with the default 'secur4u' password.

https:///vsmc/

12) You must then change the password for the localadmin user.

13) Complete the initial setup.

a) If the server will run VSOM, select "Operations Manager".

b) Set the NTP server and time zone.  An NTP server is requried for servers running VSOM.

c) Set the server host name and domain name.  Disable any unused network interfaces.

14) At the end of the initial setup, the server will be rebooted.

15) After the server reboots VSM will start.  VSOM will go through an initialization which may take 10-20 minutes to complete.  Reload the VSOM login page until the Domain field displays "localhost".

You can check that VSOM is still initializing from the catalina.log.  Run the command:

# tail -f /usr/BWhttpd/tomcat/logs/catalina.log

Then reload the VSOM login page and you will see messages indicating "VSOM is still initializing" like the example below:

Sep 10, 2013 8:20:33 PM org.apache.cxf.phase.PhaseInterceptorChain doIntercept

INFO: Interceptor has thrown exception, unwinding now

org.apache.cxf.interceptor.Fault: Operation failed: VSOM is still initializing. Try again after some time

16) Log in to VSOM as 'admin' with the password 'admin'.  The password must be changed.

17) To complete the Media Server configuration select the VSM server from System Settings > Servers, then click the Advanced button for Media Server to display the Media Server settings.  Make sure the appropriate recording partitions are selected, and at least one partition is selected for Clipping to enable video clip generation.

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

7.5 will be out in about a week or two.  You may want to wait.

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

From what you write it's fairly simple, but I have another question: Is there a way to clean all the databases and media files and "continue" with my 6.3 and jump to 7.2 from there?

The server is a 2009 one, a CIVS-MSP-2RU V01 server.  If I can't clean the server, can I image it with the 6.3 iso?  Will it support it?

Thanks!

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

7.2 is a completely different database then 6.x.  When the 7.2 install process runs it will create the new database as I understand it.

Silver

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

I don't really follow what you mean by "clean all the databases and media files"?

There *is* a VSM 7 recovery tarball (for creating a 'recovery' USB stick), but it states it only works on CPS chassis, and ones that shipped with VSM7 natively at that. My guess would be due to underlying differences in how they did RAID/Volume management.

I'm not even sure the CIVS chassis will be supported in 7.X and on, but I could be mistaken.

I would say the best bet until further notice is to use whatever the most recent recovery ISO is for the CIVS chassis (VSM631-21 Recovery?), and do the upgrades from there.

Scott

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com
Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

Yeah, the server is working (sort of) right now, on 6.3.0, they want to ditch all the info inside and use 7.2, they don't care about the old data since it's being overwritten on a daily basis anyway.

I wanted to know if I have to reimage the entire server or just delete the archive/media files to get a clean 6.3 install.

I guess I'll go ahead and reimage with the 6.3.1 DVD which says supports the CIVS-MSP-2RU (this specific server), and then jump to 7.2.

I mistakenly specified the server as a CPS-MSP-2RU-K9, but it's really a CIVS-MSP-2RU.  Will this still work?  The last image that apparently supports it is the 6.3.1 one.  I hope it's just because the CPS is reimeged via USB.

Silver

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

Hate to be the bearer of bad news, but I can't find any documentation that supports the idea of running a supported install of 7.X on any CIVS platform.  All the requirements state CPS chassis.  If there's any doubt about whether or not you need it supported, I'd check with TAC.

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com
Community Member

Hi All,

Hi All,

I have Following 

cisco CPS-MSP-1RU-K9 (VSOM 6.3.2 - 14 /VMSM 6.3.2 - 23d)

cisco CPS-MSP-2RU-K9

cisco CIVS-IPC-6030 (camera's outdoor) Version :2.0.2-24

cisco CIVS-IPC-3530 (Camera's Indoor) Version :2.0.2-24

The problem : When i am trying to add these camera's in the VSOM , in the drop down list of "Camera type " these model number of camera's are not available. Available models are 2900 series ,4300 series,4500 series and 5000 series.

How can i add 6030 and 3530 in this vsom 6.3.2 can anyone help

Upgrading software version of VSM will help? 

Silver

Well... based on the release

Well... based on the release notes, it appears you could move to version 6.3.3 and get support for these camera models.

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com
Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

We are running 7.1-2.1 on 2RU MSP.  The process described above uninstalls 6.x and creates a new database for 7.x.

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

We are also running 7.x on the old 4ru at 3 customer sites.  There is an adjustment for the load average that needs to be done or you will get "Load Critical" errors.

To reduce the server load alerts on the 4RU servers I updated the threshold at which VSM generates the high load alerts.  We could see the load on the 4ru server was exceeding the default threshold once or twice a day for brief periods and then before dropping down again.    To change the threshold I edited /usr/BWhttpd/bin/installHMconfigs and change the ‘LoadAverage’ setting to 125 from the default 80.

LoadAverage                80

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

How did you reimage the servers? This one doesn't have a CD slot, just 12 hard disks.  And I can't find a procedure to create a bootable USB to reimage the 6.x servers.

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

This information could be interesting for you...

Cisco Physical Security Partner TOI Session   - VSM 7 Migration Update

Jenifer Piccioni, VSM Product Manager at   Cisco, will outline details on the migration procedure from earlier releases   of VSM 6.x to the current version of VSM. Furthermore, details on the   migration to the upcoming VSM 7.5 will also be discussed during this Webex.

Tuesday, January 7:

8:00 AM, Pacific Daylight Time (San     Francisco, GMT-08:00)

11:00 AM, Eastern Daylight Time (New     York, GMT-05:00)

5:00 PM, Europe Time (Amsterdam,     GMT+01:00)

11:00 PM, Singapore Time (Singapore,     GMT+08:00)

Registration is required. Register Now. Registration password is "cisco".

http://ciscopartnercommunications.com/track?type=click&enid=ZWFzPTEmbXNpZD0xJmF1aWQ9MjI4MTY4Jm1haWxpbmdpZD0xMzYzMTAmbWVzc2FnZWlkPTExMzgwMSZkYXRhYmFzZWlkPTc2MTAxJnNlcmlhbD0xNjgzNDk2NSZlbWFpbGlkPWpibGFuY29yQGNpc2NvLmNvbSZ1c2VyaWQ9MV8xMDQxJnRhcmdldGlkPS...

BTW, VSM 6.3.2-MR2 is the minimum release version required to be able to migrate to 7.5.

Community Member

VSM Upgrade from 6.3.2 to 7.0 (and beyond)

But I don't to migrate, just to do a clean upgrade

2602
Views
8
Helpful
27
Replies
CreatePlease to create content