dhcp database implementation

Unanswered Question
Jan 31st, 2009
User Badges:
  • Bronze, 100 points or more

<p>HI every body!</p>

<p>Usually dhcp database is implemented using mac-ip mappings.</p>

<p>RFc 3046 suggests:  ( quote)</p>

<p>" In general dhcp server may be extended to a database with "triplets" of</p>

<p>( client mac address, client ip address,client remote id).</p>

<p> The dhcp server should implement policies that restrict the number of ip address to be assigned to a single remote id "</p>

<p>"The dhcp server may use the remote id to select the ip address to be assigned"</p>

<p> </p>

<p>Rfc explians   remote id can also carry circuit id which would be identified by giaddr in database.</p>

<p>here is the quote from rfc:</p>

<p>" The relay agent may use this feild in addition to or instead of the agent circuit id feild to select the circuit  on which to forward the dhcp reply"</p>

<p> </p>

<p>rfc explain circuit id:</p>

<p>" since circuit id is local only to a paticular agent, a circuit id should be qualified with giaddr value that identifies the agent"</p>

<p>DId any body see a database implemented this way?</p>

<p>Thanks a lot!</p>

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
drolemc Fri, 02/06/2009 - 11:23
User Badges:
  • Silver, 250 points or more

Automatic bindings are IP addresses that have been automatically mapped to the MAC addresses of hosts that are found in the DHCP database. Automatic bindings are stored on a remote host called the database agent. A DHCP database agent is any host-for example, an FTP, TFTP, or RCP server-that stores the DHCP bindings database.The bindings are saved as text records for easy maintenance.


You can configure multiple DHCP database agents and you can configure the interval between database updates and transfers for each agent.


Actions

This Discussion