Upgrading DMM 5.0.3 to 5.2.2

I see in the upgrade doc where to upgrade to 5.2.2 from 5.0.3, you must first downgrade to 5.0.2. For available files, I see under 5.1 a 5.0.2 upgrade helper to get to 5.1. Has anybody used this help, or have a recommendation on downgrading to 5.0.2?
Thanks!
dave

An update on this in case anyone else runs into the confusion. The 5.0.3helper iso patch, once applied, gets you around the requirement in the upgrade guide that requires you downgrade to 5.0.2 before upgrading to 5.1. Therefore, my upgrade path from 5.0.3 to 5.2.2 ends up being:
5.0.3 -> 5.0.3helper
5.0.3 helper -> 5.1
5.1 -> 5.2
5.2 -> 5.2.1
5.2.1 -> 5.2.2
The release notes on the 5.0.3HelperISO tried to explain this, but it didn't sink in for me.

Similar Messages

Error in Upgrade DMM 5.3 to 5.4

Hi Guys
I am having some issues, I was updating our DMM from 5.3 to 5.4 but on the process after the get in the match checksum successfully I have received this message: attached. did you see this before?
Cannot find appropiate update file: UCS-C220-MXA-V5.3.10.dm2.enc

Hi Kamal
Yes am using a FTP for the upgrade with a file iso called DMM53to54.iso and it was downloaded from cisco.com.

DMM upgrade 5.2 5.4

Hi Pros,
We are in process of planning an upgrade of DMM server from 5.2 to 5.4.
I have questions if someone can help answer...
1) We have existing MCS7835-H3 which is listed as supported by DMM 5.4. Does upgrade to DMM 5.4 have to involve installing it in VMWare or is it applicable only to fresh 5.4 installation.
I am assuming that 5.4 can be upgraded on current server without VMWare. Is my assumption correct?
2) Do I need to upgrade DMM server as 5.2 to 5.2.1, then 5.2.1 to 5.2.2, then 5.2.2 to 5.2.3, then 5.2.3 to 5.3 & finally 5.3 to 5.4 or can I directly upgrade from 5.2 to 5.4 or 5.2 > 5.3 > 5.4?
Upgrade guide just mentions 5.2 > 5.2.1 > 5.2.2 > 5.2.3 > 5.3 > 5.4. Its not clear to me.
3) What will be impact on current data on the DMM server. Will it all be able to convert or any special precautions (real world) to be taken.
Thanks & Regards,
Pratik

Hi Pratik,
I am afraid that you have to go step by step from version 5.2 till 5.4
As mentioned by Cisco, for MCS-7835-H3, the supported upgrade path is 5.2 > 5.2.1 > 5.2.2 > 5.2.3 > 5.3 > 5.4.
I know it is painful but in such a way you guarantee a very smooth upgrade.
Make sure to take a backup of all the content, and make sure as well to connect a keyboard, mouse and screen. You will need it during the upgrade process.

DMM & VP Upgrade - 5.02-5.1-5.2

Trying to upgrade DMM and Video Portal,
Both were 5.02. DMM upgrade from 5.02 to 5.1 went well just run DVD and upgraded. Trying to now upgrade VP and will ask if I want to upgrade from 5.02 to 5.2, I answer yes. according to the guide it will boot 2 times, only boots once and the presents the login prompt. once I log in at the AAI I can show info and still 5.02, if I run the software upgrade again from the AAI, I am asked if I want to overwrite the preinstall files for 5.1
It appears that it is copying the file to do the install but then not booting them or loading them to do the upgrade.
Tracy

Supported Upgrade Migration Paths
If your devices use any earlier Cisco DMS release than 5.1, you must upgrade to 5.1 before you can
upgrade to 5.2. We support only these migration paths:
- 5.0.0 > 5.0.2 > 5.1 > 5.2
- 5.0.2 > 5.1 > 5.2
- 5.1 > 5.2
NOTE: Please refer to the following Documents for information relating to the 5.2.x Release and
for the requirements for Upgrades.
Release Notes for Cisco Digital Media Suite 5.2.x
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_2/dms/release/notes/dms52rn.html
Upgrade Guide for Cisco Digital Media Suite Release 5.2.x
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_2/dms/upgrade/guide/dms52upg.pdf
In Summary, the supported Hardware platforms has changed with DMS 5.2.x and later. The Supported
hardware for 5.2.x is MCS-7835H3-DMS= (for DMM) & WAVE-574-DMS= (for Show and Share). Remember as
noted above, the "only" supported way to install 5.2.x on MCS 7825-H2 & 7825-H3 (Video Portal)
and MCS 7835-H1 & 7835-H2 (DMM) is to "UPGRADE" to 5.2.x.

