Contents

1   Alarm Description

The alarm is raised when a Diameter own node has been disabled.

2   Procedure

2.1   Handle Alarm vDicos, Diameter Own Node Disabled

Prerequisites

• This instruction references the following document:
  • Data Collection 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. Is the "Detailed Information" field of the Alarm equal to "Own Node disabled by Application"?

   Yes: No further action is required. Own Node deactivation is under Diameter Application's control.

   No: Proceed with Step 2.

2. Contact the network or node administrator. Is the node administratively disabled for maintenance reasons?

   Yes: Proceed with Step 11.

   No: Continue with the next step.

3. Navigate to the DIA-CFG-OwnNodeConfig managed object, for example:

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

4. Check the Diameter Own Node status:

   (DIA-CFG-OwnNodeConfig=abc)>show enabled

   The following is an example output:

   enabled=false

5. Is the Diameter Own Node enabled?

   Yes: Proceed with Step 8.

   No: Continue with the next step.

6. Enable the Diameter Own Node:

   (DIA-CFG-OwnNodeConfig=abc)>configure

   (config-DIA-CFG-OwnNodeConfig=abc)>enabled=true

   (config-DIA-CFG-OwnNodeConfig=abc)>commit

7. Verify the setting:

   (DIA-CFG-OwnNodeConfig=abc)>show enabled

   The following is an example output:

   enabled=true

8. Is the alarm cleared?

   Yes: Proceed with Step 11.

   No: Continue with the next step.

9. Perform data collection, refer to Data Collection Guideline.
10. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
11. Job is completed.