Oracle Communications Network Charging and Control. USSD Gateway Alarms Guide Release: 4_4_1

Size: px

Start display at page:

Download "Oracle Communications Network Charging and Control. USSD Gateway Alarms Guide Release: 4_4_1"

Garey Potter
5 years ago
Views:

1 Oracle Communications Network Charging and Control Release: 4_4_1 December 2011

2 Copyright Copyright 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR , Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. Page ii

3 Contents Copyright... ii Alarm Topic Description

5 Alarm Topic Description Alarm generation Alarms on each configured node are written to the syslog and are then captured by the smsalarmdaemon for entry in the SMF database. For management of these alarms, refer to the SMS Technical Guide. Severity levels This table describes the alarms severity levels. Level Abbr Description C These alarms are raised when the application has encountered an error which indicates that the system is unable to function. E These alarms indicate the application has encountered a serious problem completing a necessary task and could not complete the task. Warning W Warnings are raised to indicate the application encountered a problem completing a non-mission critical task. N s are raised to indicate that the application has completed a task successfully. Alarm format Alarms usually follow this format: Mon DD 24:MM:SS hostname process name: [ID alarmid user.severity] process(pid) SEVERITY: Alarm text with possible variables Where: Variable Mon DD 24:MM:SS hostname process name alarmid severity process PID SEVERITY Alarm text Description Month and date the alarm was logged. Time the alarm was logged in 24 hour format. Name of the machine on which the alarm was generated. Name of the process which logged the alarm. ID number of the alarm. Alarm severity. Name of the process which logged the alarm. Process ID of the process which logged the alarm. Alarm severity. Alarm text. This may include variables such as node number. Note: In some cases the entire alarm text is generated from variables. Note: Some alarms from some subsystems may have a different format. Example: This text shows an smsmaster alarm about pending update queues. Mar 30 13:34:54 prodsmp1 smsmaster: [ID user.warning] smsmaster(17833) WARNING: Pending queue now above 15 (Worst Node 317) Alarm text and variables The %d and %s symbols represent variables within the alarm text. These values are generated by the subsystem and added to the when the alarm is raised. Page 1

6 Alarm Topic Description, Continued Alarm text and variables (continued) Usually the %d is a number and the %s is text in the context of the to complete the alarm. Occasionally other % symbols are also used (for example, %u) for different variables. Further information For more information about the SMS Alarms subsystem, see the SMS Technical Guide. For more information about creating and maintaining the SMS Alarm Relay rule set, see the SMS User's Guide. Page 2

7 Alarm descriptions The following is a list of alarms generated by the. The first column is the alarm identifier and the second is the textual description. In the textual description, the string <x> is replaced by an appropriate value. Parts in square brackets are optional and may or may not appear depending on the exact nature of the alarm Starting. Starting Interface Stopped. Stopped Interface Service <x> enabled Service <x> disabled. SLEE management event has occurred of type service enabled, where <x> is the name of the service enabled. SLEE management event has occurred of type service disabled, where <x> is the name of the service disabled Ending. Call from the SLEE for all applications to clean up and exit. No Action Clears 0002 No Action No Action Clears 0004 No Action No Action 0006 Killed. SLEE exits No Action 0007 Re-reading configuration Oracle login set to <x> 0009 Gateway name set to <x> 0010 Timer interface name set to <x> 0011 CDR interface name set to <x> 0012 Overriding previous oracle login option! 0013 Overriding previous gateway name option! 0014 Overriding previous timer interface name option! SLEE calling all application to re-read their config files. No Action <x> = Oracle login No Action <x> = gateway name No Action <x> = Timer interface name No Action <x> = CDR interface name No Action More then one login argument supplied to gateway at start up, latest takes president. More then one login argument supplied to gateway at start up, latest takes president. More then one login argument supplied to gateway at start up, latest takes president. No Action No Action No Action Page 3

8 , Continued 0015 Overriding previous CDR interface name option! 1000 Failed to find timer interface! 1001 Uncaught JCORE::gen::Ex ception 1002 Uncaught SleeException! 1003 Uncaught std::length_error 1004 Uncaught std::domain_err or 1005 Uncaught std::out_of_rang e 1006 Uncaught std::invalid_argu ment 1007 Uncaught std::logic_error 1008 Uncaught std::range_error 1009 Uncaught std::overflow_err or 1010 Uncaught std::underflow_e rror 1011 Uncaught std::runtime_err or More then one login argument supplied to gateway at start up, latest takes president. Cannot find timer interface name in slee.cfg, inconsistent name, Gateway exits No Action Check timer interface name in slee.cfg None Page 4

9 , Continued 1012 Uncaught std::bad_alloc 1013 Uncaught std::bad_excepti on 1014 Uncaught std::bad_cast 1015 Uncaught std::bad_typeid 1016 Uncaught std::ios_base::fa ilure 1017 Uncaught std::exception 1018 Unknown exception caught! 1019 Failed to connect to Oracle! 1020 Failed to initialise database, status <x>[ <x>]! DB error <x> Oracle error id and description Failed to obtain gateway info, status <x>[ <x>]! DB error <x> Oracle error id and description Failed to obtain gateway id, status <x>[ <x>]! DB error <x> Oracle error id and description. Service Interface called "Gateway" has been deleted Failed to determine barring of IMSI <x> status <x>[ <x>]! DB error <x> Oracle error id and description. DB for imsi barring has been corrupted Search key required! No imsi number as search key for barring type. Page 5

10 , Continued 1024 Unknown barring result 1026 Failed to determine barring of MSISDN <x> status <x>[ <x>]! 1025 Failed to retrieve trace for <x> status <x>[ <x>]! 1026 Search key required! 1027 Unknown barring result 1028 Unknown parameter type! 1029 Unrecognised form 1100 Event type <x> with no dialogue! 1101 Unknown TCAP primitive type 1102 Unknown event type <x> received!. DB error <x> Oracle error id and description. DB for MSISDN barring has been corrupted. DB error <x> Oracle error id and description. DB for IMSItrace does not exist or has been corrupted. No MSISDNnumber as search key for barring type. <x> = lookup result The parameter type for a PA or PACUI is not an int or a number. Unknown form has been sent and unable to use it to do a lookup. The dialogue is always created before an event. If no dialogue for an event, this would imply that the dialogue has been lost, internal error on the SLEE. <x> = type name New dialogue created, so TCAP type must be TCAP_BEGIN, anything else is a protocol violation. <x> = TCAP type Third party has sent event to SLEE/gateway, which should have been sent elsewhere. <x> = type name Check configuration of macro node for the variable parts of the PA or PACUI. Page 6

11 , Continued 1103 Watchdog event? SLEE applications do not receive watchdog events, 1104 Interface end? The gateway is an application not an interface 1105 Interface kill? The gateway is an application not an interface 1106 Unknown SleeManageme ntevent type 1107 Unable to send CDR! 1108 Unable to locate SCF CDR Interface not running or dead or misconfigured Unknown service key <x> = service key 1109 SCF timeout! No response from service Interface 1110 MRDB timeout! No response from MRDB Interface 1111 Dialogue gets unknown event type 1112 Event on unknown dialogue! 1113 SCF closed with no operations! 1114 Unknown TCAP primitive type 1115 MS attempted to invoke operation Check CDR Interface is running Check slee config file for service key Check service Interface running Check MRDB process running <x> = type name Service application closed SLEE dialog without sending any INAP operation. <x> = TCAP type MS attempts to send TCAP_INVOKE when it has already sent it for the same transaction. <x> = operation error id Page 7

12 , Continued 1116 MS sent TC- RESULT-NL, treating as TC- RESULT-L! 1117 MS RESULT of <x> when no active operation! 1118 Response to PA has operation 1119 Response to PACUI has operation 1120 Unknown MS component 1121 MS sent TC-U- ERROR of id <x> error 1122 MS sent TC- REJECT of id <x> source <x> type <x> problem 1123 Invalid TCAP component type <x> from MS! 1124 Unknown TCAP component type <x> from MS! 1125 Unknown TCAP component type <x> from SCF! The mobile station has sent a TCAP component of type RESULT_NL (not last). The gateway is treating this component as RESULT last Result received without invoke being sent <x> = operation id Response to an UnstructuredSSNotifyReque st is not an UnstructuredSSNotifyResult. <x> = operation id Response to PACUI does not match request operation. <x> = operation id <x> = operation type Gateway received error from Result sent by MS <x> = invoke id Gateway received rejection from Result sent by MS <x> = invoke id Gateway received Invalid TCAP component from MS <x> = TCAP type Gateway received unknown TCAP component from MS <x> = TCAP type INAP protocol violation. Gateway received unknown TCAP component from SCF <x> = TCAP type Check network config Page 8

