Specifications
Chapter 3 - IP Address and Network Configuration DHCP Server Configuration
52
Mediatrix 4100
2. In the ipAddressConfig folder, set the static ETH2 connector information as follows:
3. Restart the Mediatrix 4100 so that the changes may take effect.
DHCP Server Configuration
DHCP servers generally allocate a range of IP addresses for use on a network and reserve IP addresses for
specific devices using a unique identifier for each device. The Mediatrix 4100 unique identifier is its media
access control (MAC) address.
You can locate the MAC address as follows:
on the label located on the bottom side of the unit.
in the sysMgmtMIB under the sysMacAddress variable.
Media5 recommends to reserve an IP address with an infinite lease for each Mediatrix 4100 on the network.
Connection to the DHCP Behaviour
When the Mediatrix 4100 restarts, it requests a DHCP offer to get its IP addresses and network information.
The Mediatrix 4100 waits four seconds before sending another request. The delay between each request is
increased exponentially after each request up to a maximum delay of 64 seconds, and then restarts at a 4
seconds delay.
first request: 4 seconds delay
second request: 8 seconds delay
third request: 16 seconds delay
fourth request: 32 seconds delay
fifth request: 64 seconds delay
sixth request: 4 seconds delay
seventh request: 8 seconds delay
etc.
Table 39: LAN Interface Source
Variable Default Static Value Description
lanStaticAddress 192.168.10.1 LAN IP address used by the unit’s ETH2
interface.
lanStaticNetworkMask 255.255.255.0 LAN subnet mask used by the unit’s ETH2
interface.
Note: Do not set the lanStaticAddress variable to 0.0.0.0. This could prevent the unit from properly sending
a DHCP discover request.
Note: Media5 recommends not to set the lanStaticNetworkMask variable to 255.255.255.254 because this
would only create a subnet with two addresses. This only leaves one bit host addresses. Since a subnet
must have a network (all bits 0) and a broadcast address (all bits 1), this leaves no room for hosts.
Standards Supported • RFC 2131 – Dynamic Host Configuration Protocol, section 2
• RFC 2132 – DHCP Options and BOOTP Vendor Extensions
Note: Media5 recommends to use a Windows 2000- or Unix-based DHCP server. If you run Windows NT
4.0 and use the built-in Microsoft DHCP Server, use the Site Specific instead of Vendor Specific information.