Strategy for DHCP network collectors in transition period (QIP -> Infoblox)
To make the transition period more reliable and avid problems with TCP connection for collectors
we have to design and restructuring a few current network DHCP collectors.
Current status of DHCP leases and Temp. Registration collectors:
- both of them are located on FHDHCP1 (where QIP is located);
- both of them are using direct communication with NIMI DB production;
- both of them connected to QIP audit manager to verify the DHCP lease time-end;
- they are written on Perl like one script.
The QIP and Infoblox will be running in transition period simultaneously and DHCP ares will be noved by subnet,
so the new collector (for Infoblox) will work in parallel with old one.
To make it work we need to do the following:
1 Separate DHCP leases collector from Temp. Registration collector (it's not planet to work on Infoblox in transition period);
2 Design and prepared Python code for the working new and old DHCP collectors though the same technology- Event stream,
so it avoid some TCP connection problems;
3 prepare and test the Perl components of Old collector separately -like Temp Reg. and DHCP leases;
4 Test and verify new Python components for QIP and Infoblox with Event Dispatcher;
5 Put in production the new components and shutdown the DHCP leases collector on FHDHCP1 ( leave only Temp.Reg.);
It will be enough to be ready for transition period and reliably control all network collectors .
#1 Updated by James Fromm about 10 years ago
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
- DHCP temporary registration collector consists of:
1. Existing temporary registration collector running on QIP through end of transition
2. Design, test, and install a new temporary registration collector running through the
event stream mechanism.