Contents

1   Alarm Description

The alarm is raised when a Diameter connection has failed. Missing connection between one or more Diameter peer nodes can decrease the throughput of messages between Diameter applications.

The alarm is cleared automatically when all configured connections are set up successfully.

The alarm is also cleared automatically in the following situations:

• Related peer node is disabled

  When a peer node is disabled, all vDicos, Diameter Link Failure alarms on connections related to this peer node are cleared and a new vDicos, Diameter Peer Node Disabled alarm is raised.

• Own node is disabled

  When the own node is disabled, alarms for connections (and peer nodes) related to the own node are cleared and a new vDicos, Diameter Own Node Disabled alarm is raised for the own node.

• A Diameter link is disabled

  When a Diameter link for this connection is disabled, the alarm is cleared and a new vDicos, Diameter Link Disabled alarm is raised for the connection.

2   Procedure

2.1   Handle Alarm vDicos, Diameter Link Failure

Prerequisites

• This instruction references the following documents:
  • C-Diameter Trouble Report and Support Case Writing Guideline
• No tools are required.
• The following conditions must apply:
  • The alarm is raised.
  • Diameter configuration data are correctly defined.
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

Steps

1. Contact the network administrator and verify that a connection can be built between the Own Diameter Node and the Peer Node, that is the Peer is accessible on transport level.
2. Verify that the local Diameter configuration is consistent and according to the Diameter traffic plan. Verify it against the configuration of the Peer Node.

   Navigate to the DIA-CFG-NeighbourNode MO, and print its configuration, for example:

   >dn ManagedElement=NODE06ST,XyzFunction=xyz,DIA-CFG-Application=DIA,DIA-CFG-StackContainer=abc,DIA-CFG-PeerNodeContainer=abc,DIA-CFG-NeighbourNode=node12.ericsson.com\23abc

   >show all

   Navigate to the DIA-CFG-OwnNodeConfig MO, and print its configuration, for example:

   >dn ManagedElement=NODE06ST,XyzFunction=xyz,DIA-CFG-Application=DIA,DIA-CFG-StackContainer=abc,DIA-CFG-OwnNodeConfig=abc

   >show all

   Replace the key of the DIA MOs with the stackId and hostId values of the alarm instance.

   Note:  

   Printing and verification of the configuration of the Peer Node is outside the scope of this document.

   
   
3. If the connection failure was caused by some transient network fault, the alarm is cleared automatically when the connection is set-up successfully. Is the alarm cleared?

   Yes: Proceed with Step 6.

   No: Continue with the next step.

4. In case the Peer is accessible from the Own Node and the configuration of both sides are consistent but the connection can not be established, perform data collection, refer to C-Diameter Trouble Report and Support Case Writing Guideline.
5. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
6. Job is completed.