![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 2377089.1 : Eagle: Why does Eagle generates duplicate alarm traps for " DPC prohibited alarm ( UAM 313 ) " for same DPC intermittently.
In this Document
Created from <SR 3-16583029381> Applies to:Oracle Communications EAGLE (Hardware) - Version EAGLE 46.0 and laterInformation in this document applies to any platform. GoalTo explain the cause of generating DPC prohibited alarm (UAM 313) multiple times for same DPC intermittently ****18-01-17 15:57:18**** ****18-01-17 15:57:18**** ****18-01-17 15:57:18****
SolutionDPC’s with SSN Subsystem configured produce “ DPC is Prohibited “ alarms two times. 1. 1st DPC prohibited is for linkset. As UIM and UAM generated does not have alarm description , they only show one liner alarm information. ****18-01-17 15:57:18**** ****18-01-17 15:57:18**** Terminal Logs help us to get alarm description , we can observe “ DPC is Prohibited “ alarm generates for both linkset and Subsystem Number ( SSN ). vfstppunreg 18-01-17 15:57:18 IST EAGLE 46.3.0.0.1-68.27.0 vfstppunreg 18-01-17 15:57:18 IST EAGLE 46.3.0.0.1-68.27.0
Conclusion - DPC's configured along with defined SSN will produce “DPC is Prohibited” alarm two times. one is for LSN and other will be for SSN defined for the node .
Attachments This solution has no attachment |
||||||||||||||
|