Cisco N5K-C5010P-BF Troubleshooting Guide - Page 155

Mutual exclusion check failed on peer, Merge Failure

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 155 highlights

Chapter 9 Troubleshooting Config-Sync Issues Merge Failure Send document comments to [email protected]. Use the show system internal csm info global-db cmd-tbl command to determine if the command exists in the global_db. • If the command exists in the global_db, it is possible that there is not enough space in the show run for the command. Ensure that there are no trailing space/tabs in show running config generation. • If the command does not exist in the global_db, use the show accounting log command to determine if the command was configured and to display the status of the command. - If the command status was a failure, then the command should not be displayed in show running. - If the command is displayed, then the application should correct it. • If the command was configured before reload/issu, add the command back. If the accounting log shows the command's retval as success, determine if the command is getting added to the global-db. - If the command was added correctly, copy r s, check global-db reload, and check if the command exists in the global-db. - If the command does not exist in the global-db, then the issue might be that the command is not showing up in show running on boot up. - If the command does not exist in the global_db, investigate the csm_save_global_command function. The csm_save_global_command function is where the command gets added to the global_db Mutual exclusion check failed on peer Possible Cause The imported configuration is sent to the peer. However, if the configuration is already configured on the peer outside of SP, then the import fails the mutual exclusion check on the peer. Solution Remove the failed commands from conf-t on the peer and then retry import verify/commit. Use the show system internal csm info trace command for further investigation to look at events, trace, or error messages. Merge Failure A merge between peers happens when a peer becomes reachable. A merge is initiated when CFS sends a peer add for the peer or if the peer is already reachable. Configuring the sync-peer command starts the merge session. Note For a merge to succeed, the configuration in the switch-profile on both peers must match exactly. Merge failure has many possible causes: • First time merge failure • Merge after peers that were in sync previously • Merge after reload OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 9-5

  • 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].
9-5
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 9
Troubleshooting Config-Sync Issues
Merge Failure
Use the
show system internal csm info global-db cmd-tbl
command to determine if the command
exists in the global_db.
•
If the command exists in the global_db, it is possible that there is not enough space in the show run
for the command. Ensure that there are no trailing space/tabs in show running config generation.
•
If the command does not exist in the global_db, use the
show accounting log
command to determine
if the command was configured and to display the status of the command.
–
If the command status was a failure, then the command should not be displayed in show running.
–
If the command is displayed, then the application should correct it.
•
If the command was configured before reload/issu, add the command back. If the accounting log
shows the command’s retval as success, determine if the command is getting added to the global-db.
–
If the command was added correctly, copy r s, check global-db reload, and check if the
command exists in the global-db.
–
If the command does not exist in the global-db, then the issue might be that the command is not
showing up in show running on boot up.
–
If the command does not exist in the global_db, investigate the csm_save_global_command
function. The csm_save_global_command function is where the command gets added to the
global_db
Mutual exclusion check failed on peer
Possible Cause
The imported configuration is sent to the peer. However, if the configuration is already configured on
the peer outside of SP, then the import fails the mutual exclusion check on the peer.
Solution
Remove the failed commands from conf-t on the peer and then retry import verify/commit.
Use the
show system internal csm info trace
command for further investigation to look at events, trace,
or error messages.
Merge Failure
A merge between peers happens when a peer becomes reachable.
A merge is initiated when CFS sends a peer add for the peer or if the peer is already reachable.
Configuring the sync-peer command starts the merge session.
Note
For a merge to succeed, the configuration in the switch-profile on both peers must match exactly.
Merge failure has many possible causes:
•
First time merge failure
•
Merge after peers that were in sync previously
•
Merge after reload