Sponsored Content
Operating Systems Solaris Ldoms on T5220 with existing solaris 10 OS Post 302328267 by taran on Wednesday 24th of June 2009 01:37:58 AM
Old 06-24-2009
yes it's

install the correct firmware and ldom manager software ( maybe y need a reboot of the system )
 

8 More Discussions You Might Find Interesting

1. Solaris

Problem fixing e1000gx ni to 100fdx / Solaris 10 / T5220

Hello ! i'm facing an anoying problem during configuration of our new T5220 Enperise server. I've upgarded 'em with a pci-e ethernet expantion card for four additional networkinterfaces using the nxge drivers. i could fix them to 100 fdx rather simple by adding the following settings to the ... (6 Replies)
Discussion started by: moofoo
6 Replies

2. Solaris

LDOMs on T5220

We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid? I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies

3. Solaris

Migrating Solaris 8, 9 to Guest Domains (LDOMs)

Hi Everyone, one question is it possible to migrate a physical standalone Solaris 8 or 9 OS to Guest Domain (LDOMs). If yes, can someone please provide steps to migrate these OS to LDOMs. Thanks, Kartheek. (1 Reply)
Discussion started by: bobby320
1 Replies

4. Solaris

Booting Solaris LDOMS Control Domains

We are having a discussion on what order LDOMS and control domains should be booted. I think it should be LDOMS first then Control. Can anyone tell me why I am wrong or why I am right. Thanks, :confused: (6 Replies)
Discussion started by: aeroforce
6 Replies

5. Solaris

Trying to boot Solaris without hard drives in T5220

I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode. I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management. Tinkering around I... (4 Replies)
Discussion started by: nerdboy
4 Replies

6. Solaris

Install LDoms in T2000 running Solaris 11.2

Hi, im trying a lab with Solaris 11.2 in SunFire T2000 I read about know problem with ldomsmanager version. Solaris 11 comes with ldomsmanager 2.2 and T2000 needs 1.2. I need to install ldomsmanager version 1.2 but i donīt know why... i canīt find it at oracle site. I found oracle VM for SPARC... (0 Replies)
Discussion started by: MuziKizuM
0 Replies

7. Solaris

Help required with Solaris LDoms

System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. I am trying to figure out how to run these is multiple Virtual Machines (LDoms). Unfortunately I cannot find a tutorial so am using the Oracle VM Server for SPARC 3.4 Administration Guide; which is frustrating because it assumes a... (4 Replies)
Discussion started by: apmcd47
4 Replies

8. Solaris

Oracle DBA licensing on Solaris 11 LDOMS

My understanding is that Oracle DB licensing is based on number of cores etc. If you use virtual machines (e.g.ldoms) you need to partition it properly otherwise, in theory you have to pay based on the host machine. Can anyone confirm I'm right here? And explain it in bit more detail (i.e.... (8 Replies)
Discussion started by: psychocandy
8 Replies
REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME
reboot, poweroff, halt -- restarting, powering down and stopping the system SYNOPSIS
halt [-dlnpqvxz] poweroff [-dlnqvxz] reboot [-dlnqvxz] [arg ...] DESCRIPTION
The poweroff, halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM, wait for up to 30 seconds for them to die, send a SIGKILL to the survivors and, respectively, power down, halt or restart the system. The action is logged, including entering a shutdown record into the login accounting file and sending a message via syslog(3). The options are as follows: -d Create a dump before halting or restarting. This option is useful for debugging system dump procedures or capturing the state of a corrupted or misbehaving system. -l Suppress sending a message via syslog(3) before halting or restarting. -n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or a processor is on fire. -p Attempt to powerdown the system. If the powerdown fails, or the system does not support software powerdown, the system will halt. This option is only valid for halt. -v To enable verbose messages on the console, pass the boothowto(9) flag AB_VERBOSE to reboot(2). -x To enable debugging messages on the console, pass the boothowto(9) flag AB_DEBUG to reboot(2). -z To silence some shutdown messages on the console, pass the boothowto(9) flag AB_SILENT to reboot(2). -q Do not give processes a chance to shut down before halting or restarting. This option should not normally be used. If there are any arguments passed to reboot they are concatenated with spaces and passed as bootstr to the reboot(2) system call. The string is passed to the firmware on platforms that support it. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom. SEE ALSO
reboot(2), syslog(3), utmp(5), boot(8), init(8), rescue(8), shutdown(8), sync(8) HISTORY
A reboot command appeared in Version 6 AT&T UNIX. The poweroff command first appeared in NetBSD 1.5. CAVEATS
Once the command has begun its work, stopping it before it completes will probably result in a system so crippled it must be physically reset. To prevent premature termination, the command blocks many signals early in its execution. However, nothing can defend against delib- erate attempts to evade this. This command will stop the system without running any shutdown(8) scripts. Amongst other things, this means that swapping will not be dis- abled so that raid(4) can shutdown cleanly. You should normally use shutdown(8) unless you are running in single user mode. BUGS
The single user shell will ignore the SIGTERM signal. To avoid waiting for the timeout when rebooting or halting from the single user shell, you have to exec reboot or exec halt. BSD
February 16, 2011 BSD
All times are GMT -4. The time now is 01:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy