RRN 06442 HANDLING OF UNIX ALARMS

HM8MYN02

Message Triggering Condition

UNIX-server Billing System sends a urgent alarm

Report Layout

   SWA-CHRG OUTP-UNIX
      ALARM-TYP = (A).....                             (B).....................
      -------------------------------------------------------------------------
         UNIX SERVER REPORTS:
         (1)
         LCEID         = (2).
         ALARMNUMBER   = (3). (4)...................................
                              (5)...................................
  REPORT REFERENCE NUMBER = 6442

Parameter Identification

Par. No. Meaning Remarks
(A) Alarm type
(B) Alarm status
(1) Control parameter Control parameter for the report
layout
(2) Alarm-LCEID Logical Control Element Identity
which REPORTS THE ALARM
(3) Alarmnumber Alarmnumber belonging to the
alarmnummer
(4) Alarmtext 1 Description of the alarm
(5) Alarmtext 2 Description of the alarm

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(4) Disk array hardware failure . . . . . . . . . . . E
(4) DETAILED BILLING . . . . . . . . . . . . . . . . . D
(4) DOR . . . . . . . . . . . . . . . . . . . . . . . D
(4) HOT BILLING BUFFER . . . . . . . . . . . . . . . . D
(4) LAN BREAKDOWN . . . . . . . . . . . . . . . . . . F
(4) NO HOT BILLING CENTER DEFINED . . . . . . . . . . A
(4) NO HOT BILLING CENTER REACHABLE . . . . . . . . . B
(4) NODE 1 OF UNIX-SERVER CLUSTER DOWN . . . . . . . . J
(4) NODE 2 OF UNIX-SERVER CLUSTER DOWN . . . . . . . . J
(4) PROCESS OF PACKAGE MY_NFS NOT STARTABLE . . . . . I
(4) PROCESS OF PACKAGE 1 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 2 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 3 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 4 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 5 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 6 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 7 NOT STARTBALE . . . . . . . . I
(4) PROCESS OF PACKAGE 8 NOT STARTBALE . . . . . . . . I
(4) RAW DETAILED BILLING . . . . . . . . . . . . . . . D
(4) RAW DOR . . . . . . . . . . . . . . . . . . . . . D
(4) RUN TIME . . . . . . . . . . . . . . . . . . . . . D
(4) SWITCHING DISABLED FOR PACKAGE MY_NFS . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 1 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 2 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 3 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 4 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 5 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 6 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 7 . . . . . . . . . G
(4) SWITCHING DISABLED FOR PACKAGE 8 . . . . . . . . . G
(4) SWITCHING DISABLED FOR UNIX-SERVER NODE 1 . . . . H
(4) SWITCHING DISABLED FOR UNIX-SERVER NODE 2 . . . . H
(4) WRONG HOT BILLING RAW DATA FORMAT . . . . . . . . C

Action Description

Action Meaning
A The operator has to define a Hot Billing Center via USBS of the UNIX-server.
B Check the hardware connection to Hot Billing Center on defects or the adesses between USBS and Hot Billing Center. In case no defects are detected inform the USBS maintenance personnel.
C In case of permanent fault condition there might be an inconsistency at the interface UNIX-server / S12. Inform the USBS maintenance personnel.
D An access to disk has failed. This alarm may have several reasons: The access has failed because of the disk quota has exceeded. An access (open, read or write) to the disk has failed because of an hardware failure. The accessing application has no permission to read data. Each alarm can massive impair the system. Alarm 1,2 und 3 are to lead of massive losses of charging data and the immediately sanctions for trouble shooting have to start. A description of the sanctions do you find in the UNIX-server Trouble Shooting Guide.
E A failure of hardware element within the disk array has occurred. An additional failure of hardware element within the disk array is leading to a breakdown of the disk array. Attention: The manual removing of one out of three disk-array fans will cause an immediate breakdown (reaction-time less than 10 minutes) of the disk- array. A description of the sanctions for trouble shooting do you find in the UNIX-server Trouble Shooting Guide.
F A hardware error has occured within the LANs between the UNIX-server and the system12. Each connection exists twice. The breakdown of the second link may lead to a complete breakdown of the communication and to lead of massive losses of call data. Occurs this alarm in connection with an alarm (no data can be transmitted from S12 to Billing Server) an immediately sanctions for trouble have to start. A description of the sanctions for trouble shooting do you find in the UNIX-server Trouble Shooting Guide.
G For the specified package switching is disabled. An attempt to switch the specified package will not be successful. The breakdown of package 1 or 2 lead to massive trouble of operation and losses of charging data. A description of the sanctions for trouble shooting do you find in the UNIX-server Trouble Shooting Guide.
H For the specified node of the UNIX-server cluster the switching is disabled. A redunant node take automatically over the work. The breakdown of another node can lead to massive trouble of operation and losses of charging data. A description of the sanctions for trouble shooting do you find in the UNIX-server Trouble Shooting Guide.
I The specified package is not started within the UNIX-server cluster. This may have several reasons: The system can not start the package because the 2. node is not aktiv or the switching for the package or nodes are blocked. The breakdown of package 1 or 2 lead to massive trouble of operation and losses of charging data. A description of the sanctions for trouble schooting do you find in the UNIX-server Trouble Shooting Guide.
J The specified node of the UNIX-server went down. All packages of the UNIX-server switched to the oppsite node. A automatically switching attempt of a package to this node is not possible and lead to breakdown of this package. The breakdown of package 1 or 2 lead to massive trouble of operation and losses of charging data. A description of the sanctions for trouble shooting do you find in the UNIX-server Trouble Shooting Guide.