Beruflich Dokumente
Kultur Dokumente
X
Administration Guide
Contact Information
Headquarters Axell Wireless trading as Cobham Wireless
Aerial House, Asheridge Road
Chesham, Buckinghamshire
HP5 2QD, United Kingdom
Tel: +44 1494 777000
Fax: +44 1494 777002
Commercial inquiries cw.coverage@cobham.com
Website www.cobham.com/wireless
Support issues cw.support@cobham.com
Technical Support Line, English speaking +44 1494 777 747
Notice
Confidential - Authorized Customer Use
This document may be used in its complete form only and is solely for the use of Cobham Wireless employees and
authorized Cobham Wireless channels or customers. The material herein is proprietary to Cobham Wireless. Any
unauthorized reproduction, use or disclosure of any part thereof is strictly prohibited.
All trademarks and registered trademarks are the property of their respective owners.
Disclaimer of Liability
Contents herein are current as of the date of publication. Cobham Wireless reserves the right to change the contents
without prior notice. The information furnished by Cobham Wireless in this document is believed to be accurate and
reliable. However, Cobham Wireless assumes no responsibility for its use. In no event shall Cobham Wireless be liable
for any damage resulting from loss of data, loss of use, or loss of profits and Cobham Wireless further disclaims any and
all liability for indirect, incidental, special, consequential or other similes damages. This disclaimer of liability applies to all
products, publications and services during and after the warranty period.
Revision History
Revision Changes
3.0 Alarm Forwarding module SMS support
No Incoming Messages Alarm severity
System Information Report
Polygon Manager Module
Table of Contents
1 INTRODUCTION .................................................................................................................. 1
1.1 About the AEM 3.x Server .............................................................................................. 1
1.2 AEM 3.x Server Configuration Options ............................................................................ 2
1 INTRODUCTION
NOTE: The AEM web client refers to any machine running one of the supported Web Browsers to connect to the AEM 3
Web Server. The AEM 3 web client configuration procedures are described in the AEM 3.x User Manual.
Tabs
Common Service
Control Buttons
NOTE: The service control buttons are common to all the tabs. Use the control buttons to Start, Stop or Restart the
server. To save changes, click Apply in each tab.
2.1.2.3 Database
.1.1 and click the Database tab. The
1. Access the Server Configuration dialog according to section 2
Database screen appears.
Should be
AxellAEM3
2.1.2.4 Reports
Access the Server Configuration dialog according to section 2.1.1 and click the Reports tab. Reports will
be generated each day at the set time and stored in the Automatic Report Folder.
2.1.2.5 Communication
.1.1 and click the Communication tab.
1. Launch the Server Configuration dialog according to section 2
Default values
(usually not modified)
NOTE: The default values for the system interfaces are provided above. Under normal conditions these values
should not be changed. For special installations where there is a requirement to customize these ports, please
contact Cobham Wireless support for further details.
Optional
The alarms are matched according to ID (this option cannot be disabled). To additionally match
alarms according to Alarms Text, select the option Match Alarms on Text and click Apply to save.
In the ‘No incoming Messages Alarm Severity’ option, you may edit the severity of the AEM
generated alarm when data is not received on the Transceiver interface. Default = Critical.
2.1.2.7 Personalisation
.1.1 and click the Personalisation tab.
1. Access the Server Configuration dialog according to section 2
Titles corresponding to
equipment properties
Daily Password
maintenance Policy
settings
3. In the Service Interface area, click Start. When the ‘Database Connection Open’ is displayed, the
AEM Server start-up is complete.
4. Review the messages and ensure that no errors have been logged. If they have, please correct the
issues and repeat the process. If you are unsure what the errors indicate, please contact the Cobham
Wireless Support team for assistance.
5. If the service is running correctly, navigate back to the standard Windows Services Dialog, locate
“AEM3Server” and change it to a Startup Type of “Automatic”.
For Windows Server 2012/2016– click the GUI Server Configuration button.
For Windows Server 2008 – in the Start menu, click Programs and select Cobham Wireless,
AEM 3, GUI Server and GUI Server Configuration.
The AEM GUI Server Configuration Tool will be launched.
2. In the Server Connectivity tab, set the Server Connectivity parameters as follows.
Server Address IP Address on which the AEM listens for connections. This must be the same as
the Server Address in the Server Configuration module, Communication
tab (section 2.1.2.5). Do NOT use the localhost address (127.0.0.1) even if both
the AEM Server and the GUI Server are running on the same machine
Server Port Port on which the AEM Server has been configured to listen.
This must be the same as the GUI Server Interface Port in the Server
Configuration module, Communication tab (section 2.1.2.5).
Recommended and default value = 50000; to use a different port contact
Cobham Wireless Support for more information.
Site Security HTTP (Unencrypted) or HTTPS (Encrypted). HTTPS is only available if SSL
Type certificates are detected on the server.
If HTTPS is selected, choose from the detected list of SSL certificates on the
server. When Apply is clicked, the web server is automatically updated, and the
web server service is restarted.
Server Port The port that the AEM Server has been configured to listen on.
This must be the same value configured as the SNMP Transceiver
Interface Port, in the Communication tab System Interfaces, in
the Server Configuration (section 2.1.2.5).
The recommended and default value for this is 50100, however it is
possible to use an alternative port if required. If you wish to do so,
please contact Cobham Wireless Support for further details
2.3.2.2 Communication
To configure the communication information
Parameter Description
UDP Listener Port Some selected equipment may send heartbeat messages via
UDP. This is port used for listening for these messages.
Default = 50500
Ping Interval Period between Equipment Ping events. Default = 5 min.
Ping Count No of successive failed pings before an alarm is raised.
Default = 3
Ping Timeout Time allowed before ping is considered failed.
Default = 10000 (10 seconds)
No Activity Alarm The amount of time permitted without a message (Alarm or
Heartbeat) being received by the transceiver before an alarm
is raised.
The severity of this alarm is also configurable here.
Synchronization The amount of time the server waits for a response to a
Request Timeout synchronization attempt. Default = 10 min
2.3.2.4 Personalisation
Select the interface language and click Apply.
2.4.2.2 Communication
To configure the communication information
2.4.2.3 Personalisation
Select the interface language and click Apply.
NOTE: The destinations and recipients of the alarm forwarding and event notifications are configured via an AEM web
client access.
Main tabs
Service
Control
Figure 3-1. Alarm Forwarding Module
10.187.20.92
Server Port This is the port on which the AEM Server has been configured to listen. This
must be the same value as has been configured the port on which the AEM
Server has been configured to listen. This must be the same value
configured in the Server Configuration module — Communication tab, as the
Alarm Forwarding Interface Port (section 2.1.2.5).
NOTE: The recommended and default value for this is 50400. To use an alternative
port (if required), contact Cobham Wireless Support for further details.
.1.1.
1. Access the Alarm Forwarding module according to Section 3
2. Click on the Configuration main tab, and click the SNMP Setting sub-tab.
10.187.20.92
Do NOT
modify Ports
Field Description
Agent Address The IP Address of the computer on which the AEM Agent is installed –
this is usually the computer on which the AEM Server is installed.
Message Batch Optionally this field can be modified.
Size
This is the number of SNMP alarms sent in quick succession as a ‘batch’.
For example if there were 100 alarms messages in the queue to be sent
and the batch size was 25, there would be four batches of messages sent,
a few seconds apart, from AEM to the SNMP message destination.
Default = 25
Enable SNMP This must be set to Enable for SNMP operation.
Tables
Optionally, the SNMP Tables can be disabled by setting this field to
Disabled. This is a useful option that eliminates unnecessary processor
utilization if the SNMP tables are not required.
.1.1.
1. Access the Alarm Forwarding module according to Section 3
2. Click on the Configuration tab and then the email Settings sub-tab.
.1.1.
1. Access the Alarm Forwarding module according to Section 3
2. Click on the Configuration tab and then the email Settings sub-tab.
NOTE: The SMS message may be formatted as required. They will be cropped off at the maximum length of an
SMS message.
Field Description
SMS Modem Description Select the modem via which SMS messages will be sent.
If only one modem is available, then it will be the only available option.
SMS Modem Port Select the port to be assigned to the modem.
Alarm format .1.5.2.
Format for an alarm type SMS message. See Section 3
Clearance Format .1.5.2.
Format for an alarm clear SMS message. See Section 3
Heartbeat Format .1.5.2.
Format for a heartbeat type SMS message. See Section 3
Info Message Format .1.5.2.
Format for an inform type SMS message. See Section 3
#UR# UniqueRef
#ID# AlarmID
#DT# AlarmDateTime
#SE# Severity
#VA# Value
#DE# Details
#CL# AlarmClass
#MO# MoreInfo
#TA# EquipmentTag
#PA# ParentNode
#GI# GroupID
#GN# GroupName
#U1# UserField1
#U2# UserField2
#U3# UserField3
#U4# UserField4
#U5# UserField5
For example:
An alarm type message configured as follows: Alarm,#UR#,#DT#,#SE#,#DE#,#MO#
Is displayed as: “Alarm,8693-AAAA,2018/08/28 09:07.11,Critical,Temperature is +99
Degrees,Controller Temperature”
Click to clear a
queue
Destination
Type
2. Click the relevant tab to view the status of the messages that are forwarded. Individual queues can be
cleared by clicking the adjacent Clear button.
The following status information is provided:
Status Field Description
Queued Shows the number of unacknowledged notifications queued for forwarding to the
destinations defined via AEM web client access.
Processing Shows the number of messages currently being processed in that queue.
Clear Click to clear the messages in the queue. Only messages that have not yet started
the processing phase will be cleared.
For Windows Server 2012/2016– click the Printer Alarm Logging button.
For Windows Server 2008 – in the Start menu, click Programs and select Cobham Wireless, AEM 3,
System Tools and Printer Alarm Logging.
Alarm Forwarding
Printer Module
configuration
parameters
Status
Information
The Forwarding Printer Server will be periodically polled to check if any alarms are available to print. In
the event that one or more are found, each one will be processed and removed from the request.
The process of printing will be displayed in the Diagnostics panel. If the Alarm Forwarding module is
closed, any messages that would normally be processed will be queued by the AEM Server and sent
once the application is started.
NOTE: The buttons at the bottom of the screen are used to control the service operation.
Click to access
configuration dialog
Monitoring
and status
information
Service control
options
.3.1.
1. Access the Event Notification dialog according to section 3
2. Click the Tools menu option and select Edit Configuration. The configuration dialog appears. The
Server Connectivity tab is displayed by default.
.3.1.
1. Access the Event Notification dialog according to section 3
2. Click the Tools menu, choose Edit Configuration and then click the SMS Configuration tab.
3. For each available modem (1/2/3/4), select the serial port to which the modem is connected or select
None if there is no modem or to disable a modem.
4. Click OK to save. The defined modems and their status are displayed in the Event Notification System
.3.3.
Status pane (Section 3
Field Description
Host The email server hostname
Port The port on the email server
User Name Authentication username (This may be left blank if required)
Password Authentication Password (This may be left blank if required)
Source Address Email address to be displayed in the ‘From’ field in the email with the
messages.
Use SSL When selected, will request an SSL connection to the email server
Modems
System Status
summary
Double-click on an
event to clear
notifications
Summary of current
activities
Service control
options
# Entry Description
1 Header Always “AEMMSG”
2 Message ID Automatically assigned, auto-incrementing counter for messages
3 Unique Reference The Unique Reference for the equipment
4 Severity Alarm severity. Values: Clearance, Indeterminate, Critical, Major,
Minor, Warning, Information, Catastrophic, Unknown
5 Acknowledgement Description of the acknowledgement
Description
6 Tag Tag of the equipment (where present, otherwise “”)
7 User Field 1 Equipment parameter User Field 1
8 User Field 2 Equipment parameter User Field 2
9 User Field 3 Equipment parameter User Field 3
10 User Field 4 Equipment parameter User Field 4
11 User Field 5 Equipment parameter User Field 5
For example,
AEMMSG,3378,TRANSNMP-0002,Clearance,'Equipment Communication Restored','SNMP
Transceiver 0002','SNMP Transceiver 2','','','',''
Where in this case, the Transceiver Equipment has its User Field 1 parameter set to “'SNMP Transceiver 2”
with the remaining four left empty.
Where in this case, the Transceiver Equipment has its User Field 1 parameter set to “'SNMP Transceiver 2”
with the remaining 4 left empty.
For Windows Server 2012/2016– click the Software Update Manager button.
For Windows Server 2008 – in the Start menu, click All Programs, select Cobham Wireless, AEM
3, System Tools and Software Update Manager.
The Software Update Manager Tool will be launched.
NOTE: When the application is initially run, it will contain a default configuration. This should be changed to suit
your specific installation.
Click Tools
and choose
Configuration
2. From the Tools menu, choose Configuration and Server Connectivity. The Configuration dialog
appears. The configuration dialog consists of sections:
Server Connectivity
Configured Packages
Server Address
Server Port
Package Folder
For Windows Server 2012/2016– click the Software Update Manager button.
For Windows Server 2008 – in the Start menu, click All Programs, select Cobham Wireless, AEM
3, System Tools and Software Update Manager.
The Software Update Manager Tool will be launched.
2. From the Tools menu, choose Configuration and Server Connectivity. The Configuration dialog
appears. The configuration dialog consists of sections:
Server Connectivity
Configured Packages
3. To add a package, click Add. You will be prompted with a dialog requesting three entries:
NOTE: To delete a package, select the package and click Delete.
Model Enter the EXACT name of the equipment (as displayed in AEM3) that is
targeted for this package. To associate the package with more than one
equipment model, add multiple entries.
Package Name Enter the identity of the package. This is the key to the package, and will
For Windows Server 2012/2016– click the Equipment Backup Manager button.
For Windows Server 2008 – in the Start menu, click All Programs, select Cobham Wireless,
AEM3, System Tools and Equipment Backup Manager.
The Equipment Backup Manager Tool will be launched.
NOTE: Various status information such as the time and date it was configured, is displayed in the Diagnostics Info tab.
For Windows Server 2012/2016– click the Equipment Configuration Manager button.
For Windows Server 2008 – in the Start menu, click All Programs, select Cobham Wireless, AEM
3, System Tools and Equipment Configuration Manager.
The Equipment Configuration Manager Tool will be launched.
4. In the Equipment Communication Connectivity area, enter the Login Name and Password.
During the process of either Learn or Reconfiguration, the service will connect via telnet to the
appropriate equipment. The credentials entered here will be used during that authentication.
5. In the Settings area, browse for the folder in which the Learn & Reconfiguration files will be stored.
By default, this is a sub-folder of the Equipment Configuration Manager module, but this may be
changed if needed.
Select AxellAEM3
Browse for
backup directory
5. Click Apply.
To restore a database
1. Disable the AEM Server Service:
Launch the AEM Server module – section 2.1.1
Under Service Interface, click the Stop button.
Stop service
Run Restore
3. Enter or browse for the location of the file to be restored and then click the Run Restore button. The
Log section will display information regarding the restoration process.
OnBoard Repeaters can be configured to automatically load and activate different sets of parameters as they
are transported through different geographical locations. For example: changing the bandwidth
configurations, muting a specific band, changing the output power levels, etc.
This capability is implemented by creating a polygon package via the AEM server Polygon Manager
module. Polygon packages consist of sets of map coordinates (polygons) and commands. This is
implemented by creating a pool of polygons (defined areas), a pool of required command sequences, and
then associating polygons with dedicated command sequences. A Polygon Package may include a number of
such sets.
The required package is then selected and uploaded to the relevant onboard equipment via AEM web client
access and the relevant set of commands is activated as the repeater is transported through the associated
geographical area.
Configuration
Options
Connection
Status
Equipment This is the password for the account on the equipment you wish to use to
login password deploy the polygon. This information will be provided with the equipment.
Package Folder Location AEM uses to dynamically create and maintain the polygon packages
available for deployment. This location cannot be modified.
5. Click OK.
NOTE: To draw the area on a map image, verify the map on which the coordinates (Polygons) are to be defined already
exists via AEM web client access.
.5.1).
1. Launch the Polygon Manager module (section 4
2. Click the Tools menu and choose the Manage Packages option.
3. Select the Polygon Definitions tab. The displayed screen lists any available Polygon definitions and
provides Polygon creation and management options.
NOTE: Click Add to create new Polygons. Use Edit and Delete to modify or remove (after a verification message)
a selected Polygon file.
Manually defined or
displayed using Draw
(map) coordinates
Click to
invoke map
Left-click to define
edges; right-click to
complete.
Draw the polygon by left-clicking to define the edges. The red lines represent the boundaries
of the polygon. Right-click to complete the polygon. The polygon coordinates will appear in
the Parameters field.
Click OK to complete the polygon definition. The defined polygon will be listed in the Polygon
definitions tab and will be available for creating Polygon packages.
7. To manually define the polygon, enter the three coordinates in the following format.
Latitude1,Longitude1;Latitude2,Longitude2;Latitude3,Longitude3;
Note the following:
The parameters within each set of latitude and longitude are separated by a comma (,).
The latitude and longitude sets are separated from each other by semi-colons (;).
Spaces are NOT allowed.
The definitions line ends with a semi-colon (;).
Click to Save
definitions.
.5.1).
1. Launch the Polygon Manager module (section 4
2. Click the Tools menu and choose the Manage Packages option.
3. Select the Command Set Definitions tab. The displayed screen lists any available command definition
sets and provides commands set creation and management options.
NOTE: Click Add to create new commands set. Use Edit and Delete to modify or remove (after a verification
message) a selected command set.
Click to Save
definitions.
Where:
<RF Enum> - is the band index (1\2\3\4)
<Filter Enum> - number of filter that need to be set.
<Enable> - filter is open or close - can be TRUE or FALSE.
<Bandwidth> - bandwidth in MHz
<Center_Freq DL> - center frequency of Downlink (MHz)
<Start Freq DL> - is the Downlink start frequency in MHz
<Stop Freq DL> - is the Downlink stop frequency in MHz
<Filter Type> - Filter technology (GSM/LTE/etc..)
Example:
SET FLT 1 FREQ 5 1 5 2120.5 set freq of 2120.5 MHz with BW of 5 MHz in filter 5 on band 1
SET FLT 1 FREQ 4 1 2120.2 2125.2 LTE set freq of 2120.5 to 2125.2 MHz in filter 4 on band 1
Where:
<Power Level DL> - maximum output power of DL of filter
Example:
SET FLT 3 POWER 1 20 set max out power of filter 1 on band 3 to 20dB (DL)
Where:
< DL_Gain> - max Gain of DL
< UL_Offset > - offset between max gain DL and UL
Example:
SET GAI 1 2 73 -3 band 1, filter 2: set gain of dl to 73 d SET GAI 1 2 73 -3 m and ul gain to 70 dbm
.5.1).
1. Launch the Polygon Manager module (section 4
2. Click the Tools menu and choose the Manage Packages option.
3. Select the Polygon Packages tab. The displayed screen enables creating and managing packages. The
work area lists the elements comprising the currently selected packages.
NOTE: There are two sets of management options – one for the Package, and the other for defining the elements
comprising the package.
Elements
comprising
selected Polygon and Command Set
package management options
NOTE: The package is currently empty. The contents of the package can now be configured according to the
following step.
Selected
Package
Click the bottom Add button (used to manage the elements in the package). The Package Entry ID
will indicate the index number assigned by the system to the package.
From the corresponding drop-down lists, select the Polygon and the associated Command Set for the
package.
Click OK. The defined package entry association will be added to the Polygon Package.
Repeat the procedure to add additional entries to the Polygon Package.
Below is an example of a Cobham I/O Interface device. (Since this is a customized unit, your device can
differ).
Depending on the hardware supplied, this unit will either connect directly to the AEM Server via a physical
RS-232 Serial Port (as per the version above), or may be connected via Ethernet into the network.
Edit
configuration
5. Click Apply.
########################################################################################
# Inputs
########################################################################################
INPUT=0,-1,1,Alarm Inputs,CL
INPUT=0,0,1,UPS 1 Warning,WA
INPUT=0,1,1,UPS 1 Critical,CR
INPUT=0,2,1,UPS 2 Warning,WA
INPUT=0,3,1,UPS 2 Critical,CR
INPUT=0,4,0,Spare,CL
INPUT=0,5,0,Spare,CL
INPUT=0,6,0,Spare,CL
INPUT=0,7,0,Spare,CL
########################################################################################
# Outputs – We will use only Bank 0
########################################################################################
OUTPUT=0,-1,1,Outputs,ANY,CL
OUTPUT=0,0,1,AEM Summary,ANY,CA;CR;MA;MI;WA
OUTPUT=0,1,1,AEM Catastrophic,ANY,CA
OUTPUT=0,2,1,AEM Critical,ANY,CR
OUTPUT=0,3,1,AEM Major,ANY,MA
OUTPUT=0,4,1,AEM Minor,ANY,MI
OUTPUT=0,5,1,AEM Warning,ANY,WA
OUTPUT=0,6,0,SPARE,ANY,CL
OUTPUT=0,7,0,SPARE,ANY,CL
As can be seen, there are three main sections to the file; Header, Input Definitions & Output Definitions.
5.1.2.1 Header
The first 5 lines of the file are mandatory, with the first one always being ‘[AEM 3 Axell I/O Interface]’.Under
normal circumstances these should not be changed, unless a configuration change has been made, in which
case the RELEASE_DATE and RELEASE_TIME may be modified.
Area Description
AEM System Displays the current alarm status of the AEM System as a whole. There
Status is an independent indicator for each alarm criticality within the system.
Connectivity Displays the connectivity status for both the link to the AEM Server, and
Status the link to the Alarm Shelf itself. Under correct running conditions, both
these must be Green.
Input & Output Displays the status of both the inputs and outputs being monitored by
Status the system. These inputs and outputs will be specified within the
configuration file.
It is possible to use the NTP protocol to synchronise the monitored idDAS equipment to the AEM Server. In
order to do this the NTP Service must be enabled on the Server itself as described in this section.
2. Select Administrative template, choose System, Windows Time Service, Time Providers on the
left Pane, and double-click the Enable Windows NTP Server on the right Pane.
Double-click Enable
Windows NTP Server
Select Time
Providers
3. The Enable Windows NTP Server appears. Verify the Enabled option in the upper-left side of the dialog
is set and click OK.
Enabled
4. In the left pane, select Windows Time Service, and double-click Global Configuration Settings.
Double-click Global
Configuration Settings
Select Windows
Time Service
Enabled
AnnouncedFlags = 5
Tools
Services
Windows Time
service