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.
|
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:
1.2.1 Information
The event attributes are listed in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
849346561 |
|
Source |
One of the following:
|
|
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 COM SA, AMF SI Unassigned
The event is reported by the middleware Availability Management Framework (AMF) service.
The AMF is responsible for assigning active or standby workloads to software components in the managed element through Service Units (SUs). The SUs are logical aggregations of several software components. The event is raised when a particular workload can no longer be assigned to any SU.
1.4 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.4.1 Information
| Note: |
The event is not raised if the compute resource for the active SC VM is lost. |
|
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 |

Contents