Cisco Cisco Prime Network Services Controller 3.2 Developer's Guide

Page of 163
Page 47 
OL-30968-01 
 
<pair key="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-01-
Primary/vnic-vsg-3"> 
<logicalVsgVnic descr="" dn="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-
01/vsg-CFW-inst-Ha-01-Primary/vnic-vsg-3" id="3" intId="11070" name="" 
networkDn="vmmEp/vm-mgr-VmMgr-138/folder-datacenter-261/switch-std-host-
123/portgrp-network-271" policyProfileDn="" portProfileName="VM Network" 
role="HA" status="created"/> 
</pair> 
 
<pair key="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-01-
Secondary/vnic-vsg-1"> 
<logicalVsgVnic descr="" dn="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-
01/vsg-CFW-inst-Ha-01-Secondary/vnic-vsg-1" id="1" intId="11071" name="" 
networkDn="vmmEp/vm-mgr-VmMgr-138/folder-datacenter-261/switch-std-host-
123/portgrp-network-271" policyProfileDn="" portProfileName="VM Network" 
role="Data" status="created"/> 
</pair> 
 
<pair key="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-01-
Secondary/vnic-vsg-2"> 
<logicalVsgVnic descr="" dn="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-
01/vsg-CFW-inst-Ha-01-Secondary/vnic-vsg-2" id="2" intId="11072" name="" 
networkDn="vmmEp/vm-mgr-VmMgr-138/folder-datacenter-261/switch-std-host-
123/portgrp-network-271" policyProfileDn="" portProfileName="VM Network" 
role="Management" status="created"/> 
</pair> 
 
<pair key="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-01-
Secondary/vnic-vsg-3"> 
<logicalVsgVnic descr="" dn="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-
01/vsg-CFW-inst-Ha-01-Secondary/vnic-vsg-3" id="3" intId="11073" name="" 
networkDn="vmmEp/vm-mgr-VmMgr-138/folder-datacenter-261/switch-std-host-
123/portgrp-network-271" policyProfileDn="" portProfileName="VM Network" 
role="HA" status="created"/> 
</pair> 
 
<pair key="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-01-
Primary/vnic-vsg-2/ip-2"> 
<logicalIp dn="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-
01-Primary/vnic-vsg-2/ip-2" gateway="10.25.10.1" index="2" 
ip="10.25.10.83" ipSubnet="255.255.255.0" isPrimary="no" 
status="created"/> 
</pair> 
 
<pair key="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-01-
Secondary/vnic-vsg-2/ip-2"> 
<logicalIp dn="vmcontainer/vsg-root-ten-01-CFW-inst-Ha-01/vsg-CFW-inst-Ha-
01-Secondary/vnic-vsg-2/ip-2" gateway="10.25.10.1" index="2" 
ip="10.25.10.83" ipSubnet="255.255.255.0" isPrimary="no" 
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.