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

Network OS NETCONF Operations Guide 305
53-1003231-02
VXLAN configuration and management
22
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<edit-config>
<target>
<running></running>
</target>
<config>
<overlay-gateway xmlns="urn:brocade.com:mgmt:brocade-tunnels">
<name>name1</name>
</overlay-gateway>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
3. Within the <overlay-gateway> container, include the <name> element and <attach> node to
attach existing RBridge IDs to this VXLAN gateway instance. Set the <rb-add> element to 1-2.
This adds RBridge IDs 1 and 2.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="2">
<edit-config>
<target>
<running></running>
</target>
<config>
<overlay-gateway xmlns="urn:brocade.com:mgmt:brocade-tunnels">
<name>name1</name>
<attach>
<rbridge-id>
<rb-add>1,2</rb-add>
</rbridge-id>
</attach>
</overlay-gateway>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
4. The <vlan> nodes need to be included in the <attach> node of the <overlay-gateway>
container. Since multiple VLANs cannot be specified at one time using NETCONF. Multiple such
requests needs to be sent for attaching multiple VLANs. For this example, you must repeat this
step for VLANs 5, 14, 15, 16, and 17.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3">
<edit-config>
<target>
<running></running>
</target>
<config>
<overlay-gateway xmlns="urn:brocade.com:mgmt:brocade-tunnels">
<name>name1</name>
<attach>
<vlan>
<vid>5</vid>
<mac>0000.0000.0000</mac>