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

Network OS NETCONF Operations Guide 517
53-1003231-02
Other routing operations
33
<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>
<static-route-nh>
<static-route-dest>207.95.7.0/24
</static-route-dest>
<static-route-next-hop>207.95.6.157
</static-route-next-hop>
<route-attributes>
<tag>5</tag>
<metric>10</metric>
</route-attributes>
</static-route-nh/>
</route>
</rtm-config>
</ip>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="3303" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Enabling IP load sharing
Use the <load-sharing> element to balance IP traffic across up to eight equal paths.
<rpc message-id="3304" 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">
<load-sharing/>
</rtm-config>
</ip>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="3304" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Resolving the next hop using an OSPF route
Use the <next-hop> element to allow a Brocade device to use routes learned from OSPF to resolve
a configured static route.