Professional Documents
Culture Documents
02 Mobile Diameter
02 Mobile Diameter
Overview
The diameter layer is responsible for maintaining connections to other diameter peers. This includes
connecting to the peers, sending watch dogs (keep alive), and disconnecting from the peers.
The SCA BB diameter infrastructure includes several components: the standard diameter stack, the peer
table, the routing table, and the forwarding scheme table, which defines the forwarding method for each
realm. The supported forwarding methods are high availability (HA) and load balancing (LB).
The main entity in the diameter infrastructure is the peer table. The peer table includes all the peers that
the SCE should connect to at the transport level. A Uniform Resource Identifier (URI) (usually ip:port)
identifies each peer.
The routing table and the peer table support online configuration, that is, add and remove commands are
supported while the diameter stack is up. The peer table and the routing table configurations are saved
to the running configuration.
Note Removing a peer from the peer table removes all the peer-related configuration information from the
routing table and from the forwarding scheme table.
Peer Table:
-------------------------------------------------------------
| Name | Host | Port | State |
-------------------------------------------------------------
| SER_GX | 10.121.64.38 | 3869 | Up |
| SER_GY | 10.121.64.46 | 3870 | Up |
-------------------------------------------------------------
The Peer table lists the peers and their state. The state can be Up, Down, or N/A. N/A means the stack
is not currently activated.
Note A peer is defined by a URI. Therefore, the same IP cannot be used on different ports to distinguish
between two servers except when a domain name server (DNS) is used.
In the example, the peer named SER_GY supports the Gy application on the cisco.com realm.
Load Balancing
Load balancing is completed by round robin, using the available servers. The available servers are round
robin cycled per session and not per message, that is, the messages for a specific session are all sent to
the same server.
When a server fails, it is removed from the round robin.
If a server is removed from the round robin and a session has already initiated, an alternative server
completes the session. The application can either start a new session or continue with the alternate server.
For information on configuring the load balancing scheme, see theDiameter Forwarding Mode CLI
Commands section on page 2-8.