Cisco Cisco Prime Network Services Controller 3.0 Guide Du Développeur

Page 34

OL-28369-01

dn="org-root/cfw-test5"
name="test5"
dataIpAddress="5.5.5.5"
dataIpSubnet="255.255.255.0"
status="created"/>

</pair>

</inConfigs>

</configConfMos>

Response

<configConfMos

cookie="<real_cookie>"
commCookie="5/12/0/1545"
srcExtSys="172.25.97.246"
destExtSys="172.25.97.246"
srcSvc="sam_extXMLApi"
destSvc="resource-mgr_dme"
response="yes">
<outConfigs>

<fwComputeFirewall

assocState="unassociated"
auxProps=""
configState="not-applied"
dataIpAddress="5.5.5.5"
dataIpSubnet="255.255.255.0"
descr=""
devicePolicy=""
dn="org-root/cfw-test5"
fltAggr="0"
hostname="firewall"
intId="10583"
name="test5"
status="created"/>

</pair>

</outConfigs>

</configConfMos>

Assign a Device Profile to a Compute Firewall

Beginning with Virtual Network Management Center 2.0, fw:ComputeFirewall.devicePolicy is deprecated and
should not be modified via the XML API. Instead, create a child MO of type logical:DeviceProfileAssociation, and
set logical:DeviceProfileAssociation.profileRef. The logical:DeviceProfileAssociation should be a child of
fw:ComputeFirewall.

If you modify fw:ComputeFirewall.devicePolicy, you might see inconsistent behavior between
fw:ComputeFirewall.devicePolicy and logical:DeviceProfileAssociation, and thus what is displayed in the UI.

The following example assigns the device profile my-profile-ref to the compute firewall test5, which was created in

Create a Compute Firewall

Request

<configConfMos

cookie="<real_cookie>"
inHierarchical="false">
<inConfigs>

<logicalDeviceProfileAssociation

dn="org-root/cfw-test5/device-profile"
profileRef="my-profile-ref"
status="created"/>

</pair>