Alarm and CMD On APG40

Open
USER GUIDE 1 ( 20 )
Prepared (also subject responsible if other) No.
EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

Approved Checked Date Rev Reference
EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B
Alarm and Command Administration on the APG40
Abstract
Overview and additional explanations to procedures for configuration, operation

and maintenance of the alarm and command functions on the APG40 platform.
Copyright
© Ericsson AB 2006 - All Rights Reserved
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing.
Ericsson shall have no liability for any error or damages of any kind resulting
from the use of this document.
Trademarks
Microsoft, Windows, Windows Server 2003, Microsoft Cluster Server, Internet
Information Server, Terminal Services and/or other Microsoft products
referenced herein are either trademarks or registered trademarks of Microsoft.
AXE and APG40 are trademarks of Ericsson.
Contents Page
1 Introduction .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
1.1 Revision Information . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
1.2 Purpose . . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
1.3 Prerequisites .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
2 General Information .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
2.1 Overview . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
2.1.1 Man-machine Communication Subsystem (MCS) .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
3 Configuration . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 4
3.1 Routing of Printouts . . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 4
3.1.1 Configuration in APG .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 4
3.1.2 Configuration in Remote System .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 6
3.2 Heartbeat between CP and OSS .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 6
3.2.1 Heartbeat Configuration in APG . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 7
3.2.2 Heartbeat Configuration in OSS . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 7
3.3 Exchange Header . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 7
3.4 Alarm . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 7
3.4.1 Alarm-Display . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 7
3.5 External Alarm . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 9
3.5.1 Defining and Connecting External Alarm Receivers to APG40 . .. . . .. . .. . .. . 9
A4 XSEIF R4
Open
USER GUIDE 2 ( 20 )

3.5.2 Defining and Connecting External Alarm Receivers to EMRP Connected

EXALI0 .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 10
4 Usage . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 10
4.1 Man Machine Language (MML) Command Session . .. . .. . .. . .. . .. . . .. . .. . .. . 10
4.1.1 MML Command . . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 10
4.1.2 Function Busy . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 10
4.1.3 Comments . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 10
4.1.4 Dialogue Commands .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 11
4.1.5 Parking .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 11
4.1.6 Command Editing . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 11
4.1.7 Central Processor Test Commands .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 12
4.1.8 AP Local Mode .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 12
4.1.9 Restriction of Command Usage during System Dump . . .. . .. . .. . .. . . .. . .. . .. . 12
4.1.10 End Command Session .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 12
4.2 Different Kinds of Printouts .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 13
4.2.1 Procedure Printout .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 13
4.2.2 Answer Printout . . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 13
4.2.3 Check Printout . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 13
4.2.4 Result Printout . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 13
4.2.5 Spontaneous Printout .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 14
4.3 Re-routing of printouts with IODAC .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 14
4.4 Alphanumeric Terminal, EMRP-Connected, Inspect . .. . .. . .. . .. . .. . . .. . .. . .. . 14
4.5 Alarm-Display in AP, Inspect and Repair . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.6 External Alarm Receiver in AP, Inspect and Repair . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.7 External Alarm Receiver in EXALI0, Repair . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8 Actions on Alarms . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8.1 EXTERNAL ALARM . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8.2 EXTERNAL ALARM RECEIVER FAULT . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8.3 IO BLOCKED . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8.4 IO MML SERVER FAULT . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8.5 IO PRINTOUT DESTINATION FAULTY . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 15
4.8.6 IO STORAGE SPACE WARNING . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 16
4.8.7 MCS AUTHORITY COMMAND INPUT RESTRICTED . .. . .. . .. . .. . . .. . .. . .. . 16
4.8.8 MCS AUTHORITY ILLEGAL LOGON ATTEMPT .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 16
4.8.9 USER EXCEEDED ALLOWED ACCESS ATTEMPTS . .. . .. . .. . .. . . .. . .. . .. . 16
5 Glossary . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 17
6 References . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 17
Open
USER GUIDE 3 ( 20 )

1 Introduction
1.1 Revision Information
2/198 17–ANZ 218 40/4 Rev A is based on information in 1/198 17–ANZ 218
40/4 Rev A.
Information about alarm and command administration has been extracted from
the document mentioned above and collected in this document. All information
regarding accessing an AXE with APG40 has been collected in another
document, seeHow to Access an AXE with APG40.
1.2 Purpose
This document is written for System Administrators and Operators responsible

for configuring, upgrading and performing corrective maintenance of the alarm
and command functions on the APG40.
1.3 Prerequisites
System Administrators using this document should be:

• Familiar with Windows Server 2003 system administration
• Familiar with Windows Server 2003 Cluster Server administration
• Familiar with AP system administration
2 General Information
2.1 Overview
Where specific information which is not covered in any OPI is necessary, the
information is included as recommendations or OPI-type explanations in this
document.
2.1.1 Man-machine Communication Subsystem (MCS)

The subsystem Man-machine Communication Subsystem (MCS) provides the
man-machine interface for the operation and maintenance functions in AXE.
MCS handles alphanumeric information, alarms and authorization checks.
Open
USER GUIDE 4 ( 20 )

3 Configuration
3.1 Routing of Printouts
The purpose of this function is to ensure that alphanumeric printouts from the
AXE are sent to specified destinations, and that printouts are not lost in case
of different types of hardware faults.
Output of important printouts is secured by selecting a standby destination, if the

originally specified destination is faulty, or if a fault occurs during the printout.
Different kinds of printout can be generated in the AXE. Depending on which

kind of printout is generated, routing and selection of standby destinations will
take place in different ways.
3.1.1 Configuration in APG

For IO devices connected to an APG40, it is possible to specify that re-routing
to a standby device will take place immediately, or after a specified period of
time by using cpdinsert with option -r.
If a time period is specified, and the primary IO device cannot reach the
remote destination, printouts that are queued towards this IO device will not be
re-routed to a standby device until the specified time has elapsed.
The reason for having the possibility to wait before re-routing to a standby
device is that a remote destination associated with the IO device may be
temporarily unreachable. If contact is established with the remote destination
before the time elapses, re-routing of the queued printouts is not needed.
By using cpdinsert with option -b, each printout is preceded by an extra line
that contains additional information. The additional information can for example
be used to detect if any alarms are lost. This option is to be used only in
conjunction with remote post-processing systems that have been prepared to
take care of this additional information.
OPI IO Device, System Standby, Change describes the procedure to change

the system standby device. It is recommended to use an AD device inserted by
using cpdinsert with option -x.
OPI Alphanumeric Information to File, Occasional Printout describes the

procedure to transfer occasional printouts of alphanumeric information to a file.
OPI Alphanumeric Information to File, Periodic Printout describes the procedure

to transfer spontaneous or periodical printouts of alphanumeric information to a
file. Output of alphanumeric information to a file is also implemented in another
way in APG40, using command cpdinsert with option -x in OPI Alphanumeric
Device in AP, Define.
Open
USER GUIDE 5 ( 20 )

3.1.1.1 Result Printouts

OPI IO Device Standby List, Change describes the procedure required to
change an Input/Output (IO) standby device list. This list of standby devices
can only be used for result printouts.
3.1.1.2 Spontaneous Printouts

Routing of spontaneous printouts is performed by inserting an IO device using
command cpdinsert, with option -r, and inserting the associated IO device in a
printout chain in the CP routing tables using command IOROL.
If the originally specified destination is faulty, the IO device defined as standby

or system standby device will be selected.
OPI Alphanumeric Device in AP, Define describes the procedure to define

an Alphanumeric Device (AD) to an Adjunct Processor (AP). The AD is
used for communication with the Central Processor (CP) in order to receive
spontaneous printouts.
OPI Alphanumeric Device in AP, Remove describes the procedure to remove

an Alphanumeric Device (AD) from an Adjunct Processor (AP).
OPI Printouts, Spontaneous, Route describes the procedure to change the list
of standby devices for an Input/Output (IO) device. This list of standby devices
can only be used for spontaneous printouts.
OPI Attendance Status for Control Room and IO Device, Set describes the
procedure to set the attendance status to ATT. The attendance status together
with the definition of the printout chains, OPI Printouts, Spontaneous, Route
determines the destinations spontaneous printouts are routed to.
OPI Attendance Status for Control Room and IO Device, Reset describes the
procedure to reset attendance status to unattended.
3.1.1.3 Routing of Alarm Printouts with Command Ordered Re-routing

Possibilities
This chapter describes an example showing how to route spontaneous
printouts with the possibility to re-route them to another destination when
command IODAC is executed.
Commands IOROL and cpdinsert with option -r are used to achieve rerouting of
alarms from the destination with IP address 10.0.0.1:9000 to, in this case, a
subfile if IODAC is given or the destination (AD-123) is not available within 30
minutes. For further information see OPIs listed in previous chapter.
1. Logon to the AP which houses the AP I/O functionality.
2. cpdinsert -i 10.0.0.1:9000 -r 30 -e crlf AD-123
3. cpdinsert -x *:00,30 AD-124

Open
USER GUIDE 6 ( 20 )

Note: A new subfile is created every half-hour. If no alarm printout

comes, no new subfiles are created.
4. mml
5. IOROL:PRCA=36&&56, DTYPE=FIRST, IO=AD-123, CLASSUA=6,

COND=1;
6. IOROL:DTYPE=STB, IO=AD-124;
7. IOROL:DTYPE=NEXT, IO=AD-124;
8. IOROI:PRCA=36&&56;
9. Step 9 to 12 are performed in order to verify that the re-routing works well.
IODAC:ATT;
Note: From now on the alarm printouts will be sent to AD-123.
10. Wait for any alarms or do some actions to initiate an alarm in order to
check that alarms are routed to AD-123.
11. IODAC;
Note: From now on the alarm printouts will be sent to subfile

“AD-124_YYYYMMDD_hhmm.log”, where YYYYMMDD and
hhmm indicates the date and time when the subfile was created.
The name of the active subfile ends with ".curr", while the
completed subfiles ends with ".log", thus making it easy to,
for example, process the completed subfiles further without
disturbing the active subfile.
12. Wait for any alarms or do some actions to initiate an alarm in order to
check that alarms are routed to the subfile.
13. IODAC:ATT;
3.1.2 Configuration in Remote System

Depending on the routing configuration in the APG, the remote system must be
prepared to either listen to or connect to AXE to the port that was defined.
3.2 Heartbeat between CP and OSS
Printout HB is used for remote supervision of program execution in AXE. When

command ALHBI has been executed, the printout is sent periodically from the
CP to the destination, that is, the Operations Support System (OSS).
Open
USER GUIDE 7 ( 20 )

3.2.1 Heartbeat Configuration in APG

In order to prepare sending of heartbeat, the destination which shall receive
printout HB, PRCA=35, must be defined. Use cpdinsert with options -i and -v
35 in OPI Alphanumeric Device in AP, Define.
3.2.2 Heartbeat Configuration in OSS

The OSS must be prepared to listen to HB on the port defined when the
heartbeat configuration in the APG was performed and initiate some kind of
alarm if heartbeats are missed.
Using this function, the OSS can detect lost communication to the CP in a
specific Network Element (NE).
3.3 Exchange Header

The exchange header is received when the CP is accessed and in front of
spontaneous printouts. Most spontaneous printouts are alarm printouts. The
exchange header is a part in the alarm header.
Command IOEXC is used to change the exchange header.
Command IOEXP is used to print the exchange header.
3.4 Alarm
Each situation outside or within the AXE system that causes operational
disturbance or requires manual intervention generates an alarm.
An alarm is sent as a spontaneous printout when the disturbance occurs. All

alarms are stored in an alarm list.
The alarms can be indicated visually and acoustically using an alarm-display

panel. Detailed information on the cause of the alarm is received from the
alarm printout. The alarm printout also indicates the alarm class, alarm
category, origin, administrative alarm number and the attendance situation of
the source exchange.
3.4.1 Alarm-Display
Optical and acoustic alarms are indicated at the exchange with the aid of
alarm-display panels. The lamps are placed on the alarm-display in a matrix
based on the alarm class and the alarm category. There is one single lamp
that indicates whether the exchange is manned (attended) or unmanned
(unattended). Alarms are indicated acoustically by the alarm-display panel
buzzer.
In most cases, an alarm-display is defined to show the alarm status of the own
exchange. That is, the exchange to which the alarm-display is connected. Such
an alarm-display is indicated in figure below as a grey rectangle with filled lines.
Open
USER GUIDE 8 ( 20 )

Subordinate
Subordinate Exchange 2
Exchange 1
ALD-64
ALD-64
alddef -a 10.0.0.1 -p 7012 ald-64
alddef -a 10.0.0.1 -p 7011 ald-64
ALD-1
alddef ald-1 Subordinate

Exchange 3
LAN/WAN
ALD-64
alddef -a 10.0.0.1 -p 7013 ald-64
IP address
10.0.0.1 Exchange
ALD-1
alddef ald-1
ALD-11
alddef -p 7011 ald-11
ALD-12
ALD-13
Figure 1 Local and Remote Alarm-Displays
Table 1
Exchange Alarm-Display Description

Subor ALD-1 Shows the alarm status of own exchange
dinate
Exchange
1
Subor ALD-64 Sends the alarm status to Exchange
dinate (ALD-11)
Exchange
1
dinate (ALD-12)
Exchange
2
dinate (ALD-13)
Exchange
3
Open
USER GUIDE 9 ( 20 )

Exchange ALD-1 Shows the alarm status of own exchange

Exchange ALD-11 Shows the alarm status of subordinate
Exchange 1
Exchange 2
Exchange 3
3.4.1.1 Local Alarm-Display Connect or Disconnect

OPI Alarm-Display in AP, Connect describes the procedure to connect an
alarm-display in an Adjunct Processor (AP). Some steps in the procedure must
be performed on site.
OPI Alarm-Display in AP, Disconnect describes the procedure to disconnect

an alarm-display in an Adjunct Processor (AP). Some steps in the procedure
must be performed on site.
3.4.1.2 Remote Alarm-Display Define or Delete

OPI Remote Alarm-Display in AP, Define describes the procedure to define a
remote alarm-display in an Adjunct Processor (AP).
OPI Remote Alarm-Display in AP, Delete describes the procedure to delete a

remote alarm-display in an Adjunct Processor (AP).
3.5 External Alarm
External alarms are alarms that are generated outside the AXE system, for
example fire alarms, burglar alarms etc. These system external alarms are
received, administrated and presented in the same way as system internal
alarms.
When an external alarm receiver is activated, alarm External Alarm is

issued. External Alarm is common for all external alarm receivers connected to
both an APG as well as EMRP.
3.5.1 Defining and Connecting External Alarm Receivers to APG40

OPI External Alarm Receiver in AP, Connect describes the procedure to
connect an external alarm receiver in the Adjunct Processor (AP) or change
any option for an already defined external alarm. Some steps in the procedure
must be performed on site.
OPI External Alarm Receiver in AP, Disconnect describes the procedure to

disconnect an external alarm receiver in the Adjunct Processor (AP). Some
steps in the procedure must be performed on site.
Open
USER GUIDE 10 ( 20 )

3.5.2 Defining and Connecting External Alarm Receivers to EMRP

Connected EXALI0
OPI External Alarm, Connect describes the procedure to define and connect
an external alarm receiver in an EMRP connected EXALI0. Some steps in the
procedure must be performed on site.
OPI External Alarm, Disconnect describes the procedure to disconnect an

external alarm receiver in an EMRP connected EXALI0. Some steps in the
4 Usage
4.1 Man Machine Language (MML) Command Session
4.1.1 MML Command

An MML command consists of a command code, described in a command
description, and usually a set of parameters, and is always concluded with
a semicolon. The maximum length of a command is 140 characters. The
maximum number of elements for a command is 64. The system must always
respond to a command, usually within 10 seconds.
The system’s response may be a check printout, which always is followed by

a procedure printout, or an answer printout. See Page 13 for a description of
the different kinds of printouts.
4.1.2 Function Busy

When a command is received by the application program that owns the
command and the command is busy, the command is rejected and the following
standard texts are printed:
NOT ACCEPTED
FUNCTION BUSY
4.1.3 Comments
Comments are used to identify, or give, the reason for an input on, for example,
an alphanumeric terminal. Comments begin and end with an exclamation mark
(!). However, if they are inserted immediately before the semicolon at the end
of the command, the final exclamation mark is not mandatory.
All characters in the character set except the exclamation mark, semicolon, and
control characters may be used in comments.
Open

4.1.4 Dialogue Commands

Commands that require a lot of parameters are sometimes implemented as
dialogue commands. The dialogue is started with a normal command, but
instead of a procedure printout or an answer printout, the operator receives a
command-dependent heading and a special prompt character. This special
prompt is normally a colon (:).
Each subcommand in the dialogue is concluded with a semicolon. The layout

of the parameters, procedure and answer printouts, and the way the dialogue
ends is command dependent. Most commonly, the dialogue is ended with
command END or with <EOT> (CTRL-D).
4.1.5 Parking
4.1.5.1 Parking while waiting for command input
Result printouts and spontaneous printouts are queued when the IO device to
which they are routed is occupied by an operator. An operator can fetch these
queued printouts by parking the command session with character commercial
at (@). The command session will be resumed when queued printouts have
been printed.
4.1.5.2 Parking in dialogue commands
The operator can park a dialogue command by entering character commercial
at (@). This gives the operator the heading INTERRUPTED COMMAND
<command name> and a normal prompt. The operator will then get a
new command session and is free to enter any command. The character
<EOT> (CTRL-D) is used to re-enter the dialogue. If queued printouts exist
(for example, alarm printouts), they are printed. The text RE-ENTRY TO
COMMAND <command name> and the dialogue prompt are then displayed.
It is possible to run up to four sessions simultaneously on an IO device.
4.1.6 Command Editing

Note: This feature is only available for EMRP-connected IO devices.
It is possible to edit an input before it is entered into the system, by deleting the
last typed character or characters with key $, and then retyping the remaining
characters. On the alphanumeric terminal nothing can be seen when key $ is
used, but the character or the characters will not be read into the system.
It is possible to delete a line with key CTRL-X.
Table 2 Summary of Control Functions for EMRP-connected IO devices.
Key ISO char ISO Meaning

acter code
CTRL-B STX H’02 Seizure of terminal.
CTRL-C ETX H’03 Enter operator input command.
Open

CTRL-D EOT H’04 Release terminal to get queued printouts,

return to parked command, or interrupt
printout.
CTRL-X CAN H’18 Line delete.
@ @ H’40 Request for output of queued printouts or
parking of dialogue command.
$ $ H’24 Character delete.
? ? H’3F Deblock, if auto blocked.
4.1.7 Central Processor Test Commands

Note: This feature is not available for TW-connected IO devices.
During normal operation using mml as well as when it is not possible to reach
the CP, Central Processor Test (CPT) commands may be used. CPT is also
used when the CP is down and the following message is displayed when trying
to establish an MML session:
CP not obtainable
You may now enter: APLOC, PTCOI, or EXIT command.
The CPT mode is reached by entering the command PTCOI. To return to the
normal MML session, command PTCOE is entered.
4.1.8 AP Local Mode

An ongoing MML session can be interrupted temporarily in order to execute AP
commands. This is achieved by entering command APLOC. To resume the
previously interrupted MML session, command exit is used.
4.1.9 Restriction of Command Usage during System Dump

A system dump is ordered with command SYBUP. From this time until
the system dump is complete, printout NOT ACCEPTED COMMAND
RESTRICTED DURING DUMP is received each time a command that is to be
stored on the command log is entered.
4.1.10 End Command Session

In order to end an MML session, command EXIT is used.
Ending an MML session established over an EMRP, the operator is logged off
and the terminal is released. If the operator tries to connect again on the same
terminal, user code and password is required.
Ending an MML session established over an AP with command mml, a new

shell prompt is received. The operator is still logged in on the AP and may
establish a new MML session with command mml at any time (in order to log off
completely and end the telnet or rlogin session, command exit is used).
Open

4.2 Different Kinds of Printouts

Different kinds of printouts can be generated in the AXE. Depending on which
kind of printout is generated, routing and selection of standby destinations will
take place in different ways.
The following sections give a brief description of which kinds of printouts exist.
4.2.1 Procedure Printout

Procedure Printouts are used by command programs to give the result of an
MML command with a standard text. The printout is received, immediately
after the MML command has been initiated, on the IO device from which the
MML command was initiated.
If there is a fault on the IO device, the procedure printout is lost.
4.2.2 Answer Printout

Answer Printouts are used by command programs to give the result of an MML
command where the printout contains a unique information part (specified in
a Printout Description). The printout is received, immediately after the MML
command has been initiated, on the IO device from which the MML command
was initiated.
If there is a fault on the IO device, the answer printout is lost.
4.2.3 Check Printout

A Check Printout is received immediately after an MML command has been
initiated. It is an exact copy of the MML command.
Together with the check printout, a request is also sent for confirmation that
the operator really wants the MML command to be executed. The operator
confirms the order with a single semi colon (;) - anything else will inhibit the
execution of the MML command.
If there is a fault on the IO device, the check printout is lost.
4.2.4 Result Printout

Result Printouts are used by command programs to give the result of an MML
command where the printout contains a unique information part (specified in
a Printout Description). The printout is delayed and not immediately received
after the MML command has been initiated.
Result printouts are normally routed to the IO device from which the MML
command was initiated. However, an MML command can also have a
command parameter to specify another output IO device.
When an operator establishes contact with the AXE through an AP, result
printouts are by default received on the ordering IO device. During the MML
Open

session, result printouts can also be redirected to another IO device, or sent

both to the ordering IO device and to another (specified) IO device. This is
achieved by using certain options when the MML session is established with
command mml.
If there is a fault on the IO device that should receive the result printout, the
printout can be re-routed to a common standby device.
4.2.5 Spontaneous Printout

