• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

Hi,

 

I'm trying to install redundant DMA7000's.

 

We received two DMA's both with recovery disks for version 5.0 and 5.1. So I assume they use 5.0.

After using the right configuration utility we could access the webinterface of the first DMA on the vIP.

Next, we were trying to cluster both DMA's, so we went activating licenses...

The licenses however appeared or seemed to be for version 5.2, so we went upgrading...

The upgrade of the first machine went fine, but it seemed we lost the second DMA.... it didn't upgrade in any way.

Now we seem to have an issue since DMA 2 is not in the cluster and can't be reached....

So we tried configuring the machine as a standalone DMA first, but that didn't work either.

Now we want to re-image the system but obviously we would need recovery disk version 5.2.... where to get this?

 

 

Also, we have a couple of RMX'es, a CMA4000, a VBP-E and a VBP-ST as an access proxy. We would like to use the DMA's not only for the RMX'es but also as a redundant gatekeeper. I am looking for information on how to configure this total setup, or describing the best practices or so. Anyone?

 

Thanks

 

Luuk

 

2 REPLIES 2
HP Recommended

Luke,

 

There is no 5.2 re-image disk available, you would have to re-image with 5.0 and upgrade to 5.2.1

 

http://support.polycom.com/PolycomService/support/us/support/eula/dma_7000/DMAagreement5_2_1.html

 

5.2.0 was pulled out from the website because it had a memory leak and also would not purge data properly at reboot.

 

That's probably why one of your nodes never came back.

 

I hope it helps.

HP Recommended

Hello,

 

I had the same issue with the 5.2.1 update. I "destroy" my DMA cluster (5.1 => 5.2.1). "Not ready 003" on both DMA. 

Resolution: Image with DVD (4.0) update to 5.1 and restoring backup (yes, I done a backup before ;-)).

 

Mike.

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.