73C787F 1219091606 I S topsvcs Possible malfunction on local adapter
FE2DEE00 1218184106 P S SYSXAIXIF 网络中检测到重复的 IP 地址
173C787F 1218184006 I S topsvcs Possible malfunction on local adapter
173C787F 1218184006 I S topsvcs Possible malfunction on local adapter
FE2DEE00 1217164906 P S SYSXAIXIF 网络中检测到重复的 IP 地址
173C787F 1217164906 I S topsvcs Possible malfunction on local adapter
173C787F 1217164906 I S topsvcs Possible malfunction on local adapter
625E6B9A 1215085506 P H ssa0 适配器检测到纯??辛绰
91FBD5DB 1215085306 P S ssa0 软件程写砦
91FBD5DB 1214185206 P S ssa0 软件程写砦
FE2DEE00 1214184906 P S SYSXAIXIF 网络中检测到重复的 IP 地址
FE2DEE00 1214184906 P S SYSXAIXIF 网络中检测到重复的 IP 地址
173C787F 1214184906 I S topsvcs Possible malfunction on local adapter
173C787F 1214184906 I S topsvcs Possible malfunction on local adapter
864D2CE3 1211150306 P S topsvcs NIM thread blocked
864D2CE3 1211150306 P S topsvcs NIM thread blocked
4FDB3BA1 1211150306 I S topsvcs DeadMan Switch (DMS) close to trigger
864D2CE3 1211150306 P S topsvcs NIM thread blocked
864D2CE3 1211150306 P S topsvcs NIM thread blocked
864D2CE3 1211150306 P S topsvcs NIM thread blocked
864D2CE3 1211150306 P S topsvcs NIM thread blocked
864D2CE3 1211150306 P S topsvcs NIM thread blocked
3C81E43F 1211150306 P U topsvcs Late in sending heartbeat
864D2CE3 1211150306 P S topsvcs NIM thread blocked
＃errpt -aj 864D2CE3 | pg
---------------------------------------------------------------------------
标签： TS_NIM_ERROR_STUCK_
标识符： 864D2CE3
日期／时间： 公元2006年12月11日 星期
泻牛? 2173
机器 Id： 005CF58A4C00
节点 Id： xxopaa
类： S
类型： PERM
资源名： topsvcs
说明
NIM thread blocked
可能原
A thread in a Topology Services Network Interface Module (NIM) process
was blocked
Topology Services NIM process cannot get timely access to CPU
用户原
Excessive memory consumption is causing high memory contention
Excessive disk I/O is causing high memory contention
推荐的操作
Examine I/O and memory activity on the system
Reduce load on the system
Tune virtual memory parameters
Call IBM Service if problem persists
失败原
Excessive virtual memory activity prevents NIM from making progress
Excessive disk I/O traffic is interfering with paging I/O
推荐的操作
Examine I/O and memory activity on the system
Reduce load on the system
Tune virtual memory parameters
Call IBM Service if problem persists
详细数据
检测模块
rsct,nim_control.C,1.29,5242
错误标识
6XnGH40A9ET3/8fW11g.3g0...................
参考码
Thread which was blocked
send thread
Interval in seconds during which process was blocked
180
Interface name
en1
错误信息如上:客户的机器是5100-04,HA是4.5。
处理方法如下：
IY55756: TS_NIM_ERROR_STUCK_ WHILE REPLACING IP ADDRESS BY HACMP.
![]()
![]()
APAR status
Closed as program error.
Error description Following errpt entry was logged while replacing IP address on
an adapter in a HACMP cluster without any acual error.
Those messages when calling send_error_notification in the nim
code should be suppressed.
It is related to defect 90406 but not caused by it.
.
LABEL: TS_NIM_ERROR_STUCK_
Class: S
Type: PERM
Resource Name: topsvcs
Description
NIM thread blocked
Probable Causes
A thread in a Topology Services Network Interface Module (NIM)
process was blocked
Topology Services NIM process cannot get timely access to CPU
User Causes
Excessive memory consumption is causing high memory contention
Excessive disk I/O is causing high memory contention
Recommended Actions
Examine I/O and memory activity on the system
Reduce load on the system
Tune virtual memory parameters
Call IBM Service if problem persists
Failure Causes
Excessive virtual memory activity prevents NIM from making
progress Excessive disk I/O traffic is interfering with paging
I/O
Recommended Actions
Examine I/O and memory activity on the system
Reduce load on the system
Tune virtual memory parameters
Call IBM Service if problem persists
Detail Data
DETECTING MODULE
rsct,nim_control.C,1.30.1.2,5399
ERROR ID
6XnGH40iStN.//GZ0JAXZo0...................
REFERENCE CODE
Thread which was blocked
command receive thread
Interval in seconds during which process was blocked
12
Interface name
en2
Local fix Problem summary In HACMP/ES, when a node is acquiring or releasing service
addresses it is possible for AIX error log entries such
as the following to appear:
LABEL: TS_NIM_ERROR_STUCK_
IDENTIFIER: 864D2CE3
Date/Time: Wed Apr 14 23:47:20 EST
...
Thread which was blocked
commmand receive thread
Interval in seconds during which process was blocked
7
Interface name
en1
The error log entry is harmless; it is caused by
one of RSCT Topology Services's Network Interface Module
(NIM) processes taking a few seconds to process the
operations involved during HW Address Takeover. Had the
error log entry appeared in steady state operation, this
would have indicated a real thread blockage problem.
Problem conclusion The problem was caused by the code in RSCT Topology
Services's Network Interface Module (NIM) not recognizing
instances during Hardware Address Takeover (HWAT) when
threads take a few seconds to complete a certain operation.
This apparent "blockage" causes the NIM to issue (via the
Topology Services daemon) the TS_NIM_ERROR_STUCK_ AIX
error log entry.
The code in the NIM is being changed to verify that the
connection with the adapter is open, prior to making the
TS_NIM_ERROR_STUCK_ error log entry, to prevent any
false error log entries from being made.
Temporary fix Comments
| APAR information |
| APAR number |
IY55756 |
| Reported component name |
RSCT V510 |
| Reported component ID |
5765E6110 |
| Reported release |
221 |
| Status |
CLOSED PER |
| PE |
NoPE |
| HIPER |
NoHIPER |
| Submitted date |
2004-04-15 |
| Closed date |
2004-04-28 |
| Last modified date |
2006-01-16 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Publications Referenced
|
|
| Fixed component name |
RSCT V510 |
| Fixed component ID |
5765E6110 |
| Applicable component levels |
| R221 PSY U806671 |
UP06/01/16 I 1000 |
IY56353: TS_NIM_ERROR_STUCK_ WHILE REPLACING IP ADDRESS BY HACMP.![]()
|
This record will be updated with a link to the fix if the APAR is new.
For APARs older than 365 days, contact your support center. |
![]()
APAR status
Closed as program error.
Error description Following errpt entry was logged while replacing IP address on
an adapter in a HACMP cluster without any acual error.
Those messages when calling send_error_notification in the nim
code should be suppressed.
It is related to defect 90406 but not caused by it.
.
LABEL: TS_NIM_ERROR_STUCK_
Class: S
Type: PERM
Resource Name: topsvcs
Description
NIM thread blocked
Probable Causes
A thread in a Topology Services Network Interface Module (NIM)
process was blocked
Topology Services NIM process cannot get timely access to CPU
User Causes
Excessive memory consumption is causing high memory contention
Excessive disk I/O is causing high memory contention
Recommended Actions
Examine I/O and memory activity on the system
Reduce load on the system
Tune virtual memory parameters
Call IBM Service if problem persists
Failure Causes
Excessive virtual memory activity prevents NIM from making
progress Excessive disk I/O traffic is interfering with paging
I/O
Recommended Actions
Examine I/O and memory activity on the system
Reduce load on the system
Tune virtual memory parameters
Call IBM Service if problem persists
Detail Data
DETECTING MODULE
rsct,nim_control.C,1.30.1.2,5399
ERROR ID
6XnGH40iStN.//GZ0JAXZo0...................
REFERENCE CODE
Thread which was blocked
command receive thread
Interval in seconds during which process was blocked
12
Interface name
en2
Local fix Problem summary In HACMP/ES, when a node is acquiring or releasing service
addresses it is possible for AIX error log entries such
as the following to appear:
LABEL: TS_NIM_ERROR_STUCK_
IDENTIFIER: 864D2CE3
Date/Time: Wed Apr 14 23:47:20 EST
...
Thread which was blocked
commmand receive thread
Interval in seconds during which process was blocked
7
Interface name
en1
The error log entry is harmless; it is caused by
one of RSCT Topology Services's Network Interface Module
(NIM) processes taking a few seconds to process the
operations involved during HW Address Takeover. Had the
error log entry appeared in steady state operation, this
would have indicated a real thread blockage problem.
Problem conclusion The problem was caused by the code in RSCT Topology
Services's Network Interface Module (NIM) not recognizing
instances during Hardware Address Takeover (HWAT) when
threads take a few seconds to complete a certain operation.
This apparent "blockage" causes the NIM to issue (via the
Topology Services daemon) the TS_NIM_ERROR_STUCK_ AIX
error log entry.
The code in the NIM is being changed to verify that the
connection with the adapter is open, prior to making the
TS_NIM_ERROR_STUCK_ error log entry, to prevent any
false error log entries from being made.
Temporary fix Comments
| APAR information |
| APAR number |
IY56353 |
| Reported component name |
RSCT/RMC FOR CS |
| Reported component ID |
5765F07AP |
| Reported release |
233 |
| Status |
CLOSED PER |
| PE |
NoPE |
| HIPER |
NoHIPER |
| Submitted date |
2004-04-29 |
| Closed date |
2004-04-29 |
| Last modified date |
2004-04-29 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Publications Referenced
|
|
| Fixed component name |
RSCT/RMC FOR CS |
| Fixed component ID |
5765F07AP |
| Applicable component levels |
| R233 PSY |
UP | |
IY38496: TS_NIM_ERROR_STUCK_ WHILE CLUSTER STARTUP/SHUTDOWN.![]()
![]()
APAR status
Closed as program error.
Error description Following errpt entry was logged while start up/shutdown of
cluster without any acual error.
.
LABEL : TS_NIM_ERROR_STUCK_
Resource Name: topsvcs
Description : NIM thread blocked
.
Probable Causes
A thread in Topology Services NIM process was blocked
Topology Services NIM process cannot get timely access to CPU
.
Detail Data
DETECTING MODULE
rsct,nim_control.C,1.19,5046
Interface name : en1
.
According to a dev., It's known behavior of nim. But user hope
supress of such ambiguous error logging.
Local fix Problem summary In HACMP/ES, when a node is acquiring or releasing service
addresses (including at cluster startup and shutdown), it
is possible for AIX error log entries such as the
following to appear:
LABEL: TS_NIM_ERROR_STUCK_
IDENTIFIER: 864D2CE3
Date/Time: Wed Jan 29 23:47:20 EST
...
Thread which was blocked
main thread
Interval in seconds during which process was blocked
7
Interface name
tr1
The error log entry is harmless; it is caused by
one of RSCT Topology Services's Network Interface Module
(NIM) processes taking a few seconds to process the
operations involved during IP Address Takeover. Had the
error log entry appeared in steady state operation, this
would have indicated a real thread blockage problem.
Problem conclusion The problem was caused by the code in RSCT Topology
Services's Network Interface Module (NIM) not recognizing
a special case during IP Address Takeover (IPAT): the NIM
process's main thread takes a few seconds to complete a
certain operation. This apparent "blockage" causes the NIM
to issue (via the Topology Services daemon) the
TS_NIM_ERROR_STUCK_ AIX error log entry.
The code in the NIM is being fixed to recognize the special
IPAT case, so that no "false" TS_NIM_ERROR_STUCK_ error
entry is issued.
Temporary fix Comments
| APAR information |
| APAR number |
IY38496 |
| Reported component name |
RSCT V510 |
| Reported component ID |
5765E6110 |
| Reported release |
221 |
| Status |
CLOSED PER |
| PE |
NoPE |
| HIPER |
NoHIPER |
| Submitted date |
2003-01-02 |
| Closed date |
2003-02-05 |
| Last modified date |
2003-04-17 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
IY40268 U488052
Publications Referenced
|
|
| Fixed component name |
RSCT V510 |
| Fixed component ID |
5765E6110 |
| Applicable component levels |
| R221 PSY U488305 |
UP03/04/17 I 1000 | |
|
IY84632: TS_NIM_ERROR_STUCK_ FOR DISKHB NETWORK ONLY![]()
APAR status
Closed as suggestion for future release.
Error description TS_NIM_ERROR_STUCK_ errors for just the diskhb network.
The diskhb is a fastT disk and whenever any LUN is changed
that is on the same controller as the diskhb, you will get
the TS_NIM_ERROR_STUCK_ error for a 6-9 second span.
Local fix Ignore the error if it is just for the diskhb network and
is only occuring when lun changes are made.
Problem summary Problem conclusion Temporary fix Comments This design change request will be implemented in the next
release.F
| APAR information |
| APAR number |
IY84632 |
| Reported component name |
RSCT/RMC FOR CS |
| Reported component ID |
5765F07AP |
| Reported release |
238 |
| Status |
CLOSED SUG |
| PE |
NoPE |
| HIPER |
NoHIPER |
| Submitted date |
2006-05-03 |
| Closed date |
2006-05-05 |
| Last modified date |
2006-05-05 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Publications Referenced
| | | |
|
阅读(11573) | 评论(3) | 转发(0) |
