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

Network OS NETCONF Operations Guide 309
53-1003231-02
VXLAN configuration and management
22
</edit-config>
</rpc>
<rpc-reply message-id="11" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
4. (optional) Within the <nsx-controller> container, include the <reconnect-interval> element to
change the reconnect interval between the NSX controller and the VCS fabric in case the
connection is lost. The default is 10 seconds, meaning that a reconnection is attempted every
10 seconds.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="12">
<edit-config>
<target>
<running></running>
</target>
<config>
<nsx-controller xmlns="urn:brocade.com:mgmt:brocade-tunnels">
<name>controller1</name>
<reconnect-interval>7</reconnect-interval>
</nsx-controller>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="12" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
5. Within the <nsx-controller> container, include the <activate/> element. The presence of this
element activates the NSX controller profile.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="13">
<edit-config>
<target>
<running></running>
</target>
<config>
<nsx-controller xmlns="urn:brocade.com:mgmt:brocade-tunnels">
<name>controller1</name>
<activate></activate>
</nsx-controller>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="13" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Displaying VXLAN information
Use the <get-config> RPC to retrieve the current configuration data and operational state data from
the brocade-tunnels.YANG RPC module. Refer to
“Retrieving configuration data” on page 11 for
detailed instructions.