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

Network OS NETCONF Operations Guide 103
53-1003231-02
Zone database size
10
<rpc message-id="601" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running></running>
</target>
<config>
<zoning xmlns="urn:brocade.com:mgmt:brocade-zone">
<enabled-configuration>
<cfg-action>cfg-save</cfg-action>
</enabled-configuration>
<enabled-configuration>
<default-zone-access>noaccess</default-zone-access>
</enabled-configuration>
</zoning>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="601" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Zone database size
The maximum size of a zone database is the upper limit for the defined configuration, and it is
determined by the amount of memory available for storing the master copy of the defined
configuration in flash memory.
Use the following elements to determine whether there is enough space to complete outstanding
transactions:
• db-max—Theoretical maximum size of the zoning database kept in nonvolatile memory
• db-avail—Theoretical amount of free space available
• db-committed—The size of the defined configuration currently stored in nonvolatile memory
• db-transaction—The amount of memory required to commit the current transaction
NOTE
These fields are all measured in bytes.
The supported maximum zone database size is 100 KB. If the outstanding transaction data
(db-transaction field) is less than the remaining supported space (100 KB minus db-committed),
enough space exists to commit the transaction.
Note that the db-max field shows a theoretical zone database limit of about 1 MB. However,
performance might become unacceptable if the zoning database exceeds 150 KB.