HP StorageWorks 16-EL HP StorageWorks Zoning V3.1.x/4.1.x User Guide (AA-RS26C - Page 42

Resolving Zone Conflicts, configupload, cfgClear, cfgDisable, portDisable/portEnable

Get HP StorageWorks 16-EL - SAN Switch PDF manuals and user guides View all HP StorageWorks 16-EL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

Zoning Concepts Table 3: Zone Merging Scenarios (Continued) Description Same content; different effective cfg name. Switch A defined: cfg1 zone1: ali1; ali2 effective: cfg1 zone1: ali1; ali2 Same content; different zone name. defined: cfg1 zone1: ali1; ali2 effective: irrelevant Same content; defined: cfg1:ali1: A; different alias name. B effective: irrelevant Same name; different types. effective: zone1: MARKETING Same name; different types. effective: zone1: MARKETING Same name; different types. effective: cfg1: MARKETING Switch B defined: cfg2 zone1: ali1; ali2 effective:cfg2 zone1: ali1; ali2 defined: cfg1 zone2: ali1; ali2 effective: irrelevant defined: cfg1:ali2: A; B effective: irrelevant effective: cfg1: MARKETING effective: alias1: MARKETING effective: alias1: MARKETING Expected Results Fabric segments due to Zone Conflictcfg mismatch. Fabric segments due to Zone Conflict content mismatch. Fabric segments due to Zone Conflictcontent mismatch. Fabric segments due to Zone Conflicttype mismatch. Fabric segments due to Zone Conflicttype mismatch. Fabric segments due to Zone Conflicttype mismatch. Resolving Zone Conflicts Zone conflicts can be resolved by using configupload and performing a cut and paste operation so the config info matches in both fabrics being merged. Zone conflicts can also be resolved by performing a cfgClear followed by a cfgDisable on the segmented fabric that is incorrectly configured. Then do a portDisable/portEnable on one of the ISL ports that connects the fabrics. This will cause a merge that will make the fabric consistent with the good configuration. Be careful in using the cfgClear command; this command can inadvertently delete the zone configuration in the fabric. 42 Zoning Version 3.1.x/4.1.x User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
Zoning Concepts
42
Zoning Version 3.1.x/4.1.x User Guide
Resolving Zone Conflicts
Zone conflicts can be resolved by using
configupload
and performing a cut
and paste operation so the config info matches in both fabrics being merged.
Zone conflicts can also be resolved by performing a
cfgClear
followed by a
cfgDisable
on the segmented fabric that is incorrectly configured. Then do a
portDisable/portEnable
on one of the ISL ports that connects the fabrics.
This will cause a merge that will make the fabric consistent with the good
configuration. Be careful in using the
cfgClear
command; this command can
inadvertently delete the zone configuration in the fabric.
Same content;
different effective
cfg name.
defined: cfg1
zone1: ali1; ali2
effective: cfg1
zone1: ali1; ali2
defined: cfg2
zone1: ali1; ali2
effective:cfg2
zone1: ali1; ali2
Fabric segments due to
Zone Conflictcfg
mismatch.
Same content;
different zone
name.
defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone2: ali1; ali2
effective: irrelevant
Fabric segments due to
Zone Conflict content
mismatch.
Same content;
different alias name.
defined: cfg1:ali1: A;
B
effective: irrelevant
defined: cfg1:ali2: A;
B
effective: irrelevant
Fabric segments due to
Zone Conflictcontent
mismatch.
Same name;
different types.
effective: zone1:
MARKETING
effective: cfg1:
MARKETING
Fabric segments due to
Zone Conflicttype
mismatch.
Same name;
different types.
effective: zone1:
MARKETING
effective: alias1:
MARKETING
Fabric segments due to
Zone Conflicttype
mismatch.
Same name;
different types.
effective: cfg1:
MARKETING
effective: alias1:
MARKETING
Fabric segments due to
Zone Conflicttype
mismatch.
Table 3:
Zone Merging Scenarios (Continued)
Description
Switch A
Switch B
Expected Results