A Difference In Behaviour Of LOOPBACK ON Mode From the Expected For GEMOTA NE
(Doc ID 2047063.1)
Last updated on FEBRUARY 15, 2019
Applies to:
Oracle Communications ASAP - Version 7.0.2 and laterInformation in this document applies to any platform.
Goal
One of the Network Elements had to be kept in LOOPBACK on mode due to a network issue. What we have observed in the past is that making changes in TBL_NE_CONFIG for keeping the Network into LOOPBACK requires NEP restart only, but here it didn't happen. In this case, NEP restart did not work when we kept Network Element to LOOPBACK ON mode. We had to restart the SARM server later followed by an NEP restart.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |