Cisco N5K-C5010P-BF Troubleshooting Guide - Page 156

First time merge failure, Merge after peers that were in sync previously, Merge after reload

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

Switch-profile Deletion Failure Chapter 9 Troubleshooting Config-Sync Issues Send document comments to [email protected]. Note Use the show system internal csm info trace command to view events, trace, and error messages. First time merge failure Possible Cause When peer switches are trying to synchronize configurations, the merge might fail when validating received configurations. Solution Use the show switch-profile status command to view which commands failed validation. This implies that the commands on both the switches are configured differently. Perform the following to correct the configurations: • Remove the sync-peers destination command from the switch-profile. • Use the show running switch-profile command on both peers to ensure that the configuration is exactly the same under switch-profile. • Add back the sync-peers destination command to the switch-profile. • Reissue the commit. Merge after peers that were in sync previously Possible Cause If peers were in sync and connectivity was lost, and conflicting configuration changes were made on the switches, then the merge would fail. Solution Use the show switch-profile status command to view which commands failed the merge. Correct the configurations and reissue the commit from the peer with the corrected configuration. Merge after reload Possible Cause After a switch is reloaded, it sends its switch-profile configuration to the peer. If there was a configuration change done under SP for the peer that was not reloaded, then the merge fails. Solution Use the show switch-profile status command to view which commands failed the merge. Correct the configurations and reissue the commit. Switch-profile Deletion Failure A rollback is used to delete the configurations during a switch-profile deletion. Cisco Nexus 5000 Series Troubleshooting Guide 9-6 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].
9-6
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 9
Troubleshooting Config-Sync Issues
Switch-profile Deletion Failure
Note
Use the
show system internal csm info trace
command to view events, trace, and error messages.
First time merge failure
Possible Cause
When peer switches are trying to synchronize configurations, the merge might fail when validating
received configurations.
Solution
Use the
show switch-profile status
command to view which commands failed validation.
This implies that the commands on both the switches are configured differently.
Perform the following to correct the configurations:
•
Remove the
sync-peers destination
command from the switch-profile.
•
Use the
show running switch-profile
command on both peers to ensure that the configuration is
exactly the same under switch-profile.
•
Add back the
sync-peers destination
command to the switch-profile.
•
Reissue the commit.
Merge after peers that were in sync previously
Possible Cause
If peers were in sync and connectivity was lost, and conflicting configuration changes were made on the
switches, then the merge would fail.
Solution
Use the
show switch-profile status
command to view which commands failed the merge.
Correct the configurations and reissue the commit from the peer with the corrected configuration.
Merge after reload
Possible Cause
After a switch is reloaded, it sends its switch-profile configuration to the peer. If there was a
configuration change done under SP for the peer that was not reloaded, then the merge fails.
Solution
Use the
show switch-profile status
command to view which commands failed the merge.
Correct the configurations and reissue the commit.
Switch-profile Deletion Failure
A rollback is used to delete the configurations during a switch-profile deletion.