Diameter Signaling Router (DSR) - Server Provisioning Network Error Alarm ID 32308 in Case of Customer Router Monitoring

Asset ID:	1-72-2020252.1
Update Date:	2016-05-27
Keywords:

Solution Type Problem Resolution Sure

Solution 2020252.1 : Diameter Signaling Router (DSR) - Server Provisioning Network Error Alarm ID 32308 in Case of Customer Router Monitoring

Applies to:

BNS Platform Hardware - Version DSR 4.0 to DSR 6.0 [Release DSR 4.0 to DSR 6.0]
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 4.0 to DSR 6.0 [Release DSR 4.0 to DSR 6.0]
Information in this document applies to any platform.
<

Symptoms

If a user enables Customer Router Monitoring (essentially an automatic PING facility against the gateways defined in network element XML file, assumed to be routers), and if the gateway is unreachable for any reason (such as IMI on 169.x.x.x network, for which no router exists), then this alarm will be raised. Disabling the facility will fail to clear the alarm

Cause

This is a known issue, present in DSR4 and DSR5 , documented under PR241656 / BugID 19119475. The fix is delivered in DSR7.0

If a user enables Customer Router Monitoring (essentially an automatic PING facility against the gateways defined in network element XML file, assumed to be routers), and if the gateway is unreachable for any reason (such as IMI on 169.x.x.x network, for which no router exists), then this alarm will be raised. Disabling the facility will fail to clear the alarm, and it must be cleared manually at the command line.

Solution

Here are two methods to clear the alarm. Try method 1 first. If it does not work then do method 2.

You do not need to do both methods. Only do Method 2 if method 1 does not clear the alarm.

------Method 1-----------------

1. Go to NOAM GUI then Status & Manage -> Network Element and select the SOAM Network Element and
click Disable Ping. (the although the GUI shows Disabled under Customer Router Monitoring you must still do this step)
NOTE: This will create a GUI error which can be ignored.

2. Go to command line and execute "syscheck" to be sure it is clean

3. Execute the following command:
alarm.put -e 32308 -s 5 -i SNMPv2-MIB::sysName=169.254.x.x

This should clear the alarm

------------Method 2----------------
Only if method 1 does not work.
Note this method involves reenabling the ping first.

1. Go to Status & Manage -> Network Element and select the SOAM Network Element and
click "Enable" Ping.
Note this will cause an error in the GUI which you can ignore.
This may also create an additional 32308 alarm.

2. Go to the command line of the server and run:
"syscheck"
NOTE: you should see an error related to this alarm in syscheck.
NOTE: if two 32308 alarms are show in the GUI you will have to go to the command line of both servers and run syscheck

3. Go back to the GUI and Select the OAM Network Element again and click "Disable" Ping. If there are two 32308 alarms then click Disable Ping twice.
NOTE: this will cause an error in the GUI which you can ignore.

4. Go to the SOAM command line and run "syscheck" again to verify it is clear after clicking Disable Ping.

5. If there is still a 32308 alarm still in the GUI then on the command for the server showing the alarm execute

alarm.put -e 32308 -s 5 -i SNMPv2-MIB::sysName=169.254.x.x

This clears the alarm in the lab.

Applies to:

BNS Platform Hardware
1-914CU

References

<BUG:19119475> - [241656]CUSTOMER ROUTER MONITORING FAILS TO ENABLE, DISABLE

Attachments

This solution has no attachment