Alcatel-Lucent VitalQIP 7.2 Product Description page 21

VitalQIP Product Description
VitalQIP AutoDiscovery includes a configurable Diff Engine that can compare the two inputs
received from network data extraction and VitalQIP data extraction. The output of the Diff
Engine is displayed in a user-friendly HTML format. The users can also filter the reports to see
subsets of the report like view dynamic addresses, view static addresses, filter out zero MAC
addresses etc. For programmatic processing of the output, this information is also available in
an XML format.
AutoDiscovery includes the following components:
Network Data Extractor – Discovers the Ethernet and IP network elements and related
equipment configuration information for a set of one or more subnets defining the scope of
the network query. The Network Data Extractor uses Request Profiles to determine the
scope of network discovery and other parameters applicable to the network discovery
request.
VitalQIP Data Extractor – Extracts the corresponding VitalQIP object data for the set of
subnets used by the Network Data Extractor. The VitalQIP Data Extractor uses the same
Request Profiles as the Network Data Extractor to determine the VitalQIP Organization and
list of subnets from which to extract the object data.
Diff Engine – Compares the output of the Network Data Extractor and the VitalQIP Data
Extractor, and based on a configurable set of fields (referred to as "Diff Keys"), generates a
Diff Report showing the differences between the two sets of data.
Administrative GUI – Permits the configuration of the Network Data Extractor and the
VitalQIP Data Extractor. In addition, it is the mechanism for invoking each of these
processes, and provides access to the various Diff reports.
Request Handler – Handles GUI/CLI requests to run Network Data Extractor, VitalQIP
Data Extractor and Diff Engine. It provides a common interface for all three requests. It is
logically made up of one request handler to interface with each of the three components of a
discovery job. A fourth request handler, not shown in the illustration, permits all
components to be run as a single request.
Job Status Manager – Maintains the status of requests for Network Data Extraction,
VitalQIP Data Extraction and Diff Report. It is responsible for determining when requested
actions are allowed.
Appliance Manager – This tab is used if the deployment includes the Alcatel-Lucent Integrated
Appliances. It is accessed to manage all appliances in the architecture, including the Enterprise Server
and/or the Remote DNS and DHCP appliances.
©
Copyright 2009 Alcatel-Lucent
Use pursuant to company instructions
Features
Page 21