Contents

1   Alarm Description

The alarm is raised when the relevant Diameter connection is either administratively disabled by Operation and Maintenance (OAM) or disabled by a peer.

Table 1    vDicos, Diameter Link Disabled Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Link disabled by O&M	The Diameter connection is disabled by OAM	The link is administratively disabled or a new link is created (disabled by default)	Own node	No traffic flow through the disabled link
Link disabled by peer	The Diameter connection is disabled by the peer	The link is disabled because a Disconnect Peer Request (DPR) was received	Peer

Note:  

The alarm is cleared automatically if one of the following alarms is raised:

• vDicos, Diameter Peer Node Disabled

  Alarms for connections to the peer node are cleared and a new alarm is raised for the peer node.

• vDicos, Diameter Own Node Disabled

  Alarms for connections (and peer nodes) related to the own node are cleared and a new alarm is raised for the own node.

2   Procedure

2.1   Handle Alarm vDicos, Diameter Link Disabled

Prerequisites

• This instruction references the following documents:
  • Data Collection Guideline
  • vDicos, Diameter Own Node Disabled
  • vDicos, Diameter Peer Node Disabled
• No tools are required.
• The following conditions must apply:
  • The alarm is raised.
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

Steps

1. Check the additionalText attribute of the alarm.
2. Select action according to the alarm cause indicated in the attribute text:
   • If the link is disabled by OAM, proceed with Section 2.2 Handle Reason Link Disabled by Operation and Maintenance.
   • If the link is disabled by the peer, proceed with Section 2.3 Handle Reason Link Disabled by Peer.

2.2   Handle Reason Link Disabled by Operation and Maintenance

Steps

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

   Yes: Proceed with Step 13.

   No: Continue with the next step.

2. Is the alarm raised for a connection acting as responder (incoming connection)?

   Yes: Proceed with Step 8.

   No: Continue with the next step.

3. Navigate to the DIA-CFG-Conn Managed Object (MO), 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,DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1

4. Enable the outgoing connection:

   (DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>configure

   (config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>enabled=true

   (config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>commit

5. Verify the setting:

   (DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>show enabled

   The following is an example output:

   enabled=true

6. Check the link status:

   (DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>show linkStatus

   The following is an example output:

   linkStatus=Up

7. Is the connection established?

   Yes: Proceed with Step 10.

   No: Proceed with Step 11.

8. Contact the peer node administrator to enable the connection from the peer node.
9. Proceed with Step 13.
10. Is the alarm cleared?

    Yes: Proceed with Step 13.

    No: Continue with the next step.

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

2.3   Handle Reason Link Disabled by Peer

Steps

1. Is the alarm raised for a connection acting as responder (incoming connection)?

   Yes: Continue with the next step.

   No: Proceed with Step 6.

2. Wait for the peer node to re-establish the connection and reception of a Capabilities-Exchange-Request (CER).
3. Is the alarm cleared?

   Yes: Proceed with Step 15.

   No: Continue with the next step.

4. Contact the network or peer node administrator to investigate the peer node.
5. Proceed with Step 15.
6. Navigate to the DIA-CFG-Conn MO, 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,DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1

7. Check attribute blockReason:

   (DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>show blockReason

   The following is an example output:

   blockReason="Not blocked"

8. Is attribute blockReason of the corresponding connection DPR received, cause=DoNotWantToTalkToYou, or DPR received, cause=Busy?

   Yes: Continue with the next step.

   No: Proceed with Step 11.

9. Disable and enable the connection:

   (DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>configure

   (config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>enabled=false

   (config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>commit -s

   Note:  

   The value of attribute blockReason is automatically changed to Not blocked.

   
   

   (config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>enabled=true

   (config-DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>commit

10. Verify the setting:

    (DIA-CFG-Conn=abc\23node12.ericsson.com\23conn1)>show enabled

    enabled=true

11. Wait for automatic reconnect and sending of CER.
12. Is the alarm cleared?

    Yes: Proceed with Step 15.

    No: Continue with the next step.

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