Troubleshooting
Problem
Setting some fields such as @ExpireTime in the Omnibus NcKL rules files do not take effect.
Symptom
Problem can be seen with any of the following fields:
@EventId
@ExpireTime
@ProcessReq
@SuppressEscl
@Customer
@Service
@PhysicalSlot
@PhysicalPort
@PhysicalCard
@TaskList
@NmosSerial
@NmosObjInst
@NmosCauseType
@LocalNodeAlias
@LocalPriObj
@LocalSecObj
@LocalRootObj
@RemoteNodeAlias
@RemotePriObj
@RemoteSecObj
@RemoteRootObj
@X733EventType
@X733ProbableCause
@X733SpecificProb
@X733CorrNotif
@CorrScore
@AdvCorrCauseType
@CauseType
@LocalObjRelate
@LocalObjRelate
@LocalObjRelate
@RemoteObjRelate
@RemoteObjRelate
@RemoteObjRelate
Resolving The Problem
Comment out the following rules files.
include "$NC_RULES_HOME/include-compat/omnibus36.include.compat.rules"
include "$NC_RULES_HOME/include-compat/AdvCorr36.include.compat.rules"
These rules files were intended for use with Omnibus 3.6 Object Server automations and are not necessary in Omnibus 7.x.
Commenting this out will allow the fields within the rules file to be set directly from other rules instead.
Note - Use caution when commenting rules files out of the Netcool Knowledge Library NcKL rules set. Commenting out other rules can disable the default event processing of the NcKL. The two rules files above can be commented out to allow the direct setting of certain Object Server fields on Omnibus 7.x.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21596480