Cisco N5K-C5010P-BF Troubleshooting Guide - Page 106

Merge failure troubleshooting, show cfs merge status name, show cfs peers name

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

Page 106 highlights

Cisco Fabric Services Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. Total number of switches = 3 switch Logical [VSAN 10] Merge Status: Success [ Thu Aug 5 11:36:43 2010 ] Local Fabric Domain Switch WWN IP Address 83 20:00:00:0d:ec:24:5b:c0 172.25.183.123 [Merge Master] 5 20:00:00:0d:ec:50:09:00 172.25.183.42 82 20:00:00:0d:ec:da:6e:00 172.25.183.124 switch Total number of switches = 3 Logical [VSAN 50] Merge Status: Success [ Thu Aug 5 11:36:23 2010 ] Local Fabric Domain Switch WWN IP Address 28 20:00:00:0d:ec:24:5b:c0 172.25.183.123 [Merge Master] 235 20:00:00:0d:ec:50:09:00 172.25.183.42 66 20:00:00:0d:ec:da:6e:00 172.25.183.124 switch Total number of switches = 3 Logical [VSAN 100] Merge Status: Success [ Thu Aug 5 11:33:50 2010 ] Local Fabric Domain Switch WWN IP Address 100 20:00:00:0d:ec:24:5b:c0 172.25.183.123 [Merge Master] 111 20:00:00:0d:ec:50:09:00 172.25.183.42 90 20:00:00:0d:ec:da:6e:00 172.25.183.124 switch Total number of switches = 3 If the list of switches in the show cfs merge status name command output is shorter than that of the show cfs peers name command output, then the fabric is partitioned into multiple CFS fabrics and the merge status may show that the merge has failed, is pending, or is waiting. Merge failure troubleshooting During a merge, the merge managers in the merging fabrics exchange their configuration databases with each other. The application on one of the fabrics merges the information, decides if the merge is successful, and informs all switches in the combined fabric of the status of the merge. When a merge is successful, the merged database is distributed to all switches in the combined fabric and the entire new fabric remains in a consistent state. A merge failure indicates that the merged fabrics contain inconsistent data that could not be merged. 5-34 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-34
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Cisco Fabric Services
switch
Total number of switches = 3
Logical [VSAN 10] Merge Status: Success [ Thu Aug
5 11:36:43 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Domain Switch WWN
IP Address
--------------------------------------------------------------------------------
83
20:00:00:0d:ec:24:5b:c0 172.25.183.123
[Merge Master]
5
20:00:00:0d:ec:50:09:00 172.25.183.42
82
20:00:00:0d:ec:da:6e:00 172.25.183.124
switch
Total number of switches = 3
Logical [VSAN 50] Merge Status: Success [ Thu Aug
5 11:36:23 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Domain Switch WWN
IP Address
--------------------------------------------------------------------------------
28
20:00:00:0d:ec:24:5b:c0 172.25.183.123
[Merge Master]
235
20:00:00:0d:ec:50:09:00 172.25.183.42
66
20:00:00:0d:ec:da:6e:00 172.25.183.124
switch
Total number of switches = 3
Logical [VSAN 100] Merge Status: Success [ Thu Aug
5 11:33:50 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Domain Switch WWN
IP Address
--------------------------------------------------------------------------------
100
20:00:00:0d:ec:24:5b:c0 172.25.183.123
[Merge Master]
111
20:00:00:0d:ec:50:09:00 172.25.183.42
90
20:00:00:0d:ec:da:6e:00 172.25.183.124
switch
Total number of switches = 3
If the list of switches in the
show cfs merge status name
command output is shorter than that of the
show cfs peers name
command output, then the fabric is partitioned into multiple CFS fabrics and the
merge status may show that the merge has failed, is pending, or is waiting.
Merge failure troubleshooting
During a merge, the merge managers in the merging fabrics exchange their configuration databases with
each other. The application on one of the fabrics merges the information, decides if the merge is
successful, and informs all switches in the combined fabric of the status of the merge.
When a merge is successful, the merged database is distributed to all switches in the combined fabric
and the entire new fabric remains in a consistent state. A merge failure indicates that the merged fabrics
contain inconsistent data that could not be merged.