After upgrading an ITCM Scalability Server from 11.x to 12.x on a DHCP Server, the DHCP Services stop working. How can I restore DHCP service functionality and prevent this from happening in the future?

Document ID : KB000050530
Last Modified Date : 14/02/2018
Show Technical Document Details


When installing or upgrading a Scalability Server to version 12.x, it will install and enable the Boot Server(sdmpcserver) process for OS Installation Manager.

Boot Server and DHCP both will listen on port 67 UDP, and if boot server is enabled, it will block DHCP requests from getting to the DHCP Server.

In situations where you are not using Boot Server on the DHCP Server, you can follow the steps below.

If you will need to have Boot Server enabled on the same server as your DHCP server, please see the OSIM Administrator Guide included with your product documentation.


In Order to restore functionality to your DHCP server follow the steps below to disable the Boot Server Process.

  1. Open a command prompts and run the commands in the steps below to stop, disable, and prevent the boot server process from starting.

  2. caf stop sdmpcserver

    This will stop the process.

  3. caf disable sdmpcserver

    This will disable the boot server process.

  4. caf noatuo sdmpcserver

    This will prevent the boot server process from being enabled again after a reboot.

    At this point DHCP should be functioning again as Boot Server will no longer be listening on port 67.

If you are installing/upgrading the Scalability Server trough Software Delivery and you would like to prevent the Boot Server from being enabled during the installation follow the steps below.

  1. Open the DSM Explorer and drill down to the Scalability Server package in your Software Package Library.

    For example, the location in 12.5 would be;

    /Software/Software Package Library/All Software/CA DSM Scalability Server

  2. Expand the package and expand the "Procedures" tree and find the "Install" procedure.

  3. Right click on the "Install" procedure and select "New Based On.." to create a new install procedure.***

    Figure 1

  4. Give the new procedure a unique name

    Figure 2

  5. Select the "Embedded File" tab, then select the "Properties" tab within this area.

    In the drop down list for the "Property" field, select "BOOTSERVER_ENABLED" and in the "Value" field, select "0" as this will disable boot server.

    Then select "Add to list"

    Figure 3

  6. After selecting "OK" you will see the new install procedure in the Software Package Library

    This is the procedure that should not be pushed to your Scalability Servers if you will be upgrading them through Software Delivery to ensure that Boot Server never gets enabled during the upgrade/install.

    Figure 4

This can also be done through the Infrastructure Deployment Wizard

  1. Launch the Infrastructure Deployment Wizard and select the Scalability Server package to deploy and follow the prompts until you get to step 7.

  2. In step 7 if the Infrastructure Deployment Wizard you have the Option to pass MSI arguments in the "Please enter any additional Windows install options" field.

  3. In this field, enter the line below.


    Figure 5

  4. Continue with the deployment and this MSI argument will be passed during the installation to disable boot server.

** As noted earlier if you do need boot server enabled on the same server as your DHCP server please reference the OSIM Administrator Guide included with your installation for details on how to configure this.

*** NOTE: The procedure created above is an 'added procedure'. While perfectly valid for use in this particular case, be aware it's not always an ideal choice. Being an 'added procedure' means it's not actually part of the physical package because it was made while the package was sealed. This is important to know as it will work when being deployed from the machine where it is made, but if such package is staged to an SS or distributed from an Enterprise Server, that 'added procedure' will be stripped out. If you wish to perform this in a more permanent manner for ANY package, either unseal it if possible or right-click on it and make a new version. When you make a new version, it will make a copy of the package with a different version number, but with otherwise identical content and in an unsealed state. Now you can modify and seal that package and the new procedure will stage and otherwise 'travel with' the new package.