DMM 5.2.2 - 5.2.3 MCS 7835-H2

Dear all.
I have a customer who is running DMM 5.2.2 on a MCS 7835-H2. They have purchased a C210 to run DMM 5.2.3 a migrate away from the MCS hardware platform. I know that DMM 5.2.3 is not supported on the MCS hardware platform.
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_2/dms/upgrade/guide/523UpgradeGuide.html#wp316812
However, what I would like to do is upgrade their existing 5.2.2 DMM on MCS to 5.2.3 in a migration window. Once it has been completed, backup the system and restore to DMM 5.2.3 on C210.
My question is it actually possible to upgrade DMM 5.2.2 to 5.2.3 on MCS 7835-H2, regardless of whether Cisco will support it or not.
Thanks in advance, Tim.

Just trying to find out if the migration tool is available and where I might be able to find it?
Any chance it will include pulling the content off the old MCS? I know this practice isn't recommended.
Thanks

NI-DMM Error after Labview7.1 upgrade

I have upgrade my software to Labview 7.1 and now I have big problems with the control of NI-DMM 4060.See attached file. First time I can control my DMM, but after that I got problems with the external code called by a Call Library Node. What can I do to solve this problem. I have tried to reinstall Labview without success
Attachments:
errors.doc ‏35 KB

Hey scientist,
Are you using anything related to GPIB/Serial? You posted the question talking about the NI-488 error, but really I think the error you are receiving is more pertinent to the LabVIEW: File not found error. Errors in LabVIEW generally have two possible causes - one is what the error means if LabVIEW caused it, the other is what it means if it was related to the NI-488.2 driver.
So you get a file not found error anytime you try and open any (????) file in LabVIEW 6.1? Does that mean when you try and open a VI in 6.1, or when you use a File I/O VI inside of a 6.1 VI? Can you open that same file up using LabVIEW 7.0 and 7.1? What is the type of file that you are trying to open, and where is it located?
JaredA

DMM Upgrading to 5.4 failing

Has anyone else seen this.
Have a 5.3.0 DMM installed on UCS
Setup and licensed and working
I even did a fresh install of it.
Put in the 5.3 -> 5.4 upgrade CD (yes checked the MD5 and it was a good download).
AAI - Started the upgrade
Mounts the CD then I get this
Cannot find appropriate update file: UCS-C210-DMS-V5.3.0.dm2.enc
Image also attached below
TIA

Hi Marc,
Can you send a screenshot of the content of the CD after you open it in your PC?
Can you also send a screenshot of the SHOW_INFO menu from your DMM AAI?
The error message seen normally means that the DMM is not able to find the appropriate update package files in the CD. So we should review the content of the CD itself and see if anything is missing...
Regards,
Marco

DMM 5.3 upgrade process failing

We are running the Digital Media Manager version 5.2.3 on a UCS-C210.
I have attempted to upgrade to version 5.3 twice, but each time the process is failing.
I have downloaded the ISO and burned to disk, backed up the system and kicked off the upgrade. It states it completes, informs me that I can eject the disk and reboot the system. However I have discovered I've been having to manually shut the server down and restart it, but it boots up into 5.2.3.
Is there something I am missing?
Thanks much.

