1 Events

This section describes the events that can be generated in vMRF.

1.1 MRF H.248 Link Recovered after Temporary Outage

The MRF H.248 Link Recovered after Temporary Outage event is related to signaling link state changes between vMRF and MTAS.

In case an already established SCTP transport link loss is detected, a 30 second timer is started. If the link recovers before the timer expires, the MRF H.248 Link Recovered after Temporary Outage event is reported. The timer is then cancelled. Ongoing traffic is not impacted. If the link does not recover before the timer ends, the MRF H.248 Link Unavailable alarm is raised.

1.1.1 Information

The event attributes are listed in Table 1.

Table 1 Event Attributes
Attribute Name	Attribute Value
Major Type	193
Minor Type	5308420
Managed Object Class	MrfH248Interface
Managed Object Instance	ManagedElement=1,MediaResourceFunction=1,MrfH248Control=1,MrfH248Interface= <MrfH248InterfaceId>
Specific Problem	MRF H.248 Link Recovered after Temporary Outage
Event Type	Other (1)
Probable Cause	Indeterminate (0)
Additional Text	SCTP association recovered
Perceived Severity	Warning (6)
isStateful	false

1.2 COM SA, CLM Cluster Node Unavailable

The COM SA, CLM Cluster Node Unavailable event is related to failed communication with a connected node. The event is raised by the middleware Cluster Membership (CLM) service.

The event is reported in the following cases:

The CLM has lost contact with a node and has been unable to re-establish contact for 15 minutes.
After a cluster start, the CLM has been unable to establish contact with a node for 15 minutes.

1.2.1 Information

The event attributes are listed in Table 2.

Table 2 Event Attributes
Attribute Name	Attribute Value
Major Type	193
Minor Type	849346561
Source	One of the following: safNode=<PL_name>,safCluster=myClmCluster safNode=<SC_name>,safCluster=myClmCluster
Specific Problem	COM SA, CLM Cluster Node Unavailable
Event Type	Other (1)
Probable Cause	x736UnspecifiedReason (418)
Additional Text	CLM Cluster Node Unavailable
Perceived Severity	Warning (6)
isStateful	false

Note:

Depending on the system configuration, the uuid for the affected node can be appended to Additional Text.

1.3 MRF Compute Resource Lost

The MRF Compute Resource Lost event is raised when a compute resource (that is, a VM) leaves the VNF cluster, and the administrativeState attribute of the affected MrfInstance MO is other than LOCKED, that is, either SHUTTINGDOWN or UNLOCKED. The event is raised, for example, when a VM, that is not in LOCKED state, restarts. The event indicates that traffic on affected VM is lost.

The notification of a lost VM, is handled by the active SC VM. Therefore, the loss of the active SC VM of the cluster does not trigger the event.

1.3.1 Information

The event attributes are listed in Table 3.

Note:

The event is not raised if the compute resource for the active SC VM is lost.

Table 3 Event Attributes
Attribute Name	Attribute Value
Major Type	193
Minor Type	5308432
Managed Object Class	MediaResourceFunction
Managed Object Instance	ManagedElement=1,MediaResourceFunction=1
Specific Problem	MRF Compute Resource Lost
Event Type	PROCESSINGERRORALARM (4)
Probable Cause	underlayingResourceUnavailable (165)
Additional Text	Compute resource has been lost
Perceived Severity	Warning (6)
isStateful	false

Copyright	© Ericsson AB 2018, 2019. 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.
Trademarks	All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.