Adding a Connection

Use this task to create a new Connection. The fields and configuration considerations are described in Diameter Connection Configuration Elements.

1. Click Diameter > Configuration > Connections.
2. Click Insert.
   The Diameter > Configuration > Connections [Insert] does not open if any of the following conditions exist:

   • There is no Local Node in the signaling Network Element (NE) to which the Connection can be assigned.
   • There is no Peer Node in the signaling Network Element (NE) to which the Connection can be assigned.

   Note:

   You cannot configure routes for OAM from the Network routes screen of the DSR GUI.
3. Enter a unique name for the Connection in the Connection Name field.
4. Select a AAA Protocol.
5. Select an option in the Transport Protocol field.
   The Transport Protocol that you select for your Connection must match the protocol supported by both the Local Node and the Peer Node for the Connection.
6. Select a Local Node from the list.
   The Local Node must use the same IP protocol as the Peer Node you select. If you do not see the Local Node you want to use, you might need to create a new Local Node. See Adding a Local Node.
7. Select the Connection Mode from the list. See Diameter Connection Configuration Elements.

   Responder Only connections associated with a Peer Node are not considered listen ports (SCTP, TCP, TLS, or DTLS).

8. If you set up the Connection Mode for Initiator Only, you can optionally enter a Local Initiate Port number in the field.
9. Select the Local IP Address from the list.
10. If the Transport Protocol is set to SCTP, then select the Alternate Local IP Address of this Connection from the list.
11. Select a IPFE Initiator DAMP from the list.
    This step is only needed for IPFE Initiator connections.
12. Select a Peer Node from the list.
    Initiator port ranges are divided into user-assigned and DCL-assigned sub-ranges. Depending on the type of initiator connection, fixed or Floating IPFE, there are two or more user/DCL sub-ranges. The Peer Node must use the same Transport Protocol as the Local Node that you selected. If you do not see the Peer Node you want to use, you might need to create a new Peer Node. See Adding a Peer Node.

    Diameter Transport Layer (DCL) is the software layer of the stack which implements diameter transport connections.

13. Select from the options in Peer Node Identification field.
14. If needed, select the Peer IP Address of this Connection from the Peer IP Address list.
15. If needed, select the Alternate Peer IP Address of this Connection from the Alternate Peer IP Address list.
16. If needed, enter a Transport FQDN for this Connection.
17. Select a Connection Configuration Set from the list.
18. If one is needed, select a CEX Configuration Set from the list .
19. If the Per Connection Ingress MPS Control feature is active in the system, select a Capacity Configuration Set from the list.
20. Specify the Transport Congestion Abatement Timeout.
21. Select a Remote Busy Usage setting from the list.
22. If you selected Enabled or Host Override for Remote Busy Usage, set the Remote Busy Abatement Timeout value.
23. Select from the options in Message Priority Setting field.
24. If you selected User Configured as the Message Priority Setting, select a Message Priority Configuration Set from the list.
25. Make selections from the Egress Message Throttling Configuration Set, Shared Configuration Set, Message Authenticator Configuration Set, and Ingress Status-Server Configuration Set lists.
26. Click the Suppress Connection Unavailable Alarm check box to suppress the Connection unavailable alarm.
27. Click the Suppress Connection Attempts check box to suppress the Connection attempts to a standby Peer Node, c
28. Click Test Mode check box to the test Connection.
29. Click OK, Apply, or Cancel.
30. Use the Enabling Connections procedure to enable the new connection.
    The following conditions exist:

    • Only Peer Nodes whose Dynamic attribute is NO can be selected for assignment to a connection.
    • Peer Nodes created by the Dynamic Peer Discovery feature cannot be assigned to any statically created connection.
    • CEX Configuration Sets created by the Dynamic Peer Discovery feature cannot be assigned to any statically created connection.