Cisco Cisco Security Manager 4.7 Guía Del Usuario
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Cisco Security Manager 4.7 API Specification (Version 2.0)
OL- 32164-01
Page 182
3.2.32.2
Response
3.2.33
Method ReorderPolicyConfigByName
This method is used to reorder the rules in CSM assigned to a shared policy. It is supported only for access-rules and
unified access-rules. The following gives the request and response object. Policy specific details are under
unified access-rules. The following gives the request and response object. Policy specific details are under
3.2.33.1
Request
given.
Figure 146: reorderPolicyConfigByGID request example
3.2.33.2
Response
3.3 Policy-Specific Handling
The following section gives the details of policy-specific handling for individual policies, especially in the write use
cases. In general, for all local device policies that are not shared, methods ending with GID should be used (e.g.,
addPolicyConfigByGID and modifiyPolicyConfigByGID). However, if that policy is shared, then these methods
cannot be used. Instead, methods ending with Name (e.g., addPolicyConfigByName and
deletePolicyConfigByName) need to be used after determining the shared policy name that is assigned to the device.
The changes made to the shared policy will affect all the devices that the shared policy is assigned to.
cases. In general, for all local device policies that are not shared, methods ending with GID should be used (e.g.,
addPolicyConfigByGID and modifiyPolicyConfigByGID). However, if that policy is shared, then these methods
cannot be used. Instead, methods ending with Name (e.g., addPolicyConfigByName and
deletePolicyConfigByName) need to be used after determining the shared policy name that is assigned to the device.
The changes made to the shared policy will affect all the devices that the shared policy is assigned to.
URL:
https://hostname/nbi/configservice/reorderPolicyConfigByName
HTTP Header:
Set-Cookie: asCookie=732423sdfs73242; expires=Fri, 3-Sep-2013 23:59:59 GMT; path=/;
domain=.hostdomain.com
XML Argument:
<?xml version="1.0" encoding="UTF-8"?>
<p:reorderRulesRequest xmlns:p="csm">
<csmSessionGID>00000000-0000-0000-0000-068719476739</csmSessionGID>
<name>usRule</name>
<ruleGID>00000000-0000-0000-0000-060129542454</ruleGID>
<policyType>DeviceAccessRuleFirewallPolicy</policyType>
<toOrderId>3</toOrderId>
</p:reorderRulesRequest>
https://hostname/nbi/configservice/reorderPolicyConfigByName
HTTP Header:
Set-Cookie: asCookie=732423sdfs73242; expires=Fri, 3-Sep-2013 23:59:59 GMT; path=/;
domain=.hostdomain.com
XML Argument:
<?xml version="1.0" encoding="UTF-8"?>
<p:reorderRulesRequest xmlns:p="csm">
<csmSessionGID>00000000-0000-0000-0000-068719476739</csmSessionGID>
<name>usRule</name>
<ruleGID>00000000-0000-0000-0000-060129542454</ruleGID>
<policyType>DeviceAccessRuleFirewallPolicy</policyType>
<toOrderId>3</toOrderId>
</p:reorderRulesRequest>