BEAWebLogic Network GatekeeperBEA WebLogic Network Gatekeeper Handling Alarms

BEAWebLogic Network Gatekeeper™

Handling Alarms

Version 2.2 Revised: May 15, 2006

CopyrightCopyright © 1995-2006 BEA Systems, Inc. All Rights Reserved.

Restricted Rights LegendThis software is protected by copyright, and may be protected by patent laws. No copying or other use of this software is permitted unless you have entered into a license agreement with BEA authorizing such use. This document is protected by copyright and may not be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form, in whole or in part, without prior consent, in writing, from BEA Systems, Inc.

Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA SYSTEMS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE DOCUMENT IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.

Trademarks and Service MarksCopyright © 1995-2006 BEA Systems, Inc. All Rights Reserved. BEA, BEA JRockit, BEA WebLogic Portal, BEA WebLogic Server, BEA WebLogic Workshop, Built on BEA, Jolt, JoltBeans, SteelThread, Top End, Tuxedo, and WebLogic are registered trademarks of BEA Systems, Inc. BEA AquaLogic, BEA AquaLogic Data Services Platform, BEA AquaLogic Enterprise Security, BEA AquaLogic Interaction, BEA AquaLogic Interaction Analytics, BEA AquaLogic Interaction Collaboration, BEA AquaLogic Interaction Content Services, BEA AquaLogic Interaction Data Services, BEA AquaLogic Interaction Integration Services, BEA AquaLogic Interaction Process, BEA AquaLogic Interaction Publisher, BEA AquaLogic Interaction Studio, BEA AquaLogic Service Bus, BEA AquaLogic Service Registry, BEA Builder, BEA Campaign Manager for WebLogic, BEA eLink, BEA Kodo, BEA Liquid Data for WebLogic, BEA Manager, BEA MessageQ, BEA SALT, BEA Service Architecture Leveraging Tuxedo, BEA WebLogic Commerce Server, BEA WebLogic Communications Platform, BEA WebLogic Enterprise, BEA WebLogic Enterprise Platform, BEA WebLogic Enterprise Security, BEA WebLogic Express, BEA WebLogic Integration, BEA WebLogic Java Adapter for Mainframe, BEA WebLogic JDriver, BEA WebLogic Log Central, BEA WebLogic Mobility Server, BEA WebLogic Network Gatekeeper, BEA WebLogic Personalization Server, BEA WebLogic Personal Messaging API, BEA WebLogic Platform, BEA WebLogic Portlets for Groupware Integration, BEA WebLogic Real Time, BEA WebLogic RFID Compliance Express, BEA WebLogic RFID Edge Server, BEA WebLogic RFID Enterprise Server, BEA WebLogic Server Process Edition, BEA WebLogic SIP Server, BEA WebLogic WorkGroup Edition, BEA Workshop for WebLogic Platform, BEA Workshop JSP, BEA Workshop JSP Editor, BEA Workshop Struts, BEA Workshop Studio, Dev2Dev, Liquid Computing, and Think Liquid are trademarks of BEA Systems, Inc. Accelerated Knowledge Transfer, AKT, BEA Mission Critical Support, BEA Mission Critical Support Continuum, and BEA SOA Self Assessment are service marks of BEA Systems, Inc.

All other names and marks are property of their respective owners.

BEA WebLogic Network Gatekeeper Handling Alarms i

Contents:

1. Alarm and Fault HandlingInterpreting alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Clear alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Alarm numbering overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

SLEE and SLEE utility alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

ESPA service capability alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Protocol plug-in alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

SESPA alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Resolving Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1001 SLEE: Service deactivated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1002 SLEE: Service data storage failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

1003 SLEE: Service deactivation exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

1004 SLEE: Service stop exception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

1005 SLEE: Database replication connect failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

1006 SLEE: Database replication files differ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

1007 SLEE: Database replication file names differ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

1008 SLEE: Database replication status check error . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

1009 SLEE: Database replication file too large. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

1010 SLEE: Database replication files explicitly reset . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

1011 SLEE: Faulty username-password combination . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

1012 SLEE: CORBA thread-pool overloaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

1013 SLEE: CORBA thread-pool overload - alarm ceased. . . . . . . . . . . . . . . . . . . . . . . 1-18

ii BEA WebLogic Network Gatekeeper Handling Alarms

1014 SLEE: Un-reachable listener object detected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

1015 SLEE: Un-reachable listener object removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

1016 SLEE: SLEE task could not be scheduled due to full task queue . . . . . . . . . . . . . 1-21

1017 SLEE: UNHANDLED exception raised by a SLEE task . . . . . . . . . . . . . . . . . . . 1-22

1018 SLEE: Un-reachable plug-in object removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

1019 SLEE: SLEE task pool empty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

1020 SLEE: SLEE task pool empty - alarm ceased . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

1021 SLEE: Duplicate SLEE timer reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26

1022 SLEE: Database table replaced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

1023 SLEE: Database replication error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

1024 SLEE: SLEE start-up in progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29

1025 SLEE: SLEE graceful shutdown in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

1026 SLEE: Priority task manager warning level reached . . . . . . . . . . . . . . . . . . . . . . . 1-31

1027 SLEE: OAM runtime exception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32

1028 SLEE: Product expiring alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33

1029 SLEE: Product expired alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34

1030 SLEE: Transaction limit violated by transaction group Call . . . . . . . . . . . . . . . . . 1-35

1031 SLEE: Transaction limit violated by transaction group Messaging. . . . . . . . . . . . 1-36

1032 SLEE: Transaction limit violated by transaction group Mobility . . . . . . . . . . . . . 1-37

1033 SLEE: Transaction limit violated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38

1040 SLEE global counter: Counter handler creation failed . . . . . . . . . . . . . . . . . . . . . 1-39

1041 SLEE global counter: Periodic cleanup set-up at counter handler creation failed. 1-40

1090 SLEE: CORBA warning received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41

1091 SLEE: CORBA alarm received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42

1095 SLEE: Database master changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43

1096 SLEE: Database connection failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44

1097 SLEE: Database low on disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45

1098 SLEE: Database critically low on disk space, database engine stopped . . . . . . . . 1-46

BEA WebLogic Network Gatekeeper Handling Alarms iii

1099 SLEE: Database partition critically low on disk space, database engine stop failed1-47

1100 SLEE charging: Charging data storage failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48

1101 SLEE charging: Charging service initialization failed . . . . . . . . . . . . . . . . . . . . . . 1-49

1102 SLEE charging: Charging table creation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50

1452 Plug-in manager: Request rate could not be re configured according to new node SLA1-51

1500 SLEE SCS manager: No SCS found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52

1501 SLEE SCS manager: SCS overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53

1600 SLEE EDR service: Listener execution time exceeded . . . . . . . . . . . . . . . . . . . . . 1-54

1601 SLEE EDR service: EDR listener removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55

1700 SLEE backup: Snapshot backup executed OK. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56

1701 SLEE backup: Unable to perform backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57

1702 SLEE backup: Un-handled error during backup . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

1703 SLEE backup: Unable to create master database connection. . . . . . . . . . . . . . . . . 1-59

1704 SLEE backup: Unable to insert temporary data into table . . . . . . . . . . . . . . . . . . . 1-60

1705 SLEE backup: Backup is performed on non-replicated system . . . . . . . . . . . . . . . 1-61

2101 ESPA messaging: Incoming message storage failed . . . . . . . . . . . . . . . . . . . . . . . 1-62

2102 ESPA messaging: No incoming destination address . . . . . . . . . . . . . . . . . . . . . . . 1-63

2104 ESPA messaging: Plug-in not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64

2107 ESPA messaging: Charging data storage failed . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65

2108 ESPA messaging: Status update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66

2110 ESPA messaging: No outgoing originating address. . . . . . . . . . . . . . . . . . . . . . . . 1-67

2111 ESPA messaging: No outgoing destination address. . . . . . . . . . . . . . . . . . . . . . . . 1-68

2112 ESPA messaging: Message not found in database . . . . . . . . . . . . . . . . . . . . . . . . . 1-69

2113 ESPA messaging: Message status update failed. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70

2114 ESPA messaging: Mailbox not found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71

2115ESPA messaging: Mailbox existence verification failed. . . . . . . . . . . . . . . . . . . . . 1-72

2118 ESPA messaging: Plug-ins severely overloaded . . . . . . . . . . . . . . . . . . . . . . . . . . 1-73

iv BEA WebLogic Network Gatekeeper Handling Alarms

2122 ESPA messaging: Incoming message without ID . . . . . . . . . . . . . . . . . . . . . . . . . 1-74

2127 ESPA messaging: Mailbox closed due to inactivity . . . . . . . . . . . . . . . . . . . . . . . 1-75

2128 ESPA messaging: Unexpected error message received . . . . . . . . . . . . . . . . . . . . . 1-76

2129 ESPA messaging: Failed to make notification callback. . . . . . . . . . . . . . . . . . . . . 1-77

2140 ESPA messaging: Invalid destination address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78




2208 ESPA call control: Database connection failed . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82

2213 ESPA call control: Plug-in not found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83

2214 ESPA call control: Plug-ins severely overloaded . . . . . . . . . . . . . . . . . . . . . . . . . 1-84

2216 ESPA call control: routeReq timeout detected. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85

2217 ESPA call control: release call timeout detected . . . . . . . . . . . . . . . . . . . . . . . . . . 1-86

2218 ESPA call control: Application supervision timeout detected . . . . . . . . . . . . . . . . 1-87

2219 ESPA call control: Failed to setup Network Initiated Call Handler Service . . . . . 1-88

2220 ESPA call control: Failed to notify application about call event . . . . . . . . . . . . . . 1-89

2300 ESPA user location: Plug-ins severely overloaded . . . . . . . . . . . . . . . . . . . . . . . . 1-90

2301 ESPA user location: Plug-in not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91

2302 ESPA user location: Charging data storage failed . . . . . . . . . . . . . . . . . . . . . . . . . 1-92

2309 ESPA user location: Periodic location report delivery failed . . . . . . . . . . . . . . . . 1-93

2400 ESPA user status: Plug-ins severely overloaded . . . . . . . . . . . . . . . . . . . . . . . . . . 1-94

2401 ESPA user status: Plug-in not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-95

2402 ESPA user status: Charging data storage failed . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-96

2502 ESPA charging: Plug-ins severely overloaded. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-97

2503 ESPA charging: Plug-in not found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-98

2602 ESPA user interaction: Plug-ins severely overloaded . . . . . . . . . . . . . . . . . . . . . . 1-99

2603 ESPA user interaction: Plug-in not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-100

2605 ESPA user interaction: Found no matching request or notification. . . . . . . . . . . 1-101

BEA WebLogic Network Gatekeeper Handling Alarms v

2606 ESPA user interaction: Failed to report notification. . . . . . . . . . . . . . . . . . . . . . . 1-102

2607 ESPA user interaction: Failed to log charging info . . . . . . . . . . . . . . . . . . . . . . . 1-103

2608 ESPA user interaction: Delete old request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-104

2609 ESPA user interaction: Message with no destination address . . . . . . . . . . . . . . . 1-105

2702 ESPA subscriber profile: Plug-ins severely overloaded. . . . . . . . . . . . . . . . . . . . 1-106

2703 ESPA subscriber profile: Plug-in not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-107

2800 Network initiated call handler: Failed to register listener . . . . . . . . . . . . . . . . . . 1-108

2801 Network initiated call handler: No call control plug-in found . . . . . . . . . . . . . . . 1-109

2802 Network initiated call handler: No service registered . . . . . . . . . . . . . . . . . . . . . 1-110

2803 Network initiated call handler: No enabled notification for event . . . . . . . . . . . . 1-111

2804 Network initiated call handler: No associated call . . . . . . . . . . . . . . . . . . . . . . . . 1-112

2805 Network initiated call handler: Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-113

2806 Network initiated call handler: Unknown error . . . . . . . . . . . . . . . . . . . . . . . . . . 1-114

2807 Network initiated call handler: Suspend error . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-115

3001 Policy service: Parsing of retraction rule file failed . . . . . . . . . . . . . . . . . . . . . . . 1-116

3002 Policy service: Parsing of service-specific rule file failed . . . . . . . . . . . . . . . . . . 1-117

3003 Policy service: Alarm raised from policy rule . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-118

3004 Policy service: Parsing of service-specific rule file failed at load time . . . . . . . . 1-119

3005 Policy service: Denial of service request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-120

3006 Policy service: Runtime exception in policy rule . . . . . . . . . . . . . . . . . . . . . . . . . 1-121

3007 Policy service: Service Provider level request rate limit has reached warning level . . .1-122

3008 Policy service: Service Provider level request rate limit has been reached . . . . . 1-123

3009 Policy service: Application level request rate limit has reached warning level . . 1-124

3010 Policy service: Application level request rate limit has been reached . . . . . . . . . 1-125

3100 Policy service: Total request rate warning level reached . . . . . . . . . . . . . . . . . . . 1-126

3110 Policy service: Total request rate exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-127

3200 Policy service: Service provider request rate warning level reached . . . . . . . . . . 1-128

vi BEA WebLogic Network Gatekeeper Handling Alarms

3210 Policy service: Service provider request rate exceeded . . . . . . . . . . . . . . . . . . . . 1-129

3300 Policy service: No valid global contract in the Total traffic SLA . . . . . . . . . . . . 1-130

3310 Policy service: No node contract in the Service Provider traffic SLA. . . . . . . . . 1-131

5401 Plug-in messaging-SMPP: Plug-in registration failed . . . . . . . . . . . . . . . . . . . . . 1-132

5403 Plug-in messaging-SMPP: Message sending failed . . . . . . . . . . . . . . . . . . . . . . . 1-133

5404 Plug-in messaging-SMPP: Plug-in removal failed. . . . . . . . . . . . . . . . . . . . . . . . 1-134

5405 Plug-in messaging-SMPP: Listener notification failed . . . . . . . . . . . . . . . . . . . . 1-135

5409 Plug-in messaging-SMPP: SMSC transmitter connection established . . . . . . . . 1-136

5410 Plug-in messaging-SMPP: SMSC transmitter reconnect procedure timeout. . . . 1-137

5411 Plug-in messaging-SMPP: SMSC transmitter reconnect attempt failed . . . . . . . 1-138

5412 Plug-in messaging-SMPP: SMSC receiver connection lost. . . . . . . . . . . . . . . . . 1-139

5413 Plug-in messaging-SMPP: SMSC receiver connection established. . . . . . . . . . . 1-140

5414 Plug-in messaging-SMPP: SMSC receiver reconnect procedure timeout . . . . . . 1-141

5415 Plug-in messaging-SMPP: SMSC receiver reconnect attempt failed . . . . . . . . . 1-142

5416 Plug-in messaging-SMPP: Storing message data in database failed . . . . . . . . . . 1-143

5417 Plug-in messaging-SMPP: Updating message delivery status in database failed 1-144

5418 Plug-in messaging-SMPP: Message delivery processing in database failed . . . . 1-145

5420 Plug-in messaging-SMPP: No listener available for incoming message . . . . . . . 1-146

5421 Plug-in messaging-SMPP: SMSC transmitter connection lost . . . . . . . . . . . . . . 1-147

5602 Plug-in user status-MPP: Failed to create provider . . . . . . . . . . . . . . . . . . . . . . . 1-148

5603 Plug-in user status-MPP: Registration failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-149

5605 Plug-in user status-MPP: Removal failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-150

5606 Plug-in user status-MPP: Connection established . . . . . . . . . . . . . . . . . . . . . . . . 1-151

5607 Plug-in user status-MPP: Re-connection procedure ended . . . . . . . . . . . . . . . . . 1-152

5700 Plug-in messaging-CIMD: SMSC login failed . . . . . . . . . . . . . . . . . . . . . . . . . . 1-153

5701 Plug-in messaging-CIMD: SMSC login succeeded . . . . . . . . . . . . . . . . . . . . . . . 1-154

5702 Plug-in messaging-CIMD: SMS delivery failed . . . . . . . . . . . . . . . . . . . . . . . . . 1-155

5703 Plug-in messaging-CIMD: SMSC connection failed . . . . . . . . . . . . . . . . . . . . . . 1-156

BEA WebLogic Network Gatekeeper Handling Alarms vii

5704 Plug-in messaging-CIMD: Login request sending failed . . . . . . . . . . . . . . . . . . . 1-157

5705 Plug-in messaging-CIMD: Plug-in not connected to SMSC . . . . . . . . . . . . . . . . 1-158

5706 Plug-in messaging-CIMD: Plug-in connected to SMSC . . . . . . . . . . . . . . . . . . . 1-159

5707 Plug-in messaging-CIMD: Exception when notifying listener . . . . . . . . . . . . . . 1-160

5708 Plug-in messaging-CIMD: Exception when adding data to database . . . . . . . . . 1-161

5710 Plug-in messaging-CIMD: CIMD protocol error in submit response . . . . . . . . . 1-162

5801 Plug-in messaging-MM7: Unable to create SOAP sender . . . . . . . . . . . . . . . . . . 1-163

5802 Plug-in messaging-MM7: No stored message ID matched message ID in received delivery report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-164

5803 Plug-in messaging-MM7: No message ID contained in received delivery report 1-165

5804 Plug-in messaging-MM7: Plug-in unable to parse delivery report request . . . . . 1-166

5805 Plug-in messaging-MM7: Plug-in unable to parse delivery request . . . . . . . . . . 1-167

5806 Plug-in messaging-MM7: No recipient address found in deliver request . . . . . . 1-168

5807 Plug-in messaging-MM7: Unrecognized address type in deliver request . . . . . . 1-169

5808 Plug-in messaging-MM7: SOAP request parsing error . . . . . . . . . . . . . . . . . . . . 1-170

5809 Plug-in messaging-MM7: SOAP request handling error . . . . . . . . . . . . . . . . . . . 1-171

5810 Plug-in messaging-MM7: Retrieving simple content data from SOAP message failed1-172

5811 Plug-in messaging-MM7: Retrieving multiparty content data from SOAP message failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-173

5812 Plug-in messaging-MM7: SOAP request sending failed . . . . . . . . . . . . . . . . . . . 1-174

5813 Plug-in messaging-MM7: Listener notification failed . . . . . . . . . . . . . . . . . . . . . 1-175

5814 Plug-in messaging-MM7: MM7 server connection lost . . . . . . . . . . . . . . . . . . . . 1-176

5815 Plug-in messaging-MM7: MM7 server connection established. . . . . . . . . . . . . . 1-177

5900 Plug-in location-MLP: Reading or writing configuration data failed . . . . . . . . . 1-178

5901 Plug-in location-MLP: Plug-in registration failed . . . . . . . . . . . . . . . . . . . . . . . . 1-179

5902 Plug-in location-MLP: Request sending error . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-180

5903 Plug-in location-MLP: Response retrieving error . . . . . . . . . . . . . . . . . . . . . . . . 1-181

viii BEA WebLogic Network Gatekeeper Handling Alarms

6100 Plug-in message sender-PAP: Heartbeat lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-182

6101 Plug-in message sender-PAP: Heartbeat lost - alarm ceased. . . . . . . . . . . . . . . . 1-183

6102 Plug-in message sender-PAP: Failed to get SC . . . . . . . . . . . . . . . . . . . . . . . . . . 1-184

6103 Plug-in message sender-PAP: Status notification timeout . . . . . . . . . . . . . . . . . . 1-185

7001 SLEE statistics: Failed to store statistics data . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-186

11100 ESPA access: User locked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-187

11130 ESPA access: Wrong application ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-188

11131 ESPA access: Wrong application password. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-189

11132 ESPA access: Locked application log in attempt. . . . . . . . . . . . . . . . . . . . . . . . 1-190

11133 ESPA access: Non active application account . . . . . . . . . . . . . . . . . . . . . . . . . . 1-191

11200 ESPA Message Sender: Failed to log charging info . . . . . . . . . . . . . . . . . . . . . 1-192

11201 ESPA Message Sender: Request timeout occurred . . . . . . . . . . . . . . . . . . . . . . 1-193

11202 ESPA Message Sender: Request timeout occurred . . . . . . . . . . . . . . . . . . . . . . 1-194

11203 ESPA Message Sender: Request caused exception . . . . . . . . . . . . . . . . . . . . . . 1-195

11204 ESPA Message Sender: Request caused exception . . . . . . . . . . . . . . . . . . . . . . 1-196

11205 ESPA Message Sender: Could not access persistent storage. . . . . . . . . . . . . . . 1-197

12100 SESPA access: ESPA session logged out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-198

12101 SESPA access: ESPA session error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-199

12200 SESPA user location: Application error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-200

12300 SESPA messaging: Enable Parlay X incoming message notification failed . . . 1-201

12301 SESPA messaging: Parlay X incoming message notification failed . . . . . . . . . 1-202

12302 SESPA messaging: Parlay X incoming message notification destroyed . . . . . . 1-203

12400 SESPA messaging UI: Application error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-204

12401 SESPA messaging UI: Notification error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-205

12500 SESPA user status: Application error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-206

12600 SESPA call UI: Application error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-207

12800 SESPA call control: Notification error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-208

12801 SESPA call control: Application error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-209

BEA WebLogic Network Gatekeeper Handling Alarms ix

12801 SESPA call control: Parlay X network initiated call notification destroyed . . . 1-210

12900 SESPA subscriber profile: Application error . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-211

13000 SESPA Message sender: Request timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-212

13001 SESPA Message sender: Request timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-213

13002 SESPA Message sender: Unexpected exception . . . . . . . . . . . . . . . . . . . . . . . . 1-214

13003 SESPA Message sender: Unexpected exception . . . . . . . . . . . . . . . . . . . . . . . . 1-215

14000 Legacy SMPP: Faulty application login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-216

14001 Legacy SMPP: Negative response for delivery report . . . . . . . . . . . . . . . . . . . . 1-217

14002 Legacy SMPP: Negative response for delivery report . . . . . . . . . . . . . . . . . . . . 1-218

14003 Legacy SMPP: Message delivery failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-219

14004 Legacy SMPP: Too many requests in progress . . . . . . . . . . . . . . . . . . . . . . . . . 1-220

14100 Legacy MM7: Could not login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-221

14101 Legacy MM7: Invalid account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-222

14200 Legacy PAP: Message response timed out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-223

14201 Legacy PAP: Authentication failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-224

14202 Legacy PAP: Push ID mismatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-225

22000 Plug-in OSA access: OSA gateway authentication failed . . . . . . . . . . . . . . . . . 1-226

22001 Plug-in OSA access: OSA gateway service manager unreachable . . . . . . . . . . 1-227

22002 Plug-in OSA access: OSA gateway unreachable . . . . . . . . . . . . . . . . . . . . . . . . 1-228

22003 Plug-in OSA access: No mapping available. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-229

22004 Plug-in OSA access: Internal error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-230

22101 Plug-in generic UI-HOSA: Message delivery failed - undefined. . . . . . . . . . . . 1-231

22102 Plug-in generic UI-HOSA: Message delivery failed - illegal info . . . . . . . . . . . 1-232

22103 Plug-in generic UI-HOSA: Message delivery failed - ID not found . . . . . . . . . 1-233

22104 Plug-in generic UI-HOSA: Message delivery failed - resource unavailable . . . 1-234

22105 Plug-in generic UI-HOSA: Message delivery failed - illegal range. . . . . . . . . . 1-235

22106 Plug-in generic UI-HOSA: Message delivery failed - improper user response . 1-236

22107 Plug-in generic UI-HOSA: Message delivery failed - abandon . . . . . . . . . . . . . 1-237

x BEA WebLogic Network Gatekeeper Handling Alarms

22108 Plug-in generic UI-HOSA: Message delivery failed - no operation active . . . . 1-238

22109 Plug-in generic UI-HOSA: Message delivery failed - no space available . . . . . 1-239

22110 Plug-in generic UI-HOSA: Message delivery failed - resource timeout . . . . . . 1-240

22200 Plug-in OSA MPCC: Internal callback error . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-241

22201 Plug-in OSA MPCC: OSA error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-242

22400 Plug-in OSA call UI: Internal callback error . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-243

22401 Plug-in OSA call UI: OSA error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-244

95001 Subscription handler: Subscriber profile plug-in retrieval failed. . . . . . . . . . . . 1-245

95002 Subscription handler: Subscriber profile retrieval failed . . . . . . . . . . . . . . . . . . 1-246

95003 Subscription handler: Exception received when trying to write subscription data . . . 1-247

95004 Subscription handler: Writing subscription data failed . . . . . . . . . . . . . . . . . . . 1-248

95005 Subscription handler: Exception received when trying to read subscription data1-249

95006 Subscription handler: Exception received when verifying a subscription . . . . . 1-250

95007 Subscription handler: Reading subscription data failed. . . . . . . . . . . . . . . . . . . 1-251

A. References

BEA WebLogic Network Gatekeeper Handling Alarms 1-1

C H A P T E R 1

Alarm and Fault Handling

This document enumerates the types of alarms that may be generated in the course of running WebLogic Network Gatekeeper and gives the recommended steps to resolve them.

“Interpreting alarms” on page 1-2

“Clear alarms” on page 1-2

“Alarm numbering overview” on page 1-3

“Resolving Alarms” on page 1-6

Note: There is a one-to-one correspondence between WebLogic Network Gatekeeper’s alarms and the defined SNMP traps. To view the MIB directly, point your MIB browser to the file Mm-bea-wlng-mib available in the wlng_integ directory of the Network Gatekeeper’s distribution as part of the wlng22_integ.zip file. WebLogic Network Gatekeeper does not provide a MIB browser, but most vendors of SNMP utilities do.

Alarm and Fau l t Hand l ing

1-2 BEA WebLogic Network Gatekeeper Handling Alarms

Interpreting alarmsAn alarm in the alarm list provides the following types of information:

Clear alarmsSome alarms have clear alarms indicating that the error condition that caused the initial alarm is no longer operative: that is, the situation has gone back to normal. The set of alarms/clear alarms is as follows:

Information Description

Source The name of the SLEE service name (software module) that raised the alarm and the IP address of the SLEE the service is installed in.

Severity The alarm’s severity level. One of the following:1 - warning2 - minor3 - major4 - critical

Identifier The alarm type through a number and heading.

Info Information provided by the software module that raised the alarm.

Timestamp The time and date the alarm was raised.

Type Alarm

Alarm:

Clear alarm:

1012 SLEE: CORBA thread-pool overloaded

1013 SLEE: CORBA thread-pool overload - alarm ceased

Alarm:

Clear alarm:

1019 SLEE: SLEE task pool empty

1020 SLEE: SLEE task pool empty - alarm ceased

Alarm number ing overv i ew


Alarm numbering overviewAlarm numbering is grouped by the module involved in raising the alarm, as follows:

SLEE and SLEE utility alarms1000-1099 SLEE

1100-1149 SLEE charging

1150-1199 Web server manager

Alarm:

Clear alarm:

5408 Plug-in messaging-SMPP: SMSC transmitter connection lost

5409 Plug-in messaging-SMPP: SMSC transmitter reconnected

Alarm:

Clear alarm:

5411 Plug-in messaging-SMPP: SMSC transmitter reconnect attempt failed

5409 Plug-in messaging-SMPP: SMSC transmitter reconnected

Alarm:

Clear alarm:

5412 Plug-in messaging-SMPP: SMSC receiver connection lost

5413 Plug-in messaging-SMPP: SMSC receiver reconnected

Alarm:

Clear alarm:

5415 Plug-in messaging-SMPP: SMSC receiver reconnect attempt failed

5413 Plug-in messaging-SMPP: SMSC receiver reconnected

Alarm:

Clear alarm:

5700 Plug-in messaging-CIMD: SMSC login failed

5701 Plug-in messaging-CIMD: SMSC login succeeded

Alarm:

Clear alarm:

5705 Plug-in messaging-CIMD: Plug-in not connected to SMSC

5706 Plug-in messaging-CIMD: Plug-in connected to SMSC

Alarm:

Clear alarm:

6100 Plug-in message sender-PAP: Heartbeat lost

6101 Plug-in message sender-PAP: Heartbeat established

Type Alarm



1200-1249 Servlet engine manager

1450-1499 Plug-in manager

1500-1549 SCS manager

1600-1649 SCS manager

3000-3099 Policy service

95000-95099 Subscription handler

ESPA service capability alarms11100-11199 ESPA access

2100-2199 ESPA messaging

2200-2299 ESPA call control

2300-2399 ESPA location

2400-2499 ESPA user status

2500-2599 ESPA charging

2600-2699 ESPA user interaction

2700-2799 Subscriber profile

2800-2899 Network initiated call handler

11200-11299 Message sender

Protocol plug-in alarms5400-5499 Protocol plug-in messaging/SMPP

5500-5599 Protocol plug-in user location/MPP

5600-5699 Protocol plug-in user status/MPP

5700-5799 Protocol plug-in messaging/CIMD

5800-5899 Protocol plug-in messaging/MM7

5900-5999 Protocol plug-in location/MLP

6100-6199 Protocol plug-in message sender/PAP

22000-22099 Protocol plug-in OSA access

Alarm number ing overv i ew


22200-22299 Protocol plug-in OSA MPCC

22400-22499 Protocol plug-in OSA call UI

SESPA alarms12100-12199 SESPA access

12200-12299 SESPA user location

12300-12399 SESPA messaging

12400-12499 SESPA messaging UI

12500-12599 SESPA user status

12600-12699 SESPA call UI

12800-12899 SESPA call control

12900-12999 SESPA subscriber profile

13000-13099 SESPA message sender

14000-14099 Legacy SMPP

14100-14199 Legacy MM7

14200-14299 Legacy PAP



Resolving AlarmsThe following sections describe specific alarms and what should be done if they occur.

1001 SLEE: Service deactivated

SeverityMajor

DescriptionThe indicated service has been deactivated because it has raised more critical alarms than allowed. That is, in a service’s deployment descriptor it is defined how many critical alarms the service is allowed to raise before it is taken out of service.

What to doActivate the service again.

1. Start a Network Gatekeeper Management Tool and log in.

2. Select the SLEE the where the deactivated service is installed in the SLEEs pane.

3. Select the SLEE_deployment service.

4. Select the activate method and enter the service name of the service to be activated.

5. Click Invoke.

The service is activated.

If the service keeps raising critical alarms, analyze the reason for those alarms. Trouble report the service to the service supplier if the analyses of the alarms show that the service is faulty.

1002 SLEE : Se rv ice da ta s to rage fa i l ed


1002 SLEE: Service data storage failed

SeverityMajor

DescriptionThe SLEE was not able to store service data in the database.

Possible reasons:

Neither the master nor the slave database is running

There is a network communication problem between the SLEE and the databases.

What to do1. Check that the database is running.

Enter command ps -ef|grep safe_mysqld in a command window. If the database is running, safe_mysqld is returned.

2. If the database is not running, start the database on the indicated URL. On the database server, do the following:

Run the bin/mysqld_safe & script in the /usr/local/mysql/ directory

3. If the database is running, restart the database. To stop the database, do the following:

Run the mysqladmin shutdown script in the /usr/local/mysql/bin directory.

To start the database, see above.

4. Check if the database error log (/usr/local/mysql/data/<hostname>.err) shows what caused the switch over.

5. Check the network connection between the SLEE that raised the alarm and the database.

For more information, see MySQL Reference Manual.



1003 SLEE: Service deactivation exception

SeverityMinor

DescriptionThe SLEE had to force the deactivation of the indicated service because an exception was caught from the service when the SLEE tried to deactivate the service.

What to doTrouble report the service to the service supplier.

1004 SLEE : Serv ice s top except ion


1004 SLEE: Service stop exception

SeverityMinor

DescriptionThe SLEE had to force the stopping of the indicated service because an exception was caught from the service when the SLEE tried to stop the service.

What to doTrouble report the service to the service supplier.



1005 SLEE: Database replication connect failure

SeverityCritical

DescriptionUnable to connect to both databases when verifying replication of databases.

What to doVerify that both databases are running.

1006 SLEE : Database rep l icat ion f i l es d i f fe r


1006 SLEE: Database replication files differ

SeverityCritical

DescriptionDatabase replication files differ more than the maximum allowed value.

The replication mechanism is not able to write data fast enough, or not at all.

What to doCheck the connection between the two databases.

Verify that both databases are running.



1007 SLEE: Database replication file names differ

SeverityCritical

DescriptionThe internal file names used by the database replication process are mismatching. This may occur when changing log file names explicitly, for example during backup.

What to doIf this alarm is generated when not explicitly resetting the logging, the replication files may be out of synchronization. Verify that the replication has not halted due to an error. If the replication has halted, restore the failed database.

1008 SLEE : Database rep l i cat i on s tatus check e r ro r


1008 SLEE: Database replication status check error

SeverityCritical

DescriptionError during check of database replication status. Internal error during database replication check.

What to doMake sure both databases are running. Restart or restore failed database.



1009 SLEE: Database replication file too large

SeverityCritical

DescriptionDatabase replication file is too large.

What to doFree up disk space. Explicitly change to a new log file by running the reset script

/usr/local/slee/bin/dbrunReset.sh

1010 SLEE : Da tabase rep l i cat ion f i l es e xp l i c i t l y r ese t


1010 SLEE: Database replication files explicitly reset

SeverityMinor

DescriptionSize of database replication files have reached 90% of maximum allowed size. The files will be gracefully reset.

What to doNo action needed.



1011 SLEE: Faulty username-password combination

SeverityMajor

DescriptionA user tried to perform a OAM method with inadequate user-password combination.

What to doExamine if there is a fraud attempt.

1012 SLEE : CORBA th read-poo l ove r l oaded


1012 SLEE: CORBA thread-pool overloaded

SeverityMajor

DescriptionThe CORBA thread pool utilization exceeds 80%.

What to doIncrease the CORBA thread pool size or extend the systems capacity. The thread pool size is increased through the slee_properties.xml file (corba_thread_pool attribute in the <SLEE_PROPERTIES> tag). Run the SLEEConfig.sh and restart the SLEE.



1013 SLEE: CORBA thread-pool overload - alarm ceased

SeverityMajor

DescriptionThe CORBA thread pool utilization has decreased so it is now below 78%.

What to do-

1014 SLEE : Un- reachable l i s tener ob jec t de tec ted


1014 SLEE: Un-reachable listener object detected

SeverityMajor

DescriptionThe SLEE cannot reach an object that has a listener registered.

What to doVerify that the service owning the listener is activated, that all involved SLEE processes are running, and that there is no network communication problem between the indicated SLEE’s server and the server where the un-reachable object executes.



1015 SLEE: Un-reachable listener object removed

SeverityMajor

DescriptionThe SLEE has not been able to reach an un-reachable listener object during the configured retry interval and the listener has been removed.

What to doSee alarm 1014 SLEE: Un-reachable listener object detected.

1016 SLEE : SLEE task cou ld no t be scheduled due to fu l l task queue


1016 SLEE: SLEE task could not be scheduled due to full task queue

SeverityMajor

DescriptionA SLEE task could not be scheduled because the SLEE task manager queue was full.

What to doIncrease the SLEE task manager queue size or extend the system capacity. To increase the task queue, select the SLEE service in the Network Gatekeeper Management Tool and use commands:

getTaskManagerQueueSize

setTaskManagerQueueSize



1017 SLEE: UNHANDLED exception raised by a SLEE task

SeverityMajor

DescriptionA SLEE task raised an UNHANDLED exception during method doTask.

What to doTrouble report the service that raised the exception to the service supplier.

1018 SLEE : Un-reachab le p lug- in ob jec t r emoved


1018 SLEE: Un-reachable plug-in object removed

SeverityMajor

DescriptionThe SLEE has not been able to reach an un-reachable plug-in object during the configured retry interval and the plug-in has been removed.

What to doVerify that the plug-in is activated, that all involved SLEE processes are running, and that there is no network communication problem between the indicated SLEE’s server and the server where the un-reachable object executes.



1019 SLEE: SLEE task pool empty

SeverityWarning

DescriptionAll threads in the SLEE task pool are currently busy.

What to doIncrease the SLEE task manager thread pool size or extend the system capacity. To increase the task manager thread pool size, select the SLEE service in the Network Gatekeeper Management Tool and use commands:

getTaskManagerThreadPoolSize

setTaskManagerThreadPoolSize

1020 SLEE: SLEE task poo l empty - a la rm ceased


1020 SLEE: SLEE task pool empty - alarm ceased

SeverityWarning

DescriptionThreads are available in the task pool again.

What to do-



1021 SLEE: Duplicate SLEE timer reference

SeverityWarning

DescriptionA scheduled timer has failed due to a duplicate timer reference.

What to doTrouble report the service that raised the exception to the service supplier.

1022 SLEE : Database tab le rep laced


1022 SLEE: Database table replaced

SeverityWarning

DescriptionThe indicated database table has been automatically replaced by the service. May occur when the service is updated and the format of the database table has been changed.

What to doContact BEA Support.



1023 SLEE: Database replication error

SeverityCritical

DescriptionThe database replication has halted due to an error in the slave database.

What to doLog in to the master database and execute the MySQL command SHOW SLAVE STATUS. Refer to the MySQL manual to correct the indicated error.

1024 SLEE: SLEE s tar t -up in progress


1024 SLEE: SLEE start-up in progress

SeverityWarning

DescriptionThe indicated SLEE is starting up.

What to do-



1025 SLEE: SLEE graceful shutdown in progress

SeverityWarning

DescriptionThe indicated SLEE is performing a graceful shutdown.

What to do-

1026 SLEE: P r i o r i t y task manager warn ing l eve l r eached


1026 SLEE: Priority task manager warning level reached

SeverityMinor

DescriptionPriority task queue utilization level exceeds alarm level.

What to doDecrease the number of requests sent through the system or increase the system capacity.



1027 SLEE: OAM runtime exception

SeverityWarning

DescriptionA service OAM method threw a RunTimeException.

What to doContact BEA Support and provide the trace information provided in the alarm.

1028 SLEE: P roduct exp i r ing a la rm


1028 SLEE: Product expiring alarm

SeverityWarning

DescriptionThis product will expire within x hours. It will then automatically shutdown.

What to doUpdate the license key for the product. Contact BEA Support.



1029 SLEE: Product expired alarm

SeverityMajor

DescriptionThis product has expired, shutting down.

What to doUpdate the license key for the product. Contact BEA Support.

1030 SLEE: T ransact i on l imi t v i o la ted by t ransact i on g roup Ca l l


1030 SLEE: Transaction limit violated by transaction group Call

SeverityMajor

DescriptionThe transaction limit for the transaction group Call has exceeded the limit defined in the license key. The alarm contains information on busy hour start time and end time -including date-, average busy-hour transactions per second and the limit as defined in the license key.

What to doContact BEA.



1031 SLEE: Transaction limit violated by transaction group Messaging

SeverityMajor

DescriptionThe transaction limit for the transaction group Messaging has exceeded the limit defined in the license key. The alarm contains information on busy hour start time and end time -including date-, average busy-hour transactions per second and the limit as defined in the license key.


1032 SLEE : T ransact ion l imi t v io la ted by t ransact i on g roup Mobi l i t y


1032 SLEE: Transaction limit violated by transaction group Mobility

SeverityMajor

DescriptionThe transaction limit for the transaction group Mobility has exceeded the limit defined in the license key. The alarm contains information on busy hour start time and end time -including date-, average busy-hour transactions per second and the limit as defined in the license key.




1033 SLEE: Transaction limit violated

SeverityMajor

DescriptionThe overall transaction limit has exceeded the limit defined in the license key. The alarm contains information on busy hour start time and end time -including date-, average busy-hour transactions per second and the limit as defined in the license key.


1040 SLEE g lobal counte r : Counte r hand le r c rea t i on fa i led


1040 SLEE global counter: Counter handler creation failed

SeverityMajor

DescriptionAn internal error occurred when the SLEE global counter service tried to create the counter handler for handling volatile counters.

Possible reasons:

The database is not running


What to doSee the “What to do” section in “1002 SLEE: Service data storage failed” on page 1-7.



1041 SLEE global counter: Periodic cleanup set-up at counter handler creation failed

SeverityMajor

DescriptionInternal error setting up periodic cleanup when the slee global counter service tried to create the counter handler for handling volatile counters.

Possible reasons:



What to doSee the “What to do” section in “1002 SLEE: Service data storage failed” on page 1-7.

1090 SLEE : CORBA warn ing rece ived


1090 SLEE: CORBA warning received

SeverityWarning

DescriptionA warning message has been received from the ORB. The complete message can be read in the SLEE trace file /usr/local/slee/bin/trace/.

What to doAnalyse the message in the SLEE trace file and take actions accordingly. For more information, refer to section 18 Exceptions and Error Messages in ORBacus for C++ and Java.



1091 SLEE: CORBA alarm received

SeverityMajor

DescriptionAn alarm has been received from the ORB. The complete message can be read in the SLEE trace file/usr/local/slee/bin/trace/.

What to doAnalyse the message in the SLEE trace file and take actions accordingly. For more information, refer to section 18 Exceptions and Error Messages in ORBacus for C++ and Java.

1095 SLEE : Database master changed


1095 SLEE: Database master changed

SeverityCritical

DescriptionThe database master has changed. The change was caused by a failure to create a connection with the previous database master on the indicated URL.

Possible reasons:



What to doIf using MySQL as database, see the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.

If using Oracle as database, consult the Oracle documentation for actions to take when a failover has occurred.



1096 SLEE: Database connection failed

SeverityCritical

DescriptionThe SLEE has failed to create a connection with the database on the indicated URL.

Possible reasons:



What to doIf using MySQL as database, see the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.

If using Oracle as database, consult the Oracle documentation for actions to take when a database connection failure has occurred.

1097 SLEE : Database low on d isk space


1097 SLEE: Database low on disk space

SeverityMajor

DescriptionThe database host’s database partition is beginning to run low on available disk space.

What to doMake more space available on the database partition of the disk. Check the size of the SLEE_CHARGING, SLEE_STATISTICS_DATA, SLEE_EVENT and SLEE_ALARM tables in slee_db and delete unused data.

If the database uses the same partition as the SLEE, check the number trace files stored in the /usr/local/slee/bin/trace/ directory.

When the alarm has been received, the low disk space threshold value must be changed to initiate the function again, see “SLEE and SLEE utility services” in Appendix B: List of Configuration Parameters - System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



1098 SLEE: Database critically low on disk space, database engine stopped

SeverityCritical

DescriptionThe database was stopped because the database host’s database partition was running critically low on available disk space.

What to doClean up the file system on the host’s database partition and restart the database.

As a first measure, make more space available on the database partition of the disk. Check the size of the SLEE_CHARGING, SLEE_STATISTICS_DATA, SLEE_EVENT and SLEE_ALARM tables in the slee_db and delete unused data.

If the database uses the same partition as the SLEE, check the number trace files stored in the /usr/local/slee/bin/trace/ directory.

When the alarm has been received, the critically low disk space threshold value must be changed to initiate the function again, see “SLEE and SLEE utility services” in Appendix B: List of Configuration Parameters - System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

1099 SLEE: Database par t i t i on c r i t i ca l l y l ow on d isk space , database eng ine s top fa i l ed


1099 SLEE: Database partition critically low on disk space, database engine stop failed

SeverityCritical

DescriptionThe indicated database failed to stop when the database host’s database partition was running critically low on available disk space.

There is a risk that the system will keep writing data to the database even though it is running out of disk space. This may corrupt the data in the database.

What to doClean up the file system on the host’s database partition.

As a first measure, make more space available on the database partition of the disk. Check the size of the SLEE_CHARGING, SLEE_STATISTICS_DATA, SLEE_EVENT and SLEE_ALARM tables in the slee_db and delete unused data.

If the database uses the same partition as the SLEE, check the number trace files stored in the /usr/local/slee/bin/trace directory.

Investigate why it was not possible to stop the database.

When the alarm has been received, the critically low disk space threshold value must be changed to initiate the function again, see “SLEE and SLEE utility services” in Appendix B: List of Configuration Parameters - System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



1100 SLEE charging: Charging data storage failed

SeverityCritical

DescriptionThe SLEE charging service has failed to write charging data to the database.

Possible reasons:

Neither the master nor slave database is running


What to doSee the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.

1101 SLEE charg ing : Charg ing serv i ce in i t ia l i za t i on fa i led


1101 SLEE charging: Charging service initialization failed

SeverityCritical

DescriptionThe alarm is raised if the charging service is activated before the database. That is, at installation or system restart, the database has to be started before the SLEE.

What to doStart BEA WebLogic Network Gatekeeper database before the SLEE at system installation or restart.



1102 SLEE charging: Charging table creation failed

SeverityCritical

DescriptionAn error occurred when trying to create the charging table in the database. The error occurs if the charging service is started before the database. That is, at installation or system restart, the database has to be started before the SLEE

What to doStart BEA WebLogic Network Gatekeeper database before the SLEE at system installation or restart.

1452 P lug- in manager : Reques t ra te cou ld no t be re con f igu red accord ing to new node SLA


1452 Plug-in manager: Request rate could not be re configured according to new node SLA

SeverityMajor

DescriptionThis alarm can only be raised if BEA Network Gatekeeper is used together with BEA WebLogic Network Gatekeeper.

The allowed request rate through the plug-in manager could not be updated according to the new node SLA.

What to doVerify the data in the node SLA and load the SLA again.



1500 SLEE SCS manager: No SCS found

SeverityMajor

DescriptionFound no matching SCSes.

What to doIn SCS_Manager, select getSCSList and check that the required SCS exists and is active. For MESSAGING_TYPE, check that a criteria has been added.

1501 SLEE SCS manager : SCS ove r l oad


1501 SLEE SCS manager: SCS overload

SeverityMajor

DescriptionAll matching SCSes are overloaded.

What to doDecrease traffic rate.



1600 SLEE EDR service: Listener execution time exceeded

SeverityMinor

DescriptionAn EDR listener has exceeded the maximum notify execution time when receiving a batch of EDRs.

What to doMake sure the EDR listeners keep the notify execution time as short as possible.

1601 SLEE EDR se rv ice : EDR l i s tene r r emoved


1601 SLEE EDR service: EDR listener removed

SeverityMajor

DescriptionAn EDR listener has been removed because it has exceeded the maximum notify execution time too many times.

What to doMake sure the EDR listeners keep the notify execution time as short as possible



1700 SLEE backup: Snapshot backup executed OK

SeverityWarning

DescriptionBackup executed OK.

What to doRefer to backup restoration procedure documentation.

1701 SLEE backup: Unable t o per fo rm backup


1701 SLEE backup: Unable to perform backup

SeverityCritical

DescriptionUnable to perform backup.




1702 SLEE backup: Un-handled error during backup

SeverityCritical

DescriptionUn-handled error during backup.

What to doContact BEA Support, include all alarm information.

1703 SLEE backup: Unab le to c reate maste r database connect i on


1703 SLEE backup: Unable to create master database connection

SeverityCritical

DescriptionUnable to perform backup, unable to create master database connection.




1704 SLEE backup: Unable to insert temporary data into table

SeverityCritical

DescriptionUnable to insert data from temporary tables into real tables during backup. A list is provided which tables that failed.

What to doContact BEA Support. Provide the list of tables.

1705 SLEE backup : Backup i s pe r fo rmed on non-rep l i cated sys tem


1705 SLEE backup: Backup is performed on non-replicated system

SeverityWarning

DescriptionA backup procedure intended for installations with replicated databases is performed on a non-replicated installation.




2101 ESPA messaging: Incoming message storage failed

SeverityMajor

DescriptionThe ESPA messaging service could not store an incoming message in the database.

Possible reason:

The mailbox is not created



What to doCheck mailbox

1. Start a Network Gatekeeper Management Tool and log in.

2. Select a SLEE where the ESPA messaging service is installed in the SLEEs pane.

3. Double-click the ESPA_messaging service in the Services pane.

4. Double-click the listMailboxes method.

5. Click the Invoke button in the Invoke Method window.

The registered mailboxes are displayed in the Messages pane.

6. Verify that the indicated mailbox is displayed in the Messages pane.

If not, create the mailbox. For more information, see Chapter 5: Enabling Service Providers and Applications in System Administrator’s Guide - BEA WebLogic Network Gatekeeper

Check database

7. See the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.

2102 ESPA messaging : No incoming des t inat i on address


2102 ESPA messaging: No incoming destination address

SeverityMinor

DescriptionThe ESPA messaging service received an incoming message without a destination address.

What to doNotify the originator of the message. The originators address is provided in the alarm printout.



2104 ESPA messaging: Plug-in not found

SeverityMajor

DescriptionThe ESPA messaging service could not find a messaging protocol plug-in when activated, or an outgoing message has an address format that is not supported by any messaging plug-in.

What to doIf the alarm is raised at service activation, verify that the messaging protocol plug-ins are installed and activate the messaging plug-ins before the ESPA messaging service is activated.

If the alarm is raised when a message with an unsupported address format is received, notify the originator of the message. The originators address is provided in the alarm printout.

2107 ESPA messag ing : Charg ing data s to rage fa i l ed


2107 ESPA messaging: Charging data storage failed

SeverityMajor

DescriptionThe ESPA messaging service could not write charging data to the database.

Possible reasons:

The SLEE charging service is not installed

The SLEE charging service is installed but not activated



What to doVerify that the charging service is installed and in the state activated using the getServices method in the SLEE service. If the charging service is working properly, continue with the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.



2108 ESPA messaging: Status update failed

SeverityMajor

DescriptionThe ESPA messaging service failed to change the status of a message stored in the database.

Possible reason:




2110 ESPA messaging : No outgo ing o r ig inat ing address


2110 ESPA messaging: No outgoing originating address

SeverityMajor

DescriptionThe ESPA messaging service received an outgoing message without an originating address. That is, the message will not be sent because it cannot be charged and not be replied to.

