The purpose of this operation is to determine which HFC nodes will be renumbered and which will be left untouched. The split operation should make a recommendation to the operator as to which HFC nodes it believes should be moved. This recommendation will be mindful of any static IP allocations that have been made to subscribers within the current subnet. It is recommended that further action is taken so as to ensure that static IP subscribers do not become unnecessary casualties of renumbering operation thus in this example the HFC nodes containing static IP subscribers are highlighted in "red" and assigned with an initial status of "Don't Touch". In extreme circumstances, these HFC nodes may also need to be renumbered thus the drop down menu for these HFC nodes remain operational.

The split recommendations that are presented above are based/governed on/by a simple set of rules that may be edited via [Edit Split Rules] link. The purpose of allowing multiple split rules is to enable the recommendations to be tailored by each operator's preference.

A reminder is posted to ensure the operator that what the operator is doing will not have any impact on existing subscribers until it is committed. Until such time, any IP address management operation should be permitted to proceed in advance of execution and be stored for later retrieval. This permits regular business hours development of these configurations which can then be carefully planned and then later executed in a timely and precise manner (e.g. during an outage window).

One may even be able to execute such a configuration at a specified date and time. While this would require more control of the IP address provisioning system including hardware such as routers, switches, CMTS(s), etc. it is extremely possible and desirable to do this.