Cisco Systems 5.2.x Home Theater Server User Manual


 
11-10
User Guide for Cisco Digital Media Manager 5.2.x
OL-15762-03
Chapter 11 Register DMPs
Concepts
Guidelines
Limit Your Use of Manual Registration, page 11-10
General Best Practices for Non-Medianet Autoregistration, page 11-10
Best Practices to Schedule Non-Medianet Autoregistration Events, page 11-10
Limit Your Use of Manual Registration
Caution In addition to our support for Medianet features to autoregister your DMPs, DMM includes an efficient, timesaving
feature of its own to autoregister your DMPs. Despite the presence of two robust and largely automated methods, you
can register a DMP manually for testing purposes.
We recommend that you never use the method to register a DMP manually, except in a lab for testing purposes. Manual registration
is neither suitable for, nor scalable in, a production network.
Eventually, when autoregistration finds and adds a DMP that you registered manually, the device inventory database develops
multiple records for the one device. We see this duplication as an IP address conflict, which interferes with normal operation and
triggers an alarm in DMS-Admin.
General Best Practices for Non-Medianet Autoregistration
Choose Network Ranges Cautiously
When you autoregister DMPs that are new to your DMM appliance, they restart immediately even when
they are known already to another DMM appliance, and even when they are running an event. Therefore,
when your organization uses more than one DMM appliance, be careful to autoregister only those DMPs
that you are not already managing centrally elsewhere. Otherwise, you might temporarily disrupt media
playback for the signs in your network.
Best Practices to Schedule Non-Medianet Autoregistration Events
Stagger Deployment Schedules
DMP autoregistration operations that are native to DMM (as opposed to the superficially similar
operations in a Medianet) occur in a sequence that does not tolerate disruption.
You can schedule multiple DMP autoregistration operations to run simultaneously only when they
will all search the same one subnet.
However, when you define DMP autoregistration operations to search more than one subnet, you must
not schedule them to run simultaneously, or even to overlap. When they overlap, only the first of them
can run at all. Furthermore, DMM does not show any error message to explain why the similar operations
all failed.