oracle communications network charging and control filecap3 sms gateway page 1 alarms guide alarm...

Oracle Communications Network Charging and Control

CAP3 SMS Gateway Alarms Guide

Release: 4_4_1

December 2011

Commercial In Confidence

Page ii CAP3 SMS Gateway Alarms Guide

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 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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.


CAP3 SMS Gateway Page iii Alarms Guide

Contents

Copyright ............................................................................................................................. ii Alarm Topic Description ...................................................................................................... 1 capgw .................................................................................................................................. 3


CAP3 SMS Gateway Page 1 Alarms Guide

Alarm Topic Description

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 SMS Technical Guide.

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.

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 Description

Mon DD Month and date the alarm was logged.

24:MM:SS Time the alarm was logged in 24 hour format.

hostname Name of the machine on which the alarm was generated.

process name Name of the process which logged the alarm.

alarmID ID number of the alarm.

severity Alarm severity.

process Name of the process which logged the alarm.

PID Process ID of the process which logged the alarm.

SEVERITY Alarm severity.

Alarm text 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 953149 user.warning]

smsMaster(17833) WARNING: Pending queue now above 15 (Worst Node

317)

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

Alarm generation

Severity levels

Alarm format

Alarm text and variables

Alarm Topic Description, Continued

Page 2 CAP3 SMS Gateway Alarms Guide

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.

For more information about:

The SMS Alarms subsystem, see SMS Technical Guide

Creating and maintaining the SMS Alarm Relay rule set, see SMS User's Guide

Further information



capgw

This table defines the critical error messages for the capgw application.

Alarm Text Reason Remedy

Service disabled: CAP gateway has been disabled by the SLEE.

Contact Technical Support with details.

Uncaught

std::bad_alloc Internal error. Contact Technical Support

with details.

Uncaught std::bad_cast Internal error. Contact Technical Support with details.

Uncaught

std::bad_exception Internal error. Contact Technical Support

with details.

Uncaught

std::bad_typeid Internal error. Contact Technical Support

with details.

Uncaught

std::domain_error Internal error. Contact Technical Support

with details.

Uncaught

std::exception Internal error. Contact Technical Support

with details.

Uncaught

std::invalid_argument Internal error. Contact Technical Support

with details.

Uncaught

std::ios_base::failure Internal error. Contact Technical Support

with details.

Uncaught

std::length_error Internal error. Contact Technical Support

with details.

Uncaught

std::logic_error Internal error. Contact Technical Support

with details.

Uncaught

std::out_of_range Internal error. Contact Technical Support

with details.

Uncaught

std::overflow_error Internal error. Contact Technical Support

with details.

Uncaught

std::range_error Internal error. Contact Technical Support

with details.

Uncaught

std::runtime_error Internal error. Contact Technical Support

with details.

Uncaught

std::underflow_error Internal error. Contact Technical Support

with details.

Unknown exception

caught Internal error. Contact Technical Support

with details.


Critical errors

capgw, Continued


This table defines the error messages for the capgw application.


Dialogue already

exists for an

interaction.

This is an internal error. This SLEE dialog has already been stored - duplication dialogs are invalid.


fclose(3c): %s1%s2 The CAP gateway failed to close the trace file in '/tmp/trace_prefix'.

%s1 = error number

%s2 = trace file name

The trace file may be empty. Contact Technical Support with details.

getopt error. Status:

%d Reading the supplied command line options has resulted in an error.

%d = error status.

Restart the CAP gateway.

InitialDPSMS does not

contain a calling

party number.

The CAP_InitialDPSMS does not contain a Calling Party Number. This is a mandatory parameter.


InitialDPSMS does not

contain a destination

subscriber number.

The CAP_InitialDPSMS does not contain a Destination Subscriber Number. This is a mandatory parameter.


Initialisation failed.

Exiting. The CAP gateway failed to startup successfully.


Non-InitialDPSMS

received in

TCAP_BEGIN:

Operation/Error ID:

%d.

The CAP gateway received a TCAP_BEGIN primitive that doesn't contain a CAP_InitialDPSMS.

%d = INAP operation id


signal(3C) error: %d%s The CAP gateway failed to register this signal handler with the kernel.

%d = kernel error number

%s = signal handler value

Valid signal handler values are:

SIGTERM

SIGHUP

SIGABORT

SIGUSR1

SIGUSR2


TCAP_BEGIN received

from SMCB side TCAP_BEGIN received from SMCB - invalid call flow.


TCAP_CONTINUE received

from MSC side. TCAP_CONTINUE received from MSC - invalid call flow.


TCAP_END received from

MSC side. TCAP_END received from MSC - invalid call flow.



Errors


capgw, Continued


Errors (continued)


Unable to create

dialogue to

destination

application with

service key:

The CAP gateway failed to create a dialog to SMCB using this service key.

Verify the service key being used for SMCB is correct by checking the following line in '/IN/service_packages/SLEE/etc/SLEE.cfg':

