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

Size: px

Start display at page:

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

Marian Willis
5 years ago
Views:

1 Oracle Communications Network Charging and Control SMS Centre 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 SMS Centre

3 Contents Copyright... ii Alarm Topic Description... 1 smsinterface... 3 notificationif... 6 SMS Centre Page iii

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 Critical C These alarms are raised when the application has encountered an error which indicates that the system is unable to function. Error 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. Notice N Notices 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 message when the alarm is raised. Continued on next page SMS Centre 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 message to complete the alarm message. 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 SMS Centre

7 smsinterface smsinterface scenarios This table lists the messages from checking the service. Alarm Text Reason Remedy The SMS Interface services does not appear to be running as expected If the SMS Interface does not appear to be running as expected check that the executable is present in the process list. Type: ps -u acs_oper You should see a row for smsinterface If not check alarms in the log file. Alarms problems To check for alarms, use tail - f<name of LOG_FILE from smscif.sh> See Configuration Section. If alarms are not getting logged, then the SMS alarm subsystem has not been properly installed. Contact your system administrator. smsinterface startup alarms The following is a list of alarms generated by smsinterface at startup. Alarm Text Reason Remedy Unable to read from configuration file No primary IP set in configuration file No user ID set in configuration file No password set in configuration file Failed to set configuration Unable to open trace log file [trace-logfile] for append Unable to write to trace log file as tracing not enabled Failed to append to file with error: [error-number] errordescription When the smsinterface configuration file is unreadable. When IP1 parameter is not present in the smsinterface configuration file. When userid parameter is not present in the configuration file. When no password parameter is present in the configuration file. When any of the above errors have prevented a complete configuration of the smsinterface. When unable to open the trace log file to append. If an attempt to write a trace message without first enabling trace messaging occurs. This is a report of any errors whilst attempting to write to the trace file. Check existence of configuration file and its read permissions. Add an IP1 parameter to the configuration file. Add a userid parameter to the configuration file. Add a password parameter to the configuration file. Modify parameters as specified. Check permissions to write to trace-log-file. Rectify specified I/O error. Continued on next page SMS Centre Page 3

8 smsinterface, Continued smsinterface at runtime alarms The following is a list of alarms generated by the smsinterface at runtime. Alarm Text Reason Remedy Can not encode LOGIN message Attempting to send LOGIN request failed MSISDN=msisdn, SMS failed (negative return status) Login failure SMS failed (unable to encode) MSISDN=msisdn, SMS failed (queue timeout) MSISDN=msisdn, SMS failed (response timeout) Login error (login timeout) MSISDN=msisdn, SMS failed (too many outstanding messages) When there is a problem applying the IA5 encode algorithm to the login message for the SMSC. When the attempt to login fails for some reason such as the encode problem mentioned above. A failure response is received from the SMSC for a SMS message previously sent. If a failure response is received from the SMSC for a LOGIN message previously sent. When a problem occurs attempting to IA5 encode an SMS message for the SMSC. When an SMS message held on the 'holding queue' has been held there beyond the user configurable queuetimeout time. When an SMS message previously sent to the SMSC does not receive a response (from the SMSC) in the user configurable timeout time. When no response from the SMSC has been received from a LOGIN message sent to the SMSC in the user configurable logintimeout time. If there are more SMS message events on the holding queue than the user configurable queuemaximum allowed. Contact Oracle support. Rectify earlier problems. Analyse problem with SMSC then contact Oracle support. Check login and password defined for SMSC. Contact Oracle support. Check the configured message-life value against the default then confirm that the SMSC is functioning correctly. Check the configured timeout value against the default then confirm that the SMSC is functioning correctly. Check the configured logintimeout value against the default then confirm that the SMSC is functioning correctly. Check the configured value of queuemaximum against the default then confirm that the SMSC is functioning correctly. smsinterface, connecting and disconnecting alarms The following is a list of alarms generated by the smsinterface at connecting and disconnecting. Alarm Text Reason Remedy Idle Timeout elapsed Connect error (response timeout) When no responses from the SMSC have been received in the user configurable idletimeout time. When no response from the SMSC has been received for a connect attempt in the user configurable connecttimeout time. Check the configured value of idle-timeout against the default then confirm that the SMSC is functioning correctly. Check the configured value of connect-timeout against the default value then confirm that the SMSC is functioning correctly. Continued on next page Page 4 SMS Centre

9 smsinterface, Continued smsinterface, connecting and disconnecting alarms (continued) Alarm Text Reason Remedy Connect error : errordescription errornumber Socket error : errordescription errornumber FCNTL error : errordescription errornumber INET error : errordescription errornumber When a connect fails, this message shows the error. An error was returned form the socket defined to connect to the SMSC. FCNTL error occurred when attempting to connect to the SMSC. INET error when attempting to connect to the SMSC. Confirm that the SMSC is functioning correctly. Check the port and IP address on which to connect to the SMSC are configured correctly. Check the port and IP address on which to connect to the SMSC are configured correctly. Check the port and IP address on which to connect to the SMSC are configured correctly. SMS Centre Page 5

10 notificationif notificationif alarms The alarms listed below can be raised by the notificationif. Number Severity Text Cause and Remedy 1000 Critical Cannot read configuration file 1001 Critical Cannot connect to ORACLE 1002 Warning Received SLEE event of unknown type 1003 Error No template for application name xxx, notification type xxx and language xxx 1004 Error Wrong number of variable parts 1005 Error Failed to send event to SMS interface xxx 1006 Error Failed to send event to XMSI wrapper xxx The notificationif was unable to read the configuration file and will exit with status 1. Check that the syntax of the configuration file is correct. The notificationif was unable to connect to the Oracle database and will exit with status 2. Check the value of the Oracle login configuration item. The notificationif received a SLEE event of a type that it does not recognise. Only management events and SLEE notification events are supported. The notificationif received a request for a template that does not exist in the database. The number of variable parts in the template does not match the number of variable parts found in the SLEE notification event The notificationif was unable to send an event to the specified smsinterface. Check the smsif configuration parameter. The notificationif was unable to send an event to the specified XMSI wrapper. Check the xmsiwrapperifname configuration parameter Error Unknown transport The notificationif received a request with an invalid transport parameter Critical Cannot be started from the command-line 1009 Critical Missing fromaddress configuration item 1010 Critical No such SMS i/f: xxx 1011 Critical No such XMSI wrapper: xxx 1012 Error No Messaging Management support configured The notificationif must be declared in SLEE.cfg and started as a SLEE interface. SMS Centre Page 6

Oracle Communications Network Charging and Control. Data Access Pack Alarms Guide Release: 4_4_1

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