License Management, Capacity Usage Threshold Reached

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 application is possibly unable to use additional instances of the licensed feature.

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

Table 1    Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

The application is possibly unable to use additional instances of the licensed feature

The number of reserved tokens in a capacity license approaches the value of attribute licensedCapacityLimit or are above the value of attribute capacityAlarmThreshold

The requested capacity has exceeded the value of attribute capacityAlarmThreshold or licensedCapacityLimit

License server

The requested capacity is possibly unavailable

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

393219

Managed Object Class

Lm

Managed Object Instance

ManagedElement=<node_name>,SystemFunctions=1,Lm=1,License=<License Type>

Specific Problem

License Management, Capacity Usage Threshold Reached

Event Type

qualityOfServiceAlarm (3)

Probable Cause

x733ThresholdCrossed (351)

Additional Text

Capacity usage threshold reached

Perceived Severity

One of the following:


  • major (4) – The value of attribute licensedCapacityLimit of the license identified by attribute capacityKeyId is reached.

  • warning (6) – The reserved capacity of the license identified by attribute capacityKeyId has passed the warning threshold defined by attribute capacityAlarmThreshold, but is still below the total licensed capacity.

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

This section describes the procedure to follow when this alarm is received.

Do the following:

  1. Verify the license expiration date, refer to View License Information.
  2. If necessary, contact the Ericsson supplier to order an entitlement containing the necessary licenses.
  3. Navigate to the Lm MO, for example:

    >dn ManagedElement=NODE06ST,SystemFunctions=1,Lm=1

  4. Perform a manual refresh of the license inventory to ensure that the license changes are applied:

    (Lm=1)>refreshLicenseInventory

    The system returns true if the action was successful.

  5. Verify that the license inventory has been synchronized with the Arwa server by checking the time stamp:

    (Lm=1)>show lastLicenseInventoryRefresh

    The following is an example output:

    lastLicenseInventoryRefresh="2015-10-12T00:00:00"

    A recent time stamp indicates a successful update.

  6. Is the alarm cleared?

    Yes: Proceed with Step 9.

    No: Continue with the next step.

  7. Perform data collection, refer to Data Collection Guideline.
  8. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
  9. 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.

    License Management, Capacity Usage Threshold Reached