This chapter describes known problems and associated solutions for the Diameter Adapter software. If a summary statement does not specify a particular platform, the problem applies to all platforms.
If you create a peer with transport specified as TLS, the Admin Console erroneously displays the transport type as TCP. Although, the transport is correctly recorded as TLS, the Admin Console does not fetch the correct value.
Use the CLI to view correct value of the transport attribute.
After creating Diameter service using the CLI, the Admin Console displays a Restart Required message for the domain.
Diameter Service is not dynamically reconfigurable. Restart the domain or cluster after creating Diameter service.
The asadmin create-peer command allows you to create two peers with same peer host and peer port values.
Specify the peer port using the --peerport option while creating a peer to avoid port clashes when configuring multiple peers on the same node.
You cannot configure multiple peers with same hostname and port number. To configure a single server supporting multiple applications, configure a single peer and create applications with list of supported application IDs.
When you log in to the Admin Console after creating a diameter application using the asadmin create-diameter-application command, the left pane of the Admin Console sometimes shows a HTTP 500 status error. This problem occurs when an integer id is provided to the --applicationsid option of the create-diameter-application command. Although the command succeeds, Admin Console throws an error.
Use the Admin Console to create a Diameter application with an integer applications id.