Assigning interfaces to an area – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 561

Network OS NETCONF Operations Guide
529
53-1003231-02
Performing basic OSPF configuration
34
<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>
</ospf>
</router>
</rbridge-id>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="2608" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Assigning interfaces to an area
Once you define OSPF areas, you can assign interfaces to the areas. All router ports must be
assigned to one of the defined areas on an OSPF router. When a port is assigned to an area, all
corresponding subnets on that port are automatically included in the assignment.
For example, to assign interface 7/1/8 of a router area whose area ID is 192.5.0.0, and then save
the changes, issue the following RPC.
<rpc message-id="2609" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<interface xmlns="urn:brocade.com:mgmt:brocade-interface">
<tengigabitethernet>
<name>7/1/8</name>
<ip>
<interface-te-ospf-conf
xmlns="urn:brocade.com:mgmt:brocade-ospf">
<ospf1>
<area>192.5.0.0</area>
</ospf1>
</interface-te-ospf-conf>
</ip>
</tengigabitethernet>
</interface>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="2609" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
If you want to set an interface to passive mode, use the empty <passive/> leaf element instead of
the <area> leaf element in the previous example.
If you want to block flooding of outbound LSAs on specific OSPF interfaces, instead of the <area>
element in the previous example, using the following elements: