M0125ana Aimos V2 13

A.I.M.O.S. V2.
13
Andrew Integrated Management

and Operating System
User's Manual
M0125ANA
Users Manual for A.I.M.O.S. V2.13
Copyright 2013 CommScope, Inc.

All rights reserved.
All information contained in this manual has been revised thoroughly. Yet
CommScope accepts no liability for any omissions or faults.
CommScope reserves the right to change all hardware and software characteristics
without notice.
Names of products mentioned herein are used for identification purposes only and
may be trademarks and / or registered trademarks of their respective companies.
No parts of this publication may be reproduced, stored in a retrieval system,
transmitted in any form or by any means, electronical, mechanical photocopying,
recording or otherwise, without prior written permission of the publisher.
Andrew Wireless Systems GmbH, 12-December-2013
Page 2
M0125ANA.DOC
TABLE OF CONTENTS
1
GENERAL
1.1
1.2
1.3
ABOUT COMMSCOPE
INTERNATIONAL CONTACT ADDRESSES FOR CUSTOMER SUPPORT
CONTENT CHANGES COMPARED TO PREVIOUS MANUAL VERSIONS
WELCOME TO A.I.M.O.S.
9
10
13
15
2.1
WHAT IS A.I.M.O.S.
2.2
COMMENTS ON THE MANUAL
2.2.1
Meaning of Symbols
2.2.2
Installation Instructions for A.I.M.O.S.
2.3
SYSTEM REQUIREMENTS FOR A.I.M.O.S.
2.4
GENERAL GUIDELINES
2.4.1
Installation Guidelines
2.4.2
IE Settings
2.4.2.1
IE Cache Settings
2.4.2.2
IE Security Configuration
2.4.2.3
IE Compatibility Settings
2.4.3
External Backup
2.5
A.I.M.O.S. CONTAINS
2.5.1
A.I.M.O.S. Programs (Accessible via Start Menu)
2.5.2
Services Used by A.I.M.O.S.
2.5.3
Optional A.I.M.O.S. Components
2.5.4
Test Tools (for Andrew technicians only)
2.5.5
Related Manuals
2.6
A.I.M.O.S. - CLIENT/SERVER
2.7
OMC3/ A.I.M.O.S. - SERVER INSTALLATION
2.8
CITRIX INSTALLATION
15
15
15
15
16
16
16
17
17
17
18
18
19
19
19
20
20
20
21
22
22
3
4
23
25
FOR A QUICK START

INSTALLATION PROCEDURES
4.1
4.1.1
4.1.2
4.2
4.3
4.3.1
4.3.2
4.4
4.5
4.6
PREPARATIONS
Preparation of OMC 3.54 for the Combined Installation with A.I.M.O.S.
Map (Optional Tool)
A.I.M.O.S. SETUP
A.I.M.O.S. UPDATE
A.I.M.O.S. Server Update
A.I.M.O.S. Client Update
MIGRATION FROM WINDOWS 2003 32 BIT TO WINDOWS 2008 64 BIT
HOW TO GET A.I.M.O.S. LICENSED
LOGIN SETTINGS
A.I.M.O.S. CONFIGURATION
5.1
SERVER CONFIGURATION / CONFIGURATION TOOL
5.1.1
Licenses
5.1.2
General - IP Parameters
5.1.3
Security
5.1.3.1
Password Settings
5.1.3.2
Account Settings
5.1.3.3
LDAP Settings
5.1.3.4
Visualization Login with LDAP
25
25
25
26
30
30
30
32
33
35
39
39
40
41
43
44
45
46
48
Page 3
Users Manual A.I.M.O.S. V2.13

5.1.4
SNMP Northbound Interface Settings
5.1.4.1
Server Port of the A.I.M.O.S. SNMP Agent
5.1.4.2
Default Port for Outgoing SNMP Traps
5.1.4.3
Agent Shutdown Delay
5.1.4.4
Length of Generated Community Names
5.1.4.5
Private SNMP Community Name
5.1.4.6
IP Address of Alternate SNMP Agent
5.1.4.7
Server Port of Alternate SNMP Agent
5.1.4.8
MIB Supported by the Agent
5.1.4.9
SNMPv3-related fields
5.1.5
OMC 3
5.1.6
SMTP Mail Server
5.1.6.1
Configuration of Email Forwarding
5.1.6.2
SMTP Server (Host Name or IP Address)
5.1.6.3
Server Port of the SMTP Server
5.1.6.4
From Email Address
5.1.6.5
HELO Name
5.1.6.6
SASL Login Username
5.1.6.7
SASL Login Password
5.1.7
SMPP
5.1.8
Housekeeping
5.2
PREFERENCES EDITOR - CUSTOMIZING A.I.M.O.S.
5.3
CONNECTIVITY MANAGER - MODEM MANAGEMENT
5.3.1
Discover Modems
5.3.2
Modem Groups
5.3.3
Profiles
5.3.3.1
RAS-in Profiles
5.3.3.2
Network Element Circuit Switched Profiles
5.3.3.3
Network Element Packet Switched Profiles
5.3.3.4
SMS Service Center Profiles
5.3.3.5
NE WEB Login Profiles
5.4
ACCOUNT MANAGER - USER MANAGEMENT
5.4.1
Organizations
5.4.2
Account Manager Rights
5.4.3
Account Manager Roles
5.4.3.1
The Administrator Role
5.4.3.2
The Standard User Role
5.4.3.3
The Read Only User Role
5.4.4
Account Manager Users
5.4.5
NE Owner
5.4.6
Import / Export
5.4.7
Excel Export
5.5
NORTHBOUND MANAGER (OPTION) - TRAP FORWARDING TO NMS
5.5.1
SNMP Manager
5.5.2
Workshift Assignment
5.5.3
NE Owner
5.6
ALARM POLLING
5.7
INTEGRATION OF OMC 3.54
5.8
DATABASE EXPORT / ODBC
5.9
AUTOMATIC BACKUP
5.10
AUDITORY ALARM NOTIFICATIONS
Page 4
48
49
49
49
49
49
49
50
50
50
51
51
51
52
52
52
52
53
53
53
55
57
61
63
63
64
64
65
65
65
66
67
69
71
76
76
76
76
77
79
79
80
81
81
85
86
87
88
88
89
89
M0125ANA.DOC
A.I.M.O.S. - OPERATIONS
6.1
NE MANAGEMENT - OVERVIEW
6.2
MENUS
6.2.1
File
6.2.2
Tools
6.2.3
Tree
6.2.4
View
6.2.5
Extras
6.2.6
Window
6.2.7
Menu ?
6.3
NE TREE
6.4
VISUALIZATION FILTERS AND SORT OPTIONS
6.4.1
Table Filters
6.4.1.1
Column Selection and Customizing
6.4.1.2
Sort Options and Calculations
6.4.1.3
Managing Table Filters and Sort Options
6.4.2
Using the Filter Builder
6.4.3
Network Element Filter
6.4.3.1
Customizing a Filter with the NE Filter Builder
6.4.3.2
Filter Settings
6.4.3.3
Importing a Filter from the Scheduler
6.4.3.4
Filter Type Conversion
6.5
ADD NEW NETWORK ELEMENT (NE)
6.5.1
Node X
6.5.1.1
Basic Parameter Setting
6.5.1.2
Dial Parameter Setting
6.5.2
AMR
6.5.3
MCPA
6.5.4
ION-B Controller Type TSUN1, TSUN2, TSUN3 and TSUN6
6.5.5
ION-U System / ION-E System
6.5.6
ION-M Optical System Controller Type RMC, MMC Plus, TSUN4
6.5.7
SMS Network Element
6.5.7.1
MRx18
6.5.7.2
DICE
6.5.7.3
MIR-T
6.5.7.4
ION-M MiniMaster
6.5.7.5
Generic
6.5.7.6
Generic 1
6.5.7.7
Generic 2
6.5.7.8
MR2003P
6.5.7.9
MR2133
6.6
ADD NEW FOLDER
6.7
NETWORK ELEMENT OPERATIONS
6.8
FUNCTIONS BAR
6.8.1
Supervision
6.8.1.1
Alarm History
6.8.1.2
Alarm Help
6.8.2
Configuration
6.8.3
Maintenance
6.8.4
Notes
6.8.5
Log
91
91
92
93
95
95
97
98
99
99
100
103
103
103
104
104
105
105
106
107
107
108
109
109
109
110
113
114
115
117
118
119
120
120
121
121
121
122
122
122
122
123
123
125
126
127
127
128
136
138
138
Page 5

6.9
CONFIGURATION - CONNECTIVITY
6.9.1
Circuit Switched Connection
6.9.2
Packet Switched Always On Connection
6.9.2.1
Overview
6.9.2.2
Change Connectivity Mode to Packet Switched Always On
6.9.3
Packet Switched On Demand
6.9.3.1
Overview
6.9.3.2
Change Connectivity Mode to Packet Switched On Demand
6.9.4
Local Area Network
6.9.5
Common Features and Settings for all Connection Types
6.9.5.1
Buttons
6.9.5.2
WEB-Login Configuration
6.9.5.3
Alarm Type
6.9.5.4
Zone Change Traps
6.9.5.5
WEB Server Configuration
6.9.5.6
Additional Information
6.9.6
VPN Connectivity Parameters
6.10
TOOL SCHEDULER (OPTION)
6.10.1
Customizing a Schedule
6.10.1.1 Step 1: Tab Schedule - Customize the Schedule
6.10.1.2 Step 2: Tab Network Elements - Customize the Network Elements
6.10.1.3 Step 3: Tab Actions - Customize the Actions
6.10.2
XML Import
6.10.3
Scheduler Actions
6.10.3.1 Event Triggered Actions
6.10.3.2 File Upload
6.10.3.3 Software Update
6.10.3.4 Read Performance Data
6.10.3.5 Create Performance Data Chart
6.10.3.6 Configure Node A User
6.10.3.7 Configure ION-M User
6.10.3.8 Create Export
6.11
TOOL NETWORK ELEMENT LIST
6.12
TOOL JOB MONITOR
6.13
TOOL LOG MANAGER
6.14
TOOL MAP (OPTION)
6.14.1
Buttons
6.14.2
Assign a Bitmap to a Folder
6.14.3
Assign a Bitmap to a Subfolder of a Bitmap Folder
6.14.4
Remove a Bitmap from a Folder
6.14.5
Show a Folder Bitmap as Map
6.14.6
Show a Sub-Bitmap as Map
6.14.7
Including NEs to the Vector Map
6.14.7.1 RF Units
6.14.7.2 Optical Systems
6.14.8
Selecting an NE
6.14.9
Moving an NE on the Map
6.14.10
Removing NEs from the Map
6.14.10.1
RF Units
6.14.10.2
Optical Systems
6.14.11
NE Subunit Management
6.14.11.1
Excluding NE Subunits from an Optical System
6.14.11.2
Including NE Subunits to an Optical System
6.14.12
View
Page 6
138
139
140
140
141
142
142
143
144
145
145
145
145
145
146
146
146
148
149
149
151
152
153
157
159
162
166
171
172
173
174
175
179
180
180
182
182
183
183
183
183
184
184
184
184
185
185
185
185
185
185
185
186
186
M0125ANA.DOC
6.15
TOOL WATCHDOG
6.16
TOOL PERFORMANCE MANAGER (OPTION)
6.16.1
Menus
6.16.1.1 Performance
6.16.1.2 Chart
6.16.2
Settings
6.17
TOOL PROFILES
6.17.1
Connectivity Manager Profiles
6.17.2
NE Owner Profile of Account Manager
6.17.3
Configuration Groups of Preferences Editor
6.17.4
Alarm Profiles
6.17.5
Export Profiles
6.17.6
External Tool Profiles
6.18
OMC3 ADAPTER
6.19
SNMP GUI
186
186
187
188
188
188
196
197
197
198
199
201
202
203
203
205
A.I.M.O.S. DATABASE ADMINISTRATION / MAINTENANCE TOOL
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.2
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
7.3
7.3.1
7.3.2
7.3.3
7.4
7.4.1
7.4.2
7.5
8
8.1
8.2
8.3
8.4
BACKUP
Backup to File
Include A.I.M.O.S.
Include OMC3
Backup Finished
RESTORE
Restore from File
Restore A.I.M.O.S.
Restore OMC3
The List of Backups
Restore Configuration Tool Settings
Backup Version
Restore Finished
VALIDATE
Include A.I.M.O.S.
Include OMC3
Validation Finished
UPDATE
Update From File
Update Finished
WATCHDOG
205
205
206
206
206
206
207
207
207
207
207
208
208
208
209
209
209
209
210
211
211
A.I.M.O.S. TEST TOOLS
213
AGENT SIM
COMAS TEST
MIB
TRAP MONITOR
213
215
216
216
LOGGING
9.1
LOG FILE DOCUMENTATION
9.1.1
Log File Overview
9.1.2
Log File Contents
9.1.2.1
Installation and Uninstalling
9.1.2.2
Database Server Operations
9.1.2.3
Connection to OMC3
9.1.2.4
Database Maintenance Operations
9.1.2.5
Automatic Database Backup
217
217
217
217
217
218
218
219
219
Page 7

9.1.2.6
9.1.2.7
9.1.2.8
9.1.2.9
9.1.2.10
9.1.2.11
Automatic Database Restore

Services Supervision
Connection to Network Elements, Database and Visualization
Automatic ODBC Export
Server Update
SNMP Operations
220
220
221
221
222
222
10 TROUBLESHOOTING
223
10.1
10.2
10.3
223
224
227
RAS CONNECTIONS
TECHNICAL SUPPORT
LICENSE INSTALLATION
11 GLOSSARY
12 APPENDIX A MODEM INSTALLATION AND CONFIGURATION
13 APPENDIX B DIAL-IN CONNECTIVITY
229
231
235
13.1
DIAL-IN SERVER CONFIGURATION
235
13.1.1
Security Policy
235
13.1.1.1 Local Security Policy
235
13.1.1.2 Domain Security Policy
236
13.1.2
User Account Data
238
13.1.2.1 Adding a Local Dial-in User
238
13.1.2.2 Adding a Domain Dial-in User
240
13.2
REMOTE ACCESS SERVER CONFIGURATION FOR WIN2003 SERVER
STANDARD EDITION
242
13.2.1
RRAS Server Configuration
242
13.2.2
RRAS Server Configuration Wizard
243
13.2.3
RRAS Server Properties
245
13.2.4
RRAS Policy
248
13.3
REMOTE ACCESS SERVER CONFIGURATION FOR WIN2008
252
13.3.1
252
13.3.2
254
13.3.3
259
13.3.4
Network Policies
262
13.4
TESTING THE REMOTE ACCESS SERVER CONFIGURATION
266
13.4.1
Procedure for Win2003
266
13.4.2
270
14 APPENDIX C HTTPS CERTIFICATE HANDLING
273
14.1
14.2
273
274
CERTIFICATE SELECTION
CERTIFICATE INSTALLATION
15 INDEX
Page 8
277
M0125ANA.DOC
1 General
1 GENERAL
1.1 ABOUT COMMSCOPE
CommScope is the foremost supplier of one-stop, end-to-end radio frequency (RF)
solutions. Part of the CommScope portfolio are complete solutions for wireless
infrastructure from top-of-the-tower base station antennas to cable systems and
cabinets, RF site solutions, signal distribution, and network optimization.
CommScope has global engineering and manufacturing facilities. In addition, it
maintains field engineering offices throughout the world.
Andrew Wireless Systems GmbH based in Buchdorf/ Germany, which is part of
CommScope, is a leading manufacturer of coverage equipment for mobile radio
networks, specializing in high performance, RF and optical repeaters. Our optical
distributed networks and RF repeater systems provide coverage and capacity
solution for wireless networks in both indoor installations and outdoor environments,
e.g. tunnels, subways, in-trains, airport buildings, stadiums, skyscrapers, shopping
malls, hotels and conference rooms.
Andrew Wireless Systems GmbH operates a quality management system in
compliance with the requirements of ISO 9001 and TL 9000. All equipment is
manufactured using highly reliable material. To maintain highest quality of the
products, comprehensive quality monitoring is conducted at all fabrication stages.
Finished products leave the factory only after a thorough final acceptance test,
accompanied by a test certificate guaranteeing optimal operation.
The declaration of conformity for our products is available upon request from the
local sales offices or directly from CommScope.
To make the most of this unit, we recommend you carefully read the instructions in
this manual and commission the unit only according to these instructions.
For technical assistance and support, contact the local office or CommScope directly
at one of the following addresses listed in the next chapter.
Page 9
1.2
INTERNATIONAL CONTACT ADDRESSES FOR CUSTOMER SUPPORT

Americas:
Canada
United States
CommScope Canada
Andrew LLC, A CommScope Company
Mail
505 Consumers Road, Suite 803

Toronto M2J 4V8
Canada
Mail
620 North Greenfield Parkway

Garner, NC 27529
U.S.A.
Phone
+1-905-878-3457 (Office)
+1-416-721-5058 (Cell)
Phone
+1-888-297-6433
Fax
+1-905-878-3297
Fax
+1-919-329-8950
E-mail
wisupport@commscope.com
E-mail wisupport@commscope.com
Caribbean & South American Region
(CALA)
Caribbean (CALA) & Central American

Region
CommScope Cabos do Brasil Ltda.
CommScope Mexico S.A. de C.V.
CALA Tech Support for Distributed

Coverage & Capacity Solutions
(DCCS) products:
Mail
Rua Guaporanga, 49
Praa Seca Rio de Janeiro RJ
ZIP: 21320-180
Brazil
CALA Tech Support for Distributed

Coverage & Capacity Solutions
(DCCS) products:
Mail
Av. Insurgentes Sur 688, Piso 6

Col. Del Valle, CP: 03100
Mexico City
Mexico
Phone
+1-815-546-7154 (Cell)
+55-15-9104-7722 (Office)
Phone
+52-1-55-5419-5260 (Cell)
+52-55-1346-1900 (Office)
Fax
+ 55-15-2102-4001
Fax
+52-55-1346-1901
E-mail
E-mail
APAC Countries:
China, India and Rest of Asia
Andrew International Corporation
Australia & New Zealand

Andrew Corporation (Australia) Pty Ltd.
Mail
Room 915, 9/F

Chevalier Commercial Centre
8 Wang Hoi Rd
Kowloon Bay
Hong Kong
Mail
Unit 1
153 Barry Road
Campbellfield
VIC 3061
Australia
Phone
+852-3106-6100
Phone
+613-9300-7969
Fax
+852-2751-7800
Fax
+613-9357-9110
E-mail
wisupport.China@commscope.com
E-mail
wisupport.Australia@commscope.com
Page 10
M0125ANA.DOC
1 General
Europe:
United Kingdom
Scandinavia
Andrew Wireless Systems UK Ltd
Andrew Norway (AMNW)
Mail
Unit 15, Ilex Building

Mulberry Business Park
Fishponds Road
Wokingham Berkshire
RG41 2GY
England
Mail
P.O. Box 3066

Osloveien 10
Hoenefoss 3501
Norway
Phone
+44-1189-366-792
Phone
+ 47 32-12-3530
Fax
+44-1189-366-773
Fax
+ 47 32-12-3531
E-mail
wisupport.uk@commscope.com
E-mail
Germany
France
Andrew Wireless Systems GmbH
CommScope France
Immeuble Le Lavoisier
4, Place des Vosges
92052 Courbevoie
France
Mail
Industriering 10
86675 Buchdorf
Germany
Phone
+49-9099-69-0
Phone
+33-1 82 97 04 00
Fax
+49-9099-69-930
Fax
+33-1 47 89 45 25
E-mail
E-mail
Mail
Austria
Switzerland
Andrew Wireless Systems (Austria) GmbH
CommScope Wireless Systems AG
Mail
Weglgasse 10
2320 Wien-Schwechat
Austria
Mail
Tiergartenweg 1
CH-4710 Balsthal
Switzerland
Phone
+43-1706-39-99-10
Phone
+41-62-386-1260
Fax
+43-1706-39-99-9
Fax
+41-62-386-1261
E-mail
wisupport.austria@commscope.com
E-mail
wisupport.ch@commscope.com
Italy
Iberia Region - Spain & Portugal
CommScope Italy S.r.l., Faenza, Italy
Andrew Espaa S.A.

A CommScope Company
Mail
Via Mengolina, 20
48018 Faenza (RA)
Italy
Mail
Avda. de Europa, 4 - 2 pta.

Parque Empresarial de la Moraleja
Alcobendas, Madrid 28108
Spain
Phone
+39-0546-697111
Phone
+34-91-745-20 40
Fax
+39-0546-682768
Fax
+34-91-661-87 02
E-mail
wisupport.italia@commscope.com
E-mail
wisupport.iberia@commscope.com
Page 11
Czech Republic
CommScope Solutions Czech Republic
C-Com, spol. s r.o
Mail
U Moru 888
53006 Pardubice
Czech Republic
Phone
+49 871 9659171 (Office)

+49 171 4001166 (Mobile)
Fax
+49 871 9659172
E-mail
Africa & Middle East:

Middle East & North Africa
CommScope Solutions International Inc.
(Branch)
South Africa
Andrew Wireless Solutions Africa
(PTY) LTD
11 Commerce Crescent West
Eastgate, Sandton
PO Box 786117
Sandton 2146
South Africa
Mail
PO Box 48 78 22
Unit 3206, Floor 32,
Jumeirah Business Center 5,
Jumeirah Lakes Towers,
Dubai
United Arab Emirates
Mail
Phone
+971 4 390 09 80
Phone
+ 27 11-719-6000
Fax
+971 4 390 86 23
Fax
+ 27 11-444-5393
E-mail
E-mail
table 1-1 List of international contact addresses
Page 12
M0125ANA.DOC
1 General
1.3 CONTENT CHANGES COMPARED TO PREVIOUS MANUAL VERSIONS

Compared to manual version M0125AMA for A.I.M.O.S. Version 2.12, the manual
contains the following new / modified information:
Additions / changes corresponding to a new SW feature or a feature change:
New feature / change
Chapter
Content
Update of IE Settings
2.4.2
Chapter extended and

subchapters added
Change in Client update
4.3.2
Description updated
5.1.3
Screenshot updated
5.1.3.2
Header renamed,
description added
New Password Security Level option
5.1.3.1
Description updated
Message changed
5.5.2
Screen shot updated.
Field to prevent gray text added
5.2
Description updated
Maximum User Account Inactivity
Expiry Date and Most Recent Use settings 5.4

in Account Manager - User Management
5.4.4
Description added
Use filtered NE List for NE Tree
6.4
Reference to 6.11 added
ION-E system added
6.5, 6.5.5
Descriptions added
SNMPv3 southbound support of Node A
6.5.1, 6.9
Descriptions updated
New action Configure ION-M User
6.10.3,
6.10.3.7
Description updated and

new chapter added
Use filtered NE List for NE Tree
6.11
Description updated
Description added
Page 13

Amendments to the manual for optimization purposes:
Chapter
Content
1.2
Addresses updated
2.2.1
Node X explanation added.
4.2
Information on Microsoft Package installation added
5.2
Default value added to Show Alert Box explanation.
6.2.1
Alarm import information of menu Update extended and

description of Export Node G Frequency to XML-Import File
added
6.10.2
XML-File Location field information added to a) & b), and

description for c) extended
6.10.3
Editorial change
6.10.3.8
Description extended by detailed example and reference to

chapter 6.10.2 added
13.4.2
Screen shot corrected
Page 14
M0125ANA.DOC
2 Welcome to A.I.M.O.S.
2 WELCOME TO A.I.M.O.S.
2.1 WHAT IS A.I.M.O.S.
Andrew Integrated Management and Operating System, called A.I.M.O.S. is a
comprehensive software that gives the ability to control and monitor network
elements (NE) in mobile networks.
A.I.M.O.S. is an OMC (Operation and Maintenance Center), based on the state-ofthe-art in operating complex network systems. The software bundle A.I.M.O.S.
contains an SNMP Northbound Manager (option), Map (option), Scheduler (option),
Performance Manager (option), as well as Visualization clients. All these
sophisticated power tools enable unlimited control and maintenance of network
elements in mobile networks.
2.2 COMMENTS ON THE MANUAL
The A.I.M.O.S. software is delivered with a detailed context-sensitive Online-help,
which is available at any window of the program (press F1) with the respective help
item. The Online-help is based on the A.I.M.O.S. Users Manual in electronic form.
2.2.1
Meaning of Symbols
Meaning of symbols used in the text:

Information: Additional information
Attention!: Emphasizes important information.
Warning!: Emphasizes very important information.
Textual Conventions:
If an application is accessed via menus, the menu-path to this application is
described in square brackets, e.g. [Start-Settings-Software-Install..].
If an application is started directly by a double-click, the path to the executable is
given in italics, e.g. D:\V1.9.0.109\Setup\setup.exe.
In the following the root directory (where the operating system is installed to) of
your PC is referred to as C:\ drive, the CDROM drive is referred to as D:\
drive. These declarations may vary depending on your computer system.
Node X represents all Node types, i.e. Node C, G, M, A, A+, and AM.
2.2.2
Installation Instructions for A.I.M.O.S.
The detailed description of the installation is given in chapters 3 to 5.

It is highly recommended to follow all installation steps described in
this installation instruction before starting to work with A.I.M.O.S.
Page 15
2.3 SYSTEM REQUIREMENTS FOR A.I.M.O.S.

Server
Minimum
OS
WIN 2003
Server R2
Standard
Edition, 64
bit
CPU
Intel Xeon
> 2 GHz
RAM
Network
8 GB
100 MBit
LAN
Recommendation for a Citrix

Server
Client
Recommended
WIN 2008
Server R2
Standard
Edition, 64
bit
2 x Intel
Xeon > 3
GHz
16 GB
1 GBit LAN
Disk
Space
100 GB
200 GB
Display
1280 x
1024
1280 x 1024
WEB
Browser
Internet
Explorer 8
Internet
Explorer 9
Minimum
Recommended
6 Users
12 Users
Windows
XP SP3
Pro, 32
bit
Windows 7
Pro, 64 bit
WIN 2008
Server R2
Standard
Edition, 64 bit
WIN 2008
Server R2
Standard
Edition, 64 bit
Intel
Core i5
Intel Core i7
2 x Intel Xeon
> 3 GHz
4 x Intel Xeon
> 3 GHz
8 GB
32 GB
48 GB
1 GBit LAN
1 GBit LAN
1 GBit LAN
20 GB
500 GB
1.000 GB
1920 x 1200
1280 x 1024
1280 x 1024
Internet
Explorer 9
Internet
Explorer 9
Internet
Explorer 9
4 GB
100 MBit
LAN
10 GB
1280 x
1024
Internet
Explorer
8
2.4 GENERAL GUIDELINES

2.4.1
Installation Guidelines
The Connectivity Manager of A.I.M.O.S. uses RAS connections of the
operating system (Windows RAS). Each modem to be used (SMS, RAS
Incoming connection, RAS Outgoing connection) has to be installed in the
operating system.
The WMI (Windows Management Instrumentation) service must be activated

and "operational":
Each modem to be used for Incoming connections has to be added to the RAS
Incoming Connections.
To use the Web Interface of A.I.M.O.S., set the browser (IE) settings to:
Never dial a connection in [Tools-Internet Options-Connections-DialUp and Virtual Private Network settings].
None of the three checkboxes in [Tools-Internet Options-ConnectionsDial-Up and Virtual Private Network settings-LAN Settings] must be
checked.
Page 16
M0125ANA.DOC
2.4.2
IE Settings
Observe that IE Settings are user-specific as a Windows default administrative

setting. The customer can decide to configure these settings individually for all
relevant users or to assign a universal setting via Group Policy or Registry.
If these settings are changed whilst the A.I.M.O.S. Visualization is running, a
restart of the Visualization is required in order for the changes to take effect.
2.4.2.1
IE Cache Settings
1. Select Internet Explorer Tools Internet Options General Browsing

History.
2. Click the Delete button.
3. In the Temporary Internet Files area, click the Delete Files button to clear
the cache. Close that window
4. Still under General Browsing History click the Settings button Check
for newer versions of stored pages has to be set to Every time I visit the
webpage.
5. Change setting under Days to keep pages in history to 0.
6. To exit, click the OK buttons at the bottom of the Settings and Internt Options
windows.
2.4.2.2
IE Security Configuration
Please note that the security level High set for the Internet Zone will not work. It is
necessary to set the six listed IE security options accessible via Open Tools
Internet Options Security Internet Zone Custom Level as follows:
Miscellaneous: Allow META REFRESH set to "Enable"
Miscellaneous: Submit non-encrypted form data set to "Enable"
Scripting: Active scripting set to "Enable"
Downloads: File download set to "Enable"
Downloads: Automatic prompting for file downloads set to "Enable"
For ION-M systems the following settings depend on the different MC SW

versions integrated in A.I.M.O.S.:
In case at least one ION-M system with MC SW version <V5.20 is integrated:
o Initialize and script ActiveX controls not marked as safe for scripting set
to "Enable" (Note: This setting is necessary even it is classified as
'unsecure' by IE. Otherwise the 'Maintenance->Download Logfiles' option
via ION-M web page will not work.)
OR
If only ION-M systems with MC SW version V5.20 or higher are integrated, the
following two secure settings replace the unsecure setting above:
o ActiveX controls and plug-ins: Run ActiveX controls and plug-ins => set to
"Enable", and
o ActiveX controls and plug-ins: Script ActiveX controls marked safe for
scripting => set to "Enable".
Page 17
2.4.2.3
IE Compatibility Settings
At least IE Version 8 is required as browser. However in IE 8 and from IE 10 onwards

the Browser Mode accessible via Tools menu F12 Developer Tools (see
exemplary figure of IE 10 below) has to be adjusted as follows:
in IE 8: from Internet Explorer 8 Compatibility View to "Internet Explorer 8"
from IE 10 onwards: "Internet Explorer 8" or "Internet Explorer 9 must be set"
2.4.3
External Backup
For an external backup of the A.I.M.O.S. server (e.g. with Acronis), the complete
server must be shut down.
Page 18
M0125ANA.DOC
2.5 A.I.M.O.S. CONTAINS

2.5.1
A.I.M.O.S. Programs (Accessible via Start Menu)
Designation
Short Description
See this manual, chapter
Server
Use to start the Configuration Tool for the
Configuration configuration of A.I.M.O.S. server settings.
5.1 Server Configuration /

Configuration Tool
Visualization Use to start A.I.M.O.S. Visualization (GUI).
all
Server
Use to start the Maintenance Tool for the
Maintenance A.I.M.O.S. SW & database maintenance.
7 A.I.M.O.S. Database
Administration /
Maintenance Tool
System
Information
Use to create a summary of information

that is relevant for troubleshooting
10.2 Technical Support
SNMP GUI
Use for the graphical supervision of the

SNMP Agent
5.1.4 SNMP Northbound

Interface Settings
6.19 SNMP GUI
2.5.2
Services Used by A.I.M.O.S.
Designation
Short Description
OMC3
Adapter
Used by A.I.M.O.S. for OMC3

synchronization.
2.7 OMC3/ A.I.M.O.S. - Server

Installation
5.1.5 OMC 3
5.7 Integration of OMC 3.54
6.18 OMC3 Adapter
SNMP Agent
Used by A.I.M.O.S. for the

synchronization of SNMP traps
5.1.4 SNMP Northbound

Interface Settings
6.19 SNMP GUI
Connector
5.1.2 General - IP Parameter (for

Used by A.I.M.O.S. for connection to
configuration)
NEs.
6.13 Tool Log Manager (for
supervision)
Tool
WatchDog
Used by A.I.M.O.S. to supervise and

manage all three A.I.M.O.S services
mentioned above and all started
OMC3 applications (if installed)
6.15 Tool Watchdog

7.5 WatchDog
Page 19
2.5.3
Optional A.I.M.O.S. Components
For all the components in the following an according license is required:

Designation
Short Description
Map
Use this tool to display NEs with their

location in maps.
4.1.2 Map (Optional Tool)

6.14 Tool Map (Option)
SNMP
Northbound
Manager
Use for setting the addresses of the

Network Management Systems (NMS)
which are to receive SNMP Alarm Traps.
5.5 Northbound Manager

(Option) - Trap Forwarding
to NMS
Scheduler
Use this tool for the automization of NE

Operations and for multi-configuration.
6.10 Tool Scheduler

(Option)
Performance
Manager
Use this tool for the evaluation of alarms

and performance data
6.16 Tool Performance

Manager (Option)
LDAP
Use for setting up a user management via

Windows active directory.
5.1.3.3 LDAP Settings
2.5.4
Test Tools (for Andrew technicians only)
Designation
Short Description
AgentSim
This program serves to simulate different

NE types.
8.1 Agent Sim
ComasTest
This program serves to simulate devices

connected via Comas protocol.
8.2 Comas Test
MIB
This program is a MIB viewer
8.3 MIB
TrapMonitor This program is used to receive test traps.
2.5.5
8.4 Trap Monitor
Related Manuals
Title of Manual
Manual
ODBC Interface manual
M0125B5x_ODBC_
AIMOS_Vx.pdf
Automatic Backup Feature manual
M0125B6x_AIMOS_
Auto_Backup.pdf
XML Interface Description
M0125B7x_XML_IF
_AIMOS_Vx.pdf
AIMOS SNMP Interface Description
<Title>.pdf
AIMOS SNMPv3 Configuration Guide
<Title>.pdf
AIMOS SNMP Interface Description

for Nokia NetAct
<Title>.pdf
Page 20
Location
A.I.M.O.S. CD
"~\Andrew\AIMOS\MIB
\<Title>.pdf
M0125ANA.DOC
A.I.M.O.S. Installation Variants
The following figures show three variants depending on the managed network
elements.
The Firebird data base server is installed under the NETWORK Service Account.
2.6 A.I.M.O.S. - CLIENT/SERVER
NMS
Visualization
Visualization
Client
POP3,
SMS receiver
LAN
SNMP
Agent
Server
Excel file and ODBC:
- Alarm Data
- Inventory Data
- General Repeater
Data
- Config Data
- Connectivity Data
DB
Export
ServerConfig
Tool
email,
SMS
Server Maintenance
Tool
Firebird
Connector
binary
LAN, GSM
or Packet
Data
binary
MMR/ION-M
System
SMS
SNMP
GSM/
SMS
Repeater with
SMS IF
GSM, UMTS
or
Packet
Data
LAN, GSM
or Packet
Data
Node
A/M/C/G
SNMP
BriteCell/ION-B
SNMP
A.I.M.O.S. Client/Server installation for 3G repeater systems only. A.I.M.O.S. native

clients can access the A.I.M.O.S. server remotely.
Page 21
2.7 OMC3/ A.I.M.O.S. - SERVER INSTALLATION

Front
FrontEnd
End
SNMP
Agent
Visualization
Visualization
Server
email,
SMS
Export
Import
OMC3
Adapter
DB
Foxpro
DB
Firebird
Connector
Connector
ASCII
GSM
binary
LAN, GSM
or Packet
Data
ASCII
MR & MOR
Systems
A.I.M.O.S.
server
installation
for
all
generation
repeater
systems. GUI runs on
the server only. OMC3
module (for 1st and 2nd
generation systems) is
shown at the left part.
SMS
SNMP
GSM/
SMS
binary
Repeater with
SMS IF
MMR/ION-M
System
Node
GSM, UMTS
or
Packet A/M/C/G
Data
LAN, GSM
SNMP
or Packet
Data
BriteCell/ION-B
SNMP
2.8 CITRIX INSTALLATION
CITRIX Client
Front
FrontEnd
End
Visualization
Visualization
LAN
Front
FrontEnd
End
Visualization
Visualization
CITRIX Server
Export
Import
DB
Foxpro
OMC3
Adapter
Connector
ASCII
MR & MOR
Systems
Page 22
email,
SMS
DB
Firebird
Connector
ASCII
GSM
SNMP
Agent
A.I.M.O.S. installation
with Citrix for all
generation
repeater
systems. GUI runs
remotely
as
Citrix
client.
binary
LAN, GSM
or Packet
Data
binary
MMR/ION-M
System
SMS
SNMP
GSM/
SMS
Repeater with
SMS IF
Node
GSM, UMTS
or
Packet A/M/C/G
Data
LAN, GSM
SNMP
or
Packet
Data
BriteCell/ION-B
SNMP
M0125ANA.DOC
3 For a Quick Start
3 FOR A QUICK START

This chapter gives a brief overview of the installation of A.I.M.O.S. Detailed
information is given in the respective chapter. Please keep in mind that A.I.M.O.S.
also provides an online-help covering most features and tools.
What to do
Details
Software
Installation
To prepare A.I.M.O.S for an OMC 3.54* integration, please read

chapter 4.1.1 carefully, before starting the installation procedure.
Insert the A.I.M.O.S. CD, start setup.exe for the installation or
update.exe for an update and follow the installation instructions.
Please read and observe the installation instructions in chapter 4,
as well.
Note: If an OMC 3.54* is to be integrated, the OMC3 Adapter has
to be installed, and for using SNMP Forwarding, the SNMP Agent
has to be installed (see chapter 4.2 A.I.M.O.S. Setup) .
Activate License
Key
See chapters 5.1.1 Licenses and 4.5 How to get A.I.M.O.S.

licensed.
Server
Configuration
The A.I.M.O.S. server has to be customized with the

Configuration Tool. For details see chapter 5.1 Server
Configuration / Configuration Tool.
User Management
Account Manager
Users for A.I.M.O.S. have to be created and access rights have

to be granted. For details see chapter 5.4 Account Manager User Management
Modem
Management
Connectivity
Manager
The Connectivity Manager tool has to be used to optimize

modems and connections. For details see chapter 5.3
Connectivity Manager - Modem Management.
Option SNMP
Northbound
Manager
If the optional SNMP Northbound Manager is licensed, it has to

be customized. For details see chapter 5.5 Northbound Manager
(Option) - Trap Forwarding to NMS.
Option Integration
of OMC 3.54
For integrating an existing OMC 3.54 into A.I.M.O.S. see chapter

5.7 Integration of OMC 3.54.
Visualization and
Customization of
A.I.M.O.S.
For the complete description on how to use A.I.M.O.S., please

see chapter 6 A.I.M.O.S. - Operations.
* The OMC 3.54 is the last OMC version available and the only one still supported by A.I.M.O.S.
Therefore, this manual only refers to OMC 3.54 whereas the online help still sticks to the more general
designation OMC 3.x(x).
Page 23
What to do
Modem
Configuration
Details
See chapter
The modem/modems for remote connections

have to be configured. Ensure that Flow Control
= Hardware is selected.
12 Appendix A
Modem
Installation and
Configuration
What to do
Details
Dial-In
Connection
For the connection from the repeater systems to