SERVICEKEY=INTEGER service_key_specified_for_capgw SM_MO #Added by smcbScp

Unable to obtain an

instance of SLEE

Application API.

The CAP gateway failed to register with the SLEE.


Unable to open trace

file: %s1%s2 The CAP gateway failed to open the trace file in '/tmp/trace_prefix'.

%s1 = trace file name

%s2 = error number

Check the file permissions for the trace file.

Unknown event type

received: %s The CAP gateway has received a non-TCAP event that is not a SLEE management event.

%s = SLEE event name.

None. If the problem persists contact Technical Support with details.

Unknown operation

received in

TCAP_CONTINUE:

Operation/Error ID:

%d.

Invalid operation received in a TCAP_CONTINUE.

%d = INAP Operation id


This table defines the warning messages for the capgw application.


Incorrect config type:

option:%s1, expecting

type:%s2, got %s3.

Option ignored

The CAP gateway configuration is invalid. One of the configuration parameters contains an invalid type.

%s1 = path in the configuration file for the incorrect item

%s2 = configuration type expected

%s3 = configuration type supplied

Verify the configuration parameters and restart the CAP gateway.

Missing argument for

%s Missing argument for the command line option specified.

%s = command line containing the missing argument.

Modify the '/IN/service_packages/CAP3_GW/bin/capgw.sh' startup script.


Warnings

capgw, Continued


Warnings (continued)


Option value overflow:

Option:%s, Value:%d The CAP gateway configuration is invalid. One of the configuration parameters contains a value greater than the maximum permissible parameter allowed for an unsigned integer.

%s = configuration option

%d = invalid value

Verify the configuration parameters and restart the CAP gateway.

Unknown command line

option Invalid command line option entered in the capgw.sh script.

Modify the /IN/service_packages/CAP3_GW/bin/capgw.sh startup script.

Valid options are '-c config_section' where the default config file used will be 'IN/service_packages/eserv.config'

This table defines the notice messages for the capgw application.


All subsystems

stopped. The CAP gateway has stopped. No action required.

Calling IDP InnOrNI

parameter set to: %d The CAP gateway is setting the InnOrNI parameter in the calling number when creating an IDP for SMCB, where:

%d = InnOrNI parameter value.

Valid values are:

0 (InnOrNI is set)

1 (InnOrNI is not set)

Verify that this configuration setting is correct.

Calling IDP noa

parameter set to: %d The CAP gateway is using this nature of address for the calling number when creating an IDP for SMCB, where:

%d = calling number NOA.


Calling IDP plan

parameter set to: %d The CAP gateway is using this plan parameter in the calling number when creating an IDP for SMCB, where:

%d = IDP plan parameter value.


Calling IDP present

parameter set to: %d The CAP gateway is using this present parameter in the calling number when creating an IDP for SMCB, where:

%d = IDP present parameter value.



Notices


capgw, Continued


Notices (continued)


Calling IDP screening

parameter set to: %d The CAP gateway is using this screening parameter in the calling number when creating an IDP for SMCB, where:

%d = IDP screening parameter value.


capgw startup:

initialising all

subsystems.

The CAP gateway is registering with the SLEE.

No action required.

Destination SLEE

service key set to:

%d.

The CAP gateway is using this service key for SMCB, where:

%d = the capgw service key


Initialising

configuration

subsystem

The CAP gateway is reading from the configuration file.

No action required.

Non-SLEE event type

with no dialog. Type:

%s

An internal error has occurred for a non SLEE event.

%s = SLEE event name


Service enabled: %s The CAP gateway has been enabled by the SLEE.

%s = SLEE service name (capgw).

No action required.

Setting up signal

handlers. The CAP gateway is registering signal handlers with the kernel.

No action required.

SLEE: APPLICATION_END. The CAP gateway has been terminated by the SLEE.


SLEE:

APPLICATION_KILL. The CAP gateway has been terminated by the SLEE.


SLEE: Re-reading

configuration - no

effect

The CAP gateway has been instructed by the SLEE to reread its configuration file.

No action required.

SLEE: Unknown SLEE

event type: %s. The CAP gateway has received an unknown SLEE management event.

%s = SLEE event name

No action required. If the problem persists contact Technical Support.

SLEE: WatchDog event. The CAP gateway has received a watchdog event from the SLEE.

No action required.

Startup successful. The CAP gateway is running. No action required.

Tracing prefix set to:

%s The CAP gateway has tracing turned on for this prefix.

%s = the tracing prefix number.


Using configuration

file: %s The CAP gateway is reading from this configuration file on startup or when instructed to reread its configuration.

%s = the configuration file name.

No action required.


capgw, Continued


Notices (continued)


Using configuration

section %s The CAP gateway is reading from this configuration section on startup or when instructed to reread its configuration.

%s = the configuration section name.

No action required.

oracle communications network charging and control filecap3 sms gateway page 1 alarms guide alarm...

Documents