Siemens FMX 4

back
System Administration
AccessIntegrator V3.3
UMN:ADMN
A50010-T3-B100-1-7671
UMN:ADMN System Administration
!
Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts can also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in prop-
erty damage.
Therefore only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to
comply with the applicable safety standards.
Copyright (C) Siemens AG 1998
Issued by the Information and Communication Networks Group

Hofmannstraße 51
D-81359 München
Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
AD – 2 A50010-T3-B100-1-7671
System Administration UMN:ADMN
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1 Manual concept and target groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Manual layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
2 ACI user administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Organization of function permissions in ACI . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 Permission classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.1 Creating ACI-specific global user groups . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.2 Editing the permission class table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.2.1 Defining a new assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.2.2 Changing or deleting assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.3 Function permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.3.1 Editing the function permission table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.3.1.1 Enabling or disabling functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.4 User administration after installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.5 Remote login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
3 Backup and restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Backup concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.1 Regular backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.2 Backups performed according to events. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2 Database backup and restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.1 Backing up the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.2 Restoring the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.2.3 Problems when backing up and restoring the database . . . . . . . . . . . . . . . 3-5
3.3 NE data backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.3.1 NE data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.3.2 NE data restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.4 ACI software backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
4 ACI configuration and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Configuring test and trace functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Checking events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3 Checking performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3.1 Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3.2 Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.3.3 Performance Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.4 Managing printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.5 Virus protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
5 Initialization parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 AccessIntegrator client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2 AccessIntegrator server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.3 AccessIntegrator DCN server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AP-1
A50010-T3-B100-1-7671 AD – 3
Illustrations
Fig. 2.1 Checking a user’s function permissions . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Fig. 2.2 “User Roles” dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Fig. 2.3 “Define new User Role” dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Fig. 2.4 “User Rights” dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Bild 2.5 Modifying default user rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Fig. 3.1 Database backup procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Fig. 3.2 Backup progress window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Fig. 3.3 Database restore procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Fig. 3.4 Message indicating the progress of the restore procedure. . . . . . . . . . 3-4
Fig. 3.5 NE backup procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Fig. 3.6 NE restore procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Fig. 3.7 NE backup dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Fig. 3.8 Restore dialog for a single network element. . . . . . . . . . . . . . . . . . . . . 3-8
Fig. 4.1 Event log of applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Fig. 4.2 Event details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Fig. 4.3 ACI performance features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Fig. 4.4 Process information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Fig. 4.5 Performance Monitor log settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Fig. 5.1 Registry Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Fig. 5.2 Modifying a parameter value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
AD – 4 A50010-T3-B100-1-7671
Tables
Tab. 1.1 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Tab. 2.1 Assigning permission classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Tab. 2.2 Permission classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Tab. 2.3 Default user rights according to ACI permission classes. . . . . . . . . . . . 2-6
Tab. 2.4 Internal Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Tab. 4.1 Event types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
A50010-T3-B100-1-7671 AD – 5
AD – 6 A50010-T3-B100-1-7671
1 Introduction
This chapter is an overview of:
• The O.N.M.S AccessIntegrator documentation and the various target groups
(O.N.M.S = Optimized Network Management System)
• The manual concept
• The notational conventions used.
1.1 Manual concept and target groups

The following AccessIntegrator documentation describes the management of networks
with AccessIntegrator (ACI):
– Technical Description (TED)
– Operating Manual (OMN)
– System Administration Manual (ADMN)
– Installation Manual (IMN).
Each of these manuals is intended for a particular target group as described below.
TED The Technical Description is aimed at those with a general interest in AccessIntegrator.
It contains an introduction to Access Network management using AccessIntegrator,
describes the system architecture, and provides an overview of the functionality of
AccessIntegrator.
OMN The Operating Manual is intended for those involved in the configuration and monitoring
of Access Networks and network elements. It contains step-by-step instructions on
performing the various configuration and monitoring tasks.
ADMN The System Administration Manual is intended for those responsible for ensuring the
smooth operation of the AccessIntegrator components. It describes the security mech-
anisms available and explains their use (e.g. data backup and restore).
IMN The Installation Manual is aimed at those responsible for installing the AccessIntegrator
software and configuring the underlying system. It contains detailed instructions on how
to install the individual AccessIntegrator components.
1.2 Manual layout

All of the O.N.M.S AccessIntegrator manuals listed above have basically the same
structure:
– a table of contents
– a list of illustrations
– a list of tables
– an overview of the entire manual
– the specific description
– a list of abbreviations.
A50010-T3-B100-1-7671 1–1
1.3 Notational conventions

The following notational conventions are used in all the manuals:
Notational convention Meaning
Courier Input and output

Example: Enter LOCAL for the server name.
Command not found
Italics Variables
Example: name can be up to eight characters in length.
Bold Special emphasis
Example: This name must not be deleted.
“Quotes” User interface labels (e.g. windows, menu items, buttons)
Example: Click the “OK” button.
Select the “File” menu.
<Courier> Keyboard shortcuts
Example: <CTRL> <ALT>+<ESC>
→ Menu sequences
Example: “File” → “Exit”
Additional information
i
Warnings at critical points in the procedure described
!
Tab. 1.1 Notational conventions
1–2 A50010-T3-B100-1-7671
2 ACI user administration

Function permissions are controlled on the ACI server by means of ACI permission
classes. These permission classes can be linked to global Windows NT user groups, in
which case all NT login names in the group are granted access to particular ACI func-
tions.
This chapter contains:
• An introduction to the organization of function permissions in ACI
• Information on the assignment of permission classes to user groups
• Information on granting or withdrawing access to ACI functions
• A recommendation for user administration after installation
• A description of the remote login option.
2.1 Organization of function permissions in ACI

The ACI functions available to a particular user depend on the following:
– the global NT user group to which the NT login name used belongs
– the ACI permission class assigned to the global user group
– the functions permitted in the permission class
NT workstation NT domain controller

1
Global groups:
Network
3 Maintenance
ACI client Customer Organization
2 .
.
6
4 7
5
ACI server
Permission classes: Global groups:
Super user Network
Operation & Maintenance Maintenance
Subscriber LineTest Customer Organization
Intelligence Features .
System Administration .
Subscriber Management .
Fig. 2.1 Checking a user’s function permissions
1. The user logs in under his/her login name from an NT workstation in the network.
The validity of the login name is checked in the NT domain controller.
2. If the login procedure is successful, the NT domain controller grants the login name
access to the NT workstation.
3. The user then starts the ACI client.
4. The ACI client transfers the login name and the workstation ID to the selected ACI
server.
A50010-T3-B100-1-7671 2–1
5. The ACI server requests and receives from the NT domain controller a list of the
global groups to which the login name belongs.
6. The Domain server sends the list of groups to the ACI server. The ACI server then
checks whether a permission class has been assigned to one or more groups, and
if so, which functions are permitted in each class respectively.
7. If permission classes have been assigned, the ACI server sends a list of permitted
functions to the ACI client.
Several ACI servers in a single NT domain

If the Windows NT domain controller manages several ACI servers, it is possible to
assign different permission classes to the global groups on the individual ACI servers.
For example, if the NT domain controller manages ACI server 1 and ACI server n, ACI
permission classes can be assigned separately on each server:
NT domain controller ACI server 1 ACI server n

Global groups Assigned Assigned
permission class permission class
Network Subscriber Line Test Intelligence Features
Maintenance Operating&Maintenance Operating&Maintenance
Customer Organization Subscriber Management Subscriber Line Test
Tab. 2.1 Assigning permission classes
With a user name, that e.g. belongs to the global user group Network one can under the
control of :
– Server 1 execute all functions permitted in the Subscriber Line Test permis-
sion class
– Server n execute all functions permitted in the Intelligence Features permis-
sion class
Global user groups without a permission class

If a global user group has not been assigned a permission class, AccessIntegrator
cannot be started under any login name of this group. The ACI application can only be
started by the administrator for the domain.
2–2 A50010-T3-B100-1-7671
2.2 Permission classes

Following the installation of ACI, there are six predefined permission classes:
Permission class Recommended functions
“System Administration” In this class, permission classes are assigned to global user groups
and the functions permitted in a permission class are defined.
The global group to which permissions are assigned must have
administration rights for the domain.
“Super user” This class grants permission to use all ACI functions.
The global group to which permission is assigned must have local
administration rights.
“Operation and Maintenance” This class grants permission to use the functions required to
operate the Loop Manager and to configure and maintain NEs and
boards.
“Subscriber Management” This class grants permission to generate, modify, or delete

subscriber data.
“Subscriber Line Test” This class grants permission to access the measuring equipment
(MEU= measurement unit) and functions used to test the line.
“Intelligence Features” This class grants permission to use the functions required to test
telephone connections.
Tab. 2.2 Permission classes
When the ACI client is first started, all menus are disabled, and the appropriate permis-
i sions must first be assigned, and furthermore, the assigned permissions do not come
into effect until the ACI client is restarted.
One permission class can be assigned to each global NT user group. It is recommended
that you create separate global groups for ACI users which reflect the permission
classes.
2.2.1 Creating ACI-specific global user groups

Global user groups are created on the NT domain controller. A global group can be a
member of a local group, but a local group cannot be a member of a global group.
To create a new global NT user group, activate the Start menu and select “Programs”
→ “Administrative Tools (Common)” → “User Manager for Domains”
The “User Manager” window is displayed. Select the “User” entry and the “New Global
Group” function. The associated dialog is then opened.
In the dialog box, enter the name of the new group and, if desired, a short description of
the group. At the bottom of the box, select the login names to be included in the new
group and click the “←Add” button.
Further information can be found in your Windows NT documentation or in the NT Help
system.
A50010-T3-B100-1-7671 2–3
2.2.2 Editing the permission class table

Assignments between global Windows NT user groups and ACI permission classes are
made in the ACI “User Roles” table. You can open this table if your Windows NT login
name belongs to the NT global group Domain Admins or to a global group with the
permission class System administration or Super user assigned.
Following the installation of ACI, the table furnishes a link to the Domain Admins global
group and the System administration permission class. This link cannot be
deleted!
To open the table select “Security” → “User Roles”.
Fig. 2.2 “User Roles” dialog
The “User Roles” window lists all global user groups in the “NT global groups” column.
The associated permission classes are listed in the “OS Permission Class” column.
2.2.2.1 Defining a new assignment

1. In the “User Roles” window, click the “New” button.
The “Define new User Role” dialog box is displayed.
Fig. 2.3 “Define new User Role” dialog
2–4 A50010-T3-B100-1-7671
2. In the “Windows NT global group” field, select the global group to which the new
permission class is to be assigned.
This list only includes those NT user groups which have no assigned ACI permission
class.
3. In the “Permission class” field, select the permission class.
4. By clicking “OK” , the selection is added to the database. The dialog window closes
and a corresponding entry appears in the “User Roles” window.
If you wish to cancel your selection, click the “Cancel” button. The “Define new
Permission Class Entry” dialog box is closed, and the list of assignments in the “User
Roles” window remains unchanged.
5. When you have defined all the desired assignments, click the “Close” button in the
“User Roles”.
New entries in the “User Roles” table do not become effective until ACI Client is
i restarted.
2.2.2.2 Changing or deleting assignments

To change an assignment, you must first delete the assignment between the NT user
group and the ACI permission class, and then define a new assignment.
To delete an assignment, proceed as follows:
1. In the “User Roles” window, select the entry you wish to delete .
2. Click the “Delete” button. You will be asked to confirm whether you really wish to
delete the selected entry, select “Yes” to delete, or “No” to cancel the procedure.
3. You then have two options:
– exit the “User Roles” list box using “Close”, or
– define a new assignment by clicking the “New” button and proceeding as
described under “Defining a new assignment”.
Changes to the “User Roles” table do not become effective until ACI Client is restarted.
i
A50010-T3-B100-1-7671 2–5
2.3 Function permissions

For each ACI permission class, it is possible to define the functions that can be executed
within that class. The list of functions is stored in the AccessIntegrator “User Rights”.
This table is preconfigured following installation and contains the following entries:
Operation & Maintenance
Subscriber Management
Intelligence Features
Subscriber Line Test
Super user
ACI-Commands in “User Rights” table
File Network Editor X X
View NEs in Maintenance Mode X X X X X

with Disabled Alarms
with Service ID Set
Disconnected
Connections X X X X X
Time-scheduled Jobs X X
Configuration NE Configuration General NE Parameters X X X X X

User Data X X X X X
NE Status X X X X X
Loop Management X X X X X
Cross Connect 64 kbit X X X X

2 Mbit X X X X
34 Mbit X X X X
V5 Interface X X X X X
Leased Line Management X X X X
Software Management APS Management X X X
Parameter Download X X X
NE Backup X X X
NE Restore X X X
UAK Backup X X X
UAK Restore X X X
Mobility Administration RDU Global Data X X X

POC Public Operator Code X X X
Tab. 2.3 Default user rights according to ACI permission classes
2–6 A50010-T3-B100-1-7671
Super user
Configuration Network Configuration Path Management Modify Path X X X X

Display Details
Service Management Create Service X X X X

Learn Service
Subscriber Management X X X X X
Air Connection Management Repeaters X X X X

Subscribers X X X X
Service/Path Management Delete Service/ X X X X X

Path
Equipment View Create Service X X X X X
Fault Alarm List X X X X X

Alarm Status X X X X X
Alarm Configuration X X X X
Alarm Media Configuration X X X X X
Acknowledge X X X X X
Alarm Log Display X X X X X

Alarm Log Administration X X X
Event Log Display X X X X X

Event Log Administration X X
Disconnected NEs Media X X X X X

Configuration
Detached RNT’s X X X X X
Measurement Traffic Traffic Measurement X X

PDPT X X
Performance Log Display X X X X X

Log Administration X X X X
Performance Data X X X X
Configuration X X X X
Subscriber Line Test Log Display X X X

Log Administration X X X
Subscriber Line Test Data X X X X
Configure Automatic Test X X X X
Configure Manual Test X X X X X
Configure Battery Test X X X X X
Security User Roles X X
User Rights X X
Tab. 2.3 Default user rights according to ACI permission classes (Cont.)
A50010-T3-B100-1-7671 2–7
Super user
Utilities Inventory Data Retrieval Equipment Data X X X X X
Store Inventory Data X X X
NE Upload Configuration Parameter X X X

Current Status Data X X X
Log file Data X X X
Memory Dump X X X
Trace Error Log X X X
Diagnostic Information X X X X
Mass Provisioning Mass Provisioning from File X X X

Upload Configuration X X X
Download Configuration X X X
Qd2 Telegram Trace X X X X
Consistency Check X X X X X
DCN Address Change X
Media Configuration X X X X X
Media Event List X X X X X
Options Views X X X X X
Mobile Parameter Formats X X
Startup Options X X X X X X
Internal Com- Cross Connect Conference X X X X X X
mands Configuration of CTM Global X X X X X X
Data
Open Air Interface Dialog at X X X X X X

Path Operation
Export Subscriber Data X X X X X X
Open the job scheduler X X X X X X
Tab. 2.3 Default user rights according to ACI permission classes (Cont.)
In addition to the permissions that can be allocated to a menu tree, it is also possible to
enable or disable particular functions. These functions are located under Internal
Commands in the “User Rights” table as well as in the Network Configuration
menu item.
These particular commands are shaded in the table above. They are defined as follows
in the table below:
2–8 A50010-T3-B100-1-7671
“Enabled Functions” / “Disabled Functions” Meaning
Configuration → Network Configuration → Modify Service ID and address of a path;

Path Management → Modify Path Enable/Disable “Modify” button in “Path Management” dialog box.
Configuration → Network Configuration → Display the reserved network resources of a path;

Path Management → Display Details Enable/Disable “Details” button in “Path Management” dialog box.
Configuration → Network Configuration → Create a Service;

Service Management → Create Service Enable/Disable “Create” button in “Service Management” dialog box.
Configuration → Network Configuration → Recognizes existing physical paths in the network and create them au-
Service Management → Learn Service tomatically in path and service management (ACI database);
Enable/Diable “Learn” button in “Service Management” dialog box.
Configuration → Network Configuration → Delete created services or paths;

Service/Path Management → Delete Service/Path Enable/Disable “Delete” button in “Service Management” and “Path
Mangement” dialog box.
Configuration → Network Configuration → Start the creation of a service by selecting a line card in the Equipment
Equipment View → Create Service View; Enable/Disable the menu item “Create Service” in the context
menu.
Internal Commands → Cross connect Conference Create cross connect conferences;

Enable/Disable “Conference” button in “Cross Connect” dialog box.
(Menu “Configuration” → “NE Configuration” → “Cross Connect”).
Internal Commands → Configuration of CTM Configure DECT subscriber data global to all the CTM RDUs in the net-
Global Data work; Enable/Disable “CTM Global Data” button in “Configure CTM
Global Data” dialog box.
(Menu “Configuration” →“Mobility Administration” →“RDU Global
Data”).
Internal Commands → Open Air Interface dialog Configure the air interface for mobile services during the “Create
at path operation Service” function;
Open the “Air Connection Layer” dialog when creating a service/path.
Internal Commands → Export Subscriber Data Export the subscriber data on an RDU to a file, for use of the DECT
Locator; Enable/Disable “Export” button in “Air Connection Layer”
dialog box.
(Menu “Configuration” →“Network Configuration” →“Air Connection
Management”→ “Subscribers”).
Internal Commands → Open the job scheduler Issue, modify, or delete scheduled jobs (in this version only relevant for
SW download);
Enable/Disable “Schedule” button in “Download Mode” dialog box.
Tab. 2.4 Internal Commands
A50010-T3-B100-1-7671 2–9
2.3.1 Editing the function permission table

The “User Rights” table can be edited when you are logged in to Windows NT under a
password that belongs to to the Domain Admins global group or to a global group that
is assigned to System Administration or Super user ACI permission class. To
display the table, select:
Menu “Security” → “User Rights”.
Fig. 2.4 “User Rights” dialog
The “User Rights” window contains the following information. In the field:
“Permission Classes” Select the permission classes for which enabled and disabled
functions are to be displayed.
“Enabled” Lists the menu items/functions enabled in the selected permis-
sion class.
“Disabled” Lists the menu items/functions disabled in the selected permis-
sion class.
2.3.1.1 Enabling or disabling functions

1. In the “Permission Classes” field, select the permission class whose range of func-
tions is to be modified. The two list boxes display the associated enabled and
disabled functions.
– If you wish to disable all enabled functions, click the “Disable All” button.
– If you wish to disable only one currently enabled function, select the function in
the “Enabled” area and click “>>”.
– If you wish to enable all disabled functions, click the “Enable All” button.
– If you wish to enable a function which is currently disabled, select the function in
the “Disabled area” and click “<<“.
2. Finally click the “Apply” button. The current list of enabled functions for the selected
permission class is then added to the database.
2 – 10 A50010-T3-B100-1-7671
If you click “Close” without first clicking “Apply”, the dialog is aborted. In this case, data
relating to the permitted functions remains unchanged in the database.
Changes to the “User Rights” table do not become effective until ACI Client is restarted.
i
2.4 User administration after installation

Following the installation of the ACI software, a user profile is furnished in the “User
Roles” table, namely the assignment of the global group Domain Admins belonging to
the ACI permission class System administration. This permission class then al-
lows access only to Security Management, through which users can be defined and ac-
cess rights assigned.
During the initial start up of an ACI client you also have the option of changing the default
settings of the individual permission classes, while the database is still empty. The de-
fault values are always valid for all ACI clients.
Consider the following consequences before modifying the default values:
If modifications are made, they cannot be revoked once they have been stored as per-
sistent data in the database. Independent of the default values - except the System
administration class - each permission class can be modified by enabling or dis-
abling functions.
Tab. 2.3. is an overview of the default values of the six ACI permission classes.
After a successful start of the ACI server, the following steps are recommended:
1. Start the ACI Client. A message window is displayed:
Bild 2.5 Modifying default user rights
2. Decide whether or not you wish to modify the default values:

“Yes” The “User Rights” dialog window opens ( Fig. 2.4), in which
you can modify the default functions of each ACI permission
class.
“No” or Transfer the preset values to the ACI database.
“Cancel”
3. Define Windows NT global groups (NT Domain Server) for the ACI user, if you have
not already done so.
4. Assign the global user groups according to an ACI permission class. To do so, open
the “User Roles” table, see section 2.2.2.
5. Modify, if desired, the function scope of the ACI permission classes in the “User
Rights” table. See section 2.3.1.
A50010-T3-B100-1-7671 2 – 11
6. Close the ACI Client and restart to apply the modifications.

Windows NT allows for membership in multiple global groups. This enables an ACI user
i to be assigned to more than one permission class. If an ACI user belongs to several per-
mission classes, he has the access rights of all these permission classes. As system
administrator, you then have additional variation options when assigning access rights.
2.5 Remote login

It is possible to access an AccessIntegrator server from a remote computer via the
Windows NT Remote Access Service (RAS). This may be useful, for instance, for the
diagnos of problems through the Technical Assistant Center (TAC).
The NT User Manager for Domains of the RAS server can grant access permission to
each individual login name in each associated domain. Automatic callback can also be
defined separately for each selected login name.
The following requirements must be met when logging in from a remote system:
– RAS must be installed correctly on the ACI server and the remote system.
– RAS must be configured in accordance with the network used (telephone network,
X25, or ISDN).
– In the case of automatic callback, the telephone numbers for the login name with
access to the ACI server must be preset on the RAS server.
– The login name used on the remote system must be known in the ACI server
(domain ID) and have access permission for the server.
– The Phone Book on the remote system must contain at least one entry for the
server.
– If you require file transfer from the ACI server to the remote system, the relevant
directories on the server must be released for network access (shared).
– The drives for the network must be connected to the remote computer using the File
Manager.
If these requirements are fulfilled, logging in to the ACI server from a remote system is
accomplished via the following procedure:
1. On the remote computer, click the “Remote Access Service” icon, and in this
program group, select the “Remote Access” icon. The Phone Book opens.
2. In the Phone Book, select the entry for the ACI server and click the “Dial” button.
The connection to the ACI server is then established and the login name checked. If the
login name is found to have the correct permissions, the server entry in the Phone Book
is marked as connected.
The Windows NT Event Viewer logs the activities on the RAS server and all attempts to
violate network security (see section 4.2). Further information on RAS can be found in
the corresponding Windows NT documentation.
2 – 12 A50010-T3-B100-1-7671
3 Backup and restore

All current AccessIntegrator data must be backed up at regular intervals, irrespective of
whether the data:
• is managed in the database (e.g. function permission table)
• describes network elements
• belongs to the ACI software (e.g. configuration files).
A backup may be crucial in cases where the database has been corrupted, due to
unforeseen events, and lost data must be restored. Unforeseen events can include, for
example Hardware failure, Virus infiltration or Faulty operations that result in data loss
or inconsistencies.
This chapter describes the recommended backup concept, and details the backup and
restore procedure for the three data types listed above.
3.1 Backup concept

A data backup performed at regular intervals, e.g. before an upgrade of the ACI soft-
ware, ensures accurate and up-to-date data restoration.
The backups should be copied onto an alternative medium such as tape. The Windows
NT Backup application can be used for backups (see section 3.4).
3.1.1 Regular backups

Daily backups
The database should be backed up daily. Approximately five tape sets are required,
depending on the size of your database and the capacity of your tapes. Use a new tape
set every week and proceed as follows:
– Start with the first tape set on a Friday.
– On the following Monday, switch to a new tape set and back up your data each day
until the end of the week.
– Change to the next tape set the following week.
– After the fifth week, insert the first tape set and reinitialize it.
This procedure enables you to restore the contents of your database from the previous
four weeks if necessary.
Weekly backups
Make sure you use a different tape set for each weekly backup.
Monthly backups
The network element files from the entire network should be saved on the ACI hard drive
once a month. By doing so, ACI creates a directory structure that corresponds to the
SISA tree. This directory structure should then be backed up on tape.
A50010-T3-B100-1-7671 3–1
3.1.2 Backups performed according to events

In this context, events include:
– network integration
– ACI software upgrades
– changes to the NE configuration or the ACI data.
Following network integration

To retain a defined initial status, network element data should be backed up to the ACI
hard disk following installation of the ACI software and the database. Before beginning
network administration, it is also recommended that the Windows NT file system be
backed up.
Before upgrading the ACI software

To protect the integrity of the database, a database backup should be performed before
upgrading the ACI software.
Changes to the NE configuration or the ACI data

Following frequent changes to the NE data (e.g. numerous cross connects in CMXII or
subscribers in the RDU), it is recommended that a backup run be initiated. It is also
advisable to back up the ACI software if, for example, the configuration files are modi-
fied.
3.2 Database backup and restore

Backing up as well as restoring may be carried out via ACI with the help of two routines,
which are offered in the Windows NT Start menu.
The name of the database is provided by the system internally, as well as the directory
for the restore copy. This means that at each new save routine, the existing files are
overwritten. It is therefore advisable that the data be saved on an external medium (i.e.
tape).
In order to ensure risk free backing up and restoring, the names of the database and
! directories should never be altered.
3.2.1 Backing up the database

There are two steps involved in backing up a database (see Fig. 3.1):
1. The database, named MLOS.bkp is first written to a particular directory using the
ACI application “Backup”. The default directory is
..\ACI installation directory\OS_BACKUP.
2. The directory can then be copied to tape using Windows NT Backup.
3–2 A50010-T3-B100-1-7671
Database Backup
ACI Backup
DIR
NT
Tape
Backup
Fig. 3.1 Database backup procedure
Starting the backup procedure

1. In the Start menu, select “Programs” → “AccessIntegrator Server” → “Backup”.
Backup of the database begins in the backup directory and a dialog window opens,
displaying the progress of the backup.
Fig. 3.2 Backup progress window
2. As soon as the copy function is complete, the window closes automatically.

3. Then save the directory via Windows NT onto tape (see section 3.4).
A50010-T3-B100-1-7671 3–3
3.2.2 Restoring the database

When the database must be restored, restoration can be accomplished via the directory
..\ACI installation directory\OS_BACKUP.
When the data is only available on tape then it must be transferred via Windows NT into
this directory. Afterwards, restore the database with the help of the ACI application
“Restore”.
Backup
DIR ACI Restore Database
NT
Tape Backup
Fig. 3.3 Database restore procedure
Starting the restore procedure

1. Open the task manager and select “End Task” in the tab “Applications” to end the
following tasks:
– ACI client
– ACI server
– DCN server.
2. In the Start menu select “Programs” → “AccessIntegrator” → “Restore”. Restoration
of the database in the database directory begins and a dialog window appears.
Fig. 3.4 Message indicating the progress of the restore procedure
3–4 A50010-T3-B100-1-7671
3. In this dialog window, you will be asked whether you wish to add data records from
the current log file to your database in addition to the archived data records. If you
answer with
y all changes will be incorporated in the restore process. You must therefore save
the file logical.log to another location so that it is not overwritten during the
restoration. The current default storage location is C:\Versant\DB\MLOS.
As a new storage location, _backup_.log is suggested.
n the restore procedure begins immediately. n should be specified only if the
current database status is no longer required.
The progress of the restore procedure can be monitored in the dialog window. When
the entire database has been restored, the dialog box automatically closes.
4. Open the DOS window and enter the following command:

dbuser -add -P MLOS
5. Restart the processes in the following order:
– DCN server
– ACI server
– ACI client.
3.2.3 Problems when backing up and restoring the database

If the database backup and restore routines do not run successfully, the errors can be
of various types. The error analysis may only be completed by persons with sufficient
knowledge and experience with the Versant database system. It is recommended that
the Siemens-Service personnel specializing in Versant backup/restore functions be
contacted.
A50010-T3-B100-1-7671 3–5
3.3 NE data backup and restore

The configuration data of network elements is backed up in two stages:
1. The network configuration data, stored in the respective network elements, is copied
to the AccessIntegrator hard disk. During this process, ACI creates a directory struc-
ture that corresponds to the SISA tree.
The data is stored in the directory ..\ACI installation directory\ne.
2. The configuration data can then be backed up to tape from the directory structure.
DIR
NE NE Backup
tree
NT
Tape
Backup
Fig. 3.5 NE backup procedure
During restoration, the data is, if necessary, first transferred from tape into the directory
on the hard drive. Then the NE data can be restored from the directory structure.
DIR
tree NE Restore NE
NT
Tape Backup
Fig. 3.6 NE restore procedure
3.3.1 NE data backup

Due to the time consuming nature of this procedure, it is recommended that large
networks be backed up in sections, e.g. subnetworks.
Starting the NE backup
1. In the network map, select the subnetwork or a set of NEs; by selecting nothing the
entire network (TOP) is designated for backup.
2. In the ACI main menu, select “Configuration” → “Software Management” →
“NE Backup”. The window “Backup of...” appears:
3–6 A50010-T3-B100-1-7671
Fig. 3.7 NE backup dialog
3. Define the scope of backup (only for the entire network or subnetworks):
“Selected only” Only the network elements of the selected
subnetwork are backed up.
“Selected and below” All network elements belonging to the selected
subnetwork or to some subnetwork below the
selected one are backed up.
4. Choose the “Mode of Operation” (only for a single NE or multiple selection):

“Choose FT wherever applicable” Data transfer is to take place by means of file
transfer. This option is preferable, as it is safer
and faster.
“Use only Qd2 telegrams” Data transfer is to take place by means of QD2
telegrams.
The file transfer option is preferable, as it is safer and faster. If an NE doesn’t support this
i mode, data transfer will automatically be done via QD2 telegrams .
5. Finally click “Start”. ACI will then warn you that the operation may take time.
6. Click “Yes” and the backup process begins.
The progress of the backup is displayed in the dialog “Backup of...” using the
counters “Finished :: Total” and/or progress bars.
A50010-T3-B100-1-7671 3–7
7. The backup is complete when the following message appears:

Backup - Network Element(s) completed successfully or
Backup - Network Element(s) completed with errors
8. The logfile can be displayed on the screen with the “View” button.
9. Afterwards, backup the directory structure of the NE data onto tape via the Windows
NT backup function (see section 3.4).
The logfile back_<computer>.log is stored in the directory

i ..\<ACI installation directory>\Operlog on the ACI server.
The variable <computer> designates the ACI client which has initiated the backup. The
logfile will be overwritten as soon as this ACI client starts again a backup procedure.
3.3.2 NE data restore

If the current configurations are stored in the directory structure with the network
element data, it is possible to restore faulty network elements directly. If this data is
incomplete or not present in the directory structure, the tape backup must be used (see
section 3.4).
Starting the NE data restore procedure

1. Select the NEs to be restored in the Network Map or in the DCN Tree.
2. In the main menu select: “Configuration” → “Software Management”→
“NE Restore”. This opens the “Restore of...” window:
Fig. 3.8 Restore dialog for a single network element
3–8 A50010-T3-B100-1-7671
3. Define the scope of backup (only for the entire network or subnetworks):
“Selected only” Only the network elements of the selected
subnetwork are restored.
“Selected and below” All network elements belonging to the selected
subnetwork or to some subnetwork below the
selected one are restored.
4. Choose the “Mode of Operation” (only for a single NE or multiple selection):

“Choose FT wherever applicable” Data transfer is to take place by means of file
transfer.
“Use only Qd2 telegrams” Data transfer is to take place by means of Qd2
telegrams.
The file transfer option is preferable, as it is safer and faster. If an NE doesn’t support this
i mode, data transfer will automatically be done via QD2 telegrams .
5. Finally click “Start”. ACI will then warn you that the operation may take time.
6. If you respond with “Yes”, the restore procedure is started.
The progress of the restoration is displayed in the dialog “Restore of...” using the
counters “Finished :: Total” and/or progress bars.
7. The following message indicates that restore procedure is complete:
Restore - Network Element(s) completed successfully or
Restore - Network Element(s) completed with errors.
8. The logfile can be viewed by clicking the “View” button.
The logfile rest_<computer>.log is stored in the directory

i ..\<ACI installation directory>\Operlog on the ACI server.
The variable <computer> designates the ACI client which has initiated the restoration.
The logfile will be overwritten as soon as this ACI client starts again a restore procedure.
3.4 ACI software backup and restore

The ACI software is backed up and restored using the Windows NT tape Backup appli-
cation. The backup and restore procedures are very similar; this description therefore
outlines the backup procedure only. Further information can be found in your Windows
NT documentation or in the NT Help system.
When backing up ACI data, remember that the Windows NT directory also contains
important files. Proceed as follows:
1. Insert the backup tape.
2. In the Start menu select “Programs” → “Administrative Tools (Common)” →
“Backup”.
3. In the window that appears, click the “Drives” button.
4. Double-click on the drive containing the data to be backed up.
5. A structure similar to a directory tree is then displayed. Select the files and directo-
ries to be backed up.
6. Click the “Backup” button.
7. This opens a dialog box in which the relevant backup information is entered.
8. Close the dialog with “OK” in order to start the backup procedure.
A50010-T3-B100-1-7671 3–9
3 – 10 A50010-T3-B100-1-7671
4 ACI configuration and monitoring

In the event of a failure or suspected software errors, the Test and Trace functions can
be enabled, in order to locate the errors.
To ensure the efficient operation of AccessIntegrator and to prevent the occurrence of
software faults, the following procedures should be performed:
• configure test and trace functions
• check all application-specific, system-related, and security-related events
• monitor all performance data
• assign and manage printers
• protect against virus infiltration.
4.1 Configuring test and trace functions

Test &Trace is an ACI application which logs messages from all ACI processes. It
usually records error messages only. Test &Trace supports service activities and facili-
tates troubleshooting.
Please note:
A Trace that is in operation always has an influence on the dynamics of a program. The
test and trace function should only be turned on to trace and analyze internal data. The
configuration of the application should only be performed by authorized service personal
or according to the direct instruction of such personal.
After logging, the Test &Trace must be turned off.
!
Trace Configuration File

Test &Trace is enabled and disabled via the configuration file tt.cnf.This file is
contained in the directory ..\ACI Installation directory\OS-conf.
The tt.cnf file contains parameters that control the execution and scope of the Trace
file. These parameters are preset with default values after installation.
Trace Log File

Test &Trace produces one or more log files, stored in the directory
..\ACI Installation directory\Operlog. The name of a log file has the
following format:
<process name><NT process id>.log (e.g. acis170.log)
process name Short name of the monitored process (program):

acic = ACI Client
acis = ACI Server
dcns = DCN Server
lctc = LCT Client
lcts = LCT Server
dcns-lct = DCN Server for LCT
NT process id Process ID (PID); assigned by Windows NT;
see “Windows NT Task Manager” dialog, tab “Processes”.
When the log file has reached its maximum size, its old entries are overwritten one by
one (wrap-around mechanism).
A50010-T3-B100-1-7671 4–1
A trace log file can be read with an ASCII-Editor. Send a copy of the file to the service
center for evaluation.
4.2 Checking events

The Windows NT application “Event Viewer” is used to monitor events in ACI, and is
started automatically with Windows NT.
There are three log groups:
“System” The system log records all events logged by the Windows NT system
components.
“Security” The security log records all security-related events, allowing you to
monitor changes to the security system and possible violations.
“Application” The application log records all events logged by the applications. In
this log you can find all recorded ACI events.
The application log is opened:
1. In the Start-menu choose ”Programs” → “Administrative Tools (Common)” →
“Event Viewer”. This opens the “Event Viewer...” dialog.
2. Select menu “Log” → “Application”. The application log is displayed.
3. Use a filter to reduce the scope of the protocol. Select “View” → “Filter Events...”.
The “Filter” dialog appears.
4. Choose an application in the “Source” list, for which you will get the events, e.g.
ACISERVER (Fig. 4.1).
Fig. 4.1 Event log of applications
In the log, events are listed line by line. The type of event is indicated at the beginning
of the line:
Display Color Meaning
Blue Information
i
Yellow Warning
!
Red Error
Stop
Tab. 4.1 Event types
4–2 A50010-T3-B100-1-7671
Next to the event type the date and time, the application (source), the category, the ID
number, the login name, and the name of the computer are listed. You can display
detailed information on an event by double-clicking on the appropriate line (Fig. 4.2):
Fig. 4.2 Event details
The logging must be set so that entries in the files are overwritten as soon as the log file
has reached the maximum capacity (Wrap Around). The ACI results are output in the
form of a message window when the log file is full.
Checking the log settings:
1. In the “Event Viewer” select the menu “Log” → “Log Settings”. The “Event Log
Settings” dialog window appears.
2. For the Application log, the “Event Log Wrapping” must be selected under the
“Overwrite Events as Needed” option.
system.
A50010-T3-B100-1-7671 4–3
4.3 Checking performance data

Performance data can be obtained via Windows NT. With the application:
• Control Panel check the system and monitor settings
• Task Manager check the application, processor and system performance
• Performance Monitor check the performance data of all computers within the
domain.
In the following section, the polling of the above named performance data for the Access
Integrator is briefly explained. Detailed information can be found in the Windows NT
handbook or in NT Help.
4.3.1 Control Panel

For the flawless operating of AccessIntegrator the following Windows NT settings are
important:
• Foreground application may not have priority
• The virtual memory must be sufficient
• no screen saver may be used.
In case of performance problems, be sure to check these items.
Setting foreground application priority
Following the installation of Windows NT, it is standard that the application in the fore-
ground has priority of the background. This is, however, not ideal and must be altered.
It is especially important for the ACI server that the priority settings between fore- and
background are set on a simultaneous basis:
1. Open the Windows NT control panel via the Start-Menu: “Settings” → “Control
Panel”.
2. Double click “Systems”. The “System Properties” dialog appears.
3. Activate the “Performance” tab (see Fig. 4.3).
4. Set the slide “Application Performance” on “None”.
5. Click “OK” to apply the new setting.
Enlarge virtual memory
The standard Windows NT setting for the paging file is not large enough for AccessIn-
tegrator. This means that Windows NT alone pushes the processor to the 100% of
capacity. The virtual memory must therefore be enlarged, at least double the main
memory of the computer:
1. Open the Windows NT control panel via Start-Menu: “Settings” → “Control Panel”.
2. Double click “Systems”. The “System Properties” dialog appears.
3. Activate the “Performance” tab.
4–4 A50010-T3-B100-1-7671
Fig. 4.3 ACI performance features
4. Click “Change”. The “Virtual Memory” dialog window appears.

5. Depending on your PC, enter the the following values:
– “Initial Size (MB)” : <RAM size* 2>
– “Maximum Size (MB)”: <RAM size* 2>
Click “Set”. The list field in the upper part of the dialog is then updated.
6. Transfer the modifications with “OK”. The dialog window closes and control reverts
back to the “System Properties” dialog.
7. Conclude the dialog with “OK” and restart the computer.
Deactivating the screen saver
A screen saver must never be used on the ACI computer that requires too much
computer capacity. Especially in connection to an improperly installed priority of the
foreground application. This will lead to Timeouts in AccessIntegrator as the computer
is pre-occupied with the screen saver.
1. Open the Windows NT control panel via Start-Menu: “Settings” → “Control Panel”.
2. Double click “Display”. The “Display Properties” dialog window opens.
3. Activate the “Screen Saver” tab.
4. Select the (None)in the “Screen Saver” list.
5. Confirm with “OK”.
A50010-T3-B100-1-7671 4–5
4.3.2 Task Manager

With the “Windows NT Task Manager” the ACI applications, ACI processes and the
current system performance can be monitored. You also can remove non-reacting
tasks.
Open the dialog window:
• With the right mouse button, click on an open spot in the task list and select “Task
Manager” in the context menu or
• Use the keyboard combination <Ctrl>+<Alt>+<Del> to open the “Windows NT
Security” window and click on the “Task Manager” button.
Fig. 4.4 Process information
“Applications” tab
In this tab, all applications currently running as well as the current status is displayed.
Dependent on the type of your installation (ACI server or ACI client), refer to the
following ACI applications:
– DCNS
– AccessIntegrator startup information
– O.N.M.S AccessIntegrator Server
– O.N.M.S AccessIntegrator Client connected to ...
– API Client
More information on the applications (programs) is available when you click with the
right mouse button and in the context menu select “Go to process”. The “Processes” tab
comes up. The concerned process is highlighted in the list.
4–6 A50010-T3-B100-1-7671
“Processes” tab
All processes are listed in this tab that are currently active (see Fig. 4.4 ). Here you will
find all initiated ACI processes, like:
– dcns.exe
– acis.exe
– acic.exe
– apic.exe
With the exception of the “Image Name” column, the other columns can be accessed via
the menu “View” → “Select Columns...”.
“Performance” tab
With this register, the system performance can be supervised. The individual function of
the system, like the processor capacity, available memory, used memory, cache etc.
4.3.3 Performance Monitor

The Windows NT Performance Monitor allows you to query the performance of a
process, a service, or the network locally or remote from another computer. For
example, you can check the status of the ACI server from the remote ACI client.
Open the dialog window:
Select in the Start Menu: “Programs” →”Administrative Tools (Common)” →
“Performance Monitor”.
In the “Performance Monitor” window, you can choose via the menu “View” between four
views:
“Chart” The selected objects, for example, the processor, a disk or a service can
be displayed during a certain time chart.
“Alert” The threshold values for objects can be defined, which will enable
threshold limit alarms. You can also define the actions subsequently initi-
ated by the Performance Monitor.
“Log” This view offers the option of monitoring objects over a longer period of
time and to log the results of the supervision. The log file can then be
evaluated at a later time.
“Report” This view displays an overview of several monitored objects.
The definition of monitored object is similar in all the views. When you, for example, wish
to save the supervision results from various objects in a log file, follow these steps:
1. Select in the menu “View” the “Log” item.
The display changes to log display.
2. Select in the menu “File” the “New Log Settings” item.
3. In the “Edit” menu, select the “Add To Log”.
The “Add To Log” window appears.
A50010-T3-B100-1-7671 4–7
Fig. 4.5 Performance Monitor log settings
4. Select the computer, on which objects are to be monitored.

5. Select objects and confirm the selection with “Add”. The objects to be added are
displayed in the log display.
6. Close the “Add To Log” window with “Done”.
7. In the log display, select in menu “Options” the item “Log...”.
8. Define in the “Log Options” window, a name for the log file and a directory in which
the data should be saved.
9. Click “Start Log” to start the logging. Halt the logging via the “Log Options” window.
The progress of the logging is displayed in the log display in the “File Size” field.
10. Save the settings via “File” menu.
If you wish to view a log file, proceed as follows:
– open the file with the log settings (.pml) from the “File” menu
– open the log file (.log) via menu “Options” → “Data From...”.
4.4 Managing printers

The Print Manager is opened by clicking the Start menu: “Settings” → “Printers”.
The “Printers” window displays all available printers.
You can perform the following tasks from the “File” menu:
– install printers
– define server properties
– establish links
– delete and rename printers
– change printer properties
system.
4–8 A50010-T3-B100-1-7671
4.5 Virus protection

When exchanging data via the network or on an external data volume, there is always
the danger of virus infiltration. Viruses can result in loss of data or a reduction in the func-
tionality of AccessIntegrator.
To avoid viruses, proceed as follows:
– Make sure you have installed an up-to-date virus checker. These are updated regu-
larly by the manufacturer.
– Check each data volume before copying data onto your system.
– Scan your entire system for viruses regularly.
In the case of an LCT (Local Craft Terminal), it is recommended that you include the
virus checker in the start sequence of your operating system.
If a virus is detected, remove it immediately. If your data has been corrupted, you can
restore the database from the backup directory or from tape (see section 3.2.2).
Transfer NE data from the corresponding NEs to the hard disk (see section 3.3.1).
Automatic virus checking

To automate the virus checking procedure, you must first start the Schedule service.
Select from the Start menu: “Settings” → “Control Panel”.
The “Control Panel” window appears. Proceed as follows:
1. Double click on the “Services” icon.
This opens the “Services” dialog box.
2. In the list of services, select “Schedule”.
3. Click the “Startup” button.
4. Select the “Automatic” start mode.
5. Confirm your selection with “OK”.
The Schedule service will now be started automatically each time Windows NT is
started.
6. In the “Services” window, click the “Start” button.
This starts the Schedule service immediately, i.e. you do not have to wait until
Windows NT is rebooted.
7. Exit the “Services” window.
You can then automate the virus checker as follows:
– create a batch file in which the virus checker is called
– transfer the batch file to the Schedule service using the at command
A50010-T3-B100-1-7671 4–9
The at command has the following format:

at [\\computer] time [/interactive] [/every:date |/next:date]
“command”
computer Name of a remote computer. If this parameter is not specified, the com-
mand is executed on the local system.
time Time at which the command is to be executed (range: 00:00 to
23:59).
interactive Parameter allowing the command to accept input from the user logged
in before being executed.
every:date The command is executed on each specified day of the week or month
next:date (every:) or on the next specified day of the week (next:). If date is not
specified, the current date is assumed.
Possible entries: M, T, W, Th, F, S, Su, or a number between 1 and 31
for the day of the month.
“command” Windows NT command to be executed (.exe or .com) or a batch file
(.bat or .cmd).
If you wish to find out which Schedule services are already available, enter the at
command without any parameters. The output includes the ID (id) required to delete a
service:
at [\\computer][[id] [/delete]]
If you do not specify id, all scheduled commands are deleted.
Further information on the at command can be found in the windows NT Help system.
4 – 10 A50010-T3-B100-1-7671
5 Initialization parameters
Some initialization parameters are essential for the correct operation of the AccessInte-
grator applications. These include, for example, the name of the directory under which
the AccessIntegrator software is stored. Most of these parameters are generated during
installation and are preset to their default values. The initialization parameters of
AccessIntegrator are managed in the Windows NT registry under the key
HKEY_LOCAL_MACHINE.
The following sections list and describe the registry entries specific to AccessIntegrator
Registry entries should only be modified in exceptional circumstances. If the modifica-
! tion of an entry is likely to result in inconsistencies, the relevant entry is marked with an
asterisk (*) in the tables below.
To check or modify registry entries, proceed as follows:

1. In the Start menu, select the menu item “Run”.
2. In the “Run” window, open the Registry Editor by entering regedit.
Fig. 5.1 Registry Editor
In the window, the registry keys are listed on the left-hand side. The key is repre-
sented in the form of a directory containing subkeys.
3. Select HKEY_LOCAL_MACHINE and then the desired subkey.
The associated parameters and their values are displayed on the right-hand side.
4. To edit a parameter, double-click on it. The “Edit String” window opens.
A50010-T3-B100-1-7671 5–1
Fig. 5.2 Modifying a parameter value
5. Enter the new value and confirm with the “OK” button.
The AccessIntegrator initialization parameters are listed in the registry editor under the
registry key
HKEY_LOCAL_MACHINE → SOFTWARE → Siemens AG → AccessIntegrator Vx
This part of the key is abbreviated to mandatory below. x stands for the ACI version
used. Under Siemens AG, the entries branch out as described below:
Parameters for: Stored under the subkey:

ACI clients AccessIntegrator Vx
ACI server AccessIntegrator Vx Server
DCN server AccessIntegrator Vx DCN Server
5.1 AccessIntegrator client

An AccessIntegrator client requires the following registry entries at start-up:
• Key: mandatory
Parameter name Description
OperLog* Full path name of the directory containing the log files.
Root* Full path name of the ACI root directory (installation directory).
* Parameters that must not be modified
If a value for the Root parameter is not found under this registry
! key, all mandatory parameters are set to their default values
during the start-up phase. This assumes that you are logged in
to Windows NT as the system administrator. If this is not the
case, the system (NT) will crash.
5–2 A50010-T3-B100-1-7671
• Key: mandatory → API

EnableAlm Status of the subagent Alarming:
Value 0 = Stopped, Value 1 = Running
EnablePolling Interface status:
Value 0 = SNMP Polling OFF,
Value 1 = SNMP Polling ON
EnableSlt Status of the subagent Subscriber Line Test:
EnableSubact Does not apply in this version.
EnableWdg Status of the subagent Watchdog:
• Key: mandatory → DECTlink Security

Default Export Directory for the file with DECT RDU subscriber data, used by
Directory the DECT Locator.
• Key: mandatory → Media Interface → Event Media Configuration

Sound Sound file directory for acoustic event signaling.
• Key: mandatory → Media Interface → Media Configuration

Default Sound file directory including the begin and end time within
which the signaling should take place.
• Key: mandatory → NE Management

This key is a placeholder for parameters, exclusively used for test purposes.
• Key: mandatory → Traffic Measurement

Automatic traffic Name of the directory containing the files in which data resulting
data from automatic traffic feedback is stored. This is a subdirectory
of the Traffic directory.
Manual traffic data Name of the directory containing the files in which data resulting
from manual traffic feedback is stored. This is a subdirectory of
the Traffic directory.
Traffic data share Name of the main traffic directory, which contains the subdirec-
tories Automatic and Manual and is located directly under the
ACI root directory.
PDPT executable File name of the offline tool PDPT, which is used to evaluate the
traffic data. The default file name is PDPT.EXE.
A50010-T3-B100-1-7671 5–3
• Key: mandatory → User Port Test

EnableManTest List of the supported port types.
5.2 AccessIntegrator server

An AccessIntegrator server requires the following registry entries at start-up:
• Key: mandatory Server

OperLog* Full path name of the directory containing the log files.
Root* Full path name of the ACI root directory (installation directory).
If a value for the Root parameter is not found under this registry
! key, all mandatory parameters are set to their default values
during the start-up phase. This assumes that you are logged in
to Windows NT as the system administrator. If this is not the
case, the system (NT) will crash.
• Key: mandatory Server → Common MIB Objects

MaxMLOSPorts Number of DCNs connected. This parameter is required
when starting the server in the first exploration phase.
The default value is 9.
VerifyOffset Number of NEs (package size) verified simultaneously
during the exploration phases 2 and 3. The value corre-
sponds with the value of ExpirationTimePhase.
ExpirationTimeShort Time for NE responses in the first exploration phase during
the server start-up (poll list).
Recommended range: 1 - 5 minutes.
The default value is 1 minute.
ExpirationTimeNormal Time for NE responses in exploration phases 2 and 3
during server start-up and for normal operation.
The default value is 25 minutes.
ExpirationTimeLong Waiting time for lengthy jobs, e.g. jobs involving queries
that trigger a large number of responses (e.g. SW down-
load). The default value is 60 minutes.
5–4 A50010-T3-B100-1-7671

ExpirationTimePhase Delay time for the checking of an NE package (size see
VerifyOffset) in the exploration phase 2/3 during the
server initiation. As soon as this timer runs out, the check
of the next package begins.
The default value is 40 minutes.
GVChange Changing the equipment variant (NE exchange).
Value 1, the ACI attempts to query all relevant data auto-
matically.
Value 0, the NE status becomes inconsistent and the
data must be manually corrected.
VerifyConfigChange Checking NEs after module exchange.
Value 1, ACI only checks the module that has been ex-
changed.
Value 0, ACI checks all modules of the NE.
• Key: mandatory Server → Common UI Components
NE list entries In the ACI start-up dialog, this is the maximum number of
NEs for each NE status counter.
• Key: mandatory Server → Communication

Qd2* This parameter is set to 1 if your ACI version supports NEs
that can communicate via QD2. Otherwise, it is set to 0.
If this value is missing, no startup dialog will be displayed.
Snmp* This parameter is set to 1 if your ACI version supports NEs
that can communicate via SNMP. Otherwise, it is set to 0.
• Key: mandatory → Traffic Measurement

Automatic traffic Name of the directory containing the files in which data resulting
data from automatic traffic feedback is stored. This is a subdirectory
of the Traffic directory.
Manual traffic data Name of the directory containing the files in which data resulting
from manual traffic feedback is stored. This is a subdirectory of
the Traffic directory.
Traffic data share Name of the main traffic directory, which contains the subdirec-
tories Automatic and Manual and is located directly under the
ACI root directory.
PDPT executable File name of the offline tool PDPT, which is used to evaluate the
traffic data. The default file name is PDPT.EXE.
A50010-T3-B100-1-7671 5–5
5.3 AccessIntegrator DCN server

The registry entries for a DCN server contain settings for
– DCN server
– RS232 ports
– RS485 ports.
During the start-up phase, the DCN server reads the corresponding entries in the
registry. If it does not find a specific entry, it creates the entry and sets the default values.
The entries created depend on the configuration of the boards used and on the commu-
nication mode. If the DCN server does not find any entries, the following configuration
is assumed:
RS232 Board with two ports. COM 1 is active and is used as the default port.
RS485 Board with eight ports.
DCN server parameters

The following parameter values control the DCN server process.
• Key: mandatory DCN Server → QD

ConfigurationRefresh Time interval in seconds at which the DCN server
refreshes the data from the registry. The default value is
30.
DebugLevel Activates or deactivates the internal debugging of the
DCN server. This parameter is not used to control the
Test and Trace subsystem.
The value 0 deactivates debugging.
The value 1 activates debugging.
MaxLogFiles Restricts the number of telegram log files that can be
created by a DCN server. This must be a value greater
than 1. The default value is 10.
MaxMessagesInLogfile Restricts the number of telegrams that can be recorded
in a log file. If further telegrams are to be logged, a new
file is created. The default value is 1000.
NumberOfBoards Number of boards with ports used by the DCN server.
Reassembler Timeout Time period allowed for the collection of telegrams to
form a complete message. The default value is 10.
5–6 A50010-T3-B100-1-7671
Board parameters
The boards contain the ports which are used for communication.
• Key: mandatory DCN Server → QD → Board<n>

where <n> is the board number.
Active Determines whether or not the board is active.
The value T (TRUE) means the board is active.
The value F (FALSE) means the board is not active.
The default value is T.
BoardType Communication mode for the ports on the board.
Possible values:
RS232 for RS232 communication or
RS485 for a RS485 board.
NumberOfPorts Number of ports on the board.
DeviceAddress This parameter currently applies only to RS485 boards.
It is used for internal hardware addressing.
RS232 port parameters

The port numbers correspond to the COM numbers under Windows NT: port 1 is COM1,
port 2 is COM2.
• Key: mandatory DCN Server → QD → Board 1 → Port<p>

where <p> is the port number.
Active Determines whether or not the port is active on the board.
Only one RS232 port can be active at any one time.
The value T (TRUE) means the port is active.
The value F (FALSE) means the port is not active.
BaudRate Baud rate of the port. The default value is 9600. Other
permitted values:
110, 300, 600, 1200, 2400, 4800, 14400, 9600,
19200.
The maximum value depends on the number of
connected NEs.
DebugLevel This parameter is currently not used. It controls the
internal debugging of the port. The value 0, deactivates
debugging; the value 1 activates debugging.
DebugSISA Controls the SISA trace.
The value F (FALSE) means the trace is deactivated.
The value T (TRUE) means the trace is active.
The default value is F.
A50010-T3-B100-1-7671 5–7
Flowcontrol Defines flow control for the port. Possible values:

NO No flow control (default value)
DTRDSR DTR/DSR
RTSCTS RTS/CTS
XONXOFF XON/XOff
Parity Parity of the port. Possible values:
EVEN Even parity (default value)
ODD Odd parity
NO No parity
Stopbits Number of stop bits. Possible values: 1 or 2.
RS485 port parameters
• Key: mandatory DCN Server → QD → Board 2 → Port<p>

where <p> is the port number.
Active Determines whether or not the port is active on the board.
The value T (TRUE) means the port is active.
The value F (FALSE) means the port is not active.
BitRate Bit rate of the port. The default value is 64000.
Other permitted values: 1200, 2400, 4800, 9600,
19200.
DebugLevel This parameter is currently not used. It controls the
internal debugging of the port. The value 0 deactivates
debugging; the value 1 activates debugging.
ModeOSI OSI mode. Possible values:
BUS Bus mode (Default value)
V11A V.11 asynchronous
OperatingMode Operating mode. Possible values:
BUS Bus mode (default value)
PP Point-to-point mode
Pollcycle Poll cycle consisting of two flags in a character string.
Uppercase letters indicate that the flag is switched on,
while lowercase letters indicate that it is switched off.
Possible flags:
O Optimization on
o Optimization off
P Priority mode on
p Priority mode off
The default value is Op, i.e. optimization is switched on
and priority mode is switched off.
5–8 A50010-T3-B100-1-7671
6 Abbreviations
ACI AccessIntegrator
APS Application Program System
DCN Data Communications Network
LCT Local Craft Terminal
MEU Measurement Unit
NE Network Element
O.N.M.S Optimized Network Management System
OS Operations System
Pid Process identification
POC Public Operator Code
RAS Remote Access Service
RDU Radio Distribution Unit
TAC Technical Assistant Center
UI User Interface
A50010-T3-B100-1-7671 AP – 1
AP – 2 A50010-T3-B100-1-7671

Siemens FMX 4

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Siemens FMX 4

Hochgeladen von

Copyright:

Verfügbare Formate

back

Copyright (C) Siemens AG 1998

Issued by the Information and Communication Networks Group

Technical modifications possible.

2 ACI user administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Backup and restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 ACI configuration and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

5 Initialization parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

1.1 Manual concept and target groups

1.2 Manual layout

1.3 Notational conventions

Notational convention Meaning

Courier Input and output

Tab. 1.1 Notational conventions

2 ACI user administration

2.1 Organization of function permissions in ACI

NT workstation NT domain controller

Fig. 2.1 Checking a user’s function permissions

Several ACI servers in a single NT domain

NT domain controller ACI server 1 ACI server n

Network Subscriber Line Test Intelligence Features

Maintenance Operating&Maintenance Operating&Maintenance

Customer Organization Subscriber Management Subscriber Line Test

Tab. 2.1 Assigning permission classes

Global user groups without a permission class

2.2 Permission classes

Permission class Recommended functions

“Subscriber Management” This class grants permission to generate, modify, or delete

Tab. 2.2 Permission classes

2.2.1 Creating ACI-specific global user groups

2.2.2 Editing the permission class table

Fig. 2.2 “User Roles” dialog

2.2.2.1 Defining a new assignment

Fig. 2.3 “Define new User Role” dialog

2.2.2.2 Changing or deleting assignments

2.3 Function permissions

Operation & Maintenance

File Network Editor X X

View NEs in Maintenance Mode X X X X X

Configuration NE Configuration General NE Parameters X X X X X

Cross Connect 64 kbit X X X X

Leased Line Management X X X X

Software Management APS Management X X X

Mobility Administration RDU Global Data X X X

Tab. 2.3 Default user rights according to ACI permission classes

Operation & Maintenance

Configuration Network Configuration Path Management Modify Path X X X X

Service Management Create Service X X X X

Air Connection Management Repeaters X X X X

Service/Path Management Delete Service/ X X X X X

Fault Alarm List X X X X X

Alarm Log Display X X X X X

Event Log Display X X X X X

Disconnected NEs Media X X X X X

Measurement Traffic Traffic Measurement X X

Performance Log Display X X X X X

Subscriber Line Test Log Display X X X

Subscriber Line Test Data X X X X

Configure Automatic Test X X X X

Configure Manual Test X X X X X

Configure Battery Test X X X X X

Security User Roles X X

Operation & Maintenance

Utilities Inventory Data Retrieval Equipment Data X X X X X