In this section:

For detailed information about the appropriate description of the various supported CPUs and VMs, refer to Terminology.

Overview

Before Configuring a Ribbon DSC, it is recommended that you review and understand the contents of this section before starting the Ribbon DSC initial configuration tasks.

System Configuration

Before you configure the Ribbon DSC, make sure that you have completed the following tasks:

  • installed and powered up the DSC Platform

  • completed the required password configuration

  • enabled the required licensing

  • set the system time

  • familiarized yourself with the Web UI

  • configured the system-wide IP information, including the associated IP addresses for all VMs running DSC Processes

  • configured system logging and backup

If you require help to complete the above tasks, refer to the appropriate sections of the

For more information about these books, refer to the DSC Platforms Documentation Library.

Network Planning

It is recommended that you preplan your Diameter network by considering the following:

  • How many DSC Nodes are required?

  • What Diameter ID and realm should each DSC Node use?

  • Which Diameter IDs and realms are directly connected to the Ribbon DSC?

  • What are the associated IP address(es) and which transport protocols (TCP and/or SCTP) are applicable to your system?

  • What is the required security information for Transport Layer Security (TLS)?

  • What is the required security information for IPsec?

  • How many and which VMs are licensed for Ribbon DSC applications?

  • Which DSC slots should terminate the ADN Connections?

    For redundancy, every ADN should have at least two ADN connections that terminate on different DSC slots. Ideally, these ADN Connections should not connect to a single point of failure.

  • What message flows are required through each DSC Node?

  • What type of Diameter Nodes and relevant services (for example, PCRF, HSS, and so on) have to be provisioned for each realm?

  • What is the destination of these message flows?

    • messages that may be freely relayed can use default routing

    • messages that require a redirect routing may require explicit Routing Table provisioning

    • messages that should be forcibly blocked (DEA/firewall) require explicit Routing Table provisioning

    Note

    If you are configuring a DEA (firewall) or redirect, the Routing Tables must be configured before you activate the ADN connections, or you may start receiving traffic before you know how to route this traffic. This scenario should not cause lost traffic (the previous hop should retransmit the message on error), but it is inefficient.

    Note

    The  Ribbon DSC deployments have a single DSC Instance.

Next Configuring the DSC Nodes

  • No labels