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

516 Network OS NETCONF Operations Guide
53-1003231-02
Other routing operations
33
Configuring the default route
The default route is configured with an all zeros prefix/netmask (that is, 0.0.0.0/0). This default
route gets installed in the ASIC. All traffic that does not have other matching routes is forwarded
using the default route.
The following example configures a default route with a next hop of 207.95.6.157.
<rpc message-id="3302" 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>
<static-route-nh>
<static-route-dest>0.0.0.0/0</static-route-dest>
<static-route-next-hop>207.95.6.157
</static-route-next-hop>
</static-route-nh/>
</route>
</rtm-config>
</ip>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="3302" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Other routing operations
This section describes some other commonly used route management operations. Refer to the
Network OS YANG Reference Manual for a list of all IP routing-related parameters.
Specifying route attributes
When specifying a route, include leaf elements under the <route-attributes> node that let you:
• Specify a tag value of a route to use for route filtering with a route map (<tag> element).
• Specify a cost metric of a route (<metric> element).
The following example sets the cost of a route to 10 and specifies a tag value of 5 for route filtering.
rpc message-id="3303" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>