Paul,
I assume that you were connected to CIMC, KVM or Physical Monitor/Keyboard when the remote upgrade was triggered. You do have to select few options when the remote upgrade happens, The only thing you avoid in remote upgrade process is - burning the DVD and inserting it in the drive.
I'd recommend that you setup CIMC (SETUP instructions :
http://www.cisco.com/en/US/products/ps10493/products_configuration_example09186a0080b10d66.shtml)
or KVM and open a TAC case, TAC can see where exactly the failure is happening.
I assume that you have already backed up 5.2.3's CONFIG+CONTENT before starting the upgrade to 5.3. The sysmptoms described in this thread are vey unique and would need deeper investigation.
Also once the device is UP via SSH , Get a syslog out of the device for analysis. The syslog contains dmsupgrade.log which should help TAC determine the root cause.
Worst case scenario, you may have to re-image the system using 5.2.3 FRESH ISO (different than upgrade ISO, this image can be obtained via TAC) , restore the CONTENT and CONFIG (assuming you have the backup of both) and re-trying the upgrade.
Or if this is fairly new setup you can also choose to run 5.3 FRESH ISO (assuming you don't want to retain any content and config)
I'd recommend opening a TAC case to troubleshoot this further.
Thanks,
Sagar Dhanrale

DMP 5.1 = 5.2 Upgrade Issue? "An error has occurred..."

I upgraded from 5.1 to 5.2, and the VP and DMP upgrades went fine (other than the one 4305 I managed to "brick" in the process). But
on the DMM upgrade, not so much. All seemed to work well, except when trying to access the DMM admin post-install I get the following error message: ("An error has occurred. Click on the button below to try again. If this does not work, please contact your system administrator.)
I suspected a DNS misconfiguration issue on the initial upgrade, but after verifying forward and reverse DNS FQDN's everywhere, I did a clean 5.1 build and upgrade to 5.2, and still the same issue.
Everything else seems to work fine. AAI is accessible and it sync's with SaS, and there are not other visible errors reporting anywhere else along the way, but I can't seem to get past this (Tomcat?) error.
Ideas?
Thanks...
Mike

This is a known issue that is being addressed.
Description
Certificate disappears after upgrade from 5.1 to 5.2
Solution
Regenerate Certificate by changing Hostname (can be the same hostname, just select “OK” w/o changing the name).
SnS First, then DMM
Reboot Server
This is from the AAI interface...
Let me know if this works..
T.

What are developers' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

I have a large set of code that I've painstakingly migrated from one labview version to another over the years. I have lots of deployed applications that I need to continue to support. From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward. Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again. That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example. Compatibility is often being sacrificed so NI can develop labview in the direction they choose. So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
In light of this, how are other developers managing older applicatiosn written in older versions of labview. Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate. I strongly recommend this approach. But keeping my large libraries of code separate is tough. They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi. Are other people also trying to maintain separate copies of all their code in different labview versions? How are other people managing this problem?
-Devin
I got 99 problems but 8.6 ain't one.
Solved!
Go to Solution.

Hi,
The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables. All distributables required to reproduce a test-station should be located under <Production>.
<Software_Root>
<Development>
| <Common>
| | <LabVIEW_61>
| | | <Drivers>
| | | | <DMM>
| | | | <OS>
| | | | <PS>
| | | <Utilities>
| | | <File>
| | | <Error>
| | | <String>
| | <LabVIEW_711>
| | <LabVIEW_82>
| | <LabVIEW_851>
<Programs>
* Program-specific applications that (probably) have distributables
| <Program_#1>
| | <Application_#1>
| | <Docs>
| | <Source>
*       Individual, application-specific, VIs go here
| | <Application_#2>
| | <Application_#3>
| <Program_2>
| | <Program_3>
| <Tools>
* Tools are NOT "program"-specific, and, may have distributables
| <SomeTool>
| <SomeOtherTool>
<Production>
| <COTS&Freeware>
| <Programs>
| | <Program_1>
| | | <Application_#1>
| | | | <Application_#1_Rev#1>
| | | | Application_#1.bld>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#1.llb>
*           Distributable is created from LLB "snapshot", not directly from development tree
| | | <Application_#2>
| | | | <Application_#2_Rev#1>
| | | | Application_#2.lvproj>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#2.llb>
| <Tools>
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
StyleGuide.doc ‏941 KB

DMS VP upgrade problem

Hello pros,
I've got the following strange behaviour while upgrading the vp from 5.0.2 to 5.1 or even to 5.0.3
I'm following the guide's instruction to upgrade the appliance from the AAI.
On first step,i'm being asked if i want to upgrade from 5.0.2 to 5.1 and i choose YES.Then it starts copying files from the cd and finally rebooting by it's self without giving me any option or message. Then, the vp starts booting up as if no upgrade had taken place earlier. So, i tried upgrade to 5.0.3 and then to 5.1 but i ve got the same behaviour. Any highlights here? Thank you pros

Hello,
I just want to clarify something first.
Currently, there is NOT a supported upgrade path from
DMM or VP version 5.0.3 to 5.1. This will always fail.
Cisco is currently working on this upgrade path and hopefully an upgrade image for 5.0.3 to 5.1 will be made available in the near future.
As for the 5.0.2 version to 5.1, This upgrade path is supported. After the VP boots back up, did you access the AAI to verify the version that is displayed?

DMM 5.3 on MCS-7835H3 and DMM-FA-C210-K9 Failover

Hello,
We are working with a customer that wants to add redundancy to their existing DMM environment. We initially deployed their solution on a MCS-7835H3-DMS server and eventually upgraded it to 5.3. Now they want to add Failover and purchased the DMM-FA-C210-K9 with DMM-FASW-52-K9 from another partner. After sitting idle for several months they have engaged us again to help them figure out a solution.
I see that 5.4 is able to run on a VM. I have the following questions.
Can I upgrade the MCS7835H3-DMS to v.5.4? Based on the 5.4 upgrade document, it appears to be supported.
If we can upgrade the MCS7835HE-DMS to 5.4 will Failover work with the DMM-FA-C210-K9 server?
Since they already have the DMM-FA-C210-K9 server, can it be used as a VMware Host to run 5.4 virtually?
If so, will failover work with the MCS-7835H3-DMS server running 5.4?

Ray,
The short answer to your two questions is no. Neither option is supported.
If you are running virtual host both the primary and failover servers must be virtual. You can not mix types here.
Also the MCS 7835 is not supported in a failover deployment. Only the DMM-SVR-C210-K9 as the primary server is supported per the 5.4 failover guide. http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_4/dms/failover_guide/dmsfailover.pdf . The DMM-FA-C210-K9 can be used as the standby server though.
Hope this helps
John

Upgrading a S&S 5.3.0 failover cluster to 5.3.7

Hi!
we need to upgrade our S&S to 5.3.7. Currently we have S&S and DMM 5.3.0 in failover cluster.
In pre-prod, were we have no cluster, just a single DMM and a single S&S, we upgraded the S&S easily.
But when facing the procedure for upgrading the S&S in the Failover cluster, after reading the official Cisco docs, we have few doubts:
1) We know that we'll need to break the cluster, reverting to standalones, before upgrading, but, since we just need to upgrade the S&S to 5.3.7 (DMM remains 5.3.0), is it enough if we break only the S&S cluster and revert to standalones, while keeping the DMM failover cluster with no changes?
2) Once we have upgraded the active/primary, I don't understand point 4 of the upgrading procedure, where it says “Reimage the secondary DMM and Show and Share appliances. Install the same software release that you upgraded the primary appliances to.”?
What does “REIMAGE” mean? does it mean that we'll need to install the secondary unit from zero to 5.3.7 and then, when both are 5.3.7, re-do the failover cluster? Isn't it enough to break the cluster, upgrade each member to 5.3.7, and then re-do the cluster again? or does it mean that the secondary unit will be unusable after breaking the cluster?
Does any of you know any more specific guide (or your own experience) of upgrading a failover cluster?
many thanks from Spain,
DAVID

