Operating Instructions 2/1543-AXM10104/1 Uen M

MRF H.248 Link Unavailable
Virtual Multimedia Resource Function

Contents


1 Procedure

The following procedure describes how to cease a MRF H.248 Link Unavailable alarm.

1.1 Analyzing the Alarm

Steps

  1. See details for the alarm vMRF H.248 Link Unavailable. Check the additional info field of the alarm.

1.2 Clear an Alarm when SCTP Association Is Down

Steps

  1. Identify the issuing MO of the alarm.
  2. Based on the issuing MO, continue with one of the following sections:

1.2.1 Local Endpoint Configuration Fault

Steps

  1. Check the localIpAddress attribute of the SctpEndpoint MO. If the attribute has no IP address, check the DHCP server to see if it allocates a proper IP address.
  2. Check the signalingLocalPort attribute of the MrfH248ControlMTAS for every SctpEndpoint MO.
  3. Reconfigure the signalingLocalPort attribute of the MrfH248Control MO if needed. To do this, lock all the associated MrfH248Interface MO. The value specifies the MOs before the procedure, by setting the value of the attribute, administrativeState to LOCKED. Unlock them after the reconfiguration, by setting the value of the attribute, administrativeState to UNLOCKED.
    Note: By locking the MrfH248Interface MO, the alarm will be automatically ceased and all traffic towards the MTAS will stop.
  4. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction. Continue to Perform Concluding Routines.

1.2.2 Remote Endpoint Configuration Fault

Steps

  1. Check the remotePortNumber and remoteIpAddress attributes of the MrfH248Interface MO. These are restricted values and cannot be reconfigured without deleting and recreating the MO.
  2. Ensure that the IP address and port defined in the vMRF VNF match with IP address and port defined in the MTAS. If the alarm has ceased, continue to Perform Concluding Routines.
  3. To reconfigure the attributes mentioned in Step 1, the MrfH248Interface MO must be locked, deleted, and created again. If the alarm has ceased, continue to Perform Concluding Routines.
    Note: By locking the MrfH248Interface MO, the alarm will be automatically ceased and all traffic towards MTAS will stop.
  4. If the alarm is issued again, consult the next level of maintenance support. Further actions are outside the scope of this instruction. Continue to Perform Concluding Routines.

1.3 Clear an Alarm when No ServiceChange Response Is Received from MTAS

Steps

  1. Ensure that the IP address and port defined in the vMRF VNF match with IP address and port defined in MTAS. If the alarm has ceased, continue to Perform Concluding Routines.
  2. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction. Continue to Perform Concluding Routines.

1.4 Clear an Alarm when Protocol Negotiation Failed

Steps

  1. If the additional info indicated a H.248 profile or version mismatch, confirm that the MTAS has the correct H.248 version.
  2. If the additional info described a H.248 error code received from MTAS, contact the MTAS operators with the error code.
  3. After all possible procedures on MTAS side are done, view the currently active alarms in the alarm list.
  4. If the alarm is still active, lock the MrfH248Interface MO that issued the alarm. To do this, select the MO and set the value of the attribute, administrativeState to LOCKED.
  5. Unlock the MrfH248Interface MO. To do this, select the MO and set the value of the attribute, administrativeState to UNLOCKED. Continue to Perform Concluding Routines.
    Note: By locking the MrfH248Interface MO, the alarm will be automatically ceased and all traffic towards MTAS will stop.
  6. If the alarm is raised again, consult the next level of maintenance support. Further actions are outside the scope of this instruction. Continue to Perform Concluding Routines.

1.5 Perform Concluding Routines

Steps

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