Subscriber Event Service

Subscriber Event Service
Oracle Communications Network Charging and Control
Product:
Component:
OCNCC 4.3
Subscriber Event Service
Alarms Guide
S’ware version:
Release 1.1.0
Guide version:
02.00
Release date:
December 2010
Status:
Approved
Commercial In Confidence
Copyright
Subscriber Event Service Alarms Guide, Release 1.1.0
02.00
Copyright © 2010, 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 software or related documentation 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 USA, Inc., 500 Oracle
Parkway, Redwood City, CA 94065.
This software 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 which may create a risk of personal injury. If
you use this software in dangerous applications, then you shall be responsible to
take all appropriate fail-safe, backup, redundancy, and other measures to ensure
the safe use of this software. Oracle Corporation and its affiliates disclaim any
liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.
This software 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
Subscriber Event Service
Alarms Guide
Commercial In Confidence
Contents
Copyright ............................................................................................................................. ii Alarm Topic Description ...................................................................................................... 1 SES Alarms ......................................................................................................................... 2 Subscriber Event Service
Alarms Guide
Page iii
Commercial In Confidence
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
Alarm text and
variables
This table describes the alarms severity levels.
Level
Abbr
Description
Critical
C
Error
E
Warning
W
Notice
N
These alarms are raised when the application has encountered
an error which indicates that the system is unable to function.
These alarms indicate the application has encountered a
serious problem completing a necessary task and could not
complete the task.
Warnings are raised to indicate the application encountered a
problem completing a non-mission critical task.
Notices are raised to indicate that the application has
completed a task successfully.
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.
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 (e.g.
%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.
Subscriber Event Service
Alarms Guide
Page 1
Commercial In Confidence
SES Alarms
Alarm
Severity
Text
Cause
Resolution
Service
390033
WARNING
sesTrigger(%d) WARNING:
Failed to send NoteMM
response.
390033
If problem persists, contact
support.
sesTrig
ger
390034
ERROR
slee_acs(%d) ERROR: SES
Service: no PIN in InitialDP.
390034
Contact support. Check that
only sesTrigger is sending
events to the sesService
service key.
sesTrig
ger
390035
ERROR
slee_acs(%d) ERROR: SES
Service: Illegal PIN length.
390035
Contact support. Check that
only sesTrigger is sending
events to the sesService
service key.
sesTrig
ger
390036
ERROR
slee_acs(%d) ERROR: SES
Service: Malformed PIN.
390036
Contact support. Check that
only sesTrigger is sending
events to the sesService
service key.
sesTrig
ger
390037
WARNING
slee_acs(%d) WARNING: SES
Service: Failed to find
global call plan %z .
390037
sesTrig
Check that the call plans
refered to in SES trigger rules ger
exist in the database. Correct
trigger rules or create call
plans as needed.
390038
WARNING
slee_acs(%d) WARNING: SES
Service: Failed to find
provider %z , call plan %z .
390038
Check that the call plans
sesTrig
refered to in SES trigger rules ger
exist in the database. Correct
trigger rules or create call
plans as needed.
390014
WARNING
sesTrigger(%d) WARNING:
dlclose failed: %z
390014
No action needed.
sesTrig
ger
Continued on next page
Subscriber Event Service
Alarms Guide
Page 2
Commercial In Confidence
SES Alarms, Continued
•
Alarm
Severity
Text
Cause
Resolution
Service
390015
ERROR
sesTrigger(%d) ERROR: dlopen
%z failed: %z
390015
Check (1) that the
configuration has the correct
shared library file name, (2)
that the file exists and is
readable, (3) that the
directory is in
LD_LIBRARY_PATH.
sesTrig
ger
390016
ERROR
sesTrigger(%d) ERROR: dlsym
%z %z failed: %z
390016
Check configuration. Refer to
application expert or support.
sesTrig
ger
390017
WARNING
sesTrigger(%d) WARNING: IDP
has no IMSI
390017
This code is not intended for
customer usage. Contact
support.
sesTrig
ger
390018
WARNING
sesTrigger(%d) WARNING: IDP
has no calling party number
390018
This code is not intended for
customer usage. Contact
support.
sesTrig
ger
390019
WARNING
sesTrigger(%d) WARNING: No
trigger rule for %z .
390019
Refer to application expert or
support. Update configuration
to match packet.
sesTrig
ger
390020
ERROR
sesTrigger(%d) ERROR: Failed
to create dialog to slee_acs.
390020
Check that slee_acs is running. sesTrig
Contact support.
ger
390021
WARNING
sesTrigger(%d) WARNING:
Received event with no
components
390021
Refer to network expert or
support. Check that only
desired network traffic is
delivered to sesTrigger.
sesTrig
ger
Continued on next page
Subscriber Event Service
Alarms Guide
Page 3
Commercial In Confidence
SES Alarms, Continued
•
Alarm
Severity
Text
Cause
Resolution
Service
390040
ERROR
slee_acs(%d) ERROR: Error
initialising
ses::InRoamerMessagesSelectio
n: %z
390040
Check
slee_ac
SES.sesMacroNodes.InRoamerMessa s
gesSelection section in config
file
390041
ERROR
slee_acs(%d) ERROR:
ses::InboundMessageSelection:
Error extracting general
messages: %z
390041
Check status of database and
contact support.
slee_ac
s
390042
ERROR
slee_acs(%d) ERROR:
ses::InRoamerMessageSelection
: Error extracting specific
messages: %z
390042
Check status of database and
contact support.
slee_ac
s
390043
ERROR
slee_acs(%d) ERROR:
ses::InRoamerMessageSelection
: error: %z
390043
Contact support.
slee_ac
s
390044
ERROR
slee_acs(%d) ERROR: Error
initialising
ses::OutRoamerContactCheck:
%z
390044
slee_ac
Check
SES.sesMacroNodes.OutRoamerMess s
agesSelection section in config
file
390045
ERROR
slee_acs(%d) ERROR: Error
initialising
ses::OutRoamerMessagesSelecti
on: %z
390045
Check
slee_ac
SES.sesMacroNodes.OutRoamerCont s
actCheck section in config file
390046
ERROR
slee_acs(%d) ERROR:
ses::OutRoamerMessageSelectio
n: Error extracting general
messages: %z
390046
Check status of database and
contact support.
slee_ac
s
Continued on next page
Subscriber Event Service
Page 4
Alarms Guide
Commercial In Confidence
SES Alarms, Continued
•
Alarm
Severity
Text
Cause
Resolution
Service
390047
ERROR
slee_acs(%d) ERROR:
ses::OutRoamerMessageSelectio
n: Error extracting specific
messages: %z
390047
Check status of database and
contact support.
slee_ac
s
390048
ERROR
slee_acs(%d) ERROR:
ses::OutRoamerMessageSelectio
n: error: %z
390048
Contact support.
slee_ac
s
Subscriber Event Service
Alarms Guide
Page 5
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising