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

528 Network OS NETCONF Operations Guide
53-1003231-02
Performing basic OSPF configuration
34
<rbridge-id>101</rbridge-id>
<router>
<ospf xmlns="urn:brocade.com:mgmt:brocade-ospf>
<area>
<area-id>1.1.1.1</area-id>
<nssa>
<metric>
<nssa-value>10</nssa-value>
</metric>
</nssa>
</area>
<summary-address>
<sum-address>209.157.1.0</sum-address>
<sum-address-mask>255.255.255.0</sum-address-mask>
</summary-address>
</ospf>
</router>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="2607" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Assigning an area range (optional)
You can assign a range for an area, but it is not required. Ranges allow a specific IP address and
mask to represent a range of IP addresses within an area, so that only that reference range
address is advertised to the network, instead of all the addresses within that range. Each area can
have up to 32 range addresses.
If you do assign a range for an area, you must also specify a range effect, which can be “advertise”
or “not-advertise”.
The following example RPC defines an area range for subnets on 0.0.0.10 and 0.0.0.20.
<rpc message-id="2608" 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>101</rbridge-id>
<router>
<ospf xmlns="urn:brocade.com:mgmt:brocade-ospf>
<area>
<area-id>0.0.0.10</area-id>
<normal/>
<range>
<range-address>193.45.0.0</range-address>
<range-mask>255.255.0.0</range-mask>
<range-effect>not-advertise</range-effect>
</range>
</area>
<area>
<area-id>0.0.0.20</area-id>