What to doNotify the enterprise operator.



2111 ESPA messaging: No outgoing destination address

SeverityMajor

DescriptionThe ESPA messaging service received an outgoing message without a destination address.

What to doNotify the enterprise operator.

2112 ESPA messaging : Message no t found in database


2112 ESPA messaging: Message not found in database

SeverityMinor

DescriptionThe ESPA messaging service could not find a message with the specified ID in the database. The connection with the database is broken.




2113 ESPA messaging: Message status update failed

SeverityMinor

DescriptionThe ESPA messaging service could not find a message with the specified ID in the database. The message has been deleted from the database before the status update notification has been received.

What to doThe problem is resolved by the system.

2114 ESPA messag ing : Ma i lbox no t found


2114 ESPA messaging: Mailbox not found

SeverityWarning

DescriptionThe ESPA messaging service could not find a mailbox for the received message. That is, the message is addressed to BEA WebLogic Network Gatekeeper, but the actual mailbox does not exist. That is, the address of the message is faulty. The message is automatically returned to the sender with a notification.

What to doThe problem is resolved by the system.



2115ESPA messaging: Mailbox existence verification failed

SeverityMajor

DescriptionThe ESPA messaging service could not verify if the specified mailbox exists in the database. That is, the connection with the database is broken.


2118 ESPA messaging : P lug- ins severe l y ove r loaded


2118 ESPA messaging: Plug-ins severely overloaded

SeverityMajor

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, messages cannot be sent to the network.

What to doInstall a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.



2122 ESPA messaging: Incoming message without ID

SeverityMinor

DescriptionThe Parlay messaging service received a message without an ID from a protocol plug-in.

What to doThe protocol plug-in that delivered the message to the messaging service is faulty.

2127 ESPA messag ing : Mai lbox c losed due to inact iv i t y


2127 ESPA messaging: Mailbox closed due to inactivity

SeverityWarning

DescriptionThe indicated mailbox has been closed due to inactivity. The allowed inactive time period is configurable using the setMailboxTimeout method in the ESPA_messaging service.

What to do-



2128 ESPA messaging: Unexpected error message received

SeverityMajor

DescriptionAn unexpected error message was received from the plug-in when sending an outgoing message.

What to doIdentify the original alarm from the plug-in and take actions accordingly.

2129 ESPA messaging : Fa i l ed to make no t i f i cat ion ca l lback


2129 ESPA messaging: Failed to make notification callback

SeverityMinor

DescriptionCallback to the application failed.

What to doThis alarm could occur when there are temporary network problems.

If the alarm is constantly recurring, you need to verify that the network connection to the application is functioning properly.

Verify that the application is running.



2140 ESPA messaging: Invalid destination address

SeverityWarning

DescriptionAn invalid destination address was provided when sending an SMS. The request was rejected by the Policy service due to a SLA limitation or rule on Service Provider level.

What to doInform the Service Provider providing the application that the application tries to send messages with one or more invalid destination addresses.

2141 ESPA messag ing : Inva l id des t inat i on address



SeverityWarning

DescriptionAn invalid destination address was provided when sending an SMS. The request was rejected by the Policy service due to a SLA limitation or rule on Application level.

What to doInform the Service Provider providing the application that the application tries to send messages with one or more invalid destination addresses.




SeverityWarning

DescriptionAn invalid destination address was provided when sending an MMS. The request was rejected by the Policy service due to a SLA limitation or rule on Service Provider level.

What to doInform the Service Provider providing the application that the application tries to send multimedia messages with one or more invalid destination addresses.

2143 ESPA messag ing : Inva l id des t inat i on address



SeverityWarning

DescriptionAn invalid destination address was provided when sending an MMS. The request was rejected by the Policy service due to a SLA limitation or rule on Application level.

What to doInform the Service Provider providing the application that the application tries to send multimedia messages with one or more invalid destination addresses.



2208 ESPA call control: Database connection failed

SeverityCritical

DescriptionThe ESPA call control service could not use the database. Possible reasons:




2213 ESPA ca l l cont ro l : P lug- in no t found


2213 ESPA call control: Plug-in not found

SeverityMajor

DescriptionThe ESPA call control service could not find a call control protocol plug-in when activated, or a create call leg request has an address format that is not supported by any call control plug-in.

What to doIf the alarm is raised a service activation, verify that the call control protocol plug-ins are installed and activated before the ESPA call control service is activated.

If the alarm is raised when a create call leg request with an unsupported address format is received, notify the originator of the request.



2214 ESPA call control: Plug-ins severely overloaded

SeverityWarning

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, call set up requests cannot be sent to the network.


2216 ESPA ca l l cont ro l : r outeReq t imeout de tec ted


2216 ESPA call control: routeReq timeout detected

SeverityMajor

DescriptionThe ESPA call control has issued a routeReq and no response has been received within the default timeout. The call session will be released.

What to do-



2217 ESPA call control: release call timeout detected

SeverityMajor

DescriptionThe ESPA call control has issued a release request and no response has been received within the default timeout. The call session will be released.

What to do-

2218 ESPA ca l l con t ro l : App l ica t i on superv is i on t imeout detec ted


2218 ESPA call control: Application supervision timeout detected

SeverityMajor

DescriptionThe ESPA call control has issued an eventReportReq and no response has been received within the default timeout. The call session will be released.

What to do-



2219 ESPA call control: Failed to setup Network Initiated Call Handler Service

SeverityMajor

DescriptionFailed to connect to the Network Initiated Call Handler Service (NICHS).

What to doVerify that the NICHS is started and in active mode. See “Running WebLogic Network Gatekeeper - Overview” in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

Note: The call control service will not be activated if it cannot connect itself to the NICHS.

2220 ESPA ca l l cont ro l : Fa i l ed to no t i f y app l icat ion about ca l l event


2220 ESPA call control: Failed to notify application about call event

SeverityMinor

DescriptionFailed to notify the application of the arrival of a call-related event.

What to doVerify that the NICHS is started and in active mode. See “Running WebLogic Network Gatekeeper - Overview” in System Administrator’s Guide - BEA WebLogic Network Gatekeeper

Note: The call control service will not be activated if it cannot connect itself to the NICHS.



2300 ESPA user location: Plug-ins severely overloaded

SeverityWarning

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, location requests cannot be sent to the network.


2301 ESPA use r l ocat i on : P lug- in no t found


2301 ESPA user location: Plug-in not found

SeverityWarning

DescriptionThe service could not find a call control protocol plug-in when activated, or a location request has an address format that is not supported by any user location plug-in.

What to doIf the alarm is raised a service activation, verify that the user location protocol plug-ins are installed and activated before the Parlay user location service is activated.

If the alarm is raised when a location request with an unsupported address format is received, notify the originator of the request.



2302 ESPA user location: Charging data storage failed

SeverityCritical

DescriptionThe ESPA user location service cannot write charging data to the database.

Possible reasons:





What to doVerify that the charging service is installed and in the state activated. If the charging service is working properly, continue with the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.

2309 ESPA user l ocat ion : Pe r iod ic l ocat ion repor t de l i ve r y fa i l ed


2309 ESPA user location: Periodic location report delivery failed

SeverityMinor

DescriptionA periodic location report delivery failed because the client was un-reachable.

What to doIt is up to the client to request a new location request.



2400 ESPA user status: Plug-ins severely overloaded

SeverityWarning

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, status requests cannot be sent to the network.


2401 ESPA user s tatus : P lug- in no t found


2401 ESPA user status: Plug-in not found

SeverityWarning

DescriptionThe ESPA user status service could not find a user status protocol plug-in when activated, or a status request has an address format that is not supported by any user status plug-in.

What to doIf the alarm is raised a service activation, verify that the user status protocol plug-ins are installed and activated before the ESPA user status service is activated.

If the alarm is raised when a status request with an unsupported address format is received, notify the originator of the request.



2402 ESPA user status: Charging data storage failed

SeverityCritical

DescriptionThe Parlay user status service cannot write charging data to the database.

Possible reasons:





What to doVerify that the charging service is installed and in the state activated. If the charging service is working properly, continue with the What to do section in “1002 SLEE: Service data storage failed” on page 1-7.

2502 ESPA charg ing : P lug- ins severe l y ove r loaded


2502 ESPA charging: Plug-ins severely overloaded

SeverityWarning

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, charging requests cannot be sent to the network.




2503 ESPA charging: Plug-in not found

SeverityWarning

DescriptionThe ESPA charging service could not find a charging protocol plug-in when activated, or a charging request has an address format that is not supported by any charging plug-in.

What to doIf the alarm is raised a service activation, verify that the charging protocol plug-ins are installed and activated before the ESPA charging service is activated.

If the alarm is raised when a charging request with an unsupported address format is received, notify the originator of the request.

2602 ESPA use r in te rac t i on : P lug- ins severe l y ove r loaded


2602 ESPA user interaction: Plug-ins severely overloaded

SeverityWarning

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, user interaction requests cannot be sent to the network.




2603 ESPA user interaction: Plug-in not found

SeverityWarning

DescriptionThe ESPA user interaction service could not find a user interaction protocol plug-in when activated, or a user interaction request has an address format that is not supported by any user interaction plug-in.

What to doIf the alarm is raised a service activation, verify that the user interaction protocol plug-ins are installed and activated before the ESPA user interaction service is activated.

If the alarm is raised when an interaction request with an unsupported address format is received, notify the originator of the request.

2605 ESPA use r i n te rac t ion : Found no match ing request o r no t i f i cat i on


2605 ESPA user interaction: Found no matching request or notification

SeverityWarning

DescriptionFound no enabled notification or outstanding sendInfoAndCollect-request matching the arrived message properties. The message will be discarded.

What to do-



2606 ESPA user interaction: Failed to report notification

SeverityMinor

DescriptionFailed to notify an application of an network initiated UI-event.

What to doThis alarm could occur when there are temporary network problems.

If the alarm is constantly recurring, you need to verify that the network connection to the application is functioning properly.

Verify that the application is running.

2607 ESPA use r in te rac t i on : Fa i l ed to l og charg ing in fo


2607 ESPA user interaction: Failed to log charging info

SeverityMajor

DescriptionFailed to log charging info in charging database.




2608 ESPA user interaction: Delete old request

SeverityWarning

DescriptionBecause of a collision with the primary key in the database an unanswered sendInfoAndCollectRequest was deleted.

What to doThis alarm can be disregarded if it occurs seldom.

If the alarm is constantly recurring, you may need to change the Sequence number range end ID parameter, through the Plugin_messaging_SMPP_SMS service management interface, see Appendix B: List of Configuration Parameters in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

2609 ESPA user in te ract ion : Message wi th no des t inat ion address


2609 ESPA user interaction: Message with no destination address

SeverityWarning

DescriptionA message arrived with no destination address set. The message will be discarded.

What to do-



2702 ESPA subscriber profile: Plug-ins severely overloaded

SeverityWarning

DescriptionAll protocol plug-ins of the requested type are severely overloaded. That is, subscriber profile requests cannot be sent to the network.


2703 ESPA subscr ibe r p ro f i l e : P lug- in no t found


2703 ESPA subscriber profile: Plug-in not found

SeverityWarning

DescriptionThe ESPA user interaction service could not find a subscriber profile protocol plug-in when activated, or a subscriber profile request has an address format that is not supported by any subscriber profile plug-in.

What to doIf the alarm is raised a service activation, verify that the user profile protocol plug-ins are installed and activated before the ESPA user profile service is activated.

If the alarm is raised when an subscriber profile request with an unsupported address format is received, notify the originator of the request.



2800 Network initiated call handler: Failed to register listener

SeverityMajor

DescriptionFailed to register a listener in a plug-in.

What to doCheck that there are call control capabilities installed in the system, and that the services are running.

2801 Network in i t ia ted ca l l hand le r : No ca l l con t ro l p lug- in found


2801 Network initiated call handler: No call control plug-in found

SeverityMajor

DescriptionNo call control plug-in found when trying to register as listener.

What to doCheck that there are call control plug-in installed in the system, and that the services are running.



2802 Network initiated call handler: No service registered

SeverityMajor

DescriptionNo service registered.

What to doCheck that there are call control capabilities installed in the system, and that the services are running.

2803 Network in i t ia ted ca l l hand le r : No enab led not i f i cat ion fo r event


2803 Network initiated call handler: No enabled notification for event

SeverityMajor

DescriptionReceived event in interrupt mode with no matching enabled notification request in mode interrupt. Policy service will take control of call.

What to doCheck the enabled notifications (method listNotification in SLEE Service ESPA_callcontrol) and verify that they are consistent with the expected client notification state.



