|
|
The following pages describe 3.0 and higher style alarms that are processed by the current alarm-handling mechanisms and what can be done to respond to them. Unlike the 2.2 style alarms, these alarms have only a single ID. These alarms occur in relation to standard communication and container services, and contain slightly different information than 2.2 style alarms.
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to BEA
Internal exception thrown when an MBean does not comply to the MBean specification
Send any log with stack trace to BEA.
Internal exception thrown when an MBean Object Name is malformed.
Send any log with stack trace to BEA.
Internal exception thrown when an MBean fails to register.
Send any log with stack trace to BEA.
Internal exception thrown when an instance of an MBean already exists.
Send any log with stack trace to BEA.
Internal exception thrown when a requested instance of an MBean does not exist.
Send any log with stack trace to BEA.
Internal exception thrown when a management error severity fault happens.
Send any log with stack trace to BEA.
Either the Plugin Manager rejected an application initiated request towards a plugin because a policy rule rejected that request. or the Plugin Manager rejected the registration of the plugin if the plugin is not supported.
If the exception says that the plugin is not supported, make sure that the plugin jar has been woven by aspects. Otherwise, check the SLA to make sure it allows the request.
A plugin tries to register itself in the plugin manager but one with that ID has already been registered.
Contact BEA with the appropriate log file.
No plugin appropriate for this request can be found.
Check that the plugin is correctly deployed and running. Also make sure that a route exists to this plugin (Plugin Manager > Add Route).
The Plugin Manager is asked to return a plugin corresponding to this ID but none can be found.
Contact BEA with the appropriate log file.
An internal error occurred in the Plugin Manager causing a generic exception thrown from the Plugin Manager. The exception message explains the error.
Send any log with stack trace to BEA
The number of destination addresses for the message exceeded the SMPP maximum (254)
Have the service provider send multi-destination messages in 254 unit groups.
An error occurred when a short message was sent to the SMSC.
Made sure there is no problem with the connectivity between the WLNG and the SMPP SMSC. Check the configuration of the SMSC and the configuration of the SMS SMPP Plug-in. If the problem persists, contact BEA Support
The WLNG was unable to notify the application of a network initiated message
Make sure that the network connectivity between the Access Tier of the WLNG and the application is working properly. Make sure that the endpoint URL of the notification is correct.
The WLNG received a network initiated message for which there was no registered notification.
The WLNG was unable to notify the application of a network message delivery status.
Make sure that the network connectivity between the Access Tier of the WLNG and the application is working properly. Make sure that the endpoint URL of the notification is correct.
Unable to create the needed service for calls from the WLNG to the application
Provide logs with exception stack trace to BEA
The WLNG SMPP plug-in failed with a heartbeat attempt to the SMSC and will therefore attempt to reestablish the connection between the WLNG SMPP Plug-in and the SMSC
This could indicate a network issue. Check the connectivity between the SMSC and the WLNG SMPP Plug-in.
Some of the multiple destinations to which the message was sent have failed to be delivered. This alarm is sent for each message failure.
Look in the SMSC logs to find why the messages failed.
The WLNG SMS SMPP Plug-in failed to start the transmitter or receiver connection procedure.
Verify that the configuration on the WLNG SMPP Plug-in is correct. Make sure the network layer on the WLNG can access the SMSC. Make sure the SMSC is running properly.
WLNG has detected that segments from this message are missing.
WLNG is unable to bind to the SMSC.
Check the logs. Make sure the SMSC is online and reachable
WLNG is able to bind to the SMSC.
WLNG is able to connect to the SMSC.
Check the logs. Make sure the SMSC is online and reachable.
Either there is a client error or the binary content is too large for Network Gatekeeper to handle.
Verify that the client is working correctly. Check the size of the binary content.
An error occurred when the WLNG SMS Parlay MMM plug-in tried to start a notification for an application.
Make sure the connection between the WLNG network tier and the Parlay Gateway works and that the OSA_access service of the WLNG is configured properly. The Parlay Gateway should support P_MULTI_MEDIA_MESSAGING
An error occurred when the WLNG SMS Parlay MMM plug-in tried to stop a notification for an application.
Make sure the connection between the WLNG network tier and the Parlay Gateway works and that the OSA_access service of the WLNG is configured properly. The Parlay Gateway should support P_MULTI_MEDIA_MESSAGING
A message was propagated to the WLNG SMS Parlay MMM Plug-in that did not have a application associated with it.
Unable to create the needed service for calls from the WLNG to the application.
Provide logs with exception stack trace to BEA.
The WLNG SMS Parlay MMM Plug-in was unable to destroy a notification it had created
Make sure the connection between the WLNG network tier and the Parlay Gateway works and that the OSA_access service of the WLNG is configured properly. The Parlay Gateway should support P_MULTI_MEDIA_MESSAGING
The message was sent with an address plan that was not supported by the WLNG. The WLNG will try to use the default one (P_ADDRESS_PLAN_E164).
Make sure the applications use supported address schemas.
A conversion error occurred when the WLNG SMS Parlay MMM Plug-in tried to convert the network initiated message to a message that could be sent to the application.
Make sure the Parlay Gateway is providing the WLNG SMS Parlay MMM Plug-in with valid data.
A problem occurred when an SMS Plug-in tried to publish a message that a notification was created (this is used to communicate with other plug-ins and make them also create notification towards the network).
Collect log information and contact BEA.
The Presence SIP plug-in was not able to connect to Weblogic SIP server. The presence functionality is impaired until the connection is re-established
Make sure the Weblogic SIP server is running. Log on to WLNG Management Console, on the Presence SIP plug-in administration page, and verify that SIPNodeUrl, SipNodeUsername and SIPNodePassword are configured correctly. Execute “connectToWLSS” operation to manually re-establish the connection.
An internal error has occurred while the Presence SIP plug-in was trying to send a notification to the client about the decision on a pending subscription or the status change of the presentity
Provide logs with exception stack trace to BEA
The Presence SIP plug-in was not able to notify the client about the decision on a pending subscription. No further notification will be attempted.
The client may try to get presentity information by invoking getUserPresence() and startPresenceNotification(): either operation will fail if the subscription was not authorized. Verify the client is running at the endpoint specified in the subscription to receive future notifications for new subscriptions.
An error occurred when the Presence SIP plug-in was trying to notify the client about the status change of the presentity. No further notification will be sent on the current status change.
Verify the client is running at the endpoint specified to receive future notifications.
An error occurred while Presence SIP plug-in was processing a presence subscribePresence request.
Verify the following Presence SIP plug-in configurations in the Management Console:
Make sure WLSS is running and in good condition
An error occurred while Presence SIP plug-in was processing a presence getUserPresence request. Possible causes are:
Verify the client is running at the endpoint specified in the subscription; resubmit the current request after the authorization notification has been received
An error occurred while the Presence SIP plug-in was processing a presence startPresenceNotification request. Possible causes are:
Verify the client is running at the endpoint specified in the subscription; resubmit the current request after the authorization notification has been received.
An error occurred while the Presence SIP plug-in was processing a presence startPresenceNotification() request. Possible causes are:
Verify the database is running. Try to restart WLNG. Provide logs with exception stack trace to BEA.
An internal error occurred when the Presence SIP plug-in was started. It will not function properly unless the underlying problems are corrected
Try to restart the WLNG. Provide logs with exception stack trace to BEA
An OAM operation error has occurred. This is most likely due to storage service errors
Verify the database is running. Try to restart WLNG. Provide logs with exception stack trace to BEA
The budget service discovered a site configuration mismatch between geo-redundant sites.
Verify that the list of geo redundant sites is identical on all geo redundant sites of the WLNG
Duplicate geo-redundancy masters were detected. The situation has been corrected.
Verify network connectivity between geo-redundant sites. This alarm is likely an indication of a previous network split between sites.
Communication with a remote site has failed a configured number of times. The number of failures before this alarm is raised is determined by the remote site reachability alarm threshold setting.
Verify that network connectivity between geo redundant sites is operational and that the remote site is functioning.
A new geo-redundancy master has been elected and activated
Verify that there is network connectivity between geo-redundant sites and that the remote site is operational. This alarm could be an indication of a network split or a crash at the remote site.
The WLNG was unable to reach one of the remote geo-redundant sites.
Verify that there is network connectivity between geo-redundant sites and that the remote site is operational. This alarm could be an indication of a network split or a crash at the remote site.
A mismatch in budget configuration between geo-redundant sites has been detected.
Verify that the same SLA settings have been applied on all geo-redundant sites
An error occurred while the storage service was removing expired entries from the store database table.
Verify that the database is running and provide logs with exception stack trace to BEA.
An error occurred when the Storage Service was being activated
Verify that the database is running and provide logs with exception stack traces to BEA.
An error occurred when the Storage Service was being activated.
Verify that the database is running and that there is network connectivity within the cluster. Provide logs with exception stack traces to BEA.
An error occurred while performing asynchronous writes to the persistent storage. The requested changes may have been lost without the communication service being aware of it.
Verify that the database is running and provide logs with exception stack traces to BEA.
A generic storage exception was thrown in a communication service
Provide logs with exception stack traces to BEA.
Succeeded in sending a heartbeat to the MLP Server. Plugin status has been set to active.
Failed to send a heartbeat to the MLP Server. Plugin status has been deactivated.
Check the MLP server to make sure it is available.
The Terminal Location MLP plugin failed to start.
Check the log for more information.
The Terminal Location MLP plugin failed to stop.
Check the log for more information.
The Terminal Location MLP plugin was not activated.
Check the log for more information.
The Terminal Location MLP plugin was not deactivated.
Check the log for more information.
The attempt to send a location request failed.
Make sure the MLP server is available. Check the log for more information.
Network Gatekeeper was unable to notify the application that location notification has ceased.
Make sure the AT layer and the notification URL are available. Check the log for more information.
Network Gatekeeper was unable to notify the application that a location error has occurred.
Make sure the AT layer and the notification URL are available. Check the log for more information.
Network Gatekeeper was unable to notify the application that a location notification has been received.
Make sure the AT layer and the notification URL are available. Check the log for more information.
Network Gatekeeper was unable to send a multimedia message to the network.
Check the log for more information. Common problems: missing/invalid required parameters; configuration problems; storage errors.
Network Gatekeeper was unable to get delivery status on a multimedia message from the network.
Check the log for more information. Common problems: invalid request identifier; storage errors.
Network Gatekeeper was unable to send the list of received messages to the application.
Check the log for more information. Common problems: invalid MM7 configuration; storage errors.
Network Gatekeeper was unable to send a requested received multimedia message - including attachment - to the application.
Check the log for more information. Common problems: no attachment found; storage errors.
Network Gatekeeper was unable to send an MM7 message to the network.
Check the log for more information. Common problems: MM7 Relay Server not ready or misconfigured.
Network Gatekeeper was unable to activate the MM7 plug-in.
Check the log for more information. Common problems: Plugin not ready; plugin ID duplicated.
Network Gatekeeper was unable to deactivate the MM7 plug-in.
Check the log for more information. Common problems: can’t find the plugin with the ID provided.
Network Gatekeeper was unable to start the MM7 plug-in.
Check the log for more information. Common problems: failed to located WorkContextMap; MBean-related exceptions.
Network Gatekeeper was unable to stop the MM7 plug-in.
Check the log for more information. Common problem: MBean-related exceptions.
Network Gatekeeper was unable to notify the application that a message has been received from the network.
Check the log for more information. Common problems: no matching NotificationInfo; storage errors; unsupported address type; application not available.
Network Gatekeeper was unable to notify the application that a message delivery receipt has been received from the network.
Check the log for more information. Common problems: no matching messageinfo, recipient number not found; application unavailable.
Network Gatekeeper was unable to contact the application.
Check the availability of the application.
The delivery acknowledgement does not have a recipient number that matches any of the destination addresses of the sent message. Uncommon.
Check the log for more information. Common problem: issue between WLNG and MMSC.
The incoming delivery report did not correlate to a message info. For example: the MMSC sent up a delivery report which Network Gatekeeper has no record of sending.
Check the log for more information. Common problem: Network Gatekeeper is not configured to request delivery reports but the MMSC is sending them anyway.
Network Gatekeeper does not support the address type attached to the multimedia message.
Check the log for more information and check the address type.
Network Gatekeeper is unable to start message notification.
Check the log for more information. Common problems: duplicated correlator IDs; storage errors.
Network Gatekeeper is unable to stop message notification.
Check the log for more information. Common problems: Correlator ID doesn’t exist; storage errors.
The MMSC and Network Gatekeeper are out of sync with respect to notifications. A mobile-originated message has been sent from the network no application has set up a notification to receive it.
Check the log for more information.
The SubmitResponse returned an error-code.
Look at the logs to see the specific status code and status text.
The budget quota for a subscriber with limitExceedOK set to true has been exceeded.
Because the heartbeat service is sending pings, the expiration of the timer is ignored.
The heatbeat service was able to contact the plugin
The heatbeat service was unable to contact the plugin
Network Gatekeeper was unable to start the plugin.
Check logs for more information. Possible issues: Network Gatekeeper was unable to locate the WorkContextMap; MBean-related exceptions.
Network Gatekeeper was unable to stop the plugin.
Check logs. Possible issues: MBean-related exceptions.
Network Gatekeeper was unable to activate the plugin.
Check the log for more information. Possible issues: The plugin is not ready or there is a duplicated Plugin ID.
Network Gatekeeper was unable to deactivate the plugin.
Check the log for more information. Possible issues: Network Gatekeeper is unable to find a plugin with the given ID.
Network Gatekeeper was unable to update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart WLNG.
Network Gatekeeper was unable to update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart WLNG.
Network Gatekeeper was unable update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart WLNG.
Network Gatekeeper was unable to update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart WLNG.
Network Gatekeeper was unable to update call status
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call control manager is not in active state; or the call control call is not in idle or active state.
Network Gatekeeper was unable to invoke IpMultiPartyCall.getInfoReq on the Parlay gateway
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call control manager is not in active state.
Network Gatekeeper was unable to invoke to invoke IpCallLeg.continueProcessing on Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg doesn't exist in the network; or the call leg is in releasing state.
Network Gatekeeper was unable to invoke IpMultiPartyCall.createAndRouteCallLegReq on Parlay gateway.
Check logs for more information. Possible issues: the Parlay gw is in an abnormal status or unavailable; the call is not in idle or active state; the call control manager is not in active state.
Network Gatekeeper was unable to invoke IpMultiPartyCallControlManager.createCall on Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call control manager is not in active state.
Network Gatekeeper was unable to invoke IpCallLeg.eventReportReq() on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Network Gatekeeper was unable to invoke IpCallLeg.getInfoReq() on Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Network Gatekeeper was unable to invoke IpMultiPartyCall.release on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Network Gatekeeper was unable to invoke IpCallLeg.routeReq on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Network Gatekeeper was unable to invoke IpMultiPartyCall.createCallLeg on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call does not exist in the network or is in releasing state.
The Parlay MPCC plugin for the Parlay X 3.0 Call Notification communication service failed to start.
Check the log for more information.
The Parlay MPCC plugin for the Parlay X 3.0 Call Notification communication service failed to activate.
Check the log for more information.
The Parlay MPCC plugin for the Parlay X 3.0 Call Notification communication service failed to stop.
Check the log for more information.
The Parlay MPCC plugin for the Parlay X 3.0 Call Notification communication service failed to deactivate.
Check the log for more information.
Network Gatekeeper was unable to deliver a notification to the application.
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
Network Gatekeeper was unable to deliver the location of a recorded message to the application.
| Note: | The Audio Call communication service does not support Play and Record Interaction for 4.0. |
Network Gatekeeper was unable to deliver the digits collected from the end user to the application.
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
Network Gatekeeper was unable to delete a notification registration in the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Network Gatekeeper was unable to create a notification registration in the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Network Gatekeeper was unable to set a callback for a call leg in the Parlay Gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Network Gatekeeper was unable to invoke continueProcessing on the Parlay Gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Network Gatekeeper was unable to create a call leg for the call session in the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Network Gatekeeper was unable to start the plugin.
Check the log for more information. Possible issues: unable to location WorkContextMap, MBean related exceptions.
Network Gatekeeper was unable to activate the plugin.
Check the log for more information. Possible issues: MBean related exceptions.
Network Gatekeeper was unable to change the state of the plugin to active.
Check the log for more information. Possible issues: the plugin is not ready; there are duplicate plugin IDs.
Network Gatekeeper was unable to change the state of the plugin to inactive.
Check the log for more information. Possible issues: the plugin with the ID specified cannot be found.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Network Gatekeeper was unable to invoke a method on the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure IpAppUICallRef is not null.
Network Gatekeeper was unable to invoke a method on the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure the UI session is valid.
Network Gatekeeper was unable to invoke a method on the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure the UI session is valid. Make sure the criteria are valid.
Network Gatekeeper was unable to invoke a method on the Parlay Gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure the UI session is valid.
Network Gatekeeper was received an error message back from the Parlay Gateway.
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
Network Gatekeeper was received an error message back from the Parlay gateway.
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
Network Gatekeeper was received an error message back from the Parlay gateway.
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
Network Gatekeeper was received an error message back from the Parlay Gateway.
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
Network Gatekeeper was unable to start the plug-in.
Check the log for more information.
Network Gatekeeper was unable to activate the plug-in.
Check the log for more information.
Network Gatekeeper was unable to stop the plug-in.
Check the log for more information.
Network Gatekeeper was unable to deactivate the plug-in.
Check the log for more information.
Network Gatekeeper was unable to perform the “get” method call.
Check the log for more information.
Network Gatekeeper was unable to perform the “getProfile” method call.
Check the log for more information.
Network Gatekeeper was unable to establish a call session
Check the log for more information.
Network Gatekeeper was unable to retrieve information on a call
Check the log for more information.
Network Gatekeeper was unable to end a call
Check the log for more information.
Network Gatekeeper was unable to cancel a call request
Check the log for more information.
Network Gatekeeper was unable to initiate a call attempt for the first participant
Check the log for more information. Check the plug-in connection to the SS7 stack.
Network Gatekeeper was unable to initiate a call attempt for the second participant
Check the log for more information. Check the plug-in connection to the SS7 stack.
Network Gatekeeper was unable to continue call processing
Check the log for more information. Check the plug-in connection to the SS7 stack.
Network Gatekeeper was unable to terminate an INAP dialog
Check the log for more information. Check the plug-in connection to the SS7 stack.
Network Gatekeeper was unable to release a call session
Check the log for more information. Check the plug-in connection to the SS7 stack.
Network Gatekeeper was unable to activate the plug-in instance
Check the log for more information.
Network Gatekeeper was unable to deactivate the plug-in instance
Check the log for more information.
Network Gatekeeper was unable to send a push message
Check the log for more information.
Network Gatekeeper was unable to send a result notification message
Check the log for more information.
A generic exception was thrown in a communication service.
Provide logs with exception stack traces to BEA.
|