VitalQIP Product Description
Product
Capabilities
VitalQIP Architecture
VitalQIP Enterprise Server
Arbitrates and validates access to the
information, controls IP services and
interfaces to the data repository
Relational (RDBMS) VitalQIP
database
Sybase or optional Oracle
VitalQIP Clients: Windows, Motif,
Web, CLIs
DNS, DHCP, Bootp, NIS, Local
Host Files
Remote Servers
IP address registration, DNS/DHCP configurations, and administrator definitions are stored in a central
RDBMS repository. This database can be based on an Oracle or Sybase engine and can reside on a Sun
Solaris, Windows, RedHat Linux or Alatel-Lucent Appliance. Alcatel-Lucent Technologies currently
ships VitalQIP software with a run-time version of Sybase. Alcatel-Lucent Technologies does not resell
or embed Oracle, which must be licensed separately by the customer.
Once installed and configured an appliance is turned up, the central database – or Knowledgebase – is the
center of the VitalQIP services. From this point, all DNS configurations, DHCP registrations,
administrator profiles, and addresses are maintained. The Knowledgebase then becomes the source of
information for network topologies, IP services (DNS and DHCP) information and configuration models,
administrative privileges, and profiles of individual network object profiles (such as cable modem, hubs,
routers, servers, etc.). The Knowledgebase is maintained and manipulated by both IP services and
distributed administrators using an intuitive GUI. The Knowledgebase then extends itself for the
management and maintenance of DNS and DHCP operations.
All DNS/DHCP servers communicate to the centralized database only for initial configuration or updates,
as configuration files or boot files are modified or removed. Servers can be configured to send update
information to the database as IP addresses are leased, renewed, or re-leased for DHCP and for external
dynamic DNS updates, say from Windows clients, for DNS.
Each enterprise server consists of additional daemons/services that control scheduling, remote
connections, and message queuing.
Copyright
©
2009 Alcatel-Lucent
Page 8
Use pursuant to company instructions
