eVIP, IKE Distribution Not Possible

Contents

1Introduction
1.1Alarm Description
1.2Prerequisites

2
Procedure

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is raised when the distribution of the Internet Key Exchange (IKE) processes cannot be resolved and there are no available blades for every IKE instance.

The IKE process is used to process the key exchange in case of IP Security communication.

The possible alarm causes and fault locations are explained in Table 1.

Table 1    Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

Faulty configuration

The configuration is faulty

Faulty configuration

Faulty configuration in the Managed Element

Starting the IKE processes with the current eVIP configuration cannot be done

Faulty node in the cluster

The node in the cluster is faulty

Faulty node in the cluster

Node in cluster

Insufficient available or running nodes and the IKE processes cannot be started

Note:  
The alarm can appear as a result of an installation.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

2129526786

Managed Object Class

EvipAlb

Managed Object Instance

ManagedElement=<node_name>,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=<alb_name>

Specific Problem

eVIP, IKE Distribution Not Possible

Event Type

communicationsAlarm (2)

Probable Cause

x736UnspecifiedReason (418)

Additional Text

Fault in IKE distribution

Perceived Severity

major (4)

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

This instruction references the following documents:

1.2.2   Tools

No tools are required.

1.2.3   Conditions

Before starting this procedure, ensure that the following conditions are met:

2   Procedure

Do the following:

  1. Is alarm COM SA, CLM Cluster Node Unavailable also raised?

    Yes: Alarm eVIP, IKE Distribution Not Possible can be caused by a faulty node in the cluster. Follow the instructions in COM SA, CLM Cluster Node Unavailable and then continue with the next step.

    No: Proceed with Step 3.

  2. Is alarm eVIP, IKE Distribution Not Possible cleared?

    Yes: Confirm that the alarm does not reappear. Proceed with Step 36.

    No: The cause is a faulty configuration. Continue with the next step.

Check Latest Configuration Changes

  1. Check the latest configuration changes.

    The likely cause is that a reconfiguration event violated the listed rules of IKE distribution.

    • Only one IKE instance can run on a payload blade.
    • Exactly one or zero IKE instance must run in each Abstract Load Balancer (ALB).

    These rules means that there must be at least as many payload blades as there are ALBs in the system.

Check Target Pool Configuration

Target pools limited to a few payload blades, processors, or targets in an Abstract Load Balancer (ALB) can violate the listed rules in Step 3.

  1. Check the number of ALBs to determine the number of IKE processes, for example:

    >show ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1

    The following example output shows that two ALBs are configured and it means that two IKE processes are to be started:

    EvipAlbs=1
   EvipAlb=alb_0
   EvipAlb=alb_1
  2. Check the ALB configuration one by one to determine where the IKE process can be started within an ALB, for example:
    1. >show -r ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=alb_0,EvipTargetPools=1

      The following is an example output:

      EvipTargetPools=1
   EvipTargetPool=SCs_rr
      distributionMethod="round_robin"
      stickyGroup="no"
      udpStateless="no"
      EvipPayload=6
   EvipTargetPool=sticky-SCs_rr
      distributionMethod="round_robin"
      stickinessTimeout="300"
      stickyGroup="yes"
      udpStateless="no"
      EvipPayload=6
    2. >show -r ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=alb_1,EvipTargetPools=1

      The following is an example output:

      EvipTargetPools=1
   EvipTargetPool=SCs_rr
      distributionMethod="round_robin"
      stickyGroup="no"
      udpStateless="no"
      EvipPayload=6
   EvipTargetPool=sticky-SCs_rr
      distributionMethod="round_robin"
      stickinessTimeout="300"
      stickyGroup="yes"
      udpStateless="no"
      EvipPayload=6

    The two examples show that only node 6 is available for two ALBs; alb_0 and alb_1. The IKE distribution is not possible with the configuration in these examples.

Configure New Target Pools or Add One or More Nodes to Existing Target Pools

Attention!

Risk of system malfunction or traffic disturbance.

The target pool plays a central role on traffic handling. If you are unfamiliar with eVIP configuration, consult with next level of maintenance support.

Step 6 through Step 29 show how to add payloads 1 and 5 to target pools in alb_0 and payload 4 to alb_1.

  1. Navigate to the EvipTargetPool Managed Object (MO) for alb_0, for example:

    >dn ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=alb_0,EvipTargetPools=1,EvipTargetPool=SCs_rr

  2. Enter Config mode:

    (EvipTargetPool=SCs_rr)>configure

  3. Add a payload, for example:

    (config-EvipTargetPool=SCs_rr)>EvipPayload=1

  4. Navigate to the EvipTargetPool MO:

    (config-EvipPayload=1)>up

  5. Commit the setting:

    (config-EvipTargetPool=SCs_rr)>commit

  6. Verify the setting:

    (EvipTargetPool=SCs_rr)>show EvipPayload

    The following is an example output:

    EvipPayload=1
  7. Navigate to the second EvipTargetPool MO, for example:

    (EvipTargetPool=SCs_rr)>up

    (EvipTargetPools=1)>EvipTargetPool=sticky-SCs_rr

  8. Enter Config mode:

    (EvipTargetPool=sticky-SCs_rr)>configure

  9. Add a payload, for example:

    (config-EvipTargetPool=sticky-SCs_rr)>EvipPayload=5

  10. Navigate to the EvipTargetPool MO:

    (config-EvipPayload=5)>up

  11. Commit the setting:

    (config-EvipTargetPool=sticky-SCs_rr)>commit

  12. Verify the setting:

    (EvipTargetPool=sticky-SCs_rr)>show EvipPayload

    The following is an example output:

    EvipPayload=5
  13. Navigate to the EvipTargetPool MO for alb_1, for example:

    (EvipTargetPool=sticky-SCs_rr)>dn ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=alb_1,EvipTargetPools=1,EvipTargetPool=SCs_rr

  14. Enter Config mode:

    (EvipTargetPool=SCs_rr)>configure

  15. Add a payload, for example:

    (config-EvipTargetPool=SCs_rr)>EvipPayload=4

  16. Navigate to the EvipTargetPool MO:

    (config-EvipPayload=4)>up

  17. Commit the setting:

    (config-EvipTargetPool=SCs_rr)>commit

  18. Verify the setting:

    (EvipTargetPool=SCs_rr)>show EvipPayload

    The following is an example output:

    EvipPayload=4
  19. Navigate to the second EvipTargetPool MO for alb_1, for example:

    (EvipTargetPool=SCs_rr)>up

    (EvipTargetPools=1)>EvipTargetPool=sticky-SCs_rr

  20. Enter Config mode:

    (EvipTargetPool=sticky-SCs_rr)>configure

  21. Add a payload, for example:

    (config-EvipTargetPool=sticky-SCs_rr)>EvipPayload=4

  22. Navigate to the EvipTargetPool MO:

    (config-EvipPayload=4)>up

  23. Commit the setting:

    (config-EvipTargetPool=sticky-SCs_rr)>commit

  24. Verify the setting:

    (EvipTargetPool=sticky-SCs_rr)>show EvipPayload

    The following is an example output:

    EvipPayload=4

Check ALB Configuration

  1. Check the ALB configuration one by one to determine where the IKE process can be started, for example:
    1. (EvipTargetPool=sticky-SCs_rr)>show -r ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=alb_0,EvipTargetPools=1

      The following output example shows that eVIP can start the IKE process on payload nodes 1, 5, and 6 in ALB alb_0:

      EvipTargetPools=1
   EvipTargetPool=SCs_rr
      distributionMethod="round_robin"
      stickyGroup="no"
      udpStateless="no"
      EvipPayload=1
      EvipPayload=6
   EvipTargetPool=sticky-SCs_rr
      distributionMethod="round_robin"
      stickinessTimeout="300"
      stickyGroup="yes"
      udpStateless="no"
      EvipPayload=5
      EvipPayload=6
    2. (EvipTargetPool=sticky-SCs_rr)>show -r ManagedElement=NODE06ST,Transport=1,Evip=1,EvipAlbs=1,EvipAlb=alb_1,EvipTargetPools=1

      The following output example shows that eVIP can start the IKE process on payload nodes 4 and 6 in ALB alb_1:

      EvipTargetPools=1
   EvipTargetPool=SCs_rr
      distributionMethod="round_robin"
      stickyGroup="no"
      udpStateless="no"
      EvipPayload=4
      EvipPayload=6
   EvipTargetPool=sticky-SCs_rr
      distributionMethod="round_robin"
      stickinessTimeout="300"
      stickyGroup="yes"
      udpStateless="no"
      EvipPayload=4
      EvipPayload=6

    If payload nodes 1, 4, 5, and 6 all are running or available, a possible IKE distribution is that two IKE processes are started on payload nodes 1 and 5.

Check Available Payload Nodes

  1. Check the available payload nodes to determine where the IKE process can be started, for example:

    >ssh -l <user> SC-1

    >ssh -l <user> PL-4

    >ssh -l <user> PL-5

    >ssh -l <user> PL-6

  2. Can you log on to the nodes?

    Yes: The nodes are running and IKE distribution can be done. Continue with the next step.

    No: Proceed with Step 34.

  3. Is the alarm cleared?

    Yes: Confirm that the alarm does not reappear. Proceed with Step 36.

    No: Continue with the next step.

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


Copyright

© Ericsson AB 2015. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    eVIP, IKE Distribution Not Possible