Cisco N5K-C5010P-BF Troubleshooting Guide - Page 157

Application failure, Failure from dependent commands, Application does not respond

Page 157 highlights

Chapter 9 Troubleshooting Config-Sync Issues Switch-profile Deletion Failure Send document comments to [email protected]. Note To check for commands that failed deletion, use the show switch-profile status commit command to view the status. Alternatively, use the show switch-profile session-history command by matching the session based on the timestamp/session type. Switch-profile deletion failure has many possible causes: • Application failure • Failure from dependent commands • Application does not respond Other known switch-profile deletion issues: • Rollback fails with "Deletion of switch profile failed" message (CSCti97003) • Port-channel interface not deleted on switch-profile delete (CSCtf17697) Application failure Possible Cause Switch-profile deletion failure might be that the application failed the command. It is possible that the configuration is deleted out of order. The switch-profile does not order configurations as displayed in the show run output. There might be out of sequence issues that occur during the deletion of the switch-profile. Solution Use the resequence-database command in the conf-sync mode to resequence the commands in SP in the order that the commands appear in show running. After resequencing the commands, reissue the delete. Failure from dependent commands Possible Cause Switch-profile deletion failure results from dependent commands in conf-t mode. If a command inside SP is referenced by another command outside of SP and the first command inside SP is deleted, then failure occurs because the command outside of SP still references it. Solution Correct the commands, references, and reissue the delete. Application does not respond Possible Cause The deletion fails because the application does not respond due to the application owning the command. Solution Correct the commands and reissue the delete. OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 9-7

  • 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-7
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 9
Troubleshooting Config-Sync Issues
Switch-profile Deletion Failure
Note
To check for commands that failed deletion, use the
show switch-profile status commit
command to
view the status. Alternatively, use the
show switch-profile session-history
command by matching the
session based on the timestamp/session type.
Switch-profile deletion failure has many possible causes:
Application failure
Failure from dependent commands
Application does not respond
Other known switch-profile deletion issues:
Rollback fails with "Deletion of switch profile failed" message (CSCti97003)
Port-channel interface not deleted on switch-profile delete (CSCtf17697)
Application failure
Possible Cause
Switch-profile deletion failure might be that the application failed the command. It is possible that the
configuration is deleted out of order.
The switch-profile does not order configurations as displayed in the show run output. There might be out
of sequence issues that occur during the deletion of the switch-profile.
Solution
Use the
resequence-database
command in the conf-sync mode to resequence the commands in SP in
the order that the commands appear in show running. After resequencing the commands, reissue the
delete.
Failure from dependent commands
Possible Cause
Switch-profile deletion failure results from dependent commands in conf-t mode.
If a command inside SP is referenced by another command outside of SP and the first command inside
SP is deleted, then failure occurs because the command outside of SP still references it.
Solution
Correct the commands, references, and reissue the delete.
Application does not respond
Possible Cause
The deletion fails because the application does not respond due to the application owning the command.
Solution
Correct the commands and reissue the delete.