Cisco N5K-C5010P-BF Troubleshooting Guide - Page 107

Recovering from a Merge Failure with the CLI, show cfs lock, show cfs merge status 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 107 highlights

Chapter 5 Troubleshooting SAN Switching Issues Cisco Fabric Services Send document comments to [email protected]. If a new switch is added to the fabric and the merge status for any application shows In Progress for a prolonged period of time, then there may be an active session for that application in a switch. Check the lock status for that application on all the switches by using the show cfs lock command. If any locks exist, the merge does not proceed. Commit the changes or clear the session lock so that the merge proceeds. Note Merge failures must be analyzed correctly. Exercise caution when choosing a switch for blank commit. Small configurations may wipe out the large configurations. Recovering from a Merge Failure with the CLI To recover from a merge failure using the CLI, perform the following steps: Step 1 To identify a switch that shows a merge failure, enter the show cfs merge status name command. Example: switch(config)# show cfs merge status name ntp Physical-fc-ip Merge Status: Success [ Thu Aug 5 11:47:58 2010 ] Local Fabric Switch WWN IP Address 20:00:00:0d:ec:da:6e:00 172.25.183.124 [Merge Master] switch Total number of switches = 1 switch(config)# show cfs merge status name ntp Physical-fc-ip Merge Status: Success [ Thu Aug 5 11:43:39 2010 ] Local Fabric Switch WWN IP Address 20:00:00:0d:ec:50:09:00 172.25.183.42 [Merge Master] MDS-9134 20:00:00:0d:ec:da:6e:00 172.25.183.124 Total number of switches = 2 Step 2 For a more detailed description of the merge failure, enter the show cfs internal session-history name detail command. Example: switch(config)# show cfs internal session-history name ntp Time Stamp Source WWN Event User Name Session ID Thu Aug 5 11:45:19 2010 20:00:00:0d:ec:da:6e:00 LOCK_ACQUIRED admin 34684 Thu Aug 5 11:45:19 2010 20:00:00:0d:ec:da:6e:00 COMMIT[2] admin 34689 Thu Aug 5 11:45:20 2010 20:00:00:0d:ec:da:6e:00 LOCK_RELEASED OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 5-35

  • 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-35
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Cisco Fabric Services
If a new switch is added to the fabric and the merge status for any application shows In Progress for a
prolonged period of time, then there may be an active session for that application in a switch. Check the
lock status for that application on all the switches by using the
show cfs lock
command. If any locks
exist, the merge does not proceed. Commit the changes or clear the session lock so that the merge
proceeds.
Note
Merge failures must be analyzed correctly. Exercise caution when choosing a switch for blank commit.
Small configurations may wipe out the large configurations.
Recovering from a Merge Failure with the CLI
To recover from a merge failure using the CLI, perform the following steps:
Step 1
To identify a switch that shows a merge failure, enter the
show cfs merge status name
<application-name>
command.
Example:
switch(config)# show cfs merge status name ntp
Physical-fc-ip
Merge Status: Success [ Thu Aug
5 11:47:58 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Switch WWN
IP Address
--------------------------------------------------------------------------------
20:00:00:0d:ec:da:6e:00 172.25.183.124
[Merge Master]
switch
Total number of switches = 1
switch(config)# show cfs merge status name ntp
Physical-fc-ip
Merge Status: Success [ Thu Aug
5 11:43:39 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Switch WWN
IP Address
--------------------------------------------------------------------------------
20:00:00:0d:ec:50:09:00 172.25.183.42
[Merge Master]
MDS-9134
20:00:00:0d:ec:da:6e:00 172.25.183.124
Total number of switches = 2
Step 2
For a more detailed description of the merge failure, enter the
show cfs internal session-history name
<application name>
detail
command.
Example:
switch(config)#
show cfs internal session-history name ntp
--------------------------------------------------------------------------------
Time Stamp
Source WWN
Event
User Name
Session ID
--------------------------------------------------------------------------------
Thu Aug
5 11:45:19 2010
20:00:00:0d:ec:da:6e:00
LOCK_ACQUIRED
admin
34684
Thu Aug
5 11:45:19 2010
20:00:00:0d:ec:da:6e:00
COMMIT[2]
admin
34689
Thu Aug
5 11:45:20 2010
20:00:00:0d:ec:da:6e:00
LOCK_RELEASED