• Housekeeping - Using Sandb Zonecheck To Remove Obsolete Zones
• Name
• Description
• Procedure

Housekeeping - Using Sandb Zonecheck To Remove Obsolete Zones

Name

eusan-mgt1:/opt/emc/sandb/TOOLS/zone_check -file <xml_filename>

Description

This document details the required procedure for obsolete zone removals for the London campus.

When a host is decomissioned from the san environment, the zones are left in place for a few weeks in case any removed storage needs to be re-activated.

These zones will eventually need to be removed from the environment, which used to be a manual process, but was prone to human error.

Zone_check allows a SAN administrator to parse an XML file that is taken from Connectrix Manager and remove any zones which have become obsolete.

Procedure

The first stage of this process is to export the current zone_set from within the Connectrix Manager fabric that you intend to parse. To do this, launch Connectrix Manager, go to the zoning window, and select export, to export the current zoneset to /tmp/<cgc|rdc>_<red|blue>_cleanup_date.xml.

If the fabric that you are parsing happens to be in the RDC building, you will need to scp the file to /tmp on eusan-mgt1.

To do this :

scp filename.xml username@eusan-mgt1:/tmp

Now that the xml file is in place, run the zone_check script against the xml file to produce a list of zones to be verified as follows:

 bash-2.03$ /opt/emc/sandb/TOOLS/zone_check -file /tmp/cgc_red_cleanup.xml
 ERROR : WWN element not defined for zone ukfxprsd05_1811_07ba   : 10000000c92ed55b
 ERROR : WWN association not found for ldneqtsdca500dr_0587_04ba : 500604844a3726d3|10000000c9544213
 ERROR : WWN element not defined for zone clonecgc-c_1081_03aa   : 50060b0000bdd41a
 ERROR : WWN element not defined for zone eqsor1c_1067_03da      : 10000000c95ad0a2
 ERROR : WWN element not defined for zone ukfxprsd29_1067_04ca   : 10000000c9416061
 ERROR : WWN association not found for ldneqtsdca500dr_0587_03da : 10000000c9544213|5006048c4a3726d2
 ERROR : WWN element not defined for zone eqsor2c_1067_03da      : 10000000c95ad0e5
 ERROR : WWN element not defined for zone clonecgc-6_1081_03aa   : 50060b0000bdd448
 ERROR : WWN element not defined for zone loncgceccinf02_1868_03ab       : 5006048452a69b22
 ERROR : WWN element not defined for zone clonecgc-8_1081_03aa   : 50060b0000bdd44a
 ERROR : WWN association not found for ldneqtsdds500dr_1811_04ba : 5006048449afa0d3|10000000c954420f
 ERROR : WWN association not found for ldneqtsdcb500dr_0587_04ba : 10000000c95442fd|500604844a3726d3
 ERROR : WWN association not found for ukfiprsd03_0294_07ba      : 500604844a36dd96|10000000c9516f7e
 ERROR : WWN element not defined for zone clonecgc-0_1081_03aa   : 50060b0000bdd44e

Now parse the above list and verify each entry for removal.

The output will give 2 separate error codes:

 ERROR : WWN element not defined for zone <zonename > : This means that the WWN element listed is not found within sandb (possible decomission)

 ERROR : WWN association not found for <zonename>     : This means that sandb has not found any association required by this zone.

To check each line of output, use the symmaskdb command to verify that the appropriate WWN is now not masked to any devices within symapi database:

 bash-2.03$ symmaskdb -sid 587 -wwn 10000000c9544213 list devs

 Symmetrix ID        : 000287890587

 Originator Port wwn : 10000000c9544213
 User-generated Name : ldneqtsdca500dr/lpfc0

 No Devices were found for that WWN

Repeat the above step for each line of output, and save the results in the weekend workplan for zone removal on a Saturday.

YOU MUST CHECK EVERY SINGLE LINE OF OUTPUT - IF IN DOUBT, DO NOT INCLUDE THE ZONE FOR REMOVAL - SPEAK TO ME!

Where a WWN is found within the symapi database, please mail tim1.robinson@citigroup.com, giving details of the zone that is required to add into the zone_check exceptions list (an example of this is where new gatekeeper zones/management zones are added which sandb will need to be manually told about).