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

Network OS NETCONF Operations Guide 507
53-1003231-02
Configuring a route map
32
1. Issue the <edit-config> RPC to configure the <hide-routemap-holder> node in the
urn:brocade.com:mgmt:brocade-ip-policy namespace.
2. Under the <hide-routemap-holder> node, include a <route-map> node element for each
instance of the route map.
3. Under the <route-map> node, include the following elements.
a. In the <name> element, specify the route map name.
b. In the <action-rm> element, specify “permit” or “deny”.
c. In the <instance> element, specify the instance ID.
d. Specify the <content>/<match> hierarchy of node elements.
4. Under the <match> node, specify one of the following:
• An <interface> node element, containing a leaf element that defines the interface
next-hop interface to be used for matching. For example:
<interface>
<tengigabitethernet-rmm>0/1</tengigabitethernet=rmm>
<interface
• <ip>/<next-hop> node elements, containing a leaf element that specifies an IP prefix list
to be used for next-hop matching. For example:
<ip>
<next-hop>
<prefix-list-rmm-n>pre-test</prefix-list-rmm-n>
</next-hop>
</ip>
The following example configures a route-map named test that comprises two instances; instance
1 denies entry for any routes whose next-hop interface is te 0/1, and instance 2 allows entry for
routes whose next-hop matches the IP subnets specified in the prefix-list pre-test (not shown).
Additionally, each matched route has its tag set to 5000.
<rpc message-id="913" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<hide-routemap-holder xmlns="urn:brocade.com:mgmt:brocade-ip-policy>
<route-map>
<name>test</name>
<action-rm>deny</action-rm>
<instance>1</instance>
<content>
<match>
<interface>
<tengigabitethernet-rmm>0/1</tengigabitethernet-rmm>
</interface>
</match>
</content>
</route-map>
<route-map>
<name>test</name>
<action-rm>permit</action-rm>
<instance>2</instance>
<content>