This feature provides
customers the ability to configure wildcard based Diameter realm
routing to avoid configuring individual Diameter peers and/or
realms for all possible Diameter servers in their network.
The wildcard Diameter
routes can be statically configured under a Diameter endpoint configuration
using the CLI "route-entry realm * peer peer_name".
These route entries
are treated as default route entries and they will be selected when
there is no matching host@realm based or no realm based
route entry available.
The wildcard route
entry can be configured in the following ways:
route-entry realm * peer peer_name
- or -
route-entry host * realm * peer peer_name
Both these configurations
have the same effect; matches to any host and any realm.
The wildcard Diameter
route is added along with other realm based route entries in diabase. The
wildcard route entry will be selected to route a message only if
the message's destination realm does not match with any
of the other static realm based routes.
For
example,
route-entry realm
abc.com peer peer1
route-entry realm
def.com peer peer2
route-entry realm * peer
peer-default
If the message's
destination realm is abc.com then
the message will be routed to peer1. If
the message's destination realm is def.com then the message
will be routed to peer2.
If the destination realm is xyz.com then
the message will be routed to "peer-default".
When multiple wildcard
route entries are configured with same weights, then the routes
are selected in a round robin fashion. When multiple wildcard route
entries are configured with different weights, then the route with
the highest weight will be selected.
In case when there
are multiple wildcard routes with higher and equal weights and some routes
with lower weights, then only the higher weight routes will be selected
in round robin-fashion. The lower weight route can be selected only
when the higher weight routes are not valid because of the peers
being not in good state.