Considerations for Peer Management

Following are the considerations for peer management in Diameter Endpoint:

  • The DRA creates a route table for every endpoint profile. Peers configured within the endpoint are a primary source of route entries in the route table.

  • Peers have an optional CLI to set the Destination-Host-Name that is different from the peer name. If the destination host name is not set, it copies the peer name into the Destination-Host-Name.

  • Each peer creates a direct and a realm-based route entry. It adds one more route entry when the Destination-Host-Name is different from the peer name.

  • The default weight of the static route is 10. You cannot configure the weight of routes formed from the peer entries. However, you can override them with a higher value using a route entry with the same host and realm combination.

  • The route table gets populated on the endpoint profile update notification, with each entry status as ‘Pending’.

  • You can add the dynamic route in the response path only if the session is referring a realm-based route entry. For a direct route entry, you cannot add the dynamic route in the response path.

  • The weight of a new dynamic route is the same as the route selected in the request path.

  • Dynamic routes have the expiration time configured. The active time of the dynamic routes enables during the selection of routes.