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

506 Network OS NETCONF Operations Guide
53-1003231-02
Configuring a route map
32
a. In the <name> element, specify the IP prefix list name.
b. In the <instance> element, specify the instance ID.
c. In the <action-ipp> element, specify “permit” or “deny”.
d. In the <prefix-ipp> element, specify the prefix IP4 address.
e. Optional: In the <ge-ipp> element, specify the lower limit of the mask length,
f. Optional: In the <le-ipp> element, specify the upper limit of the mask length.
The following example configures an IP prefix list named test with two instances. A route is
considered a match for instance 1 if this route is inside subnet 1.2.0.0/16 and has a mask length
between 17 and 30. That is, route 1.2.1.0/24 matches, but route 1.2.1.1/32 does not, due to mask
length.
<rpc message-id="913" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<ip xmlns="urn:brocade.com:mgmt:brocade-common-def">
<hide-prefix-holder
xmlns="urn:brocade.com:mgmt:brocade-ip-policy>
<prefix-list>
<name>test</name>
<instance>1</instance>
<action-ipp>deny</action-ipp>
<prefix-ipp>1.2.0.0/16</prefix-ipp>
<ge-ipp>17</ge-ipp>
<le-ipp>30</le-ipp>
</prefix-list>
<prefix-list>
<name>test</name>
<instance>2</instance>
<action-ipp>permit</action-ipp>
<prefix-ipp>1.1.0.0/16</prefix-ipp>
</prefix-list>
</hide-prefix-holder>
</ip>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="913" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Configuring a route map
A route map is a policy mechanism that allows or denies entry to a subsystem based on the next
hop interface. Refer to the Network OS Administrator’s Guide for a conceptual description of route
maps.
To configure a route map, perform the following steps.