1 Alarm Description
The alarm is raised when a Diameter own node has been disabled, either administratively or by the system because of a fault.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
Diameter own node disabled |
The Diameter own node has been disabled |
Diameter own node disabled |
Own node configuration |
No service provided by the own node |
2 Procedure
2.1 Handle Alarm vDicos, Diameter Own Node Disabled
Prerequisites
- This instruction references the following document:
- No tools are required.
- Tthe following conditions must apply:
- The alarm is raised.
- An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
Steps
- Contact the network or node administrator. Is the node
administratively disabled for maintenance reasons?
Yes: Proceed with Step 10.
No: Continue with the next step.
- 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
- Check the Diameter Own Node status:
(DIA-CFG-OwnNodeConfig=abc)>show enabled
The following is an example output:
enabled=false
- Is the Diameter Own Node enabled?
Yes: Proceed with Step 7.
No: Continue with the next step.
- Enable the Diameter Own Node:
(DIA-CFG-OwnNodeConfig=abc)>configure
(config-DIA-CFG-OwnNodeConfig=abc)>enabled=true
(config-DIA-CFG-OwnNodeConfig=abc)>commit
- Verify the setting:
(DIA-CFG-OwnNodeConfig=abc)>show enabled
The following is an example output:
enabled=true
- Is the alarm cleared?
Yes: Proceed with Step 10.
No: Continue with the next step.
- Perform data collection, refer to Data Collection Guideline.
- Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
- Job is completed.

Contents