- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Vpar Reboot
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 04:22 AM
тАО04-11-2007 04:22 AM
Vpar Reboot
with 4 vpars
one of then reboted automatically sending error messages to other 3 vpars
I am attaching the error messages for reference.
the vpar which booted did not give any coredump and did not have any syslog entry.
can anyone help me
Apr 11 16:06:50 vpcl EMS [2746]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179961859 -r /system/events/ipmi_fpl/ipmi_fpl -n 179961860 -a
Apr 11 16:07:02 vpcl cimserverd[2298]: cimserver[1833] not running, attempting restart
Apr 11 16:07:05 vpcl EMS [2746]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179961859 -r /system/events/ipmi_fpl/ipmi_fpl -n 179961861 -a
Apr 11 16:07:05 vpcl EMS [2746]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179961859 -r /system/events/ipmi_fpl/ipmi_fpl -n 179961862 -a
Apr 11 16:07:14 vpcl cimserver[8860]: Listening on HTTPS port 5989.
Apr 11 16:07:14 vpcl cimserver[8860]: Listening on local connection socket.
Apr 11 16:07:14 vpcl cimserver[8860]: Started HP-UX WBEM Services version A.02.00.11.
ARCHIVED MONITOR DATA:
Event Time..........: Wed Apr 11 16:06:50 2007
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 267
System..............: vpcl
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" :wor "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...: 10.39.141.19
Event Id............: 0x461cf98a00000000
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 rx8640
EMS Version.....................: A.04.20
STM Version.....................: C.54.00
System Serial Number............: DEH4641C3E
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#267
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: 0xf680007911e00000 0x0500000000000009
Time Stamp: Wed Apr 11 14:49:05 2007
Event keyword: INIT_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Implementation dependent data field
Decoded data field:
Reporting entity ID: 17 ( Cab 0 Cell 1 CPU 1 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 121 (0x79)
:TRUE :144@
Apr 11 16:06:50 vpcl EMS [2746]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179961859 -r /system/events/ipmi_fpl/ipmi_fpl -n 179961860 -a
Apr 11 16:07:02 vpcl cimserverd[2298]: cimserver[1833] not running, attempting restart
Apr 11 16:07:05 vpcl EMS [2746]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179961859 -r /system/events/ipmi_fpl/ipmi_fpl -n 179961861 -a
Apr 11 16:07:05 vpcl EMS [2746]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179961859 -r /system/events/ipmi_fpl/ipmi_fpl -n 179961862 -a
Apr 11 16:07:14 vpcl cimserver[8860]: Listening on HTTPS port 5989.
Apr 11 16:07:14 vpcl cimserver[8860]: Listening on local connection socket.
Apr 11 16:07:14 vpcl cimserver[8860]: Started HP-UX WBEM Services version A.02.00.11.
ARCHIVED MONITOR DATA:
Event Time..........: Wed Apr 11 16:06:50 2007
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 267
System..............: vpcl
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" :wor "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...: 10.39.141.19
Event Id............: 0x461cf98a00000000
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 rx8640
EMS Version.....................: A.04.20
STM Version.....................: C.54.00
System Serial Number............: DEH4641C3E
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#267
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: 0xf680007911e00000 0x0500000000000009
Time Stamp: Wed Apr 11 14:49:05 2007
Event keyword: INIT_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Implementation dependent data field
Decoded data field:
Reporting entity ID: 17 ( Cab 0 Cell 1 CPU 1 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 121 (0x79)
:TRUE :144@
ARCHIVED MONITOR DATA:
Event Time..........: Wed Apr 11 16:07:05 2007
Severity............: SERIOUS
Monitor.............: fpl_em
Event #.............: 548
System..............: vpcl
Summary:
OS legacy PA hex fault code (Bxxx)
Description of Error:
OS legacy PA hex fault code (Bxxx). Possible I/O error or system panic
Probable Cause / Recommended Action:
fault/panic
-
Additional Event Data:
System IP Address...: 10.39.141.19
Event Id............: 0x461cf99900000000
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 rx8640
EMS Version.....................: A.04.20
STM Version.....................: C.54.00
System Serial Number............: DEH4641C3E
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#548
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: 0xbf80033824e00000 0x000000000002ba00
Time Stamp: Wed Apr 11 14:49:07 2007
Event keyword: HP-UX_HEX_FAULT_CODE
Alert level name: Critical
Reporting vers: 1
Data field type: Legacy 20-bit PA HEX chassis code
Decoded data field: Legacy PA HEX Chassis Code = 0x2ba00
Reporting entity ID: 36 ( Cab 0 Cell 2 CPU 4 )
Reporting entity Full Name: HP-UX Kernel
IPMI Event ID : 824 (0x338)
Time S@
CURRENT MONITOR DATA:
Event Time..........: Wed Apr 11 16:07:05 2007
Severity............: MAJORWARNING
Monitor.............: fpl_em
Event #.............: 547
System..............: vpcl
Summary:
OS crashdump started (D700)
Description of Error:
OS crashdump started (D700)
Probable Cause / Recommended Action:
panic occurred
-
Additional Event Data:
System IP Address...: 10.39.141.19
Event Id............: 0x461cf99900000003
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 rx8640
EMS Version.....................: A.04.20
STM Version.....................: C.54.00
System Serial Number............: DEH4641C3E
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#547
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: 0x7f80033724e00000 0x00000000000ad700
Time Stamp: Wed Apr 11 14:49:09 2007
Event keyword: HP-UX_CRASHDUMP_STARTED
Alert level name: Warning
Reporting vers: 1
Data field type: Legacy 20-bit PA HEX chassis code
Decoded data field: Legacy PA HEX Chassis Code = 0xad700
Reporting entity ID: 36 ( Cab 0 Cell 2 CPU 4 )
Reporting entity Full Name: HP-UX Kernel
IPMI Event ID : 823 (0x337)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 05:29 AM
тАО04-11-2007 05:29 AM
Re: Vpar Reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 05:34 AM
тАО04-11-2007 05:34 AM
Re: Vpar Reboot
It also says the crash dump is stared.
Do you see the crash dump generated in /var/adm/crash?
If yes, log a sw support call with HP and get it analyzed to know the root cause.
Check /etc/shutdownlog, /var/adm/syslog/OLDsyslog.log, /var/tombstones for possible error messages related to the panic.
What version of Vpar you are using?
Are you upto date on the OS and Vpar recommended patches and firmware?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 09:26 PM
тАО04-11-2007 09:26 PM
Re: Vpar Reboot
sysname = HP-UX
release = B.11.23
version = U (unlimited-user license)
machine = ia64
Firmware info:
Firmware revision = 5.024
FP SWA driver revision: 1.18
IPMI is supported on this system.
BMC version: 2.4
vParProvider B.11.23.01.04 vPar Provider - HP-UX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2007 10:17 PM
тАО04-11-2007 10:17 PM
Re: Vpar Reboot
Firmware:
log on to the MP, change to the command menu and run "sysrev"
MP:CM> sysrev
vPar:
run swlist and grep for Virtual Partitions.
e.g.
T1335AC A.03.03.06 HP-UX Virtual Partitions
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!