Brocade Network OS NETCONF Operations Guide v4.1.1 - Manual (Page 498)

466 Network OS NETCONF Operations Guide
53-1003231-02
Port-based Policier
29
<edit-config>
<target>
<running/>
</target>
<config>
<policy-map xmlns="urn:brocade.com:mgmt:brocade-policer">
<po-name>pmap1</po-name>
<class>
<cl-name>default</cl-name>
<port-shape>3000</port-shape>
</class>
</policy-map>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="2345" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Binding the policy map to an interface
To associate a policy map to an interface and apply policing parameters, perform the following
steps.
1. Issue the <edit-config> RPC to configure the <interface> node in the
urn:brocade.com:mgmt:brocade-interface workspace.
2. Under the <interface> node, include the <gigabitethernet>, <tengigabitethernet>,
<fortygigabitethernet>, <hundredgigabitethernet>, or <port-channel> node.
3. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>, or
<hundredgigabitethernet> node, include the <name> leaf element and specify the interface in
[rbridge-id/]slot/port format to identify the interface you want to configure.
4. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>, or
<hundredgigabitethernet> node, include the <shutdown> leaf element, and include the delete
operation in the element tag to enable the interface.
5. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>, or
<hundredgigabitethernet> node, include the <service-policy> node element located in the
urn:brocade.com:mgmt:brocade-policer namespace.
6. Under the <service-policy> node, include the following leaf elements:
a. In the <in> leaf element, specify the name of the policy map to bind to the interface for
ingress traffic.
b. In the <out> leaf element, specify the name of the policy to bind to the interface for egress
traffic.
7. Issue the <bna-config-cmd> RPC to save the running-config file to the startup-config file.
The following example binds policymap1 to both ingress and egress traffic on 10 Gb Ethernet
interface 22/0/1.
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="2346" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>