SpectrSERVER slow to activate models at startup due to NCM Policies
search cancel

SpectrSERVER slow to activate models at startup due to NCM Policies

book

Article ID: 246272

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

SpectrSERVER is slow to activate models at start (5 to 10 minutes per landscape approximately).  Sometimes it doesn't start to activate models up to 15+ minutes after starting the landscape. The pstacks show the following:

Thread::schedule() [/opt/SPECTRUM/lib/libmoot.so.1]Thread::wait(unsigned int) [/opt/SPECTRUM/lib/libmoot.so.1]ItcRemoteCall::remoteCallBase(int) [/opt/SPECTRUM/lib/libitc.so.1]ItcRemoteCall::remoteCall(int, unsigned int, ...) [/opt/SPECTRUM/lib/libitc.so.1]IHHostConfig::get_policy_results(CsModelHandleList*, char const*, CsError::CsError_e&) [/usr/Spectrum/SS/Modules/SA-SCMSS.so.1]IHHostConfig::handle_verify_policy_request(CsModelHandle const&, CsModelHandle*, unsigned char*, char**) [/usr/Spectrum/SS/Modules/SA-SCMSS.so.1]IHHostConfig::trig_action(CsModelHandle const&, CsAction const*) [/usr/Spectrum/SS/Modules/SA-SCMSS.so.1]CsModelType::trig_action(CsModelHandle const&, CsAction const*, CsVPConnHandle const&) [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsModel::action(CsAction*, CsVPConnHandle const&, CsSecurityIf const*) [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsModelIf::action(CsAction*, CsVPConnHandle const&, CsSecurityIf const*) const [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsVnmModelHandle::action(CsAction*, CsConnHandle const&) const [/opt/SPECTRUM/lib/../SS/libIHapi.so.1]CsVnmModelHandle::action(CsAction*) const [/opt/SPECTRUM/lib/../SS/libIHapi.so.1]IHGCMembershipMonitor::handle_rel_change(CsModelHandle const&, CsRelHandle const&, CsRelEnum::CsRelChange_e, CsRelEnum::CsRelSide_e, CsModelHandle const&, CsMTypeHandle const&) [/usr/Spectrum/SS/Modules/SA-SCMSS.so.1]CsIHRelWatcher::notify(CsIncidentParm const*, CsSecurityIf const*) [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsRelation::trig_rel_change(CsAssociation const&, CsRelEnum::CsRelChange_e, CsSecurityIf const*) [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsRelation::notify_models(CsAssociation const&, CsRelEnum::CsRelChange_e, int, CsSecurityIf const*) [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsRelation::activate(CsAssociation*) [/opt/SPECTRUM/lib/../SS/libsskrnl.so.1]CsWorkQueue::process_work_node(CsWorkNode*) [/opt/SPECTRUM/lib/libwkmgr.so.1]CsWorkScheduler::do_work() [/opt/SPECTRUM/lib/libwkmgr.so.1]

 

Environment

Release : 21.2.10

Component : Spectrum Core / SpectroSERVER

Cause

This is due to NCM policies being associated with global collections. This is resolved in 21.2.12.

Resolution

This issue is resolved in 21.2.12. NCM policies associated with global collections no longer cause performance issues with SpectroSERVER activation.