Deleting Zones in Bulk

Deleting Zones Using an XML File

The XML file created specifically for deleting multiple Zones to the eG Enterprise system, should contain entries of the following format:

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

<Zone action="delete">

        <Element>

        <zonename><comma-separated list of zones></zonename>

          </Element>

    </Zone>

For instance:

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

<Zone action="delete">

    <Element>

        <zonename>zone1,zone2</zonename>

    </Element>

</Zone>

Note that the XML tags are the same as the input parameters of the ‘DeleteZone’ command supported by eG CLI (see Deleting a Zone)

Once the XML file is created on the orchestrator’s host, invoke the following command from the orchestrator to update the eG manager with all the modifications contained in the XML file:

egcli deletezone -managerid <ManagerID> -file <Fullpath_to_the_XML_file>

For example:

egcli deletezone -managerid mgr153 -file E:\ bulkdeletezone.xml

Note:

• Every Zone specification should be included within the main <Zone></Zone> block only.
• A single XML file should not contain more than one <Zone></Zone> block.
• An XML file that is created for deleting Zones should not include sections pertaining to any other operation.

Deleting Zones Using a CSV File

The CSV file created specifically for deleting multiple Zones to the eG Enterprise system, should contain the following entries:

Element,action

Zone,delete

zonename

<Names of the zones>

.

.

.

For instance:

Element,action

Zone,delete

zonename

zone1

zone2

zone3

Once the CSV file is created on the orchestrator’s host, invoke the following command from the orchestrator to update the eG manager with all the modifications contained in the CSV file:

egcli deletezone -managerid <ManagerID> -file <Fullpath_to_the_CSV_file>

For example:

egcli deletezone -managerid mgr153 -file E:\ bulkzonedelete.csv