Modified: for 12.1.1



The Diameter Protocol (Rx) interface is supported on SBC CNe.  The Signaling Gateway (SG) Pod applies the SBC configuration related to DS, D+, DIAMETER, and Lawful Intercept (LI) IMS Signaling, similar to the SLB (Load Balancer).  In a VNF environment, the Diameter Agent and Diameter client are located on the same system.  

For Diameter Rx in the CNF environment, The Diameter Agent runs on the SC or RS pod with the Diameter Client running on the SG Pod. For Lawful Intercept (LI), the Diameter Client is IM and is co-hosted on the SG Pod with the Diameter client.

Diameter Architecture with SG Pod

The message exchanged between the SC/RS Pod (Diameter Agent) and the SG Pod (Diameter Client) must be serialized using FBS and sent using Inter-pod ICM service. The SG Pod is fixed to a 1:1 model. It is not scalable horizontally, which prevents storing redundancy data in the database and directly storing the information in the standby SG Pod.

On VNF, the Diameter client tracks each of the Diameter agents via registration messages sent from individual Diameter agents. Registration and maintaining the agent list on the Diameter Client propagates the Diameter node configuration change. The Diameter agent reads the configuration directly from CDB for both the CNF & VNF environment.

CLI Changes

The following fields are added to the existing diamNode configuration to enable the IP address and port allocation from the NS/PFE :

  • ipNamev4
  • ipNamev6
  • networkSegmentName

The requirements for the newly introduced CLI fields are:

  • You cannot modify the ipNameV4/ipNameV6 unless the diamNode is disabled.
  • The ipAddress (networkSegmentName) assigned for the diamNode is from the new Network Segment Table NsTableType="NS_SG".
  • The ipInterfaceGroup associated with the diamNode contains at least one ipInterface type NS_SG.
  • All the fields related to ipAddress/ipMetaVar are hidden for CNF.
  • You cannot modify the network segment table if the ipName is in use by the diamNode.
set addressContext default diamNode <> ipInterfaceGroupName <> networkSegmentName <> ipNameV4 <> ipNameV6 <> originRealm <> primaryOriginHost <>secondaryOriginHost <> state <enabled/diabled> dumpPdu <enabled/disabled> transactionTimeout <>

where :

  • networkSegmentName = the networkSegmentName configured in the corresponding ipInterfaceGroup > interface
  • ipNameV4 = the ipNameV4 configured in the corresponding ipInterfaceGroup > interface
  • ipNameV6 = the ipNameV6 configured in the corresponding ipInterfaceGroup > interface
Note
  • Can be configured as ipNameV4, ipNameV6, both, or none.
  • The ipName will be resolved into the IP address.
  • ipV4Address and ipV6Address are not configurable on the SBC CNe

Command Syntax

diamNode Example for SBC CNe
% set addressContext default diamNode <node name> 
	originRealm <realm name>
	primaryOriginHost <Host name>
	secondaryOriginHost <Secondary host>
	state <disabled | enabled>
	ipInterfaceGroupName <IG Name>
	networkSegmentName <Network Segment name>
	ipNameV4 <IPv4 address>
	ipNameV6 <IPv6 address>
	peer <peer name>
		state <disabled | enabled>         
		ipAddress <IPv4 address>
		fqdn <FQDN>
		tcpPort <port>
		deviceWatchdogTimer <timer value>
		deviceWatchdogTimerAnswerTimeout <timeout value>
    realmRoute <Realm Route name>
		peer <Peer name>
		realm <Realm>
		appId rx
        state <disabled | enabled>