Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 146
114
Network OS NETCONF Operations Guide
53-1003231-02
Zoning information
10
<zone-name-pattern>zone1</zone-name-pattern>
</show-zoning-enabled-configuration>
</rpc>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3">
<enabled-configuration xmlns="urn:brocade.com:mgmt:brocade-zone">
<cfg-name>cfg1</cfg-name>
<enabled-zone>
<zone-name>zone1</zone-name>
<member-entry>
<entry-name>10:00:00:00:00:00:00:01</entry-name>
</member-entry>
</enabled-zone>
<has-more>false</has-more>
</enabled-configuration>
</rpc-reply>
To support pagination, users must specify the last zone that was received and the zone plugin will
return a block of the database immediately following the specified zone object. For example, for a
zone configuration containing 200 zones and containing 1 WWN member each, the initial zone
request procedure would look like the following:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<show-zoning-enabled-configuration
xmlns="urn:brocade.com:mgmt:brocade-zone"></show-zoning-enabled-configuration>
</rpc>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<enabled-configuration xmlns="urn:brocade.com:mgmt:brocade-zone">
<cfg-name>cfg1</cfg-name>
<enabled-zone>
<zone-name>zone1</zone-name>
<member-entry>
<entry-name>10:00:00:00:00:00:00:01</entry-name>
</member-entry>
</enabled-zone>
..
<enabled-zone>
<zone-name>zone100</zone-name>
<member-entry>
<entry-name>10:00:00:00:00:00:00:64</entry-name>
</member-entry>
</enabled-zone>
<has-more>true</has-more>
</enabled-configuration>
</rpc-reply>
The next zone request would be:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<show-zoning-enabled-configuration xmlns="urn:brocade.com:mgmt:brocade-zone">
<last-rcvd-zone-name>zone100</last-rcvd-zone-name >
</show-zoning-enabled-configuration>
</rpc>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">