Sponsored Content
Full Discussion: HPUX Boot failure.
Operating Systems HP-UX HPUX Boot failure. Post 302877219 by vbe on Friday 29th of November 2013 05:43:04 AM
Old 11-29-2013
So id you havent changed anything before the last reboot ( compiled a new kernel? ) then the message says it all
Code:
 WARNING: The BMC System Event Log (SEL) is full.
          Use MP SL command to clear space so SEL events can be recorded.

I never had to configure a RP3440 so I dont remember what its using (GSP or MP) The closest I got is a
Code:
ant:/home/vbe $ model
9000/800/L2000-54

having a gsp...
But both (gsp or mp) should work the same way, you may need to do some search...
On the console I used to type ctrl-B and I get to the gsp console which would display something like Service Processor Login: Since I never configured them I'd press <enter> and you get the GSP prompt: GDP > type h for help...
SL is for show log - I dont remember how you remove them ( Years since last time I went there...) maybe just looking at them sufiice... So look carefullly at the menu and the help...
Then you would type co to return to the OS console.. Its my supprt dispatch week so sorry cant spend more time with you... will try to follow though and if I have a moment...
Good Luck!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HP-UX respawning boot failure

Hello. System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below) From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Discussion started by: westcoast
2 Replies

2. Linux

Boot failure

Hi all I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
Discussion started by: joshighanshyam
2 Replies

3. Solaris

INT18 boot failure

I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
Discussion started by: priky
3 Replies

4. Solaris

Boot failure

I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot. SunOS Release 5.10 Version Generic_127128_11 32-bit Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved. Use... (3 Replies)
Discussion started by: Sesha
3 Replies

5. SCO

stage 1 boot failure: error loading hd (40)/boot

hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies

6. Debian

clusterKnoppix Live Cd boot failure

I'm trying to run clusterKnoppix live cd from a couple machines but it only works from one computer. The other three, my toshiba laptop, emachine, and hp machine can't find the filesystem.. the live cd stops booting and gives me a error saying it couldn't find knoppix filesystem and then gives me a... (0 Replies)
Discussion started by: iamhe
0 Replies

7. HP-UX

fail to boot HPUX

HPUX running in D-Class (L1000), pretty old HPUX version - hpux 11.00 Attempt 1 -- To boot from normal (primary) Unable to boot - system complains failure SYSTEM ALERT System Name : uninitialized DATE : 10/22/2011 Time : 03/41:12 Alert Level 15 = Fatal hardware or configuration... (12 Replies)
Discussion started by: ckwan
12 Replies

8. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

9. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
ipmievd(8)																ipmievd(8)

