Before you start provisioning the DSC, it is assumed that you have planned your network (refer to Before Configuring the Ribbon DSC).

If you are configuring a Diameter Edge Agent (DEA), the routing tables should be provisioned before activating the ADN connections or you might start receiving traffic before provisioning message routing. No traffic loss occurs in this scenario (the previous hop should re-transmit the message on error), but this provisioning is inefficient

For information about provisioning routing tables, refer to Configuring Ribbon DSC Routing Tables.

 The following list provides you with steps for configuring the DSC Diameter basic configuration tasks.

  1. Provision IP Addresses, IP Routes, and hostnames (if required). 

    The  IP Addresses, IP Routes, and hostnames should have been configured during the initial configuration process. For information about this process, refer to the following:

    If you want to reconfigure the IP Addresses, IP Routes, and hostnames, refer to 

    1. for the DSC 8000, Configuring DSC 8000 Network Information
       

    2. for the DSC SWe (on VMware, on VMware), Configuring DSC SWe Network Information
       

    3. for the DSC SWe (on OpenStack), you cannot reconfigure these parameters 

       

  2. Create the Diameter Node with the appropriate (local) Diameter ID and realm and activate this node (refer to Configuring DSC Nodes).
     
  3. If you want the Diameter Node to advertise capabilities other than RELAY, configure an appropriate CER Parameter Set and define the Diameter Node CER Parameter Set name  (refer to Configuring CER Parameter Sets).   
     

  4. Create and configure the Transport Server objects (refer to Configuring Transport Servers).

    Note

     It is recommended that you configure one Transport Server for each Diameter Instance for each transport protocol (TCP/SCTP) you are using. 

  5. Provision the transport protocol (TCP/SCTP), local IP address or hostname, and port (refer to Configuring SCTP Parameter Sets).

     

  6. Activate the Transport Server and make sure that it is in UP state (refer to Configuring Transport Servers).


        

  7. Create the Diameter Node ADN objects and configure the remote Diameter ID and realm (refer to Configuring Adjacent Diameter Nodes).

    Note

    You must perform this task for each ADN.

  8. Activate the ADN (refer to Configuring Adjacent Diameter Nodes) 

    Note

     Do NOT activate the ADN Connections under the ADN until any explicit routing rules have been provisioned.

  9. If you need any explicit routing or parameter set overrides, provision them now (refer to Configuring the Server Pools and Configuring Realm Routing Tables and Records).

  10. Create the Diameter Node ADN Connection objects on each Diameter Process Instance (refer to Configuring ADN Connections).

  11. When you are ready to enable traffic, activate the ADN Connections (refer to Configuring ADN Connections).

  • No labels