Sponsored Content
Full Discussion: rebooting HMC
Operating Systems AIX rebooting HMC Post 302622479 by zxmaus on Thursday 12th of April 2012 08:03:44 AM
Old 04-12-2012
your lpars will report the reboot potentially as sysplanar error in errpt
there are certain firmware levels on the hmc that might cause loss of lpar profiles / corruption

But either way - no need to bring down your lpars or the frame ... but make sure you have a backup of your configuration
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

soft rebooting

When I do a hard reboot, the system recognizes both the ttya and the ttyb, but when I do a hard reboot, it only doesn't recognize the ttyb. Is there a way I can fix this??? Thanks!:confused: (5 Replies)
Discussion started by: nattie_h
5 Replies

2. UNIX for Advanced & Expert Users

Problems when rebooting the system

Hi ! I am working on a server. We have ABAQUS installed on it. I added a compiler to .env file and added usr/local...../IMSL/... to the path. Then i restarted the computer and I get this error: when I am doing interactive option (Red hat Lunix OS) Start service local Yes/no/Continue? no... (1 Reply)
Discussion started by: dsmv
1 Replies

3. UNIX for Dummies Questions & Answers

Server rebooting frequently

O/P of the uname -a Server Server 4.0 3.0 3516 Pentium IV(TM)-ISA/PCI Server is getting rebooted frequetly... I don't know what is the problem in server ... Any help why the server is getting rebooted frequetly. Can i check what is the problem like in log files (5 Replies)
Discussion started by: srikanthus2002
5 Replies

4. Solaris

rebooting resetting loop

while installing unix solaris I found that one of the CD's is corupted so I bring another copy of solaris CD's and type reboot instead of 'reboot cdrom' then the server goes in infinite loop of rebooting resetting??I tried to use ctrl+break but didnt work....how can I break this loop....plz help?? (4 Replies)
Discussion started by: mm00123
4 Replies

5. Shell Programming and Scripting

Not able to 'su' to other user when rebooting the server

Hi All, I have created one script with starting letter 'S' (Example: Start) and stored in the path "/etc/rc.d/". This script was called automatically when we reboot the server. In this script i am using 'su' command to switch other user but it is not working, it giving some error. su... (2 Replies)
Discussion started by: Selva_Kumar
2 Replies

6. Linux

Rebooting Mounted servers

Hi All, We have two servers DSERV1(red hat 8.0) and DSERV2(scounix 3.2) where DSERV1 is the NFS server and DSERV2 is the NFS client. We want to reboot these servers and wanted to know the steps(precautions) we have to follow in order to do this. After reboot should we do anything specific to... (2 Replies)
Discussion started by: jisha
2 Replies

7. AIX

hmc not rebooting

Anyone faced this? I rebooted the HMC through command line after patch installation (hmcshutdown -t now -r) The strange thing happened was the hmc never rebooted, I was not able to connect it through graphical view or through ssh, but the session through which i issued the command was still... (4 Replies)
Discussion started by: balaji_prk
4 Replies

8. Solaris

error while rebooting box

I got following while whenver i reboot my box WARNING: add_spec: No major number for hpfc WARNING: add_spec: No major number for hpfc Error: Unable to init open counts. Kernel struct change? and hpfc is related to agilent fiber channel driver .. i do not know why it requires as i 've... (1 Reply)
Discussion started by: fugitive
1 Replies

9. Red Hat

Server rebooting unexpectedly

hi, I have been working on Solaris am very new to linux. My concern is as it goes....our server is getting rebooted automatically and I am not able to understand anything from the var log messages. Could anybody help me out in troubleshooting the issue. 2.6.18-128.el5 #1 x86_64 GNU/Linux is... (1 Reply)
Discussion started by: EmbedUX
1 Replies

10. What is on Your Mind?

Rebooting a career

Apologies if this is not the correct place to post this. I used to have a job supporting several custom applications that ran on Unix platforms. I used shell scripting, sed, awk, and SQL, but all on a pretty basic level. I also performed non-technical tasks like helping with project management,... (4 Replies)
Discussion started by: intranslation
4 Replies
prtconf(1M)															       prtconf(1M)

NAME
prtconf - print system configuration SYNOPSIS
/usr/sbin/prtconf [-V] | [-F] | [-x] | [-bpv] | [-acDPv] [dev_path] The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree. If a device path is specified on the command line for those command options that can take a device path, prtconf will only display informa- tion for that device node. The following options are supported: -a Display all the ancestors device nodes, up to the root node of the device tree, for the device specified on the command line. -b Display the firmware device tree root properties for the purpose of platform identification. These properties are "name", "compat- ible", "banner-name" and "model". -c Display the device subtree rooted at the device node specified on the command line, that is, display all the children of the device node specified on the command line. -D For each system peripheral in the device tree, displays the name of the device driver used to manage the peripheral. -F Returns the device path name of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SUNW,Ultra-30 is ffb, the command returns: /SUNW,ffb@1e,0:ffb0. This option could be used to create a symlink for /dev/fb to the actual console device. -p Displays information derived from the device tree provided by the firmware (PROM) on SPARC platforms or the booting system on platforms.The device tree information displayed using this option is a snapshot of the initial configuration and may not accu- rately reflect reconfiguration events that occur later. -P Includes information about pseudo devices. By default, information regarding pseudo devices is omitted. -v Specifies verbose mode. -V Displays platform-dependent PROM (on SPARC platforms) or booting system (on platforms) version information. This flag must be used by itself. The output is a string. The format of the string is arbitrary and platform-dependent. -x Reports if the firmware on this system is 64-bit ready. Some existing platforms may need a firmware upgrade in order to run the 64-bit kernel. If the operation is not applicable to this platform or the firmware is already 64-bit ready, it exits silently with a return code of zero. If the operation is applicable to this platform and the firmware is not 64-bit ready, it displays a descriptive message on the standard output and exits with a non-zero return code. The hardware platform documentation contains more information about the platforms that may need a firmware upgrade in order to run the 64-bit kernel. This flag overrides all other flags and must be used by itself. The following operands are supported: dev_path The path to a target device minor node, device nexus node, or device link for which device node configuration information is displayed The following exit values are returned: 0 No error occurred. non-zero With the -F option (SPARC only), a non-zero return value means that the output device is not a frame buffer. With the -x option, a non-zero return value means that the firmware is not 64-bit ready. In all other cases, a non-zero return value means that an error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ fuser(1M), modinfo(1M), sysdef(1M), attributes(5) Sun Hardware Platform Guide SPARC Only openprom(7D) The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in potentially all circumstances. The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use. On platforms, the use of prtconf -vp provides a subset of information from prtconf -v. The value of integer properties from prtconf -vp might require byte swapping for correct interpretation. 9 Aug 2005 prtconf(1M)
All times are GMT -4. The time now is 12:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy