Table of Contents
Advertisement
A View is a visual hierarchy of servers and services. There are two types of views in Services Manager.
A Services Manager administrator must first set up the Director View, which then enables the Services
Manager administrator or other network administrators to set up the Operating Views. The Director
View is the hierarchical view that encompasses all servers and services on the network. The Director
View is the whole "pie" of servers and services that you plan to manage using Services Manager
The Operating Views are pieces of the pie, or smaller chunks of the network's servers and services
that you expect to be managed together. The Operating Views cannot be set up until the Director
View is set up. The pie cannot be cut unless it has been made. Operating Views can overlap. In other
words, you can have servers and services belonging to more than one Operating View. Users are set
up after the Views are defined. More than one User can have management privileges over the same
view.
3.1.3
VitalQIP Access control
Access Control (AC) is a feature that allows a network administrator to control which machines are
allowed access to which subnets, based on subscriber and device information. This is implemented by
mapping a User Class to these devices (via MAC address) and subscribers.
Subscribers and devices can either be added by an administrator (Administrator registration), or
automatically added by the system when a subscriber comes online and authenticates him- or herself
(Automatic registration). For Administrator device registration, the administrator logs onto the AC GUI
and creates the subscriber and then creates the device, associates them both, and assigns a User
Class. At this point, QIP will update the DHCP cache with the MAC-User Class mapping. When the
device comes onto the network, it already exists in the DHCP server cache, and thus automatically
gets service. For Automatic registration, the device does not yet exist in the DHCP server‟s cache,
thus it gives the user an IP from the default subnet. The user must then log onto the Self-Reg GUI
accessible from the default subnet. We automatically look up their MAC address (either in the DB if
the lease update has propagated to QIP already or via the Active Lease Service on the remote) and
associate it with the subscriber they logged on as and the subscriber's User Class. QIP sends the info to
the DHCP server, the user reboots and gets service.
Access Control Self Registration - The Access Control functionality implemented in 7.2PR1 is
expanded to include a new Self Registration module. Customers will be able to register themselves
and/or their devices via the Self Registration module. The self registration module will allow users to
authenticate themselves (they must already be defined a subscriber in QIP) and register a new device
for which MAC address is not defined in VitalQIP.
3.1.4
VitalQIP ENUM Manager
VitalQIP ENUM Manager provides a centralized management solution enabling administration of ENUM
domains (e.g., e164.arpa.) and the Naming Authority Pointer (NAPTR) records in VitalQIP
Lucent DNS server. VitalQIP
®
VitalQIP
database and manage and update Lucent DNS servers. Lucent‟s DNS server resolves queries
for telephone number to URI/URL translation for On-Net calling and other ENUM capabilities.
Using an XML/SOAP interface, E.164 records can be loaded from a variety of sources into VitalQIP
The interface supports dynamic loading of new records from provisioning systems, such as Alcatel-
VitalQIP Product Description
®
ENUM Manager provides the ability to administer ENUM records in the
Copyright © 2011 Alcatel-Lucent Technologies
USE PURSUANT TO COMPANY INSTRUCTIONS
®
and the
®
.
Page 36 of 50
Advertisement
Table of Contents
