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

Network OS NETCONF Operations Guide 91
53-1003231-02
Fabric interface configuration management
8
a. In the <rbridge-id> leaf element, specify the RBridge ID of the switch for which you want to
change the priority.
b. In the <priority> field, specify the new priority in the range 1 through 255.
The following example sets the priority of routing bridge 12 to 10.
<rpc message-id="1207" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<fabric xmlns="urn:brocade.com:mgmt:brocade-fabric-service">
<route>
<mcast>
<rbridge-id>
<rbridge-id>12</rbridge-id>
<priority>10</priority>
</rbridge-id>
</mcast>
</route>
</fabric>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1207" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Obtaining the running configuration
You can use the <get-config> RPC to return fabric route multicast configuration information. The
configuration currently effective on the switch is referred to as the running configuration. Any
configuration change you make while the switch is online is made to the running configuration. The
running configuration is nonpersistent.
NOTE
To save configuration changes, you must save the running-config file to a file, or you can apply the
changes by copying the running configuration to the startup configuration.
To obtain the route multicast configuration, issue the <get-config> RPC with a subtree filter that
restricts the output to the contents of the <fabric>/</route>/<mcast> node, as show in the
following example.
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1208" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter type="subtree">
<fabric xmlns="urn:brocade.com:mgmt:brocade-fabric-service">
<route>
<mcast/>
</route>
</fabric>