Operating Instructions 20/1543-AXM 101 04/1 Uen A

MRF Signaling IP Interface Configuration Failure
Virtual Multimedia Resource Function

Contents


1 MRF Signaling IP Interface Configuration Failure Alarm Description

The alarm is a primary alarm. The alarm is issued by the SctpEndpoint MO. The severity of the alarm is Major.

The alarm indicates that there are no free signaling IP addresses in the MO-based IP address pool.

The alarm is raised when the IP signaling interface setup fails because there are no free signaling IP addresses defined in the SignalingIpPool MO.

The possible alarm causes and fault locations are explained in the table below.
Table 1   Alarm Attributes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

No IP address is allocated to IP signaling interface.

IP signaling interface configuration fails as no IP address can be allocated.

There is no free IP address in the MO-based pool for IP signaling interfaces.

SctpEndpoint MO

No traffic is possible on the affected signaling IP interface on the VM.
The alarm attributes are listed and explained in the table below.
Table 2   Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

5308440

Managed Object Class

SctpEndpoint

Managed Object Instance

ManagedElement=1,Transport=1,SctpEndpoint=<sctpEndpointId>

Specific Problem

vMRF Signaling IP Interface Configuration Failure

Event Type

communicationsAlarms (2)

Probable Cause

CommunicationsProtocolError (305)

Additional Text

No free IP IPv4 address in Transport=<transportId>; uuid=<UUID_value>(1)

Perceived Severity

Major
(1) <uuid> is the identity of the Virtual Machine from which the alarm is issued.

2 Procedure

These procedures describe how to cease an MRF Signaling IP Interface Configuration Failure alarm.

2.1 Cease the Alarm by Adding Another IP Pool

To cease the MRF Signaling IP Interface Configuration Failure alarm, the MO-based IP pool must be extended, either by unlocking a locked IP pool, or by adding another SignalingIpPool MO so that a larger IP pool is available for signaling IP interfaces.

Note: The ranges of the pools are not required to be adjacent, but the subnet mask and gateway of all pools belonging to the same network interface need to be the same.

Prerequisites

  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

Steps

  1. List all the IP pools by issuing the following command:.

    >show -v -r ManagedElement=1,Transport=1

    Check the output for any SignalingIpPool MOs with attribute ipPoolState LOCKED

    • If there are locked IP pools, consider unlocking them by changing the attribute ipPoolState to UNLOCKED.

      This triggers the allocation of free IP addresses from that pool.

      If the alarm is still active, continue with the next step.

    • If there are no locked IP pools, continue with the next step.

  2. In the MOM, navigate to ManagedElement=1,Transport=1:
    >ManagedElement=1,Transport=1
  3. Enter Config mode:
    (ManagedElement=1,Transport=1)>configure
  4. Create a SignalingIpPool MO for the signaling network:
    (config-ManagedElement=1,Transport=1)>SignalingIpPool=1
  5. Define the starting value of the IP pool range:
    (config-ManagedElement=1,Transport=1,SignalingIpPool=1)>ipPoolRangeStart=<IP_Pool_Start_Address>
    Note: The IP pool range starting value can only be an IPv4 address.
  6. Define the ending value of the IP pool range:
    (config-ManagedElement=1,Transport=1,SignalingIpPool=1)>ipPoolRangeEnd=<IP_Pool_End_Address>
    Note: The IP pool range ending value can only be an IPv4 address.
  7. Add values for the following attributes of the SignalingIpPool MO:

    • gatewayAddress

    • ipPoolState

    • subnetMaskLength

  8. Commit the changes:
    (config-ManagedElement=1,Transport=1,SignalingIpPool=1)>commit
Legal |© Ericsson AB 2019