Multiple RDM Alarm Found In The Node Chain (Doc ID 781210.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Communications Network Mediation - Version: 5.0.1 and later   [Release: 5.1 and later ]
Information in this document applies to any platform.

Goal

Multiple RDM (Remote Data manager) alarms are generating in secondary Charging Gateway Function (CGF). The seconday node chain (SC) is configured to allow the received billing records to be forward to the primary CGF (PC), via intern nodal link between seconday CGF (CC: CC_CGF2 - CC1) to primary (EP:Temp_EP_CGF1).

Problem reproduction steps:
1. Setup one primary and one secondary CGF with the same node chain configuration, on different hosts.
2. Connect secondary CGF, Collection Cartridge (CC) node to primary CGF, Enhancement Processor (EP) node.
3. Ensure both CGFs are operating.
4. Disconnect primary CGF from the network for ~2 hrs.
5. Reboot primary CGF.
6. Reconnect primary CGF into the network.
7. Put billing traffic to secondary CGF and make it routed to primary CGF1 for processing.
8. Check whether RDM alarm is generating.


CGF Alarm log
===========

2008-02-20 13:45:20; Critical; Undefined; rdm:[RDM] Failed to copy
/opt/NM501/input/2s9r1l-99g-eydyiq0a/0_2sctfo-99g-eydylttu_Feb_20__2008_13_44_18_712.arch to
node
2s9r1l-99g-eydyiq0a @ 10.9.213.41:12004; logMsgManClear: CRITICAL#EOR#
2008-02-20 13:45:20; Informational; logMsgAutoClear GOOD [RDM] Connection timed out while trying
to connect to RDM at 10.9.213.41:12004#EOR#
2008-02-20 13:46:21; Critical; Undefined; rdm:[RDM] Failed to copy
/opt/NM501/input/2s9r1l-99g-eydyiq0a/0_2sctfo-99g-eydylttu_Feb_20__2008_13_45_18_720.arch to
node
2s9r1l-99g-eydyiq0a @ 10.9.213.41:12004; logMsgManClear: CRITICAL#EOR#
2008-02-20 13:46:21; Informational; logMsgAutoClear GOOD [RDM] Connection timed out while trying to connect to RDM at 10.9.213.41:12004#EOR#

The alarm indicated in the SC is found to be complaining the connectivity between it’s CC and EP in PC.

Further looking into the node manager status listing from SC, it is noticed that all nodes indicated PC are found to be stopped.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms