Editing a Connection Configuration Set

Use this task to edit an existing Connection Configuration Set.

When the Connection Configuration Sets page opens, the fields are populated with the currently configured values.

If the selected Connection Configuration Set is being used by a Local Node, any changes to the selected Connection Configuration Set will not take effect for Peer-initiated connections until the next time the Peer Node connects to the Local Node.

The Connection Configuration Set Name cannot be edited.

Note: You must disable all Connections that use a particular Connection Configuration Set before you can edit it. See Disabling Connections.

Changes to the Connection Configuration Set take effect after the changes are saved and the Connections that refer to the changed Connection Configuration Set are set to the "Enabled" Admin state.

  1. Select Diameter > Configuration > Configuration Sets > Connection Configuration Sets.

    The Connection Configuration Sets page appears.

  2. Select the Connection Configuration Set you want to edit.
  3. Click Edit.

    The Connection Configuration Sets [Edit] page appears.

  4. Update the relevant fields.

    For information about each field, see Connection Configuration Set elements.

  5. Click:
    • OK to save the data and return to the Connection Configuration Sets page.
    • Apply to save the data and remain on this page.
    • Cancel to return to the Connection Configuration Sets page without saving any changes.

    If OK or Apply is clicked and any of the following conditions exist, an error message appears:
    • The selected Connection Configuration Set no longer exists; it has been deleted by another user
    • Any field is empty (no value was entered)
    • The value in any field is not valid or is out of range
    • Under the SCTP Options tab, the Retransmit Maximum Timeout is less than the Retransmit Minimum Timeout
    • Under the SCTP Options tab, the Number of Retransmits Triggering Path Failure is greater than the Number of Retransmits Triggering Association Failure
    • At least one connection that is using this Connection Configuration Set is not in the "Disabled" Admin State

Parent topic: Connection Configuration Set configuration