Cisco N5K-C5020P-BF Troubleshooting Guide - Page 84

Full zone database synchronization failure across two switches

Get Cisco N5K-C5020P-BF - Nexus 5020 Switch PDF manuals and user guides
UPC - 882658211935
View all Cisco N5K-C5020P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 84 highlights

Zoning Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. • To further troubleshoot this issue, capture the output from the show tech-support zone command and the show logging log command. Full zone database synchronization failure across two switches A full zone database synchronization failure may occur when two switches connect using the E or TE port and have different zone set distribution policies. As a result of a fabric isolation/merge, one fabric might not have the full zone set database in the running configuration. Possible Cause The zone set distribution takes effect while sending merge requests to the adjacent switch or while activating a zone set. The zone distribute policy can be set differently on two switches and that could cause synchronization failure. Solution Use the show zone status command to verify the distribution policy on both switches. Example: VSAN: 100 default-zone: deny distribute: active only Interop: default mode: basic merge-control: allow When the distribute policy is set to active only the active zone set is distributed. Also verify that the distribute policy is set to full. To enable the full zone set and active zone set distribution to all switches on a per-VSAN basis in the configuration mode, use the zoneset distribute full vsan command. Mismatched default zone policy in switches in VSAN causes unexpected results when accessing storage A mismatched default zone policy in all switches in the VSAN in the basic zone mode might cause unexpected results for any hosts accessing storage. Possible Cause If the default zone policy is set to permit and if there is no active zone set for VSAN, then all the members of the VSAN can see all the other nodes. Solution One approach is to migrate the zone operation mode from basic to enhanced. Enhanced zoning synchronizes the zone configuration across all switches in the VSAN. This eliminates the possibility of mismatched default zone policies. • Use the show zone status command to display the status of the zone. VSAN: 300 default-zone: deny distribute: active only Interop: default mode: basic merge-control: allow • Use the zone default-zone command to set the default zone policy and use the zone mode enhanced command to set the operation to enhanced zoning mode. Another approach is the foillowing: 5-12 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01

  • 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
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
5-12
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Zoning
•
To further troubleshoot this issue, capture the output from the
show tech-support zone
command
and the
show logging log
command.
Full zone database synchronization failure across two switches
A full zone database synchronization failure may occur when two switches connect using the E or TE
port and have different zone set distribution policies. As a result of a fabric isolation/merge, one fabric
might not have the full zone set database in the running configuration.
Possible Cause
The zone set distribution takes effect while sending merge requests to the adjacent switch or while
activating a zone set.
The zone distribute policy can be set differently on two switches and that could cause synchronization
failure.
Solution
Use the
show zone status
command to verify the distribution policy on both switches.
Example:
VSAN: 100 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow
When the distribute policy is set to active only the active zone set is distributed. Also verify that the
distribute policy is set to full.
To enable the full zone set and active zone set distribution to all switches on a per-VSAN basis in the
configuration mode, use the
zoneset distribute full vsan
<vsan-id>
command.
Mismatched default zone policy in switches in VSAN causes unexpected
results when accessing storage
A mismatched default zone policy in all switches in the VSAN in the basic zone mode might cause
unexpected results for any hosts accessing storage.
Possible Cause
If the default zone policy is set to permit and if there is no active zone set for VSAN, then all the members
of the VSAN can see all the other nodes.
Solution
One approach is to migrate the zone operation mode from basic to enhanced. Enhanced zoning
synchronizes the zone configuration across all switches in the VSAN. This eliminates the possibility of
mismatched default zone policies.
•
Use the
show zone status
command to display the status of the zone.
VSAN: 300 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow
•
Use the
zone default-zone
command to set the default zone policy and use the
zone mode enhanced
<vsan-id>
command to set the operation to enhanced zoning mode.
Another approach is the foillowing: