Alarm Library

Alarm_Library
Alarm Code Alarmname EMS Classification Service Affected Technology Domain

7404 High DC Volt Nokia Notification No LTE RAN
7403 Low DC VoltaNokia Service ThreateNo LTE RAN
7413 Genset Run Nokia Notification No LTE RAN
7414 Genset Fail Nokia Service ThreateNo LTE RAN
7415 Fuel Tank EmNokia Service ThreateNo LTE RAN
7412 Battery Stole Nokia Service ThreateNo LTE RAN
7401 AC Failure Al Nokia Performance DeNo LTE RAN
7653 CELL FAULT Nokia Outage Yes LTE RAN
7650 BASE STATI Nokia Outage Yes LTE RAN
10070 DR FILE SY - EMS Alarm No LTE RAN
61652 R&D Service - EMS Alarm No LTE RAN
10073 VCENTER/ES- EMS Alarm No LTE RAN
61649 LMP access v- EMS Alarm No LTE RAN
10000 Directory serv- EMS Alarm No LTE RAN
10072 STATUS AND- EMS Alarm No LTE RAN
10007 Disk sharing s- EMS Alarm No LTE RAN
10008 JACORB servic - EMS Alarm No LTE RAN
10009 OSI service is- EMS Alarm No LTE RAN
10006 Disk sharing s- EMS Alarm No LTE RAN
10014 Backup action- EMS Alarm No LTE RAN
10010 Database serv- EMS Alarm No LTE RAN
10012 Database table - EMS Alarm No LTE RAN
10013 Database con- EMS Alarm No LTE RAN
10016 Scheduling se- EMS Alarm No LTE RAN
10017 FTP service i - EMS Alarm No LTE RAN
10018 Load balancer- EMS Alarm No LTE RAN
10015 Insufficient s - EMS Alarm No LTE RAN
10024 WAS service i- EMS Alarm No LTE RAN
10021 Available disk- EMS Alarm No LTE RAN
10022 WAS Deployme - EMS Alarm No LTE RAN
10023 WAS HTTP ser - EMS Alarm No LTE RAN
10030 DNS service i- EMS Alarm No LTE RAN
10031 NTP service i- EMS Alarm No LTE RAN
10027 An Intelligen - EMS Alarm No LTE RAN
10029 WAS thread po - EMS Alarm No LTE RAN
10037 Node is not w- EMS Alarm No LTE RAN
10034 HP SIM report- EMS Alarm No LTE RAN
10033 SOCKS proxy- s EMS Alarm No LTE RAN
10042 NFS service i- EMS Alarm No LTE RAN
10038 Certificate is - EMS Alarm No LTE RAN
10040 OMAgentAF ser - EMS Alarm No LTE RAN
10041 OMAgent core- EMS Alarm No LTE RAN
10050 Virtual machi - EMS Alarm No LTE RAN
10051 Virtual mach - EMS Alarm No LTE RAN
10043 File system cl- EMS Alarm No LTE RAN
10044 HP SIM servic- EMS Alarm No LTE RAN
10055 vSphere HA de - EMS Alarm No LTE RAN
10053 The datastore- EMS Alarm No LTE RAN
10054 The host CPU- EMS Alarm No LTE RAN
Page 1
Alarm_Library
10052 The datastore- EMS Alarm No LTE RAN
10059 NetAct self-mo - EMS Alarm No LTE RAN
10056 The host memo - EMS Alarm No LTE RAN
10057 The host serv- EMS Alarm No LTE RAN
10058 Insufficient r - EMS Alarm No LTE RAN
10062 Network Upli - EMS Alarm No LTE RAN
10063 vSphere HA en - EMS Alarm No LTE RAN
10060 The network co - EMS Alarm No LTE RAN
10061 The vSphere -H EMS Alarm No LTE RAN
10084 WAS Directory - EMS Alarm No LTE RAN
10081 JMS notificat - EMS Alarm No LTE RAN
10082 Relative time - EMS Alarm No LTE RAN
10083 The number of - EMS Alarm No LTE RAN
10064 VDP data stora - EMS Alarm No LTE RAN
10091 vManager is n- EMS Alarm No LTE RAN
10085 Process File D - EMS Alarm No LTE RAN
10086 One or severa- EMS Alarm No LTE RAN
10087 WAS is out o - EMS Alarm No LTE RAN
10100 Available disk- EMS Alarm No LTE RAN
86022 Self-monitorin- EMS Alarm No LTE RAN
10005 service is not - EMS Alarm No LTE RAN
200002 Available REP- EMS Alarm No LTE RAN
200003 Number of file- EMS Alarm No LTE RAN
200001 Available REP- EMS Alarm No LTE RAN
200012 FS usage of E- EMS Alarm No LTE RAN
200015 FS usage of ET - EMS Alarm No LTE RAN
200100 Available PM - EMS Alarm No LTE RAN
200101 Available PM - EMS Alarm No LTE RAN
200023 Overload dete- EMS Alarm No LTE RAN
200103 Inode usage i- EMS Alarm No LTE RAN
200104 Disk usage of- EMS Alarm No LTE RAN
200105 Inode usage i- EMS Alarm No LTE RAN
200102 Disk usage of- EMS Alarm No LTE RAN
209086 PERFORMANC - EMS Alarm No LTE RAN
209087 DB CONNECT - EMS Alarm No LTE RAN
200106 PM data prese - EMS Alarm No LTE RAN
209085 ALL PM PIPE- EMS Alarm No LTE RAN
209090 CANNOT CRE - EMS Alarm No LTE RAN
209091 LOCAL PART- EMS Alarm No LTE RAN
Page 2
Alarm_Library
209088 ADAPTATION- EMS Alarm No LTE RAN
209089 NO MAXVALU- EMS Alarm No LTE RAN
209162 LOCAL PART- EMS Alarm No LTE RAN
209160 TABLES WIT - EMS Alarm No LTE RAN
209095 COSPRCMX -H EMS Alarm No LTE RAN
209166 Configured PM - e EMS Alarm No LTE RAN
209167 Configured PM - EMS Alarm No LTE RAN
20395_61261Receive bandw - Notification No LTE RAN
86610 Rule with Id: - EMS Alarm No LTE RAN
10075 INSUFFICIEN- EMS Alarm No LTE RAN
70244 Corrupted Al - EMS Alarm No LTE RAN
20007 Internal servic- EMS Alarm No LTE RAN
69303 RRC CSSR Nokia Performance DeYes LTE RAN
69304 UL HARQ degr Nokia Performance DeYes LTE RAN
69302 RSSI PUCCHNokia Performance DeYes LTE RAN
69309 VOLTE CSSRNokia Performance DeYes LTE RAN
69306 Zero Traffic CNokia Performance DeYes LTE RAN
69307 Sleeping CellNokia Performance DeYes LTE RAN
69308 VOLTE DROPNokia Performance DeYes LTE RAN
7112 BASE STATI - Service ThreateNo LTE RAN
69305 ERAB DROP Nokia Performance DeYes LTE RAN
69310 Hanging cellsNokia Performance DeYes LTE RAN
7113 BASE STATI - Service ThreateNo LTE RAN
7656 BASE STATI Nokia Service ThreateNo LTE RAN
61029 LOS on unit 0Nokia Service ThreateNo LTE RAN
61050 Missing or noNokia Service ThreateNo LTE RAN
61201 Transport modNokia Service ThreateNo LTE RAN
61079 SFP HW FAI - Service ThreateNo LTE RAN
7102 BASE STATI - Performance DeYes LTE RAN
7110 BASE STATIO- Performance DeYes LTE RAN
7651 BASE STATI Nokia Performance DeYes LTE RAN
7657 BASE STATI Nokia Performance DeYes LTE RAN
41003 LICENSE CAP Nokia Performance DeYes LTE RAN
7406 High TemperaNokia Performance DeYes LTE RAN
61611 TWAMP PLR NokiaT Performance DeYes LTE RAN
61610 TWAMP RTT - Performance DeNo LTE RAN
7654 CELL OPERANokia Performance DeYes LTE RAN
7114 CELL SERVI - Performance DeYes LTE RAN
7108 BASE STATI - Not Reachable No LTE RAN
61022 BFD GROUP - Not Reachable No LTE RAN
61076 LINK OAM LI- Not Reachable No LTE RAN
61077 LINK OAM CR - Not Reachable No LTE RAN
71103 ID CONFLIC Nokia Not Reachable No LTE RAN
71104 NE CONNECT Nokia Not Reachable No LTE RAN
61075 LINK OAM LO- Not Reachable No LTE RAN
925 Network ElemNokia Notification No LTE RAN
7101 BASE STATI - Notification No LTE RAN
Page 3
Alarm_Library
7402 Rectifire ModNokia Notification No LTE RAN
7405 Battery Fuse Nokia Notification No LTE RAN
7411 Fan Fail SensNokia Notification No LTE RAN
7409 Temperature Nokia Notification No LTE RAN
7410 SPD Sensor Nokia Notification No LTE RAN
7407 Battery CurrenNokia Notification No LTE RAN
7408 Door Sensor Nokia Notification No LTE RAN
7416 AC outdoor reNokia Notification No LTE RAN
7652 BASE STATIONokia Notification No LTE RAN
9047 ALARMS FRO Nokia Notification No LTE RAN
7662 Spare Base St- Notification No LTE RAN
9069 ALARM BRIDG - Notification No LTE RAN
7665 BASE STATI Nokia Notification No LTE RAN
9228 ALARM DATANokia Notification No LTE RAN
9255 Alarm Databas Nokia Notification No LTE RAN
9252 NETWORK EL Nokia Notification No LTE RAN
9229 ACK UPLOAD- Notification No LTE RAN
9251 Network ElemNokia Notification No LTE RAN
9450 CONNECTION - Notification No LTE RAN
9451 SNMP AGENT - Notification No LTE RAN
61006 BTS booted Nokia Notification No LTE RAN
61010 BTS reset reqNokia Notification No LTE RAN
9256 ACK DATABA- Notification No LTE RAN
46100 NETACT SOFNokia Notification No LTE RAN
61030 DEAD PEER - Notification No LTE RAN
61058 SynchronizatiNokia Notification No LTE RAN
61059 Synchronous Nokia
E Notification No LTE RAN
61074 CRL UPDATE- Notification No LTE RAN
61500 Too many logiNokia Notification No LTE RAN
61410 CCM FAULT L- Notification No LTE RAN
61411 ETH AIS FAU- Notification No LTE RAN
61523 Bluetooth repeNokia Notification No LTE RAN
61510 AUTOMATIC - Notification No LTE RAN
61520 Bluetooth En Nokia Notification No LTE RAN
61521 Bluetooth pai Nokia Notification No LTE RAN
61522 Bluetooth netNokia Notification No LTE RAN
61526 WI-FI CARD - Notification No LTE RAN
61527 WI-FI CARD - Notification No LTE RAN
61605 BFD 1 down,in Nokia Notification No LTE RAN
61525 SFP HW WARN - Notification No LTE RAN
61524 ssh enabled Nokia Notification No LTE RAN
61613 NTP Server isNokia Notification No LTE RAN
61606 BFD $SESSI - Notification No LTE RAN
61607 Auto-negotiatNokia Notification No LTE RAN
61631 ToP master seNokia Notification No LTE RAN
61618 BTS AND/OR- Notification No LTE RAN
61619 Toggling: LOSNokia Notification No LTE RAN
61623 SyncE SSM Tim Nokia Notification No LTE RAN
61624 SyncE QualityNokia Notification No LTE RAN
61616 Vendor BTS cerNokia Notification No LTE RAN
Page 4
Alarm_Library
61639 IPSEC EMER- Notification No LTE RAN
61632 DUP ADDR ON - Notification No LTE RAN
61638 CONFIGURAT - Notification No LTE RAN
61641 IP Traffic Ca Nokia Notification No LTE RAN
61642 BTS Local OANokia Notification No LTE RAN
70064 BACKUP ER Nokia Notification No LTE RAN
61648 LMP CARRIE- Notification No LTE RAN
61643 IPSEC TUNN- Notification No LTE RAN
70025 POSSIBLE SNokia Notification No LTE RAN
70162 RAID ARRAYNokia Notification No LTE RAN
70164 ETHERNET LNokia Notification No LTE RAN
70111 FAILED TO Nokia Notification No LTE RAN
70158 FILE SYSTE Nokia Notification No LTE RAN
70159 MANAGED OB Nokia Notification No LTE RAN
70173 BACKEND DA Nokia Notification No LTE RAN
70186 CLUSTER OPNokia Notification No LTE RAN
70189 MANAGED OB Nokia Notification No LTE RAN
70166 MANAGED ONokia Notification No LTE RAN
70168 CLUSTER STNokia Notification No LTE RAN
70267 EXTERNAL UNokia Notification No LTE RAN
70268 EXTERNAL LNokia Notification No LTE RAN
70358 SSL CONNECNokia Notification No LTE RAN
70255 DRBD SYNCH Nokia Notification No LTE RAN
71054 O&M MEDIATNokia Notification No LTE RAN
71057 NWI3 NOTIFINokia Notification No LTE RAN
71001 MEASUREMENokia Notification No LTE RAN
71052 OMS FILE T Nokia Notification No LTE RAN
70377 SYSTEM CLONokia Notification No LTE RAN
71000 PM FTP CONNokia Notification No LTE RAN
71105 BTS O&M TONokia Notification No LTE RAN
71101 OMS ALARM Nokia Notification No LTE RAN
71136 NE O&M UPD- Notification No LTE RAN
71107 INSECURE ONokia Notification No LTE RAN
71129 TROUBLESHO Nokia Notification No LTE RAN
7655 CELL NOTIFINokia Notification No LTE RAN
71106 TROUBLESHO Nokia Notification No LTE RAN
71137 WARNINGS RNokia Notification No LTE RAN
71108 TRACE CONN Nokia EMS Alarm No LTE RAN
30001 SYSTEM USE- EMS Alarm No LTE RAN
30002 USER DOES -N EMS Alarm No LTE RAN
30003 UNUSED US - EMS Alarm No LTE RAN
30000 APPLICATIO - EMS Alarm No LTE RAN
30007 NETWORK EL - EMS Alarm No LTE RAN
30004 USER ACCOU - EMS Alarm No LTE RAN
30005 POTENTIAL - EMS Alarm No LTE RAN
30006 POTENTIAL B- EMS Alarm No LTE RAN
7100 BASE STATI - Service ThreateYes LTE RAN
30008 DIRECTORY - EMS Alarm No LTE RAN
30009 Potential bru - EMS Alarm No LTE RAN
71058 NE O&M CONNokia Outage Yes LTE RAN
7658 BASE STATIO- Notification No LTE RAN
69301 Test T&PNokia Performance DeYes LTE RAN
76539 ALL CELL F Nokia Outage Yes LTE RAN
7425 EXTERNAL AL Nokia Notification No LTE RAN
Page 5
Alarm_Library
60407 AUTOMATION Nokia EMS Alarm No LTE RAN
69311 Test Alarm U Nokia EMS Alarm No LTE RAN
60404 ENTRY CRITNokia EMS Alarm No LTE RAN
Page 6
Alarm_Library
Vendor Category MO Default Severity Alarm Type Alarming Delay (minutes)
NOKIA FM EnodeB Minor environmental 1
NOKIA FM EnodeB Major environmental 1
NOKIA FM Cell Critical Quality of ser 10
NOKIA FM EnodeB Critical equipment 10
NOKIA FM EMS Major - 10
NOKIA FM EMS Minor - 10
NOKIA FM EMS Critical operationalVio 10
NOKIA FM EMS Critical processingErr 10
NOKIA FM EMS Minor processingErr 10
NOKIA FM EMS Major processingErr 10
NOKIA FM EMS Critical qualityOfServi 10
Page 7
Alarm_Library
NOKIA FM EMS Critical equipment 10
NOKIA FM EMS Critical communicatio 10
NOKIA FM EMS Major operationalVio 10
NOKIA FM EMS Major operationalVio 10
NOKIA FM EMS Minor processingErr 10
Page 8
Alarm_Library
NOKIA FM EnodeB Minor - 10
NOKIA PM Cell Major User Defined 10
NOKIA FM EnodeB Critical Quality of ser 10
NOKIA FM EnodeB Critical communicatio 10
NOKIA FM EnodeB Critical Communicatio 10
NOKIA FM EnodeB Major equipment 10
NOKIA FM EnodeB Major communicatio 10
NOKIA FM EnodeB Critical Operational Vi 10
NOKIA FM Cell Major Quality of ser 10
NOKIA FM Cell Critical Quality of ser 10
NOKIA FM EnodeB Major Processing Er 10
NOKIA FM EnodeB Minor communicatio 10
NOKIA FM EnodeB Warning Quality of ser 10
Page 9
Alarm_Library
NOKIA FM EnodeB Critical Environmental 10
NOKIA FM EnodeB Minor Quality of ser 10
NOKIA FM EnodeB Minor equipment 10
NOKIA FM EnodeB Critical Processing Er 10
NOKIA FM EnodeB Minor Processing Er 10
NOKIA FM EnodeB Warning Processing Er 10
NOKIA FM EnodeB Warning communicatio 10
Page 10
Alarm_Library
NOKIA FM EnodeB Warning Communicatio 10
NOKIA FM EnodeB Major equipment 10
NOKIA FM EnodeB Minor equipment 10
NOKIA FM EnodeB Major Quality of ser 10
NOKIA FM EnodeB Major Quality of ser 10
NOKIA FM EnodeB Minor Quality of ser 10
NOKIA FM EnodeB Critical equipment 10
NOKIA FM Cell Minor Quality of ser 10
NOKIA FM EMS Critical securityViolat 10
NOKIA FM EMS Major securityViolat 10
NOKIA FM EMS Minor securityViolat 10
NOKIA FM EMS Minor securityViolat 10
NOKIA FM EnodeB Critical Equipment 10
NOKIA FM Cell Major - 10
NOKIA FM Cell Major - 10
NOKIA FM EnodeB Major - 10
Page 11
Alarm_Library
Page 12
Alarm_Library
Estimated time to Close(Minutes) Incident Creation TT Delay (minutes) WO Delay (minutes)
120 No - -
120 Yes 0-
120 No - -
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
60 Yes 0 20
60 Yes 0-
120 No - -
120 No - -
120 No - -
120 No - -
600 No - -
120 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
Page 13
Alarm_Library
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
Page 14
Alarm_Library
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
600 No - -
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 Yes 0-
120 No - -
120 No - -
Page 15
Alarm_Library
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
Page 16
Alarm_Library
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
120 No - -
60 Yes 0-
120 No - -
120 No - -
60 Yes 0-
12 No - -
10 Yes 0-
10 Yes 0-
10 No - -
Page 17
Alarm_Library
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
10 No - -
Page 18
Alarm_Library
Clear Name Clear Trap Software Release Description Impact Suggestion Generic Alarm Name
- Yes 17A This is an e - - -
- Yes 17A Check the reason
- for theCheck
fault the
fromreason
-the supplementary
for the fault from text the
fieldsupplementary
of the alarm. t
- for theCheck
fault the
fromreason
-the supplementary
fieldsupplementary
of the alarm. t
- Yes - - - - -
- Yes - - - - -
- Yes - - - - -
- Yes - - - - -
- Yes 8_17.2 In case both2. directory
If both directory
servers
3. Contactare
servers
Nokia
not
- running,
areTechnical
not this
running,
Support
alarmthenwill
forNetAct
be help.
raised
willfor
noteac fun
- Yes - - - case the-2.LDAP
In Referrequests- section
to the reach "Directory
the directory service"
serverunder VM which
Trouble fa
- Yes 8_17.2 The directoryDirectory Server 3. Contact
will return
Nokia
- inconsistent
Technical Support
data that forcauses
help. some of
- Yes 8_17.2 The database LDAP acceContact5. Checkthe the- online documentation "Administering High
- Yes 8_17.2 Writing to th NFS-depend 6. Contact
4. Check "CORBA Nokia
- Technical
Service" Support for help.
under Troubleshooting NetA
- Yes 8_17.2 The JACORB CORBA
s Name5.
4. Check the troubleshooting sectionfor
Contact Nokia
- Technical Support ofhelp.
the Operating D
- Yes 8_17.2 The OSI servOSI service5. Check Contactthe Nokia
- online Technical Support "Administering
documentation for help. High
- Yes 8_17.2 Reading from NFS-depend 6. Contact Nokia
/backup - Technical Support for help.
- Yes 8_17.2 The backup T t he previo2. CheckContact"Databases"
Nokia
- Technical
underSupport for help. NetAct in
Troubleshooting
- Yes 8_17.2 The database All databas3. Contact Nokia
- Technical Support for help.
# perl /opt/cpf/oma/AF/cpf_scripts/tablespace_usage.pl
- Yes 8_17.2 The tablespac When the ta 4. Contact Nokia
- Technical Support
2. Check "Databases" under Troubleshooting for help. NetAct in
- Yes 8_17.2 The number The databaservice 3. Contact crond - start
Nokia Technical Support for help.
- Yes 8_17.2 There are noScheduled5. 4. Check
If the above
the- document
steps do "Administrering
not help, contactFTP" Nokia
in Technic
the Ope
- Yes 8_17.2 The FTP serv File transf 5. 6. Check
Contactthe Nokia
- document
Technical Support for Load
"Administering help. Balancers
- Yes 8_17.2 The load balBalancing t6. Contact Nokia - Technical Support for help.
- Yes 8_17.2 The backup T t he next ba 3. For assistance,
-
Check the document contact Nokia Technical
"Administering JavaSupport
EE" in thewith
- Yes 8_17.2 The WebSpher Requests
When the pfile
4. Delete
1. Contact Nokia
- full, Technical
systemunnecessary
is no data data Support
canfrom thefor
be added. filehelp.
This
systemcanorcause
incre
- Yes 8_17.2 The file systeThe NetAct3. 2.Performance
Contactthe
Check Nokia
- document
Data Technical
Collection
Support
Framework
"Administering for Java
help.(DCFW)
EE" in the is d
- Yes 8_17.2 The WebSphe All Adminis3.
Processing 4.HTTP
Contact
Check Nokia
- document
requests
the Technical
may take Support timefor
"Administering
more help.
toJava
get processed
EE" in the
- Yes 8_17.2 The IBM HTTP If all IBM HTTP 4. Contact
servers
Check Nokia
the- are not
Technical
document running, Support
then none
"Administering for DNS
help.
of the
in HTTP
NetAct" re
- Yes 8_17.2 The DNS serv Host name5. Contact Nokia
- Technical Support
Check the document "Administering NTP Service" infor help.
- Yes 8_17.2 The NTP serv The system2. 6. Symptoms
Contact Nokia- collected
Technical Support for help.
at /var/log/cpfwas_logs-*.zip.
- Yes 8_17.2 A minor alarm Websphere2. 3.AContact
In case of - memory
your issues, administrator
local system collect heap dumps or Nokia at Tec
/va
- Yes 8_17.2 The WebSpher Requests s4. 3. If
Check /var/log/selfmon/logger.log
the alarm - remains active for a long for time,
logs and
check error
thed
- Yes 8_17.2 VM is down.Services in5. 3. Contact
Click on Nokia
- event
the Technical
for moreSupport for help.
information.
- Yes 8_17.2 The HP Syste Affected s 4. Contact Nokia
- Technical Support
3. Click on the event for more information. for help.
- Yes 8_17.2 The HP Syste Affected D 3. 4. Click
Contact on Nokia
- event
the Technical
for moreSupport for help.
information.
- Yes 8_17.2 The HP Syste Affected s 5. 4. Check
Contactthe Nokia
- document
Technical Support for SOCKS
"Administering help. Proxy"
- Yes 8_17.2 The SOCKSApplicatio
pr 6. Contact
Check Nokia
-
the document Technical Support for
"Administering High help.
Availability" fo
- Yes 8_17.2 The NFS serv File Acces 5. 1. Contact
Check which Nokia
- ofTechnical Support
the certificates areforabout
help.to expire by
- Yes 8_17.2 The certificaCorrespondi 2. Contact -
Nokia Technical
4. Check the section "Administering O&M Support for help.
Agent" of the
- Yes 8_17.2 The OMAgentA Alarms will5. Contact Nokia
- Technical
4. Check the section "Administering O&M Support for help.
Agent" of the
- Yes 8_17.2 The OMA Agen NetAct Sel2. 5. Check
ContactvCenter
Nokia
- Technical Support
for the detailed for help.
cause of the error.
- Yes 8_17.2 CPU usage of When the C 3. Check
2. ContactvCenter
Nokia
- Technical Support
cause of the error.
- Yes 8_17.2 Memory usage When the m Contactthe
3. Check Nokia
- document
Technical Support for High
"Administering help. Availability
- Yes 8_17.2 The file syst File Acces 4. Contact
6. To collectNokiaTechnical
-the needed Linux Support for help.use the RH
information,
- Yes 8_17.2 The HP Syste
Hardware a7.
- Error in the network-partitionedContact
2. Check vCenteryour
-
host local
for the detailed cause of or
system administrator theNokia
error.Tec
- Yes 8_17.2 - No port groups
•Host
VDP are
error
enabled
backup3. Contact
jobfor vSphere
Nokia
fails.- Technical
HA Support for help.
- Yes 8_17.2 If the datastore
• Cloning
disk space
fails.
NOTE:
2. usage
Check This exceeds
-alarm for
vCenter isthe
not
thespecified
raised
detailedforthreshold,
all theofadditional
cause then
the an thic
error. ala
- Yes 8_17.2 The host CPWhen the h3. Contact Nokia - Technical support for help.
Page 19
Alarm_Library
2. Check the section "Reconfiguring the datastore usag
- Yes 8_17.2 The datastorWhen2. Highthe da
3. Check
Contact
Availability
2. Nokia
-
functionality Technical
failure Support for help. and /var/lo
/var/log/vcenterselfmon/logfile.log.*
- Yes 8_17.2 NetAct self-m 3. VM recovery 3.the
If Contact
ishost
notmemory
Nokia
possible
- Technical
with critical
consumption Support
service
alarmfor still
help.
failures
persists, and
- Yes 8_17.2 The host meThe memory 7. Check
1. Collect the log- processes
file bundle running
for ESXin orthe
ESXihosthosts
that and
usesvCe m
- Yes 8_17.2 The host swaWhen the s2. Contact Nokia
- Technical Support
Check vCenter for the detailed cause of the error. for help.
- Yes 8_17.2 There
vCenter are insWhen
alarm resou
to monitor 3. Contact
11.loss
Click of on Nokia
-Next.Technical
network Support for
uplink redundancy onhelp.
a virtual switch
- Yes 8_17.2 Physical failure
Reason: Lastorredund
misconfiguration
12.Click
5. Clickon onIssues
-Finish.
in some of Issues
> All the uplink components (NIC, ca
- Yes 8_17.2 vSphere hasn't VMreceived
will be 2. 6.VMware
Select the
Check - alarm,
tools
vCenter heartbeats
forright
the clickor detected
detailedandcause
selectany"Reset
of network
the to Gree
error. or
- Yes 8_17.2 The networkLost netwo1. 3. Check
ContactvCenterNokia
- Technical Support
cause of the error.
- Yes 8_17.2 The vSphereThe VMs ar2. 5. Contact
Check the Nokia
- Troubleshooting
Technical Support NetActfordocument
help. in the O
- Yes 8_17.2 Websphere co Directory s6. If the problem - persists, contact your local administrat
- Yes 8_17.2 There are toIf the num 3. Without
Checkanalysis
the- Websphere
if the messages
Application are Server
deletedsection
then therein t
- Yes 8_17.2 Garbage collRequests s3. 4. Check
If the problem
the- Websphere
persists Application
for more than an hour,
Server share
section in t
- Yes 8_17.2 The Webspher WAS applica 4. Click
7. If the on problem
- back
the persists for moremark)
button(arrow than an hour, in
present share
the rt
- Yes 8_17.2 The VDP stora VDP backup
2. Service 8.
or Repeat
VM levelthe -high
steps (from step-7
availability alarms to are
8) for
notrest of the VM
managed.
- Yes 8_17.2 VM level high 3. VM restoration
The process Check
3. may /var/l-
is
Try tonot not
restartpossible
be ablethe to in
process.case a VM is in poweroff/suspe
open a new socket or create any
- Yes 8_17.2 One or more- The process 4. Contact
where may start
NokiaTechnical
- misbehaving
applicationName Support
if it name
is the reaches
for
of help. maximum
the failing applicfil
- Yes 8_17.2 One or sever1. Application
The WAS If the
Note:
serviceapplication
1. Duemay - tobe restart
restricted ispermissions
unavailable not or successful,
restarted.
when then contactg
handling
- Yes 8_17.2 The memory2.a Requests 2. submitted
If disk usage -to aofWASthe file
instance
system mayreach
not the
be processed.
threshold, th
- Yes 8_17.2 The file sys When the fi3. If Problem- not resolved Contact Nokia Technical Sup
- Yes 8_17.2 An applicati O&M AgentInvestigate4.NCheck the- trouble shooting guideline to restart the se
- Yes 8_17.2 The service The service5. Contact Nokia - Technical Support for help.
- Yes 8 The REP fileWhen the fi- -
- Yes 8 The number The o perfor- -
- Yes 8 Available REWhen the R - -
- Yes 8 The number The of perfor- -
- Yes 8 The number Ifo backup - -
- Yes 8 The file sys The perfor- -
- Yes 8 The number Some o PM dat - -
- Yes 8 The number Some o PM dat - -
- Yes 8 The number Some o PM da - -
- Yes 8 The file sys If backup - -
- Yes 8 The number There o are - -
- Yes 8 The file sys Some PM dat - -
- Yes 8 The file sys Some PM da - -
- Yes 8 The file sys Some PM dat - -
- Yes 8 PM South and If disk us - -
- Yes 8 PM South and If disk in - -
- Yes 8 The file sys There are - -
- Yes 8 The system d Already pr - -
- Yes 8 PM South med If disk in - -
- Yes 8 PM North med If disk us - -
- Yes 8 PM North med If disk in - -
- Yes 8 PMNumber
3. South medofIf files
disk inusexport
- directory - crossed the defined threshold;
- Yes 8 4. Number
Failed ofNo
to connectfiles
morein the
to notify
fil- database.
directoryPM - crossed the defined
DB partitioning threshold.
manager (pmpmgrmx) h
- Yes 8 More informationPerformanc
is available
- in the-error log $OMCLOGDIR/dbpm-pmpmgm/w
- Yes 8 This alarm
1. Disk i Files
usage prese-defined threshold.
crossed -
- Yes 8 2. Disk inodeNo usage
morecrossed
fil- defined - threshold
- Yes 8 This alarm
Local indexcan Performanc
is occur when
unusable - for athere are
- insufficient
partitioned privileges to
PM measurement create
table. PMaDB partition
partit
- Yes 8 Adaptation name Performanc
is the-identifier for- PM DB partitioning manager when calling
Page 20
Alarm_Library
PM DB Partitioning Manager (pmpmgrmx) was unable to acquire the lock for th
- Yes 8 Adaptation Name Performanc
is the- identifier for- PM DB Partitioning Manager when calling
- Yes 8 More information
Adaptation Performanc
name is available
the-identifier in the of-certain
error logadaptation
$OMCLOGDIR/dbpm-pmpmgm/w
that PM DB partitioning
- Yes 8 More information
Local index is Data can
loss be
unusable - for
found from- the error
a partitioned log of pmpmgrmx
PM measurement table.inPM$OMCLOGD
DB partit
- Yes 8 Adaptation name
Performanc
is the - identifier for - PM DB
Found some tables with data on PM_MAXVALUE partition above the threshold partitioning manager when calling
- Yes 8 No data should Performanc
be accumulated
- on-this partition above the PM_MAXVALUE th
- Yes 8 This alarm is
Cosprcmx can
Performanc
occur while
hanged when
- processing
there are - insufficient
PM data for privileges to create a partition
an adaptation.
- Yes 8 In the
PM export cosprc
“Userfilter
Additional for Information”,
configuration- file contains- you can moreobtain
thanthe one information
filter definedsuch as Pr
which is
- Yes 8 $OMCLOGDIR/etload/werlog8890.0.log.
PM export convertFiltering o-
configuration file- contains more than one convert defined w
For detailed Converting
information- about the error, - please check the following log file of th
PM pipe configuration file contains -more than one export pipe defined which is
No more fil-
No more fil- -
- Yes - - aware that
Be - this configuration
- could - lead to an outage situation. For detailed
No more fil- -
- Yes - - - - -
- Yes - - - - -
- Yes - - - - -
- Yes - - - - -
- Yes 17A User Define - - -
- Yes 17A User
The problem causes a base station- unit/service to be degraded or faulty.
Define - -
- Yes 17A Check the reason - for the - fault from-the supplementary text field of the alarm.
- Yes 17A Userproblem
The Define - causes a -base station- unit/service to be degraded or faulty.
- Yes 17A Check the reason - for the -Check
fault the
fromreason -the supplementary
for the fault from text the of the alarm. t
fieldsupplementary
- Yes 17A alarm. - loss of remote alarm.management - access to other network elements in
LOS on unitYes 17A The fault is generated
- loss
Lossofofsynchronization
only
4.
2. Connect
whenfor
synchronization
Check thea- SFP
loop
interface
ififthe
thecable
interface
validityisand
notcheck
interface is
(couldconfigured
isused
used whether
be wrongas
asaa
assynchronizati
LMP
the alarm
type). (that is
synchronizat d
Missing or nYes 17A The fault is generated
Depending
- no calls are only
3. on
1. Insert
when
useaof
Re-commission
possible the
compliant
-the
for interface
Ethernet
the to SFPis interface,
connections
remove not
module.
configured
the over the
hardware
thisabove-described
as
unit LMPreferenc
unit (that is
- Yes 17A NOTE:
A unit variable
malfunctioning - lossofoftheshould
remote
NOTE:
SFPbe management
Before
replaced
transceiver - re-commissioning,
by
wasaccess
appropriateto other
detected. HWthenetwork
names
hardwareelements
configured
unit mu in
- Yes 17A The SFP hasThe reported
SFP isaReplace transmission
FAULT IDthe- fault condition and has disabled the lase
- Yes 17A The service/The
problem causes service 4348:station
a base EFaultId_AntBlockedAl
- unit/service to be degraded or faulty.
- for the-
The problem causes a cell service to fault from -thebesupplementary
degraded or faulty. text field of the alarm.
- Yes 17A Check
The the reason
problem - causes for athe-basefault from-the
station supplementary
unit/service text field of
to be degraded or the alarm.
faulty.
- Yes 17A Check the reason - for the - fault from-the supplementary text field of the alarm.
- Yes 17A Check the reason - for the Check
fault the
fromreason -the supplementary
fieldsupplementary
of the alarm. t
- Yes 17A A major fault- A major faul-
- Yes 17A Not enough P You are notOrder and in-
- Yes 17A This alarm
The is an eis-raised if the -every
packet
lostloss - ratio equals
measurement packet
or exceeds
will trigger
the configured
the alarm an
- Yes 17A threshold value Theduring
same TWAMP
profile the
again
measurement
as current
(PLR>=0).
configured
this observation
TWAMP - RTT packets
session interval
thresholdare lost
(DSCP of because
value 15 isminutes.
value, of degraded
notpacket
too close
size)tom a
- Yes 17A The RTT threbecause the values,
measurement
so that - this packets
alarm are could
scheduled
be resultlaterof sporadic
than beformi
The problem - causes for athe Check
cellfault the
fromreason
service -the
to besupplementary
for the fault
degraded from
text the
or faulty. fieldsupplementary
of the alarm. t
- Yes 17A Check - for the- fault from -
The problem causes a base station unit/service to be degraded of
the reason the supplementary text field or the alarm.
faulty.
- Yes 17A Check the reason - for the -1. fault
Check if the far end has BFD switched on. alarm.
from -the supplementary text field of the
- Yes 17A The alarm isThe commun 2. Check the- Ethernet
3. cabling and network
interface connectionsatofthe
configuration theloca
fa
LINK OAM LYes 17A On an interf The Etherne Insert athe
4. Check Link
- Ethernet
OAM loopback.
interface configuration at the loca
LINK OAM CYes 17A Always the latestThe Etherne
received 5. Insert
critical a Link
link
- eventOAM shallloopback.
be reported.
- Yes 17A Two or moreOMS can no Give unique-
- Yes 17A OMS has reje Network el- -
LINK OAM Yes 17A A loopback iNormal trafNone -
- Yes 17A This alarm i - - -
- Yes 17A The base stat - - -
Page 21
Alarm_Library
- Yes 17A This problem
The is an ex- causes a -base station- unit/service to be degraded or faulty.
- Yes 17A Check
The the reason
problem - causes for athe
-basefault from-the
station supplementary
unit/service text field of
to be degraded or the alarm.
faulty.
- Yes 17A Check the reason - for the- fault from-the supplementary text field of the alarm.
- Yes 17A A fault has o- - -
- Yes 17A -Check the reason
The Network - Elementsfor the Check
For fault
are more the
from
unable reason
-the
information supplementary
to send for alarm
the fault
see the from
events.
NMStexttroubleshooting
the
fieldsupplementary
of the alarm. mant
- Yes 17A -This Problems in- the alarm This
system Alarm inside
is- not themanually
NMS
is a spare alarm for handling late churn in the release. Please see (1) add clearable.
- Yes 17A This alarm is-with
- Interaction applicable
alarm -correlator
independent - of the value of actCategoryAlarms
server
- Yes 17A fails with critical - error. For more information - see the Alarm Correlator troublesh
- Yes 17A A transmissi- A transmissi-
- Yes 17A The Alarm
Alarm Upload D- has failedThis duealarm
Grep the
to an i-error
error logseither
with "ALARM_UPLOAD_FOR_THE
- Yes 17A in Alarm Upload - InitiatorAfter
or incorrecting
Alarm
Situation is over when - Uploader.
the problem trigger the
maintenance modeAlarm Upload. o
is switched
- Yes 17A This alarm i - This Alarm is- not manually clearable.
- Yes 17A The Ack
This alarmUpl-is generatedThis Situation
when alarm is i-over when
maintenance mode
maintenance
is activated modefor an
is switched
object. Tho
- Yes 17A Supplementary - information This fields:
Alarm If is- alarms
not manually9251 (targeted
clearable.to the Maintenance
- Yes 17A This alarm i New alarms Check status -
- Yes 17A This alarm i New alarms Check statu-
- Yes 17A 2. The "$date" The format
fault isNo theactions
local time a- stamp (GMT+/-xx:xx). For example: 201
- Yes 17A A change
Ack Upload to has
The failed
BTS doe Reset
due to an theerror
BT - either
- Yes 17A in Ack Upload - Initiator or Check
in Ackthe Uploader.
/v-
- Yes 17A -Software
the signalman is- loss
excessively Check
of synchronization
2. Check operat
attenuated that - theif the interface
interface at istheused
far-end
as ainterface
synchronizati is sw
- Yes 17A - the port at the - IKE connected
SAs and 3. Check
far
IPSec end whether
SAs
node
- cannot isthere
switched
beareestablished
active
off alarms or re-keyed.
at the far end
- Yes 17A Probable cause: PossibleThe transmission
i 4. Connect alinks - loopselected
cable and for check
clock source
whetherare thefaulty.
alarmTh d
Synchronous Yes 17A - It is not present NoneCertificate
The for TimingMonitor
Check over the
Revocation
DNS Packet.
-received
names. clock not
List could quality.be updated. New revoke
- Yes 17A This alarm i remain unknown Check to thethesize
- BTS. of the file at the Certificate Revocation L
- Yes 17A Five
7. consecuNone
RDI_CCM, priority 1 Check
1.
(lowest
Check yourthe- cabling.
priority): An RDI flag is detected in the CCM fra
- Yes 17A Example: CCM The
Note:For FSMr3/AirScale fault
transpo
level2. Check
5 prio
1. unit types, 1
thecause
-
cabling.CCM REMOTE_DEFECT_INDICATION
interface configuration
is provided at as:
the"module
remote peer. type nam
- Yes 17A For Flexi Zone TheMicro
transpoBTS,2. Check
interface the - is
configuration
provided as:at
1. Determine if this event is expected. Investigate EIF
the "interface
remote peer.
number". audit
- Yes 17A The Flexi ZoTo prevent 2. If this action - is unexpected, disable the bluetooth.
- Yes 17A -ATherequested
bluetooth The
certificate
request
config Provide
could
mode
1. Determinenotthe
set be-explicitly
to cstored inenabled
the remaining
if the bluetooth should be storage
enabled.available o
- Yes 17A - The bluetooth As aconfig
risk mmode2. Determine
1. If thisAutoFallback
action- if is unexpected,
this logic,
event which disable
automatically
is expected. the bluetooth.
Investigate enablesauditth
- Yes 17A The Flexi ZoNone 2. If this action- is unexpected,
1. Determine if this event is expected. Investigate auditdisable the bluetooth.
- Yes 17A The Flexi ZoNone 2.
1. If this action
Check the- releaseis unexpected,
notes of the disable the bluetooth.
downloaded BTS soft
- Yes 17A The internal The interna1. 2. Check
Replace the the
- release
Flexi Zone notesBTS. of the downloaded BTS soft
- Yes 17A The internal The interna2. Replace the - Flexi Zone Micro BTS.
BFD 1 down,Yes 17A The alarm isThe communi 2. If
3. Check if the
the internal - BFD supply functionality
voltage causes in the peer is switched
the alarm, check
SFP HW WAYes 17A There is an The backha 4. If the TX BIAS/TX
-
1. Determine if this event is expected. output power causes the alarm, re
- Yes 17A Note: The
Note : For eachSSH Update
access
FlexiNTS audi
Zone: Note:
to
server the
2. Check The
site
instance, SSH
is -
the NTP disabled
access
timersserverby to default.
the site
are configuration To
is
started separatelydisabled
mitigate
at theand the
by
BTS.the
risk def
a sepain
- Yes 17A alarm is raised. Flexi This
Zonethreshold
3.
Access
Check time
Point
the-isconfigured
might
not used loseto threshold
time
clear synchronization
thevalue
alarm. for theif NTP
therese a
BFD $SESSYes 17A The alarm isThe commun Check
Confirmthe BF
that - the Ethernet Synchronization master/slave
Auto-negotiaYes 17A -This
Thealarm
eNB doesi If thenot alar Note:
receive
1. CheckaThe reply Flexi
the -from
cable Zone
ToP Micro
connectivity.
Master BTS andaFlexi
within certainZone time Access
(5 se
- Yes 17A - The eNB receivesPlease referfrom 2. ToP
to
Checkstatus
Master
theof- TOP"3080:
granted configuration.
EFaultId_BtsReferenceClockMissi
message rates (sync message ra
- Yes 17A The networkNo e immediat Update
Note: Detailed the t- information about the toggling frequency
Toggling: LOYes 17A An FTM fault, None
Note: The interface numbering alarm
2. Confirm history - file,
is similar
that which
configuration
to ETHLK. can be downloaded
settings using the aB
for ssmEnabled
SyncE SSMYesT 17A Example:
Note: The DN:SYNC-1/STPG-1/STPU-1-4
SyncE
interface
Flexi is
Zone n2.3.
numbering Troubleshoot
Micro
Confirm FDD,
shall -Flexi
that beeNB with for
similar
Zone backhaul
unit 1, interface
configuration
to
MicroETHLK. provider
TDD: 4about
settings for the reaso
ssmEnab
SyncE QualitYes 17A E.g: DN:SYNC-1/STPG-1/STPU-1-4
SyncE is no 3.longer
Troubleshoot a working
- forwith unit
synchronization
Backhaul
1,interface provider
4. source. on the reason S
- Yes 17A Note: For Flexi As Zone
long as Controller,
For most the BTS - period
typesof(including
advanceat notification
least FSMr3, is a Airscale,
non-con
Page 22
Alarm_Library
Start IPsec emergency bypass by making the security g
- Yes 17A The BTS hasthe Configured
situation byisplugging
1.Check for -duplicate
resolved out
bythethecable IPv6oraddresses
administrator.configuring wrong security
configured in the
- Yes 17A During the
M-Plane I This allows
connection 2.Change
the local peer
is established or-with
delete
tofallback
continue
the identified
functioning
configuration duplicate
without
as a IPv6 disruptio
result addres
- Yes 17A of M-plane
Port valuesrecovery
Thebe
can activeaction.
LMP None
or <ItHW will be - visible until
MODULE NAME next site reset.
>-<PORT ID>.
IP Traffic Yes 17A (For E.g: LMP None or FSM-EIF1, An IP FSM-EIF2
Traffi
A specific BTS local operator account has been locked. - or FTIF-EIF1)
- Yes 17A The number No
- Plugin of failed
furtherlogin Check attempts
the va - for a BTS local operator account has exce
- Yes 17A - File SystemAs an effec1. If the failure-isifnot
Determine thistracked
event isbyexpected:
any of these whethersteps, please
a qualifi
- Yes 17A The Flexi
This alarmZoUpdate audi
will be triggered when at- least
2. Otherwise, it shall
one beprimary
treatedIPSecas a security
tunnel fails,warning.
and B
- Yes 17A As a result ofBTS failure
traffiin The
at least operator
one -primary IPSec tunnel, BTS has automatica
- Yes 17A There is rea Someone ma Security
1. Checklog- the Maintenance Module and find the faulty D
- Yes 17A RedundancyIno the case2. The redundancy -
fsipSwitchPortName=xxxx of the RAID array should
attribute-list be automa
fsipSwitchPortA
- Yes 17A The redundan In case of b) setMakeconfig-mode
sure - thatoffthe NetAct Registration Service IOR
- Yes 17A The NWI3 ada NetAct cann c) If attributes - fsnwi3NEAccountUsername and fsnwi3N
- Yes 17A The availableThere is a 3. If the alarm - is not cleared, contact your NSN represe
- Yes 17A Recovery group The (RG):
system A4.recovery
high
Alarm availability
forgroup
-a recovery
consists
services group of
(HAS)
one
implies
or
willmore
periodically
a multiple
recovery error
attemp
units
sit
- Yes 17A The MySQL
- restart The
d CORBA
Power-off If this does not
- solve the problem, there is something w
- Yes 17A - power-off. - ApplicableThis onlyisto annodes.
i - The named node is being powered off.
- Yes 17A Notice that the TheMO MO(orhas its
This sub-MOs)
is an i - can remain locked because of the depend
- Yes 17A The administThe When an MO
(re)start This isislocked,
may an
have i - been
the alarm system
initiated by anofoperator
the cluster or clears
be causedthe
- Yes 17A The whole clu
When
8. Some permissions do the cluster
This
- the alarm
is
not numeric restarted,
map to anyi- uservalidthe alarm
ID ofgroups. system clears
a RUIM user must be in the ran all alarms th
- Yes 17A 9. User ID is
The NE is tryingThe
not
In case a
uservalidac
to contact - number.
the
of problems
NetAct account
the external -
generated
2 and 3,must be
NetAct
during
a newassigned
LDAP
time-based with
NE account, at least
server replication,
in but
the the one valid
following
NE RuimR p
didscn
- Yes 17A 1. NE connects While
This toalarm
the
RuimReplicator
NetAct
NetAct
-indicates
Wrong LDAP
LDAP
serveris
- server
that experiencing
is
the overloaded
to verify
certificate
SSL isproblems
connectionthe
or shut
used password
down.
with external
information
is unsuccessful LDA
by Ro
- Yes 17A Note that,
DRBD when
is used Note
If toan
the that
SSL the
replicate
node -running
External
connection
user
datawill of
the LDAP
still
-primary
an isapplication
attempted
be
does
able not
DRBD to partition
but
support
log no
in using
(and connection
SSL
the "TLS_OR_PLAIN
between protocol
application) is made
two nodes. be
is func
- Yes 17A Currently synchronisation
The serviceThis istodown
situati
the identified
if the
- node secondary
with the primary
DRBD partition
DRBD isornot logical
func
- Yes 17A This alarm isInset caseby OMS
of Nounit actions
when r- WBTS O&M operation reply sending from
- Yes 17A The OMS send There mighUpload the i-
- Yes 17A The number Some o measu If NetAct co-
- Yes 17A Starting of aFile trans 8. If the
If theproblem
cross - mark
persists, see
(x) is the troubleshooting
present on the ntp server documeIP (i
- Yes 17A The local cl When this # a 2) -
- Yes 17A This alarm will Measuremen
not be set Normally
immediately the- after a file transfer operation fails, but on
- Yes 17A Number of cFurther co Disconnect -
- Yes 17A Alarm uploadActive ala Check the ca -
- Yes 17A The request The alarm Verify the c -
- Yes 17A Network elem The O&M me The alarm m-
- Yes 17A There was aTroubleshoo Depending on -
- Yes 17A Check the reason- for the Checkfault thefromreason
-the supplementary
fieldsupplementary
of the alarm. t
- Yes 17A Troubleshooti The file is - In NetAct8-system troubleshooting files can be found
- Yes 17A The OMS has The alarm Operator sho -
- Yes 17A Trace connec - - -
- Yes - There has beThis might Please check -
- Yes - A login atte This might Please check -
- Yes - An unused us The account Check if the-
- Yes - An user accoThe accoun Contact syst-
- Yes - There have bThis might Please check -
- Yes - There
The problem causes a base station- unit/service to be degraded or faulty.
have b
This might Please check
- Yes 17A Check the reason- for the - fault from-the supplementary text field of the alarm.
- Yes - There have bThis might Please check -
- Yes 17A This alarm i The manage In case of certificate- validation failure this alarm is canc
- Yes - A critical fa in LTE System - Libraries. -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
Page 23
Alarm_Library
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
- Yes 0.1 - - - -
Page 24
Alarm_Library
Probable Cause
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Page 25
Alarm_Library
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Page 26
Alarm_Library
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Page 27
Alarm_Library
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Page 28
Alarm_Library
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Page 29
Alarm_Library
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Page 30

Alarm Library

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Alarm Library

Caricato da

Copyright:

Formati disponibili

Alarm_Library

Alarm Code Alarmname EMS Classification Service Affected Technology Domain

Potrebbero piacerti anche