HP StorageWorks 2/32 SAN switch 2/32, version 4.0.2b release notes - Page 27

Known Issues MIB and SNMP To reduce security exposures, the following functionality has been removed from the MIB: • Firmware download • Configuration file download • Configuration file upload This was accomplished by removing support for the following MIBs: • swFwUpgrade • swCfUpload • swCfDownload NOTE: Use the API or other management methods to access these functions. Zoning The following summarizes zoning limitations. • If the zoneset members between two switches are not listed in the same order in both configurations, the configurations are considered a mismatch, resulting in the switches segmenting in the fabric. For example: cfg1 = z1; z2 is different from cfg1 = z2; z1, even though members of the configuration are the same. Workaround: If zoneset members between two switches have the same name defined in the configuration, make sure zoneset members are listed in the same order. One simple approach to making sure that the zoneset members are in the same order is to keep the members in alphabetical order. • The zone configuration file may not propagate because of size issues. Workaround: When merging a switch into an existing fabric, make sure the allotted zone database size of the joining switch is larger than the zone database size that is currently deployed in the fabric. The maximum storage size allocated for the zone database varies between switch models, so use the cfgsize command to verify that the actual configuration is less than the maximum allocated memory for the zoning database. • When the "default access when zoning is not active" feature is set to "0", and no zoning configuration is in effect, the switch enforces a "dummy_zone" and a "null_zone" that appear in the configUpload files. SAN switch 2/32, version 4.0.2b release notes 27