Sun 6800 - SC's- neither are contactable!


 
Thread Tools Search this Thread
Operating Systems Solaris Sun 6800 - SC's- neither are contactable!
# 22  
Old 04-27-2009
Quote:
Originally Posted by sbk1972
yeap, will do. Difficult job to upgrade the firmware ?
No, no biggie. Just go through the appropriate steps in the README for your upgrade and you'll be fine.
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies

2. Solaris

d240 media tray is automatically restarting on sunfire 6800

d240 media tray(domain C) is which is connected to SUNFIRE 6800 (DOMAIN C),automatically restarting.remaining domains A and B are working fine..why i dont know..with out human intervention this domain is restarting automatically for 3 to 4 days in a day..plz solve this problem.why like this going... (4 Replies)
Discussion started by: tv.praveenkumar
4 Replies

3. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

4. Solaris

Sunfire 6800 / sol 8 / scadm

Good morning all Once again, I come seeking wisdom :-) I have a sunfire 6800 with two domains. Both Sc controllers are uncontactabe, probably due to network issues, but as the server is on a different site, Im a little stuck. So, am trying to use scadm, as I know I can view / configure... (7 Replies)
Discussion started by: sbk1972
7 Replies

5. UNIX for Dummies Questions & Answers

Sun Solaris 10: How do I create a bootup disc? The Sun website confuses me

Hey there, I am starting a Computer Science Foundation year at the end of this month and am trying to get a little bit ahead of the game. I have always wanted to learn Unix and am currently struggling with creating a boot disc to run Solaris (I have chosen to study this) from as opposed to... (0 Replies)
Discussion started by: Jupiter
0 Replies

6. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document... (1 Reply)
Discussion started by: shafeeq
1 Replies
Login or Register to Ask a Question
DMESG(1)						      General Commands Manual							  DMESG(1)

NAME
dmesg - print or control the kernel ring buffer SYNOPSIS
dmesg [-c] [-r] [-n level] [-s bufsize] DESCRIPTION
dmesg is used to examine or control the kernel ring buffer. The program helps users to print out their bootup messages. Instead of copying the messages by hand, the user need only: dmesg > boot.messages and mail the boot.messages file to whoever can debug their problem. OPTIONS
-c Clear the ring buffer contents after printing. -r Print the raw message buffer, i.e., don't strip the log level prefixes. -s bufsize Use a buffer of size bufsize to query the kernel ring buffer. This is 16392 by default. (The default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger than the default then this option can be used to view the entire buffer. -n level Set the level at which logging of messages is done to the console. For example, -n 1 prevents all messages, except panic messages, from appearing on the console. All levels of messages are still written to /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear. When the -n option is used, dmesg will not print or clear the kernel ring buffer. When both options are used, only the last option on the command line will have an effect. SEE ALSO
syslogd(8) AVAILABILITY
The dmesg command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/. DMESG(1)