The SARM Server is Going Down For a Large Work Order (Doc ID 1562343.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Communications ASAP - Version 7.0.1 to 7.0.2 [Release 7.0.0]
Information in this document applies to any platform.
***Check on Currency On NOV-3-2016***

Symptoms

Work Orders got stuck in the SARM when a large WO was loaded with 800 NEs included in the workorder.

The following information was observed in the SARM diagnostic file:


>> 094135.487:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[TECH_TYPE,AXE10]
>> 094135.487:195: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[A1141CODE,OF/UE]
>> 094135.487:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[SFTWR_LOAD,BTLE9]
>> 094135.488:195:SANE:NE Log :4250:sarm/sarm/sarm/nep_driver.c
NE Event for DYN_NE.290_0: (Down) 'Primary Connect Request'
>> 094135.488:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[NE_TYPE,AXE_LOCAL]
>> 094135.488:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[PORT,11111]
>> 094135.488:195: LOW:ASC_cppalloc :348 :control/libcontrol/ctlib.c
Successfully obtained a Session from the Pool
>> 094135.488:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[HOST_USERID,xxxxx]
>> 094135.488:195: LOW:ASC_cprpcexec() :1238:control/libasc/ctlib.c
Executing RPC [SSP_ne_log]. Retry Count [0]
>> 094135.489:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[HOST_IPADDR,127.0.0.1]
>> 094135.489:197: LOW:ASDL Dispatch :4247:sarm/sarm/sarm/nep_driver.c
p_wo_comm_param:[A1141CODE,BED/UD]


However, the corresponding messages in the NEP_4 were as follows:


>> 094936.845:93: LOW:Sess Mgr :2059:sarm/libnep/sess_mgr.c
DYN_NE.290_0: Connect Failed: Port 02BF5820 'DYN_DEV.342_0', Port State -1, NE State 0
>> 094936.845:93: LOW: :808 :sarm/libnep/sarm_notify.c
SARM is available
>> 094936.846:93:PROG:System Event :2088:sarm/libnep/sess_mgr.c
ASAP System Event: SYS_WARN
NE DYN_NE.290_0 Primary Port Connection Failure
>> 094936.846:93: LOW:Port Unbind :3198:sarm/libnep/sess_mgr.c
Port Unbind, Port 02BF5820, Device DYN_DEV.342_0
>> 094936.846:93: LOW:SARM_NE_CONNECT :1560:sarm/libnep/sess_mgr.c
DYN_NE.290_0: Connect Request, at prim[1]
>> 094936.846:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[HOST_USERID], value[AXE10]
>> 094936.846:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[HOST_IPADDR], value[BTLE9]
>> 094936.847:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[A1141CODE], value[AXE_LOCAL]
>> 094936.847:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[PORT], value[62051]
>> 094936.847:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[HOST_USERID], value[xxxxx]
>> 094936.847:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[HOST_IPADDR], value[127.0.0.1]
>> 094936.847:93: LOW:DYNIP check :1630:sarm/libnep/sess_mgr.c
check comm param, label[A1141CODE], value[OF/UE]

Where the first 2 parameters are supposed to be "TECH_TYPE" and "SFTWR_LOAD". But they were replaced by "HOST_USERID" and "HOST_IPADDR", which were definitely wrong. Please note, the parameter values were right (AXE10, BTLE9), but the labels were wrong.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms