Operating Instructions 3/1543-AXM10104/1 Uen L
[ Topics hidden with current filter selection ]

MRF IP Address Collision
Virtual Multimedia Resource Function

Contents


1 Overview

This instruction concerns alarm handling.

1.1 MRF IP Address Collision Alarm Description

This alarm is a primary alarm. The alarm is issued by the MrfMediaInterface Managed Object (MO). The severity of the alarm is Major.

The MRF IP Address Collision alarm indicates that the IP address allocated to a MRF IP interface is already used in the network. The MRF IP interface that issued the alarm cannot be used while the alarm is active. The collision can occur in the following cases:

  • A MRF media IP interface is activated with an IP address already used in the network.

  • The IP interface of another host in the network is activated with the IP address already used by a MRF media IP interface.

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

Cause

Description

Reason

Location

Impact

MRF IP Address Collision,

media IP interface

An IP address collision on the MRF media IP interface is detected.

Configuration error

IP pool in cloud, vMRF deployment parameter

The MTAS is notified about the situation and it releases all ongoing calls on the MRF media IP interface (IPv4 or IPv6) the collision occurred on. The interface cannot be used for traffic while the alarm is active.

Peer IP interface
The alarm is ceased in the following case:

  • The alarm is ceased when the IP address of either the MRF media IP interface or the peer IP interface is reconfigured, and no address collision is detected with the new IP address.

The following are the consequences for the node if the alarm is not solved:

  • While the alarm is active, MRF capacity is degraded since the affected VM cannot be used for either IPv4 or IPv6 traffic depending on the type of the interface that raised the alarm. The MTAS is notified about the situation.

Table 2   Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

5308417

Managed Object Class

MrfMediaInterface

Managed Object Instance

ManagedElement=<node_name>,MediaResourceFunction=1, MrfResource=1,MrfInstance=<mrf_instance>,MrfMediaInterface=<mrf_media_ip_interface>

Specific Problem

MRF IP Address Collision

Event Type

communicationsAlarm (2)

Probable Cause

configurationOrCustomisationError (159)

Additional Text

Detected IP address collision in MRF media IP interface; uuid:<uuid>(1)

Perceived Severity

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

2 Procedure

The following procedures describe how to cease a MRF IP Address Collision alarm.

2.1 Resolve IP Address Collision in Deployments with Manual IP Allocation

  1. Power off the VM.

    For more information, see the relevant VMware documentation.

    Note: Shutting down a VM can impact the traffic.

    To minimize the traffic impact, lock the VM to be deleted from the cluster. Lock the MrfInstance MO that represents the VM.

  2. Correct the colliding IP addresses in VM Guest Properties.
  3. Power on the VM.
  4. If the alarm has ceased, continue with Perform Concluding Routines.

2.2 Alarm Resolution in Deployments with Cloud Pool based IP Allocation

2.2.1 Resolve IP Address Collision in OpenStack and CEE Deployments with Cloud Pool based IP Allocation

  1. Check the relevant IP allocation settings based on fault location to see if it allocates a proper IP address to the MRF media IP interface. Make sure that static IP addresses reserved by other peers on the network are excluded from the IP address pool.
  2. Check the details of the MRF IP Address Collision alarm and note the ipAddress attribute of the MrfMediaInterface MO for the IP address that caused the address collision.
  3. Reconfigure the IP address pool so that it does not contain the IP address that caused the collision.
  4. Scale in the VM from which the alarm is issued.

    For more information on scaling the affected VM, see vMRF Configuration Management or the relevant VNF Life Cycle Management documentation.

  5. Scale out the VNF to restore capacity.
  6. If the alarm has ceased, continue with Perform Concluding Routines.

2.2.2 Resolve IP Address Collision in VMware vCloud Director Deployments with Cloud Pool based IP Allocation

  1. Check the relevant IP allocation settings based on fault location to see if it allocates a proper IP address to the MRF media IP interface. Make sure that static IP addresses reserved by other peers on the network are excluded from the IP address pool.
  2. Check the details of the MRF IP Address Collision alarm and note the ipAddress attribute of the MrfMediaInterface MO for the IP address that caused the address collision.
  3. Reconfigure the IP address pool so that it does not contain the IP address that caused the collision.
  4. Scale in the VM from which the alarm is issued.

    For more information on scaling the affected VM, see vMRF Configuration Management or the relevant VNF Life Cycle Management documentation.

  5. Scale out the VNF to restore capacity.
  6. If the alarm has ceased, continue with Perform Concluding Routines.

2.2.3 Resolve IP Address Collision in VMware vSphere Deployments with Cloud Pool based IP Allocation

  1. Check the relevant IP allocation settings based on fault location to see if it allocates a proper IP address to the MRF media IP interface. Make sure that static IP addresses reserved by other peers on the network are excluded from the IP address pool.
  2. Check the details of the MRF IP Address Collision alarm and note the ipAddress attribute of the MrfMediaInterface MO for the IP address that caused the address collision.
  3. Reconfigure the IP address pool so that it does not contain the IP address that caused the collision.
  4. Power off the VM from which the alarm is issued.

    Powering off the VM releases its IP address.

    Note: Powering off a VM can impact the traffic.

    To minimize the traffic impact, lock the VM to be deleted from the cluster. Lock the MrfInstance MO that represents the VM.

  5. Power on the VM from which the alarm was issued.

    When the VM is powered on, it receives an IP address from the reconfigured IP address pool.

  6. If the alarm has ceased, continue with Perform Concluding Routines.

2.3 Resolve IP Address Collision by Reconfiguring Peer IP Interface

The alarm is ceased if the colliding IP address is removed from a peer IP interface in the network. A typical scenario for this remedy is that the IP address has been used without collision for some time in vMRF before the alarm was issued.

Steps

  1. Provide the unit responsible for the other network element with the information needed to reconfigure IP address on the peer IP interface.

    Make sure that no static IP address is reserved by other peers on the network and the vMRF IP address pool at the same time.

  2. Wait until the new IP address is recognized as unique in the network, and the alarm is ceased. Continue with Perform Concluding Routines.

2.4 Perform Concluding Routines

Steps

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