Cisco Cisco Prime Network Services Controller 3.2 Developer's Guide

Page 78 

OL-30968-01 

</pair> 

</outConfigs> 

</configConfMos> 

Attribute Dictionary 

The following example creates a dictionary that defines the various attribute IDs and names. 

POST URL: https://10.193.33.221/xmlIM/policy-mgr 
XML API payload: 
<configConfMos 

cookie="<real_cookie>"> 
<inConfigs> 

<!-- Create Sample VnspCustomDictionary under org-tenant1 --> 

<pair key="org-root/attr-dict-custom-userAttrs"> 

<policyVnspCustomDictionary dn="org-root/attr-dict-custom-userAttrs"> 

<policyVnspCustomAttr dataType="string" id="1" name="userAttr1" /> 
<policyVnspCustomAttr dataType="string" id="2" name="userAttr2" /> 
<policyVnspCustomAttr dataType="string" id="3" name="dept" /> 
<policyVnspCustomAttr dataType="string" id="4" name="production" /> 

</policyVnspCustomDictionary> 

</pair> 

</inConfigs> 

</configConfMos> 

<configConfMos 

cookie="<real_cookie>" 
commCookie="7/15/0/1a3" 
srcExtSys="10.193.33.221" 
destExtSys="10.193.33.221" 
srcSvc="sam_extXMLApi" 
destSvc="policy-mgr_dme" 
response="yes"> 
<outConfigs> 

<pair key="org-root/attr-dict-custom-userAttrs"> 

<policyVnspCustomDictionary 

descr="" 
dn="org-root/attr-dict-custom-userAttrs" 
intId="24245" 
name="userAttrs" 
status="created"/> 

</pair> 

</outConfigs> 

</configConfMos> 

Policy 

Beginning with version 2.0, Prime Network Services Controller no longer uses the adminState property for ACL 
policies because VSG compute firewalls do not support a value of disabled for this property; the default value is 
enabled. However, Prime Network Services Controller continues to use the adminState property in other types of 
policies, such as those used by ASA 1000V. 

If you set the adminState property via the API for an ACL policy, the response will contain the following error 
message: 
<configConfMos 

cookie="<real_cookie>" 
commCookie="7/12/0/55" 
srcExtSys="10.193.76.15" 
destExtSys="10.193.76.15" 
srcSvc="sam_extXMLApi" 
destSvc="policy-mgr_dme" 
response="yes" 
errorCode="170" 
invocationResult="unidentified-fail"