A.I.M.O.S. Dial-In connections can be used. The
installation for the Dial-In connections varies
depending on the used operation system.
Page 24
See chapter
13 Appendix B
Dial-In
Connectivity
M0125ANA.DOC
4 Installation Procedures
4 INSTALLATION PROCEDURES
4.1 PREPARATIONS
Note: Please observe that for detailed information about port and firewall settings a
separate document (the Whitepaper Architectural Examples for secure data
network environments of Andrew Repeater Elements, Data Connections and
Components) is available.
When using A.I.M.O.S. or OMC 3.54 in a Citrix environment the Installation Mode
of Citrix must be activated in advance.
4.1.1
Preparation of OMC 3.54 for the Combined Installation with A.I.M.O.S.
For A.I.M.O.S. to run with an OMC 3.54 on the same machine, the following steps
have to be executed before A.I.M.O.S. is installed:
In case ION (MMR) systems are integrated into the OMC 3.54, these systems have
to be manually deleted and later manually integrated into A.I.M.O.S.
The OMC3 Adapter of A.I.M.O.S. does not support the automatic data transfer of
these systems into A.I.M.O.S.
The OMC3 users and their defined rights are not mapped automatically to A.I.M.O.S.
due to a different logic. This information has to be transferred manually. A helpful
option in the OMC3 is to print a list of the users and their rights.
The OMC3 SNMP agent has to be stopped. The traps are all transferred to
A.I.M.O.S. via the OMC3 Adapter (see chapter 6.18) and forwarded via the
A.I.M.O.S. Northbound SNMP Agent (see chapters 5.1.4 and 5.5) which is based
on the A.I.M.O.S. database. Take care that the distinguished names of the network
elements that are mapped on A.I.M.O.S. side to the field trap info are entered.
Otherwise for that specific NE the alarms would not be forwarded via the SNMP
Northbound Agent.
Make sure that the OMC3 IP Server is stopped. This server scans automatically and
locks the RAS entries on the server, but together with A.I.M.O.S. at least a couple of
them are reserved for A.I.M.O.S. and the supervision of the 3rd generation NE.
The automatic backup of the OMC3 has to be stopped. For the common scenario
the backup is triggered from the Server Maintenance Tool. To execute a backup
either manually or automatically out of the OMC 3.54 application could lead to data
inconsistency between the OMC3 database and the A.I.M.O.S. database.
Every OMC3 application has to be stopped manually before the installation of
A.I.M.O.S. After the A.I.M.O.S. setup the OMC3 Adapter service will only start
up correctly in case any OMC3 application was completely stopped.
4.1.2
Map (Optional Tool)
This tool is based on the product Microsoft Map Point. Please follow the installation
instructions given by Microsoft. For details about the A.I.M.O.S. Map tool please see
chapter 6.14.
Prior to using this tool:
a license for A.I.M.O.S. with tool Map included has to be installed,
Microsoft MapPoint 2006 or 2009 with the correct maps (e.g. for Europe or the
US) has to be installed.
Page 25
4.2 A.I.M.O.S. SETUP

Insert the A.I.M.O.S. CD into the CD drive and install A.I.M.O.S. by starting
D:\Setup\setup.exe ...or any other path depending on the letter representing the CD
drive.
Note: Unlike in former versions of Windows, the file Andrew A.I.M.O.S. V2.x.0.msi
will no longer work for an installation under Windows 2008 or Windows 7. For
those and subsequent systems using the setup.exe file is mandatory.
The following window is only
displayed if the Microsoft Visual
C++ Package suggested (which is
required by the Firebird Database
Server) is not yet installed on your
system,. In that case confirm by
clicking the Install button.
The InstallShield Wizard starts.
Click Next >.
Choose to accept the terms in the

license agreement.
Page 26
M0125ANA.DOC
Enter your user name and

(optionally) your organization.
Select to install A.I.M.O.S. for all

users of the PC.
Confirm the selection of the

installation folder or select a
different folder (Change).
Please observe that the name
of such an individual folder
must not contain any special
character.
Select the setup type of

installation:
Client: Only the A.I.M.O.S.
client is installed. The client
needs a connection to the
A.I.M.O.S. server.
Note: The installation of an
A.I.M.O.S.
client
requires
Windows admin rights.
The
Typical
Server:
A.I.M.O.S. server with the
database is installed to this
PC. The OMC3 adapter and
the SNMP Northbound Agent
are not installed.
Note: The installation of an A.I.M.O.S. server requires Windows admin rights.
Custom: Select this setup type for the installation of additional features (e. g. OMC3
Adapter or SNMP Agent) by selecting the according feature in the
Custom Setup Select the program parts you want to install as explained in the
following:
Page 27
TestTools: This test tool (Hardware Simulation tool) is for Commscope technicians
only. It is not part of the A.I.M.O.S. application package and can be used for system
analysis.
SNMP Agent: This service is necessary for the SNMP Northbound Interface. It must
be selected for using SNMP alarm forwarding.
A.I.M.O.S. Client: This is the A.I.M.O.S. GUI.
OMC3 Adapter: Install this part only if A.I.M.O.S. has to run with OMC 3.54.
To confirm the selected

installation, click Install.
(By
clicking
Back
changes
to
the
installation setup can be
made.)
Page 28
M0125ANA.DOC
The status of the

installation process is
displayed.
Then, the installation is

complete.
Click Finish.
Before starting the Visualization, access the Server Configuration / Configuration

Tool (chapter 5.1) for licensing and for further settings. The licensing procedure is
described in chapter 4.5.
For updates please continue with the next chapter.
Page 29
4.3 A.I.M.O.S. UPDATE

4.3.1
A.I.M.O.S. Server Update
For an update of A.I.M.O.S. versions V1.3.x up to V1.4.x, stop the services

A.I.M.O.S. Connector, A.I.M.O.S. SNMP Agent and (if installed) A.I.M.O.S. OMC3
Adapter [Start-Settings-Control Panel-Administrative ToolsServices].
For versions V1.5.x and higher, the services are stopped automatically by the
update
routine.
Start
the
update
procedure
by
double-clicking
D:\Update\Update.exe.
Administrative rights are required for the update procedure.
Under Windows 2000 an update is only possible up to V2.5.0.
Under Windows 2008 we recommend using the "Administrator" account for the
update procedure.
After an update to V2.9 or higher, the SMPP passwords (configured in the Server
Configuration Tool; see sections 5.1 and 5.1.7) must be entered anew.
For licensing information please refer to chapter 4.5 How to get A.I.M.O.S. licensed.
For more detailed information about the server update refer to chapter 7.4 Update.
When using A.I.M.O.S. in a Citrix environment the Installation Mode of Citrix must
be activated in advance.
4.3.2
A.I.M.O.S. Client Update
As soon as an A.I.M.O.S. server update is finished, the client update will start
automatically with the next start of any Visualization client. But - depending on the
client and/or server version - the automated update may not be possible or restricted:
Client Version (update from ... to)
Automatic Update
from version V2.12 onwards to a version >/=V2.13
Possible *
Restrictions for Server Versions
With 64-Bit versions of Windows7 the client update is only working if Windows
option run as admin is chosen. *
Uninstall the according old client and carry out the new setup.exe again, available
either from the A.I.M.O.S. CD or via download.
*
Due to the data base change from InterBase to

Firebird, a client update from A.I.M.O.S.
versions before V2.13.0 is not possible, and an
error
message
will
be
displayed.
In such a case, unsinstall the old A.I.M.O.S.
client and install a new Client V2.13.
Page 30
M0125ANA.DOC
Note: An automatic update of an A.I.M.O.S. client requires Windows admin rights,
otherwise the Login screen will appear again.
If the following warning is
displayed initially, close it by
choosing 'No' and start the
Visualization anew.
Then, the actual client update procedure starts. Depending on the software version
not all of the screens shown in the following may be displayed. In any case, confirm
all screens you get with 'Yes'.
When the client update is finished,

the following screen is displayed:
Page 31
4.4 MIGRATION FROM WINDOWS 2003 32 BIT TO WINDOWS 2008 64 BIT

To update and migrate an existing A.I.M.O.S. installation only possible for
A.I.M.O.S. version 2.8 and higher from a Windows 2003 Server system to a
Windows 2008 Server system, proceed step by step as described in the following:
Old Windows 2003 Server (preparation):
1.
Update A.I.M.O.S. to version 2.8 or higher*, otherwise check at A.I.M.O.S.

Visualization with "?" and "Info" if an A.I.M.O.S. patch was installed.
2.
Check with "add or remove programs" and "Modify" which optional features are
installed, e.g. TestTools, SNMP Agent, Server, Client, OMC3 Adapter.
3.
Perform a database backup with the A.I.M.O.S. Maintenance Tool. The

database backup is saved as zip file.
New Windows 2008 Server (preparation):

4.
Install A.I.M.O.S. version 2.8 or higher* with the same optional features as
before and, if possible, to exactly the same location as at the Windows 2003
system. Please note:"C:\Program Files" could not be possible due to windows
restrictions. If applicable, install all A.I.M.O.S. patches as before. Please note: If
your Windows 2003 Server was updated, no patch installation is required
anymore.
5.
Copy the database backup zip file from the Windows 2003 system to the
A.I.M.O.S. installation.
6.
If applicable: Copy all repeater update files from the Windows 2003 system to
exactly the same location resp. to the relative location.
Further steps (which cannot be prepared):

7.
Shut down the Windows 2003 Server or at least deactivate all tasks in scheduler
8.
If possible: Make sure that its IP address is now used by the Windows 2008
Server. Otherwise all IP connections from A.I.M.O.S. to a repeater have to be
updated (because all repeaters still refer to IP address of the old A.I.M.O.S.
Server).
9.
If applicable: Switch all modems from the Windows 2003 system to the Windows
2008 system and make sure that incoming and outgoing connections are
working properly. Please also refer to chapter 13 Appendix B Dial-In
Connectivity.
10. Make a restore of the A.I.M.O.S. installation at the Windows 2008 Server with
the A.I.M.O.S. Maintenance Tool. Restore the most recent backup zip file from
the Windows 2003 A.I.M.O.S. installation.
Please Note: If your installation is now located in another directory, e.g.
"C:\Program Files (x86)", do not check the option "Restore Server Configuration
Tool Settings". In this case after restore a review of all settings in the Server
Configuration / Configuration Tool is mandatory.
*
The installed A.I.M.O.S. version at the windows 2003 system and at the windows 2008 system has
to be identical.
Page 32
M0125ANA.DOC
11 To basically check your new installation, proceed as follows:
11.1 Perform a database validation with the A.I.M.O.S. Maintenance Tool, then
check the database integration.
11.2 Perform a "Try Connection" to all repeaters, to check if each connection is
working properly.
11.3 Check all log files for hints or pending adaptations.
11.4 If applicable: Check all scheduled repeater updates in the Tool Scheduler
(Option).
4.5 HOW TO GET A.I.M.O.S. LICENSED

Please note: In case of any problems during license installation, refer to the
corresponding Troubleshooting chapter 10.3.
There are 3 different types of A.I.M.O.S. licenses:
Time-limited (60 days) trial license
This license includes all optional features and expires after 60 days. It can be
extended to a second trial period.
To order a trial license, please contact WIsupport@commscope.com.
Time-limited (14 days) update license
This license is installed automatically during update. It has the same restrictions as
the original license. This license ensures that there is no interruption in the use of
A.I.M.O.S. SW after an update. Within this time period (14 days) a not-time-limited
(permanent) license must be installed.
Not time-limited (permanent) license
This license must be purchased. To get your A.I.M.O.S. SW licensed permanently,
proceed as described in the following.
Page 33
1. Install the A.I.M.O.S. SW as explained in the previous chapters.

2. Put the A.I.M.O.S. License File received by e-mail onto the A.I.M.O.S. Server file
system (e.g. drive C:).
3. Select StartPrograms Andrew A.I.M.O.S. Server Configuration to start
the A.I.M.O.S. Configuration Tool and choose Licenses.
Press the Add License File button.
3. Select the License File and press the OK button.

4. Double-check that the license you are going to install
o is for your Organization (MCC/MNC), and
o has not already been used for another A.I.M.O.S. project within your
Organization
Note:
It is illegal to install and use the A.I.M.O.S. Server Software on multiple
physical or virtual servers. A license file is for one single installation only.
5. Type YES and press OK button:
Page 34
M0125ANA.DOC
4.6 LOGIN SETTINGS

Server only:
If the Visualization is automatically launched directly after the setup procedure (see
chapter 4.2), a valid license must be installed during the login process. For this
purpose the Configuration Tool (see 5.1 Server Configuration / Configuration Tool)
will be started automatically but no further settings can be made.
Thus, if more settings are required or in case of doubt, starting the Server
Configuration to install the license and to configure the system before the
Visualization is started for the first time is recommended. In that case, please
proceed as described in chapter 4.5 How to get A.I.M.O.S. licensed.
Client only:
The following Watchdog Client window is displayed if no connection to the
WatchDog service can be established at the first start of the Visualization after a
Client only installation.
Make the required entries, i.e. Server IP (= IP Adress of the A.I.M.O.S. Server) and
Server Port (= Server Port of the WatchDog) for setting information see
explanation of login dialogue in the Server and Client Settings section on the next
page). Confirm with the Enter key or by clicking the button Change A.I.M.O.S.
Server IP / Port (each connection try is shown in the status bar) to get to the login
dialogue, where the entries made will be adopted.
It is also possible to close the window without making these entries by clicking the
red X; in that case, the entries have to be made in the login dialogue.
After a successful first login the WatchDog message will no longer be displayed in
subsequent logins.
In case the window is displayed again or does not close, please verify the network
settings of the A.I.M.O.S. Server and A.I.M.O.S. Client as well as those of the
network used (e. g. firewall settings, etc.).
Page 35

Server and Client Settings:
In the A.I.M.O.S. login screen, use the Hide Connection Setup / Show Connection
Setup buttons to hide / show the fields IP Address of the Database Server and
Server Port of the WatchDog (generally, these fields are only displayed if the
information is still missing or incorrect):
The fields must be set as follows:

IP Address of the Database Server IP address of the A.I.M.O.S. server (127.0.0.1
is the address of the computer you are working at).
Server Port of the WatchDog The default port 7422 can be changed if it is used
by another application, but please observe that the Server Port of the WatchDog of
the Server Configuration / Configuration Tool (see chapter 5.1) must be adapted
accordingly. For port and firewall settings a security whitepaper is also available (see
chapter 4.1).
Note: If LDAP has already been enabled (e g. on the Server level in case of a Client
installation) the login differs slightly. For details see chapter 5.1.3.4.
Only at the first login as Admin the system will prompt a window to enter an
individual password after entering the Username Admin and the initial default
password start:
Then, the license

must be installed
(via the A.I.M.O.S.
Server Configuration /
Configuration Tool):
Page 36
M0125ANA.DOC
If no valid license is at hand, abort the login by clicking No. You can resume the
process as soon as a license is available, either directly by starting the A.I.M.O.S.
Visualization anew (continue here) or via the Server Configuration / Configuration
Tool as explained in chapter 4.5.
Upon clicking Yes a window to choose the license file will open:
Browse to the
location
where
the license file is
stored and open
it.
The License Key

will be entered
automatically to the
Add License
window:
Upon clicking OK the license will be installed and the following confirmation is
displayed:
Click OK to start the Visualization.

Page 37

For your notes:
Page 38
M0125ANA.DOC
5 A.I.M.O.S. Configuration
5 A.I.M.O.S. CONFIGURATION
Please note: All settings made in the following chapters (except 5.8 to 5.10) are
included in an A.I.M.O.S. backup file, so it is recommendable to make a new backup
if settings in the A.I.M.O.S. Configuration Tool or other configuration settings
described in the next chapters were changed.
5.1 SERVER CONFIGURATION / CONFIGURATION TOOL
Select StartPrograms Andrew A.I.M.O.S.
Server Configuration
to start * the A.I.M.O.S. Configuration Tool.
* Please note: Only users with the "Administrator Role" assigned (see chapter 5.4.3.1) are allowed to
start the Sever Configuration.
The Security page is only available for the user Admin irrespective of the user role
assigned.
Click the button 'Reload' to delete the changes made in the current session and to
display the actual settings.
Use the Backup button to make a backup of all current "Configuration Tool" settings
(except those of the page Licenses) in an "A.I.M.O.S. Settings File", which is an
A.I.M.O.S.-specific file format ending on "set" that cannot be changed.
Use the Restore button to restore all "Configuration Tool" settings (except those of
the page Licenses).
Note:
Please observe that these Backup / Restore buttons are not identical to the
A.I.M.O.S. database backup/restore described in chapters 7.1 & 7.2. However, some
of the settings saved or restored by them are also part of the A.I.M.O.S. database
backup/restore.
Page 39
5.1.1
Licenses
The following items and tools can be activated by the A.I.M.O.S. license:
Number of NEs
Expiration date (one option is endless)
SNMP Northbound Manager
Map
Scheduler
Performance Manager
LDAP
These items may cause a new or additional license key request. For more
information please contact Andrew Wireless Systems product support.
Regarding the licensing procedure and important restrictions to be observed, see
also chapter 4.5 How to get A.I.M.O.S. licensed.
Open the tab Licenses. Click the Add license button to register the license key for
A.I.M.O.S.
Enter the Organization

Code and the License Key.
Or press Browse to select
the License file from a
directory.
Double-clicking the license key file in the explorer at the PC where the database is
installed will automatically add the new license key.
Please note: In case of any problems during license installation, refer to the
corresponding Troubleshooting chapter 10.3.
Page 40
M0125ANA.DOC
5.1.2
General - IP Parameters
Select General to check or edit the IP parameters.
The following IP Ports/Settings have to be configured or can be accepted as default

(for port settings please see Security Whitepaper as explained in chapter 4.1):
Parameter
Path / Description
Server Port of the

OMC Server
ServerConfigTool | General | Server Port of the OMC

Server (A.I.M.O.S.)
SNMP Trap Port of ServerConfigTool | General | SNMP Trap Port of the

the OMC Server
OMC Server (A.I.M.O.S.)
Default
7420
162
Base-Port for Connections to V.)
Server ConfigTool / General

Base-Port for Connections to Visualizations
50000
Visu Gateway Port
Port for communication between OMC Server and

A.I.M.O.S. Visu.
Please note: Use default setting 5060 if you wish to
update an old A.I.M.O.S. client (V2.5.0.111 or less).
Please observe that port 5060 is also the default port
of SIP (Session Initiation Protocol) for VoIP
communication.
5060
Server Port of the

WatchDog *
ServerConfigTool | General | Server Port of the

WatchDog
7422
Default shutdown
timeout (Minutes)
The WatchDog informs about applications that need to

be stopped for some features (e.g. Backup) and will
stop them automatically after a defined period.
Changes made with these applications will not be
saved. Enter the time the WatchDog will wait before
shutting them down, so that this period can be used to
save the changes.
* This setting must be consistent with the Server Port of the WatchDog of the Visualization (see 4.6).
Page 41
Parameter
Path / Description
Default
Modem Session
Timeout (Minutes)
A connection to a unit will be terminated after an

adjustable time. Enter the idle time (in minutes) after
which a session will be terminated.
Alarm Limiter
Recovery Time
(Minutes)
Recovery time (t1):

The value for t1 is configurable from 0 (alarm limiter
mode disabled) to 1440 minutes (default is 10 min). **
10
** The corresponding alarming configuration is explained in more detail in the following.
Alarming configuration with recovery time setting:
When an alarm of a specific type (e. g. Amplifier alarm) from a specific NE is raised
by the NE for the first time, and then cleared by the NE (= first red bar / first alarm
in the illustration above), the Alarm Limiter Recovery Time setting does not yet take
effect.
This alarm will be raised and cleared in the A.I.M.O.S. Visualization as notified by
the according NE via the A.I.M.O.S. southbound interface.
If the same alarm is notified again by the same NE a second time (or several
times) after the first alarm was cleared in an interval that is smaller that the recovery
time (t1) set (= green bars 1. 4. in the illustration above), the A.I.M.O.S.
Visualization will show this condition in two ways:
1. NE-generated alarm:
Even if this specific alarm is raised (and cleared) several times in intervals below
the recovery time (t1) set, it will be shown in the A.I.M.O.S. Visualization as one
single alarm (= second blue bar in the middle line in the illustration above) of this
specific alarm type, e. g. Amplifier alarm.
2. Intermittent Alarm generated by A.I.M.O.S.:
Additionally, the A.I.M.O.S. Visualization shows an Intermittent Alarm (= first blue
bar in the bottom line in the illustration above) to inform the user that a series of
recurring alarms is visualized as one. This indication also specifies the alarm type
concerned.
Page 42
M0125ANA.DOC
Example:
Clearing the alarms:

1. NE-generated alarm:
The alarm actually generated by the NE (due to recurring alarms of the same type)
will stay active until the recovery time (t1) set has elapsed without a recurrence of
this specific alarm type.
Example: If the default recovery time of 10 minutes is set, the alarm visualization
stays active until 10 minutes have elapsed after the last clearance of this alarm by
the NE without the alarm recurring again.
Clearing this alarm in advance can be achieved by a manual clear or by an active
alarm query.
2. Intermittent Alarm generated by A.I.M.O.S.:
The Intermittent Alarm will be displayed until it is cleared manually by the user
irrespective of the alarm condition notified by the NE.
Once these alarms are cleared, the cycle will start anew (in an according alarm case)
as illustrated in the figure on the previous page.
5.1.3
Security
Select Server Configuration Tool / Security (only available for user Admin
irrespective of the user role assigned) to check or edit Password Settings (see
5.1.3.1), Account Settings (see 5.1.3.2), and (in case a license for LDAP is installed)
LDAP Settings (only available if a license for LDAP is installed; see 5.1.3.3).
Page 43
5.1.3.1
Password Settings
As a general restriction, using passwords that may easily be guessed is not allowed.
Thus, it will not be possible to use passwords containing for example:
more than three identical characters

a series of more than three ascending or descending letters or figures, e.g.
"123", abc, etc.
a user name, e.g. "admin" or the current user name
evident terms, e.g.:
- password or passwort
- qwert
- azert
- aimos
Upper or lower case variations of all the excluded words listed above are not allowed
either.
Minimum Password Length
Passwords should have a length in the range from 5 to 40 characters. The value in
this field specifies how long the password must be at least *. Each password must
fulfill this requirement.
* for scheduler action Configure Node A User as explained in chapter 6.10.3.6 the maximum setting
possible is 16
Password Security Level

Use this entry to specify whether passwords must contain certain characters.
Numbers, special characters* or a combination of these are possible.
The following levels are available:
Special characters are !$%&/{[(<=>)]}\?^`'"*+~-_.:,;#|@. All country-specific

characters such as , , , , , etc. are not allowed. To avoid accidental usage of
such characters make sure that the keyboard layout set in the operating system
corresponds to the actual keyboard layout.
A modification in the security level will result in an obligatory password change with
the next login if the current password does not match the new regulations. In that
case the system will prompt the user to set a new password when he logs in again.
Page 44
M0125ANA.DOC
Initial Password Durability
This value within a range from 0 to 744 hours sets the length of time the initial
password of a newly created account is valid until the first login is required to change
the password. When the set period expires before the initial password has been
changed, the account is disabled. A value of 0 indicates, that the password will never
expire; use this value in order to disable the password expiration facility.
Note: For enabling locked accounts use the Account Manager (see 5.4.4).
Password Durability
This value within a range from 0 to 365 days decides the period of days after which
passwords will expire. A value of 0 indicates, that the password will never expire; use
this value in order to disable the password expiration facility. If a password has
expired, a login is prevented until a new password is assigned.
Password History
This value in a range from 1 to 255 specifies the number of distinguished passwords
that must be used before a certain one can be used again. A value of 3 indicates, for
example, that three different passwords must have been used in between before a
password can be used once again, i.e. the user may have a list of four passwords in
circulation.
5.1.3.2
Account Settings
These settings specify the criteria for account lockouts due to invalid login attempts
or for user account deactivation after a definable inactivity period.
Please observe that the first two settings apply to the Administrator account, as well.
Account Lockout Threshold
This value (3 - 255 is possible) sets the number of invalid login attempts that are
allowed before an account (incl. Administrator) is locked out temporarily as specified
in the Account Lockout Duration.
Account Lockout Duration
This value sets the length of time (1 - 1440 minutes is possible) an account (incl.
Administrator) is locked after the Account Lockout Threshold has been reached.
Permanent Account Lockout Threshold
This value (3 - 255 is possible) sets the number of invalid login attempts that are
allowed before an account (excl. Administrator) is disabled.
Example: If the Account lockout threshold is set to 5, the Account lockout duration to
30, and the Permanent Account lockout threshold to 6, the according account will be
locked after 5 invalid login attempts for 30 minutes before another login attempt is
possible. If this fails, too, the number of 6 invalid attempts is reached and the account
will be disabled after the next invalid attempt.
Maximum User Account Inactivity (Days)
If an account is not used for the period set in this field, it will be deactivated
automatically. Settings from 0 to 365 days are possible; the default value is 90
(setting 0 means the feature is not used, i.e. inactivity of an account will not lead to its
deactivation).
Page 45

Notes:
- For enabling locked or deactivated accounts use the Account Manager (see 5.4.4).
- If Account Lockout Threshold and Permanent Account Lockout Threshold are set to
the same value or if the Permanent Account Lockout Threshold is set to a smaller
value than the Account Lockout Threshold, only the Permanent Account Lockout
Threshold becomes active; i.e. once the set number of allowed invalid login
attempts has been reached, the account will be deactivated (thus, in such a
constellation the Account Lockout Threshold will be ineffective).
5.1.3.3
LDAP Settings
Use these fields to configure the settings for user management via Windows Active
Directory (LDAP). Please observe that these settings are only displayed if an LDAP
license is installed.
Before configuring these settings in A.I.M.O.S., LDAP must be configured a follows:
The client computer (where AIMOS_Visu.exe is executed) needs to be a member of
a domain that is managed by an Active Directory Domain Controller. The LDAPdriven login also requires that the current Windows user is a domain user within the
same domain. Within the Active Directory, the user account must be assigned to a
global user group that corresponds to one of the A.I.M.O.S. user roles.
The server must support the Active Directory services and the LDAP interface. LDAP
must be accessible from the client side; thus the server and client side firewall must
allow this.
LDAP Enabled
Use to enable / disable this function on A.I.M.O.S. pages.
When activated, the LDAP (Lightweight Directory Access Protocol) interface
synchronizes between the user information base of a LDAP-connected server and
the user and role system built into A.I.M.O.S. The server side is typically realized by
an instance of the Active Directory (AD) service on a Microsoft Windows Server
based computer.
To achieve this, A.I.M.O.S. queries the active directory, using the configured LDAP
path, whenever a windows user (i.e. a member of the configured domain) attempts to
log on in the AIMOS_Visu program. Please note that this does not happen for a user
named "Admin".
In the active directory, the group membership state of the requesting user is queried
for groups that are named starting "AIMOS_" (see example below). The group names
configured in A.I.M.O.S. are looked up in the list of AD group memberships by putting
the text "AIMOS_" in front of each role name found in the AIMOS account manager.
Thus, the A.I.M.O.S. role name "Standard User Role" would match an AD group
membership of a group exactly named "AIMOS_Standard User Role" etc.:
Page 46
M0125ANA.DOC
After successfully querying the AD via LDAP, the user information found in the AD is
replicated into the A.I.M.O.S. user base and the user group memberships found in
the AD is reflected into the role membership.
Moreover, if a user is found to be disabled or non-existing in the AD, this is also
replicated into A.I.M.O.S. by disabling this user. By replicating the user and role
information into the A.I.M.O.S. user database, a user would still be able to log on to
AIMOS_Visu if the AD server would become temporarily unavailable. Note that for a
local logon, the user would need to have a known password. As replicated users
does not have a password by default (and also an empty password would not be
accepted of course), the A.I.M.O.S. Admin would need to assign a password to a
replicated user in the Account Manager first, in order to enable such a user to logon
without LDAP access.
Note:
Please also observe that after the expiration of the LDAP license all users that were
created via LDAP will be automatically deactivated. Users explicitly created or
changed (e. g. by a new password) by the Admin will stay active. All users
deactivated due to license expiration will also remain inactive when LDAP is
activated again.
LDAP Domain
Enter the name of the domain. Only Windows users who are member of this domain
can take advantage of the LDAP interface feature.
LDAP Path
Enter the LDAP Path using LDAP URL syntax like this:
LDAP://myserver/cn=Users,dc=mydomain,dc=com
LDAP Connect String
This is the connect string that used to configure the OLE DB Provider for Microsoft
Directory Services.
Example that uses an Administrator account from domain mydomain to query the
server:
Provider=ADsDSOObject;User
ID=mydomain\Administrator;Password=mypassword;Encrypt
Password=True;Mode=Read;Bind Flags=0;ADSI Flag=-2147483648
To configure the connect string, use this example as a template and change the
values for the User ID and the Password fields according to your needs.
Page 47
5.1.3.4
Visualization Login with LDAP
Please observe that LDAP will affect the login to the Visualization, only, if all of the
following conditions are fulfilled:
LDAP has been configured correctly
LDAP has been enabled in A.I.M.O.S.
LDAP is available at this computer
an LDAP login to A.I.M.O.S. has been assigned to the user currently logged in to
Windows
In that case the login will be as follows:
Instead of the general field for entering the Username a choice between the
A.I.M.O.S. user "Admin" and the user currently logged in to Windows is provided for
this field. If the current Windows user is selected, no password entry is required. (In
the examples above the Windows user "Administrator" was logged in.)
5.1.4
SNMP Northbound Interface Settings
Select Server Configuration Tool / SNMP Northbound.
Notes: For port settings also see Security Whitepaper as explained in chapter 4.1.
The screen shot above includes the SNMPv3-specific fields (listed in section
5.1.4.9). Without SNMPv3 these will not be available.
Page 48
M0125ANA.DOC
5.1.4.1
Server Port of the A.I.M.O.S. SNMP Agent
The default listening port of a SNMP Agent is 161. In order to avoid conflicts with the
Microsoft SNMP Agent, which might be installed on some computers and already
using the default port, the A.I.M.O.S. SNMP Agent uses port 163 by default.
If this value is set to the default SNMP Agent port, the Microsoft SNMP Agent must
not
be
installed
or
must
not
use
port
161;
i.e.
the
file
[WinDir]\SYSTEM32\DRIVERS\ETC\SERVICES must not assign port 161 to
snmp/udp.
5.1.4.2
Default Port for Outgoing SNMP Traps
With A.I.M.O.S. the SNMP managers which receive an alarm notification in case an
alarm arises can be defined. The SNMP managers have to be defined with IP
address and IP port. If the IP port is not entered, this default port is used. Path:
ServerConfigTool | SNMP Northbound| Default Port for outgoing SNMP Traps;
default: 162.
5.1.4.3
Agent Shutdown Delay
If the A.I.M.O.S. SNMP agent is stopped, a shutdown notification for the SNMP
manager is sent. Enter a shutdown delay (in seconds). The A.I.M.O.S. SNMP agent
will be shut down after this delay, i.e. the A.I.M.O.S. SNMP agent will wait for the
acknowledgements of this notification before it is stopped.
5.1.4.4
Length of Generated Community Names
If the SNMP Login is used (via A.I.M.O.S. Login), community names are created by
the A.I.M.O.S. SNMP agent. Enter the length of the name in the range of 1 to 40
chars, default is 8 chars.
Note: The longer the name the saver is the connection.
5.1.4.5
Private SNMP Community Name
In case the SNMP Manager is not capable to perform the login process (via
A.I.M.O.S. login), a Private Community Name can be entered here. With this private
community name full access (administrator rights) to the MIB is allowed. Do not enter
a private community name if the SNMP Manager shall use the login process.
5.1.4.6
IP Address of Alternate SNMP Agent
SNMP requests, which are unknown to the A.I.M.O.S. SNMP agent can be forwarded
to another SNMP agent. Enter the IP address of this alternative SNMP agent. The
default value is IP address 127.0.0.1, i.e. unknown requests are forwarded to the
Microsoft SNMP agent running on the same computer like the A.I.M.O.S. SNMP
Agent.
Page 49
5.1.4.7
Server Port of Alternate SNMP Agent
SNMP requests, which are unknown to the A.I.M.O.S. SNMP agent can be forwarded
to another SNMP agent. Enter the IP port of this alternative SNMP agent. The default
value is IP port 161.
5.1.4.8
MIB Supported by the Agent
The A.I.M.O.S. SNMP Agent supports 3 MIBs. Usually the A.I.M.O.S. MIB should be
used unless the higher level supervision system requires a specific MIB for reading
the alarm table or restarting the alarm synchronization:
If the OID 1.3.6.1.4.1.6408.100.1.3(mRestart) is needed to start the alarm

synchronization, OMC3 MIB should be selected.
If Nokia NetAct is used, NE3S MIB should be selected.

For
Nokia
NetAct
a
separate
manual
is
available
via
"~\Andrew\AIMOS\MIB\Q0217RHA.pdf" (i.e. in the same directory as the
SNMP Interface Description).
Otherwise A.I.M.O.S. MIB should be selected, even if OMC3 Trap Format or Nokia
Trap Format is needed. In case of the A.I.M.O.S. MIB any Trap Format can be
selected in the A.I.M.O.S. Visualization program, Northbound Manager.
If NE3S is selected as "MIB Supported by the Agent", the additional field
"Translation Scheme for Nokia DN" is available to choose the name scheme to be
used for NEs. Available are Legacy, Improved, or Extended. For more details, refer
to the Nokia NetAct manual under "~\Andrew\AIMOS\MIB\Q0217RHA.pdf"
5.1.4.9
SNMPv3-related fields
For customers using SNMPv3 the following additional fields are available:
Supported Security Models and Levels
Security Engine ID
Security Level
User Name
Authentication Algorithm
Authentication Password
Encryption Algorithm
Encryption Password
These are described in detail in the AIMOS SNMPv3 Configuration Guide which is
provided for customers using this feature. For the location of this guide see section
2.5.5.
Page 50
M0125ANA.DOC
5.1.5
OMC 3
Note: For port settings also see Security Whitepaper as explained in chapter 4.1.
IP Parameter
Description
IP Address of the
OMC3 Adapter
Enter the IP address of the PC (or network interface) where the

OMC3 adapter is installed.
Server Port of the

OMC3 Adapter
Enter the server port of the PC (or network interface) where the
OMC3 adapter is installed. The default port is 7421
OMC3 Database
File Location
Enter or select path and filename of the OMC3.54 database file.
The OMC3 adapter integrates alarms of repeater systems of the first and second
generation, which are supervised by an OMC3.54.
5.1.6
SMTP Mail Server
5.1.6.1
Configuration of Email Forwarding
Select Server Configuration Tool / SMTP.

To make A.I.M.O.S. sending alarm notification emails, you first have to set up the
SMTP (Simple Mail Transport protocol) parameters using the Server Configuration
tool.
The first three parameters (SMTP Server, Server Port and From Address) are
obligatory.
1. For the SMTP Server, you can either enter the IP-Address (preferred, if it's a static
address) or the host name. Leaving this field blank disables the email function.
2. The Server Port of the SMTP Server defaults to 25, which is most often used.
3. The From Address is the mail address that A.I.M.O.S. should use as a sender
address of the emails (e.g. "aimos@customer.com"). It depends on the SMTP
Server configuration whether this can be any arbitrary address.
Most SMTP Servers will require this address to correspond to some account data
on the server side.
Page 51

The remaining parameters (HELO Name, SASL User Name and Password) are for
authentification and need to be adjusted according to the requirements of the SMTP
server. Many servers do solely rely on the from-address matching an email account.
In this case, these parameters can be left blank.
Please ask the server administrator for details.
Note that "POP-before-SMTP" authentification is not supported.
After changing these parameters the A.I.M.O.S. Connector service must be restarted
in order to activate the changes.
Please observe the email status display in the first tab page of the diagnostic dialog
that can be opened by double-clicking the A.I.M.O.S. Connector symbol near the
clock in the status bar to verify that emailing was activated.
After setting these SMTP parameters, you need to enter email addresses of the
users that you want to receive emails. To do so, open the Account Manager in the
A.I.M.O.S. Visualization program and enter the email address in the appropriate field
of a user record. Also, switch the "Active" check next to the email address field on.
You can even enter more than one email address for one user by separating the
addresses with a comma.
You can monitor the email sending using the A.I.M.O.S._Connector services
diagnostic dialog:
Change to the Diagnosis tab page and check the "All monitoring enabled" mark.
Then select the email tab card. Email activity is logged to the "eMail Errors" and
"eMail Monitor" lists.
5.1.6.2
SMTP Server (Host Name or IP Address)
A.I.M.O.S. offers the possibility to send emails in case alarms arise. Enter the SMTP
server. Enter the IP address or the Host name.
5.1.6.3
Server Port of the SMTP Server
If a SMTP server is installed, a server port number can be entered, which can differ
from the standard server port number (25).
Note: For port settings also see Security Whitepaper as explained in chapter 4.1.
5.1.6.4
From Email Address
Enter a sender address (email address) if necessary.

5.1.6.5
HELO Name
Enter the HELO name if necessary.

The Helo name is part of the SMTP protocol. It identifies the SMTP client. Some
servers do not accept MAIL requests before HELO. Clients use HELO as the first
request in every session. This field is used when A.I.M.O.S. tries to contact a user by
mail.
Page 52
M0125ANA.DOC
5.1.6.6
SASL Login Username
Enter the SASL Username if necessary.

Acronym for Simple Authentication and Security Layer. SASL is a method for adding
authentication support to connection-based protocols. SASL takes effect when a
protocol initiates a command for identifying and authenticating a user to a server.
SASL also includes an option for negotiating protection of subsequent protocol
interactions. With this option in effect, SASL places a security layer between the
protocol and the connection.
5.1.6.7
SASL Login Password
Enter the SASL password if necessary.

5.1.7
SMPP
The Short Message Peer-to-Peer (SMPP) protocol is a telecommunications industry

protocol for exchanging SMS messages. The SMPP protocol version supported by
A.I.M.O.S. is V3.4.
To use this protocol, a Short Message Service Centre (SMSC) must be reachable
from the A.I.M.O.S. server over an IP connection and the SMSC must provide a
SMPP account that supports both sending and receiving short messages over a fix
phone number. The A.I.M.O.S. Connector acts as a SMPP client while the SMSC is
the server. The client role is also referred to as an External Short Message Entity
(ESME).
Once the SMPP settings are completed and this service is Enabled (by tagging the
according field), a new "virtual modem" named "SMPP-Gateway" will show up in the
Connectivity Manager where this virtual modem can be used in communication
groups just as regular modems.
Source Address (own Phone No): Enter the phone no. from which the SMS
messages will be sent.
The Registered Delivery option can be used to request delivery receipts from the
SMSC, which will be included in the log files and can help in troubleshooting.
Page 53

Source Address (own Phone No): Enter the phone no. from which the SMS
messages will be sent.
The Registered Delivery option can be used to request delivery receipts from the
SMSC, which will be included in the log files and can help in troubleshooting.
Mode: Two modes are available for the SMPP communication. The appropriate
mode, like all the other SMPP settings, must be chosen in accordance with the
capabilities of the SMSC and the provided SMPP account information.
One-Connection Mode: In this mode, only one TCP/IP connection between ESME
and SMSC is used and both sending and receiving of short messages is processed
using this single connection. The single connection will be opened in transceiver
mode.
Two-Connection Mode: In this mode, two separate TCP/IP connections between
ESME and SMSC will be used, one for sending short messages and the second for
receiving incoming short messages. Both use the same phone number. The first
connection will be opened either in transmitter mode (if Registered Delivery option
is switched off) or in transceiver mode (if Registered Delivery is on) while the
second connection will operate in receiver mode. Note that in two-connection mode,
the two-connection must use different remote port numbers, unless the remote IP
addresses are distinct. For entering the data for sending use the fields in the left
column, for receiving information use the right one.
Remote IP Address / Port are the address information of the SMSC server side and
must be provided, while the Local IP Address / Port settings are optional and
usually only required in situations where a firewall is used that needs fixed address
information in order to allow communication.
The parameters SystemID, Password, System Type, Type of Number (TON) and
Numbering Plan Indicator (NPI) are usually provided by the SMSC server as part of
the account information and must be entered accordingly. Note that SystemID is
sometimes referred to as "User Name". For some SMSCs, the System Type setting
might not be required at all.
Page 54
M0125ANA.DOC
5.1.8
Housekeeping
Use to set how many days certain data should be saved either on the A.I.M.O.S.
server file system or in the A.I.M.O.S. database. Depending on the type of data
select to 'Delete database data older than x days' or to 'Delete archive files older than
x days'.
The screenshot above shows the preset default values of the parameter x; for the
individual value ranges of x refer to the explanations in the following.
Watchdog Logs: (see also chapter 9.1.2.7)
a) Delete database data older than x days
not configurable since there are no database data
b) Delete archive files older than x days
The archive files are deleted from the hard disk after the set number of days.
The range for x is 1 to 365 days.
Checks as to which files have to be deleted are carried out once a day.
Connector Logs: (see also 9.1.2.8)
SNMP Agent Logs: (see also 9.1.2.11)
Page 55

Alarm History:
Alarms older than x days are deleted from alarm history database table and
saved as archive files.
The range for x is 1 to 364 days
Checks as to which data have to be deleted are carried out once a day.
Old alarms are moved / archived into the file in bundles of 100, i.e. 100 alarms
are archived and deleted from database, then, after a pause of some seconds
the next 100 alarms are moved, etc. This ensures the archive process is
running in the background and does not interfere with operational tasks, even
when a very high number of alarms have to be archived.
The Alarm History Archive Files thus created are weekly files, i.e. each
Monday a new file is created. The file name contains the date of the
respective weeks Monday (local time). Into such a weekly file the alarms are
moved for one week.
Checks as to which files have to be deleted are carried out each Monday.
Performance Data:
See also chapters 6.10.3.4 and 6.16.
Performance data older than x days are deleted from the performance data
database table (but not archived to a file).
Checks as to which data have to be deleted are carried out once a day.
Only valid / available for Node X performance data csv files.
The files are deleted from the hard disk after the set number of days.
Schedule Runs: (see also 6.10)
Schedule runs log files are deleted from the database after x days.
No archive files will be created.
There are no archive files.
Page 56
M0125ANA.DOC
5.2 PREFERENCES EDITOR - CUSTOMIZING A.I.M.O.S.

The Preferences Editor is used to customize certain system settings, e.g. alarm
settings, the connectivity pages, the tool Scheduler, etc.
When new NEs are created, A.I.M.O.S. uses the Connectivity settings chosen here
as default.
Please observe that access to this tool (and the available fields) can be configured in
the Account Manager rights as explained in chapter 5.4.2.
StartAll ProgramsAndrew A.I.M.O.S.Visualization.
In A.I.M.O.S. Visualization select Tools / Preferences Editor.
Note: The settings of this tool are effective for all NEs.
The parameters displayed in the Preferences Editor depend on the A.I.M.O.S.
configuration. If the tool Scheduler is not licensed, the Alarm Polling parameters
will be displayed. With a Scheduler license the Preferences Editor shows the
Scheduler parameters, instead.
Page 57
Connectivity: Customize connectivity related settings.

Red marked lines/parameters in the connectivity pages
(see chapter 6.9) are an indication that there is an
inconsistency between the current connectivity settings
of an NE and the settings of the Preferences Editor.
Preferred Notification Type: Select the alarm reporting mode to be used by the
NEs ( Field Alarm Type of Connectivity page; see section 6.9.5.3). This setting
applies only to NEs that use the SNMP protocol for communication, which has been
configured when the NE was created (see section 6.5).
Notification = unacknowledged mode. Alarm delivery is not reliable, an alarm can get
lost along the transmission over the network.
Inform = acknowledged mode. Alarm delivery is reliable; every alarm will be
retransmitted if necessary until A.I.M.O.S. confirms the delivery.
Blank = (empty setting). No preference is set so that the alarm type setting of the
NEs will not be checked by A.I.M.O.S. and the parameter will not be marked red in
the connectivity pages irrespective of the setting.
Note: The alarm notification type of
ION-M systems that do not use the SNMP protocol is similar to 'Inform' and
cannot be changed.
all SMS-connected NEs is similar to 'Notification' and cannot be changed.
Preferred Packet Switched On Demand Idle TimeOut: The Packet Switched On
Demand session is initiated by the NE on request by a so called 'Wake-up-SMS'. It
will be closed automatically when no communication has taken place for the time
interval set as idle timeout. The default setting is 5 minutes.
Expected SMS Response: Specifies the time in minutes the Connector should wait
for an SMS response.
Available Connectivity Modes: In the default setting all connection modes are
displayed which A.I.M.O.S. can handle. Select the modes from the list which will be
useable in your network for connecting NEs.
Scheduler: Only available when the tool Scheduler is licensed (see also chapter
6.10 Tool Scheduler (Option)).
Concurrent Network Element Connections:
Circuit Switched
SMS
Packet Switched Always On
Local Area Network
Dial Server
These settings are used to limit the number of concurrently executed scheduled
activities to a reasonable maximum. This limit can be applied individually for each
connection type (Circuit Switched, Packet Switched On Demand, etc.). As an effect,
no more that the number of scheduled activities specified here will be started in
parallel for every single type of connection.
For example, after setting this number to 3 for "Circuit Switched", no more than 3
parallel modem connections to network elements will be started by the scheduler. So
this number should not exceed the number of communication resources (i.e.
modems) that are available for the respective type of communication. Otherwise,
internal contention for the resources might grow and scheduled activities are more
likely to fail after a timeout waiting for a resource.
Page 58
M0125ANA.DOC
Alarm Polling: Alarm Polling parameters are only available when the tool Scheduler
is not licensed.
Use to customize the polling settings. How individual NEs are included into Alarm
Polling is described in chapter 5.6 Alarm Polling.
Alarm Polling Active: Set the check-mark to activate alarm polling. (This parameter
can also be set in Configuration General as explained in chapter 5.6.)
Time Plan Settings: Select a time interval for polling.
Next Run Time: This field indicates the next execution date and time according to
the Time Plan Settings with the check-mark enabled.
NE: Sequential Delay Seconds: Interval time between pollings of individual network
elements.
Severity Icons: Customize the colors for each severity level. The NE-icons in the NE
Tree and in the supervision will change their color immediately after saving.
Note: If the Map is opened, close and reopen it to adopt the severity colors.
Alarm Settings:
Auto Recognition: Check the severity levels which shall be recognized
automatically in the list box.
With activated Auto Recognition, alarms will be transferred from the active alarm list
to the alarm history as soon as they have been cleared. If not, each alarm requires
an additional manual recognize by an A.I.M.O.S. user.
Note: It is recommended to activate Auto Recognition if alarms are just
forwarded and not maintained in A.I.M.O.S. Alarms need not to be recognized
in the A.I.M.O.S. database.
Cannot Handle Information Alarms: In some cases it is possible that the customer
system cannot handle the alarm severity Information. In this case set the checkmark to treat information as warnings.
Alarm Representation
Audible Alarm Notification: Select Control Panel Settings if an audible alarm
notification is desired.
Show Alert Box: Display a message box: Settings can be Always, if active alarms
are not in view, or Never (= default value).
Show Alert Cause: Settings can be Any new alarm or Severity getting worse.
Show Alarm List in Severity Colors: Tag to show the background colors of the
alarm list in Supervision in the colors designated to the levels in Preferences
Editor / Severity Icons.
Page 59

Other Settings:
Visual Improvements (prevent gray text): If this option is checked, the display of
text is changed as follows to achieve a better contrast:
- lines that are ReadOnly in black font (instead of gray)
- changeable lines in bold font (instead of normal font)
Restore Network Element Tree on Visu Start: Checking this option makes the
Visualization restoring the Expanded State of all folders in the Network Element Tree.
Legacy Taskbar Representation: Can be set
check-mark) to configure the system as follows:
Legacy Taskbar
Representation is ON
The task bar provides a
Taskbar Buttons
button
for
the
Visualization.
to ON (check-mark set) or OFF (no
Legacy Taskbar Representation

is OFF
Apart from the button for the main
window of the Visualization the
task bar also provides buttons for
each window that is opened.
Only the main window Every open window is displayed.
Windows-Flip-3D
is displayed.
(Windows 7 Aero)
Taskbar Thumbnail Only a preview for the A preview for each open window
window
is is displayed.
Preview (Windows main
displayed.
7 Aero)
Show Visu Log: Set the check-mark to display the tab Log (see chapter 6.8.5) in the
functions bar (see chapter 6.8). This feature shows the internal debug logs that are
generated by the A.I.M.O.S. Connector Service for the respective NE.
Geographic Position Format: Use the drop-down menu to select the format in
which the geographic position shall be displayed.
GPS Position Visualization: Select the format for the GPS position display.
Buttons:
Set Default Severity Colors: Click to set the severity colors to the default settings.
NE Configuration Groups: Click to open the NE Configuration Groups window to
set or edit Configuration Group profiles, which is also available via menu Tools
Profiles (for more details see chapter 6.17.3).
Page 60
M0125ANA.DOC
5.3 CONNECTIVITY MANAGER - MODEM MANAGEMENT

The basic idea of the Connectivity Manager is
to define communication resource groups assignable to network elements,

to present the communication resources available on the A.I.M.O.S. server,
to allow parameterization of these resources,
to get an overview of the modems displayed at a glance. The modems are
sorted column by column.
to maintain the connection settings
Please observe that access to this tool can be configured in the Account Manager
rights as explained in chapter 5.4.2.
In A.I.M.O.S. Visualization select Tools / Connectivity Manager.
First of all customize the connection settings with this tool.
Red marked lines/parameters in the connectivity

pages are an indication that there is an inconsistency
between the current connectivity settings of an NE
and the settings of the Connectivity Manager.
Page 61

Modem Info: read only; data are readout from the operating system (OS).
Interface: Communication port of the modem stored in the device manager of the
OS.
Name by OS: The name of the modem stored in the device manager of the OS.
Modem State: Dynamically updated, displays the current state of the modem.
Modem Properties: read only; data are readout from the modem.
Incoming Connection: Yes: modem is configured for incoming connections. No: not
configured for incoming connections. This has to be set in the operating system. See
chapter 13 for more information.
SMS Capable: Yes: modem is SMS capable. No: modem is not SMS capable.
Wireless Modem: Yes: modem is wireless capable. No: modem is not wireless
capable.
Modem Settings: Customize the modem settings.
Name by User: Optional setting. Customize the name of the modem, used as
identification in A.I.M.O.S. As default the OS-internal name of the modem will be
displayed.
Enabled: Set the checkmark to enable the modem for outgoing connections or SMS.
SMS Service Center: Select a profile from the list box. The profiles listed are
configured in Profiles / SMSC Profiles.
SIM PIN: Insert PIN number if necessary for the initialization of the modem.
Init String: Enter the init string if required. Normally the init string is preset and has
not to be entered.
Reset Command: If required, enter a reset command especially for this modem.
Dial Prefix: In case phone number has to be proceeded by a prefix.
Phone Number (Data/Voice): Use this phone number of the modem / SIM card to
transmit data.
Phone Number (SMS): If required enter a phone number for transmitting SMS. If this
value is not set, A.I.M.O.S. will use Phone Number Data/Voice.
Breather Interval: This is the time until a new call can be established after a
previous call (guard time). The default setting is 10 seconds.
Note: Once the SMPP service is enabled (see chapter 5.1.7 SMPP), a new "virtual
modem" named "SMPP-Gateway" will show up in the Connectivity Manager. This
virtual modem can be used in communication groups just as regular modems.
Wireless Status: read only; these settings are only effective for wireless modems.
Data are detected from A.I.M.O.S. and read out from the wireless modem.
Status Age: Date and time of the last status request.
Signal Strength: Signal strength in dBm.
Network Provider: Displays the network provider.
Other Info: read only.
Manufacturer: Read out from the modem, manufacturer of the modem.
Software Version: Read out from the modem. SW version of the modem.
Dial Up Network Name: Read out from OS. Name assigned to the dial-up
connection.
Identification: Identification number of the modem, will be generated automatically
by the OS.
Page 62
M0125ANA.DOC
5.3.1
Discover Modems
Click Discover Modems to discover connected modems. A.I.M.O.S. will start directly
a modem scan and the progress will be displayed in an information window. New
modems connected will be displayed separate columns in the Connectivity Manager.
Discover modem can only be executed when all modems are idle.
5.3.2
Modem Groups
It is required to generate modem groups. Click Modem Groups to generate modem

groups.
Note: Each SMS modem can operate in CS or SMS mode whether it is assigned
to a modem group or not. Due to performance issues it is recommended to use
separate modem(s) for CS respective SMS mode.
Modem Groups: Select for each modem group which modem(s) should be included.
Name: Assign a name to the modem group.
Comment: Additional information.
Modem Usage:
None: not included in a modem group
CS: Circuit switched mode
SMS: SMS mode
Page 63
5.3.3
Profiles
Click Profiles to facilitate the configuration of connectivity settings by generating

profiles. Each profile contains specific data.
Note: In each profile but SMSC profile specific data can be substituted by <?>.
This is helpful if NE-specific access data are required. Click the button
Query to insert the substitute <?>. This will cause the query of this
parameter on the Connectivity Page of the NE when editing the
connection data.
Each profile window provides the following buttons to create new or delete existing
profiles and to undo or save the settings made.
The following profiles, which are also accessible via the menu Tools Profiles (see
chapter 6.17), can be generated:
5.3.3.1
RAS-in Profiles
Incoming remote access profiles have to be configured for the incoming connections
from the NEs to A.I.M.O.S.
Name: Assign a name to the RAS-in profile.

Phone number: Insert the phone number of the modem that is enabled for incoming
connections (see chapter 5.3 Connectivity Manager - Modem Management).
Username: Insert the username to get access to A.I.M.O.S.
Password: Insert the password to get access to A.I.M.O.S.
Page 64
M0125ANA.DOC
5.3.3.2
Network Element Circuit Switched Profiles
Network Element Circuit Switched Profiles have to be configured to establish

connections from A.I.M.O.S. to the NEs.
Name: Assign a name to the NE profile, e.g. the assigned NE type.
Username: Insert the PPP username to get access to the NE.
Password: Insert the PPP password to get access to the NE.
5.3.3.3
Network Element Packet Switched Profiles
Configure the Network Element Packet Switched Profiles for the connection modes
'packet switched always on' or 'packet switched on demand' used in NEs.
Name: Assign a name to the PS profile.
Network Initialization String: Enter the additional init string if required.
Network Access Number: Enter phone number of packed data network.
Authentication User Name: Enter username for packet data connections.
Authentication Password: Enter password for packet data connections.
5.3.3.4
SMS Service Center Profiles
With the SMS Service Center Profiles an SMS service center number will be
assigned to modems in A.I.M.O.S. / NE.
SMS Service Center Number: Insert the phone number of the service center.
Name: Assign a name to the SMS profile.
Page 65
5.3.3.5
These profiles serve to set specific login credentials for an NE. They are assigned to
an NE via the Configuration / Connectivity tab of the functions bar (see chapter 6.9).
The default Network Element WEB Login Profiles (one per NE type) are factory-set
before delivery. These are:
- ION-M Default
- ION-B Default
- Node M Default
- AMR Default
- Node C Default
- MCPA Default
- Node G Default
- MRx18 Default
- Node A Default
They will be used if the option <use defaults> is set as WEB-Login Configuration on
the Connectivity page of the NE (see section 6.9.5.2)
Parameters can be changed if desired or new profiles can be created:
Name: Assigned name of the profile.
Username: Username to login to the according NE.*
Password: Password to login to the according NE.*
* For the default usernames and passwords refer to the Users Manual of the according NE.
Login button of the Web tab:

IF EITHER
the option <use defaults> is set as WEB-Login Configuration on the Connectivity
page of the NE (see section 6.9.5.2),
OR
the WEB-Login Configuration on the Connectivity Page of an NE (see section
6.9.5.2) is NOT set to <empty> (i.e. WEB Login credentials have been explicitly set
for this NE),
the Web tab of the Configuration page of the functions bar (see Web part in chapter
6.8.2) will display a Login button by which username and password will be entered
automatically into the Login dialogue.
In order to prevent such a possibility (either for all NEs or only for certain NE types),
delete the corresponding default WEB Login Profile(s). As a result the option <use
defaults> will no longer be available on the Connectivity Page, and instead the option
<empty> is provided for this NE. The option <empty> indicates that no WEB Login
Configuration is present / selected, and consequently, no Login button will be
available on the WEB tab of the Visualization.
Page 66
M0125ANA.DOC
5.4 ACCOUNT MANAGER - USER MANAGEMENT

The user management is configured and edited in the Account menu of A.I.M.O.S.
A.I.M.O.S.Visualization.
In
A.I.M.O.S.
StartAll
ProgramsAndrew
Visualization select Tools / Account Manager.
A right-mouse-click on a user name opens a contextmenu for editing the user settings (items depending on
user rights / roles; see chapters 5.4.2 & 5.4.3).
When Login using this User is chosen, the system will
log out of the current Visualization session and open
the login screen for the selected user.
When changing a password using this menu (Change
Password) please observe the obligatory Security
restrictions explained in chapter 5.1.3. If the new
password is not accepted, the reason is indicated in
the status bar of the dialogue:
A password may be rejected for the following reasons (for information regarding the
password requirements see chapter 5.1.3):
Too Short
Password is smaller than required minimum password length.
Too Simple
Password does not fulfill some basic requirements (e. g. "123456789").
Invalid
Password contains invalid signs or does not fulfill the configured PW standard.
Mismatch
Password has already been used within the Password History setting.
Please note: A possible temporary lockout will be reset by a password change.
If LDAP is enabled (chapter 5.1.3.3), passwords cannot be changed.
Page 67

Regarding user management in the Account Manager please also observe the
following:
If LDAP (see chapter 5.1.3.3) is enabled and functioning, users can neither be
created nor deleted. Role assignment changes are also not possible. In this case,
these functions are taken over by the Windows Server specified in the Server
Configuration / Configuration Tool.
The "Initial Password Durability" as specified in chapter 5.1.3 does not apply to the
pre-defined user "Admin", which is available after the first installation.
Deleting the pre-defined user "Admin" or the pre-defined "Administrator Role" is not
possible.
Name, assigned role, and owner of the pre-defined user "Admin" cannot be
changed. Furthermore, it is not possible to deactivate this user via the "Account
Manager".
Please note: The day displayed in the Most Recent Use column is the date when
the Visu was used the last time. This information is used by the Maximum User
Account Inactivity feature (of the Security page in the Server Configuration /
Configuration Tool) by which an account can be deactivated after a certain
(definable) period of inactivity (for details see chapter 5.1.3.2).
Example:
The user 'John Doe' in this scenario has not been logged in since the 20th October
2010 and correspondingly his account was automatically deactivated:
In order to reactivate such an account, set the check mark for 'User Active' in the
Edit User window (see also section 5.4.4) and it will be Enabled again:
Page 68
M0125ANA.DOC
5.4.1
Organizations
In the Account menu choose Organizations, or click the button Organizations to

get the context menu.
Add organizations by clicking the Add button.
Select
Country
and
Organization from the list.
Edit the organization settings if necessary:

MCC, MNC, Organization
Code (MCNC), Company
Kind, Company Name,
and
Company
Short
Name are pre-defined and
cannot be changed.
Company Text: Enter
additional information (free
text).
The following values are

valid for the SNMP Alarm
Forwarding only.
Please see chapter 5.5
Northbound
Manager
(Option) - Trap Forwarding
to NMS for additional
information.
Page 69

Language: Select the preferred language to be used for A.I.M.O.S. alarm messages.
Time Format: Select the time format to be used, either the Local Time of the
database server or UTC (Coordinated Universal Time).
Alarm Forwarding: Select the alarm forwarding format, either None (no formatting),
SNMP V1 or SNMP V2C.
Active Workshift: Select the Active Workshift.
Auto Recognition Severities: Use to select severities for which no manual
recognition is required. Alarms with severity levels that are selected in this field will
be recognized automatically.
RDN Separator: Enter the RDN Separator. Default is equal '='.
RDN Concatenator: Enter the RDN Concatenator. Default is comma ','.
CC Concatenator: Enter the CC Concatenator. Default is comma ','.
RDN Translation: Enter the RDN Translation (Replace strings in alarm messages).
Manage Params in Alarm List / History: Set the check-mark to activate the display
of these parameters in the alarm list: Param Count, Param 1, Param 2, Param 1
Value, Param 2 Value, Param 1 Unit 1 and Param 2 Unit . To avoid a performance
decrease of the database the detection and transmission of these parameters is
disabled by default. The columns will be blank in the alarm list / history. Note: This
feature will be initialized after a restart of the A.I.M.O.S. visualization.
Alarm History Initial Size Limit: The alarm history display size (i.e. the number of
alarms displayed) is limited to this setting to avoid performance decrease of the
Visualization. The default value is 5000. Set the value in intervals of 500. Set the
value 0 to get all alarms listed. Note: This feature will be initialized after a restart of
the A.I.M.O.S. visualization.
Legacy Trap Info in SNMP Traps: (currently no longer provided in this tool)
Setting up to SW V2.2:
AlarmTraps contain 4 Trap Info fields:
- aimosCustomerMasterInfo:
contains Trap Info of all NEs, apart from optical
systems: For those the Trap Info of the Master Controllers will be displayed.
- aimosCustomerRemotInfo:
contains Trap Info of Remote Units
- aimosCustomerSubRackInfo: contains Trap Info of SubRacks
- aimosCustomerCableInfo:
is not implemented.
From SW V2.3 onwards:
Trap Info will be forwarded always to aimosCustomerMasterInfo, the other 3 Trap
Info fields leave blank.
Click the check-mark to get the previous practice. Note that this will decrease the
performance of the database.
aimosAlarmLogTable Limit (A.I.M.O.S.MIB): The alarm log table size is limited to
this setting to avoid performance decrease of the database. Default value is 1000.
The last 1000 alarms of the alarm history are displayed. Set the value 0 to get all
alarms listed.
Page 70
M0125ANA.DOC
5.4.2
Account Manager Rights
In A.I.M.O.S. Visualization select Tools / Account Manager.

In the Account menu choose from the context menu Roles.
Click Roles to get the context menu Roles Overview (displayed to the right) or use
the buttons.
All roles are displayed. Access rights (read and/or write access rights) can be
maintained easily by using roles.
Please note: No user can change his own rights. To revoke rights e.g. from predefined administrator role, please create a new role with "Account Management"
rights and log in with a user attached to this role.
Click Insert to add a role.
Page 71
Enter the name of

the role
and
check
the
checkbox behind
the respective right
to grant the access
right
(Read
or
Write) for the role.
Carry out a re-login
for the changes to
take effect.
The first set of

rights in the list are
for the use of
A.I.M.O.S..
Rights preceded by
"OMC3-"
are
OMC3 rights (for
the use of an
integrated OMC3).
The OMC3 Adapter
has to be installed.
For
a
detailed
explanation of the
OMC3 rights refer
to
manual
M0042AJA,
chapter 11.9.
With
no
OMC
installed, only the
rights
for
A.I.M.O.S. will be
displayed.
The following tables show the actions, tools, menus, or tabs that will be affected by
the according (A.I.M.O.S.) right
Note: The common features Tree, Help, and Info are available irrespective of any
right.
Page 72
M0125ANA.DOC
Only if the according Read and Write rights in the following table are granted, the
corresponding features listed are available without any restriction:
Read & Write Available feature
Tool Account Manager
Account
Import new Organizations
Management
NE Owner Profiles
Alarm Clear
Manual Clear
Accessible via
Menu Tools
Menu File
Tool Profiles
Right mouse click on
alarm,
or
Menu
Extras, or Supervision
Alarm Delete Manual Delete
tab (> Alarm History)
Configuration tab
Functions bar
Get GPS Position
GPS Position button /
Show updated GPS Position
NE Operation
NE Configuration Group Profiles Tool Profiles
Tool Profiles
Set Time
Reboot
Send Service Center Number *
Network
Element
Send Configuration *
Operation
Set Factory Default *
Finish Installation
Configuration
Read Unique System
Tool Preferences Editor 1)
Menu Tools
Check Detected Channels 2)
HW/RF tab:
Cell Allocation
Uncheck All 2)
2)
Check Unused Channels
Check Sequence of Channels 2)
HW/RF tab:
2)
Mobile Allocation
Uncheck Sequ. of Channels
Uncheck All 2)
NSOG Filter New 3)
Functions bar
NSOU Filter New 3)
Rename (of a component name) Menu Tree or 4)
Tool Connectivity Manager
Menu Tools
SMS Center Profiles
Connectivity A.I.M.O.S. RAS-in Profiles
Management NE Circuit Switched Profiles
Menu Tools > Profiles
NE Packet Switched Profiles
Log
Management
Tool Log Manager / Log Files /

Log Profiles / Clear /
Log Options
Maintenance
Maintenance tab / Change

Description / Delete
Restore
*
1)
2)
Chapter
5.4
6.2.1
6.17.2
6.2.5
6.8.1
6.8.1.1
6.8.2
6.17.3
6.17.6
6.7
5.2
6.8.2
6.8.2
6.2.3
5.3
6.17.1
Menu Tools
Tool Log Manager
6.13
Functions bar
6.8.3
NE Operation
6.7
SMS-connected NE only
Restrictions to certain sections / features possible depending on other rights see other entries in
table(s);
3)
4)
Node G only
ION only
right-mouse click in NE Tree
Page 73
Read & Write Available feature

Tool Map
Assign Map to Folder
Map
Delete Map from Folder
Remove from Map
Northbound
Tool Northbound Manager
Management
Performance Tool Performance Manager
Manager
Alarm Profiles
Reporting
Export Profiles
Scheduler
Tool Scheduler
Recognize
Recognize all
Supervision
Alarms
Import new Alarms
New
Rename (of a folder)
Topology
Move
Delete
Drag & drop an NE to Map
Watchdog
Tool Watchdog
Accessible via
Menu Tools
Chapter
6.14
Menu Tree
6.2.3
Menu Tools
5.5
Menu Tools
Tool Profiles
Tool Profiles
Menu Tools
6.16
6.17.4
6.17.5
6.10
Menu Extras or
Functions bar > tab
Supervision
6.2.5
6.8.1
Menu Tree or right6.2.3

mouse click in NE Tree
6.14
6.15
Menu Tools
Additionally, all of the unrestricted features in the following tables are available as
well.
If the according Read rights in the following table are granted, the corresponding
features listed are available generally on a read-only basis; features that are
available without restriction are marked 1):
Read
Account
Management
Available feature
Tool Account Manager
NE Owner Profiles
Configuration tab with all
subordinate tabs, except Web tab
GPS Position button
NE Configuration Group Profiles
Insert / Edit / Delete
Get Time 1)
Query All 1)
Export NE Data to 1)
1)
Configuration XML-Import File
NE Configur. Group Profiles 1)
Try Connection 1)
Read Network Structure 1)
Read HID 1)
Accessible via
Menu Tools
Tool Profiles
Chapter
5.4
6.17.2
Functions bar
6.8.2
Tool Profiles
Notes tab
6.17.3
6.8.4
Network
Element
Operation
6.7
Menu View
Menu Tools
6.2.4
5.2
Get Service Center Number 1)

( SMS-connected NE only)
Nokia Specific Problem 1)

Tool Preferences Editor
Page 74
M0125ANA.DOC
Read
Available feature
Tool Connectivity Manager
Connectivity
section
of
tool
Preferences Editor
SMS Center Profiles
A.I.M.O.S. RAS-in Profiles
NE Circuit Switched Profiles
NE Packet Switched Profiles
Tool Job Monitor 1)
Tool Log Manager
Show Visu Log entry in tool P.E. 1)
Log tab 1)
Logging Enabled 1)
Maintenance tab
Backup 1)
Export to file 1)
Tool Map
Locate in Map 1)
Show Map 1)
Accessible via
Menu Tools
Chapt.
5.3
Menu Tools
5.2
Network
Element List
Northbound
Management
Performance
Manager
Reporting
Excel Export button 1)
Scheduler
Tool Scheduler
Scheduler section of tool P.Editor 1)
Connectivity
Management
Job Monitor
Log
Management
Maintenance
Map
Menu
Tools
Profiles
>
6.17.1
Menu Tools
Menu Tools
Tool Pref. Editor
Functions bar
Menu Tree
Functions bar
NEO / Button
Menu File
Menu Tools
6.12
6.13
5.2
6.8.5
6.2.3
6.8.3
6.7
6.2.1
6.14
Menu Tree
6.2.3
Tool Network Element List 1)
Menu Tools
6.11
Tool Northbound Manager
Menu Tools
5.5
Tool Performance Manager

Alarm Profiles
Menu Tools
Tool Profiles
Supervision tab
Maintenance tab
Log tab
HID / Inventory Data
Alarm History
Notes tab
Tool Pref. Editor
Menu Tools
Tool Pref. Editor
Supervision tab
Alarm Settings
6.16
6.17.4
6.8.1
6.8.3
6.8.5
6.8.3
6.8.1.1
Display of Alarms
1)
Auditory Alarm Notifications 1)

Query Alarms
1)
Menu Extras
NEO
Supervision tab
Menu ?
Menu View
Menu View
6.8.4
6.10
5.2
6.8.1
6.8.2
6.2.5
5.10
6.7
6.8.1.2
6.2.7
Supervision
Alarm Help 1)
Topology
Standard View 1)
NSO View 1)
6.2.4
Severity Icons / Alarm Settings /
Alarm Representation
Preferences Editor
5.2
(sections of tool Pref. Editor) 1)
Read right alone w/o effect; Write right required; see previous table
Additionally, all features granted without any right (next table) are available as well.
Page 75

Even if none of the rights are granted, some features are nevertheless available on
a read-only basis. However, none of the actions / tools in the previous tables will be
available.
Available feature
Accessible via
Chapter
General tab of Configuration tab
Functions bar
6.8.2
Notes tab (except functions Insert, Edit, Delete)
Functions bar
6.8.4
Note: The common features Tree, Help, and Info are available irrespective of any
right.
5.4.3
Account Manager Roles
Roles can be assigned to users in the 'Edit User' menu of the Account Manager.
A role is a profile with defined access rights. By default three roles are pre-defined:
5.4.3.1
The Administrator Role
The administrator role is a pre-defined profile. These users have full read and write
access rights to the database. Only users with the "Administrator Role" assigned are
allowed to start the Sever Configuration (see chapter 5.1).
5.4.3.2
The Standard User Role
The standard user is a pre-defined user with read rights and the rights to control the
alarm system and the device parameters.
5.4.3.3
The Read Only User Role
The read only user is a predefined user with read access rights only.
Page 76
M0125ANA.DOC
5.4.4
Account Manager Users
A.I.M.O.S. is delivered with a

pre-installed user account
"Admin". After the login to
A.I.M.O.S., user accounts for
A.I.M.O.S. can be created,
edited or deleted.
In A.I.M.O.S. Visualization
select Tools / Account
Manager.
Start the Account Manager
and select Account - Insert
user or the button Insert.
Enter the data for the new
user.
Please observe that the user
name does not distinguish
between small and capital
letters, i.e. "admin" equals
"AdMin", etc.
Set an 'Expiry Date' to limit
the validity of an account up
to a certain date: in this
example the user 'Contractor'
will no longer be able to login
from 1st January 2014
owards. Reactivating such
an account is possible by
deleting or extending the
'Expiry Date', and by setting
the User Active check mark.
For a description of the SNMPv3-specific fields (as listed in section 5.1.4.9) refer to
the AIMOS SNMPv3 Configuration Guide provided for customers using this feature
(location see section 2.5.5).
Page 77

Select the Organization. Only activated organizations can be selected. To activate
other organizations click Other....
Select the organization from the list and confirm the selection.
Check the Enabled box (default:
checked). If the 'Enabled' box for the
user is unchecked, the user has no
access to the database. With this box a
user can temporarily be granted access
to / excluded from the database.
Note: Please observe that this option
can also be used to enable
permanently locked user accounts.
Enter the User Name of the new user account. Using very short names is not
recommended, since this will make it harder to find a valid password due to the strict
security rules for A.I.M.O.S. (see chapter 5.1.3.1).
Enter the User Text: Enter comments.
Select the Assigned Role or click New... to create a new role.
Select the Assigned Folder to restrict the access for the user to the selected folder.
Leave folder [Root] to give access to all maintained NEs.
Select Assigned NE Owner to assign a certain NE Owner Profile (see chapter 5.4.5)
to the user. Then, the user will only see NEs assigned to this specific profile.
Enter additional information for the new user:
Phone Number: Enter the phone number of the user.
eMail Alarm Forwarding: If the user is supposed to receive alarm messages via
eMail, check the 'Enabled' box and make a selection in the next field.
eMail Alarm Severities: Only alarms of the selected severity levels from the list
provided will be sent out. With the setting None selected no alarms will be sent.
eMail: Enter the eMail address of the user to where the alarms should be sent.
SMS Alarm Forwarding: If the user is supposed to receive alarm messages via
SMS, check the 'Enabled' box and make a selection in the next fields.
SMS Modem Group: Choose the modem (type) to be used for alarm forwarding.
Observe that no alarms can be sent out if this selection is not made (setting empty).
SMS Alarm Severities: Only alarms of the selected severity levels from the list
provided will be sent out. With the setting None selected no alarms will be sent.
SMS: Enter the SMS account number of the user to where the alarms should be
sent.
The initial password 'start' is assigned to the new user account and has to be
changed by the user after the first login.
Page 78
M0125ANA.DOC
5.4.5
NE Owner
To each NE an individual NE Owner can be assigned. Alarms of individual NEs can

be sent to different specified destinations via the SNMP Northbound Interface using
the 'NE Owner' setting.
All organizations specified for the according country in A.I.M.O.S. by default can be
selected as 'NE Owner' via Identification in the Configuration / General tab (see
also chapter 6.8.2).
To view the 'NE Owner Profiles' or to create a new 'NE Owner', click the NE Owner
button in the Account Manager. This profile is also accessible via the menu Tools
Profiles. (see chapter 6.17). When the button New is clicked a new column will be
added at the end of the table to enter the data for the new NE Owner:
These settings must be saved and then the new 'NE Owner' can also be selected in
the Configuration / General tab (see chapter 6.8.2).
In Tools/Northbound Manager specify to which destination (IP address) the alarms of
an individual NE (or NE owner) should be sent (see chapter 5.5.3).
5.4.6
Import / Export
For the user "admin", the Account menu of the

Account Manager also provides the features
Export and Import.
Export: Use to export all roles and users in an
"Account Configuration Data File". This is an
A.I.M.O.S.-specific file format ending on "acd",
which cannot be changed.
Please note:
Neither the settings in "Organizations" and
"NE Owner" nor passwords will be exported.
An export made with SW V2.6.1 or older
cannot be imported into SW V2.7 or later
versions.
This feature is not connected to the Export
button (for Excel exports of user data)
described in the next chapter.
Import: Use to import all roles and users from an "Account Configuration Data File".
Please note:If a role or user with the same name as an already existing one is
imported, possible settings that were already made for this user or role will be
overwritten.
Users added in this way must be enabled manually after the import is complete.
Page 79

Since passwords are not imported, the initial password "start" is required again for
the first login, which should be done within the period set for the Initial Password
Durability in the Server Configuration / Configuration Tool (see chapter 5.1.3.1
Password Settings).
No users or roles will be deleted by the import procedure.
An import is not organization-specific.
The user "admin" will not be deactivated or changed by an import.
5.4.7
Excel Export
Use the (Excel-)Export button of the Account Manger in order to save all user data
as an Excel file. This button can be made available to all users and is not connected
to the Export feature of the Account menu described in the previous chapter.
Page 80
M0125ANA.DOC
5.5 NORTHBOUND MANAGER (OPTION) - TRAP FORWARDING TO NMS

The Northbound SNMP Manager offers the possibility of setting the addresses of the
Network Management Systems (NMS) which are to receive SNMP Alarm Traps.
Access to this tool can be configured in the Account Manager rights as explained in
chapter 5.4.2.
In A.I.M.O.S. Visualization select Tools / Northbound Manager.
If the mask is started for the first time, it looks as follows:
The page is divided in two parts:

- SNMP Manager see section 5.5.1
- Workshift see section 5.5.2
5.5.1
SNMP Manager
Menu / Buttons
Insert a new SNMP Manager.
Edit the selected SNMP Manager ( see section 5.5.3)
Delete the selected SNMP Manager.
Test-Trap
Send a Test-Trap to test the connection to the SNMP Managers.
Columns: Double-clicking on a field will open the Edit SNMP Manager window for
the selected SNMP Manger.
ID
This column contains an internal unique identifier of each SNMP Manager. Its values
are set by the program.
IP Address
This column holds the IP Address of the SNMP Managers which is to receive SNMP
Alarm Traps. If the SNMP Manager does not expect to receive SNMP Traps at the
'Default Port for Outgoing SNMP Traps' specified by the A.I.M.O.S. Configuration
Tool (see chapters 5.1 & 5.1.4.2), another specific IP port number may be specified
by appending a colon and the IP port number (e.g. 192.168.0.1:164).
Page 81

Name
This column provides the possibility to specify a name for the SNMP Manager entry
helping to disclose its identity. This name should be unique. If you left the name
empty, A.I.M.O.S. tries to discover the IP Addresses DNS name. This may take up to
a few seconds. If this fails, the IP Address itself will be used as name, too.
Interface Type
In this column define the kind of alarm forwarding. Keep the set default value unless
you want to force the SNMP Agent to use an older type of alarm forwarding for
compatibility reasons or if your SNMP Manager requires the traps to be in the format
specified by the Nokia Enhanced SNMP Solution Suite (NE3S).
The alarms sent away are always SNMPv2 notifications.
A.I.M.O.S. alarm forwarding as defined by the A.I.M.O.S.-MIB. The decision made by
means of the setting 'Alarm Forwarding' within the Account Manager determines
whether an alarm is sent away as SNMPv1 trap or as SNMPv2 notification.
The meanings of the values are:
MIBDefault currently the same as A.I.M.O.S.
OMC3Default alarm forwarding as used in OMC V3.54 with the standard

interface. The alarms sent away are always SNMPv1 traps.
OMC3Nokia alarm forwarding as used in OMC V3.54 with the Nokia interface.
The alarms sent away are always SNMPv1 traps.
NE3S alarm forwarding as defined in the Nokia Enhanced SNMP Solution Suite
(NE3S). The decision made by means of the setting 'Alarm Forwarding' within
the Account Manager determines whether an alarm is sent away as SNMPv1
trap or as SNMPv2 notification.
A.I.M.O.S. Obsolete should not be used unless otherwise notified.
GPS Position Format

Choose the trap format for the GPS position information from the list provided in the
Edit SNMP Manager window.
Page 82
M0125ANA.DOC
Time Display Format
This column is used in order to indicate of how date and time values are encoded
and transmitted by the A.I.M.O.S. SNMP Agent in traps/notifications. The MIB
SNMPv2-TC defines the textual convention DateAndTime, which serves as basis for
the formats offered in A.I.M.O.S.
It is defined as follows: A date-time specification.
Field
1
2
3
4
5
6
7
8
9
10
Octets
1-2
3
4
5
6
7
8
9
10
11
Contents
year
month
day
hour
minutes
seconds; (use 60 for leap-second)
deci-seconds
direction from UTC
hours from UTC
minutes from UTC
Range
0..65536
1..12
1..31
0..23
0..59
0..60
0..9
'+' / '-'
0..11
0..59
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0.
If only local time is known, time zone information (fields 8-10) is not present.
In general, A.I.M.O.S. provides three date and time formats:
1. SNMP:
This format uses the Textual Convention DateAndTime mentioned above.
2. OSI:
This format is identical to the previous one except
- the deci-seconds are omitted and
- if no time zone information is present (i.e. the UTC Time Format is used),
the direction from UTC contains the character 'Z' and the subsequent values are not
used.
3. Windows:
Date and time values are formatted as defined in the windows country settings.
The short date format and the long time format, separated by a blank, is used.
Both, the OSI and the SNMP Format, may be transmitted in three ways:
1. Binary
The values are encoded as defined in the MIB. Thus, the year needs two octets
(bytes), the month one... This format requires the smallest amount of memory.
2. Text
If a SNMP Management System has difficulties to decode the date and time values,
we offer an ASCII format. Each digit will use one octet (byte).
3. Formatted
This format is the same like text appended by formatting characters like minus,
comma and colon.
Page 83

ACK Capability
This column is provided in order to state the SNMP Managers ability to perform an
acknowledgement.
If this column is checked, the SNMP Agent expects an acknowledgement for each
trap sent out. Each trap will be periodically re-sent until acknowledgement is
detected.
By default, ACK Capability is unchecked and cannot be checked by a user due to
the high risk of misconfiguration. In case the SNMP manager is not available or not
configured correctly, a strong A.I.M.O.S. overall performance degradation could be
the result when each alarm trap is re-sent periodically.
Furthermore, the acknowledgement of each alarm trap is, generally, not a vital
feature as the A.I.M.O.S. SNMP agent and SNMP manager are usually within the
same LAN with very limited risk of lost traps. In cases where the ACK Capability is
indeed required, it is possible to activate it via a WIN registry key. Please contact
WISupport@commscope.com.
Recognize Trap
The A.I.M.O.S. SNMP Agent may run in one of four predefined modes. This can be
setup by means of the A.I.M.O.S. Configuration Tool.
In case the SNMP Agent operates either in
A.I.M.O.S. Default Mode (MIB supported by the Agent is set to AIMOS Default)
or in
NE3S Mode (MIB supported by the Agent is set to Nokia Enhanced SNMP
Solution Suite)
the Trap on Recognition feature is supported.
In that case you may check or uncheck the option Recognize Trap. If checked,
each recognition of an alarm forces the SNMP Agent to raise a particular trap
(A.I.M.O.S.-MIB: aimosAlarmRecognized / NE3S: noiAlarmAckStateChanged).
Enabled
If this column is not checked, this SNMP Manager will be excluded from Alarm
Distribution.
Page 84
M0125ANA.DOC
5.5.2
Workshift Assignment
A.I.M.O.S. is shipped with one default workshift. If you want to use the workshift
facility, you should add at least one additional workshift.
This will be done by selecting Workshift Insert
from the menu. In the following window you have
to assign a name. If you want to have the
heartbeat feature enabled, you have to specify the
interval in minutes here.
Insert a new Workshift.
Activate a Workshift.
Edit the selected Workshift.
Delete the selected Workshift.
After that you may want to change the name of the default workshift (Menu Workshift,
Edit, Default Workshift) and the heartbeat interval as well.
Please note: An active workshift cannot be deleted.
In order to specify the recipient of traps in dependence of the time, proceed as
follows:
In the Northbound Manager, select

the Default Workshift by a rightmouse click on the field highlighted
in blue and select Create
Activation Script Files from the
context menu:
Page 85
Select the desired directory,

(recommended is AIMOS), and
click OK to create the activation
files for all workshifts.
This is confirmed by the following message:
To activate a workshift, configure the Windows Scheduler to execute the

corresponding activation file. Observe that for each workshift a separate activation
has to be executed in the Windows Scheduler.
5.5.3
NE Owner
Use
the
Edit
button to specify to
which destination
(IP address) the
alarms
of
an
individual NE or
NE Owner should
be sent (for more
information on NE
Owners
see
chapter 5.4.5).
For a description of the SNMPv3-specific fields (as listed in section 5.1.4.9) which are
not shown in the screen shot above refer to the AIMOS SNMPv3 Configuration
Guide provided for customers using this feature (location see section 2.5.5).
Page 86
M0125ANA.DOC
5.6 ALARM POLLING

Use the alarm polling as an additional diagnostic feature. While alarm polling is
activated, A.I.M.O.S. contacts the designated NEs and reads out the alarms of the
NEs.
Note: - Currently alarm polling is only supported for NEs that are connected
via LAN or a packet switched always on network.
- Once the Scheduler tool is licensed, alarm polling is available in the
Scheduler only. For details about alarm polling in the Scheduler please
see chapter 6.10 Tool Scheduler (Option).
This chapter describes how individual NEs are included into Alarm Polling. Please
observe that the Alarm Polling settings can be customized in the Preferences Editor
as described in chapter 5.2.
Step 1: Select the NE which shall be included in the alarm polling in the NE Tree.
In the example below a Node A is selected.
Step 2: Select Configuration / General.
Step 3: In the Settings section set the check-mark for Include in Alarm Polling
to configure alarm polling for this NE:
(The parameter Alarming Enabled is not relevant for Alarm Polling; for details about this
parameter see chapter 6.2.3 Tree.)
Step 4: Repeat Steps 2 to 4 for each NE to be scheduled for alarm polling.
Step 5: To activate Alarm Polling either move to OMC level and set the check
mark for 'Alarm Polling Active' or activate it in the Preferences Editor
where the settings can additionally be customized (see chapter 5.2).
Note: On NE level, the parameter 'Alarm Polling Active' cannot be changed. It
shows whether alarm polling has already been activated. If it is not yet tagged,
activate Alarm Polling on OMC level or in the Preferences Editor. Either way
Alarm Polling activation is effective for all NEs scheduled for alarm polling.
Alarm polling is not activated
Alarm polling is activated
Page 87
5.7 INTEGRATION OF OMC 3.54

Please observe that OMC 3.54 has to prepared (before A.I.M.O.S. is installed) as
explained in chapter 4.1.1 Preparation of OMC 3.54 for the Combined Installation
with A.I.M.O.S..
The integration of an Andrew OMC 3.54 is optional and required with repeaters of the
1st and 2nd generation.
Note: For the connection to the OMC 3.54 the optional OMC3 Adapter has to be
installed (see chapter 4.2 A.I.M.O.S. Setup).
From that point every alarm of a 1st & 2nd generation repeater is automatically
forwarded via the OMC3 Adapter.
An Andrew OMC 3.54 can be created in each folder.
In A.I.M.O.S. Visualization select the OMC entry in the NE Tree with a right-mouse
click and choose New -> Add OMC 3.54.
The Andrew OMC 3.54 has to be installed at the same PC where A.I.M.O.S. is
installed, the IP-Address is 127.0.0.1 (Local host), the port is 7421.
Click the Save button to save the entry in the A.I.M.O.S. database and button 'Try
connection' for test purpose. Click Next.
Click Get to import the unique identifier for the OMC 3.54. Click Next.
Click Get to import the complete topology maintained by the Andrew OMC 3.54. Click
Close to finish the wizard.
The optional OMC3 Adapter service integrates an OMC 3.54 for 1st and 2nd
generation repeaters into A.I.M.O.S. The customization for this tool has to be made
within the 'Server Configuration' tool (Start - Programs - Andrew A.I.M.O.S. - Server
Configuration). For details see chapter 5.1.5 and the online help of the A.I.M.O.S.
Server Configuration / Configuration Tool (chapter 5.1).
5.8 DATABASE EXPORT / ODBC

With an installed ODBC driver data queries from the A.I.M.O.S. database can be
made via Excel.
The installation and use of the ODBC Export is described in a separate manual,
contained in the Manual folder of the A.I.M.O.S. Installation CD-ROM.
Page 88
M0125ANA.DOC
5.9 AUTOMATIC BACKUP

A script-based automatic backup/restore of the A.I.M.O.S. database (as described in
chapters 7.1 and 7.2) can be installed with the Windows task scheduler:
The installation and use of the automatic backup feature is described in a separate
manual (M0125B6), which is contained in the 'Manual' folder of the A.I.M.O.S.
Installation CD-ROM.
5.10
AUDITORY ALARM NOTIFICATIONS
This feature is accessible in the

A.I.M.O.S. Visualization via menu Extras
(see chapter 6.2.5).
It can be used to assign individual
sounds depending on the respective
severity level to the alarm notifications.
Page 89

For your notes:
Page 90
M0125ANA.DOC
6 A.I.M.O.S. - Operations
6 A.I.M.O.S. - OPERATIONS
6.1 NE MANAGEMENT - OVERVIEW
In the main program window the complete functionality of A.I.M.O.S. is available at

one mouse-click. Each single function is arranged in a functionality-structured group.
The NE Tree gives a complete and detail-adjustable overview of all NEs contained in
the maintained network.
The NE-specific functions are logically structured underneath unique tabs.
All information for single NEs or for the complete system hierarchy is given in the
Management Interface. Possible changes of settings are highlighted and can be
recognized at a glance.
Menu Bar
With the menus in the menu bar the main functionality of the program can be
customized.
NE Tree
The NE Tree displays the structure and the NEs of the supervised network. With the
NE Tree the selection of the managed network level and NE is made.
Page 91

Functions
The Functions bar offers the selection of the respective functionality available for
each NE selected with the NE Tree.
Management Interface
The Management Interface is the Input/Output and information panel for the user.
Status Bar
The Status Bar displays the following information on selections made in the user
interface:
IP address
database
User
name
License
information
Progress Shows
active
or Skin / Selected
bar
inactive CAPS, NUM, appearance
SCROLL, INSERT
Alarm Status
The Alarm Status gives an overview of the alarms of the selected level/network
element.
6.2 MENUS
This chapter provides a short summary of each main menu. The available menu
items / submenus depend on the NE selected in the NE Tree as well as on the tab
selected in the Functions Bar. For the following examples an ION MC with tab
Supervision was selected; if another type of NE or another tab is selected, less menu
items / submenus may be available. This chapter only describes those submenus in
detail which are not explained further in later section of the manual.
The icons to the right of the menu bar provide shortcuts to the submenus of the Tools
menu (see section 6.2.2).
Page 92
M0125ANA.DOC
6.2.1
File
Excel-Export: Depending on the tab selected in the Functions Bar (see chapter 6.8)
the according data can be saved as Excel file. This is also possible via the Excel
Export button of the according tab.
Access can be configured in the Account Manager (chapter 5.4.2).
Export NE Data to XML-Import File: Select to export NE data (of all NEs in
A.I.M.O.S. except OMC3) from the A.I.M.O.S. database into a re-importable xml file.
Please note: It is possible that coded passwords might be exported, as well. Thus,
the generated file should be protected, i.e. it should not be freely available. Although
the actual password text is not exported, the information provided could be used to
create, change, or take over the units.
After entering the desired filename in the Save to XML file window. such a file can
be used for xml file import with the Tool Scheduler (Option); see chapter 6.10.2.
Confirm with OK.
Page 93

Export Node G Frequency to XML-Import File: Select to export Node G frequency
data from the A.I.M.O.S. database into a re-importable xml file. For procedure, see
description of Export NE Data to XML-Import File in the above.
Export to File: Saves an NE backup (generated in A.I.M.O.S.) into a hard disk file,
which can be used for a restore on an ION MC. For this restore, however, the file
must be copied to the ION MC. The restore cannot be done via A.I.M.O.S. directly,
but it is possible to access the ION web page via the Web tab of the A.I.M.O.S.
Configuration page; see chapter 6.8.2. Please also observe that the file generated by
this backup cannot be used for an xml import via the tool Scheduler.
Save As: Use to save a web page as file.
Delete: Deletes an NE backup file (generated in A.I.M.O.S.) from the hard disk.
Update:
Access to this menu can be configured in the Account Manager (chapter 5.4.2).
Choose Import new Organizations to add a supplementary organization via
xml file.
Choose Import new Alarms to update alarm data via xml file, e. g. after the
update of an NE, without having to update A.I.M.O.S. Please observe that after a
successful alarm update all visualizations have to be restarted in order for the
changes to take effect.
Both updates will be confirmed as follows:
processed is the total number of alarms checked

inserted is the number of new alarms
updated" are alarms where the text has changed (alarm text or description)
failed are alarms where a failure occurred during import
Change Login: Choose to login with a new user name.

Exit Application: The current Visualization will be closed.
Page 94
M0125ANA.DOC
6.2.2
Tools
Tool
Preferences Editor
Connectivity Manager
Scheduler (option)
Account Manager
Northbound Manager (option)
Network Element List
Log Manager
Job Monitor
Map (option)
WatchDog
Performance Manager
Profiles
see chapter
5.2
5.3
6.10
5.4
5.5
6.11
6.13
6.12
6.14
6.15
6.16
6.17
The OMC 3 menu, by which the OMC 3 is started, is only available with OMC 3
installed. For details see OMC 3 manual. Please observe that access to the OMC 3
tool can be configured in the Account Manager rights (chapter 5.4.2).
6.2.3
Tree
Note: Access to the actions New, Rename, Move,
and Delete can be configured in the Account Manager
(chapter 6.4.2).
Network Element Operations: For details refer to
chapter 6.7.
New: Depending on the desired action refer to chapter
6.6 Add New Folder, 5.7 Integration of OMC 3.54, or 6.5
Add New Network Element (NE) for a more detailed
description.
Add a Note: A window is

opened where a note for the
NE selected in the NE Tree
can be entered.
This note will be displayed
when tab Notes is selected in
the Functions Bar (see also
chapter 6.8.4 Notes).
Page 95
Rename: Select to enter or

change the Component Name
of the NE selected in the NE
Tree. The current Component
Name will be highlighted and
can be directly typed in.
Move to Root (OMC): Moves the selected NE to the top level folder (OMC).
Move to new Folder: Moves the selected NE to a new folder.
Move: Use to move folders or NEs to another folder, which can also be achieved by
drag and drop. Only permissible transactions will be allowed, otherwise the function
is not available or will not respond.
Delete: The NE selected in the NE
Tree will be deleted after
confirming the following warning
message as instructed (by typing
YES and clicking OK).
Alarming History: Opens the Alarm History window for the selected NE.
Alarming Enabled: If this option is not tagged, alarms sent by the selected NE will
not be visualized by A.I.M.O.S. (i.e. the check-mark should only be removed under
special circumstances, e. g. for tests, maintenance of the NE, etc.). To show that
alarming has been disabled a Stop sign will be displayed beside the respective NE
in the NE Tree (see section 6.3).
Logging Enabled: If this option is tagged, a window logging the current jobs for the
selected NE is displayed. When this NE log window is closed, the check-mark is
removed as well.
Expand / Collapse: Saves the same purpose as clicking + or - in the NE Tree.
Refresh: Although A.I.M.O.S. updates the screen contents automatically, you can
use Refresh/F5 as reinsurance that the screen shows the current status.
Actions relating to Map: The actions Locate in Map, Assign Map to Folder, Show
Map, and Delete Map from Folder are only available when tool Map is licensed (see
chapter 6.14) and the according right was granted in the Account Manager (see
chapter 5.4.2). Depending on the selected unit, different commands are possible. For
details please also see chapter 6.14.
Page 96
M0125ANA.DOC
6.2.4
View
Locate NE: Serves the same purpose as the button
Locate (under tab Supervision; see chapter 6.8.1),
which shows the alarming NE in NE Tree.
Show JobStatus: Shows the current status of the job
in process.
Standard View: = normal view.
NSO View: Special view for NSOG or NSOU.
Alarm Text in Extra Line: If tagged, alarms are displayed in two lines (as shown in
chapter 6.8.1); otherwise all information is displayed in one line:
Alarm History: Opens the Alarm History window for the selected NE.
Specific Problem Values for Nokia: Replaces the numbers by special ones for N.
HID's from Sub-Network Elements: Shows the HIDs of subordinate NEs, as well.
Max. Log Rows to Load: Limits the protocol.
Show All: Select this option to display all available information including the
A.I.M.O.S.-internal data, which are not shown otherwise.
Load Grid Layout:
Save Grid Layout:
Delete Grid Layout:
For grid layouts see chapter

6.4.1.3 Managing Table Filters and
Sort Options.
Filter Builder: See chapter 6.4.2 Using the Filter Builder.

Note: For more details on grid layouts and filters in general see chapter 6.4
Visualization Filters and Sort Options.
Page 97
6.2.5
Extras
Locate NE: The selected NE is highlighted in the NE Tree.

The actions below are also available via the button
Recognize of the Supervision tab (see chapter 6.8.1).
Select All: Use to select all alarms of the NE currently
selected in the NE tree.
Recognize All: All selected alarms are recognized. *
Recognize: Use to recognize alarms individually. *
Manual Clear: Moves selected alarm(s) from the
alarm list into the Alarm History. *
Manual Delete: Permanently deletes selected
alarm(s) from the alarm list and also from the Alarm
History. *
* Access to the actions Recognize, Recognize all, Manual Clear, and Manual Delete can be
configured in the Account Manager (chapter 5.4.2).
Change Description: Use to change the description of an NE backup.

Auditory Alarm Notifications: for more information see chapter 0.
When available (e. g. in the tab Notes), use Insert, Edit, and Delete to insert, edit,
or delete the selected element (e. g. a note).
Change my Password: Use to change your password. For more information on
password setting see chapter 5.4 Account Manager - User Management.
Connector Logs: Opens the Connector Logs Window.
Get Directory retrieves the list of log files available on the
Connector page from the Connector to refresh the list
displayed.
Click Get File to store the selected log data as zip file:
Connector logs should be sent to the Technical Support to

speed up trouble analysis (see also chapter 10.2
Technical Support).
Page 98
M0125ANA.DOC
6.2.6
Window
All applications of A.I.M.O.S. are listed. With one mouse-click the tools can be
brought to the front.
Tool Windows: A list of all Visualization tools that are active in the background is
displayed (in the example above only the tool Network Element List is active). Click
on a tool in the list to access the respective tool window.
Close all Tool Windows: All tool windows from the list shown above will be closed.
6.2.7
Menu ?
Help: Opens the Welcome page of the online help
Alarm Help: Opens the Alarm Help for the selected
alarm.
Suggest a Feature: Users can use this item to suggest
new features for A.I.M.O.S. by sending an according
mail.
Info: Opens the Version

Info window:
When the
button is
clicked, first, the database
version is displayed and,
upon a second click on the
button, the update history
of the database, as well as
the installed data base
patches.
A third click provides further information on the corresponding A.I.M.O.S. version.
Page 99
6.3 NE TREE
The NE Tree is the control interface for the navigation through the complete network
managed by the program.
All properties of the selected component are logically sorted by the Functions and
displayed in the Management Interface.
After the installation, A.I.M.O.S. only contains the OMC database symbol in the NE
Tree. The OMC (database) is the highest level of the hierarchical structure of the
management and maintenance system.
In this level the overall functionality of A.I.M.O.S. is combined. Select the OMC in the
NE Tree. The Functions bar will show the tabs, the MANAGEMENT INTERFACE will
display the fields available at this level of the managed system.
Page 100
M0125ANA.DOC
Note: From SW version V2.9.1 onwards the acronym SRMU (Subrack Master Unit),
i.e. the optical transceiver in an ION-M system, will be replaced by the current
designation MU OTRx (Master Unit Optical Transceiver) in the NE Tree.
Please observe that in other parts of A.I.M.O.S. the former designation SRMU
may still be used.
To create new network elements, new folders or to add OMC3, use the context
menu items 'New...' (right-mouse click) or menu Tree - New....
The levels and components can be (respective chapter of manual in brackets):

New Folder (6.6)
Integration of OMC 3.54 (5.7)
Any New Network Element... (NE) (6.5)
To manage the network elements use the context menu item 'Network Element
Operations' (right-mouse click) or menu Tree - Network.
For more details see chapter 6.7 Network Element Operations
Page 101

Under certain conditions the Symbol column in the NE Tree provides additional
information on the status of the respective NE. The meaning of the symbol can be
verified in the NE Status column:
The following symbols are

available:
Description:
Off Duty *
NE is powered on but 'out of operation area', which means

that no alarms are generated.
Shut Down *
NE is 'out of service'.
Alarming Disabled
If the option Alarming Enabled in the Tree menu (see

section 6.2.3) is not tagged, alarms sent by the selected NE
will not be visualized by A.I.M.O.S. (observe that this status
is only sensible under special circumstances, e. g. for tests,
maintenance of the NE, etc.).
Planned
The NE has been created already but the full information set
from the NE has not been received by the A.I.M.O.S.
database yet.
* These suspended periods are currently only supported for the Node AM (see also Heartbeat
description of Configuration tab, section 6.8.2).
Page 102
M0125ANA.DOC
6.4 VISUALIZATION FILTERS AND SORT OPTIONS

Note: If the Scheduler option is licensed, please observe that filters can also be
customized via this tool. For details refer to chapter 6.10 Tool Scheduler (Option).
The tool Network Element List (see chapter 6.11) also offers a button to use a filtered
Network Element List as filter for the NE Tree.
6.4.1
Table Filters
Each table can be filtered by filter options depending on the type of table (e. g. alarm
list) and the data available. The examples in the following descriptions are taken from
the alarm list (as the most commonly used table); please observe that since the table
filters are context-sensitive available options may differ in other tables.
Note: All filters and sort options are applied on a "per-user" basis.
6.4.1.1
Column Selection and Customizing
Click the icon in the table header to view or select

which columns should be displayed (see figure to the
right). Set or delete the check-mark for each column
to make the selection.
A default selection depending on the type of NE is
already factory-set.
(To be able to determine the position of a column
drag it at the column header to the desired position
and drop it there or use the Field Chooser of the
advanced sort options explained in chapter 6.4.1.2.)
Please observe that for Network Elements with GPS
function Raise-Latitude and Raise-Longitude must
be selected to show the GPS position of an NE at
the time of an alarm since these columns are not
part of the default selection. To also show the
position of the NE when the alarm was cleared,
select Clear-Latitude and Clear-Longitude, as well.
.
.
Each table can be filtered

additionally using the dropdown button provided in some
columns:
With the drop-down button the filter can
be deactivated (All) and a simple filtering
can easily be adjusted (Custom...).
Two filter criteria can be set and logically
combined (Logic AND and logic OR).
Page 103
6.4.1.2
Sort Options and Calculations
Each table can be sorted.

o Click the column headers to sort data by this column
ascending or descending
or
o right-mouse click the column header to get the
advanced sort options illustrated to the right. With those:
the criteria for the sorted display of data can be
adjusted
1)
an easy calculation can be performed
the fields to be displayed can be selected with the
Field Chooser by dragging the columns from the field
chooser to the data table 2)
the rows can be adjusted to fit the displayed data best
1)
When the Footer is selected in the context

menu, initially, only an empty bar is displayed at
the bottom of the window. By a right-mouse click
on it the highlighted footer field can be configured
to perform easy calculations using the data of the
column above. So, each column can be configured
separately. The available calculations depend on
the respective column.
2)
When the Field Chooser is selected, the Customization

window, where the columns are displayed in alphabetical
order, is displayed to add or remove additional columns to /
from the table by drag & drop. Unlike customizing the
columns as explained in chapter 6.4.1.1 the exact position of
a column can be determined with the Field Chooser.
Note: The settings for the sort options and calculations can
be saved via the menu View (see chapter 6.2.4).
6.4.1.3
Managing Table Filters and Sort Options
Use the menu View to save, load and delete customized filter and sort settings for
tables in a grid layout.
Load Grid Layout: Use to load a
(formerly saved) column arrangement.
Select Reset to Default to set the grid
layout back to factory settings.
Save Grid Layout: Use to save the
current column arrangement.
Delete Grid Layout: Use to delete a
(formerly saved) column arrangement.
Page 104
M0125ANA.DOC
6.4.2
Using the Filter Builder
With the Filter builder of the menu View a more detailed

filter can be created, deleted, imported and exported.
(Note: This feature is different from the NE Filter Builder explained in chapter 6.4.3).
A filter can consist of several groups of conditions. Conditions are the defined criteria
for the selection.
6.4.3
Network Element Filter
The NE filter is situated on the top of the NE Tree. Five pre-set filters are available.
Additionally, the NE Filter Builder can be used to create a customized view (
Custom Filter). Please note that a filter does not affect the visualization of the alarms
(i.e. all alarms will be displayed and not only those of NEs included by the selected
filter).
Click
to get a predefined view of the network elements.
to open the NE Filter Builder and create a customized filter (see following
Click
chapter 6.4.3.1). This customized filter will be added to the end of the list box.
Please note that only one list entry Custom Filter is available in the list box. In case
of changes of the Custom Filter its former settings will be overwritten. Move the
mouse pointer over the list entry Custom Filter to get a description of it.
Page 105
6.4.3.1
Customizing a Filter with the NE Filter Builder
Note: Once entries have been made in the individual fields (for details see chapter
6.4.3.2 Filter Settings), the buttons OK and Cancel will also be available and the
buttons Apply and Undo will become active.
Click
Arrow to list all available filters. Scroll through the list to select a filter.
Click
to get the amount of NEs matching your filter settings.
The button Convert into Static Filter is explained in chapter 6.4.3.4.

Use the buttons Add or Delete to add or to delete a filter.
Use the button Apply to save you settings and visualize your filter definition in the
NE Tree. Please observe that afterwards neither Undo nor Cancel will be available.
This filter definition becomes the Custom Filter definition. The OK button has the
same effect but, additionally, it will close the window.
To undo your settings and recover the settings that were last stored use the Undo
button BEFORE clicking Apply or OK. The Cancel button serves the same purpose
but, additionally, it will close the window.
Page 106
M0125ANA.DOC
6.4.3.2
Filter Settings
Note: If no choice is made in one or more of these fields, no filter is set for the
respective characteristic.
... except those...: Select except those to show in the NE Tree all network elements
which do not match the filter builder definition.
...located beneath: Reflects the NE Tree. Select the folder.
...of Type: Select the type of NE.
...and Sub Type: If there are sub types available, the list box is active. A selection of
several sub types is possible.
...running SW VerNo: If type is selected, choose VerNo from list or make an
individual entry.
...owned by: Select the owner.
...in Configuration Group: Select the NE Configuration Group. A Configuration
Group profile can be created via the Connectivity Manager (see chapter 5.3.3) or via
menu Tools Profiles (see chapter 6.17.3).
...connected via: Select the connection type.
...with NE Status: Select from the list provided (see NE Filter Builder window on
previous page) to filter network elements of the according NE status.
...having active Alarms: Select Any, Yes or No to filter NEs having active alarms or
not.
...having disabled Alarms: Select Any, Yes or No to filter NEs having disabled
alarms or not.
...having received event: Make a selection (one or more is possible) to filter NEs
having received the selected event(s). For details about these events see chapter
6.10.3.1 Event Triggered Actions.
6.4.3.3
Importing a Filter from the Scheduler
To import a filter created with the tool Scheduler (as described in chapter 6.10 Tool
Scheduler (Option), section 6.10.1.2 Step 2: Tab Network Elements - Customize the
Network Elements), proceed as follows:
After a right-mouse click on Custom Filter select Assign from Schedule and a list
of available schedule filters is displayed. Choose the desired filter but please observe
that if a Custom Filter has already been stored, its settings will be overwritten and
cannot be retrieved afterwards.
Page 107
6.4.3.4
Filter Type Conversion
As default, filters are created as dynamic filters, i.e. the chosen filter will always
evaluate the current state according to the given criteria and adapt the selection / NE
Tree accordingly.
It is, however, possible to convert a dynamic filter into a static filter, which will always
show the selection that was made when it was last stored. To do so, use the Convert
into Static Filter button in the NE Filter Builder window (or in the Schedule Wizard).
Alternatively, it is also possible to do a right-mouse click in the NE Filter Builder
window (or in the Schedule Wizard) and select Convert into Static Filter.
In both cases a different Filter Builder/Schedule Wizard will be displayed, where an

individual selection of NEs can be made by setting or removing the tags as desired.
Confirm your selection and the filter will be changed accordingly. When it is selected
again, it will always show the tagged NEs only.
Note: Please observe that this change is irreversible, i.e. turning this filter back into a
dynamic one is not possible. A right-mouse click in the static Filter Builder/Schedule
Wizard will prompt the selection Create Dynamic Filter from Scratch to access the
dynamic Filter Builder/Schedule Wizard, where all filter settings have to be entered
anew.
Page 108
M0125ANA.DOC
6.5 ADD NEW NETWORK ELEMENT (NE)

To add a new NE
-
right-mouse click the database level or folder in the NE Tree, select menu
New / Any New Network Element
or
-
select in A.I.M.O.S. Visualization Tree / New / Any New Network Element.

Select the type of NE to be created from the list (in the right part of the screen
an illustration of the highlighted NE will be displayed) and confirm with Next:
Node M, Node G, Node C, Node

AM(+)*, Node A
AMR
OneBase MCPA CellExtender
Legacy ION-B Optical System
ION Optical System
MRx18
DICE
MIR-T
ION-M MiniMaster
generic
generic 1
generic 2
MR2003P
MR2133
* For Network Elements of the Node AM(+) type, choose type Node A from the list.
Depending on the type of NE, the corresponding protocol is selected automatically.

6.5.1
Node X
6.5.1.1
Basic Parameter Setting
The Node X i.e. Node C, Node G, Node M, or Node A ( choose this type also for
a Node A+ or a Node AM) is the highest management and supervision level of a
Node X system. When a Node X system is initialized to A.I.M.O.S., its complete
structure is queried and transmitted to the A.I.M.O.S. database.
When the corresponding Node X entry from the list has been selected and confirmed
(click Next), the New Node X' wizard starts (the Use SNMPv3 parameter is
available for Node A only):
Page 109

IP-Address / Port: Enter the IP address and IP port of the new NodeX system.
Network Connection Type: Select the network connection type from the list to be
used for connections to this Node X (only available types are suggested).
Modem Group: Select from the list box. The modem groups are predefined in the
tool 'Connectivity Manager' with the function 'Modem Group'.
Uplink Connection Parameters: Select Overwrite or No Change.
Choose Overwrite if A.I.M.O.S. shall set or overwrite the uplink connectivity
parameters (Connection from Node X to A.I.M.O.S.) in the Node X system.
Note: If the 'Uplink Connection Parameters' are set to 'Overwrite', alarms from the
Node X system are sent to A.I.M.O.S. automatically. If the alarm forwarding from the
Node X system should not be changed, select 'No change'.
SNMPv3: This parameter is available for NEs of the Node A type, only. Set
according to NE configuration.
After entering these Basic

Parameters of the new Node X
click Next.
The parameters required in the following screens depend on the Network Connection
Type selected. In the screens displayed the type Circuit Switched is chosen.
6.5.1.2
Dial Parameter Setting
A: Overwrite was chosen as Uplink Connection Parameter:

Enter telephone number and PPP login
data (RAS-modem connection) or the
A.I.M.O.S. IP address (LAN connection)
of the A.I.M.O.S. server and click Next.
Enter A.I.M.O.S. IP address and phone

no. of A.I.M.O.S. and the PPP user name
and password.
Click Save to make the entry to the
database.
Page 110
M0125ANA.DOC
B: No Change was chosen as Uplink Connection Parameter:
Enter telephone number and PPP login
data (RAS-modem connection) or the
A.I.M.O.S. IP address (LAN connection)
of the A.I.M.O.S. server.
Click Save to make the entry to the
database.
Then, continue as follows irrespective of the Uplink Connection Parameter selected

(the exemplary screens are made with the parameter Overwrite):
It is recommended to click Try Connection to setup a test connection:
The progress will be shown in the status/details window.
If the test connection is successfully finished (as shown in the illustration above),
click Next to proceed.
(If the test connection fails, check the hardware, e g. cable, network adapter, etc., the
software / RAS connection, and the IP parameters for the connection.)
Enter Component Name
and Trap Info and select
an NE Owner from the
list provided.
(These data can be
displayed in the NE Tree
via the context menu
Field Chooser.)
Click Get to import the
unique identifier of the
Node system.
Page 111
When this job is finished, click Next.
Now the current status and

settings of the Node X system
can be queried:
Check the respective box to
query the information and click
Get.
If active alarms are

queried and an alarm
is active at the Node
X system, an alarm
message will pop up.
Click Show to see details of the alarm(s).

Click Close to shut the alarm information window.
Click Close to shut the installation of the NE connection.

Assign the Node X to a folder by selecting the Node X. Click in the context menu
Move and choose the desired folder.
Page 112
M0125ANA.DOC
6.5.2
AMR
Select the New AMR entry from the list and click Next.
The 'New AMR' wizard starts:
Enter the Basic Parameters of the new AMR:

IP-Address / Port: Enter the IP address and IP port of the new AMR system.
Network Connection Type: Select the network connection type from the list to be
used for connections to this AMR (only available types are suggested).
Uplink Connection Parameters: Select Overwrite or No Change. Choose
Overwrite if A.I.M.O.S. shall set or overwrite the uplink connectivity parameters
(connection from AMR to A.I.M.O.S.) in the AMR system.
AMR system are sent to A.I.M.O.S. automatically. If the alarm forwarding from the
AMR system should not be changed, select 'No change'.
Refer to chapter 6.5.1.2 Dial Parameter Setting for the step by step instruction.
Assign the AMR to a folder by selecting the AMR. Click in the context menu Move
and choose the desired folder.
Page 113
6.5.3
MCPA
Select the OneBase MCPA CellExtender entry from the list and click Next.
The 'New OneBase MCPA ' wizard starts:
Enter the Basic Parameters of the New OneBase MCPA CellExtender:

IP-Address / Port: Enter the IP address and IP port of the new OneBase MCPA
CellExtender system.
Network Connection Type: Select the network connection type to be used for
connections to this MCPA (only available types are suggested). Standard is LAN. If
the communication group for a connection via modem (RAS outgoing) is selected,
click Next and enter the telephone number and PPP login data for the MCPA system.
(connection from MCPA to A.I.M.O.S.) in the MCPA system.
MCPA system are sent to A.I.M.O.S. automatically. If the alarm forwarding from the
MCPA system should not be changed, select 'No change'.
Assign the MCPA to a folder by selecting the MCPA. Click in the context menu Move
Page 114
M0125ANA.DOC
6.5.4
ION-B Controller Type TSUN1, TSUN2, TSUN3 and TSUN6
Select the Legacy ION-B Optical System entry from the list and click Next.
Note: Observe that ION-B systems with a TSUN4 controller must be created as an
ION-M Optical System element as explained in chapter 6.5.6.
The Legacy ION-B Optical System level is the highest management and
supervision level of an ION-B system. When it is initialized to A.I.M.O.S., its complete
structure is queried and transmitted to the A.I.M.O.S. database.
The 'New Legacy ION-B ' wizard starts.
Enter the Basic Parameters of the new Legacy ION-B Optical System:
IP-Address / Port: Enter the IP address and IP port of the new ION-B system.
connections to this ION-B (only available types are suggested). If the communication
group for a connection via modem (RAS outgoing) is selected, click Next and enter
the telephone number and PPP login data for the ION-B system.
Click Save to make the entry in the database and Next to proceed.
It is recommended to click 'Try connection' to setup a test connection.
If the test connection fails, check the hardware (cable, network adapter,...), the
software (RAS connection) and the IP parameters for the connection.
Click 'Next>>>'.
Click Get to import the unique identifier of the ION-B system.
Click Get to import the complete structure of the ION-B system. This will request the
current topology of the ION-B system with all components. The answer to this
request is evaluated and entries are made to the database for all system
components.
Page 115

Click 'Next>>>'.
Now the current status and settings of the ION-B system can be queried. Check the
respective box to query the information and click Get.
If active alarms are queried and an alarm
is active at the ION-B system, an alarm
message will pop up.
Click 'Show' to see details of the
alarm(s).
Assign the ION-B to a folder by selecting the ION-B. Click in the context menu Move
When the connection has to be established through LAN interface it is required to
configure the following parameters via the ION-B WEB interface:
1) 'Network Host IP'
2) 'Network Subnet Mask'
3) 'Network Gateway'
4) 'OMC IP Address' (A.I.M.O.S.)
5) Check that 'Alarm Notification' is 'Enabled'
6) Ensure the 'LAN' connectivity option in the 'Connectivity Table' is 'Enabled'
7) Number of 'Retry' of 'LAN' connectivity option in the 'Connectivity Table'
When the connection has to be established through a modem connection (dial-out,
dial-in) interface it is required to configure the following parameters:
1) 'Modem Driver' (not required in ION-B Supervision Unit SW v 4.1.1 and previous
SW version)
2) 'Modem AT Baud'
3) 'Initialization String'
4) 'PIN Number' when enabled (depending on the modem SIM card)
5) Enable the 'Startup PPP Service On Boot'
6) Dial-in account: 'User Name' and 'Password'
7) Check that 'Alarm Notification' is 'Enabled'
8) 'OMC IP Address' (A.I.M.O.S.)
9) Enable the 'CS' (Circuit Switched Network) connectivity option in the 'Connectivity
Table'
10) 'Phone No' of the enabled CS connectivity option (ppp login)
11) 'User Name' and 'Password' of the enabled CS connectivity option (ppp login)
12) Number of 'Retry' of 'CS' connectivity option in the 'Connectivity Table'
13) Disable connectivity options different from CS
For a detailed description on how to configure the ION-B Supervision Unit see 'ION-B
Remote Supervision System User Manual'.
Note:
Page 116
In order to contact an ION-B through A.I.M.O.S. web interface, the

Internet Explorer settings [Tools-Internet Options-Security] have to
be set to Allow Meta Refresh enabled.
M0125ANA.DOC
6.5.5
Note: Please observe that currently for these systems only alarming is available.
Thus, no configuration is possible yet.
Select the ION-U System / ION-E System entry from the list and click Next.
The 'New ION-U System' / 'New ION-E System' wizard starts (as the wizard setup is
the same for both systems only the screen for ION-U is shown here):
Enter the Basic Parameters of the new ION System:

IP-Address / Port: Enter the IP address and IP port of the new ION system.
connections to this ION-U / ION-E (only available types are suggested). If the
communication group for a connection via modem (RAS outgoing) is selected, click
Next and enter the telephone number and PPP login data for the ION-U / ION-E
system.
(connection from ION system to A.I.M.O.S.) in the ION system.
ION system are sent to A.I.M.O.S. automatically. If the alarm forwarding from the ION
system should not be changed, select 'No change'.
Assign the ION-U / ION-E system to a folder by selecting the corresponding ION-U /
ION-E entry. Click in the context menu Move and choose the desired folder.
Page 117
6.5.6
ION-M Optical System Controller Type RMC, MMC Plus, TSUN4
An ION-M Optical System is the highest management and supervision level of an

ION-M system. When it is initialized to A.I.M.O.S., its complete structure is queried
and transmitted to the A.I.M.O.S. database.
Select the New ION-M entry from the list and click Next.
The 'New ION-M Optical System' wizard starts:
Enter the Basic Parameters of the new ION-M Optical System:

IP-Address / Port: Enter the IP address and IP port of the new ION-M system.
Login User: Enter the username to be used for the login to the ION-M system.
Login Password: Enter the password for the login to the ION-M system.
connections to this ION-M (only available types are suggested). If the communication
group for a connection via modem (RAS outgoing) is selected, click Next and enter
the telephone number and PPP login data for the ION-M system.
(connection from ION-M system to A.I.M.O.S.) in the ION-M system.
ION-M system are sent to A.I.M.O.S. automatically. If the alarm forwarding from the
ION-M system should not be changed, select 'No change'.
Assign the ION-M system to a folder by selecting the ION-M entry. Click in the
context menu Move and choose the desired folder.
Page 118
M0125ANA.DOC
6.5.7
SMS Network Element
The SMS-connected Network Element level is the supervision level of repeater

systems with an SMS interface.
Select the New SMS-connected NE from the list. This can be:
MRx18
DICE
MIR-T
ION-M MiniMaster
Generic
Generic1
Generic2
MR2003P
MR2133
The wizard for the new NE starts:
Note: The required entries vary depending on the type of SMS-connected NE.
Page 119

Telephone number: Enter the telephone number of the new SMS-connected NE
and add information on the location of the device for identification purpose.
Location: Enter the location.
Port Configuration: Alarms can be assigned to ports according to the settings at the
NE or the ports can be disabled. For several SMS-connected Network Elements
ports are preset. For details on the inputs please see the documentation of the
device.
Click button 'Set' to send the device a configuration SMS for the initialization of the
device to A.I.M.O.S.
Click Next.
Now the current status and settings of the SMS-connected system can be queried.
Check the respective box to query the information and click Get.
If active alarms are queried and an alarm is active at the NE, an alarm message will
pop up.
6.5.7.1
MRx18
Select the 'MRx18' entry if the device is a member of the MRx18 family
(miniRepeater family) and capable of the SMS feature.
It is mandatory to enter the telephone number of the modem.

6.5.7.2
DICE
Select the 'DICE' entry if the device is a member of the DICE family (miniRepeater)
and capable of the SMS feature.
The default port configuration
is as follows:
The ports are preset for typical miniRepeater applications.
Page 120
M0125ANA.DOC
6.5.7.3
MIR-T
Select the 'MIR-T' entry if the device is a member of the MIR-T family and capable of
the SMS feature.
is as follows:
The ports are preset for typical MIR-T applications.

6.5.7.4
ION-M MiniMaster
Select the 'ION-M MiniMaster' entry if the device is an ION-M MiniMaster and
capable of the SMS feature.
6.5.7.5
Generic
Select the 'Generic' entry if the device is no member of the other repeater families
is as follows:
Ports 1 to 4 are preset to external alarms, port 5 to 'Heartbeat'.
Page 121
6.5.7.6
Generic 1
Select the 'Generic1' entry if the device is no member of the other repeater families
is as follows:
Ports 1 to 5 are preset to external alarms.

6.5.7.7
Generic 2
Select the 'Generic2' entry if the device is no member of the other repeater families
is as follows:
6.5.7.8
MR2003P
Select the 'MR2003P' entry if the device is an MR2003P and capable of the SMS
feature.
is as follows:
6.5.7.9
MR2133
Select the 'MR2133' entry if the device is an MR2133 and capable of the SMS
feature.
is as follows:
Page 122
M0125ANA.DOC
6.6 ADD NEW FOLDER

Folders serve to organize the network components in a clearly arranged way and to
control access to network components for the users. Access to NEs in a folder can
be assigned to users.
For best visualization of the network feel free to create as many folders as
necessary. Select the destination level (OMC or folder) in the NE Tree with a rightmouse click, choose the New / New Folder and enter a name for the folder. Or
select in A.I.M.O.S. Visualization Tree / New / New Folder.
The network elements can easily be assigned to a folder by dragging the NEs to the
folder with drag-and-drop.
6.7 NETWORK ELEMENT OPERATIONS

To manage the network elements use the context menu item 'Network Element
Operations', which is accessible by a right-mouse click or via the menu: Tree
Network. Depending on the NE type selected, all NE operations available for this
specific type are displayed:
The example above shows the NE Operations menu of a Node AM but the following
survey lists all operations that are available. When an operation is chosen, it will be
carried out for the selected NE.
Please observe that access to some of the operations may also depend on the
Account Manager rights (for details see chapter 5.4.2).
Finish Installation: This operation is only available if an NE has not yet been set up
completely. In such a case use it to finish the setup.
Try connection: Use to test the connection to the NE. Performing this operation is
recommended after the installation is finished.
Read Unique System ID...: Use to get the system-specific ID.
Read Network Structure: Available in systems with NE subunits to read the
complete network topology into A.I.M.O.S., e. g. after changes in the system
topology. 1)
Query Alarms: Use to read all current alarms of the NE into A.I.M.O.S. 2)
Query All: This operation opens a submenu with further actions that can be
performed. All are listed but only those available for the selected NE are active
(tagged).
Page 123

Upon clicking the button Get all tagged operations are carried out and the progress
will be displayed in the right part of the screen.
The following operations correspond to a main NE operation:

Network Structure = 1);
Active Alarms = 2);
Hardware Inventory Data = 3)
The Parameter Settings and Current State Values depend on the selected NE type.
For details see the following table:
Get Parameter Settings
Get Current State Values
Node G /
Node M /
Node C /
Node A
Get Version Info

Get Heartbeat Config
Get Config
Query Connectivity
User Texts
Alarm Severities (not for Node C)
ION-M
Query All Params
Query Actual State
Get RepeaterType
Get Segment
Get ALSEV
Get H-Beat
Get RSSI
Get RF Status
Get CI
Get SW-Version
Get SMSC
MRx18
Get Config
Read HIDs: Use to read HID information into A.I.M.O.S.; this operation should be
done after changes of the HW. 3)
Set Time: Use to set the time and date for the NE. The submenu also offers a Get
command to see the current settings.
Reboot: Use to reboot the NE.
Get GPS Position: Use to determine the coordinates of the NE (Node AM only),
which will be displayed in the Configuration window (see chapter 6.8.2).
Send Configuration: Use to initialize SMS connection for NE.
Set Factory Default: Use to set NE back to factory-set default values.
Get Service Center Number: Use to retrieve the Service Center Number of an
SMS-connected NE.
Page 124
M0125ANA.DOC
Send Service Center Number: Use to send the Service Center Number of an SMSconnected NE.
Delete Pending Configuration Data: This operation overwrites planned settings
with current settings to get rid of [legacy]* planned settings.
* or [outdated]
If you are sure to continue,

confirm
the
following
notification:
Backup: Use to store the configuration data of the NE into the database. The
following operations will be performed (automation via Tool Scheduler (Option) is
possible; see chapter 6.10.3):
Alarm Severities
Started
Get HW/RF
Get Version Info

Get Heartbeat Config
Wrapping and saving backup file
Query Connectivity
Compressing backup data
User Texts
Saved backup to database
6.8 FUNCTIONS BAR

The Functions bar contains the tabs with the features and functions available for the
Network Element selected with the NE Tree.
The tabs are sorted in a hierarchical way: The upper tabs are determined by the NE
selected in the NE Tree. The example shows the upper tab 'Configuration', which
holds the lower tab 'User'. Depending on the size of the window not all tabs available
might be displayed right away; use the arrow buttons to scroll to the left or right.
Note: Depending on the type of NE and its supported features, the tabs vary.
The upper tabs can be: Supervision
Notes
Configuration
Log
Maintenance
Page 125
6.8.1
Supervision
Tab Supervision lists all alarms for the selected NE. Depending on the selection in
the NE Tree, all alarms of the NE, the complete system, or the complete network are
displayed.
Alarms can be recognized, manually cleared or deleted via the button Recognize
(see also chapter 6.2.5 Extras).
Access to the actions Manual Clear, Manual Delete,
Recognize, and Recognize all can be configured in the
Account Manager (chapter 5.4.2).
Alarm Help opens the Alarm Help for the selected alarm.
The button Locate shows the alarming NE in the NE Tree.
The button Excel Export allows saving the alarm list (of the
selected NE, folder, or the complete network) in an Excel
compatible file format. Access can be configured in the
Customize the design of the alarm list in Configuration / Alarm Settings.
The displayed columns depend on the selection made in the table filter as explained
in chapter 6.4.1.1.
Please observe for Network Elements with GPS function that the columns Latitude
and Longitude (scroll to end of list as explained in chapter 6.4.1.1) must be selected
to show the GPS position of an NE at the time of an alarm since these columns are
not part of the default selection. In case of an alarm of an NE with GPS coordinates
the context menu GPS Position is available by a right-mouse click on the alarm. The
coordinates can be copied to the Windows clipboard or to Google Maps to display
the NE in a map:
Coordinates of the last known
NE position.
Coordinates of the position,

where the alarm was raised.
Page 126
M0125ANA.DOC
6.8.1.1
Alarm History
Click Alarm History to show the last 5.000 alarms. The number of listed alarms can
be edited with Alarm History Initial Size Limit in Account / Button Organizations.
Access to the actions Select All and Manual Delete can be configured in the
Click Select All to mark all displayed alarms.

Tag Complete List to show all alarms available in the alarm history. Note that this
may cause a performance decrease due to the number of alarms.
6.8.1.2
Alarm Help
Select an alarm and click Recognize - Show Alarm Help or press button F1 to view
further information on the alarm.
The context-sensitive Troubleshooting help appears.
Remarks can be added and saved with the alarm message.
Page 127
6.8.2
Configuration
Please observe that access to this tab can be configured in the Account Manager
In some lower tabs the button
is provided to import the current repeater data.
Note: Only the supported features of the selected NE can be customized within
the respective tab.
Changes in the A.I.M.O.S. database can be made in the white fields of the left row.
Depending on the tab, changes to the NE settings can either be made by clicking the
Edit NE button or using the checkbox
Changes have to be confirmed with the OK button or with
The lower tabs can be:

1) General
Information on the NE is listed here, profiles can be assigned (see chapter 6.17), and
Alarming and Alarm Polling can be en/disabled.
For NEs supporting the corresponding feature (currently only available for the Node
AM), this tab also provides the GPS Position button which opens a popup menu:
If the GPS position was not submitted by the
NE during the creation process, it is possible
that, initially, only Get GPS Position and Show
updated Get GPS Position in Google Maps
are provided (availability can be restricted by
Account Manager Rights, see section 5.4.2).
These serve to determine the coordinates of the NE, which are displayed in the
Configuration window, or to directly display the NE in a map.
Page 128
M0125ANA.DOC
With the extended popup menu these

coordinates can then be copied to the
Windows clipboard or to Google Maps
to display the NE in a map.
With every alarm of the respective NE its
GPS position will be updated.
2) Connectivity
All data for the connection to and from the NE are displayed here. Contents of the
Connectivity page vary depending on the type of connection supported by the NE.
For further information refer to chapter 6.9 Configuration - Connectivity.
3) Heartbeat
Heartbeat status and configuration are displayed and can be changed. The heartbeat
is a kind of "I am alive" message of the NEs sent by the individual NE via the same
communications channel as the alarms. Its purpose (when activated) is to guarantee
that an NE is 'in operation' and able to send out alarms (communications channel for
alarms from NE to A.I.M.O.S. is functioning) if required.
HeartBeat Status displays
the Next Expected and Last
Received heartbeats of an
NE.
HeartBeat Config displays
the heartbeat configuration
settings of the respective NE.
The
HeartBeat
Resume
Config is only displayed for
NEs supporting this feature
(e.g. Node AM). For more
details see * notice on next
page.
Upon clicking the Edit NE button, the following features can be configured:
Page 129

Enabled: When tagged, the NE will send a regular heartbeat that will be monitored by
A.I.M.O.S.:
Interval: Set the interval at which
the heartbeat will be sent.
Heartbeat Overtime: Time period
the system will wait until a
Heartbeat missing alarm is
generated if the heartbeat is not
received within the configured
Interval.
* For NEs with suspended heartbeat supervision while Shut Down or Off Duty
(these conditions are visualized in the Symbol and NE Status columns of the NE
Tree see section 6.3) the HeartBeat Resume Config settings are available, as
well. If the according Maximal Duration is set and no heartbeat is received within
the configured period, the system will generate a Heartbeat resume missing alarm.
Note: With default setting 0 minutes this feature is not active, i.e. the system will
wait until the NE is no longer Shut Down or Off Duty, until supervision is resumed
and a new heartbeat is expected.
4) User
Use to display and change the NE user settings. This page is only available for NEs
supporting this feature (currently only Node AM/ Node A+ and ION-M). The following
screen shot shows an exemplary view of a Node A+:
For the User Manager two settings are available: A.I.M.O.S. or NE. If it is set to
A.I.M.O.S., the A.I.M.O.S. password requirements as specified in section 5.1.3.1
Password Settings will be valid for setting the User Passwords below; with setting NE
the requirements are determined by the SW of the corresponding NE. For details on
these, check the SW manual of the NE.
Page 130
M0125ANA.DOC
For NEs of the Node AM type, the Password Duration in Days for a User can be set
from 1 999 days when the corresponding check mark is set. When no setting is
made for this parameter, the password does not expire:
Page 131
5) HW/RF
In this section hardware settings are listed. For details on NE specific hardware
settings please read the manual of the respective NE.
For a Node G the following tabs are available:
Please observe that after performing 'Show Set Values' in tab 'Cell Allocation' or
'Mobile Allocation' a context-sensitive menu can be accessed by a right-mouse click.
In case of a Node G with Frequency Shifting the following tabs are available:
For a Node A the following tabs are available:
With the button 'Sync NE' the current data of the NE are queried and the display is
updated accordingly.
The tab System Configuration provides the additional selection Enable GPSBased Configuration (under Network Element Settings) if the NE supports this
feature:
6) External I/Os
This section lists the settings for configurable external alarms.
Page 132
M0125ANA.DOC
7) Alarm Settings
On the OMC level the tab Alarm Severities is available in order to set the severities
of alarms generated by A.I.M.O.S.:
In the tab Clear Modes set whether recognized alarms (either manually or using the
Auto-Recognize feature) should be cleared automatically upon recognition.
The following settings are available for other NEs:
Note: To save settings, always click the
button.
In order to set the severities of alarms generated by the selected NE, the tab Alarm
Severities is available:
Page 133
The Actual Severity and Actual Latency (time an alarm must be active before it is
informed to A.I.M.O.S.) are displayed:
Tag Show Set Values to display the Planned Severity and Planned Latency
columns where the severity and latency settings can be changed.
Available severity levels are: critical, major, minor, warning, disabled, and (if
supported by the selected NE) information The alarm latency can be set at predefined intervals in a range from 0 to 60 minutes.
Alarm Thresholds:
For all NEs supporting the feature (i.e. Node type network elements), this additional
tab is available (for details see SW manual of the corresponding Node).
Page 134
M0125ANA.DOC
8) Web
Use this tab to access the web interface of the selected NE. If certain criteria are
fulfilled for the corresponding NE (for details see chapter 5.3.3.5), a Login button is
provided by which username and password will be entered automatically to the login
page to go directly to the home page of the NE. Otherwise, login data will have to be
entered manually.
If HTTPS is chosen as WEB Server Configuration in the Connectivity page (see
section 6.9.5.5), a certificate installation is required before the first access and the
system will prompt an according Security Alert. The detailed procedure is explained
in chapter 14.
Note: A change of settings made in the web interface is saved to the NE only. The
database of A.I.M.O.S. is not updated automatically. To synchronize the database of
A.I.M.O.S., use either the Event Triggered Actions of the Tool Scheduler (Option)
(see section 6.10.3.1) or the NE operation Query All (see chapter 6.7). If important
settings for the A.I.M.O.S. connection are changed (e.g. connectivity mode, IP
address, username, or password), make sure to adjust these in the Connectivity
page of A.I.M.O.S. (see section 6.9 Configuration - Connectivity), as well.
For refreshing the screen display, a Refresh button is available.
9) NE Image
Use this tab to insert an image of your choice for the NE.:
Click the Load from File button and browse to the location where your image is filed:
Supported image types are:

Page 135
6.8.3
Maintenance
Please observe that access to this tab can be configured in the Account Manager
Note: Only the supported features of the selected NE can be customized within
the respective tab.
The tabs can be:
Backup/Restore
This tab serves to make a backup of all settings within the NE (automation via Tool
Scheduler (Option) is possible; see chapter 6.10.3). If changes made to the NE seem
to be incorrect, a previous stage of all settings can be restored in the NE.
Use the Excel Export button to save a survey of available backups as Excel file.
The Export to File button saves the data in zip file format (see also chapter 6.2.1).
Use this function also to copy the configuration of an NE to a new repeater with the
same software and hardware versions.
Revision Info
This section contains a listing of hardware and software information.
Inventory Data
This section is a listing of all components with the Hardware Inventory Data.
The selection made here

There are 3 different views available:
determines the list of NEs displayed in the Maintenance view illustrated above. The
displayed data can be saved as Excel file (Excel Export button).
A) Current HIDs shows the HW currently installed on site. The displayed period,
which may still be stored from a former view (B or C), does not affect the list.
B) HIDs valid between shows the HW installed on site in a specific time frame that
can be set as desired.
C) HIDs changed between shows all changes (e.g. added or removed) in a specific
time frame that can be set as desired.
The following examples explain the information given in the individual columns of the
Maintenance table.
Page 136
M0125ANA.DOC
Example 1: A new device (identified by ID Number & Serial Number) has been added
Example 2: An existing device (identified by ID Number & Serial Number) has been
removed
Example
1&2
1
Column
Reported
Reported State
Outdated
Outdated State
Outdated
Entry
date/time
new/added
no entry
no entry
date/time
Outdated State
removed
Explanation
date/time the device has been added
device is not outdated
date/time the device has
removed
device has been removed
been
Example 3: A device (identified by ID Number & Serial Number) has been changed
two times (e.g. new SW versions)
Example 4: A device (identified by ID Number & Serial Number) has been changed
(e.g. new SW version) and removed afterwards
Example
3&4
Column
Reported
Reported State
Outdated
Outdated State
Reported
Reported State
Outdated
Outdated State
Reported
Reported State
Outdated
Outdated State
Reported
Reported State
Outdated
Outdated State
Entry
Explanation
Legacy data (line 1)
date/time
date/time the device has been added
new/added
date/time the device has become
date/time
obsolete (the 1st time)
obsolete
Legacy data (line 2)
date/time the device has been
date/time
changed the 1st time
changed
date/time
date/time the device has become
obsolete the 2nd time
obsolete
New data (line 3)
date/time
changed the 2nd time
changed
no entry
device is not outdated
no entry
New data (line 2)
date/time
changed
changed
date/time
removed
removed
Page 137
6.8.4
Notes
Notes can be attached for each separate NE (see also Add a note in chapter 6.2.3
Tree). These notes can be saved as Excel file with the Excel Export button.
6.8.5
Log
The feature Log is only displayed when Show Visu Log is tagged in the Preferences
Editor (see chapter 5.2). It shows the internal debug logs that are generated by the
A.I.M.O.S. Connector service for the respective NE.
These logs can be saved as Excel file with the Excel Export button.
Please observe that access to this tab can also be configured in the Account
Manager (see chapter 5.4.2).
6.9 CONFIGURATION - CONNECTIVITY

The Connectivity page displays all parameters that are necessary to establish the
communication connections between A.I.M.O.S. and the network elements.
NEs already integrated into A.I.M.O.S. database via CS connection and capable of
Packet Data communication can be switched to Packet Data via the Configuration /
Connectivity settings.
Note: To make use of packet data communication it is required that A.I.M.O.S. server
is connected to packet data network via LAN. It is also required that the A.I.M.O.S.
server has received a fixed IP address from the packet data network.
Red marked lines/parameters in the connectivity pages
are an indication that there is an inconsistency among
the current connectivity settings of an NE
- relating to the settings in the Connectivity Mode
or
- relating to the settings of the Preferences Editor (5.2).
Click Edit NE to display the values that can be changed.
Circuit and the packet switched connections are configured as fallback systems. If
the preferred connection type is unavailable, the NE will attempt to use the other
connection type if it is supported by the modem.
Page 138
M0125ANA.DOC
For NEs supporting VPN, additional parameters are provided (see chapter 6.9.6).
For NEs supporting SNMPv3 the
corresponding parameter is available in
the Common Connectivitiy section:
The following NE-related data may be
available in the Network Element
section irrespective of the communication
type selected. Their availability only
depends on the NE type and settings (for
explanations see chapter 6.9.5):
6.9.1
Circuit Switched Connection
The example shows the circuit connectivity settings of a Node.
Note:
Check in Tools / Connection
Manager whether the needed
Modem Groups and RAS-in
Profiles are created. If they are
not, create them.
Buttons: see chapter 6.9.5.1.
Common Connectivity
Connectivity Mode: Displays the
connectivity mode for connecting
this NE.
A.I.M.O.S. (= A.I.M.O.S. related
settings)
Dial-Out Modem Group:
Select modem group from list.
OMC IP Address:
A.I.M.O.S. IP Address.
OMC IP Port: A.I.M.O.S. IP Port.
Dial-In Configuration:
A.I.M.O.S. RAS-in profile.
Network Element: NE related settings. Only available settings are displayed. If the
network connection is set to RAS, the CS IP address and port are used by A.I.M.O.S.
CS IP Address / IP Port: IP address and IP port of an NE connected via circuit
switched connection.
Dial-In Configuration: NE profile.
CS Phone Number: NE phone number (data call).
Packet Switched Settings (Fallback): Select the PS profile.
WEB-Login Configuration: see chapter 6.9.5.2.
Alarm Type: see chapter 6.9.5.3.
Inform Timeout: see chapter 6.9.5.3.
Inform Retries: see chapter 6.9.5.3.
Zone Change Traps: see chapter 6.9.5.4.
WEB Server Configuration: see chapter 6.9.5.5.
Additional Information: see chapter 6.9.5.6.
Page 139
6.9.2
Packet Switched Always On Connection
6.9.2.1
Overview
NE permanently holds the packet switched modem connection.

The example shows connectivity settings of a Node.
Note: Check in Tools / Connection Manager whether the needed PS Profiles are
created. If they are not, create them.
Common Connectivity
Connectivity Mode: Displays the connectivity mode for connecting this NE.
A.I.M.O.S. A.I.M.O.S. related settings.
OMC IP Address: A.I.M.O.S. IP address.
OMC IP Port: A.I.M.O.S. IP port.
Network Element: NE related settings. Only available settings are displayed.
PS IP Address / IP Port: IP address and IP port of an NE connected via packet
Packet Switched Settings: NE packet switched profile.
Page 140
M0125ANA.DOC
6.9.2.2
Change Connectivity Mode to Packet Switched Always On
To change to the connectivity mode 'Packet Switched Always On' proceed as shown
in this example:
Step 1: Check in chapter 5.3 Connectivity Manager - Modem Management

whether the needed PS Profile is created. If not create the PS profile.
Step 2: Select Configuration / Connectivity tab of the NE to be modified.
Step 3: Click Edit NE to edit the settings of the NE.
Step 4: Select Connectivity Mode 'Packet Switched Always On'.
Step 5: Select the PS-profile in Packet Switched Settings.
Step 6: Customize the other settings.
Step 7. Confirm the window with OK.
Step 8: The parameters PS IP Address and PS IP Port in the current settings

will be marked red. This gives notice that the NE is not yet online.
Step 9: A.I.M.O.S. will establish a CS connection to the repeater showing the

progress in an information window. Wait until the dial-up is successfully
finished. This can take up to two minutes. Then A.I.M.O.S. displays the PS IP
Address and PS IP Port transmitted from the repeater.
Page 141
6.9.3
6.9.3.1
Overview
NE establishes a packet
switched connection only
when a message needs to
be sent. This example
connectivity
shows
settings of a Node.
Note: Check in Tools /
Connection
Manager
whether the needed PS
Profile, the SMS Modem
Groups and the SMS
Profile are created. If not
create them.

Common Connectivity
Dial-Out Modem Group: A.I.M.O.S. SMS Modem Group. Used to send out an SMS
that requests the NE to establish the network connection (Wake-up SMS).
OMC IP Address: A.I.M.O.S.
OMC IP Port: A.I.M.O.S.
PS IP Address / IP Port: IP address and IP port of the NE connected via packet
SMS Phone Number: The SMS phone number of the NE.
SMS Profile: NE SMS profile.
Packet Switched Settings: NE PS profile.
Page 142
M0125ANA.DOC
6.9.3.2
Change Connectivity Mode to Packet Switched On Demand
To change to packet switched on demand connection, proceed as shown in this

example:
Step 1: Check in Tools / Connection Manager whether the needed PS

Profile, the SMS Modem Group and the SMS Profile are created. If not create
them.
Step 2: Click Edit NE to edit the settings of the NE.
Step 3: Select connectivity mode Packet Switched On Demand.
Step 4: Select an SMS-capable SMS Modem Group in Dial Out Modem

Group. This is necessary to send a wake-up-SMS to the NE to get the IPAddress of the NE.
Step 5: Select the PS Profile in Packet Switched Settings.
Step 6: Select the SMS Profile in SMS Profile. The SMS Service Center
Number will be then read out from the SMS profile.
Step 7: Customize the other settings. Ensure there are no red marked lines.
Step 8. Confirm the window with OK.
Step 9: A.I.M.O.S. will establish a connection to the repeater showing the

progress in an information window. Wait until A.I.M.O.S. displays the PS IP
Address/IP Port transmitted from the repeater. The PS-connection is possible
when the IP-Address is transmitted or manually entered.
Page 143
6.9.4
Local Area Network
NE is within the same LAN like A.I.M.O.S. This example shows connectivity settings
of an ION-M.

Common Connectivity
OMC IP Address: A.I.M.O.S. IP address.
OMC IP Port: A.I.M.O.S. IP port.
LAN IP Address / Port: IP address and IP port of the NE connected via LAN.
Page 144
M0125ANA.DOC
6.9.5
Common Features and Settings for all Connection Types
6.9.5.1
Buttons
Sync NE: Click to synchronize the data from A.I.M.O.S. with the data set in the NE.
An information window will pop up showing the processing of the job status. The
status of the synchronizing will be marked additionally in the column Job Status of
the NE Tree.
Edit NE: Click to edit or to change the connectivity mode and/or the parameters of
the NE.
6.9.5.2
WEB-Login Configuration
Choose the NE WEB Login

Profile for the selected NE.
For more information on this
profile type refer to chapter
5.3.3.5.
The example to the right is
taken from a Circuit Switched
connection.
Note: To set up an individual WEB-Login Configuration, select <no matching profile>
to make the fields "Username" and "Password" visible / editable.
6.9.5.3
Alarm Type
Alarm reporting mode used by the NE; for restrictions see chapter 5.2.
Notification = unacknowledged mode. Alarm delivery is not reliable, an alarm can get
lost along the transmission over the network.
Inform = acknowledged mode. Alarm delivery is reliable; every alarm will be
retransmitted if necessary until A.I.M.O.S. confirms the delivery. Only if this type is
chosen, the options Inform Timeout & Inform Retries are available for NEs supporting
these features:
Inform Timeout: Set the period the NE shall wait if A.I.M.O.S. is not responding to
an Inform message until the NE tries to send the message again.
Inform Retries: Set how many times an NE shall retry to send an Inform message if
A.I.M.O.S. is not responding until the NE stops trying.
6.9.5.4
Zone Change Traps
If the check mark is set, the NE will send a trap each time it changes the zone. It is
recommended to use this option only if absolutely necessary as it might result in a
high number of traps being sent out.
Page 145
6.9.5.5
WEB Server Configuration
Select which type of encryption is used by A.I.M.O.S. for accessing the
corresponding NE selected in the NE Tree. Choose between:
- HTTP only
no encryption
- HTTPS only
HTTPS encryption will be used *

- Standard
Depending on the NE configuration: A.I.M.O.S. either uses

HTTP w/o encryption, even if an NE supports HTTPS (e. g. Node AM;
in that case HTTPS can only be used from external sources), or
automatically chooses HTTPS encryption for NEs supporting HTTPS.
* Please make sure that the selected NE supports HTTPS when choosing this
encryption type and that a certificate installation is required for using HTTPS. For a
detailed description refer to chapter 14.
6.9.5.6
Additional Information
These data are read only. Extended information, e. g. on the Revision Info, is
available in the Maintenance tab (see chapter 6.8.3).
Sync Age: Date and time of the last synchronization.
Software Version (formerly Agent Version): Version of the NE SNMP Agent
Current MIB Version: Version of the NE-specific SNMP management information
base (MIB).
WIP MIB Version: SNMP MIB version of the manufacturer used for A.I.M.O.S./NE
communication (Common Part).
Sys Description: Short description of the NE.
Sys Contact: Contact info for technical support for the NE.
Sys Location: Location info of the NE.
6.9.6
VPN Connectivity Parameters
For NEs supporting VPN connectivity, the VPN section is provided below the
A.I.M.O.S. section. When the corresponding check-mark is set and the setting is
confirmed, the VPN parameters are displayed and can be edited via the Edit NE
button:
Page 146
M0125ANA.DOC
When the check-mark is removed, the latest settings will be displayed:
The following parameters can be edited:

Protcol: Specifies the VPN protocol: 0 = VPN is not supported; 1 = UDP; 2 = TCP
Main Server [x]* IP Address: IP address of main VPN server of VPN Server Group
No. [x]. This server is contacted first. If connection fails (TIMEOUT), the
UVS_BackupServerIP is contacted.
Main Server [x]* IP Port: IP port of main VPN server of VPN Server Group No. [x].
Backup Server [x]* IP Address: IP address of VPN backup server of VPN Server
Group No. 1. This server is only contacted if UVS_MainServerIP of VPN Server
Group No. [x] cannot be reached.
Backup Server [x]* IP Port: IP port of VPN backup server of VPN Server Group
No. [x].
[x] stands for Server / Group numbers 1-4.
The following parameters are not editable:

Current Server IPAddress: VPN Client IP address of the NE
Server Assignment State: This field shows if the NE is assigned to a VPN Server
Group: 0 = VPN is not supported; 1 = unassigned; 2 = assigned
Assigned Server Group: Group No. of the VPN server the NE is connected to
Connection Mode: Shows if VPN is actually active or not: 0 = VPN is not supported;
1 = failed; 2 = VPN mode is secure
VPN IP Address: IP address of the VPN server the NE is connected to
Page 147
6.10
TOOL SCHEDULER (OPTION)
This optional tool is designed for the automization of Network Element Operations
and to execute configuration changes on multiple NEs. Desired times for such
operations can be set. The time schedule is configured and edited in the Scheduler
menu of A.I.M.O.S. When this tool is licensed, alarm polling is available in the
Scheduler only, and the parameters displayed in the Preferences Editor (chapter 5.2)
will change accordingly.
Access to this tool and its features can be configured in the Account Manager rights
as explained in chapter 5.4.2.
Start All Programs Andrew A.I.M.O.S. Visualization.
In the A.I.M.O.S. Visualization select Tools / Scheduler.
Schedule Info: General information about the schedule. *

The following two fields are created automatically and cannot be changed:
Date and Time of Creation: Date and Time of the schedule creation.
Created by user: Name of the user who created the schedule.
Schedule Settings: Information about the time schedule settings. *
Next Retry Run Time: Indicates when the next retry after a failed run is scheduled.
Manual Start: To start a schedule manually, click the Start Now button.
Schedule Connectivity Settings: Information about the connectivity settings. *
* see tab Schedule (chapter 6.10.1.1) for more detailed explanations
Page 148
M0125ANA.DOC
Buttons:
Click New to create a schedule (see next chapter).
Click Edit NE Filter to modify the filter criteria of a schedule (see chapters 6.10.1.2
and 6.4.3.2).
Click Edit Actions to edit the Scheduler actions (see chapters 6.10.1.3 and 6.10.3).
Click View Runs to display the progress and result of a schedule in the Schedule
Runs window.
Click Start Now to start a schedule manually.
To create a new schedule, either click the New button or use the menu item
Scheduler New Schedule. Then, continue as follows:
6.10.1
Customizing a Schedule
6.10.1.1
Step 1: Tab Schedule - Customize the Schedule
Name: The first schedule name will be created automatically as Schedule 101. The
number is incremented automatically when creating additional schedules. The name
should be changed to indicate the purpose of the schedule.
Comment: This optional entry field can be filled with additional information to further
identify the schedule.
Page 149
Schedule Kind: Choose between four options:

Choose XML-Import to import XML files into the A.I.M.O.S. database. For details
see chapter 6.10.2. (The tabs Network Elements and Actions are not required and
will thus no longer be provided for creating this schedule.)
Choose Network Element Actions to customize the available NE Actions in tab
Actions (see chapters 6.10.1.3 and 6.10.3).
Choose System Actions to customize the creation of performance data charts.
Consequently, in tab Actions (see chapter 6.10.1.3) only this specific action is
available (see chapter 6.10.3.5) and the tab Network Elements is not required. It
will thus no longer be provided for creating such a schedule.
Choose Export Actions to make the action Create Export (see chapter 6.10.3.8)
available.
Time Plan Settings: Select a time interval Once, Several Times a Day, Daily,
Weekly, Monthly the schedule shall run. Default setting is Once. Define the start
time of the schedule with the calendar.
Next Run Time: This field indicates the next execution date and time according to
the Time Plan Settings with the check-mark enabled.
Failed Run: Number of Retries: Set the number of retries for the schedule.
Failed Run: Retry Interval: Set the interval between the retries for the schedule.
Enabled: Set the check-mark to enable the schedule.
Connectivity Settings:
Modem Group Name: Leave this field empty (= default) to force the Scheduler to
maintain circuit switched connections as defined for each NE. If the schedule should
run using a separate Modem Group for circuit switched connections, specify that
group here.
Modem: Max. Wait Minutes: This setting defines the max. time the scheduler will
wait to acquire access to a modem.
Modem: Max Connect Attempts: Maximum attempts to connect a single NE.
NE: Sequential Delay Seconds: Interval time between finishing a scheduled job
(NE A) and starting another scheduled job (NE B) within the same schedule; valid for
all connection types. The default setting of 0 minutes is recommended because
otherwise (setting >0) the NEs will be processed sequentially and not in parallel,
which might lead to a slow performance.
Possible use case: The activation of the heartbeat can be distributed in a time range
of 24 hours. The heartbeat of 100 repeaters shall be sent to A.I.M.O.S. once a day.
A sequential interval value of 600 seconds will distribute the execution of the
heartbeat activation to ensure a consistent workload of the connection.
Page 150
M0125ANA.DOC
6.10.1.2
Step 2: Tab Network Elements - Customize the Network Elements
The available filter criteria that can be set in the Schedule Wizard are exactly the
same as in the filter builder of the NE Tree. For a detailed description of them please
refer to chapter 6.4.3.2 Filter Settings.
To select a filter click the respective filter tab under the menu bar. Use the arrow
button
to scroll through the tabs if the list is longer and exceeds the screen width.
Use the buttons Add or Delete to add or to delete a filter.
Click
to get the amount of repeaters
matching your filter settings:
Use the button Show in Tree to visualize your filter definition in the NE Tree.
Upon leaving the Scheduler you will be asked whether this filter definition should
become a Custom Filter in the NE Tree as if it was created by the NE Filter Builder
(described in chapter 6.4.3 Network Element Filter) or not.
Note: If you decide to make it the custom filter definition, please consider that only
one custom filter is possible.
As default, filters are created as dynamic filters by the Schedule Wizard. For
converting a dynamic into a static filter the Convert into Static Filter button is
provided. For details about filter types and their conversion refer to chapter 6.4.3.4.
Page 151
6.10.1.3
Step 3: Tab Actions - Customize the Actions
Select one or more

action(s) the scheduler
shall run. For more
details
on
the
Scheduler Actions see
chapter 6.10.3.
Note: When System
Actions is chosen as
Schedule Kind in the
Schedule tab of the
Schedule Wizard (see
chapter 6.10.1.1), only
the
action
Create
Performance
Data
Chart (see chapter
6.10.3.5) is available.
All available schedule actions are listed left-hand. Mark the action you want to
perform and click Add. It will be listed in the selected schedule actions right-hand.
Some actions require additional settings. To customize those actions press the Edit
button. If this button is disabled (gray), there is no need for additional settings.
Use the buttons Up and Down to change the order of the selected schedule action.
Use the button Delete to remove an action.
Not until Schedule, Network Elements, and Actions are completed, the button OK will
be activated.
Step 4: Click OK: Use Cancel to abort the Scheduler.
Page 152
M0125ANA.DOC
6.10.2
XML Import
Three different types of XML imports are available; sample XML files for all are
available in the folder \Program Files\Andrew\A.I.M.O.S.\XML. Depending on the file
type selected in the field XML Import File Name, the according type will be
displayed accordingly in the XML Import Type field. The available file types are:
New Network Element(s): The creation of this type of file for xml import is
described in section 6.2.1 File.
Node G Frequency Setting(s): The creation is user-specific. The creation of
this type of file for xml import is described in section 6.2.1 File.
Importable xml file. The creation of this type of file for xml import is described
in section 6.10.3.8 Create Export.
The same folder also contains the corresponding XML-Schemas (.xsd). The XMLSchema is used to express a set of rules to which the XML document must conform
in order to be considered 'valid'.
DO NOT MAKE ANY CHANGES IN THE XML SCHEMAS (.xsd).
XML files can be edited with an XML Editor (e.g. Microsoft XML Notepad).
Page 153

Sample of an XML Schema:
a) Import of new Network Elements (NEs)

This import can be used
for bulk integration of
NEs.
Fill XML file with
required
data
(component name, type
of NE Type, Connection
Type, IP Address, IP
Port, Modem Group,
Modem, Phone Number).
See sample file for
details.
In the Schedule Wizard, the

field XML-File Location
must be set to Client:
Page 154
M0125ANA.DOC
Press Import XML button.

Define/able schedule for auto-integration of NEs into A.I.M.O.S.
b) Import of Node G channel settings

This import can be used
for (recurring) changes of
NodeG channel settings.
It is recommended
to create/fill the XML file
via a frequency planning
tool.
In the Schedule Wizard,
the
field
XML-File
Location must be set to
Client, as shown under
c).
Press
button.
Define/able schedule for

(recurring)
changes
of
Node G channel settings.
Import
XML
Page 155

c) Importable xml file
o The file to be imported must be located in ~\Andrew\AIMOS\UploadFiles\OMC,

i.e. if the file to be imported is generated automatically and is also to be imported
automatically (= without changing the schedule), the file must always be available
in this location under the same name.
o In the field XML-File Location, the setting Server is obligatory. If it is not
possible to select a file or not the file desired in the next field XML Import File,
check in the Connector Log file or in the Log Manager whether validation of this file
was successful. In case validation has failed, the log shows the message Failed to
parse. Additionally, the log contains information as to why validation has failed.
Only if errors have occurred, the Schedule Wizard must be started anew after they
have been corrected; then, selecting the file will be possible.
If an xml file that has already been selected in the Scheduler is changed later, the
file is automatically validated afterwards. In case of an error the corresponding
error message Failed to parse will also be shown in the Connector Log file. In
case of a successful validation the message (also when the schedule is started) is:
Reflect [x] changes to the database. Please note: in case of a validation error no
View Runs entry will be made as the prerequsites for a Run have not been
fulfilled.
Page 156
M0125ANA.DOC
o Irrespective of the XML validation by A.I.M.O.S., validation can also be done

separately using a suitable XML Tool and the XML schema
~\Andrew\AIMOS\XML\AIMOS_Import_CM.xsd. In case of an automated
generation of the file to be imported, validating the generated file automatically with
the schema provided and a suitable XML Tool before the import is recommended.
o Validation is done both when the schedule is generated and when it is executed.
For more details and for xml export information, see also chapter 6.10.3.8 in this
manual
as
well
as
document
XML
Interface
Description
(M0125B7x_XML_IF_AIMOS_Vx.pdf).
6.10.3
Scheduler Actions
The Schedule Actions Editor opens when the Edit Actions button in the main
window of the Scheduler is clicked. The available choice of actions can vary
depending on the system configuration and on the selection made under Schedule
Kind in the Schedule tab of the Schedule Wizard (see chapter 6.10.1.1):
Note: For a better overview, the list of

displayed actions can be reduced by
entering a short keyword (e.g. RSSI) in
the Available Actions Filter field, and
only the actions corresponding to this
keyword will be shown.
To edit an action, highlight it in the left part of the window and click the Add button.
The highlighted action is then displayed in the right part of the window, as well, and
can be edited by clicking the Edit button. If this button is disabled (gray), there is no
need for additional settings.
Page 157

In the Actions tab of the Schedule wizard (see chapter 6.10.1.3) an action can be
selected for a schedule.
Some actions are uniquely available in the Scheduler and will be explained
individually, i.e.:
Event Triggered Actions
see chapter 6.10.3.1
File Upload
Software Update
Read Performance Data
Currently only available for Node C, G, or M except two-box (DCM1 units) with a SW version <1.5.
Create Performance Data Chart
Uniquely available when System Actions is chosen as Schedule Kind in the Schedule tab of the
Schedule Wizard (see chapter 6.10.1.1).
Configure Node A User
Available for Node A only.
Configure ION-M User
Suppress Mobile Radio Signal
Use this action to switch off the RF during

certain time periods.
Copy NE Configuration
see description below
Use this action to select an NE backup file (created before) in order to transfer it
to other NEs (of the same type):
Available for NEs of the NodeX type only.
Create Export
Only available when Export Actions is chosen as Schedule Kind in the Schedule tab of the
Schedule Wizard (see chapter 6.10.1.1).
Run External Tool

Use this action to start external tools (e.g. exe or batch
files) via A.I.M.O.S. A corresponding profile must have been
created in the External Tool Profiles (see chapter 6.17.6) before.
Select the External Tool

Profile to be executed and confirm with OK.
Page 158
M0125ANA.DOC
Most of the actions correspond to a Network Element Operations (accessible by a
right-mouse click or via the menu Tree Network) or to a feature in a tab of the
Functions Bar. These actions and the corresponding operation / feature are:
Scheduler Action
Try Connection
Send Config SMS
Read Unique System ID
Read Network Structure
Query All Params
Query Actual State
Query Alarms
Read Hardware Inventory Data
Synchronize Time
Reboot Network Element
Create NE Configuration Backup
Network Element Operation

Try Connection
Send Configuration
Query All Unique System ID
Read Unique System ID
Query All Network Structure
Query All Parameter Settings
Query All Current State Values
Query All Active Alarms / Query Alarms
Read HIDs
Set Time *
Reboot
Backup
* In the NE operation the time can also be set freely, while the Scheduler action always sets the
current time.
For details refer to the corresponding Network Element Operation in chapter 6.7.
Scheduler Action
Tab Configuration
Configure Alarm Severity
Alarm Settings
Configure Heartbeat
Heartbeat
Read HW/RF Data
HW-RF / Sync NE
Set Frequency Allocation for Node x (not available for all Node
A types)
HW-RF
Set Pilot Power to Total Power Ratio for Node x
Configure A.I.M.O.S. Dial-In (use to set Dial-In parameters)
Configure NE Connectivity (use to set the parameters Alarm
Type, Inform Timeout, Inform Retries, Zone Change Traps,
WEB Server Configuration, as well as the VPN Connectivity
Parameters).
Scheduler Action
Restore Most Recent Backup
For details refer to the corresponding feature in chapter
6.9 Configuration - Connectivity, or 6.8.3 Maintenance.
6.10.3.1
Connectivity
Connectivity
Tab Maintenance
Backup/Restore
6.8.2 Configuration,
Event Triggered Actions
In case the Event Triggered Actions are selected, one of the following actions will be
performed depending on the selection made under having received event: in
Step 2 (see chapter 6.10.1.2).
Page 159

a) Alarm: System Configuration Changed
If the NE has sent a config has changed message, an automatic sync between NE
database and A.I.M.O.S. database will be triggered by performing the following
commands:
Read Network Structure (=Topology)
Query all Params
Query Actual State
Read Hardware Inventory Data
b) Alarm: CA List Change Alarm

If the NE (Node G only) has sent a 'CA list change alarm'-'clear' (!) trap, the following
action is performed:
Read HW/RF Data
Page 160
M0125ANA.DOC
c) Notification: System Startup
If the NE has sent a system is up and running message,
or
d) Alarm: Alarm Queue Overflow
If the NE (ION only) has sent an 'Alarm Queue Overflow' message,
this schedule triggers an automatic alarm sync by performing the following action:
Query Alarms
e) Alarm: System Replaced

This action will send the according configuration file (as determined by the selected
Configuration Group; see chapter 6.4.3.2 Filter Settings) to the NE. From A.I.M.O.S.
V2.5 this feature is only available for Node AM repeaters, however, further NEs may
be included in future releases.
f) Clear: System Off Duty
If the NE Alarm 'System Off Duty' has been cleared (currently Node AM only),
A.I.M.O.S. triggers an automatic sync between NE database and A.I.M.O.S.
database, performing the following commands:
'Read Network Structure' (= Topology); not applicable for NodeAM;
'Query all Params'
'Query Actual State'
'Query Alarms'
'Read Hardware Inventory Data'
'Read HW/RF data'
Note: Once the Event Triggered Actions are selected, the detailed actions (which
show up in brackets) are performed automatically, it is NOT required to add any other
actions. Nevertheless it is possible to add other actions too.
Page 161
6.10.3.2
File Upload
To upload configuration files to NEs from A.I.M.O.S. an according schedule has to be

customized in the Scheduler (a schedule is also required for a manual upload start).
Before starting with the schedule, make sure that the required configuration files
have been made available at the A.I.M.O.S. server via the following path (NodeA for
NodeA/-AM or MC for ION-M):
Then, create a schedule for the upload by clicking the New button and proceed as
follows:
1. Tab Schedule
Enter a name for the Schedule and the Time Plan Settings. Regarding the Time Plan
observe that there are two options.
If desired, the time for the file upload can be explicitly set by entering the specific
time and date. However, the schedule can also be used to start uploads manually
(which will be the more common practice) by entering a point in time in the past in
this field and setting the Run Schedule field to Once.
If a time in the future was set, the Next Run Time (formerly Next Execution
Date/Time) will be displayed in the according field after the Schedule is Enabled by
setting the check-mark. The field stays empty after enabling if a time in the past was
set.
Page 162
M0125ANA.DOC
2. Tab Network Elements
Enter the Type and Sub Type of the NE for which the upload shall be carried out in
the according fields.
3. Tab Actions
Choose the action Upload Repeater File and click the Add button. When the action
is displayed under the Selected Schedule Actions, click the Edit button:
Select the configuration file for the according NE type and confirm with OK:
The schedule is now customized. Confirm the Schedule Wizard with OK.
Page 163
If the Time Plan Settings were set to a time in the past, the following message will be
prompted:
If this message is answered with Yes, the set Time Plan Settings will be ignored and
the upload will start automatically at an early point in time set by the system. To be
able to start the upload manually, answer this message with No.
Page 164
M0125ANA.DOC
4. Starting the File Upload
To start the upload manually, select the according schedule in the Scheduler (by
clicking in a field of the corresponding schedule column) and click the Start Now
button of the Schedule Settings (see chapter 6.10).
By clicking the View Runs button the progress of the upload will be displayed in the
Schedule Runs window:
When the upload is finished, this will also be stated in the Schedule Runs window.
To see more details (or in case the upload could not be completed successfully), use
the buttons View Results or Log Manager (see also chapter 6.13 Tool Log
Manager) where more extensive information will be provided.
Page 165
6.10.3.3
Software Update
To carry out a software update from A.I.M.O.S. for a certain type of NE an according
schedule has to be customized in the Scheduler (a schedule is also required for a
manual update start).
Before starting with the schedule, the required update file (zip format) which has
been provided by CommScope must be filed in the corresponding folder of the
A.I.M.O.S. server.
Thus, after having received the zip file from CommScope, file it under:
For a Node A update, file the corresponding zip file in

the NodA folder, which also serves for Node A+ or
Node AM update files
The MC folder is provided for ION-M update files.
An update via A.I.M.O.S. is not possible for other NE
types (Node C, G, M, MRx18, or ION-B).
Creating subfolders for various update files is not
necessary as each zip file can be uniquely
distinguished by its name which includes the NE type
and SW version, e.g.:
For ION-M the name of the file is ION-M_Vx.y.z.zip, where x.y.z represents
the SW version to be uploaded. Depending on the Update contents two files
may be provided, which have the same name but differ considerably in size. In
this case, using the smaller file is recommended for A.I.M.O.S.
Please consider in advance whether the update should be carried out in two steps
(first, all the update files will be transferred to the individual NEs one by one, and in a
second step, which can also be started later, the update will be activated in the NEs)
or whether the update should be activated in an NE directly after the files were
transferred (immediate activation) *. Please observe, however, that in the latter case
the time span between the activation of the SW update of the first and of the last NE
in line is very long, since much time must be calculated for the file transfer. If the files
are transferred in a first step to all NEs, the time span for the activation procedure
itself will be much shorter.
*
For NEs of type Node A only the immediate activation is available; for Node AM and Node A+ both
schedule options are possible.
In any case, a schedule must be created for the update by clicking the New button
and proceeding as follows:
Page 166
M0125ANA.DOC
1. Tab Schedule
Enter a name for the Schedule and the Time Plan Settings. Regarding the Time Plan
observe that there are two options.
If this is desired, the time for the SW update can be explicitly set by entering the
specific time and date. However, the schedule can also be used to start the update
manually (which will be the more common practice) by entering a point in time in the
past in this field and setting the Run Schedule field to Once.
If a time in the future was set, the Next Run Time (formerly Next Execution
Date/Time) will be displayed in the according field after the Schedule is Enabled by
setting the check-mark. The field stays empty after enabling if a time in the past was
set.
2. Tab Network Elements
Enter the Type and Sub Type of the NE for which the update shall be carried out in
the according fields.
Page 167

3. Tab Actions
Choose the action Update Repeater Software and click the Add button. When the
action is displayed under the Selected Schedule Actions, click the Edit button:
Select the NE Type to be

updated (Node A must be also
chosen for Node AM or
Node A+).
Depending on the NE Type

chosen, the system prompts
the available update files (file
format .zip) for this type in
the SW File field. Select the
correct zip file for the NEs to
be updated.
Page 168
M0125ANA.DOC
In the field Mode select the update mode:
If the update should be carried out in two steps (first file transfer to all NEs and then
activation), choose the option Upload. If the activation for each NE should start
directly after the file transfer, choose the option Upload with immediate Activation
(observe that if a Node A SW File has been selected, only the immediate Activation
mode is possible).
Confirm your choices with OK.
This schedule is now customized. Confirm the Schedule Wizard with OK.
If the Time Plan Settings

were set to a time in the
past,
the
following
message
will
be
prompted:
If this message is answered with Yes, the set Time Plan Settings will be ignored and
the SW update will start automatically at an early point in time set by the system. To
be able to start the SW update manually, answer this message with No.
4. Activating the SW Update
If the option Upload with immediate Activation was selected in step 3, only this
schedule is required. In this case please proceed directly with step 5.
Otherwise, a second schedule must be created for the activation.
To do so, repeat steps 1 to 3 as explained above but observe the following:
Page 169
In the tab Schedule

(step 1) the name
entered
for
the
schedule must differ
from the name of the
first schedule, e. g.:
In tab Actions (step 3) choose the
action Activation.
Then, continue as explained in the
above before proceeding with step 5.
5. Starting the SW Update

To start the update manually, select the according schedule(s)* in the Scheduler (by
clicking in a field of the corresponding schedule column) and click the Start Now
button of the Schedule Settings (see chapter 6.10).
* If two schedules have been created for the SW update (file transfer and activation separate), start
the file transfer, first, and after the transfer is finished start the schedule for the activation. It is also
possible to wait some time in between the two schedules.
By clicking the View Runs button the progress of the upload will be displayed in the
Schedule Runs window:
When the upload is finished, this will also be stated in the Schedule Runs window.
To see more details (or in case the upload could not be completed successfully), use
the buttons View Results or Log Manager (see also chapter 6.13 Tool Log
Manager) where even more extensive information will be provided.
Page 170
M0125ANA.DOC
6.10.3.4
Read Performance Data
Explanation:
Performance data are saved to the A.I.M.O.S. database and can then be used by the
Tool Performance Manager (Option) described in chapter 6.16, if this tool is licensed
(Node X and ION). In addition, csv files are saved to the hard disc of the A.I.M.O.S.
server (Node X only).
For NEs of the Node X type observe the following:
Before carrying out such a schedule, the corresponding performance data to

be queried have to be configured on the website of the Node. For details on
performance data configuration, see Software Manual of the Node X.
If the data are to be used for comparative purposes, make sure that all Nodes
are set to the same time (UTC time, not local time). To set the correct time,
use the NE Operation Set Time (see section 6.7).
In case of a Node AM, the GPS statistics will be queried as well and written
into the A.I.M.O.S. folder on the A.I.M.O.S. server. They will not be used by
the Performance Manager.
Application:
If no Performance Manager license is installed, only the (Node X) csv files can be
used for evaluation with a 3rd party tool (e.g. Excel).
With a Performance Manager license performance data can be evaluated with the
tool Performance Manager (see chapter 6.16).
Do not use this action at an interval of <15 minutes since the minimal measurement
interval is currently 15 minutes.
Procedure:
Start the Schedule action as explained in chapter 6.10.1.3 and the following steps will
be carried out automatically:
Node X only:
At the first start, all available data dating back up to one week are saved to the hard
disk (~\Andrew\AIMOS\Bin\NodeXStatisticsDownload) of the A.I.M.O.S. server as
"[NE Unique System ID]_[date of performance data, 8-digit].csv".
Node X and ION:
All data are saved to the A.I.M.O.S. data base and can be graphically visualized
by the Performance Manager.
Logging:
Failure, warning and other information messages are stored in the Log Manger tool
(see chapter 6.13). In case of failure, please send the generated file(s) to Technical
Support (see also chapter 10.2).
Page 171
6.10.3.5
Create Performance Data Chart
This action is uniquely available when System Actions is chosen as Schedule Kind in
the Schedule tab of the Schedule Wizard (see chapter 6.10.1.1).
It can be used to generate charts * pre-defined in the Tool Performance Manager
(Option) described in chapter 6.16 to be sent out via mail at specified intervals.
*
For NEs of the Node X type the Read Performance Data schedule (see section 6.10.3.4) must be
carried out before these charts can be provided by the Performance Manager.
Upon adding the action to the Selected Schedule Actions (Add button) and clicking
the Edit button, the following window will open:
Chart Name: Select a chart from the list. This list contains all charts available in the
Performance Manager.
User Name: Select the user from the list.
eMail Receipient: Enter a mail address to which the created charts should be sent.
For general information about customizing an action please refer to chapter 6.10.1.3.
Page 172
M0125ANA.DOC
6.10.3.6
Configure Node A User
Use this action to configure (or change) up to 6 users for Node AM* Network
Elements by specifying Role Name, User Name and Password. Configuring User 1
(= Super User) and User 2 (= Operator User) is mandatory, all other users are
optional. A user for whom no data are entered (marked <empty>) will not be created.
*this action is currently not available for other NE types
Note: Please observe to enter all data completely in this mask since only the data
entered here will be valid after the scheduled action has been performed. Thus, when
a single user is to be changed make sure the data for all the other users are still
specified correctly in the schedule, otherwise they will be changed, too, according to
the data in the schedule or even deleted if they are marked <empty>.
Thus, to delete a User remove all entered data so that it will be again marked
<empty> before performing the action again.
Use the field WEB User Management to activate / deactivate the configuration of a
Node AM via Web.
For changing passwords please observe that the following restrictions laid down in
the tab Security of the Server Configuration (see 5.1.3.1) do also apply here:
- General Password Settings
- Minimum Password Length *
- Password Security Level
*
Please observe that for this action the value entered for the Minimum Password Length must not
exceed 16 characters.
Page 173
6.10.3.7
Configure ION-M User
Use this action to configure (or change) a user for ION-M Network Elements by
specifying User Manager, Password Duration in Days, User Name, Password, and
Password Expiration.
The following entries are possible:

- The User Manager can be entered solely only the User Manager will be
adjusted.
- Duration can be entered solely only the Duration will be adjusted.
- User Name and both password fields can be filled in solely on all MCs with the
corresponding User the password will be adjusted.
- User Name and expiration fields can be filled in solely on all MCs with the
corresponding User the expiration will be adjusted.
- The four rules above can be combined without restrictions.
Notes:
If User Manager = AIMOS, the passwords must be 8 digits long and correspond to
the Password Security Level set in the Server Configuration / Configuration Tool (see
chapter 5.1.3.1 Password Settings).
If User Manager = NE, the password must be 8 digits long and correspond to the
following Security Level of the Server Configuration / Configuration Tool (see chapter
5.1.3.1 Password Settings):
Page 174
M0125ANA.DOC
6.10.3.8
Create Export
When Export Actions is chosen as Schedule Kind in the Schedule tab of the
Schedule Wizard (see section 6.10.1.1), the action Create Export by which most
exports of the Tool Network Element List (section 6.11) can be executed
automatically is available.
As for all other scheduled tasks the following criteria are specified via the Scheduler
homepage (see page 148) and in the Schedule Wizard:
The time of execution for the export is defined in Step 1 of the Schedule Wizard
under Time Plan Settings (see also section 6.10.1.1).
Network Elements to be included into the export are selected via the Edit NE
Filter button of the Scheduler homepage ( see also Step 2 of the Schedule
Wizard, section 6.10.1.2).
Choose the action Create Export to specify how data are to be exported and
depending on the Selected Schedule Action, proceed as follows:
A) Create Network Element List Export
These exports can be configured in the Export Profiles of the Tool Profiles (section
6.17.5).
Configure the Create Export window as follows:
Profile Name: All profiles created in the "Export Profiles" (section 6.17.5) are
available.
Destination: Specify the destination to which the data are to be exported. A write
permission for the selected folder is required.
Type: Define the type of document (xml or Excel) to be created.
B) Create Importable XML Export

For details and for xml import information, see also chapter 6.10.2 in this manual as
well as document XML Interface Description (M0125B7x_XML_IF_AIMOS_Vx.pdf).
The following example illustrates how an xml export is done by configuring the
corresponding schedule:
Page 175

a) Schedule Tab
b) Network Elements Tab
Page 176
M0125ANA.DOC
c) Actions Tab
Step 1: Press Edit button and select folder to which xml file should be saved:
Page 177

Step 2: If you want to start the schedule right away, click the Start Now-Button,
otherwise use the Time Plan Settings for this schedule:
Step 3: When the Schedule is finished (this may take some time), the xml file is
saved in the folder specified in step 1.
Page 178
M0125ANA.DOC
6.11
TOOL NETWORK ELEMENT LIST
Access to this tool can be configured in the Account Manager rights as explained in
chapter 5.4.2.
In A.I.M.O.S. Visualization select Tools / Network Element List.
This tool gives an overview of all installed NEs and their subunits. By default all
network elements are displayed. Use Select a View to choose a specific view from
the list box.
The listing can be customized by sort options and filters.
Note: For setting filters to customize the screen display and for saving this
customized view, refer to chapter 6.4.1 Table Filters.
With the different tabs filtered views can easily be displayed.
Via the Export Profiles (of the Tool Profiles) and the Scheduler Action Create
Export exporting these views is also possible. See sections 6.17.5 and 6.10.3.8.
Buttons:
Button Show in Tree serves to use the filtered NE List as a filter for the NE Tree.
Button Locate highlights the selected device in the NE Tree.
Button (Excel-)Export saves the sorted and filtered data into an Excel file.
Button Refresh updates the displayed list.
Page 179
6.12
TOOL JOB MONITOR
In A.I.M.O.S. Visualization select Tools / Job Monitor.
This tool lists all current
jobs. The list of jobs can
be saved as Excel file
with the (Excel-)Export
button.
Set the Fade Out time
in seconds to adjust the
time, jobs are listed after
their completion.
6.13
TOOL LOG MANAGER
The Log Manager displays the complete logs that are generated by the A.I.M.O.S.
Connector service. Access to this tool can be configured in the Account Manager
In A.I.M.O.S. Visualization select Tools / Log Manager.
Click the buttons

Prev Anomaly or
Next Anomaly, to
highlight Warnings
and Errors, and to
jump to previous
or following ones.
The tool is also accessible as follows:

as menu item:
by a right mouse-click in NE Tree or via menu Tree
as button: in the Connectivity Manager in the window opened by Discover
Modems (see 5.3.1)
in the dialogue for creating new NEs (see 6.5)
in all windows opened by NE Operations except Delete Pending
Configuration Data
Page 180
M0125ANA.DOC
Timestamp: Date and/or time the log event occurred.
Message: Log/Alarm message.
Severity: Possible states of the severity can be: Info, Warning, Error, Severe. Please
note that these states are not identical with the alarm severities of the NEs
configured in A.I.M.O.S.
NE Number: An automatically generated A.I.M.O.S. internal number of the NE.
SDN: The system distinguished name (SDN) is an A.I.M.O.S. internal identification
name of the NE.
Component Name: The user defined name of the NE.
Thread: Short name of the functional module of the Connector service; useful to
identify the general domain that a log line applies to.
Thread Name: Like Thread; long name.
Direction: The direction will be displayed only if any communication takes place. The
following directions can be displayed: SB out, SB in, SNMP NB, NB out, NB in,
Unspec in, Unspec out.
Log Kind: Specifies the kind of the log. The following log kinds can occur:
communication = interpreted data by the Connector service;
communication raw: uninterpreted data;
connectivity = belongs to dial-up;
data base = the Connector service accesses the database;
program condition = each kind which can not assigned to one of the possible log
kinds.
Command: Displays the command which caused this log line.
Modem Number: An automatically generated A.I.M.O.S. internal identification
number of the modem.
Communication Resource: Displays which communication takes place, Modem or
LAN.
User Number: An automatically generated A.I.M.O.S. internal identification number
of the user.
MCNC: The A.I.M.O.S. internal unique identifier for network providers consists of the
MCC and the MNC.
User Name: Displays the user sending the command shown in column 'Command'.
Automatically generated alarms are not allocated to a user name.
Schedule Run: Logs that were created by the Scheduler are listed in this column.
Note: From V2.6 onwards Account Manager actions as well as Visu logins and
logouts will also be logged in the Log Manager.
Check Boxes
These two check boxes are helpful if it is necessary to view logs lines exactly.
Active: Remove the check-mark to deactivate the log recording. After setting the
check-mark again the log manager will start listing again. The logs accumulated
during the break remain in the Connector service cache.
Autoscroll: Remove the check-mark to deactivate the automatic jump to the last line
of the log list. Set the check-mark to activate the autoscroll again.
Page 181

Buttons
Clear: Clears the window. The logs will not be deleted permanently in the Connector
service.
Excel Export: Saves the visible logs as Excel file.
Log Files: The logs will be saved automatically every day. Use this button to open a
specific log file as csv-file. The most recent 30 log files are listed and sorted by date.
Double-click a date or click Get the File to open the zipped file in a new window.
Open the displayed csv-file in Excel with a double-click.
Log Profiles: The selected profile determines the content and volume of the logs.
Possible Profiles are: Minimum, Standard, Extended and Maximum. It is
recommended to select Minimum or Standard for the operating state. Extended or
Maximum should only be set after consultation with Andrew support.
6.14
TOOL MAP (OPTION)
Please observe that this tool has to prepared (before A.I.M.O.S. is installed) as
explained in chapter 4.1.2 Map (Optional Tool) and that access to this tool can be
configured in the Account Manager rights (chapter 5.4.2). The possibility to drag and
drop NEs to this tool depends on the Topology rights of the Account Manager.
The tool Map allows displaying all NEs with their location in maps.
Prior to using tool Map:
- a license for A.I.M.O.S. with Map has to be installed
- Microsoft MapPoint 2006 or 2009 with the correct maps (e.g. for Europe or the
US) has to be installed.
If MapPoint is installed without maps, only a grey map without content is displayed.
The display of maps can be customized. Please see chapter 6.14.12.
In A.I.M.O.S. Visualization select Tools / Map.
Drag folders or NEs to be displayed from the NE Tree and drop them at a map.
6.14.1
Buttons
Use theZoom In and Zoom Out buttons to adjust the resolution of the map.
Parent Map switches to the higher-level map.
Locate in Tree switches to the NE Tree of A.I.M.O.S. and highlights the selected
NEs.
Page 182
M0125ANA.DOC
6.14.2
Assign a Bitmap to a Folder
Preparation: Create a folder in the NE Tree. Move at least one NE into this new
folder and place the NE on the vector map.
How to: Right-click the new folder and select Map-Assign Map to Folder from the
context menu. Select a bitmap (.bmp) with at least 300x300 pixels, a smaller bitmap
does not make much sense. You may have to press F5 in the NE Tree to update the
NE Tree and NE Map.
Verification: The NE located in the folder should vanish from the vector map due to
the fact, that an NE can only be placed on its parent map. You can then drag and
drop the folder onto the vector map and it should behave like a normal NE. Check the
summary alarm of the folder. Try to drag the NE subunits onto the vector map; it
should no longer be possible, but it should be possible to drag them onto the bitmap.
You can open the bitmap by double-clicking the selected folder icon on the vector
map or selecting Map Show Map from the context menu in the NE Tree.
6.14.3
Assign a Bitmap to a Subfolder of a Bitmap Folder
Preparation: You can assign a bitmap to folders, which are placeable on the parent
bitmap (drag-and-drop).
How to: Assign a second bitmap to a subfolder. Press F5 if the NE Tree does not
refresh. The folder should then be dragable to the parent bitmap.
Verification: The newly assigned bitmap folder and its NE subunits should behave
like a bitmap folder that has the vector map as parent. The folder itself should only be
dragable to the parent bitmap; all its NE subunits should only be dragable onto the
newly assigned bitmap.
6.14.4
Remove a Bitmap from a Folder
How to: Right click a folder with a bitmap assigned in the NE Tree of A.I.M.O.S. and
select Map Delete Map from folder from the context menu.
Verification: The folder icon should be removed from the vector map / parent map.
The NE subunits should reappear on the parent map, if they were placed before the
map was assigned to the folder, but this only works correctly with the vector map until
now. Anyway, the NE subunits should be placeable onto the parent map now.
6.14.5
Show a Folder Bitmap as Map
How to: Select a folder with a bitmap assigned in the vector map, so it gets
highlighted. Double-click on the highlighted icon in the map or select Map Show
Map of the NE context menu in the NE Tree.
Verification: The bitmap you did assign to the folder should show up instead of the
vector map. The Zoom In and Zoom Out buttons should be disabled. The Parent
Map button should be enabled. You can now drag and drop NEs located in the
folder onto the map. The behavior of NEs on the bitmap should correspond to their
behavior on the vector map. Pressing the button Parent Map should get you back to
the vector map.
Page 183
6.14.6
Show a Sub-Bitmap as Map
Preparation: You can assign a Bitmap to folders, which are placeable on the parent
bitmap (drag-and-drop).
How to: Select a folder with a bitmap assigned located on a bitmap of a folder, so it
gets highlighted. Double-click on the highlighted icon in the bitmap or select Map
Show Map of the NE context menu in the NE Tree.
Verification: The bitmap should exactly behave like a bitmap located on the vector
map. Pressing the button Parent Map should get you back to the parent bitmap.
6.14.7
Including NEs to the Vector Map
6.14.7.1
RF Units
Preparation: Align the Map Window window to the left of the screen and move the
main window out of the right side of the screen, so you can still see the NE Tree.
How to: Pick an RF unit, not included in a bitmap assigned folder and drag-and-drop
it onto the Map Window.
RF units are:
Folder with assigned bitmap
MR repeater
Node A
Node C
Node M
Node G
SMS
Verification: The NE should appear on the Map Window at the place you did drop it.
If the NE has no alarm, the icon should be the icon for this NE type. It should be
selected in the Map Window and have no additional colored ring around. If this NE
is in alarm mode, it should have a ring around, colored with the color of highest
severity this NE has at the moment. Whenever a severity changes, the icon should
change automatically.
6.14.7.2
Optical Systems
Preparation: Align the Map Window window to the left of the screen and move the
main window out of the right side of the screen, so you can still see the NE Tree.
How to: Pick an optical NE not included in a bitmap assigned folder and drag-anddrop it onto the Map Window. The upcoming confirmation box should once be
answered with Yes. After you have confirmed the result, you should drag the same
NE once again onto the map, answering No to the confirmation box.
Optical systems are:
BCA Britecell
MC Master Controller
MOR Optical Repeater
Page 184
The includable subunits are:

BCL3 Britecell Level 3 for BCA
RU Remote Unit for MC
SLV Slave for MOR
M0125ANA.DOC
Verification: If you have included the NE subunits, all includable NE subunits should
be on the Map Window as well, placed aside the optical master. The optical master
should have the summery alarm of each NE subunit APART from those included on
the Map Window. If the summary alarm state changes, the icon should change to
the new state as well.
If you exclude the NE subunits from the Map Window, the icon should have the
summary alarm of ALL subunits.
You should not be able to drag and drop NE subunits of an optical system out of the
NE Tree into the map, independent whether or not the optical master is on the map.
6.14.8
Selecting an NE
How to: Select an NE on the Map by clicking on it once. If more than one NE was
selected accidentally, a popup window will appear to specify the selection.
Verification: The selected NE should now be highlighted and its icon should change
to an icon identifying the NE type. Verify that the selected NE is in the NE Tree. If
more than one NE was selected accidentally, a popup window will appear to specify
the selection. The selected NE should then be highlighted.
6.14.9
Moving an NE on the Map
How to: Select an NE on the map. Then drag it to the desired location.
Verification: Provided that the mouse cursor was moved far enough, the icon should
now appear at the place where it was dragged.
6.14.10
Removing NEs from the Map
6.14.10.1 RF Units
How to: Right-click a selected RF unit in the vector map and select Delete in the
context menu.
Verification: The RF unit should vanish from the vector map.
6.14.10.2 Optical Systems
How to: Right-click a selected master icon of an optical system and select Delete in
the context menu.
Verification: The optical master and all its subunits should vanish from the vector
map. This should work with every NE on the map.
6.14.11
NE Subunit Management
6.14.11.1 Excluding NE Subunits from an Optical System

How to: Select the icon of an optical master that has NE subunits on the map, rightclick on it, and select Remove Subunits.
Verification: All of its subunits should disappear from the map. The icon of the optical
master should now show the summary severity color of all its subunits.
Page 185
6.14.11.2 Including NE Subunits to an Optical System

How to: Select the icon of an optical master that has no NE subunits on the map,
right-click on it, and select Include Subunits.
Verification: All of the NE subunits should appear in the map. The icon of the optical
master should now show the summary severity color of all its subunits, apart from the
recently placed subunits.
6.14.12
View
This sub-menu of the tool Map offers the following views:

Empty: Map appears in grey. Only the major cities are displayed.
Road: Map appears in yellow. All major streets as well as all special locations, e. g.
fairs, ports, parks, lakes, rivers, and airports, are shown.
Terrain: Map appears in green. All major geographical characteristics are displayed.
Road and Data: Similar to Road.
Political: Map appears with the same content as in Road, but the background color
differs between the political borders.
Flash Alarms: NEs with active alarms will be indicated by a flashing circle-mark.
6.15
TOOL WATCHDOG
In the A.I.M.O.S. Visualization select Tools / WatchDog.
With this tool all running applications are displayed. If necessary, applications can be
paused and started again.
For further information please also refer to chapter 7.5 WatchDog.
6.16
TOOL PERFORMANCE MANAGER (OPTION)
This tool mainly serves for creating comparative charts of alarms and performance
data, which can be stored, exported, or saved as image files.
Access to this tool can be configured in the Account Manager rights (see chapter
5.4.2).
With the Performance Manager tool alone, only charts from alarm data can be
created. In order to be able to create charts from performance data, as well, or for
generating charts at certain intervals and sending them out via mail, the tool
Scheduler (see chapter 6.10) is also required.
Page 186
M0125ANA.DOC
Before the performance data can be used by the Performance Manager, they have to
be retrieved from the respective NEs as follows:
In order to get the performance data of an NE - i.e. csv file on HD (Node X only) and
data in database (Node X & ION) - use the Scheduler action Read Performance
Data explained in chapter 6.10.3.4.
Using the action Create Performance Data Chart (see 6.10.3.5) of the Scheduler it
is possible to generate charts (which must be pre-defined in the Performance
Manager) at certain intervals and to send them out via mail at specified addresses.
Both the intervals and mail addresses can be customized in the Scheduler action.
In the A.I.M.O.S. Visualization select Tools / Performance Manager.
The name of the chart currently selected is displayed here.
The chart selected will be displayed in this area

when the evaluation is finished.
Use these fields to specify the chart settings

(for details see section 6.16.2).
The settings of the chart currently selected
are displayed.
6.16.1
Menus
Page 187
6.16.1.1
Performance
Apart from the common items Undo, Refresh, and Close this menu also provides
the possibility to export alarm data as excel file (Export Alarm Data).
Confirm chart settings with Apply (or use the Apply button). For details see 6.16.2.
6.16.1.2
Chart
New Chart: All settings made are deleted use to define a new chart from scratch.
Save Chart Configuration / Save as New Chart Configuration: Use to save a
chart configuration for later use or to make it available for the Scheduler action
Create Performance Data Chart (see chapter 6.10.3.5).
Use Save Chart Configuration to save it under the given name (no name will be
requested) or Save as New Chart Configuration to save it under a new name (the old
name will, however, be suggested). When a chart is saved for the first time the Chart
Title (see next section) is suggested as its name.
Loading a configuration again may take some time since the evaluation starts anew.
Load: Use to load a pre-defined chart configuration from the list provided.
This list contains a series of pre-defined factory-set configurations as well as
individually set (see 6.16.2) and saved (see next menu item) personal configurations.
The factory-set configurations serve to generate charts for the most useful
evaluations since creating a chart configuration from scratch is a complex matter.
Rename: Use to change the name of a chart already saved.
Delete: Use to delete configurations that were already saved.
Save as Image File: Select a path to save the current chart series as image file
(emf, etc.). This way of storage is recommended if the main purpose is to be able to
quickly view a chart at a later time.
Print Chart / Print Chart with Aspect Ratio: Use to print a chart.
6.16.2
Settings
Notes:
When setting the chart parameters, please keep in mind that not all of the various
combinations make sense. Due to the great variety of setting options it is not
possible to give examples for all. In view of this complexity of the Performance
Manager, experience in working with charts is indispensible for this tool.
In addition, no more than 16 different types of measurement values should be
integrated in one chart, since the number of colors for the distinction of the values
is restricted.
The pre-defined configurations that can be loaded via the Chart menu (see 6.16.1.2)
may be used as reference and modified in order to meet individual requirements. If
you plan to keep a factory-set configuration for later use, take care not to overwrite it.
To keep both configurations, save the modified version under a new name.
Page 188
M0125ANA.DOC
The following settings can be made to customize a chart:
Depending on your choices in the
individual fields the further options will be
adapted accordingly. Since the
parameters vary, the screen shots in the
following are always of an exemplary
nature.
This explanation is intended to provide an
overview of the most important setting
options. At the end of this chapter an
exemplary chart is added to illustrate the
various settings.
A field that is marked red (e. g. beside
Series Type or Data Source in the
example to the left) indicates that a
problem or warning message is available
for this selection. Move the cursor over
the respective option to display the
message as illustrated in the following
examples.
.
.
.
.
The combination of settings is not possible and, thus, not accepted.

This example shows a warning /
recommendation since Series
Type Bar can lead to undesirable
results when combined with Data
Source Exact Time:
Per each measured value/result a single bar will be generated where the individual
bars all have the same distance and do not represent the time line. Thus, Series
Type Lines might be a more suitable choice, here, because it positions the data
points forming the chart line in chronological order, which is usually a main reason
for choosing Exact Time. Therefore, this warning / recommendation is provided,
here. However, the choice is not rejected for it is possible that in rare cases the
chronological order might be irrelevant.
Page 189

Chart Scope:
Choose the interval for which the evaluation should
be made. Depending on the choice made for Time
Period further information, such as First Day and
Amount of Days (max. 365) or Last Day for a Fix
Period of Time, may be required.
NE Filter:
Opens the NE Filter Builder to customize a filter (see chapter 6.4.3.2) for the
evaluation.
Alarm Filter:
Displays the list of alarm profiles that were created via Tools Profiles Alarm
Profiles (see chapter 6.17 and 6.17.4). By choosing a certain profile the alarms to be
used for the chart can be specified.
Chart Layout:
Chart Title:
Specify a title, which will be displayed on top of the chart.
Series Layout:
Select the layout for the chart, e. g. 3D.
Color Scheme: Choose from a selection of available patterns.

Max. Points per Page:
Use to restrict the number of items on the X-Axis. The chart may thus be stretched
over several pages. Use the arrow buttons below the chart to page through the chart:
The default setting 0 means there is no restriction, and the chart will be made to fit on
one page.
Series Count:
Enter the number of Chart Series to be shown in one chart. Up to four are possible
and if more than 1 is chosen, the category Chart Series will be extended into Chart
Series 1 and (depending on the setting) Chart Series 2, Chart Series 3, and Chart
Series 4).
Bottom Axis / Top Axis:
At the bottom and / or top of the chart an X-axis can be defined and to each Chart
Series its individual axis can be assigned. The setting options for Bottom and Top
Axis are the same.
Data Source: Select the Data Source to be
used for the axis (NE, Alarm Type, or Date
Time). If none is selected, the according axis
will not be provided.
Sort Order:
Values sorts the chart (X-axis = Bottom Axis and/or Top Axis) according to the
values of the Y-Axis (ascending or descending).
Labels sorts the order on the X-Axis either alphabetically or chronologically
(depending on the Data Source of the X-Axis: types or time), ascending or
descending.
Page 190
M0125ANA.DOC
Depending on the Data Source selected, specify Type or Severities:
For Data Source Network Element select the Type for the classification (e. g.
Folder, NE Type, etc.).
For Data Source Alarm Type select the Severities to be used by setting the
check-marks accordingly.
For Data Source Date Time select the Type (= interval to be used) for the
classification (e. g. Hourly, Daily, etc.).
Left Axis / Right Axis:
Select the scale for the Y-Axes by choosing
between a linear and a variety of logarithmic
divisions. Different settings for the Left Axis
and Right Axis are possible.
A logarithmic division is recommendable if the span of values is great, so that lower
values can also be displayed in a distinct way (see also example at the end of the
chapter).
Chart Series (n):
For each chart series select the Source Type, the Series Type and assign the
Horizontal Axis (Bottom or Top) and Vertical Axis (Left or Right). Please also have a
look at the example at the end of this chapter to get a better understanding of the
various setting possibilities.
Source Type:
Select the source for each series (Alarm
Data* or Performance Data**; reset is
possible by selecting the empty field).
* Alarm Data refers to all alarms in A.I.M.O.S. no matter if visible in Supervision or Alarm History.
** Performance Data refers to data downloaded by A.I.M.O.S. via the tool Scheduler (see chapter
6.10.3.5.); currently this source is only supported for Node C, G, or M except two-box (DCM1 units)
with a SW version <1.5.
Series Type:
Select the type for each series (Line, Bar,
or Pie).
Horizontal Axis: Select to which
horizontal axis (Bottom or Top) this chart
series shall be assigned.
Vertical Axis:
Select to which vertical axis (Left or Right) this chart series shall be assigned.
Page 191

For each Chart Series the Calculation (Y-Axis) and Grouping (Z-Axis) can be
individually defined. Making entries for the Z-Axis is not obligatory and for a chart
with more than one Chart Series this further distinction is not recommended since the
large number of data can easily result in an unclear or even confusing chart.
Depending on the selection made for Source Type, the Data Source options for the
Y- and Z-Axis will vary.
For Alarm Data the options are as follows:
Calculation (Y-Axis):
Select the Data Source to be used for the Y-Axis (i.e. Alarm Raise Count, Active
Alarm Count, Availability, or Alarm Duration).
o
o
o
Alarm Raise Count: Amount of all alarms raised, irrespective of whether alarms
were subsequently cleared or recognized.
Active Alarm Count: Amount of alarms (that were not cleared) for a specific time.
Availability: The availability gives an indication of
the success ratio of a Network Element. When this
option is chosen as data source, a further
distinction (Type) is provided to choose between
the following:
Suspended is the ratio of suspended* periods to the charts scope.
Active is the ratio of not suspended* periods to the charts scope.
Success is the ratio of periods without any alarm to the charts scope less
suspended* times.
Failure is the ratio of periods with active alarms to the charts scope less
suspended* times
* Suspended times (periods) are currently only supported for the Node AM. Network
Elements are suspended when they are Off Duty (NE is powered on but 'out of operation
area', which means that no alarms are generated) or Shut Down (i.e. 'out of service').
Alarm Duration: Indicates the overall alarm duration of all alarms. If an alarm is
still active at the end of the charts scope, the alarm is treated as if it was cleared
at the end of the charts scope.
For all types of data source you can enter minimum or maximum values (or a
combination of both) to be used for the evaluation. If you only want to see the top
scores in the set period, enter the according figure in the field Top (e. g. Top 5). The
example on the next page illustrates such a setting.
Page 192
M0125ANA.DOC
Example: The X-Axis shows various alarm times and the Y-Axis the sum of alarms
for each point in time. If Top 5 is chosen in this case, the chart will be reduced to
those alarm times with the most, second most etc. up to fifth most alarms, as shown
in the following illustration:
After selecting Top 5 the chart will look as follows:
Page 193
Grouping (Z-Axis):
Select the Data Source to be used for grouping
(Network Element, Alarm Type, or Date Time).
Depending on the Data Source selection, specify Type or Severities (the available
choices are the same as for the X-Axis see description Bottom Axis / Top Axis):
A color code will be used in the chart to visualize the individual groups.
If Performance Data is selected as Source Type, the following options vary from the
explanation above:
As Data Source in the Calculation (YAxis) the options NE Data and Channel
Data are provided. The available settings
are as follows (Channel is only provided
if Channel Data is selected):
Measurement
shows the type of
value that was
selected in the
Node (in this
example i.e. DL Rx
Power) and
transferred to
A.I.M.O.S. via the
Scheduler.
Channel provides a context-sensitive list depending on the available data.
Aggregation: If more measurement values are available for the same measured
variable on the X-Axis*, use this field to decide which value should be
represented in the chart (e. g. minimum or maximum value or an average of all).
* This can be the case when Bottom Axis -> Type -> Hourly was selected but 4 measurements
per hour are made; thus 4 values are available.
- As Data Source in the Grouping (Z-Axis) only the option Network Element is
provided.
In all other respects the explanation for the Source Type Alarm Data is valid for the
Performance Data, as well.
Page 194
M0125ANA.DOC
When all settings are made, click the Apply button to generate the according chart
series and continue with the further series, if required.
Example:
The exemplary chart on the next page was generated with the following settings:
The Time Period from 15th to 21st of
September 2009 was used for the
evaluation.
The number of Network Elements of the
Bottom Axis is restricted to 40.
Therefore, the chart extends over the
required number of pages.
Two Chart Series are defined.
Since no Chart Series is assigned to the
Top Axis, it is not displayed in the chart.
The left axis is divided logarithmically
the distance from 0 to 10 and from 10 to
100 is the same and values below 10 can
thus also be clearly distinguished.
Not assigned in the exemplary chart.
The (orange) bars in the chart represent
the rate the individual NEs (Each Single
NE was chosen as Type for the Bottom
Axis) were operating (= not Off Duty) but
in alarm state (Availability Failure).
Not defined.
The (red) lines in the chart show the

Alarm Raise Count of the individual NEs
(Each Single NE was chosen as Type for
the Bottom Axis) up to a maximum
value of 200.
Not defined.
Page 195
6.17
TOOL PROFILES
In the A.I.M.O.S. Visualization select Tools / Profiles.

This tool provides shortcuts to the profiles that can also be set via the Connectivity
Manager, Account Manager or Preferences Editor depending on the profile type.
Once a profile has been created, it can be assigned to NEs via the according tab in
the Functions bar (see chapter 6.8).
Only when the tool Performance Manager (see chapter 6.16) is licensed, the Alarm
Profiles are available. This profile serves to assign individual names to certain
alarms. The alarm groups specified here can be used by the Performance Manager.
For more details see chapter 6.17.4.
Page 196
M0125ANA.DOC
6.17.1
Connectivity Manager Profiles
Assign these profiles to an NE via the Configuration / Connectivity tab of the

functions bar (see chapter 6.9).
Access to these profiles can be configured in the Account Manager (chapter 5.4.2).
For details about the SMC Service Center
Profiles see chapter 5.3.3.4.
For details about the RAS-in Profiles see

chapter 5.3.3.1.
For details about the Network Element Circuit Switched Profiles see chapter 5.3.3.2.
For details about the Network Element

Packet Switched Profiles see chapter
5.3.3.3.
For details about the Network Element Web Login Profiles see chapter 5.3.3.5.
6.17.2
NE Owner Profile of Account Manager
Assign the NE Owner profile to an NE via the Configuration / General tab of the
functions bar (see chapter 6.8.2).
Access to this profile can be configured in the Account Manager (chapter 5.4.2).
For details about the NE Owner Profiles see chapter 5.4.5.

Page 197
6.17.3
Configuration Groups of Preferences Editor
Assign the NE Configuration Group

profile to an NE via the Identification field
in the Configuration / General tab of the
functions bar (see chapter 6.8.2).
Long Name: This name will be displayed in the Identification field of the Functions
bar under the Configuration / General tab (see chapter 6.8.2).
Short Name: This name will be displayed in the field ...in Configuration Group of
the NE Filter Builder (see chapter 6.4.3.2) for quick identification when choosing the
filter settings.
Configuration File: Choose the correct file for the according NE from the list of
available files.
This profile is also available via the Preferences Editor (see chapter 5.2).
Access
can
be
configured
in
the
Page 198
M0125ANA.DOC
Account Manager Rights ('Configuration'; see 5.4.2).
6.17.4
Alarm Profiles
Alarm Profiles provides two menus (Alarm Profiles and View) to create, export, edit,
delete and view the alarm profiles that can be used by the Performance Manager
(chapter 6.16) for the creation of alarm charts. The Alarm Profiles window displays a
table of all available alarms.
Profiles can be created via Alarm Profiles Profile Management Create new
Profile and entering a name.
Each profile will be added as a new table column:
Page 199

Alarms that should belong to a profile must be tagged in the respective column. To
set the check-marks it is also possible to select/highlight the desired alarms and use
the Alarm Profiles menu item Add selected Alarms to Profile. To add all alarms to
a profile they can be quickly selected using the menu item Select All Please observe
that access to this action can be configured in the Account Manager (chapter 5.4.2).
To delete alarms from a profile click the according check-marks or highlight the
according alarms and use the Alarm Profiles menu item Delete selected Alarms
from Profile.
To display the alarms of all profiles or only of an individual
one, use the All Profiles button to select all or an
individual profile. The displayed table and button will
change accordingly:
This selection is also possible via the menu item Profile
Filter of the View menu.
Please observe that if an alarm line is clicked in this view, the according alarm will be
removed from this profile, as if it was unchecked.
Furthermore, the View menu can be used to save
or load individual grid layouts for the table and
provides a Filter Builder to customize it further. For
further details on grid layouts and filter builder
please refer to chapters 6.4.1.3 and 6.4.2.
Use the Excel Export button to save the Alarm Profile settings currently displayed as
Excel file.
Page 200
M0125ANA.DOC
6.17.5
Export Profiles
Access to the Export Profiles must be configured in the Account manager

(Reporting right). For details see chapter 5.4.2.
Available for an export mainly are queries ("views") provided in the Network Element
List (chapter 6.11). Three pre-configured profiles are available right away:
With the Scheduler action "Create Export" (see chapter 6.10.3.8) the Export Profiles
can be configured further and the export can be scheduled as required. Creating an
Excel or xml file is possible.
In the Export Profiles select which data are to be exported and configure the
available parameters as follows:
Profile Name: Specify a unique name for the export. This name will also be available
in the export configuration of the Scheduler. If an already existing name is entered,
the entry will be marked red and the system will prompt you to change it.
Export Name: Available data types (mainly views from the Network Element List,
chapter 6.11) are listed (not configurable).
Export Details: The data to be exported can be specified using the Edit button to
open a checkbox list for an individual data selection:
Type:
Select the View to be exported (see also
Network Element List, chapter 6.11).
Fields to export:
In this list the data to be exported can be
individually specified by tagging /
untagging the according checkbox. (The
items available in the list depend on the
Export Type.)
You can also open the context-sensitive

select action menu (see next page),
which offers multiple choices for a quick
selection.
Page 201

select action: Opens a context-sensitive list of multiple actions (the choice depends
on the NE type) by which several data can be selected for or removed from the
export, e. g.:
The same list is available by a right mouse-click in the selection field.

When a selection is made here, any individual selection made before will be
overwritten, it is, however, possible to adjust the selection afterwards by tagging /
untagging certain choices.
By clicking the New button a new query can be defined as explained in the above
and will be added at the end of the list.
6.17.6
Access to the External Tool Profiles must be configured in the Account manager
(Reporting right). For details see chapter 5.4.2.
An External Tool Profile must be configured in order to be able to execute the Run
External Tool action of the Tool Scheduler (Option), chapter 6.10.3. This action
serves to start external tools (e.g. exe or batch files) via A.I.M.O.S.
The following parameters must be set:
Name:
Executable:
Arguments:
Working Directory:
Page 202
Define a name for the profile.

Select the name of the external tool (= executable) which
should be filed on the A.I.M.O.S. server under
Bin\ExternalTools.
Define the parameters for the external tool.
Specify the path of the working directory to be used.
M0125ANA.DOC
6.18
OMC3 ADAPTER
This service is started automatically and used by A.I.M.O.S. for OMC3

synchronization.
Status window of the OMC3 Adapter under Windows 2003:
To start the visualization of this service double-click on the OMC3 icon in the system
tray.
Note: Please observe that the OMC3 Adapter is not visible in the "system tray"
with Windows 2008 irrespective of the A.I.M.O.S. version.
6.19
SNMP GUI
This program is used for the graphical supervision of the SNMP Agent service, which
is used by A.I.M.O.S. for the synchronization of SNMP traps. For the configuration of
the SNMP Agent please refer to chapter 5.1.4. Program and service are started
automatically
To start the visualization of this service
double-click on the SNMP icon (green circle) in the system tray (Win2003)
or
select Start Programs Andrew A.I.M.O.S. SNMP GUI (Win2008).
Page 203
In the Status tab the performance data of the SNMP Agent are displayed:
The Diagnosis tab can be used to get more detailed information on the
performance data in the Status tab or for logging purposes. The tabs that are
included in the Diagnosis tab are selected in the Settings tab:
Use the Settings tab to select which data are made available in the Diagnosis tab
by tagging the according fields:
Page 204
M0125ANA.DOC
7 A.I.M.O.S. Database Administration / Maintenance Tool
7 A.I.M.O.S. DATABASE ADMINISTRATION / MAINTENANCE TOOL

Select StartProgramsAndrew A.I.M.O.S.
Server Maintenance.
to start the A.I.M.O.S. Maintenance Tool.
Select the required function (all explained in the following chapters) in the navigation
window. Available are Backup, Restore, Validate, Update, and WatchDog.
7.1 BACKUP
Use
the
backup
functionality to make
backups
of
the
OMC3/A.I.M.O.S.
database (automation
is possible via the
Automatic
Backup
feature; see chapter
5.9).
The path and filename
of the backup have to
be
entered
or
selected.
The contents of the backup have to be selected: A.I.M.O.S. and/or OMC3.
It is recommended to make a backup of the OMC3/A.I.M.O.S. after major changes or
before an update.
Start the selected backup(s) with the 'Start' button.
7.1.1
Backup to File
Select or enter the path to and the name of the backup file. Enter the complete name
of the file with suffix .aimosbackup*, e. g. backup_3_8_04.aimosbackup.
A number is automatically attached to the filename of the backup file
(e. g. backup_3_8_04[0000].aimosbackup).
Please note: A backup includes all vital settings from the A.I.M.O.S. Server
Configuration / Configuration Tool (see chapter 5.1). The Configuration Tool settings
(see section 7.2.5) will be included automatically, thus, if settings in the A.I.M.O.S.
Configuration Tool were changed, it is recommendable to make a new backup.
Please observe that the Configuration Tool itself also provides a button to make a
backup of most of its current settings (see chapter 5.1).
* Until A.I.M.O.S. version 2.9.0 the backup file was saved with suffix .zip.
Page 205
7.1.2
Include A.I.M.O.S.
Check this checkbox to make a backup of the complete A.I.M.O.S. database.

7.1.3
Include OMC3
Check this checkbox to make a backup of the OMC3 database.

Note: Before the OMC3 backup can be started all open accesses of the OMC3
are stopped (and restarted after backup) by the WatchDog.
To use this feature an OMC 3.54 has to be installed.
7.1.4
Backup Finished
Successful backups will be

displayed in the backup
window.
7.2 RESTORE
Use the Restore functionality of
A.I.M.O.S. to restore former
stages of the software.
(Automation is possible via the
Automatic Backup feature; see
chapter 5.9.
Here, the list of backups is displayed
Notes:
The restore can only be carried out if a backup of A.I.M.O.S. has been saved
before.
Only a backup of the running version can be restored (see also chapter 7.2.6
Backup Version).
The WatchDog will close all necessary applications for the restore and will start
these applications automatically after the restore.
Page 206
M0125ANA.DOC

The backup file has to be selected. The version of the selected backup file is
displayed.
Note: All changes since the date of the backup are lost.
Start the selected procedure(s) by clicking the 'Start' button.
7.2.1
Restore from File
Select or enter the path to and the name of the .aimosbackup file *. Registry
entries, the A.I.M.O.S. database and the OMC3 database can be restored. Previous
backup files are displayed in the list of backups.
Please note that before and after a restore it is always recommended to check all
settings in the A.I.M.O.S. Configuration Tool. This is essential because unwanted
registry settings could have been restored or windows settings may have significantly
changed since the restored backup was created.
* Until A.I.M.O.S. version 2.9.0 the backup file was saved with suffix .zip.
7.2.2
Restore A.I.M.O.S.
Check this checkbox to include the A.I.M.O.S. database to the restore procedure.
7.2.3
Restore OMC3
Check this checkbox to include the OMC3 database to the restore procedure.
Note: Before the OMC3 restore can be started the WatchDog stops all open
accesses of the OMC3 database and restarts them after the restore.
To use this feature an OMC 3.54 has to be installed.
7.2.4
The List of Backups
The files of all previous backups are displayed in this list. Select the file from the list
and start the restore procedure.
7.2.5
Restore Configuration Tool Settings
This option serves to restore all settings of the Server Configuration Tool (see
chapter 5.1 Server Configuration / Configuration Tool) at the time of the backup.
If the check-mark is not set, only the settings of the pages "Licenses", "Security",
"Logging", and the settings "Visu Gateway Port" (at "General" page) and "Length of
Generated Community Name" (at "SNMP" page) will be restored. Set the check-mark
to restore all other Configuration Tool settings, as well.
Please observe that the Configuration Tool itself also provides a button to make a
backup/restore of most of its current settings (see chapter 5.1).
Note: In a migration scenario from Windows 32 Bit to Windows 64 Bit, do NOT
set the check-mark for the first Restore if the Table of Contents has
changed (e.g: Windows 32 Bit: "C:\Program Files; Windows 64 Bit:
"C:\Program Files (x86)").
Page 207
7.2.6
Backup Version
When a file is selected, the A.I.M.O.S. version under which this file was created is
displayed. If this version corresponds to the running A.I.M.O.S. version, it is written in
green indicating that a restore is possible. If the file was created by a former version
of A.I.M.O.S., restoring it is not possible and the writing is red.
7.2.7
Restore Finished
Successful Restore jobs will be displayed in the restore window:
7.3 VALIDATE
Validating a database means to check the consistency of the database and to repair
errors, if necessary. It is recommended to validate the database of the
OMC3/A.I.M.O.S. if errors occur within the program or if the operating system is
ended abruptly, e. g. in case of a power failure.
Start the selected validation procedure(s) by clicking the 'Start' button.

Page 208
M0125ANA.DOC
7.3.1
Include A.I.M.O.S.
Check this checkbox to include the A.I.M.O.S. database to the validation procedure.
7.3.2
Include OMC3
Check this checkbox to include the OMC3 database to the validation procedure. To
use this feature an OMC 3.54 has to be installed.
7.3.3
Validation Finished
Successful validation procedures will be displayed in the validation window:
7.4 UPDATE
Use the update functionality to update the A.I.M.O.S. server (please also see chapter
4.3.1).
Page 209
7.4.1
Update From File
Select or enter the path to and the file name of the update zip file. Start the update by
clicking the 'Start' button.
(In case of updates from very old versions the following screen appears:
Confirm with 'Yes'.

After the confirmation an automatic restart of the program is initiated. )
Please note: Depending on the speed of the A.I.M.O.S. server a red X may be
displayed shortly to indicate the restart. It is not an indication of a program error.
Confirm with the OK button to finish the update.

Please note:
It is required to install a permanent license within two weeks otherwise usage of the
A.I.M.O.S. visualization will no longer be permitted.
To install the License File for a permanent use of A.I.M.O.S., please refer to chapter
4.5 How to get A.I.M.O.S. licensed.
Page 210
M0125ANA.DOC
7.4.2
Update Finished
Successful updates will be displayed in the update window:
7.5 WATCHDOG
Please also see chapter 6.15 Tool Watchdog.
The WatchDog displays all running A.I.M.O.S. applications. If necessary, e.g. for a
validation of a database, the WatchDog stops and automatically re-starts applications
accessing the database(s).
With the context menu of the right-mouse click on the top line applications can be:
paused (stopped with the option to re-start the application)
started, after they have been paused
stopped (shutdown the application with the possibility for the application to save
changes).
Also A.I.M.O.S. can be shut down.
Page 211

With the context menu of the right-mouse click on a single application the application
can be:
paused
started, after it has been paused
stopped
terminated (shutdown the application without the possibility for the application to
save changes.
When an application running on a computer that is not the server computer is
stopped (e. g. a visualization running on a client), a message can be sent to inform
the user about the stopping of the application and a timer can be set.
Page 212
M0125ANA.DOC
8 A.I.M.O.S. Test Tools
8 A.I.M.O.S. TEST TOOLS

When the option Test Tools is selected in the Custom Setup (see chapter 4.2), the
hardware simulation tools AgentSim, ComasTest, MIB, and TrapMonitor, which can
be used for system analysis, will be installed.
They can be started via
StartPrograms Andrew A.I.M.O.S.:
Note: Please observe that these tools should
only be used by Andrew technicians.
8.1 AGENT SIM

This tool serves to simulate different NE types, except SMS-connected NEs, OMC3
systems, and optical network systems (ION).
Please observe that at the first start of "AgentSim" under Windows 2008 with active
Windows Firewall the following alert is displayed:
Set the check-mark for Private networks, such as shown in the figure above
and confirm by clicking "Allow Access". If this alert is quit with "Cancel", the program
will not function properly and can not be used for test purposes. At the next program
start the alert is no longer displayed to change this. So please make sure to follow
this procedure.
Page 213

-
To simulate an NE via AgentSim, start the program and select the NE type you
would like to simulate from the list provided:
Do not close the window for the time of the session; just minimize it.
-
Then, the NE can be created as explained in chapter 6.5. Please verify that the IP
port is set to 165 (default setting):
When 0 is entered four times as
IP-Address in the new NE
dialogue in the Visualization, the
correct address (corresponding
to IP address of the OMC server
see chapter 5.1.2) and port
will be set automatically.
Note: For common application it
is not necessary to adjust the
configuration of the AgentSim. If
adjustments are required for
special purposes, open the file
AgentSim.ini under
~\Andrew\AIMOS\Bin
and make the required setting
before starting the AgentSim.
These two settings

must be equal.
* These two settings must correspond to the settings in the A.I.M.O.S. server and in the Server
Configuration / Configuration Tool (see chapter 5.1.2: OmcIp corresponds to IP Address of the
OMC Server and OmcPort corresponds to SNMP Trap Port of the OMC Server).
Now, the AgentSim.exe window can be used to simulate certain events for the
NE, e. g. raising test alarms, etc.:
Page 214
M0125ANA.DOC
8 A.I.M.O.S. Test Tools
8.2 COMAS TEST

This tool serves to simulate ION-M and OMC3 systems (devices connected via
Comas protocol). Please observe that at a first start under Windows 2008 with active
Windows Firewall an alert similar to the one for the AgentSim is displayed. Answer
the alert as explained in chapter 8.1.
Possible selections are:

MC for an ION
system
OMC3 for an OMC3
system
Corresponding to
IP-Address / Port of
New ION-M window
(see below).
To simulate such systems, start the program and create the required NEs as
explained in chapter 6.5. Please verify that the IP Port is set to 7420. When 0 is
entered four times as IP-Address during the NE creation in the Visualization, the
correct IP Address (corresponding to IP address of the OMC server see
chapter 6.1.2) and Port will be set automatically.
Corresponding to
Partner IP / Port of
Comas window (see
above).
After clicking the Open Session button in the Comas-Test window, the tool can
be used to simulate certain events for the system, e. g. raising test alarms, etc.:
Do not close the Comas-Test window for the time of the session; just minimize it.
Page 215
8.3 MIB
This tool is a MIB viewer; see exemplary figures below:
Select a MIB and Open it to view

its contents:
8.4 TRAP MONITOR

This tool is used to receive test traps.
The Trap Port corresponds to the Default Port for outgoing SNMP Traps of the
Server Configuration / Configuration Tool (see chapter 5.1.4.2 for details).
corresponds to the A.I.M.O.S. server

The user who is allowed to receive the test traps must be configured in the Account
Manager (see chapter 5.4).
Page 216
M0125ANA.DOC
9 Logging
9 LOGGING
9.1 LOG FILE DOCUMENTATION
A.I.M.O.S. provides a variety of different log files depending on the purpose. All log
files are stored at the A.I.M.O.S. Server.
9.1.1
Log File Overview

Connection to OMC3
Server Update
SNMP Operations
9.1.2
Log File Contents
9.1.2.1
Content abstract:
It contains all information which is collected during A.I.M.O.S.

installation and uninstalling procedures.
Location: ~\Andrew\AIMOS\Bin\Log
Name: ProcessingServices.log
Trigger: ProcessingServices.jse and UninstallServices.jse
Size: > 5 KB The exact size depends on how many installation and uninstalling
procedures were performed.
Size required per day (role of thumb): none
Configuration: not required
Rotation: none
Format: [Date] [Time] [Event]
Example: 2010-10-08 10:14:00.300; Guardian starting: "[Firebird Installation
Directory]\Firebird_2_5\bin\fbserver.exe"
Note: This log file contains all operations which are performed in addition to the
InstallShield installation and uninstalling procedures.
Page 217
9.1.2.2
Content abstract:
It contains all information which is collected during all Firebird

Database Server operations.
Location: ~\Andrew\AIMOS\Firebird
Name: firebird.log
Trigger: FirebirdServerServerDefaultInstance & FirebirdGuardianDefaultInstance
Size: > 4 KB - The exact size depends on how many database procedures were
performed.
Size required per day (role of thumb): approx. 1 KB per day
Rotation: none
Format:
Example:
[Database Server Name] [Date & Time]

[Event]
[Additional Event Information]
AIMOS_TEST (Server)
Fri Oct 08 10:22:09 2010
Server: setting SWEEP_QUANTUM to 250, USER_QUANTUM to 1000,
SWEEP_YIELD_TIME to 1 ms, and MAX_THREADS to 1
SQL_COMPILER_RECURSION to 2000
Note: The contents or format of this log file is determined by Borland.
9.1.2.3
Connection to OMC3
Content abstract:
It contains all information which is collected during OMC3

Adapter operations.
Location: ~\Andrew\AIMOS\Bin
Name: AIMOS_OMC3_Adapter.Dmp
Trigger: A.I.M.O.S. OMC3 Adapter
Size: > 4 KB - The exact size depends on how many OMC3 operations were
performed.
Rotation: none
Example: 08.10.2010 10.14.13.253 Application Starting ...
Note: This log file is only available if a connection via OMC3 Adapter was
established or, respectively, if a supervision of old Andrew repeaters is intended.
Page 218
M0125ANA.DOC
9 Logging
9.1.2.4
Content abstract:
It contains all information which is collected by all database

maintenance operations.
Name: AIMOS_Maintenance.log
Trigger: A.I.M.O.S. Maintenance Tool
Size: > max. 3 MB - The exact size depends on how many database maintenance
operations were performed.
Rotation: If the limit of 3 MB is reached, the first 1.5 MB will be deleted.
Format: [Date] [Time] [Event ID] [Source ID] [Event]
Example:
09.10.2010 13.04.20.495 [ 2621926] [ App. ]
Starting checkpoint: Validate: Load database information
9.1.2.5
Content abstract:
It contains all information which is collected by all automatic

backup operations.
Name: autobackup.log
Trigger: AIMOS_db_backup.js
Size: > 1 KB - The exact size depends on how many backup operations were
performed.
Rotation: configurable via AIMOS_db_backup.js
Example: 9.10.2010 13:12:25.11: Starting automatic backup, version: 3.2
More Information: see Users Manual for Automatic Backup Feature (M0125B6),
chapter 5.1.
Note: This log file is only available if the Automatic Backup Feature is used or a
redundant A.I.M.O.S. Server Configuration is intended, respectively,
Page 219
9.1.2.6
Content abstract:
It contains all information which is collected by all automatic

restore operations.
Name: autorestore.log
Trigger: AIMOS_db_restore.js
Size: > 1 KB - The exact size depends on how many restore operations were
performed.
Rotation: configurable via AIMOS_db_restore.js
Example: 9.10.2010 13:19:46.894: Restore Started, version=3.2
More Information: see Users Manual for Automatic Backup Feature (M0125B6),
chapter 5.2.
Note: This log file is only available if the Automatic Backup Feature is used
respectively a redundant A.I.M.O.S. Server Configuration is intended.
9.1.2.7
Content abstract:
It contains all information which is collected by A.I.M.O.S.

Watchdog Service.
Name: WatchdogAutomatedObject[ID].Log
Trigger: A.I.M.O.S. Watchdog Service
Size: > 4 KB - The exact size depends on how A.I.M.O.S. is used.
Rotation:
Configurable in the Housekeeping tab of the Server Configuration /

Configuration Tool.
Format: [Date] [Time] [ID] [Error Classification] [Event]

Example:
08.10.2010
14.35.53.146
[00000004A4]CRITICAL
ERROR
:
TClientWinSocket
| <Method: <Unknown Exception Source>> | Unhandled
Exception Catched | Exception: Windows socket error: An operation was attempted
on something that is not a socket (10038), on API 'closesocket' |
Page 220
M0125ANA.DOC
9 Logging
9.1.2.8
Content abstract:
Contains all information collected by A.I.M.O.S. Connector

Service and A.I.M.O.S. Visualization.
Name:
AIMOS_Connector_Log_[Current_Year]_[Current_Month]_[Current_Day].Log
Trigger: A.I.M.O.S. Connector Service and AIMOS_Visu.exe
Size: > 20 KB - The exact size depends on how A.I.M.O.S. is used and how logging
is configured.
Configuration: see chapter 6.13 Tool Log Manager
Rotation: Files are stored on a daily basis and compressed. The duration of their
storage can be set in the Housekeeping tab of the Server Configuration /
Configuration Tool.
Format: [Timestamp],[Message],[Severity],[Log Kind],[Thread],[Thread
Name],[Unit Nr],[Unit SDN],[Component Name],[Modem No.],
[Comm.Resource],[Command],[Direction],[MCNC],[User No.],[User
Name],[Run No.],
Example: "2010/10/08 10:14:08.097","Initializing Communication
Resources",Info,Program Condition,CCOORD,"Comm. Resource
Coordinator",,"","",,"","",,,,"",
9.1.2.9
Content abstract: Contains all information collected by A.I.M.O.S. AutoExport.

Name: AIMOS_AutoExport.log
Trigger: AIMOS_AutoExport.jse
Size: > 1 KB - The exact size depends on how A.I.M.O.S. AutoExport is used.
Rotation: none
Format: [Date]__[Time] [AIMOS_Version] [Event]
Example: 2010_10_09__13_37 V2.6.0.101 Information: Standard configuration was
used. check_Config_file()
More Information: see ODBC Interface manual (M0125B5), chapters 4.5.7.3 &
4.5.7.4
Note: This log file is only available if the Tool AIMOS_AutoExport is installed&used
or if a cyclic database export is intended, respectively.
Page 221
9.1.2.10
Server Update
Content abstract:
It contains all information which is collected during the application

update of an A.I.M.O.S. Update.
Location: "~\Andrew\AIMOS"
Name: "Install.txt"
Trigger: "MSIEXEC.exe"
Size: > 10 KB - The exact size depends on how many database procedures were
performed.
Rotation: none
Note: The contents or format of this log file is determined by Microsoft TM. More
Information about the database update can be found in chapter 9.1.2.4 Database
Maintenance Operations.
9.1.2.11
SNMP Operations
Content abstract: Contains all information collected by A.I.M.O.S. SNMP Agent

Location: "~\Andrew\AIMOS\Bin\Log"
Name: "AIMOS_SNMP_Agent[Current_Year]_[Current_Month]_[Current_Day].Log"
Trigger: "A.I.M.O.S. SNMP Agent"
Size: > 4KB - The exact size depends on how A.I.M.O.S. SNMP Agent is used.
Configuration: To activate logging please refer to chapter 6.19 SNMP GUI.
Rotation: Files are stored on a daily basis. The duration of their storage can be set in
the Housekeeping tab of the Server Configuration / Configuration Tool.
Example: 11/26/2010 4:27:10 PM - ProcessConfigChanged11/26/2010 4:27:12 PM ProcessConfigChanged11/26/2010 4:27:12 PM - ProcessCloseQueries11/26/2010
4:27:21 PM - ProcessCloseQueries
Page 222
M0125ANA.DOC
10 Troubleshooting
10 TROUBLESHOOTING
10.1
RAS CONNECTIONS
In case of failures with the dial-in procedure ensure to check the following items:
Verify that communication with the Modem is possible: In order to run this
check, the incoming connection must be deleted (basic remote access
server) or the RRAS server must be stopped (advanced remote access
server). They must be added again after this test. Open Control Panel (Start>Settings->Control Panel), double click on Phone and Modem Options.
Select Modems Tab and select your modem. Click on Properties and select
the Diagnostics tab. Press query modem. Check the output to verify if
communication to the modem is possible.
Verify that the Modem is logged in into the mobile network (only wireless
modems) refer to the modem documentation to find out how to check this.
MC35/MC88: the blinking scheme of the green LED indicates whether the
modem is logged in into the network. A regular blinking scheme indicates that
the modem is not logged in. Short single periodical flashes indicate that the
modem is logged in to GSM/Circuit switched. Short double periodical flashes
indicate that the modem is logged in to GPRS. Possible reasons are -SIM card
protected by a PIN -no antenna connected to the modem -no network
coverage.
Wrong phone number configured at NE.

Ensure that the SIM card is allowed to make data calls. In many cases SIM
cards have different phone numbers for voice and data calls.
Interoperability problems of wireline modems to wireless modems. It has been

detected that some mobile networks do not allow modem connections
between wireline and wireless modem.
Password not stored in the reversible encryption format. Ensure that the
security policy allows storing the password of the dial-in user in a reversible
encryption format (ref. chapter 13.1.1). After changing this option, the
password of the dial-in user needs to be set again.
Dial-in user defined at the wrong location. Windows allows adding users on a
local machine or within a domain. If A.I.M.O.S runs as on a standalone
machine the dial-in user must be defined locally. If A.I.M.O.S runs on a
machine that is part of a windows domain, the user can be defined locally or
within the domain. If the user is defined locally, the format on the remote
machine must be: <server name>\<user name> (ref. to chapter 13.1.2).
The Remote Desktop Connection (RDC) to A.I.M.O.S. stops when a connection to an

NE is built up:
MS Windows always adds an outgoing RAS connection to the routing table during
connection setup. Especially in cases where NEs and client are in the same network
address range (e.g. addresses of A.I.M.O.S., clients and NEs all start with 10.x.y.z ),
the Windows OS chooses the better route through the NE as soon as the connection
to the NE is established and the RDC drops.
Page 223

If a RAS connection to an NE is built up from A.I.M.O.S. server, check whether:
a) A ping goes through from RMC / client to A.I.M.O.S. and vice versa. If not, fixed
routes have to be defined.
b) All required ports are open throughout the entire path. If ping works both ways but
either alarming or web-interface do not work, the ports on the link have to be
revisited.
10.2
TECHNICAL SUPPORT
If a question arises about A.I.M.O.S. or the equipment, first look in the A.I.M.O.S.
documentation or consult online help. If the answer cannot be found, please do not
hesitate to contact CommScope Solutions product support:
+49 90 99 69 333 Germany
WIsupport@commscope.com
When you call, you should have the appropriate product documentation at hand.
Please be prepared to give the following information:
Version number of A.I.M.O.S. software.
Type of server/modem hardware incl. network hardware and network structure.
OS (operating system).
Exact content of any messages that appeared.
A description of how the error occurred.
The repeater hard- and software information (if applicable).
To speed up the trouble analysis, prepare the following:
1. System Information tool
Start the System Information* in
Start menu
Confirm all screens with OK:
(this screen is only visible with Win7:)

*
For Windows 7 / 2008 starting the "System Information" tool with the option "Run As
Administrator..." is mandatory.
Page 224
M0125ANA.DOC
10 Troubleshooting
In the background, the following status screen is displayed during the process:
The final screen shows the location of the file containing the script created in
this process:
Send this file to technical support.

2. Visu Logs
Sending the Visu Log files to technical support, as well, also serves to speed up the
analysis.
The Visu Log files can be created using the Excel Export in the Log tab* (see
chapter 6.8.5):
* Please observe that the Log tab must first be activated via the Preferences Editor Other
Settings Show Visu Log (see chapter 5.2) since it is deactivated by default.
Page 225
3. Major SW Errors
From A.I.M.O.S. V2.8.0 onwards major SW errors (e.g. Access Violation, Stack
Overflow, Out of Memory, etc.) will be communicated to the customer as follows:
In such a case a 'bug report' can be sent to our Technical Support

(WISupport@commscope.com), which will make it easier for us to locate and fix the
problem. If the according computer is not capable of sending out e-mails, use the
button "save bug report" to create a text file which can then be sent from another
computer.
Note: If Application seems to be frozen is displayed as exception message
(last line), and the program up time (in the middle of the window)
shows a value of around 10 minutes, close the window by the button
.
You should then be able to continue without error. In that case
contacting the Technical Support is not required.
Page 226
M0125ANA.DOC
10 Troubleshooting
10.3
LICENSE INSTALLATION
The following error messages might be prompted during the license installation:
'You are not allowed to install the following license:'
The A.I.M.O.S. user has not the right to install a license.
Another A.I.M.O.S. user who is allowed to install a license (e.g. Admin) must
be used.
'The following license cannot be used for your organization:'
A license for another Organization has already been installed or a license for
another Organization was installed and has been deleted (e.g. 244004). The
MCNC of the license to be installed and the previous one do not match.
A new installation or a database restore (a backup prior to the initial license
installation) is required.
'The following license is invalid:'
The license is not valid, i.e. it was probably changed / damaged.
Please contact Technical Support.
'The following license is not valid for A.I.M.O.S. V2.x.x.x:'
The versions of the license and of A.I.M.O.S. do not match.
A new license must be requested.
'The installation of the following license has failed:'
The database is probably damaged.
Please generate a database backup and contact Technical Support.
Page 227

For your notes:
Page 228
M0125ANA.DOC
11 Glossary
11 GLOSSARY
A.I.M.O.S.
Andrew Integrated Management and Operating System
Company Kind
The kind of company is automatically added when a new organization is added.
Company kind can be: 0 = Telecommunication company (Telco) or 2 = Provider.
DCM1
Digital Channel Module of the 1st generation used in Node M/C two-box repeaters.
The successive one-box models are equipped with the DCM2 module.
ION
Intelligent Optical Network; two systems are available:
ION-B = Intelligent Optical Network - Britecell
ION-M = Intelligent Optical Network - MMR (= successor of MMR)
LDAP
Lightweight Directory Access Protocol (= application protocol for reading and editing
directories over an IP network).
MANAGEMENT INTERFACE
The Management Interface displays all information available for the selected system
or NE. If settings or values can be changed, the possible changes are displayed in
different colors.
MCC
Mobile Country Code. Unique identifier for Network Providers
MCNC
Mobile Country-Mobile Network Code / Organization Code. Consists of the MCC and
the MNC and is used in A.I.M.O.S. as unique identifier for the Network Provider.
MIB
Management Information Base
MMR
MMR optical systems are the predecessor of the ION-M system. From A.I.M.O.S.
Version 2.8 onwards the designation 'ION-M' replaces 'MMR' in the software.
MNC
Mobile Network Code: Unique national identifier for Network Providers
MU OTRx
Master Unit Optical Transceiver (equals SRMU): Optical transceiver in an ION-M
system. This term is gradually replacing the former designation SRMU.
Page 229

NE
Network Element
NE3S
Nokia Enhanced SNMP Solution Suite
NMS
Network Management System
RDN
Relative Distinguished Name: Unique identifier for a component in the subsystem the
component is a member of.
SASL
Acronym for Simple Authentication and Security Layer. SASL is a method for adding
authentication support to connection-based protocols. SASL takes effect when a
protocol initiates a command for identifying and authenticating a user to a server.
SASL also includes an option for negotiating protection of subsequent protocol
interactions. With this option in effect, SASL places a security layer between the
protocol and the connection.
SDN
System Distinguished Name: Unique identifier for a repeater system, consisting of
several RDSs.
SMPP
Short Message Peer-to-Peer protocol: The SMPP protocol is a telecommunications
industry protocol for exchanging SMS messages. The SMPP protocol version
supported by A.I.M.O.S. is V3.4.
SMSC
Short Message Service Centre: To use a SMPP protocol a SMSC must be reachable
from the A.I.M.O.S. server over an IP connection, and the SMSC must provide a
SMPP account that supports both sending and receiving short messages over a fix
phone number.
SRMU
Subrack Master Unit (equals MU OTRx): Optical transceiver in an ION-M system.
This designation is gradually replaced by the new term MU OTRx.
UTC
Coordinated Universal Time, the official measure of time in the world, which is
independent from the time zones. Such a measure is calculated as a statistical
average of several worldwide atomic clocks and it's periodically corrected by adding
or subtracting the "Leap Second" to keep the difference between UTC and Earth
rotation time below 0.9 seconds. In practice UTC corresponds to the Greenwich
Mean Time (GMT), the mean solar time of the zero meridian crossing Greenwich
(Great Britain).
Page 230
M0125ANA.DOC
12 Appendix A Modem Installation and Configuration
12 APPENDIX A MODEM INSTALLATION AND CONFIGURATION

This chapter describes the procedure for the modem installation. This procedure has
to be done for each modem.
Depending on the operating system the configuration menu is called via the following
menu:
Start -> Settings -> Control Panel -> Phone and Modem Options
or
Start -> Control Panel -> Phone and Modem Options

The following figures show how to configure the modem.
This picture shows how to set the
location
information.
These
parameters do not have any
relevance for the dial-in/dial-out
configuration,
but
Windows
requires setting them.
Modem configuration, location information

After the entered data are
confirmed with the OK button, a
new window will appear.
Modem configuration, Dialing Rules
Page 231
Selecting the modems tab shows the

installed modems.
Click on the Add button in order to

add a modem.
Modem configuration, Modems

The following window will appear.
Flag the option Dont detect my

modem; I will select from a list. Then
press Next
Modem configuration, install new modem
Select the correct manufacturer and

model of your modem.
Modem configuration, install new modem, select modem type
Page 232
M0125ANA.DOC
12 Appendix A Modem Installation and Configuration
Select the COM port that is used

to connect the modem.
Modem configuration, install new modem, select COM port
Click on Finish to complete

your modem configuration.
Modem configuration, install new modem, finish

A new window appears.
Click the
button.
Properties
Modem configuration, Modems
Page 233
Click the Diagnostics tab and then Query Modem button. If the
communication with the modem is possible, the window will change.
Modem configuration, Diagnostics (1)
Modem configuration, Diagnostics (2)
In the Advanced Tab select the Change Default Preferences ... button.
Ensure that Flow Control = Hardware is selected.
Modem configuration, Advanced
Change Default Preferences
Click OK twice to finish the modem configuration.
Page 234
M0125ANA.DOC
13 Appendix B Dial-In Connectivity

13.1 Dial-In Server Configuration
13 APPENDIX B DIAL-IN CONNECTIVITY

The following chapters contain the descriptions for setting up a remote access
server. The screenshots displayed may be slightly different depending on the
operating system language settings and exact version of the operating system.
13.1
DIAL-IN SERVER CONFIGURATION
Please observe that the setup described (screen shots are taken from a Win2003
server) is the recommended setup, but not mandatory. Since the procedure for
Win2008 is similar this description can be used as well, but please observe that
some screens may look slightly different.
The following dial-in authentication Node X
method is used:
13.1.1
ION-M (MMR)
Britecell /ION-B
MD5-CHAP
Security Policy
The users password needs to be stored in a way that allows windows to decrypt the
password. This is a prerequisite for the MD5-CHAP authentication algorithm to work
successfully.
The procedure for the setting of the Security policy depends on the fact whether the
A.I.M.O.S computer is a standalone machine or part of windows domain.
13.1.1.1
Local Security Policy
This chapter is applicable only for an A.I.M.O.S machine that is not part of a windows
domain.
The Local security Policy management console can be opened via:
Start Administrative Tools Local Security Policy
Ensure that the effective setting of the option Store password using reversible
encryption for all users in the domain is set to enabled. After changing the value, do
a right-mouse click on security settings in the left window and select the option
reload in order to retrieve the current effective setting of the value.
Local Security Policy:

Note: If the dial-in user already exists before changing the Local Security Policy, the
password has to be set again in order to ensure that the password is stored in
the correct mode.
Page 235
13.1.1.2
Domain Security Policy
This chapter is applicable only for an A.I.M.O.S machine that is part of a windows
domain. In this case the domain settings override the local settings.
Go to administrative tools/active directory users and computers.
Double-click on the dial-in user (e.g. altegr) and select account:
Enable "store password using reversible

encryption" and apply:
Note: If the dial-in user already exists
before changing the Domain Security
Policy, the password has to be set again
in order to ensure that the password is
stored in the correct mode.
Page 236
M0125ANA.DOC

Select again dialin user (altegr)
Make a right click
on it and select
Set password...
Set the password again:
Note:
The
domain
security policy is
not affected by
these
settings;
"Store passwords
using reversible
encryption" is still
disabled for all
other users.
Default Domain Security Settings
Default Domain Controller Security Settings
Page 237
13.1.2
User Account Data
The User Account can be added as local user on the A.I.M.O.S. machine or as a
domain user on the windows domain server. This is described in the following
chapters.
13.1.2.1
Adding a Local Dial-in User
In case of an A.I.M.O.S system that is not part of a windows domain, the dial-in user
must be added as a local account. If the A.I.M.O.S system is part of a windows
domain, the dial-in user can be added locally as described in this chapter or as a
domain user (ref. to next chapter 13.1.2.2).
The user configuration can be opened as follows: Right click on My Computer
Manage.
The following window will appear.
Computer Management, Users

In the left part of the window select Computer Management -> System Tools ->
Local Users and Groups -> Users. In the main window, do a right-mouse click and
select the option New User. The window New User appears. Fill in as follows:
The default username/ password is
altegr/altegr. Please ensure that all
remote elements (ION/MMR, Node X,
Britecell) are configured to use this
login. In this configuration the user on
the remote device can be set to either
altegr or <server name>\altegr. Both
options work.
Uncheck the option User must
change password at next logon.
Note: Verify if User cannot change
password needs to be set. Set the
check-mark for Password never
expires.
Click the button Create in order to
create the user and press the Close
button.
Page 238
Computer Management, New User
M0125ANA.DOC

The next window appears:
Computer Management, Users

The new user has to be configured as a dial-in user. Select the user altegr. Do a
right-mouse click and select Properties.
In the following window

select the Dial-in tab.
In the Dial-in tab ensure that Remote

Access Permission (Dial-in or VPN) is
set to Allow access.
Click Apply and OK.
Computer Management, user properties, General (left) and Dial-in (right)

This finishes the dial-in user account configuration.
Windows uses the following mechanism to find a dial-in user:
If the A.I.M.O.S machine is not part of a windows domain, it searches for a local user
account.
If the A.I.M.O.S machine is part of a windows domain, windows uses the following
mechanism to find the user:
If during the dial-in procedure, the dial-in user is given in the format <A.I.M.O.S
server name>\<username>, windows searches for a local user account.
Page 239

If during the dial-in procedure, the dial-in user is given in the format <domain
name>\<username>, windows searches for a domain user account,
If during the dial-in procedure, the dial-in user is given in the format <username>,
windows searches for a domain user account.
13.1.2.2
Adding a Domain Dial-in User
On the domain server the domain user configuration can be opened as follows: Right
click on My Programs->Administrative Tool->Active Directory Users and Computers.
The following window will appear:
Active Directory Users and Computers

Select Users in the left part of the window, do a right-mouse click on the main
window, and select New -> User. The following window appears:
The default username/ password is
altegr/altegr.
Please ensure that all remote elements
(ION/MMR, Node X, Britecell) are
configured to use this login.
In this configuration the user on the
remote device can be set to either
altegr or <domain name>\altegr. Both
options work.
Press Next.
Active Directory Users and Computers, New User (1)
Page 240
M0125ANA.DOC

Ensure Password never expires is
checked and press Next.
Press Finish.
Active Directory Users and Computers, New User (2) and New User (3)
Active Directory Users and Computers, Properties

Select the user you just added, do a right-mouse click on the main window and select
Properties
Page 241
Ensure that password never expires is

checked.
Select the Dial-in tab.
In the Dial-in tab,

ensure that Allow access is checked.
Active Directory Users and Computers, Account (left) and Dial-in (right)
This finishes the domain user configuration.
The RAS service shall be enabled via the Windows Routing and RAS service.
Incoming Connections, which are configured via the Settings->Network and Dialup
Connections, have to be removed before.
13.2
REMOTE ACCESS SERVER CONFIGURATION FOR WIN2003 SERVER

STANDARD EDITION
13.2.1
The RRAS server configuration can be started via Start Programs

Administrative Tools Routing and remote access.
The configuration consists of the following parts:
RRAS server configuration wizard
RRAS server configuration properties
Configure RRAS policy
The configuration is not possible, if the windows firewall is running. It must be
stopped and disabled during the configuration of the RRAS service. It can be started
again afterwards.
It needs to be taken into account that the firewall must be configured to receive traps
on UDP port that is configured in A.I.M.O.S. (default value = 162).
Page 242
M0125ANA.DOC

13.2 Remote Access Server Configuration For Win2003
S
S
Both Windows Firewall and the routing and RAS server use the same
resources. So, before the RRAS can be started the firewall needs to be
disabled. The routing and RAS service also provides a firewall service:
If a firewall is running proceed as follows:
Select "Start - Control Panel - Windows Firewall"
On the general Tab ensure that the firewall is switched off.
Now stop and disable the Windows FW (windows firewall/internet connection
service(ICS)) service via 'Start-Administrative Tools'.
Now configure the RRAS service: select Start Administrative Tools Routing
and Remote Access.
In the left part of the window
do a right-mouse click on
<hostname>(local)
and
select configure and enable
Routing
and
Remote
Access.
RRAS (1)
A new window pops up.
RRAS (2)
13.2.2
Select
Remote access server
and press Next.
RRAS, Routing and Remote Access Server Setup

Page 243
Select Dial-up and press Next.
Select From a specified range of

addresses and press Next.
RRAS, IP address assignment

RRAS, Remote Access
Press New in order to add a

static pool of IP addresses.
RRAS, Address Range Assignment
Add an IP range according to your preferences. Ensure to reserve enough IP
addresses (1 for the RAS server + 1 for each remote device that can be connected
simultaneously the minimum number of IP addresses is the number of modems
connected to the system increased by one).
RRAS, New Address Range

RRAS, Address Range Assignment
Page 244
M0125ANA.DOC

S
S
Select No, use Routing
and Remote Access to
authenticate connection
reqests and press Next.
RRAS, Managing Multiple Remote Access Server
RRAS, Completing the Routing and Remote Access Server Setup Wizard
13.2.3
Open the RRAS server configuration via Start Programs Administrative Tools
Routing and remote access.
In the left part of Routing and RAS window, do a right-mouse click on

<hostname>(local) and select Properties.
Page 245

In the Security tab press the button
Authentication Methods.
In the General tab select

Remote access server.
RRAS, Properties, General (left) and Security (right)
Only check
(CHAP)
Encrypted
authentication
RRAS, Authentication Methods

In the IP tab, ensure that Allow IP-based
remote access and demand-dial connections
is set.
In the PPP tab, all flags shall be

unchecked.
RRAS, IP
RRAS, Properties, PPP
Page 246
M0125ANA.DOC

S
S
RRAS, Ports
In the left window select Ports, do a right-mouse click, and select Pproperties.
Select the device to be used for RAS
and click on Configure.

RRAS, Ports, Properties
Set the flag for Remote access connections (inbound only).
Configure Device
Page 247
13.2.4
RRAS Policy
A new policy needs to be created.

In the left part of the window select <hostname> (local) Remote Access Policy.
Do a right-mouse click in the main window and select the option to define a new
policy.
RRAS, policy
The RRAS Policy Wizard starts:
Press Next.
Select the option Set up a custom

policy and enter any policy name.
RRAS Policy Wizard: Policy Configuration Method
Page 248
M0125ANA.DOC

S
S
Click on the Add button to define the Select
Day-And-Time-Restrictions
and click on the Add button.
policy conditions.
RRAS Policy Wizard: Policy Conditions (left) and Select Attribute (right)
Ensure that the permission is granted at
any time and click OK.
Confirm with Next.
RRAS Policy Wizard: Time of day constraints (left) and Policy Conditions (right)
Ensure that Grant remote
permission is selected.
access
Click on Edit Profile.
RRAS Policy Wizard: permissions (left) and Profile (right)
Page 249

In all Edit Dial-in Profile tabs illustrated in the following set the flags as illustrated:
RRAS Policy Wizard, Edit Dial-in Profile: Dial-in Constraints (left) and IP (right)
In the Authentication tab, ensure that
ONLY Encryption authentication
(CHAP) is selected.
RRAS Policy Wizard, Edit Dial-in Profile: Multilink (left) and Authentication (right)
Page 250
M0125ANA.DOC

S
S
RRAS, policy wizard, Edit Dial-in Profile, Encryption (left) and Advanced (right)
Click Finish to complete the Policy Wizard.
RRAS, policy wizard

Ensure to restart the RRAS service:
<hostname>(local) and select All Tasks -> Restart.
Page 251
13.3
REMOTE ACCESS SERVER CONFIGURATION FOR WIN2008
The following chapters contain the descriptions for setting up a remote access
server. The screenshots displayed may be slightly different depending on the
operating system language settings and version of the operating system.
13.3.1
To install the Routing and Remote Access proceed as follows:

Install Windows Server 2008.
Click Start Administrative Tools Server Manager.
Under Roles Summary, click Add roles.
Click Next.
Select the Network Policy and Access Services role
and click Next.
Page 252
M0125ANA.DOC

13.3 Remote Access Server Configuration for Win2008
Select the Network Policy Server and the Routing and Remote Access Services.
and click Next.

Note: The check-marks for the subordinate Remote Access Service and Routing
will be set automatically.
Click Install.
When the Installation Results dialog box appears, click Close.
Page 253
13.3.2
Use the following steps to configure and enable the Routing and Remote Access
service:
Click Start, Administrative Tools, Routing and Remote Access:
By default, the local computer is listed as a server. Right-click the server, and then
select Configure and Enable Routing and Remote Access:
Page 254
M0125ANA.DOC

Click Next.
Click Custom configuration, and then click Next.

Select all the services except NAT.
Continue the Wizard as illustrated and click Next to get to the next screen.
Page 255
Select From a specified range of adresses
Page 256
M0125ANA.DOC

Select New
Add IP address.
Make sure that

enough
IP
addresses
are
available (one for
the RAS server
and one for each
remote connection
that
shall
be
possible
simultaneously).
At
least
the
amount of modems
connected shall be
reserved.
Select Next.
Page 257
Select No. and click Next.
Click Finish.
Click OK, click Start service, and then click Finish.
Page 258
M0125ANA.DOC

13.3.3
Open the RRAS server configuration via Start Programs Administrative Tools
Routing and remote access.

<hostname>(local) and select Properties.
In the General tab select
IPv4 Remote access server.
In the Security tab press the button

Authentication Methods.
RRAS, Properties, General (left) and Security (right)
Page 259
Only
check
Encrypted
authentication (CHAP)
RRAS, Authentication Methods

In the IPv4 tab, ensure that Enable IPv4
Forwarding and Static address pool are
tagged. Choose Allow RAS.
RRAS, IP
Page 260
In the PPP tab, all flags shall be

unchecked.
RRAS, Properties, PPP
M0125ANA.DOC

RRAS, Ports
In the left window select Ports, do a right-mouse click, and select Properties.
Select the device to be used for RAS
and click on Configure.

RRAS, Ports, Properties
Set the flag for Remote access connections (inbound only).
Configure Device
Page 261
13.3.4
Network Policies
A new policy needs to be created.

In the left part of the window select Start Administrative Tools Network Policy
Server Policies Network Policies.
Do a right-mouse click in the main window and select the option to define a new
policy.
Enter a Policy name

and
select the Type of

network access server.
Continue with Next.
Click Add to specify

the conditions.
Page 262
M0125ANA.DOC

Select the Day and Time Restrictions
and click the Add button.
Ensure that permission is

granted at any time and click
OK.
Confirm with
Next.
Page 263
Select that Access is

granted.
If required, click Add to

add the EAP types shown in the following.
Make sure that ONLY

Encryption authentication (CHAP) is selected and continue with Next.
Page 264
M0125ANA.DOC

Continue with Next.
Click Finish to complete the New Network Policy.
Page 265
13.4
TESTING THE REMOTE ACCESS SERVER CONFIGURATION
The procedure described in this chapter is not a mandatory installation step, but
allows verifying that the configuration of the RAS server was successful.
An extra modem is required to run this procedure. The extra modem is configured for
a dial out connection and connects to the RAS server. The two involved modems can
be installed on the same or on different computers.
13.4.1
For setting up the dial-out connection, open the Network connection window (Start>Settings->Network Connection). Start the New Connection wizard.
Network Connections
Click Next and make the

settings as illustrated in the
following:
Network Connection Wizard (1)
Page 266

M0125ANA.DOC

13.4 Testing the Remote Access Server Configuration
Select the modem that you

want to use for the outgoing
connection.
Select a name
connection.
for
this
Page 267
Enter the phone number of

the modem for the incoming
connection.
Ensure that Anyones

use is tagged.
Enter the user name

password that you used for
the RRAS server/incoming
connection. The default is
altegr/altegr.
Page 268
M0125ANA.DOC

Before completing the New

Connection Wizard with
Finish you can choose to
Add a shortcut to this
connection by setting the
according flag.
Press the Dial button. After

a while the system should
indicate that the network
connection was successfully
setup.
Start dial out connection
Page 269
13.4.2
First, a new dial-out connection has to be created. To do so, choose, Start

Control Panel Network and Sharing Center Set up a new Connection or
Network.
Choose Set up a dial-up

connection
and click Next.
Set Up a Connection or Network
Select the modem to

be used for the
outgoing connection.
(Depending on the
system setup you
may also need to click
Next to get to the
next screen.)
Create a Dial-up Connection (1)
Enter the phone number of
the
modem
for
the
incoming connection, as
well as the user name and
password that you used for
the RRAS server/incoming
connection. The default is
altegr/altegr.
Type in
name.
connection
Ensure that Allow other

people is tagged.
Click Connect.
Page 270
M0125ANA.DOC

In case the following error

message appears (e. g. if
the modem is not on or at
the first setup) select to Set
up the connection anyway.
The connection setup is

now finished.

To configure the new dial-out connection, proceed as explained in the following.
Choose Start Control Panel Network and Sharing Center Change
Adapter Settings:
Select the newly created dialout connection by a right-mouse

click and choose Properties.
Page 271
In the Networking tab select the Internet In the Internet Protocol Version 4
Protocol Version 4 (TCP/IPv4) and (TCP/IPv4) Properties set the tags as
shown below and click Advanced:
choose Properties:
In the Advanced TCP/IP Settings set the tags as shown and set the Interface Metric
to 1:
Confirm with OK.
Page 272
M0125ANA.DOC
14 Appendix C HTTPS Certificate Handling

14.1 Certificate Selection
14 APPENDIX C HTTPS CERTIFICATE HANDLING

In order to cause A.I.M.O.S. to use HTTPS not only within the WEB tab card
(integrated WEB browser) but also during a file upload / SW update, it is necessary
to install the certificate at the A.I.M.O.S. server into the 'Local Computer' certificate
store. To do so, proceed as follows
14.1
CERTIFICATE SELECTION
The recommended way to select the certificate is to use the Security Alert of the Web
tab card as explained on the next page. It is, however, also possible to select the
certificate via the Internet Explorer. To do so, choose Continue to this website (not
recommended) when the first-time connection to the NE is not successful.
Click Certificate Error to continue.
To select the certificate choose View certificates
Then, continue with the installation (see 14.2).
Page 273

The more direct way to select the certificate is using the Security Alert of the Web
tab card. This alert will be opened when the Web tab card for an NE is opened for the
first time if the NE supports HTTPS and HTTPS is selected as encryption type in the
WEB Server Configuration (see chapter 6.9.5.5):
Click View Certificate to continue.

Then, proceed with the installation as follows:
14.2
CERTIFICATE INSTALLATION
Note: For remote A.I.M.O.S. clients it is necessary to import the certificate at each
client machine (per Windows user: standard import; or for all users: import to 'Local
Computer' store).
Click Install Certificate .
Page 274
M0125ANA.DOC
14 Appendix C HTTPS Certificate Handling

14.2 Certificate Installation
Browse
to the Trusted Root Certification Authorities and tag Show physical stores to
display the Local Computer directory to install the certificate there. Otherwise the
certificate will be installed to the default Registry directory and will only be available
for the current user:
Choose the Local Computer
directory to make certificate available
for all Windows user accounts of the
machine including the 'Local System
account' which is the logon account
used by the A.I.M.O.S. Connector
service (that actually performs the
HTTP upload requests during the
corresponding schedules).
Click OK to continue.
Click Yes if presented with the following warning.
The successful certificate import will be confirmed as follows:
Click OK to end the procedure.
Page 275

For your notes:
Page 276
M0125ANA.DOC
15 Index
15 INDEX
? Menu ................................................................. 99
A.I.M.O.S.
Backup/Restore Database ..................... 205, 206
Components .................................................... 19
Main Program .................................................. 91
Rights .............................................................. 72
Validate.......................................................... 208
Visu Version Info.............................................. 99
Account Management........................................... 70
Account Manager ................................................. 67
NE Owner ........................................................ 79
Organizations................................................... 69
Roles ......................................................... 70, 76
Users ............................................................... 77
Accounts, Enable............................................ 45, 78
ACK Capability ..................................................... 84
Actions, Scheduler.............................................. 158
Adapter, OMC 3.54......................................... 72, 88
Add
Folder ............................................................ 123
License ............................................................ 40
New Network Element ........... Look Up New NE
Administrator Role .......................................... 72, 76
AgentSim ............................................................ 213
Alarm
Forwarding....................................................... 70
Help ............................................................... 127
History ........................................................... 127
Latency .......................................................... 133
Limiter .............................................................. 42
List ................................................................. 126
Polling .............................................................. 87
Polling, Settings ............................................... 59
Profiles................................................... 196, 199
Representation ................................................ 59
Settings............................................................ 57
Severities ....................................................... 133
Thresholds ..................................................... 134
Type................................................................. 57
Alarms
Alarming Enabled ............................................ 96
Export ...................................................... 93, 126
External.......................................... 121, 122, 132
Flash .............................................................. 186
Import .............................................................. 94
Message ........................................ 112, 116, 120
Port Assignment ............................................ 120
Query ..................................................... 123, 161
Recognize, Select All....................................... 98
Text in Extra Line............................................. 97
Alternate SNMP Agent, IP Address / Port ............ 49
Andrew OMC 3.54 ................................................ 88
Any New Network Element ................................. 108
Assigned Folder, Role .......................................... 78
Auditory Alarm Notifications ................................. 89
Automatic Backup................................................. 89
Backup/Restore
Database ......................................... 89, 205, 206
NE Configuration ........................... 125, 136, 159
Server Configuration Tool Settings .......... 39, 207
CC Concatenator.................................................. 70
ComasTest ......................................................... 215
CommScope........................................................... 9
Configuration
A.I.M.O.S. .................................................39, 205
Alarm System ................................................ 160
Connectivity ................................................... 138
Data ............................................................... 125
Dial-In ............................................................ 139
Dial-In Server................................................. 235
Email Forwarding............................................. 51
File, Send ...................................................... 161
File, Upload ................................................... 162
Function......................................................... 128
GPS-Based.................................................... 132
Group Profile, Select...................................... 107
Group Profile, Set .......................................... 198
LDAP ............................................................... 46
Modem......................................................24, 231
Port ................................................................ 120
Remote Access / RRAS Server Win2003 ...... 242
Remote Access / RRAS Server Win2008 ...... 252
Server .........................................................23, 39
WEB Server................................................... 146
Configuration Tool .. Look Up Server Configuration
Connectivity........................................................ 128
Connectivity Management .................................... 70
Connectivity Manager........................................... 61
Modem Management....................................... 61
Modem Properties, Settings ............................ 62
Modems (Discover, Groups) ............................ 63
Profiles............................................................. 64
Wireless Status................................................ 62
Connector Logs .................................................... 98
Contact Addresses ....................................10, 11, 12
Coordinated Universal Time ................................. 70
Create Export ..................................................... 175
Create Performance Data Chart......................... 172
Database Administration Tool ............................ 205
Database Version Info .......................................... 99
Declaration of Conformity ....................................... 9
Default Port, Outgoing SNMP Traps .................... 49
Email .................................................................... 52
Enable, Accounts ............................................45, 78
Event Triggered Actions ..................................... 159
Excel Export ......................................................... 93
Alarm Data..................................................... 188
Alarm List....................................................... 126
Alarm Profile Settings .................................... 200
Backup List, HID ............................................ 136
Job List .......................................................... 180
Logs (Visu Logs).....................................138, 182
NE List ........................................................... 179
Notes ............................................................. 138
User Data ........................................................ 80
Export
Create............................................................ 175
NE Backup to File ............................................ 94
Profiles........................................................... 201
Users ............................................................... 80
via ODBC......................................................... 88
XML File .......................................................... 93
External I/Os....................................................... 132
External Tools
Profiles........................................................... 202
Extras Menu ......................................................... 98
Page 277

Fade Out ............................................................ 180
Field Chooser ............................................. 104, 111
File Menu.............................................................. 92
File Upload ......................................................... 162
Filters
Conversion of Filter Type............................... 108
Custom Filter ................................................. 105
Customize in Scheduler ................................. 151
Filter Builder................................................... 105
Filter Settings................................................. 107
Import from Scheduler ................................... 107
NE Filter (Builder) .................................. 105, 106
NE List ........................................................... 179
Static/Dynamic............................................... 107
Table Filters ................................................... 103
Folder
Add ................................................................ 123
Assigned .......................................................... 78
Footer ................................................................. 104
Functions (Bar) ............................................. 91, 125
Generated Community Names ............................. 49
GPS Position ...................................................... 128
Alarms ........................................................... 126
Get......................................................... 124, 128
Show Columns............................................... 103
Trap Format ..................................................... 82
Visualization..................................................... 60
GPS-Based Configuration .................................. 132
Grid Layouts ....................................................... 104
Group Profile, Select .......................................... 107
Group Profile, Set ............................................... 198
Hardware Inventory Data.................................... 136
Heartbeat............................................................ 128
HELO Name ......................................................... 52
Housekeeping....................................................... 55
HW/RF................................................................ 132
IE Settings ............................................................ 17
Import
Alarms, Organizations ..................................... 94
Users ............................................................... 80
XML File................................................... 92, 153
Including NEs to the Map ................................... 184
Inventory Data .................................................... 136
IP Address / Port, Alternate SNMP Agent ............ 49
Job Monitor......................................................... 180
LDAP .................................................................... 46
Legacy Taskbar .................................................... 60
Licenses ......................................................... 33, 40
List of Backups ................................................... 207
Local Time ............................................................ 70
Lockout Settings ................................................... 45
Log Feature .................................................. 60, 138
Login............................................................... 35, 48
Change ............................................................ 94
Configuration, WEB ....................................... 145
Loggings ........................................................ 181
SASL ............................................................... 53
SNMP .............................................................. 49
WEB Profiles............................................ 66, 135
Maintenance, Function ....................................... 136
Maintenance, Tool .............................................. 205
Management Interface.......................................... 91
Map .................................................................... 182
Buttons, Check Boxes ................................... 182
Include Subunits ............................................ 186
Including NEs................................................. 184
View............................................................... 186
Page 278
MapPoint 2006, 2009 ......................................... 182

MCC, MCNC .................................................69, 229
Menu Bar.............................................................. 91
Menus................................................................... 92
? Menu............................................................. 99
Extras .............................................................. 98
File................................................................... 92
Tools................................................................ 95
Tree ................................................................. 95
View................................................................. 97
Windows .......................................................... 99
MIB ................................................................50, 229
MIB, Test Program ............................................. 216
Minimum Password Length .................................. 44
MMR................................................................... 229
MNC ..............................................................69, 229
Modem (Groups, Usage) ...................................... 63
MU OTRx ........................................................... 229
NE ...................................................................... 230
Filter (Builder) .........................................105, 106
List ................................................................. 179
New ............................................................... 108
Number.......................................................... 181
Operations ..................................................... 123
Owner, Account Manager ................................ 79
Owner, Northbound Manager .......................... 85
Tree ..........................................91, 100, 108, 125
Vector Map .................................................... 182
NE3S .......................................................50, 84, 230
Network Element ................................ Look Up NE
Network Policies Win2008.................................. 262
New NE .............................................................. 108
AMR............................................................... 113
DICE .............................................................. 120
Generic, 1, 2 ...........................................121, 122
ION-B............................................................. 115
ION-E System................................................ 117
ION-M ............................................................ 118
ION-M miniMaster.......................................... 121
ION-U System ............................................... 117
MCPA ............................................................ 114
MIR-T............................................................. 121
MR2003P, MR2133 ....................................... 122
MRx18 ........................................................... 120
Node X........................................................... 109
SMS-Connected NE ...................................... 119
NMS ................................................................... 230
Node X ................................................................. 15
Nokia Enhanced SNMP Solution Suite............... 230
Northbound Interface............................................ 49
Northbound Manager............................................ 81
NE Owner ........................................................ 85
Notes .................................................................. 138
ODBC ................................................................... 88
Off Duty, System .........................................130, 161
OMC Version Info................................................. 99
OMC3 ................................................................... 51
Adapter .....................................................88, 203
Backup/Restore Database..............205, 206, 207
Rights .............................................................. 72
Validate Database ......................................... 208
Online Help........................................................... 15
Organization Code ............................................... 40
Organizations, Account Manager ......................... 69
Outgoing SNMP Traps, Default Port .................... 49
Parent Map......................................................... 182
M0125ANA.DOC
15 Index
Password
Lockout Settings .............................................. 45
Node A(M) ..................................................... 172
Settings...................................................... 44, 45
Performance Data Chart, Create ........................ 172
Performance Data, Read .................................... 171
Performance Manager ........................................ 186
Preferences Editor................................................ 57
Alarm Polling, Settings..................................... 59
Connectivity Pages .......................................... 58
Scheduler Settings........................................... 58
Severity Icons .................................................. 59
Private SNMP Community Name ......................... 49
Profiles ............................................................... 196
Query Alarms.............................................. 123, 161
Query All............................................................. 124
RDN.................................................................... 230
Concatenator, Separator, Translation.............. 70
Read Only User Role............................................ 76
Read Performance Data ..................................... 171
Recognize Trap .................................................... 84
Removing NEs from the Map.............................. 185
Replace, System ................................................ 161
Restore ...........................Look Up Backup/Restore
Revision Info....................................................... 136
Rights, Account Manager ..................................... 70
Roles .................................................................... 76
Account Manager............................................. 70
Administrator.................................................... 76
Standard User.................................................. 76
RRAS Policy Win2003........................................ 248
RRAS Server Properties Win2003...................... 245
RRAS Server Properties Win2008...................... 259
SASL .................................................................. 230
Login ................................................................ 53
Scheduler ........................................................... 148
Actions ........................................................... 157
Connectivity Settings ..................................... 150
Create Performance Data Chart .................... 172
Customize Actions ......................................... 152
Customize Network Elements........................ 151
Customize Schedule...................................... 149
File Upload..................................................... 162
Read Performance Data ................................ 171
Software Update ............................................ 166
XML Import .................................................... 153
SDN.................................................................... 230
Select New NE ........................... Look Up New NE
Server Configuration............................... 23, 39, 207
Severity Colors ..................................................... 57
Severity Icons ....................................................... 59
Show Alarm Help.......................................... 99, 126
SMPP ........................................................... 53, 230
SMPP-Gateway .................................................... 53
SMSC ........................................................... 53, 230
SMS-Connected NE, Add ................................... 119
SMTP ................................................................... 51
SNMP
Agent ..................................................48, 81, 203
Agent Shutdown Delay .................................... 49
Alarm Forwarding .......................................70, 81
Alarm Traps ..................................................... 81
Alternate Agent IP Address, Port ..................... 50
GUI ................................................................ 203
Manager Settings............................................. 81
MIB Version Info .............................................. 99
Northbound...................................................... 48
Outgoing Traps................................................ 48
Private Community Name................................ 49
Traps ............................................................... 70
UDP ................................................................. 48
V2C.................................................................. 70
Software Update................................................. 166
Sort Options ....................................................... 104
SRMU..........................................................229, 230
Standard User Role .............................................. 76
Status Bar........................................................91, 92
Supervision Tab ................................................. 126
System Off Duty, Clear....................................... 161
System Replaced ............................................... 161
Table Filters........................................................ 103
Technical Support .............................................. 224
Test Tools........................................................... 213
Test-Trap.............................................................. 81
Time Format ......................................................... 70
Time Schedule Option ........................................ 148
Tools Menu........................................................... 95
Trap
Forwarding....................................................... 81
Info, Legacy Trap Info...................................... 70
Recognize........................................................ 84
SNMP .............................................................. 70
TrapMonitor ........................................................ 216
Traps/Notifications................................................ 81
Tree View ...................................Look Up NE Tree
Update A.I.M.O.S. / From File .....................209, 210
Uplink Connection Parameter............................. 110
User Data, Export ................................................. 80
User Name ......................................................77, 92
Users Import/Export.............................................. 80
UTC ...............................................................70, 230
Validate, Database ............................................. 208
Vector Map ......................................................... 182
Version Info .......................................................... 99
View.................................................................... 186
Menu................................................................ 97
Runs .............................................................. 149
Visu Logs...............................................60, 138, 225
Visu Version Info .................................................. 99
WatchDog
Client Window.................................................. 35
Tool................................................................ 186
WEB Server Configuration ................................. 146
Windows Menu..................................................... 99
Workshift Assignment........................................... 85
Workshift Settings ................................................ 81
XML Import, Export .......................................93, 153
Zoom In, Out ...................................................... 182
Page 279

M0125ana Aimos V2 13

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

M0125ana Aimos V2 13

Загружено:

Авторское право:

Доступные форматы

A.I.M.O.S. V2.

Andrew Integrated Management

Users Manual for A.I.M.O.S. V2.13

Copyright 2013 CommScope, Inc.

FOR A QUICK START

Users Manual A.I.M.O.S. V2.13

Users Manual A.I.M.O.S. V2.13

A.I.M.O.S. DATABASE ADMINISTRATION / MAINTENANCE TOOL

A.I.M.O.S. TEST TOOLS

Users Manual A.I.M.O.S. V2.13

Automatic Database Restore

14 APPENDIX C HTTPS CERTIFICATE HANDLING

Users Manual for A.I.M.O.S. V2.13

INTERNATIONAL CONTACT ADDRESSES FOR CUSTOMER SUPPORT

Andrew LLC, A CommScope Company

505 Consumers Road, Suite 803

620 North Greenfield Parkway

Caribbean (CALA) & Central American

CommScope Cabos do Brasil Ltda.

CommScope Mexico S.A. de C.V.

CALA Tech Support for Distributed

CALA Tech Support for Distributed

Av. Insurgentes Sur 688, Piso 6

Australia & New Zealand

Room 915, 9/F

Andrew Wireless Systems UK Ltd

Andrew Norway (AMNW)

Unit 15, Ilex Building

P.O. Box 3066

Andrew Wireless Systems GmbH

Andrew Wireless Systems (Austria) GmbH

CommScope Wireless Systems AG

Iberia Region - Spain & Portugal

CommScope Italy S.r.l., Faenza, Italy

Andrew Espaa S.A.

Avda. de Europa, 4 - 2 pta.

Users Manual for A.I.M.O.S. V2.13

+49 871 9659171 (Office)

+49 871 9659172

Africa & Middle East:

table 1-1 List of international contact addresses

1.3 CONTENT CHANGES COMPARED TO PREVIOUS MANUAL VERSIONS

Chapter extended and

Change in Client update

New Password Security Level option

Screen shot updated.

Field to prevent gray text added

Maximum User Account Inactivity

Expiry Date and Most Recent Use settings 5.4

Use filtered NE List for NE Tree

Reference to 6.11 added

ION-E system added

SNMPv3 southbound support of Node A

New action Configure ION-M User

Description updated and

Use filtered NE List for NE Tree

Users Manual for A.I.M.O.S. V2.13

Node X explanation added.

Information on Microsoft Package installation added

Default value added to Show Alert Box explanation.

Alarm import information of menu Update extended and

XML-File Location field information added to a) & b), and

Description extended by detailed example and reference to