Spontaneous Printouts can be generated by application programs in response
to certain events and contain a unique information part (specified in a Printout
Description). Spontaneous printouts are placed in different groups, where
each group contains printouts with the same functional representation. Each
group has its own Printout Category (PRCA). An alarm printout is a kind of
spontaneous printout.
All spontaneous printouts with the same PRCA will be routed in the same way.
Each spontaneous printout also belongs to a printout class. There are six
printout classes. All spontaneous printouts normally belong to printout class
zero (0), except the alarm printouts which use classes 1 to 5, which correspond
to alarm classes 0 to 4 (often named A1, A2, A3, O1, and O2).
When an operator establishes contact with the AXE through an AP, it is

possible to specify that all spontaneous printouts will be received.
4.3 Re-routing of printouts with IODAC
OPI Attendance Status for Control Room and IO Device, Set describes the
procedure to set the attendance status to attended (ATT). The attendance
status together with the definition of the printout chains determines if
spontaneous printouts shall be re-routed or not. How to configure this function,
see chapter Routing of Alarm printouts with command ordered re-routing
possibilities Page 5 .
OPI Attendance Status for Control Room and IO Device, Reset describes the
procedure to reset attendance status (set it to unattended).
4.4 Alphanumeric Terminal, EMRP-Connected, Inspect
OPI Alphanumeric Terminal, EMRP-Connected, Inspect describes the

inspection and maintenance of alphanumeric terminals. The inspection is
confined to the printer paper and ribbon (refilling the paper or changing the
ribbon).
Open

4.5 Alarm-Display in AP, Inspect and Repair

OPI Alarm-Display in AP, Inspect and Repair describes the procedure to
inspect and repair an alarm-display in an Adjunct Processor (AP). Some steps
in the procedure must be performed on site.
4.6 External Alarm Receiver in AP, Inspect and Repair
OPI External Alarm Receiver in AP, Inspect and Repair describes the procedure
to inspect and repair external alarm receivers in the Adjunct Processor (AP).
Some steps in the procedure must be performed on site.
4.7 External Alarm Receiver in EXALI0, Repair

OPI External Alarm Receiver in EXALI0, Repair describes the procedure to
repair an external alarm receiver connected to an EMRP connected EXALI0.
Some steps in the procedure must be performed on site.
4.8 Actions on Alarms

4.8.1 EXTERNAL ALARM
OPI EXTERNAL ALARM describes actions to take when an EXTERNAL
ALARM alarm is received.
4.8.2 EXTERNAL ALARM RECEIVER FAULT

OPI EXTERNAL ALARM RECEIVER FAULT describes actions to take when
an EXTERNAL ALARM RECEIVER FAULT alarm is received.
4.8.3 IO BLOCKED
OPI IO BLOCKED describes actions to take when an IO BLOCKED alarm
is received.
OPI Typewriter Equipment, Test and Repair describes the procedure to test
the Typewriter Interface (TWI) V24I and the Typewriter Device (TWD). The
test is useful if the alarm printout IO BLOCKED is received, or if erroneous or
abnormal results are detected during the device handling. Some steps in the
4.8.4 IO MML SERVER FAULT

OPI IO MML SERVER FAULT describes actions to take when an IO MML
SERVER FAULT alarm is received.
4.8.5 IO PRINTOUT DESTINATION FAULTY

OPI IO PRINTOUT DESTINATION FAULTY describes actions to take when an
IO PRINTOUT DESTINATION FAULTY alarm is received.
Open

4.8.6 IO STORAGE SPACE WARNING

OPI IO STORAGE SPACE WARNING describes actions to take when an IO
STORAGE SPACE WARNING alarm is received.
4.8.7 MCS AUTHORITY COMMAND INPUT RESTRICTED

OPI MCS AUTHORITY COMMAND INPUT RESTRICTED describes actions
to take when an MCS AUTHORITY COMMAND INPUT RESTRICTED alarm
is received. The alarm is received when an operator has blocked all MML
command entries with command IOUAE with parameter USER=ALL.
4.8.8 MCS AUTHORITY ILLEGAL LOGON ATTEMPT

OPI MCS AUTHORITY ILLEGAL LOGON ATTEMPT describes actions to take
when an MCS AUTHORITY ILLEGAL LOGON ATTEMPT alarm is received.
The IO device is locked up after a predefined number of unsuccessful system
logon attempts. These logon attempts are made from a terminal connected
locally at the AXE or from a terminal connected remotely over a data link.
4.8.9 USER EXCEEDED ALLOWED ACCESS ATTEMPTS

OPI USER EXCEEDED ALLOWED ACCESS ATTEMPTS describes the action
to take when a USER EXCEEDED ALLOWED ACCESS ATTEMPTS alarm is
received. The alarm indicates that a user has exceeded the number of attempts
that is allowed while logging onto MCS Authority System.
Open

5 Glossary
AD Alphanumeric Device
AP Adjunct Processor
APG40 Adjunct Processor Group 40
CP Central Processor
CPT Central Processor Test
EMRP Extension Module Regional Processor
IO Input/Output
IP Internet Protocol
MCS Man-machine Communication Subsystem
MML Man Machine Language
NE Network Element
OPI Operational Instruction
OSS Operations Support System
TW Typewriter
TWD Typewriter Device
TWI Typewriter Interface
6 References
Operational Instructions
[1] IO BLOCKED
20/154 31-ANZ 218 01 Uen
[2] IO Device Standby List, Change

21/154 31-ANZ 218 01 Uen
[3] Alphanumeric Information to File, Periodic Printout

20/154 31-CNZ 218 1003 Uen
[4] Alphanumeric Information to File, Occasional Printout

21/154 31-CNZ 218 1003 Uen
[5] External Alarm Receiver in EXALI0, Repair

Open

20/154 31-CNZ 218 1015 Uen
[6] IO Device, System Standby, Change

20/154 31-CNZ 218 1016 Uen
[7] External Alarm, Connect

20/154 31-CNZ 218 1022 Uen
[8] External Alarm, Disconnect

21/154 31-CNZ 218 1022 Uen
[9] EXTERNAL ALARM

22/154 31-CNZ 218 1022 Uen
[10] EXTERNAL ALARM RECEIVER FAULT

23/154 31-CNZ 218 1022 Uen
[11] Printouts, Spontaneous, Route

21/154 31-CNZ 218 1024 Uen
[12] Attendance Status for Control Room and IO Device, Set

22/154 31-CNZ 218 1024 Uen
[13] Attendance Status for Control Room and IO Device, Reset

23/154 31-CNZ 218 1024 Uen
[14] MCS AUTHORITY ILLEGAL LOGON ATTEMPT

20/154 31-CNZ 218 1034 Uen
[15] MCS AUTHORITY COMMAND INPUT RESTRICTED

29/154 31-CNZ 218 1035 Uen
[16] Alphanumeric Terminal, EMRP-Connected, Inspect

21/154 31-CNZ 218 1047 Uen
[17] Typewriter Equipment, Test and Repair

22/154 31-CNZ 218 1047 Uen
[18] USER EXCEEDED ALLOWED ACCESS ATTEMPTS

1/154 31-CNZ 218 1077 Uen
[19] Alphanumeric Device in AP, Remove

2/154 31-CNZ 218 1084 Uen
[20] IO STORAGE SPACE WARNING

3/154 31-CNZ 218 1084 Uen
[21] IO PRINTOUT DESTINATION FAULTY

4/154 31-CNZ 218 1084 Uen
[22] Alphanumeric Device in AP, Define

5/154 31-CNZ 218 1084 Uen
Open

[23] Alarm-Display in AP, Connect

1/154 31-CNZ 218 1086 Uen
[24] Alarm-Display in AP, Disconnect

2/154 31-CNZ 218 1086 Uen
[25] Alarm-Display in AP, Inspect and Repair

3/154 31-CNZ 218 1086 Uen
[26] Remote Alarm-Display in AP, Define

4/154 31-CNZ 218 1086 Uen
[27] Remote Alarm-Display in AP, Delete

5/154 31-CNZ 218 1086 Uen
[28] External Alarm Receiver in AP, Connect

1/154 31-CNZ 218 1087 Uen
[29] External Alarm Receiver in AP, Disconnect

2/154 31-CNZ 218 1087 Uen
[30] External Alarm Receiver in AP, Inspect and Repair

3/154 31-CNZ 218 1087 Uen
[31] IO MML SERVER FAULT

3/154 31-CNZ 218 1103 Uen
Manual Pages
[32] afpdef: Adjunct Processor File Processing, File, Define

1/190 80-CNZ 220 1014 Uen
[33] cdhdef: Common Destination Handling, Destination, Define

1/190 80-CNZ 220 1015 Uen
[34] cdhdsdef: Common Destination Handling, Destination Set, Define

6/190 80-CNZ 220 1015 Uen
[35] cpdinsert: IO Device in CP, Insert

5/190 80-CNZ 218 1103 Uen
[36] mml: Man-Machine Language, Commands, Execute

