VitalQIP Product Description
Copyright © 2011 Alcatel-Lucent Technologies
USE PURSUANT TO COMPANY INSTRUCTIONS
Page
32
of
50
Automatic DHCP – no Client identifier (CID) required
Manual BOOTP – CID to IP
Automatic BOOTP – No CID required
Alcatel-Lucent‟s DHCP is a totally open system environment and provides support for multiple versions
of DHCP on various platforms, including support of native Microsoft DHCP and IBM DHCP.
VitalQIP also allows the ability to customize how a server responds or processes DHCP packets through
an integrated API.
Configuring DHCP Servers
VitalQIP software provides an intuitive interface for the configurations of DHCP servers and the
server‟s policies. Examples of the available policies are:
Registered clients only – The ability to restrict the assignment of DHCP addresses to “known”
clients via the client-identifier field.
Dynamic Updates – Turn on/off dynamic DNS updates from a DHCP server.
Accept Client Names – Turns on/off the ability to update the enterprise server with client host
names.
Synchronize Servers – Scheduling of database side active lease synchronization. This allows
the database to extract MAC address and host names currently active in a DHCP server‟s lease
files.
Alcatel-Lucent has implemented several new policies that are included in the VitalQIP software
release.
DHCP Intelligent Templates
By re-using infrastructure configuration data and object class types such as routers or servers, Alcatel-
Lucent facilitates the managing and configuration of DHCP templates. (DHCP templates define what
DHCP options are passed to a client when assigning leases.) Most DHCP server vendors require that
templates be created and that information such as default routers, which typically change per subnet,
be statically defined in the template. This can result in thousands of templates (since each router
must be unique) and extensive support/administration. VitalQIP software allows for minimal template
configurations to be used for entire enterprises or service provider networks.
As an example, when a subnet is defined a device may be added with an object class of router. When
a DHCP scope/registration is performed, VitalQIP software will “dynamically” extract that router
address and define the default gateway in the DHCP configuration file as that address, eliminating the
need to statically define the router in the template. Intelligent templates also make the task of
migrating from one address space to another quick and easy (no templates are required to change).
