Operating Instructions 12/1543-AXM10104/1 Uen L

MRF IP Auto-Configuration Failure
Virtual Multimedia Resource Function

Contents


1 Overview

This instruction concerns alarm handling.

1.1 MRF IP Auto-Configuration Failure Alarm Description

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

The alarm is raised when IP auto-configuration of a media IP address in a VM fails, for example, if the DHCP client cannot obtain, renew, or rebind an IP address, or if the lease time of the IP address ends.

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

Alarm Cause

Alarm Cause

Fault Reason

Fault Location

Impact

Stateless IPv6 autoconfiguration failed.

The vMRF media interface has not received an IP address.

If no IPv6 addresses are configured statically for media interfaces, vMRF attempts to autoconfigure the IPv6 addresses. If autonomous flag is set in received Router Advertisement, vMRF invokes IPv6 Stateless Address Autoconfiguration for media interfaces, according to RFC 4862. Otherwise, vMRF initiates DHCP discovery in network. Thus in case autoconfiguration fails, this alarm is raised with any DHCP-related fault reason.
One of the following components:

  • Network router

  • Network

  • Cloud environment

No user plane traffic is possible on the affected media interface. If all media interfaces are down, MTAS is instructed not to offer new sessions to the VM connected to the media interface while the problem persists. Ongoing calls are not affected.
The following is the consequence for the VM if the alarm is not ceased:

  • No user plane traffic is possible on the media interface with the specified IP version.

The alarm attributes are listed and explained in Table 2.

Table 2   Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

5308426

Managed Object Class

MrfMediaInterface

Managed Object Instance

ManagedElement=1,MediaResourceFunction=1,MrfResource=1, MrfInstance=<MrfInstanceId>,MrfMediaInterface=<MrfMediaInterfaceId>

Specific Problem

MRF IP Auto-Configuration Failure

Event Type

communicationsAlarms (2)

Probable Cause

CommunicationsProtocolError (305)

Additional Text

DHCP Server <IP_address>, <cause>(1), State: <state>; uuid: <uuid>(2)

Perceived Severity

major (4)
(1) <cause> is the fault reason from .
(2) <uuid> is the identity of the Virtual Machine from which the alarm is issued.

2 Cease the MRF IP Auto-Configuration Failure Alarm

The following procedure describes how to cease an MRF IP Auto-Configuration Failure alarm.

Prerequisites

  • You have logged into the node.

Steps

  1. Check if the network router supports the RFC 4862 standard.
    Option Description

    If RFC 4862 is supported by the network router:

    Enable stateless IPv6 autoconfiguration for the network in the router.

    If RFC 4862 is not supported by the network router:

    Redeploy the VNF from a HOT or OVF file which supports static IP address allocation.

  2. If the alarm does not cease, consult the next level of maintenance support. Further actions are outside the scope of this instruction.

2.1 Perform Concluding Routines

Steps

  1. Make a report.
  2. The job is completed.
Legal |© Ericsson AB 2016–2019