Cisco III System Message Guide - Page 284

Sys-7, Sys_controller Messages, Sys_controller-3

Page 284 highlights

SYS_CONTROLLER Messages Chapter 2 Messages and Recovery Procedures SYS-7 Error Message %SYS-7-NV_LOCK_EACCES: Failed to acquire/release nvram lock at [chars]:[dec]. REQ path: [chars] pid:[dec] proc: [chars] RFS client:[dec] c/s:[dec]/[dec] mode:[dec]. OWN nv_ifs_path: [chars] proc: [chars] RFS client:[dec] c/s:[dec]/[dec] rfs_ac:[dec] nv_ifs_pid:[dec] local_lock:[dec] rfs_lock:[dec] last_req:[dec] nv_fs_ac:[dec] nv_ifs_trace: [chars] Explanation A request to release NVRAM has failed. Recommended Action This message can be ignored if it is seen during a switchover, reload, or bootup. If this message is seen under normal conditions, Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. SYS_CONTROLLER Messages This section contains system controller (SYS_CONTROLLER) messages. SYS_CONTROLLER-3 Error Message %SYS_CONTROLLER-3-CREATE_IBC_FAILED: Creation of ibc idb failed Explanation The IBC IDB creation has failed. Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Error Message %SYS_CONTROLLER-3-INIT_IBC_FAILED: Initialization of ibc failed Explanation IBC initialization has failed. Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at 2-254 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02

  • 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
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368

2-254
Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY
OL-11469-02
Chapter 2
Messages and Recovery Procedures
SYS_CONTROLLER Messages
SYS-7
Error Message
%SYS-7-NV_LOCK_EACCES: Failed to acquire/release nvram lock at
[chars]:[dec]. REQ path: [chars] pid:[dec] proc: [chars] RFS client:[dec]
c/s:[dec]/[dec] mode:[dec]. OWN nv_ifs_path: [chars] proc: [chars] RFS
client:[dec] c/s:[dec]/[dec] rfs_ac:[dec] nv_ifs_pid:[dec] local_lock:[dec]
rfs_lock:[dec] last_req:[dec] nv_fs_ac:[dec] nv_ifs_trace: [chars]
Explanation
A request to release NVRAM has failed.
Recommended Action
This message can be ignored if it is seen during a switchover, reload, or bootup.
If this message is seen under normal conditions, Copy the error message exactly as it appears on the
console or in the system log. Research and attempt to resolve the error using the Output Interpreter
Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
SYS_CONTROLLER Messages
This section contains system controller (SYS_CONTROLLER) messages.
SYS_CONTROLLER-3
Error Message
%SYS_CONTROLLER-3-CREATE_IBC_FAILED: Creation of ibc idb failed
Explanation
The IBC IDB creation has failed.
Recommended Action
Copy the error message exactly as it appears on the console or in the system
log. Research and attempt to resolve the issue using the tools and utilities provided at
. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at
, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the
show logging
and
show tech-support
commands and your
pertinent troubleshooting logs.
Error Message
%SYS_CONTROLLER-3-INIT_IBC_FAILED: Initialization of ibc failed
Explanation
IBC initialization has failed.
Recommended Action
Copy the error message exactly as it appears on the console or in the system
log. Research and attempt to resolve the issue using the tools and utilities provided at
. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at