1/190 80-CNZ 218 1104 Uen
Command Descriptions
[37] SYBUP: System Functions, Backup Information Output, Punch

3/190 82-CNZ 211 3071 Uen
[38] IOROL: IO SUBSYSTEM FUNCTIONS, ROUTING LIST, LOAD

8/190 82-CNZ 213 42 Uen
Open

[39] IOEXC: IO SUBSYSTEM FUNCTIONS, EXCHANGE IDENTITY, CHANGE

1/190 82-CNZ 213 1025 Uen
[40] PTCOE: PROCESSOR TEST, CONNECTION, END

32/190 82-CNZ 214 077 Uen
[41] PTCOI: PROCESSOR TEST, CONNECTION, INITIATE

33/190 82-CNZ 214 077 Uen
[42] ALHBI: Alarm Functions, Heart Beat Sending, Initiate

8/190 82-CNZ 218 1005 Uen
[43] IODAC: IO SUBSYSTEM FUNCTIONS, DEVICE ATTENDANCE,

CHANGE
2/190 82-CNZ 218 1048 Uen
[44] IOEXP: IO Subsystem Functions, Exchange Identity, Print

1/190 82-CNZ 218 1056 Uen
[45] APLOC: AP Maintenance, AP Local Mode, Change

1/190 82-CNZ 218 1089 Uen
[46] EXIT: Man-Machine Communication Functions, Log Off

2/190 82-CNZ 218 1089 Uen
Other References
[47] HB
3/190 83-CNZ 213 1005 Uen
[48] NOT ACCEPTED

1/190 83-CNZ 218 1050 Uen
[49] How to Access an AXE with APG40

3/198 17–ANZ 218 40/4

Alarm and CMD On APG40

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarm and CMD On APG40

Uploaded by

Copyright:

Available Formats

Open

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

Alarm and Command Administration on the APG40

Overview and additional explanations to procedures for configuration, operation

AXE and APG40 are trademarks of Ericsson.

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

3.5.2 Defining and Connecting External Alarm Receivers to EMRP Connected

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

1.1 Revision Information

This document is written for System Administrators and Operators responsible

System Administrators using this document should be:

2.1.1 Man-machine Communication Subsystem (MCS)

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

3.1 Routing of Printouts

Output of important printouts is secured by selecting a standby destination, if the

Different kinds of printout can be generated in the AXE. Depending on which

3.1.1 Configuration in APG

OPI IO Device, System Standby, Change describes the procedure to change

OPI Alphanumeric Information to File, Occasional Printout describes the

OPI Alphanumeric Information to File, Periodic Printout describes the procedure

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

3.1.1.1 Result Printouts

3.1.1.2 Spontaneous Printouts

If the originally specified destination is faulty, the IO device defined as standby

OPI Alphanumeric Device in AP, Define describes the procedure to define

OPI Alphanumeric Device in AP, Remove describes the procedure to remove

3.1.1.3 Routing of Alarm Printouts with Command Ordered Re-routing

1. Logon to the AP which houses the AP I/O functionality.

2. cpdinsert -i 10.0.0.1:9000 -r 30 -e crlf AD-123

3. cpdinsert -x *:00,30 AD-124

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

Note: A new subfile is created every half-hour. If no alarm printout

5. IOROL:PRCA=36&&56, DTYPE=FIRST, IO=AD-123, CLASSUA=6,

Note: From now on the alarm printouts will be sent to AD-123.

Note: From now on the alarm printouts will be sent to subfile

3.1.2 Configuration in Remote System

3.2 Heartbeat between CP and OSS

Printout HB is used for remote supervision of program execution in AXE. When

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

3.2.1 Heartbeat Configuration in APG

3.2.2 Heartbeat Configuration in OSS

3.3 Exchange Header

Command IOEXC is used to change the exchange header.

Command IOEXP is used to print the exchange header.

An alarm is sent as a spontaneous printout when the disturbance occurs. All

The alarms can be indicated visually and acoustically using an alarm-display

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

alddef ald-1 Subordinate

alddef -a 10.0.0.1 -p 7013 ald-64

Figure 1 Local and Remote Alarm-Displays

Exchange Alarm-Display Description

EAB/AZA/DG Christian Magnusson 2/198 17–ANZ 218 40/4 Uen

EAB/AZA/DGC (S. Telin) PC-APM 2006-05-03 B

Exchange ALD-1 Shows the alarm status of own exchange

3.4.1.1 Local Alarm-Display Connect or Disconnect