Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Assume that GCP Kubernetes Cluster is created beforehand based on various cloud providers installation guide here.

This section describe describes how to setup Diameter Server and Diameter Client hosted in the same Kubernetes Cluster. For example, the Diameter Server and Diameter Client hosted in GCP Kubernetes Cluster.

Assumed that the Diameter Server and Diameter Client workflows have been created with the following configurations.

...

  1. On the Configure EC Tab, fill in the EC Deployment Name and the rest of the fields if needed. Click Next to continue.

  2. On the Configure Auto Scale Tab, do not enable Auto Scaling. Click Next to continue.

  3. On the Configure Workflow Tab, create a new real time workflow from the selected workflow template i.e., Diameter Server or Diameter Client (either one). Click Next to continue.

  4. On the Configure Network Tab, create a Network Service type ClusterIP with appropriate port. The Service Name must be set to the Diameter Server or Diameter Client hostname.

...

Following the creation of the both ECD, let’s monitor the Kubernetes Services type ClusterIP that is being created.

...

Info

Kubernetes creates DNS records for Services and Pods. You can contact Services with consistent DNS names instead of IP addresses.

The Service Name in the form of <servicec<service-name>.<namespace> resolves to the cluster IP of the Service. <namespace> can be eliminated omitted if both ECD are located in the same namepsace, i.e., uepe

(OldNext, user may select and enable both ECD on the cluster one by one via the desktop-online WEB UI respectively.

...

To view Diameter Server workflow debug log, go back to the Manage menu. Select Execution Manager > Running Workflows.

...

Select the Diameter Server workflow that is currently running and click Open Monitor.

Then select Enable Debug and select Diameter Stack agent in the agent debug panel to view the debug log.

...

If connection established successfully between Diameter Server and Diameter Client, Capabilities-Exchange pair messages and repeat Device Watchdog messages are seen in the agent debug panel.

Code Block
2024-09-09 11:46:28 Diameter_Stack_1 Received Capabilities-Exchange-Request from peer /10.11.1.20:49810
{Additional_AVPs=null, Vendor_Id=9008, Auth_Application_Id=[4], Acct_Application_Id=null, EndToEndIdentifier=-113390639, Product_Name=MediationZone, className=D_Capabilities_Exchange_Request, Vendor_Specific_Application_Id=null, rawCmdflags=0x80, Origin_Host=client-digitalroute-com, Inband_Security_Id=[0], Is_Error=false, Supported_Vendor_Id=null, Firmware_Revision=-1, Origin_State_Id=1725853587, Is_Request=true, HopByHopIdentifier=2015775414, Host_IP_Address=[10.11.1.20], Origin_Realm=digitalroute.com, Is_Retransmit=false, Is_Proxiable=false}

2024-09-09 11:46:28 Diameter_Stack_1 transmitting targeted Capabilities-Exchange-Answer e2e=-113390639 hbh=2015775414 target=/10.11.1.20:49810 cmd={Additional_AVPs=null, Vendor_Id=9008, Auth_Application_Id=[16777238, 4], Acct_Application_Id=null, EndToEndIdentifier=-113390639, Product_Name=MediationZone, className=D_Capabilities_Exchange_Answer, Vendor_Specific_Application_Id=null, rawCmdflags=0x0, Origin_Host=server-digitalroute-com, Inband_Security_Id=[0], Is_Error=false, Supported_Vendor_Id=[9, 13019, 10415, 5535], Firmware_Revision=-1, Error_Message=Successful handshake, Origin_State_Id=1725853494, Is_Request=false, HopByHopIdentifier=2015775414, Host_IP_Address=[10.11.0.12], Result_Code=2001, Origin_Realm=digitalroute.com, Failed_AVP=null, Is_Retransmit=false, Is_Proxiable=false}
Code Block
2024-09-09 11:46:59 Diameter_Stack_1 Received Device-Watchdog-Request from peer client-digitalroute-com
{rawCmdflags=0x80, Origin_Host=client-digitalroute-com, Is_Error=false, EndToEndIdentifier=-113390638, className=D_Device_Watchdog_Request, Origin_State_Id=null, Is_Request=true, HopByHopIdentifier=2015775415, Origin_Realm=digitalroute.com, Is_Retransmit=false, Is_Proxiable=false}

2024-09-09 11:46:59 Diameter_Stack_1 transmitting targeted Device-Watchdog-Answer e2e=-113390638 hbh=2015775415 target=/10.11.1.20:49810 cmd={EndToEndIdentifier=-113390638, className=D_Device_Watchdog_Answer, rawCmdflags=0x0, Origin_Host=server-digitalroute-com, Is_Error=false, Error_Message=null, Origin_State_Id=null, Is_Request=false, HopByHopIdentifier=2015775415, Result_Code=2001, Origin_Realm=digitalroute.com, Failed_AVP=null, Is_Retransmit=false, Is_Proxiable=false}

(The following section is Deprecated)

The following examples shows how to setup both Diameter server and client inside the same cluster.

...