Skip to ContentSkip to Footer
시작 내용
- Community Home
- >
- HPE Community, Korea
- >
- HP-UX
- >
- 관련 event문의 ipmi_fpl
HP-UX
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
-
정보
- 커뮤니티
- Welcome
- 시작하기
- 포럼 FAQ
- 랭킹 개요
- 참여규칙
- Tips and Tricks
- 접촉
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- 다른 HPE 사이트
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
포럼
-
블로그
-
정보
-
한국어
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 친구에게 이메일 보내기
- 부적절한 컨텐트 신고
날짜: 11-02-2008 10:00 PM
날짜: 11-02-2008 10:00 PM
관련 event문의 ipmi_fpl
아래의 log를 부탁드리겠습니다.
rx4640:/]/opt/resmon/bin/resdata -R 191168514 -r /system/events/ipmi_fpl/ipmi_fpl -n 191168513 -a |more
ARCHIVED MONITOR DATA:
Event Time..........: Sat Nov 1 12:12:05 2008
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 4552
System..............: rx4640
Summary:
INIT initiated
Description of Error:
This is the equivalent of a TOC event in the PA RISC Architecture. On IPF
systems, this event is called an INIT.
This event can be triggered by the "tc" command from the MP, or from the button
labeled "TOC" or "Transfer of Control" on the Management card or bezel of the
system. There are also other causes of an INIT generated by software.
Data: Local CPU Number
Probable Cause / Recommended Action:
Software has requested an INIT or the INIT button has been pressed.
No action is required.
Additional Event Data:
System IP Address...: X.X.X.X
Event Id............: 0x490bc90500000000
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fpl_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx4640
EMS Version.....................: A.04.20
STM Version.....................: C.58.00
System Serial Number............: SGH4720697
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#4552
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
IPMI event hex: 0xf480007902e00a60 0x0000000000000002
Time Stamp: Sat Nov 1 02:55:30 2008
Event keyword: INIT_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Major change in system state
Decoded data field: System State = 2(Major Change to Log in Activity)
State Change Event = 0(At BIB)
LED Command Valid = 0(LED state is not updated)
LED Run = 0(off (default))
LED Attention = 0(reserved)
LED Stopped = 0(off (default))
Reporting entity ID: 2 ( Cab 0 Cell 0 CPU 2 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 121 (0x79)
rx4640:/]/opt/resmon/bin/resdata -R 191168514 -r /system/events/ipmi_fpl/ipmi_fpl -n 191168513 -a |more
ARCHIVED MONITOR DATA:
Event Time..........: Sat Nov 1 12:12:05 2008
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 4552
System..............: rx4640
Summary:
INIT initiated
Description of Error:
This is the equivalent of a TOC event in the PA RISC Architecture. On IPF
systems, this event is called an INIT.
This event can be triggered by the "tc" command from the MP, or from the button
labeled "TOC" or "Transfer of Control" on the Management card or bezel of the
system. There are also other causes of an INIT generated by software.
Data: Local CPU Number
Probable Cause / Recommended Action:
Software has requested an INIT or the INIT button has been pressed.
No action is required.
Additional Event Data:
System IP Address...: X.X.X.X
Event Id............: 0x490bc90500000000
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fpl_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx4640
EMS Version.....................: A.04.20
STM Version.....................: C.58.00
System Serial Number............: SGH4720697
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#4552
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
IPMI event hex: 0xf480007902e00a60 0x0000000000000002
Time Stamp: Sat Nov 1 02:55:30 2008
Event keyword: INIT_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Major change in system state
Decoded data field: System State = 2(Major Change to Log in Activity)
State Change Event = 0(At BIB)
LED Command Valid = 0(LED state is not updated)
LED Run = 0(off (default))
LED Attention = 0(reserved)
LED Stopped = 0(off (default))
Reporting entity ID: 2 ( Cab 0 Cell 0 CPU 2 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 121 (0x79)
1 응답 1
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 친구에게 이메일 보내기
- 부적절한 컨텐트 신고
날짜: 11-21-2008 11:00 PM
날짜: 11-21-2008 11:00 PM
관련 event문의 ipmi_fpl
해당 서버에서 TOC(Transfer-Of-Control)가 발생된경우고요.
TOC는 사용자에 의해서나 서비스가드, OS 패닉 등에 의해 발생합니다.
사용자가 TOC 버튼이나 TC 커멘드를 이용하여 TOC를 발생
안시켰다면
서비스가드나 OS 패닉 등으로 TOC를 유발 시켰을테고요.
위의 로그가 생성된 시간으로 /var/adm/crash 에 덤프가
생성 되어 있을겁니다.
덤프 분석 하면 원인 확인 가능합니다
ps.아이테니움 계열은 TOC를 init 으로 표기 합니다.
TOC는 사용자에 의해서나 서비스가드, OS 패닉 등에 의해 발생합니다.
사용자가 TOC 버튼이나 TC 커멘드를 이용하여 TOC를 발생
안시켰다면
서비스가드나 OS 패닉 등으로 TOC를 유발 시켰을테고요.
위의 로그가 생성된 시간으로 /var/adm/crash 에 덤프가
생성 되어 있을겁니다.
덤프 분석 하면 원인 확인 가능합니다
ps.아이테니움 계열은 TOC를 init 으로 표기 합니다.
위에 명시된 의견은 Hewlett Packard Enterprise가 아닌 저자의 개인 의견입니다. 이 사이트를 사용하면 이용 약관에 동의하게되며 참여 규칙 .