Dell PowerVault 56F Dell PowerVault 56F 16-Port Fibre Channel Switch Inst - Page 142

Dell_FC_Switch# 0x103fce60 tTimers: Oct 14 11:07:43

Get Dell PowerVault 56F PDF manuals and user guides View all Dell PowerVault 56F manuals
Add to My Manuals
Save this manual to your list of manuals

Page 142 highlights

The software includes several message queues that are used for inter-task communication. Each queue holds a maximum of 64 messages. Under normal operations, a task sends a message to another task on a queue, and occupies a slot in the queue. After the message is received, its slot in the queue is open for another message. If the receiving task does not run for a period of time, and the sender task sends more than 64 messages to the same queue before the first message is processed by the receiving task, the queue overflows and the message is discarded. This event causes the MQ-QWRITE error to be printed on the display, as well as on the Telnet window, if open. The error is also stored in the error log which can be viewed with the errShow command. NOTE: The error log is cleared upon reboot. There may be several reasons for this error. In some cases, the system may recover without human intervention, however in most cases it will not. In some cases, the error can even indicate a task crash. These problems can be diagnosed by technical support provided enough information is collected to allow a detailed analysis of the specific case. The MQ-QWRITE error message is shown in Figure A-2 (the front panel displays an abridged version of the message). Dell_FC_Switch# 0x103fce60 (tTimers): Oct 14 11:07:43 Error MQ-QWRITE, 1, mqWrite failed, queue = 0x103d1d20, msg = 0x103fd3d0, errno = 0x3d0002 Traceback: _mqWrite+0x44 (0x10065864) _mPathAllShow+0x1158 (0x10078498) The most notable parameters are: The ID of the task that attempted to send the message (tTimers in Figure A-2) The queue ID (0x103d1d20 in Figure A-2) The message pointer (0x103fd3d0 in Figure A-2) The following commands should be executed, and their output, together with the complete message log should be used when analyzing the error. NOTE: Some of these commands can only be run from the root account. Table A-3 describes commands for gathering errors. A-6 Installation and Troubleshooting Guide

  • 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
A-6
Installation and Troubleshooting Guide
Ê;É;ÌÇ)Ï6·6´´½´
The software includes several message queues that are used for inter-task communi-
cation. Each queue holds a maximum of 64 messages. Under normal operations, a
task sends a message to another task on a queue, and occupies a slot in the queue.
After the message is received, its slot in the queue is open for another message.
If the receiving task does not run for a period of time, and the sender task sends more
than 64 messages to the same queue before the first message is processed by the
receiving task, the queue overflows and the message is discarded. This event causes
the
MQ-QWRITE
error to be printed on the display, as well as on the
Telnet
window,
if open. The error is also stored in the error log which can be viewed with the
errShow
command.
NOTE: The error log is cleared upon reboot.
There may be several reasons for this error. In some cases, the system may recover
without human intervention, however in most cases it will not. In some cases, the
error can even indicate a task crash.
These problems can be diagnosed by technical support provided enough information
is collected to allow a detailed analysis of the specific case.
The MQ-QWRITE error message is shown in Figure A-2 (the front panel displays an
abridged version of the message).
±²³´µ¶·0¹Ìº··&:¹:"-.È+·+µµ¼µ·+4¿!ÏÀ¶
The most notable parameters are:
¿
The ID of the task that attempted to send the message (
tTimers
in Figure A-2)
¿
The queue ID (
0x103d1d20
in Figure A-2)
¿
The message pointer (
0x103fd3d0
in Figure A-2)
The following commands should be executed, and their output, together with the
complete message log should be used when analyzing the error.
NOTE: Some of these commands can only be run from the root account.
Table A-3 describes
ÏEËEF/1$(
commands for gathering errors.
Dell_FC_Switch# 0x103fce60 (tTimers): Oct 14 11:07:43
Error MQ-QWRITE, 1, mqWrite failed,
queue = 0x103d1d20, msg = 0x103fd3d0,
errno = 0x3d0002
Traceback:
_mqWrite+0x44 (0x10065864)
_mPathAllShow+0x1158 (0x10078498)