The Skype extension for Firefox has a long history of being problematic in Firefox. Various older version of that extension have been "blocklisted" by Mozilla from time to time due to causing a high number of Firefox crashes in the last 3 or 4 years. <br />
http://kb.mozillazine.org/Problematic_extensions
You don't need that Skype extension in Firefox to be able to use Skype '''or''' to use Firefox.

DMM 5.2.2 7835H2 migration to DMM 5.4 VM

Hi all,
We are currently running DDM 5.2.2 on an MCS 7835H2 server and are using DMP 4400's only. We are looking to migrate to DMM 5.4 as using our Software Upgrade Contract. I have been reviewing the migration options/upgrade options and understand the process of having to go through the 5.2.2>5.2.3>5.3>5.4>5.4.1.
However i don't have access to either an MCS 7835H3 or a C210 server, but I do have access to a C220M3. Is there a migration path to take me from 5.2.2 to 5.4.1 running on our UCS B series which are running VMWare 5.0?
I have seen the migration document that references migration from the 7835H2 to the C210 at http://www.cisco.com/en/US/docs/video/digital_media_systems/hw/platform/migration/dmm-mcs-ucs.html
But as mentioned above don't have access to a C210 to undertake this. Is there a way take the configuration from 5.2.2 and import this directly in to a fresh install of 5.4 (I'm guessing not). can I use the C220 instead of the C210? If this is possible can I run throught the migration, undertake the upgrades to get me to DMM 5.4.1, install a duplicate DMM 5.4.1 in VMware and backup the C220 and restore to the VMware install?
Thanks for any assitance.
Regards
David
Happy New Year

Hi David,
Regarding licenses, they are tight to the serial number of the hardware, so a new license is always needed after an hardware migration. You just need to email [email protected] after the software initialization on the new hardware as documented at:
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_4/dmm/user/guide/admin/licenses.html#wp1156561
Best Regards,
Marco

DMM-DMS on 5.0 and 4310G DMP Compatibility

I just bought 2 new 4310G DMP's and when they come up, they show as up for a short period of time and then show down. I ensured that the passwords are the same on the DMP's and the DMM. Is there an compatibility issue with the firmware, by chance? I haven't been able to find anything, but that is my last guess.

Hi there,
Are you actually running 5.0 with a new DMP (which should ship with 5.4x) ?
I have not tried this myself but the app releases match the corresponding DMP firmware versions and each update calls for updating the firmware on the endpoints.
http://www.cisco.com/c/en/us/td/docs/video/digital_media_systems/5_x/5_4/dms/upgrade/guide/541upgrade.html
Any information provided as a member of public community support forums is provided as-is and is not warrantied by Cisco or endorsed by TAC.

Upgrading DMM 5.0.3 to 5.2.2

Similar Messages

Maybe you are looking for