ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Discrepancies between what NCM policies are returned via REST, to what is shown in the Spectrum OneClick GUI


Article ID: 237569


Updated On:


CA Spectrum DX NetOps


Discrepancies between what NCM_Policy_Device_List (0x903774) is reporting via REST, to what is shown in the OneClick GUI. Only 33 policies show in OC GUI, while REST/CLI show return 50

REST is:



<?xml version="1.0" encoding="UTF-8"?>  
<rs:model-request throttlesize="
xsi:schemaLocation=" ../../../xsd/Request.xsd ">     
<rs:search-criteria xmlns="">               
<attribute id="
0x10000"> <!-- MODEL TYPE NAME -->                       
<rs:requested-attribute id="
0x1006e"/> <!-- POLICY NAME -->   
<rs:requested-attribute id="
0x82004c"/> <!-- POLICY DEFINITION -->   
<rs:requested-attribute id="
0x82004b"/> <!-- POLICY STATE - ACTIVE = 1 -->   
<rs:requested-attribute id="
0x820114"/> <!-- POLICY TYPE --> 

The CLI returns a Model_Handle (MH) that is invalid (and not shown in the OneClilck GUI):

[[email protected]/usr/Spectrum/vnmsh] $ ./show attributes mh=0x95d627 | grep NCM_Policy_Device_List
0x820068    NCM_Policy_Device_List            0                    0x957bee

However, when searching for this MH, nothing is returned:

./show models | grep 0x957bee


The Policy Model_Handles have become invalid, so OneClick cannot resolve them and they are not listed under the Explorer pane of OneClick. However, because they're still in the DB, they are returned by REST or CLI calls since they read directly from what's in the DB for those Models and do not have to resolve them with other attributes like OneClick.


DX NetOps Spectrum 20.2 or later


Setting a Locator search in OneClick for:

'Model Type Name (0x10000)' = 'NCM_Policy'

Everything in the results but not in the policy list shown in OneClick Explorer Policies is considered as invalid. 

These can then be deleted manually. After this, the results returned via REST, should be the same as what is shown in the OneClick GUI.