Outputs

Radio Commander BR 7.0 / UMR 3.0

Output Manual OML:Non Standard
Maintenance
A50023-X4005-A2-4-7619
2 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
f Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in prop-
erty damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The systemcomplies with the standard EN 60950 / IEC 60950. All equipment connected has to comply
with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile
knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und
Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und
wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte
mssen die zutreffenden Sicherheitsbestimmungen erfllen.
Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.
Copyright (C) Siemens AG 2003-2003.
Issued by the Information and Communication Networks Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
A50023-X4005-A2-4-7619 3
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
Issues
Change indications (Ind.):
N = new; G = modied; 0 = deleted;
Document Title Page(s) Issue/Ind.
MMN:UMR 3.0 . . . . . . . . 1... 54 4/ N
This document consists of a total of 54 Pages.
Issue History
Issue
Number
Date of Is-
sue
Reason for Update
Draft1 Jan. 2003 First Draft release.
1
2
3
4 Dec. 2003 FEKAT correction CU9965
4 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
A50023-X4005-A2-4-7619 5
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Time of Network Element out of sync with OMC (500) . . . . . . . . . . . . . . . . . 9
2.2 SW Recovery Action (501) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Disk Generic HW Error (502) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 Mirror/SubMirror Failure (503) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.5 MetaDb Failure (504) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.6 Threshold Crossed (505) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7 OMT-OMP Communication Failure (OMT) (506) . . . . . . . . . . . . . . . . . . . . 15
2.8 Disconnected BSS (507). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.9 1 O-Link Down (508). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.10 LAN Card Failure (509). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.11 Possible Fault on a HSI Communication Board (510) . . . . . . . . . . . . . . . . 19
2.12 Possible Fault on a PCM Communication Board (511) . . . . . . . . . . . . . . . 20
2.13 PCM Switch Failure (512) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.14 External Alarm Device Failure (513) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.15 Log Instance Reached Warning Threshold (514) . . . . . . . . . . . . . . . . . . . . 23
2.16 Log Instance Reached Minor Threshold (515) . . . . . . . . . . . . . . . . . . . . . . 24
2.17 Log Instance Reached Major Threshold (516) . . . . . . . . . . . . . . . . . . . . . . 25
2.18 Log Instance Reached Critical Threshold (517) . . . . . . . . . . . . . . . . . . . . . 26
2.19 The Agent Has Hit Configured Threshold Level (518) . . . . . . . . . . . . . . . . 27
2.20 The MPA has Hit Configured Threshold Level (519) . . . . . . . . . . . . . . . . . 28
2.21 B-Link Corba Disconnected (520). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.22 R-Link CMISE Disconnected (521) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.23 SubMirror Resyncing (522) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.24 Network Unavailable (523) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.25 The nbManagedElementId Received doesnt Match the NodeB Configuration
within RC (524) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.26 SubMirror Failure (525). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.27 Alignment Procedure Failed (527) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.28 OMP-OMP Communication failure (OMP) (528). . . . . . . . . . . . . . . . . . . . . 36
2.29 NetViewer Server indeterminate notification (529) . . . . . . . . . . . . . . . . . . . 37
2.30 NetViewer Server critical notification (530) . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.31 NetViewer Server major notification (531) . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.32 NetViewer Server minor notification (532) . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.33 NetViewer Server warning notification (533). . . . . . . . . . . . . . . . . . . . . . . . 41
2.34 NetViewer Connection Map Under Configuration (534) . . . . . . . . . . . . . . . 42
2.35 NetViewer Connection Down (535). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.36 Local SMLC state file does not exist! (536) . . . . . . . . . . . . . . . . . . . . . . . . 44
3 Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.1 serviceResponse (RC_LOG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.2 serviceResponse (SbsOcm:session) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3 serviceFailure (RC_LOG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.4 serviceFailure (SbsOcm:session) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
3.5 unauthorizedAccessAttempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.6 sbsOimFileTransferControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.7 outOfHoursActivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.8 authenticationFailure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.1 Specific Problems for the Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
A50023-X4005-A2-4-7619 7
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
1 Introduction
The goal of this manual is to describe all alarms and systeminformations which can gen-
erated by the Radio Commander.
The software attempts to provide a precise error description for each alarm containing
all informations for the operator and manufacturer for rapid localization, investigation
and elimination of the fault. There is no relation between the number of described faults
and their frequency of occurrence in the system.
This manual is organized according to the error ID's.
Error ceased messages clears all alarms for a certain probable cause of one object.
Error ID:
Shows the Error ID for the notification
MOC:
Identifies the managed object class of the fault or error.
Version:
Format not yet defined.
Error information:
This gives a detailed overview about the occurred error:
<eventType>
Values:
communicationAlarm
environmentalAlarm
equipmentAlarm
qualityOfServiceAlarm
processingErrorAlarm
<probableCause>
Identies the probable cause of the fault or error. The probable cause is taken out of
a predened set of values dened for each alarm type.
<specicProblems>
This is a short description of the error.
<perceivedSeverity>
According to the CCITT Rec. X.733 all alarmnotications produced in switching sys-
tems have to be classied concerning the severity of their impact on the NE's func-
tionality.
Values: indeterminate, critical, major, minor, warning
<tresholdInfo>
Gives information about the reached threshold.
<monitoredAttributes>
Currently not used.
<additionalText>
This eld will be used to give reason for the occurred error/event. According to
CCITT X.733 this part, when present, allows a free form text description to be re-
ported.
8 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
Immediate defense action:
This section describes the defense action accomplished by the software every time the
particular Failure Event occurs. The defense action is accomplished to attempt to solve
or at least to overcome the problem.
n.a. is reported if no defense action is associated to the Failure Event.
Proposed repair actions:
Describes the actions the operator must perform to attempt to solve the problem.
Every time that a diagnostic on a faulty object fails, the operator has to replace the faulty
module (specified in the Test Report) following the procedure described in the according
maintenance manual.
Error description:
Concise description of the probable cause of the error.
1.1 Abbreviations
Abbr. Meaning
BSC Base Station Controller
BSS Base Station Subsystems
CLI Command Line Interface
GUI Graphical User Interface
LAN Local Area Network
LMT Local Maintenance Terminal
(m) Value is mandatory
MOC Managed Object Class
MSC Mobile Services Switching Center
n.a. Not available
NE Network Element
(o) Value is optional
OMP Operating and Maintenance Processor
OMT Operating and Maintenance Terminal
PCM Puls Code Modulation
RC Radio Commander
SMLC Serving Mobile Location Center
WAN Wide Area Network
Tab. 1.1 Abbreviations
A50023-X4005-A2-4-7619 9
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2 Alarms
2.1 Time of Network Element out of sync with OMC (500)
Error ID: 500
MOC: DNODEB, DRNC, DBSS
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmClockSynchronisa-
tionProblem
<specificProblems> Time of Network Element
out of sync with OMC
<perceivedSeverity> warning
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> reason: NE time is out of
sync with RCtime, NEtime
set. Date and Time:
outOfSyncBy:
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
No action required
Error description: The error is generated in case the BSC, RNC or NodeN clock
is not synchronized with the OMP clock.
Periodic time check must be activated explicitly from GUI or
CLI session.
At the configured time intervals, OMP checks whether the
clock of each NE connected is synchronized with the OMP. If
the difference is bigger than a predefined threshold, then date
& time of the BSC, RNCor NodeB are set and this error is gen-
erated.
Note: at the time the O-link, Ift-R or Itf B connection is estab-
lished, date & time of the BSC, RNC or NodeB are set without
generating an alarm, even if the threshold was exceeded
10 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.2 SW Recovery Action (501)
Error ID: 501
MOC: OMP, OMT
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> softwareProgramAbnormallyTer-
minated
<specificProblems> SW recovery action
<perceivedSeverity> warning
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> <the individual recovery informa-
tion (what will be recovered)>
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
no repair action necessary - automatic recovery, take alarmas
notice
Error description: RC initiates autonomous SW recovery action
A50023-X4005-A2-4-7619 11
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.3 Disk Generic HW Error (502)
Error ID: 502
MOC: HDD
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmDiskProblem
<specificProblems> Disk Generic HW Error
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
Try to make a back-up of all data.
Proposed repair ac-
tions:
1.Locate the effected disk.
2.Contact local SUN service or local staff to replace the faulty
disk and provide the following information:
Effected OMP.
Type of effected disk.
3.Make sure that after have replaced the disk the related alarm
is ceased. If the alarm after few minutes is still active contact
local SUN service or local staff. Otherwise give hddReplace
command available on CLI/GUI.
Error description: A physical error was detected in the hard disk.The following
cases are possible:
OMP failure on disk with system software
No redundancy/mirroring, only one disk
May be that the RC stops working. Then it is not longer possi-
ble to access/maintain of the RC and the connected radio sub-
systems.
Redundancy/mirroring, two or more disks
The system switches automatically to redundant disk. The
system and RC will continue working.
OMP failure on disk with RC data
No redundancy/mirroring, only one disk
The RC stops working immediately. It is not longer possible to
access/maintain of the RC and the connected radio sub-
systems.
Redundancy/mirroring, two or more disks
The system switches automatically to redundant disk. The
system and RC will continue working.
12 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.4 Mirror/SubMirror Failure (503)
Error ID: 503
MOC: DATAUNIT
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmDiskProblem
<specificProblems> Mirror/SubMirror failure
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1. Locate the effected disk on OMP: execute metastat and
metadb SDS maintenance commands to see what is/are the
specific problemwithin Solstice Disk Suite Object (Mirror/Sub-
mirror). See Solstice Disksuite 4.2 User's Guide for further de-
tails.
2. Contact local SUN service or local staff.
Provide the error message and exact information fromthe pre-
vious step.
Error description: Solstice Disk Suite Object (Mirror/Submirror) malfunction.
A50023-X4005-A2-4-7619 13
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.5 MetaDb Failure (504)
Error ID: 504
MOC: DISKLAYOUT
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmDatabaseInconsistency
<specificProblems> MetaDb failure
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.Locate the affected meta DB replicas on OMP: execute
metadb SDS maintenance command to see what is/are the
specific problem within Solstice Disk Suite Object (meta DB
Replicas). See Solstice Disksuite 4.2 User's Guide for further
details.
2.Contact local SUN service or local staff.
It is necessary to reconfigure the MetaDB.
Provide the error message and exact information about your
system.
Error description: Solstice Disk Suite Object (MetaDB Replica) malfunction on
OMP. RC could will stop working soon.
14 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.6 Threshold Crossed (505)
Error ID: 505
MOC: DATAUNIT
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> gsmSystem ResourcesOverload
<specificProblems> Threshold crossed
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
Do not write on this Data Unit anymore, until related alarm
ceases.
Proposed repair ac-
tions:
1.) Perform fault clearance task T-15 Checking available disk
space to collect information.
2.) Free some space on the involved data unit (for example de-
lete old files) or expand the quota assigned to the involved
data unit (for example adding a new disk to the system), using
information collected from previous step.
Error description: The involved data unit of type equal to ufs has crossed the re-
lated threshold.
A50023-X4005-A2-4-7619 15
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.7 OMT-OMP Communication Failure (OMT) (506)
Error ID: 506
MOC: OMT
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmLinkFailure
<specificProblems> OMT-OMP communication failure
(OMT)
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1. Check the network cable of the OMT:
Are the network cable plugs inserted correctly into the sockets
at both ends?
2. Check the network connection to OMT from an UNIX shell
in the primary OMP with the following
command:
ping <omt_name>
If the network connection is OK, the OMT will acknowledge.
3. Check whether OMT is shutdown.
If there is still no connection between OMT and OMP contact
your local staff.
Error description: A communication failure is detected on connection with the
OMT.
16 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.8 Disconnected BSS (507)
Error ID: 507
MOC: OLINK
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmLinkFailure
<specificProblems> Disconnected BSS
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Check whether there is only one, several or all BSS resp.
BSC concerned.
2.) Performfault clearance tasks T-26 Checking X.25 configu-
ration, T-27 Checking X.25 link status, T-28 Tracing an X.25
link, and T-32 Checking status of PCMcard or T-33 Checking
status of HSI ports.
3.) Check plugs and HSI or PCM card on the OMP using the
corresponding manuals.
4.) Check the following processes: osinetd, osimcsd,
em_cmip, x25netd
5.) Check failed BSC status from LMT.
Error description: The BSS is disconnected.
There are three possibilities where the connection between
BSS and OMP can be disturbed. This depends on how the
BSS is connected to the OMP:
- Direct link between OMP and BSS using HSI card (A)
- WAN link between OMP and BSS using HSI card
- PCM (nailed-up) link: connection from OMP to MSC using
Sprite card (B)
- PCM (nailed-up) link: connection from MSC to BSS (C)
A50023-X4005-A2-4-7619 17
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.9 1 O-Link Down (508)
Error ID: 508
MOC: OLINK
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmLost Redundancy
<specificProblems> 1 O-link down
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Check physical connection.
2.) If available check the Sprite card and Sprite port.
3.) Perform fault clearance task T-26 Checking X.25 configu-
ration, T-27 Checking X.25 link status, T-28 Tracing an X.25
link.
4.) Check osinetd process.
5.) Check ftcserver.luc process.
6.) Check failed BSC status from LMT.
Error description: The Olink redundancy is lost. The specified Olink is discon-
nected.
18 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.10 LAN Card Failure (509)
Error ID: 509
MOC: OMP
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> LAN Card Failure
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Check network connections of the OMP:
Are the network cable plugs inserted correctly into the sockets
at both ends?
If the plugs are inserted correctly this alarm means that one
lan card is faulted. Then contact your local staff providing the
error message and exact information about your OMP.
If the plugs aren't inserted correctly, plug themin. Note that for
this version of RC the emitted alarm will not be cleared.
Error description: On Extended Redundant OMP one lan card (or network con-
nection) is faulted.
OMP switched to redundant lan card and emitted this alarmto
indicate this situation.
A50023-X4005-A2-4-7619 19
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.11 Possible Fault on a HSI Communication Board (510)
Error ID: 510
MOC: HSI_CARD
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> Possible Fault on a HSI Communi-
cation Board
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Check plugs and HSI card on the OMP using the corre-
sponding manuals.
2.) Check the following processes: osinetd, osimcsd,
em_cmip, x25netd
3.) Performfault clearance tasks T-26 Checking X.25 configu-
ration, T-27 Checking X.25 link status, T-28 Tracing an X.25
link, and T-33 Checking status of HSI ports.
4.) Contact your local staff to check the cables and the HSI
card itself using the corresponding manual. Provide the alarm
number and message and exact information fromthe previous
step.
Error description: All OLinks which are connected to the same HSI card became
faulty.
20 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.12 Possible Fault on a PCM Communication Board (511)
Error ID: 511
MOC: SPRITE_CARD
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> Possible Fault on a PCM Commu-
nication Board
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Check plugs and PCM Card on the OMP using the corre-
sponding manuals.
2.) Check the following processes: osinetd, osimcsd,
em_cmip, x25netd
3.) Performfault clearance tasks T-26 Checking X.25 configu-
ration, T-27 Checking X.25 link status, T-28 Tracing an X.25
link, and T-33 Checking status of HSI ports.
4.) Contact your local staff to check the cables and the Sprite
card itself using the corresponding manual. Provide the alarm
number and message and exact information fromthe previous
step.
Error description: All OLinks which are connected to the same PCM card be-
came faulty.
A50023-X4005-A2-4-7619 21
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.13 PCM Switch Failure (512)
Error ID: 512
MOC: OMP
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> PCM Switch failure
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Contact your local staff to check the cables plugged in correct-
ly: FromOMP to PCMSwitch and fromPCMSwitch to the net-
work using the correspondent manual.
Error description: PCMSwitch failure. The connection fromOMP to PCMSwitch
(so called Selector Unit) or fromPCMSwitch to the network is
disturbed.
22 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.14 External Alarm Device Failure (513)
Error ID: 513
MOC: EXT_ALARM_DEVICE
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> External Alarm Device Failure
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1. Check the components of the alarm device panel (e.g.
lamp(s), siren) using the corresponding manual.
2. Check the cables whether they are plugged in correctly and
into the correct ports.
Error description: A fault occurred on External Alarm Device Panel.
A50023-X4005-A2-4-7619 23
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.15 Log Instance Reached Warning Threshold (514)
Error ID: 514
MOC: RC_LOG
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Storage Capacity Problem
<specificProblems> Log instance reached warning
threshold
<perceivedSeverity> warning
<thresholdInfo> triggeredThreshold:"SbsOim":sb-
sOimCapacityAlarmThreshold
observedValue: integer (an addi-
tional capacity alarm threshold ex-
ceeded)
<monitoredAttributes> attributeId: "SbsOim":sbsOimMax-
LogSizeMegaByte
attributeValue: integer (max log
size of the log instance expressed
in MegaByte)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Increase the size (maxLogSize parameter) of the alarmed
log instance.
2.) Increase the additional threshold value of the alarmed log
instance.
Error description: An additional capacity threshold has been reached or exceed-
edby the log instance.
24 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.16 Log Instance Reached Minor Threshold (515)
Error ID: 515
MOC: RC_LOG
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Storage Capacity Problem
<specificProblems> Log instance reached minor thres-
hold
<perceivedSeverity> minor
<thresholdInfo> triggeredThreshold:"SbsOim":sb-
sOimCapacityAlarmThreshold
observedValue: integer (mi-
norThreshold or capacity alarm
threshold exceeded)
<monitoredAttributes> attributeId: "SbsOim":sbsOimMax-
LogSizeMegaByte
attributeValue: integer (max log
size of the log instance expressed
in MegaByte)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Increase the size (maxLogSize parameter) of the alarmed
log instance.
2.) Increase the minor threshold value of the alarmed log in-
stance.
Error description: A minor capacity threshold has been reached or exceeded by
the log instance named.
A50023-X4005-A2-4-7619 25
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.17 Log Instance Reached Major Threshold (516)
Error ID: 516
MOC: RC_LOG
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Storage Capacity Problem
<specificProblems> Log instance reached major thresh-
old
<perceivedSeverity> major
<thresholdInfo> triggeredThreshold:"SbsOim":sb-
sOimCapacityAlarmThreshold
observedValue: integer (ma-
jorThreshold or capacity alarm
threshold exceeded)
<monitoredAttributes> attributeId: "SbsOim":sbsOimMax-
LogSizeMegaByte
attributeValue: integer (max log
size of the log instance expressed
in MegaByte)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Increase the size (maxLogSize parameter) of the alarmed
log instance.
2.) Increase the major threshold value of the alarmed log in-
stance.
Error description: A major capacity threshold has been reached or exceeded by
the log instance named.
26 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.18 Log Instance Reached Critical Threshold (517)
Error ID: 517
MOC: RC_LOG
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Storage Capacity Problem
<specificProblems> Log instance reached critical
threshold
<perceivedSeverity> critical
<thresholdInfo> triggeredThreshold:"SbsOim":sb-
sOimCapacityAlarmThreshold
observedValue: integer (criticalTh-
reshold or capacity alarmthreshold
exceeded)
<monitoredAttributes> attributeId: "SbsOim":sbsOimMax-
LogSizeMegaByte
attributeValue: integer (max log
size of the log instance expressed
in MegaByte)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Increase the size (maxLogSize parameter) of the alarmed
log instance.
2.) Increase the critical threshold value of the alarmed log in-
stance.
3.) If the log full condition has been reached set the logFullAc-
tion to wrap for going on writing log records by dropping the
oldest ones.
Error description: A critical capacity threshold has been reached/exceeded by
the log instance or a log full condition has occurred.
A50023-X4005-A2-4-7619 27
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.19 The Agent Has Hit Congured Threshold Level (518)
Error ID: 518
MOC: RC
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Threshold Crossed
<specificProblems> The agent has hit configured
threshold level
<perceivedSeverity> minor
<thresholdInfo> thresholdLevel: integer
<monitoredAttributes> (o)
<additionalText> The agent has hit certain threshold
level
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
If critical threshold was crossed, then the operator has three
possibilities:
1. Turn on automatic overload (if it was not activated yet), then
the link to the overloaded agent will be automatically locked af-
ter the critical threshold was crossed (Alternative 1)
2. Turn off automatic overload handling (if it was not deactivat-
ed yet), then he has the possibility to use (Alternative 2), but
be aware, the system can be really overloaded.
3. Re-configure the overload parameters (Alternative 3), but
be aware, because the system can be really overloaded.
Error description: An agent (BSS or RNS) has crossed the pre-configured
threshold level of events-per-agent.
The overload handling is implemented in the MPA (Message
Protocol Adapter) and it offers 4 threshold levels (warning, mi-
nor, major, critical - selectable during installation or frommain-
tenance terminal) for check the overload situation on the links
or on the MPA itself. In overload situation one alarmis emitted
with severity for the corresponding thresholds level.
28 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.20 The MPA has Hit Congured Threshold Level (519)
Error ID: 519
MOC: RC
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Threshold Crossed
<specificProblems> The MPA has hit configured thresh-
old level
<perceivedSeverity> minor
<thresholdInfo> thresholdLevel: integer
<monitoredAttributes> (o)
<additionalText> The agent has hit certain threshold
level
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
If critical threshold was crossed, then the operator has three
possibilities:
1. Turn on automatic overload (if it was not activated yet), then
the link to the overloaded agent will be automatically locked af-
ter the critical threshold was crossed.
2. Turn off automatic overload handling (if it was not deactivat-
ed yet), then he has the possibility to use, but be aware, the
system can be really overloaded.
3. Re-configure the overload parameters, but be aware, be-
cause the system can be really overloaded.
Error description: An MPA (Message Protocol Adapter) has crossed the pre-
configured threshold level of events-per-MPA.
The overload handling is implemented in the MPA and it offers
4 threshold levels (warning, minor, major, critical - selectable
during installation or frommaintenance terminal) for check the
overload situation on the links or on the MPA itself. In overload
situation one alarmis emitted with severity for the correspond-
ing thresholds level.
A50023-X4005-A2-4-7619 29
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.21 B-Link Corba Disconnected (520)
Error ID: 520
MOC: ITFB
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> Link Failure
<specificProblems> B-link Corba disconnected
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Check Network connection.
Error description: n.a.
30 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.22 R-Link CMISE Disconnected (521)
Error ID: 521
MOC: ITFR
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> R-link CMISE disconnected
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Check network connections of the OMP:
Are the network cable plugs inserted correctly into the sockets
at both ends?
If not, plug them in; the network connection will establish itself
within a few seconds.
If the plugs are inserted correctly or network connection
doesn't establish then contact your local staff providing the er-
ror message and exact information about your OMP.
Error description: OMP has no access to the LAN ( lan card(s) or network con-
nection(s) are faulted).
This alarm will only appear on the OMT running on the OMP.
The following scenarios can be the reason for this alarm:
- complete RNC outage
- restart of the RNC
- FE problems on RNC
- LAN problems
A50023-X4005-A2-4-7619 31
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.23 SubMirror Resyncing (522)
Error ID: 522
MOC: DATAUNIT
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmDiskProblem
<specificProblems> SubMirror Resyncing
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
No Action.
Error description: Solstice DiskSuite Submirror is resyncing, i.e. there are data
transferred fromone part of a mirror to the other, normally after
replacing a faulty disk. The duration of resyncing depends on
the disk capacity and the amount of stored data. It can take
more than one hour.
Working with the Radio Commander is not affected.
32 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.24 Network Unavailable (523)
Error ID: 523
MOC: OMP
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmEquipmentFailure
<specificProblems> Network unavailable
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Check network connections of the OMP:
2.) Are the network cable plugs inserted correctly into the
sockets at both ends? If not, plug themin; the network connec-
tion will establish itself within a few seconds.
3.) If the plugs are inserted correctly or network connection
doesn't establish then contact your local staff providing the er-
ror message and exact information about your OMP.
Error description: OMP has no access to the LAN ( lan card(s) or network con-
nection(s) are faulted).
This alarm will only appear on the OMT running on the OMP.
A50023-X4005-A2-4-7619 33
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.25 The nbManagedElementId Received doesnt Match the
NodeB Conguration within RC (524)
Error ID: 524
MOC: ITFB, ITFR
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> Configuration or Customization Er-
ror
<specificProblems> The nbManagedElementId re-
ceived doesn't match the NodeB
configuration within RC
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Reconfigure B-Link with correct IOR of the NodeB.
Error description: n.a.
34 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.26 SubMirror Failure (525)
Error ID: 525
MOC: DATAUNIT
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> gsmLostRedundancy
<specificProblems> SubMirror failure
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Depending on the occurred error condition, following actions
can be undertaken:
- Condition 1: also alarms on all HDDs belonging to an exter-
nal disk channel are active
Repair action: check physical connection of the external disk
channel to the system. If disconnected then re-connect it to
the system. If a HDD is defect replace it. Wait until all hdd be-
longing to the re-connected channel alarms are ceased. Then
give first disablediskmirror and then enablediskmirror com-
mands available on CLI/GUI.
- Condition 2: also an alarmon a hdd which data unit instance
belong to is active.
Repair action: physically replace faulted hard disk or re-con-
nect it to the related channel, then give hddReplace command
available on CLI/GUI.
- Condition 3: no alarmon a HDD which data unit instance be-
long to is active.
Locate the effected SDS object (Mirror/Submirror) disk: exe-
cute metastat and metadb SDS maintenance commands to
see what is/are the specific problem. See Solstice Disksuite
4.2 User's Guide for further details.
Then Contact local SUN service or local staff, providing the er-
ror message and exact information about your system above
retrieved.
Error description: Lost of redundancy of a Data unit instance.
This error occurred only in a mirrored disk layout configuration
and it can be due to a logical error to an SDS object or to a
physical fault.
A50023-X4005-A2-4-7619 35
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.27 Alignment Procedure Failed (527)
Error ID: 527
MOC: sbsTrauEquipment, sbsBtsePico, sbsBtseP, sbsBtseEM, sb-
sBtsE, sbs3gManagedElement, nbManagedElement,
nb2ManagedElement (all alarms generate locally at Radio
Commander)
Version: n.a.
Error information: <eventType> processingErrorAlarm
<probableCause> Software Program Abnormally
<specificProblems> Alignment Procedure Failed
<perceivedSeverity> warning
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Try re-aligning using commands.
Error description: An error occurred during an alignment phase
36 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.28 OMP-OMP Communication failure (OMP) (528)
Error ID: 528
MOC: OMP
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> gsmLinkFailure
<specificProblems> OMP-OMP Communication failure
(OMP)
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1. Check the network cable of the OMP:
Are the network cable plugs inserted correctly into the sockets
at both ends?
2. Check the network connection to OMP from an UNIX shell
in the primary OMP with the following command:
ping <omp_name>
If the network connection is OK, the OMP will acknowledge.
3. Check whether OMP is shutdown. If there is still no connec-
tion between primary OMP and another OMP contact your lo-
cal staff.
Error description: A communication failure is detected on connection with other
OMP.
A50023-X4005-A2-4-7619 37
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.29 NetViewer Server indeterminate notication (529)
Error ID: 529
MOC: OimMicrowavesEquipment
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> Equipment Failure
<specificProblems> NetViewer Server indeterminate
notification
<perceivedSeverity> indeterminate
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Open NetViewer to get more details on the NetViewer equip-
ment state/status.
Error description: An equiment notification of indeterminate severity received.
38 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.30 NetViewer Server critical notication (530)
Error ID: 530
MOC: OimMicrowavesEquipment
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> Equipment Failure
<specificProblems> NetViewer Server critical notifica-
tion
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Open NetViewer to get more details on the NetViewer equip-
ment state/status.
Error description: An equiment notification of critical severity received.
A50023-X4005-A2-4-7619 39
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.31 NetViewer Server major notication (531)
Error ID: 531
MOC: OimMicrowavesEquipment
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> Equipment Failure
<specificProblems> NetViewer Server major notification
<perceivedSeverity> major
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Open NetViewer to get more details on the NetViewer equip-
ment state/status.
Error description: An equiment notification of major severity received.
40 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.32 NetViewer Server minor notication (532)
Error ID: 532
MOC: OimMicrowavesEquipment
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> Equipment Failure
<specificProblems> NetViewer Server minor notifica-
tion)
<perceivedSeverity> minor
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Open NetViewer to get more details on the NetViewer equip-
ment state/status.
Error description: An equiment notification of minor severity received.
A50023-X4005-A2-4-7619 41
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.33 NetViewer Server warning notication (533)
Error ID: 533
MOC: OimMicrowavesEquipment
Version: n.a.
Error information: <eventType> equipmentAlarm
<probableCause> Equipment Failure
<specificProblems> NetViewer Server warning notifica-
tion
<perceivedSeverity> warning
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
Open NetViewer to get more details on the NetViewer equip-
ment state/status.
Error description: An equiment notification of warning severity received.
42 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.34 NetViewer Connection Map Under Conguration (534)
Error ID: 534
MOC: OimNetviewerLink
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> LinkFailure
<specificProblems> NetViewer Connection Map Under
Configuration
<perceivedSeverity> warning
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
No action required.
Wait until map reconfiguration is completed.
Error description: A communication failure is detected due to a map reconfigura-
tion.
A50023-X4005-A2-4-7619 43
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
2.35 NetViewer Connection Down (535)
Error ID: 535
MOC: OimNetviewerLink
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> LinkFailure
<specificProblems> NetViewer Connection Down
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1.) Check network connections of the OMP:
Are the network cable plugs inserted correctly into the sockets
at both ends?
2.) If the plugs are inserted correctly this alarmmeans that one
lan card is faulted. Then contact your local staff providing the
error message and exact information about your OMP. If the
plugs aren't inserted correctly, plug them in. Note that for this
version of RC the emitted alarm will not be cleared.
Error description: The Netviewer is disconnected.
44 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
2.36 Local SMLC state le does not exist! (536)
Error ID: 536
MOC: OimSmlc
Version: n.a.
Error information: <eventType> communicationsAlarm
<probableCause> LinkFailure
<specificProblems> Local SMLC state file does not ex-
ist
<perceivedSeverity> critical
<thresholdInfo> (o)
<monitoredAttributes> (o)
<additionalText> (o)
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
1. Check Network connection between RC and SMLC server
Are the cable plugs inserted correctly into the sockets at both
ends?
2. Check the FTP script, which is responsible for the file trans-
fer.
Error description: The RC can not find/open the local SMLC state file.
A50023-X4005-A2-4-7619 45
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
3 Notications
3.1 serviceResponse (RC_LOG)
3.2 serviceResponse (SbsOcm:session)
Error ID: n.a.
MOC: RC_LOG
Version: n.a.
Error information: <eventType> serviceReport
<serviceReportCause> (m) serviceResponse
<additionalText> (o) the following:
<reason> SeeLogs on security event log in-
stance
delete log records
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
<affectedUser> (o) "The affected RC user login
name"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security audit trail report as described in X.740 is given.
Error ID: n.a.
MOC: "SbsOcm":session
Version: n.a.
Error information: <eventType> serviceReport
<serviceReportCause> (m) serviceResponse
<additionalText> (o) the following:
46 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
3.3 serviceFailure (RC_LOG)
<reason> (m)create User Profile
delete User Profile
set User Profile
import Security Data
export Security Data
import Password Dictionary
export Password Dictionary
delete Password Dictionary
abort User Session
change Own Password
change System Password
abort Unix Session
RC login
RC logout
reset Failed Login Counter
set Global Settings
lock Display
unlock Display
create Authorization Profile
delete Authorization Profile
set Authorization Profile
create Subprofile
delete Subprofile
set Subprofile
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
<affectedUser> (o) "The affected RC user login
name"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security audit trail report as described in X.740 is given.
Error ID: n.a.
MOC: RC_LOG
Version: n.a.
A50023-X4005-A2-4-7619 47
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
3.4 serviceFailure (SbsOcm:session)
Error information: <eventType> serviceReport
<serviceReportCause> (m) serviceFailure
<additionalText> (o) the following:
<reason> SeeLogs on security event log in-
stance
delete log records
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
<affectedUser> (o) "The affected RC user login
name"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security audit trail report as described in X.740 is given.
Error ID: n.a.
MOC: "SbsOcm":session
Version: n.a.
Error information: <eventType> serviceReport
<serviceReportCause> (m) serviceFailure
<additionalText> (o) the following:
<reason> (m) create User Profile
delete User Profile
set User Profile
import Security Data
export Security Data
import Password Dictionary
export Password Dictionary
delete Password Dictionary
abort User Session
change Own Password
48 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
change System Password
abort Unix Session
RC login
RC logout
SeeLogs on security event log in-
stance
delete log records
reset Failed Login Counter
set Global Settings
lock Display
unlock Display
create Authorization Profile
delete Authorization Profile
set Authorization Profile
create Subprofile
delete Subprofile
set Subprofile
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
<affectedUser> (o) "The affected RC user login
name"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security audit trail report as described in X.740 is given.
A50023-X4005-A2-4-7619 49
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
3.5 unauthorizedAccessAttempt
Error ID: n.a.
MOC: "SbsOim":sbsOimAuthProfile
Version: n.a.
Error information: <eventType> securityServiceOrMechanismVio-
lation
<securityAlarmCause> (m) unauthorizedAccessAttempt
<securityAlarmSeverity> (m) warning
<securityAlarmDetector> (m) RC
<serviceUser> (m) "RC user login name"
<serviceProvider> (m) RC
<additionalText> (o) the following:
<reason> (m) unauthorized entered CLI
command
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security service or mechanism violation as described in
X.736 occurred.
50 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
3.6 sbsOimFileTransferControl
Error ID: n.a.
MOC: "SbsOim":sbsOimFileTransferControl
Version: n.a.
Error information: <eventType> "SbsOim":SbsUploadInfoType. It
describes the event type (startUp-
load, endUpload, endConversion)
which notification is related to.
<fileTransferId> The transfer identifier assigned by
RC to each upload procedure.
<fileName> The path name of the file uploaded.
<result> The result of the upload (success,
aborted, failed, none).
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: This notification is used to inform the begin and the end of an
upload regarding a file of measures.
A50023-X4005-A2-4-7619 51
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
3.7 outOfHoursActivity
Error ID: n.a.
MOC: "SbsOim":sbsOimUserProfile
Version: n.a.
Error information: <eventType> timeDomainViolation
<securityAlarmCause> (m) outOfHoursActivity
<securityAlarmSeverity> (m) warning
<securityAlarmDetector> (m) RC
<serviceUser> (m) "RC user login name"
<serviceProvider> (m) RC
<additionalText> (o) the following:
<reason> (m)
command not in allowed time re-
strictions
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security service or mechanism violation as described in
X.736 occurred.
52 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
3.8 authenticationFailure
Error ID: n.a.
MOC: "SbsOcm":session
Version: n.a.
Error information: <eventType> securityServiceOrMechanismVio-
lation
<securityAlarmCause> (m) authenticationFailure
<securityAlarmSeverity> (m) warning
<securityAlarmDetector> (m) RC
<serviceUser> (m) "RC user login name"
<serviceProvider> (m) RC
<additionalText> (o) the following:
<reason> (m) RC login failed
RC login failed: OMT unknown
RC login failed: OMT has inappro-
priate type
RC login failed: OMT not unlocked
RC login failed: Display host un-
known
RC login failed: Display host not
unlocked
RC login failed: Wrong password
RC login failed: Password expired
RC login failed: Out of allowed time
period
RC login failed: Invalid Unix user
for RC operator
RC login failed: RC operator ac-
count blocked
<dateAndTime> (m) "DateAndTime"
<userName> (m) "RC user login name"
<hostName> (m) "Hostname of OMT"
<sessionNumber> (m) "Number of OMT session"
<terminalAddress> (m) "Display of OMT session"
Immediate defense
action:
n.a.
Proposed repair ac-
tions:
n.a.
Error description: A security service or mechanism violation as described in
X.736 occurred.
A50023-X4005-A2-4-7619 53
Outputs
Radio Commander BR 7.0 / UMR 3.0
Output Manual OML:Non Standard Maintenance
4 Appendix
4.1 Specic Problems for the Alarm List
Error ID Specic Problems
502 Disk Generic HW Error
503 Mirror/SubMirror Failure
504 MetaDb Failure
505 Threshold crossed
506 OMT-OMP communication failure (OMT)
507 Disconnected BSS
508 1 O-Link down
509 LAN Card Failure
510 Possible Fault on a HSI Communication Board
511 Possible Fault on a PCM Communication Board
512 PCM Switch failure
513 External Alarm Device Failure
515 Log instance reached minor threshold
516 Log instance reached major threshold
517 Log instance reached critical threshold
518 The agent has hit configured threshold level
519 The MPA has hit configured threshold level
520 B-link Corba disconnected
521 R-link CMISE disconnected
522 Sub Mirror Resyncing
523 Network unavailable
524 The nbManagedElementId received doesn't match the NodeB configura-
tion within RC
525 SubMirror failure
528 OMP-OMP Communication failure (OMP)
529 NetViewer Server indeterminate notification
530 NetViewer Server critical notification
531 NetViewer Server major notification
532 NetViewer Server minor notification
535 NetViewer Connection Down
Tab. 4.1 Specic Problems for the Alarm List in the GUI (without warnings)
54 A50023-X4005-A2-4-7619
Output Manual OML:Non Standard Maintenance Outputs
Radio Commander BR 7.0 / UMR 3.0
536 Local SMLC state file does not exist!
Error ID Specic Problems
Tab. 4.1 Specic Problems for the Alarm List in the GUI (without warnings)