Explanation: The maxPacketSize is a configurable parameter set on the channel. If a peer attempts to send a packet that exceeds this value, the packet will be rejected and the TCP Connection will be closed.
User response: If you determine that the incoming packet is valid and you would like to allow packets of that size through the channel, the maxPacketSize configuration value can be increased.
Explanation: There is no open route to the desired realm. Therefore it is not possible to send the Diameter Packet.
User response: Verify that the configuration properties are correct.
Explanation: An invalid Diameter Packet was received.
User response: This indicates that the Diameter Packet being sent by the Diameter peer is not a valid packet.
Explanation: An Exception occurred while reading the Diameter Packet from the channel.
User response: If possible, turn on all tracing and send the trace.log file to IBM suport.
Explanation: The DiameterBaseApi is not able to locate the Channel Framework Service which it needs in order to start successfully.
User response: Check the log files for any errors related to starting up the Channel Framework Service.
Explanation: A configuration error occurred.
User response: Verify that the channel chain configuration is correct.
Explanation: A configuration error occurred.
User response: Verify that the channel chain configuration is correct.
Explanation: The TCP connection is not open. Therefore it is not possible to send the Diameter Packet to the specified Diameter Peer.
User response: The administrator should verify the state and condition of the Diameter Peer. It may be in an invalid state. In addition, the path between the Diameter Client and the Diameter Peer should be verified. A firewall may have an impact on the state of a connection between the Diameter Client and Diameter Peer.
Explanation: A connection to the designated Peer Host reached the Open state. Diameter Data packets may now be sent and received on the connection.
User response: No action is required.
Explanation: A connection to the designated Peer Host has transitioned out of the Open state. Diameter Data packets will not be transmitted or received from the Diameter Peer.
User response: The TCP connection has been terminated between this Diameter Component and its corresponding peer. This may be due to network transitions, or it may be due to the peer shutting power down.
Explanation: Threads are used to dynamically support each Diameter connection to a peer.The Diameter Component must not require more than 5 threads per Peer Connection.
User response: Increase the number of threads available through the Administration Console.If you feel that the number of threads must easily handle the number of connections, please contact yourservice representative.
Explanation: An internal error has occurred inside the Connection Finite State Machine. This error will likely affect any connection with the specified Peer Host.
User response: Turn on all tracing and send the trace.log file to IBM support.
Explanation: The Capabilities Exchange Request packet received from the Peer Host is incorrectly formed. A protocol error has been returned to the Peer Host in the Capabilities Exchange Answer.
User response: The CER packet has been determined to be incorrectly formed by the local Diameter implementation. Contact IBM support.
Explanation: This is a message that adds information to DHAC0104W. The Error Message and Value are appended to the end of this message.
User response: This information should assist IBM support in understanding and resolving configuration or implementation differences between the two Diameter implementations.
Explanation: An exception occured while transmitting the Capabilities Exchange Answer. The message associated with the Exception is displayed. The connection will be moved to the closed state.
User response: This exception might be due to a failure in the connection with the peer. Or, it might be due to another internal problem. The connection will be reset and retried. If it is not able to recover after multiple retry attempts, verify the connectivity between the Diameter Client (application server) and the target peer. If connectivity exists, turn on all tracing in the Diameter Client. Look for the error to occur in the trace.log file. If the failure is not apparent, contact IBM support for further assistance.
Explanation: A Channel Exception was received while setting up a virtual connection to the Peer Host. This is an internal error.
User response: Turn on tracing for all Diameter packages. Gather tracing information and contact IBM support.
Explanation: A Chain Exception was received while setting up a virtual connection to the Peer Host. This is an internal error.
User response: Turn on tracing for all Diameter packages. Gather tracing information and contact IBM support.
Explanation: An exception occurred while setting up a connection to the Peer Host. This is an internal error.
User response: Turn on tracing for all Diameter packages. Gather tracing information and contact IBM support.
Explanation: The first packet to be received on an inbound connection must contain the Origin-Host AVP. The first packet received did not contain Origin-Host AVP. The connection is shut down.
User response: The Diameter Peer that is interacting is not complying with the Diameter Protocol. Identify all peers establishing connections with the Diameter Client If an unexpected peer is attempting access, modify fire wall rules to deny this peer access. This might also be caused by an incorrect implementation of the protocol.
Explanation: The Origin-Host AVP is present, but the Origin-Host name has zero length. It is therefore unusable. The connection will be shut down.
User response: The Diameter Peer that is interacting is not complying with the Diameter Protocol. Identify all peers that are establishing connections with the Diameter Client. If an unexpected peer is attempting access, modify the fire wall rules to deny access to this peer. This may also be caused by an incorrect implementation of the protocol.
Explanation: The first packet received on an inbound connection must contain the Origin-Host AVP. The first packet received did not contain the Origin-Host AVP. The connection is shut down.
User response: The Diameter Peer that is interacting is not complying with the Diameter Protocol. Identify all peers that are establishing connections with the Diameter Client. If an unexpected peer is attempting access, modify the fire wall rules to deny access to this peer. This may also be caused by an incorrect implementation of the protocol.
Explanation: The Peer that has connected with the Diameter Client is not present in the Diameter Configuration. Only peers listed in this configuration will be allowed to connect to the Diameter Client. This connection will be shut down.
User response: If the Origin-Host name is a valid Origin-Host that you wish to allow interaction with the Diameter Client, make sure that the exact Origin-Host is specified in the appropriate Diameter_xx.properties file.
Explanation: The Origin-Host name specified in the packet is used to determine whether or not the connection shall remain alive. In this case, the Origin-Host of the received packet is greater than the Origin-Host value assigned to the Diameter Client. Therefore, this connection will be torn down.
User response: No action is necessary. This is a valid exchange to determine which connection between the two peers will remain up.
Explanation: The Connection State Machine is not able to accept this connection. The State Machine is already processing a connection and cannot accept another connection.
User response: No action may be necessary. This is caused when a Diameter Peer attempts to establish more than one connections to the Diameter Client. Only one is allowed. The Origin-Host name and IP address of the initiator should be checked to make sure that the Diameter Peer is correctly accessing the Diameter Client.
Explanation: The Connection State Machine has accepted a connection from the peer whose Origin-Host name is specified in the message. This connection has successfully passed the election process. The State Machine will accept and process the CER message.
User response: No action is required.
Explanation: The Origin-Host name of the peer was determined to be incorrect. The Origin-Host name value is not in the list of Diameter Peers that the Diameter Client is allowed to connect with.
User response: Check the Diameter_xx.properties file for the Origin-Host name that is listed in the message. If it is not present, add it and restart the appropriate application. If it is present, validate all other configuration information for that Diameter Peer.
Explanation: Before this connection could be processed, another connection with the same Origin-Host name was received and processed. This connection will be shut down.
User response: No action is required.
Explanation: The watchdog timer has expired the maximum number of times without receiving any response from the Diameter Peer. The connection associated with Origin-Host will be shut down immediately. After a restart interval, the Diameter Client will attempt to re-establish a connection with the peer.
User response: The administrator should verify the state and condition of the Diameter Peer. It may be in an invalid state. In addition, the path between the Diameter Client and the Diameter Peer should be verified. A firewall might be impacting the connection between the two.
Explanation: The underlying communication path has failed. The packet cannot be transmitted. The connection will be torn down, and the state machine will go to the Closed state. After a restart interval, the Diameter Client will attempt to re-establish a connection with the peer.
User response: The administrator should verify the state and condition of the Diameter Peer. It may be in an invalid state. In addition, the path between the Diameter Client and the Diameter Peer should be verified. A firewall might be impacting the connection between the two.
Explanation: A request packet was received, but the appropriate callback was not found. The application registering with the Diameter Base services did not register a callback to receive Request packets.
User response: Collect data from the error and contact IBM support for further investigation.
Explanation: An answer packet was received, but the appropriate callback was not found. A record of the corresponding Diameter Request packet was found, but no callback was present in this record. The record of the Diameter Request will also be discarded along with the received answer.
User response: This is an internal error. Please contact your service representative. The application has not registered a callback during registration. In addition, the application has not specified a callback in its initial request to send the packet.
Explanation: An answer packet was received, but the appropriate callback was not found. This may be due to a duplicate reply being sent. The first reply will clean up the resources and complete the transaction. Any subsequent reply will be discarded with this message.
User response: This will occur when there are duplicates introduced due to fail-over and fail-back situations. If this continues to occur and no data packets are being received by the application using this service, contact IBM support for further investigation.
Explanation: The first packet to be received on an inbound connection must contain a valid Origin-Host AVP. The packet received did not have a valid Origin-Host AVP. The Vendor-Specific bit was set when it should not have been set. The connection is shut down.
User response: The Diameter Peer that is interacting is not complying with the Diameter Protocol. Identify all peers establishing connections with the Diameter Client. If an unexpected peer is attempting access, modify fire wall rules to deny access to this peer. This may also be caused by an incorrect implementation of the protocol.
Explanation: Threads are retrieved for use from a specific Thread Pool. The Thread Pool must be named DiameterThreadPool. This Thread Pool is then used for each new thread that must be created by the Diameter infrastructure. This message appears when there is no DiameterThreadPool configured.
User response: Through the Integrated Solutions Console, you can create a Thread Pool with the number of threads that you expect to use. A general rule of thumb is to allocate 3 threads per Diameter connection that you plan to use. This Thread Pool can monitored through the Integrated Solutions Console.
Explanation: The Thread Pool Manager Service is used by some internal components to locate their Thread Pool. In this invocation, the Thread Pool Manager Service could not be found in the internal WebSphere Application Server registry.
User response: Contact IBM support.
Explanation: The Connection State Machine is not able to accept this connection. This security configuration used on this connection does not match the expected security configuration.
User response: Check the value of the inbandSecurityPolicy for this connection in the properties file. This value must match the actual security type used by this connection. If they do not match, either modify the setting in the properties file or modify the settings used by the Diameter peer.
Explanation: The Connection State Machine is not able to accept this connection. The Source IP address for this connection must match the remotePeerIpAddress configuration in the properties file.
User response: Check the value of the remotePeerIpAddress for this connection in the properties file. This value must match the actual IP address of the host that has set up this connection. Modify the properties file to match the IP address of the remote peer. Insure that no NAT translation is taking place, or that the IP address that is used matches the external IP address.
Explanation: The Capabilities Exchange Answer packet received from the Peer Host is incorrectly formed. The connection will be disconnected.
User response: The CEA packet has been judged to be incorrectly formed by the local Diameter implementation. Turn on tracing. Check the packet contents to see which AVP or AVPs are not correctly formed. This might be cause by implementation defects or by differing interpretations of the Specicifications. Contact IBM support.
Explanation: This is a message that adds information to DHAC0129W. The Error Message and Value are appended to the end of this message.
User response: This information should assist a service representative in understanding and resolving configuration or implementation differences between the two Diameter implementations. Contact IBM support.
Explanation: A request packet has been removed from the pending queue because there has not been a response in the expected amount of time.
User response: Verify that the connection with the peer is functioning correctly. If necessary adjust the packetTimeout value in the properties file to increase the allowed amount of time packets can remain in the pending queue.
Explanation: The Capabilities Exchange Answer packet that was received from the Peer Host did not pass protocol validation. The connection will be disconnected.
User response: The CEA packet did not pass protocol validation by the local Diameter implementation. Turn on tracing for the com.ibm.diameter.cfsm package and reinitiate the connection scenario for further information about the failure. Some possible causes could be a Result-Code AVP that indicates an error or failure, incompatible application support, an invalid origin host name or an invalid hopByHop identifier.
Explanation: None
User response: None