Feature #487

DHCP Collector Transition Plan

Added by James Fromm almost 11 years ago. Updated over 9 years ago.

Start date:
Due date:
% Done:


Estimated time:
90.00 h


To make the transition period as smooth as possible (QIP->Infoblox), the following steps will be taken:

  • Split the existing DHCP collector code and the Temporary Registration collector code into two separate modules.
  • Turn off DHCP collector on QIP, and then start the DHCP collector on SNMPbridge.
  • New DHCP collector using the event stream mechanism consists of:
  1. Two Event Notifiers for DHCP leases (one for QIP, the other for Infoblox).
  2. Event Notifiers send events to a single dispatcher running in productions.
  3. To event consumers (QIP/Infoblox) subscribe to dispatcher and populate the database tables.
DHCP temporary registration collector consists of:
  1. Existing temporary registration collector running on QIP through end of transition
  2. period.
  3. Design, test, and install a new temporary registration collector running through the
  4. event stream mechanism.


#1 Updated by Vladimir Bravov over 10 years ago

  • Status changed from New to Assigned
  • Assignee set to Vladimir Bravov
  • % Done changed from 0 to 80
  • Estimated time set to 80.00 h

1 Set source data via SNMPBRIDGE;
2 make configuration for auto- restart;
3 set regression tests from file;
5 make configuration updates for deployment;
6 design monitoring (connection diagnostic ) and deploy it ;
7 set the copmlex testing using development DB and nimisrv system

#2 Updated by Vladimir Bravov over 9 years ago

  • % Done changed from 80 to 100
  • Estimated time changed from 80.00 h to 90.00 h

Also available in: Atom PDF