NAME
ipmievd - IPMI event daemon for sending events to syslog SYNOPSIS
ipmievd [-c|-h|-d N|-v|-V] -I open <open | sel> [<option>] ipmievd [-c|-h|-v|-V] -I lan -H <hostname> [-p <port>] [-U <username>] [-A <authtype>] [-L <privlvl>] [-a|-E|-P|-f <password>] [-o <oemtype>] [-O <sel oem>] sel [<option>] ipmievd [-c|-h|-v|-V] -I lanplus -H <hostname> [-p <port>] [-U <username>] [-L <privlvl>] [-a|-E|-P|-f <password>] [-o <oemtype>] [-O <sel oem>] [-C <ciphersuite>] sel [<option>] DESCRIPTION
ipmievd is a daemon which will listen for events from the BMC that are being sent to the SEL and also log those messages to syslog. It is able to run in one of two modes: either using the Event Message Buffer and asynchronous event notification from the OpenIPMI kernel driver or actively polling the contents of the SEL for new events. Upon receipt of an event via either mechanism it will be logged to syslog with the LOG_LOCAL4 facility. It is based on the ipmitool utility and shares the same IPMI interface support and session setup options. Please see the ipmitool manpage for more information on supported IPMI interfaces. OPTIONS
-a Prompt for the remote server password. -A <authtype> Specify an authentication type to use during IPMIv1.5 lan session activation. Supported types are NONE, PASSWORD, MD2, MD5, or OEM. -c Present output in CSV (comma separated variable) format. This is not available with all commands. -C <ciphersuite> The remote server authentication, integrity, and encryption algorithms to use for IPMIv2 lanplus connections. See table 22-19 in the IPMIv2 specification. The default is 3 which specifies RAKP-HMAC-SHA1 authentication, HMAC-SHA1-96 integrity, and AES-CBC-128 encryption algorightms. -E The remote server password is specified by the environment variable IPMI_PASSWORD. -f <password_file> Specifies a file containing the remote server password. If this option is absent, or if password_file is empty, the password will default to NULL. -h Get basic usage help from the command line. -H <address> Remote server address, can be IP address or hostname. This option is required for lan and lanplus interfaces. -I <interface> Selects IPMI interface to use. Supported interfaces that are compiled in are visible in the usage help output. -L <privlvl> Force session privilege level. Can be CALLBACK, USER, OPERATOR, ADMIN. Default is ADMIN. -m <local_address> Set the local IPMB address. The default is 0x20 and there should be no need to change it for normal operation. -o <oemtype> Select OEM type to support. This usually involves minor hacks in place in the code to work around quirks in various BMCs from vari- ous manufacturers. Use -o list to see a list of current supported OEM types. -O <sel oem> Open selected file and read OEM SEL event descriptions to be used during SEL listings. See examples in contrib dir for file format. -p <port> Remote server UDP port to connect to. Default is 623. -P <password> Remote server password is specified on the command line. If supported it will be obscured in the process list. Note! Specifying the password as a command line option is not recommended. -S <sdr_cache_file> Use local file for remote SDR cache. Using a local SDR cache can drastically increase performance for commands that require knowl- edge of the entire SDR to perform their function. -t <target_address> Bridge IPMI requests to the remote target address. -U <username> Remote server username, default is NULL user. -d N Use device number N to specify the /dev/ipmiN (or /dev/ipmi/N or /dev/ipmidev/N) device to use for in-band BMC communication. Used to target a specific BMC on a multi-node, multi-BMC system through the ipmi device driver interface. Default is 0. -v Increase verbose output level. This option may be specified multiple times to increase the level of debug output. If given three times you will get hexdumps of all incoming and outgoing packets. -V Display version information. If no password method is specified then ipmievd will prompt the user for a password. If no password is entered at the prompt, the remote server password will default to NULL. COMMANDS
help This can be used to get command-line help. It may also be placed at the end of commands to get option usage help. > ipmievd help Commands: open Use OpenIPMI for asyncronous notification of events sel Poll SEL for notification of events open This command starts ipmievd with the OpenIPMI event watching mechanism which relies on the Event Message Buffer feature of IPMI. This requires a properly installed and configured OpenIPMI driver on Linux and is only valid to be run through the open interface. See the ipmitool manpage and associated documentation for more information on setting up the OpenIPMI driver. Note: Some BMC do not support the Event Message Buffer required for this command. Other BMCs claim to support it but do not actu- ally deliver events to it. If this is the case please use the sel method. daemon Launch process as a daemon and reparent to init process. All messages will be sent to syslog. This is the default action. nodaemon Do NOT become a daemon, instead log all messages to stderr. pidfile=<filename> Save process ID to this file when in daemon mode. Defaults to /var/run/ipmievd.pidN (where N is the ipmi device number -- defaults to 0). sel This command starts ipmievd with the SEL Polling event watching mechanism. This will poll the SEL periodically to determine if new events have been logged. This command should work with all BMCs and is capable of using the LAN interface as well to monitor a remote system and log its events to a local syslog. daemon Launch process as a daemon and reparent to init process. All messages will be sent to syslog. This is the default action. nodaemon Do NOT become a daemon, instead log all messages to stderr. pidfile=<filename> Save process ID to this file when in daemon mode. Defaults to /var/run/ipmievd.pidN (where N is the ipmi device number -- defaults to 0). timeout=<seconds> Time between checks for SEL polling method. Default is 10 seconds. EXAMPLES
Example 1: Daemon process watching OpenIPMI for events > ipmievd -I open open daemon Example 2: Local non-daemon process checking remote SEL every 30 seconds > ipmievd -I lan -H 1.2.3.4 -f passfile sel nodaemon timeout=30 Reading Sensors... Waiting for Events... AUTHOR
Duncan Laurie <duncan@iceblink.org> SEE ALSO
IPMItool Homepage http://ipmitool.sourceforge.net Intelligent Platform Management Interface Specification http://www.intel.com/design/servers/ipmi OpenIPMI Homepage http://openipmi.sourceforge.net Duncan Laurie ipmievd(8)
All times are GMT -4. The time now is 12:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy