top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is the importance of Peer and Realm Tables for a diameter node ?

+1 vote
683 views
What is the importance of Peer and Realm Tables for a diameter node ?
posted Jan 16, 2015 by Harshita Dhaliwal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Every diameter node maintains peer and realm table. It is used to forward a diameter message to correct destination. Peer table has entry of very next peer connected to it and Realm table has application related information for example: which node supports what application in a particular realm. so when a node receives a diameter message and if it a proxy node then it forwards this message by using application id to correct destination based on the realm table.
Hope you got it.

answer Jan 17, 2015 by Harshita
Similar Questions
+3 votes
Allowed host and realm naming for a diameter node

I am trying to clarify the allowed naming convention for the host and realm of a diameter node. This relates to the values used in the Origin-Host AVP (AVP Code 264) and Origin-Realm AVP (AVP Code 296). I have reviewed the Diameter RFCs and cannot find a definitive answer to this issue.

The reason for asking this question is that I am in discussion with a vendor of a Diameter Routing Agent (DRA) which claims that the host of a diameter node has to be in the format host.realm.
(1) Example of the only allowed format according to the vendor:Origin-Realm: example.com
Origin-Host: node.example.com
I want to clarify if multiple subdomains are allowed to be added in the host without being present in the realm.(2) Example:Origin-Realm: example.com
Origin-Host: node.site1.example.com

According to the vendor, the example 2 is not allowed. To have the host as in example 2, the realm will have to be site1.example.com.
Could someone please clarify this naming issue or point me to the standard where this is defined.

+2 votes
Diameter Peer and Realm

Probably is bigineer question. Diameter protocol maintains two table one is peer and other is realm. My question here is what is the requirement of having two tables here. We can have only one i.e. Peer Table which will tell us which peer to be reached. Looks that I am missing some part...

0 votes
Is it necessary a Diameter node should have information of its possible peer even before getting CER message ?

In one Diameter blog, I saw a statement in which mentioned, if a Diameter node receive CER from unknown peer it responds back to that peer with Result-Code AVP set to "DIAMETER_UNKNOWN_PEER".
Now my query, Does a Diameter node keep its potential peers information in advance ?

+1 vote
In what scenarios, a diameter node maintains two connection with peer ?

I went through an article of diameter, it mentions " Diameter standard advises that a diameter node to maintain two connection primary and secondary connection". Diameter node uses first connection in normal conditions and go for second one if primary connection is abrupted or not available. How far it is correct and where it is used exactly ?

...