12-5
UserGuide for Cisco Digital Media Manager5.4.x
OL-15762-05
Chapter12 Register DMPs
Concepts
Partial Support for Cisco Medianet 2.1 Features
Some DMP endpoints support some Cisco Medianet 2.1 features.
Note We do not support any Medianet features on DMP4305G endpoints.
Tip To assess your network for Medianet readiness, see http://cisco.com/go/mra.
To review solution reference network designs (SRNDs) for Medianet, see
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns819/landing_vid_medianet.html.
DHCP Server Configuration Notes for MSI Service Discovery
For your MSI service discovery purposes as a DMP administrator, Medianet must know that a DMM
server is available and know exactly which addressable node it is on your network. You must configure
your DHCP server to facilitatethis information-sharing model.
Configuration methods vary among platforms and implementations.
dhcpd Example, page 12-6
Windows Server Example, page 12-6
DMP4310G
DMP 4310G endpoints support discovery via DHCP and can
learn their physical location. In addition, they know and can
broadcast their product type, model, and software version.
Through their use of your Medianet, they can receive the ir IP
address, VLAN assignment, and network configuration settings
automatically. Furthermore, they receive information from
Medianet through DHCP
1
that helps them to autoregister
themselves with your DMM server.
Later, after a successful autoregistration, the splash screen on
these DMPs includes key parameters and states explicitly that
setup succeeded.
DMP4400G
Medianet 2.1 feature support by DMP 4400G endpoints is
equivalent to support by DMP 4310G endpoints, with just
one exception.
Ordinarily, a DMP 4400G can participate in networks via
Ethernet or Wi-Fi.
However:
A Wi-Fi connection by a DMP 4400G prevents it from obtaining or using
any Location Services information that Medianet might be configured
toprovide.
1. With DHCP option 125 (V-I Vendor-Specific Information) for service discovery, after you configure your
supported DHCP server to support this option. See RFC 3925.