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

518 Network OS NETCONF Operations Guide
53-1003231-02
Other routing operations
33
<rpc message-id="3305" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<rbridge-id xmlns="urn:brocade.com:mgmt:brocade-rbridge">
<rbridge-id>30</rbridge-id>
<ip>
<rtm-config xmlns="urn:brocade.com:mgmt:brocade-rtm">
<route>
<next-hop>
<proto>ospf</proto>
</next-hop>
</route>
</rtm-config>
</ip>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="3305" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Using recursion to resolve the next hop
Use the <next-hop-recursion> element to allow a Brocade device to resolve a route by using up to
10 recursive-level lookups of other routes.
<rpc message-id="3306" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<rbridge-id xmlns="urn:brocade.com:mgmt:brocade-rbridge">
<rbridge-id>30</rbridge-id>
<ip>
<rtm-config xmlns="urn:brocade.com:mgmt:brocade-rtm">
<route>
<next-hop-recursion/>
</route>
</rtm-config>
</ip>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="3306" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>