Unable To Set LOOPBACK For NEP Server Independently
(Doc ID 2271337.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications ASAP - Version 7.2.0 to 220.127.116.11.0 [Release 7.2 to 7.3.0]
Information in this document applies to any platform.
On : ASAP 18.104.22.168.0 version, Network Element Processor
The user is Unable to set LOOPBACK for the NEP server independently.
The customer wants one of the Network Element Processors (NEPs) to be in loopback mode independently, while all other NEPs should hit their respective Network Elements. The customer tried the following scenarios but work orders were still failing.
1. Customer modified the ASAP.cfg file where global LOOPBACK_ON parameter is set to 0 and under [NEPq] server section, LOOPBACK_ON is set to 1.
2. Customer modified tbl_ne_config table of SARM where LOOPBACK_ON field is set to 1 for NEPq
Note: In both the above scenarios, we are seeing LOOPBACK_ON = 1 in the list of Order parameters passed in JNEPq.diag log
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