Today, I'd like to share a case.
Problem Description
U2000 version: U2000V200R018C10SPC240
OSS version of the upper-layer NMS: FM V1R2C30
Symptom:
1. See from the upper-layer NMS, the U2000 reports a large number of alarms
2. U2000 Alarms are delayed on the OSS
Problem Analysis
1. Analyze the (/opt/oss/server/var/logs/irp_agent_2019xxxx) log of the U2000 NBI IRP service. In normal cases, the OSS sends get_subscription_status command to the U2000 every minute.But during the period for restarting the IRP service on the U2000 of 15:15-15:19. The OSS does not send the send get_subscription_status command to the U2000. Corba re-subscription is triggered on the OSS side. For 15:20-15:24. The symptom is the same.
2. During each subscription, the OSS triggers full synchronization of alarms.
Root Cause
The CORBA northbound heartbeat period of the OSS and U2000 is 1 minute. When the IRP service of the U2000 is restarted, the OSS detects that the heartbeat times out and issues the subscription again. In this case, full alarm synchronization is triggered. As a result, a large number of active alarms are reported to the OSS. Alarm synchronization and new alarm reporting are in the same channel. Therefore, new alarms are delayed during alarm synchronization.
Solution Description
The northbound IRP service of the U2000 is restarted for about 2 minutes. Therefore, the OSS needs to change the heartbeat timeout period to a value greater than 2 minutes, for example, 3 minutes.
Welcome to leave a message below.
We’ll study together.
Thank you!
