Contents

1   Introduction

This document describes the License Management, Capacity Usage Threshold Reached alarm and provides instructions for fault management.

Note:  

This alarm is not applicable to Network License Server (NeLS) deployments.

1.1   Alarm Description

License Management, Capacity Usage Threshold Reached is raised when the number of reserved tokens in a capacity license approaches the licensedCapacityLimit.

This primary alarm is issued by the ManagedElement=1,SystemFunctions=1,Lm=1,LicenseId=<licenseId> Managed Object (MO).

Possible alarm causes and fault locations are explained in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
351	License Management, Capacity Usage Threshold Reached	Requested capacity has exceeded the capacityAlarmThreshold or the licensedCapacityLimit.	LM Server	Requested capacity may be unavailable.

The following consequences are expected if the alarm condition is not resolved:

• The application may not be able to use additional instances of the licensed feature.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
activeSeverity	WARNING: The reserved capacity of the license identified by the CapacityKey.capacityKeyId has passed the warning threshold defined by the Lm.capacityAlarmThreshold parameter but is still below the total licensed capacity. MAJOR: The CapacityKey.licensedCapacityLimit of the license identified by the capacityKeyId has been reached.
additionalInfo	Not Applicable
additionalText	"Capacity usage threshold reached"
eventType	QUALITYOFSERVICEALARM
lastEventTime	A time stamp of the last alarm update, such as an alarm status change or severity change.
majorType	193
minorType	393219
originalAdditionalText	Content of the additionalText field when the alarm was raised.
originalEventTime	Time stamp when the alarm was raised.
originalSeverity	Value of the activeSeverity level when the alarm was raised.
probableCause	351 (x733 Threshold Crossed)
sequenceNumber	The notification identity for this object instance. It is not the same as the fmAlarmId since multiple notifications may be sent for one alarm instance. This value changes for every notification (such as a severity change or alarm clear).
source	ManagedElement=1,SystemFunctions=1,Lm=1,License=<licenseId>
specificProblem	License Management, Capacity Usage Threshold Reached

1.2   Prerequisites

This section lists the prerequisite documents, tools, and conditions for the alarm handling procedure.

1.2.1   Documents

Review the following documents before starting the procedure:

• Personal Health and Safety Information (Reference [1])
• System Safety Information (Reference [2])
• The User Guide for your LM deployment:
  • "Installing License Key Files" in the LM User Guide for Sentinel RMS (Reference [3])
  • "Installing License Key Files" in the LM User Guide for ELIM (Reference [4])
• "Configuration Management Using CLI" in the COM Management Guide for your version of the product software.

1.2.2   Tools

Ensure that the following tools are available before starting the procedure:

• Element Management System (for example: OSS)
• Ericsson Command-Line Interface (ECLI)

For more information on these tools, refer to the documentation for your version of the product software.

1.2.3   Conditions

Ensure that the following conditions are met before starting the procedure:

• Know the IP address of the blade where ECLI is running.
• Have the proper authority to handle configuration management of the Network Elements.
• Be familiar with basic Unix commands.

2   Procedure

This section describes the alarm handling procedure.

2.1   Analyzing the Alarm

The License Management, Capacity Usage Threshold Reached alarm clears automatically when the reserved capacity drops below the Lm.capacityAlarmThreshold minus a hysteresis value defined by the Lm.capacityAlarmHysteresis configuration parameter. For more information about Lm.capacityAlarmThreshold and Lm.capacityAlarmHysteresis, refer to "Configuration Management" in the User Guide for your LM deployment.

• LM User Guide for Sentinel RMS (Reference [3])
• LM User Guide for ELIM (Reference [4])

If the alarm persists, or if it is triggered frequently, adjusting the LM configuration, ordering a new license with higher capacity, or both may be required.

To determine the fault location and cause:

1. In ECLI, navigate to the Lm MO, for example:

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

2. Show the current percentage value of Lm.capacityAlarmHysteresis:

   (Lm=1)>show capacityAlarmHysteresis

3. Show the current percentage value of Lm.capacityAlarmThreshold:

   (Lm=1)>show capacityAlarmThreshold

4. Show information about the affected capacity license:

   (Lm=1)>show --moc CapacityKey --condition (keyId=="<licenseId>")

   Where <licenseId> is the license identify from the alarm source. For example:

   (Lm=1)>show --moc CapacityKey --condition (keyId=="FAT1020383")
   CapacityKey=1
      capacityUnit="token"
      expiration="2016-10-1"
      grantedCapacityLevel=900
      keyId="FAT1020383"
      licensedCapacityLimitReached=false
      name="FAT1020383"
      productType=""
      validFrom="2014-3-5"
      version="1.0"
      licensedCapacityLimit
         value=1000
   

5. Provide the LM configuration and license information for capacity planning.
   • After obtaining a work order to adjust the LM configuration, refer to Section 2.2.
   • After obtaining a work order for a new license with higher capacity, refer to Section 2.3.

2.2   Actions to Adjust the LM Configuration

After obtaining a work order to adjust the LM configuration:

1. In ECLI, navigate to the Lm MO, for example:

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

2. Verify that Lm.capacityAlarmHysteresis has the proper value:

   (Lm=1)>show capacityAlarmHysteresis

3. If necessary, set a new percentage value for Lm.capacityAlarmHysteresis:
   1. (Lm=1)>configure
   2. (config-Lm=1)>capacityAlarmHysteresis=<n>

      Where <n> is the new parameter value.

   3. (config-Lm=1)>commit
4. Verify that Lm.capacityAlarmThreshold has the proper value:

   (Lm=1)>show capacityAlarmThreshold

5. If necessary, set a new percentage value for capacityAlarmThreshold:
   1. (Lm=1)>configure
   2. (config-Lm=1)>capacityAlarmThreshold=<n>

      Where <n> is the new parameter value.

   3. (config-Lm=1)>commit
6. Check the alarm status.

   If the alarm is still active, or if it is triggered frequently, a new license with higher capacity may be required.

2.3   Actions to Order and Install a New License Key File

After obtaining a work order for a new license with higher capacity:

1. If necessary, contact your Ericsson supplier and order a new license key file with the required changes.
2. Install the new license key file.

   For more information on installing a license key file, refer to "Installing License Key Files" in the User Guide for your LM deployment.

   • LM User Guide for Sentinel RMS (Reference [3])
   • LM User Guide for ELIM (Reference [4])
3. After installing the license key file, check the alarm status.
4. If the alarm is still active, navigate to the Lm MO in ECLI, for example:

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

5. Trigger an extra refresh of the license inventory to ensure that the license changes are applied:

   (Lm=1)>refreshLicenseInventory

   The system returns true if the action was executed successfully.

6. Verify that LM has the latest license information by checking the lastLicenseInventoryRefresh time stamp:

   (Lm=1)>show lastLicenseInventoryRefresh

   A recent time stamp indicates a successful update.

7. Check the alarm status.

   If the alarm is still active, consult the next level of maintenance support. Further actions are outside the scope of this instruction.

Reference List

[1] Personal Health and Safety Information, 12446-2885 Uen
[2] System Safety Information, 12446-2886 Uen
[3] LM User Guide for Sentinel RMS, 1/1553-APR 901 0503/6 Uen
[4] LM User Guide for ELIM, 2/1553-APR 901 0503/6 Uen