2804 Network initiated call handler: No associated call

SeverityMajor

DescriptionReceived event in interrupt mode with no associated call.

What to doVerify that the application that originally registered for notifications on the call is active.

2805 Ne twork in i t ia ted ca l l hand le r : Over load


2805 Network initiated call handler: Overload

SeverityMajor

DescriptionService is severely overloaded.

What to doDecrease traffic.



2806 Network initiated call handler: Unknown error

SeverityMajor

DescriptionUnexpected error.


2807 Ne twork in i t ia ted ca l l hand le r : Suspend e r ro r


2807 Network initiated call handler: Suspend error

SeverityMajor

DescriptionThe service is suspended and cannot process any events.

What to doUse Network Gatekeeper Management Tool to resume it, see Chapter 10: Running WebLogic Network Gatekeeper - Overview in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



3001 Policy service: Parsing of retraction rule file failed

SeverityMajor

DescriptionThe rule engine cannot parse the rule file that retracts all not service-specific objects from the context.

What to doVerify that the rule file exists.

Verify that the syntax in the rule file is correct. See the log file for the policy service (policy.log) for information on the error.

3002 Po l i cy se rv ice : Pars ing o f se rv i ce-spec i f i c ru le f i l e fa i l ed


3002 Policy service: Parsing of service-specific rule file failed

SeverityMajor

DescriptionThe rule engine cannot parse the service-specific rule file.

What to doVerify that the rule file exists and that the path to the rule is correct.




3003 Policy service: Alarm raised from policy rule

SeverityMinor

DescriptionFailed to match whitelist for service provider.

What to doVerify that the specified whitelist exists in the SLEE.list.matcher service.

3004 Po l i cy se rv i ce : Pars ing o f se rv ice-spec i f i c ru le f i l e fa i l ed a t l oad t ime


3004 Policy service: Parsing of service-specific rule file failed at load time

SeverityMajor

DescriptionThe policy service cannot parse the service-specific rule file when it is about to be loaded into the database. Probably this is a syntax error in the rule file.

What to doVerify that the rule file exists and that the path to the rule file is correct.




3005 Policy service: Denial of service request

SeverityMinor

DescriptionThe policy service denied a service request.

What to do-

3006 Po l icy se rv ice : Runt ime except i on in po l i cy ru le


3006 Policy service: Runtime exception in policy rule

SeverityMajor

DescriptionThe policy service encountered a run-time exception.




3007 Policy service: Service Provider level request rate limit has reached warning level

SeverityMinor

DescriptionThe request rate limit for the method indicated in the alarm text has reached the warning level. The level is by default 80% of the maximum request rate limit as specified in the Service Provider SLA.

What to doInform the Service Provider that the request limit is closing in to its’ maximum. Investigate if the SLA needs to be re-negotiated.

3008 Po l i c y se rv ice : Se rv ice P rov ide r l eve l r equest ra te l imi t has been reached


3008 Policy service: Service Provider level request rate limit has been reached

SeverityMajor

DescriptionThe request rate limit for the method indicated in the alarm text has reached its’ maximum level as specified in the Service Provider SLA. The request was rejected.

What to doInform the Service Provider that the request limit has reached its maximum level. Investigate if the SLA needs to be re-negotiated.



3009 Policy service: Application level request rate limit has reached warning level

SeverityMinor

DescriptionThe request rate limit for the method indicated in the alarm text has reached the warning level. The level is by default 80% of the maximum request rate limit as specified in the Application level SLA.

What to doInform the Service Provider that the request limit is closing in to its’ maximum. Investigate if the SLA needs to be re-negotiated.

3010 Po l i c y se rv ice : App l icat ion l eve l r equest ra te l imi t has been reached


3010 Policy service: Application level request rate limit has been reached

SeverityMajor

DescriptionThe request rate limit for the method indicated in the alarm text has reached its’ maximum level as specified in the Application level SLA. The request was rejected.

What to doInform the Service Provider that the request limit has reached its maximum level. Investigate if the SLA needs to be re-negotiated.



3100 Policy service: Total request rate warning level reached

SeverityMinor

DescriptionThe total request rate from WebLogic Network Gatekeeper towards a network node has reached the warning level (default 80%).

What to doCheck the global contract data for the node in the total traffic SLA.

Investigate if it is possible to get access to more capacity in the network node. If that’s not possible, decrease the allowed request rate towards the network node in one or more of the service provider traffic SLAs.

3110 Po l i cy se rv ice : To ta l reques t ra te exceeded


3110 Policy service: Total request rate exceeded

SeverityMajor

DescriptionThe total request rate from WebLogic Network Gatekeeper towards a network node has exceeded the maximum allowed level defined in the total traffic SLA.

What to doSee alarm “3100 Policy service: Total request rate warning level reached” on page 1-126.



3200 Policy service: Service provider request rate warning level reached

SeverityMinor

DescriptionThe request rate from a specific service provider towards a network node reached the warning level (default 80%).

What to doCheck the node contract data in the service provider traffic SLA.

Consider upgrading the service provider. That is, move the service provider to a service provider group with a SP traffic SLA allowing a higher request rate towards the node.

3210 Po l i cy se rv i ce : Se rv i ce p rov ider reques t ra te exceeded


3210 Policy service: Service provider request rate exceeded

SeverityMajor

DescriptionThe request rate for a specific service provider towards a node exceeded the maximum allowed level for that service provider.

What to doSee alarm “3200 Policy service: Service provider request rate warning level reached” on page 1-128.



3300 Policy service: No valid global contract in the Total traffic SLA

SeverityMajor

DescriptionNo valid global contract for the node is found in the total traffic SLA.

What to doAdd a valid global contract in the total traffic SLA.

For updating the total traffic SLA, see Chapter 6: Protecting the Network with Traffic SLAs in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

3310 Po l i c y se rv i ce : No node cont ract in the Serv ice P rov ide r t ra f f i c SLA


3310 Policy service: No node contract in the Service Provider traffic SLA

SeverityMinor

DescriptionNo node contract for the node found in the service provider traffic SLA.

What to doAdd a valid node contract in the service provider traffic SLA.

For more information on updating the service provider traffic SLA, see Chapter 6: Protecting the Network with Traffic SLAs in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



5401 Plug-in messaging-SMPP: Plug-in registration failed

SeverityMajor

DescriptionThe protocol plug-in failed to register itself in the plug-in manager. The alarm occurs if the plug-in manager is not installed or if it is not in active state.

What to doVerify that the plug-in manager is active and restart the plug-in.

5403 P lug- in messag ing-SMPP: Message sending fa i l ed


5403 Plug-in messaging-SMPP: Message sending failed

SeverityMajor

DescriptionThe protocol plug-in failed to send the short message to the SMSC.

What to doVerify the physical connection with the SMSC and that the plug-in is configured properly.



5404 Plug-in messaging-SMPP: Plug-in removal failed

SeverityMajor

DescriptionThe protocol plug-in failed to unregister itself from the plug-in manager. The alarm occurs if the plug-in manager is not in active state.


5405 P lug- in messaging-SMPP: L is tener not i f i ca t i on fa i led


5405 Plug-in messaging-SMPP: Listener notification failed

SeverityMajor

DescriptionThe plug-in failed to notify a listener of the result when sending or receiving a message.

What to doVerify that the generic messaging SCS proxy (Parlay_messaging service) owning the listener object is active, that all SLEE processes are running, and that there are no network communication problems between the SLEEs.



5409 Plug-in messaging-SMPP: SMSC transmitter connection established

SeverityWarning

DescriptionThe plug-in has established a connection to the SMSC.

What to do-

5410 P lug- in messag ing-SMPP: SMSC t ransmi t te r reconnec t p rocedure t imeout


5410 Plug-in messaging-SMPP: SMSC transmitter reconnect procedure timeout

SeverityWarning

DescriptionThe plug-in has failed to reconnect to the SMSC during the configured duration and terminates the re-connection procedure.

What to doVerify the network connection. Restart the re-connection procedure using the resetSMPPConnection method in the Plugin_messaging_SMPP service.



5411 Plug-in messaging-SMPP: SMSC transmitter reconnect attempt failed

SeverityWarning

DescriptionA re-connection attempt in the re-connection procedure has failed.

What to doThe plug-in will keep on trying to connect until it succeeds or until the re-connection procedure times out.

5412 P lug- in messaging-SMPP: SMSC rece ive r connec t i on los t


5412 Plug-in messaging-SMPP: SMSC receiver connection lost

SeverityWarning

DescriptionThe plug-in has lost connection with the SMSC.

What to doMake sure the network connection to the SMSC is working properly.

The plug-in will automatically try to reconnect to the SMSC again. The total re-connection procedure duration and the interval between individual re-connection attempts depends on configuration settings in the Plugin_messaging_SMPP service.



5413 Plug-in messaging-SMPP: SMSC receiver connection established

SeverityWarning

DescriptionThe plug-in has established a connection to the SMSC.

What to do-

5414 P lug- in messag ing-SMPP: SMSC rece ive r reconnec t p rocedure t imeout


5414 Plug-in messaging-SMPP: SMSC receiver reconnect procedure timeout

SeverityWarning

DescriptionThe plug-in has failed to reconnect to the SMSC during the configured duration and terminates the re-connection procedure.

What to doVerify the network connection. Restart the re-connection procedure using the resetSMPPConnection method in the Plugin_messaging_SMPP service.



5415 Plug-in messaging-SMPP: SMSC receiver reconnect attempt failed

SeverityWarning

DescriptionA re-connection attempt in the re-connection procedure has failed.

What to doThe plug-in will keep on trying to connect until it succeeds or until the re-connection procedure times out.

5416 P lug- in messag ing-SMPP : S to r ing message data in da tabase fa i led


5416 Plug-in messaging-SMPP: Storing message data in database failed

SeverityMajor

DescriptionThe plug-in failed to store message data in the database.




5417 Plug-in messaging-SMPP: Updating message delivery status in database failed

SeverityMajor

DescriptionThe plug-in failed to the message delivery status in the database.


5418 P lug- in messagi ng-SMPP: Message de l i ve r y p r ocess ing in database fa i l ed


5418 Plug-in messaging-SMPP: Message delivery processing in database failed

SeverityMajor

DescriptionThe plug-in failed to store message data in the database.




5420 Plug-in messaging-SMPP: No listener available for incoming message

SeverityMajor

DescriptionNo registered listener was found for the incoming message. The plug-in was unable to deliver the incoming message.

What to doVerify that the generic messaging SCS proxy (Parlay_messaging service) owning the listener object is active, that all SLEE processes are running, and that there are no network communication problems between the SLEEs.

5421 P lug- in messag ing-SMPP: SMSC t ransmit te r connec t i on los t


5421 Plug-in messaging-SMPP: SMSC transmitter connection lost

SeverityWarning

DescriptionThe plug-in has lost connection with the SMSC. That is, it failed to send a heartbeat to the SMSC.

What to doMake sure the network connection to the SMSC is working properly.

The plug-in will automatically try to reconnect to the SMSC again. The total re-connection procedure duration and the interval between individual re-connection attempts depends on configuration settings in the Plugin_messaging_SMPP service.



5602 Plug-in user status-MPP: Failed to create provider

SeverityMajor

DescriptionThe plug-in failed to connect to the MPC node.

What to doVerify that the MPC node is running.

Verify that the configuration parameters are correct. For more information see Appendix B: List of Configuration Parameters in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

5603 P lug- in use r s tatus-MPP: Reg is t ra t i on fa i l ed


5603 Plug-in user status-MPP: Registration failed

SeverityMajor

DescriptionThe protocol plug-in failed to register itself in the plug-in manager. The alarm occurs if the plug-in manager is not installed or if it is not in active state.

What to doVerify that the plug-in manager is installed and activated.



5605 Plug-in user status-MPP: Removal failed

SeverityMajor

DescriptionThe protocol plug-in failed to unregister itself from the plug-in manager. The alarm occurs if the plug-in manager is not in active state.

What to doVerify that the plug-in manager is activated.

5606 P lug- in use r s ta tus-MPP : Connect i on es tab l i shed


5606 Plug-in user status-MPP: Connection established

SeverityWarning

DescriptionThe plug-in established connection to the MPC Node.

What to do-



5607 Plug-in user status-MPP: Re-connection procedure ended

SeverityWarning

DescriptionThe plug-in stopped trying to connect to MPC node.

What to doRestart the re-connection procedure.

Verify that the MPC node is running.

Verify that the configuration parameters are correct. For more information see Appendix B: List of Configuration Parameters in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

5700 P lug- in messag ing-CIMD: SMSC log in fa i l ed


5700 Plug-in messaging-CIMD: SMSC login failed

SeverityMajor

DescriptionThe protocol plug-in failed to log in to the SMSC due to a faulty user name and/or password.

What to doVerify the registered SMSC login parameters with the SMSC responsible.



5701 Plug-in messaging-CIMD: SMSC login succeeded

SeverityMinor

DescriptionThe protocol plug-in has successfully logged in to the SMSC.

What to do-

5702 P lug- in messag ing-C IMD: SMS de l i ve ry fa i l ed


5702 Plug-in messaging-CIMD: SMS delivery failed

SeverityMinor

DescriptionNo messaging SCS proxy could be obtained for SMS delivery.

What to doVerify that messaging SCS proxies are installed in the system and that they are activated.



5703 Plug-in messaging-CIMD: SMSC connection failed

SeverityMajor

DescriptionThe protocol plug-in failed to connect to the SMSC.

What to doVerify the SMSC addressing parameters registered in the plug-in and the status of the SMSC.

5704 P lug- in messag ing-C IMD: Log in request sending fa i l ed


5704 Plug-in messaging-CIMD: Login request sending failed

SeverityMajor

DescriptionThe protocol plug-in failed to send the Login request to the SMSC.

What to doVerify the SMSC addressing parameters registered in the plug-in and the status of the SMSC.



5705 Plug-in messaging-CIMD: Plug-in not connected to SMSC

SeverityMajor

DescriptionThe protocol plug-in has detected that it is not connected to the SMSC. The alarm is raised at plug-in start up or if the connection is lost.

What to doIf the alarm is raised at startup, it will automatically cease then the connection is successfully established.

If the alarm is raised during operation, the plug-in will try to re-establish the connection during the specified re-connection time. If this is successful the alarm will cease. Otherwise, the status of the SMSC has to be verified and the connection has to be manually restored through the plug-in’s reconnect OAM method.

Alarm 5706 is received as an acknowledgment on the successful connection in all the above cases.

5706 P lug- in messag ing-CIMD: P lug- in connected to SMSC


5706 Plug-in messaging-CIMD: Plug-in connected to SMSC

SeverityMinor

DescriptionThe protocol plug-in has successfully connected to the SMSC.

What to do-



5707 Plug-in messaging-CIMD: Exception when notifying listener

SeverityMajor

DescriptionFailed to notify listener.

What to doVerify that the SCS ESPA is running.

5708 P lug- in messaging-CIMD: Except ion when adding data to database


5708 Plug-in messaging-CIMD: Exception when adding data to database

SeverityMajor

DescriptionFailed to add data to message info database.

What to doVerify that the database is running.



5710 Plug-in messaging-CIMD: CIMD protocol error in submit response

SeverityMajor

DescriptionParameter pair mismatch for destination addresses and service center timestamps.

What to doReport protocol error to SMSC vendor.

5801 P lug- in messag ing-MM7: Unable to c reate SOAP sender


5801 Plug-in messaging-MM7: Unable to create SOAP sender

SeverityMajor

DescriptionThe protocol plug-in plug-in could not create a SOAP sender.

What to doVerify the MMSC addressing parameters registered in the plug-in.



5802 Plug-in messaging-MM7: No stored message ID matched message ID in received delivery report

SeverityMajor

DescriptionThe protocol plug-in has received a delivery report from the MMSC that could not be associated with a message ID of previously sent message.

What to do-

5803 P lug- in messaging-MM7: No message ID conta ined in r ece ived de l i ve r y r epo r t


5803 Plug-in messaging-MM7: No message ID contained in received delivery report

SeverityMajor

DescriptionThe protocol plug-in has received a delivery report from the MMSC without a message ID.

What to do-



5804 Plug-in messaging-MM7: Plug-in unable to parse delivery report request

SeverityMajor

DescriptionThe protocol plug-in has received a delivery report request from the MMSC that could not be parsed.

What to do-

5805 P lug- in messaging-MM7: P lug- in unab le to pa rse de l i ve r y request


5805 Plug-in messaging-MM7: Plug-in unable to parse delivery request

SeverityMajor

DescriptionThe protocol plug-in has received a deliver request from the MMSC that could not be parsed.

What to do-



5806 Plug-in messaging-MM7: No recipient address found in deliver request

SeverityMajor

DescriptionThe protocol plug-in could not find a recipient address in a deliver request received from the MMSC.

What to do-

5807 P lug- in messag ing-MM7: Unrecogn i zed address t ype in de l i ve r request


5807 Plug-in messaging-MM7: Unrecognized address type in deliver request

SeverityMajor

DescriptionThe protocol plug-in could not recognize the address type in a deliver request received from the MMSC.

What to do-



5808 Plug-in messaging-MM7: SOAP request parsing error

SeverityWarning

DescriptionThe protocol plug-in has detected an error when parsing a SOAP request from the MMSC.

What to do-

5809 P lug- in messag ing-MM7: SOAP request hand l ing e r ro r


5809 Plug-in messaging-MM7: SOAP request handling error

SeverityMajor

DescriptionThe SOAP engine has reported that it failed to handle a SOAP request from the MMSC.

What to do-



5810 Plug-in messaging-MM7: Retrieving simple content data from SOAP message failed

SeverityWarning

DescriptionThe protocol plug-in failed to retrieve a content/attachment data of a MIME simple type from a SOAP message because the data was corrupt.

What to do-

5811 P lug- in messaging-MM7: Re t r iev ing mul t ipa r t y conten t da ta f rom SOAP message fa i led


5811 Plug-in messaging-MM7: Retrieving multiparty content data from SOAP message failed

SeverityWarning

DescriptionThe protocol plug-in failed to retrieve a content/attachment data of a MIME multiparty type from a SOAP message because the data was corrupt.

What to do-



5812 Plug-in messaging-MM7: SOAP request sending failed

SeverityMajor

DescriptionThere was an error trying to send a SOAP request.

What to do-

5813 P lug- in messag ing-MM7: L i s tene r no t i f i ca t i on fa i l ed


5813 Plug-in messaging-MM7: Listener notification failed

SeverityMajor

DescriptionThere was an error trying to notify a plug-in listener.

What to do-



5814 Plug-in messaging-MM7: MM7 server connection lost

SeverityMajor

DescriptionAn error was encountered when checking the remote MM7 server using heartbeats. The plug-in has been deactivated.

What to doMake sure there are no network problems.

5815 P lug- in messaging-MM7: MM7 se rve r connect ion es tab l i shed


5815 Plug-in messaging-MM7: MM7 server connection established

SeverityMajor

DescriptionThe connection with the remote MM7 server is OK again and the plug-in has been activated again.

What to do-



5900 Plug-in location-MLP: Reading or writing configuration data failed

SeverityMajor

DescriptionThe protocol plug-in failed to read or write configuration data to the database.


5901 P lug- in loca t ion-MLP : P lug- in r eg i s t ra t i on fa i led


5901 Plug-in location-MLP: Plug-in registration failed

SeverityMajor

DescriptionThe protocol plug-in failed to register itself to or de-register from the plug-in manager. The alarm occurs if the plug-in manager is not installed or if it is not in active state.




5902 Plug-in location-MLP: Request sending error

SeverityMajor

DescriptionThe protocol plug-in failed to send a request to the MLP server.

What to doVerify the network connection and the MLP server connection data configured in the plug-in.

If there has been an outage in the MLP server, perform the method registerInResourceManager in the MLP plug-in service.

5903 P lug- in l ocat ion-MLP: Response re t r i ev ing e r ro r


5903 Plug-in location-MLP: Response retrieving error

SeverityMajor

DescriptionThe protocol plug-in failed to parse the XML result retrieved from the MLP server.

What to doVerify the network connection and the MLP server connection data configured in the plug-in. Verify the MLP version used.



6100 Plug-in message sender-PAP: Heartbeat lost

SeverityWarning

DescriptionThe heartbeat between the PPG and the plug-in was lost.

What to doMake sure plug-in heartbeat configuration is correct and that the server receiving heartbeat requests is up and running.

6101 P lug- in message sender -PAP: Hear tbeat l os t - a la rm ceased


6101 Plug-in message sender-PAP: Heartbeat lost - alarm ceased

SeverityWarning

DescriptionThe heartbeat between the PPG and the plug-in has been established.

What to do-



6102 Plug-in message sender-PAP: Failed to get SC

SeverityMinor

DescriptionThe plug-in could not retrieve a message sender service capability.

What to doVerify that the SC manager is working correctly. Verify that a service capability of type message sender is registered in the SC manager.

6103 P lug- in message sender-PAP: S ta tus no t i f i ca t i on t imeout


6103 Plug-in message sender-PAP: Status notification timeout

SeverityMinor

DescriptionA thread waiting for a status notification for a previously sent PAP message timed out.

What to doNo information available.



7001 SLEE statistics: Failed to store statistics data

SeverityMinor

DescriptionFailed to store statistics data.

What to doCheck the status of the database and check if the disk is full.

11100 ESPA access : User l ocked


11100 ESPA access: User locked

SeverityMinor

DescriptionAn ESPA user has failed to log in three times and has been locked.

What to doUnlock the user through the ESPA access OAM interface.



11130 ESPA access: Wrong application ID

SeverityMinor

DescriptionThe application was not allowed to log in. Tried to login with the wrong ID credentials (that is, a non existing service provider account/application account/application instance ID combination) will cause this alarm.

What to doMake sure the application is provided with the correct ID combination. Note that this alarm may indicate an intrusion attempt.

11131 ESPA access : Wrong app l ica t ion password


11131 ESPA access: Wrong application password

SeverityMinor

DescriptionThe application tried to log in with the wrong password.

What to doMake sure the application is provided with the correct credentials. Note that this alarm may indicate an intrusion attempt.



11132 ESPA access: Locked application log in attempt

SeverityMinor

DescriptionThe application tried to log in after being blocked. Consecutive calls to login after initial lock will cause this alarm.

What to doUnlock the application. Make sure the application is provided with the correct credentials. Note that this alarm may indicate an intrusion attempt.

11133 ESPA access : Non ac t i ve app l icat ion account


11133 ESPA access: Non active application account

SeverityMinor

DescriptionThe application tried to log in on non active account (service provider account, application account or service instance group level).

What to doActivate the account on the relevant level if it should be active.



11200 ESPA Message Sender: Failed to log charging info

SeverityMajor

DescriptionESPA Message sender could not write a CDR to the charging database.

What to doMake sure charging service is running.

11201 ESPA Message Sender : Request t imeout occur red


11201 ESPA Message Sender: Request timeout occurred

SeverityMinor

DescriptionAn asynchronous internal call to a SESPA module timed out.

What to doMake sue that the system is not too heavily loaded. Make sure that there are no network-related issues.



11202 ESPA Message Sender: Request timeout occurred

SeverityMinor

DescriptionAn asynchronous internal call to a plug-in timed out.

What to doMake sue that the system is not too heavily loaded. Make sure that there are no network-related issues.

11203 ESPA Message Sender : Reques t caused except ion


11203 ESPA Message Sender: Request caused exception

SeverityMinor

DescriptionAn internal request to a SESPA module caused an exception.

What to doMake sure that there are no network-related issues.



11204 ESPA Message Sender: Request caused exception

SeverityMinor

DescriptionAn internal request to a plug-in caused an exception.

What to doMake sure that there are no network-related issues.

11205 ESPA Message Sender : Cou ld not access pers is tent s to rage


11205 ESPA Message Sender: Could not access persistent storage

SeverityMajor

DescriptionCould not store information in the database.

What to doMake sure that the database is accessible.



12100 SESPA access: ESPA session logged out

SeverityMinor

DescriptionESPA has logged out a SESPA session (application instance) due to too many logged in application instances for the application instance group. The maximum number of concurrent logged in application instances is specified in the application instance group’s SLA. The oldest session is logged out first.

What to doIf ESPA logs out active sessions, the SLA has to be re-negotiated with the service provider. That is, the maximum number of concurrent logged in application instances in the SLA has to be increased.

If an application creates a lot of sessions that are logged out by ESPA, the application might be faulty. That is, the application does not log out un used sessions.

12101 SESPA access : ESPA sess i on e r ro r


12101 SESPA access: ESPA session error

SeverityWarning

DescriptionSESPA was unable to recover an ESPA session. That is, the ESPA object was unreachable.

What to doThe application is notified and will log in again and a new session is created.



12200 SESPA user location: Application error

SeverityMinor

DescriptionError occurs when invoking an application.

What to doCheck the network connection between the WebLogic Network Gatekeeper and the client.

Check that the client is not overloaded and thereby fails to respond in a timely fashion.

12300 SESPA messag ing : Enab le Par lay X incoming message not i f i cat i on fa i l ed


12300 SESPA messaging: Enable Parlay X incoming message notification failed

SeverityWarning

DescriptionSESPA was unable to enable the Parlay X incoming message notification for the application at restart of the server.

What to doManually remove the old notification and create a new notification through the SESPA messaging OAM interface. For more information on how to create a Parlay X incoming message notification, see Chapter 5: Enabling Service Providers and Applications in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



12301 SESPA messaging: Parlay X incoming message notification failed

SeverityMinor

DescriptionSESPA was unable to notify an application that a new message is available.

What to doVerify that the application is up and running.

12302 SESPA messag ing : Par lay X incoming message not i f i cat ion dest royed


12302 SESPA messaging: Parlay X incoming message notification destroyed

SeverityMinor

DescriptionA Parlay X incoming message notification for an application was destroyed (disabled).

What to doCreate a new notification through the SESPA messaging OAM interface. For more information on how to create a Parlay X incoming message notification, see Chapter 5: Enabling Service Providers and Applications in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



12400 SESPA messaging UI: Application error

SeverityMinor

DescriptionError invoking application.

What to doMake sure that the application is running and is accessible from the WebLogic Network Gatekeeper.

12401 SESPA messag ing U I : No t i f i ca t i on e r ro r


12401 SESPA messaging UI: Notification error

SeverityWarning

DescriptionFailed to re-enable notification after service restart.

What to doThe application must manually enable this notification.



12500 SESPA user status: Application error

SeverityMinor



12600 SESPA ca l l U I : App l ica t i on e r ro r


12600 SESPA call UI: Application error

SeverityMinor





12800 SESPA call control: Notification error

SeverityWarning

DescriptionFailed to re-enable notification after service restart.

What to doThe application must manually enable this notification.

12801 SESPA ca l l cont ro l : Appl i ca t i on e r ro r


12801 SESPA call control: Application error

SeverityMinor





12802 SESPA call control: Parlay X network initiated call notification destroyed

SeverityMinor

DescriptionA Parlay X network initiated call notification for an application was destroyed (disabled).

What to doCreate a new notification through the SESPA call control OAM interface. For more information on how to create a Parlay X network initiated call notifications, see Chapter 5: Enabling Service Providers and Applications in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

12900 SESPA subscr ibe r p ro f i l e : App l ica t i on e r ro r


12900 SESPA subscriber profile: Application error

SeverityMinor





13000 SESPA Message sender: Request timeout

SeverityMinor

DescriptionAn asynchronous request to ESPA timed out.

What to doMake sure the system is not overloaded. Verify that there are no network-related issues.

13001 SESPA Message sender : Reques t t imeout


13001 SESPA Message sender: Request timeout

SeverityMinor

DescriptionAn asynchronous call to an application timed out.

What to doMake sure the application is not overloaded or faulty. Verify that there are no network-related issues.



13002 SESPA Message sender: Unexpected exception

SeverityMinor

DescriptionA request to ESPA resulted in an unexpected exception.

What to doVerify that there are no network-related issues.

13003 SESPA Message sende r : Unexpec ted except ion


13003 SESPA Message sender: Unexpected exception

SeverityMinor

DescriptionA request to an application resulted in an unexpected exception.

What to doVerify that the application behaves correctly.



14000 Legacy SMPP: Faulty application login

SeverityWarning

DescriptionAn ESME tried to login with non-existing system id.

What to doIdentify the origin of the login attempt.

14001 Legacy SMPP: Negat i ve response fo r de l i ve r y repor t


14001 Legacy SMPP: Negative response for delivery report

SeverityWarning

DescriptionReceived a negative response from ESME for delivery report

What to doVerify behavior of application.



14002 Legacy SMPP: Negative response for delivery report

SeverityWarning

DescriptionReceived a negative response from ESME for delivery report


14003 Legacy SMPP: Message de l i ve r y fa i l ed


14003 Legacy SMPP: Message delivery failed

SeverityWarning

DescriptionFailed to deliver message to ESME.




14004 Legacy SMPP: Too many requests in progress

SeverityWarning

DescriptionESME request rejected because of too many requests in progress.


14100 Legacy MM7: Cou ld not l og in


14100 Legacy MM7: Could not login

SeverityMinor

DescriptionLegacy MM7 is unable to properly login to ESPA. Error with account.

What to doMake sure the account is properly configured in ESPA Access and Legacy MM7.



14101 Legacy MM7: Invalid account

SeverityWarning

DescriptionAn application tried to login with an invalid VAS and VASP ID.

What to doMake sure the account is properly configured in Legacy MM7. Make sure the application uses correct login information.

14200 Legacy PAP: Message response t imed out


14200 Legacy PAP: Message response timed out

SeverityMinor

DescriptionAn expected response to a previously sent message timed out.




14201 Legacy PAP: Authentication failed

SeverityWarning

DescriptionAn application failed to authenticate itself.

What to doMake sure that a client id mapping has been added for the client. See chapter Setting Up Application Connections - Legacy Applications, section PAP application connection in the System Administrator’s Guide.

14202 Legacy PAP : Push ID mismatch


14202 Legacy PAP: Push ID mismatch

SeverityWarning

DescriptionPush-id in response does not match push-id sent to application in request.

What to doMake sure the application sends back the correct push-id in the response.



22000 Plug-in OSA access: OSA gateway authentication failed

SeverityMajor

DescriptionThe OSA access plug-in failed to authenticate with the OSA gateway.

What to doVerify the OSA gateway connection data with the OSA gateway operator. Verify that the user certificate is still valid. For more information, see Chapter 7: Connecting to OSA Gateways in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.

22001 P lug- in OSA access : OSA gateway se rv ice manager unreachab le


22001 Plug-in OSA access: OSA gateway service manager unreachable

SeverityMajor

DescriptionThe OSA manager object obtained from the OSA gateway is considered dead. Might be a network problem.

What to doThe OSA gateway plug-in will automatically try to authenticate the OSA gateway at next service request.



22002 Plug-in OSA access: OSA gateway unreachable

SeverityMajor

DescriptionThe OSA access plug-in could not reach any of the connected OSA gateways (OSA frameworks) defined. Might be a network problem.

What to doVerify the network connection.

22003 P lug- in OSA access : No mapping ava i lab le


22003 Plug-in OSA access: No mapping available

SeverityMajor

DescriptionThe application requesting a service from the OSA gateway does not have a valid mapping towards the requested OSA service.

What to doVerify the current mapping. If no mapping exists, create a mapping according to the information in Enabling Service Providers and Applications in System Administrator’s Guide - BEA WebLogic Network Gatekeeper.



22004 Plug-in OSA access: Internal error

SeverityMajor

DescriptionAn unexpected internal error has occurred.


22101 P lug- in gener ic U I -HOSA: Message de l i ve r y fa i l ed - undef ined


22101 Plug-in generic UI-HOSA: Message delivery failed - undefined

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_UNDEFINED.

What to doContact the HOSA gateway owner.



22102 Plug-in generic UI-HOSA: Message delivery failed - illegal info

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ILLEGAL_INFO.


22103 P lug- in gener i c U I -HOSA : Message de l i ve r y fa i l ed - ID no t found


22103 Plug-in generic UI-HOSA: Message delivery failed - ID not found

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ID_NOT_FOUND.




22104 Plug-in generic UI-HOSA: Message delivery failed - resource unavailable

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_RESOURCE_UNAVAILABLE.


22105 P lug- in gener ic U I -HOSA: Message de l i ve r y fa i l ed - i l l ega l range


22105 Plug-in generic UI-HOSA: Message delivery failed - illegal range

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ILLEGAL_RANGE.




22106 Plug-in generic UI-HOSA: Message delivery failed - improper user response

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_IMPROPER_USER_RESPONSE.


22107 P lug- in gene r i c U I -HOSA : Message de l i ve r y fa i l ed - abandon


22107 Plug-in generic UI-HOSA: Message delivery failed - abandon

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ABANDON.




22108 Plug-in generic UI-HOSA: Message delivery failed - no operation active

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_NO_OPERATION_ACTIVE.


22109 P lug- in gene r ic U I -HOSA : Message de l i ve r y fa i l ed - no space ava i lab le


22109 Plug-in generic UI-HOSA: Message delivery failed - no space available

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_NO_SPACE_AVAILABLE.




22110 Plug-in generic UI-HOSA: Message delivery failed - resource timeout

SeverityMinor

DescriptionThe HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_RESOURCE_TIMEOUT.


22200 P lug- in OSA MPCC: In te rna l ca l lback e r ro r


22200 Plug-in OSA MPCC: Internal callback error

SeverityMinor

DescriptionCallback communication between OSA MPCC plug-in and ESPA (internally in the WebLogic Network Gatekeeper) failed.




22201 Plug-in OSA MPCC: OSA error

SeverityMinor

DescriptionCommunication between the plug-in and OSA gateway failed.

What to doCheck the OSA gateway logs to determine what caused the error.

22400 P lug- in OSA ca l l U I : In te rna l ca l lback e r ro r


22400 Plug-in OSA call UI: Internal callback error

SeverityMinor

DescriptionCallback communication between OSA call UI plug-in and ESPA (internally in the WebLogic Network Gatekeeper) failed.




22401 Plug-in OSA call UI: OSA error

SeverityMinor

DescriptionCommunication between the plug-in and OSA gateway failed.

What to doCheck the OSA gateway logs to determine what caused the error.

95001 Subscr ip t ion hand le r : Subscr iber p ro f i l e p lug- in re t r i eva l fa i l ed


95001 Subscription handler: Subscriber profile plug-in retrieval failed

SeverityMinor

DescriptionThe subscription handler could not find a subscriber profile plug-in when trying to access the subscriber profile database.

What to doVerify that an active subscriber profile plug-in is available.



95002 Subscription handler: Subscriber profile retrieval failed

SeverityMinor

DescriptionThe subscription handler received an exception when trying to retrieve the subscriber profile for the specified subscriber. Possible cause could be that the subscriber does not have a subscriber profile specified.

What to doVerify that the subscriber profile exists. Check for alarms from the subscriber profile plug-in.

95003 Subscr ip t i on hand le r : Except i on rece ived when t r y ing to wr i te subsc r ip t i on data


95003 Subscription handler: Exception received when trying to write subscription data

SeverityMinor

DescriptionThe subscription handler received an exception when trying to write subscription data to the specified subscriber’s subscriber profile.

What to doMake sure the correct database username and password combination is defined in the plug-in. Check the load on the subscriber profile database server.

Check for alarms from the subscriber profile plug-in to get more information.



95004 Subscription handler: Writing subscription data failed

SeverityMinor

DescriptionA set error was reported by the subscriber profile plug-in or the set request timed out when trying to write subscription data to the specified subscriber’s subscriber profile.



95005 Subscr ip t i on hand le r : Except ion rece i ved when t r y ing to read subscr ip t i on data


95005 Subscription handler: Exception received when trying to read subscription data

SeverityMinor

DescriptionAn exception occurred when trying to read subscription data from the specified subscriber’s subscriber profile.





95006 Subscription handler: Exception received when verifying a subscription

SeverityMinor

DescriptionAn exception occurred when trying to verify if the specified subscriber has a subscription to the specified application.



95007 Subscr ip t i on hand le r : Read ing subscr ip t i on data fa i l ed


95007 Subscription handler: Reading subscription data failed

SeverityMinor

DescriptionA get error was reported by the subscriber profile plug-in or the get request timed out when trying to read subscription data from the specified subscriber’s subscriber profile.






A P P E N D I X A

References

Architectural Overview - BEA WebLogic Network Gatekeeper

System Administrator’s Guide - BEA WebLogic Network Gatekeeper

Application Developer’s Guide - Parlay X Web Services for BEA WebLogic Network Gatekeeper

Application Developer’s Guide - Extended Web Services for BEA WebLogic Network Gatekeeper

API Descriptions - Parlay X Web Services for BEA WebLogic Network Gatekeeper

API Descriptions - Extended Web Services for BEA WebLogic Network Gatekeeper

User’s Guide - BEA WebLogic Network Gatekeeper Application Test Environment

Integration Guildelines for Partner Relationship Management - WebLogic Network Gatekeeper

Web Services API Description for Partner Relationship Management - WebLogic Network Gatekeeper

Standards API specifications

Parlay X specifications

See http://www.parlay.org

Database

MySQL Reference Manual

Orb

Refe rences


ORBacus for C++ and Java

Servlet engine

Tomcat Servlet Engine documentation

Documents

BEAWebLogic Network GatekeeperBEA WebLogic Network Gatekeeper Handling Alarms