Cisco N5K-C5010P-BF Troubleshooting Guide - Page 152

Verify failed, Commands that failed commit, Another session in progress, show switch-profile buffer

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

Commit Failure Chapter 9 Troubleshooting Config-Sync Issues Send document comments to [email protected]. This error message indicates that some feature commands have not been configured. Feature commands are not allowed to be configured within SP and have to be configured on BOTH peers from conf-t. Verify failed Possible Cause The commands listed failed mutual-exclusion checks. These commands have already been configured under conf-t. Solution If you do not want these commands synchronized, remove the commands from conf-t. Alternatively, delete these commands from the switch-profile buffer and reissue the commit. To delete commands from the switch-profile buffer, perform the following: • View commands in the SP buffer using the show switch-profile buffer command. • Delete commands indicated by the sequence numbers with the buffer delete command. • Use the buffer-move command to rearrange commands in the buffer. This is command is useful when commands in the buffer are not ordered correctly. Commands that failed commit Possible Cause Commands failed during commit. Solution Correct the reason for the failure and re-issue the commit. If the commit continues to fail, issue the same command from conf-t. If it succeeds from conf-t, check for any errors relating to the command using the show system internal csm info trace command. For every command executed from config-sync, there is a csm_cmd_status[0x0] line in the trace log that indicates that the command was successful. Another session in progress Possible Cause Conflict occurs if conf-t or config-sync has taken a lock. Solution Compare the vPC domain IDs of the two switches and ensure that they match. Use the show system internal csm global info command to check whether conf-t or config-sync has taken a lock. • If conf-t has taken a lock and not released it, command output, similar to the following example, is displayed. Note The client type should be set to 2 as shown in the example. Cisco Nexus 5000 Series Troubleshooting Guide 9-2 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-2
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 9
Troubleshooting Config-Sync Issues
Commit Failure
This error message indicates that some feature commands have not been configured. Feature commands
are not allowed to be configured within SP and have to be configured on BOTH peers from conf-t.
Verify failed
Possible Cause
The commands listed failed mutual-exclusion checks. These commands have already been configured
under conf-t.
Solution
If you do not want these commands synchronized, remove the commands from conf-t.
Alternatively, delete these commands from the switch-profile buffer and reissue the commit.
To delete commands from the switch-profile buffer, perform the following:
•
View commands in the SP buffer using the
show switch-profile buffer
command.
•
Delete commands indicated by the sequence numbers with the
buffer delete <range>
command.
•
Use the
buffer-move <seq id> <seq id>
command to rearrange commands in the buffer.
This is command is useful when commands in the buffer are not ordered correctly.
Commands that failed commit
Possible Cause
Commands failed during commit.
Solution
Correct the reason for the failure and re-issue the commit.
If the commit continues to fail, issue the same command from conf-t. If it succeeds from conf-t, check
for any errors relating to the command using the
show system internal csm info trace
command.
For every command executed from config-sync, there is a csm_cmd_status[0x0] line in the trace log that
indicates that the command was successful.
Another session in progress
Possible Cause
Conflict occurs if conf-t or config-sync has taken a lock.
Solution
Compare the vPC domain IDs of the two switches and ensure that they match.
Use the
show system internal csm global info
command to check whether conf-t or config-sync has
taken a lock.
•
If conf-t has taken a lock and not released it, command output, similar to the following example, is
displayed.
Note
The client type should be set to 2 as shown in the example.