Adding a zone to a zone configuration – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual

Page 152

Advertising

120

Network OS NETCONF Operations Guide

53-1003231-02

Zone configuration management

</member-zone>

</cfg>

</defined-configuration>

<enabled-configuration>

<cfg-action>cfg-save</cfg-action>

</enabled-configuration>

</zoning>

</config>

</edit-config>

</rpc>

<rpc-reply message-id="617" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">

<ok/>

</rpc-reply>

NOTE

Zone aliases are not valid zone configuration members. Adding an alias to an existing zone
configuration will not be blocked. However, the attempt to enable a zone configuration that contains
aliases will fail with an appropriate error message.

Adding a zone to a zone configuration

The following procedure adds a zone to a zone configuration and saves the modified zoning
configuration to nonvolatile memory.

1. Issue an <edit-config> RPC to configure the <zoning>/<defined-configuration> node in the

urn:brocade.com:mgmt:brocade-zone namespace and add a <cfg> node with the following
elements:

a. Include the <cfg-name> element containing the name of the zoning configuration to which

you want to add zones.

b. Include a <member-zone> element for each zone you want to add to the configuration.

Each <member-zone> element must contain a <zone-name> element containing the
name of a zone.

2. Issue the <edit-config> RPC on the <zoning>/<enabled-configuration> node and set the value

of the <cfg-action> element to “cfg-save” to save the modified configuration to nonvolatile
memory.

The following example adds zoneC to cfg3.

?xml version="1.0" encoding="UTF-8"?>

<edit-config>

</target>

<defined-configuration>

<cfg>

<cfg-name>cfg3</cfg-name>

<member-zone>

<zone-name>zoneC</zone-name>

</member-zone>

</cfg>

</defined-configuration>

Advertising