1. Alarms and KPIs Guide
  2. Alarms and Events
  3. Full Address Based Resolution (FABR) Alarms and Events (22600-22640)
  4. 22632 - ComAgent Registration Failure

3.12.14 22632 - ComAgent Registration Failure

Alarm Group:
FABR
Description:
FABR application is unavailable and DSR cannot successfully process FABR traffic.
Severity:
Critical
Instance:
Full Address Based Resolution
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDiameterComAgentRegistFailNotify
Cause:

This alarm is raised when ComAgent fails to register:

  • Service with DPService.
    • The DPService routed service entry missing in ComAgent table.
    • FABR routing service has been enabled on the MP blade, but DP routed service entry is not present in the ComAgtRoutedService table on MP blade.
  • ServiceNotificationHandler after the successful ComAgent service registration.
Diagnostic Information:
  1. Check the ComAgtRoutedService table entries, by running the below command on the MP1 command prompt. iqt -p -s'|' ComAgtRoutedService
  2. Entry corresponding to the DP routed service used by FABR must be present with id=11 and name=DPService. For example: 11|DPService|No|Yes|0

Recovery:

  1. Check the ComAgtRoutedService table entries, by running the below command on the MP1 command prompt.
    iqt -p -s'|' ComAgtRoutedService
  2. Entry corresponding to the DP routed service used by FABR must be present with id=11 and name=DPService. For example:
    11|DPService|No|Yes|0
  3. Disable the FABR application to clear the ComAgent Service Registration Failure alarm.
  4. Check the ComAgtRoutedService table on NOAM server blade to identify if there is any mismatch with the MP blade.
  5. Check the ComAgtRoutedService table on SOAM server blade to identify if there is any mismatch with the MP blade (in case of 3-tier architecture).
  6. If DP routed service entry is not present, then add it to the MP blade using the ivi command (after turning off the inetrep using pm.set off inetrep), then restart the inetrep process.
    Afterwards, please restart the DSR process by running pm.set off dsr; followed by pm.set on dsr; on MP blade command prompt.
  7. It is recommended to contact My Oracle Support for assistance.