13 , Continued 1126 Unknown TCAP primitive type <x> from SCF! 1127 TC-INVOKE (<x>) from SCF has unknown operation 1128 Unexpected end of mobile dialogue! 1129 Unexpected end of SCF dialogue! 1130 Timer interface closed! 1131 Unexpected end of unrecognised dialogue 1132 End of unknown dialogue 1133 Failed to log statistic 1134 IMSI <x> MRDB handle <x> not found! 1135 Failed to encode Unicode character 1136 Second TC- BEGIN from MS! 1137 Invalid UTF-8 character 1138 Response to PACUI has wrong invoke id! INAP protocol violation. Gateway received unknown TCAP primitive from SCF <x> = TCAP type INAP protocol violation. Gateway received unknown operation from SCF <x> = invoke id operation No event has been sent to inform of end of mobile dialogue No event has been sent to inform of end of SCF dialogue support All Calls aborted Third party has opened a dialogue to the gateway and then closes it with out sending an event. <x> = dialogue <x> = dialogue SMS stats library is unable to log statistics <x> = MRDB Interface handle not found in slee config file. <x> = imsi & name <x> = string Received TC-BEGIN twice in same dialogue. TCAP protocol error Obtained invalid character from db. <x> = string MAP response to the MAP request, triggered by the PACUI has the wrong invoke id. Check slee config file Page 9

14 , Continued 1139 Unknown command line option 1140 Response to PA has wrong invoke id! 1141 Missing argument for <x> 1142 Unable to find 1A5 equivalent of UTF-8 character <x> 2000 User Information isn't a direct reference[ from <x>][ to <x>]! 2001 Duplicate MAP open 2002 Can't get MAP open destination 2003 Can't get MAP open origination 2004 Can't find MAP open 2005 Duplicate PUSSR 2006 TC-INVOKE has unknown operation 2007 TC-BEGIN has unknown component type Wrong command line option in starting the gateway, gateway ignores option and continues. <x> = option MAP response to the MAP request, triggered by the PA has the wrong invoke id. Wrong command line option in starting the gateway. Cannot display given character. User information in TCAP BEGIN isn t a direct reference <x> = source & destination Kills dialogue Kills dialogue Kills dialogue Kills dialogue Kills dialogue <x> = operation <x> = TCAP type warning Warning 2008 No PUSSR 2009 Unknown application context of <x>[ from <x>][ to <x>]! <x> = context, source & destination Page 10

15 , Continued 3000 MSISDN lookup failed! 3001 Unknown trans_opt 3002 Unable to construct builder! 3003 Connect to Resource when already connected! 3004 Disconnect forward connection when not connected! 3005 Unable to construct builder! 3006 Establish temporary connection when connected! 3007 Play announcement when not connected! 3008 Play announcement build failed! 3009 Prompt and Collect when not connected! 3010 Prompt and Collect build failed! 9000 <x>:internal error! MSISDN not found in DB Field in DB not 0 or 1 <x> = trans operation As a result of ETC Task released from SCF Message sent from Service Interface for a Connect to resource has already been sent Message sent from Service Interface for a Disconnect forward connection when not connected As a result of CTR Task released from SCF Message sent from Service Interface for a Establish temporary connection when already connected Message sent from Service Interface for a Play announcement when not connected IF has not been provisioned in DB Message sent from Service Interface for a Prompt and Collect when not connected IF has not been provisioned in DB Check Service Check Service Check Service Check Service Check Service Page 11

Oracle Communications Network Charging and Control. SMS Centre Alarms Guide Release: 4_4_1

Oracle Communications Network Charging and Control SMS Centre Release: 4_4_1 December 2011 Copyright Copyright 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation